Communication Interaction Method, Device, Computer Equipment, Storage Medium and Program Product

Abstract

The present application relates to a communication interaction method, apparatus, computer device, storage medium, and program product. The method is applied to an application platform on which a first mini-program is running, and includes: receiving a first communication negotiation request sent by the first mini-program; the first communication negotiation request includes target service interface information of a second mini-program, and the first communication negotiation request is used to request communication interaction with the second mini-program; when the target service corresponding to the target service interface information is authorized for the first mini-program, sending a second communication negotiation request to the second mini-program; the second communication negotiation request includes the target service interface information; receiving verification information sent by the second mini-program, and forwarding the verification information to the first mini-program to instruct the first mini-program to perform communication interaction with the second mini-program based on the verification information and the target service interface information. Using the application platform as a negotiation intermediary, negotiation communication between different mini-programs is realized, improving the communication interaction performance.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a communication interaction method, apparatus, computer equipment, storage medium and program product. Background Art

[0002] Mini programs are programs that run on a designated application platform and can be invoked without installation to provide fixed services. Since mini programs use web technology, they need to rely on the application platform. Mini programs running on the application platform can usually only obtain relevant information about the application platform, and their operating resources and permissions are restricted by the application platform.

[0003] Traditionally, multiple different mini-programs can be run on an application platform. If a mini-program needs to perform business interaction with another mini-program, it is usually necessary to embed a link address of the other mini-program in the mini-program so as to jump to the other mini-program through the link address.

[0004] However, the link address jump method has a limited amount of information, resulting in poor interaction performance between the two applets. Summary of the invention

[0005] Based on this, it is necessary to provide a communication interaction method, device, computer equipment, computer-readable storage medium and computer program product that can improve the communication interaction performance between different applets in an application platform in response to the above technical problems.

[0006] In a first aspect, the present application provides a communication interaction method, which is applied to an application platform, where a first applet runs on the application platform, and the method includes:

[0007] Receiving a first communication negotiation request sent by the first applet; the first communication negotiation request includes target service interface information of the second applet, and the first communication negotiation request is used to request communication interaction with the second applet;

[0008] When the target service corresponding to the target service interface information is authorized to the first applet, sending a second communication negotiation request to the second applet; the second communication negotiation request includes the target service interface information;

[0009] Receive verification information sent by the second applet, and forward the verification information to the first applet to instruct the first applet to communicate and interact with the second applet based on the verification information and the target service interface information.

[0010] In one of the embodiments, before receiving the first communication negotiation request sent by the first applet, the method further includes:

[0011] Displaying a first rights request interface in the first mini-program; the first rights request interface includes a mini-program list and a service list, the mini-program list includes at least one mini-program related to the first mini-program and subscribed by the user, and the service list includes at least one service of each mini-program in the mini-program list;

[0012] In response to the first authorization operation triggered by the user in the first authorization request interface, the authorization applet corresponding to the first authorization operation and the authorization service of the authorization applet are authorized to the first applet, and the basic information of the authorization applet and the service interface information corresponding to the authorization service of the authorization applet are sent to the first applet.

[0013] In one of the embodiments, the first communication negotiation request is generated by the first applet according to the target service interface information corresponding to the target service of the second applet when the first applet determines that the target service of the second applet corresponding to the target collaboration task is authorized.

[0014] In one embodiment, the method further comprises:

[0015] Receive a request for permission sent by the first mini program; the request for permission is generated by the first mini program according to a permission opening operation triggered by a user when the first mini program determines that the target service of the second mini program corresponding to the target collaboration task is not authorized;

[0016] Displaying a second authorization request interface in the first applet; the second authorization request interface includes the second applet and the target service of the second applet;

[0017] In response to the second authorization operation triggered by the user in the second authorization interface, the target service of the second applet corresponding to the second authorization operation is authorized to the first applet, and the target service interface information corresponding to the target service of the second applet is sent to the first applet.

[0018] In one embodiment, the method further comprises:

[0019] Receive at least one service of the second mini program sent by the developer platform after the second mini program is registered and released; at least one service of the second mini program is a service that can be used by other mini programs to communicate and interact with the second mini program, and at least one service of the second mini program includes the target service of the second mini program.

[0020] In one embodiment, the first communication negotiation request also includes basic information of a logged-in user of the application platform, and sending the second communication negotiation request to the second applet includes:

[0021] Determine whether the logged-in user has subscribed to the second mini program;

[0022] If so, a second communication negotiation request is sent to the second applet.

[0023] In a second aspect, the present application further provides a communication interaction device, which is applied to an application platform, and the application platform runs a first applet, and the device includes:

[0024] A first receiving module is used to receive a first communication negotiation request sent by the first applet; the first communication negotiation request includes target service interface information of the second applet, and the first communication negotiation request is used to request communication interaction with the second applet;

[0025] A first sending module is used to send a second communication negotiation request to the second applet when the target service corresponding to the target service interface information is authorized to the first applet; the second communication negotiation request includes the target service interface information;

[0026] A second receiving module, used to receive verification information sent by the second applet;

[0027] The second sending module is used to forward the verification information to the first applet to instruct the first applet to communicate with the second applet based on the verification information and the target service interface information.

[0028] In a third aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the communication interaction method in the first aspect when executing the computer program.

[0029] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the communication interaction method in the first aspect above.

[0030] In a fifth aspect, the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the communication interaction method in the first aspect above.

[0031] The above-mentioned communication interaction method, apparatus, computer equipment, storage medium and computer program product can be applied to an application platform, and a first applet is running in the application platform. The application platform receives a first communication negotiation request sent by the first applet, and the first communication negotiation request includes the target service interface information of the second applet. The first communication negotiation request is used to request communication interaction with the second applet; then, when the target service corresponding to the target service interface information is authorized to the first applet, a second communication negotiation request carrying the target service interface information is sent to the second applet, and then the verification information sent by the second applet is received, and the verification information is forwarded to the first applet to instruct the first applet to communicate and interact with the second applet based on the verification information and the target service interface information. That is to say, the communication interaction method proposed in the embodiment of the present application can realize communication interaction between different mini-programs in the application platform through communication negotiation on the application platform; that is, the application platform is used as a negotiation intermediary, and the service interface and verification information and other functions between the mini-programs cooperate with each other, so as to meet the communication interaction needs between any mini-programs in the application platform, which can not only improve the interaction performance between the mini-programs, but also provide users with richer service forms, and improve the convenience and operability of the function implementation between the mini-programs. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 An application environment diagram of a communication interaction method in an embodiment;

[0034] Figure 2 is a flow chart of a communication interaction method in one embodiment;

[0035] Figure 3 is a flow chart of a communication interaction method in another embodiment;

[0036] Figure 4 is a flow chart of a communication interaction method in another embodiment;

[0037] Figure 5 This is an architecture diagram of a mini-program platform in one embodiment;

[0038] Figure 6 An interactive flow chart of negotiation communication performed by an application platform based on a mini-program in one embodiment;

[0039] Figure 7 is a structural block diagram of a communication interaction device in one embodiment;

[0040] Figure 8 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0042] First, the terms used in this application are explained, including:

[0043] Platform: The system or program where the Mini Program runs. It contains some user information and can be provided to the Mini Program for use with authorization. The most common example is WeChat. With user authorization, the Mini Program may obtain the user's WeChat name, mobile phone number and other information.

[0044] As for the platform, it can include an application platform and a developer platform. The application platform refers to an application program running on the user terminal device, involving a user front-end interface and back-end services; the developer platform is usually in the form of a web page, which can be used as a platform for the activation and release of mini-programs. Developers activate mini-programs on the developer platform and release the developed mini-programs. After release, the mini-programs can run on the application platform; the developer platform can provide developers with a web interface and back-end services.

[0045] Mini Program: A program that runs on a designated platform (such as an application platform) and provides fixed services and can be invoked without installation. These programs are dependent on the platform and cannot run independently. After authorization, the mini program can also obtain information provided by the platform through designated protocols.

[0046] With the development of network technology, some software that originally needed to be installed can be loaded by clicking when they are actually used. At the same time, mini programs can always be loaded to the latest version when used, and the upgrade and update operations can be saved.

[0047] Since mini programs use web technology and rendering web pages requires a browser (or browser core), mini programs must rely on an application or platform (such as WeChat, Alipay, etc.). For this reason, the running resources and permissions of mini programs are restricted by the platform and cannot effectively use the platform's system resources. Therefore, in addition to interface display, more calculations will be performed in the cloud.

[0048] Currently, the mini-program platforms on the market (mainly referring to the application platforms that run mini-programs) only provide the platform's own information to mini-programs. The mutual calls between mini-programs are very weak. The most common practice is to embed the link address of another mini-program in one mini-program, and use the link address to bring the information to another mini-program for opening. However, because of the way of jumping through the link address, the information carried in the link address is extremely limited. Not only is the amount of information small, but some sensitive information may also be exposed when transmitted in this way.

[0049] For example, for a mini program that needs to transfer file data, it is impossible to transfer file data to another mini program through a link address; for example: in an application platform, when a user subscribes to a network disk mini program and then subscribes to a cloud conference mini program, if the recorded conference video of the cloud conference mini program is to be stored in the network disk mini program, in the current architecture, unless the two mini programs negotiate an agreement during the development process, file transfer cannot be achieved. Therefore, the interaction performance between traditional mini programs is poor and cannot meet the daily use needs of users.

[0050] Based on this, an embodiment of the present application proposes a communication interaction method, so that mini-programs can communicate and call each other through negotiation in the platform under the premise of user authorization.

[0051] The communication interaction method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. In which, a plurality of different mini-programs 102 can be run in the application platform 10, and after the user subscribes to the mini-program, the subscribed mini-program can be opened and run in the application platform; illustratively, in the case where the user subscribes to the first mini-program and the second mini-program, after the user's authorization, the first mini-program can communicate and interact with the second mini-program through the negotiation of the application platform. In which, in the case where the user authorizes the first mini-program to access the second mini-program, the first mini-program can communicate and interact with the second mini-program through the service interface of the second mini-program; in the case where the user authorizes the second mini-program to access the first mini-program, the second mini-program can communicate and interact with the first mini-program through the service interface of the first mini-program.

[0052] The application platform 10 can be installed and run in the terminal device as an application (or application software) for users to use; the application platform 10 can include but is not limited to social application software, payment application software, etc. The embodiment of the present application does not specifically limit the type of application platform, and small programs can be run in the application platform. Exemplarily, the terminal device can include but is not limited to various personal computers, laptops, smart phones, tablet computers and portable wearable devices. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, etc.

[0053] In an exemplary embodiment, Figure 2 As shown, a communication interaction method is provided, which is applied to Figure 1 Taking the application platform in as an example, a first applet is running in the application platform, and the first applet needs to communicate and interact with the second applet. The communication and interaction process may include the following steps 202 to 206. Among them:

[0054] Step 202: Receive a first communication negotiation request sent by a first applet.

[0055] The first communication negotiation request includes target service interface information of the second applet, and the first communication negotiation request is used to request communication interaction with the second applet.

[0056] Normally, for different mini-programs on an application platform, if the corresponding communication interaction function is not developed during the development of each mini-program, the mini-programs cannot achieve communication interaction; wherein, the communication interaction function may include but is not limited to adding a link address of another mini-program in a mini-program, or developing a communication function between two mini-programs. In the embodiment of the present application, the application platform is used as a communication negotiation medium, and communication negotiation can be performed for any mini-program in the application platform, thereby realizing a quick communication interaction function between different mini-programs.

[0057] When a logged-in user of an application platform is using a first mini-program in the application platform, if the logged-in user wants to access a second mini-program through the first mini-program, communication negotiation can be performed through the application platform, and if the negotiation is successful, the first mini-program can communicate and interact with the second mini-program in the application platform.

[0058] Exemplarily, when a logged-in user triggers a target collaboration task in the first applet, the first applet can generate a first communication negotiation request based on the relevant information of the target collaboration task, and send the first communication negotiation request to the application platform, and the first communication negotiation request is used to request the application platform to communicate and negotiate with the second applet, thereby realizing communication interaction between the first applet and the second applet. Exemplarily, the relevant information of the target collaboration task may include, but is not limited to, at least one of the basic information of the first applet, the basic information of the second applet to be accessed by the first applet, and the target service interface information of the target service of the second applet corresponding to the target collaboration task.

[0059] It should be noted that the second applet can provide a variety of different services for the first applet (or other applet), each service can correspond to one or more service interfaces, and the collaborative tasks between applet can be generated for a certain service, and the corresponding service interface corresponding to the service needs to be used to communicate with each other when processing the collaborative task. In addition, the service interface can be set with service interface information, including but not limited to interface type, interface identifier, interface address, etc.

[0060] Exemplarily, when the first mini program detects a target collaboration task, it can generate a first communication negotiation request based on the target service interface information of the second mini program corresponding to the target collaboration task, and send the first communication negotiation request to the application platform, wherein the target service interface information of the second mini program can be used to characterize the target service of the second mini program.

[0061] Step 204: When the target service corresponding to the target service interface information is authorized to the first applet, a second communication negotiation request is sent to the second applet.

[0062] The second communication negotiation request includes target service interface information. Based on the target service interface information, the target service of the second applet can be determined. For example, when the target service of the second applet is authorized to the first applet, the application platform will conduct communication negotiation with the second applet, that is, send the second communication negotiation request carrying the target service interface information to the second applet.

[0063] Exemplarily, the authorization operation of the target service of the second applet can be performed after the first applet triggers the target collaboration task, or when the first applet starts running, or when the first applet requests user authorization from the application platform, and of course, it can also be performed after the application platform receives the first communication negotiation request sent by the first applet; in addition, the authorization operation can be performed when the first applet actively requests authorization, or it can be passively performed by the application platform according to the triggering conditions, wherein the triggering conditions include but are not limited to the first applet actively requesting authorization, receiving the first communication negotiation request, etc. In the embodiment of the present application, there is no specific limitation on the execution time, active execution or passive execution of the authorization operation, etc. In actual application, it can be flexibly set according to the needs of the scene, or it can be executed separately at different times.

[0064] Step 206, receiving the verification information sent by the second applet, and forwarding the verification information to the first applet to instruct the first applet to communicate and interact with the second applet based on the verification information and the target service interface information.

[0065] Exemplarily, when the second applet receives the second communication negotiation request sent by the application platform, it can feedback verification information for communication interaction to the application platform. The verification information may include but is not limited to communication verification credentials such as communication tokens, communication keys, communication signatures, and communication verification algorithms; then, the application platform can forward the verification information sent by the second applet to the first applet, so that the first applet can communicate and interact with the second applet based on the verification information and target service interface information of the second applet, thereby executing the target collaboration task. That is to say, when executing the target collaboration task, the first applet can send a communication request to the second applet by calling the target service interface of the second applet. The communication request can carry the verification information of the second applet and communication interaction data, etc. The communication interaction data may include any data sent by the first applet to the second applet. For example, when the first applet is a cloud conference applet and the second applet is a network disk applet, the communication interaction data may be the conference video data recorded in the cloud conference applet.

[0066] Exemplarily, when the second mini program receives the second communication negotiation request, it may also first verify the legitimacy of the second communication negotiation request, and if the verification is successful, feedback the verification information to the application platform. Optionally, when the second communication negotiation request includes target service interface information, the legitimacy verification may include determining whether the target service corresponding to the target service interface information is in an open state. In other implementations, the second communication negotiation request may also carry basic information of the first mini program, and the legitimacy verification may also include whether the target service of the second mini program is authorized to the first mini program, that is, determining whether the first mini program has the right to call the target service of the second mini program; in this case, the target service of the second mini program can be authorized to the first mini program through authorization between mini programs, such as developer authorization.

[0067] Optionally, the second communication negotiation request may also carry basic information of the logged-in user of the application platform, and the legitimacy verification may also include whether the logged-in user authorizes the target service of the second mini program to the first mini program, that is, the authorization operation is performed through the platform user. If the logged-in user authorizes the target service of the second mini program to the first mini program, it is determined that the legitimacy verification is passed.

[0068] The above communication interaction method can be applied to an application platform, and a first applet is running in the application platform. The application platform receives a first communication negotiation request sent by the first applet, and the first communication negotiation request includes the target service interface information of the second applet. The first communication negotiation request is used to request communication interaction with the second applet; then, when the target service corresponding to the target service interface information is authorized to the first applet, a second communication negotiation request carrying the target service interface information is sent to the second applet, and then the verification information sent by the second applet is received, and the verification information is forwarded to the first applet to instruct the first applet to communicate and interact with the second applet based on the verification information and the target service interface information. In other words, the communication interaction method proposed in the embodiment of the present application can realize communication interaction between different applet in the application platform through communication negotiation through the application platform; that is, the application platform is used as a negotiation intermediary, and the service interface and verification information between the applet functions are mutually coordinated to meet the communication interaction needs between any applet in the application platform, which can not only improve the interaction performance between the applet, but also provide users with richer service forms, and improve the convenience and operability of the function implementation between the applet.

[0069] In an exemplary embodiment, the above authorization operation can be performed before the first mini-program triggers the target collaborative task, that is, the first mini-program performs the rights request operation first, wherein the rights request operation may include requesting the information rights of the application platform and the service rights of other mini-programs. Exemplarily, the information rights request of the application platform and the service rights request of other mini-programs can be performed simultaneously or separately. Exemplarily, Figure 3 As shown, before the above step 202: receiving the first communication negotiation request sent by the first applet, the method may further include steps 302 to 304. Among them:

[0070] Step 302: Display a first rights request interface in the first mini-program.

[0071] Among them, the first rights request interface includes a mini-program list and a service list. The mini-program list includes at least one mini-program related to the first mini-program and subscribed by the user, and the service list includes at least one service of each mini-program in the mini-program list.

[0072] Exemplarily, when the information rights request of the application platform and the service rights request of other mini-programs are executed simultaneously, the first rights request interface may also include user information of the application platform, including but not limited to user name, user mobile phone number, etc.

[0073] For example, when the information rights request of the application platform and the service rights request of other applets are executed separately, the service rights request of other applets can be executed before or after the information rights request of the application platform. The embodiment of the present application does not specifically limit the order of rights requests.

[0074] Exemplarily, during the running of the first mini program, the application platform may display a first authorization interface in the first mini program based on the authorization request of the first mini program. For example, the first mini program may send a authorization request to the application platform when it starts running, and the authorization request may be used to request user information authorization of the application platform and service authorization of other mini programs. Another example is that the first mini program may send a first authorization request to the application platform when it starts running, and the first authorization request may be used to request user information authorization of the application platform. Then, the first mini program may send a second authorization request to the application platform when performing collaborative tasks related to collaborative communication, and the second authorization request may be used to request service authorization of other mini programs.

[0075] Exemplarily, during the running of the first mini program, the application platform may also display the first authorization request interface in the first mini program according to the running status of the first mini program; for example: the application platform may display the first authorization request interface in the first mini program according to the startup status of the first mini program, and the first authorization request interface may include user information of the application platform, a mini program list, and a service list; for another example: the application platform may also display the first authorization request interface in the first mini program according to the collaborative task status of the first mini program, and the first authorization request interface may include a mini program list and a service list.

[0076] It should be noted that when the first mini program independently executes the information rights request of the application platform, the rights request interface displayed in the first mini program may include the user information of the application platform.

[0077] Exemplarily, when the first mini program requests service rights, a first rights request interface may be displayed in the first mini program, and the first rights request interface includes a mini program list and a service list, wherein the mini program list may include at least one mini program related to the first mini program and subscribed by the user, and the service list includes at least one service of each mini program in the mini program list. In other words, the application platform can determine the mini program related to the first mini program based on the relevant information of the first mini program, and the mini program related to the first mini program must also meet the user's subscription conditions, that is, determine at least one mini program related to the first mini program among all the mini programs subscribed by the user to form a mini program list in the first rights request interface. In other words, mini programs that are related to the first mini program but not subscribed by the user will not be displayed to the user for selection when requesting service rights.

[0078] Exemplarily, for each mini-program in the mini-program list, the open services corresponding to each mini-program can also be displayed to the user in the form of a service list for the user to make an authorization selection; wherein the open services corresponding to the mini-program can include one or more, and at least one service of the mini-program included in the service list can be all open services of the mini-program, or can be at least one service related to the first mini-program. The open services of the mini-program can be marked when the mini-program is registered or published. For example, when registering the mini-program, the open service list of the mini-program can be set or uploaded so that the application can perform user authorization operations based on the open services of the mini-program.

[0079] Step 304, in response to the first authorization operation triggered by the user in the first authorization request interface, the authorization applet corresponding to the first authorization operation and the authorization service of the authorization applet are authorized to the first applet, and the basic information of the authorization applet and the service interface information corresponding to the authorization service of the authorization applet are sent to the first applet.

[0080] Exemplarily, the user can select an authorizable mini-program and at least one authorizable service corresponding to the mini-program in the first authorization request interface. The user can also select multiple mini-programs and multiple services corresponding to each mini-program for authorization at the same time. The first authorization request interface can also include authorization controls, such as: agree or authorize, etc. When the user clicks the authorization control, the application platform can obtain the first authorization operation triggered by the user, and the first authorization operation can include the authorized mini-program selected by the user and the authorized service corresponding to the authorized mini-program. Then, the application platform can authorize the authorized mini-program corresponding to the first authorization operation and the authorized service of the authorized mini-program to the first mini-program, and send the basic information of the authorized mini-program and the service interface information corresponding to the authorized service of the authorized mini-program to the first mini-program.

[0081] Exemplarily, for the first mini program, it may store the basic information of the authorized authorization mini program and the service interface information corresponding to the authorization service of the authorization mini program, or the first mini program may modify the authorization status of all related mini programs and the services corresponding to the mini programs stored in its database according to the basic information of the authorization mini program and the service interface information corresponding to the authorization service of the authorization mini program; for example: all mini programs related to the first mini program and the open services corresponding to each mini program may be stored in the database of the first mini program, but the initial status of each mini program and the corresponding open service may be unauthorized; after obtaining authorization, the first mini program may change the status of the authorization mini program from an unauthorized state to an authorized state, and change the status of the authorization service corresponding to the authorization mini program from an unauthorized state to an authorized state.

[0082] On this basis, before sending the first communication negotiation request to the application platform, the first mini program can first determine based on the database whether the target service of the second mini program required for the target collaboration task is authorized. That is, when it is determined that the target service of the second mini program required for the target collaboration task is authorized, the first communication negotiation request is generated according to the target service interface information corresponding to the target service of the second mini program, and the first communication negotiation request is sent to the application platform.

[0083] In this embodiment, the application platform may display a first authorization request interface in the first applet before receiving the first communication negotiation request sent by the first applet; the first authorization request interface includes an applet list and a service list, the applet list includes at least one applet related to the first applet and subscribed by the user, and the service list includes at least one service of each applet in the applet list; then, in response to the first authorization operation triggered by the user in the first authorization request interface, the authorization applet corresponding to the first authorization operation and the authorization service of the authorization applet are authorized to the first applet, and the basic information of the authorization applet and the service interface information corresponding to the authorization service of the authorization applet are sent to the first applet. That is to say, before the first applet performs the collaborative task with other applet, the authorization request operation is performed first, so that the user authorizes the first applet to access the service permissions of other applet, and in the case of authorization, the feasibility of the first applet accessing the services of other applet is improved, thereby improving the communication interaction capability and communication interaction efficiency between different applet.

[0084] In an exemplary embodiment, there is a possibility that when requesting service rights, the user does not authorize the second applet and the open services in the second applet, resulting in the first applet being unable to send the first communication negotiation request to the application platform when accessing the second applet because the target service of the second applet is not authorized; in this case, the first applet can also send a request for rights to the application platform so that the user can authorize the target service of the second applet. Exemplarily, based on the above embodiment, if Figure 4 As shown, the communication interaction method may further include steps 402 to 406. Among them:

[0085] Step 402, receiving a permission request sent by the first mini program; the permission request is generated by the first mini program according to a permission activation operation triggered by the user when it is determined that the target service of the second mini program corresponding to the target collaborative task is not authorized.

[0086] In this example, when the first mini program executes the first service authorization request, the user has not authorized the target service of the second mini program, which includes that the user has not authorized the second mini program, and of course all open services corresponding to the second mini program are not authorized. It may also include that the user authorizes the second mini program and at least one service, but does not authorize the target service of the second mini program; when the first mini program needs to execute a target collaboration task with the second mini program, the first mini program determines based on the database that the target service of the second mini program corresponding to the target collaboration task is not authorized. At this time, the first mini program can send a request for authorization to the application platform. The request for authorization is used to request authorization for the target service of the second mini program, wherein the request for authorization can carry service information of the target service of the second mini program, and can also carry basic information of the second mini program; optionally, the service information of the target service may include but is not limited to at least one of the service name, service description, service address (ie, service interface), service category, etc.

[0087] Step 404: display a second authorization request interface in the first applet; the second authorization request interface includes the second applet and the target service of the second applet.

[0088] Exemplarily, after receiving a rights request from the first mini program that carries the service information of the target service of the second mini program, the application platform may display a second rights request interface in the first mini program based on the rights request. The second rights request interface may only include the second mini program and the target service of the second mini program; that is, different from the first service rights request mentioned above, this service rights request may only be made for the target service of the second mini program, while the first service rights request may be made for all other mini programs and corresponding services related to the first mini program.

[0089] Optionally, the second authorization request interface may also include other unauthorized services in the second mini program. That is to say, this service authorization request can be for all unauthorized services in the open services corresponding to the second mini program except for authorized services, including the target service of the second mini program, so that users can synchronously authorize other services of the second mini program at one time, reducing the number of service authorization operations when using other services subsequently, thereby improving authorization efficiency.

[0090] Optionally, the second authorization request interface may also include other unauthorized applets related to the first applet and services corresponding to other applets, and / or unauthorized services corresponding to other authorized applets related to the first applet. In other words, this service authorization request may also be performed synchronously for other unauthorized applets and unauthorized services related to the first applet, so as to provide a service authorization basis for the subsequent execution of other collaborative tasks, thereby improving the execution efficiency of other collaborative tasks, that is, improving the communication and interaction performance between applets.

[0091] Step 406, in response to the second authorization operation triggered by the user in the second authorization interface, the target service of the second applet corresponding to the second authorization operation is authorized to the first applet, and the target service interface information corresponding to the target service of the second applet is sent to the first applet.

[0092] If the user agrees to authorize the target service of the second applet, the user can trigger the second authorization operation by clicking the authorization control in the second authorization interface; accordingly, when responding to the second authorization operation, the application platform can authorize the target service of the second applet corresponding to the second authorization operation to the first applet, and send the target service interface information corresponding to the target service of the second applet to the first applet. Optionally, the first applet can store the target service interface information corresponding to the target service of the second applet, and can also modify the authorization status of the target service of the second applet, etc.

[0093] Next, when the target service of the second applet is authorized, a first communication negotiation request is generated according to the target service interface information corresponding to the target service of the second applet, and the first communication negotiation request is sent to the application platform so that the application platform can perform communication negotiation with the second applet.

[0094] In this embodiment, if the first service rights request does not authorize the second mini program or the target service of the second mini program, a rights request can be initiated to the application platform again, so that the user can authorize the target service of the second mini program based on the second rights request interface, and then, when authorized, a communication negotiation request is initiated for the target collaboration task, thereby realizing communication interaction between the first mini program and the second mini program and completing the target collaboration task; this method can improve the flexibility of service rights request, meet the rights request and negotiation communication in different scenarios, and improve the negotiation communication performance and efficiency.

[0095] In an exemplary embodiment, when requesting service rights, the other mini-programs that need to be requested are mini-programs in the application platform and these mini-programs have open services. The mini-programs in the application platform can be registered and published through the developer platform. After registration and publication, the mini-programs can be run and used in the application platform. This example briefly describes the registration and publication process of the mini-program. On the basis of the above embodiment, for the application platform, the communication interaction method may also include:

[0096] Receive at least one service of the second mini program sent by the developer platform after the second mini program is registered and released; at least one service of the second mini program is a service that can be used by other mini programs to communicate and interact with the second mini program, and at least one service of the second mini program includes the target service of the second mini program.

[0097] In this example, the registration and publishing process is described by taking the above-mentioned second applet as an example. The developer platform can be a platform designed for developers of applet. The developer platform can run on the terminal and can be used as a web platform for different developers. If you need to launch a second applet on the application platform, you can first activate the second applet on the developer platform and develop the program for the second applet. For the completed second applet, you can also register and publish the second applet on the developer platform. After registration and publishing, the developer platform can send the second applet to the application platform, so that users can search and use the second applet in the application platform.

[0098] Exemplarily, in the communication interaction scheme proposed in the embodiment of the present application, when the developer registers and publishes the second mini program on the developer platform, the developer can also simultaneously upload the open service list of the second mini program. The open service list may include at least one service and corresponding service information. After the second mini program completes registration and publication, the developer platform can send the second mini program, at least one service of the second mini program, and the corresponding service information to the application platform, so that when the application platform performs service authorization, it can generate and display a corresponding authorization request interface based on at least one service of the second mini program, so that the user can perform service authorization.

[0099] For example, for a second mini program that has been registered and released, if the open service list of the second mini program was not uploaded when it was previously registered and released, the developer can also upload the corresponding open service list for the second mini program that has been registered and released through the developer platform. In this case, the developer platform can send the open service list of the second mini program to the application platform, and accordingly, the application platform can receive at least one service of the second mini program sent by the developer platform. For mini programs with open services, when performing service authorization, the application platform can display the mini programs that are related to the mini program (such as the first mini program) that is subscribed by the user and has open services, as well as at least one service of the mini program in the first authorization interface.

[0100] In this embodiment, for mini-programs involved in collaborative tasks, developers can register the mini-programs on the developer platform and upload the corresponding open service list so that the application platform can obtain the registered mini-programs and the corresponding development service list, thereby providing users with a service authorization interface to facilitate users to authorize the mini-programs and corresponding services. After authorization, the mini-programs can communicate and interact through negotiation on the application platform, thereby improving the communication and interaction performance between mini-programs.

[0101] In an exemplary embodiment, the above-mentioned first communication negotiation request may also include basic information of the logged-in user of the application platform. When the application platform determines that the target service corresponding to the target service interface information is authorized to the first mini program, when sending the second communication negotiation request to the second mini program, it may also first determine whether the logged-in user continues to subscribe to the second mini program. If the logged-in user continues to subscribe to the second mini program, the second communication negotiation request may be sent to the second mini program. When the logged-in user no longer subscribes to the second mini program, the second mini program cannot be continued to be used, and the second communication negotiation request cannot be sent to the second mini program.

[0102] Exemplarily, if the logged-in user no longer subscribes to the second applet, the application platform can display negotiation failure information in the first applet, and the negotiation failure information can include the reason for the negotiation failure, such as the user no longer subscribes or has not subscribed to the second applet. Optionally, the application platform can also provide the user with a subscription control for the second applet. If the logged-in user wants to continue to access the second applet to complete the target collaboration task, the subscription control can be triggered to send a subscription request for the second applet to the application platform, so that when subscribing to the second applet, the application platform sends a second communication negotiation request carrying the target service interface information of the second applet to the second applet. Optionally, the second communication negotiation request can also include the basic information of the first applet, wherein the basic information of the first applet can be used by the second applet to verify the identity and authorization of the first applet, and when the verification is passed, the second applet can feedback verification information to the application platform, so that the application platform forwards the verification information to the first applet, so that the first applet can communicate and interact with the second applet based on the verification information and the target service interface.

[0103] In this embodiment, before the application platform communicates and negotiates with the second mini program, it can first determine whether the user is subscribed to the second mini program, and if it is determined that the user is subscribed to the second mini program, send a second communication negotiation request to the second mini program; through subscription judgment, it can avoid the situation where the user subscribes first and then unsubscribes midway, which can improve the accuracy and reliability of communication negotiation.

[0104] In an exemplary embodiment, a complete embodiment of communication interaction is provided, wherein the mini program platform may include an application platform of the mini program and a developer platform of the mini program, Figure 5 As shown, the mini program platform may include: a mini program registration module, a user authorization module and an authentication negotiation module, wherein the mini program registration module is set on the developer platform, and the user authorization module and the authentication negotiation module are set on the application platform; it should be noted that the developer platform may also include a user (developer) login module and other business modules, and the application platform may also include a user login module and other business modules. Specifically:

[0105] 1. Mini Program Registration Module: This module is set up on the developer platform. Mini Programs need to be registered on the developer platform when they are launched on the application platform. Compared with the traditional registration scheme, in this example, in addition to registering the basic information of the Mini Program, the services and service interfaces exposed by the Mini Program also need to be registered.

[0106] For example, the basic information of the mini program may include but is not limited to the basic information of the mini program provider, compliance information and other certification documents. In addition, the mini program must also provide a list of available services, i.e., an open service list. The open service list may include at least one service and service information. These services are functional services provided by the mini program when called by other mini programs. The service information may include but is not limited to:

[0107] 1) Service name, the name of the service provided, such as file upload

[0108] 2) Service description, describing the service, for example: providing other services to upload files

[0109] 3) Service address (also known as service interface), the web address (or interface address) when other services call this service

[0110] 4) Service classification: Services can be classified and the entire category can be authorized when users authorize, so as to simplify the difficulty of user authorization.

[0111] Taking the network disk applet as an example, upload services, modification services, deletion services, etc. can be classified as write services, and download services, sharing services, etc. can be classified as read services. When authorizing services, the service list can include write services and read services. When a user authorizes a certain type of service, it is equivalent to authorizing all services under this type of service, avoiding the user from selecting and authorizing each service separately, which can increase the difficulty of user service authorization and improve service authorization efficiency. In addition, it can also simplify the content information of the authorization request interface and improve the simplicity and readability of the interface.

[0112] It should be noted that the above service classification can be optional, that is, the developer can classify the service or not. For classified services, the application platform can display the service category in the rights request interface, and for unclassified services, the service can be displayed in the rights request interface. In addition, when displaying the service category, the rights request interface can also be provided with an expansion control for the service category. By triggering the expansion control, the user can expand and display all services under the service category. By default, if the user selects the service category, all services under the service category are selected by default; of course, when expanding all services under the service category, the user can also selectively select or deselect services.

[0113] In addition, for developers, in order to facilitate their registration of all open services under the mini program, that is, to improve the registration efficiency of open services, the developer platform can also provide developers with a service registration interface, which can support the use of JSON files, YAML files, XML files and other file types to publish services with one click.

[0114] 2. User authorization module: It is set on the application platform. When the mini program uses user information, a relevant information authorization interface will pop up to ask the user to authorize. In this example, in addition to authorizing the user's information in the application platform, the user will also be informed and authorized of other subscribed mini programs and corresponding services.

[0115] refer to Figure 6 As shown, for the permission request operation of a Mini Program, when the Mini Program needs to use the permissions of the application platform or certain permissions of other Mini Programs, the corresponding permission request interface (such as a confirmation dialog box) will pop up for the user to select and authorize. The user can choose to grant permissions to the permission requesting Mini Program (such as the first Mini Program, which can also be called the calling Mini Program). If the other Mini Programs (such as the second Mini Program, which can also be called the called Mini Program) that the permission requesting Mini Program (the first Mini Program) needs to call are not in the user's subscription list, the called Mini Program will not be displayed in the permission request interface for the user to select.

[0116] After the user completes the authorization, the calling applet (first applet) can obtain the user authorization information through existing protocols, such as OAuth2 or related authentication methods, including the basic information of the logged-in user in the application platform and at least one service information of the called applet that it needs to call. Then, communication negotiation and service call can be carried out through the third authentication negotiation module below.

[0117] 3. Authentication negotiation module: Set up on the application platform, the authentication negotiation module is mainly responsible for the access authentication protocol required for communication between mini-programs when a mini-program (such as the first mini-program) subscribed by a user (such as the second mini-program) accesses another mini-program (such as the second mini-program).

[0118] When the calling applet (such as the first applet) obtains the service permission of the called applet (such as the second applet) that needs to access the service, when making a service call, the two cannot directly connect for communication interaction. Instead, they need to communicate and negotiate through the authentication negotiation module of the application platform before they can communicate and interact based on the verification information of the communication negotiation. That is, unlike the current system that distributes AK / SK (secret key) to the calling applet in advance, the called applet must negotiate through the application platform to ensure the legitimacy of the access source.

[0119] When the calling applet (first applet) needs to use the function of the called applet (second applet), the calling applet (first applet) has obtained the service interface information of the called applet (second applet) from the application platform after the user has authorized it. At this time, when the target collaboration task of the calling applet (first applet) needs to access the target service of the called applet, continue to refer to Figure 6As shown, the specific steps include:

[0120] 1) When a user initiates a target collaboration task, the calling applet queries the database for the target service interface of the called applet corresponding to the target collaboration task;

[0121] The database may store authorized applets and corresponding authorized services (including service interface information of authorized services), or all applets and corresponding services related to the caller applet may be stored in the database, and according to user authorization, the status of the authorized applets and corresponding authorized services is marked as authorized. When the caller applet queries the database to find the target service interface of the called applet corresponding to the target collaborative task, and the target service of the called applet corresponding to the target service interface is in the authorized state, the following step 2) may be executed.

[0122] 2) The calling applet sends a first communication negotiation request to the authentication negotiation module in the application platform. The first communication negotiation request may include basic information of the current service's logged-in user, basic information of the called applet, and target service interface information corresponding to the called applet;

[0123] 3) The authentication negotiation module of the application platform determines whether the logged-in user is no longer subscribed to either the calling applet or the called applet. If so, an error message is returned and the process is terminated;

[0124] For example, when the logged-in user is no longer subscribed to either the caller applet or the called applet, subscription reminder information or subscription controls may be displayed to the user so that the user can continue to perform the target collaborative task through the subscription operation if necessary.

[0125] 4) After confirming that the two mini-programs of the logged-in user are still subscribed, the authentication negotiation module of the application platform sends a second communication negotiation request carrying the basic information of the calling mini-program, the basic information of the logged-in user, and the target service interface information corresponding to the called mini-program to the called mini-program. When sending, the second communication negotiation request will be signed according to the specified protocol to ensure communication security;

[0126] 5) After receiving the second communication negotiation request, the called applet generates verification information, such as a token with a fixed time, and returns it to the authentication negotiation module of the application platform;

[0127] 6) The authentication negotiation module of the application platform sends the token to the calling applet;

[0128] 7) The calling applet communicates with the called applet through the token and the target service interface, and calls the relevant services of the called applet;

[0129] 8) The calling applet uses the token refresh service provided by the called applet to refresh the token when it is about to expire, ensuring that the token is valid;

[0130] 9) If the token expires, follow the process starting from step 2) to request the application platform to negotiate for the token again.

[0131] The communication interaction scheme proposed in this embodiment requires that the mini-program obtain the personal information of the mini-program application platform user level when running, and also provides the mutual coordination function between the mini-programs subscribed by the user, so that the services subscribed by the user can be organically combined into a more powerful service; for different mini-programs in the application platform, the mini-program application platform is used as a negotiation intermediary, and the registration interface, negotiation token and other functions are used to coordinate with each other, so as to provide the application platform users with richer service forms and improve the communication interaction performance.

[0132] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0133] Based on the same inventive concept, the embodiment of the present application also provides a communication interaction device for implementing the communication interaction method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more communication interaction device embodiments provided below can refer to the limitations on the communication interaction method above, and will not be repeated here.

[0134] In an exemplary embodiment, Figure 7 As shown, a communication interaction device is provided, which is applied to an application platform, and the application platform runs a first applet, including: a first receiving module 702, a first sending module 704, a second receiving module 706 and a second sending module 708, wherein:

[0135] The first receiving module 702 is used to receive a first communication negotiation request sent by the first applet; the first communication negotiation request includes target service interface information of the second applet, and the first communication negotiation request is used to request communication interaction with the second applet.

[0136] The first sending module 704 is used to send a second communication negotiation request to the second applet when the target service corresponding to the target service interface information is authorized to the first applet; the second communication negotiation request includes the target service interface information.

[0137] The second receiving module 706 is used to receive the verification information sent by the second applet;

[0138] The second sending module 708 is used to forward the verification information to the first applet to instruct the first applet to communicate with the second applet based on the verification information and the target service interface information.

[0139] In one embodiment, the device further comprises:

[0140] A first display module is configured to display a first rights request interface in the first mini-program before receiving a first communication negotiation request sent by the first mini-program; the first rights request interface includes a mini-program list and a service list, the mini-program list includes at least one mini-program related to the first mini-program and subscribed by the user, and the service list includes at least one service of each mini-program in the mini-program list;

[0141] The first authorization module is used to respond to the first authorization operation triggered by the user in the first authorization request interface, authorize the authorization applet corresponding to the first authorization operation and the authorization service of the authorization applet to the first applet, and send the basic information of the authorization applet and the service interface information corresponding to the authorization service of the authorization applet to the first applet.

[0142] In one of the embodiments, the first communication negotiation request is generated by the first applet according to the target service interface information corresponding to the target service of the second applet when the first applet determines that the target service of the second applet corresponding to the target collaboration task is authorized.

[0143] In one embodiment, the device further comprises:

[0144] A third receiving module is used to receive a permission request sent by the first mini program; the permission request is generated by the first mini program according to a permission opening operation triggered by a user when it is determined that the target service of the second mini program corresponding to the target collaboration task is not authorized;

[0145] The second display module is used to display a second rights request interface in the first applet; the second rights request interface includes the second applet and the target service of the second applet;

[0146] The second authorization module is used to respond to the second authorization operation triggered by the user in the second authorization interface, authorize the target service of the second mini program corresponding to the second authorization operation to the first mini program, and send the target service interface information corresponding to the target service of the second mini program to the first mini program.

[0147] In one embodiment, the device further comprises:

[0148] The fourth receiving module is used to receive at least one service of the second mini program sent by the developer platform after the second mini program is registered and released; at least one service of the second mini program is a service that can be used by other mini programs to communicate and interact with the second mini program, and at least one service of the second mini program includes the target service of the second mini program.

[0149] In one embodiment, the first communication negotiation request also includes basic information of a logged-in user of the application platform, and the first sending module 704 includes:

[0150] A determination unit, used to determine whether the logged-in user has subscribed to the second mini program;

[0151] The sending unit is used to send a second communication negotiation request to the second mini program when it is determined that the logged-in user has subscribed to the second mini program.

[0152] Each module in the above communication interaction device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0153] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal. An application platform may be installed and run in the terminal. A first applet may be run in the application platform. The internal structure diagram of the computer device may be as follows: Figure 8As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a communication interaction method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0154] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0155] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the steps of the communication interaction method in any of the above embodiments are implemented.

[0156] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the communication interaction method in any of the above embodiments are implemented.

[0157] In one embodiment, a computer program product is provided, including a computer program, which implements the steps of the communication interaction method in any of the above embodiments when executed by a processor.

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

[0159] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0160] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0161] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A communication interaction method, characterized in that: Applied to an application platform, the application platform running a first applet, the method comprising: receiving a first communication negotiation request sent by the first applet; the first communication negotiation request includes target service interface information of the second applet, and the first communication negotiation request is used to request communication interaction with the second applet; When the target service corresponding to the target service interface information is authorized to the first applet, sending a second communication negotiation request to the second applet; the second communication negotiation request includes the target service interface information; Receive verification information sent by the second applet, and forward the verification information to the first applet to instruct the first applet to communicate and interact with the second applet based on the verification information and the target service interface information.

2. The method according to claim 1, characterized in that Before receiving the first communication negotiation request sent by the first applet, the method further includes: Displaying a first rights request interface in the first mini-program; the first rights request interface includes a mini-program list and a service list, the mini-program list includes at least one mini-program related to the first mini-program and subscribed by the user, and the service list includes at least one service of each mini-program in the mini-program list; In response to the first authorization operation triggered by the user in the first authorization request interface, the authorization applet corresponding to the first authorization operation and the authorization service of the authorization applet are authorized to the first applet, and the basic information of the authorization applet and the corresponding service interface information of the authorization service are sent to the first applet.

3. The method according to claim 2, characterized in that The first communication negotiation request is generated by the first applet according to the target service interface information corresponding to the target service of the second applet when the first applet determines that the target service of the second applet corresponding to the target collaboration task is authorized.

4. The method according to claim 3, characterized in that The method further comprises: Receiving a request for permission sent by the first mini program; the request for permission is generated by the first mini program according to a permission opening operation triggered by a user when the first mini program determines that the target service of the second mini program corresponding to the target collaborative task is not authorized; Displaying a second rights request interface in the first applet; the second rights request interface includes the second applet and a target service of the second applet; In response to a second authorization operation triggered by the user in the second authorization interface, the target service of the second applet corresponding to the second authorization operation is authorized to the first applet, and the target service interface information corresponding to the target service of the second applet is sent to the first applet.

5. The method according to claim 3, characterized in that: The method further comprises: Receive at least one service of the second mini program sent by the developer platform after the second mini program is registered and released; at least one service of the second mini program is a service that can be used by other mini programs to communicate and interact with the second mini program, and at least one service of the second mini program includes the target service of the second mini program.

6. The method according to claim 1, characterized in that The first communication negotiation request also includes basic information of a logged-in user of the application platform, and the sending of the second communication negotiation request to the second applet includes: Determine whether the logged-in user has subscribed to the second mini program; If so, a second communication negotiation request is sent to the second applet.

7. A communication interaction device, characterized in that: Applied to an application platform, the application platform runs a first applet, and the device includes: A first receiving module, configured to receive a first communication negotiation request sent by the first applet; the first communication negotiation request includes target service interface information of the second applet, and the first communication negotiation request is used to request communication interaction with the second applet; A first sending module, configured to send a second communication negotiation request to the second applet when the target service corresponding to the target service interface information is authorized to the first applet; the second communication negotiation request includes the target service interface information; A second receiving module, used to receive the verification information sent by the second applet; The second sending module is used to forward the verification information to the first applet to instruct the first applet to communicate with the second applet based on the verification information and the target service interface information.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images