Application sharing processing method and apparatus, computer device, and storage medium

Abstract

The application relates to a processing method and device for application sharing, computer equipment, a storage medium and a computer program product. The method comprises the following steps: displaying an application identifier of at least one target application to be shared corresponding to a member account of a target organization; displaying a sharing member range for the target application, wherein the sharing member range comprises a plurality of sharing member accounts, and the plurality of sharing member accounts belong to a cooperative organization which has a cooperative relationship with the target organization; and in response to a confirmation operation on the target application and the sharing member range, adding an application entrance of the target application in an application accommodation area of each group of sharing member accounts divided from the sharing member range. The method can effectively improve the processing efficiency of sharing the target application to the sharing member accounts in the cooperative organization.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an application-sharing processing method, apparatus, computer device, storage medium, and computer program product. Background Technology

[0002] With the development of computer technology, collaborative work has become an important way to improve office efficiency. Instant messaging applications provide a platform for communication among members of an organization and allow them to access specific applications and perform specific functions within the instant messaging application. For different members to interact based on a specific application, each member needs to have that application added to their instant messaging application.

[0003] However, when there are many members who may need to interact based on the same application and these members do not belong to the same organization, the data processing volume is large when adding the application to each member account of different organizations in an instant messaging application, which leads to the problem of low data processing efficiency. Summary of the Invention

[0004] Therefore, it is necessary to provide a processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product for application sharing that can improve data processing efficiency in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a method for processing application sharing. The method includes:

[0006] For each member account of the target organization, display the application identifier of at least one target application to be shared;

[0007] Displays the scope of shared members for the target application, which includes multiple shared member accounts belonging to a partner organization that has a cooperative relationship with the target organization;

[0008] In response to the confirmation operation of the target application and the shared member scope, for each group of shared member accounts divided from the shared member scope, the application entry of the target application is asynchronously added to the application containment area of ​​each of the shared member accounts in the same group.

[0009] Secondly, this application also provides an application-sharing processing apparatus, the apparatus comprising:

[0010] The application display module is used to display the application identifier of at least one target application to be shared, corresponding to the member account of the target organization.

[0011] The scope display module is used to display the scope of shared members for the target application. The scope of shared members includes multiple shared member accounts, which belong to a cooperative organization that has established a cooperative relationship with the target organization.

[0012] The application sharing module is used to respond to the confirmation operation of the target application and the shared member scope, and asynchronously add the application entry of the target application to the application containing area of ​​each group of shared member accounts in the same group of shared member accounts for each group of shared member accounts.

[0013] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0014] For each member account of the target organization, display the application identifier of at least one target application to be shared;

[0015] Displays the scope of shared members for the target application, which includes multiple shared member accounts belonging to a partner organization that has a cooperative relationship with the target organization;

[0016] In response to the confirmation operation of the target application and the shared member scope, for each group of shared member accounts divided from the shared member scope, the application entry of the target application is asynchronously added to the application containment area of ​​each of the shared member accounts in the same group.

[0017] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0018] For each member account of the target organization, display the application identifier of at least one target application to be shared;

[0019] Displays the scope of shared members for the target application, which includes multiple shared member accounts belonging to a partner organization that has a cooperative relationship with the target organization;

[0020] In response to the confirmation operation of the target application and the shared member scope, for each group of shared member accounts divided from the shared member scope, the application entry of the target application is asynchronously added to the application containment area of ​​each of the shared member accounts in the same group.

[0021] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0022] For each member account of the target organization, display the application identifier of at least one target application to be shared;

[0023] Displays the scope of shared members for the target application, which includes multiple shared member accounts belonging to a partner organization that has a cooperative relationship with the target organization;

[0024] In response to the confirmation operation of the target application and the shared member scope, for each group of shared member accounts divided from the shared member scope, the application entry of the target application is asynchronously added to the application containment area of ​​each of the shared member accounts in the same group.

[0025] The aforementioned application sharing processing method, apparatus, computer equipment, storage medium, and computer program product, through member accounts corresponding to the target organization, displays an application identifier of at least one target application to be shared, as well as a sharing member scope for the target application. The sharing member scope includes multiple sharing member accounts belonging to cooperative organizations that have established cooperative relationships with the target organization. This facilitates adding shareable applications from the target organization to the member accounts of the cooperative organizations within that target organization. In response to a confirmation operation on the target application and the sharing member scope, for each group of sharing member accounts divided from the sharing member scope, the application entry point of the target application is asynchronously added to the application containment area of ​​each group of sharing member accounts. Processing within each group can be synchronous, and processing within the same group can be asynchronous, thereby enabling asynchronous and parallel addition of the target application to the sharing member accounts within the cooperative organization. This effectively improves the processing efficiency of sharing the target application to the sharing member accounts within the cooperative organization. Attached Figure Description

[0026] Figure 1 This is an application environment diagram for applying a shared processing method in one embodiment;

[0027] Figure 2 This is a flowchart illustrating the application of a shared processing method in one embodiment;

[0028] Figure 3 This is a schematic diagram illustrating the page changes of upstream and downstream entities created and joined by the target organization in one embodiment.

[0029] Figure 4 This is a schematic diagram showing a page of a shared application in one embodiment;

[0030] Figure 5This is a schematic diagram illustrating page changes when selecting the shared member scope of a target application in one embodiment;

[0031] Figure 6 This is a diagram illustrating the interaction process of a shared application in one embodiment;

[0032] Figure 7 This is a schematic diagram of a page where the target application is added asynchronously in one embodiment;

[0033] Figure 8 This is an interactive diagram illustrating the modification of the shared state in one embodiment;

[0034] Figure 9 This is a schematic diagram illustrating the page changes during the authorization process for an administrator of a collaborative organization in one embodiment.

[0035] Figure 10 This is a schematic diagram illustrating the page changes when selecting a target application in one embodiment;

[0036] Figure 11 This is a schematic diagram illustrating the interaction for canceling a shared application in one embodiment;

[0037] Figure 12 This is an interactive diagram illustrating the adjustment of the scope of shared members in one embodiment;

[0038] Figure 13 This is a schematic diagram of a page displaying a prompt message for a target application in one embodiment;

[0039] Figure 14 This is an interactive diagram illustrating the application sharing status and the scope of shared members in one embodiment;

[0040] Figure 15 This is a flowchart illustrating the application of a shared processing method in another embodiment;

[0041] Figure 16 This is a structural block diagram of a shared processing device used in one embodiment;

[0042] Figure 17 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0044] The application sharing processing method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, terminals 102, 106, and 108 communicate with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or located in the cloud or on another server. Members of organization X can log in to the instant messaging application client via terminal 102, and members of organization Y can log in via terminals 106 and 108. They can access the same application by accessing the application entry points added in the instant messaging application client, facilitating information exchange or collaborative task processing among members of different organizations. They can also access other applications through the instant messaging application and utilize the functions provided by other applications to perform various data processing tasks, thereby improving data processing efficiency and the convenience of interaction between members of different organizations.

[0045] like Figure 1 As shown, account A belongs to organization X, and accounts B and C belong to organization Y. Organization X and organization Y have a cooperative relationship. Accounts A, B, and C need to collaborate through the target application M. Terminal 102 is where account A is located, terminal 106 is where account B is located, and terminal 108 is where account C is located. Accounts A, B, and C log into the instant messaging application client through different terminals. On terminal 102, where account A is logged in, at least one target application to be shared with at least a portion of members in organization Y is displayed, along with the scope of shared members for the target application. Specifically, the scope of shared members can be organization Y, at least a portion of departments within organization Y, or at least a portion of member accounts within at least a portion of departments in organization Y. Taking accounts B and C as two of the multiple shared member accounts included in the shared member scope as an example, in response to account A's confirmation operation on the target application and the shared member scope, when accounts B and C in the shared member scope are grouped together, the application entry for the target application is asynchronously added to the application area of ​​each account B and account C. For example... Figure 1 As shown, the time when the application entry for adding the target application is displayed on terminal 106 is later than the time when the application entry for the target application is displayed on terminal 108.

[0046] Among them, terminals 102, 106, and 108 can be, but are not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, aircraft, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. Server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0047] In one embodiment, such as Figure 2As shown, an application sharing processing method is provided. Taking the application of this method to a computer device as an example, the computer device can be... Figure 1 The method specifically includes the following steps:

[0048] Step 202: For the member account of the target organization, display the application identifier of at least one target application to be shared.

[0049] In this context, a target organization is a social group organized according to specific purposes, tasks, and forms. An organization comprises multiple members and can be distinguished from other organizations by its name, registration code, and other identifying features. These members can be organized according to a specific organizational structure or exist as independent individuals. For example, the target organization can be a company with an organizational structure or an independent group. For instance, a target organization might have 500 members, numbered 1 to 500. Members numbered 1 to 100 belong to sub-department A, 101 to 200 to sub-department B, 201 to 300 to sub-department C, 301 to 400 to sub-department D, and 401 to 500 to sub-department E. Sub-departments A, B, and C belong to secondary department M, and sub-departments D and E belong to secondary department N. Secondary departments M and N belong to target organization X. As another example, target organization X might include members numbered 1 to 500, with each member directly subordinate to target organization X.

[0050] A member account is an account used by members of a target organization to log in to a designated platform. This account identifies the member's organizational membership on that platform. This platform can be an instant messaging application, an application that enables interaction over a network. Instant messaging applications can be web applications or applications installed on a terminal. Specifically, the instant messaging application can be an enterprise-level office application associated with the organization. Each member of the organization can log in to this instant messaging application using their member account to engage in one-on-one or group conversations with other members within the organization or with members of other organizations. They can also interact with the target application through the application entry point within the instant messaging application. For example, the instant messaging application might only allow one member account to be online at a time. If a user belongs to multiple different organizations, they can switch between member accounts corresponding to different organizations to log in. For instance, user Zhang San belongs to both organization A and organization B, meaning he has member account 'a' for organization A and member account 'b' for organization B. When Zhang San logs in to the instant messaging application using member account 'a' and enters the conversation page corresponding to organization A, he can switch his login account to member account 'b' using the organization switching operation to enter the conversation page corresponding to organization B. Specifically, a member account in the target organization can be any account within the target organization, meaning any member account in the target organization has application sharing permissions. A member account in the target organization can also be an administrator account within the target organization that has application sharing permissions. This administrator account can be an account with administrative permissions for the entire target organization, or an account with application management permissions configured only for the target organization and its partner organizations.

[0051] A target application is an application accessible to the target organization's member accounts and shared with members of the collaborating organization. Sharing the target application with collaborating organization members adds application entry points to at least a portion of the collaborating organization's member accounts for direct access, enabling members of the target organization and collaborating organization to collaborate and interact based on the target application. Specifically, a target application can be a subroutine running in the instant messaging application's runtime environment, an application installed on a terminal, or a web application. An application identifier is used to identify different applications and can be at least one of the following: application name, application icon, etc. Specifically, a target application can be one or more applications selected from multiple shareable applications. Shareable applications are those that the target organization's member accounts have sharing permissions for but are not shared with collaborating organizations. Within a specific application, the application entry point added to the instant messaging application represents applications authorized by organization members, address book applications, encrypted applications, standalone applications, applications in the testing phase, shared applications, deactivated applications, installed third-party applications, and applications built by the target organization itself. Installed third-party applications and applications built by the target organization are shareable applications.

[0052] Specifically, on a terminal, a user logs into the instant messaging application client using a member account of the target organization and accesses the application page. The client responds to the shared application addition operation triggered by the member account on the instant messaging application page, displaying the application identifier of at least one application to be shared. When there are multiple applications to be shared, multiple application identifiers matching each application are displayed.

[0053] Step 204: Display the scope of shared members for the target application. The scope of shared members includes multiple shared member accounts, which belong to partner organizations that have established a cooperative relationship with the target organization.

[0054] In this context, a cooperative organization is a group of organizations that has established a cooperative relationship with a target organization. Similar to the target organization, members of a cooperative organization can be divided according to a certain organizational structure or can be independent individuals. For example, a cooperative organization can be a company with an organizational structure or an independent group. Specifically, a cooperative organization and a target organization that have established a cooperative relationship can be two organizations that have joined the same organizational space, where the target organization is the creator of that organizational space and the cooperative organization is the joiner. In specific applications, the target organization can be an upstream organization that creates upstream and downstream relationships, such as an upstream distributor or brand owner in the collaboration process. A cooperative organization can be a downstream organization that joins the upstream and downstream relationships created by the upstream organization and collaborates and communicates with the upstream organization; a cooperative organization can specifically be a supplier. In specific applications, an upstream organization can have multiple downstream organizations and collaborate with multiple downstream organizations. For an organization A, it can either join the upstream and downstream relationships created by the upstream organization S, becoming a downstream organization of upstream organization S, or it can create its own upstream and downstream relationships, becoming an upstream organization of a downstream organization H that joins that upstream and downstream relationship.

[0055] The shared member scope is used to characterize the set of shared objects within a collaborative organization that serve as the target application. The specific shared member scope can be determined based on the scope selection granularity, which can be based on the collaborative organization's organizational structure. The scope selection granularity can include the collaborative organization, its departments, members within those departments, and members of the entire collaborative organization. The shared member scope is selected using member accounts within the target organization. When the scope selection granularity for a member account is set to "members," the displayed shared member scope is the shared member identifier. Each shared member identifier corresponds one-to-one with a shared member account, representing a unique organizational member. For example, when the target organization selects all members of collaborative organizations A, B, and C as the target application's shared objects, the displayed shared member scope includes the first organizational identifier of selected collaborative organization A, the second organizational identifier of collaborative organization B, and the third organizational identifier of collaborative organization C. For example, when the target organization selects shared objects for the application, including cooperative organization A, department B1 in cooperative organization B, and members c01 to c20 in cooperative organization C, the displayed range of shared members includes the first organization identifier of the selected cooperative organization A, the department identifier of department B1 in cooperative organization B, and the member identifiers of members c01 to c20 in cooperative organization C. For ease of description, the following embodiments use one cooperative organization as an example.

[0056] A shared member account is a member account within a collaborative organization that serves as a shared object for a target application; it is the smallest unit within the scope of shared members. A shared member account can be a subset of member accounts within the collaborative organization, or it can be all member accounts of the organization. The specific number of shared member accounts can be determined based on the chosen scope of shared members.

[0057] Specifically, on the application page of the instant messaging application logged in by the member account of the target organization, the scope of shared members selected from the cooperative organization according to the organizational structure of the cooperative organization is displayed. This is to add the application entry of the target application to the application area of ​​each shared member account in the scope of shared members, so that the shared member account can access the target application through the application entry and realize specific collaboration with the members of the target organization.

[0058] In a specific application, such as Figure 3 As described, member accounts of the target organization can access the instant messaging application's workbench, where a "Upstream / Downstream" function card is displayed. When a member account clicks the "Upstream / Downstream" function card, the instant messaging application client displays the upstream and downstream partners created by the target organization, as well as those already joined. When a member account selects one of the upstream or downstream partners, such as Upstream / Downstream 1, ... Figure 4 As shown, entering the details page of Upstream / Downstream 1 displays the number of members and enterprises included in Upstream / Downstream 1. The page also allows setting the person in charge for Upstream / Downstream 1 for management purposes. The details page further displays the shared applications and trigger entries for adding applications within Upstream / Downstream 1. Clicking the "Shared Application" control on the details page leads to the shared application page, which displays a list of shared applications and an entry point for viewing each application, facilitating the viewing and management of shared applications. The instant messaging application client responds to member accounts within the target organization by clicking "Add Application," allowing selection of the target application and the scope of sharing members. For example... Figure 5 As shown, the target applications selected by the member accounts of the target organization are Application 1 and Application 2, and the selected shared member scope is Company B and the first-level distributor.

[0059] Step 206: In response to the confirmation operation of the target application and the scope of shared members, for each group of shared member accounts divided from the scope of shared members, the application entry of the target application is added asynchronously in the application containment area of ​​each shared member account in the same group.

[0060] The confirmation action is triggered by a member account within the target organization and is used to determine the target application and the scope of sharing members. Specifically, the confirmation action can be triggered after confirming the target application and the scope of sharing members, or after confirming the scope of sharing members and the target application, or simultaneously. The confirmation action can be triggered by a confirmation button, and the specific triggering method can be configured according to actual needs, such as clicking, double-clicking, long-pressing, swiping, or controlling the cursor to hover over the confirmation button's display area for a preset duration. For example, on the application page of an instant messaging application, application identifiers 1 to 9 that can be shared are first displayed. In response to the member account of the target organization selecting application identifier 2 from application identifiers 1 to 9, the selection options for the scope of shared members for the target application represented by application identifier 2 are displayed. The selection options for the scope of shared members can include cooperative organization A and cooperative organization B. In response to the member account of the target organization selecting the organization identifier of cooperative organization A and the department identifier of department b1 in cooperative organization B, the instant messaging application client switches the organization identifier of cooperative organization A and the department identifier of department b1 in cooperative organization B from an unselected state to a selected state, and displays a shared member scope confirmation button that is in a triggerable state. In response to the member account of the target organization triggering the shared member scope confirmation button, all members of cooperative organization A and members of department b1 in cooperative organization B are identified as shared member accounts.

[0061] The shared member scope includes multiple shared member accounts. To improve the processing efficiency of adding application entry points for target applications within shared member accounts, these shared member accounts are divided into multiple groups. Specifically, the division into multiple groups can be based on the number of groups, organizational structure, or random allocation.

[0062] The application containment area is the area within an instant messaging application used to contain the entry point for applications granted access permissions. This area can be a portion of one of the multiple main pages corresponding to the menu bar within the instant messaging application. For example, when a shared member account accesses the target page via the "Workbench" tab in the menu bar, the application containment area is displayed on that page. This allows the user corresponding to the shared member account to quickly access the target application within the instant messaging application, facilitating access to that application.

[0063] Asynchronous addition of the target application's entry point refers to adding the target application's entry point sequentially to the application containment areas of each shared member account within the same group. For example, if the shared member accounts in the same group include accounts 1 to N (N is a positive integer, N≥2), all N shared member accounts have the target application's entry point added to their respective application containment areas, but the addition times for these entry points differ. Furthermore, for multiple shared member accounts belonging to different groups, the addition times for the target application's entry point in their respective application containment areas can be the same or different.

[0064] The application entry point is one of the triggers for users to access the target application. By responding to a trigger action on the application entry point, users can enter the application page corresponding to the target application. The application entry point can also be a shortcut that matches the target application. By responding to a trigger action on the application entry point, users can enter the application interface of the target application.

[0065] Specifically, in response to the confirmation operation of the target organization's member account on the target application and the shared member scope, the instant messaging application client sends a sharing request for the target application to the instant messaging application server. The sharing request carries information corresponding to the shared member scope. The instant messaging application server groups multiple shared member accounts from the shared member scope, and adds the target application to each group of shared member accounts according to the divided groups. In the application area of ​​each shared member account in the same group, the application entry of the added target application is displayed asynchronously.

[0066] In practical applications, the target organization is the upstream enterprise, and the collaborating organization is the downstream enterprise. At least some members of the upstream enterprise and at least some members of the downstream enterprise join the same upstream / downstream space. The administrator of the upstream enterprise selects the target application to be shared and the scope of application sharing within the downstream enterprise on the application page of the instant messaging application; that is, the organizational members within the downstream enterprise who need to share the target application. The sharing process is as follows: Figure 6 As shown, after receiving the target application and application sharing scope reported by the instant messaging application client, the instant messaging application server retrieves the downstream enterprises participating in the upstream and downstream spaces, as well as the departments and members of each enterprise that have joined the upstream and downstream spaces. The instant messaging application server asynchronously initializes and installs the application task for each member in the application sharing scope of the downstream enterprise, and at the same time, sets the members and departments of the downstream enterprise participating in the upstream and downstream spaces as the application visibility scope of the target application.

[0067] In a specific application, such as Figure 7As shown, Account A and Account B are two shared member accounts grouped together. The target applications are Application 1 and Application 2. The application entry of the added target application is displayed in the application area of ​​Account A, which is displayed later than the application entry of the added target application in the application area of ​​Account B. In actual application, the time difference between asynchronously displaying the application entry of the added target application among the various shared member accounts in the same group can be very small.

[0068] The aforementioned application sharing method displays the application identifier of at least one target application to be shared, as well as the sharing member scope for the target application, corresponding to the member accounts of the target organization. The sharing member scope includes multiple sharing member accounts belonging to cooperative organizations that have established cooperative relationships with the target organization. This facilitates adding shareable applications from the target organization to the member accounts of the cooperative organizations that are part of the target organization. In response to the confirmation operation of the target application and the sharing member scope, for each group of sharing member accounts divided from the sharing member scope, the application entry of the target application is asynchronously added to the application containment area of ​​each group of sharing member accounts. The processing of each group can be performed synchronously, and the processing within the same group can be performed asynchronously, so as to realize the asynchronous and parallel addition of the target application to the sharing member accounts of the cooperative organization, thereby effectively improving the processing efficiency of sharing the target application to the sharing member accounts of the cooperative organization.

[0069] In some embodiments, in response to a confirmation operation on the target application and the shared member scope, for each group of shared member accounts divided from the shared member scope, an application entry for the target application is asynchronously added to the application containment area of ​​each shared member account in the same group, including:

[0070] In response to the confirmation operation for the target application and the scope of shared members, multiple shared member accounts in the scope of shared members are randomly assigned to multiple queues. For each queue, the same target application addition process is performed on each shared member account in the queue in sequence, so that the application entry of the target application is added asynchronously in the application containment area of ​​the shared member accounts belonging to the same queue.

[0071] A queue is a first-in, first-out (FIFO) linear list. Queues allow element removal from the front and insertion from the back. The end where insertion occurs is called the tail, and the end where removal occurs is called the head. The data elements in a queue are called queue elements. Inserting an element into a queue is called enqueueing, and removing an element is called dequeueing. The element that entered the queue earliest is removed first. In each queue, for shared member accounts that are the entry point for the target application, they are inserted from the tail. The processor sequentially adds each shared member account to the queue using the same target application method, and then removes the added shared member account from the head of the queue.

[0072] Specifically, the addition of target applications for shared member accounts in each queue can be implemented using coroutines. A coroutine is equivalent to a user-mode thread; thread scheduling is handled by the operating system, while coroutine scheduling is controlled by the user. Compared to processes, threads have faster context switching and lower resource overhead. Coroutines run within threads and are scheduled by a user-mode scheduler, eliminating the need for repeated system calls and leveraging the concurrency advantages of threads, resulting in higher execution efficiency. The processor randomly assigns multiple shared member accounts from the shared member scope to multiple queues, and each queue uses a coroutine to handle the addition of target applications for each shared member account, effectively reducing data processing resource overhead and improving data processing efficiency.

[0073] In this embodiment, the scope of shared members includes multiple shared member accounts. By creating multiple queues, each queue synchronously executes the addition processing of target applications for the shared member accounts, which can effectively improve data processing efficiency. At the same time, the addition processing of target applications for each shared member account in the same queue is asynchronous, which can avoid the excessive data processing load caused by centralized data processing and improve the utilization of processing resources.

[0074] In some embodiments, in response to a confirmation operation on the target application and the shared member scope, for each group of shared member accounts divided from the shared member scope, an application entry for the target application is asynchronously added to the application containment area of ​​each shared member account in the same group, including:

[0075] In response to the confirmation operation for the target application and the scope of shared members, an application authorization message for the target application is sent to the administrator account of the cooperating organization. In response to the administrator account's authorization confirmation operation for the application authorization message, the application entry of the target application is asynchronously added to the application containment area of ​​each of the shared member accounts in the same group within the scope of shared members.

[0076] In this context, the administrator account of a collaborative organization is an account with administrative privileges over members within the organization. There can be one or more administrator accounts. When there are multiple administrator accounts, in response to any one of these accounts confirming the application authorization message, the shared member accounts within the collaborative organization are added to the list of accounts authorized to access the target application. The application authorization message prompts the administrator of the collaborative organization to authorize the target application. This message may include authorization prompts and operation buttons, including a confirm authorization button and a deny authorization button. When the administrator account of the collaborative organization presses the confirm authorization button, the authorization operation for the target application is triggered. The authorization confirmation operation is the authorization action for the target application indicated in the application authorization message. Specifically, it may be triggered by pressing the confirm authorization button in the application authorization message.

[0077] In practical applications, when a member account of the target organization sends an application authorization message for the target application to the administrator account of the collaborating organization, if no authorization confirmation or denial operation is detected from the administrator account within a preset time period, the application entry for the target application can be added directly to the shared member accounts within the shared member scope. When a shared member account accesses the target application indicated by the application entry for the first time, the authorization message for that target application will be displayed. If, after a member account of the target organization sends an application authorization message for the target application to the administrator account of the collaborating organization, the administrator account triggers a denial operation by clicking the denial button, the application sharing process for the shared member accounts of the collaborating organization will be canceled.

[0078] Furthermore, in response to the confirmation operation of the target organization's member account regarding the target application and the shared member scope, the instant messaging application client sends an application authorization message for the target application to the administrator account of the collaborating organization. On the display page of the instant messaging application client logged into by the administrator account of the collaborating organization, the application authorization message and a confirmation button are displayed. In response to the authorization confirmation operation triggered by the administrator account clicking the confirmation button, the instant messaging application client authorizes the application for the shared member accounts within the shared member scope. This allows shared member accounts within the shared member scope to directly access the target application through the application entry point after adding the target application's entry point to the application's containment area, eliminating the need for each shared member account to separately authorize the target application. This improves operational convenience and effectively saves data processing resources during the authorization process. Figure 8 As shown, after obtaining authorization from the administrator of the cooperative organization, the sharing status of shared member accounts in the cooperative organization can be adjusted, and application entry points for the target application can be added.

[0079] In a specific application, such as Figure 9 As shown, the target organization is upstream company A. Company A's member accounts share application 1 with downstream company B. Company B's administrator receives an authorization message for application 1 and displays an authorization message card. The instant messaging application client responds to the authorization message card triggered by Company B's administrator and displays the authorization details page for application 1. The authorization details page displays the authorization details information for application 1 and an authorization confirmation button. By triggering the authorization confirmation button, unified authorization can be granted to all members of Company B involved in the upstream and downstream processes.

[0080] In this embodiment, by sending the application authorization message of the target application to the administrator account of the cooperative organization, the same authorization for the target application can be achieved for all shared member accounts within the scope of the cooperative organization. This enables unified authorization for different shared member accounts, centralized data processing, and avoids the fragmented data processing that would otherwise occupy data processing resources for a long time. This effectively improves the centralized utilization rate of data processing resources.

[0081] In some embodiments, the application sharing processing method further includes: in response to the first access operation triggered by the shared member account for the added application entry in the application containment area, displaying the authorization message of the target application; and in response to the authorization operation triggered by the shared member account in response to the authorization message, displaying the application page of the target application.

[0082] Specifically, when the administrator of a collaborating organization fails to authorize or deny authorization for the target application within a specified time, or when the collaborating organization has not set up an administrator, the application entry point for the target application can be directly added to the application storage area of ​​the shared member account within the collaborating organization. The first access operation refers to the first access operation to the target application indicated by the application entry point. When a shared member account accesses the target application for the first time through the application entry point, authorization is not yet processed. The authorization message for the target application is displayed on the shared member account's display page to ensure that subsequent accesses can directly enter the target application's application page through the application entry point. The target application's application page is the interactive page provided by the target application, allowing users to interact with the application to achieve its corresponding functions.

[0083] In a specific application, when a shared member account accesses the target application for the first time, the user logs into the instant messaging application client through the shared member account. The application's application page displays the application's containment area, and the newly added application entry for the target application is displayed in the application's containment area. In response to the shared member account's first access operation for the newly added application entry, the instant messaging application client displays the target application's authorization message. In response to the authorization operation triggered by the shared member account's authorization message, the instant messaging application client enters the target application's application page.

[0084] In this embodiment, by instructing the shared member account to authorize the target application when the shared member account accesses the target application for the first time, it is possible to effectively avoid the need for the shared member account to agree to obtain account information before accessing the application and processing data each time the target application is accessed. This effectively reduces the operational complexity of subsequent accesses to the target application and improves interaction efficiency.

[0085] In some embodiments, each application sharing operation of a member account within a target organization can achieve the sharing of one target application, or the sharing of two or more target applications. For sharing two or more target applications simultaneously, the process can be either sequential or combined. Sequential processing involves sharing the previous target application to each sharing member account before sharing the next target application. Combined processing treats the at least two target applications as a whole, and the process of adding application entries for the target application to each sharing member account within the same group is asynchronous. The process of adding application entries for the at least two target applications to the previous sharing member account within the same group is executed only after the previous sharing member account has completed adding application entries for the at least two target applications.

[0086] Specifically, taking the number of target applications to be shared as at least two as an example, the process of adding application entry points for the target applications includes: for each sharing member account, simultaneously adding application entry points for at least two target applications in the application accommodation area of ​​the sharing member account.

[0087] In a specific application, a member account of the target organization selects Application 1 and Application 2 as the target applications to be shared, and selects a sharing member account A of the collaborating organization as one of the application sharing objects. After the member account of the target organization triggers the confirmation sharing operation, the newly added Application 1 entry 1 and Application 2 entry 2 will be displayed simultaneously in the application containing area of ​​the sharing member account A of the collaborating organization. Specifically, after the member account of the target organization triggers the confirmation sharing operation, it also includes sending application authorization information for Application 1 and Application 2 to the administrator account of the collaborating organization. The administrator account of the collaborating organization can grant authorization to Application 1 and Application 2 with one click, or authorize Application 1 and Application 2 separately, or authorize one of Application 1 and Application 2.

[0088] In this embodiment, by adding application entry points to two or more target applications simultaneously, the number of times entry points are added to the application area of ​​the shared member account can be reduced, thus reducing the number of interactions with the same shared member account and providing users with an intuitive experience of adding two or more target applications at once.

[0089] In some embodiments, corresponding to a member account of the target organization, displaying at least one application identifier of a target application to be shared includes: in response to an application sharing event triggered by a member account of the target organization, displaying candidate application identifiers of shareable applications in the target organization; and in response to a selection operation on at least one target application identifier among the candidate application identifiers, displaying at least one target application identifier as selected.

[0090] The application sharing event refers to the time when the process of configuring application sharing parameters is triggered. Specifically, an "Application Sharing" entry point can be displayed in the menu bar of the instant messaging application. Member accounts of the target organization can access the application sharing parameter configuration page by clicking the "Application Sharing" entry point. On the application sharing parameter configuration page, application icons of applications that can be shared by member accounts of the target organization are displayed. Each shareable application icon represents an application whose application entry has been added to the application area of ​​at least some members of the target organization. This allows sharing member accounts of the collaborating organization to directly access the application entry and collaborate with at least some members of the target organization after adding the application entry to the shared target application. The application sharing parameter configuration page also displays the organization icons of collaborating organizations that have established cooperative relationships with the target organization. Member accounts of the target organization can select at least some members from the collaborating organizations to share the target application.

[0091] Specifically, the instant messaging application client responds to the application sharing event triggered by a member account of the target organization, and displays the application sharing parameter configuration page, such as... Figure 10As shown, on the application sharing parameter configuration page, candidate application identifiers of shareable applications in the target organization are displayed. At this time, the display status of the candidate application identifiers is unselected. In response to the member account of the target organization selecting at least one target application identifier from the candidate application identifiers, the instant messaging application client updates the display status of at least one target application identifier from unselected to selected.

[0092] In this embodiment, by displaying multiple candidate application identifiers for member accounts of the target organization to select, it is possible to simultaneously share one or more target applications. This effectively reduces the operational complexity of sharing two or more target applications and improves data processing efficiency.

[0093] In some embodiments, the application sharing processing method further includes unsharing processing for the shared application, specifically including: in response to a member account of the target organization triggering an unsharing operation for the shared application, corresponding to the member account of the target organization, unshowing the range of shared members selected for the shared application, and for each group of shared member accounts that have added the shared application to the cooperative organization, asynchronously unshowing the application entry of the shared application in the respective application containment area of ​​the same group of shared member accounts.

[0094] In this context, a shared application is an application added to a collaborating organization's shared member account by a member account of the target organization. The sharing process of a shared application can be implemented through the above embodiments, and will not be repeated here. Both sharing and unsharing of a shared application are controlled by member accounts of the target organization. For example, if sharing of a shared application is controlled by an administrator account of the target organization, then unsharing of a shared application is also controlled by an administrator account of the target organization. The administrator account controlling application sharing and the administrator account controlling application unsharing can be different administrator accounts within the target organization.

[0095] Specifically, when a member account of the target organization wants to unshare a shared application, the application entry for that shared application needs to be undisplayed in the application containment area of ​​each shared member account within the scope of the shared member account of the shared application.

[0096] Furthermore, the process of canceling the sharing of a shared application is the reverse of the process of sharing the target application. The member objects processed are the same. For shared member accounts with application entries for the shared application added, the cancellation of sharing is performed in groups. This parallel and asynchronous processing improves the data processing efficiency of canceling the sharing of the shared application. In specific applications, the instant messaging application client responds to the cancellation operation of a member account of the target organization for a shared application by initiating a cancellation request for the shared application to the instant messaging application server. Based on the identifier of the shared application carried in the cancellation request, the instant messaging application server determines the scope of shared members for that shared application. The instant messaging application server groups multiple shared member accounts within the shared member scope and, according to the predefined groups, sequentially cancels the sharing of the shared application for each group of shared member accounts. Within the application display area of ​​each shared member account in the same group, the added application entry for the shared application is asynchronously removed.

[0097] In a specific application, the target organization is an upstream enterprise, and the collaborating organizations are downstream enterprises. At least some members of the upstream enterprise and at least some members of the downstream enterprise join the same upstream / downstream space. The administrator of the upstream enterprise selects the shared application on the application page of the instant messaging application to unshare it. The unsharing process is as follows: Figure 11 As shown, after receiving a report from the instant messaging application client that a shared application needs to be unshared, the instant messaging application server retrieves the application sharing scope of the downstream enterprise that has the shared application. The instant messaging application server asynchronously performs a parallel application unloading task for each member in the application sharing scope of the downstream enterprise, so that the application entry of the shared application is removed from the application containing area of ​​the member accounts that share the shared application in the downstream enterprise, and the application visibility scope of the shared application is cleared.

[0098] In this embodiment, an asynchronous parallel processing method is used to cancel the sharing of shared applications, which enables multiple groups of shared member accounts to cancel sharing simultaneously, effectively improving data processing efficiency.

[0099] In some embodiments, the application sharing processing method further includes a process for adjusting the scope of shared members. The adjustment of the scope of shared members includes two scenarios: the first is triggered by a member account of the target organization; the second is where the shared member scope selected by the member account of the target organization is for a collaborating organization or a department within a collaborating organization, and the shared member accounts included in the shared member scope are adaptively adjusted when the members of the collaborating organization or the members of the department change.

[0100] Specifically, the adjustment of shared member scope triggered by a member account of the target organization includes: responding to a shared member scope adjustment operation triggered by a member account of the target organization for a shared application, displaying newly added shared member scopes that change from unselected to selected, and deselected shared member scopes that change from selected to unselected. In the application containment areas of the newly added shared member accounts included in the newly added shared member scope, the application entry for the target application is added asynchronously; in the application containment areas of the deselected shared member accounts included in the deselected shared member scope, the application entry for the target application is deselected asynchronously.

[0101] Specifically, member accounts within the target organization can adjust the scope of shared members on the shared application's shared parameter configuration page. When adding a new shared member account, the desired scope can be selected, updating the displayed state from unselected to selected. Conversely, when removing a shared member account, the desired scope can be selected, updating the displayed state from selected to unselected. The scope for adding and removing shared members can be a subset of multiple collaborating organizations, a subset of departments within a collaborating organization, or a subset of shared member accounts within a single collaborating organization or department.

[0102] In a specific application, the target organization is an upstream enterprise, and the collaborating organizations are downstream enterprises. At least some members of the upstream enterprise and at least some members of the downstream enterprise join the same upstream / downstream space. The administrator of the upstream enterprise selects the shared application on the application page of the instant messaging application to unshare the application. The process of adjusting the scope of shared members is as follows: Figure 12 As shown, after receiving the shared member scope adjustment results reported by the instant messaging application client, the instant messaging application server determines the newly added and removed shared members in the adjusted shared member scope. For each member in the downstream enterprise whose application sharing scope has been removed, the instant messaging application server asynchronously performs a parallel application uninstallation task to remove the application entry of the target application from the application's containment area in the downstream enterprise's account where the shared member's account has been removed. Simultaneously, the application visibility scope of the target application is updated based on the removed shared member account. For each member in the downstream enterprise whose application sharing scope has been added, the instant messaging application server asynchronously performs a parallel application add task to add the shared application's entry to the application's containment area in the downstream enterprise's account where the newly added shared member's account has been added. Simultaneously, the application visibility scope of the target application is updated based on the newly added shared member account.

[0103] In this embodiment, when the scope of shared members is adjusted, by identifying newly added and canceled shared member accounts, only the changed shared member accounts need to be processed, which effectively reduces the amount of data processing and improves data processing efficiency. For newly added shared member accounts included in the scope of newly added shared members, the application entry point of the target application is added asynchronously for the newly added shared member accounts. For canceled shared member accounts included in the scope of canceled shared members, the application entry point of the target application is removed asynchronously for the canceled shared member accounts. This enables effective utilization of data processing resources and improves resource utilization.

[0104] In one embodiment, the application sharing processing method further includes: when the members of the cooperative organization change, determining the changed member account; and if the changed member account belongs to the scope of shared members, adjusting the display status of the application entry of the target application in the application containment area of ​​the changed member account according to the change type corresponding to the changed member account.

[0105] Specifically, changes in the membership of a cooperative organization include at least one of two scenarios: the addition of new members or the departure of members. The change types corresponding to the member accounts that have changed include addition and departure.

[0106] For new members, the process of determining whether their account belongs to the scope of shared members includes: determining whether the scope of shared members includes enterprise nodes or department nodes. If not, the new member is determined not to belong to the scope of shared members. If so, determining whether the new member belongs to the enterprise represented by the enterprise node or the department represented by the department node. If so, the new member belongs to the scope of shared members. If not, the new member is determined not to belong to the scope of shared members.

[0107] For departing members, the process of determining whether their account belongs to the scope of shared members includes: when the scope of shared members includes shared member accounts, determine whether the departing member is included in the shared member accounts. If it is included, the departing member is determined to belong to the scope of shared members. If it is not included, obtain the enterprise node or department node included in the scope of shared members, and determine whether the departing member belongs to the enterprise represented by the enterprise node or the department represented by the department node. If it belongs, the departing member is determined to belong to the scope of shared members. If it does not belong, the departing member is determined not to belong to the scope of shared members.

[0108] In a specific application, when an instant messaging application client detects a change in the members of a collaborative organization, it identifies the changed member account and reports it to the instant messaging application server. The instant messaging application server then determines whether the changed member account belongs to the shared member scope based on the change type. If the changed member account belongs to the shared member scope, the server sends an adjustment command to the client of the changed member account to adjust the display status of the target application's entry point within the application's coverage area.

[0109] In this embodiment, when the members of the cooperative organization change, by identifying the changed member account, and if the changed member account belongs to the scope of shared members, the display status of the application entry of the target application in the application containment area of ​​the changed member account is adjusted according to the change type corresponding to the changed member account. This enables the synchronous adjustment of the shared applications of newly added and departing members without the need for the member account of the target organization to operate, thereby improving the convenience of user operation.

[0110] In some embodiments, the scope of shared members includes at least one department of the cooperative organization; the application sharing processing method further includes: in response to a new member event of at least one department in the scope of shared members, adding an application entry of the target application in the application containment area of ​​the new member; in response to a exit event of at least one department in the scope of shared members, canceling the display of the application entry of the target application in the application containment area of ​​the exiting member.

[0111] Specifically, when the shared member scope is configured for departments within a collaborative organization, it's possible to monitor changes in personnel within those departments. This allows for targeted, small-scale monitoring, reducing the data processing resources required for monitoring. When a new member is added to at least one department within the shared member scope, an application entry point for the target application is added to the application's application area. Conversely, when a member leaves at least one department within the shared member scope, the application entry point for the target application is removed from the application's application area.

[0112] In this embodiment, targeted, small-scale monitoring is achieved by monitoring only whether there are changes in personnel in departments configured as shared members within the cooperative organization, thereby reducing the data processing resources required for monitoring.

[0113] In some embodiments, in response to a new member event of at least one department in the shared member scope, adding a target application in the application containment area of ​​the new member includes: in response to a new member event of at least one department in the shared member scope, assigning the account of the new member to a new member queue to which the target application is to be added, and sequentially performing target application addition processing on the accounts of each new member in the new member queue, so that the application entry of the target application is asynchronously added to the application containment area of ​​each new member's account.

[0114] Specifically, when the client of the instant messaging application detects that at least one department in the shared member scope has a new department member, it reports the department member addition event to the instant messaging application server. The instant messaging application server assigns the account of the new member to the new member queue of the target application to be added, and processes the account of each new member in the new member queue to add the target application in sequence, so that the application entry of the target application is added asynchronously in sequence in the application containment area of ​​each new member's account.

[0115] In this embodiment, by assigning the accounts of newly added members to the new member queue of the target application to be added, and processing the application entry of the target application in sequence, it is possible to make full use of data processing resources and improve resource utilization.

[0116] In some embodiments, in response to a department member exit event in at least one department within the shared member scope, the application entry of the target application is canceled in the application containment area of ​​the exiting member, including: in response to a department member exit event in at least one department within the shared member scope, assigning the exiting member's account to an exiting member queue for the target application to be removed; sequentially removing the target application from the accounts of each exiting member in the exiting member queue, so that the application entry of the target application is asynchronously canceled in the application containment area of ​​each exiting member's account.

[0117] Specifically, when the client of the instant messaging application detects that at least one department in the shared member scope has a member who has left the department, it reports the member's departure event to the instant messaging application server. The instant messaging application server assigns the account of the departing member to the departure member queue of the target application to be removed, and performs the target application removal process on the accounts of each departing member in the departure member queue in sequence, so that the application entry of the target application is removed asynchronously in sequence in the application containment area of ​​each departing member's account.

[0118] In this embodiment, by assigning the accounts of the exiting members to the exiting member queue of the target application to be removed, and removing the application entry of the target application in sequence, it is possible to make full use of data processing resources and improve resource utilization.

[0119] In some embodiments, the application sharing processing method further includes: displaying the current number of shareable members of the target application corresponding to the member accounts of the target organization; and displaying an operation prompt message to increase the number of shareable members of the target application when the number of shareable member accounts included in the shareable member range of the target application is greater than the current number of shareable members.

[0120] The target applications to be shared are divided into two types based on whether they have sharing member restrictions: applications with no limit on the number of sharing members and applications with a limit on the number of sharing members. The number of sharing members can be obtained by the target organization's member accounts applying to the target application's provider or the instant messaging application's platform, etc., and the number of sharing members is adjustable. For example, taking the example of a target organization's member accounts applying to the target application's provider for a certain number of members, the target organization can provide a certain number of virtual resources to the target application's provider. Upon receiving these virtual resources, the target application's provider will automatically authorize the target organization's member application.

[0121] Specifically, for the member account of the target organization, the current number of members that can be shared by the target application is displayed. The number of shared member accounts included in the selected shared member range of the member account of the target organization is compared with the current number of members that can be shared. When the number of shared member accounts is greater than the current number of members that can be shared, an operation prompt message to increase the number of shared members of the target application is displayed so that the member account of the target organization can expand the number of members.

[0122] Furthermore, when a member account of the target organization selects multiple target applications, and at least two target applications have current shareable member limits, the smallest current shareable member limit is used as the threshold. The number of shared member accounts included in the shared member range selected by the member account of the target organization is compared with this threshold. When the number of shared member accounts exceeds the threshold, a prompt message to increase the number of shared members is displayed for target applications whose current shareable member limit is less than the threshold.

[0123] In a specific application, the cooperating organization's department A includes 50 people, department B includes 200 people, and department C includes 150 people. The target application currently has 300 members who can share the data. When a member account of the target organization selects department A, department B, or department C, since 50 + 200 + 150 = 400 > 300, a prompt message to increase the number of shared members is displayed, corresponding to the application identifier of the target application.

[0124] In this embodiment, when the number of shared member accounts exceeds the current number of shareable members, an operation prompt message is displayed to increase the number of shared members for the target application. This facilitates the target organization's member accounts to promptly expand the current number of shareable members, improving user convenience.

[0125] In some embodiments, the application sharing processing method further includes: in response to a member account of the target organization selecting a superior department in the collaborating organization, when the number of people in the superior department is greater than the current number of shareable members of the target application, displaying candidate subordinate departments of the superior department. Displaying the scope of shared members for the target application includes: in response to selecting at least a portion of the target subordinate departments from the candidate subordinate departments, displaying the target subordinate departments in the selected state, wherein the scope of shared members includes the shared member accounts contained in each of the target subordinate departments in the selected state.

[0126] In this context, "superior department" refers to a department relative to its subordinate departments. A superior department includes one or more subordinate departments, and a subordinate department belongs to a superior department. When a member account of the target organization selects the scope of shared members within a collaborating organization, selecting a department within that organization selects all member accounts under that department as shared member accounts. For example, if department A of the collaborating organization has 500 people, when a member account of the target organization selects department A, the number of selected shared member accounts will be 500.

[0127] In a specific application, the cooperating organization's superior department A comprises 500 people, subordinate departments a1 comprise 100 people, subordinate departments a2 comprise 180 people, and subordinate departments a3 comprise 220 people. The target application currently has 300 shareable members. When a member account of the target organization has selected superior department A, since the total number of people in superior department A is greater than the current number of shareable members in the target application, candidate subordinate departments a1, a2, and a3 of superior department A are displayed. When a member account of the target organization selects target subordinate departments a1 and a2 from the candidate subordinate departments a1, a2, and a3, the selected target subordinate departments a1 and a2 are displayed, and the scope of shared members includes the 220 shared member accounts contained in each of the target subordinate departments a1 and a2.

[0128] In this embodiment, when the number of members in the superior department exceeds the current number of members that can be shared by the target application, the candidate subordinate departments of the superior department are displayed to facilitate the filtering of member accounts of the target organization. This allows member accounts of the target organization to select shared member accounts within the allowed number range from the cooperating organizations, improving the convenience of user operation.

[0129] In some embodiments, the application sharing processing method further includes: in response to a member account of the target organization selecting a target sub-department of the cooperating organization, when the number of people in the target sub-department is greater than the current number of shareable members, displaying candidate member accounts included in the target sub-department. Displaying the scope of shared members for the target application includes: in response to selecting at least a portion of the target member accounts from the candidate member accounts, displaying the scope of shared members as the selected target member accounts.

[0130] The target sub-department is the direct department of the member account of the cooperative organization. When the number of people in the target sub-department is greater than the current number of members that can be shared, the candidate member accounts contained in the target sub-department are displayed so that the member accounts of the target organization can directly select member accounts, thereby achieving accurate member account selection and reasonable arrangement of the current number of members that can be shared.

[0131] In a specific application, a cooperative organization has a sub-department M with 80 members and a sub-department N with 40 members. The target application currently has 50 members that can share resources. When a member account in the target organization has selected the target sub-department M, since the total number of members in the target sub-department M is greater than the current number of members that can share resources in the target application, candidate member accounts 1 to 80 of the target sub-department M are displayed. When a member account in the target organization selects target member accounts 1 to 40 from candidate member accounts 1 to 80, the selected target member accounts 1 to 40 are displayed, and the range of shared members includes those in target member accounts 1 to 40.

[0132] In this embodiment, when the number of people in the target sub-department is greater than the current number of shareable members in the target application, the candidate member accounts contained in the target sub-department are displayed to facilitate member filtering by the member accounts of the target organization. This allows the member accounts of the target organization to select shared member accounts within the allowed number range from the cooperating organizations, thereby improving the convenience of user operation.

[0133] In some embodiments, the application sharing processing method further includes: displaying the effective sharing time of the target application corresponding to the member account of the target organization; and displaying an operation prompt message to increase the effective sharing time of the target application when the current time exceeds the effective sharing time of the target application.

[0134] The target applications to be shared are divided into two types based on whether they have sharing time restrictions: applications with no time limit and applications with a time limit. The sharing time can be obtained by a member account of the target organization applying to an authorized entity such as the provider of the target application or the platform of the instant messaging application. The sharing time is adjustable. For example, if a member account of the target organization applies for time from the provider of the target application, the target organization can provide a certain number of virtual resources to the provider. Upon receiving these virtual resources, the provider automatically authorizes the time request.

[0135] Specifically, for the member account of the target organization, the effective sharing time of the target application is displayed, such as the remaining effective time, such as 30 days, or the expiration time, such as October 1, 2022. The current time is compared with the effective sharing time of the target application. When the current time exceeds the effective sharing time of the target application, an operation prompt message to extend the effective sharing time of the target application is displayed to remind the member account of the target organization to apply for an extension of the sharing time.

[0136] In a specific application, such as Figure 13 As shown, Application 1 is an application with a limited sharing time, and Application 2 is an application with a limited number of users. If the current time exceeds the valid sharing time of Application 1, a "Renew Now" message will be displayed for Application 1. If the number of users in the selected application's sharing range exceeds the current shareable number of members for Application 2, a "Expand Now" message will be displayed.

[0137] In this embodiment, by displaying an operation prompt message to extend the effective sharing time of the target application when the current time exceeds the effective sharing time of the target application, it is possible to facilitate the timely processing of the sharing time extension application by the member accounts of the target organization, thereby improving the timeliness of user operation processing.

[0138] In a specific application scenario, taking upstream and downstream enterprises in an instant messaging application as an example, a method for application sharing is provided. This method can be applied in scenarios where there are many members in the downstream enterprise and large-scale application sharing is required.

[0139] In instant messaging applications, a company can create upstream and downstream spaces, which are essentially a directory of contact information for multiple upstream and downstream companies. A company can create or join multiple different upstream and downstream spaces, and data across different spaces belonging to the same company is completely isolated. The company that creates the upstream / downstream space is the upstream company, which may be a distributor, brand owner, etc., involved in the collaboration process. After the upstream / downstream space is created, the companies that join and collaborate with the upstream company are the downstream companies, which may be suppliers. One upstream company can correspond to multiple downstream companies and collaborate with them. Corresponding to the upstream / downstream space, there exists an upstream / downstream directory, a cross-company directory used for end-to-end collaboration. Members joining the upstream / downstream space can communicate and collaborate without adding each other as friends. Within the upstream / downstream space, the upstream company can share applications with members of downstream companies who have joined the space. Application sharing means that the upstream company installs an application on the downstream company's website, allowing collaboration between the upstream and downstream companies through the same application.

[0140] Specifically, upstream enterprise administrators can click "Add Application" on the shared application list page to view applications already shared in upstream and downstream spaces. Selecting the application to be shared will display all installed third-party and self-built applications for the enterprise to share. However, shareable applications are only a subset of those used by upstream enterprise members. Examples include applications authorized by members, self-built robot applications, address book applications, encrypted applications, standalone applications, applications in the testing phase, applications shared with the enterprise by upstream / downstream partners, industry solution applications, and deactivated applications. These will not be considered shareable applications and will not appear in the shareable application list, nor can they be added or shared.

[0141] Upstream enterprise administrators can select the scope of shared members. Generally, the default scope includes all groups and enterprises in the current upstream and downstream ecosystem. Upstream enterprise administrators can modify the scope of shared members, such as selecting groups or enterprises, and can also select multiple groups and enterprises for application sharing. When an upstream enterprise administrator triggers a confirmation sharing operation, the server sends an authorization message to the administrators of the downstream enterprises to which the members in the shared member scope belong, enabling unified authorization for all members within that downstream enterprise. If a downstream enterprise administrator does not process the authorization message, they can first add the shared application to each shared member. Each shared member can then authorize the shared application upon their first access to it.

[0142] During the sharing process, each member in the sharing scope is added to a different queue, and application sharing is achieved asynchronously and in parallel through coroutines corresponding to each queue. When the administrator of the upstream enterprise successfully shares the selected shared application to each member in the subsequent sharing scope, any changes in the number of enterprises and the number of employees in the sharing scope need to be updated in real time. For example... Figure 14 As shown, the administrator of the upstream enterprise can view the sharing scope and sharing status.

[0143] Specifically, within the upstream and downstream space, upstream enterprises can share, cancel, or adjust the scope of shared applications. For example... Figure 15 As shown, the request processing service handles requests, while the asynchronous grouping execution service performs asynchronous tasks such as installation and deletion, and notifies lower-level enterprise administrators. The application management service is responsible for installing applications for each enterprise and controlling the visibility of those applications. Lower-level enterprise administrators can view applications through the management service, and higher-level enterprises can adjust and control the application sharing scope through this service.

[0144] During the application sharing process, after receiving the target application and application sharing scope reported by the instant messaging application client, the instant messaging application server retrieves the downstream enterprises participating in the upstream and downstream spaces, as well as the departments and members of each enterprise that have joined the upstream and downstream spaces. The instant messaging application server asynchronously initializes and installs the application task for each member in the application sharing scope of the downstream enterprise, and at the same time, sets the scope of members and departments of the downstream enterprise participating in the upstream and downstream spaces as the application visibility scope of the target application.

[0145] Specifically, taking a shared member scope including 100,000 accounts as an example, when an upstream enterprise asynchronously and in parallel shares its application with downstream enterprises, and the number of users is limited, it's necessary to calculate whether the number of users within the current shared member scope exceeds the application's maximum allowed user count. If the shared member scope includes the root nodes of upstream and downstream entities (such as group nodes of multiple enterprises), specific enterprises need to be selected, and then the organizational nodes configured for each enterprise in the upstream and downstream spaces need to be retrieved. If the configuration is for a downstream enterprise and the organizational node is a department in the upstream space, specific members need to be selected. During upstream and downstream address book maintenance, for enterprises joining the upstream and downstream sectors, internal address book change events are monitored. If a change event falls within the shared member scope of the enterprise participating in the upstream and downstream sectors, the total number of members joining the upstream and downstream sectors for that enterprise is calculated to determine if it exceeds the application's shared user limit. When calculating the number of users in the upstream and downstream sectors, only the total number of users from each enterprise in the upstream and downstream enterprise list needs to be retrieved; there's no need to retrieve the internal address book again.

[0146] During the unsharing process, after receiving a report from the instant messaging application client that a shared application needs to be unshared, the instant messaging application's server retrieves the application sharing scope that has been added to the downstream enterprise's application sharing scope. The instant messaging application's server then asynchronously performs a parallel application unloading task for each member within the downstream enterprise's application sharing scope. This process removes the application entry for the shared application from the application's display area within the application area of ​​the member accounts that share the shared application within the downstream enterprise, and simultaneously clears the application's visible scope.

[0147] During the process of adjusting the shared member scope, after receiving the adjusted shared member scope report from the instant messaging application client, the instant messaging application server determines the newly added and removed shared members in the adjusted shared member scope. For each member in the downstream enterprise whose application sharing scope has been removed, the instant messaging application server asynchronously performs a parallel application unloading task to remove the application entry of the target application from the application's containment area in the downstream enterprise's account where the shared member's scope has been removed. Simultaneously, the application visibility scope of the target application is updated based on the removed shared member account. For each member in the downstream enterprise whose application sharing scope has been added, the instant messaging application server asynchronously performs a parallel application adding task to add the shared application's entry to the application's containment area in the downstream enterprise's account where the new shared member's scope has been added. Simultaneously, the application visibility scope of the target application is updated based on the new shared member account.

[0148] On the server side, the real-time sharing scope is written to key-value pairs. The keys in the key-value pairs are the upstream / downstream identifier and the application identifier, and the values ​​are the sharing member scopes. The actual operation logic is processed through a queue. Specifically, the logic includes: obtaining the actual sharing layer member scope corresponding to the shared application, refining the sharing member scope to the department nodes and members at the enterprise level; obtaining the application identifiers of all enterprises in the upstream / downstream space, and obtaining a list of enterprises that have installed the shared application, thus identifying enterprises that need to install the shared application, enterprises that need to uninstall the application, and enterprises that need to modify the application's sharing scope; upstream enterprises updating the sharing member scope corresponding to the application; saving the upstream / downstream information that initiated the sharing application; for enterprises that need to install the application, installing the application for them; firstly, establishing the upstream / downstream space, updating the sharing member scope corresponding to the application, specifically including the application's visibility scope and information about upstream and downstream shared applications; and sending an application installation card to the downstream enterprise's administrator account. After installation, updating the application authorization table. For enterprises that need to uninstall the application, updating the application information and authorization status.

[0149] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0150] Based on the same inventive concept, this application also provides an application sharing processing apparatus for implementing the application sharing processing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations of one or more application sharing processing apparatus embodiments provided below can be found in the limitations of the application sharing processing method described above, and will not be repeated here.

[0151] In one embodiment, such as Figure 16 As shown, an application sharing processing device is provided, including: an application display module 1602, a range display module 1604, and an application sharing module 1606, wherein:

[0152] Application display module 1602 is used to display the application identifier of at least one target application to be shared, corresponding to the member account of the target organization.

[0153] The scope display module 1604 is used to display the scope of shared members for the target application. The scope of shared members includes multiple shared member accounts, which belong to cooperative organizations that have established cooperative relationships with the target organization.

[0154] Application sharing module 1606 is used to respond to the confirmation operation of the target application and the scope of shared members, and asynchronously add the application entry of the target application to the application containment area of ​​each group of shared member accounts in the same group of shared member accounts for each group of shared member accounts.

[0155] In one embodiment, the application sharing module is further configured to, in response to a confirmation operation for the target application and the scope of shared members, randomly assign multiple shared member accounts in the scope of shared members to multiple queues; for each queue, sequentially perform the same target application addition process on each shared member account in the queue, so that the application entry of the target application is asynchronously added to the application containment area of ​​each shared member account belonging to the same queue.

[0156] In one embodiment, the application sharing module is further configured to send an application authorization message for the target application to the administrator account of the cooperating organization in response to a confirmation operation for the target application and the scope of shared members; and to asynchronously add the application entry of the target application to the application authorization message in the application containment area of ​​each of the shared member accounts in the same group within the scope of shared members in response to the authorization confirmation operation of the administrator account.

[0157] In one embodiment, the application sharing processing device further includes an authorization processing module, which displays an authorization message for the target application in response to the first access operation triggered by the shared member account for the added application entry in the application containment area; and displays the application page of the target application in response to the authorization operation triggered by the shared member account in response to the authorization message.

[0158] In one embodiment, the number of target applications to be shared is at least two; the application sharing module is also used to simultaneously add the application entry points of at least two target applications to the application containment area of ​​each shared member account.

[0159] In one embodiment, the application display module is further configured to display candidate application identifiers of shareable applications in the target organization in response to an application sharing event triggered by a member account of the target organization; and to display at least one target application identifier as selected in response to a selection operation on at least one target application identifier among the candidate application identifiers.

[0160] In one embodiment, the application sharing processing device further includes a de-sharing processing module, which is used to respond to a de-sharing operation triggered by a member account of the target organization for a shared application, and to de-display the range of shared members selected for the shared application corresponding to the member account of the target organization; and to asynchronously de-display the application entry of the shared application in the application containment area of ​​each group of shared member accounts in the cooperative organization for each group of shared member accounts.

[0161] In one embodiment, the application sharing processing device further includes a scope adjustment module, which is used to respond to a shared member scope adjustment operation triggered by a member account of the target organization for a shared application, displaying newly added shared member scopes that change from unselected to selected and deselected shared member scopes that change from selected to unselected; asynchronously adding the application entry of the target application to the application containment area of ​​each newly added shared member account included in the newly added shared member scope; and asynchronously deselecting the display of the application entry of the target application in the application containment area of ​​each deselected shared member account included in the deselected shared member scope.

[0162] In one embodiment, the application sharing processing device further includes an application entry display status adjustment module, which is used to determine the changed member account when the members of the cooperative organization change; and, if the changed member account belongs to the scope of shared members, adjust the display status of the application entry of the target application in the application containing area of ​​the changed member account according to the change type corresponding to the changed member account.

[0163] In one embodiment, the scope of shared members includes at least one department of the cooperative organization; the application sharing processing device further includes an application entry display status adjustment module, which, in response to a new member addition event of at least one department in the scope of shared members, adds the application entry of the target application in the application containment area of ​​the new member; and, in response to a exit event of at least one department in the scope of shared members, cancels the display of the application entry of the target application in the application containment area of ​​the exiting member.

[0164] In one embodiment, the display status adjustment module is further configured to, in response to a new member event of at least one department in the shared member scope, assign the account of the new member to the new member queue of the target application to be added; and sequentially perform target application addition processing on the accounts of each new member in the new member queue, so that the application entry of the target application is asynchronously added in the application containment area of ​​each new member's account.

[0165] In one embodiment, the display status adjustment module is further configured to, in response to a department member exit event of at least one department in the shared member scope, assign the exiting member's account to the exiting member queue of the target application to be removed; and sequentially remove the target application from the accounts of each exiting member in the exiting member queue, so that the application entry of the target application is asynchronously canceled in the application containing area of ​​each exiting member's account.

[0166] In one embodiment, the application sharing processing device further includes a prompt message display module, which displays the current number of shareable members of the target application corresponding to the member accounts of the target organization; when the number of shareable member accounts included in the shareable member range of the target application is greater than the current number of shareable members, it displays an operation prompt message to increase the number of shareable members of the target application.

[0167] In one embodiment, the range display module is further configured to, in response to a member account of the target organization selecting a superior department in the cooperative organization, display candidate subordinate departments of the superior department when the number of people in the superior department is greater than the current number of shareable members of the target application; and, in response to selecting at least a portion of the target subordinate departments from the candidate subordinate departments, display the target subordinate departments in the selected state; the shared member range includes the shared member accounts contained in each of the target subordinate departments in the selected state.

[0168] In one embodiment, the range display module is further configured to, in response to a member account of the target organization selecting a target sub-department of the cooperative organization, display candidate member accounts included in the target sub-department when the number of people in the target sub-department is greater than the current number of shareable members; in response to selecting at least a portion of the target member accounts from the candidate member accounts, display the target member accounts in the selected state; and the shared member range includes the target member accounts in the selected state.

[0169] In one embodiment, the application sharing processing device further includes a prompt message display module, which displays the effective sharing time of the target application corresponding to the member account of the target organization; and displays an operation prompt message to increase the effective sharing time of the target application when the current time exceeds the effective sharing time of the target application.

[0170] The modules in the shared processing device described above can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device, or stored in the memory of the computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0171] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 17As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements an application-sharing processing method. The display unit of the computer device is used to form a visually visible image. It can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0172] Those skilled in the art will understand that Figure 17 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0173] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0174] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0175] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0176] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0177] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0178] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0179] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for processing application sharing, characterized in that, The method includes: For each member account of the target organization, display the application identifier of at least one target application to be shared; Displays the scope of shared members for the target application, which includes multiple shared member accounts belonging to a partner organization that has a cooperative relationship with the target organization; In response to the confirmation operation of the target application and the shared member scope, for each group of shared member accounts divided from the shared member scope, the application entry of the target application is asynchronously added to the application containment area of ​​each of the shared member accounts in the same group; In response to a member account of the target organization triggering a de-sharing operation for a shared application, the selected range of shared members for the shared application is de-displayed for the member account of the target organization; for each group of shared member accounts that have the shared application added to the cooperative organization, the application entry of the shared application is asynchronously de-displayed in the application containment area of ​​each of the shared member accounts in the same group.

2. The method according to claim 1, characterized in that, In response to the confirmation operation of the target application and the shared member scope, for each group of shared member accounts divided from the shared member scope, the application entry of the target application is asynchronously added to the application containment area of ​​each of the shared member accounts in the same group, including: In response to the confirmation operation for the target application and the shared member scope, multiple shared member accounts in the shared member scope are randomly assigned to multiple queues; For each queue, the same target application addition process is performed sequentially on each of the shared member accounts in the queue, so that the application entry of the target application is added asynchronously in the application containment area of ​​each of the shared member accounts belonging to the same queue.

3. The method according to claim 1, characterized in that, In response to the confirmation operation of the target application and the shared member scope, for each group of shared member accounts divided from the shared member scope, the application entry of the target application is asynchronously added to the application containment area of ​​each of the shared member accounts in the same group, including: In response to the confirmation operation for the target application and the shared member scope, an application authorization message for the target application is sent to the administrator account of the cooperating organization; In response to the administrator account's authorization confirmation operation for the application authorization message, the application entry of the target application is asynchronously added to the application containment area of ​​each of the shared member accounts in the same group within the shared member scope.

4. The method according to claim 1, characterized in that, The method further includes: In response to the shared member account triggering the first access operation for the added application entry in the application containment area, the authorization message of the target application is displayed; In response to the authorization operation triggered by the shared member account in relation to the authorization message, the application page of the target application is displayed.

5. The method according to claim 1, characterized in that, The number of target applications to be shared is at least two; the method further includes: For each of the shared member accounts, at least two application entry points for each of the target applications are simultaneously added to the application containment area of ​​the shared member account.

6. The method according to claim 1, characterized in that, Corresponding to the member account of the target organization, display the application identifier of at least one target application to be shared, including: In response to an application sharing event triggered by a member account of the target organization, candidate application identifiers for shareable applications in the target organization are displayed; In response to a selection operation for at least one target application identifier among the candidate application identifiers, the at least one target application identifier is displayed as selected.

7. The method according to claim 1, characterized in that, The method further includes: In response to the shared member scope adjustment operation triggered by the member account of the target organization for the shared application, the newly added shared member scope that changes from unselected to selected and the canceled shared member scope that changes from selected to unselected are displayed. In the application containment area of ​​each newly added shared member account included in the scope of newly added shared members, the application entry of the target application is added asynchronously; In the application containment area of ​​each of the unshared member accounts included in the scope of unshared members, the application entry of the target application is asynchronously removed.

8. The method according to claim 1, characterized in that, The method further includes: When the members of the cooperative organization change, the account of the member that has changed; If the changed member account belongs to the shared member scope, adjust the display status of the application entry of the target application in the application containment area of ​​the changed member account according to the change type corresponding to the changed member account.

9. The method according to claim 1, characterized in that, The scope of shared members includes at least one department of the cooperative organization; the method further includes: In response to a new member event in at least one department within the shared member scope, an application entry for the target application is added to the application containment area of ​​the new member. In response to a department member exit event in at least one department within the shared member scope, the application entry for the target application is removed from the application containment area of ​​the exiting member.

10. The method according to claim 9, characterized in that, The response to a new department member event in at least one department within the shared member scope, adding the target application to the application containing the new member, includes: In response to a new member event in at least one department within the shared member scope, the account of the new member is assigned to the new member queue of the target application to be added. The target application is added sequentially to the accounts of each new member in the new member queue, so that the application entry of the target application is added asynchronously to the application area of ​​each new member's account.

11. The method according to claim 9, characterized in that, In response to a department member exit event in at least one department within the shared member scope, the application entry for the target application is disabled in the application containment area of ​​the exiting member, including: In response to a member exit event from at least one department within the shared member scope, the account of the exiting member is assigned to the exiting member queue to be removed from the target application; The target application is removed sequentially from the accounts of each exiting member in the exiting member queue, so that the application entry of the target application is asynchronously removed from the application containing area of ​​each exiting member's account.

12. The method according to claim 1, characterized in that, The method further includes: The number of members that can currently share the target application is displayed, corresponding to the member accounts of the target organization; When the number of shared member accounts included in the shared member range of the target application is greater than the current number of shareable members, an operation prompt message to increase the number of shared members of the target application is displayed.

13. The method according to claim 12, characterized in that, The method further includes: In response to a member account of the target organization selecting a superior department in the cooperative organization, when the number of people in the superior department is greater than the current number of shareable members of the target application, candidate subordinate departments of the superior department are displayed; The display of the shared member scope for the target application includes: In response to selecting at least a portion of the target subordinate departments from the candidate subordinate departments, the selected target subordinate departments are displayed; The scope of shared members includes the shared member accounts contained in each of the target subordinate departments that are selected.

14. The method according to claim 12, characterized in that, The method further includes: In response to a member account of the target organization selecting a target sub-department of the cooperative organization, when the number of people in the target sub-department is greater than the current number of shareable members, the candidate member accounts contained in the target sub-department are displayed; The display of the shared member scope for the target application includes: In response to selecting at least a subset of target member accounts from the candidate member accounts, the selected target member accounts are displayed; The shared member range includes the target member account that is currently selected.

15. The method according to any one of claims 1 to 14, characterized in that, The method further includes: The effective sharing time of the target application is displayed for the member account corresponding to the target organization. If the current time exceeds the effective sharing time of the target application, display an operation prompt message to increase the effective sharing time of the target application.

16. An application-sharing processing device, characterized in that, The device includes: The application display module is used to display the application identifier of at least one target application to be shared, corresponding to the member account of the target organization. The scope display module is used to display the scope of shared members for the target application. The scope of shared members includes multiple shared member accounts, which belong to a cooperative organization that has established a cooperative relationship with the target organization. The application sharing module is used to respond to the confirmation operation of the target application and the shared member scope, and asynchronously add the application entry of the target application to the application containing area of ​​each group of shared member accounts in the same group of shared member accounts for each group of shared member accounts. The unshare processing module is used to respond to the unshare operation triggered by a member account of the target organization for a shared application. For the member account of the target organization, it cancels the display of the selected sharing member range for the shared application; for each group of sharing member accounts that have shared applications added to the cooperative organization, it asynchronously cancels the display of the application entry of the shared application in the application containment area of ​​each sharing member account in the same group.

17. The apparatus according to claim 16, characterized in that, The application sharing module is also used to respond to the confirmation operation for the target application and the scope of shared members by randomly assigning multiple shared member accounts in the scope of shared members to multiple queues; for each queue, the same target application addition process is performed on each shared member account in the queue in sequence, so that the application entry of the target application is added asynchronously in the application containment area of ​​the shared member accounts belonging to the same queue.

18. The apparatus according to claim 16, characterized in that, The application sharing module is also used to send an application authorization message for the target application to the administrator account of the cooperating organization in response to the confirmation operation for the target application and the scope of sharing members; and to asynchronously add the application entry of the target application to the application authorization message in the application containment area of ​​each of the shared member accounts in the same group within the scope of sharing members in response to the authorization confirmation operation of the administrator account.

19. The apparatus according to claim 16, characterized in that, The application sharing processing device also includes an authorization processing module, which is used to display the authorization message of the target application in response to the first access operation triggered by the shared member account for the added application entry in the application containing area; In response to the authorization action triggered by the shared member account in response to the authorization message, the application page of the target application is displayed.

20. The apparatus according to claim 16, characterized in that, The number of target applications to be shared is at least two; the application sharing module is also used to simultaneously add the application entry points of at least two target applications to the application containment area of ​​each shared member account.

21. The apparatus according to claim 16, characterized in that, The application display module is also used to display candidate application identifiers of shareable applications in the target organization in response to an application sharing event triggered by a member account of the target organization; and to display at least one target application identifier as selected in response to a selection operation of at least one target application identifier among the candidate application identifiers.

22. The apparatus according to claim 16, characterized in that, The application sharing processing device further includes a scope adjustment module, which is used to respond to the shared member scope adjustment operation triggered by the member account of the target organization for the shared application, display the newly added shared member scope that changes from unselected to selected and the canceled shared member scope that changes from selected to unselected; asynchronously add the application entry of the target application to the application area of ​​each newly added shared member account included in the newly added shared member scope; asynchronously cancel the display of the application entry of the target application in the application area of ​​each canceled shared member account included in the canceled shared member scope.

23. The apparatus according to claim 16, characterized in that, The application sharing processing device also includes an application entry display status adjustment module, which is used to determine the changed member account when the members of the cooperative organization change; and when the changed member account is within the scope of shared members, adjust the display status of the application entry of the target application in the application containing area of ​​the changed member account according to the change type corresponding to the changed member account.

24. The apparatus according to claim 16, characterized in that, The scope of shared members includes at least one department of the cooperative organization; the application sharing processing device further includes an application entry display status adjustment module, which, in response to a new member addition event of at least one department in the scope of shared members, adds the application entry of the target application in the application containment area of ​​the new member; and in response to a exit event of at least one department in the scope of shared members, cancels the display of the application entry of the target application in the application containment area of ​​the exiting member.

25. The apparatus according to claim 24, characterized in that, The display status adjustment module is also used to respond to the addition of a department member event in at least one department within the shared member scope, to assign the account of the new member to the new member queue of the target application to be added; and to add the target application to the account of each new member in the new member queue in sequence, so that the application entry of the target application is added asynchronously in the application containment area of ​​each new member's account.

26. The apparatus according to claim 24, characterized in that, The display status adjustment module is also used to respond to the exit event of at least one department member in the shared member scope, assign the exit member's account to the exit member queue of the target application to be removed; and sequentially remove the target application from the accounts of each exit member in the exit member queue, so that the application entry of the target application is asynchronously canceled in the application containing area of ​​each exit member's account.

27. The apparatus according to claim 16, characterized in that, The application sharing processing device also includes a prompt message display module, which displays the current number of members that can be shared by the target application, corresponding to the member accounts of the target organization; when the number of shared member accounts included in the shared member range of the target application is greater than the current number of members that can be shared, an operation prompt message for increasing the number of shared members of the target application is displayed.

28. The apparatus according to claim 27, characterized in that, The range display module is also used to respond to the member account of the target organization's selection operation of the superior department in the cooperative organization. When the number of people in the superior department is greater than the current number of shareable members of the target application, the candidate subordinate departments of the superior department are displayed. In response to selecting at least a subset of target subordinate departments from the candidate subordinate departments, the selected target subordinate departments are displayed; the scope of shared members includes the shared member accounts contained in each of the selected target subordinate departments.

29. The apparatus according to claim 27, characterized in that, The range display module is also used to respond to a member account of the target organization selecting a target sub-department of the cooperative organization, and when the number of people in the target sub-department is greater than the current number of shareable members, display the candidate member accounts contained in the target sub-department; In response to selecting at least a subset of target member accounts from candidate member accounts, the selected target member accounts are displayed; the shared member scope includes the selected target member accounts.

30. The apparatus according to any one of claims 16 to 29, characterized in that, The application sharing processing device also includes a prompt message display module, which displays the effective sharing time of the target application corresponding to the member account of the target organization; and displays an operation prompt message to increase the effective sharing time of the target application when the current time exceeds the effective sharing time of the target application.

31. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 15.

32. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 15.

33. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 15.

Images