WO2021068789A1 - 内容分享方法及装置 - Google Patents

内容分享方法及装置 Download PDF

Info

Publication number
WO2021068789A1
WO2021068789A1 PCT/CN2020/118652 CN2020118652W WO2021068789A1 WO 2021068789 A1 WO2021068789 A1 WO 2021068789A1 CN 2020118652 W CN2020118652 W CN 2020118652W WO 2021068789 A1 WO2021068789 A1 WO 2021068789A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
sharing
interface
specific organization
organization
Prior art date
Application number
PCT/CN2020/118652
Other languages
English (en)
French (fr)
Inventor
康上明学
汪荣军
吴星和
Original Assignee
钉钉控股（开曼）有限公司
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 钉钉控股（开曼）有限公司 filed Critical 钉钉控股（开曼）有限公司
Priority to JP2022521529A priority Critical patent/JP7379688B2/ja
Publication of WO2021068789A1 publication Critical patent/WO2021068789A1/zh
Priority to US17/717,004 priority patent/US20220239986A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1822—Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/10—Multimedia information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
    • H04N21/25866—Management of end-user data
    • H04N21/25875—Management of end-user data involving end-user authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
    • H04N21/2668—Creating a channel for a dedicated end-user group, e.g. insertion of targeted commercials based on end-user profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/27—Server based end-user applications
    • H04N21/274—Storing end-user multimedia data in response to end-user request, e.g. network recorder
    • H04N21/2743—Video hosting of uploaded data from client
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/478—Supplemental services, e.g. displaying phone caller identification, shopping application
    • H04N21/4788—Supplemental services, e.g. displaying phone caller identification, shopping application communicating with other users, e.g. chatting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership

Definitions

  • One or more embodiments of this specification relate to the field of Internet technology, and in particular to a content sharing method and device.
  • users can realize data transmission based on communication applications, so that efficient communication between users can be realized. For example, a single chat can be established between users to achieve one-to-one communication; and in order to improve communication efficiency, a group chat can be established to achieve efficient communication between all group members.
  • group communication tends to be easily mixed with a large amount of small chat content between members, and may even overwhelm some valuable content.
  • one or more embodiments of this specification provide a content sharing method and device.
  • a content sharing method including:
  • the server receives a content sharing request initiated by the sharing user, where the content sharing request is used to share the content to be shared submitted by the sharing user in a specific organization where the sharing user is located;
  • the server publishes the content to be shared to the specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • a content sharing method including:
  • the server receives the content sharing request initiated by the sharing party user
  • the server publishes the content to be shared provided by the sharing party user to a specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • a content sharing method including:
  • the terminal determines the content to be shared provided by the sharing user and the specific organization where the sharing user is located;
  • the terminal initiates a content sharing request to the server, so that the server publishes the content to be shared to the specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • a content sharing method including:
  • the terminal displays the messaging interface of the group where the local user is located, and the group corresponds to the specific organization where the local user is located;
  • the terminal activates a content sharing interface related to the specific organization according to a trigger operation for an access entry included in the messaging interface, and the content sharing interface is used to display shared content from members of the specific organization.
  • a content sharing device including:
  • the request receiving unit enables the server to receive a content sharing request initiated by the sharing user, where the content sharing request is used to share the content to be shared submitted by the sharing user in a specific organization where the sharing user is located;
  • the content publishing unit enables the server to publish the content to be shared to the specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • a content sharing device including:
  • the request receiving unit enables the server to receive the content sharing request initiated by the sharing party user
  • the content publishing unit enables the server to publish the content to be shared provided by the sharing user to a specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • a content sharing device including:
  • the determining unit enables the terminal to determine the content to be shared provided by the sharing user and the specific organization where the sharing user is located;
  • the requesting unit enables the terminal to initiate a content sharing request to the server, so that the server publishes the content to be shared to the specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization .
  • a content sharing device including:
  • the group interface display unit enables the terminal to display the messaging interface of the group where the local user is located, the group corresponding to the specific organization where the local user is located;
  • the sharing interface display unit enables the terminal to activate a content sharing interface related to the specific organization according to a trigger operation for the access entry contained in the messaging interface, and the content sharing interface is used to display information from the specific organization Shared content of members of.
  • an electronic device including:
  • a memory for storing processor executable instructions
  • the processor executes the executable instruction to implement the method according to the first aspect or the second aspect.
  • a computer-readable storage medium is provided with computer instructions stored thereon, and when the instructions are executed by a processor, the method as described in the first aspect or the second aspect is implemented A step of.
  • an electronic device including:
  • a memory for storing processor executable instructions
  • the processor implements the method according to the third aspect or the fourth aspect by running the executable instruction.
  • a computer-readable storage medium is provided, and computer instructions are stored thereon.
  • the instructions are executed by a processor, the implementation is as described in the third aspect or the fourth aspect. Method steps.
  • Fig. 1 is a schematic structural diagram of a content sharing system provided by an exemplary embodiment.
  • Fig. 2 is a flowchart of a method for sharing content on a server side according to an exemplary embodiment.
  • Fig. 3 is a flowchart of another server-side content sharing method provided by an exemplary embodiment.
  • Fig. 4 is a flowchart of a method for sharing content on a terminal side according to an exemplary embodiment.
  • Fig. 5 is a flowchart of another terminal-side content sharing method provided by an exemplary embodiment.
  • Fig. 6 is a schematic diagram of a content sharing interface provided by an exemplary embodiment.
  • Fig. 7 is a schematic diagram of a group chat interface provided by an exemplary embodiment.
  • Fig. 8 is a schematic diagram of another group chat interface provided by an exemplary embodiment.
  • Fig. 9 is a schematic diagram of another content sharing interface provided by an exemplary embodiment.
  • Fig. 10 is a schematic diagram of pushing shared content on a group chat interface according to an exemplary embodiment.
  • Fig. 11 is another schematic diagram of pushing shared content on a group chat interface according to an exemplary embodiment.
  • Figures 12-13 are schematic diagrams of accessing content sharing interfaces provided by an exemplary embodiment.
  • Figures 14-15 are schematic diagrams of inviting users to join an organization provided by an exemplary embodiment.
  • Fig. 16 is a schematic structural diagram of a server-side device provided by an exemplary embodiment.
  • Fig. 17 is a block diagram of a content sharing device on the server side according to an exemplary embodiment.
  • Fig. 18 is a schematic structural diagram of another server-side device provided by an exemplary embodiment.
  • Fig. 19 is a block diagram of another server-side content sharing device provided by an exemplary embodiment.
  • Fig. 20 is a schematic structural diagram of a terminal-side device according to an exemplary embodiment.
  • Fig. 21 is a block diagram of a content sharing device on the terminal side according to an exemplary embodiment.
  • Fig. 22 is a schematic structural diagram of another terminal-side device provided by an exemplary embodiment.
  • Fig. 23 is a block diagram of another terminal-side content sharing device provided by an exemplary embodiment.
  • the steps of the corresponding method are not necessarily executed in the order shown and described in this specification.
  • the method may include more or fewer steps than described in this specification.
  • a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. description.
  • Fig. 1 is a schematic structural diagram of a content sharing system provided by an exemplary embodiment.
  • the system may include a server 11, a network 12, and several electronic devices, such as a mobile phone 13, a mobile phone 14, and a mobile phone 15.
  • the server 11 may be a physical server including an independent host, or the server 11 may be a virtual server carried by a host cluster.
  • the server 11 can run a program on the server side of an application to implement related business functions of the application.
  • the server 11 runs an instant messaging application program, it can be implemented as the server side of the instant messaging application. .
  • instant messaging applications may include ordinary instant messaging applications or enterprise instant messaging applications, which are not limited in this specification.
  • instant messaging applications can also be used as an integrated functional platform for many other functions, such as approval events (such as leave, office supplies applications, financial approval events, etc.), attendance events, task events,
  • approval events such as leave, office supplies applications, financial approval events, etc.
  • attendance events such as leave, office supplies applications, financial approval events, etc.
  • task events such as log events.
  • Mobile phones 13-15 are just one type of electronic equipment that users can use. In fact, users can obviously also use electronic devices such as the following types: tablet devices, notebook computers, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.). Various embodiments do not limit this.
  • 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 an instant messaging application program, it can be implemented as the instant messaging application's program. Client.
  • the client application of the instant messaging application can be pre-installed on the electronic device, so that the client can be started and run on the electronic device; of course, when an online "client” such as HTML5 technology is used When you do not need to install the corresponding application on the electronic device, you can get and run the client.
  • the network 12 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
  • electronic devices such as mobile phones 13-15 can also communicate and interact through the network 12, such as establishing a single chat communication session between any two electronic devices; or, several electronic devices can participate in the same group chat communication session. This allows any user to send communication messages to all other users in the group chat communication session through its own electronic device.
  • PSTN Public Switched Telephone Network
  • Fig. 2 is a flowchart of a method for sharing content on a server side according to an exemplary embodiment. As shown in Figure 2, the method is applied to a server (for example, the server 11 shown in Figure 1, etc.), and may include the following steps:
  • Step 202 The server receives a content sharing request initiated by a sharing user, where the content sharing request is used to share the content to be shared submitted by the sharing user in a specific organization where the sharing user is located.
  • a server-side program of an application is running on the server, so that the server is configured with the server side of the application; accordingly, the terminal used by the sharing user runs the terminal-side program of the above-mentioned application, so that The terminal is configured as a client of the application. Therefore, the server and the terminal used by the sharing party user can interact based on the above-mentioned application.
  • the aforementioned applications may be communication applications, such as instant messaging applications or other types of communication applications.
  • the sharing party user refers to a user who performs content sharing operations.
  • the above sharing party user wishes to share the above-mentioned content to be shared to a specific organization where he/she belongs.
  • the other users can also become the aforementioned sharing party users.
  • the sharing user is a user role, not a fixed user.
  • the sharing party user may add the content to be shared to the content sharing request to send it to the server.
  • the sharing party user can send the content to be shared and the content sharing request to the server independently of each other.
  • the sharing party user can send the content to be shared to a certain storage space (such as the storage space maintained by the server, or other storage space reachable by the server) in advance, and instruct the server to obtain the above-mentioned waiting space from the storage space through the content sharing request. Share content.
  • the sharing party user may be any member in the above-mentioned specific organization.
  • each member in the specific organization can serve as the aforementioned sharing user to share content with respect to the specific organization.
  • the sharing party user may be a member with sharing permission in the above-mentioned specific organization.
  • the permissions of different members of the specific organization can be different, so that those members with sharing permissions can serve as the above-mentioned sharing party users to share content for the specific organization, and other members who do not have sharing permissions You cannot share content for that specific organization.
  • the members of the specific organization may include an administrator and ordinary members, the administrator may have the sharing authority, and the administrator may grant or withdraw the sharing authority to at least one ordinary member.
  • the specific organization has a corresponding organizational structure, and each member is at a corresponding level in the organizational structure, then members of the corresponding level not lower than the preset level can have the sharing authority, while members below the preset level No sharing permission.
  • the specific organization may have an associated test task, and members can automatically obtain the sharing permission after completing the test task. Members of this specific organization can also obtain sharing permissions through other means, and this manual does not limit this.
  • the content to be shared may include any type of content, such as text, picture, video, audio, table, etc., which is not limited in this specification.
  • members of a specific organization in this specification have a relatively close relationship, which is different from the loose relationship in related technologies such as community (BBS, Bulletin Board System), post bar, etc., so that members are in When publishing content to be shared, it is necessary to consider the above-mentioned relatively close interrelationships, and proactively avoid publishing inappropriate content to be shared, so that content sharing between members is relatively more efficient and controllable.
  • BSS Community
  • Bulletin Board System Bulletin Board System
  • the members in the above-mentioned specific organization satisfy the predefined user relationship to reflect the above-mentioned relatively close mutual relationship.
  • the predefined user relationship can include: belonging to the same group, where the group can be understood as an enterprise, hospital, school, army, government agency, etc., or departments within the above-mentioned various groups, and this manual does not describe this limit.
  • the predefined user relationship may include: participating in the same event, and the event may include task events, conference events, diagnosis and treatment events, teaching events, and the like.
  • the above-mentioned user relationship can also include other types of relatively close mutual relationships, such as friend relationships and cooperative relationships between members, and can also satisfy the above-mentioned multiple relationships at the same time (such as belonging to the same group and participating in the same event at the same time, For example, at the same time having a cooperative relationship and participating in the same event, etc.), this manual does not limit this.
  • the above-mentioned specific organization may be established on the basis of an existing group.
  • the above-mentioned specific organization can be established based on the organizational structure of the enterprise maintained by the server, so that the members of the enterprise are added as members of the specific organization, the organizational structure formed by the members of the specific organization, and the enterprise The organizational structure formed by the members of the enterprise can be the same (or there can be differences).
  • the administrator of the aforementioned enterprise can initiate an organization establishment request to the server, so that the server can establish the aforementioned specific organization based on the organizational structure of the enterprise.
  • the joining form of the above-mentioned specific organization may be an invitation system.
  • the applicant user can initiate a joining request for the specific organization to the server, and based on the received joining request, the server can initiate the above joining request after determining that the applicant user is an invitation to join for members of the specific organization In the case of, add the applicant user to the specific organization, otherwise refuse to add.
  • the server will agree to the request of the applicant user and add the applicant user to the specific organization.
  • the server will reject the joining request.
  • Step 204 The server publishes the content to be shared to the specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • the server publishes the content to be shared to a specific organization
  • the content to be shared by causing the content to be shared to be displayed in a content sharing interface related to the specific organization, compared with the related art in the related art
  • the related group corresponding to the specific organization is displayed.
  • all shared content can be displayed uniformly in the content sharing interface, and the displayed content can be prevented from being affected by the chat content between group members, ensuring that members of the characteristic organization can better In order to conveniently view the shared content, it helps to improve the efficiency of content communication.
  • the content sharing interface related to a specific organization that is, there is a preset association between the content sharing interface and the specific organization.
  • the content sharing interface corresponds to the entire specific organization, so that when any member publishes the content to be shared to the specific organization (assuming that any member has the sharing permission), the The content to be shared is presented on the content sharing interface.
  • the above-mentioned specific organization may include sub-organizations, and the relationship between the specific organization and the sub-organization is similar to the relationship between an enterprise and a department, a hospital and a department, a school and a class, etc., and the above-mentioned content related to the specific organization
  • the sharing interface may include: a general content sharing interface corresponding to a specific organization, a content sharing sub-interface corresponding to a child organization, that is, the content sharing general interface corresponds to the entire specific organization, and the content sharing sub-interface corresponds to the child organization (that is, the entire specific organization). Part of the organization).
  • a specific organization can contain multiple sub-organizations, each sub-organization can be independent of each other, or there can be at least a part of overlap, and even some higher-level sub-organizations can completely contain one or more other lower-level sub-organizations Organization;
  • the development department corresponds to a sub-organization 1
  • the software development department subordinate to the development department corresponds to a sub-organization 2
  • the hardware development department corresponds to a sub-organization 3, so sub-organization 1 It can be considered that it includes child organization 2 and child organization 3, and child organization 2 and child organization 3 are independent of each other.
  • the content to be shared in response to a content sharing request initiated by a sharing party user, can be published to a specific organization or a child of a specific organization Organize, so as to be presented in the general content sharing interface or the content sharing sub-interface.
  • the server can determine whether to publish the content to be shared to a specific organization or a sub-organization of the specific organization according to the permission level of the user of the sharing party; where the permission level of the user on the sharing party matches the permission level requirements of the specific organization (of course At this time, it will usually match the permission level requirements of the sub-organization), the server can publish the content to be shared to a specific organization by default to be displayed on the content sharing interface, and the permission level of the user on the sharing party matches
  • the sub-organization (the sharing user can be in the sub-organization or not in the sub-organization) corresponding to the permission level requirements but does not match the specific organization
  • the server can publish the content to be shared to the specific organization by default Sub-organizations are presented in the corresponding content sharing sub-interface.
  • the server can determine to publish the content to be shared to a specific organization or the sub-organization of the sharing user according to the configuration information of the sharing user, so as to be presented on the general content sharing interface or the sub-organization of the sharing user.
  • the content sharing sub-interface corresponding to the organization in other words, the permission level of the sharing user may match the permission level requirements of the specific organization, but the sharing user can still set the above configuration information to publish the content to be shared to this
  • the sub-organization where the sharing user is located is presented in the corresponding content sharing sub-interface instead of being published to the specific organization and presented in the corresponding content sharing general interface.
  • the above-mentioned content sharing general interface and content sharing sub-interface have corresponding access permissions, so that only users with corresponding access permissions can access. For example, it can be determined whether the user can access the corresponding content sharing interface according to the user's affiliation to a specific organization or sub-organization. Among them, the access rights of the general content sharing interface can be restricted to all members of a specific organization, that is, because these members belong to a specific organization, these members have access rights to the general content sharing interface corresponding to the specific organization, and do not belong to that organization.
  • the access rights of the content sharing sub-interface can be restricted to members of the corresponding sub-organization, that is, because these members belong to the sub-organization, these members have content sharing corresponding to the sub-organization
  • the access rights of the sub-interface users who do not belong to the sub-organization cannot access it even if they belong to a specific organization.
  • other methods can also be used to determine whether the user has the authority to access the corresponding content sharing interface. For example, for the content sharing sub-interface corresponding to the above-mentioned sub-organization, it can be set that all members of a specific organization have access rights, which is not restricted in this manual.
  • the server may establish an associated group for the above-mentioned specific organization, so that the group members and the members of the specific organization have a one-to-one correspondence, so that members of the specific organization can communicate efficiently based on the associated group.
  • the server can also establish a corresponding organization for the group.
  • interaction can be realized between the content sharing interface related to the specific group and the messaging interface of the associated group, so that members can realize quick interface switching.
  • the messaging interface of the associated group may include an access entry for the content sharing interface, and vice versa, an access entry for the messaging interface can also be added to the content sharing interface.
  • the number of associated groups can be one, and the group members of this associated group are all members of a specific organization; or, the number of associated groups can be multiple, and all members of a specific organization are located in these associations.
  • the server may also send the content to be shared to an associated group of the specific organization. Allows members to choose to view the content to be shared on the content sharing interface or the content receiving and sending interface. For example, members who are originally on the messaging interface do not need to switch to the content sharing interface or search for the content to be shared in the content sharing interface.
  • the messaging interface can quickly view the content of the content to be shared.
  • the server can also improve the convenience of viewing the shared content for members in other ways. For example, the server can send the access link of the content to be shared in the content sharing interface to the associated group of a specific organization.
  • the member cannot directly view the content of the content to be shared in the messaging interface, it only needs to be in the messaging interface. If the access link is triggered in, you can quickly jump and view the content of the content to be shared without having to search for the content to be shared in the content sharing interface.
  • Fig. 3 is a flowchart of another server-side content 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, etc.), and may include the following steps:
  • Step 302 The server receives the content sharing request initiated by the sharing party user.
  • a server-side program of an application is running on the server, so that the server is configured with the server side of the application; accordingly, the terminal used by the sharing user runs the terminal-side program of the above-mentioned application, so that The terminal is configured as a client of the application. Therefore, the server and the terminal used by the sharing party user can interact based on the above-mentioned application.
  • the aforementioned applications may be communication applications, such as instant messaging applications or other types of communication applications.
  • the sharing party user refers to a user who performs content sharing operations.
  • the above sharing party user wishes to share the above-mentioned content to be shared to a specific organization where he/she belongs.
  • the other users can also become the aforementioned sharing party users.
  • the sharing user is a user role, not a fixed user.
  • the sharing party user does not belong to the above-mentioned specific organization, but the sharing party user can still use the sharing method so that members of the specific organization can view the above-mentioned content to be shared.
  • the sharing party user may add the content to be shared to the content sharing request to be sent to the server.
  • the sharing party user can send the content to be shared and the content sharing request to the server independently of each other.
  • the sharing party user can send the content to be shared to a certain storage space (such as the storage space maintained by the server, or other storage space reachable by the server) in advance, and instruct the server to obtain the above-mentioned waiting space from the storage space through the content sharing request. Share content.
  • the content to be shared may include any type of content, such as text, picture, video, audio, table, etc., which is not limited in this specification.
  • the sharing user in the case of belonging to the above-mentioned specific organization, may be any member in the specific organization.
  • each member in the specific organization can serve as the aforementioned sharing user to share content with respect to the specific organization.
  • the sharing party user may be a member with sharing permission in the above-mentioned specific organization.
  • the permissions of different members of the specific organization can be different, so that those members with sharing permissions can serve as the above-mentioned sharing party users to share content for the specific organization, and other members who do not have sharing permissions You cannot share content for that specific organization.
  • the members of the specific organization may include an administrator and ordinary members, the administrator may have the sharing authority, and the administrator may grant or withdraw the sharing authority to at least one ordinary member.
  • the specific organization has a corresponding organizational structure, and each member is at a corresponding level in the organizational structure, then members whose corresponding level is not lower than the preset level can have sharing permissions, while members below the preset level No sharing permission.
  • the specific organization may have an associated test task, and members can automatically obtain the sharing permission after completing the test task. Members in this specific organization can also obtain sharing permissions through other means, and this manual does not limit this.
  • members of a specific organization in this specification have a relatively close relationship, which is different from the loose relationship in related technologies such as community (BBS, Bulletin Board System), post bar, etc., so that members are in When publishing content to be shared, it is necessary to consider the above-mentioned relatively close interrelationships, and proactively avoid publishing inappropriate content to be shared, so that content sharing between members is relatively more efficient and controllable.
  • BSS Community
  • Bulletin Board System Bulletin Board System
  • the members in the above-mentioned specific organization satisfy the predefined user relationship to reflect the above-mentioned relatively close mutual relationship.
  • the predefined user relationship can include: belonging to the same group, where the group can be understood as an enterprise, hospital, school, army, government agency, etc., or departments within the above-mentioned various groups, and this manual does not describe this limit.
  • the predefined user relationship may include: participating in the same event, and the event may include task events, conference events, diagnosis and treatment events, teaching events, and the like.
  • the above-mentioned user relationship can also include other types of relatively close mutual relationships, such as friend relationships and cooperative relationships between members, and can also satisfy the above-mentioned multiple relationships at the same time (such as belonging to the same group and participating in the same event at the same time, For example, at the same time having a cooperative relationship and participating in the same event, etc.), this manual does not limit this.
  • the above-mentioned specific organization may be established on the basis of an existing group.
  • the above-mentioned specific organization can be established based on the organizational structure of the enterprise maintained by the server, so that the members of the enterprise are added as members of the specific organization, the organizational structure formed by the members of the specific organization, and the enterprise The organizational structure formed by the members of the enterprise can be the same (or there can be differences).
  • the administrator of the aforementioned enterprise can initiate an organization establishment request to the server, so that the server can establish the aforementioned specific organization based on the organizational structure of the enterprise.
  • the joining form of the above-mentioned specific organization may be an invitation system.
  • the applicant user can initiate a joining request for the specific organization to the server, and based on the received joining request, the server can initiate the above joining request after determining that the applicant user is an invitation to join for members of the specific organization In the case of, add the applicant user to the specific organization, otherwise refuse to add.
  • the server will agree to the request of the applicant user and add the applicant user to the specific organization.
  • the server will reject the joining request.
  • Step 304 The server publishes the content to be shared provided by the sharing user to a specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • the server publishes the content to be shared to a specific organization
  • the content to be shared by causing the content to be shared to be displayed in a content sharing interface related to the specific organization, compared with the related art in the related art
  • the related group corresponding to the specific organization is displayed.
  • all shared content can be displayed uniformly in the content sharing interface, and the displayed content can be prevented from being affected by the chat content between group members, ensuring that members of the characteristic organization can better In order to conveniently view the shared content, it helps to improve the efficiency of content communication.
  • the content sharing interface related to a specific organization that is, there is a preset association between the content sharing interface and the specific organization.
  • the content sharing interface corresponds to the entire specific organization, so that when any member publishes the content to be shared to the specific organization (assuming that any member has the sharing permission), the The content to be shared is presented on the content sharing interface.
  • the above-mentioned specific organization may include sub-organizations, and the relationship between the specific organization and the sub-organization is similar to the relationship between an enterprise and a department, a hospital and a department, a school and a class, etc., and the above-mentioned content related to the specific organization
  • the sharing interface may include: a general content sharing interface corresponding to a specific organization, a content sharing sub-interface corresponding to a child organization, that is, the content sharing general interface corresponds to the entire specific organization, and the content sharing sub-interface corresponds to the child organization (that is, the entire specific organization). Part of the organization).
  • a specific organization can contain multiple sub-organizations, each sub-organization can be independent of each other, or there can be at least a part of overlap, and even some higher-level sub-organizations can completely contain one or more other lower-level sub-organizations Organization;
  • the development department corresponds to a sub-organization 1
  • the software development department subordinate to the development department corresponds to a sub-organization 2
  • the hardware development department corresponds to a sub-organization 3, so sub-organization 1 It can be considered that it includes child organization 2 and child organization 3, and child organization 2 and child organization 3 are independent of each other.
  • the content to be shared in response to a content sharing request initiated by a sharing party user, can be published to a specific organization or a child of a specific organization Organize, so as to be presented in the general content sharing interface or the content sharing sub-interface.
  • the server can determine whether to publish the content to be shared to a specific organization or a sub-organization of the specific organization according to the permission level of the user of the sharing party; where the permission level of the user on the sharing party matches the permission level requirements of the specific organization (of course At this time, it will usually match the permission level requirements of the sub-organization), the server can publish the content to be shared to a specific organization by default to be displayed on the content sharing interface, and the permission level of the user on the sharing party matches
  • the sub-organization (the sharing user can be in the sub-organization or not in the sub-organization) corresponding to the permission level requirements but does not match the specific organization
  • the server can publish the content to be shared to the specific organization by default Sub-organizations are presented in the corresponding content sharing sub-interface.
  • the server can determine to publish the content to be shared to a specific organization or the sub-organization of the sharing user according to the configuration information of the sharing user, so as to be presented on the general content sharing interface or the sub-organization of the sharing user.
  • the content sharing sub-interface corresponding to the organization in other words, the permission level of the sharing user may match the permission level requirements of the specific organization, but the sharing user can still set the above configuration information to publish the content to be shared to this
  • the sub-organization where the sharing user is located is presented in the corresponding content sharing sub-interface instead of being published to the specific organization and presented in the corresponding content sharing general interface.
  • the above-mentioned content sharing general interface and content sharing sub-interface have corresponding access permissions, so that only users with corresponding access permissions can access. For example, it can be determined whether the user can access the corresponding content sharing interface according to the user's affiliation to a specific organization or sub-organization. Among them, the access rights of the general content sharing interface can be restricted to all members of a specific organization, that is, because these members belong to a specific organization, these members have access rights to the general content sharing interface corresponding to the specific organization, and do not belong to that organization.
  • the access rights of the content sharing sub-interface can be restricted to members of the corresponding sub-organization, that is, because these members belong to the sub-organization, these members have content sharing corresponding to the sub-organization
  • the access rights of the sub-interface users who do not belong to the sub-organization cannot access it even if they belong to a specific organization.
  • other methods can also be used to determine whether the user has the authority to access the corresponding content sharing interface. For example, for the content sharing sub-interface corresponding to the above-mentioned sub-organization, it can be set that all members of a specific organization have access rights, which is not restricted in this manual.
  • the server may establish an associated group for the above-mentioned specific organization, so that the group members and the members of the specific organization have a one-to-one correspondence, so that members of the specific organization can communicate efficiently based on the associated group.
  • the server can also establish a corresponding organization for the group.
  • interaction can be realized between the content sharing interface related to the specific group and the messaging interface of the associated group, so that members can realize quick interface switching.
  • the messaging interface of the associated group may include an access entry for the content sharing interface, and vice versa, an access entry for the messaging interface can also be added to the content sharing interface.
  • the number of associated groups can be one, and the group members of this associated group are all members of a specific organization; or, the number of associated groups can be multiple, and all members of a specific organization are located in these associations.
  • the server may also send the content to be shared to an associated group of the specific organization. Allows members to choose to view the content to be shared on the content sharing interface or the messaging interface. For example, members who are originally on the messaging interface do not need to switch to the content sharing interface or search for the content to be shared in the content sharing interface.
  • the messaging interface can quickly view the content of the content to be shared.
  • the server can also improve the convenience of viewing the shared content for members in other ways. For example, the server can send the access link of the content to be shared in the content sharing interface to the associated group of a specific organization.
  • the member cannot directly view the content of the content to be shared in the messaging interface, it only needs to be in the messaging interface. If the access link is triggered in, you can quickly jump and view the content of the content to be shared without having to search for the content to be shared in the content sharing interface.
  • Fig. 4 is a flowchart of a method for sharing content on a terminal side according to an exemplary embodiment. As shown in Fig. 4, the method is applied to a terminal (for example, the mobile phones 13-15 shown in Fig. 1), and may include the following steps:
  • Step 402 The terminal determines the content to be shared provided by the sharing user and the specific organization in which the sharing user is located.
  • the sharing party user refers to a user who performs content sharing operations.
  • the above sharing party user wishes to share the above-mentioned content to be shared to a specific organization where he/she belongs.
  • the other users can also become the aforementioned sharing party users.
  • the sharing user is a user role, not a fixed user.
  • the sharing user is the user who performs the sharing operation on the terminal.
  • the sharing user usually needs to log in his pre-registered account information on the terminal, that is, the terminal distinguishes the corresponding user's account information based on the logged-in account information. Identity.
  • the content to be shared may include any type of content, such as text, picture, video, audio, table, etc., which is not limited in this specification.
  • members of a specific organization in this specification have a relatively close relationship, which is different from the loose relationship in related technologies such as community (BBS, Bulletin Board System), post bar, etc., so that members are in When publishing content to be shared, it is necessary to consider the above-mentioned relatively close interrelationships, and proactively avoid publishing inappropriate content to be shared, so that content sharing between members is relatively more efficient and controllable.
  • BSS Community
  • Bulletin Board System Bulletin Board System
  • the members in the above-mentioned specific organization satisfy the predefined user relationship to reflect the above-mentioned relatively close mutual relationship.
  • the predefined user relationship can include: belonging to the same group, where the group can be understood as an enterprise, hospital, school, army, government agency, etc., or departments within the above-mentioned various groups, and this manual does not describe this limit.
  • the predefined user relationship may include: participating in the same event, and the event may include task events, conference events, diagnosis and treatment events, teaching events, and the like.
  • the above-mentioned user relationship can also include other types of relatively close mutual relationships, such as friend relationships and cooperative relationships between members, and can also satisfy the above-mentioned multiple relationships at the same time (such as belonging to the same group and participating in the same event at the same time, For example, at the same time having a cooperative relationship and participating in the same event, etc.), this manual does not limit this.
  • the above-mentioned specific organization may be established on the basis of an existing group.
  • the above-mentioned specific organization can be established based on the organizational structure of the enterprise maintained by the server, so that the members of the enterprise are added as members of the specific organization, the organizational structure formed by the members of the specific organization, and the enterprise The organizational structure formed by the members of the enterprise can be the same (or there can be differences).
  • the administrator of the aforementioned enterprise can initiate an organization establishment request to the server, so that the server can establish the aforementioned specific organization based on the organizational structure of the enterprise.
  • the joining form of the above-mentioned specific organization may be an invitation system.
  • the applicant user can initiate a joining request for the specific organization to the server, and based on the received joining request, the server can initiate the above joining request after determining that the applicant user is an invitation to join for members of the specific organization In the case of, add the applicant user to the specific organization, otherwise refuse to add.
  • the server will agree to the request of the applicant user and add the applicant user to the specific organization.
  • the server will reject the joining request.
  • Step 404 The terminal initiates a content sharing request to the server, so that the server publishes the content to be shared to the specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • a server-side program of an application is running on the server, so that the server is configured with the server side of the application; accordingly, the terminal used by the sharing user runs the terminal-side program of the above-mentioned application, so that The terminal is configured as a client of the application. Therefore, the server and the terminal used by the sharing party user can interact based on the above-mentioned application.
  • the aforementioned applications may be communication applications, such as instant messaging applications or other types of communication applications.
  • the terminal may add the content to be shared to the content sharing request to send to the server.
  • the terminal may independently send the content to be shared and the content sharing request to the server.
  • the terminal may send the content to be shared to a certain storage space (such as the storage space maintained by the server, or other storage space reachable by the server) in advance, and instruct the server to obtain the content to be shared from the storage space through the content sharing request .
  • the sharing party user may be any member in the above-mentioned specific organization.
  • each member in the specific organization can serve as the aforementioned sharing user to share content with respect to the specific organization.
  • the sharing party user may be a member with sharing permission in the above-mentioned specific organization.
  • the permissions of different members of the specific organization can be different, so that those members with sharing permissions can serve as the above-mentioned sharing party users to share content for the specific organization, and other members who do not have sharing permissions You cannot share content for that specific organization.
  • the members of the specific organization may include an administrator and ordinary members, the administrator may have the sharing authority, and the administrator may grant or withdraw the sharing authority to at least one ordinary member.
  • the specific organization has a corresponding organizational structure, and each member is at a corresponding level in the organizational structure, then members of the corresponding level not lower than the preset level can have the sharing authority, while members below the preset level No sharing permission.
  • the specific organization may have an associated test task, and members can automatically obtain the sharing permission after completing the test task. Members of this specific organization can also obtain sharing permissions through other means, and this manual does not limit this.
  • the server publishes the content to be shared to a specific organization
  • the content to be shared by causing the content to be shared to be displayed in a content sharing interface related to the specific organization, compared with the related art in the related art
  • the related group corresponding to the specific organization is displayed.
  • all shared content can be displayed uniformly in the content sharing interface, and the displayed content can be prevented from being affected by the chat content between group members, ensuring that members of the characteristic organization can better In order to conveniently view the shared content, it helps to improve the efficiency of content communication.
  • the content sharing interface related to a specific organization that is, there is a preset association between the content sharing interface and the specific organization.
  • the content sharing interface corresponds to the entire specific organization, so that when any member publishes the content to be shared to the specific organization (assuming that any member has the sharing permission), the The content to be shared is presented on the content sharing interface.
  • the above-mentioned specific organization may include sub-organizations, and the relationship between the specific organization and the sub-organization is similar to the relationship between an enterprise and a department, a hospital and a department, a school and a class, etc., and the above-mentioned content related to the specific organization
  • the sharing interface may include: a general content sharing interface corresponding to a specific organization, a content sharing sub-interface corresponding to a child organization, that is, the content sharing general interface corresponds to the entire specific organization, and the content sharing sub-interface corresponds to the child organization (that is, the entire specific organization). Part of the organization).
  • a specific organization can contain multiple sub-organizations, each sub-organization can be independent of each other, or there can be at least a part of overlap, and even some higher-level sub-organizations can completely contain one or more other lower-level sub-organizations Organization;
  • the development department corresponds to a child organization 1
  • the software development department under the development department corresponds to a child organization 2
  • the hardware development department corresponds to a child organization 3.
  • the child organization 1 It can be considered that it includes child organization 2 and child organization 3, and child organization 2 and child organization 3 are independent of each other.
  • the content to be shared in response to a content sharing request initiated by a sharing party user, can be published to a specific organization or a child of a specific organization Organize, so as to be presented in the general content sharing interface or the content sharing sub-interface.
  • the server can determine whether to publish the content to be shared to a specific organization or a sub-organization of the specific organization according to the permission level of the user of the sharing party; where the permission level of the user on the sharing party matches the permission level requirements of the specific organization (of course At this time, it will usually match the permission level requirements of the sub-organization), the server can publish the content to be shared to a specific organization by default to be displayed on the content sharing interface, and the permission level of the user on the sharing party matches
  • the sub-organization (the sharing user can be in the sub-organization or not in the sub-organization) corresponding to the permission level requirements but does not match the specific organization
  • the server can publish the content to be shared to the specific organization by default Sub-organizations are presented in the corresponding content sharing sub-interface.
  • the server can determine to publish the content to be shared to a specific organization or the sub-organization of the sharing user according to the configuration information of the sharing user, so as to be presented on the general content sharing interface or the sub-organization of the sharing user.
  • the content sharing sub-interface corresponding to the organization in other words, the permission level of the sharing user may match the permission level requirements of the specific organization, but the sharing user can still set the above configuration information to publish the content to be shared to this
  • the sub-organization where the sharing user is located is presented in the corresponding content sharing sub-interface instead of being published to the specific organization and presented in the corresponding content sharing general interface.
  • the above-mentioned content sharing general interface and content sharing sub-interface have corresponding access permissions, so that only users with corresponding access permissions can access. For example, it can be determined whether the user can access the corresponding content sharing interface according to the user's affiliation to a specific organization or sub-organization. Among them, the access rights of the general content sharing interface can be restricted to all members of a specific organization, that is, because these members belong to a specific organization, these members have access rights to the general content sharing interface corresponding to the specific organization, and do not belong to that organization.
  • the access rights of the content sharing sub-interface can be restricted to members of the corresponding sub-organization, that is, because these members belong to the sub-organization, these members have content sharing corresponding to the sub-organization
  • the access rights of the sub-interface users who do not belong to the sub-organization cannot access it even if they belong to a specific organization.
  • other methods can also be used to determine whether the user has the authority to access the corresponding content sharing interface. For example, for the content sharing sub-interface corresponding to the above-mentioned sub-organization, it can be set that all members of a specific organization have access rights, which is not restricted in this manual.
  • the server may establish an associated group for the above-mentioned specific organization, so that the group members and the members of the specific organization have a one-to-one correspondence, so that members of the specific organization can communicate efficiently based on the associated group.
  • the server can also establish a corresponding organization for the group.
  • interaction can be realized between the content sharing interface related to the specific group and the messaging interface of the associated group, so that members can realize quick interface switching.
  • the messaging interface of the associated group may include an access entry for the content sharing interface, and vice versa, an access entry for the messaging interface can also be added to the content sharing interface.
  • the number of associated groups can be one, and the group members of this associated group are all members of a specific organization; or, the number of associated groups can be multiple, and all members of a specific organization are located in these associations.
  • the messaging interface and the content sharing interface belong to the same application, for example, both belong to the aforementioned communication application.
  • the terminal when the terminal activates the content sharing interface related to a specific organization according to the trigger operation for the access entry included in the message sending and receiving interface, there may be multiple display modes.
  • the terminal when the messaging interface and the content sharing interface are completely independent, the terminal is equivalent to jumping from the messaging interface to the content sharing interface, that is, only the messaging interface or the content sharing interface is displayed on the terminal screen at the same time; for another example, The terminal can display the content sharing interface floating above the messaging interface; for another example, the terminal can display the messaging interface and the content sharing interface side by side.
  • the server may also send the content to be shared to an associated group of the specific organization. Allows members to choose to view the content to be shared on the content sharing interface or the messaging interface. For example, members who are originally on the messaging interface do not need to switch to the content sharing interface or search for the content to be shared in the content sharing interface.
  • the messaging interface can quickly view the content of the content to be shared.
  • the server can also improve the convenience of viewing the shared content for members in other ways. For example, the server can send the access link of the content to be shared in the content sharing interface to the associated group of a specific organization.
  • the member cannot directly view the content of the content to be shared in the messaging interface, it only needs to be in the messaging interface. If the access link is triggered in, you can quickly jump and view the content of the content to be shared without having to search for the content to be shared in the content sharing interface.
  • Fig. 5 is a flowchart of another terminal-side content sharing method provided by an exemplary embodiment. As shown in Fig. 5, the method is applied to a terminal (for example, the mobile phones 13-15 shown in Fig. 1), and may include the following steps:
  • Step 502 The terminal displays the messaging interface of the group where the local user is located, and the group corresponds to the specific organization where the local user is located.
  • the local user is the user corresponding to the logged-in account of the terminal.
  • the messaging interface is used for the local user to view the communication messages sent by other members in the group, or to send communication messages to other members.
  • members of a specific organization in this specification have a relatively close relationship, which is different from the loose relationship in related technologies such as community (BBS, Bulletin Board System), post bar, etc., so that members are in When publishing content to be shared, it is necessary to consider the above-mentioned relatively close interrelationships, and proactively avoid publishing inappropriate content to be shared, so that content sharing between members is relatively more efficient and controllable.
  • BSS Community
  • Bulletin Board System Bulletin Board System
  • the members in the above-mentioned specific organization satisfy the predefined user relationship to reflect the above-mentioned relatively close mutual relationship.
  • the predefined user relationship can include: belonging to the same group, where the group can be understood as an enterprise, hospital, school, army, government agency, etc., or departments within the above-mentioned various groups, and this manual does not describe this limit.
  • the predefined user relationship may include: participating in the same event, and the event may include task events, conference events, diagnosis and treatment events, teaching events, and the like.
  • the above-mentioned user relationship can also include other types of relatively close mutual relationships, such as friend relationships and cooperative relationships between members, and can also satisfy the above-mentioned multiple relationships at the same time (such as belonging to the same group and participating in the same event at the same time, For example, at the same time having a cooperative relationship and participating in the same event, etc.), this manual does not limit this.
  • the above-mentioned specific organization may be established on the basis of an existing group.
  • the above-mentioned specific organization can be established based on the organizational structure of the enterprise maintained by the server, so that the members of the enterprise are added as members of the specific organization, the organizational structure formed by the members of the specific organization, and the enterprise The organizational structure formed by the members of the enterprise can be the same (or there can be differences).
  • the administrator of the aforementioned enterprise can initiate an organization establishment request to the server, so that the server can establish the aforementioned specific organization based on the organizational structure of the enterprise.
  • the joining form of the above-mentioned specific organization may be an invitation system.
  • the applicant user can initiate a joining request for the specific organization to the server, and based on the received joining request, the server can initiate the above joining request after determining that the applicant user is an invitation to join for members of the specific organization In the case of, add the applicant user to the specific organization, otherwise refuse to add.
  • the server will agree to the request of the applicant user and add the applicant user to the specific organization.
  • the server will reject the joining request.
  • Step 504 The terminal activates a content sharing interface related to the specific organization according to the trigger operation for the access entry contained in the messaging interface, and the content sharing interface is used to display information from members of the specific organization. Share content.
  • the above-mentioned local user can quickly start the content sharing interface by triggering the access entry without having to exit the messaging interface and open it again.
  • Content sharing interface can be independent of the messaging interface, so that the terminal can switch from the messaging interface to the content sharing interface in response to a trigger operation for the access entry.
  • the content sharing interface can take other forms, such as a window interface located in the messaging interface; the area of the window interface is usually relatively small and only occupies a part of the content sharing interface, so that local users can view the content sharing interface. At the same time, you can also view the messaging interface.
  • the messaging interface and the content sharing interface belong to the same application, for example, both belong to the aforementioned communication application.
  • the terminal when the terminal activates the content sharing interface related to a specific organization according to the trigger operation for the access entry included in the message sending and receiving interface, there may be multiple display modes.
  • the terminal when the messaging interface and the content sharing interface are completely independent, the terminal is equivalent to jumping from the messaging interface to the content sharing interface, that is, only the messaging interface or the content sharing interface is displayed on the terminal screen at the same time; for another example, The terminal can display the content sharing interface floating above the messaging interface; for another example, the terminal can display the messaging interface and the content sharing interface side by side.
  • the terminal may display reminder information in the display area of the above-mentioned access entrance, and the reminder information is used to indicate that there is unread shared content and/or unread interactive content in the content sharing interface.
  • Unread shared content is the unread shared content in the content sharing interface.
  • Unread interactive content is the interactive content in the unread state in the content sharing interface.
  • the interactive content is sent by other users to the local user to realize the interaction between other users and the local user.
  • the interactive content can include comment content and comments. Reply content, private message content, like content, etc.
  • the reminder information can have multiple forms to meet the reminder effect under different needs; for example, the reminder information can include a reminder mark (such as a red dot), and the local user can determine the above unread shared content and/or unread based on this The presence or absence of interactive content (the presence of a reminder logo indicates that it exists, and the absence of a reminder logo indicates that it does not exist).
  • the reminder information can include a reminder value, which is the number of unread shared content and/or unread interactive content. Based on this, the local user can determine the existence and quantity of the aforementioned unread shared content and/or unread interactive content (the presence of a reminder value indicates that it exists and the reminder value is the amount of content, and no reminder value indicates that it does not exist).
  • the content can be shared All shared content is displayed uniformly in the interface, and the displayed content can be prevented from being affected by the small chat content between group members, ensuring that members of the characteristic organization can more conveniently view the shared content, which helps Improve the efficiency of content delivery.
  • the content sharing interface related to a specific organization that is, there is a preset association between the content sharing interface and the specific organization.
  • the content sharing interface corresponds to the entire specific organization, so that when any member publishes the content to be shared to the specific organization (assuming that any member has the sharing permission), the The content to be shared is presented on the content sharing interface.
  • the above-mentioned specific organization may include sub-organizations, and the relationship between the specific organization and the sub-organization is similar to the relationship between an enterprise and a department, a hospital and a department, a school and a class, etc., and the above-mentioned content related to the specific organization
  • the sharing interface may include: a general content sharing interface corresponding to a specific organization, a content sharing sub-interface corresponding to a child organization, that is, the content sharing general interface corresponds to the entire specific organization, and the content sharing sub-interface corresponds to the child organization (that is, the entire specific organization). Part of the organization).
  • a specific organization can contain multiple sub-organizations, each sub-organization can be independent of each other, or there can be at least a part of overlap, and even some higher-level sub-organizations can completely contain one or more other lower-level sub-organizations Organization;
  • the development department corresponds to a child organization 1
  • the software development department under the development department corresponds to a child organization 2
  • the hardware development department corresponds to a child organization 3.
  • the child organization 1 It can be considered that it includes child organization 2 and child organization 3, and child organization 2 and child organization 3 are independent of each other.
  • the content to be shared in response to a content sharing request initiated by a sharing party user, can be published to a specific organization or a child of a specific organization Organize, so as to be presented in the general content sharing interface or the content sharing sub-interface.
  • the server can determine whether to publish the content to be shared to a specific organization or a sub-organization of the specific organization according to the permission level of the user of the sharing party; where the permission level of the user on the sharing party matches the permission level requirements of the specific organization (of course At this time, it will usually match the permission level requirements of the sub-organization), the server can publish the content to be shared to a specific organization by default to be displayed on the content sharing interface, and the permission level of the user on the sharing party matches
  • the sub-organization (the sharing user can be in the sub-organization or not in the sub-organization) corresponding to the permission level requirements but does not match the specific organization
  • the server can publish the content to be shared to the specific organization by default Sub-organizations are presented in the corresponding content sharing sub-interface.
  • the server can determine to publish the content to be shared to a specific organization or the sub-organization of the sharing user according to the configuration information of the sharing user, so as to be presented on the general content sharing interface or the sub-organization of the sharing user.
  • the content sharing sub-interface corresponding to the organization in other words, the permission level of the sharing user may match the permission level requirements of the specific organization, but the sharing user can still set the above configuration information to publish the content to be shared to this
  • the sub-organization where the sharing user is located is presented in the corresponding content sharing sub-interface instead of being published to the specific organization and presented in the corresponding content sharing general interface.
  • the above-mentioned content sharing general interface and content sharing sub-interface have corresponding access permissions, so that only users with corresponding access permissions can access. For example, it can be determined whether the user can access the corresponding content sharing interface according to the user's affiliation to a specific organization or sub-organization. Among them, the access rights of the general content sharing interface can be restricted to all members of a specific organization, that is, because these members belong to a specific organization, these members have access rights to the general content sharing interface corresponding to the specific organization, and do not belong to that organization.
  • the access rights of the content sharing sub-interface can be restricted to members of the corresponding sub-organization, that is, because these members belong to the sub-organization, these members have content sharing corresponding to the sub-organization
  • the access rights of the sub-interface users who do not belong to the sub-organization cannot access it even if they belong to a specific organization.
  • other methods can also be used to determine whether the user has the authority to access the corresponding content sharing interface. For example, for the content sharing sub-interface corresponding to the above-mentioned sub-organization, it can be set that all members of a specific organization have access rights, which is not restricted in this manual.
  • the terminal may also receive the content sent by the server to the foregoing messaging interface, so that The local user can choose to view the content to be shared in the content sharing interface or the messaging interface. For example, if the local user is originally located in the messaging interface, there is no need to switch to the content sharing interface or search for the content to be shared in the content sharing interface. You can quickly view the content of the content to be shared on the messaging interface.
  • the terminal can also receive the access link of the content in the content sharing interface sent by the server to the messaging interface.
  • the server By running the server-side program of the application T on the server and the terminal-side program of the application T on the terminal, the server can be configured as the server of the application T and the terminal can be configured as the client of the application T, thus The server and the client cooperate to realize the content sharing scheme in this manual.
  • the application T can provide a content sharing function, for example, the content sharing function can be called a "small circle”.
  • Fig. 6 is a schematic diagram of a content sharing interface provided by an exemplary embodiment. As shown in FIG. 6, the small circle function provided by the application T can include a content sharing interface 60 so that shared content can be presented in the content sharing interface 60.
  • the content sharing interface 60 may include a summary information display area 610 for displaying summary information related to the content sharing interface 60.
  • the summary information may include: the name of the organization corresponding to the content sharing interface 60 is "e-commerce dry goods sharing", content sharing The number of shared content (dynamic) in the interface 60 is 29,384, and the number of members included in the aforementioned organization "e-commerce dry goods sharing” is 82,892.
  • the content sharing interface 60 may include a key member introduction area 620 for displaying information of key members in the organization.
  • key members can include "ring masters", which are equivalent to the administrators of the aforementioned organizations.
  • key members may include well-known users, for example, well-known users in the organization "e-commerce dry goods sharing” may include “well-known e-commerce mentors” and so on.
  • the content sharing interface 60 may include a group chat entry display area 630 to display the corresponding access entry for the messaging interface (ie, the group chat interface) of the associated group of the above organization.
  • the associated group of the aforementioned organization "e-commerce dry goods sharing” may include "e-commerce study class 1", "e-commerce study class 2" and so on. Due to the limited area of the group chat entrance display area 630, it is usually only possible to display the access entrances corresponding to some associated groups, while the related information and access entrances of other associated groups can be triggered by triggering the group chat entrance display area 630 "View all" option to view.
  • the content sharing interface 60 may include a must-see information display area 640 for displaying the most important shared information, that is, must-see information.
  • the must-see information display area 640 may include "a summary of dry goods article catalog + links" and the like.
  • the must-see information display area 640 due to the limited area of the must-see information display area 640, usually only part of the must-see information can be displayed, and other must-see information can be viewed by triggering the "view all" option in the must-see information display area 640.
  • the content sharing interface 60 may include a top information display area 650 for displaying shared information with relatively high importance (but lower than must-see information), that is, top information.
  • the top information display area 650 may include "column dry goods catalog summary + link", "traffic is very important for a store," and so on.
  • the limited area of the top information display area 650 usually only part of the top information can be displayed, and other top information can be viewed by triggering the "view all" option in the top information display area 650.
  • the remaining area of the content sharing interface 60 can be used to display the existing shared content in the above-mentioned organization "e-commerce dry goods sharing", for example, display the shared content in reverse order in the form of a list, so that users can view the recently released shared content first .
  • the content sharing interface 60 includes shared content 660.
  • the shared content 660 may include the information of the content sharing party (such as avatar, name, etc.), the shared content, interactive information for the content (such as the number of reposts, the number of comments, the number of likes, comment information, comment reply information, etc.), etc. content.
  • the shared content 660 is set (the content posted by the circle owner is set by the system as must-see or top by default, or is actively set by the circle owner or other users with administrative rights) as must-see content or top content, you can add corresponding tags To characterize it, for example, a "sticky" tag is shown for the shared content 660 in FIG. If there are multiple pieces of comment information, comment reply information, etc., these information can be arranged according to the time of publication, for example, in reverse order according to the time of publication, so that users can view the most recently published information first.
  • the content sharing interface 60 may include a type selection area 670 to facilitate the user to quickly filter the shared content shown.
  • the type selection area 670 in FIG. 6 shows type options such as "All”, “Essence”, “Live Video”, and “Operation Tools", so that the user can select one or more type options to make the content Only this type of shared content is shown in the sharing interface 60, which is convenient for the user to view.
  • type tags should be added to facilitate screening and display by matching between type tags and type options.
  • the organization "e-commerce dry goods sharing” can have one or more related groups, such as "e-commerce study class 1" and "e-commerce study class 2" in the group chat entrance display area 630.
  • groups such as "e-commerce study class 1" and "e-commerce study class 2" in the group chat entrance display area 630.
  • FIG. 7 is a schematic diagram of a group chat interface provided by an exemplary embodiment.
  • the group chat interface 70 corresponding to the associated group "e-commerce class 1" may include an access entry 710 for the content sharing interface 60 described above. Therefore, when the user sends and receives group chat messages in the group chat interface 70, the access portal 710 can be triggered to quickly jump from the group chat interface 70 to the content sharing interface 60.
  • unread shared content or interactive content (or both) in the content sharing interface 60 it can be in the upper left corner of the access portal 710 (or other locations or areas related to the access portal 710)
  • a reminder mark 711 is shown, for example, the reminder mark 711 may be a dot. Therefore, even if the user is on the group chat interface 70, it can still be quickly determined based on the reminder identifier 711 that there is unread shared content and/or interactive content in the content sharing interface 60.
  • Fig. 8 is a schematic diagram of another group chat interface provided by an exemplary embodiment.
  • FIG 8 in the case where there is unread shared content or interactive content (or both) in the content sharing interface 60, it can be displayed in the upper left corner of the access portal 710 (it can also be related to the access portal 710).
  • a digital logo 712 is shown in other locations or areas of ), so that even if the user is on the group chat interface 70, it can still be quickly determined based on the digital logo 712 that there is unread shared content and/or interactive content in the content sharing interface 60 .
  • the digital identifier 712 includes the number 9, it indicates that the number of unread shared content and/or interactive content in the content sharing interface 60 is nine.
  • Fig. 9 is a schematic diagram of another content sharing interface provided by an exemplary embodiment.
  • the group chat interface 70 shown in FIG. 8 can be switched to the content sharing interface 90 shown in FIG. 9.
  • the content contained in the content sharing interface 90 is the same as the aforementioned content sharing interface 60. similar.
  • the content sharing interface 90 may include a content viewing portal 910 as shown in FIG. 9, so that the user can view the corresponding 9 pieces of new content by triggering the content viewing portal 910, that is, the aforementioned unidentified content. Reading shared content and/or interactive content.
  • the user may need to join the organization "e-commerce dry goods sharing" in advance.
  • users may need to join the organization "e-commerce dry goods sharing” before they can view all content such as those shown in Figure 6 in the content sharing interface 60, otherwise they can only view part of the content, such as limited to the summary information display area. 610.
  • the key member introduction area 620, the group chat entrance display area 630, etc., and other content cannot be viewed.
  • the content sharing interface 90 can include The content publishing option 920 shown in 9 enables the user to publish content by triggering the content publishing option 920 to realize content sharing.
  • the content publishing option 920 can be suspended in the content sharing interface 90, and the position of the content publishing option 920 on the device screen remains unchanged when the user flips through the content sharing interface 90, so that the user can conveniently publish the content at any time. 920 implements a trigger operation.
  • FIG. 10 is a schematic diagram of pushing shared content on a group chat interface according to an exemplary embodiment.
  • the organization "e-commerce dry goods sharing” can have an associated group “e-commerce study class 1". If the user "Xiaobai” publishes a dynamic in the organization "e-commerce dry goods sharing", that is, a piece of shared content is published, then The shared content can be automatically pushed to the group chat interface 1000 as shown in FIG. 10, so that group members can view the corresponding content 1010 in the group chat interface 1000.
  • the content 1010 is displayed in the floating window at the top of the group chat interface 1000, so that the content 1010 can be displayed in the upper layer of the group chat message in the group chat interface 1000, avoiding the group chat message pairing Content 1010 causes obscuration or flooding.
  • the content 1010 has a large amount of information and may not be displayed in the floating window as shown in FIG. 10, only part of the content can be displayed in the floating window from front to back, and the user can trigger the content 1010 and jump Go to the display page of the content 1010 in the content sharing interface 90, so that the user can view the content 1010 completely, and the user does not need to actively search for the content 1010 in the content sharing interface 90.
  • the floating window can also show the user's reading status of related shared content, such as "read”, "unread”, and so on.
  • Fig. 11 is another schematic diagram of pushing shared content on a group chat interface according to an exemplary embodiment. If the user "Xiaobai” publishes a dynamic in the organization “e-commerce dry goods sharing", that is, publishes a shared content, the shared content can be automatically pushed to the group chat interface 1100 as shown in Figure 11, and the sharing The content will be displayed in the group chat interface 1100 in the form of a communication message 1110, so that other group members can view it. Similar to the embodiment shown in FIG.
  • the amount of information about the shared content is relatively large, it may not be completely displayed in the display area of the communication message 1110, then only part of the content may be displayed in the display area from front to back, and The user can trigger the communication message 1110 and jump to the display page of the above-mentioned shared content in the content sharing interface 90, so that the user can view the shared content completely, and the user does not need to actively search for the shared content in the content sharing interface 90.
  • Figures 12-13 are schematic diagrams of accessing content sharing interfaces provided by an exemplary embodiment.
  • the application T can provide the user with an access portal 1210 independent of the associated group, so that the user can access the content sharing interface of the organization he has joined based on the access portal 1210, for example, based on the access portal 1210 to access the aforementioned The content sharing interface 90 and so on.
  • the application T may include a tab bar as shown at the bottom of FIG. 12, and the user can trigger the "message", “DING", "work”, and “contacts” contained in the tab bar. "My" and other tabs, switch between the corresponding tabs. For example, when the "My" tab is triggered, the function interface 1200 as shown in FIG. 12 may be shown.
  • the user can directly jump to the content sharing interface 90 shown in Figure 9 by triggering the access entry 1200 shown in Figure 12; and if the user If multiple organizations are added at the same time, the user can jump to the organization management interface 1300 shown in FIG. 13 by triggering the access entry 1210 shown in FIG. 12, and the organization management interface 1300 includes all organizations that the user has joined
  • the corresponding access portal allows the user to directly jump to the corresponding content sharing interface by selecting and triggering an access portal.
  • a reminder mark 1211 may be shown at the access entrance 1210 to indicate that there is unread shared content and/or interactive content in the organization to which the user has joined.
  • a digital identifier can be displayed on the access portal corresponding to the organization.
  • the digital identifier 1310 corresponding to the organization "e-commerce dry goods sharing” indicates that there are 9 unread shares
  • the content and/or interactive content indicates that there are 3 unread shared content and/or interactive content.
  • the summary information display area 610 may include an application option 611, and the user can request to join the organization "e-commerce dry goods sharing" by triggering the application option 611.
  • users can directly join the organization "E-commerce dry goods sharing" without review, or users need to join the organization "E-commerce dry goods sharing” after approval by members with management rights such as circle owners.
  • the user may need to join a certain associated group before being able to trigger the application option 611, otherwise the application option 611 cannot be triggered, and the content sharing interface 60 may not even be viewed. Then, you can manage the process of adding a user to an associated group. For example, when the associated group is an internal group of an enterprise, the user must be located in or added to the organization structure of the enterprise, otherwise the associated group cannot be added Group, so as to ensure that the members of the related group are closely related, and prevent irrelevant people from joining the related group and the corresponding organization at will.
  • FIGS. 14-15 are schematic diagrams of inviting users to join an organization provided by an exemplary embodiment.
  • the owner of the organization “e-commerce dry goods sharing” is the user “Xiaobai”
  • the browsing content sharing interface 1400 presented to the user “Xiaobai” by the application T may include an invitation option 1410.
  • the user "Xiaobai” can select one or more of its associated users, and invite and join the organization "E-commerce dry goods sharing”.
  • the associated users here can include the user "Xiaobai” in the application T Friends of, local contacts of the terminal, members of the group to which they belong, and members of the enterprise to which they belong, etc. This manual does not limit this.
  • the user “Xiaohong” can receive the invitation message 1510 sent by the user “Xiaobai” through the single chat interface 1500 as shown in FIG. "Red” can select "Join now” or “Forget it” contained in the invitation message 1510 to accept or decline the invitation.
  • the invitation message 1510 may not contain options, but may be linked to the content sharing interface 60 as shown in FIG. 6, so that the user "Xiaohong” can join the organization based on the application option 611 while browsing the content sharing interface 60. E-commerce dry goods sharing".
  • this manual provides an efficient and convenient content sharing program, which enables members who join the same organization to share content.
  • the organization members in this specification are relatively more closely related.
  • the organization "e-commerce dry goods sharing" in the above embodiment is applied to the e-commerce scenario, which is convenient for e-commerce.
  • the operators of the platform provide content sharing functions for a large number and types of merchants. For example, different types of merchants may be in different groups.
  • the content sharing solution in this manual can also be applied to many other scenarios, such as the internal empowerment of enterprise groups, education and training, enterprise services, official accounts and brand operations, and social organizations (such as chambers of commerce). Or conference), government agencies, public security, military, chain enterprises, franchisees, distributors, hospitals, fan groups, interest groups, etc. This manual does not limit this.
  • the owner can grant management rights to one or more members of the organization. If all members with management rights are called administrators, then different administrators can have differentiated management rights; for example, only administrators in the organization can publish shared content in the content sharing interface, and different administrators can manage The difference in authority allows it to publish only the type of sharing content corresponding to its own management authority.
  • Fig. 16 is a schematic structural diagram of a device according to an exemplary embodiment.
  • the device includes a processor 1602, an internal bus 1604, a network interface 1606, a memory 1608, and a non-volatile memory 1610, and of course, it may also include hardware required for other services.
  • the processor 1602 reads the corresponding computer program from the non-volatile memory 1610 to the memory 1608 and then runs it to form a content sharing device on a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each
  • the logic unit can also be a hardware or a logic device.
  • the content sharing device may include:
  • the request receiving unit 1701 enables the server to receive a content sharing request initiated by the sharing user, where the content sharing request is used to share the content to be shared submitted by the sharing user in a specific organization where the sharing user is located;
  • the content publishing unit 1702 enables the server to publish the content to be shared to the specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • the sharing user is any member in the specific organization; or, the sharing user is a member with sharing permission in the specific organization.
  • the members in the specific organization satisfy a predefined user relationship.
  • the predefined user relationship includes: belonging to the same group and/or participating in the same event.
  • the specific organization has a corresponding associated group; the device further includes:
  • the organization establishing unit 1703 enables the server to establish the specific organization for the associated group, so that group members and members of the specific organization correspond one-to-one.
  • the messaging interface of the associated group includes an access entry to the content sharing interface.
  • it also includes:
  • the content sending unit 1704 enables the server to send the content to be shared and/or the access link of the content to be shared in the content sharing interface to the associated group of the specific organization.
  • it also includes:
  • the receiving unit 1705 is configured to enable the server to receive a request to join the specific organization from the applicant user;
  • the response unit 1706 is configured to enable the server to add the applicant user to the specific organization when it is determined that the applicant user initiates the joining request for the joining invitation sent by the members of the specific organization , Otherwise refuse to add.
  • the specific organization includes a sub-level organization
  • the content sharing interface includes: a general content sharing interface corresponding to the specific organization and a content sharing sub-interface corresponding to the sub-level organization.
  • the content publishing unit 1702 is specifically configured to:
  • the access authority of the general content sharing interface is restricted to all members of the specific organization
  • the access authority of the content sharing sub-interface is restricted to all members of the specific organization or members of corresponding sub-organizations.
  • the server implements the content sharing method by running a server program of an instant messaging application.
  • Fig. 18 is a schematic structural diagram of a device according to an exemplary embodiment.
  • the device includes a processor 1802, an internal bus 1804, a network interface 1806, a memory 1808, and a non-volatile memory 1810, and of course, it may also include hardware required for other services.
  • the processor 1802 reads the corresponding computer program from the non-volatile memory 1810 to the memory 1808 and then runs it to form a content sharing device on a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each
  • the logic unit can also be a hardware or a logic device.
  • the content sharing device may include:
  • the request receiving unit 1901 enables the server to receive the content sharing request initiated by the sharing party user;
  • the content publishing unit 1902 enables the server to publish the content to be shared provided by the sharing user to a specific organization, so that the content to be shared is presented on a content sharing interface related to the specific organization.
  • Fig. 20 is a schematic structural diagram of a device according to an exemplary embodiment. Please refer to FIG. 20.
  • the device includes a processor 2002, an internal bus 2004, a network interface 2006, a memory 2008, and a non-volatile memory 2010. Of course, it may also include hardware required for other services.
  • the processor 2002 reads the corresponding computer program from the non-volatile memory 2010 to the memory 2008 and then runs it to form a content sharing device on a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each
  • the logic unit can also be a hardware or a logic device.
  • the content sharing device may include:
  • the determining unit 2101 enables the terminal to determine the content to be shared provided by the sharing user and the specific organization where the sharing user is located;
  • the request unit 2102 enables the terminal to initiate a content sharing request to the server, so that the server publishes the content to be shared to the specific organization, so that the content to be shared is presented in content sharing related to the specific organization interface.
  • Fig. 22 is a schematic structural diagram of a device according to an exemplary embodiment. Please refer to FIG. 22.
  • the device includes a processor 2202, an internal bus 2204, a network interface 2206, a memory 2208, and a non-volatile memory 2210. Of course, it may also include hardware required for other services.
  • the processor 2202 reads the corresponding computer program from the non-volatile memory 2210 to the memory 2208 and then runs it to form a content sharing device on a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each
  • the logic unit can also be a hardware or a logic device.
  • the content sharing device may include:
  • the group interface display unit 2301 enables the terminal to display the messaging interface of the group where the local user is located, the group corresponding to the specific organization where the local user is located;
  • the sharing interface display unit 2302 enables the terminal to activate a content sharing interface related to the specific organization according to a trigger operation for the access entry contained in the messaging interface, and the content sharing interface is used to display information from the specific organization.
  • it also includes:
  • the reminder information display unit 2303 enables the terminal to display reminder information in the display area of the access entrance, where the reminder information is used to indicate that there is unread shared content and/or unread interactive content in the content sharing interface.
  • the content sharing interface and the messaging interface belong to the same application.
  • the sharing interface display unit 2302 is specifically configured to:
  • the terminal is made to display the messaging interface and the content sharing interface side by side.
  • a typical implementation device is a computer.
  • the specific form of the computer can 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 receiving and sending device, and a game control A console, a tablet computer, a wearable device, or a combination of any of these devices.
  • the computer includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • processors CPU
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-permanent memory in a computer readable medium, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, 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 (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory 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 this 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.
  • first information may also be referred to as second information, and similarly, the second information may also be referred to as first information.
  • word “if” as used herein can be interpreted as "when” or “when” or "in response to determination”.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Graphics (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本说明书一个或多个实施例提供一种内容分享方法及装置，该方法可以包括：服务器接收分享方用户发起的内容分享请求，所述内容分享请求用于将所述分享方用户提交的待分享内容在所述分享方用户所处的特定组织内进行分享；所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。

Description

内容分享方法及装置
本申请要求2019年10月09日递交的申请号为201910954054.4、发明名称为“内容分享方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本说明书一个或多个实施例涉及互联网技术领域，尤其涉及一种内容分享方法及装置。
背景技术
在相关技术中，用户之间可以基于通讯应用实现数据传输，使得在用户之间实现高效通讯。例如，用户之间可以建立单聊以实现一对一通讯；而为了提升通讯效率，可以通过建立群聊以实现所有群组成员之间的高效通讯。
但是，群组通讯往往容易夹杂成员之间的大量闲聊内容，甚至可能淹没一些有价值的内容。
发明内容
有鉴于此，本说明书一个或多个实施例提供一种内容分享方法及装置。
为实现上述目的，本说明书一个或多个实施例提供技术方案如下：
根据本说明书一个或多个实施例的第一方面，提出了一种内容分享方法，包括：
服务器接收分享方用户发起的内容分享请求，所述内容分享请求用于将所述分享方用户提交的待分享内容在所述分享方用户所处的特定组织内进行分享；
所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
根据本说明书一个或多个实施例的第二方面，提出了一种内容分享方法，包括：
服务器接收分享方用户发起的内容分享请求；
所述服务器将所述分享方用户提供的待分享内容发布至特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
根据本说明书一个或多个实施例的第三方面，提出了一种内容分享方法，包括：
终端确定分享方用户提供的待分享内容和所述分享方用户所处的特定组织；
所述终端向服务器发起内容分享请求，使所述服务器将所述待分享内容发布至所述 特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
根据本说明书一个或多个实施例的第四方面，提出了一种内容分享方法，包括：
终端展示本端用户所处群组的消息收发界面，所述群组对应于所述本端用户所处的特定组织；
所述终端根据针对所述消息收发界面中所含访问入口的触发操作，启动与所述特定组织相关的内容分享界面，所述内容分享界面用于展示来自所述特定组织的成员的分享内容。
根据本说明书一个或多个实施例的第五方面，提出了一种内容分享装置，包括：
请求接收单元，使服务器接收分享方用户发起的内容分享请求，所述内容分享请求用于将所述分享方用户提交的待分享内容在所述分享方用户所处的特定组织内进行分享；
内容发布单元，使所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
根据本说明书一个或多个实施例的第六方面，提出了一种内容分享装置，包括：
请求接收单元，使服务器接收分享方用户发起的内容分享请求；
内容发布单元，使所述服务器将所述分享方用户提供的待分享内容发布至特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
根据本说明书一个或多个实施例的第七方面，提出了一种内容分享装置，包括：
确定单元，使终端确定分享方用户提供的待分享内容和所述分享方用户所处的特定组织；
请求单元，使所述终端向服务器发起内容分享请求，使所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
根据本说明书一个或多个实施例的第八方面，提出了一种内容分享装置，包括：
群组界面展示单元，使终端展示本端用户所处群组的消息收发界面，所述群组对应于所述本端用户所处的特定组织；
分享界面展示单元，使所述终端根据针对所述消息收发界面中所含访问入口的触发操作，启动与所述特定组织相关的内容分享界面，所述内容分享界面用于展示来自所述特定组织的成员的分享内容。
根据本说明书一个或多个实施例的第九方面，提出了一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器通过运行所述可执行指令以实现如第一方面或第二方面所述的方法。
根据本说明书一个或多个实施例的第十方面，提出了一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如第一方面或第二方面所述方法的步骤。
根据本说明书一个或多个实施例的第十一方面，提出了一种电子设备，包括：
处理器；
用于存储处理器可执行指令的存储器；
其中，所述处理器通过运行所述可执行指令以实现如第三方面或第四方面所述的方法。
根据本说明书一个或多个实施例的第十二方面，提出了一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如第三方面或第四方面所述方法的步骤。
附图说明
图1是一示例性实施例提供的一种内容分享系统的架构示意图。
图2是一示例性实施例提供的一种服务器侧的内容分享方法的流程图。
图3是一示例性实施例提供的另一种服务器侧的内容分享方法的流程图。
图4是一示例性实施例提供的一种终端侧的内容分享方法的流程图。
图5是一示例性实施例提供的另一种终端侧的内容分享方法的流程图。
图6是一示例性实施例提供的一种内容分享界面的示意图。
图7是一示例性实施例提供的一种群聊界面的示意图。
图8是一示例性实施例提供的另一种群聊界面的示意图。
图9是一示例性实施例提供的另一种内容分享界面的示意图。
图10是一示例性实施例提供的一种在群聊界面推送分享内容的示意图。
图11是一示例性实施例提供的另一种在群聊界面推送分享内容的示意图。
图12-图13是一示例性实施例提供的一种访问内容分享界面的示意图。
图14-图15是一示例性实施例提供的一种邀请用户加入组织的示意图。
图16是一示例性实施例提供的一种服务器侧的设备的结构示意图。
图17是一示例性实施例提供的一种服务器侧的内容分享装置的框图。
图18是一示例性实施例提供的另一种服务器侧的设备的结构示意图。
图19是一示例性实施例提供的另一种服务器侧的内容分享装置的框图。
图20是一示例性实施例提供的一种终端侧的设备的结构示意图。
图21是一示例性实施例提供的一种终端侧的内容分享装置的框图。
图22是一示例性实施例提供的另一种终端侧的设备的结构示意图。
图23是一示例性实施例提供的另一种终端侧的内容分享装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本说明书一个或多个实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本说明书一个或多个实施例的一些方面相一致的装置和方法的例子。
需要说明的是：在其他实施例中并不一定按照本说明书示出和描述的顺序来执行相应方法的步骤。在一些其他实施例中，其方法所包括的步骤可以比本说明书所描述的更多或更少。此外，本说明书中所描述的单个步骤，在其他实施例中可能被分解为多个步骤进行描述；而本说明书中所描述的多个步骤，在其他实施例中也可能被合并为单个步骤进行描述。
图1是一示例性实施例提供的一种内容分享系统的架构示意图。如图1所示，该系统可以包括服务器11、网络12、若干电子设备，比如手机13、手机14和手机15等。
服务器11可以为包含一独立主机的物理服务器，或者该服务器11可以为主机集群承载的虚拟服务器。在运行过程中，服务器11可以运行某一应用的服务器侧的程序，以实现该应用的相关业务功能，比如当该服务器11运行即时通讯应用的程序时，可以实现为该即时通讯应用的服务端。
在本实施例中，即时通讯应用可以包括普通即时通讯应用或企业即时通讯应用，本说明书并不对此进行限制。其中，即时通讯应用除了能够实现通讯功能之外，还可以作为诸多其他功能的集成化功能平台，比如对于审批事件(如请假、办公物品申领、财务等审批事件)、考勤事件、任务事件、日志事件等团体事件的处理，本说明书一个或多 个实施例并不对此进行限制。
手机13-15只是用户可以使用的一种类型的电子设备。实际上，用户显然还可以使用诸如下述类型的电子设备：平板设备、笔记本电脑、掌上电脑(PDAs，Personal Digital Assistants)、可穿戴设备(如智能眼镜、智能手表等)等，本说明书一个或多个实施例并不对此进行限制。在运行过程中，该电子设备可以运行某一应用的客户端侧的程序，以实现该应用的相关业务功能，比如当该电子设备运行即时通讯应用的程序时，可以实现为该即时通讯应用的客户端。
需要指出的是：即时通讯应用的客户端的应用程序可以被预先安装在电子设备上，使得该客户端可以在该电子设备上被启动并运行；当然，当采用诸如HTML5技术的在线“客户端”时，无需在电子设备上安装相应的应用程序，即可获得并运行该客户端。
而对于手机13-15与服务器11之间进行交互的网络12，可以包括多种类型的有线或无线网络。在一实施例中，该网络12可以包括公共交换电话网络(Public Switched Telephone Network，PSTN)和因特网。同时，手机13-15等电子设备之间也可以通过该网络12进行通讯交互，比如在任意两台电子设备之间建立单聊通讯会话；或者，若干电子设备可以参与至同一群聊通讯会话，使得任一用户可以通过自身的电子设备向该群聊通讯会话中的其他所有用户发送通讯消息。
图2是一示例性实施例提供的一种服务器侧的内容分享方法的流程图。如图2所示，该方法应用于服务器(例如图1所示的服务器11等)，可以包括以下步骤：
步骤202，服务器接收分享方用户发起的内容分享请求，所述内容分享请求用于将所述分享方用户提交的待分享内容在所述分享方用户所处的特定组织内进行分享。
在一实施例中，服务器上运行有某一应用的服务器侧程序，使得该服务器被配置该应用的服务端；相应地，分享方用户所使用的终端上运行有上述应用的终端侧程序，使得该终端被配置为该应用的客户端。因此，服务器与分享方用户使用的终端之间可以基于上述应用实现交互。例如，上述应用可以为通讯应用，比如即时通讯应用或其他类型的通讯应用。
在一实施例中，分享方用户是指实施内容分享操作的用户，比如上述分享方用户希望将上述的待分享内容分享至自身所处的特定组织。类似地，当其他用户希望向自身所处的组织内分享内容时，该其他用户也可以成为上述的分享方用户。换言之，分享方用户为一种用户角色，而非某一固定的用户。
在一实施例中，分享方用户可以将待分享内容添加在内容分享请求中，以发送至服 务器。或者，分享方用户可以将待分享内容与内容分享请求相互独立地发送至服务器。或者，分享方用户可以预先将待分享内容发送至某一存储空间(如服务器维护的存储空间，或者服务器可达的其他存储空间)，并通过内容分享请求指示服务器从该存储空间获得上述的待分享内容。
在一实施例中，分享方用户可以为上述特定组织内的任一成员。换言之，该特定组织内的每个成员均可以作为上述的分享方用户，以针对该特定组织进行内容分享。
在一实施例中，分享方用户可以为上述特定组织内具有分享权限的成员。换言之，该特定组织内的不同成员所具有的权限可以存在差异，使得具有分享权限的这部分成员可以作为上述的分享方用户，以针对该特定组织进行内容分享，而不具有分享权限的其他成员则无法针对该特定组织进行内容分享。例如，该特定组织的成员中可以包括管理员和普通成员，管理员可以具有分享权限，且管理员可以向至少一个普通成员赋予或收回分享权限。再例如，该特定组织存在相应的组织结构，各个成员在该组织结构中处于对应的层级，那么对应层级不低于预设层级的成员可以具有分享权限，而低于该预设层级的成员则不具有分享权限。又例如，该特定组织可以存在相关联的测试任务，成员在完成该测试任务的情况下，可以自动获得分享权限。该特定组织内的成员还可以通过其他方式获得分享权限，本说明书并不对此进行限制。
在一实施例中，待分享内容可以包含任意类型的内容，比如文字、图片、视频、音频、表格等，本说明书并不对此进行限制。
在一实施例中，本说明书的特定组织内的成员之间具有相对紧密的相互关系，而区别于相关技术中诸如社区(BBS，Bulletin Board System)、贴吧等场景下的松散关系，使得成员在发布待分享内容时需要针对上述相对紧密的相互关系加以考量，并主动避免发布不恰当的待分享内容，使得成员之间的内容分享相对更加高效、可控。
在一实施例中，上述特定组织内的成员之间满足预定义的用户关系，以体现出上述相对紧密的相互关系。例如，该预定义的用户关系可以包括：归属于同一团体，这里的团体可以理解为企业、医院、学校、部队、政府机关等，或者上述各类团体内的部门等，本说明书并不对此进行限制。再例如，该预定义的用户关系可以包括：参与同一事件，该事件可以包括任务事件、会议事件、诊疗事件、教学事件等。当然，上述用户关系还可以包括其他类型的相对紧密的相互关系，比如成员之间具有好友关系、合作关系等，还可以同时满足上述的多种关系(譬如同时归属于同一团体且参与同一事件，再譬如同时具有合作关系且参与同一事件等)，本说明书并不对此进行限制。
在一实施例中，上述特定组织可以在已有团体的基础上建立。比如，针对已经存在的企业，可以基于服务器所维护的该企业的组织结构建立上述的特定组织，使得企业成员被添加为该特定组织的成员、该特定组织的成员形成的组织结构与该企业内的企业成员形成的组织结构可以相同(也可以存在差异)。例如，上述企业的管理员可以通过向服务器发起组织建立请求，使得服务器可以基于该企业的组织结构建立起上述的特定组织。
在一实施例中，上述特定组织的加入形式可以为邀请制。例如，申请方用户可以向服务器发起针对该特定组织的加入请求，而服务器基于接收到的该加入请求，可以在确定申请方用户为针对该特定组织的成员所发出的加入邀请而发起上述加入请求的情况下，将该申请方用户添加至该特定组织，否则拒绝添加。换言之，需要由特定组织的成员向申请方用户发出加入邀请后，由该申请方用户针对该加入邀请发起加入请求，服务器才会同意申请方用户的请求、将该申请方用户添加至特定组织，而当申请方用户在未收到加入邀请的情况下直接发出针对该特定组织的加入请求时，服务器将会拒绝该加入请求。
步骤204，所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
在一实施例中，服务器将待分享内容发布至特定组织后，通过使得该待分享内容呈现于与该特定组织相关的内容分享界面中，相比于相关技术中在该特定组织对应的关联群组内发布待分享内容，可以在该内容分享界面中对所有被分享的内容进行统一展示，且可以避免所展示的内容被群组成员之间的闲聊内容影响，确保该特征组织的成员能够更为便捷地查看被分享的内容，有助于提升内容的传达效率。
在一实施例中，与特定组织相关的内容分享界面，即该内容分享界面与该特定组织之间存在预设关联。例如，该特定组织仅存在一个相关的内容分享界面，该内容分享界面对应于整个特定组织，使得任一成员将待分享内容发布至该特定组织(假定该任一成员具有分享权限)时，该待分享内容都被呈现于该内容分享界面。再例如，上述特定组织可以包括子级组织，该特定组织与子级组织之间的关系类似于企业与部门、医院与科室、学校与班级等之间的关系，而上述与特定组织相关的内容分享界面可以包括：对应于特定组织的内容分享总界面、对应于子级组织的内容分享子界面，即内容分享总界面对应于整个特定组织、内容分享子界面对应于子级组织(即整个特定组织的一部分)。特定组织可以包含多个子级组织，各个子级组织之间可以相互独立，也可以存在至少一 部分重叠，甚至一些层级较高的子级组织可以完全包含其他的一个或多个层级较低的子级组织；譬如在企业场景下，开发部门对应于一子级组织1，而开发部门下属的软件开发部门对应于一子级组织2、硬件开发部门对应于一子级组织3，那么子级组织1可以认为包含子级组织2和子级组织3，而子级组织2与子级组织3之间相互独立。
在一实施例中，在同时存在上述的内容分享总界面和内容分享子界面的情况下，针对分享方用户所发起的内容分享请求，待分享内容可以被发布至特定组织或特定组织的子级组织，从而呈现于内容分享总界面或内容分享子界面。例如，服务器可以根据分享方用户的权限级别，确定将待分享内容发布至特定组织还是该特定组织的子级组织；其中，在分享方用户的权限级别匹配于特定组织对应的权限等级需求(当然，此时通常也会匹配于子级组织对应的权限等级需求)的情况下，服务器可以默认将待分享内容发布至特定组织、以呈现于内容分享总界面，在分享方用户的权限级别匹配于子级组织(分享方用户可以处于该子级组织，也可以不处于该子级组织)对应的权限等级需求但不匹配于特定组织的情况下，服务器可以默认将待分享内容发布至特定组织的子级组织、以呈现于相应的内容分享子界面。再例如，服务器可以根据分享方用户的配置信息，确定将待分享内容发布至特定组织或该分享方用户所处的子级组织，从而呈现于内容分享总界面或分享方用户所处的子级组织对应的内容分享子界面；换言之，分享方用户的权限级别可能匹配于特定组织对应的权限等级需求，但该分享方用户仍然可以通过设定上述的配置信息，从而将待分享内容发布至该分享方用户所处的子级组织、以呈现于相应的内容分享子界面中，而非发布至该特定组织而呈现于相应的内容分享总界面中。
在一实施例中，上述的内容分享总界面、内容分享子界面存在相应的访问权限，使得仅具有相应访问权限的用户可以进行访问。例如，可以根据用户对特定组织或子级组织的归属情况，确定该用户是否可以访问相应的内容分享界面。其中，内容分享总界面的访问权限可以被限制为特定组织的所有成员，即由于这些成员归属于特定组织，使得这些成员具有针对该特定组织对应的内容分享总界面的访问权限，而不属于该特定组织的用户则无法访问；内容分享子界面的访问权限可以被限制为相应子级组织的成员，即由于这些成员归属于该子级组织，使得这些成员具有针对该子级组织对应的内容分享子界面的访问权限，而不属于该子级组织的用户即便归属于特定组织也无法访问。当然，还可以通过其他方式确定用户是否具有对相应内容分享界面进行访问的权限。比如，对于上述的子级组织对应的内容分享子界面而言，可以设定为特定组织的所有成员均具有访问权限，本说明书并不对此进行限制。
在一实施例中，服务器可以为上述的特定组织建立关联群组，使群组成员与特定组织的成员一一对应，便于该特定组织的成员基于关联群组进行高效沟通。类似地，对于原本已经存在的群组，服务器也可以针对该群组建立相应的组织。对于特定组织及其关联群组而言，可以在与该特定群组相关的内容分享界面与该关联群组的消息收发界面之间实现互动，以便于成员实现快捷的界面切换。例如，关联群组的消息收发界面中可以包含内容分享界面的访问入口，反之也可以在内容分享界面中添加消息收发界面的访问入口。需要指出的是：关联群组的数量可以为一个，这个关联群组的群组成员为特定组织的所有成员；或者，关联群组的数量可以为多个，特定组织的所有成员分别位于这些关联群组内。
在一实施例中，针对分享方用户需要分享的待分享内容，除了将其呈现于与特定组织相关的内容分享界面之外，服务器还可以将该待分享内容发送至特定组织的关联群组，使得成员可以选择在内容分享界面或内容收发界面查看该待分享内容，比如原本就位于消息收发界面的成员无需专门切换至内容分享界面、无需在内容分享界面中寻找该待分享内容，即可在消息收发界面快捷地查看该待分享内容的内容。服务器还可以通过其他方式来提升成员对待分享内容的查看便捷度。例如，服务器可以将待分享内容在内容分享界面内的访问链接发送至特定组织的关联群组，那么虽然成员无法直接在消息收发界面中查看到待分享内容的内容，但是只需要在消息收发界面中触发该访问链接，即可快速跳转和查看该待分享内容的内容，而无需在内容分享界面中寻找该待分享内容。
图3是一示例性实施例提供的另一种服务器侧的内容分享方法的流程图。如图3所示，该方法应用于服务器(例如图1所示的服务器11等)，可以包括以下步骤：
步骤302，服务器接收分享方用户发起的内容分享请求。
在一实施例中，服务器上运行有某一应用的服务器侧程序，使得该服务器被配置该应用的服务端；相应地，分享方用户所使用的终端上运行有上述应用的终端侧程序，使得该终端被配置为该应用的客户端。因此，服务器与分享方用户使用的终端之间可以基于上述应用实现交互。例如，上述应用可以为通讯应用，比如即时通讯应用或其他类型的通讯应用。
在一实施例中，分享方用户是指实施内容分享操作的用户，比如上述分享方用户希望将上述的待分享内容分享至自身所处的特定组织。类似地，当其他用户希望向自身所处的组织内分享内容时，该其他用户也可以成为上述的分享方用户。换言之，分享方用户为一种用户角色，而非某一固定的用户。在一些情况下，分享方用户并不属于上述的 特定组织，但该分享方用户仍然可以通过分享的方式，使得该特定组织的成员可以查看到上述的待分享内容。
在一实施例中，分享方用户可以将待分享内容添加在内容分享请求中，以发送至服务器。或者，分享方用户可以将待分享内容与内容分享请求相互独立地发送至服务器。或者，分享方用户可以预先将待分享内容发送至某一存储空间(如服务器维护的存储空间，或者服务器可达的其他存储空间)，并通过内容分享请求指示服务器从该存储空间获得上述的待分享内容。
在一实施例中，待分享内容可以包含任意类型的内容，比如文字、图片、视频、音频、表格等，本说明书并不对此进行限制。
在一实施例中，在属于上述特定组织的情况下，分享方用户可以为该特定组织内的任一成员。换言之，该特定组织内的每个成员均可以作为上述的分享方用户，以针对该特定组织进行内容分享。
在一实施例中，分享方用户可以为上述特定组织内具有分享权限的成员。换言之，该特定组织内的不同成员所具有的权限可以存在差异，使得具有分享权限的这部分成员可以作为上述的分享方用户，以针对该特定组织进行内容分享，而不具有分享权限的其他成员则无法针对该特定组织进行内容分享。例如，该特定组织的成员中可以包括管理员和普通成员，管理员可以具有分享权限，且管理员可以向至少一个普通成员赋予或收回分享权限。再例如，该特定组织存在相应的组织结构，各个成员在该组织结构中处于对应的层级，那么对应层级不低于预设层级的成员可以具有分享权限，而低于该预设层级的成员则不具有分享权限。又例如，该特定组织可以存在相关联的测试任务，成员在完成该测试任务的情况下，可以自动获得分享权限。该特定组织内的成员还可以通过其他方式获得分享权限，本说明书并不对此进行限制。
在一实施例中，本说明书的特定组织内的成员之间具有相对紧密的相互关系，而区别于相关技术中诸如社区(BBS，Bulletin Board System)、贴吧等场景下的松散关系，使得成员在发布待分享内容时需要针对上述相对紧密的相互关系加以考量，并主动避免发布不恰当的待分享内容，使得成员之间的内容分享相对更加高效、可控。
在一实施例中，上述特定组织内的成员之间满足预定义的用户关系，以体现出上述相对紧密的相互关系。例如，该预定义的用户关系可以包括：归属于同一团体，这里的团体可以理解为企业、医院、学校、部队、政府机关等，或者上述各类团体内的部门等，本说明书并不对此进行限制。再例如，该预定义的用户关系可以包括：参与同一事件， 该事件可以包括任务事件、会议事件、诊疗事件、教学事件等。当然，上述用户关系还可以包括其他类型的相对紧密的相互关系，比如成员之间具有好友关系、合作关系等，还可以同时满足上述的多种关系(譬如同时归属于同一团体且参与同一事件，再譬如同时具有合作关系且参与同一事件等)，本说明书并不对此进行限制。
在一实施例中，上述特定组织可以在已有团体的基础上建立。比如，针对已经存在的企业，可以基于服务器所维护的该企业的组织结构建立上述的特定组织，使得企业成员被添加为该特定组织的成员、该特定组织的成员形成的组织结构与该企业内的企业成员形成的组织结构可以相同(也可以存在差异)。例如，上述企业的管理员可以通过向服务器发起组织建立请求，使得服务器可以基于该企业的组织结构建立起上述的特定组织。
在一实施例中，上述特定组织的加入形式可以为邀请制。例如，申请方用户可以向服务器发起针对该特定组织的加入请求，而服务器基于接收到的该加入请求，可以在确定申请方用户为针对该特定组织的成员所发出的加入邀请而发起上述加入请求的情况下，将该申请方用户添加至该特定组织，否则拒绝添加。换言之，需要由特定组织的成员向申请方用户发出加入邀请后，由该申请方用户针对该加入邀请发起加入请求，服务器才会同意申请方用户的请求、将该申请方用户添加至特定组织，而当申请方用户在未收到加入邀请的情况下直接发出针对该特定组织的加入请求时，服务器将会拒绝该加入请求。
步骤304，所述服务器将所述分享方用户提供的待分享内容发布至特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
在一实施例中，服务器将待分享内容发布至特定组织后，通过使得该待分享内容呈现于与该特定组织相关的内容分享界面中，相比于相关技术中在该特定组织对应的关联群组内发布待分享内容，可以在该内容分享界面中对所有被分享的内容进行统一展示，且可以避免所展示的内容被群组成员之间的闲聊内容影响，确保该特征组织的成员能够更为便捷地查看被分享的内容，有助于提升内容的传达效率。
在一实施例中，与特定组织相关的内容分享界面，即该内容分享界面与该特定组织之间存在预设关联。例如，该特定组织仅存在一个相关的内容分享界面，该内容分享界面对应于整个特定组织，使得任一成员将待分享内容发布至该特定组织(假定该任一成员具有分享权限)时，该待分享内容都被呈现于该内容分享界面。再例如，上述特定组织可以包括子级组织，该特定组织与子级组织之间的关系类似于企业与部门、医院与科 室、学校与班级等之间的关系，而上述与特定组织相关的内容分享界面可以包括：对应于特定组织的内容分享总界面、对应于子级组织的内容分享子界面，即内容分享总界面对应于整个特定组织、内容分享子界面对应于子级组织(即整个特定组织的一部分)。特定组织可以包含多个子级组织，各个子级组织之间可以相互独立，也可以存在至少一部分重叠，甚至一些层级较高的子级组织可以完全包含其他的一个或多个层级较低的子级组织；譬如在企业场景下，开发部门对应于一子级组织1，而开发部门下属的软件开发部门对应于一子级组织2、硬件开发部门对应于一子级组织3，那么子级组织1可以认为包含子级组织2和子级组织3，而子级组织2与子级组织3之间相互独立。
在一实施例中，在同时存在上述的内容分享总界面和内容分享子界面的情况下，针对分享方用户所发起的内容分享请求，待分享内容可以被发布至特定组织或特定组织的子级组织，从而呈现于内容分享总界面或内容分享子界面。例如，服务器可以根据分享方用户的权限级别，确定将待分享内容发布至特定组织还是该特定组织的子级组织；其中，在分享方用户的权限级别匹配于特定组织对应的权限等级需求(当然，此时通常也会匹配于子级组织对应的权限等级需求)的情况下，服务器可以默认将待分享内容发布至特定组织、以呈现于内容分享总界面，在分享方用户的权限级别匹配于子级组织(分享方用户可以处于该子级组织，也可以不处于该子级组织)对应的权限等级需求但不匹配于特定组织的情况下，服务器可以默认将待分享内容发布至特定组织的子级组织、以呈现于相应的内容分享子界面。再例如，服务器可以根据分享方用户的配置信息，确定将待分享内容发布至特定组织或该分享方用户所处的子级组织，从而呈现于内容分享总界面或分享方用户所处的子级组织对应的内容分享子界面；换言之，分享方用户的权限级别可能匹配于特定组织对应的权限等级需求，但该分享方用户仍然可以通过设定上述的配置信息，从而将待分享内容发布至该分享方用户所处的子级组织、以呈现于相应的内容分享子界面中，而非发布至该特定组织而呈现于相应的内容分享总界面中。
在一实施例中，上述的内容分享总界面、内容分享子界面存在相应的访问权限，使得仅具有相应访问权限的用户可以进行访问。例如，可以根据用户对特定组织或子级组织的归属情况，确定该用户是否可以访问相应的内容分享界面。其中，内容分享总界面的访问权限可以被限制为特定组织的所有成员，即由于这些成员归属于特定组织，使得这些成员具有针对该特定组织对应的内容分享总界面的访问权限，而不属于该特定组织的用户则无法访问；内容分享子界面的访问权限可以被限制为相应子级组织的成员，即由于这些成员归属于该子级组织，使得这些成员具有针对该子级组织对应的内容分享子 界面的访问权限，而不属于该子级组织的用户即便归属于特定组织也无法访问。当然，还可以通过其他方式确定用户是否具有对相应内容分享界面进行访问的权限。比如，对于上述的子级组织对应的内容分享子界面而言，可以设定为特定组织的所有成员均具有访问权限，本说明书并不对此进行限制。
在一实施例中，服务器可以为上述的特定组织建立关联群组，使群组成员与特定组织的成员一一对应，便于该特定组织的成员基于关联群组进行高效沟通。类似地，对于原本已经存在的群组，服务器也可以针对该群组建立相应的组织。对于特定组织及其关联群组而言，可以在与该特定群组相关的内容分享界面与该关联群组的消息收发界面之间实现互动，以便于成员实现快捷的界面切换。例如，关联群组的消息收发界面中可以包含内容分享界面的访问入口，反之也可以在内容分享界面中添加消息收发界面的访问入口。需要指出的是：关联群组的数量可以为一个，这个关联群组的群组成员为特定组织的所有成员；或者，关联群组的数量可以为多个，特定组织的所有成员分别位于这些关联群组内。
在一实施例中，针对分享方用户需要分享的待分享内容，除了将其呈现于与特定组织相关的内容分享界面之外，服务器还可以将该待分享内容发送至特定组织的关联群组，使得成员可以选择在内容分享界面或消息收发界面查看该待分享内容，比如原本就位于消息收发界面的成员无需专门切换至内容分享界面、无需在内容分享界面中寻找该待分享内容，即可在消息收发界面快捷地查看该待分享内容的内容。服务器还可以通过其他方式来提升成员对待分享内容的查看便捷度。例如，服务器可以将待分享内容在内容分享界面内的访问链接发送至特定组织的关联群组，那么虽然成员无法直接在消息收发界面中查看到待分享内容的内容，但是只需要在消息收发界面中触发该访问链接，即可快速跳转和查看该待分享内容的内容，而无需在内容分享界面中寻找该待分享内容。
图4是一示例性实施例提供的一种终端侧的内容分享方法的流程图。如图4所示，该方法应用于终端(例如图1所示的手机13～15等)，可以包括以下步骤：
步骤402，终端确定分享方用户提供的待分享内容和所述分享方用户所处的特定组织。
在一实施例中，分享方用户是指实施内容分享操作的用户，比如上述分享方用户希望将上述的待分享内容分享至自身所处的特定组织。类似地，当其他用户希望向自身所处的组织内分享内容时，该其他用户也可以成为上述的分享方用户。换言之，分享方用户为一种用户角色，而非某一固定的用户。从终端的角度而言，分享方用户为在终端上 实施分享操作的用户，该分享方用户通常需要在终端上登录其预先注册的账号信息，即终端基于所登录的账号信息来区分相应用户的身份。
在一实施例中，待分享内容可以包含任意类型的内容，比如文字、图片、视频、音频、表格等，本说明书并不对此进行限制。
在一实施例中，本说明书的特定组织内的成员之间具有相对紧密的相互关系，而区别于相关技术中诸如社区(BBS，Bulletin Board System)、贴吧等场景下的松散关系，使得成员在发布待分享内容时需要针对上述相对紧密的相互关系加以考量，并主动避免发布不恰当的待分享内容，使得成员之间的内容分享相对更加高效、可控。
在一实施例中，上述特定组织内的成员之间满足预定义的用户关系，以体现出上述相对紧密的相互关系。例如，该预定义的用户关系可以包括：归属于同一团体，这里的团体可以理解为企业、医院、学校、部队、政府机关等，或者上述各类团体内的部门等，本说明书并不对此进行限制。再例如，该预定义的用户关系可以包括：参与同一事件，该事件可以包括任务事件、会议事件、诊疗事件、教学事件等。当然，上述用户关系还可以包括其他类型的相对紧密的相互关系，比如成员之间具有好友关系、合作关系等，还可以同时满足上述的多种关系(譬如同时归属于同一团体且参与同一事件，再譬如同时具有合作关系且参与同一事件等)，本说明书并不对此进行限制。
在一实施例中，上述特定组织可以在已有团体的基础上建立。比如，针对已经存在的企业，可以基于服务器所维护的该企业的组织结构建立上述的特定组织，使得企业成员被添加为该特定组织的成员、该特定组织的成员形成的组织结构与该企业内的企业成员形成的组织结构可以相同(也可以存在差异)。例如，上述企业的管理员可以通过向服务器发起组织建立请求，使得服务器可以基于该企业的组织结构建立起上述的特定组织。
在一实施例中，上述特定组织的加入形式可以为邀请制。例如，申请方用户可以向服务器发起针对该特定组织的加入请求，而服务器基于接收到的该加入请求，可以在确定申请方用户为针对该特定组织的成员所发出的加入邀请而发起上述加入请求的情况下，将该申请方用户添加至该特定组织，否则拒绝添加。换言之，需要由特定组织的成员向申请方用户发出加入邀请后，由该申请方用户针对该加入邀请发起加入请求，服务器才会同意申请方用户的请求、将该申请方用户添加至特定组织，而当申请方用户在未收到加入邀请的情况下直接发出针对该特定组织的加入请求时，服务器将会拒绝该加入请求。
步骤404，所述终端向服务器发起内容分享请求，使所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
在一实施例中，服务器上运行有某一应用的服务器侧程序，使得该服务器被配置该应用的服务端；相应地，分享方用户所使用的终端上运行有上述应用的终端侧程序，使得该终端被配置为该应用的客户端。因此，服务器与分享方用户使用的终端之间可以基于上述应用实现交互。例如，上述应用可以为通讯应用，比如即时通讯应用或其他类型的通讯应用。
在一实施例中，终端可以将待分享内容添加在内容分享请求中，以发送至服务器。或者，终端可以将待分享内容与内容分享请求相互独立地发送至服务器。或者，终端可以预先将待分享内容发送至某一存储空间(如服务器维护的存储空间，或者服务器可达的其他存储空间)，并通过内容分享请求指示服务器从该存储空间获得上述的待分享内容。
在一实施例中，分享方用户可以为上述特定组织内的任一成员。换言之，该特定组织内的每个成员均可以作为上述的分享方用户，以针对该特定组织进行内容分享。
在一实施例中，分享方用户可以为上述特定组织内具有分享权限的成员。换言之，该特定组织内的不同成员所具有的权限可以存在差异，使得具有分享权限的这部分成员可以作为上述的分享方用户，以针对该特定组织进行内容分享，而不具有分享权限的其他成员则无法针对该特定组织进行内容分享。例如，该特定组织的成员中可以包括管理员和普通成员，管理员可以具有分享权限，且管理员可以向至少一个普通成员赋予或收回分享权限。再例如，该特定组织存在相应的组织结构，各个成员在该组织结构中处于对应的层级，那么对应层级不低于预设层级的成员可以具有分享权限，而低于该预设层级的成员则不具有分享权限。又例如，该特定组织可以存在相关联的测试任务，成员在完成该测试任务的情况下，可以自动获得分享权限。该特定组织内的成员还可以通过其他方式获得分享权限，本说明书并不对此进行限制。
在一实施例中，服务器将待分享内容发布至特定组织后，通过使得该待分享内容呈现于与该特定组织相关的内容分享界面中，相比于相关技术中在该特定组织对应的关联群组内发布待分享内容，可以在该内容分享界面中对所有被分享的内容进行统一展示，且可以避免所展示的内容被群组成员之间的闲聊内容影响，确保该特征组织的成员能够更为便捷地查看被分享的内容，有助于提升内容的传达效率。
在一实施例中，与特定组织相关的内容分享界面，即该内容分享界面与该特定组织 之间存在预设关联。例如，该特定组织仅存在一个相关的内容分享界面，该内容分享界面对应于整个特定组织，使得任一成员将待分享内容发布至该特定组织(假定该任一成员具有分享权限)时，该待分享内容都被呈现于该内容分享界面。再例如，上述特定组织可以包括子级组织，该特定组织与子级组织之间的关系类似于企业与部门、医院与科室、学校与班级等之间的关系，而上述与特定组织相关的内容分享界面可以包括：对应于特定组织的内容分享总界面、对应于子级组织的内容分享子界面，即内容分享总界面对应于整个特定组织、内容分享子界面对应于子级组织(即整个特定组织的一部分)。特定组织可以包含多个子级组织，各个子级组织之间可以相互独立，也可以存在至少一部分重叠，甚至一些层级较高的子级组织可以完全包含其他的一个或多个层级较低的子级组织；譬如在企业场景下，开发部门对应于一子级组织1，而开发部门下属的软件开发部门对应于一子级组织2、硬件开发部门对应于一子级组织3，那么子级组织1可以认为包含子级组织2和子级组织3，而子级组织2与子级组织3之间相互独立。
在一实施例中，在同时存在上述的内容分享总界面和内容分享子界面的情况下，针对分享方用户所发起的内容分享请求，待分享内容可以被发布至特定组织或特定组织的子级组织，从而呈现于内容分享总界面或内容分享子界面。例如，服务器可以根据分享方用户的权限级别，确定将待分享内容发布至特定组织还是该特定组织的子级组织；其中，在分享方用户的权限级别匹配于特定组织对应的权限等级需求(当然，此时通常也会匹配于子级组织对应的权限等级需求)的情况下，服务器可以默认将待分享内容发布至特定组织、以呈现于内容分享总界面，在分享方用户的权限级别匹配于子级组织(分享方用户可以处于该子级组织，也可以不处于该子级组织)对应的权限等级需求但不匹配于特定组织的情况下，服务器可以默认将待分享内容发布至特定组织的子级组织、以呈现于相应的内容分享子界面。再例如，服务器可以根据分享方用户的配置信息，确定将待分享内容发布至特定组织或该分享方用户所处的子级组织，从而呈现于内容分享总界面或分享方用户所处的子级组织对应的内容分享子界面；换言之，分享方用户的权限级别可能匹配于特定组织对应的权限等级需求，但该分享方用户仍然可以通过设定上述的配置信息，从而将待分享内容发布至该分享方用户所处的子级组织、以呈现于相应的内容分享子界面中，而非发布至该特定组织而呈现于相应的内容分享总界面中。
在一实施例中，上述的内容分享总界面、内容分享子界面存在相应的访问权限，使得仅具有相应访问权限的用户可以进行访问。例如，可以根据用户对特定组织或子级组织的归属情况，确定该用户是否可以访问相应的内容分享界面。其中，内容分享总界面 的访问权限可以被限制为特定组织的所有成员，即由于这些成员归属于特定组织，使得这些成员具有针对该特定组织对应的内容分享总界面的访问权限，而不属于该特定组织的用户则无法访问；内容分享子界面的访问权限可以被限制为相应子级组织的成员，即由于这些成员归属于该子级组织，使得这些成员具有针对该子级组织对应的内容分享子界面的访问权限，而不属于该子级组织的用户即便归属于特定组织也无法访问。当然，还可以通过其他方式确定用户是否具有对相应内容分享界面进行访问的权限。比如，对于上述的子级组织对应的内容分享子界面而言，可以设定为特定组织的所有成员均具有访问权限，本说明书并不对此进行限制。
在一实施例中，服务器可以为上述的特定组织建立关联群组，使群组成员与特定组织的成员一一对应，便于该特定组织的成员基于关联群组进行高效沟通。类似地，对于原本已经存在的群组，服务器也可以针对该群组建立相应的组织。对于特定组织及其关联群组而言，可以在与该特定群组相关的内容分享界面与该关联群组的消息收发界面之间实现互动，以便于成员实现快捷的界面切换。例如，关联群组的消息收发界面中可以包含内容分享界面的访问入口，反之也可以在内容分享界面中添加消息收发界面的访问入口。需要指出的是：关联群组的数量可以为一个，这个关联群组的群组成员为特定组织的所有成员；或者，关联群组的数量可以为多个，特定组织的所有成员分别位于这些关联群组内。
在一实施例中，消息收发界面与内容分享界面归属于同一应用，比如均归属于上述的通讯应用。其中，当终端根据针对消息收发界面中所含访问入口的触发操作，而启动与特定组织相关的内容分享界面时，可能存在多种展示方式。例如：在消息收发界面与内容分享界面完全独立的情况下，终端相当于从消息收发界面跳转至内容分享界面，即终端屏幕上同一时刻仅展示出消息收发界面或内容分享界面；再例如，终端可以在消息收发界面的上方悬浮展示内容分享界面；又例如，终端可以并列展示消息收发界面和内容分享界面。
在一实施例中，针对分享方用户需要分享的待分享内容，除了将其呈现于与特定组织相关的内容分享界面之外，服务器还可以将该待分享内容发送至特定组织的关联群组，使得成员可以选择在内容分享界面或消息收发界面查看该待分享内容，比如原本就位于消息收发界面的成员无需专门切换至内容分享界面、无需在内容分享界面中寻找该待分享内容，即可在消息收发界面快捷地查看该待分享内容的内容。服务器还可以通过其他方式来提升成员对待分享内容的查看便捷度。例如，服务器可以将待分享内容在内容分 享界面内的访问链接发送至特定组织的关联群组，那么虽然成员无法直接在消息收发界面中查看到待分享内容的内容，但是只需要在消息收发界面中触发该访问链接，即可快速跳转和查看该待分享内容的内容，而无需在内容分享界面中寻找该待分享内容。
图5是一示例性实施例提供的另一种终端侧的内容分享方法的流程图。如图5所示，该方法应用于终端(例如图1所示的手机13～15等)，可以包括以下步骤：
步骤502，终端展示本端用户所处群组的消息收发界面，所述群组对应于所述本端用户所处的特定组织。
在一实施例中，本端用户为终端的已登录账号对应的用户。消息收发界面用于本端用户查看所处群组内的其他成员所发送的通讯消息，或者向其他成员发送通讯消息。
在一实施例中，本说明书的特定组织内的成员之间具有相对紧密的相互关系，而区别于相关技术中诸如社区(BBS，Bulletin Board System)、贴吧等场景下的松散关系，使得成员在发布待分享内容时需要针对上述相对紧密的相互关系加以考量，并主动避免发布不恰当的待分享内容，使得成员之间的内容分享相对更加高效、可控。
在一实施例中，上述特定组织内的成员之间满足预定义的用户关系，以体现出上述相对紧密的相互关系。例如，该预定义的用户关系可以包括：归属于同一团体，这里的团体可以理解为企业、医院、学校、部队、政府机关等，或者上述各类团体内的部门等，本说明书并不对此进行限制。再例如，该预定义的用户关系可以包括：参与同一事件，该事件可以包括任务事件、会议事件、诊疗事件、教学事件等。当然，上述用户关系还可以包括其他类型的相对紧密的相互关系，比如成员之间具有好友关系、合作关系等，还可以同时满足上述的多种关系(譬如同时归属于同一团体且参与同一事件，再譬如同时具有合作关系且参与同一事件等)，本说明书并不对此进行限制。
在一实施例中，上述特定组织可以在已有团体的基础上建立。比如，针对已经存在的企业，可以基于服务器所维护的该企业的组织结构建立上述的特定组织，使得企业成员被添加为该特定组织的成员、该特定组织的成员形成的组织结构与该企业内的企业成员形成的组织结构可以相同(也可以存在差异)。例如，上述企业的管理员可以通过向服务器发起组织建立请求，使得服务器可以基于该企业的组织结构建立起上述的特定组织。
在一实施例中，上述特定组织的加入形式可以为邀请制。例如，申请方用户可以向服务器发起针对该特定组织的加入请求，而服务器基于接收到的该加入请求，可以在确定申请方用户为针对该特定组织的成员所发出的加入邀请而发起上述加入请求的情况 下，将该申请方用户添加至该特定组织，否则拒绝添加。换言之，需要由特定组织的成员向申请方用户发出加入邀请后，由该申请方用户针对该加入邀请发起加入请求，服务器才会同意申请方用户的请求、将该申请方用户添加至特定组织，而当申请方用户在未收到加入邀请的情况下直接发出针对该特定组织的加入请求时，服务器将会拒绝该加入请求。
步骤504，所述终端根据针对所述消息收发界面中所含访问入口的触发操作，启动与所述特定组织相关的内容分享界面，所述内容分享界面用于展示来自所述特定组织的成员的分享内容。
在一实施例中，通过在消息收发界面中添加内容分享界面的访问入口，使得上述的本端用户可以通过触发该访问入口的方式，快捷地启动内容分享界面，而无需退出消息收发界面再打开内容分享界面。内容分享界面可以独立于消息收发界面，使得终端响应于针对访问入口的触发操作，可以从消息收发界面切换至内容分享界面。或者，内容分享界面可以采用其他形态，比如位于消息收发界面内的窗口界面；其中，窗口界面的面积通常相对较小、仅占内容收发界面的一部分，以便于本端用户在查看内容分享界面的同时，还可以查看消息收发界面。
在一实施例中，消息收发界面与内容分享界面归属于同一应用，比如均归属于上述的通讯应用。其中，当终端根据针对消息收发界面中所含访问入口的触发操作，而启动与特定组织相关的内容分享界面时，可能存在多种展示方式。例如：在消息收发界面与内容分享界面完全独立的情况下，终端相当于从消息收发界面跳转至内容分享界面，即终端屏幕上同一时刻仅展示出消息收发界面或内容分享界面；再例如，终端可以在消息收发界面的上方悬浮展示内容分享界面；又例如，终端可以并列展示消息收发界面和内容分享界面。
在一实施例中，终端可以在上述访问入口的展示区域中展示提醒信息，该提醒信息用于表明内容分享界面中存在未读分享内容和/或未读互动内容。未读分享内容为内容分享界面中处于未读状态的分享内容。未读互动内容为内容分享界面中处于未读状态的互动内容，互动内容由其他用户发送至本端用户，以实现其他用户与本端用户之间的互动，譬如互动内容可以包括评论内容、评论回复内容、私信内容、点赞内容等。提醒信息可以具有多种形式，以满足不同需求下的提醒效果；例如提醒信息可以包括一提醒标识(譬如一红色圆点)，本端用户可以据此确定上述未读分享内容和/或未读互动内容的存在与否(出现提醒标识表明存在，未出现提醒标识则表明不存在)，再例如提醒信息可以包 括提醒数值，该提醒数值为未读分享内容和/或未读互动内容的数量，本端用户可以据此确定上述未读分享内容和/或未读互动内容的存在与否、数量多少(出现提醒数值表明存在且提醒数值即为内容数量，未出现提醒数值则表明不存在)。
在一实施例中，通过将待分享内容展示于与该特定组织相关的内容分享界面中，相比于相关技术中在该特定组织对应的关联群组内发布待分享内容，可以在该内容分享界面中对所有被分享的内容进行统一展示，且可以避免所展示的内容被群组成员之间的闲聊内容影响，确保该特征组织的成员能够更为便捷地查看被分享的内容，有助于提升内容的传达效率。
在一实施例中，与特定组织相关的内容分享界面，即该内容分享界面与该特定组织之间存在预设关联。例如，该特定组织仅存在一个相关的内容分享界面，该内容分享界面对应于整个特定组织，使得任一成员将待分享内容发布至该特定组织(假定该任一成员具有分享权限)时，该待分享内容都被呈现于该内容分享界面。再例如，上述特定组织可以包括子级组织，该特定组织与子级组织之间的关系类似于企业与部门、医院与科室、学校与班级等之间的关系，而上述与特定组织相关的内容分享界面可以包括：对应于特定组织的内容分享总界面、对应于子级组织的内容分享子界面，即内容分享总界面对应于整个特定组织、内容分享子界面对应于子级组织(即整个特定组织的一部分)。特定组织可以包含多个子级组织，各个子级组织之间可以相互独立，也可以存在至少一部分重叠，甚至一些层级较高的子级组织可以完全包含其他的一个或多个层级较低的子级组织；譬如在企业场景下，开发部门对应于一子级组织1，而开发部门下属的软件开发部门对应于一子级组织2、硬件开发部门对应于一子级组织3，那么子级组织1可以认为包含子级组织2和子级组织3，而子级组织2与子级组织3之间相互独立。
在一实施例中，在同时存在上述的内容分享总界面和内容分享子界面的情况下，针对分享方用户所发起的内容分享请求，待分享内容可以被发布至特定组织或特定组织的子级组织，从而呈现于内容分享总界面或内容分享子界面。例如，服务器可以根据分享方用户的权限级别，确定将待分享内容发布至特定组织还是该特定组织的子级组织；其中，在分享方用户的权限级别匹配于特定组织对应的权限等级需求(当然，此时通常也会匹配于子级组织对应的权限等级需求)的情况下，服务器可以默认将待分享内容发布至特定组织、以呈现于内容分享总界面，在分享方用户的权限级别匹配于子级组织(分享方用户可以处于该子级组织，也可以不处于该子级组织)对应的权限等级需求但不匹配于特定组织的情况下，服务器可以默认将待分享内容发布至特定组织的子级组织、以 呈现于相应的内容分享子界面。再例如，服务器可以根据分享方用户的配置信息，确定将待分享内容发布至特定组织或该分享方用户所处的子级组织，从而呈现于内容分享总界面或分享方用户所处的子级组织对应的内容分享子界面；换言之，分享方用户的权限级别可能匹配于特定组织对应的权限等级需求，但该分享方用户仍然可以通过设定上述的配置信息，从而将待分享内容发布至该分享方用户所处的子级组织、以呈现于相应的内容分享子界面中，而非发布至该特定组织而呈现于相应的内容分享总界面中。
在一实施例中，上述的内容分享总界面、内容分享子界面存在相应的访问权限，使得仅具有相应访问权限的用户可以进行访问。例如，可以根据用户对特定组织或子级组织的归属情况，确定该用户是否可以访问相应的内容分享界面。其中，内容分享总界面的访问权限可以被限制为特定组织的所有成员，即由于这些成员归属于特定组织，使得这些成员具有针对该特定组织对应的内容分享总界面的访问权限，而不属于该特定组织的用户则无法访问；内容分享子界面的访问权限可以被限制为相应子级组织的成员，即由于这些成员归属于该子级组织，使得这些成员具有针对该子级组织对应的内容分享子界面的访问权限，而不属于该子级组织的用户即便归属于特定组织也无法访问。当然，还可以通过其他方式确定用户是否具有对相应内容分享界面进行访问的权限。比如，对于上述的子级组织对应的内容分享子界面而言，可以设定为特定组织的所有成员均具有访问权限，本说明书并不对此进行限制。
在一实施例中，在内容被分享至特定组织的情况下，除了将其呈现于与特定组织相关的内容分享界面之外，终端还可以接收服务器发送至上述消息收发界面中的该内容，使得本端用户可以选择在内容分享界面或消息收发界面查看该待分享内容，比如本端用户原本就位于消息收发界面则无需专门切换至内容分享界面、无需在内容分享界面中寻找该待分享内容，即可在消息收发界面快捷地查看该待分享内容的内容。或者，终端还可以接收服务器发送至上述消息收发界面中的上述内容在内容分享界面内的访问链接，那么虽然本端用户无法直接在消息收发界面中查看到待分享内容的内容，但是只需要在消息收发界面中触发该访问链接，即可快速跳转和查看该待分享内容的内容，而无需在内容分享界面中寻找该待分享内容。
下面以某一应用T为例，对本说明书的内容分享方案进行示例性描述。
通过在服务器上运行该应用T的服务器侧程序、在终端上运行该应用T的终端侧程序，可使服务器被配置为该应用T的服务端、终端被配置为该应用T的客户端，从而由服务端与客户端之间进行配合，以实现本说明书的内容分享方案。
针对本说明书的内容分享方案，应用T可以提供一内容分享功能，譬如该内容分享功能可以称之为“小圈子”。图6是一示例性实施例提供的一种内容分享界面的示意图。如图6所示，应用T所提供的小圈子功能可以包含内容分享界面60，使得分享内容可以被呈现于该内容分享界面60中。
内容分享界面60可以包括概要信息展示区域610，以用于展示与内容分享界面60相关的概要信息，比如概要信息可以包括：内容分享界面60对应组织的名称为“电商干货分享”、内容分享界面60中的分享内容(动态)的数量为29384条、上述组织“电商干货分享”所含成员的数量为82892人。
内容分享界面60可以包括关键成员介绍区域620，以用于展示组织内的关键成员的信息。例如，关键成员可以包括“圈主”，相当于上述组织的管理员。再例如，关键成员可以包括知名用户，比如组织“电商干货分享”中的知名用户可以包括“知名电商导师”等。通过对关键成员的信息展示，可以帮助未加入该组织的用户通过这些关键成员的信息而快速了解该组织的相关情况，从而引导或吸引这些用户加入该组织。
内容分享界面60可以包括群聊入口展示区域630，以针对上述组织的关联群组的消息收发界面(即群聊界面)展示出相应的访问入口。例如，上述组织“电商干货分享”的关联群组可以包括“电商学习班1”、“电商学习班2”等。由于群聊入口展示区域630的面积有限，因而通常只能够展示出部分关联群组对应的访问入口，而其他关联群组的相关信息和访问入口等，可以通过触发群聊入口展示区域630中的“查看全部”选项进行查看。
内容分享界面60可以包括必看信息展示区域640，以用于展示重要程度最高的分享信息，即必看信息。例如，必看信息展示区域640可以包括“干货文章目录汇总+链接”等。类似地，由于必看信息展示区域640的面积有限，因而通常只能够展示出部分必看信息，而其他必看信息可以通过触发必看信息展示区域640中的“查看全部”选项进行查看。
内容分享界面60可以包括置顶信息展示区域650，以用于展示重要程度相对较高(但低于必看信息)的分享信息，即置顶信息。例如，置顶信息展示区域650可以包括“专栏干货目录汇总+链接”、“流量对一个店铺来说非常重要，…”等。类似地，由于置顶信息展示区域650的面积有限，因而通常只能够展示出部分置顶信息，而其他置顶信息可以通过触发置顶信息展示区域650中的“查看全部”选项进行查看。
内容分享界面60的剩余区域可以用于展示上述组织“电商干货分享”中已存在的分 享内容，譬如以列表的形式对这些分享内容进行倒序展示，以便于用户优先查看到最近发布的分享内容。例如图6所示，内容分享界面60中包含分享内容660。分享内容660可以包括内容分享方的信息(如头像、名称等)、所分享的内容、针对该内容的互动信息(如转发数量、评论数量、点赞数量、评论信息、评论回复信息等)等内容。如果分享内容660被设定(圈主发布的内容被系统默认为必看或置顶，或者由圈主或其他具有管理权限的用户主动进行设定)为必看内容或置顶内容，可以添加相应标记予以表征，比如图6中针对分享内容660示出了“置顶”标签。若存在多条评论信息、评论回复信息等，这些信息可以按照发布时刻进行排列，譬如按照发布时刻进行倒序排列，以便于用户优先查看到最近发布的信息。
内容分享界面60可以包括类型选择区域670，以便于用户对所示出的分享内容进行快捷筛选。例如，图6中的类型选择区域670中示出了“全部”、“精华”、“直播视频”、“运营工具”等类型选项，使得用户可以通过选择一个或多个类型选项，以使得内容分享界面60中仅示出这部分类型的分享内容，便于用户进行查看。相应地，对于组织“电商干货分享”内所发布的分享内容，应当被添加有相应的类型标签，以便于通过类型标签与类型选项之间的匹配实现筛选展示。
如前所述，组织“电商干货分享”可以存在一个或多个关联群组，譬如群聊入口展示区域630中的“电商学习班1”、“电商学习班2”等。当检测到用户触发某一群聊入口时，可以快捷切换至相应的群聊界面。当然，该用户应当为相应的关联群组的成员，才能够确保顺利实现切换，否则可以先触发将该用户添加为群组成员的处理流程。
类似地，用户可以从关联群组的群聊界面快捷地访问内容分享界面60。例如，图7是一示例性实施例提供的一种群聊界面的示意图。如图7所示，在关联群组“电商学习班1”对应的群聊界面70中，可以包含针对上述内容分享界面60的访问入口710。因此，当用户在群聊界面70中收发群聊消息时，可以通过触发访问入口710的方式，从群聊界面70快速跳转至内容分享界面60。
在内容分享界面60中存在未读的分享内容或互动内容(或者两者均有)的情况下，可以在访问入口710的左上角(也可以是与该访问入口710相关的其他位置或区域)示出一提醒标识711，譬如该提醒标识711可以为一圆点。因此，即便用户位于群聊界面70的情况下，仍然可以基于该提醒标识711快速确定内容分享界面60中存在未读的分享内容和/或互动内容。
提醒标识711还可以变换为其他形式。例如，图8是一示例性实施例提供的另一种 群聊界面的示意图。如图8所示，在内容分享界面60中存在未读的分享内容或互动内容(或者两者均有)的情况下，可以在访问入口710的左上角(也可以是与该访问入口710相关的其他位置或区域)示出一数字标识712，使得即便用户位于群聊界面70的情况下，仍然可以基于该数字标识712快速确定内容分享界面60中存在未读的分享内容和/或互动内容。其中，当数字标识712包含数字9时，表明内容分享界面60中未读的分享内容和/或互动内容的数量为9条。
图9是一示例性实施例提供的另一种内容分享界面的示意图。基于用户针对上述数字标识712的触发操作，可由图8所示的群聊界面70切换至如图9所示的内容分享界面90，该内容分享界面90所含的内容与前述的内容分享界面60类似。对应于上述的数字标识712，内容分享界面90中可以包含如图9所示的内容查看入口910，使得用户可以通过触发该内容查看入口910的方式，查看相应的9条新内容，即前述未读的分享内容和/或互动内容。
虽然上述实施例中，介绍了诸如内容分享界面60所含的内容，以及内容分享界面60与群聊界面70之间的快捷切换，但是用户可能需要预先加入组织“电商干货分享”。例如，用户可能需要加入该组织“电商干货分享”后，才能够在内容分享界面60中查看到诸如图6所示的所有内容，否则仅能够查看到部分内容，譬如仅限于概要信息展示区域610、关键成员介绍区域620、群聊入口展示区域630等，而无法查看到其他内容。或者，虽然能够查看内容分享界面60的所有内容，但无法发布内容(即无法实施内容分享)；相应地，在用户加入该组织“电商干货分享”后，内容分享界面90中可以包含如图9所示的内容发布选项920，使得用户可以通过触发该内容发布选项920来发布内容，实现内容分享。内容发布选项920可以悬浮于内容分享界面90中，并且用户在翻动内容分享界面90的过程中，该内容发布选项920在设备屏幕上的位置不变，使得用户可以随时便捷地针对该内容发布选项920实施触发操作。
某一分享内容被用户发布至组织“电商干货分享”后，该分享内容除了被展示于上述的内容分享界面90(或内容分享界面60)之外，还可以被推送至相应的关联群组。例如，图10是一示例性实施例提供的一种在群聊界面推送分享内容的示意图。组织“电商干货分享”可以存在一关联群组“电商学习班1”，若用户“小白”在该组织“电商干货分享”发布了一条动态，即发布了一条分享内容，则该分享内容可以被自动推送至如图10所示的群聊界面1000，以便于群组成员在群聊界面1000中查看相应的内容1010。在图10所示的实施例中，内容1010被展示于群聊界面1000顶部的悬浮窗口中，使得该 内容1010可以悬浮展示于群聊界面1000内的群聊消息的上层，避免群聊消息对内容1010造成遮挡或淹没。
如果内容1010的信息量较大，可能无法完整地显示在如图10所示的悬浮窗口中，那么可以仅在悬浮窗口中从前向后地显示部分内容，而用户可以通过触发该内容1010并跳转至该内容1010在内容分享界面90内的展示页面，以便于用户完整地查看内容1010，且无需用户主动在内容分享界面90中寻找该内容1010。悬浮窗口中还可以示出用户对相关分享内容的读取状态，比如“已读”、“未读”等。
图11是一示例性实施例提供的另一种在群聊界面推送分享内容的示意图。若用户“小白”在该组织“电商干货分享”发布了一条动态，即发布了一条分享内容，则该分享内容可以被自动推送至如图11所示的群聊界面1100，且该分享内容将以通讯消息1110的形式展示于该群聊界面1100中，以便于其他群组成员查看。与图10所示实施例类似地，如果分享内容的信息量较大，可能无法完整地显示在通讯消息1110的展示区域中，那么可以仅在该展示区域中从前向后地显示部分内容，而用户可以通过触发该通讯消息1110并跳转至上述分享内容在内容分享界面90内的展示页面，以便于用户完整地查看该分享内容，且无需用户主动在内容分享界面90中寻找该分享内容。
图12-图13是一示例性实施例提供的一种访问内容分享界面的示意图。如图12所示，应用T可以向用户提供独立于关联群组的访问入口1210，以使得用户基于该访问入口1210对自身所加入组织的内容分享界面进行访问，比如基于该访问入口1210访问前述的内容分享界面90等。应用T可以包括如图12底部所示的标签栏，用户可以通过触发该标签栏所含的“消息”、“DING”、“工作”、“联系人”。“我的”等标签，在相应的标签页之间进行切换。举例而言，在“我的”标签页被触发的情况下，可以示出如图12所示的功能界面1200。
假定用户仅加入了上述的组织“电商干货分享”，则该用户可以通过触发如图12所示的访问入口1200，直接跳转至如图9所示的内容分享界面90；而如果该用户同时加入了多个组织，则该用户可以通过触发如图12所示的访问入口1210，跳转至如图13所示的组织管理界面1300，该组织管理界面1300包含该用户已加入的所有组织对应的访问入口，使得用户可以通过选择和触发某一访问入口，以直接跳转至对应的内容分享界面。
与前述图7-图8所示实施例相类似的，访问入口1210处可以示出提醒标识1211，以表明用户所加入的组织内存在未读的分享内容和/或互动内容。而在用户进一步进入图13所示的组织管理界面1300后，可以在组织对应的访问入口上示出数字标识，比如组 织“电商干货分享”对应的数字标识1310表明存在9条未读的分享内容和/或互动内容，再比如组织“广告人不哭”对应的数字标识1320表明存在3条未读的分享内容和/或互动内容。
用户可以通过多种方式加入上述的组织。例如在图6所示的实施例中，概要信息展示区域610中可以包含申请选项611，用户可以通过触发该申请选项611，以请求加入组织“电商干货分享”。根据预先定义的权限规则，用户可以免审核地直接加入该组织“电商干货分享”，或者用户需要在诸如圈主等具有管理权限的成员审核通过后加入该组织“电商干货分享”等。
用户可能需要首先加入某一关联群组后才能够触发申请选项611，否则无法触发申请选项611，甚至可能无法查看到内容分享界面60。那么，可以针对用户加入关联群组的过程进行管理，比如当关联群组为某一企业的内部群组时，该用户必须位于或被添加至该企业的组织结构中，否则无法加入该关联群组，从而确保该关联群组的成员之间具有紧密关联，避免无关人员随意加入关联群组和相应的组织。
组织的成员扩展可以采用邀请制。例如，图14-图15是一示例性实施例提供的一种邀请用户加入组织的示意图。如图14所示，组织“电商干货分享”的圈主为用户“小白”，应用T向该用户“小白”呈现的浏览内容分享界面1400中可以包括邀请选项1410。通过触发邀请选项1410，用户“小白”可以选取自身的一个或多个关联用户，并邀请且加入组织“电商干货分享”，此处的关联用户可以包括用户“小白”在应用T中的好友、终端本地的联系人、所属群组中的成员、所属企业中的成员等，本说明书并不对此进行限制。
假定用户“小红”被用户“小白”选中，该用户“小红”可以通过如图15所示的单聊界面1500接收到用户“小白”发送的邀请消息1510，使得该用户“小红”可以选择该邀请消息1510所含的“立即加入”或“算了”，以接受或拒绝邀请。或者，邀请消息1510可以不含选项，而是可以链接至如图6所示的内容分享界面60，使得用户“小红”可以在浏览内容分享界面60的过程中，基于申请选项611加入组织“电商干货分享”。
综上所述，本说明书提供了高效、便捷的内容分享方案，可使加入同一组织的成员之间实现内容分享。相比于相关技术中的社区、贴吧等，本说明书中的组织成员之间具有相对更加紧密的关联，比如上述实施例中的组织“电商干货分享”应用于电商场景下，便于电子商务平台的运营人员对数量众多、类型众多的商家提供内容分享功能，比如不同类型的商家可能分别位于不同的群组中，那么上述运营人员只需要将这些群组都关联 至组织“电商干货分享”，即可针对该组织“电商干货分享”发布分享内容，而上述群组中的商家都可以通过内容分享界面查看到该分享内容，而无需运营人员加入所有群组、在每个群组中一一发送分享内容。
当然，除了上述的电商场景之外，本说明书的内容分享方案还可以应用于很多其他场景，比如企业集团的内部赋能、教育培训、企业服务、公众号和品牌运营、社会组织(如商会或大会)、政府机关、公安、部队、连锁企业、加盟商、渠道商、医院、粉丝群、兴趣群等，本说明书并不对此进行限制。
除了上述的圈主之外，组织内还可以存在其他具有管理权限的成员。例如，圈主可以向组织内的一个或多个成员赋予管理权限。如果将所有具备管理权限的成员均称为管理员，那么不同管理员可以具有差异化的管理权限；例如，组织内仅有管理员能够在内容分享界面内发布分享内容，且不同管理员由于管理权限的差异，使其仅能够发布自身管理权限对应类型的分享内容。
图16是一示例性实施例提供的一种设备的示意结构图。请参考图16，在硬件层面，该设备包括处理器1602、内部总线1604、网络接口1606、内存1608以及非易失性存储器1610，当然还可能包括其他业务所需要的硬件。处理器1602从非易失性存储器1610中读取对应的计算机程序到内存1608中然后运行，在逻辑层面上形成内容分享装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图17，在软件实施方式中，该内容分享装置可以包括：
请求接收单元1701，使服务器接收分享方用户发起的内容分享请求，所述内容分享请求用于将所述分享方用户提交的待分享内容在所述分享方用户所处的特定组织内进行分享；
内容发布单元1702，使所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
可选的，所述分享方用户为所述特定组织内的任一成员；或者，所述分享方用户为所述特定组织内具有分享权限的成员。
可选的，所述特定组织内的成员之间满足预定义的用户关系。
可选的，所述预定义的用户关系包括：归属于同一团体和/或参与同一事件。
可选的，所述特定组织存在对应的关联群组；所述装置还包括：
组织建立单元1703，使所述服务器针对所述关联群组建立所述特定组织，使群组成员与所述特定组织的成员一一对应。
可选的，所述关联群组的消息收发界面中包含所述内容分享界面的访问入口。
可选的，还包括：
内容发送单元1704，使所述服务器将所述待分享内容和/或所述待分享内容在所述内容分享界面内的访问链接发送至所述特定组织的关联群组。
可选的，还包括：
接收单元1705，使所述服务器接收到申请方用户针对所述特定组织的加入请求；
响应单元1706，使所述服务器在确定所述申请方用户为针对所述特定组织的成员所发出的加入邀请而发起所述加入请求的情况下，将所述申请方用户添加至所述特定组织，否则拒绝添加。
可选的，所述特定组织包括子级组织；所述内容分享界面包括：对应于所述特定组织的内容分享总界面、对应于所述子级组织的内容分享子界面。
所述内容发布单元1702具体用于：
使所述服务器根据所述分享方用户的权限级别，将所述待分享内容发布至所述特定组织或所述特定组织的子级组织，使所述待分享内容被呈现于所述内容分享总界面或所述内容分享子界面；或者，
使所述服务器根据所述分享方用户的配置信息，将所述待分享内容发布至所述特定组织或所述分享方用户所处的子级组织，使所述待分享内容被呈现于所述内容分享总界面或所述分享方用户所处的子级组织对应的内容分享子界面。
可选的，
所述内容分享总界面的访问权限被限制为所述特定组织的所有成员；
所述内容分享子界面的访问权限被限制为所述特定组织的所有成员或相应子级组织的成员。
可选的，所述服务器通过运行即时通讯应用的服务端程序，以实现所述内容分享方法。
图18是一示例性实施例提供的一种设备的示意结构图。请参考图18，在硬件层面，该设备包括处理器1802、内部总线1804、网络接口1806、内存1808以及非易失性存储器1810，当然还可能包括其他业务所需要的硬件。处理器1802从非易失性存储器1810中读取对应的计算机程序到内存1808中然后运行，在逻辑层面上形成内容分享装置。当 然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图19，在软件实施方式中，该内容分享装置可以包括：
请求接收单元1901，使服务器接收分享方用户发起的内容分享请求；
内容发布单元1902，使所述服务器将所述分享方用户提供的待分享内容发布至特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
图20是一示例性实施例提供的一种设备的示意结构图。请参考图20，在硬件层面，该设备包括处理器2002、内部总线2004、网络接口2006、内存2008以及非易失性存储器2010，当然还可能包括其他业务所需要的硬件。处理器2002从非易失性存储器2010中读取对应的计算机程序到内存2008中然后运行，在逻辑层面上形成内容分享装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图21，在软件实施方式中，该内容分享装置可以包括：
确定单元2101，使终端确定分享方用户提供的待分享内容和所述分享方用户所处的特定组织；
请求单元2102，使所述终端向服务器发起内容分享请求，使所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
图22是一示例性实施例提供的一种设备的示意结构图。请参考图22，在硬件层面，该设备包括处理器2202、内部总线2204、网络接口2206、内存2208以及非易失性存储器2210，当然还可能包括其他业务所需要的硬件。处理器2202从非易失性存储器2210中读取对应的计算机程序到内存2208中然后运行，在逻辑层面上形成内容分享装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图23，在软件实施方式中，该内容分享装置可以包括：
群组界面展示单元2301，使终端展示本端用户所处群组的消息收发界面，所述群组对应于所述本端用户所处的特定组织；
分享界面展示单元2302，使所述终端根据针对所述消息收发界面中所含访问入口的触发操作，启动与所述特定组织相关的内容分享界面，所述内容分享界面用于展示来自所述特定组织的成员的分享内容。
可选的，还包括：
提醒信息展示单元2303，使所述终端在所述访问入口的展示区域中展示提醒信息，所述提醒信息用于表明所述内容分享界面中存在未读分享内容和/或未读互动内容。
可选的，所述内容分享界面与所述消息收发界面归属于同一应用。
可选的，所述分享界面展示单元2302具体用于：
使所述终端从所述消息收发界面跳转至所述内容分享界面；
或者，使所述终端在所述消息收发界面的上方悬浮展示所述内容分享界面；
或者，使所述终端并列展示所述消息收发界面和所述内容分享界面。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带、磁盘存储、量子存储器、基于石墨烯的存储介质或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在本说明书一个或多个实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本说明书一个或多个实施例的较佳实施例而已，并不用以限制本说明书一个或多个实施例，凡在本说明书一个或多个实施例的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本说明书一个或多个实施例保护的范围之内。

Claims (26)

  1. 一种内容分享方法，其特征在于，包括：
    服务器接收分享方用户发起的内容分享请求，所述内容分享请求用于将所述分享方用户提交的待分享内容在所述分享方用户所处的特定组织内进行分享；
    所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
  2. 根据权利要求1所述的方法，其特征在于，所述分享方用户为所述特定组织内的任一成员；或者，所述分享方用户为所述特定组织内具有分享权限的成员。
  3. 根据权利要求1所述的方法，其特征在于，所述特定组织内的成员之间满足预定义的用户关系。
  4. 根据权利要求3所述的方法，其特征在于，所述预定义的用户关系包括：归属于同一团体和/或参与同一事件。
  5. 根据权利要求1所述的方法，其特征在于，所述特定组织存在对应的关联群组；所述方法还包括：
    所述服务器针对所述关联群组建立所述特定组织，使群组成员与所述特定组织的成员一一对应。
  6. 根据权利要求5所述的方法，其特征在于，所述关联群组的内容收发界面中包含所述内容分享界面的访问入口。
  7. 根据权利要求5所述的方法，其特征在于，还包括：
    所述服务器将所述待分享内容和/或所述待分享内容在所述内容分享界面内的访问链接发送至所述特定组织的关联群组。
  8. 根据权利要求1所述的方法，其特征在于，还包括：
    所述服务器接收到申请方用户针对所述特定组织的加入请求；
    所述服务器在确定所述申请方用户为针对所述特定组织的成员所发出的加入邀请而发起所述加入请求的情况下，将所述申请方用户添加至所述特定组织，否则拒绝添加。
  9. 根据权利要求1所述的方法，其特征在于，所述特定组织包括子级组织；所述内容分享界面包括：对应于所述特定组织的内容分享总界面、对应于所述子级组织的内容分享子界面。
  10. 根据权利要求9所述的方法，其特征在于，所述服务器将所述待分享内容发布至所述特定组织，包括：
    所述服务器根据所述分享方用户的权限级别，将所述待分享内容发布至所述特定组织或所述特定组织的子级组织，使所述待分享内容被呈现于所述内容分享总界面或所述内容分享子界面；或者，
    所述服务器根据所述分享方用户的配置信息，将所述待分享内容发布至所述特定组织或所述分享方用户所处的子级组织，使所述待分享内容被呈现于所述内容分享总界面或所述分享方用户所处的子级组织对应的内容分享子界面。
  11. 根据权利要求9所述的方法，其特征在于，
    所述内容分享总界面的访问权限被限制为所述特定组织的所有成员；
    所述内容分享子界面的访问权限被限制为所述特定组织的所有成员或相应子级组织的成员。
  12. 根据权利要求1所述的方法，其特征在于，所述服务器通过运行即时通讯应用的服务端程序，以实现所述内容分享方法。
  13. 一种内容分享方法，其特征在于，包括：
    服务器接收分享方用户发起的内容分享请求；
    所述服务器将所述分享方用户提供的待分享内容发布至特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
  14. 一种内容分享方法，其特征在于，包括：
    终端确定分享方用户提供的待分享内容和所述分享方用户所处的特定组织；
    所述终端向服务器发起内容分享请求，使所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
  15. 一种内容分享方法，其特征在于，包括：
    终端展示本端用户所处群组的消息收发界面，所述群组对应于所述本端用户所处的特定组织；
    所述终端根据针对所述消息收发界面中所含访问入口的触发操作，启动与所述特定组织相关的内容分享界面，所述内容分享界面用于展示来自所述特定组织的成员的分享内容。
  16. 根据权利要求15所述的方法，其特征在于，还包括：
    所述终端在所述访问入口的展示区域中展示提醒信息，所述提醒信息用于表明所述内容分享界面中存在未读分享内容和/或未读互动内容。
  17. 根据权利要求15所述的方法，其特征在于，所述内容分享界面与所述消息收发 界面归属于同一应用。
  18. 根据权利要求15所述的方法，其特征在于，所述终端启动与所述特定组织相关的内容分享界面，包括：
    所述终端从所述消息收发界面跳转至所述内容分享界面；
    或者，所述终端在所述消息收发界面的上方悬浮展示所述内容分享界面；
    或者，所述终端并列展示所述消息收发界面和所述内容分享界面。
  19. 一种内容分享装置，其特征在于，包括：
    请求接收单元，使服务器接收分享方用户发起的内容分享请求，所述内容分享请求用于将所述分享方用户提交的待分享内容在所述分享方用户所处的特定组织内进行分享；
    内容发布单元，使所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
  20. 一种内容分享装置，其特征在于，包括：
    请求接收单元，使服务器接收分享方用户发起的内容分享请求；
    内容发布单元，使所述服务器将所述分享方用户提供的待分享内容发布至特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
  21. 一种内容分享装置，其特征在于，包括：
    确定单元，使终端确定分享方用户提供的待分享内容和所述分享方用户所处的特定组织；
    请求单元，使所述终端向服务器发起内容分享请求，使所述服务器将所述待分享内容发布至所述特定组织，使所述待分享内容被呈现于与所述特定组织相关的内容分享界面。
  22. 一种内容分享装置，其特征在于，包括：
    群组界面展示单元，使终端展示本端用户所处群组的消息收发界面，所述群组对应于所述本端用户所处的特定组织；
    分享界面展示单元，使所述终端根据针对所述消息收发界面中所含访问入口的触发操作，启动与所述特定组织相关的内容分享界面，所述内容分享界面用于展示来自所述特定组织的成员的分享内容。
  23. 一种电子设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器通过运行所述可执行指令以实现如权利要求1-13中任一项所述的方法。
  24. 一种计算机可读存储介质，其上存储有计算机指令，其特征在于，该指令被处理器执行时实现如权利要求1-13中任一项所述方法的步骤。
  25. 一种电子设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器通过运行所述可执行指令以实现如权利要求14-18中任一项所述的方法。
  26. 一种计算机可读存储介质，其上存储有计算机指令，其特征在于，该指令被处理器执行时实现如权利要求14-18中任一项所述方法的步骤。
PCT/CN2020/118652 2019-10-09 2020-09-29 内容分享方法及装置 WO2021068789A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2022521529A JP7379688B2 (ja) 2019-10-09 2020-09-29 コンテンツ共有方法及び装置
US17/717,004 US20220239986A1 (en) 2019-10-09 2022-04-08 Content sharing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910954054.4 2019-10-09
CN201910954054.4A CN112636936A (zh) 2019-10-09 2019-10-09 内容分享方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/717,004 Continuation US20220239986A1 (en) 2019-10-09 2022-04-08 Content sharing method and apparatus

Publications (1)

Publication Number Publication Date
WO2021068789A1 true WO2021068789A1 (zh) 2021-04-15

Family

ID=75283548

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/118652 WO2021068789A1 (zh) 2019-10-09 2020-09-29 内容分享方法及装置

Country Status (4)

Country Link
US (1) US20220239986A1 (zh)
JP (1) JP7379688B2 (zh)
CN (1) CN112636936A (zh)
WO (1) WO2021068789A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113392322A (zh) * 2021-06-08 2021-09-14 深圳市小铭工业互联网有限公司 一种基于流程的结构化多元即时通信系统及聊天方法
CN113746722B (zh) * 2021-08-25 2022-08-26 北京字跳网络技术有限公司 信息处理方法、装置、设备以及存储介质
CN115987539A (zh) * 2022-05-09 2023-04-18 阿尔特汽车技术股份有限公司 一种群组分享车辆控制权限的方法
JP2024029839A (ja) * 2022-08-23 2024-03-07 キヤノン株式会社 スキャン装置、画像処理方法及びプログラム

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080133776A1 (en) * 2006-12-05 2008-06-05 Samsung Electronics Co., Ltd Discovery apparatus and method
CN104023069A (zh) * 2014-06-13 2014-09-03 可牛网络技术（北京）有限公司 一种信息分享方法和设备
CN104202357A (zh) * 2014-08-08 2014-12-10 深信服网络科技（深圳）有限公司 内容分享方法和系统
CN109521918A (zh) * 2018-10-15 2019-03-26 北京达佳互联信息技术有限公司 一种信息分享方法、装置、电子设备及存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003085090A (ja) 2001-09-07 2003-03-20 Fuji Electric Co Ltd 情報共有システム
JP2014071874A (ja) 2012-10-02 2014-04-21 Sharp Corp 管理サーバ装置、参加登録システム、参加登録方法、参加登録プログラム
CN102891897B (zh) * 2012-10-30 2016-12-21 北京奇虎科技有限公司 网页分享方法和服务器及客户端
US10346378B1 (en) * 2018-11-30 2019-07-09 Slack Technologies, Inc. Data storage architecture for an enterprise communication system
CN110321036A (zh) * 2019-04-25 2019-10-11 维沃移动通信有限公司 一种通信方法、终端及计算机可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080133776A1 (en) * 2006-12-05 2008-06-05 Samsung Electronics Co., Ltd Discovery apparatus and method
CN104023069A (zh) * 2014-06-13 2014-09-03 可牛网络技术（北京）有限公司 一种信息分享方法和设备
CN104202357A (zh) * 2014-08-08 2014-12-10 深信服网络科技（深圳）有限公司 内容分享方法和系统
CN109521918A (zh) * 2018-10-15 2019-03-26 北京达佳互联信息技术有限公司 一种信息分享方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
JP2022541686A (ja) 2022-09-26
JP7379688B2 (ja) 2023-11-14
CN112636936A (zh) 2021-04-09
US20220239986A1 (en) 2022-07-28

Similar Documents

Publication Publication Date Title
WO2021068789A1 (zh) 内容分享方法及装置
Brandtzæg et al. Too many Facebook “friends”? Content sharing and sociability versus the need for privacy in social network sites
WO2020135142A1 (zh) 项目群组的创建方法、项目管理方法及装置
US9325752B2 (en) Private interaction hubs
CN108632127A (zh) 会话筛选方法及装置
TW201918946A (zh) 變更群組類型的方法、群組創建方法及裝置
Maxwell et al. Stakeholder communication in service implementation networks: expanding relationship management theory to the nonprofit sector through organizational network analysis
TW201828170A (zh) 團體資訊的獲取方法及裝置、互動系統
US20180069906A1 (en) Method and system for private communication with multiple parties
US20150081787A1 (en) System and method for tagging images in a social network
US20210097496A1 (en) Method and Apparatus for Managing Resume Information, and Method and Apparatus for Managing Recruitment Information
WO2019062587A1 (zh) 任务生成方法及装置
US9939994B2 (en) Tracking and managing items in a collaborative exchange
Johnson Corporate strategy and the social networking phenomena
Naik Organizational use of social media: The shift in communication, collaboration and decision-making
TW202116044A (zh) 內容分享方法及裝置
KR20150145896A (ko) 폐쇄형 개인정보 보호서비스 시스템 및 방법
WO2017141126A1 (en) A system and method for providing social association tags in social network application
van der Sanden et al. Social Supply and the Potential for Harm Reduction in Social Media Drug Markets
Lips et al. Kiwis managing their online identity information
Crager et al. Facebook All-in-one for Dummies
Dyak How to Use Social Media & Virtual Meetings to Improve Your Board's Governance
Nelson et al. Facebook All-in-one for Dummies
Al-Sabaawi The comparative analysis of social network in international and local corporate business
Alobaidi A study of outline to the advantages and disadvantages of social media

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: 20873448

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022521529

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20873448

Country of ref document: EP

Kind code of ref document: A1