Extended domain platform for non-member user account management

Abstract

An apparatus comprising: a processor and a memory, wherein the memory includes executable instructions to: detect that a first user has invited a second user to a communication session, wherein the first user is associated with a first user account registered to a first domain platform and the second user is not associated with any of the user accounts registered to the first domain platform, the first domain platform defining first user permissions granted to the user accounts registered to the first domain platform; cause a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to user accounts registered to the second domain platform; and grant the second user permissions to the second user account.

Description

Background Technology

[0001] More and more people use messaging apps (such as Facebook) every day. TM Messenger TM Discord TM iMessage TM Kakao Talk TM Line TM Skype TM Snapchat TM Telegram TM Viber TM WeChat TM WhatsApp TM Slack TM Microsoft Teams TM (etc.) for personal and commercial purposes. While most messaging applications are developed and marketed to individual consumers, some offer workplace solutions such as group chat, file sharing, and group video calls to enhance collaboration within an organization. However, these workplace messaging applications come with various strict or harsh boundary restrictions between people inside and outside the organization's boundaries, making it difficult for activities on the messaging application to be disclosed to those who are not authorized members of the organization. Due to these boundary restrictions, members tend to prefer messaging applications with fewer or no boundary restrictions so that they can more easily communicate and collaborate with people who are not members of the organization. In this situation, the organization may not be aware that its members are using unverified messaging applications to collaborate with people outside the organization's boundaries. Even if the organization is aware of such activities, the chat room is operated by a third-party messaging application solution provider, so the organization has no real control over the messaging activities, nor can it track or record the activities or take any confidentiality and security measures. Therefore, there are still important areas where new and improved implementations are needed to enhance communication between parties on both sides of the organizational boundary in a more controlled and manageable manner. Summary of the Invention

[0002] In one implementation, an apparatus includes a processor and a memory in communication with the processor. The memory includes executable instructions that when executed by the processor cause the processor to control the apparatus to perform functions including: detecting that a first user has invited a second user to a communication session, wherein the first user is associated with a first user account registered to a first domain platform and the second user is not associated with any of the user accounts registered to the first domain platform, the first domain platform defining first user permissions granted to the user accounts registered to the first domain platform; based on detecting that the first user has invited the second user to the communication session, causing a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to user accounts registered to the second domain platform; and granting the second user permissions to the second user account.

[0003] In another implementation, a method for operating an apparatus for providing a communication solution between a user registered to a domain platform and another user not registered to the same domain platform includes: detecting that a first user has invited a second user to a communication session, wherein the first user is associated with a first user account registered to a first domain platform and the second user is not associated with any of the user accounts registered to the first domain platform, the first domain platform defining first user permissions granted to the user accounts registered to the first domain platform; based on detecting that the first user has invited the second user to the communication session, causing a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to user accounts registered to the second domain platform; and granting the second user permissions to the second user account.

[0004] In another implementation, a non-transitory computer-readable medium contains instructions that, when executed by a processor, cause a computer to perform the following functions: detecting that a first user has invited a second user to a communication session, wherein the first user is associated with a first user account registered to a first domain platform and the second user is not associated with any of the user accounts registered to the first domain platform, the first domain platform defining first user permissions granted to the user accounts registered to the first domain platform; based on detecting that the first user has invited the second user to the communication session, causing a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to user accounts registered to the second domain platform; and granting the second user permissions to the second user account.

[0005] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the DETAILED DESCRIPTION. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Additionally, the claimed subject matter is not limited to implementations that solve any or all of the problems BRIEF DESCRIPTION OF DRAWINGS

[0006] The accompanying drawings, which are included to provide a further understanding of the subject matter and are incorporated in and constitute a part of this application, illustrate

[0007] Figure 1 Embodiments of a system configured to provide a borderless communication and collaboration solution between members of an organization and non-members outside the organization's boundaries are shown.

[0008] Figure 2 is a flow diagram illustrating operations for a borderless communication and collaboration solution by a device of the system shown in Figure 1

[0009] Figures 3A-3C Figures 4A-4C Figures 5A-5C Figures 6A-6C Figures 7A-7C Figures 8A-8C Embodiments in which a communication session is initiated using a borderless communication and collaboration solution and a non-member is invited to the communication session are shown.

[0010] Figure 9 is a block diagram illustrating an example computer system on which aspects of the disclosure can be implemented. ​​​​​​DETAILED DESCRIPTION

[0011] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the relevant teachings. However, it will be apparent to one skilled in the art that the teachings can be practiced without these details. In other instances, well-known methods, procedures, components, and / or circuitry have been described at a relatively high level, without detail, in order to avoid unnecessarily obscuring aspects of the present teachings.

[0012] The present description is directed to providing a borderless communication and collaboration solution between people (e.g., members) within a domain or identity platform and people (e.g., non-members) outside the domain or identity platform so that the members can communicate and collaborate with the non-members in a simpler, more convenient, and less restrictive manner while the organization operating the domain can track and monitor the activities between the members and the non-members. To this end, an extended domain platform is provided in addition to the main domain platform of the organization. When a member initiates a communication session with a non-member, a non-member user account can be created for the non-member and registered in the extended domain platform. Since the non-member user account is not registered to the main domain platform, there is no need to modify the main domain platform to add the non-member information. The extended domain platform can define user permissions for the non-member user account, including permissions for accessing the communication session. As a result, the non-member can immediately participate in the communication session without having to create an account or sign up for a new communication service. Depending on the user permissions granted, the non-member can search for or initiate a communication session with a member or non-member registered to the main domain platform or the extended domain platform. Since the members and the non-members can communicate with each other with little or no restrictions, the present description provides a technical solution to the technical problem of existing solutions imposing strict or severe restrictions on the communication between the members and the non-members. Furthermore, once the non-member is registered to the extended domain platform, the organization can track and monitor all activities conducted by the non-member and apply rules and restrictions to ensure security and confidentiality. The organization can remove the non-member from all ongoing communication sessions or change or revoke the user permissions granted to the non-member whenever deemed necessary. Thus, the present description provides a technical solution to the technical problem of existing solutions where the organization cannot track, monitor, and manage the communication and collaboration sessions between the members and the non-members.

[0013] Figure 1An embodiment of a system 10 configured to provide a borderless communication and collaboration solution between members of an organization 20 and non-members outside a boundary 30 of the organization 20 is shown. The boundary 30 can define a network domain of the organization 20. For example, the members can be registered users of the network domain, and the non-members can be users of other network domains. The organization 20 can operate a device 100, a primary domain platform 110, and an extended domain platform 120. The device 100 can be configured to provide the borderless communication and collaboration solution between the members and the non-members. For example, the device 100 can be a messenger application server configured to host a communication session, such as a group chat room, an audio conference, a video conference, and the like. The device 100 can be connected to the primary domain platform 110 and the extended domain platform 120.

[0014] The primary domain platform 110 can be a directory-based identity-related service platform for a domain network, such as Microsoft Active Directory, for authenticating and authorizing the members 150A and 150B (hereinafter collectively referred to as "members 150") of the organization 20 and the member devices 140A and 140B (hereinafter collectively referred to as "member devices 140") associated with the members 150. The primary domain platform 110 can include two or more domain platforms. This can happen when two or more organizations each having an established domain platform are merged together, or when an organization operating one domain platform is acquired by another organization operating another domain platform.

[0015] The primary domain platform 110 can manage user accounts associated with the members 150 of the organization 20, and store and manage member information (e.g., name, email address, phone number, network alias, messenger ID, job title, department, team, supervisor, and the like) of the members 150 associated with the member user accounts registered to the primary domain platform 110. The primary domain platform 110 can define and grant user rights to the member user accounts of the members 150 registered to the primary domain platform 110. The user rights granted to the member user accounts can include a right to invite a user not associated with any of the user accounts registered to the primary domain platform 110 or the extended domain platform 120 to participate in a communication session, a right to add a second user to a domain directory managed by the primary domain platform 110 or the extended domain platform 120 so that the second user is searchable on the domain directory, a right to revoke a user right granted to a non-member user account, a right to remove a non-member user account from the extended domain platform 120, and the like. The member user rights can also specify access rights, security permission levels, and the like of the member user accounts associated with the members 150. Based on the user rights, the primary domain platform 110 can enforce security policies on the member devices 140 and software installed in the member devices 140.

[0016] The extended domain platform 120 can be a directory-based identity-related service platform for authenticating and authorizing non-members 180A and 180B (hereinafter collectively referred to as "non-members 180") who are not members of the organization 20 and non-member devices 170A and 170B (hereinafter collectively referred to as "non-member devices 170") associated with the non-members 180. The extended domain platform 120 can create a non-member user account associated with a non-member when the non-member has been invited to a communication session by a member. The extended domain platform 120 can store and manage non-member user account and non-member information (e.g., name, email address, phone number, network alias, messenger ID, job title, department, team, supervisor, etc.) of the non-members 180 associated with the non-member user accounts registered to the extended domain platform 120.

[0017] The extended domain platform 120 can define and grant user rights for the non-member user accounts. The user rights granted to the non-member user accounts can include rights to access a domain directory managed by the primary domain platform 110 or the extended domain platform 120, rights to start a new communication session, rights to invite users registered to the primary domain platform 110 or the extended domain platform 120 to a communication session, and the like. The non-member user rights can also specify access rights, security permission levels, and the like for the non-member user accounts. Based on the non-member user rights, the extended domain platform 120 can enforce security policies on the non-member devices 170 and software installed in the non-member devices 170.

[0018] The non-members 180 associated with the non-member user accounts registered to the extended domain directory 120 and the members 150 associated with the member user accounts registered to the primary domain directory 110 can be mutually exclusive. Thus, the non-member accounts and the member accounts can be stored and managed by two different domain platforms, respectively. This can allow the primary domain platform 110 to be kept free from any non-member information, making it easier to manage and maintain the member user accounts and information stored in the primary domain platform 110. Thus, the likelihood of activities at the extended domain platform 120 (e.g., creating, editing, or deleting a non-member account) having any negative impact on the integrity of the member user accounts and information stored in the primary domain platform 110 is much smaller. In addition, the extended domain platform 120 does not need to manage member user accounts, and managing and maintaining non-member user accounts and information becomes much simpler and easier.

[0019] Device 100 can connect to member devices 140 via network 130, which can include an intranet of organization 20. Member devices 140A and 140B can be associated with members 150A and 150B, respectively. Device 100 and member devices 140 can connect to Internet 160 via network 130. Non-member devices 170 can also connect to Internet 160. Non-member devices 170A and 170B can be associated with non-members 180A and 180B, respectively.

[0020] In one implementation, device 100 can be a messaging application server configured to host and manage communication sessions (e.g., chat sessions, audio call sessions, video call sessions, etc.) between member devices 140 and between member devices 140 and non-member devices 170. Member devices 140 and non-member devices 170 can be any computing device having communication capabilities, such as a mobile phone, a tablet PC, a desktop PC, a laptop PC, etc. Member devices 140 and non-member devices 170 can operate a messaging application configured to operate in communication with messaging application server 100.

[0021] Figure 2 is a flowchart of operations performed by device 100 for providing a communication solution between members of an organization and non-members who are not members of the organization.

[0022] At 210, device 100 can detect that a member of organization 20, such as member 150A, has invited a non-member, such as non-member 180A, to participate in a communication session (e.g., a chat room, a voice conference, a video conference, etc.). Member 150A can be associated with a member user account registered with primary domain platform 110. Non-member 180A can not be associated with any of the member user accounts registered with primary domain platform 110. Primary domain platform 110 can define user permissions granted to member user accounts registered with primary domain platform 110.

[0023] For example, device 100 can receive identification information (e.g., a phone number, an email address, a messenger alias, etc.) of non-member 180A from member device 140A associated with member 150A via network 130. Such identification information can be received when member 150A initiates a new communication session or adds non-member 180A to an existing communication session. Device 100 can control primary domain platform 110 to search primary domain platform 110 for the received identification information and determine whether the received identification information is associated with any of the existing member user accounts registered with primary domain platform 110. When no matching member user account is found from the search, device 100 can determine that member 150A has invited a non-member to participate in a communication session.

[0024] At 220, the device 100 can cause a non-member user account associated with the non-member 180A to be created and registered to the extended domain platform 120. The extended domain platform 120 can be distinct from the primary domain platform 100. The extended domain platform 120 can define user permissions granted to non-member user accounts registered to the extended domain platform 120. The device 100 can then communicate with the non-member device 170A via the Internet 160 to invite the non-member 180A to participate in a communication session.

[0025] The non-member user account can be automatically created when the non-member 180A is invited to participate in a communication session. The non-member 180A can not need to perform or complete a sign-up or registration process. For example, both the member 150A and the non-member 180A can use the same messaging application platform (e.g., a messaging mobile application) hosted by the device 100. The member 150A can select the name or phone number of the non-member 180A on a contact list of the messaging mobile application to invite the non-member 180A into a chat room. Upon receiving the selected name or phone number of the non-member 180A from the member device 140A, the device 100 can automatically create a non-member user account for the non-member 180A. Alternatively, the non-member user account can be created when the device 100 receives user input from the member device 140A by the user 150A to create a non-member user account associated with the non-member 180A.

[0026] At step 230, the device 100 can grant the non-member user account user permissions defined by the extended domain platform 120. The user permissions granted to the non-member user account can include permissions to access a domain directory managed by the primary domain platform 110 or the extended domain platform 120, permissions to start a new communication session, permissions to invite users registered to the primary domain platform 110 or the extended domain platform 120 to participate in a communication session, and the like. Thus, the non-member 180A can be granted permissions to communicate with the member 180A despite not being registered to the primary domain platform 110.

[0027] By registering the non-member user account to the extended domain platform 120, the primary domain platform 110 can decouple the responsibility of managing both member user accounts and non-member user accounts, thereby making it easier to manage member user accounts. For example, the primary domain platform 110 can perform bulk data updates to member user accounts without accidentally updating non-member accounts. Further, a member or IT personnel can add, edit, or delete non-member user accounts to or from the extended domain platform 120 without accidentally altering or deleting member user accounts.

[0028] Upon registration with the extended domain platform, non-member 180A can become an entity of a domain directory that the organization can identify, track, monitor, and manage within the organization's domain. Further, member 150 can be able to search for non-member 180A via extended domain platform 120.

[0029] Accordingly, device 100 can automatically detect that non-member 180A is invited to participate in a communication session, and can automatically create a non-member user account for non-member 180A and register the non-member user account with extended domain platform 120. Accordingly, member 150A who has invited non-member 180A can initiate the communication session as if member 150A is initiating a communication with another member registered with primary domain platform 110. Member 150A can not need to take any additional action to report non-member 180A or the communication session with non-member 180A to organization 20. Non-member 180A can participate in the communication session without going through any registration or verification steps. Accordingly, member 150A can be able to communicate with non-member 180A immediately.

[0030] Device 100 can also be configured to track and monitor the activities of non-member 180A to ensure that non-member 180A complies with security and privacy rules enforced by primary domain platform 110 and extended domain platform 120. Device 100 can also track and monitor all activities in the communication session. When predetermined conditions are met, device 100 can revoke the permissions granted to non-member 180A and remove non-member 180A from the communication session. For example, device 100 can receive a request from member device 140A to revoke the user permissions granted to non-member 180A, which can include removing non-member 180A from the communication session. This can occur when the collaboration between member 150A and non-member 180A is complete and non-member 180A no longer needs access to the messages and information exchanged during the communication session. Alternatively, device 100 can monitor the activities in the communication session and revoke the permissions granted to non-member 180A when there is no activity during a predetermined time period (e.g., 24 hours, one week, etc.).

[0031] When the user's privileges are revoked, the non-member 180A can be removed from the communication session and no longer allowed to access messages or information exchanged during the communication session. For example, the device 100 can delete data related to the communication session from the non-member device 170A. This can ensure that messages and information shared during the communication session are not mishandled by the non-member 180A. In addition to removing the non-member from the communication session with the member 150A, the device 100 can be configured to identify all member-related communication sessions in which the non-member 180A is participating, remove the non-member 180A from all of the identified communication sessions, and remove data related to the identified communication sessions from the non-member device 170A. This can occur when the device 100 determines that the non-member 180A poses a security threat or has not been active during a predetermined period of time. Thus, the device 100 can allow the organization 20 to manage communication sessions involving non-members in a quick and efficient manner.

[0032] Figures 3A to 8C Embodiments of how to initiate a communication session and how to invite a non-member to a communication session are shown. Figure 3A 、 Figure 3B and Figure 3C show embodiments of graphical user interfaces (GUIs) of a messaging application on a non-member device (e.g., non-member device 170A) associated with a non-member Peter (e.g., non-member 180A), a member device (e.g., member device 140A) associated with a member Will (e.g., member 150A), and another member device (e.g., member device 140B) associated with another member Wasif (e.g., member 150B), respectively. The messaging application can operate to communicate with the device 100.

[0033] Referring to Figure 3A 、 Figure 3B and Figure 3C , Will can interact with the GUI of the messaging application (e.g., member device 140A) running on his phone to indicate that he wants to start a new communication session (e.g., a new chat session) with Peter (e.g., non-member 180A) and Wasif (e.g., member 140B). For example, Will can touch the new chat icon 310 displayed in the upper right corner of the GUI. At this point, the device 100 can not know who Will wants to invite to the chat session, so Peter's phone (e.g., non-member device 170A) and Wasif's phone (e.g., member device 140B) can not display any information related to the chat session, which is shown as blank in Figure 3A and Figure 3C .

[0034] Referring toFigure 4A 、 Figure 4B and Figure 4C Upon receiving Will's input initiating a new chat session, Will's device can display a GUI for selecting members or non-members to be invited to the chat session. Since the messaging application operates in association with device 100 and the home domain platform 110, Will's device can be able to display other members, such as Christ Naidoo, Alvin Tao, and Laurence Gilbertson, as shown in Figure 4B . Will's device can also be able to display non-members, such as Daria Mariano, David Power, and Peter Peterson, whose contact information (e.g., name, phone number, email address, messenger alias, etc.) is locally stored in the phone or in cloud space. Will can then select the members or non-members he wants to invite to the chat session. Figure 4B Will's device displays that Will has selected non-member Peter and member Wasif. Will's device can then notify device 100 that Peter and Wasif are to be invited to the chat session. Upon receiving information about Peter and Wasif, device 100 can determine that Peter is not a member of organization 20 and then create an account for Peter and register the account with the extended domain platform 120. Device 100 can then provision the account for Peter with predetermined permissions so that once Peter enters the chat session, Peter can interact with Will and Wasif. Thus, when Will selects Peter as an invitee to the chat session, Peter is automatically registered with the extended domain platform 120. No further action is required by Will or Peter.

[0035] Referring to Figure 5A 、 Figure 5B and Figure 5C Once Peter's account is created and registered with the extended domain platform 120, the messaging application running on Will's device can display a GUI for the chat session in which Will can type a message and post the message to Peter and Wasif. Peter's device and Wasif's device can not display any information related to the chat session until Will sends a message. Figure 5B The message "Peter, when can you start?" typed by Will is shown.

[0036] Referring to Figure 6A 、 Figure 6B and Figure 6CMessages sent from Will's device can be sent to device 100 and then relayed to Peter's device and Wasif's device. The messages can then be displayed on the GUI of the messaging application running on Peter's and Wasif's devices. For example, as shown in Figure 6A and Figure 6C , Will's messages can be listed in the chat list on Peter's device and Wasif's device.

[0037] Referring to Figure 7A , Figure 7B and Figure 7C , when Peter and Wasif select Will's messages from the message list, Peter's device and Wasif's device can display the chat session screen on which Will's messages are displayed, as shown in Figure 7A and Figure 7C . Peter's chat session screen can indicate that the chat session is owned by organization 20 and that Will has added Peter and Wasif to the chat session. Thus, despite being a non-member, Peter can participate in the chat session without taking any additional steps to register himself to the directory service of organization 20 or sign up for a new messaging service.

[0038] Referring to Figure 8A , Figure 8B and Figure 8C , when Peter's account is created and registered to the extended domain platform 120, device 100 can provide predetermined permissions, including the permission to read messages posted by others and to post messages to others. For example, as shown in Figure 8A , in response to Will's messages, Peter can post a response "I'm ready to start as early as next week." Peter's response can be sent to device 100 and then relayed to Will's device and Wasif's device, which can display Peter's response on the chat session GUI, as shown in Figure 8B and Figure 8C . Thus, device 100 can provide a borderless communication and collaboration solution between members and non-members of an organization that makes it easy for members and non-members to join and use, and for the organization to track, monitor, and manage.

[0039] Device 100 can be configured to work with two or more organizations that do not share the same member and extended host domain platform. When a non-member is invited to two chat sessions by two different members of two different organizations, device 100 can create two different non-member user accounts for the non-member and register the two different accounts to two different extended domain platforms, each operated by a different organization. Each account can be managed according to different rules set by the different organizations. Thus, a non-member can participate in as many communication sessions as desired according to need, as long as the organizations provide a borderless communication and collaboration solution.

[0040] Figure 9 FIG. 9 is a block diagram illustrating an example computer system 900 upon which aspects of the disclosure can be implemented. The computer system 900 can include a bus 902 or other communication mechanism for communicating information, and a processor 904 coupled with the bus 902 for processing information. The computer system 900 can also include a main memory 906, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus 902 for storing information and instructions to be executed by the processor 904. The main memory 906 can also be used for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor 904. The computer system 900 can implement, for example, device 100, member device 140, and non-member device 170.

[0041] The computer system 900 can further include a read only memory (ROM) 908 or other static storage device coupled to the bus 902 for storing static information and instructions for the processor 904. A storage device 910, such as a flash memory or other non-volatile memory, can be coupled to the bus 902 for storing information and instructions.

[0042] The computer system 900 can be coupled via the bus 902 to a display 912, such as a liquid crystal display (LCD), for displaying information. One or more user input devices, such as example user input device 914, can be coupled to the bus 902 and can be configured for receiving various user input, such as user command selections, and transmitting such to the processor 904 or the main memory 906. The user input device 914 can include physical structures or virtual implementations, or both, that provide user input modes or options for controlling, for example, a cursor through the display 912 or visible to a user by other techniques, and such modes or operations can include, for example, virtual mice, track balls, or cursor direction keys.

[0043] The computer system 900 can include various resources of the processor 904 that execute various program instructions in an overlapped or interleaved manner. Instructions can be read into the main memory 906 from another machine-readable medium, such as the storage device 910. In some examples, hardwired circuitry can be used in place of or in combination with software instructions. The term "machine-readable medium" as used herein refers to any medium that participates in providing instructions to a machine to cause the machine to operate in a specific fashion. Such a medium can take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media can include, for example, optical or magnetic disks, such as the storage device 910. Transmission media can include optical or electrical signals that are conveyed through a physical connection, or wireless signals such as acoustic waves or electromagnetic waves, e.g., those generated during radio- wave and infra-red data communications, that are capable of carrying data to a physical mechanism for detection by the machine.

[0044] The computer system 900 can further include a communication interface 918 coupled to the bus 902 for sending and receiving data, including program code, in the form of packets, among other data, through the network link 920 to a network 922, such as one based on the Internet. The network link 920 can provide data communication through one or more networks to other devices. For example, the network link 920 can provide a connection through local network 922 to a host computer 924 or to data equipment operated by an Internet Service Provider (ISP) 926 for access to servers 930, such as through the Internet 928, for obtaining application code.

[0045] Additional features, characteristics, and advantages of the present application will be described hereinafter by way of various items:

[0046] Item 1. An apparatus comprising a processor and a memory in communication with the processor, the memory comprising executable instructions that, when executed by the processor, cause the processor to control the apparatus to perform the following functions: detect that a first user has invited a second user to a communication session, wherein the first user is associated with a first user account registered to a first domain platform and the second user is not associated with any of the user accounts registered to the first domain platform, the first domain platform defining first user permissions granted to the user accounts registered to the first domain platform; based on detecting that the first user has invited the second user to the communication session, cause a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to user accounts registered to the second domain platform; and grant the second user permissions to the second user account.

[0047] Item 2. The device of item 1, wherein to cause the second user account to be created and registered to the second domain platform, the instructions, when executed by the processor, further cause the processor to control the device to perform the function of controlling the second domain platform to automatically create and register the second user account in response to detecting that the first user has invited the second user to the communication session.

[0048] Item 3. The device of item 1, wherein to cause the second user account to be created and registered to the second domain platform, the instructions, when executed by the processor, further cause the processor to control the device to perform the functions of receiving user input from a first user device associated with the first user to create the second user account with the second domain platform, and controlling the second domain platform to create and register the second user account in response to the user input received from the first device.

[0049] Item 4. The device of item 1, wherein the first user permissions include at least one of a permission to invite a user not associated with any of the user accounts registered to the first domain platform or the second domain platform to a communication session, a permission to add the second user to a domain directory managed by the first domain platform or the second domain platform such that the second user is searchable on the domain directory, a permission to revoke the second user permissions granted to the second user account, and a permission to remove the second user account from the second domain platform.

[0050] Item 5. The device of item 1, wherein the second user permissions include at least one of a permission to access a domain directory managed by the first domain directory or the second domain directory, a permission to start a new communication session, and a permission to invite a user registered to the first domain platform or the second domain platform to a communication session.

[0051] Item 6. The device of item 1, wherein the user registered to the first domain platform and the user registered to the second domain platform are mutually exclusive.

[0052] Item 7. The device of item 1, wherein to detect that the first user has invited the second user to the communication session, the instructions, when executed by the processor, further cause the processor to control the device to perform the function of receiving identification information of the second user from a first user device associated with the first user via a communication network.

[0053] Item 8. The device according to Item 7, wherein the identification information includes the second user's telephone number, email address, or message sender alias.

[0054] Item 9. The device according to Item 1, wherein the instructions, when executed by the processor, further cause the processor to control the device to perform the following functions: detecting that a predetermined condition is met relative to the second user; and revoking the second user privileges granted to the second user.

[0055] Item 10. The device according to Item 9, wherein, in order to detect that the predetermined condition is met, the instruction, when executed by the processor, further causes the processor to control the device to perform the following functions: receiving a request from a first user device associated with the first user for revoking the second user permission granted to the second user; or detecting that there is no activity in the communication session during a predetermined time period.

[0056] Item 11. A method for operating an apparatus for providing a communication solution between a user registered to a domain platform and another user not registered to the same domain platform, comprising: detecting that a first user has invited a second user to participate in a communication session, wherein the first user is associated with a first user account registered to a first domain platform and the second user is not associated with any of the user accounts registered to the first domain platform, the first domain platform defining first user permissions granted to the user accounts registered to the first domain platform; based on detecting that the first user has invited the second user to participate in the communication session, causing a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to the user accounts registered to the second domain platform; and granting the second user permissions to the second user account.

[0057] Item 12, the method according to Item 11, wherein causing the second user account to be created and registered to the second domain platform includes controlling the second domain platform to automatically create and register the second user account in response to detecting that the first user has invited the second user to participate in the communication session.

[0058] Item 13. The method according to Item 12, wherein causing the second user account to be created and registered to the second domain platform includes: receiving user input from a first user device associated with the first user for creating the second user account to the second domain platform; and controlling the second domain platform to create and register the second user account in response to the user input received from the first device.

[0059] Item 14. The method of item 11, wherein the first user permissions comprise at least one of: a permission to invite a user not associated with either of the user accounts registered to the first domain platform or the second domain platform to participate in a communication session; a permission to add the second user to a domain directory managed by the first domain platform or the second domain platform such that the second user is searchable on the domain directory; a permission to revoke the second user permissions granted to the second user account; and a permission to remove the second user account from the second domain platform.

[0060] Item 15. The method of item 14, wherein the second user permissions comprise at least one of: a permission to access a domain directory managed by the first domain directory or the second domain directory; a permission to start a new communication session; and a permission to invite a user registered to the first domain platform or the second domain platform to participate in a communication session.

[0061] Item 16. The method of item 11, wherein the user registered to the first domain platform and the user registered to the second domain platform are mutually exclusive.

[0062] Item 17. The method of item 11, wherein detecting that the first user has invited the second user to participate in the communication session comprises receiving identification information of the second user from a first user device associated with the first user via a communication network.

[0063] Item 18. The device of item 17, wherein the identification information comprises a phone number, an email address, or a messenger alias of the second user.

[0064] Item 19. The method of item 11, further comprising: detecting that a predetermined condition is satisfied with respect to the non-member; and removing the non-member from the communication session.

[0065] Item 20. A non-transitory computer-readable medium containing instructions that, when executed by a processor, cause a computer to perform the following functions: detecting that a first user has invited a second user to a communication session, wherein the first user is associated with a first user account registered to a first domain platform and the second user is not associated with any of the user accounts registered to the first domain platform, the first domain platform defining first user permissions granted to the user accounts registered to the first domain platform; based on detecting that the first user has invited the second user to the communication session, causing a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to user accounts registered to the second domain platform; and granting the second user permissions to the second user account.

[0066] While various embodiments have been described, this description is intended to be exemplary, rather than limiting, and it will be appreciated that many other embodiments and implementations are possible within the scope of the embodiments. Although many possible combinations of features have been described in the context of the embodiments, other combinations of features are possible and are encompassed by the disclosed features. Unless specifically stated otherwise, any feature of any embodiment can be used with any other feature or element of any other embodiment or in combination with any other feature or element of any other embodiment. Thus, it will be understood that any of the features shown and / or discussed in this disclosure can be implemented together in any suitable combination. Therefore, unless otherwise noted, the embodiments are not limited to the specific embodiments described herein. Further, various modifications and changes can be made within the scope of the attached claims and their equivalents.

[0067] While the foregoing has described examples and / or other examples that are believed to be the most useful, it is understood that various modifications can be made within the scope of the present disclosure and the inventive subject matter disclosed herein, and that the teachings herein can be applied without departing from the true spirit and scope of the present disclosure. The appended claims are intended to claim any and all embodiments (both singular and in combination) that come within the scope of the following claims and their equivalents.

[0068] Unless otherwise indicated, in the specification, including the appended claims, all measurements, values, ratings, positions, magnitudes, sizes and other specifications are understood to be modified in all instances by the term "approximately" unless otherwise indicated. They are intended to have a reasonable range around the stipulated value to account for variations in and tolerances of the functions to which the values pertain, and of the art in general.

[0069] The scope of protection is limited to the scope of the claims that follow this disclosure. That scope is intended to and should be construed as being consistent with the ordinary meaning of the language used in the claims whenever the claim language makes it appropriate that would not be inconsistent with any claim limitations under 35 U.S.C. § 101, 102, or 103. However, all claims are intended to be supported by substitute specific embodiments disclosed herein, to the extent required by 35 U.S.C. § 112, first paragraph. Accordingly, no disclaimer of any claim limitation is intended.

[0070] Except as otherwise indicated, no statement in this specification is to be construed as a substantial change, either literal or relative. Except as otherwise indicated, no statement in this specification is to be construed as a disclaimer or disavowal of any claim element.

[0071] It will be understood that the terms and expressions used herein have the ordinary meaning as is accorded to such terms and expressions with respect to their corresponding individual fields of endeavor and as found in the context thereof and that single functional or structural elements to which multiple referents could have been made are not necessarily excluded from the various embodiments simply because they are not specifically referenced. The use of certain terms in various places of this specification is as a matter of language choice and not a limitation on the scope of the present disclosure, unless otherwise indicated.

[0072] The abstract is provided to allow readers to quickly ascertain the nature of technical disclosures. It is submitted with the understanding that it will not be used to interpret or limit the scope or the meaning of the claims. In addition, in the foregoing Detailed Description, various features are grouped together in examples for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed disclosure requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter can lie in fewer than all features of a single disclosed example. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed disclosure.

Claims

1. A device comprising: a processor; and a memory in communication with the processor, the memory comprising executable instructions that, when executed by the processor, cause the processor to control the device to perform the following functions: detect that a first user has invited a second user to a communication session, wherein the first user is associated with a first user account registered to a first domain platform and the second user is not associated with a user account registered to the first domain platform, the first domain platform defining first user permissions granted to the user accounts registered to the first domain platform, the first user permissions including a permission to invite unregistered users not associated with a user account registered to the first domain platform to the communication session; based on detecting that the first user has invited the second user to the communication session, cause a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to user accounts registered to the second domain platform; and grant the second user account the second user permissions, the second user permissions including a permission to participate in the communication session when invited by a registered user associated with a user account registered to the first domain platform. To cause the second user account to be created and registered to the second domain platform, the instructions, when executed by the processor, further cause the processor to control the device to perform the following function: control the second domain platform to automatically create and register the second user account in response to detecting that the first user has invited the second user to the communication session.

2. The apparatus of claim 1, wherein, To cause the second user account to be created and registered to the second domain platform, the instructions, when executed by the processor, further cause the processor to control the device to perform the following functions:

3. The apparatus of claim 1, wherein, receive, from a first user device associated with the first user, user input to create the second user account with the second domain platform; and control the second domain platform to create and register the second user account in response to the user input received from the first user device. The first user permissions further include at least one of:

4. The apparatus of claim 1, wherein, a permission to invite users not associated with either of the user accounts registered to the first domain platform or the second domain platform to a communication session; a permission to add the second user to a domain directory managed by the first domain platform or the second domain platform such that the second user is searchable on the domain directory; a permission to revoke the second user permissions granted to the second user account; and a permission to remove the second user account from the second domain platform. The second user permissions further include at least one of: a permission to access a domain directory managed by the first domain platform or the second domain platform; 5. The apparatus of claim 1, wherein, a permission to start a new communication session; and a permission to invite users associated with user accounts registered to the first domain platform or the second domain platform to a communication session. ​ ​ 6. The apparatus of claim 1, wherein, A plurality of first user accounts registered to the first domain platform are mutually exclusive with a plurality of second user accounts registered to the second domain platform.

7. The apparatus of claim 1, wherein, To detect that the first user has invited the second user to the communication session, the instructions, when executed by the processor, further cause the processor to control the device to perform the function of receiving, from a first user device associated with the first user, identification information of the second user via a communication network.

8. The apparatus of claim 7, wherein, The identification information includes a phone number, an email address, or a messenger alias of the second user.

9. The apparatus of claim 1, wherein, The instructions, when executed by the processor, further cause the processor to control the device to perform the function of: detecting, with respect to the second user, that a predetermined condition is satisfied; and revoking second user permissions granted to the second user.

10. The apparatus of claim 9, wherein, To detect that the predetermined condition is satisfied, the instructions, when executed by the processor, further cause the processor to control the device to perform the function of: receiving, from a first user device associated with the first user, a request to revoke the second user permissions granted to the second user; or detecting that there is no activity in the communication session during a predetermined time period.

11. A method for operating a device for providing a communication solution between a user registered to a domain platform and another user not registered to the same domain platform, comprising: detecting that a first user has invited a second user to a communication session, wherein the first user is associated with a first user account registered to a first domain platform and the second user is not associated with a user account registered to the first domain platform, the first domain platform defining first user permissions granted to the user accounts registered to the first domain platform, the first user permissions including a permission to invite unregistered users not associated with a user account registered to the first domain platform to the communication session; based on detecting that the first user has invited the second user to the communication session, causing a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to user accounts registered to the second domain platform; and granting the second user permissions to the second user account, the second user permissions including a permission to participate in the communication session when invited by a registered user associated with a user account registered to the first domain platform.

12. The method of claim 11, wherein, Causing the second user account to be created and registered to the second domain platform includes controlling the second domain platform to automatically create and register the second user account in response to detecting that the first user has invited the second user to the communication session.

13. The method of claim 12, wherein, Causing the second user account to be created and registered to the second domain platform includes: receiving, from a first user device associated with the first user, user input to create the second user account with the second domain platform; and controlling the second domain platform to create and register the second user account in response to the user input received from the first user device.

14. The method of claim 11, wherein, The user registered to the first domain platform and the user registered to the second domain platform are mutually exclusive.

15. A computer readable medium containing instructions that, when executed by a processor, cause a computer to perform the following functions: detecting that a first user has invited a second user to a communication session, wherein, The first user is associated with a first user account registered to a first domain platform and the second user is not associated with a user account registered to the first domain platform, the first domain platform defining first user permissions granted to the user account registered to the first domain platform, the first user permissions including a permission to invite an unregistered user not associated with a user account registered to the first domain platform to the communication session; based on detecting that the first user has invited the second user to the communication session, causing a second user account associated with the second user to be created and registered to a second domain platform, the second domain platform being different from the first domain platform and defining second user permissions granted to user accounts registered to the second domain platform; and the second user account is granted the second user permissions, the second user permissions including a permission to participate in the communication session when invited by a registered user associated with a user account registered to the first domain platform.

Images