WO2023036172A1 - 交互方法、装置和电子设备 - Google Patents

交互方法、装置和电子设备 Download PDF

Info

Publication number
WO2023036172A1
WO2023036172A1 PCT/CN2022/117519 CN2022117519W WO2023036172A1 WO 2023036172 A1 WO2023036172 A1 WO 2023036172A1 CN 2022117519 W CN2022117519 W CN 2022117519W WO 2023036172 A1 WO2023036172 A1 WO 2023036172A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
team
target
account
interface
Prior art date
Application number
PCT/CN2022/117519
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 北京字跳网络技术有限公司
Publication of WO2023036172A1 publication Critical patent/WO2023036172A1/zh
Priority to US18/392,477 priority Critical patent/US20240127186A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/105—Human resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance

Definitions

  • the present disclosure relates to the field of computer technology, and in particular to an interaction method, device and electronic equipment.
  • users can use electronic devices to achieve various functions. For example, users can use electronic devices for online office work, and can also use electronic devices to watch various videos.
  • video applications serve as a content platform that can provide various content to a large number of users.
  • an embodiment of the present disclosure provides an interaction method, the method including: displaying a first application interface, wherein the first application interface includes an interface of the first application; creating a second application account in the first application interface , wherein the second application account is used to log in to the second application.
  • the embodiment of the present disclosure provides an interaction method, the method includes: in the first application interface, configuring the permissions of the second team members of the target second application team, wherein the target associated with the first application interface The first application team is bound to the target second application team.
  • an embodiment of the present disclosure provides an interaction device, including: a selection display unit, configured to display a first application interface, where the first application interface includes an interface of the first application; In the application interface, a second application account is created, wherein the second application account is used to log in to the second application.
  • an embodiment of the present disclosure provides an interaction device, including: a configuration unit configured to configure permissions of second team members of the target second application team in the first application interface, wherein the first application interface The associated target first application team is bound to the target second application team.
  • an embodiment of the present disclosure provides an electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, so that the one or more processors implement the interaction method as described in the first aspect or the second aspect.
  • an embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the steps of the interaction method described in the first aspect or the second aspect are implemented.
  • Figure 1 is a flowchart of one embodiment of an interaction method according to the present disclosure
  • FIG. 2 is a flowchart of an embodiment of another interaction method according to the present disclosure
  • Fig. 3 is a schematic diagram of an application scenario of the interaction method according to the present disclosure.
  • Fig. 4 is a schematic diagram of an application scenario of the interaction method according to the present disclosure.
  • Fig. 5 is a schematic diagram of an application scenario of the interaction method according to the present disclosure.
  • Fig. 6 is a schematic diagram of an application scenario of the interaction method according to the present disclosure.
  • Fig. 7 is a schematic diagram of an application scenario of the interaction method according to the present disclosure.
  • Fig. 8 is a schematic structural diagram of an embodiment of an interaction device according to the present disclosure.
  • Fig. 9 is a schematic structural diagram of an embodiment of another interaction device according to the present disclosure.
  • FIG. 10 is an exemplary system architecture to which the interaction method of an embodiment of the present disclosure can be applied.
  • Fig. 11 is a schematic diagram of a basic structure of an electronic device provided according to an embodiment of the present disclosure.
  • the term “comprise” and its variations are open-ended, ie “including but not limited to”.
  • the term “based on” is “based at least in part on”.
  • the term “one embodiment” means “at least one embodiment”; the term “another embodiment” means “at least one further embodiment”; the term “some embodiments” means “at least some embodiments.” Relevant definitions of other terms will be given in the description below.
  • FIG. 1 shows the flow of an embodiment of the interaction method according to the present disclosure.
  • the interaction method includes the following steps:
  • Step 101 displaying a first application interface.
  • the execution subject of the interaction method may display the first application interface.
  • the first application interface may include any interface of the first application.
  • Step 102 in the first application interface, create a second application account.
  • the second application account is used to log in to the second application.
  • the specific types of the first application and the second application can be set in actual application scenarios, and are not limited here.
  • the first application may include an office application
  • the second application may include a video playback application; as an example, an account for the video playback application may be established in the office application.
  • the interaction method provided in this embodiment can provide a new way to create a second application account by creating a second application account in the first application.
  • the user needs to create an account in the second application during the process of using the first application, there is no need to jump to the second application to perform the account creation operation, which improves the user's operation efficiency.
  • the creation of batches of second application accounts can be realized on the first application interface, thereby further improving the operation efficiency of users creating accounts for use in the second application .
  • a technical path in which messages can be exchanged between the accounts of two applications may be adopted to realize the intercommunication between the two applications.
  • the two accounts that can send messages to each other in the related technology are both accounts independently created in their respective applications.
  • the accounts in each application remain independent in this application, and other applications other than this application cannot use this account. Perform operations such as creation or management.
  • the method further includes: binding the created second application account to team members in the target first application team.
  • the target first application team is a team in the first application account system, and the team in the first application account system includes team members.
  • the first application account system may include multiple teams.
  • Team A and Team B may include members Xiao Wang and Xiao Zhang.
  • Team B may include members Xiao Li and Xiao Liu.
  • the created second application account (for example, the account name is called the front office of company A) can be bound to Xiao Wang in team A.
  • the creator who performs the creation operation may be a user (for example, an administrator) with operation authority in a certain team.
  • the binding the created second application account to team members in the target first application team includes: selecting team members from the team members of the target first application team as the target A team member; bind the created second application account with the target team member.
  • team members may be selected from the first application team to bind with the second application account.
  • Xiao Wang can be selected from Team A as a target team member, and bound to the created second application account "front desk of company A".
  • the method further includes: releasing the binding between the team members in the target first application team and the second application account.
  • the binding between the team member and the second application account can also be released.
  • the binding between Xiao Wang in team A and the created second application account "foreground of company A" can be released.
  • the unbinding between the team member and the second application account can be performed by the administrator of the first application team (for example, the administrator of team A), or by the second application bound with the second application.
  • a team member (such as Xiao Wang in team A) operates.
  • the method further includes: in response to unbinding the team member bound by the second application account from the target first application team, releasing the binding between the second application account and the bound team member determining; displaying prompt information, wherein the prompt information is used to prompt to bind a new team member for the second application account.
  • the second application account bound to the team member can be automatically unbound from the first application team. Then, a prompt message may be displayed to prompt the user to re-bind the team members of the first application team with the second application account.
  • the second application account can be used as a shell, and through the variable relationship of the binding relationship, the connection between the second application account and the team members of the first application team can be realized.
  • a flexible binding relationship is realized between members of different first application teams, so that the second application account can be reused by different first team members.
  • the second application account can accumulate a large number of users and resources. If the user of the second application account leaves the first application team, the second application account can be inherited by other members of the first application team (change binding ), thereby inheriting the users and resources of the second application account.
  • the method further includes: performing a management operation on the created second application account on the first application interface, wherein the management operation includes at least one of the following: view, search and filter.
  • the created second application account is bound to the target second application team.
  • the target second application team is a team in the second application account system, and the team in the second application account system includes team members.
  • the foreground of the created second application account A company is bound to the target second application team A company.
  • the second application account is bound to the target second application team, which can provide the basis for managing the second application account, and facilitate the management of accounts under several second application teams with the second application team as a unit. .
  • the step 102 may include: determining a target second application team bound to the target first application team, wherein the target first application team is associated with the first application interface; In the interface, create a second application account belonging to the target second application team.
  • the target first application team may be bound to at least one team in the second application.
  • Company A in the first application may be bound with Company A in the second application.
  • a second application account belonging to the target second application team can be created.
  • the second application account created in the first application interface can be automatically bound to the second application team A company bound by Company A, that is, in In the application interface of Company A, a second application account (such as the front desk of Company A) is automatically created for Company A.
  • a second application account is created, and the created second application account is automatically bound to the second application team bound to the first application team. In this way, it is possible to automatically create an employee account for the second application team on the first application interface, reducing the user's manual binding operations and time.
  • the method before determining the target second application team bound to the target first application team, the method further includes: in the first application interface, receiving the second application team identifier input by the user; according to The second application team identifier sends a first binding request; based on the verification result of the first binding request, it is determined whether to bind the target first application team associated with the first application interface and the second application team entered by the user Identify the indicated second application team.
  • the first binding request is used to request to bind the target first application team and the second application team indicated by the second application team identifier input by the user.
  • the target first application team may be team A, and in the first application interface of team A, the user may input the identifier of the second application team (such as "company B").
  • the first binding request may be sent according to the second application team identifier (for example, "company B”).
  • the first binding request may be used to request binding of Team A and the company indicated by "Company B". Based on the verification result of the first binding request, it may be determined whether to bind Team A and the company indicated by "Company B".
  • the verification method for the first binding request can be set according to actual application scenarios, and is not limited here.
  • the verification method can verify multiple aspects, such as whether the company indicated by Team A and "Company B" are the same subject; another example, whether the administrator of "Company B" in the second application agrees to the binding wait.
  • establishing the first team in the first application may establish a binding relationship with at least one second application team in the second application.
  • the management of the second application team based on the first application team can be realized, and the management efficiency of the team members of the second application team can be improved.
  • the step of verifying the first binding request includes: verifying whether the subject corresponding to the target first application team and the subject corresponding to the second application team identifier input by the user are the same; The second application sends a binding confirmation notification to the management user corresponding to the second application team identifier; based on the confirmation operation on the binding confirmation notification, it is confirmed that the verification of the first binding request is passed.
  • subjects can be understood as the subject in the legal sense.
  • subjects may include natural persons, legal persons, unincorporated organizations, etc.
  • FIG. 4 shows a process of verifying the first binding request.
  • the verification of the first binding request may include verification of whether the subject is the same, and after verifying that the subject is the same, the management user of the second application team may confirm whether to perform the binding. In this way, it is possible to bind the accounts of the same subject on different platforms, which is convenient for the same subject to manage. In addition, the team management user of the second application team confirms the binding, and the human user can confirm again that the binding to be implemented is correct, so as to improve the accuracy of the binding.
  • the method further includes: in the second application interface, receiving the first application team identifier input by the user; sending a second binding request according to the first application team identifier, wherein the first The second binding request is used to request to bind the target second application team and the first application team indicated by the first application team identifier input by the user; determine whether to bind the second application interface based on the verification result of the second binding request The associated target second application team and the first application team identifier input by the user indicate the first application team.
  • the method further includes: if the first application account currently logged into the first application has a bound second application account, displaying the login entry of the second application in the first application; based on the The login entry uses the second application account bound to the currently logged-in first application account to log in and display the second application interface.
  • FIG. 5 shows the flow of an embodiment of the interaction method according to the present disclosure.
  • the interaction method includes the following steps:
  • Step 501 in the first application interface, configure the authority of the second team members of the target second application team.
  • the target first application team associated with the first application interface is bound to the target second application team.
  • the second application team may be called an enterprise number, and the second team members may be called an enterprise employee number or an employee number.
  • the second application team may have some functional tools, and the second team members belonging to the second application team may have the authority to use part or all of the functional tools of the team.
  • the types of functional tools can be set according to actual application scenarios, and are not limited here.
  • the second team member functional tools may include but not limited to at least one of the following: marketing tools (such as shopping carts, subscription components).
  • configuring the authority of the second team member can realize the management of the authority of the second application account in the first application interface, and realize the authorization of the second application account.
  • Management shortcut management When the user uses the first application, if there is a need to perform permission operations on the second application account in the second application, there is no need to jump to the second application to perform operations.
  • the access to configure permissions for the second application account may only be set in the first application. In this way, the authority for managing the second application account can be tightened to the first application, so as to avoid problems such as authority abuse of the second application account.
  • configuring the permissions of the second team members of the target second application team in the first application interface includes: displaying the preset first permissions of the target second application team in the first application interface Identifier, the preset first authority identifier indicates the team authority possessed by the second application team; according to the selection operation on the displayed preset first authority identifier, the first authorization request is sent according to the selected first authority identifier; based on the The authorization result of the first authorization request determines the preset first authority possessed by the second team member.
  • the second application team may have some functional tools, and the second team members belonging to the second application team may have the authority to use part or all of the functional tools of the team.
  • the types of functional tools can be set according to actual application scenarios, and are not limited here.
  • the second team member functional tools may include but not limited to at least one of the following: marketing tools (such as shopping carts, subscription components).
  • the second team members can inherit some of the team permissions of the second team, which is convenient for the second team members to carry out some activities, such as explaining the business of the enterprise within the scope of public domain traffic. Therefore, the efficiency of the second team member in advancing team-related affairs can be improved.
  • the method further includes: in the first application interface, receiving a second application team identifier input by the user; sending a first binding request according to the second application team identifier, wherein the first A binding request is used to request binding of the target first application team and the second application team indicated by the second application team identifier input by the user; based on the verification result of the first binding request, determine whether to bind the first application interface
  • the associated target first application team and the second application team identifier input by the user indicate the second application team.
  • the verifying step of verifying the first binding request includes: verifying whether the subject corresponding to the target first application team and the subject corresponding to the second application team identifier input by the user are the same; The second application sends a binding confirmation notification to the management user corresponding to the second application team identifier; based on the confirmation operation on the binding confirmation notification, it is confirmed that the verification of the first binding request is passed.
  • the above-mentioned second application may belong to a public domain traffic application.
  • an account type that belongs to an enterprise may be added, for example, it may be called an enterprise employee number.
  • the enterprise employee account can realize the inheritance of account assets, provide the basis for the data openness required for refined operations, and can have more employee account quotas.
  • the second application team in the second application can also be called the enterprise account, and the enterprise account can be based on the tool capabilities of the online enterprise account, and the employee account of the enterprise can also be authorized to have the corresponding tool capabilities; Account binding of the application team and review of the creation of enterprise employee numbers.
  • the first application team associated with the enterprise account can open N enterprise employee accounts whose authority belongs to the enterprise, and authorize the marketing capabilities of the enterprise account to the employee account of the enterprise employee account , all kinds of data of the employee account will flow into the enterprise account.
  • the operator of the enterprise account that is, the first application account bound to the enterprise account of the second application, may be a team member of the first application team. You can use your first application account to log in to the second application enterprise account (the only login method that is not an enterprise account), and the relationship will be inherited by other users after the first application user leaves
  • the employee account operator that is, the first application account bound to the enterprise employee account of the second application, can use his first application account to log in to the enterprise employee account (in some application scenarios, it can be an employee account), the real-name user of the enterprise employee account of the second application, after resignation, the binding relationship will be inherited by other users in the first application.
  • the first application can be used as an entry for creating, managing, and logging in, and the enterprise employee number in the second application needs to be bound with the first application account before use.
  • FIG. 3 shows an account relationship diagram applicable to some embodiments of the present application.
  • the first application team may be bound to the second application team (which may be called an enterprise number), and the binding relationship may be one-to-one or one-to-many.
  • the first application team can be bound with the first application account.
  • the second application team can be bound with the second application account (which can be called an enterprise employee number) (the binding operation can be performed, for example, by a user in the first application team who has permission to operate in the first application interface).
  • the first application account can be bound with the second application account, or can be bound with the second application team.
  • FIG. 4 shows a binding process between the first application team and the second application team.
  • the binding process between the first application team and the second application team may include: the administrator of the first application team clicks "Add Enterprise Number" in the "Enterprise Account Management" module of the management background; then, enter the enterprise ID to search for the enterprise number (For example, precise search may be included), and abnormal situations may occur during the search process: not found, and the enterprise number does not meet the binding requirements.
  • the enterprise account verification paralleled with the first application can be understood as the server or client of the second application.
  • the enterprise number can be understood as the second enterprise team in the second application.
  • the verification file upload entry can be displayed, and the application binding can be triggered after the verification file is uploaded.
  • the second application account bound to the second application team (also referred to as the enterprise employee number bound to the enterprise number) can be initiated by the administrator of the first application team in the first application to create, For binding, logout.
  • FIG. 6 shows a schematic diagram of creating a second application account in the first application.
  • the enterprise number paralleled with the first application can be understood as the server or client of the second application; the enterprise number review paralleled with the first application can be understood as the electronic device for reviewing the application related to the binding of the enterprise number .
  • the business center can be understood as an electronic device that supports the creation of employee numbers.
  • the administrator of the first application team can create multiple second application accounts at one time. For each second application account, one or more team members of the first application team may be bound to the second application account.
  • the administrator of the first application team may set the first application member as the operator of the second application account (ie bind with the second application account). Operational permissions can be inherited among first application team members. After the second application account is created, the default operator is the user of the first application selected during creation, and there is no need for repeated operations.
  • FIG. 7 shows a schematic diagram of a first application account that is not bound to a second application account in the first application.
  • you can click the "Modify Settings" control in the first application and re-select the operator of the enterprise employee account (re-bind the first application account).
  • the administrator of the first application team needs to complete, for example, SMS verification.
  • SMS verification is passed, the robot reminder is automatically triggered, and the first app user bound to the second app enterprise employee number signs an agreement, completes real-name authentication, and submits employment qualifications.
  • the real-name authentication and employment qualifications are reviewed by the second application enterprise account. After the review is passed, the operator officially completes the modification.
  • the enterprise number paralleled with the first application can be understood as the server or client of the second application; the enterprise number review paralleled with the first application can be understood as the electronic device for reviewing the application related to the binding of the enterprise number .
  • the first app applies for changing the binding, and can submit the corresponding materials for review by the enterprise account.
  • the enterprise account review can determine whether the review is passed, and if it passes or fails, the corresponding result can be returned.
  • the administrator of the first application team can manage the second application account in the first application.
  • the account list of the second application may be viewed, searched, screened for account information, and the like.
  • FIG. 5 shows a schematic diagram of the ability to configure an enterprise number for an employee number in the first application.
  • the first application can obtain some authorized capabilities of the enterprise number, and the first application can display the capability identifiers of these capabilities as authorization items in the first application.
  • the user selects some or all authorization items from the displayed authorization items, and sends them to the enterprise number of the second application to apply for authorization. If the authorization application is passed, the first application can receive a notification of successful authorization, and the employee number of the second application can obtain the permission to use the corresponding authorization capability.
  • the team administrator of the first application can modify the permission configuration of the enterprise employee number of the second application, add notes, and the like.
  • the first application user can perform some operations based on the bound second application account. For example, account information settings: the first app account needs to log in to the second app to complete the modification of basic information such as account avatar and name; account content and user operations: users of the first app can complete operations such as video shooting and message reply in the second app.
  • account information settings the first app account needs to log in to the second app to complete the modification of basic information such as account avatar and name
  • account content and user operations users of the first app can complete operations such as video shooting and message reply in the second app.
  • the present disclosure provides an embodiment of an interaction device, which corresponds to the method embodiment shown in FIG. 1 , and the device can specifically be applied to in various electronic devices.
  • the interaction device of this embodiment includes: a display unit 801 and a creation unit 802 .
  • the display unit is used to display the first application interface, wherein the first application interface includes the interface of the first application;
  • the creation unit is used to create a second application account in the first application interface, wherein the second The application account is used to log in to the second application.
  • the specific processing of the display unit 801 and the creation unit 802 of the interactive device and the technical effects brought about by them can refer to the relevant descriptions of step 101 and step 102 in the corresponding embodiment in FIG. 1 respectively, and will not be repeated here. .
  • the device is further configured to: bind the created second application account with team members in the target first application team, wherein the target first application team is the first application account system
  • the team in the first application account system includes team members.
  • the binding the created second application account to team members in the target first application team includes: selecting team members from the team members of the target first application team as the target A team member; bind the created second application account with the target team member.
  • the device is further configured to: release the binding between the team members in the target first application team and the second application account.
  • the device is further configured to: in response to the unbinding of the team member bound by the second application account from the target first application team, release the association between the second application account and the bound team member. Binding; displaying prompt information, wherein the prompt information is used to prompt to bind a new team member for the second application account.
  • the device is further configured to: perform a management operation on the created second application account on the first application interface, wherein the management operation includes at least one of the following: view, search and filter.
  • the created second application account is bound to the target second application team, wherein the target second application team is a team in the second application account system, and the teams in the second application account system include team member.
  • the creating the second application account in the first application interface includes: determining the target second application team bound to the target first application team, wherein the target first application team is related to the first application team An application interface association; in the first application interface, create a second application account belonging to the target second application team.
  • the device before determining the target second application team bound to the target first application team, is further configured to: in the first application interface, receive the second application team identifier input by the user; The second application team identifier, sending a first binding request, wherein the first binding request is used to request the binding target first application team and the second application team indicated by the second application team identifier input by the user; Based on the verification result of the first binding request, it is determined whether to bind the target first application team associated with the first application interface and the second application team indicated by the second application team identifier input by the user.
  • the step of verifying the first binding request includes: verifying whether the subject corresponding to the target first application team and the subject corresponding to the second application team identifier input by the user are the same; The application sends a binding confirmation notification to the management user corresponding to the second application team identifier; based on the confirmation operation on the binding confirmation notification, it is confirmed that the verification of the first binding request is passed.
  • the device before the determination of the target second application team bound to the target first application team, the device is further configured to: receive the first application team identifier input by the user in the second application interface; Send a second binding request according to the first application team identifier, where the second binding request is used to request the binding target second application team and the first application indicated by the first application team identifier input by the user Team: Based on the verification result of the second binding request, determine whether to bind the target second application team associated with the second application interface and the first application team indicated by the first application team identifier input by the user.
  • the device is further configured to: if the first application account currently logged into the first application has a bound second application account, in the first application, display the login entry of the second application; based on the The above login entry uses the second application account bound to the currently logged-in first application account to log in and display the second application interface.
  • the present disclosure provides an embodiment of an interaction device, which corresponds to the method embodiment shown in FIG. 1 .
  • the device can be applied to in various electronic devices.
  • the interaction device in this embodiment includes: a configuration unit 901 .
  • the configuration unit is used for configuring the unit, used for configuring the permissions of the second team members of the second application team in the first application interface, wherein the first application team associated with the first application interface and the second application team Team bonding.
  • step 201 for the specific processing of the configuration unit 901 of the interaction device and the technical effects brought about by it, reference may be made to the relevant description of step 201 in the embodiment corresponding to FIG. 2 , and details are not repeated here.
  • configuring the permissions of the second team members of the second application team in the first application interface includes: displaying the preset first permission identifier of the second application team in the first application interface, The preset first authority identifier indicates the team authority possessed by the second team; according to the selection operation on the displayed preset first authority identifier, a first authorization request is sent according to the selected first authority identifier; based on the first authorization The authorization result of the request determines the preset first authority possessed by the second team member.
  • the device is further configured to: in the first application interface, receive a second application team identifier input by the user; send a first binding request according to the second application team identifier, wherein the The first binding request is used to request to bind the target first application team and the second application team indicated by the second application team identifier input by the user; determine whether to bind the first application based on the verification result of the first binding request The target first application team associated with the interface and the second application team indicated by the second application team identifier input by the user.
  • the step of verifying the first binding request includes: verifying whether the subject corresponding to the target first application team and the subject corresponding to the second application team identifier input by the user are the same; The application sends a binding confirmation notification to the management user corresponding to the second application team identifier; based on the confirmation operation on the binding confirmation notification, it is confirmed that the verification of the first binding request is passed.
  • FIG. 10 shows an exemplary system architecture in which the interaction method of an embodiment of the present disclosure can be applied.
  • the system architecture may include terminal devices 1001 , 1002 , and 1003 , a network 1004 , and a server 1005 .
  • the network 1004 is used as a medium for providing communication links between the terminal devices 1001 , 1002 , 1003 and the server 1005 .
  • Network 1004 may include various connection types, such as wire, wireless communication links, or fiber optic cables, among others.
  • the terminal devices 1001, 1002, 1003 can interact with the server 1005 through the network 1004 to receive or send messages and the like.
  • Various client applications can be installed on the terminal devices 1001, 1002, and 1003, such as web browser applications, search applications, and news information applications.
  • the client applications in the terminal devices 1001, 1002, and 1003 can receive instructions from users, and complete corresponding functions according to instructions from users, for example, add corresponding information to information according to instructions from users.
  • the terminal devices 1001, 1002, and 1003 may be hardware or software.
  • the terminal devices 1001, 1002, and 1003 may be various electronic devices with display screens and supporting web browsing, including but not limited to smartphones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, moving picture expert compression standard audio layer 3), MP4 (Moving Picture Experts Group Audio Layer IV, moving picture expert compression standard audio layer 4) player, laptop portable computer and desktop computer, etc.
  • the terminal devices 1001, 1002, and 1003 are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules (such as software or software modules for providing distributed services), or as a single software or software module. No specific limitation is made here.
  • the server 1005 may be a server providing various services, for example, receiving information acquisition requests sent by the terminal devices 1001, 1002, and 1003, and obtaining display information corresponding to the information acquisition requests in various ways according to the information acquisition requests. And the relevant data showing the information is sent to the terminal devices 1001, 1002, 1003.
  • the interaction method provided by the embodiments of the present disclosure may be executed by a terminal device, and correspondingly, the interaction means may be set in the terminal devices 1001 , 1002 , and 1003 .
  • the interaction method provided by the embodiment of the present disclosure may also be executed by the server 1005 , and accordingly, the interaction device may be set in the server 1005 .
  • terminal devices, networks and servers in FIG. 10 are only illustrative. According to the implementation needs, there can be any number of terminal devices, networks and servers.
  • FIG. 11 it shows a schematic structural diagram of an electronic device (such as the terminal device or server in FIG. 10 ) suitable for implementing the embodiments of the present disclosure.
  • the terminal equipment in the embodiment of the present disclosure may include but not limited to such as mobile phone, notebook computer, digital broadcast receiver, PDA (personal digital assistant), PAD (tablet computer), PMP (portable multimedia player), vehicle terminal (such as mobile terminals such as car navigation terminals) and fixed terminals such as digital TVs, desktop computers and the like.
  • the electronic device shown in FIG. 11 is only an example, and should not limit the functions and application scope of the embodiments of the present disclosure.
  • an electronic device may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 1101, which may be stored in a read-only memory (ROM) 1102 according to a program or loaded into a random access memory from a storage device 1108. (RAM) 1103 to execute various appropriate actions and processing. In the RAM 1103, various programs and data necessary for the operation of the electronic device 1100 are also stored.
  • the processing device 1101, the ROM 1102, and the RAM 1103 are connected to each other through a bus 1104.
  • An input/output (I/O) interface 1105 is also connected to the bus 1104 .
  • the following devices can be connected to the I/O interface 1105: input devices 1106 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; including, for example, a liquid crystal display (LCD), speaker, vibration an output device 11011 such as a computer; a storage device 1108 including, for example, a magnetic tape, a hard disk, and the like; and a communication device 1109 .
  • the communication means 1109 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. While FIG. 11 shows an electronic device having various means, it is to be understood that implementing or having all of the means shown is not a requirement. More or fewer means may alternatively be implemented or provided.
  • embodiments of the present disclosure include a computer program product, which includes a computer program carried on a non-transitory computer readable medium, where the computer program includes program code for executing the method shown in the flowchart.
  • the computer program may be downloaded and installed from a network via communication means 1109, or from storage means 1108, or from ROM 1102.
  • the processing device 1101 the above-mentioned functions defined in the methods of the embodiments of the present disclosure are executed.
  • the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two.
  • a computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can transmit, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device .
  • Program code embodied on a computer readable medium may be transmitted by any appropriate medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.
  • the client and the server can communicate using any currently known or future network protocols such as HTTP (HyperText Transfer Protocol, Hypertext Transfer Protocol), and can communicate with digital data in any form or medium
  • HTTP HyperText Transfer Protocol
  • the communication eg, communication network
  • Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), internetworks (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network of.
  • the above-mentioned computer-readable medium may be included in the above-mentioned electronic device, or may exist independently without being incorporated into the electronic device.
  • the above computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device: displays a first application interface, wherein the first application interface includes an interface of the first application ; In the first application interface, create a second application account, where the second application account is used to log in to the second application.
  • the electronic device is further configured to: bind the created second application account with team members in the target first application team, wherein the target first application team is the first application account
  • the team in the system, the team in the first application account system includes team members.
  • the binding the created second application account to team members in the target first application team includes: selecting team members from the team members of the target first application team as the target A team member; bind the created second application account with the target team member.
  • the electronic device is further configured to: release the binding between the team members in the target first application team and the second application account.
  • the electronic device is further configured to: in response to unbinding the team member bound by the second application account from the target first application team, untie the relationship between the second application account and the bound team member. Binding; displaying prompt information, wherein the prompt information is used to prompt to bind a new team member for the second application account.
  • the electronic device is further configured to: perform a management operation on the created second application account on the first application interface, wherein the management operation includes at least one of the following: view, search and filter.
  • the created second application account is bound to the target second application team, wherein the target second application team is a team in the second application account system, and the teams in the second application account system include team member.
  • the creating the second application account in the first application interface includes: determining the target second application team bound to the target first application team, wherein the target first application team is related to the first application team An application interface association; in the first application interface, create a second application account belonging to the target second application team.
  • the electronic device before determining the target second application team bound to the target first application team, is further configured to: in the first application interface, receive the second application team identifier input by the user; The second application team identifier sends a first binding request, wherein the first binding request is used to request the binding target first application team and the second application team indicated by the second application team identifier input by the user ; Based on the verification result of the first binding request, determine whether to bind the target first application team associated with the first application interface and the second application team indicated by the second application team identifier input by the user.
  • the step of verifying the first binding request includes: verifying whether the subject corresponding to the target first application team and the subject corresponding to the second application team identifier input by the user are the same; The application sends a binding confirmation notification to the management user corresponding to the second application team identifier; based on the confirmation operation on the binding confirmation notification, it is confirmed that the verification of the first binding request is passed.
  • the electronic device before the determination of the target second application team bound to the target first application team, is further configured to: in the second application interface, receive the first application team identifier input by the user ; According to the first application team identifier, send a second binding request, wherein the second binding request is used to request the binding target second application team and the first application team identifier input by the user indicated by the first Application team: Based on the verification result of the second binding request, determine whether to bind the target second application team associated with the second application interface and the first application team indicated by the first application team identifier input by the user.
  • the electronic device is further configured to: if the first application account currently logged into the first application has a bound second application account, display the login entry of the second application in the first application;
  • the login portal uses the second application account bound to the currently logged-in first application account to log in and display the second application interface.
  • the above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the electronic device, the electronic device: in the first application interface, configures the Permissions, wherein the first application team associated with the first application interface is bound to the second application team.
  • configuring the permissions of the second team members of the second application team in the first application interface includes: displaying the preset first permission identifier of the second application team in the first application interface, The preset first authority identifier indicates the team authority possessed by the second team; according to the selection operation on the displayed preset first authority identifier, a first authorization request is sent according to the selected first authority identifier; based on the first authorization The authorization result of the request determines the preset first authority possessed by the second team member.
  • the electronic device is further configured to: in the first application interface, receive a second application team identifier input by the user; send a first binding request according to the second application team identifier, wherein the The first binding request is used to request to bind the target first application team and the second application team indicated by the second application team identifier input by the user; based on the verification result of the first binding request, determine whether to bind the first application team The target first application team associated with the application interface and the second application team indicated by the second application team identifier input by the user.
  • the step of verifying the first binding request includes: verifying whether the subject corresponding to the target first application team and the subject corresponding to the second application team identifier input by the user are the same; The application sends a binding confirmation notification to the management user corresponding to the second application team identifier; based on the confirmation operation on the binding confirmation notification, it is confirmed that the verification of the first binding request is passed.
  • Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, or combinations thereof, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and Includes conventional procedural programming languages - such as the "C" language or similar programming languages.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as through an Internet service provider). Internet connection).
  • LAN local area network
  • WAN wide area network
  • Internet service provider such as AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • each block in a flowchart or block diagram may represent a module, program segment, or portion of code that contains one or more logical functions for implementing specified executable instructions.
  • the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved.
  • each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations can be implemented by a dedicated hardware-based system that performs the specified functions or operations , or may be implemented by a combination of dedicated hardware and computer instructions.
  • the units involved in the embodiments described in the present disclosure may be implemented by software or by hardware. Wherein, the name of the unit does not constitute a limitation of the unit itself under certain circumstances, for example, the creating unit may also be described as “the unit for creating the second application account”.
  • FPGAs Field Programmable Gate Arrays
  • ASICs Application Specific Integrated Circuits
  • ASSPs Application Specific Standard Products
  • SOCs System on Chips
  • CPLD Complex Programmable Logical device
  • a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device.
  • a machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium.
  • a machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing.
  • machine-readable storage media would include one or more wire-based electrical connections, portable computer discs, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read only memory
  • EPROM or flash memory erasable programmable read only memory
  • CD-ROM compact disk read only memory
  • magnetic storage or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Tourism & Hospitality (AREA)
  • Data Mining & Analysis (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Hardware Design (AREA)
  • Human Computer Interaction (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)

Abstract

一种交互方法、装置和电子设备。方法包括：展示第一应用界面（101），其中，第一应用界面包括第一应用的界面；在第一应用界面中，创建第二应用账户（102），其中，所述第二应用账户用于登录第二应用。由此，提供了一种新的交互方式。

Description

交互方法、装置和电子设备
相关申请的交叉引用
本申请要求于2021年09月07日提交的，申请号为202111046967.X、发明名称为“交互方法、装置和电子设备”的中国专利申请的优先权，该申请的全文通过引用结合在本申请中。
技术领域
本公开涉及计算机技术领域，尤其涉及一种交互方法、装置和电子设备。
背景技术
随着计算机的发展，用户可以使用电子设备实现各种功能。例如，用户可以使用电子设备进行线上办公，也可以使用电子设备观看各种视频。
在一些场景中，视频类应用作为内容平台，可以向广大用户提供各种内容。
发明内容
提供该公开内容部分以便以简要的形式介绍构思，这些构思将在后面的具体实施方式部分被详细描述。该公开内容部分并不旨在标识要求保护的技术方案的关键特征或必要特征，也不旨在用于限制所要求的保护的技术方案的范围。
第一方面，本公开实施例提供了一种交互方法，该方法包括： 展示第一应用界面，其中，第一应用界面包括第一应用的界面；在第一应用界面中，创建第二应用账户，其中，所述第二应用账户用于登录第二应用。
第二方面，本公开实施例提供了一种交互方法，该方法包括：在第一应用界面中，配置目标第二应用团队的第二团队成员的权限，其中，第一应用界面所关联的目标第一应用团队，与目标第二应用团队绑定。
第三方面，本公开实施例提供了一种交互装置，包括：选展示单元，用于展示第一应用界面，其中，第一应用界面包括第一应用的界面；创建单元，用于在第一应用界面中，创建第二应用账户，其中，所述第二应用账户用于登录第二应用。
第四方面，本公开实施例提供了一种交互装置，包括：配置单元，用于在第一应用界面中，配置目标第二应用团队的第二团队成员的权限，其中，第一应用界面所关联的目标第一应用团队，与目标第二应用团队绑定。
第五方面，本公开实施例提供了一种电子设备，包括：一个或多个处理器；存储装置，用于存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如第一方面或者第二方面所述的交互方法。
第六方面，本公开实施例提供了一种计算机可读介质，其上存储有计算机程序，该程序被处理器执行时实现如第一方面或者第二方面所述的交互方法的步骤。
附图说明
结合附图并参考以下具体实施方式，本公开各实施例的上述和其他特征、优点及方面将变得更加明显。贯穿附图中，相同或相似的附图标记表示相同或相似的元素。应当理解附图是示意性的，原件和元素不一定按照比例绘制。
图1是根据本公开的交互方法的一个实施例的流程图；
图2是根据本公开的另一种交互方法的一个实施例的流程图；
图3是根据本公开的交互方法的一个应用场景的示意图；
图4是根据本公开的交互方法的一个应用场景的示意图；
图5是根据本公开的交互方法的一个应用场景的示意图；
图6是根据本公开的交互方法的一个应用场景的示意图；
图7是根据本公开的交互方法的一个应用场景的示意图；
图8是根据本公开的交互装置的一个实施例的结构示意图；
图9是根据本公开的另一种交互装置的一个实施例的结构示意图；
图10是本公开的一个实施例的交互方法可以应用于其中的示例性系统架构；
图11是根据本公开实施例提供的电子设备的基本结构的示意图。
具体实施方式
下面将参照附图更详细地描述本公开的实施例。虽然附图中显示了本公开的某些实施例，然而应当理解的是，本公开可以通过各种形式来实现，而且不应该被解释为限于这里阐述的实施例，相反提供这些实施例是为了更加透彻和完整地理解本公开。应当理解的是，本公开的附图及实施例仅用于示例性作用，并非用于限制本公开的保护范围。
应当理解，本公开的方法实施方式中记载的各个步骤可以按照不同的顺序执行，和/或并行执行。此外，方法实施方式可以包括附加的步骤和/或省略执行示出的步骤。本公开的范围在此方面不受限制。
本文使用的术语“包括”及其变形是开放性包括，即“包括但不限于”。术语“基于”是“至少部分地基于”。术语“一个实施例”表示“至少一个实施例”；术语“另一实施例”表示“至少一个另外的实施例”；术语“一些实施例”表示“至少一些实施例”。其他术语的相关定义将在下文描述中给出。
需要注意，本公开中提及的“第一”、“第二”等概念仅用 于对不同的装置、模块或单元进行区分，并非用于限定这些装置、模块或单元所执行的功能的顺序或者相互依存关系。
需要注意，本公开中提及的“一个”、“多个”的修饰是示意性而非限制性的，本领域技术人员应当理解，除非在上下文另有明确指出，否则应该理解为“一个或多个”。
本公开实施方式中的多个装置之间所交互的消息或者信息的名称仅用于说明性的目的，而并不是用于对这些消息或信息的范围进行限制。
请参考图1，其示出了根据本公开的交互方法的一个实施例的流程。如图1所示该交互方法，包括以下步骤：
步骤101，展示第一应用界面。
在本实施例中，交互方法的执行主体(例如服务器和/或终端设备)可以展示第一应用界面。
在这里，第一应用界面可以包括第一应用的任意界面。
步骤102，在第一应用界面中，创建第二应用账户。
在这里，第二应用账户用于登录第二应用。
可以理解，第一应用和第二应用的具体类型，可以实际应用场景设置，在此不做限定。作为示例，第一应用可以包括办公类应用，第二应用可以包括视频播放类应用；作为示例，可以办公类应用中，建立视频播放类应用的账号。
需要说明的是，创建第二应用账户，以及后续的对第二应用账户进行管理，由用户在第一应用中发起操作。
需要说明的是，本实施例提供的交互方法，通过在第一应用中创建第二应用账户，可以提供新的创建第二应用账户的途径。此外，若用户在使用第一应用的过程中，有创建第二应用账户的需求，不必跳转到第二应用中执行账户创建的操作，提高了用户的操作效率。进一步地，若用户存在创建多个第二应用账户的需求，可以在第一应用界面实现批量的第二应用账户的创建，从而进一步提升用户创建用于在第二应用中使用的账户的操作效率。
对比来说，在一些相关技术中，可能会采用两个应用的账号 之间可以消息互发的技术路径，实现两个应用的互通。但是，相关技术中两个可以互发消息的账号，均为在各自的应用中独立创建的账号，每个应用中的账号在本应用中保持独立，不能由本应用之外的其它应用对此账号进行创建或者管理等的操作。
在一些实施例中，所述方法还包括：将所创建的第二应用账户，与目标第一应用团队中的团队成员绑定。
在这里，目标第一应用团队为第一应用账户体系中的团队，第一应用账户体系中的团队包括团队成员。
作为示例，第一应用账号体系中可能包括多个团队。例如，团队甲和团队乙。团队甲中可以包括成员小王和小张。团队乙中可以包括成员小李和小刘。
作为示例，可以将所创建的第二应用账户(例如账户名为A公司前台)，与团队甲中的小王绑定。
可以理解的是，在第一应用界面创建第二应用账户时，执行创建操作的创建者可以是某个团队中具有操作权限的用户(例如，管理员)。
在一些实施例中，所述将所创建的第二应用账户，与目标第一应用团队中的团队成员绑定，包括：从所述目标第一应用团队的团队成员中，选取团队成员作为目标团队成员；绑定所创建的第二应用账户和所述目标团队成员。
在这里，在创建第二应用账户之后，可以从第一应用团队中选取团队成员，与第二应用账户进行绑定。作为示例，在创建第二应用账户后，可以从团队甲中，选取小王作为目标团队成员，与所创建的第二应用账户“A公司前台”进行绑定。
在一些实施例中，所述方法还包括：解除目标第一应用团队中的团队成员与第二应用账户之间的绑定。
在这里，还可以解除团队成员与第二应用账户之间的绑定。作为示例，可以解除团队甲中小王与所创建的第二应用账户“A公司前台”之间的绑定。
在一些实施例中，团队成员与第二应用账户之间的解除绑定， 可以由第一应用团队的管理员(例如团队甲的管理员)操作，也可以由与第二应用绑定的第一团队成员(例如团队甲中的小王)操作。
在一些实施例中，所述方法还包括：响应于第二应用账户所绑定的团队成员与目标第一应用团队解除绑定，解除第二应用账户与所绑定的团队成员之间的绑定；展示提示信息，其中，所述提示信息用于提示为第二应用账户绑定新的团队成员。
在团队成员与第一应用团队解除绑定时，可以自动将该团队成员所绑定的第二应用账户与第一应用团队之间解绑。然后，可以展示提示信息，以提示用户为第二应用账户重新绑定第一应用团队的团队成员。
作为示例，第一应用中的团队甲中的小王，与第二应用中的A公司前台，之间具有绑定关系。如果第一团队甲中的小王与团队甲解除绑定(例如小王从团队甲中离职)，可以接触A公司前台与小王之间的绑定关系。这个时候，可以理解为，第二应用中的A公司前台与团队甲中的某个成员解除绑定关系，但是与团队甲之间保持绑定关系，可以为第二应用中的A公司前台绑定新的团队甲中的成员。
需要说明的是，通过将第二应用账户与第一应用团队的团队成员绑定，可以将第二应用账户作为一个壳子，通过绑定关系这种可变关系，实现在第二应用账户与不同第一应用团队中的成员之间实现灵活的绑定关系，实现第二应用账户被不同的第一团队成员复用。通俗来说，第二应用账户可以积累大量的用户和资源，如果第二应用账户的使用者离开第一应用团队，那么第二应用账户可以由第一应用团队中的其他成员继承(换绑定)，从而继承第二应用账户的用户和资源。
在一些实施例中，所述方法还包括：在第一应用界面，对所创建的第二应用账户进行管理操作，其中，所述管理操作包括以下至少一项：查看、搜索和筛选。
在一些实施例中，所创建的第二应用账户与目标第二应用团 队绑定。
在这里，所述目标第二应用团队为第二应用账户体系中的团队，第二应用账户体系中的团队包括团队成员。
作为示例，所创建的第二应用账号A公司前台，与目标第二应用团队A公司绑定。
需要说明的是，第二应用账号与目标第二应用团队绑定，可以提供对第二应用账号进行管理的基础，便于以第二应用团队为单元，对若干第二应用团队下的账号进行管理。
在一些实施例中，所述步骤102，可以包括：确定与目标第一应用团队绑定的目标第二应用团队，其中，目标第一应用团队与所述第一应用界面关联；在第一应用界面中，创建属于所述目标第二应用团队的第二应用账户。
在这里，目标第一应用团队可能与第二应用中的至少一个团队绑定。例如，第一应用中的甲公司，可能与第二应用中的A公司绑定。
在目标第一应用团队的第一应用界面，可以创建属于目标第二应用团队的第二应用账户。作为示例，第一应用界面属于第一应用团队甲公司，那么在第一应用界面中所创建的第二应用账户，可以自动绑定至甲公司所绑定的第二应用团队A公司，即在甲公司的应用界面中，自动为A公司创建第二应用账号(例如A公司前台)。
需要说明的是，在第一应用团队的第一应用界面，创建第二应用账户，所创建的第二应用账户自动绑定至第一应用团队所绑定的第二应用团队。由此，可以实现在第一应用界面自动为第二应用团队创建员工账户，减少用户手动进行绑定的操作和时间。
在一些实施例中，在确定与目标第一应用团队绑定的目标第二应用团队，其中之前，所述方法还包括：在第一应用界面中，接收用户输入的第二应用团队标识；根据所述第二应用团队标识，发送第一绑定请求；基于对第一绑定请求的验证结果，确定是否绑定第一应用界面所关联的目标第一应用团队和用户输入的第二 应用团队标识所指示第二应用团队。
在这里，所述第一绑定请求用于请求绑定目标第一应用团队和用户输入的第二应用团队标识所指示的第二应用团队。
作为示例，目标第一应用团队可以甲团队，在甲团队的第一应用界面中，用户可以输入第二应用团队标识(例如“公司B”)。可以根据第二应用团队标识(例如“公司B”)，发送第一绑定请求。第一绑定请求可以用于请求绑定团队甲和“公司B”所指示的公司。基于对第一绑定请求的验证结果，可以确定是否绑定团队甲和“公司B”所指示的公司。
在这里，对第一绑定请求的验证方式，可以根据实际应用场景设置，在此不做限定。
作为示例，验证方式可以对多个方面进行验证，例如团队甲和“公司B”所指示的公司，是否是同一主体；再例如，第二应用中“公司B”的管理员，是否同意绑定等。
需要说明的是，建立第一应用中第一团队，可以与第二应用中至少一个第二应用团队之间建立绑定关系。由此，可以实现基于第一应用团队对第二应用团队进行管理，提高对第二应用团队的团队成员的管理效率。
在一些实施例中，所述对所述第一绑定请求的验证步骤，包括：验证目标第一应用团队对应的主体和用户输入的第二应用团队标识对应的主体是否相同；如果相同，在第二应用中向第二应用团队标识对应的管理用户发送绑定确认通知；基于对所述绑定确认通知的确认操作，确认第一绑定请求验证通过。
在这里，主体可以理解为法律意义上的主体。例如，主体可以包括自然人、法人、非法人组织等。
在这里，请参考图4，图4中示出了对第一绑定请求进行验证的过程。
需要说明的是，对第一绑定请求的验证，可以包括对主体是否相同的验证，在验证主体相同之后，可以由第二应用团队的管理用户确认是否进行绑定。由此，可以实现将同一主体在不同平 台的账号绑定起来，便于同一主体进行管理。并且，第二应用团队的团队管理用户的确认绑定，可以由人类用户再次确定本次待实施的绑定无误，提高绑定的准确性。
在一些实施例中，所述方法还包括：在第二应用界面中，接收用户输入的第一应用团队标识；根据所述第一应用团队标识，发送第二绑定请求，其中，所述第二绑定请求用于请求绑定目标第二应用团队和用户输入的第一应用团队标识所指示的第一应用团队；基于对第二绑定请求的验证结果，确定是否绑定第二应用界面所关联的目标第二应用团队和用户输入的第一应用团队标识所指示第一应用团队。
在一些实施例中，所述方法还包括：如果当前登录第一应用的第一应用账户具有绑定的第二应用账户，在第一应用中，展示第二应用的登录入口；基于在所述登录入口使用当前登录的第一应用账户所绑定的第二应用账户登录，展示第二应用界面。
请参考图5，其示出了根据本公开的交互方法的一个实施例的流程。如图5所示该交互方法，包括以下步骤：
步骤501，在第一应用界面中，配置目标第二应用团队的第二团队成员的权限。
在这里，第一应用界面所关联的目标第一应用团队，与目标第二应用团队绑定。
在这里，第二应用团队可以称为企业号，第二团队成员可以称为企业员工号或者员工号。
第二应用团队可能具有一些功能工具，属于第二应用团队的第二团队成员，可以具有使用团队的部分或者全部功能工具的权限。
功能工具的种类可以根据实际应用场景设置，在此不做限定。作为示例，第二团队成员功能工具可以包括但是不限于以下至少一项：营销工具(例如购物车、留资组件)。
需要说明的是，在第一应用界面中，配置第二团队成员(即第二应用账户)的权限，可以实现在第一应用界面中管理第二应 用账户的权限，实现对第二应用账户的管理快捷管理。在用户使用第一应用的过程中，如果有对第二应用中的第二应用账户进行权限操作的需求，无需跳转到第二应用中进行操作。
在一些实施例中，可以对第二应用账户进行权限配置的入口，可以仅设置在第一应用中。由此，可以将对第二应用账户进行管理的权限收紧到第一应用中，避免第二应用账户出现权限滥用等问题。
在一些实施例中，所述在第一应用界面中，配置目标第二应用团队的第二团队成员的权限，包括：在第一应用界面中，展示目标第二应用团队的预设第一权限标识，预设第一权限标识指示第二应用团队所具有的团队权限；根据对所展示的预设第一权限标识的选择操作，根据所选择的第一权限标识发送第一授权请求；基于对第一授权请求的授权结果，确定所述第二团队成员所具有的预设第一权限。
第二应用团队可能具有一些功能工具，属于第二应用团队的第二团队成员，可以具有使用团队的部分或者全部功能工具的权限。
功能工具的种类可以根据实际应用场景设置，在此不做限定。
作为示例，第二团队成员功能工具可以包括但是不限于以下至少一项：营销工具(例如购物车、留资组件)。
由此，可以第二团队成员可以继承一些第二团队的团队权限，便于第二团队成员进行一些活动，例如对企业业务在公域流量范围内进行一些解释说明。从而，可以提高第二团队成员推进团队相关事务的效率。
在一些实施例中，所述方法还包括：在第一应用界面中，接收用户输入的第二应用团队标识；根据所述第二应用团队标识，发送第一绑定请求，其中，所述第一绑定请求用于请求绑定目标第一应用团队和用户输入的第二应用团队标识所指示的第二应用团队；基于对第一绑定请求的验证结果，确定是否绑定第一应用界面所关联的目标第一应用团队和用户输入的第二应用团队标识 所指示第二应用团队。
在一些实施例中，对所述第一绑定请求进行验证的验证步骤，包括：验证目标第一应用团队对应的主体和用户输入的第二应用团队标识对应的主体是否相同；如果相同，在第二应用中向第二应用团队标识对应的管理用户发送绑定确认通知；基于对所述绑定确认通知的确认操作，确认第一绑定请求验证通过。
在一些应用场景中，存在一些账号使用痛点，例如，第一，越规模化的账号矩阵运营，存在越大的人员流动风险：企业员工使用私人账号运营，企业无法完全管控账号和资产，当员工离职或工作变动时，账号资产、数据企业无法继承。第二，需要若干账号运营，但具备运营能力的企业号额度有限，企业需要的运营能力不足。第三，数据缺失，难以精细化运营：企业无法完全掌握私人账号和不同主体企业账号的经营数据，无法满足数据统一汇总、精细化运营需求。
在一些实施例中，上述第二应用可以属于公域流量应用。
在这里，由于公域流量特点(以内容为核心分配流量，只要做好内容就能获得流量，不会受到原始积累干扰)，企业通过公域流量账号矩阵可以更好地实现线上低成本获客(相比广告投放更低成本、相比即时通信应用等私域更容易获客)。
在本申请的一些实施例中，在第二应用中，可以新增一种归属权属于企业的账号类型，例如可以称为企业员工号。企业员工号可以实现账号资产的继承，为精细化运营需要的数据开放能力提供基础，可以有较多员工号额度。
在一些实施例中，第二应用中第二应用团队，也可以称为企业号，企业号可以基于线上企业号工具能力，授权给企业员工号使其也具备相应工具能力；执行与第一应用团队的账号绑定、创建企业员工号的审核。
在一些实施例中，需要新增企业员工号账号类型：关联企业号之后的第一应用团队可以开通N个权限归属于企业的企业员工号，将企业号的营销能力授权给企业员工号员工账号，员工账 号的各类数据会流入企业号。
在一些应用场景中，企业号运营者，即与第二应用的企业号绑定的第一应用账户，可以是第一应用团队的团队成员。可以用自己的第一应用账号登录第二应用企业号(非企业号的唯一登录方式)，第一应用用户离职后关联关系会被其他用户继承
在一些应用场景中，员工号运营者，即与第二应用的企业员工号绑定的第一应用账户，可以用自己的第一应用账号登录企业员工号(在一些应用场景中，可以是员工号的唯一登录方式)，第二应用的企业员工号的实名用户，离职后绑定关系会被第一应用中的其他用户继承。
在本申请的一些实施例中，第一应用可以作为创建、管理、登录的入口，第二应用中的企业员工号需要和第一应用账号绑定之后再使用。
作为示例，请参考图3，图3中示出了本申请一些实施例可以适应的账号关系图。
在图3中，第一应用团队可以与第二应用团队(可以称为企业号)进行绑定，绑定关系可以是一对一或者一对多。第一应用团队可以第一应用账号进行绑定。第二应用团队可以与第二应用账号(可以称为企业员工号)进行绑定(绑定操作例如可以由第一应用团队中有权限操作的用户在第一应用界面中执行)。第一应用账号可以与第二应用账号绑定，也可以与第二应用团队进行绑定。
在一些实施例中，请参考图4，图4示出了第一应用团队与第二应用团队的绑定过程。第一应用团队和第二应用团队的绑定过程，可以包括：第一应用团队的管理员在管理后台“企业号管理”模块点击“新增企业号”；然后，输入企业号ID搜索企业号(例如，可以包括精确搜索)，搜索的过程可能出现异常情况：未搜索到、企业号不符合绑定要求。
在图4中，与第一应用并列的企业号审核，可以理解为第二应用的服务端或者客户端。企业号可以理解为第二应用中的第二 企业团队。
在一些实施例中，如果输入的企业号主体和第一应用团队的主体一致，可以点击申请绑定。
在一些实施例中，如果企业号主体和第一团队主体的不一致，可以展示验证文件上传入口，可以在上传验证文件后触发申请绑定。
在一些实施例中，与第二应用团队绑定的第二应用账户(也可以称为与企业号绑定的企业员工号)，可以由第一应用团队的管理员在第一应用发起创建、换绑定、注销。
在一些实施例中，请参考图6，图6示出了在第一应用中创建第二应用账户的示意图。在图6中，与第一应用并列的企业号，可以理解为第二应用的服务端或者客户端；与第一应用并列的企业号审核，可以理解为审核企业号绑定相关申请的电子设备。业务中台，可以理解为支持员工号创建的电子设备。
第一应用团队的管理员可以一次性创建多个第二应用账号。针对每个第二应用账号，可以为该第二应用账号绑定一个或者多个第一应用团队的团队成员。
在一些应用场景中，第一应用团队的管理员可以将第一应用成员设置为第二应用账户的运营者(即与第二应用账户绑定)。运营权限可以在第一应用团队成员之间继承。第二应用账号创建后，默认运营者即为创建时选择的第一应用用户，无需重复操作。
在一些实施例中，请参考图7，图7示出了第一应用中未第二应用账户更换绑定的第一应用账户的示意图。在一些应用场景中，换绑定，可以点击第一应用中的“修改设置”控件，重新选择企业员工号运营者(重新绑定第一应用账号)。确认修改后，第一应用团队管理员需要完成例如短信验证。短信验证通过后，自动触发机器人提醒，第二应用企业员工号所绑定的第一应用用户签署协议、完成实名认证、雇佣资质提交。实名认证和雇佣资质由第二应用企业号审核，审核通过之后，运营者正式完成修改。
在图7中，与第一应用并列的企业号，可以理解为第二应用 的服务端或者客户端；与第一应用并列的企业号审核，可以理解为审核企业号绑定相关申请的电子设备。第一应用申请换绑，可以提交相应材料供企业号审核。企业号审核可以判断审核是否通过，如果通过或者不通过，均可以传回相应结果。
在一些实施例中，第一应用团队的管理员可以在第一应用中对第二应用账户进行管理。例如，可以对第二应用账户列表进行查看、搜索、筛选账号信息等。
在一些实施例中，请参考图5，图5示出了在第一应用中为员工号配置企业号所具有的能力的示意图。第一应用可以获取企业号的一些可授权的能力，第一应用可以将这些能力的能力标识作为授权项展示在第一应用中。用户从所展示的授权项中选择部分或全部授权项，发送至第二应用的企业号进行授权申请。如果授权申请通过，那么第一应用可以接收到授权成功通知，第二应用的员工号获取到使用相应授权能力的权限。
在一些实施例中，第一应用团队管理员可以修改第二应用的企业员工号的权限配置、添加备注等。
在一些实施例中，第一应用用户可以基于所绑定的第二应用账户，进行一些操作。例如，账号信息设置：第一应用账户需要登录第二应用完成账号头像、名称等基础信息修改；账号内容和用户运营：第一应用用户，可以第二应用内完成视频拍摄和消息回复等操作。
进一步参考图8，作为对上述各图所示方法的实现，本公开提供了一种交互装置的一个实施例，该装置实施例与图1所示的方法实施例相对应，该装置具体可以应用于各种电子设备中。
如图8所示，本实施例的交互装置包括：展示单元801和创建单元802。其中，展示单元，用于展示第一应用界面，其中，第一应用界面包括第一应用的界面；创建单元，用于在第一应用界面中，创建第二应用账户，其中，所述第二应用账户用于登录第二应用。
在本实施例中，交互装置的展示单元801和创建单元802的具体处理及其所带来的技术效果可分别参考图1对应实施例中步骤101、步骤102的相关说明，在此不再赘述。
在一些实施例中，所述装置还用于：将所创建的第二应用账户，与目标第一应用团队中的团队成员绑定，其中，所述目标第一应用团队为第一应用账户体系中的团队，第一应用账户体系中的团队包括团队成员。
在一些实施例中，所述将所创建的第二应用账户，与目标第一应用团队中的团队成员绑定，包括：从所述目标第一应用团队的团队成员中，选取团队成员作为目标团队成员；绑定所创建的第二应用账户和所述目标团队成员。
在一些实施例中，所述装置还用于：解除目标第一应用团队中的团队成员与第二应用账户之间的绑定。
在一些实施例中，所述装置还用于：响应于第二应用账户所绑定的团队成员与目标第一应用团队解除绑定，解除第二应用账户与所绑定的团队成员之间的绑定；展示提示信息，其中，所述提示信息用于提示为第二应用账户绑定新的团队成员。
在一些实施例中，所述装置还用于：在第一应用界面，对所创建的第二应用账户进行管理操作，其中，所述管理操作包括以下至少一项：查看、搜索和筛选。
在一些实施例中，所创建的第二应用账户与目标第二应用团队绑定，其中，所述目标第二应用团队为第二应用账户体系中的团队，第二应用账户体系中的团队包括团队成员。
在一些实施例中，所述在第一应用界面中，创建第二应用账户，包括：确定与目标第一应用团队绑定的目标第二应用团队，其中，目标第一应用团队与所述第一应用界面关联；在第一应用界面中，创建属于目标第二应用团队的第二应用账户。
在一些实施例中，在确定与目标第一应用团队绑定的目标第二应用团队之前，所述装置还用于：在第一应用界面中，接收用户输入的第二应用团队标识；根据所述第二应用团队标识，发送 第一绑定请求，其中，所述第一绑定请求用于请求绑定目标第一应用团队和用户输入的第二应用团队标识所指示的第二应用团队；基于对第一绑定请求的验证结果，确定是否绑定第一应用界面所关联的目标第一应用团队和用户输入的第二应用团队标识所指示第二应用团队。
在一些实施例中，对所述第一绑定请求的验证步骤，包括：验证目标第一应用团队对应的主体和用户输入的第二应用团队标识对应的主体是否相同；如果相同，在第二应用中向第二应用团队标识对应的管理用户发送绑定确认通知；基于对所述绑定确认通知的确认操作，确认第一绑定请求验证通过。
在一些实施例中，在所述确定与目标第一应用团队绑定的目标第二应用团队之前，所述装置还用于：在第二应用界面中，接收用户输入的第一应用团队标识；根据所述第一应用团队标识，发送第二绑定请求，其中，所述第二绑定请求用于请求绑定目标第二应用团队和用户输入的第一应用团队标识所指示的第一应用团队；基于对第二绑定请求的验证结果，确定是否绑定第二应用界面所关联的目标第二应用团队和用户输入的第一应用团队标识所指示第一应用团队。
在一些实施例中，所述装置还用于：如果当前登录第一应用的第一应用账户具有绑定的第二应用账户，在第一应用中，展示第二应用的登录入口；基于在所述登录入口使用当前登录的第一应用账户所绑定的第二应用账户登录，展示第二应用界面。
进一步参考图9，作为对上述各图所示方法的实现，本公开提供了一种交互装置的一个实施例，该装置实施例与图1所示的方法实施例相对应，该装置具体可以应用于各种电子设备中。
如图9所示，本实施例的交互装置包括：配置单元901。其中，配置单元，用于配置单元，用于在第一应用界面中，配置第二应用团队的第二团队成员的权限，其中，第一应用界面所关联的第一应用团队，与第二应用团队绑定。
在本实施例中，交互装置的配置单元901的具体处理及其所带来的技术效果可分别参考图2对应实施例中步骤201的相关说明，在此不再赘述。
在一些实施例中，所述在第一应用界面中，配置第二应用团队的第二团队成员的权限，包括：在第一应用界面中，展示第二应用团队的预设第一权限标识，预设第一权限标识指示第二团队所具有的团队权限；根据对所展示的预设第一权限标识的选择操作，根据所选择的第一权限标识发送第一授权请求；基于对第一授权请求的授权结果，确定第二团队成员所具有的预设第一权限。
在一些实施例中，所述装置还用于：在第一应用界面中，接收用户输入的第二应用团队标识；根据所述第二应用团队标识，发送第一绑定请求，其中，所述第一绑定请求用于请求绑定目标第一应用团队和用户输入的第二应用团队标识所指示的第二应用团队；基于对第一绑定请求的验证结果，确定是否绑定第一应用界面所关联的目标第一应用团队和用户输入的第二应用团队标识所指示第二应用团队。
在一些实施例中，对所述第一绑定请求的验证步骤，包括：验证目标第一应用团队对应的主体和用户输入的第二应用团队标识对应的主体是否相同；如果相同，在第二应用中向第二应用团队标识对应的管理用户发送绑定确认通知；基于对所述绑定确认通知的确认操作，确认第一绑定请求验证通过。
请参考图10，图10示出了本公开的一个实施例的交互方法可以应用于其中的示例性系统架构。
如图10所示，系统架构可以包括终端设备1001、1002、1003，网络1004，服务器1005。网络1004用以在终端设备1001、1002、1003和服务器1005之间提供通信链路的介质。网络1004可以包括各种连接类型，例如有线、无线通信链路或者光纤电缆等等。
终端设备1001、1002、1003可以通过网络1004与服务器1005交互，以接收或发送消息等。终端设备1001、1002、1003上可以 安装有各种客户端应用，例如网页浏览器应用、搜索类应用、新闻资讯类应用。终端设备1001、1002、1003中的客户端应用可以接收用户的指令，并根据用户的指令完成相应的功能，例如根据用户的指令在信息中添加相应信息。
终端设备1001、1002、1003可以是硬件，也可以是软件。当终端设备1001、1002、1003为硬件时，可以是具有显示屏并且支持网页浏览的各种电子设备，包括但不限于智能手机、平板电脑、电子书阅读器、MP3播放器(Moving Picture Experts Group Audio Layer III，动态影像专家压缩标准音频层面3)、MP4(Moving Picture Experts Group Audio Layer IV，动态影像专家压缩标准音频层面4)播放器、膝上型便携计算机和台式计算机等等。当终端设备1001、1002、1003为软件时，可以安装在上述所列举的电子设备中。其可以实现成多个软件或软件模块(例如用来提供分布式服务的软件或软件模块)，也可以实现成单个软件或软件模块。在此不做具体限定。
服务器1005可以是提供各种服务的服务器，例如接收终端设备1001、1002、1003发送的信息获取请求，根据信息获取请求通过各种方式获取信息获取请求对应的展示信息。并展示信息的相关数据发送给终端设备1001、1002、1003。
需要说明的是，本公开实施例所提供的交互方法可以由终端设备执行，相应地，交互装置可以设置在终端设备1001、1002、1003中。此外，本公开实施例所提供的交互方法还可以由服务器1005执行，相应地，交互装置可以设置于服务器1005中。
应该理解，图10中的终端设备、网络和服务器的数目仅仅是示意性的。根据实现需要，可以具有任意数目的终端设备、网络和服务器。
下面参考图11，其示出了适于用来实现本公开实施例的电子设备(例如图10中的终端设备或服务器)的结构示意图。本公开实施例中的终端设备可以包括但不限于诸如移动电话、笔记本电 脑、数字广播接收器、PDA(个人数字助理)、PAD(平板电脑)、PMP(便携式多媒体播放器)、车载终端(例如车载导航终端)等等的移动终端以及诸如数字TV、台式计算机等等的固定终端。图11示出的电子设备仅仅是一个示例，不应对本公开实施例的功能和使用范围带来任何限制。
如图11所示，电子设备可以包括处理装置(例如中央处理器、图形处理器等)1101，其可以根据存储在只读存储器(ROM)1102中的程序或者从存储装置1108加载到随机访问存储器(RAM)1103中的程序而执行各种适当的动作和处理。在RAM 1103中，还存储有电子设备1100操作所需的各种程序和数据。处理装置1101、ROM 1102以及RAM 1103通过总线1104彼此相连。输入/输出(I/O)接口1105也连接至总线1104。
通常，以下装置可以连接至I/O接口1105：包括例如触摸屏、触摸板、键盘、鼠标、摄像头、麦克风、加速度计、陀螺仪等的输入装置1106；包括例如液晶显示器(LCD)、扬声器、振动器等的输出装置11011；包括例如磁带、硬盘等的存储装置1108；以及通信装置1109。通信装置1109可以允许电子设备与其他设备进行无线或有线通信以交换数据。虽然图11示出了具有各种装置的电子设备，但是应理解的是，并不要求实施或具备所有示出的装置。可以替代地实施或具备更多或更少的装置。
特别地，根据本公开的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本公开的实施例包括一种计算机程序产品，其包括承载在非暂态计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信装置1109从网络上被下载和安装，或者从存储装置1108被安装，或者从ROM 1102被安装。在该计算机程序被处理装置1101执行时，执行本公开实施例的方法中限定的上述功能。
需要说明的是，本公开上述的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组 合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本公开中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本公开中，计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读信号介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：电线、光缆、RF(射频)等等，或者上述的任意合适的组合。
在一些实施方式中，客户端、服务器可以利用诸如HTTP(HyperText Transfer Protocol，超文本传输协议)之类的任何当前已知或未来研发的网络协议进行通信，并且可以与任意形式或介质的数字数据通信(例如，通信网络)互连。通信网络的示例包括局域网(“LAN”)，广域网(“WAN”)，网际网(例如，互联网)以及端对端网络(例如，ad hoc端对端网络)，以及任何当前已知或未来研发的网络。
上述计算机可读介质可以是上述电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。
上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被该电子设备执行时，使得该电子设备：展示第一 应用界面，其中，第一应用界面包括第一应用的界面；在第一应用界面中，创建第二应用账户，其中，所述第二应用账户用于登录第二应用。
在一些实施例中，所述电子设备还用于：将所创建的第二应用账户，与目标第一应用团队中的团队成员绑定，其中，所述目标第一应用团队为第一应用账户体系中的团队，第一应用账户体系中的团队包括团队成员。
在一些实施例中，所述将所创建的第二应用账户，与目标第一应用团队中的团队成员绑定，包括：从所述目标第一应用团队的团队成员中，选取团队成员作为目标团队成员；绑定所创建的第二应用账户和所述目标团队成员。
在一些实施例中，所述电子设备还用于：解除目标第一应用团队中的团队成员与第二应用账户之间的绑定。
在一些实施例中，所述电子设备还用于：响应于第二应用账户所绑定的团队成员与目标第一应用团队解除绑定，解除第二应用账户与所绑定的团队成员之间的绑定；展示提示信息，其中，所述提示信息用于提示为第二应用账户绑定新的团队成员。
在一些实施例中，所述电子设备还用于：在第一应用界面，对所创建的第二应用账户进行管理操作，其中，所述管理操作包括以下至少一项：查看、搜索和筛选。
在一些实施例中，所创建的第二应用账户与目标第二应用团队绑定，其中，所述目标第二应用团队为第二应用账户体系中的团队，第二应用账户体系中的团队包括团队成员。
在一些实施例中，所述在第一应用界面中，创建第二应用账户，包括：确定与目标第一应用团队绑定的目标第二应用团队，其中，目标第一应用团队与所述第一应用界面关联；在第一应用界面中，创建属于目标第二应用团队的第二应用账户。
在一些实施例中，在确定与目标第一应用团队绑定的目标第二应用团队之前，所述电子设备还用于：在第一应用界面中，接收用户输入的第二应用团队标识；根据所述第二应用团队标识， 发送第一绑定请求，其中，所述第一绑定请求用于请求绑定目标第一应用团队和用户输入的第二应用团队标识所指示的第二应用团队；基于对第一绑定请求的验证结果，确定是否绑定第一应用界面所关联的目标第一应用团队和用户输入的第二应用团队标识所指示第二应用团队。
在一些实施例中，对所述第一绑定请求的验证步骤，包括：验证目标第一应用团队对应的主体和用户输入的第二应用团队标识对应的主体是否相同；如果相同，在第二应用中向第二应用团队标识对应的管理用户发送绑定确认通知；基于对所述绑定确认通知的确认操作，确认第一绑定请求验证通过。
在一些实施例中，在所述确定与目标第一应用团队绑定的目标第二应用团队之前，所述电子设备还用于：在第二应用界面中，接收用户输入的第一应用团队标识；根据所述第一应用团队标识，发送第二绑定请求，其中，所述第二绑定请求用于请求绑定目标第二应用团队和用户输入的第一应用团队标识所指示的第一应用团队；基于对第二绑定请求的验证结果，确定是否绑定第二应用界面所关联的目标第二应用团队和用户输入的第一应用团队标识所指示第一应用团队。
在一些实施例中，所述电子设备还用于：如果当前登录第一应用的第一应用账户具有绑定的第二应用账户，在第一应用中，展示第二应用的登录入口；基于在所述登录入口使用当前登录的第一应用账户所绑定的第二应用账户登录，展示第二应用界面。
上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被该电子设备执行时，使得该电子设备：在第一应用界面中，配置第二应用团队的第二团队成员的权限，其中，第一应用界面所关联的第一应用团队，与第二应用团队绑定。
在一些实施例中，所述在第一应用界面中，配置第二应用团队的第二团队成员的权限，包括：在第一应用界面中，展示第二应用团队的预设第一权限标识，预设第一权限标识指示第二团队 所具有的团队权限；根据对所展示的预设第一权限标识的选择操作，根据所选择的第一权限标识发送第一授权请求；基于对第一授权请求的授权结果，确定第二团队成员所具有的预设第一权限。
在一些实施例中，所述电子设备还用于：在第一应用界面中，接收用户输入的第二应用团队标识；根据所述第二应用团队标识，发送第一绑定请求，其中，所述第一绑定请求用于请求绑定目标第一应用团队和用户输入的第二应用团队标识所指示的第二应用团队；基于对第一绑定请求的验证结果，确定是否绑定第一应用界面所关联的目标第一应用团队和用户输入的第二应用团队标识所指示第二应用团队。
在一些实施例中，对所述第一绑定请求的验证步骤，包括：验证目标第一应用团队对应的主体和用户输入的第二应用团队标识对应的主体是否相同；如果相同，在第二应用中向第二应用团队标识对应的管理用户发送绑定确认通知；基于对所述绑定确认通知的确认操作，确认第一绑定请求验证通过。
可以以一种或多种程序设计语言或其组合来编写用于执行本公开的操作的计算机程序代码，上述程序设计语言包括但不限于面向对象的程序设计语言—诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络——包括局域网(LAN)或广域网(WAN)—连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
附图中的流程图和框图，图示了按照本公开各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，该模块、程序段、或代码的一部分包含一 个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本公开实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现。其中，单元的名称在某种情况下并不构成对该单元本身的限定，例如，创建单元还可以被描述为“创建第二应用账户的单元”。
本文中以上描述的功能可以至少部分地由一个或多个硬件逻辑部件来执行。例如，非限制性地，可以使用的示范类型的硬件逻辑部件包括：现场可编程门阵列(FPGA)、专用集成电路(ASIC)、专用标准产品(ASSP)、片上系统(SOC)、复杂可编程逻辑设备(CPLD)等等。
在本公开的上下文中，机器可读介质可以是有形的介质，其可以包含或存储以供指令执行系统、装置或设备使用或与指令执行系统、装置或设备结合地使用的程序。机器可读介质可以是机器可读信号介质或机器可读储存介质。机器可读介质可以包括但不限于电子的、磁性的、光学的、电磁的、红外的、或半导体系统、装置或设备，或者上述内容的任何合适组合。机器可读存储介质的更具体示例会包括基于一个或多个线的电气连接、便携式计算机盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或快闪存储器)、光纤、便捷式紧凑盘只读存储器(CD-ROM)、光学储存设备、磁储存设备、或上述内容的任何合适组合。
以上描述仅为本公开的较佳实施例以及对所运用技术原理的 说明。本领域技术人员应当理解，本公开中所涉及的公开范围，并不限于上述技术特征的特定组合而成的技术方案，同时也应涵盖在不脱离上述公开构思的情况下，由上述技术特征或其等同特征进行任意组合而形成的其它技术方案。例如上述特征与本公开中公开的(但不限于)具有类似功能的技术特征进行互相替换而形成的技术方案。
此外，虽然采用特定次序描绘了各操作，但是这不应当理解为要求这些操作以所示出的特定次序或以顺序次序执行来执行。在一定环境下，多任务和并行处理可能是有利的。同样地，虽然在上面论述中包含了若干具体实现细节，但是这些不应当被解释为对本公开的范围的限制。在单独的实施例的上下文中描述的某些特征还可以组合地实现在单个实施例中。相反地，在单个实施例的上下文中描述的各种特征也可以单独地或以任何合适的子组合的方式实现在多个实施例中。
尽管已经采用特定于结构特征和/或方法逻辑动作的语言描述了本主题，但是应当理解所附权利要求书中所限定的主题未必局限于上面描述的特定特征或动作。相反，上面所描述的特定特征和动作仅仅是实现权利要求书的示例形式。

Claims (20)

  1. 一种交互方法，其特征在于，包括：
    展示第一应用界面，其中，第一应用界面包括第一应用的界面；
    在第一应用界面中，创建第二应用账户，其中，所述第二应用账户用于登录第二应用。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    将所创建的第二应用账户，与目标第一应用团队中的团队成员绑定，其中，所述目标第一应用团队为第一应用账户体系中的团队，第一应用账户体系中的团队包括团队成员。
  3. 根据权利要求2所述的方法，其特征在于，所述将所创建的第二应用账户，与目标第一应用团队中的团队成员绑定，包括：
    从所述目标第一应用团队的团队成员中，选取团队成员作为目标团队成员；
    绑定所创建的第二应用账户和所述目标团队成员。
  4. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    解除目标第一应用团队中的团队成员与第二应用账户之间的绑定。
  5. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    响应于第二应用账户所绑定的团队成员与目标第一应用团队解除绑定，解除第二应用账户与所绑定的团队成员之间的绑定；
    展示提示信息，其中，所述提示信息用于提示为第二应用账户绑定新的团队成员。
  6. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在第一应用界面，对所创建的第二应用账户进行管理操作，其中，所述管理操作包括以下至少一项：查看、搜索和筛选。
  7. 根据权利要求1所述的方法，其特征在于，所创建的第二应用账户与目标第二应用团队绑定，其中，所述目标第二应用团队为第二应用账户体系中的团队，第二应用账户体系中的团队包括团队成员。
  8. 根据权利要求1所述的方法，其特征在于，所述在第一应用界面中，创建第二应用账户，其中，所述第二应用账户用于登录第二应用，包括：
    确定与目标第一应用团队绑定的目标第二应用团队，其中，目标第一应用团队与所述第一应用界面关联；
    在第一应用界面中，创建属于目标第二应用团队的第二应用账户。
  9. 根据权利要求8所述的方法，其特征在于，在确定与目标第一应用团队绑定的目标第二应用团队之前，所述方法还包括：
    在第一应用界面中，接收用户输入的第二应用团队标识；
    根据所述第二应用团队标识，发送第一绑定请求，其中，所述第一绑定请求用于请求绑定目标第一应用团队和用户输入的第二应用团队标识所指示的第二应用团队；
    基于对第一绑定请求的验证结果，确定是否绑定第一应用界面所关联的目标第一应用团队和用户输入的第二应用团队标识所指示第二应用团队。
  10. 根据权利要求9所述的方法，其特征在于，对所述第一绑 定请求进行验证的验证步骤，包括：
    验证目标第一应用团队对应的主体和用户输入的第二应用团队标识对应的主体是否相同；
    如果相同，在第二应用中向第二应用团队标识对应的管理用户发送绑定确认通知；
    基于对所述绑定确认通知的确认操作，确认第一绑定请求验证通过。
  11. 根据权利要求8所述的方法，其特征在于，在确定与目标第一应用团队绑定的目标第二应用团队之前，所述方法还包括：
    在第二应用界面中，接收用户输入的第一应用团队标识；
    根据所述第一应用团队标识，发送第二绑定请求，其中，所述第二绑定请求用于请求绑定目标第二应用团队和用户输入的第一应用团队标识所指示的第一应用团队；
    基于对第二绑定请求的验证结果，确定是否绑定第二应用界面所关联的目标第二应用团队和用户输入的第一应用团队标识所指示第一应用团队。
  12. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    如果当前登录第一应用的第一应用账户具有绑定的第二应用账户，在第一应用中，展示第二应用的登录入口；
    基于在所述登录入口使用当前登录的第一应用账户所绑定的第二应用账户登录，展示第二应用界面。
  13. 一种交互方法，其特征在于，包括：
    在第一应用界面中，配置目标第二应用团队的第二团队成员的权限，其中，第一应用界面所关联的目标第一应用团队，与目标第二应用团队绑定。
  14. 根据权利要求13所述的方法，其特征在于，所述在第一应用界面中，配置目标第二应用团队的第二团队成员的权限，包括：
    在第一应用界面中，展示目标第二应用团队的预设第一权限标识，预设第一权限标识指示第二应用团队所具有的团队权限；
    根据对所展示的预设第一权限标识的选择操作，根据所选择的第一权限标识发送第一授权请求；
    基于对第一授权请求的授权结果，确定所述第二团队成员所具有的预设第一权限。
  15. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    在第一应用界面中，接收用户输入的第二应用团队标识；
    根据所述第二应用团队标识，发送第一绑定请求，其中，所述第一绑定请求用于请求绑定目标第一应用团队和用户输入的第二应用团队标识所指示的第二应用团队；
    基于对第一绑定请求的验证结果，确定是否绑定第一应用界面所关联的目标第一应用团队和用户输入的第二应用团队标识所指示第二应用团队。
  16. 根据权利要求15所述的方法，其特征在于，对所述第一绑定请求的验证步骤，包括：
    验证目标第一应用团队对应的主体和用户输入的第二应用团队标识对应的主体是否相同；
    如果相同，在第二应用中向第二应用团队标识对应的管理用户发送绑定确认通知；
    基于对所述绑定确认通知的确认操作，确认第一绑定请求验证通过。
  17. 一种交互装置，其特征在于，包括：
    展示单元，用于展示第一应用界面，其中，第一应用界面包括第一应用的界面；
    创建单元，用于在第一应用界面中，创建第二应用账户，其中，所述第二应用账户用于登录第二应用。
  18. 一种交互装置，其特征在于，包括：
    配置单元，用于在第一应用界面中，配置第二应用团队的第二团队成员的权限，其中，第一应用界面所关联的第一应用团队，与第二应用团队绑定。
  19. 一种电子设备，其特征在于，包括：
    一个或多个处理器；
    存储装置，用于存储一个或多个程序，
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-12中任一或者如权利要求13-16中任一所述的方法。
  20. 一种计算机可读介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现如权利要求1-12中任一或者如权利要求13-16中任一所述的方法。
PCT/CN2022/117519 2021-09-07 2022-09-07 交互方法、装置和电子设备 WO2023036172A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/392,477 US20240127186A1 (en) 2021-09-07 2023-12-21 Interaction method and apparatus, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111046967.XA CN115774501A (zh) 2021-09-07 2021-09-07 交互方法、装置和电子设备
CN202111046967.X 2021-09-07

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/392,477 Continuation US20240127186A1 (en) 2021-09-07 2023-12-21 Interaction method and apparatus, and electronic device

Publications (1)

Publication Number Publication Date
WO2023036172A1 true WO2023036172A1 (zh) 2023-03-16

Family

ID=85387873

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/117519 WO2023036172A1 (zh) 2021-09-07 2022-09-07 交互方法、装置和电子设备

Country Status (3)

Country Link
US (1) US20240127186A1 (zh)
CN (1) CN115774501A (zh)
WO (1) WO2023036172A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150370905A1 (en) * 2014-06-20 2015-12-24 Atlis Labs Ltd Method and system for consumer rating and address book maintenance
WO2017028649A1 (zh) * 2015-08-14 2017-02-23 北京奇虎科技有限公司 一种基于即时通讯接入智能设备的方法和装置
CN108965109A (zh) * 2018-06-27 2018-12-07 腾讯科技（深圳）有限公司 一种即时通讯控制方法、装置及存储介质
CN109088812A (zh) * 2018-07-17 2018-12-25 腾讯科技（深圳）有限公司 信息处理方法、装置、计算机设备和存储介质
CN109167717A (zh) * 2017-07-29 2019-01-08 成都牵牛草信息技术有限公司 根据角色间的通讯关系预设即时通讯账号联系人及预设通讯录的方法
CN109167755A (zh) * 2017-07-28 2019-01-08 成都牵牛草信息技术有限公司 管理系统中即时通讯账号的管理方法

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9781051B2 (en) * 2014-05-27 2017-10-03 International Business Machines Corporation Managing information technology resources using metadata tags
US10191785B2 (en) * 2016-06-30 2019-01-29 Paypal, Inc. User data management across multiple apps on a user device
US11869005B2 (en) * 2019-09-17 2024-01-09 Plaid Inc. System and method linking to accounts using credential-less authentication
CN116155586A (zh) * 2020-02-12 2023-05-23 华为技术有限公司 一种账号数据共享方法及电子设备
US11463446B2 (en) * 2020-09-28 2022-10-04 Dropbox, Inc. Team member transfer tool
US11153293B1 (en) * 2021-02-09 2021-10-19 Slack Technologies, Llc Identity information linking
US11824937B2 (en) * 2021-04-04 2023-11-21 Rissana, LLC System and method for handling the connection of user accounts to other entities

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150370905A1 (en) * 2014-06-20 2015-12-24 Atlis Labs Ltd Method and system for consumer rating and address book maintenance
WO2017028649A1 (zh) * 2015-08-14 2017-02-23 北京奇虎科技有限公司 一种基于即时通讯接入智能设备的方法和装置
CN109167755A (zh) * 2017-07-28 2019-01-08 成都牵牛草信息技术有限公司 管理系统中即时通讯账号的管理方法
CN109167717A (zh) * 2017-07-29 2019-01-08 成都牵牛草信息技术有限公司 根据角色间的通讯关系预设即时通讯账号联系人及预设通讯录的方法
CN108965109A (zh) * 2018-06-27 2018-12-07 腾讯科技（深圳）有限公司 一种即时通讯控制方法、装置及存储介质
CN109088812A (zh) * 2018-07-17 2018-12-25 腾讯科技（深圳）有限公司 信息处理方法、装置、计算机设备和存储介质

Also Published As

Publication number Publication date
CN115774501A (zh) 2023-03-10
US20240127186A1 (en) 2024-04-18

Similar Documents

Publication Publication Date Title
US10778542B2 (en) Rule based subscription cloning
US10841385B2 (en) Efficient means to test server generated applications on mobile device
CN107924411B (zh) 一种事务系统中ui状态的恢复的方法和系统
US10574736B2 (en) Local microservice development for remote deployment
CN107408042B (zh) 用于移动应用的高效和直观的数据绑定
US9858174B2 (en) Updatable native mobile application for testing new features
CN105900467B (zh) 离线内容共享
US10944560B2 (en) Privacy-preserving identity asset exchange
US20120265803A1 (en) Personal cloud
EP3155576A1 (en) Providing a subscription for a service using an existing subscription
US20220374538A1 (en) Permission control method and device and electronic equipment
WO2022111290A1 (zh) 展示方法、装置和电子设备
US20160205092A1 (en) Utilizing X.509 Authentication for Single Sign-On Between Disparate Servers
US20240104671A1 (en) Method and apparatus for group management, electronic device, and storage medium
WO2023246483A1 (zh) 一种信息处理方法、装置、设备及介质
WO2023011528A1 (zh) 信息交互方法、装置和电子设备
WO2023186130A1 (zh) 信息展示和信息发送方法、装置、设备、介质和产品
WO2023036172A1 (zh) 交互方法、装置和电子设备
WO2022206287A1 (zh) 商服交互方法、装置、设备及存储介质
CN113840013B (zh) 一种分级管理的文档系统
US11716213B2 (en) Autonomous screenshare of dynamic magnification view without primary collaboration interruption
WO2023039698A1 (en) Systems and methods for accessing online meeting materials
WO2023011523A1 (zh) 会话信息显示方法、装置和电子设备
WO2023131115A1 (zh) 信息交互方法、装置、电子设备及存储介质
CN111367590A (zh) 中断事件处理方法及其装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE