CN114237840A

CN114237840A - Resource interaction method, device, terminal and storage medium

Info

Publication number: CN114237840A
Application number: CN202111436006.XA
Authority: CN
Inventors: 杨俊拯
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-11-29
Filing date: 2021-11-29
Publication date: 2022-03-25
Also published as: WO2023093452A1

Abstract

The embodiment of the application discloses a resource interaction method, a resource interaction device, a resource interaction terminal and a storage medium, and belongs to the technical field of communication. The method comprises the following steps: acquiring resource interaction data, wherein the resource interaction data is generated by resource interaction initiating equipment when receiving resource interaction triggering operation on a target application; determining a target application and target interaction equipment based on the resource interaction data, wherein the target application is an application for performing resource interaction, and the target interaction equipment is at least one equipment for performing resource interaction; and calling a target interaction resource at the target interaction device through the target application. According to the scheme of the embodiment of the application, distributed calling of resources can be achieved, and further more types of application functions can be achieved.

Description

Resource interaction method, device, terminal and storage medium

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a resource interaction method, a resource interaction device, a resource interaction terminal and a storage medium.

Background

With the continuous development of Application (App) technology, more and more multifunctional and rich applications are brought to the end, and convenience is brought to daily life of people.

In the related art, before using an application, a user first needs to download an application installation package from an application store, install the application in a terminal by parsing the application installation package, and then click an application icon to start the application. In addition, the user shares the application to other devices, that is, shares the download path of the application installation package to other devices, or sends the application installation package data to other devices. In this case, the shared device needs to download and install the application according to the download path of the application installation package or the data of the application installation package.

Disclosure of Invention

The embodiment of the application provides a resource interaction method, a resource interaction device, a terminal and a storage medium. The technical scheme is as follows:

in one aspect, an embodiment of the present application provides a resource interaction method, where the method includes:

acquiring resource interaction data, wherein the resource interaction data is generated by resource interaction initiating equipment when receiving resource interaction triggering operation on a target application, and the resource interaction triggering operation comprises at least one of sharing operation and sharing operation;

determining the target application and target interaction equipment based on the resource interaction data, wherein the target application is an application for resource interaction, and the target interaction equipment is at least one equipment for resource interaction;

and calling a target interaction resource at the target interaction equipment through the target application.

In another aspect, an embodiment of the present application provides a resource interaction method, where the method includes:

responding to a resource interaction triggering operation of the target application, and generating resource interaction data;

and responding to a resource calling request of the interactive participation equipment, providing target interactive resources for the interactive participation equipment, and sending the resource calling request through the target application after the interactive participation equipment determines the target application and the target interactive equipment based on the resource interactive data.

In another aspect, an embodiment of the present application provides a resource interaction apparatus, where the apparatus includes:

the resource interaction system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring resource interaction data, and the resource interaction data is generated by resource interaction initiating equipment when receiving resource interaction triggering operation on a target application;

a determining module, configured to determine the target application and a target interaction device based on the resource interaction data, where the target application is an application for performing resource interaction, and the target interaction device is at least one device for performing resource interaction;

and the calling module is used for calling the target interaction resource at the target interaction equipment through the target application.

the first generation module is used for responding to resource interaction triggering operation of the target application and generating resource interaction data;

and the providing module is used for responding to a resource calling request of the interactive participation equipment and providing target interactive resources for the interactive participation equipment, wherein the resource calling request is sent by the interactive participation equipment through the target application after the target application and the target interaction equipment are determined by the interactive participation equipment based on the resource interaction data.

In another aspect, an embodiment of the present application provides a terminal, where the terminal includes a processor and a memory, where the memory stores at least one instruction, at least one program, a code set, or a set of instructions, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by the processor to implement the resource interaction method according to the above aspect.

In another aspect, an embodiment of the present application provides a computer-readable storage medium, in which at least one instruction, at least one program, a code set, or a set of instructions is stored, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by a processor to implement the resource interaction method according to the above aspect.

In another aspect, embodiments of the present application provide a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to execute the resource interaction method provided by the above-mentioned aspect.

The technical scheme provided by the application can comprise the following beneficial effects:

in the embodiment of the application, based on the sharing or sharing operation of the target application, the resource interaction initiating device generates resource interaction data, the interaction participating device determines the target application and the target interaction device based on the acquired resource interaction data, and then the target interaction resource at the target interaction device is called through the target application. Compared with the related art, the shared and shared object in the embodiment of the application is not the target application itself but a resource corresponding to the target application. The resources corresponding to the target application are shared with other equipment, so that the other equipment can call the corresponding resources through the target application, and the function of the target application is realized. Through the mechanism, the target application can use the resources of the current equipment and can call the resources of other equipment, so that the distributed calling of the resources is realized, and further more types of application functions can be realized.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.

FIG. 1 illustrates a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application;

FIG. 2 illustrates a flow chart of a resource interaction method provided by an exemplary embodiment of the present application;

FIG. 3 illustrates a flow chart of a resource interaction method provided by another exemplary embodiment of the present application;

FIG. 4 illustrates an application manager interface diagram provided by an exemplary embodiment of the present application;

FIG. 5 illustrates an application manager interface diagram provided by another exemplary embodiment of the present application;

FIG. 6 illustrates an application manager interface diagram provided by another exemplary embodiment of the present application;

fig. 7 is a schematic interface diagram illustrating resource sharing via a graphic code according to an exemplary embodiment of the present application;

FIG. 8 is a schematic diagram illustrating an interface for sharing resources via an interactive link according to an exemplary embodiment of the present application;

fig. 9 is a schematic interface diagram illustrating resource sharing by near field communication according to an exemplary embodiment of the present application;

FIG. 10 illustrates a schematic diagram of a device selector architecture provided by an exemplary embodiment of the present application;

FIG. 11 illustrates a flow chart of a resource interaction method provided by another exemplary embodiment of the present application;

FIG. 12 is a schematic diagram illustrating an interface for canceling resource sharing according to an exemplary embodiment of the present application;

FIG. 13 illustrates a flow chart of a resource interaction method provided by another exemplary embodiment of the present application;

FIG. 14 illustrates a schematic diagram of device level resource sharing provided by an exemplary embodiment of the present application;

FIG. 15 is a schematic diagram illustrating a principle of user-level resource sharing provided by an exemplary embodiment of the present application;

FIG. 16 shows a flowchart of a resource interaction method provided by another example embodiment of the present application;

FIG. 17 illustrates a schematic diagram of an interface for creating a shared group provided by an exemplary embodiment of the present application;

FIG. 18 shows a flowchart of a resource interaction method provided by another example embodiment of the present application;

FIG. 19 is a schematic diagram illustrating an interface for joining a shared group according to an exemplary embodiment of the present application;

FIG. 20 is an interface diagram illustrating resource sharing for a collaborative sketchpad application provided by an exemplary embodiment of the present application;

FIG. 21 illustrates a schematic diagram of device level resource sharing provided by an exemplary embodiment of the present application;

FIG. 22 illustrates a schematic diagram of user-level resource sharing provided by an exemplary embodiment of the present application;

FIG. 23 illustrates an interface diagram for dissembling a shared group provided by an exemplary embodiment of the present application;

FIG. 24 illustrates a schematic diagram of an interface for removing shared members provided by an exemplary embodiment of the present application;

FIG. 25 is a schematic diagram illustrating an interface for exiting a shared group provided by an exemplary embodiment of the present application;

FIG. 26 is a block diagram illustrating an exemplary embodiment of a resource interaction apparatus;

fig. 27 is a block diagram illustrating a structure of a resource interaction apparatus according to another exemplary embodiment of the present application;

fig. 28 shows a block diagram of a terminal according to an exemplary embodiment of the present application.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

Reference herein to "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

The terms appearing herein are explained below.

The micro application is a target application in the embodiment of the present application, and the micro application may be regarded as a set formed by services, and is used to implement a specific business logic, that is, an application function of the micro application, through invocation between the services. Unlike the traditional application which can only run on a specific operating system, the service of the micro application can be the service on different operating systems, namely the micro application supports heterogeneous operating systems, and cross-platform running can be realized. Different from the traditional application which needs to be downloaded before being used and is bound with the device, the micro-application adopts a subscription mechanism and is bound with the user, namely, after the micro-application is subscribed by a certain device under the user account, each device under the user account can use the micro-application. Different from the traditional application that the application installation package needs to be downloaded and installed before the operation, for example, before the android application is operated, the apk package needs to be downloaded, the micro application only needs to download the corresponding application script before the operation, and in the micro application process, the micro application engine executes the application script to realize the application function. Compared with the traditional application, the code amount of the application script is lower, so that the occupied storage space is smaller, and the dynamic deployment and updating are facilitated.

Service: as the minimum unit in the running process of the micro-application, is used for realizing a specific task. For example, the screen capture service is used for realizing the screen capture function of the device, and the screen projection service is used for realizing the screen projection of the display picture between the devices. Moreover, the service called in the running process of the micro application can be a service on the current device or a service on other devices. For example, in the running process of the micro application, the device screenshots of other devices can be obtained by calling the screenshot service on other devices, and the device screenshots of other devices can be displayed by calling the picture display service. Different from the traditional application installation process, all services used in the operation process need to be installed locally in advance, and the service logic of the micro application is dynamically assembled in the operation process, so that the service in the micro application supports dynamic deployment, namely the service corresponding to the service logic is dynamically deployed to the current equipment based on the service logic executed by the current equipment in the operation process. Accordingly, when the application function of the same micro application is implemented by a plurality of devices, since the business logic of different devices may be different, the services deployed at different devices may also have differences, that is, the services in the micro application have the characteristic of differential deployment. In one possible implementation, the services constituting the micro application may include a static service and a dynamic service, where the static service refers to a service provided by the host application and needs to be pre-installed in the device, and the dynamic service refers to a service supporting dynamic deployment and may be dynamically deployed in the device during the running process of the micro application.

It should be noted that, in the embodiment of the present application, the object shared and shared is a resource, and the foregoing service is only one type of resource. Resources in this application thus include file resources, hardware resources, and service resources. File resources are resources that exist in the form of files, such as pictures, videos, audio, word documents, table files, and the like. The hardware resource refers to hardware capability of the device, such as photographing and image capturing capability of a camera, computing capability of a Central Processing Unit (CPU), and the like. Often such resources often require a layer of software interface packaging to be used. The service resources are screen capture service, screen projection service, local search service, navigation service and the like which are proposed in the foregoing.

The following describes an implementation environment of embodiments of the present application.

Referring to fig. 1, a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application is shown. The implementation environment includes a first terminal 111, a second terminal 112, a third terminal 121, and a fourth terminal 122, the first terminal 111 and the second terminal 112 log in a first user account 110, the third terminal 121 and the fourth terminal 122 log in a second user account 120, and the implementation environment further includes a server 130.

In this embodiment, the target application 140 is respectively bound to the first user account 110 and the second user account 120, that is, if any terminal under the first user account 110 or the second user account 120 subscribes to the target application 140, other terminals under the first user account 110 or the second user account 120 also subscribe to the target application 140, so that the first terminal 111, the second terminal 112, the third terminal 121, and the fourth terminal 122 all subscribe to the target application 140.

The target application 140 may be regarded as a collection of multiple resources, where the resources may be file resources such as pictures, files, and videos, or service resources such as a screen capture service and a screen projection service, or hardware resources such as a photographing capability of a camera and a computing capability of a CPU, which is not limited in this embodiment of the present application.

Optionally, the target application 140 may be a photo album application, a multi-device screen capture application, a game screen projection application, a collaborative drawing board application, and the like, which is not limited in this embodiment of the present application. In addition, different applications correspond to different resource types, for example, an album application corresponds to file resources such as pictures and videos, and a multi-device screen capture application, a game screen projection application and the like correspond to service resources such as screen capture services and screen projection services.

The first user account 110 further includes other terminals, which are only exemplified by the first terminal 111 and the second terminal 112 in the embodiment of the present application, and similarly, the second user account 120 also includes other terminals, which are only exemplified by the third terminal 121 and the fourth terminal 122 in the embodiment of the present application. The types of devices of the first terminal 111, the second terminal 112, the third terminal 121, and the fourth terminal 122 are the same or different, and include: the mobile phone comprises at least one of a smart phone, a tablet computer, an electronic book reader, a motion Picture Experts Group Audio Layer III (MP 3) player, a motion Picture Experts Group Audio Layer IV (MP 4) player, a laptop portable computer, a desktop computer, a smart home, an intelligent wearable device and the like.

The first terminal 111, the second terminal 112, the third terminal 121, and the fourth terminal 122, and other terminals are connected to the server 130 through a wireless network or a wired network.

The server 130 may be at least one of a server, a server cluster composed of a plurality of servers, a cloud computing platform, and a virtualization center. The server 130 is deployed with the following modules: user management 131, device group management 132, shared group management 133, and resource gateway management 134. The user management 131 is configured to manage user account information, and the device group management 132 is configured to manage all device information corresponding to a user account. The shared group management 133 is used to manage devices or user accounts in a shared group when sharing resources. The resource gateway management 134 is used for managing a mapping relationship between the device and the resource gateway, and is used for implementing resource calling of the application.

In the embodiment of the application, sharing or sharing of resources can be realized among different terminals and different users. The sharing refers to that the sharing party shares the resource with the shared party, and the shared party can call the resource of the sharing party. In a possible implementation manner, the sharing party and the shared party may be terminals, and the terminals may be different terminals under the same user account, or different terminals under different user accounts, for example, the sharing party and the shared party may be any two terminals among the first terminal 111, the second terminal 112, the third terminal 121, and the fourth terminal 122. For example, the first terminal 111 is taken as a sharing party, and the third terminal 121 is taken as a shared party. The third terminal 121 as the shared party may invoke the resource corresponding to the target application 140 in the sharing party first terminal 111.

In another possible implementation, the sharing party and the shared party may be different users. For example, the first user account 110 is taken as a sharing party, and the second user account 120 is taken as a shared party. Any terminal in the second user account 120 may invoke the resource corresponding to the target application 140 in all terminals in the first user account 110, for example, the third terminal 121 in the second user account 120 may invoke the resource corresponding to the target application 140 in the first terminal 111 and the second terminal 112 in the first user account 110.

The sharing refers to that a plurality of sharing members are associated together to form a sharing group, and all the sharing members in the same group can mutually call the resources of other members. In one possible embodiment, the sharing group member may be a terminal, for example, the sharing group member may be at least two terminals of the first terminal 111, the second terminal 112, the third terminal 121, and the fourth terminal 122. Illustratively, the first terminal 111, the second terminal 112, and the third terminal 121 form a sharing group, and all terminals may mutually call the resource corresponding to the target application 140 in other terminals. For example, the first terminal 111 may call the second terminal 112, the third terminal 121 and include the resources corresponding to the target application 140 in itself, and similarly, the second terminal 112 and the third terminal 121 are also called.

In another possible implementation, the members of the shared group may also be different users. For example, the first user account 110 and the second user account 120 form a sharing group, and the members in the sharing group include all terminals under the first user account 110 and the second user account 120, that is, the members in the sharing group are the first terminal 111, the second terminal 112, the third terminal 121, and the fourth terminal 122, and all the terminals can mutually call resources corresponding to the target application 140 in other terminals. For example, the first terminal 111 may call the second terminal 112, the third terminal 121, the fourth terminal 122 and include the resources corresponding to the target application 140 in itself; the second terminal 112 may invoke the first terminal 111, the third terminal 121, the fourth terminal 122 and include the resources corresponding to the target application 140 in itself. Similarly, the same applies to the third terminal 121 and the fourth terminal 122.

In the embodiment of the present application, a resource interaction method is described by taking a resource interaction initiating device and an interaction participating device as examples. The resource interaction initiating device and the interaction participating device may be a smart phone, a television, a Personal Computer (PC), an intelligent wearable device, an intelligent home, and the like, which is not limited in the embodiment of the present application. Optionally, the resource interaction initiating device and the interaction participating device may be different devices of the same user, or may also be different devices of different users, which is not limited in this embodiment of the present application. Referring to fig. 2, a flowchart of a resource interaction method provided by an exemplary embodiment of the present application is shown, where the method includes:

step 210, in response to the resource interaction triggering operation for the target application, the resource interaction initiating device generates resource interaction data.

In the embodiment of the application, the resource interaction initiating device subscribes to the target application, and generates resource interaction data when receiving the resource interaction triggering operation of the target application by the user.

In one possible implementation, the target application may be a micro-application.

Optionally, the target application may be an album application, a multi-device screen capture application, a game fighting application, a collaborative drawing board application, and the like, which is not limited in this embodiment of the present application.

In one possible implementation, the resource interaction triggering operation may be a sharing operation.

Optionally, the sharing operation may be a click operation, a long-press operation, and the like of a sharing key of the target application interface, which is not limited in this embodiment of the present application.

It should be noted that sharing means that the resource interaction mode is unidirectional, that is, the resource interaction initiating device shares the interaction resource to the interaction participating device, and the interaction participating device may invoke the resource of the resource interaction initiating device, but the resource interaction initiating device cannot invoke the resource of the interaction participating device.

In another possible implementation, the resource interaction triggering operation may be a sharing operation.

Optionally, the sharing operation may be a click operation, a long-press operation, and the like on a sharing key of the target application interface, which is not limited in this embodiment of the application.

It should be noted that sharing refers to that the resource interaction mode is bidirectional, that is, the resource interaction initiating device shares the interaction resource to the interaction participating device, and the interaction participating device and the resource interaction initiating device can mutually invoke the resource of the other party.

And the resource interaction data carries identification information, wherein the identification information at least comprises a target application identification, so that the resource interaction initiating device and the interaction participating device perform resource interaction. The resource interaction data generated by the resource interaction initiating device is different when the resource interaction triggering operation is different, that is, the target application is respectively subjected to the sharing operation and the sharing operation.

Step 220, the interactive participation device obtains resource interaction data.

Regarding the manner of acquiring the resource interaction data, in a possible embodiment, the resource interaction initiating device may send the resource interaction data, and the interaction participating device acquires the resource interaction data. In another possible implementation manner, after the resource interaction initiating device encapsulates the resource interaction data, the interaction participating device obtains the resource interaction data from the resource interaction initiating device.

In step 230, the interaction participating device determines a target application and a target interaction device based on the resource interaction data, where the target application is an application for performing resource interaction, and the target interaction device is at least one device for performing resource interaction.

In the embodiment of the application, the resource interaction data includes identification information for determining the target application and the target interaction device, and the interaction participation device determines the target application and the target interaction device based on the identification information.

Optionally, the number of target interaction devices may be one or multiple, and this is not limited in this embodiment of the application.

Optionally, the target interaction device may be different devices of the same user, or may also be different devices of different users, which is not limited in this embodiment of the present application.

In addition, it should be noted that the resource interaction initiating device is one of the target interaction devices, and in the embodiment of the full text application, for convenience of description, the target interaction device is taken as the resource interaction initiating device for example.

Step 240, after the interactive participation device determines the target application and the target interactive device based on the resource interactive data, the resource calling request is sent through the target application.

And after determining the target application and the target interaction equipment, the interaction participation equipment sends a resource calling request to the resource interaction initiating equipment. The resource calling request is used for calling a target interaction resource at the target interaction device, and the target interaction resource is determined according to the service logic of the target application, namely the resource required to be used for realizing the application function of the target application.

In step 250, in response to the resource call request of the interactive participation device, the resource interaction initiating device provides the target interactive resource to the interactive participation device.

And after receiving the resource calling request of the interaction participation equipment, the resource interaction initiating equipment provides target interaction resources for the interaction participation equipment. The target interaction resource may be a file resource, a hardware resource, a service resource, and the like, which is not limited in this embodiment of the present application.

Optionally, the file resource may be a picture, a video, an audio, a word document, a table file, and the like, which is not limited in this embodiment of the present application.

Optionally, the hardware resource may be a photographing capability of the camera, a camera shooting capability, various sensor capabilities, a hardware computing capability, and the like, which is not limited in this embodiment of the application.

Optionally, the service resource may be a screen capture service, a local search service, a video playing service, a navigation service, a screen projection service, and the like, which is not limited in this embodiment of the present application.

In addition, it should be noted that different target applications correspond to different target interaction resources. For example, if the target application is an album application, the corresponding target interactive resource is a picture or a video and belongs to one of file resources; if the target application is a multi-camera application, the corresponding target interaction resource is the shooting and camera shooting capability of the camera and belongs to one of hardware resources; if the target application is the screen capture service application, the corresponding target interaction resource is the screen capture service and belongs to one of the service resources.

In step 260, the interactive participation device calls a target interactive resource at the target interactive device through the target application.

The interaction participation device calls a target interaction resource at the target interaction device through the target application of the interaction participation device.

The interactive participation equipment sends a calling request to the target interactive equipment through the target application to request to call the target interactive resource, and the target interactive equipment locally calls the target interactive resource and feeds back a calling result to the interactive participation equipment. Taking the target application as an album application as an example, the interactive participation device sends a call request to the target interaction device through the album application to request to call the photo resource of the album application, and the target interaction device calls the local photo resource and feeds the photo resource back to the interactive participation device.

In summary, in the embodiment of the present application, based on the sharing or sharing operation on the target application, the resource interaction initiating device generates resource interaction data, and the interaction participating device determines the target application and the target interaction device based on the acquired resource interaction data, so as to invoke the target interaction resource at the target interaction device through the target application. Compared with the related art, the shared and shared object in the embodiment of the application is not the target application itself but a resource corresponding to the target application. The resources corresponding to the target application are shared with other equipment, so that the other equipment can call the corresponding resources through the target application, and the function of the target application is realized. Through the mechanism, the target application can use the resources of the current equipment and can call the resources of other equipment, so that the distributed calling of the resources is realized, and further more types of application functions can be realized.

In the embodiment of the application, the target application is determined through the application manager, the target interaction device is determined through the application manager and the device selector, and the target interaction resource at the target interaction device is called through the resource gateway. The resource interaction method is described below by taking a resource interaction initiating device and an interaction participating device as examples. Referring to fig. 3, a flowchart of a resource interaction method provided by another exemplary embodiment of the present application is shown, where the method includes:

in step 310, in response to the resource interaction triggering operation on the target application, the resource interaction initiating device generates resource interaction data through an application manager, where the application manager is used to manage resource interaction of different applications.

The resource interaction initiating device is deployed with an application manager, and the application manager is used for managing application and realizing resource interaction between the resource interaction initiating device and the interaction participating device.

In one possible implementation, the application manager may be an application with a UI (user interface).

Regarding the modality of the application manager, in one possible implementation, the application manager may be a super application, which may be one piece of client software that manages a variety of different applications. The user can subscribe or unsubscribe to the application in the super application. The user can also select a target application from the super applications and perform sharing operation or sharing operation on the target application. Illustratively, as shown in FIG. 4, the super application includes an application list interface 41 and an application details interface 42. The application list interface 41 displays the different applications to which the user has subscribed. And taking the application A as a target application, clicking the application A43 by a user, receiving a triggering operation of the user on the application A43 by the resource interaction initiating device, entering an application detail interface 42, wherein the application detail interface 42 comprises a sharing key 421 and a sharing key 422, and the super application generates resource interaction data by clicking the sharing key 421 or the sharing key 422.

In another possible implementation, the application manager may be implemented in an application icon option. Illustratively, as shown in fig. 5, taking application a as a target application, a user presses an icon of application a52 for a long time, the resource interaction initiating device receives a user's trigger operation on application a52, pops up the operation option interface 51, the operation option interface 51 includes a share button 511 and a share button 512, and the super application generates resource interaction data by clicking on the share button 511 and the share button 512.

In another possible embodiment, the application is embedded in the form of an insert. For example, as shown in fig. 6, when an application a is taken as a target application, and a user opens the application a62, the resource interaction initiating device receives a trigger operation of the user on an application a62, the interface of the application a62 pops up the sharing operation interface 61, the sharing operation interface 61 includes a sharing key 611 and a sharing key 612, and the super application generates resource interaction data by clicking the sharing key 611 or the sharing key 612.

311, the resource interaction initiating device generates a graphic code based on the resource interaction data; or, generating an interaction link based on the resource interaction data; or sending the resource interaction data in a near field communication mode.

In a possible implementation manner, after a user performs a resource interaction triggering operation on a target application, a resource interaction initiating device generates a graphic code, where the graphic code includes resource interaction data.

Optionally, the graphic code may be a two-dimensional code, a barcode, and the like, which is not limited in this embodiment of the application.

Illustratively, as shown in fig. 7, the album application is taken as a target application, and the application manager is taken as a super application as an example. The user 76 clicks the album application 711 on the application list interface 71 of the super application, the resource interaction initiating device receives the triggering operation of the album application 711 by the user 76, and the resource interaction initiating device enters the application detail interface 72, and the application detail interface 72 includes a sharing key 721 and a sharing key 722. The user 76 clicks the sharing key 721, the resource interaction initiating device receives the triggering operation of the user 76 on the sharing key 721, generates resource interaction data through the super application, and displays the sharing mode interface 73. When the user clicks the two-dimensional code sharing key 731, the resource interaction initiating device receives a trigger operation of the user on the two-dimensional code sharing key 731, and generates a two-dimensional code 74, where the two-dimensional code 74 includes resource interaction data.

In another possible implementation manner, after the user performs the resource interaction triggering operation on the target application, the resource interaction initiating device generates an interaction link, where the interaction link includes resource interaction data.

Optionally, the interactive link may be a short message link, a WeChat link, or the like, which is not limited in this embodiment of the application.

Illustratively, as shown in fig. 8, the game fighting application is used as a target application, and the application manager is used as a super application. The user 86 clicks the game viewing application 811 on the application list interface 81 of the super application, the resource interaction initiating device receives the triggering operation of the user 86 on the game viewing application 811, and the resource interaction initiating device enters the application detail interface 82, wherein the application detail interface 82 comprises a sharing key 821 and a sharing key 823. The user 86 clicks the sharing key 821, the resource interaction initiating device receives the triggering operation of the user 86 on the sharing key 821, resource interaction data is generated through the super application, and the sharing mode interface 83 is displayed. The user 86 clicks the short message sharing key 831, the resource interaction initiating device receives the triggering operation of the user 86 on the short message sharing key 831, and generates a short message link 84, and the short message link 84 contains resource interaction data.

In another possible implementation, after the user performs the resource interaction triggering operation on the target application, the resource interaction initiating device sends an NFC (near field communication) signal, where the NFC signal carries the resource interaction data.

Illustratively, as shown in fig. 9, the multi-device screenshot application is taken as a target application, and the application manager is taken as a super application as an example. The user 94 clicks the multi-device screenshot application 911 on the application list interface 91 of the super application, the resource interaction initiating device receives the triggering operation of the user 94 on the multi-device screenshot application, and the resource interaction initiating device enters the application detail interface 92, and the application detail interface 92 comprises a sharing key 921 and a sharing key 922. The user 94 clicks the sharing key 921, the resource interaction initiating device receives the triggering operation of the user 94 on the sharing key 921, resource interaction data is generated through the super application, and the sharing mode interface 93 is displayed. The user 94 clicks the touch-and-play sharing key 931, and the resource interaction initiating device receives a trigger operation of the user 94 on the touch-and-play sharing key 931 and simultaneously sends an NFC signal, where the NFC signal includes resource interaction data.

Step 312, the interactive participation device analyzes the graphic code to obtain resource interactive data; or, the resource interaction data is obtained by analyzing the interaction link; or receiving the resource interaction data in a near field communication mode.

In a possible implementation manner, the interaction participating device obtains the resource interaction data by analyzing the graphic code generated by the resource interaction initiating device.

Illustratively, as shown in fig. 7, the resource interaction initiating device generates a two-dimensional code 74, the two-dimensional code 74 includes resource interaction data, the user 77 scans the two-dimensional code 74 through a scanning control 751 in an application list interface 75 of a super application in the interaction participating device, and the interaction participating device parses the resource interaction data from the two-dimensional code 74.

In another possible implementation manner, the interaction participating device obtains the resource interaction data by analyzing the interaction link sent by the resource interaction initiating device.

Illustratively, as shown in fig. 8, the resource interaction initiating device generates a short message link 84 and sends the short message link 84 to the interaction participating device, where the short message link 84 includes resource interaction data. The interactive participation device receives the short message link 84, and when the user 87 clicks the short message link 84, the interactive participation device analyzes the short message link 84 to obtain the resource interactive data.

In another possible implementation manner, the interaction participating device receives an NFC signal sent by the resource interaction initiating device to obtain the resource interaction data.

For example, as shown in fig. 9, the resource interaction initiating device generates resource interaction data through the super application and sends an NFC signal, where the NFC signal includes the resource interaction data, and the interaction participating device receives the NFC signal sent by the resource interaction initiating device, that is, receives the resource interaction data.

Step 313, based on the resource interaction data, the interaction participation device determines a target application through the application manager, and starts the target application, and the application manager is used for managing resource interaction of different applications.

In the embodiment of the application, the interactive participation device is deployed with an application manager, and the application manager is used for managing the applications subscribed in the interactive participation device. Because the resource interaction data carries identification information, wherein the identification information at least comprises a target application identification, the interaction participation equipment determines a target application through the application manager based on the target application identification in the resource interaction data, and starts the target application in the interaction participation equipment.

Illustratively, as shown in fig. 7, the interactive participation device parses the resource interaction data from the two-dimensional code 74, determines the target application as an album application 78 through the super application of the interactive participation device based on the target application identifier in the resource interaction data, and starts the album application 78.

Illustratively, as shown in fig. 8, the interactive participation device parses the resource interaction data from the short message link 84, determines the target application as a game play application 85 through the super application of the interactive participation device based on the target application identifier in the resource interaction data, and starts the game play application 85.

For example, as shown in fig. 9, the interaction participant device receives an NFC signal sent by the resource interaction initiator device, obtains resource interaction data from the NFC signal, determines, based on a target application identifier in the resource interaction data, that a target application is a multi-device screenshot application 95 through a super application of the interaction participant device, and starts the multi-device screenshot application 95.

Step 314, based on the resource interaction data, the interaction participation device determines the target interaction device through the application manager and the device selector.

In an embodiment of the application, a device selector determines a target interaction device and generates a target resource gateway address of the target interaction device.

In the embodiment of the present application, the device selector includes three sub-modules, which are an application device group management sub-module, a device selection policy sub-module, and a gateway conversion sub-module. The application device group management submodule is used for managing the device group range of the current running of the target application, namely the device range of the resources which can be called by the target application.

In addition, the device group range of the application device group management submodule is not fixed. In a possible implementation manner, in a default state, the device group range of the application device group management submodule is the current device or the device under the current user account. The default state indicates that the current device or the device under the current user account does not perform resource interaction with other devices. Illustratively, when the interactive participation device does not perform resource interaction with the resource interaction initiating device, the device group range of the application device group management submodule of the interactive participation device is the interactive participation device.

In another possible implementation, in the case of resource interaction, the device group range of the application device group management submodule changes, and the device group range is set by the application manager. Under the condition of resource interaction, the device on which the target application runs not only includes the current device or the device under the current user account, but also includes the device performing resource interaction with the device or the device under the user account, so that the device group range of the application device group management submodule changes. Since the application manager is used to manage resource interactions of the application, the scope of the device can be determined by the application manager, and thus the device group scope of the application device group management submodule can be determined by the application manager. Illustratively, when the interaction participation device performs resource interaction with the resource interaction initiation device, the device group range of the application device group management submodule is set as the interaction participation device and the resource interaction initiation device through the application manager.

The device selection strategy submodule is used for providing a plurality of device selection strategies, namely determining target interaction devices from the device group range managed by the application device group management submodule and forming a target interaction device list.

Optionally, the device selection policy may be to select all devices, select a current device, select another device, and the like, which is not limited in this embodiment of the application. Wherein, selecting other devices means selecting all devices except the current device.

Optionally, the device selection policy may be to select a specific device, for example, select a mobile phone device, select a television device, and the like, which is not limited in this embodiment of the application.

In a possible implementation manner, the target application interface has an equipment selection interface, different equipment selection policy keys exist in the equipment selection interface, for example, all equipment keys are selected, a current equipment key is selected, other equipment keys are selected, or a specific equipment key is selected, and a user clicks different equipment selection policy keys according to own requirements.

In the embodiment of the application, by adjusting the device group range managed by the application device group management submodule and the device selection policy provided by the device selection policy submodule, an application developer can directly share resources among different devices and different users without perceiving the devices and without changing the application.

And the gateway conversion sub-module converts the target interactive equipment list acquired from the equipment selection strategy sub-module into a corresponding target gateway address list.

For example, as shown in fig. 10, the device selector 1003 includes three sub-modules, namely a device selection policy sub-module 1004, a gateway conversion sub-module 1005, and an application device group management sub-module 1006. When the interaction participating device obtains the resource interaction data, the target application 1002 is determined by the application manager 1001 based on the target application identifier of the resource interaction data, and the device group range managed by the application device group management sub-module 1006 is set by the application manager 1001, where the device group range is all devices currently running in the target application, and includes not only the resource interaction initiating device and the interaction participating device, but also other devices. These devices may belong to the same user or to different users. Further, the target application 1002 transmits its own device selection policy, for example, all devices are selected, to the device selection policy sub-module 1004, and based on the device selection policy, the device selection policy sub-module 1004 selects a target interaction device from the range of device groups managed by the application device group management sub-module 1006, and generates a target interaction device list.

Step 315, after the interactive participation device determines the target application and the target interactive device based on the resource interactive data, the resource calling request is sent through the target application.

Step 315 is performed in step 240, which is not described in detail in this embodiment of the present application.

Step 316, in response to the resource invoking request of the interactive participation device, the resource interaction initiating device provides the target interactive resource to the interactive participation device through the resource gateway, and the resource gateway is used for managing the invoking of the resource in the device.

The resource interaction initiating device is provided with a resource gateway, and when receiving a resource calling request of the resource interaction initiating device, the resource interaction initiating device calls a target interaction resource of a local target application through the resource gateway and provides the target interaction resource for the interaction participating device through the resource gateway.

The resource gateway is a unified entry gateway that calls resources on the target interaction device and supports access to different types of resources.

Optionally, the resource gateway provides a file server to support access to file-type resources, such as access to pictures, videos, word documents, and the like.

Optionally, the resource gateway provides an HTTP (hypertext transfer protocol) server to support calling services on the device through restful api. The service may be a screen capture service, a screen projection service, or the like.

Step 317, in response to the gateway address update of the resource gateway, the resource interaction initiating device sends a gateway address update message to the server, so that the server synchronizes the updated gateway address to the device selector of the other device, where the device selector stores the mapping relationship between the device identifier and the gateway address.

In a possible implementation manner, since the unused applications correspond to different resources, when the resource interaction initiating device subscribes to a new application or unsubscribes from an application, the resource interaction initiating device automatically updates the gateway address of the resource gateway, and manages and synchronizes the updated gateway address to the resource gateway of the server side. In order to ensure the consistency of resources during resource sharing and sharing, the resource gateway manages and synchronizes the updated gateway address to the device selector of other devices. The device selector stores the mapping relation between the device and the gateway address.

Step 318, based on the device identifier of the target interactive device, the interactive participating device obtains a target resource gateway address of the target interactive device, where the target resource gateway address is a gateway address of a resource gateway in the target interactive device, and the resource gateway is used to manage the calling of resources in the device.

In the embodiment of the application, resource gateway management is deployed at a server side and is used for managing the mapping relationship between target interaction equipment and a resource gateway. That is, when we need to call the resource on the target interactive device, it needs to manage and query the access address of the resource gateway at the target interactive device through the resource gateway before the resource at the target interactive device can be called. Because the device selector stores the mapping relation between the device identifier and the gateway address, the gateway conversion submodule in the device selector in the interaction participation device acquires the corresponding relation between the target interaction device and the resource gateway from the resource gateway management based on the device identifier of the target interaction device, converts the corresponding relation one by one, generates the target resource gateway address, and feeds the target resource gateway address back to the target application.

In one possible implementation, the resource gateway of the target interaction device may be discovered through an active registration mechanism.

In another possible implementation, the resource gateway of the target interaction device may be discovered through an auto discovery mechanism.

For example, as shown in fig. 10, the device selection policy sub-module 1004 transmits the target interaction device list to the gateway conversion sub-module 1005, the gateway conversion sub-module 1005 obtains the corresponding relationship between the target interaction device and the resource gateway from the resource gateway management 1007 at the server side, converts the target interaction device and the resource gateway one by one, and generates a target resource gateway address, and the gateway conversion sub-module 1005 feeds back the generated target resource gateway address to the target application 1002.

Step 319, based on the target resource gateway address, the interactive participating device accesses the target resource gateway through the target application to obtain the target interactive resource.

And the interaction participation equipment accesses the resource gateway in the target interaction equipment through the target application based on the target resource gateway address to acquire the target interaction resource.

In the embodiment of the application, the target application is determined through the application manager, the target interaction device is determined through the application manager and the device selector, and the target interaction resource at the target interaction device is called through the resource gateway, so that distributed calling of the resource is realized, and further more types of application functions can be realized.

In a possible implementation manner, when the resource interaction triggering operation is a sharing operation, the resource interaction data includes a target application identifier, a sharing party identifier and a sharing instance identifier, the target application identifier is used for determining a target application, the sharing party identifier is used for determining a target interaction device, and the sharing instance identifier is used for obtaining a target interaction resource. A resource sharing method is described below, as shown in fig. 11, which illustrates a resource interaction method provided in another exemplary embodiment of the present application, and the method is applied to a resource interaction initiating device, i.e., a sharing party. It should be noted that the resource interaction initiating device is one of the sharing parties, and for convenience of description, the sharing party is taken as the resource interaction initiating device for example.

Step 1101, in response to the device-level sharing operation on the target application, the resource interaction initiating device generates, through the application manager, resource interaction data including a target application identifier and a device identifier.

In this embodiment, the device-level sharing operation means that both the sharing party and the shared party are devices, and the devices may be different devices of the same user or different devices of different users. In this case, the resource interaction data generated by the resource interaction initiating device through the application manager includes the target application identifier and the device identifier, where the device identifier is used to characterize the device corresponding to the sharing party. The target application identifier and the device application identifier have uniqueness, so that different target applications correspond to different target application identifiers, and different devices correspond to different target interaction device identifiers.

Step 1102, in response to a user-level sharing operation on the target application, the resource interaction initiating device generates resource interaction data including a target application identifier and a user identifier through the application manager, where the user identifier is used to characterize a user corresponding to the sharing party.

In this embodiment, the user-level sharing operation means that both the sharing party and the shared party are users, and one device or multiple devices may be provided under the user account. In this case, the resource interaction data generated by the resource interaction initiating device through the application manager includes the target application identifier and the user identifier, where the user identifier is used to represent the user account information. The target application identifier and the user identifier have uniqueness, so that different target applications correspond to different target application identifiers, and different user accounts correspond to different user identifiers. In addition, it should be noted that the user identifier is used to represent user account information corresponding to the sharing party, but not user account information corresponding to the shared party.

Step 1103, in response to the resource invocation request of the interaction participation device, the resource interaction initiating device performs permission verification on the sharing instance identifier included in the resource invocation request.

In the embodiment of the application, the resource interaction data further includes a sharing instance identifier, and the sharing instance identifier is used for indicating an event of the shared party calling the sharing party resource. The sharing instance identifier has uniqueness, so that different events of the shared party calling the sharing party resource correspond to different sharing instance identifiers.

And when the interaction participating equipment determines the target application and the target interaction equipment based on the target application identification and the equipment identification or the user identification in the resource interaction data, sending a calling request to the resource interaction initiating equipment, wherein the calling request is used for calling the target interaction resource at the target interaction equipment. Since the calling request includes the sharing instance identifier, the resource interaction initiating device needs to perform permission verification on the sharing instance identifier before the interaction participating device calls the target interaction resource at the target interaction device. And the authority check is used for verifying whether the target interaction resource provided by the resource interaction initiating device is consistent with the target interaction resource required by the interaction participating device.

And step 1104, in response to the sharing instance identifier passing the permission check, the resource interaction initiating device provides the target interaction resource to the interaction participating device.

In a possible implementation manner, the resource interaction initiating device provides the target interaction resource to the interaction participating device if the sharing instance identifier passes the permission check.

In another possible implementation manner, if the resource interaction initiating device fails to verify the authority of the sharing instance identifier, the target interaction resource cannot be provided to the interaction participating device.

In step 1105, in response to the sharing cancellation operation on the target application, the resource interaction initiating device deletes the sharing instance identifier.

In a possible implementation manner, the sharing party already completes the sharing of the resource to the shared party, and based on the user cancelling the sharing, the sharing party deletes the sharing instance identifier. For example, a user performs a sharing cancellation operation on a target application, a resource interaction initiating device receives the sharing cancellation operation of the user on the target application, the resource interaction initiating device deletes a sharing instance identifier, and an interaction participating device cannot call a resource of the resource interaction initiating device.

In another possible implementation manner, in the process of sharing resources with the shared party by the sharing party, the user cancels the sharing, and the sharing party deletes the sharing instance identifier. For example, in the process of sharing resources with the interaction participation device, the resource interaction device performs a sharing cancellation operation on the target application by the user, the resource interaction initiation device receives the sharing cancellation operation on the target application by the user, the resource interaction initiation device deletes the sharing instance identifier, and the interaction participation device cannot call the resources of the resource interaction initiation device.

For example, as shown in fig. 8, the target application is a game play application, the application manager is a super application, and a game play device-level sharing operation is described as an example, in this case, the sharing party is a resource interaction initiating device, and the shared party is an interaction participating device. The user 86 clicks the game viewing application 811 on the application list interface 81 of the super application, the resource interaction initiating device receives the triggering operation of the user 86 on the game viewing application 811, and the resource interaction initiating device enters the application detail interface 82, wherein the application detail interface 82 comprises a sharing key 821 and a sharing key 823. The user 86 clicks the sharing key 823, the resource interaction initiation device receives a triggering operation of the sharing key 823 by the user 86, generates resource interaction data through the super application, and displays the sharing mode interface 83. The user 86 clicks the short message sharing key 831, the resource interaction initiating device receives a triggering operation of the user on the short message sharing key 831, and generates a short message link 84, the short message link 84 contains resource interaction data, the resource interaction data comprises a game fighting application identifier, and the device identifier is a resource interaction initiating device identifier and a sharing instance identifier. The resource interaction initiating device sends the short message link 84 to the interaction participating device, the user 87 clicks the short message link 84, the interaction participating device obtains resource interaction data by analyzing the short message link 84, determines that the game fighting application is the target application through the application identifier, and sends a resource calling request to the resource interaction initiating device, wherein the resource calling request comprises a sharing instance identifier, namely the interaction participating device needs to call the resource of the resource interaction initiating device, namely screen throwing service. The resource interaction initiating device receives a resource calling request of the interaction participating device, authority verification is carried out on a sharing instance identifier contained in the resource calling request, namely the resource provided by the resource interaction initiating device for the interaction participating device is screen throwing service, the resource required by the interaction participating device is screen throwing service, the resource interaction initiating device and the resource are consistent, the resource interaction initiating device passes the authority verification on the sharing instance identifier, the interaction participating device calls the screen throwing resource of the resource interaction initiating device, and a game of a sharing party is watched through a game watching application 85 of the interaction participating device.

Illustratively, as shown in fig. 12, during a game process in the interactive participation device screen-shooting resource interaction initiating device, the user 86 clicks the game fighting application 811 again on the application list interface 81 of the super application, the resource interaction initiating device receives a trigger operation of the user 86 on the game fighting application 811, enters a cancel interface 1201, the cancel interface 1201 includes a cancel sharing key 1202, the user clicks the cancel sharing key 1202, and the resource interaction initiating device receives the trigger operation of the user 86 on the cancel sharing key 1202, enters the application detail interface 82, and deletes a sharing instance identifier. When the user 87 clicks the short message link 84 again and receives the short message, the interaction participation device cannot call the screen projection service of the resource interaction initiating device because the resource interaction initiating device deletes the sharing instance identifier, and the game fighting application 85 displays a black screen.

A resource sharing method is described below, as shown in fig. 13, which illustrates a resource interaction method provided in another exemplary embodiment of the present application, and the method is applied to an interaction participating device, i.e., a shared party. It should be noted that the interactive participation device is one of the shared parties, and for convenience of identification, the shared party is taken as the interactive participation device for example.

Step 1301, the interaction participation device obtains resource interaction data, the resource interaction data is generated by the resource interaction initiating device when receiving a sharing operation of the target application, and the resource interaction data comprises a target application identifier and a sharing party identifier.

The interaction participating device obtains the resource interaction data from the resource interaction initiating device. The resource interaction data comprises a target application identifier and a sharing party identifier. The target application identification is used for determining the target application, and the sharing party identification is used for determining the target interaction equipment. In the implementation of the present application, the target interaction device is a resource interaction initiating device, but it should be noted that the target interaction device is not limited to the resource interaction initiating device.

In a possible implementation manner, when the sharing manner of the resource interaction initiating device and the interaction participating device is device-level sharing, the sharing party identifier is a device identifier.

In another possible implementation manner, when the sharing manner of the resource interaction initiating device and the interaction participating device is user-level sharing, the sharing party identifier is a user identifier.

Step 1302, based on the resource interaction data, the interaction participation device determines a target application through an application manager, and starts the target application, where the application manager is used to manage resource interaction of different applications.

In the embodiment of the application, based on the target application identifier in the resource interaction data, the interaction participating device determines the target application through the application manager, the application and the application of the resource interaction initiating device are the same application, and the target application is run.

In this embodiment of the present application, the sharing party identifier may be an apparatus identifier or a user identifier, and methods for determining the target interaction apparatus in these two cases are different, which are described below.

And step 1303, in the case that the sharing party identifier is the device identifier, the interaction participating device determines the device characterized by the device identifier as a candidate interaction device through the application manager.

In a possible implementation manner, based on the sharing party identifier in the resource interaction data being the device identifier, the application manager in the interaction participating device configures, through the device identifier, a device group range managed by the application device group management submodule in the device selector, where the device group range includes all devices of the sharing party, and determines devices in the device group range as candidate interaction devices. For example, in the embodiment of the present application, the sharing party is only the resource interaction initiating device, and therefore the device range is the resource interaction initiating device, and the resource interaction initiating device is the candidate interaction device.

Optionally, the number of candidate interaction devices may be one or multiple, which is not limited in this embodiment of the application.

In step 1304, when the sharing party identifier is the user identifier, the interaction participation device obtains at least one device identifier corresponding to the user identifier through the application manager, and determines the device represented by the device identifier as a candidate interaction device.

In the embodiment of the application, a user management module and a device management module are deployed at the server end. The user management module is used for managing information of all user accounts, and the equipment management module is used for managing equipment information under each user account. The user identification is used for representing user account information, the equipment identification is used for representing corresponding equipment information under a user account, the number of equipment under the user account can be one or more, and different equipment corresponds to different equipment identifications.

In a possible implementation manner, based on the sharing party identifier in the resource interaction data being the user identifier, the application manager of the interaction participating device queries, through the user identifier, the user management module and the device management module for a device list under the user account corresponding to the user identifier. Further, the application manager configures, through the user identifier, a device group range managed by the application device group management submodule in the device selector, where the device group range is a device list queried by the application manager, and determines all devices in the device list as candidate interactive devices.

In addition, step 1303 and step 1304 may be selected to be executed alternatively, which is not limited in this embodiment of the application.

Step 1305, the interactive participation device obtains a device selection policy of the target application; and determining the selected interactive equipment which accords with the equipment selection strategy as the target interactive equipment through the equipment selector.

When the sharing party and the shared party share the target application device, the interactive participation device acquires a device selection strategy of the target application based on the triggering operation of the user on a device selection interface of the target application, and transmits the device selection strategy into a device selection strategy sub-module of the device selector, and the device selection strategy sub-module screens out the target interactive device from a device group range, namely candidate interactive devices, managed by the application device group management sub-module based on the device selection strategy.

Step 1306, the interactive participation device displays a device selection list based on the candidate interactive devices; and determining the selected candidate interaction device in the device selection list as the target interaction device through the device selector.

When the sharing party and the shared party share at a user level, interactive participation equipment acquires an equipment selection strategy of a target application based on the triggering operation of a user on a target application equipment selection interface, and transmits the equipment selection strategy to an equipment selection strategy submodule of an equipment selector, wherein the equipment selection strategy submodule screens out target interactive equipment from an equipment selection list (namely a candidate interactive equipment) which is an equipment group range managed by an application equipment group management submodule based on the equipment selection strategy. It should be noted that, at this time, the interactive participation device is any device under the account of the user of the shared party.

It should be noted that, step 1305 and step 1306 may be selected to be executed alternatively, and this is not limited in this embodiment of the application.

Step 1307, based on the sharing instance identifier, the interaction participating device invokes the target interaction resource at the target interaction device through the target application, and the target interaction device is configured to perform permission verification on the sharing instance identifier and provide the target interaction resource when the sharing instance identifier passes the permission verification.

The method comprises the steps that an interaction participation device determines a target application and a target interaction device based on a target application identifier and a sharing party identifier in resource interaction data, and sends a resource calling request to the target interaction device, namely a resource interaction initiating device, wherein the resource calling request comprises a sharing instance identifier, the resource interaction initiating device carries out authority verification on the sharing instance identifier, and after the sharing instance identifier passes the authority verification of the resource interaction initiating device, a target interaction resource is provided for the interaction participation device, namely the interaction participation device can call the resource of the resource interaction initiating device through the target application.

For example, as shown in fig. 14, a schematic diagram of a device-level resource sharing principle is shown, and a target application is taken as an album application, a sharing party is taken as a resource interaction initiating device mobile phone a, and a shared party is taken as an interaction participating device mobile phone B for example.

The mobile phone a generates resource interaction data through the first application manager 1401, where the resource interaction data includes a target application identifier, a device identifier, and a sharing instance identifier. The mobile phone B obtains the resource interaction data, determines that the target application is the album application 1404 through the second application manager 1402 based on the target application identifier, and starts the album application 1404. Meanwhile, based on the device identifier, the device group range of the application device group management submodule in the device selector 1405 is set to the mobile phone a by the second application manager 1402, and is determined to be a candidate device. The device selection policy based on the user's selection at the device selection interface of the photo album application 1404 is to select all devices, thus determining the candidate device handset a as the target interactive device. Further, the device selector 1405 obtains the target resource gateway address of the target interaction device handset a from the resource gateway management 1406, and feeds back the target resource gateway address to the album application 1404. Further, a resource calling request is sent to the target interaction device mobile phone A, the resource calling request comprises a sharing instance identifier, and after the target interaction device mobile phone A verifies the authority of the sharing instance identifier, photo resources corresponding to the photo album application are provided for the mobile phone B. The mobile phone B traverses the resource gateway 1403 in the target resource gateway address through the album application 1404, and calls the photo resource corresponding to the album application 1404.

Illustratively, as shown in FIG. 15, a schematic diagram of user-level shared resource interaction is shown. The target application is taken as an album application, the sharing party is taken as a user a, and the shared party is taken as a user B, wherein the user a includes a mobile phone a and a mobile phone B under an account, and the user B includes a mobile phone C under an account.

Any device under the user a account generates resource interaction data through an application manager thereof, for example, the mobile phone a under the user a account generates resource interaction data through the first application manager 1501, and the resource interaction data includes a target application identifier, a user identifier, and a sharing instance identifier. Any device under the account of the user B acquires the resource interaction identifier, for example, the mobile phone C under the account of the user B acquires the resource interaction data, determines that the target application is the album application 1505 through the second application manager 1502 based on the target application identifier, starts the album application 1505, and simultaneously queries a device list under the account of the user a through the second application manager 1502 and the user management module 1507 and the device management module 1508 on the server side based on the user identifier, where the device list includes the mobile phone a and the mobile phone B. Further, the mobile phone C sets the device group range of the application device group management submodule in the device selector 1506 as the device list through the second application manager 1502, and determines the devices in the device list, that is, the mobile phone a and the mobile phone B, as candidate devices. The device selection policy based on the user's device selection interface at the album application 1505 is to select all devices, thus determining candidate devices cell phone a and cell phone B as target interactive devices. Further, the target resource gateway addresses of the target interaction devices handset a and handset B are obtained from the resource gateway management 1509 through the device selector 1506, and the target resource gateway addresses are fed back to the album application 1505. Further, the mobile phone C sends a resource calling request to the target interaction device mobile phone A and the mobile phone B, the resource calling request comprises a sharing example identifier, and after the target interaction device mobile phone A and the mobile phone B verify the authority of the sharing example identifier, photo resources corresponding to the photo album application are provided for the mobile phone C. The cell phone C calls the photo resource corresponding to the album application 1505 by the album application 1505 traversing the

resource gateways

1503 and 1504 in the target resource gateway address.

In the embodiment of the application, based on the target application identifier, the sharing party identifier and the sharing instance identifier, the interaction participation device can call the resource corresponding to the target application at the resource interaction initiating device, so that resource sharing between the resource interaction initiating device and the interaction participation device is realized, and resource sharing modes are enriched.

In another possible implementation, the resource interaction triggering operation is a sharing operation, the resource interaction data includes a target application identifier and a sharing group identifier, the target application identifier is used to determine a target application, and the sharing group identifier is used to determine a sharing group. The resource sharing method is described as shown in fig. 16, which illustrates a resource interaction method provided by another exemplary embodiment of the present application, and the method is applied to a resource interaction initiating device, i.e., a sharing group owner. It should be noted that the resource interaction initiating device is one of the sharing group owners, and for convenience of description, the sharing group owner is taken as the resource interaction initiating device for example.

Step 1601, in response to the sharing operation on the target application, the resource interaction initiating device generates, by the application manager, resource interaction data including the target application identifier and the sharing group identifier.

In the embodiment of the application, based on the sharing operation of the user on the target application, the resource interaction initiating device generates resource interaction data through the application manager, wherein the resource interaction data comprises a target application identifier and a sharing group identifier.

The sharing refers to that a plurality of devices or users are associated together to form a sharing group, and the devices or users in the same sharing group can mutually call resources of other devices or users. The device or user that creates the shared group is referred to as the shared group owner. Only after the shared group owner creates the shared group can other devices or users join the shared group. The sharing operation refers to an operation of creating a sharing group, the sharing group identifier is used for representing the created sharing group, and other devices or users can join the sharing group through the sharing group identifier. In addition, it should be noted that the sharing group id has uniqueness, and different sharing groups have different sharing group ids. In the embodiment of the present application, the resource interaction initiating device is a shared group owner.

For example, as shown in fig. 17, a collaborative drawing board application is taken as a target application, an application manager is a super application, and a resource interaction initiating device is taken as a sharing group owner for explanation.

A user 1708 clicks a collaborative sketchpad application 1704 on an application list interface 1701 of a super application, a resource interaction initiating device receives a triggering operation of the user on the collaborative sketchpad application 1704 and enters an application detail interface 1702, the application detail interface 1702 comprises a sharing key 1705 and a sharing key 1706, the user 1708 clicks the sharing key 1706, the resource interaction initiating device receives a triggering operation of the user 1708 on the sharing key 1706, resource interaction data is generated through the super application, the resource interaction data comprises a target application identifier and a sharing group identifier, a sharing group creating interface 1703 is displayed at the same time, and at this time, the resource interaction initiating device is a sharing group owner 1707.

Step 1602, in response to the device-level sharing operation on the target application, the resource interaction initiating device sends a first shared group creation request to the server, where the first shared group creation request includes a device identifier, and the server is configured to create a shared group formed by devices based on the first shared group creation request.

In the embodiment of the application, a server is deployed with shared group management, and the shared group management is used for managing creation of a shared group and joining and quitting of members of the shared group. Therefore, when the resource interaction initiating device receives the sharing operation of the target application device level by the user, a sharing group creation request is sent to the sharing group management device, the sharing group creation request comprises the device identification of the resource interaction initiating device, the sharing group management device creates a sharing group based on the creation request, and the resource interaction initiating device is the sharing group owner.

In the embodiment of the present application, device-level sharing means that all members of a sharing group are devices. Optionally, the device may belong to the same user account, or may belong to different user accounts, which is not limited in this embodiment of the present application.

Step 1603, in response to the user-level sharing operation on the target application, the resource interaction initiating device sends a second sharing group creation request to the server, the second sharing group creation request includes a user identifier, and the server is configured to create a sharing group formed by users based on the second sharing group creation request.

In the embodiment of the application, when the resource interaction initiating device receives a user-level sharing operation of a user on a target application, a sharing group creation request is sent to a sharing group manager, the sharing group creation request includes a user identifier corresponding to a user account to which the resource interaction initiating device belongs, the sharing group manager creates a sharing group based on the creation request, and the user to which the resource interaction initiating device belongs is a sharing group owner. All devices under the user account are included in the shared group.

In this embodiment, the user-level sharing means that the members of the sharing group include all devices under different user accounts.

Step 1604, in response to the resource invoking request of the interaction participating device, the resource interaction initiating device provides the target interaction resource to the interaction participating device through the resource gateway, and the resource gateway is used for managing invoking of the resource in the device.

After the interactive participation device determines the target application and joins the sharing group based on the target application identification and the sharing group identification in the resource interaction data, a resource calling request is sent to the target interaction device in the sharing group, the resource calling request is used for calling the target interaction resource at the target interaction device, and the target interaction device in the sharing group, namely the resource interaction initiating device, provides the target interaction resource to the interactive participation device through the resource gateway after receiving the resource calling request.

Step 1605, the resource interaction initiating device calls the target interaction resource at the interaction participating device through the target application.

In this embodiment of the present application, since the devices in the shared group may call the resources of all the devices mutually, the resource interaction initiating device may also call the target interaction resource at the interaction participating device through the target application.

A resource sharing method is described below, as shown in fig. 18, which illustrates a resource interaction method provided in another exemplary embodiment of the present application, and the method is applied to an interaction participant device, it should be noted that the interaction participant device is one of sharing members, and for convenience of description, the sharing member is taken as an interaction participant device for example.

Step 1801, the interaction participating device obtains resource interaction data, where the resource interaction data is generated by the resource interaction initiating device in receiving the sharing operation of the target application, and the resource interaction data includes a target application identifier and a sharing group identifier.

The interactive participation equipment acquires resource interactive data from the resource interactive initiating equipment, wherein the resource interactive data comprises a target application identifier and a sharing group identifier. The shared group identification is used to characterize a shared group to which the interactive participation device is to join.

Step 1802, based on the resource interaction data, the interaction participation device determines a target application through an application manager, and starts the target application, where the application manager is used to manage resource interaction of different applications.

Step 1803, the interactive participation device joins the sharing group represented by the sharing group identifier through the application manager.

In the embodiment of the application, based on the sharing group identifier in the resource interaction data, the interaction participation device joins the sharing group corresponding to the sharing group identifier through the application manager. It should be noted that the interactive participation device joins the sharing group in the role of sharing member, which is functionally different from the role of sharing group owner. First, the sharing group owner needs to get the agreement of the sharing group owner, second, the sharing group owner has the authority to move the sharing member out of the sharing group, and the sharing member only has the authority to actively exit the sharing group, and third, the sharing group owner has the authority to dissolve the sharing group, and the sharing member does not have the authority.

In a possible embodiment, the interactive participation device as a sharing member can only join one sharing group, for example, after the interactive participation device joins the first sharing group represented by the first sharing group identifier through the application manager, when the interactive participation device joins the second sharing group represented by the second sharing group identifier through the application manager again, the interactive participation device needs to exit the first sharing group, otherwise, the interactive participation device cannot join the second sharing group.

Illustratively, as shown in fig. 19, the collaborative palette application is targeted for application, and the super application is illustrated as an application manager. The resource interaction initiating device 1901 creates a shared group 1902 as a shared group owner, generates resource interaction data, and transmits the resource interaction data to the interaction participating device 1903 through an NFC signal. The interaction participation device 1903 acquires the resource interaction data through an NFC signal, joins the sharing group 1902 as a sharing member through a sharing group identifier in the resource interaction data, but the interaction participation device 1903 has already joined a sharing group before, because the collaborative drawing board application interface pops up a sharing group selection interface 1904, the sharing group selection interface 1904 includes a join sharing group button 1905 and a give up join sharing group button 1906, the user clicks the join sharing group button 1905, and the interaction participation device 1903 receives a trigger operation of the user on the join sharing group button 1905, and then automatically withdraws the joined sharing group, and joins the sharing group 1902 as a sharing member 1903.

In another possible implementation manner, the interaction participation device as a sharing member may join a plurality of sharing groups at the same time, and the resource interaction between the sharing group and the sharing group does not interfere with each other. For example, after the interaction participation device joins the first sharing group represented by the first sharing group representation through the application manager, the interaction participation device may also join the second sharing group represented by the second sharing group representation through the application manager, and resource interaction between the first sharing group and the second sharing group is not interfered with each other.

In the embodiment of the present application, the members in the sharing group may be devices or users, and the method for determining the target interactive device in the two cases is different, and is described below.

In step 1804, in case that the sharing group includes the device identifier, the interaction participating device determines, through the application manager, the device characterized by the device identifier as a candidate interaction device.

In a possible implementation manner, the members of the shared group are devices, different devices correspond to different device identifiers, an application manager in the interaction participating device configures a device group range managed by an application device group management submodule in the device selector according to the device identifiers in the shared group, the device group range includes all devices in the shared group, and the devices in the device group range are determined as candidate devices.

Step 1805, when the shared group includes the user identifier, the interaction participating device obtains at least one device identifier corresponding to the user identifier through the application manager, and determines the device characterized by the device identifier as a candidate interaction device.

In a possible implementation manner, the members of the sharing group are users, the user identifiers are used to represent user account information, the device identifiers are used to represent corresponding device information under user accounts, the number of devices under user accounts may be one or more, and different devices correspond to different device identifiers.

In the embodiment of the application, an application manager in the interactive participation device queries a device list under a user account corresponding to the user identifier from user management and device management of the server through the user identifier. Further, the application manager configures a device group range managed by the application device group management submodule in the device selector, where the device group range is a device list under all user accounts in the shared group, the device list includes all devices under all user accounts in the shared group, and all devices in the device list are determined as candidate interactive devices.

Step 1806, the interactive participation device obtains a device selection policy of the target application; and determining the candidate interaction equipment which accords with the equipment selection strategy as target interaction equipment through an equipment selector.

Step 1806 refers to step 1305, which is not described in detail in this embodiment of the present application.

Step 1807, the interactive participation device displays a device selection list based on the candidate interactive devices; and determining the selected candidate interaction device in the device selection list as the target interaction device through the device selector.

Step 1807 refers to step 1306, which is not described herein again.

Step 1808, the interactive participation device provides the target interactive resource to the target interactive device.

Step 1809, the interactive participation device invokes the target interactive resource at the target interactive device through the target application.

In steps 1808 to 1809, since all the devices in the shared group may invoke resources of all the devices, the interaction participating device may provide a target interaction resource to the target interaction device, and meanwhile, the interaction participating device may invoke the target interaction resource at the target interaction device through the target application.

For example, as shown in fig. 20, a collaborative drawing board application is taken as an example of a target application, an application manager is taken as a super application, a resource interaction initiating device is taken as a sharing group owner, and an interaction participating device is taken as a sharing group member, so as to describe shared resource interaction.

The user 2007 clicks a start key 2009 on an application detail page 2003 of the collaborative sketchpad application of the resource interaction initiating device 2001, the resource interaction initiating device 2001 receives a trigger operation of the user 2007 on the start key 2009, and an operation interface 2004 of the collaborative sketchpad application is displayed. The user 2008 clicks the start key 2010 on the application detail page 2005 of the collaborative palette application of the interactive participation device 2002, and the interactive participation device 2002 receives a trigger operation of the user 2008 on the start key 2010 and displays an operation interface 2006 of the collaborative palette application. Since the resource interaction initiating device 2001 and the interaction participating device 2002 are both in a shared group, the resource interaction initiating device 2001 and the interaction participating device 2002 can call a drawing data synchronization service of each other, that is, the content of the collaborative drawing application of the resource interaction initiating device 2001 and the interaction participating device 2002 can be synchronized with each other in real time, for example, the content of the collaborative drawing application of the interaction initiating device 2002 can be displayed on an operation interface 2004 of the collaborative drawing application of the resource interaction initiating device 2001, and the content of the collaborative drawing application of the resource interaction initiating device 2001 can also be displayed on an operation interface 2006 of the collaborative drawing application of the interaction participating device 2002.

For example, as shown in fig. 21, a schematic diagram of resource interaction of device-level sharing is shown, and a sharing group formed by taking a target application as an album application, taking a mobile phone a as a sharing group owner, and taking a mobile phone B and a mobile phone C as sharing members is described as an example. Since the mobile phone a, the mobile phone B, and the mobile phone C are all in a shared group, the mobile phone a, the mobile phone B, and the mobile phone C can all call the resources of the other party, and the following description will only take the example that the mobile phone B calls the resources of the mobile phone a and the mobile phone C as an example.

The mobile phone a sends a sharing group creation request to a sharing group manager 2108 of the server through the first application manager 2101, creates a sharing group, where the sharing group of the sharing group is the mobile phone a, and generates resource interaction data including a target application identifier and a sharing group identifier through the first application manager 2101. The mobile phone B and the mobile phone C acquire resource interaction data, determine that the target application is an album application 2106 based on the target application identifier, join the sharing group based on the sharing group identifier, and acquire a device list under the sharing group from a sharing group management 2108, wherein the device list in the sharing group management 2108 comprises the mobile phone A, the mobile phone B and the mobile phone C. Taking the example that the mobile phone B calls the resources of the members in the shared group, the mobile phone B obtains the device list of the current shared group from the shared group management 2108 through the second application manager 2102, and sets the device group range of the application device group management submodule in the device selector 2103 as the device list of the shared group, and at this time, all devices on the device list of the shared group, that is, the mobile phone a, the mobile phone B, and the mobile phone C, are candidate devices. The device selection policy based on the user's device selection interface at the album application 2106 is to select all devices, thus determining candidate devices cell phone a, cell phone B, cell phone C as target interactive devices. Further, the device selector 2103 obtains the target resource gateway addresses of the target interaction devices, namely, the mobile phone a, the mobile phone B and the mobile phone C, from the resource gateway management 2109, and feeds the target resource gateway addresses back to the album application 2106. The mobile phone B traverses the

resource gateways

2105, 2107 and 2104 in the target resource gateway address through the photo album application 2106 and calls photo resources in the mobile phone A, the mobile phone B and the mobile phone C. In addition, the mobile phone B also provides photo resources corresponding to the photo album application for the mobile phone A and the mobile phone C. In addition, it should be noted that any mobile phone in the sharing group can see the photos in all the mobile phones, i.e., the mobile phone a, the mobile phone B, and the mobile phone C, when the photo album application is opened.

Illustratively, as shown in fig. 22, a schematic diagram of resource interaction of user-level sharing is shown, and the target application is taken as an album application, and the user a is taken as a sharing group owner, and the user B and the user C are taken as sharing members for illustration. The device under the account of the user A is a mobile phone A and a mobile phone B, the device under the account of the user B is a mobile phone C, the device under the account of the user D is a mobile phone D and a mobile phone E, and each mobile phone corresponds to different device identifications. In the following description, it is exemplified that any one of the mobile phones under the accounts of the user a, the user B, and the user C in the shared group can call resources of the mobile phone under the account of another user.

The mobile phone a under the account of the user a sends a shared group creation request to the shared group management 2210 of the server side through the first application manager 2201 and creates a shared group, the shared group of the shared group is the user a, and resource interaction data including a target application identifier and a shared group identifier is generated through the first application manager 2201. User B and user C obtain resource interaction data, determine that the target application is an album application 2114 based on the target application identifier, identify that user B and user C join the sharing group based on the sharing group, and obtain a user list under the sharing group from the sharing group management 2210, where the user list in the sharing group management 2210 includes user a, user B, and user C, which respectively correspond to different user identifiers. Further, the sharing group members, that is, user a, user B, and user C, traverse the user identifiers in the user list through their respective application managers, and query all devices through the user management 2211 and the device management 2212 on the server side, so as to generate a complete device list, where the list includes mobile phone a, mobile phone B, mobile phone C, mobile phone D, and mobile phone E. The mobile phone C under the account of the user B acquires the device list through the second application manager 2202, and determines the device group range device of the application device group management submodule in the device selector 2203 as the device list, and determines all the devices, namely, the mobile phone a, the mobile phone B, the mobile phone C, the mobile phone D, and the mobile phone E, on the device list as candidate devices. The device selection policy based on the user's device selection interface at the album application 2206 is to select all devices, thus determining candidate devices cell phone a, cell phone B, cell phone C, cell phone D, and cell phone E as target interactive devices. Further, the device selector 2203 obtains the target resource gateway addresses of the target interaction devices, namely, the mobile phone a, the mobile phone B, the mobile phone C, the mobile phone D, and the mobile phone E, from the resource gateway management 2213, and feeds back the target resource gateway addresses to the album application 2206. The mobile phone C traverses the

resource gateways

2204, 2205, 2209, 2207 and 2208 in the target resource gateway address through the album application 2206, and calls the photo resources in the mobile phone a, the mobile phone B, the mobile phone C, the mobile phone D and the mobile phone E. In addition, the mobile phone C also provides photo resources corresponding to the photo album application to the mobile phone A, the mobile phone B, the mobile phone D and the mobile phone E. It should be noted that when any one of the mobile phones under the accounts of the sharing group member user a, the user B, and the user C opens the album application, all the mobile phones, that is, the photos of the mobile phone a, the mobile phone B, the mobile phone C, the mobile phone D, and the mobile phone E, can be viewed.

In the embodiment of the application, the resource interaction initiating device creates a sharing group, and the interaction participating device joins the sharing group based on the sharing group identifier.

In addition, in the embodiment of the present application, the sharing group owner may dissemble the sharing group. And the resource interaction initiating device responds to the sharing group dismissal operation and sends a sharing group dismissal instruction to the server so that the server dismisses the sharing group and deletes the sharing group identification based on the sharing group dismissal instruction. The interactive participation device exits the shared group through the application manager in response to the shared group dismissal message.

In the embodiment of the application, based on the shared group dismissal operation of the user, the resource interaction initiating device sends a shared group dismissal instruction to the shared group management of the server side, and the shared group management dismisses the shared group after receiving the shared dismissal instruction and deletes the shared group identifier. The interactive participation equipment acquires the sharing group dismissal message through sharing group management and exits the sharing group through the application manager.

For example, as shown in fig. 23, taking a collaborative drawing board application as an example of a target application, a shared group owner is described to be resolved, where a resource interaction initiating device is a shared group owner, and an interaction participating device is a shared member.

A user 2310 clicks a dismissal shared group button 2305 on a collaborative drawing board application shared group interface 2301, a resource interaction initiating device 2303 receives a triggering operation of the user 2310 on the dismissal shared group button 2305, a dialog box 2306 pops up on the collaborative drawing board application shared group interface 2301, the user 2310 clicks a determination button 2307, the resource interaction initiating device 2303 sends a shared group dismissal instruction to a shared group management, the shared group management dismisses the shared group after receiving the dismissal instruction, deletes the shared group identifier, and the collaborative drawing board application returns to an application detail interface 2302. The interactive participation device 2304 receives the dismissal instruction and exits the shared group through the application manager. At this time, the resource interaction initiating device 2303 and the interaction participating device 2304 are not in the same sharing group, and they cannot mutually invoke the drawing data synchronization service of the other party, and when they start the collaborative palette application, they can only see the content of their own collaborative palette application on their respective application operation interfaces 2308, 2309.

In the embodiment of the present application, the sharing group owner may also remove the sharing group member. The resource interaction initiating device responds to the removing operation, and sends a removing instruction to the server, so that the server updates the sharing group based on the removing instruction, and synchronizes the updating result to the sharing party in the sharing group, wherein the removing instruction comprises the interaction participation device to be removed. The interactive participation device exits the shared group through the application manager in response to a removal message indicating that the shared group is removed.

In this embodiment of the application, based on the removal operation of the user, the resource interaction initiation device sends a removal instruction to the shared group manager at the server side, where the removal instruction includes a device to be removed or the user, for example, the device to be removed is an interaction participation device, that is, the removal instruction includes the interaction participation device to be removed. And after receiving the removal instruction, the shared group management removes the device to be removed from the device or user list of the shared management group, simultaneously updates the device list or the user list, and synchronizes the updated result to all members of the shared group. And the interactive participation equipment acquires the removal message through the shared group management and exits the shared group through the application processor.

For example, as shown in fig. 24, taking a collaborative drawing board application as an example of a target application, a shared group owner removal sharing member is described, where a resource interaction initiating device is the shared group owner, and an interaction participating device is a to-be-removed shared member.

A user 2409 clicks a user kick-out button 2408 on a collaborative palette application shared group interface 2403, a resource interaction initiating device 2401 receives a trigger operation of the user 2409 on the user kick-out button 2408, a dialog box 2404 pops up on the collaborative palette application shared group interface 2403, the user 2409 clicks a determination button 2405, the resource interaction initiating device 2401 sends a removal instruction to a shared group manager, the removal instruction includes a device to be removed, namely an interaction participating device, the interaction participating device is removed from a device list after the sharing group manager receives the removal instruction, and the updated device list is synchronized to other members of the shared group. And at the same time, update the members of the shared group in coordination with the palette application shared group interface 2403. The interactive participation device 2402 receives the removal message and exits the sharing group through the application manager. At this time, the resource interaction initiating device 2401 and the interaction participating device 2402 are not in the same sharing group, and they cannot mutually invoke the drawing data synchronization service of the other party, and when they start the collaborative palette application, they can only see the content of their own collaborative palette application in their respective application operation interfaces 2406, 2407.

In the embodiment of the present application, the sharing member may also actively exit the sharing group. The interactive participation device responds to the quitting operation, quits the sharing group through the application manager, and sends out quitting information to the server, and the server is used for updating the sharing group based on the quitting information and synchronizing the updating result to the target interactive device. The resource interaction initiating device receives an exit message sent by the server, and the exit message is triggered by the interaction participating device which actively exits the sharing group.

In the embodiment of the application, based on the quitting operation of the user, the interactive participation device quits the sharing group through the application manager and sends a quitting message to the sharing group management of the server side, and after receiving the quitting message, the sharing group management deletes the interactive participation device from the device list managed by the sharing group, updates the device list and synchronizes the updated result to all members of the sharing group. And the resource interaction initiating device receives an exit message sent by the interaction participating device through the shared group management.

For example, as shown in fig. 25, taking a collaborative drawing board application as an example of a target application, a description is given to a sharing member exiting a sharing group, where a resource interaction initiating device is a sharing group owner, and an interaction participating device is a sharing member exiting the sharing group.

A user 2510 clicks a key 2509 for exiting the shared group on the collaborative palette application shared group interface 2503, an interactive participation device 2502 receives a trigger operation of the user 2510 on the key 2509 for exiting the shared group, a dialog box 2504 pops up on the collaborative palette application shared group interface 2503, the user 2510 clicks a determination key 2505, the interactive participation device 2502 exits the shared group through an application manager and sends an exit message to the shared group management, the shared group management removes the interactive participation device from a device list after receiving the exit message and synchronizes the updated device list to other members of the shared group. While the collaborative palette application of interactive participant device 2502 returns to application detail interface 2506. The resource interaction initiating device 2501 receives the exit message issued by the interaction participating device 2502 through the shared group management. At this time, the interaction participating device 2502 and the resource interaction initiating device 2501 are not in the same sharing group, and they cannot call the drawing data synchronization service of each other, and when they start the collaborative palette application, they can only see the content of their own collaborative palette application on their respective application operation interfaces 2508, 2507.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Referring to fig. 26, a block diagram of a resource interaction apparatus according to an exemplary embodiment of the present application is shown, where the apparatus includes:

an obtaining module 2601, configured to obtain resource interaction data, where the resource interaction data is generated by a resource interaction initiating device when receiving a resource interaction triggering operation on a target application, and the resource interaction triggering operation includes at least one of a sharing operation and a sharing operation;

a determining module 2602, configured to determine, based on the resource interaction data, the target application and a target interaction device, where the target application is an application for performing resource interaction, and the target interaction device is at least one device for performing resource interaction;

an invoking module 2603, configured to invoke, by the target application, a target interaction resource at the target interaction device.

Optionally, the determining module 2602 includes:

a first determining unit, configured to determine the target application through an application manager based on the resource interaction data, and start the target application, where the application manager is configured to manage resource interaction of different applications;

a second determining unit, configured to determine, based on the resource interaction data, the target interaction device through the application manager and the device selector.

Optionally, the second determining unit is configured to:

and determining the target interaction device through the application manager and the device selector based on the sharer identification.

Optionally, the second determining unit is further configured to:

under the condition that the sharing party identifier is the equipment identifier, determining the equipment represented by the equipment identifier as candidate interaction equipment through the application manager; or the like, or, alternatively,

under the condition that the sharing party identifier is a user identifier, acquiring at least one device identifier corresponding to the user identifier through the application manager, and determining a device represented by the device identifier as a candidate interactive device;

determining, by the device selector, the target interaction device from the candidate interaction devices.

Optionally, the second determining unit is further configured to:

acquiring a device selection strategy of the target application; determining, by the device selector, the candidate interaction device that meets the device selection policy as the target interaction device; or the like, or, alternatively,

displaying a device selection list based on the candidate interaction devices; determining, by the device selector, the selected candidate interactive device in the device selection list as the target interactive device.

Optionally, the invoking module 2603 is configured to:

and acquiring the target interaction resource from the target interaction equipment through the target application based on the sharing instance identifier, wherein the target interaction equipment is used for performing authority verification on the sharing instance identifier and providing the target interaction resource when the sharing instance identifier passes the authority verification.

Optionally, the second determining unit is further configured to:

determining, by the application manager and the device selector, the target interaction device based on the shared group identification;

optionally, the apparatus further comprises:

and the providing module is used for providing the target interaction resource for the target interaction equipment.

Optionally, the second determining unit is further configured to:

joining, by the application manager, the shared group characterized by the shared group identification;

determining, by the application manager, candidate interaction devices in the shared group;

Optionally, the second determining unit is further configured to:

determining, by the application manager, a device characterized by a device identifier as the candidate interactive device if the shared group includes the device identifier;

and under the condition that the sharing group contains the user identification, acquiring at least one device identification corresponding to the user identification through the application manager, and determining the device characterized by the device identification as the candidate interactive device.

Optionally, the second determining unit is further configured to:

Optionally, the apparatus further comprises:

a first quitting module, configured to, in response to a quitting operation, quit the shared group through the application manager, and send a quitting message to a server, where the server is configured to update the shared group based on the quitting message, and synchronize an update result to the target interaction device;

a second exit module for exiting the shared group through the application manager in response to a shared group dismissal message;

a third exit module to exit the shared group through the application manager in response to a removal message indicating that the shared group is removed.

Optionally, invoking module 2603 for:

acquiring a target resource gateway address of the target interaction device based on the device identifier of the target interaction device, wherein the target resource gateway address is a gateway address of a resource gateway in the target interaction device, and the resource gateway is used for calling resources in management equipment;

and accessing the target resource gateway through the target application to acquire the target interactive resource based on the target resource gateway address.

Optionally, the obtaining module 2601 is configured to:

analyzing the graphic code to obtain the resource interaction data; or the like, or, alternatively,

analyzing the resource interaction data from the interaction link; or the like, or, alternatively,

and receiving the resource interaction data in a near field communication mode.

Optionally, the target interaction resource includes at least one of a file resource, a hardware resource, and a service resource.

Referring to fig. 27, a block diagram of a resource interaction apparatus according to an exemplary embodiment of the present application is shown, where the apparatus includes:

a first generating module 2701, configured to generate resource interaction data in response to a resource interaction triggering operation on a target application;

a providing module 2702, configured to provide a target interactive resource to an interactive and participating device in response to a resource invocation request of the interactive and participating device, where the resource invocation request is sent by the interactive and participating device through a target application after the target application and the target interactive device are determined based on the resource interaction data by the interactive and participating device.

Optionally, the generating module 2701 includes:

the generation unit is used for responding to resource interaction triggering operation of the target application and generating the resource interaction data through an application manager, and the application manager is used for managing resource interaction of different applications;

optionally, the providing module 2702 includes:

a providing unit, configured to provide the target interaction resource to the interaction device through a resource gateway in response to the resource invocation request of the interaction device, where the resource gateway is used to manage invocation of resources in a device.

Optionally, the generating unit is configured to:

and responding to the sharing operation of the target application, and generating the resource interaction data containing the target application identification and the sharer identification through the application manager.

Optionally, the generating unit is further configured to:

generating, by the application manager, the resource interaction data including the target application identification and a device identification in response to a device-level sharing operation for the target application;

and responding to the user-level sharing operation of the target application, and generating the resource interaction data containing the target application identification and a user identification through the application manager, wherein the user identification is used for representing a user corresponding to a sharing party.

Optionally, the providing unit is configured to:

responding to the resource calling request of the interactive participation equipment, and performing authority verification on the sharing instance identifier contained in the resource calling request;

and responding to the sharing instance identification passing the permission verification, and providing the target interaction resource for the interaction participation equipment.

Optionally, the apparatus further comprises:

a deletion module to:

and in response to the sharing cancellation operation of the target application, deleting the sharing instance identifier.

Optionally, the generating unit is further configured to:

generating, by the application manager, the resource interaction data including a target application identifier and a sharing group identifier in response to a sharing operation for the target application;

optionally, the apparatus further comprises:

a calling module, configured to call the target interaction resource at the interaction participation device through the target application.

Optionally, the apparatus further comprises:

a first sending module configured to:

responding to a device-level sharing operation of the target application, and sending a first sharing group creation request to a server, wherein the first sharing group creation request contains a device identifier, and the server is used for creating a sharing group formed by devices based on the first sharing group creation request;

a second sending module, configured to:

and responding to the user-level sharing operation of the target application, and sending a second sharing group creation request to a server, wherein the second sharing group creation request comprises a user identifier, and the server is used for creating a sharing group formed by users based on the second sharing group creation request.

Optionally, the apparatus further comprises:

a third sending module, configured to:

and responding to the sharing group disassembling operation, sending a sharing group disassembling instruction to the server so that the server can disassemble the sharing group based on the sharing group disassembling instruction, and deleting the sharing group identification.

Optionally, the apparatus further comprises:

a fourth sending module, configured to:

responding to the removing operation, sending a removing instruction to a server so that the server updates the sharing group based on the removing instruction, and synchronizing the updating result to the sharing party in the sharing group, wherein the removing instruction comprises the interactive participation equipment to be removed.

Optionally, the apparatus further comprises:

a receiving module to:

and receiving an exit message sent by the server, wherein the exit message is triggered by the interactive participation device which actively exits the sharing group.

Optionally, the apparatus further comprises:

an update module to:

responding to the gateway address update of the resource gateway, and sending a gateway address update message to a server so that the server synchronizes the updated gateway address to a device selector of other equipment, wherein the device selector stores a mapping relation between an equipment identifier and a gateway address.

Optionally, the apparatus further comprises:

a second generation module to:

generating a graphic code based on the resource interaction data; or the like, or, alternatively,

generating an interaction link based on the resource interaction data; or the like, or, alternatively,

and sending the resource interaction data in a near field communication mode.

It should be noted that: the device provided in the above embodiment is only illustrated by dividing the functional modules, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.

Referring to fig. 28, a block diagram of a terminal 2800 according to an example embodiment of the present application is shown. Terminal 2800 in the present application may include one or more of the following components: a processor 2810 and a memory 2820, wherein the processor 2810 is electrically connected to the memory 2820.

The processor 2810 may include one or more processing cores. A processor 2810 interfaces with various interfaces and connections throughout the terminal 2800 to perform various functions and process data for the terminal 2800 by executing or performing instructions, programs, code sets, or instruction sets stored in memory 2820, and calling data stored in memory 2820. Alternatively, the processor 2810 may be implemented in hardware using at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 2810 may integrate one or a combination of a CPU, a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing contents required to be displayed by the touch display screen; the modem is used to handle wireless communications. It is to be appreciated that the modem can be implemented as a separate communication chip, rather than being integrated into the processor 2810.

The Memory 2820 may include a Random Access Memory (RAM) or a Read-Only Memory (ROM). Optionally, the memory 2820 includes a non-transitory computer-readable medium. The memory 2820 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 2820 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playing function, an image playing function, and the like), instructions for implementing the above method embodiments, and the like, and the operating system may be an Android (Android) system (including a system based on Android system depth development), an IOS system developed by apple inc (including a system based on IOS system depth development), or other systems. The storage data area may also store data created by terminal 2800 in use (e.g., phone books, audio-visual data, chat log data), and the like.

In this embodiment, the memory 2820 stores at least one instruction, and the at least one instruction is used for the processor 2810 to execute the resource interaction method as shown in the above embodiment.

In an embodiment of the present application, the terminal 2800 may further include an NFC component configured to receive and transmit an NFC signal, such that the terminal 2800 may process the NFC signal through the processor 2810.

Optionally, the terminal 2800 further includes a camera, configured to scan the graphic code, so that the processor obtains the resource interaction data from the graphic code through parsing.

Optionally, terminal 2800 can also include a touch display screen, which can be a capacitive touch display screen for receiving touch operations by a user on or near the touch display screen using a finger, a stylus, or any other suitable object, as well as displaying user interfaces of various applications. A touch display screen is generally provided on the front panel of the terminal 2800. The touch display screen may be designed as a full-face screen, a curved screen, or a profiled screen. The touch display screen can also be designed to be a combination of a full-face screen and a curved-face screen, and a combination of a special-shaped screen and a curved-face screen, which is not limited in the embodiment of the present application.

In addition, those skilled in the art will appreciate that the architecture of terminal 2800 as illustrated in the above-described figures is not meant to be limiting with respect to terminal 2800, and that a terminal may include more or less components than those shown, or some components may be combined, or a different arrangement of components. For example, the terminal 2800 may further include a radio frequency circuit, a camera module, a sensor (not including a temperature sensor), an audio circuit, a Wireless Fidelity (WiFi) module, a power source, and a bluetooth module, which are not described herein again.

The embodiment of the present application also provides a computer-readable storage medium, which stores at least one program code, and the program code is loaded and executed by a processor to implement the resource interaction method as described in the above embodiments.

According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the resource interaction method provided in the various alternative implementations of the above aspects.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method for resource interaction, the method comprising:

2. The method of claim 1, wherein determining the target application and target interaction device based on the resource interaction data comprises:

determining the target application through an application manager based on the resource interaction data, and starting the target application, wherein the application manager is used for managing resource interaction of different applications;

and determining the target interaction device through the application manager and the device selector based on the resource interaction data.

3. The method according to claim 2, wherein when the resource interaction triggering operation is a sharing operation, the resource interaction data includes a target application identifier and a sharing party identifier;

the determining the target interaction device through the application manager and the device selector based on the resource interaction data includes:

4. The method of claim 3, wherein the determining, by the application manager and the device selector, the target interaction device based on the sharer identification comprises:

5. The method of claim 4, wherein the determining, by the device selector, the target interaction device from the candidate interaction devices comprises:

6. The method of claim 3, wherein the resource interaction data further comprises a sharing instance identifier;

the invoking, by the target application, a target interaction resource at the target interaction device includes:

based on the sharing instance identifier, the target interaction resource at the target interaction device is called through the target application, and the target interaction device is used for performing authority verification on the sharing instance identifier and providing the target interaction resource when the sharing instance identifier passes the authority verification.

7. The method according to claim 2, wherein when the resource interaction triggering operation is a sharing operation, the resource interaction data includes a target application identifier and a sharing group identifier;

the method further comprises the following steps:

and providing the target interaction resource to the target interaction equipment.

8. The method of claim 7, wherein the determining, by the application manager and the device selector, the target interaction device based on the shared group identity comprises:

9. The method of claim 8, wherein the determining, by the application manager, candidate interaction devices in the shared group comprises:

determining, by the application manager, a device characterized by a device identifier as the candidate interactive device if the shared group includes the device identifier; or the like, or, alternatively,

10. The method of claim 8, wherein the determining, by the device selector, the target interaction device from the candidate interaction devices comprises:

11. The method of claim 8, further comprising:

responding to an exit operation, exiting the shared group through the application manager, and sending an exit message to a server, wherein the server is used for updating the shared group based on the exit message and synchronizing an updating result to the target interaction equipment;

exiting, by the application manager, the shared group in response to a shared group dismissal message;

exiting, by the application manager, the shared group in response to a removal message indicating that the shared group was removed.

12. The method according to any one of claims 1 to 11, wherein said invoking, by said target application, a target interaction resource at said target interaction device comprises:

13. The method according to any one of claims 1 to 11, wherein the obtaining resource interaction data comprises:

and receiving the resource interaction data in a near field communication mode.

14. The method of any one of claims 1 to 11, wherein the target interaction resource comprises at least one of a file resource, a hardware resource, and a service resource.

15. A method for resource interaction, the method comprising:

16. The method of claim 15, wherein generating resource interaction data in response to a resource interaction triggering operation on a target application comprises:

responding to a resource interaction triggering operation of the target application, and generating the resource interaction data through an application manager, wherein the application manager is used for managing resource interaction of different applications;

the providing the target interactive resource to the interactive participation device in response to the resource calling request of the interactive participation device comprises:

and responding to the resource calling request of the interactive participation equipment, and providing the target interactive resource to the interactive participation equipment through a resource gateway, wherein the resource gateway is used for managing the calling of the resource in the equipment.

17. The method of claim 16, wherein generating, by an application manager, the resource interaction data in response to the resource interaction triggering operation on the target application comprises:

18. The method of claim 17, wherein generating, by the application manager, the resource interaction data including a target application identifier and a sharer identifier in response to the sharing operation for the target application comprises:

19. The method of claim 18, wherein the resource interaction data further comprises a sharing instance identifier;

20. The method of claim 19, further comprising:

21. The method of claim 16, wherein generating, by an application manager, the resource interaction data in response to the resource interaction triggering operation on the target application comprises:

the method further comprises the following steps:

invoking, by the target application, the target interaction resource at the interaction participation device.

22. The method of claim 21, further comprising:

23. The method of claim 21, further comprising:

24. The method of claim 21, further comprising:

25. The method of claim 21, further comprising:

26. The method of claim 16, further comprising:

27. The method according to any one of claims 15 to 26, wherein after generating the resource interaction data, the method comprises:

and sending the resource interaction data in a near field communication mode.

28. The method according to any of claims 15 to 26, wherein the target interaction resource comprises at least one of a file resource, a hardware resource and a service resource.

29. An apparatus for resource interaction, the apparatus comprising:

the resource interaction triggering operation comprises at least one of a sharing operation and a sharing operation;

30. An apparatus for resource interaction, the apparatus comprising:

31. A terminal, characterized in that the terminal comprises a processor and a memory, in which at least one instruction, at least one program, a set of codes, or a set of instructions is stored, which is loaded and executed by the processor to implement the resource interaction method according to any one of claims 1 to 14, or to implement the resource interaction method according to any one of claims 15 to 28.

32. A computer readable storage medium having stored therein at least one instruction, at least one program, a set of codes, or a set of instructions, which is loaded and executed by a processor to implement the resource interaction method of any of claims 1 to 14 or to implement the resource interaction method of any of claims 15 to 28.

33. A computer program product, characterized in that it comprises computer instructions which, when executed by a processor, implement the resource interaction method according to any one of claims 1 to 14, or implement the resource interaction method according to any one of claims 15 to 28.