WO2019114654A1 - 跨团体的数据共享方法及装置 - Google Patents

跨团体的数据共享方法及装置 Download PDF

Info

Publication number
WO2019114654A1
WO2019114654A1 PCT/CN2018/120078 CN2018120078W WO2019114654A1 WO 2019114654 A1 WO2019114654 A1 WO 2019114654A1 CN 2018120078 W CN2018120078 W CN 2018120078W WO 2019114654 A1 WO2019114654 A1 WO 2019114654A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
project
cooperation
cross
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/120078
Other languages
English (en)
French (fr)
Inventor
余鹏
丁扬
姚志高
方奕东
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to EP18888467.0A priority Critical patent/EP3726446A4/en
Priority to JP2020529359A priority patent/JP7294748B2/ja
Priority to US16/766,819 priority patent/US12354064B2/en
Publication of WO2019114654A1 publication Critical patent/WO2019114654A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Definitions

  • One or more embodiments of the present disclosure relate to the field of terminal technologies, and in particular, to a cross-group data sharing method and apparatus.
  • one or more embodiments of the present specification provide a cross-group data sharing method and apparatus.
  • a method for data sharing across groups including:
  • the any group and the other groups implement cross-group collaboration to share cooperation data in the group cooperation process between the any group and the other groups.
  • a cross-group data sharing method including:
  • the cross-group collaboration platform determines a group participating in the cooperation project to be set as a project partner of the cooperation project
  • the cross-group collaboration platform shares collaboration data between project partners of the collaborative project.
  • a cross-group data sharing method including:
  • Any group initiates a collaborative project creation request to the cross-group collaborative platform to create a collaborative project on the cross-group collaborative platform;
  • the cooperation data is shared between the any group and at least one other group participating in the cooperation project.
  • a cross-group data sharing method including:
  • the cooperation data is shared between the any group and at least one other group participating in the cooperation project.
  • an inter-group data sharing apparatus including:
  • the approval unit enables any group to initiate a collaborative approval process for other groups
  • a collaboration unit when the cooperation approval process passes the approval, enabling the any group to cooperate with the other group to achieve inter-group cooperation, so as to share cooperation in the group cooperation process between the any group and the other group data.
  • an inter-group data sharing apparatus including:
  • the inter-group collaboration platform Determining a unit, the inter-group collaboration platform determining a group participating in the cooperation project to be set as a project partner of the cooperation project;
  • the sharing unit enables the cross-group collaborative platform to share cooperation data between project partners of the cooperation project.
  • an inter-group data sharing apparatus including:
  • the sharing unit shares the cooperation data between the any group and at least one other group participating in the cooperation project.
  • an inter-group data sharing apparatus including:
  • Participation unit to enable any group to participate in collaborative projects created on cross-group collaboration platforms
  • the sharing unit shares the cooperation data between the any group and at least one other group participating in the cooperation project.
  • FIG. 1 is a schematic structural diagram of an inter-group collaboration system according to an exemplary embodiment
  • FIG. 2 is a flowchart of a cross-group data sharing method according to an exemplary embodiment
  • FIG. 3 is a flowchart of a platform-side cross-group data sharing method according to an exemplary embodiment
  • FIG. 4A is a flowchart of a data sharing method based on creating a side of a cross-group according to an exemplary embodiment
  • FIG. 4B is a flowchart of a method for sharing data based on a participant-side cross-group according to an exemplary embodiment
  • FIG. 5 is a schematic diagram of an interaction process for implementing cross-enterprise collaboration according to an exemplary embodiment
  • FIG. 6 is a schematic diagram of a project creation application interface provided by an exemplary embodiment
  • FIG. 7 is a schematic diagram of an approval interface provided by an exemplary embodiment
  • FIG. 8 is a schematic diagram of a project management interface provided by an exemplary embodiment
  • FIG. 9 is a schematic diagram of a project participation application interface provided by an exemplary embodiment.
  • FIG. 10 is a schematic diagram of another approval interface provided by an exemplary embodiment
  • FIG. 11 is a schematic diagram of an approval interface for adding a trusted partner according to an exemplary embodiment
  • FIG. 12 is a schematic diagram of another project management interface provided by an exemplary embodiment
  • FIG. 13 is a schematic diagram of still another project management interface provided by an exemplary embodiment
  • FIG. 14 is a schematic structural diagram of an apparatus according to an exemplary embodiment
  • FIG. 15 is a block diagram of a cross-group data sharing apparatus according to an exemplary embodiment
  • FIG. 16 is a block diagram of a platform-side cross-group data sharing apparatus according to an exemplary embodiment
  • FIG. 17 is a block diagram of a data sharing apparatus based on creating a side of a cross-group according to an exemplary embodiment
  • FIG. 18 is a block diagram of a participant-side cross-group data sharing apparatus according to an exemplary embodiment.
  • the steps of the corresponding method are not necessarily performed in the order shown and described in the specification in other embodiments. In some other embodiments, the method may include more or fewer steps than those described herein. In addition, the individual steps described in this specification may be decomposed into multiple steps for description in other embodiments; while the multiple steps described in this specification may be combined into a single step in other embodiments. description.
  • FIG. 1 is a schematic structural diagram of an inter-group collaboration system according to an exemplary embodiment.
  • the system may include a server 11, a network 12, and a plurality of electronic devices corresponding to respective groups, such as a mobile phone 131 of a group 1, a PC 132, a mobile phone 141 of a group 2, a PC 142, a mobile phone 151 of a group 3, a PC 152, and the like. .
  • the server 11 may be a physical server including a separate host, or the server 11 may be a virtual server hosted by the host cluster. During the running process, the server 11 can run a server-side program of an application to implement related business functions of the application, for example, when the server 11 runs a program of the inter-group collaborative platform, the inter-group collaborative platform can be implemented. Server.
  • the mobile phones 131 to 151 and the PCs 132 to 152 are only some types of electronic devices that can be used by members corresponding to the group.
  • electronic devices such as tablet devices, notebook computers, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc., one or more of the present specification can also be used.
  • the electronic device can run a client-side program of an application to implement related business functions of the application, for example, when the electronic device runs a program of a cross-group collaborative platform, the inter-group collaboration can be implemented.
  • the client of the platform is not limited to a program of an application to implement related business functions of the application.
  • the application of the client of the inter-group collaboration platform can be pre-installed on the electronic device so that the client can be launched and run on the electronic device; of course, when adopting an online "client” such as HTML5 technology "You can get and run the client without installing the appropriate application on the electronic device.”
  • the network 12 that interacts between the mobile phones 131-151 and the PCs 132-152 and the server 11 may include multiple types of wired or wireless networks.
  • the network 12 may include a Public Switched Telephone Network (PSTN) and the Internet.
  • PSTN Public Switched Telephone Network
  • FIG. 2 is a flowchart of a platform-side cross-group data sharing method provided by an exemplary embodiment. As shown in FIG. 2, the method is applied to an electronic device (such as the mobile phones 131-151 and PC132-152 shown in FIG. 1), and may include the following steps:
  • step 202 any group initiates a collaborative approval process for other groups.
  • the any group may initiate a cooperative project for the cross-group collaboration of the other groups, that is, the group as the initiator of the cooperation project and other groups as the participants, then Describe the cooperation approval process of other groups to determine whether to allow the cooperation project to be created; for example, when the approval is passed, the cooperation project can be smoothly created, so that the group and the other group can realize cross-group collaboration based on the cooperation project, and When the approval fails, the collaborative project will not be allowed to be created, and cross-group collaboration will not be achieved.
  • the cooperation project can be created by any one of the groups, and the data management and processing control for the cooperation project are implemented in any one of the groups, and the server of the inter-group collaboration platform is only used as the group and other The data channel between the groups; or the project creation request may be initiated by the any group to the server of the cross-group collaboration platform, and the cooperation project creates a cooperation project, performs data management and processing control on the cooperation project, and the like.
  • the cooperation project of the cross-group collaboration may be initiated by other groups, that is, the other group as the initiator of the cooperation project, the any group as the participant, then the cooperation approval process for the other group may be initiated.
  • This cooperation project makes it impossible to achieve cross-group collaboration.
  • the creation process of the cooperation project is similar to the above embodiment, and the cooperation group may create a cooperation project by itself, and the server of the inter-group collaboration platform only serves as a data channel, or may be a group of other groups.
  • a project creation request is initiated to the server of the cross-group collaboration platform, and the cooperation project creates a cooperation project, performs data management and processing control on the cooperation project, and the like.
  • Step 204 When the cooperation approval process passes the approval, the any group and the other group implement cross-group collaboration to share cooperation data in the group collaboration process between the any group and the other group. .
  • the any group when the any group is the originator of the cooperation project, the any group may obtain verification information corresponding to the cooperation item to provide to the other community.
  • the verification information may include any form of an invitation code (a character string composed of several characters), a barcode (such as a one-dimensional barcode, a two-dimensional code, etc.), and the present specification does not limit this.
  • the any group may provide the verification information to other groups by any means, such as sending by instant messaging application, mail, short message, telephone, etc., or even verbally, and the present specification does not limit this.
  • the other group may send an item participation request including the verification information, so that after the verification information passes the verification, confirm that the other group participates in The collaborative project thereby enabling cross-group collaboration between the any of the groups and the other groups.
  • the cooperation project is created and maintained by the any group
  • the other group sends the above project participation request to the group and is verified by the any group; when the cooperation project is served by the server of the inter-group collaboration platform
  • other groups send the above project participation request to the server and be verified by the server.
  • the other group when the group is a participant of the cooperation project and the other group is an initiator, the other group may obtain verification information corresponding to the cooperation item and notify the any group. Then, the any group may participate in the cooperation project through the verification information to achieve cross-group collaboration with the other groups; for example, when the cooperation project is created and maintained by the other group, the A group sends the above project participation request to the other group and is verified by the other group; when the cooperation project is created and maintained by the server of the cross-group collaboration platform, the group sends the above project participation request to The server is authenticated by the server.
  • any one of the groups may perform trust evaluation or approval on other groups in advance, and pre-configure a group such as long-term cooperation and high trust as a trusted group, when the other groups are pre-configured.
  • a trusted group any one of the groups may directly implement cross-group cooperation with the other groups while ignoring the cooperation approval process, thereby contributing to the improvement of the collaboration efficiency.
  • any of the above groups is a group AA
  • other groups include a group BB, a group CC, etc.
  • cooperation data can be shared among all groups.
  • the cooperation data of the group AA can be shared to the group BB and the group CC
  • the cooperation data of the group BB can be shared to the group AA and the group CC
  • the cooperative data of the group CC It can be shared to the group AA and the group BB so that the sharing of the cooperation data can be achieved between any two of the groups participating in the cross-group collaboration.
  • each group participating in the cross-group collaboration may set at least one other group as a shared object.
  • the group AA sets the group BB as a shared object, and the cooperation data of the group AA can be shared to the group BB, Shared to the community CC; of course, the community CC can still set the group AA as a shared object, so that the cooperation data is shared by the community CC to the group AA unidirectionally.
  • FIG. 3 is a flowchart of a platform-side cross-group data sharing method provided by an exemplary embodiment. As shown in FIG. 3, the method is applied to a server (such as the server 11 shown in FIG. 1), and may include the following steps:
  • Step 302 Create a cooperation project across the group collaboration platform.
  • the cross-group collaboration platform may create a corresponding collaborative project based on a project creation request initiated by any group.
  • the cross-group collaboration platform may create a cooperation project by itself or create a cooperation project by other means, which is not limited in this specification.
  • the cross-group collaborative platform may specify a community associated with the collaborative project; wherein, when the collaborative project is created based on a project creation request initiated by any community, any of the The group specifies the associated group. For example, groups that are allowed to participate in the collaborative project can be restricted to those designated groups, while others cannot participate in the collaborative project.
  • the cross-group collaboration platform can send project participation invitations to designated groups such that the groups can participate in the collaborative project by confirming the response to the project participation invitation.
  • the cross-group collaboration platform may control the group participating in the cooperation project by other means without specifying the group associated with the cooperation project. For example, when a collaborative project is created based on a project creation request initiated by any group, the cross-group collaborative platform may participate in the invitation to the project sent to the target community based on the target group indicated by the any group. For another example, when the cooperation project is created based on a project creation request initiated by any group, the inter-group collaboration platform may provide verification information corresponding to the cooperation project to the any group, and the group may send the verification information. To other groups.
  • Step 304 The cross-group collaboration platform determines a group participating in the cooperation project to be set as a project partner of the cooperation project.
  • the cross-group collaborative platform may determine that any of the groups participate in the collaborative project. For example, when the group AA initiates a project creation request to the cross-group collaboration platform, so that the cross-group collaboration platform creates a corresponding cooperation project, the group AA may participate in the cooperation project by default.
  • the inter-group collaborative platform may determine that the target group participates in the collaborative project when an item participation invitation sent to the target group indicated by the any group is acknowledged. For example, assume that the group AA initiates a project creation request to the inter-group collaboration platform, such that the inter-group collaboration platform creates a corresponding cooperation project, and the group AA may indicate at least one target group to the inter-group collaboration platform, such as when the group AA indicates the group BB.
  • the inter-group collaboration platform may send a project participation invitation for the cooperation project to the target group such as the group BB or the group CC; wherein, when the group BB confirms the participation invitation of the project, it may determine The group BB participates in the cooperation project, and when the group CC refuses to answer or ignore the participation invitation of the project, it can be determined that the group CC does not participate in the cooperation project.
  • the group AA may indicate the target group before the cooperation project is created, such that the cooperation project is restricted between the group AA and the target group indicated by the group, and other groups are not allowed to participate in the cooperation project; in another case
  • the group AA may indicate the target group after the cooperation project is created; in another case, the group AA may update the target group after the cooperation project is created even if the target group is indicated before the cooperation project is created, this specification This is not a limitation.
  • the inter-group collaboration platform determines that the at least one group participates in the cooperation item;
  • the verification information is visible to the project partner of the cooperation project.
  • the group AA may be first confirmed as the project partner of the collaborative project, and the verification information may be visible to the group AA, such that the group AA may wish to cooperate with, for example,
  • the target group such as the group BB transmits the verification information, and the group BB can participate in the cooperation item described above based on the verification information.
  • the verification information may only be visible to the project partner who initiated the project creation request, such as only to the above-mentioned group AA, so that even if the group BB participates in the above-mentioned cooperation project and becomes a project partner, it may not be able to view. Go to the verification information.
  • the verification information can be visible to all project partners. For example, if the group BB participates in the above cooperation project and becomes a project partner, the verification information can be viewed, thereby further transmitting the verification information to the other. group.
  • the verification information may include any form of an invitation code (a character string composed of several characters), a barcode (such as a one-dimensional barcode, a two-dimensional code, etc.), and the present specification does not limit this.
  • an invitation code a character string composed of several characters
  • a barcode such as a one-dimensional barcode, a two-dimensional code, etc.
  • each project partner can start or end at any time by participating in or withdrawing from the cooperation project.
  • the sharing behavior of the cooperation data realizes the asynchronous participation or asynchronous exit of the cooperation project by each project partner, and does not need to reach the agreement among all the project partners to start or synchronously end the sharing behavior, which is convenient for multiple groups. Rapid synergy between the two parties, and even if some project partners have not joined or withdrawn from the cooperation project, it does not affect the local synergy between other project partners, which helps to improve the synergy efficiency.
  • Step 306 the cross-group collaboration platform shares cooperation data between project partners of the cooperation project.
  • the cross-group collaboration platform may share cooperation data of any project partner to all project partners in the cooperation project.
  • the cooperation data of the group AA can be shared to the group BB and the group CC
  • the cooperation data of the group BB can be shared to the group AA and the group CC
  • the group CC's collaborative data can be shared with Group AA and Group BB so that collaboration data can be shared between any two of the project partners.
  • the cross-group collaboration platform may acquire a shared object setting request initiated by any project partner; the inter-group collaboration platform may share the cooperation data of the any project partner to the shared object.
  • the group AA may select a project partner who wishes to implement sharing based on the shared object setting request, for example, when the shared object selected by the group AA is the group BB.
  • the shared data of the group AA can be shared to the group BB without being shared to the group CC; similarly, each project partner can set the shared object of the cooperation data of itself.
  • the cross-group collaboration platform may share the cooperation data between the remaining project partners without causing the sharing termination.
  • the sharing strategy adopted by the cross-group collaboration platform is to share the cooperation data of any project partner to all the project partners in the cooperation project
  • the “all project partners” may be updated to the above “remaining The project partner” and continue to implement the sharing strategy;
  • the cross-group collaboration platform determines the shared object corresponding to each project partner based on the shared object setting request, the cooperation data of the part of the project partner that has exited may be terminated to be shared to The remaining project partners will terminate the sharing of the cooperation data of the remaining project partners to the part of the project partners who have exited.
  • the project partner when any shared object set by any project partner exits the cooperation project, and the project partner does not belong to the shared object of other project partners, the project partner may be The cooperation project was kicked out to avoid the resources it occupied for the cooperation project.
  • the inter-group collaboration platform may store cooperation data generated by the project partner in a shared space corresponding to the cooperation project, and the shared space opens an authority to a project partner of the cooperation project.
  • the shared space corresponding to the cooperation project may be located on the cross-group collaborative platform, or may be located in a storage space outside the cross-group collaborative platform, which is not limited in this specification.
  • the cooperation data generated by all the project partners of the same cooperation project will be uniformly stored in the shared space corresponding to the cooperation project, so that each project partner can share the cooperation data in the shared space, which is helpful for upgrading. Sharing efficiency.
  • the cross-group collaboration platform may record the cooperation data generated by each project partner in a corresponding partner shared space; the cross-group collaboration platform may be respectively in the project partner of the cooperation project.
  • the automatic synchronization of the cooperation data is realized between the corresponding partner sharing spaces.
  • each project partner can use the corresponding partner shared space to record the cooperation data, and the partner shared space can be more consistent with the actual situation of the corresponding project partner, such as network status, storage space size, and the like;
  • the partner shared space can be the local storage space of the project partner, so even if the network status is not stable, the project partner can ensure that the cooperation data is stored in the local storage space, and after the network state is restored.
  • the collaborative data is automatically synchronized by the shared space of each partner by the cross-group collaboration platform.
  • the cross-group collaboration platform implements automatic synchronization of cooperation data between the shared spaces of the respective partners
  • periodic (or triggered) full data synchronization or incremental data synchronization may be adopted, and space may be shared in any partner.
  • any cooperation data within the data is edited or new cooperation data appears, the edited cooperation data or the newly added cooperation data is synchronized to the shared space of other partners without delay.
  • other forms of data synchronization schemes may also be employed, and the disclosure does not limit this.
  • the inter-group collaboration platform may record access rights of the cooperation data in the internal system of the at least one project partner, and the access rights are invalidated when the corresponding project partner exits the cooperation project.
  • the inter-group collaborative platform assists the said user by recording access rights to the internal system of the other project partner
  • a project partner accesses the collaborative data in the internal system of the other project partner.
  • the project partner can record the cooperation data in its own internal system, so that the internal team members of the project partner can retrieve the relevant cooperation data; and at the same time, record the access rights in the cross-group collaboration.
  • the platform rather than being assigned to project partners, helps limit the abuse of access rights by project partners and ensures that access to internal systems is achieved under the management of cross-group collaborative platforms.
  • the cross-group collaboration platform can establish cross-group collaboration separately by recording access rights to the internal system of the other project partner.
  • the access channel between the platform and the any project partner, the cross-group collaboration platform and the another project partner enables the project partner to implement secure access to the other project partner via the cross-group collaboration platform.
  • the access scope of the access authority to the corresponding internal system may include at least one of the following: a specific access path, data of a specific authority, data of a specific type, data generated by a specific time period, and employee generated by a specific department.
  • the data, etc., are not limited by this specification.
  • FIG. 4A is a flowchart of a data sharing method based on creating a side of a cross-group according to an exemplary embodiment. As shown in FIG. 4A, the method is applied to an electronic device (such as the mobile phones 131-151 and PC132-152 shown in FIG. 1), and may include the following steps:
  • any group initiates a collaborative project creation request to the inter-group collaborative platform to create a collaborative project on the cross-group collaborative platform.
  • step 404A the cooperation data is shared between the any group and at least one other group participating in the cooperation project.
  • the any group may indicate the target group related to the cooperation item to the cross-group collaboration platform, so that the cross-group collaboration platform sends a project participation invitation to the target group;
  • the project participation invitation receives a confirmation response from the target group, the target group is confirmed to participate in the cooperation project.
  • the any group may initiate a cooperation approval process for the target group, and when the cooperation approval process for the target group passes the approval, the any group to the inter-group collaboration platform Instructing the target group to cause the cross-group collaboration platform to send a project participation invitation to the target group.
  • any one of the groups may perform trust evaluation or approval on other groups in advance, and pre-configure a group such as long-term cooperation and high trust as a trusted group, when the target group is pre-configured.
  • the any group may indicate the target group to the inter-group collaboration platform if the cooperation approval process is ignored, so that the cross-group collaboration platform sends the project to the target group Participate in the invitation to increase the efficiency of the target group's participation in the collaborative project.
  • the any group may obtain verification information corresponding to the cooperation item, the verification information is also recorded in the cross-group collaboration platform; then, the any group sends the location to the target group
  • the verification information is such that when the target group sends a project participation request including the verification information to the inter-group collaboration platform, it is confirmed to participate in the cooperation item.
  • the verification information may include any form of an invitation code (a character string composed of several characters), a barcode (such as a one-dimensional barcode, a two-dimensional code, etc.), and the present specification does not limit the same.
  • the any group may initiate a cooperation approval process for the target group, and when the cooperation approval process for the target group passes the approval, the any group sends the organization to the target group. Describe the verification information. In an embodiment, when the target community is a pre-configured trusted community, the any group sends the verification information to the target community if the cooperation approval process is ignored.
  • any of the above-mentioned groups is a group AA
  • other groups participating in the cooperation project include a group BB, a group CC, and the like
  • cooperation data can be shared among all groups.
  • the cooperation data of the group AA can be shared to the group BB and the group CC
  • the cooperation data of the group BB can be shared to the group AA and the group CC
  • the cooperative data of the group CC It can be shared to group AA and group BB so that sharing of collaborative data can be achieved between any two project partners of all project partners.
  • each group participating in the cooperation project may initiate a sharing object setting request to the inter-group collaboration platform, and set at least one group participating in the cooperation project as a shared object, for example, the group AA sets the group BB as a sharing. Objects, then the cooperation data of the group AA can be shared to the group BB, not shared to the group CC; of course, the group CC can still set the group AA as a shared object, so that the cooperation data is shared by the group CC to the group AA unidirectionally.
  • FIG. 4B is a flowchart of a method for sharing data based on a participant-side cross-group according to an exemplary embodiment. As shown in FIG. 4B, the method is applied to an electronic device (such as the mobile phones 131-151 and PC132-152 shown in FIG. 1), and may include the following steps:
  • step 402B any group participates in the cooperation project created on the cross-group collaboration platform.
  • the cooperation project may be created by an embodiment such as that shown in FIG. 3 above; in other embodiments, the cooperation project may also be created by other means, and the specification does not limit this.
  • the any group may perform a confirmation response to the project participation invitation to participate in the cooperation project.
  • the inter-group collaboration platform may send a project participation invitation to the group under the instruction of the group requesting to create the cooperation project or the group that has participated in the cooperation project.
  • the cooperation approval process for other groups participating in the cooperation project may be initiated, and when the cooperation approval process for the other group is approved, the project is Participate in the invitation to confirm the response.
  • the other community is a pre-configured trusted group, the any group acknowledgment the project participation invitation in the case of ignoring the cooperation approval process.
  • the group may send an item participation request including the verification information to the inter-group collaboration platform to The verification information participates in the cooperation item corresponding to the cooperation item.
  • the any group initiates a collaborative approval process for other groups that send the verification information, and when the cooperation approval process for the other group passes the approval, the any group to the cross
  • the group collaboration platform sends a project participation request including the verification information.
  • the any group when the other community is a pre-configured trusted community, the any group sends the verification information including the verification information to the inter-group collaboration platform, ignoring the cooperation approval process. Project participation request.
  • step 404B the cooperation data is shared between the any group and at least one other group participating in the cooperation project.
  • any of the above-mentioned groups is a group AA
  • other groups participating in the cooperation project include a group BB, a group CC, and the like
  • cooperation data can be shared among all groups.
  • the cooperation data of the group AA can be shared to the group BB and the group CC
  • the cooperation data of the group BB can be shared to the group AA and the group CC
  • the cooperative data of the group CC It can be shared to group AA and group BB so that sharing of collaborative data can be achieved between any two project partners of all project partners.
  • each group participating in the cooperation project may initiate a sharing object setting request to the inter-group collaboration platform, and set at least one group participating in the cooperation project as a shared object, for example, the group AA sets the group BB as a sharing. Objects, then the cooperation data of the group AA can be shared to the group BB, not shared to the group CC; of course, the group CC can still set the group AA as a shared object, so that the cooperation data is shared by the group CC to the group AA unidirectionally.
  • enterprise equipment used by enterprise members of enterprise AA, enterprise BB, and enterprise CC runs a client with cross-group collaborative platform, and the enterprise members of enterprise AA are corresponding.
  • the enterprise equipment used by enterprise members of enterprise AA, enterprise BB, and enterprise CC runs a client with cross-group collaborative platform, and the enterprise members of enterprise AA are corresponding.
  • On the client log in to its own user account and configure it to correspond to the collaboration end 1 of the enterprise AA.
  • the enterprise member of the enterprise BB logs in its own user account on the corresponding client and configures it to correspond to the collaboration of the enterprise BB.
  • End 2 the enterprise member of the enterprise CC logs in its own user account on the corresponding client, and configures it to correspond to the collaboration terminal 3 of the enterprise CC.
  • the enterprise AA is taken as an example; there may be several enterprise members in the enterprise AA, and the electronic devices used by the enterprise members respectively run the clients of the cross-group collaborative platform, although the user accounts of the enterprise members logged in on the client are different,
  • the corresponding client can be understood as being configured as the above-mentioned collaboration terminal 1, that is, "synergy 1" can be understood as a collection of clients logged in by all enterprise members of the enterprise AA. It is not the client corresponding to the user account of a certain enterprise member in the enterprise AA.
  • the collaboration end 2 of the enterprise BB and the coordination end 3 of the enterprise CC can also be understood as similar "sets", which will not be described here.
  • FIG. 5 is a schematic diagram of an interaction process for implementing cross-enterprise collaboration according to an exemplary embodiment.
  • collaborative research and development between the enterprise AA, the enterprise BB, and the enterprise CC may be implemented, and the interaction process may include The following steps:
  • step 501 the collaboration end 1 submits a project creation application.
  • FIG. 6 is a schematic diagram of a project creation application interface provided by an exemplary embodiment; if the application is initiated by a member of the enterprise AA, the collaboration terminal 1 may provide a project creation application interface 600 as shown in FIG.
  • the project creation application interface 600 can be entered to create a cooperation project, and when the white label 604 is selected, the corresponding project participation application interface can be entered to participate in the cooperation project created by other enterprises.
  • Xiaobai needs to fill in content related to the cooperation project, such as project name, project description, shared content, project leader, project member, partner enterprise, and the like.
  • the “shared content” indicates the type of cooperation data that the enterprise AA can share to the partner enterprise in the cooperation project.
  • the “basic information of the project”, the “member information of the project”, and the “work item” are selected in FIG. 6 .
  • Relevant data and configuration, etc., and in some cases, only some types of cooperation data may be checked, and this specification does not limit this; meanwhile, in other embodiments, in addition to the above-mentioned types of cooperation data, There are other types of collaborative data, and this specification does not limit this.
  • “Project Leader” and “Project Member” represent the members of the enterprise AA related to the cooperation project, so that after logging in to the collaboration terminal 1, the relevant members can participate in the cooperation project and share the cooperation data with the partner enterprise, and the enterprise AA Other members are unable to do this.
  • the “partner company” may include any enterprise registered on the cross-group collaboration platform. For example, Xiaobai may add the corresponding enterprise as a partner enterprise by inputting the enterprise name and enterprise ID.
  • the cooperation project to be created is an "X project", which is used for "cooperative development of new products for user needs"
  • enterprise AA project The person in charge is Xiaobai, the project members are white and black, the partner company is enterprise BB, enterprise CC, and the “basic information of the project”, “member information of the project” and “work item related data” allowed by the enterprise AA are allowed. Cooperative data sharing with the “configuration” is shared with the partner company. After confirming the correctness, Xiaobai can submit the project creation application for the “X Project” by triggering the “Submit Application” option in the application interface 600.
  • Step 502 Determine whether the project creation application passes the approval; when the approval is passed, the collaboration terminal 1 sends a project creation request to the server.
  • the collaboration 1 may create an internal approval operation for the project creation application of the "X Project".
  • FIG. 7 is a schematic diagram of an approval interface provided by an exemplary embodiment.
  • the "approval process” at the top and the “approval content” at the bottom are included, from the "approval process”.
  • the approving personnel for the project creation application include Xiaobai's supervisor and the second-level supervisor.
  • the approving personnel can create an application for the approval operation after viewing the “approval content”, and both the white and the approving personnel can During the entire approval process, the approval process for the above-mentioned project creation application is reviewed based on the “approval process”, in which: after submitting the application, Xiaobai will be reviewed by the supervisor; when the supervisor is approved, the second-level supervisor will review; After passing, confirm the approval.
  • the approval process of step 502 is not required. In some scenarios, the approval process can be completely omitted. In other scenarios, the approval process can be improved. For example, when the set partner company is a pre-configured trusted partner, the approval process can be omitted or directly approved, without the manual implementation of the supervisor and the secondary supervisor. Approval, which helps the rapid creation of collaborative projects. Among them, the configuration of the "trusted partner" will be detailed below.
  • the project creation application interface 600 is filled in by Xiaobai, and Xiaobai is the project leader of the enterprise AA for the cooperation project, this is obviously not necessary; in fact, the application creation application interface is created. There is no necessary relationship between the members who fill in the 600 and the project leader. This manual does not limit this.
  • Step 503 The server creates a corresponding cooperation item according to the item creation request sent by the collaboration end 1.
  • Step 504 The server generates a unique corresponding invitation code for the created cooperation item, and the collaboration end 1 can obtain the invitation code.
  • step 505 the collaboration end 1 sends the invitation code to the collaboration end 2 corresponding to the enterprise BB and the coordination end 3 corresponding to the enterprise CC.
  • the enterprise BB and the enterprise CC may be added to the cooperation project created by the enterprise AA based on the “invitation code”, thereby avoiding the participation of unrelated enterprises, and helping to improve data security in the process of cross-enterprise cooperation.
  • the collaboration end 1 can obtain the invitation code and display it in the approval interface 700 through an interaction operation with the server.
  • the invitation code can be as shown in FIG. 7.
  • the collaboration end 1 may provide a sending function for the invitation code to quickly send the invitation code indicated by the approval interface 700 to the collaboration terminal 2 and the collaboration terminal 3.
  • members such as Xiaobai of the enterprise AA may send the invitation code to the members of the enterprise BB or the enterprise CC through any other means, such as instant messaging applications, mails, short messages, telephones, etc., this specification does not limit.
  • FIG. 8 is a schematic diagram of a project management interface provided by an exemplary embodiment. It is assumed that after logging in to the collaboration terminal 1, the white can view the project management interface 800 as shown in FIG. 8 to view information about the X project. .
  • the project management interface 800 can provide tags 802-806, which respectively correspond to the enterprise AA as the party, the enterprise BB as the partner, and the enterprise CC; wherein, it is assumed that the white card selects the tag 804 corresponding to the enterprise BB, and the enterprise BB has not participated yet. To the cooperation project, it can be shown as “the partner has not joined the project” as shown in Figure 8.
  • the enterprise BB and the enterprise CC do not necessarily participate in the cooperation project created by the enterprise AA.
  • the enterprise AA can still complete the cooperative research and development process with the enterprise BB. Data sharing will not be affected by the fact that corporate CCs are not involved in the collaborative project.
  • the enterprise AA can take the lead in participating in the cooperation project and generate corresponding cooperation data, and will not be due to the fact that the enterprise BB and the enterprise CC have not participated yet. affected.
  • step 506 the collaboration terminal 2 and the collaboration terminal 3 respectively submit project participation applications.
  • FIG. 9 is a schematic diagram of a project participation application interface provided by an exemplary embodiment; as shown in FIG. 9, a tag 902-904 may be included in the project participation application interface 900, when the tag 902 is detected. When triggered, you can enter the corresponding project creation application interface to create a cooperation project. This can be referred to the embodiment shown in Figure 6, and will not be described here. When it is detected that the tag 904 is triggered, you can enter the project to participate. Apply interface 900 to participate in collaborative projects created by other companies.
  • the member of the enterprise BB opens the above-mentioned project participation application interface 900 on the collaboration terminal 2, thereby participating in the cooperation project-X project created by the enterprise AA as an example, and describes the participation cooperation project; and the members of the enterprise CC are in the coordination end.
  • the process of participating in the cooperation project is similar to the above process of the enterprise BB.
  • the project participation application interface 900 may provide an input box for filling in the invitation code. By filling in the input box, such as "b11fce" provided by the collaboration terminal 1, the project participation application interface 900 may be shown.
  • Cooperative project-X project related information such as project name, project description, shared content, partner enterprise-enterprise AA, etc.
  • members of the enterprise BB can configure the project leader and project members in the “information of the party”, for example, the project leader is Xiaomei, and the project members are Lao Wang and A Huang.
  • the project participation application for the "X project” is submitted by triggering the project to participate in the "submit application” option in the application interface 900.
  • step 507 it is determined whether the project participation application has passed the approval; when the approval is passed, the process proceeds to step 508.
  • the collaboration 2 may participate in an internal approval operation for the project participation application of the "X Project".
  • FIG. 10 is a schematic diagram of an approval interface provided by an exemplary embodiment.
  • the “approval process” at the top and the “approval content” below are included, from the “approval process”.
  • the approvers of the project participation application include Xiaomei (assuming that Xiaomei submitted the project participation application based on the project participation application interface 900 shown in Fig. 9), and the approver can view the approval.
  • the project participates in the application for approval, and Xiaomei and the approving personnel can check the approval progress of the above-mentioned project participation application based on the “approval process” throughout the approval process, in which: after submitting the application, Xiaomei submits the application. It shall be audited by the supervisor; after the supervisor has passed the examination, it shall be reviewed by the second-level supervisor; when the second-level supervisor is approved, the approval shall be confirmed.
  • the approval process of step 507 is not required. In some scenarios, the approval process can be completely omitted. In other scenarios, the approval process can be improved. For example, when the set partner company is a pre-configured trusted partner, the approval process can be omitted or directly approved, without the manual implementation of the supervisor and the secondary supervisor. Approval, which helps the rapid participation of collaborative projects. Among them, the configuration of “trusted partner” is similar to the “trusted partner” mentioned in step 502 above.
  • FIG. 11 is a schematic diagram of an approval interface for adding a trusted partner according to an exemplary embodiment.
  • a triggering operation for the "click this application” option in the project participation application interface 900 as shown in FIG. 9 is detected, an approval operation of configuring the enterprise AA as a "trusted partner" of the enterprise BB may be initiated, and The corresponding approval progress is viewed in an approval interface 1100 such as that shown in FIG.
  • the project creation application interface 600 shown in FIG. 6 it is also possible to display the "click this application” or the like for the added partner enterprise, thereby quickly adding the corresponding partner enterprise as a trusted cooperation. square.
  • Step 508 After the collaboration terminal 2 and the collaboration terminal 3 participate in the cooperation project, the cooperation data is shared with the collaboration terminal 1.
  • FIG. 12 is a schematic diagram of another project management interface provided by an exemplary embodiment. It is assumed that after logging in to the collaboration terminal 1, the project management interface 1200 shown in FIG. 12 can be viewed. View information about the X project.
  • the project management interface 1200 can provide tags 1202 to 1206, which respectively correspond to the enterprise AA as the party, the enterprise BB as the partner, and the enterprise CC; wherein, it is assumed that the white card selects the tag 1204 corresponding to the enterprise BB, and the enterprise BB has participated.
  • the cooperation project it can be displayed as the information shown in Figure 12, such as the project leader is Xiaomei, the project members are Lao Wang and A Huang, the shared content is “basic information of the project”, “member information of the project” and “ Work item related data and configuration” and so on.
  • the project management interface 1200 may include an access option 1208 as shown in FIG. 12, and the enterprise member such as white, white, and black of the collaborative end 1 may cooperate with the enterprise BB by triggering the access option 1208. Data for fast shared access.
  • enterprise members such as white, white, and black of the peer 1 can view the access options corresponding to the enterprise CC, thereby performing fast shared access to the cooperation data generated by the enterprise CC.
  • the enterprise members such as Xiaomei, Laowang, and Ahuang of the collaboration end 2, or the enterprise members of the collaborative end 3, can view the access option of the enterprise AA by triggering the tag 1202, and quickly perform the cooperation data generated by the enterprise AA. Shared access.
  • the enterprise BB and the enterprise CC There may be many situations between the enterprise BB and the enterprise CC. For example, in one case, only the sharing of cooperation data between the “owner” and the “partner” of the cooperation project is allowed, and the sharing between the “partners” is not allowed, then between the enterprise AA and the enterprise BB.
  • the cooperation data can be shared between the enterprise AA and the enterprise CC, but the cooperation data is not allowed to be shared between the enterprise BB and the enterprise CC.
  • all the participants of the cooperation project can mutually share the cooperation data, so that between the enterprise AA and the enterprise BB, between the enterprise AA and the enterprise CC, and between the enterprise BB and the enterprise CC, Achieve the sharing of collaborative data.
  • each collaboration terminal may have a corresponding storage space.
  • the collaboration terminal 1 corresponds to the storage space 1
  • the collaboration terminal 2 corresponds to the storage space 2.
  • the collaboration terminal 3 corresponds to the storage space 3 and the cooperation data generated by the enterprise member for storing the enterprise CC
  • the storage space may be For cloud space or local space, it can be a public space or a system space inside an enterprise.
  • each project participant When participating in the cooperation project-X project, each project participant gives the access rights of its storage space to the server of the inter-group collaboration platform, for example, the enterprise AA will access the storage space 1, and the enterprise BB will access the storage space 2.
  • the rights and enterprise storage respectively assign the access rights of the storage space 3 to the server of the inter-group collaboration platform; then, when the white triggers the access option 1208 as shown in FIG. 12, the server of the inter-group collaboration platform verifies the white space.
  • the access rights to the storage space 2 given by the enterprise BB can be utilized, and the access to the storage space 2 can be realized on the collaboration terminal 1, so that the cooperation data can be shared and the storage space can be ensured. Data security.
  • the server of the inter-group collaboration platform can actively synchronize data between the storage spaces corresponding to the respective collaboration ends, and then each project participant only needs to store its own storage space. Space access, you can view the cooperation data generated by all project participants, which can further simplify the operation.
  • the cooperation item may have a corresponding unified storage space, and all the collaboration ends correspond to the unified storage space, and the generated cooperation data is stored in the unified storage space.
  • FIG. 13 is a schematic diagram of still another project management interface provided by an exemplary embodiment.
  • an access option 1302 corresponding to all project participants may be included, and the enterprise AA, Both the enterprise BB and the enterprise CC can access the unified storage space corresponding to the cooperation project-X project based on the access option 1302.
  • the server of the inter-group collaboration platform may be based on the access option.
  • 1302 implements the identity information of the trigger of the triggering operation, and limits the cooperation data accessed by the trigger in the unified storage space. For example, when the trigger belongs to the enterprise AA, the cooperation data generated by the enterprise AA itself, the enterprise BB, and the enterprise CC can be accessed. When the trigger belongs to the enterprise BB, the cooperation data generated by the enterprise BB itself and the enterprise AA can be accessed, and the enterprise cannot be accessed.
  • the cooperation data generated by CC when the trigger belongs to the enterprise CC, can access the cooperation data generated by the enterprise CC itself and the enterprise AA, and cannot access the cooperation data generated by the enterprise BB.
  • the participants of the cooperation project may withdraw at any time.
  • the enterprise AA can still share the cooperation data with the enterprise BB.
  • the server of the cross-group collaboration platform can maintain the access rights of the cooperation data of the enterprise AA and the enterprise BB to the enterprise CC; of course, the enterprise CC can also access the cooperation data.
  • the enterprise AA and the enterprise BB will not be able to continue to access the cooperation data generated by the enterprise CC.
  • FIG. 14 is a schematic structural diagram of an apparatus provided by an exemplary embodiment.
  • the device includes a processor 1402, an internal bus 1404, a network interface 1406, a memory 1408, and a non-volatile memory 1410, and of course may also include hardware required for other services.
  • the processor 1402 reads the corresponding computer program from the non-volatile memory 1410 into the memory 1408 and then operates to form a cross-group data sharing device at a logical level.
  • one or more embodiments of the present specification do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution body of the following processing flow is not limited to each.
  • a logical unit which can also be a hardware or logic device.
  • the platform-based cross-group data sharing device may include:
  • the approval unit 1501 enables any group to initiate a cooperation approval process for other groups
  • the collaboration unit 1502 when the cooperation approval process passes the approval, enables the any group to cooperate with the other groups to achieve cross-group collaboration, in the process of sharing the group collaboration between the any group and the other groups. Cooperation data.
  • the approval unit 1501 is specifically configured to:
  • collaboration unit 1502 is specifically configured to:
  • the approval unit 1501 is specifically configured to:
  • collaboration unit 1502 is specifically configured to:
  • the any group participates in the cooperation project through the verification information to achieve cross-group collaboration with the other groups.
  • the cooperation item is created by any of the groups or the other groups that are the initiators;
  • the cooperation project is created by the inter-group collaboration platform after the cooperation project creation request is initiated by the any group or the other group as the initiator to the inter-group collaboration platform.
  • the collaboration unit 1502 enables the any group to implement cross-group collaboration with the other community if the cooperation approval process is ignored.
  • the platform-based cross-group data sharing device may include:
  • the determining unit 1602 is configured to determine, by the cross-group collaboration platform, a group participating in the cooperation project to be set as a project partner of the cooperation project;
  • the sharing unit 1603 causes the inter-group collaborative platform to share cooperation data between project partners of the cooperation project.
  • the determining unit 1602 causes the inter-group collaborative platform to determine a group that has participated in the cooperation project by using at least one of the following manners:
  • the inter-group collaboration platform determines that any one of the groups participates in the cooperation project;
  • the inter-group collaboration platform determines that the target group participates in the cooperation project
  • the inter-group collaboration platform determines that the at least one group participates in the cooperation item; wherein the verification information pair The project partners of the cooperation project are visible.
  • the sharing unit 1603 is specifically configured to:
  • the cross-group collaboration platform shares cooperation data of any project partner to all project partners in the cooperation project.
  • the sharing unit 1603 is specifically configured to:
  • the cross-group collaboration platform acquires a shared object setting request initiated by any project partner
  • the cross-group collaboration platform shares the cooperation data of the any project partner to the project partner indicated by the shared object setting request, and avoids sharing the cooperation data of the any project partner with other project partners.
  • the sharing unit 1603 is specifically configured to:
  • the cross-group collaborative platform shares cooperation data among the remaining project partners.
  • the sharing unit 1603 is specifically configured to:
  • the cross-group collaboration platform stores the cooperation data generated by the project partner in a shared space corresponding to the cooperation project, and the shared space opens the authority to the project partner of the cooperation project.
  • the sharing unit 1603 is specifically configured to:
  • the cross-group collaboration platform records the cooperation data generated by each project partner in the corresponding partner sharing space
  • the cross-group collaboration platform automatically synchronizes cooperation data between the partner shared spaces of the project partners of the cooperation project.
  • the sharing unit 1603 is specifically configured to:
  • the cross-group collaboration platform records access rights of the cooperation data of the internal system allocated by the at least one project partner, and the access rights are invalidated when the corresponding project partner withdraws from the cooperation project;
  • the inter-group collaborative platform assists any of the recorded access rights to the internal system of the other project partner
  • the project partner accesses the cooperation data in the internal system of the other project partner.
  • the access scope of the access authority to the corresponding internal system includes at least one of the following:
  • Specific access paths data for specific permissions, specific types of data, data generated for a specific time period, data generated by employees in a particular department.
  • the data sharing device based on the cross-group of the created party side may include:
  • the request unit 1701 enables any group to initiate a cooperation project creation request to the inter-group collaboration platform to create a cooperation project on the cross-group collaboration platform;
  • the sharing unit 1702 allows the cooperation data to be shared between the any group and at least one other group participating in the cooperation project.
  • it also includes:
  • Instructing unit 1703 causing the any group to indicate a target group related to the cooperation item to the cross-group collaboration platform, so that the cross-group collaboration platform sends a project participation invitation to the target group;
  • the target group is confirmed to participate in the cooperation item.
  • it also includes:
  • the obtaining unit 1704 is configured to enable the any group to obtain verification information corresponding to the cooperation item, where the verification information is further recorded in the cross-group collaboration platform;
  • the sending unit 1705 when the any group sends the verification information to the target community, so that when the target community sends the project participation request including the verification information to the inter-group collaboration platform, it is confirmed to participate in the Cooperation projects.
  • the sending unit 1705 is specifically configured to:
  • the group initiates a cooperation approval process for the target group, and when the cooperation approval process for the target group passes the approval, the any group sends the verification information to the target group;
  • the any group sends the verification information to the target community if the cooperation approval process is ignored.
  • the data sharing device based on the cross-group of the participant side may include:
  • the participation unit 1801 enables any group to participate in the cooperation project created on the cross-group collaboration platform;
  • the sharing unit 1802 allows the cooperation data to be shared between the any group and at least one other group participating in the cooperation project.
  • the participating unit 1801 is specifically configured to:
  • the any group receives the project participation invitation sent by the cross-group collaboration platform
  • the any group has a confirmation response to the project participation invitation to participate in the cooperation project.
  • the participating unit 1801 is specifically configured to:
  • the any group obtains verification information sent by other groups that have participated in the cooperation project;
  • the any group sends a project participation request including the verification information to the inter-group collaboration platform to participate in the cooperation item when the verification information corresponds to the cooperation item.
  • the participation unit 1801 causes the any group to send an item participation request including the verification information to the inter-group collaboration platform by:
  • the any group initiates a cooperation approval process for other groups that send the verification information, and when the cooperation approval process for the other group passes the approval, the any group sends the inclusion to the inter-group collaboration platform.
  • a project participation request for verification information
  • the any group sends an item participation request including the verification information to the inter-group collaboration platform without ignoring the cooperation approval process.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • a typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, and a game control.
  • a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • flash memory or other memory technology
  • compact disk read only memory CD-ROM
  • DVD digital versatile disk
  • Magnetic cassette tape disk storage
  • quantum memory graphene-based storage media or other magnetic storage devices or any other non-transporting media
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • first, second, third, etc. may be used to describe various information in one or more embodiments of the specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • the first information may also be referred to as the second information without departing from the scope of one or more embodiments of the present disclosure.
  • the second information may also be referred to as the first information.
  • the word "if” as used herein may be interpreted as "when” or "when” or "in response to a determination.”

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Data Mining & Analysis (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • General Business, Economics & Management (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本说明书一个或多个实施例提供一种跨团体的数据共享方法及装置，该方法可以包括：任一团体启动针对其他团体的合作审批流程；当所述合作审批流程通过审批时，所述任一团体与所述其他团体实现跨团体协同，以在所述任一团体与所述其他团体之间共享团体协同过程中的合作数据。

Description

跨团体的数据共享方法及装置
本申请要求2017年12月15日递交的申请号为201711353985.6、发明名称为“跨团体的数据共享方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本说明书一个或多个实施例涉及终端技术领域，尤其涉及一种跨团体的数据共享方法及装置。
背景技术
在相关技术中，往往涉及到多个团体之间的合作场景，使得多个团体的团体成员可以协同完成相关事件的处理。在合作过程中，需要在参与合作的多个团体之间对合作数据进行共享，相关技术中往往通过即时通讯、邮箱等渠道进行数据传输，不仅存在安全性低、难以管控的问题，而且共享效率十分低下。
发明内容
有鉴于此，本说明书一个或多个实施例提供一种跨团体的数据共享方法及装置。
为实现上述目的，本说明书一个或多个实施例提供技术方案如下：
根据本说明书一个或多个实施例的第一方面，提出了一种跨团体的数据共享方法，包括：
任一团体启动针对其他团体的合作审批流程；
当所述合作审批流程通过审批时，所述任一团体与所述其他团体实现跨团体协同，以在所述任一团体与所述其他团体之间共享团体协同过程中的合作数据。
根据本说明书一个或多个实施例的第二方面，提出了一种跨团体的数据共享方法，包括：
跨团体协同平台创建合作项目；
所述跨团体协同平台确定参与所述合作项目的团体，以设定为所述合作项目的项目合作方；
所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据。
根据本说明书一个或多个实施例的第三方面，提出了一种跨团体的数据共享方法， 包括：
任一团体向跨团体协同平台发起合作项目创建请求，以在所述跨团体协同平台上创建合作项目；
所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
根据本说明书一个或多个实施例的第四方面，提出了一种跨团体的数据共享方法，包括：
任一团体参与跨团体协同平台上创建的合作项目；
所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
根据本说明书一个或多个实施例的第五方面，提出了一种跨团体的数据共享装置，包括：
审批单元，使任一团体启动针对其他团体的合作审批流程；
协同单元，当所述合作审批流程通过审批时，使所述任一团体与所述其他团体实现跨团体协同，以在所述任一团体与所述其他团体之间共享团体协同过程中的合作数据。
根据本说明书一个或多个实施例的第六方面，提出了一种跨团体的数据共享装置，包括：
创建单元，使跨团体协同平台创建合作项目；
确定单元，使所述跨团体协同平台确定参与所述合作项目的团体，以设定为所述合作项目的项目合作方；
共享单元，使所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据。
根据本说明书一个或多个实施例的第七方面，提出了一种跨团体的数据共享装置，包括：
请求单元，使任一团体向跨团体协同平台发起合作项目创建请求，以在所述跨团体协同平台上创建合作项目；
共享单元，使所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
根据本说明书一个或多个实施例的第八方面，提出了一种跨团体的数据共享装置，包括：
参与单元，使任一团体参与跨团体协同平台上创建的合作项目；
共享单元，使所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
附图说明
图1是一示例性实施例提供的一种跨团体协同系统的架构示意图；
图2是一示例性实施例提供的一种跨团体的数据共享方法的流程图；
图3是一示例性实施例提供的一种基于平台侧的跨团体的数据共享方法的流程图；
图4A是一示例性实施例提供的一种基于创建方侧的跨团体的数据共享方法的流程图；
图4B是一示例性实施例提供的一种基于参与方侧的跨团体的数据共享方法的流程图；
图5是一示例性实施例提供的一种实现跨企业协同的交互过程的示意图；
图6是一示例性实施例提供的一种项目创建申请界面的示意图；
图7是一示例性实施例提供的一种审批界面的示意图；
图8是一示例性实施例提供的一种项目管理界面的示意图；
图9是一示例性实施例提供的一种项目参与申请界面的示意图；
图10是一示例性实施例提供的另一种审批界面的示意图；
图11是一示例性实施例提供的一种添加受信任合作方的审批界面的示意图；
图12是一示例性实施例提供的另一种项目管理界面的示意图；
图13是一示例性实施例提供的又一种项目管理界面的示意图；
图14是一示例性实施例提供的一种设备的结构示意图；
图15是一示例性实施例提供的一种跨团体的数据共享装置的框图；
图16是一示例性实施例提供的一种基于平台侧的跨团体的数据共享装置的框图；
图17是一示例性实施例提供的一种基于创建方侧的跨团体的数据共享装置的框图；
图18是一示例性实施例提供的一种基于参与方侧的跨团体的数据共享装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本说明书一个或多个实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本说明书一个或多个实施例的一些方面相一致的装置和方法的例子。
需要说明的是：在其他实施例中并不一定按照本说明书示出和描述的顺序来执行相应方法的步骤。在一些其他实施例中，其方法所包括的步骤可以比本说明书所描述的更多或更少。此外，本说明书中所描述的单个步骤，在其他实施例中可能被分解为多个步骤进行描述；而本说明书中所描述的多个步骤，在其他实施例中也可能被合并为单个步骤进行描述。
图1是一示例性实施例提供的一种跨团体协同系统的架构示意图。如图1所示，该系统可以包括服务器11、网络12、对应于各个团体的若干电子设备，比如团体1的手机131、PC132，团体2的手机141、PC142、团体3的手机151、PC152等。
服务器11可以为包含一独立主机的物理服务器，或者该服务器11可以为主机集群承载的虚拟服务器。在运行过程中，服务器11可以运行某一应用的服务器侧的程序，以实现该应用的相关业务功能，比如当该服务器11运行跨团体协同平台的程序时，可以实现为该跨团体协同平台的服务端。
手机131～151、PC132～152只是团体对应的成员可以使用的部分类型的电子设备。实际上，显然还可以使用诸如下述类型的电子设备：平板设备、笔记本电脑、掌上电脑(PDAs，Personal Digital Assistants)、可穿戴设备(如智能眼镜、智能手表等)等，本说明书一个或多个实施例并不对此进行限制。在运行过程中，该电子设备可以运行某一应用的客户端侧的程序，以实现该应用的相关业务功能，比如当该电子设备运行跨团体协同平台的程序时，可以实现为该跨团体协同平台的客户端。
需要指出的是：跨团体协同平台的客户端的应用程序可以被预先安装在电子设备上，使得该客户端可以在该电子设备上被启动并运行；当然，当采用诸如HTML5技术的在线“客户端”时，无需在电子设备上安装相应的应用程序，即可获得并运行该客户端。
而对于手机131～151、PC132～152与服务器11之间进行交互的网络12，可以包括多种类型的有线或无线网络。在一实施例中，该网络12可以包括公共交换电话网络(Public Switched Telephone Network，PSTN)和因特网。
图2是一示例性实施例提供的一种基于平台侧的跨团体的数据共享方法的流程图。如图2所示，该方法应用于电子设备(比如图1所示的手机131～151、PC132～152)，可以包括以下步骤：
步骤202，任一团体启动针对其他团体的合作审批流程。
在一实施例中，该任一团体可以发起针对所述其他团体的跨团体协同的合作项目，即该任一团体作为该合作项目的发起方、其他团体作为参与方，那么可以通过启动针对 所述其他团体的合作审批流程，确定是否允许创建该合作项目；例如，当审批通过时，该合作项目可以顺利创建，使得该任一团体与该其他团体可以基于该合作项目实现跨团体协同，而当审批未通过时，则该合作项目将不允许被创建、从而无法实现跨团体协同。
其中，可由该任一团体自行创建合作项目，那么针对该合作项目的数据管理、处理控制等，均在该任一团体处实现，而跨团体协同平台的服务端仅作为该任一团体与其他团体之间的数据通道；或者，可由该任一团体向跨团体协同平台的服务端发起项目创建请求，并由该服务端创建合作项目、对该合作项目进行数据管理和处理控制等。
在一实施例中，可由其他团体发起跨团体协同的合作项目，即该其他团体作为该合作项目的发起方、该任一团体作为参与方，那么可以通过启动针对该其他团体的合作审批流程，确定是否允许该任一团体参与该合作项目；例如，当审批通过时，该任一团体可以顺利参与该合作项目、实现跨团体协同，而当审批未通过时，则该任一团体不允许参与该合作项目、从而无法实现跨团体协同。
其中，对于其他团体发起的合作项目，该合作项目的创建过程与上述实施例相似，可以由该其他团体自行创建合作项目，而跨团体协同平台的服务端仅作为数据通道，或者可由该其他团体向跨团体协同平台的服务端发起项目创建请求，并由该服务端创建合作项目、对该合作项目进行数据管理和处理控制等。
步骤204，当所述合作审批流程通过审批时，所述任一团体与所述其他团体实现跨团体协同，以在所述任一团体与所述其他团体之间共享团体协同过程中的合作数据。
在一实施例中，当该任一团体为合作项目的发起方时，该任一团体可以获取对应于所述合作项目的验证信息，以提供至所述其他团体。比如，验证信息可以包括邀请码(若干字符构成的字符串)、条码(如一维条形码、二维码等)等任意形式，本说明书并不对此进行限制。其中，该任一团体可以通过任意方式将验证信息提供至其他团体，比如通过即时通讯应用、邮件、短信、电话等进行发送，甚至口头告知等，本说明书并不对此进行限制。
然后，当所述其他团体通过所述验证信息参与至所述合作项目时，比如该其他团体可以发送包含该验证信息的项目参与请求，从而在该验证信息通过验证后，确认该其他团体参与至该合作项目，从而在所述任一团体与所述其他团体之间实现跨团体协同。其中，当合作项目由该任一团体创建和维护时，其他团体将上述的项目参与请求发送至该任一团体，并由该任一团体进行验证；当合作项目由跨团体协同平台的服务端创建和维护时，其他团体将上述的项目参与请求发送至该服务端，并由该服务端进行验证。
在一实施例中，当该任一团体为合作项目的参与方、所述其他团体为发起方时，该其他团体可以获取对应于该合作项目的验证信息，并告知该任一团体。然后，该任一团体可以通过该所述验证信息参与至所述合作项目，以实现与所述其他团体之间的跨团体协同；例如，当合作项目由该其他团体创建和维护时，该任一团体将上述的项目参与请求发送至该其他团体，并由该其他团体进行验证；当合作项目由跨团体协同平台的服务端创建和维护时，该任一团体将上述的项目参与请求发送至该服务端，并由该服务端进行验证。
在一实施例中，所述任一团体可以预先对其他团体进行信任度评估或审批，将诸如长期合作、信任度高的团体预配置为受信任团体，那么当所述其他团体为预配置的受信任团体时，所述任一团体可以在忽略所述合作审批流程的情况下，直接与所述其他团体实现跨团体协同，有助于提升协同效率。
在一实施例中，假定上述的任一团体为团体AA，而其他团体包括团体BB、团体CC等，那么这些团体之间在共享合作数据时，可以具有多种情况。在一种情况下，可以在所有团体之间共享合作数据，比如团体AA的合作数据可以共享至团体BB和团体CC，团体BB的合作数据可以共享至团体AA和团体CC，团体CC的合作数据可以共享至团体AA和团体BB，从而在所有参与跨团体协同的团体中的任意两个团体之间均可以实现对合作数据的共享。在另一种情况下，参与跨团体协同的每一团体可以将至少一个其他团体设置为共享对象，比如团体AA将团体BB设置为共享对象，那么团体AA的合作数据可以共享至团体BB、不共享至团体CC；当然，团体CC仍然可以将团体AA设置为共享对象，从而由团体CC单向地将合作数据共享至团体AA。
图3是一示例性实施例提供的一种基于平台侧的跨团体的数据共享方法的流程图。如图3所示，该方法应用于服务器(比如图1所示的服务器11)，可以包括以下步骤：
步骤302，跨团体协同平台创建合作项目。
在一实施例中，跨团体协同平台可以基于任一团体发起的项目创建请求，创建相应的合作项目。
在另一实施例中，跨团体协同平台可以自行创建合作项目，或者通过其他途径创建合作项目，本说明书并不对此进行限制。
在一实施例中，跨团体协同平台在创建合作项目时，可以指定与该合作项目相关联的团体；其中，当合作项目是基于任一团体发起的项目创建请求而创建时，可由该任一团体对相关联的团体进行指定。例如，可以将允许参与至该合作项目的团体限制为指定 的这些团体，而其他团体则无法参与至该合作项目。再例如，跨团体协同平台可以向指定的这些团体发送项目参与邀请，以使得这些团体可以通过对该项目参与邀请进行确认应答后参与至该合作项目。
在一实施例中，跨团体协同平台在创建合作项目时，可以不指定与该合作项目相关联的团体，而通过其他方式控制参与至该合作项目的团体。例如，当合作项目是基于任一团体发起的项目创建请求而创建时，跨团体协同平台可以根据该任一团体指示的目标团体，向该目标团体发送的项目参与邀请。再例如，当合作项目是基于任一团体发起的项目创建请求而创建时，跨团体协同平台可以向该任一团体提供对应于该合作项目的验证信息，该任一团体可以将该验证信息发送至其他团体。
步骤304，所述跨团体协同平台确定参与所述合作项目的团体，以设定为所述合作项目的项目合作方。
在一实施例中，当所述合作项目是基于任一团体发起的项目创建请求而创建时，所述跨团体协同平台可以确定所述任一团体参与所述合作项目。例如，当团体AA向跨团体协同平台发起项目创建请求，使得跨团体协同平台创建了相应的合作项目时，可以默认为该团体AA参与至该合作项目中。
在一实施例中，当向所述任一团体指示的目标团体发送的项目参与邀请得到确认应答时，所述跨团体协同平台可以确定所述目标团体参与所述合作项目。例如，假定团体AA向跨团体协同平台发起项目创建请求，使得跨团体协同平台创建了相应的合作项目，该团体AA可以向跨团体协同平台指示至少一个目标团体，比如当该团体AA指示团体BB和团体CC为目标团体时，跨团体协同平台可以向该团体BB、团体CC等目标团体发送针对该合作项目的项目参与邀请；其中，当团体BB对该项目参与邀请进行确认应答时，可以确定该团体BB参与至该合作项目中，当团体CC对该项目参与邀请进行拒绝应答或忽略时，可以确定该团体CC未参与该合作项目。在一种情况下，团体AA可以在合作项目创建之前指示目标团体，使得该合作项目限制于团体AA及其指示的目标团体之间、不允许其他团体参与至该合作项目；在另一种情况下，团体AA可以在合作项目创建之后指示目标团体；在又一种情况下，团体AA即便在合作项目创建之前指示了目标团体，仍然可以在合作项目创建之后对该目标团体进行更新，本说明书并不对此进行限制。
在一实施例中，当收到的至少一个团体发送的项目参与请求中包含对应于所述合作项目的验证信息时，所述跨团体协同平台确定所述至少一个团体参与所述合作项目；其 中，所述验证信息对所述合作项目的项目合作方可见。例如，当合作项目由团体AA发起的项目创建请求而创建时，团体AA可以被首先确认为该合作项目的项目合作方，而验证信息可以对团体AA可见，使得团体AA可以向希望合作的诸如团体BB等目标团体发送该验证信息，而该团体BB可以基于该验证信息参与至上述的合作项目。在一种情况下，验证信息可以仅对发起项目创建请求的项目合作方可见，比如仅对上述的团体AA开放，使得即便团体BB参与至上述的合作项目后成为项目合作方，仍然可能无法查看到该验证信息。在另一种情况下，验证信息可以对所有的项目合作方可见，比如团体BB参与至上述的合作项目后成为项目合作方，即可查看到该验证信息，从而进一步将该验证信息发送至其他团体。
在一实施例中，验证信息可以包括邀请码(若干字符构成的字符串)、条码(如一维条形码、二维码等)等任意形式，本说明书并不对此进行限制。
在一实施例中，通过创建合作项目，并将参与该合作项目的团体作为项目合作方以共享合作数据，使得每个项目合作方均可以通过参与或退出该合作项目的方式，随时开始或结束对合作数据的共享行为，实现了各个项目合作方对该合作项目的异步参与或异步退出，无需在所有项目合作方之间全部达成一致后同步开始或同步结束该共享行为，便于在多个团体之间快速实现协同，并且即便部分项目合作方尚未加入或退出合作项目，也不影响其他项目合作方之间的局部协同，有助于提升协同效率。
步骤306，所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据。
在一实施例中，所述跨团体协同平台可以将任一项目合作方的合作数据共享至所述合作项目中的所有项目合作方。例如，当团体AA、团体BB和团体CC为同一合作项目的项目合作方时，团体AA的合作数据可以共享至团体BB和团体CC，团体BB的合作数据可以共享至团体AA和团体CC，团体CC的合作数据可以共享至团体AA和团体BB，从而在所有项目合作方中的任意两个项目合作方之间均可以实现对合作数据的共享。
在一实施例中，所述跨团体协同平台可以获取任一项目合作方发起的共享对象设置请求；所述跨团体协同平台可以将所述任一项目合作方的合作数据共享至所述共享对象设置请求指示的项目合作方，并避免向其他项目合作方共享所述任一项目合作方的合作数据。例如，当团体AA、团体BB和团体CC为同一合作项目的项目合作方时，团体AA可以基于共享对象设置请求而选取希望实施共享的项目合作方，比如当团体AA选取的共享对象为团体BB，那么团体AA的共享数据可以共享至团体BB、而不会共享至团 体CC；类似地，每个项目合作方均可以对自身的合作数据的共享对象进行设置。
在一实施例中，当部分项目合作方退出所述合作项目时，所述跨团体协同平台可以在剩余的项目合作方之间共享合作数据，而不会造成共享终止。其中，当跨团体协同平台采用的共享策略为将任一项目合作方的合作数据共享至所述合作项目中的所有项目合作方时，该“所有项目合作方”可以更新为上述的“剩余的项目合作方”，并继续实施该共享策略；当跨团体协同平台基于共享对象设置请求确定每一项目合作方对应的共享对象时，可以终止将已退出的该部分项目合作方的合作数据共享至剩余的项目合作方，并终止将剩余的项目合作方的合作数据共享至已退出的该部分项目合作方。
在一实施例中，当任一项目合作方设定的共享对象全部退出合作项目，且该任一项目合作方并不属于其他项目合作方的共享对象时，可以将该任一项目合作方从该合作项目中踢出，以避免其占用合作项目的资源。
在一实施例中，所述跨团体协同平台可以将所述项目合作方产生的合作数据存储于所述合作项目对应的共享空间，所述共享空间对所述合作项目的项目合作方开放权限。其中，合作项目对应的共享空间可以位于该跨团体协同平台上，也可以位于该跨团体协同平台之外的存储空间，本说明书并不对此进行限制。基于该实施例，同一合作项目的所有项目合作方产生的合作数据将统一存储于该合作项目对应的共享空间，便于各个项目合作方对该共享空间内的合作数据进行共享调用，有助于提升共享效率。
在一实施例中，所述跨团体协同平台可以将每一项目合作方产生的合作数据，记录于相应的合作方共享空间；所述跨团体协同平台可以在所述合作项目的项目合作方分别对应的合作方共享空间之间实现对合作数据的自动同步。基于该实施例，每一项目合作方可以利用自身对应的合作方共享空间来记录合作数据，该合作方共享空间可以更加符合于相应项目合作方的实际情况，比如网络状况、存储空间大小等；例如，合作方共享空间可以为项目合作方的本地存储空间，那么即便网络状态不太稳定的情况下，项目合作方也可以确保将合作数据存储于该本地存储空间，并在网络状态恢复稳定后由跨团体协同平台对各个合作方共享空间进行合作数据的自动同步。
其中，跨团体协同平台对各个合作方共享空间之间实施对合作数据的自动同步时，可以采用周期性(或触发性)的全量数据同步或增量数据同步，还可以在任一合作方共享空间内的任意合作数据被编辑或出现新增合作数据时，无延迟地将编辑后的合作数据或新增合作数据同步至其他合作方共享空间。当然，还可以采用其他形式的数据同步方案，本公开并不对此进行限制。
在一实施例中，所述跨团体协同平台可以记录至少一个项目合作方分配的对自身的内部系统中合作数据的访问权限，所述访问权限在相应的项目合作方退出所述合作项目时失效；当任一项目合作方发起对另一项目合作方的合作数据的访问请求时，所述跨团体协同平台通过记录的对所述另一项目合作方的内部系统的访问权限，协助所述任一项目合作方对所述另一项目合作方的内部系统中的合作数据进行访问。基于该实施例，项目合作方可以将合作数据记录于自身的内部系统中，便于该项目合作方的内部团体成员对相关的合作数据进行调取使用；同时，通过将访问权限记录于跨团体协同平台，而并非分配至项目合作方，有助于限制项目合作方对该访问权限的滥用，确保对内部系统的访问操作在跨团体协同平台的管理下实现。例如，当任一项目合作方发起对另一项目合作方的合作数据的访问请求时，跨团体协同平台通过记录的对该另一项目合作方的内部系统的访问权限，可以分别建立跨团体协同平台与该任一项目合作方、跨团体协同平台与该另一项目合作方之间的访问通道，使得该任一项目合作方可以经由跨团体协同平台对该另一项目合作方实现安全访问。
在一实施例中，所述访问权限对相应内部系统的访问范围可以包括以下至少之一：特定访问路径、特定权限的数据、特定类型的数据、特定时间段产生的数据、特定部门的员工产生的数据等，本说明书并不对此进行限制。
图4A是一示例性实施例提供的一种基于创建方侧的跨团体的数据共享方法的流程图。如图4A所示，该方法应用于电子设备(比如图1所示的手机131～151、PC132～152)，可以包括以下步骤：
步骤402A，任一团体向跨团体协同平台发起合作项目创建请求，以在所述跨团体协同平台上创建合作项目。
步骤404A，所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
在一实施例中，所述任一团体可以向所述跨团体协同平台指示与所述合作项目相关的目标团体，以使所述跨团体协同平台向所述目标团体发送项目参与邀请；其中，当所述项目参与邀请得到所述目标团体的确认应答时，所述目标团体被确认为参与至所述合作项目。
在一实施例中，所述任一团体可以启动针对所述目标团体的合作审批流程，并当针对所述目标团体的合作审批流程通过审批时，所述任一团体向所述跨团体协同平台指示所述目标团体，以使所述跨团体协同平台向所述目标团体发送项目参与邀请。在一实施 例中，所述任一团体可以预先对其他团体进行信任度评估或审批，将诸如长期合作、信任度高的团体预配置为受信任团体，那么当所述目标团体为预配置的受信任团体时，所述任一团体可以在忽略所述合作审批流程的情况下，向所述跨团体协同平台指示所述目标团体，以使所述跨团体协同平台向所述目标团体发送项目参与邀请，从而提升该目标团体参与至合作项目的效率。
在一实施例中，所述任一团体可以获取对应于所述合作项目的验证信息，所述验证信息还被记录于所述跨团体协同平台；然后，所述任一团体向目标团体发送所述验证信息，以使所述目标团体向所述跨团体协同平台发送包含所述验证信息的项目参与请求时，被确认为参与所述合作项目。其中，验证信息可以包括邀请码(若干字符构成的字符串)、条码(如一维条形码、二维码等)等任意形式，本说明书并不对此进行限制。
在一实施例中，所述任一团体可以启动针对所述目标团体的合作审批流程，并当针对所述目标团体的合作审批流程通过审批时，所述任一团体向所述目标团体发送所述验证信息。在一实施例中，当所述目标团体为预配置的受信任团体时，所述任一团体在忽略所述合作审批流程的情况下，向所述目标团体发送所述验证信息。
在一实施例中，假定上述的任一团体为团体AA，而参与所述合作项目的其他团体包括团体BB、团体CC等，那么这些团体之间在共享合作数据时，可以具有多种情况。在一种情况下，可以在所有团体之间共享合作数据，比如团体AA的合作数据可以共享至团体BB和团体CC，团体BB的合作数据可以共享至团体AA和团体CC，团体CC的合作数据可以共享至团体AA和团体BB，从而在所有项目合作方中的任意两个项目合作方之间均可以实现对合作数据的共享。在另一种情况下，参与至合作项目的每一团体可以向跨团体协同平台发起共享对象设置请求，将参与该合作项目的至少一个团体设置为共享对象，比如团体AA将团体BB设置为共享对象，那么团体AA的合作数据可以共享至团体BB、不共享至团体CC；当然，团体CC仍然可以将团体AA设置为共享对象，从而由团体CC单向地将合作数据共享至团体AA。
图4B是一示例性实施例提供的一种基于参与方侧的跨团体的数据共享方法的流程图。如图4B所示，该方法应用于电子设备(比如图1所示的手机131～151、PC132～152)，可以包括以下步骤：
步骤402B，任一团体参与跨团体协同平台上创建的合作项目。
在一实施例中，合作项目可以通过诸如上述图3所示的实施例而创建；在其他实施例中，合作项目也可以通过其他方式创建，本说明书并不对此进行限制。
在一实施例中，所述任一团体收到所述跨团体协同平台发送的项目参与邀请后，可以对所述项目参与邀请进行确认应答，以参与至所述合作项目。其中，跨团体协同平台可以在请求创建该合作项目的团体或者已参与至该合作项目的团体的指示下，向该任一团体发送项目参与邀请。
在一实施例中，所述任一团体收到项目参与邀请后，可以启动针对参与该合作项目的其他团体的合作审批流程，并当针对所述其他团体的合作审批流程通过审批时，对项目参与邀请进行确认应答。在一实施例中，当所述其他团体为预配置的受信任团体时，所述任一团体在忽略所述合作审批流程的情况下，对项目参与邀请进行确认应答。
在一实施例中，所述任一团体收到已参与至所述合作项目的其他团体发送的验证信息后，可以向所述跨团体协同平台发送包含所述验证信息的项目参与请求，以在所述验证信息对应于所述合作项目时参与至所述合作项目。
在一实施例中，所述任一团体启动针对发送所述验证信息的其他团体的合作审批流程，并当针对所述其他团体的合作审批流程通过审批时，所述任一团体向所述跨团体协同平台发送包含所述验证信息的项目参与请求。在一实施例中，当所述其他团体为预配置的受信任团体时，所述任一团体在忽略所述合作审批流程的情况下，向所述跨团体协同平台发送包含所述验证信息的项目参与请求。
步骤404B，所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
在一实施例中，假定上述的任一团体为团体AA，而参与所述合作项目的其他团体包括团体BB、团体CC等，那么这些团体之间在共享合作数据时，可以具有多种情况。在一种情况下，可以在所有团体之间共享合作数据，比如团体AA的合作数据可以共享至团体BB和团体CC，团体BB的合作数据可以共享至团体AA和团体CC，团体CC的合作数据可以共享至团体AA和团体BB，从而在所有项目合作方中的任意两个项目合作方之间均可以实现对合作数据的共享。在另一种情况下，参与至合作项目的每一团体可以向跨团体协同平台发起共享对象设置请求，将参与该合作项目的至少一个团体设置为共享对象，比如团体AA将团体BB设置为共享对象，那么团体AA的合作数据可以共享至团体BB、不共享至团体CC；当然，团体CC仍然可以将团体AA设置为共享对象，从而由团体CC单向地将合作数据共享至团体AA。
需要说明的是：本说明书中在描述“团体”实施操作时，应当理解为通过归属于相应团体的用户账号实施相应的操作，比如发起项目创建请求、发起项目参与请求、发送 验证信息、做出确认应答、指示目标团体等合作管理操作，再比如实施项目合作、生成合作数据等协同作业操作等，本说明书并不对此进行限制。
为了便于理解，以企业场景下的跨企业协同研发为例，对本说明书一个或多个实施例的技术方案进行说明。当然，本说明书中的“团体”除了企业之外，还可以包括学校、医院、部队、政府机关等多种类型，本说明书并不对此进行限制。
假定在企业AA、企业BB与企业CC之间需要实现协同研发，企业AA、企业BB、企业CC的企业成员使用的电子设备上运行有跨团体协同平台的客户端，企业AA的企业成员在相应的客户端上登录自身的用户账号、将其配置为对应于企业AA的协同端1，企业BB的企业成员在相应的客户端上登录自身的用户账号、将其配置为对应于企业BB的协同端2，企业CC的企业成员在相应的客户端上登录自身的用户账号、将其配置为对应于企业CC的协同端3。
其中，以企业AA为例；企业AA中可以存在若干企业成员，这些企业成员使用的电子设备上分别运行有跨团体协同平台的客户端，虽然这些企业成员在客户端上登录的用户账号不同，但是由于这些企业成员均归属于企业AA，因而相应的客户端均可以理解成被配置为上述的协同端1，即“协同端1”可以理解为企业AA的所有企业成员登录的客户端的集合，而并非企业AA内某一个企业成员的用户账号对应的客户端。类似地，企业BB的协同端2、企业CC的协同端3也可以理解为类似的“集合”，此处不再赘述。
图5是一示例性实施例提供的一种实现跨企业协同的交互过程的示意图。通过在上述的协同端1～3以及跨团体协同平台的服务端之间实施如图5所示的交互过程，可以实现企业AA、企业BB与企业CC之间的协同研发，该交互过程可以包括以下步骤：
步骤501，协同端1提交项目创建申请。
在一实施例中，假定由企业AA发起对合作项目的创建操作，由该企业AA内部提交项目创建申请，以申请创建相应的合作项目。例如图6是一示例性实施例提供的一种项目创建申请界面的示意图；假定由企业AA的成员小白发起申请，协同端1可以提供如图6所示的项目创建申请界面600，当小白选取标签602时，可以进入该项目创建申请界面600、以创建合作项目，而当小白选取标签604时，可以进入相应的项目参与申请界面、以参与其他企业创建的合作项目。
在一实施例中，在项目创建申请界面600内，小白需要填写与合作项目相关的内容，比如项目名称、项目描述、共享内容、项目负责人、项目成员、合作方企业等。其中，“共享内容”表示企业AA可以在该合作项目中共享至合作方企业的合作数据的类型，比 如图6中勾选了“项目的基本信息”、“项目的成员信息”、“工作项相关的数据和配置”等，而在一些情况下可以仅勾选部分类型的合作数据，本说明书并不对此进行限制；同时，在其他实施例中，除了上述类型的合作数据之外，还可以存在其他类型的合作数据，本说明书并不对此进行限制。“项目负责人”与“项目成员”表示企业AA内部与该合作项目相关的成员，使得相关成员在登录协同端1之后，可以参与至该合作项目、与合作方企业共享合作数据，而企业AA的其他成员则无法实现该操作。“合作方企业”可以包括在跨团体协同平台上注册的任意企业，比如小白可以通过输入企业名称、企业ID等方式，将相应的企业添加为合作方企业。
在一实施例中，基于如图6所示的实施例，假定所需创建的合作项目为“X项目”，该合作项目用于“合作研发面向用户需求的新产品…”，企业AA的项目负责人为小白、项目成员为白白和小黑，合作方企业为企业BB、企业CC，且允许将企业AA产生的“项目的基本信息”、“项目的成员信息”、“工作项相关的数据和配置”等合作数据共享至合作方企业。在确认无误后，小白可以通过触发项目创建申请界面600内的“提交申请”选项，提交针对“X项目”的项目创建申请。
步骤502，确定项目创建申请是否通过审批；当审批通过时，由协同端1向服务端发送项目创建请求。
在一实施例中，协同端1可以针对“X项目”的项目创建申请启用内部的审批操作。例如图7是一示例性实施例提供的一种审批界面的示意图，在如图7所示的审批界面中，包括位于上方的“审批流程”和下方的“审批内容”，从“审批流程”可以看出，对项目创建申请的审批人员包括小白的主管和二级主管，审批人员可以通过查看“审批内容”后，对该项目创建申请实施审批操作，而小白和审批人员均可以在整个审批过程中，基于“审批流程”查看针对上述的项目创建申请的审批进度，其中：小白提交申请后，由主管审核；当主管审核通过后，由二级主管审核；当二级主管审核通过后，确认审批通过。
需要指出的是：步骤502的审批过程并非必须。在一些场景下，可以完全省略该审批过程。在另一些场景下，可以改进该审批过程，比如当设定的合作方企业为预配置的受信任合作方时，可以省去审批过程或者直接通过审批、而不需要主管和二级主管手动实施审批，从而有助于合作项目的快速创建。其中，对于“受信任合作方”的配置，将在下文中予以详述。
此外，虽然在上述实施例中，由小白对项目创建申请界面600进行填写，且小白为 企业AA针对该合作项目的项目负责人，但是这显然并非必要；实际上，对项目创建申请界面600进行填写的成员与项目负责人之间并无必然关系，本说明书并不对此进行限制。
步骤503，服务端根据协同端1发送的项目创建请求，创建相应的合作项目。
步骤504，服务端为创建的合作项目生成唯一对应的邀请码，而协同端1可以获取该邀请码。
步骤505，协同端1将邀请码发送至企业BB对应的协同端2、企业CC对应的协同端3。
在一实施例中，可以基于“邀请码”的形式，使企业BB、企业CC添加至企业AA创建的合作项目，而避免无关企业的加入，有助于提升跨企业合作过程中的数据安全性。例如图7所示，在上述的审批通过后，协同端1可以通过与服务端之间的交互操作，获取邀请码并展示于审批界面700中，比如该邀请码可以为如图7所示的字符串“b11fce”。
在一实施例中，协同端1可以提供针对邀请码的发送功能，以将审批界面700所示的邀请码快捷地发送至协同端2、协同端3。在其他实施例中，企业AA的小白等成员可以通过其他任意途径，将邀请码发送至企业BB、企业CC的成员，比如即时通讯应用、邮件、短信、电话等，本说明书并不对此进行限制。
在一实施例中，在创建了上述的合作项目-X项目后，企业AA的项目负责人、项目成员等登录协同端1后，可以查看该X项目的相关信息。例如图8是一示例性实施例提供的一种项目管理界面的示意图，假定小白在登录协同端1后，可以查看到如图8所示的项目管理界面800，以查看X项目的相关信息。项目管理界面800可以提供标签802～806，分别对应于作为本方的企业AA、作为合作方的企业BB和企业CC；其中，假定小白选取了企业BB对应的标签804，而企业BB尚未参与至该合作项目，可以展示为如图8所示的“合作方人员尚未加入该项目”。
其中，企业BB和企业CC并不一定都会参与企业AA创建的合作项目，比如仅企业BB参与该合作项目、企业CC不参与该合作项目，那么企业AA仍然可以与企业BB完成合作研发过程中的数据共享，并不会由于企业CC不参与该合作项目而受到影响。类似地，即便企业BB、企业CC尚未参与至该合作项目的情况下，企业AA也可以率先参与至该合作项目中，并产生相应的合作数据，并不会由于企业BB、企业CC尚未参与而受到影响。可见，各个项目参与方对于合作项目的参与为异步实现，相互之间并不存在必然的关联或影响，并不需要所有项目参与方均予以确认后才能够创建或参与至合作项 目中，可以简化操作、提升效率。
步骤506，协同端2、协同端3分别提交项目参与申请。
在一实施例中，图9是一示例性实施例提供的一种项目参与申请界面的示意图；如图9所示，在项目参与申请界面900中可以包括标签902-904，当检测到标签902被触发时，可以进入相应的项目创建申请界面、以创建合作项目，这可以参考如图6所示的实施例，此处不再赘述；当检测到标签904被触发时，可以进入该项目参与申请界面900，以参与其他企业创建的合作项目。
下面以企业BB的成员在协同端2上开启上述的项目参与申请界面900，从而参与至企业AA创建的合作项目-X项目为例，对参与合作项目进行描述；而企业CC的成员在协同端3上参与该合作项目的过程，与企业BB的上述过程类似。如图9所示，项目参与申请界面900可以提供用于填写邀请码的输入框，通过在该输入框内填写诸如协同端1提供的“b11fce”，可以在该项目参与申请界面900上示出合作项目-X项目的相关信息，比如项目名称、项目描述、共享内容、合作方企业-企业AA等。同时，企业BB的成员可以对“本方信息”中的项目负责人、项目成员等进行配置，比如设定项目负责人为小美、项目成员为老王和阿黄等。在确认无误后，通过触发项目参与申请界面900内的“提交申请”选项，提交针对“X项目”的项目参与申请。
步骤507，确定项目参与申请是否通过审批；当审批通过时，转入步骤508。
在一实施例中，协同端2可以针对“X项目”的项目参与申请启用内部的审批操作。例如图10是一示例性实施例提供的一种审批界面的示意图，在如图10所示的审批界面中，包括位于上方的“审批流程”和下方的“审批内容”，从“审批流程”可以看出，对项目参与申请的审批人员包括小美(假定由小美基于图9所示的项目参与申请界面900提交了项目参与申请)的主管和二级主管，审批人员可以通过查看“审批内容”后，对该项目参与申请实施审批操作，而小美和审批人员均可以在整个审批过程中，基于“审批流程”查看针对上述的项目参与申请的审批进度，其中：小美提交申请后，由主管审核；当主管审核通过后，由二级主管审核；当二级主管审核通过后，确认审批通过。
需要指出的是：步骤507的审批过程并非必须。在一些场景下，可以完全省略该审批过程。在另一些场景下，可以改进该审批过程，比如当设定的合作方企业为预配置的受信任合作方时，可以省去审批过程或者直接通过审批、而不需要主管和二级主管手动实施审批，从而有助于合作项目的快速参与。其中，对于“受信任合作方”的配置，与上文中步骤502提及的“受信任合作方”类似，可以理解为：对于合作项目的创建或参 与进行审批，主要是考虑到合作方企业是否可信任、是否存在合作风险等问题，因而对于一般的合作方企业而言，一次审批操作的结果仅能够适用于一次创建或参与相应的合作项目(即该合作方企业参与的合作项目)的过程中，而对于一些长期合作、明显可信的企业，可以在单次审批时将其配置为“受信任合作方”或添加至“受信任合作方名单”，并将该审批操作的结果适用于多次创建或参与相应的合作项目的过程中，或者将该审批操作的结果适用于某一时间段(比如1年)内发生的所有创建或参与相应的合作项目的过程中，从而避免了每次创建或参与相应的合作项目时均需要实施审批操作。
例如，图11是一示例性实施例提供的一种添加受信任合作方的审批界面的示意图。当检测到针对如图9所示的项目参与申请界面900中的“点此申请”选项的触发操作时，可以发起将该企业AA配置为企业BB的“受信任合作方”的审批操作，并在诸如图11所示的审批界面1100中查看到相应的审批进度。类似地，在如图6所示的项目创建申请界面600中，也可以针对添加的合作方企业展示出“点此申请”或类似的选项，从而将相应的合作方企业快速添加为受信任合作方。
步骤508，协同端2、协同端3参与合作项目后，与协同端1之间实现合作数据的共享。
在一实施例中，图12是一示例性实施例提供的另一种项目管理界面的示意图，假定小白在登录协同端1后，可以查看到如图12所示的项目管理界面1200，以查看X项目的相关信息。项目管理界面1200可以提供标签1202～1206，分别对应于作为本方的企业AA、作为合作方的企业BB和企业CC；其中，假定小白选取了企业BB对应的标签1204，而企业BB已参与至该合作项目，可以展示为如图12所示的信息，比如项目负责人为小美、项目成员为老王和阿黄、共享内容为“项目的基本信息”、“项目的成员信息”和“工作项相关的数据和配置”等。
在一实施例中，项目管理界面1200可以包括如图12所示的访问选项1208，协同端1的小白、白白、小黑等企业成员可以通过触发该访问选项1208，对企业BB产生的合作数据进行快速的共享访问。类似地，通过触发标签1206，协同端1的小白、白白、小黑等企业成员可以查看到对应于企业CC的访问选项，从而对企业CC产生的合作数据进行快速的共享访问。
类似地，协同端2的小美、老王、阿黄等企业成员，或者协同端3的企业成员，可以通过触发标签1202查看到企业AA的访问选项，并对企业AA产生的合作数据进行快速的共享访问。
而对于企业BB与企业CC之间，可能存在多种情况。比如，在一种情况下，仅允许合作项目的“本方”与“合作方”之间实现合作数据的共享，而不允许“合作方”之间实现共享，那么企业AA与企业BB之间、企业AA与企业CC之间可以对合作数据进行共享，但是企业BB与企业CC之间并不允许实现合作数据的共享。在另一种情况下，合作项目的所有参与方之间均可以相互实现合作数据的共享，使得企业AA与企业BB之间、企业AA与企业CC之间、企业BB与企业CC之间均可以实现对合作数据的共享。
对于各个协同端所产生的合作数据，可以存在多种存储与访问的实现方案，本说明书并不对此进行限制。
在一实施例中，每一协同端可以存在对应的存储空间，比如协同端1对应于存储空间1、用于存储企业AA的企业成员产生的合作数据，协同端2对应于存储空间2、用于存储企业BB的企业成员产生的合作数据，协同端3对应于存储空间3、用于存储企业CC的企业成员产生的合作数据，本说明书并不限制上述存储空间的位置，比如该存储空间可以为云端空间或本地空间，可以为公共空间或企业内部的系统空间。在参与到合作项目-X项目时，每一项目参与方将自身存储空间的访问权限赋予跨团体协同平台的服务端，比如企业AA将存储空间1的访问权限、企业BB将存储空间2的访问权限、企业存储将存储空间3的访问权限分别赋予跨团体协同平台的服务端；那么，当小白触发如图12所示的访问选项1208时，跨团体协同平台的服务端在验证该小白属于协同端1后，可以利用企业BB赋予的针对存储空间2的访问权限，在协同端1上实现对该存储空间2的访问，从而既可以实现对合作数据的共享，又能够确保存储空间的数据安全性。
其中，除了对各个协同端对应的存储空间进行访问之外，跨团体协同平台的服务端可以主动对各个协同端对应的存储空间之间进行数据同步，那么各个项目参与方只需要对自身的存储空间进行访问，即可查看到所有项目参与方产生的合作数据，可以进一步简化操作。
在一实施例中，合作项目可以存在对应的统一存储空间，所有协同端均对应于该统一存储空间，并将产生的合作数据存储于该统一存储空间内。例如，图13是一示例性实施例提供的又一种项目管理界面的示意图，在如图13所示的项目管理界面1300中，可以包括对应于所有项目参与方的访问选项1302，企业AA、企业BB和企业CC均可以基于该访问选项1302对合作项目-X项目对应的统一存储空间进行访问。其中，当仅允许合作项目的“本方”与“合作方”之间实现合作数据的共享，而不允许“合作方”之间实现共享时，跨团体协同平台的服务端可以根据对访问选项1302实施触发操作的触发者 的身份信息，限制该触发者在统一存储空间内访问到的合作数据。例如，当触发者属于企业AA时，可以访问企业AA自身、企业BB和企业CC产生的合作数据，当触发者属于企业BB时，可以访问企业BB自身和企业AA产生的合作数据、无法访问企业CC产生的合作数据，当触发者属于企业CC时，可以访问企业CC自身和企业AA产生的合作数据、无法访问企业BB产生的合作数据。
在一实施例中，合作项目的参与方可以随时退出，比如企业CC退出后，企业AA仍然可以与企业BB实现合作数据的共享。以企业CC为例，在企业CC退出合作项目后，跨团体协同平台的服务端可以维持企业AA和企业BB对企业CC的合作数据的访问权限；当然，企业CC也可以对合作数据的访问权限进行设置，以使得企业CC退出合作项目后，企业AA与企业BB将无法继续访问该企业CC产生的合作数据。
图14是一示例性实施例提供的一种设备的示意结构图。请参考图14，在硬件层面，该设备包括处理器1402、内部总线1404、网络接口1406、内存1408以及非易失性存储器1410，当然还可能包括其他业务所需要的硬件。处理器1402从非易失性存储器1410中读取对应的计算机程序到内存1408中然后运行，在逻辑层面上形成跨团体的数据共享装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图15，在软件实施方式中，基于平台侧的跨团体的数据共享装置可以包括：
审批单元1501，使任一团体启动针对其他团体的合作审批流程；
协同单元1502，当所述合作审批流程通过审批时，使所述任一团体与所述其他团体实现跨团体协同，以在所述任一团体与所述其他团体之间共享团体协同过程中的合作数据。
可选的，所述审批单元1501具体用于：
所述任一团体发起针对所述其他团体的跨团体协同的合作项目时，启动针对所述其他团体的合作审批流程。
可选的，所述协同单元1502具体用于：
所述任一团体获取对应于所述合作项目的验证信息，以提供至所述其他团体；
当所述其他团体通过所述验证信息参与至所述合作项目时，所述任一团体与所述其他团体实现跨团体协同。
可选的，所述审批单元1501具体用于：
所述任一团体参与所述其他团体发起的跨团体协同的合作项目时，启动针对所述其他团体的合作审批流程。
可选的，所述协同单元1502具体用于：
所述任一团体获取所述其他团体提供的对应于所述合作项目的验证信息；
所述任一团体通过该所述验证信息参与至所述合作项目，以实现与所述其他团体之间的跨团体协同。
可选的，
所述合作项目由作为发起方的所述任一团体或所述其他团体创建；
或者，所述合作项目由作为发起方的所述任一团体或所述其他团体向跨团体协同平台发起合作项目创建请求后，由所述跨团体协同平台创建。
可选的，当所述其他团体为预配置的受信任团体时，所述协同单元1502使所述任一团体在忽略所述合作审批流程的情况下，与所述其他团体实现跨团体协同。
请参考图16，在软件实施方式中，基于平台侧的跨团体的数据共享装置可以包括：
创建单元1601，使跨团体协同平台创建合作项目；
确定单元1602，使所述跨团体协同平台确定参与所述合作项目的团体，以设定为所述合作项目的项目合作方；
共享单元1603，使所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据。
可选的，所述确定单元1602通过下述方式中至少之一，使所述跨团体协同平台确定已参与所述合作项目的团体：
当所述合作项目是基于任一团体发起的项目创建请求而创建时，所述跨团体协同平台确定所述任一团体参与所述合作项目；
当向所述任一团体指示的目标团体发送的项目参与邀请得到确认应答时，所述跨团体协同平台确定所述目标团体参与所述合作项目；
当收到的至少一个团体发送的项目参与请求中包含对应于所述合作项目的验证信息时，所述跨团体协同平台确定所述至少一个团体参与所述合作项目；其中，所述验证信息对所述合作项目的项目合作方可见。
可选的，所述共享单元1603具体用于：
所述跨团体协同平台将任一项目合作方的合作数据共享至所述合作项目中的所有项目合作方。
可选的，所述共享单元1603具体用于：
所述跨团体协同平台获取任一项目合作方发起的共享对象设置请求；
所述跨团体协同平台将所述任一项目合作方的合作数据共享至所述共享对象设置请求指示的项目合作方，并避免向其他项目合作方共享所述任一项目合作方的合作数据。
可选的，所述共享单元1603具体用于：
当部分项目合作方退出所述合作项目时，所述跨团体协同平台在剩余的项目合作方之间共享合作数据。
可选的，所述共享单元1603具体用于：
所述跨团体协同平台将所述项目合作方产生的合作数据存储于所述合作项目对应的共享空间，所述共享空间对所述合作项目的项目合作方开放权限。
可选的，所述共享单元1603具体用于：
所述跨团体协同平台将每一项目合作方产生的合作数据，记录于相应的合作方共享空间；
所述跨团体协同平台在所述合作项目的项目合作方分别对应的合作方共享空间之间实现对合作数据的自动同步。
可选的，所述共享单元1603具体用于：
所述跨团体协同平台记录至少一个项目合作方分配的对自身的内部系统中合作数据的访问权限，所述访问权限在相应的项目合作方退出所述合作项目时失效；
当任一项目合作方发起对另一项目合作方的合作数据的访问请求时，所述跨团体协同平台通过记录的对所述另一项目合作方的内部系统的访问权限，协助所述任一项目合作方对所述另一项目合作方的内部系统中的合作数据进行访问。
可选的，所述访问权限对相应内部系统的访问范围包括以下至少之一：
特定访问路径、特定权限的数据、特定类型的数据、特定时间段产生的数据、特定部门的员工产生的数据。
请参考图17，在软件实施方式中，基于创建方侧的跨团体的数据共享装置可以包括：
请求单元1701，使任一团体向跨团体协同平台发起合作项目创建请求，以在所述跨团体协同平台上创建合作项目；
共享单元1702，使所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
可选的，还包括：
指示单元1703，使所述任一团体向所述跨团体协同平台指示与所述合作项目相关的目标团体，以使所述跨团体协同平台向所述目标团体发送项目参与邀请；
其中，当所述项目参与邀请得到所述目标团体的确认应答时，所述目标团体被确认为参与至所述合作项目。
可选的，还包括：
获取单元1704，使所述任一团体获取对应于所述合作项目的验证信息，所述验证信息还被记录于所述跨团体协同平台；
发送单元1705，使所述任一团体向目标团体发送所述验证信息，以使所述目标团体向所述跨团体协同平台发送包含所述验证信息的项目参与请求时，被确认为参与所述合作项目。
可选的，所述发送单元1705具体用于：
所述任一团体启动针对所述目标团体的合作审批流程，并当针对所述目标团体的合作审批流程通过审批时，所述任一团体向所述目标团体发送所述验证信息；
或者，当所述目标团体为预配置的受信任团体时，所述任一团体在忽略所述合作审批流程的情况下，向所述目标团体发送所述验证信息。
请参考图18，在软件实施方式中，基于参与方侧的跨团体的数据共享装置可以包括：
参与单元1801，使任一团体参与跨团体协同平台上创建的合作项目；
共享单元1802，使所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
可选的，所述参与单元1801具体用于：
所述任一团体收到所述跨团体协同平台发送的项目参与邀请；
所述任一团体对所述项目参与邀请进行确认应答，以参与至所述合作项目。
可选的，所述参与单元1801具体用于：
所述任一团体获取已参与至所述合作项目的其他团体发送的验证信息；
所述任一团体向所述跨团体协同平台发送包含所述验证信息的项目参与请求，以在所述验证信息对应于所述合作项目时参与至所述合作项目。
可选的，所述参与单元1801通过下述方式使所述任一团体向所述跨团体协同平台发送包含所述验证信息的项目参与请求：
所述任一团体启动针对发送所述验证信息的其他团体的合作审批流程，并当针对所述其他团体的合作审批流程通过审批时，所述任一团体向所述跨团体协同平台发送包含 所述验证信息的项目参与请求；
或者，当所述其他团体为预配置的受信任团体时，所述任一团体在忽略所述合作审批流程的情况下，向所述跨团体协同平台发送包含所述验证信息的项目参与请求。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带、磁盘存储、量子存储器、基于石墨烯的存储介质或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺 序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在本说明书一个或多个实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本说明书一个或多个实施例的较佳实施例而已，并不用以限制本说明书一个或多个实施例，凡在本说明书一个或多个实施例的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本说明书一个或多个实施例保护的范围之内。

Claims (28)

  1. 一种跨团体的数据共享方法，其特征在于，包括：
    任一团体启动针对其他团体的合作审批流程；
    当所述合作审批流程通过审批时，所述任一团体与所述其他团体实现跨团体协同，以在所述任一团体与所述其他团体之间共享团体协同过程中的合作数据。
  2. 根据权利要求1所述的方法，其特征在于，所述任一团体启动针对其他团体的合作审批流程，包括：
    所述任一团体发起针对所述其他团体的跨团体协同的合作项目时，启动针对所述其他团体的合作审批流程。
  3. 根据权利要求2所述的方法，其特征在于，所述任一团体与所述其他团体实现跨团体协同，包括：
    所述任一团体获取对应于所述合作项目的验证信息，以提供至所述其他团体；
    当所述其他团体通过所述验证信息参与至所述合作项目时，所述任一团体与所述其他团体实现跨团体协同。
  4. 根据权利要求1所述的方法，其特征在于，所述任一团体启动针对其他团体的合作审批流程，包括：
    所述任一团体参与所述其他团体发起的跨团体协同的合作项目时，启动针对所述其他团体的合作审批流程。
  5. 根据权利要求4所述的方法，其特征在于，所述任一团体与所述其他团体实现跨团体协同，包括：
    所述任一团体获取所述其他团体提供的对应于所述合作项目的验证信息；
    所述任一团体通过该所述验证信息参与至所述合作项目，以实现与所述其他团体之间的跨团体协同。
  6. 根据权利要求2-5中任一项所述的方法，其特征在于，
    所述合作项目由作为发起方的所述任一团体或所述其他团体创建；
    或者，所述合作项目由作为发起方的所述任一团体或所述其他团体向跨团体协同平台发起合作项目创建请求后，由所述跨团体协同平台创建。
  7. 根据权利要求1所述的方法，其特征在于，还包括：
    当所述其他团体为预配置的受信任团体时，所述任一团体在忽略所述合作审批流程的情况下，与所述其他团体实现跨团体协同。
  8. 一种跨团体的数据共享方法，其特征在于，包括：
    跨团体协同平台创建合作项目；
    所述跨团体协同平台确定参与所述合作项目的团体，以设定为所述合作项目的项目合作方；
    所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据。
  9. 根据权利要求8所述的方法，其特征在于，所述跨团体协同平台确定已参与所述合作项目的团体，包括以下至少之一：
    当所述合作项目是基于任一团体发起的项目创建请求而创建时，所述跨团体协同平台确定所述任一团体参与所述合作项目；
    当向所述任一团体指示的目标团体发送的项目参与邀请得到确认应答时，所述跨团体协同平台确定所述目标团体参与所述合作项目；
    当收到的至少一个团体发送的项目参与请求中包含对应于所述合作项目的验证信息时，所述跨团体协同平台确定所述至少一个团体参与所述合作项目；其中，所述验证信息对所述合作项目的项目合作方可见。
  10. 根据权利要求8所述的方法，其特征在于，所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据，包括：
    所述跨团体协同平台将任一项目合作方的合作数据共享至所述合作项目中的所有项目合作方。
  11. 根据权利要求8所述的方法，其特征在于，所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据，包括：
    所述跨团体协同平台获取任一项目合作方发起的共享对象设置请求；
    所述跨团体协同平台将所述任一项目合作方的合作数据共享至所述共享对象设置请求指示的项目合作方，并避免向其他项目合作方共享所述任一项目合作方的合作数据。
  12. 根据权利要求8所述的方法，其特征在于，所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据，包括：
    当部分项目合作方退出所述合作项目时，所述跨团体协同平台在剩余的项目合作方之间共享合作数据。
  13. 根据权利要求8所述的方法，其特征在于，所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据，包括：
    所述跨团体协同平台将所述项目合作方产生的合作数据存储于所述合作项目对应的共享空间，所述共享空间对所述合作项目的项目合作方开放权限。
  14. 根据权利要求8所述的方法，其特征在于，所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据，包括：
    所述跨团体协同平台将每一项目合作方产生的合作数据，记录于相应的合作方共享空间；
    所述跨团体协同平台在所述合作项目的项目合作方分别对应的合作方共享空间之间实现对合作数据的自动同步。
  15. 根据权利要求8所述的方法，其特征在于，所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据，包括：
    所述跨团体协同平台记录至少一个项目合作方分配的对自身的内部系统中合作数据的访问权限，所述访问权限在相应的项目合作方退出所述合作项目时失效；
    当任一项目合作方发起对另一项目合作方的合作数据的访问请求时，所述跨团体协同平台通过记录的对所述另一项目合作方的内部系统的访问权限，协助所述任一项目合作方对所述另一项目合作方的内部系统中的合作数据进行访问。
  16. 根据权利要求15所述的方法，其特征在于，所述访问权限对相应内部系统的访问范围包括以下至少之一：
    特定访问路径、特定权限的数据、特定类型的数据、特定时间段产生的数据、特定部门的员工产生的数据。
  17. 一种跨团体的数据共享方法，其特征在于，包括：
    任一团体向跨团体协同平台发起合作项目创建请求，以在所述跨团体协同平台上创建合作项目；
    所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
  18. 根据权利要求17所述的方法，其特征在于，还包括：
    所述任一团体向所述跨团体协同平台指示与所述合作项目相关的目标团体，以使所述跨团体协同平台向所述目标团体发送项目参与邀请；
    其中，当所述项目参与邀请得到所述目标团体的确认应答时，所述目标团体被确认为参与至所述合作项目。
  19. 根据权利要求17所述的方法，其特征在于，还包括：
    所述任一团体获取对应于所述合作项目的验证信息，所述验证信息还被记录于所述 跨团体协同平台；
    所述任一团体向目标团体发送所述验证信息，以使所述目标团体向所述跨团体协同平台发送包含所述验证信息的项目参与请求时，被确认为参与所述合作项目。
  20. 根据权利要求19所述的方法，其特征在于，所述任一团体向目标团体发送所述验证信息，包括：
    所述任一团体启动针对所述目标团体的合作审批流程，并当针对所述目标团体的合作审批流程通过审批时，所述任一团体向所述目标团体发送所述验证信息；
    或者，当所述目标团体为预配置的受信任团体时，所述任一团体在忽略所述合作审批流程的情况下，向所述目标团体发送所述验证信息。
  21. 一种跨团体的数据共享方法，其特征在于，包括：
    任一团体参与跨团体协同平台上创建的合作项目；
    所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
  22. 根据权利要求21所述的方法，其特征在于，所述任一团体参与跨团体协同平台上创建的合作项目，包括：
    所述任一团体收到所述跨团体协同平台发送的项目参与邀请；
    所述任一团体对所述项目参与邀请进行确认应答，以参与至所述合作项目。
  23. 根据权利要求21所述的方法，其特征在于，所述任一团体参与跨团体协同平台上创建的合作项目，包括：
    所述任一团体获取已参与至所述合作项目的其他团体发送的验证信息；
    所述任一团体向所述跨团体协同平台发送包含所述验证信息的项目参与请求，以在所述验证信息对应于所述合作项目时参与至所述合作项目。
  24. 根据权利要求23所述的方法，其特征在于，所述任一团体向所述跨团体协同平台发送包含所述验证信息的项目参与请求，包括：
    所述任一团体启动针对发送所述验证信息的其他团体的合作审批流程，并当针对所述其他团体的合作审批流程通过审批时，所述任一团体向所述跨团体协同平台发送包含所述验证信息的项目参与请求；
    或者，当所述其他团体为预配置的受信任团体时，所述任一团体在忽略所述合作审批流程的情况下，向所述跨团体协同平台发送包含所述验证信息的项目参与请求。
  25. 一种跨团体的数据共享装置，其特征在于，包括：
    审批单元，使任一团体启动针对其他团体的合作审批流程；
    协同单元，当所述合作审批流程通过审批时，使所述任一团体与所述其他团体实现跨团体协同，以在所述任一团体与所述其他团体之间共享团体协同过程中的合作数据。
  26. 一种跨团体的数据共享装置，其特征在于，包括：
    创建单元，使跨团体协同平台创建合作项目；
    确定单元，使所述跨团体协同平台确定参与所述合作项目的团体，以设定为所述合作项目的项目合作方；
    共享单元，使所述跨团体协同平台在所述合作项目的项目合作方之间共享合作数据。
  27. 一种跨团体的数据共享装置，其特征在于，包括：
    请求单元，使任一团体向跨团体协同平台发起合作项目创建请求，以在所述跨团体协同平台上创建合作项目；
    共享单元，使所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
  28. 一种跨团体的数据共享装置，其特征在于，包括：
    参与单元，使任一团体参与跨团体协同平台上创建的合作项目；
    共享单元，使所述任一团体与参与所述合作项目的至少一个其他团体之间共享合作数据。
PCT/CN2018/120078 2017-12-15 2018-12-10 跨团体的数据共享方法及装置 Ceased WO2019114654A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP18888467.0A EP3726446A4 (en) 2017-12-15 2018-12-10 METHOD AND DEVICE FOR SHARING DATA BETWEEN GROUPS
JP2020529359A JP7294748B2 (ja) 2017-12-15 2018-12-10 グループ間でデータを共有するための方法、プログラムおよび装置
US16/766,819 US12354064B2 (en) 2017-12-15 2018-12-10 Method and apparatus for sharing data across groups

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711353985.6A CN109934546A (zh) 2017-12-15 2017-12-15 跨团体的数据共享方法及装置
CN201711353985.6 2017-12-15

Publications (1)

Publication Number Publication Date
WO2019114654A1 true WO2019114654A1 (zh) 2019-06-20

Family

ID=66818963

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/120078 Ceased WO2019114654A1 (zh) 2017-12-15 2018-12-10 跨团体的数据共享方法及装置

Country Status (5)

Country Link
US (1) US12354064B2 (zh)
EP (1) EP3726446A4 (zh)
JP (1) JP7294748B2 (zh)
CN (1) CN109934546A (zh)
WO (1) WO2019114654A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110445627A (zh) * 2019-08-12 2019-11-12 腾讯科技（深圳）有限公司 群组更新方法、装置、计算机设备以及计算机存储介质

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7106873B2 (ja) * 2018-01-23 2022-07-27 富士フイルムビジネスイノベーション株式会社 情報処理装置及び情報処理プログラム
US11373255B2 (en) * 2019-09-24 2022-06-28 Procore Technologies, Inc. Computer system and method for mirroring data across different accounts of a software as a service (SaaS) application
WO2023014477A1 (en) * 2021-08-03 2023-02-09 Microsoft Technology Licensing, Llc Controlling access to shared resources in a segmented environment
JP7718196B2 (ja) * 2021-09-15 2025-08-05 富士フイルムビジネスイノベーション株式会社 資料利用管理装置及びオンライン会議システム
US20240354705A1 (en) * 2021-09-16 2024-10-24 Microsoft Technology Licensing, Llc Moderated access to shared resources across segment boundaries in a segmented environment
CN114528567A (zh) * 2022-01-28 2022-05-24 中银金融科技有限公司 一种跨数据中心的共享数据的权限管理方法
US12299637B2 (en) * 2022-09-26 2025-05-13 Sap Se Cross data center data federation for asset collaboration
JP2025178072A (ja) * 2024-05-24 2025-12-05 株式会社パルコデジタルマーケティング 情報処理システム及びプログラム

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105335843A (zh) * 2015-10-10 2016-02-17 北京今目标信息技术有限公司 一种跨企业协同办公的方法、装置和系统
CN106372861A (zh) * 2016-09-28 2017-02-01 诚品优选（北京）电子商务有限公司 一种企业生态协同容器的构建方法
CN106485471A (zh) * 2016-10-10 2017-03-08 广州支点网络科技股份有限公司 合作伙伴关系的实现方法及其实现系统
CN107169733A (zh) * 2017-05-04 2017-09-15 太仓鸿策腾达网络科技有限公司 一种用于实现企业和企业伙伴之间的信息交互方法

Family Cites Families (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1116132A2 (en) 1998-09-22 2001-07-18 Science Applications International Corporation User-defined dynamic collaborative environments
US8024661B2 (en) 2001-10-18 2011-09-20 Autodesk, Inc. Collaboration framework
AU2002234258A1 (en) 2001-01-22 2002-07-30 Sun Microsystems, Inc. Peer-to-peer network computing platform
US20030023677A1 (en) * 2001-07-25 2003-01-30 Graham Morison Zuill On-line project collaboration system
JP2003044519A (ja) 2001-07-27 2003-02-14 Lion Corp 容器包装製品開発会議システム
JP2003067548A (ja) 2001-08-24 2003-03-07 Takenaka Komuten Co Ltd プロジェクト情報共有システム及びプロジェクト情報処理装置
JP2003122862A (ja) 2001-10-10 2003-04-25 Knowledgenet Corp 技術開発スキルの仲介方法
CA2524527A1 (en) 2005-10-26 2007-04-26 Ibm Canada Limited - Ibm Canada Limitee Systems, methods and tools for facilitating group collaborations
US9350560B2 (en) * 2006-05-31 2016-05-24 International Business Machines Corporation Selective information sharing across team spaces
US20080189609A1 (en) 2007-01-23 2008-08-07 Timothy Mark Larson Method and system for creating customized output
EP2111593A2 (en) 2007-01-26 2009-10-28 Information Resources, Inc. Analytic platform
US7797274B2 (en) 2007-12-12 2010-09-14 Google Inc. Online content collaboration model
WO2010008685A2 (en) 2008-05-28 2010-01-21 Aptima, Inc. Systems and methods for analyzing entity profiles
US20110126197A1 (en) 2009-11-25 2011-05-26 Novell, Inc. System and method for controlling cloud and virtualized data centers in an intelligent workload management system
US10387836B2 (en) * 2015-11-24 2019-08-20 David Howard Sitrick Systems and methods providing collaborating among a plurality of users
US10467677B2 (en) 2011-09-28 2019-11-05 Nara Logics, Inc. Systems and methods for providing recommendations based on collaborative and/or content-based nodal interrelationships
US9965745B2 (en) * 2012-02-24 2018-05-08 Box, Inc. System and method for promoting enterprise adoption of a web-based collaboration environment
US9881091B2 (en) 2013-03-08 2018-01-30 Google Inc. Content item audience selection
WO2014152997A2 (en) 2013-03-14 2014-09-25 Sticky Storm, LLC Software-based tool for digital idea collection, organization, and collaboration
US9715476B2 (en) 2013-04-10 2017-07-25 Microsoft Technology Licensing, Llc Collaborative authoring with scratchpad functionality
US9535909B2 (en) * 2013-09-13 2017-01-03 Box, Inc. Configurable event-based automation architecture for cloud-based collaboration platforms
US11336648B2 (en) 2013-11-11 2022-05-17 Amazon Technologies, Inc. Document management and collaboration system
US9276938B2 (en) 2013-11-27 2016-03-01 General Electric Company Cross-enterprise workflow
US9817805B1 (en) 2014-06-24 2017-11-14 Google Inc. Systems and methods for providing a collaborative document environment
US9800659B2 (en) * 2015-02-02 2017-10-24 International Business Machines Corporation Enterprise peer-to-peer storage and method of managing peer network storage
US9846528B2 (en) 2015-03-02 2017-12-19 Dropbox, Inc. Native application collaboration
US20160344677A1 (en) * 2015-05-22 2016-11-24 Microsoft Technology Licensing, Llc Unified messaging platform for providing interactive semantic objects
JP5896261B1 (ja) 2015-08-18 2016-03-30 株式会社ロラン メール配信用サーバ
US9652225B1 (en) * 2016-01-04 2017-05-16 International Business Machines Corporation Development community assessment via real-time workspace monitoring
JP6620669B2 (ja) * 2016-05-12 2019-12-18 富士ゼロックス株式会社 情報処理装置及び情報処理プログラム
JP6576981B2 (ja) * 2016-07-29 2019-09-18 デルタ ピーディーエス カンパニー，リミテッド 階層的プロジェクト管理装置
CN106230862A (zh) * 2016-09-09 2016-12-14 郑州云海信息技术有限公司 一种业务平台及业务管理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105335843A (zh) * 2015-10-10 2016-02-17 北京今目标信息技术有限公司 一种跨企业协同办公的方法、装置和系统
CN106372861A (zh) * 2016-09-28 2017-02-01 诚品优选（北京）电子商务有限公司 一种企业生态协同容器的构建方法
CN106485471A (zh) * 2016-10-10 2017-03-08 广州支点网络科技股份有限公司 合作伙伴关系的实现方法及其实现系统
CN107169733A (zh) * 2017-05-04 2017-09-15 太仓鸿策腾达网络科技有限公司 一种用于实现企业和企业伙伴之间的信息交互方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3726446A4

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110445627A (zh) * 2019-08-12 2019-11-12 腾讯科技（深圳）有限公司 群组更新方法、装置、计算机设备以及计算机存储介质
CN110445627B (zh) * 2019-08-12 2021-10-26 腾讯科技（深圳）有限公司 群组更新方法、装置、计算机设备以及计算机存储介质

Also Published As

Publication number Publication date
EP3726446A1 (en) 2020-10-21
US20210019705A1 (en) 2021-01-21
US12354064B2 (en) 2025-07-08
EP3726446A4 (en) 2021-09-01
CN109934546A (zh) 2019-06-25
JP7294748B2 (ja) 2023-06-20
JP2021507333A (ja) 2021-02-22

Similar Documents

Publication Publication Date Title
US12354064B2 (en) Method and apparatus for sharing data across groups
EP3069307B1 (en) Document management and collaboration system
KR102206950B1 (ko) 워크플로우에 기초한, 블록체인 네트워크 상에서의 비공개 트랜잭션의 관리
US8464164B2 (en) System and method to create a collaborative web-based multimedia contextual dialogue
US9542391B1 (en) Processing service requests for non-transactional databases
WO2020135142A1 (zh) 项目群组的创建方法、项目管理方法及装置
US8812404B2 (en) Information aggregation service
KR101894835B1 (ko) 위치 연관 메시지 제시 기법
TW202030656A (zh) 跨鏈用權系統及方法、裝置、電子設備、儲存媒體
CN115668185B (zh) 用于在基于组的通信系统中管理外部批准供应和外部消息传递通信请求的方法和设备
US20160044071A1 (en) Sharing a web browser session between devices in a social group
WO2019096086A1 (zh) 共享空间的访问方法、权限管理方法及装置
US20150304369A1 (en) Sharing content between collocated mobile devices in an ad-hoc private social group
WO2012177564A2 (en) Automatic sharing of event content by linking devices
CN109923571A (zh) 用于团队协作工具中的通道的实况会议
US20130097233A1 (en) Using devices to link social network profiles
TW201914263A (zh) 通訊方法、信息共享方法及裝置
WO2018223869A1 (zh) 任务提醒方法及装置、提醒消息的生成和展示方法及装置
CN104980339A (zh) 文件分享方法及装置
TW201911158A (zh) 考勤設置方法及裝置
CN115174284A (zh) 在线会议的发起方法及系统
WO2019019929A1 (zh) 签名档的生成方法、签名档模板的分享方法及装置
CN105376307A (zh) 一种数据中心间的异步备份方法
US9104846B2 (en) Access provisioning via communication applications
US10608936B1 (en) Implementing data sharing features in legacy software applications

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18888467

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020529359

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018888467

Country of ref document: EP

Effective date: 20200715

WWG Wipo information: grant in national office

Ref document number: 16766819

Country of ref document: US