WO2023093452A1

WO2023093452A1 - Resource interaction method and apparatus, and terminal and storage medium

Info

Publication number: WO2023093452A1
Application number: PCT/CN2022/128064
Authority: WO
Inventors: 杨俊拯
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-11-29
Filing date: 2022-10-27
Publication date: 2023-06-01
Also published as: CN114237840A

Abstract

A resource interaction method and apparatus, and a terminal and a storage medium, which belong to the technical field of communications. The method comprises: acquiring resource interaction data, wherein the resource interaction data is generated by a resource interaction initiating device when having received a resource interaction trigger operation for a target application (220); determining the target application and a target interaction device on the basis of the resource interaction data, wherein the target application is an application for performing resource interaction, and the target interaction device is at least one device for performing resource interaction (230); and calling, by means of the target application, a target interaction resource at the target interaction device (260). By means of the solution of the embodiments of the present application, distributed calling of resources can be realized, such that application functions of more types can be realized.

Description

Resource interaction method, device, terminal and storage medium

This application claims the priority of the Chinese patent application with the application number 202111436006.X and the title of the invention "resource interaction method, device, terminal and storage medium" filed on November 29, 2021, the entire contents of which are incorporated herein by reference Applying.

technical field

The embodiments of the present application relate to the field of communication technologies, and in particular to a resource interaction method, device, terminal, and storage medium.

Background technique

With the continuous development of application (Application, App) technology, more and more multi-functional applications emerge as the times require, bringing convenience to people's daily life.

In related technologies, before using the application, the user first needs to download the application installation package from the application store, and install the application in the terminal by parsing the application installation package, and then click the application icon to start the application. In addition, when the user shares the application with other devices, it means sharing the download path of the application installation package with other devices, or sending the data of the application installation package 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 before using it.

Contents of the invention

Embodiments of the present application provide a resource interaction method, device, terminal, and storage medium. Described technical scheme is as follows:

On the one hand, the embodiment of the present application provides a resource interaction method, the method includes:

Acquiring resource interaction data, the resource interaction data is generated by the resource interaction initiating device when receiving a resource interaction trigger operation for the target application, the resource interaction trigger operation includes at least one of a sharing operation and a sharing operation;

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

A target interaction resource at the target interaction device is invoked by the target application.

On the other hand, an embodiment of the present application provides a resource interaction method, the method including:

generating resource interaction data in response to a resource interaction trigger operation on the target application;

In response to the resource invocation request of the interaction participating device, provide the target interaction resource to the interaction participating device. After the resource invoking request is determined by the interaction participating device based on the resource interaction data to determine the target application and the target interaction device, through the sent by the target application.

On the other hand, an embodiment of the present application provides a resource interaction device, the device includes:

An acquisition module, configured to acquire resource interaction data, which is generated by the resource interaction initiating device when receiving a resource interaction trigger operation on the target application;

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

A calling module, configured to use the target application to call the target interaction resource on the target interaction device.

A first generation module, configured to generate resource interaction data in response to a resource interaction trigger operation on the target application;

A providing module, configured to provide a target interaction resource to the interaction participation device in response to a resource invocation request of the interaction participation device, and the resource invocation request is determined by the interaction participation device based on the resource interaction data to determine a target application and a target interaction device, sent through the target application.

On the other hand, an embodiment of the present application provides a terminal, the terminal includes a processor and a memory, at least one program is stored in the memory, and the at least one program is loaded and executed by the processor to implement the above-mentioned The resource interaction method described in the aspect.

On the other hand, an embodiment of the present application provides a computer-readable storage medium, at least one program is stored in the readable storage medium, and the at least one program is loaded and executed by a processor to implement the above-mentioned Resource interaction methods.

On the other hand, an embodiment of the present application provides a computer program product, the computer program product includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; the processor of the terminal reads the computer program from the computer-readable storage medium. Instructions, the processor executes the computer instructions, so that the terminal executes the resource interaction method provided in the above aspects.

Description of drawings

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

FIG. 2 shows a flowchart of a resource interaction method provided by an exemplary embodiment of the present application;

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

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

Fig. 5 shows a schematic diagram of an application manager interface provided by another exemplary embodiment of the present application;

Fig. 6 shows a schematic diagram of an application manager interface provided by another exemplary embodiment of the present application;

Fig. 7 shows a schematic diagram of an interface for sharing resources through graphic codes provided by an exemplary embodiment of the present application;

Fig. 8 shows a schematic diagram of an interface for sharing resources through interactive links provided by an exemplary embodiment of the present application;

Fig. 9 shows a schematic diagram of an interface for sharing resources through near-field communication provided by an exemplary embodiment of the present application;

Fig. 10 shows a schematic structural diagram of a device selector provided by an exemplary embodiment of the present application;

Fig. 11 shows a flowchart of a resource interaction method provided by another exemplary embodiment of the present application;

Fig. 12 shows a schematic diagram of an interface for canceling resource sharing provided by an exemplary embodiment of the present application;

Fig. 13 shows a flowchart of a resource interaction method provided by another exemplary embodiment of the present application;

Fig. 14 shows a schematic diagram of the principle of device-level resource sharing provided by an exemplary embodiment of the present application;

Fig. 15 shows a schematic diagram of the 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 exemplary embodiment of the present application;

Fig. 17 shows a schematic diagram of an interface for creating a sharing group provided by an exemplary embodiment of the present application;

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

Fig. 19 shows a schematic diagram of an interface for joining a sharing group provided by an exemplary embodiment of the present application;

Fig. 20 shows a schematic diagram of an interface of collaborative drawing board application resource sharing provided by an exemplary embodiment of the present application;

Fig. 21 shows a schematic diagram of the principle of device-level resource sharing provided by an exemplary embodiment of the present application;

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

Fig. 23 shows a schematic diagram of an interface for disbanding a sharing group provided by an exemplary embodiment of the present application;

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

Fig. 25 shows a schematic diagram of an interface for exiting a sharing group provided by an exemplary embodiment of the present application;

Fig. 26 shows a structural block diagram of a resource interaction device provided by an exemplary embodiment of the present application;

Fig. 27 shows a structural block diagram of a resource interaction device provided by another exemplary embodiment of the present application;

Fig. 28 shows a structural block diagram of a terminal provided by an exemplary embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the implementation manners of the present application will be further described in detail below in conjunction with the accompanying drawings.

The "plurality" mentioned herein means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently. The character "/" generally indicates that the contextual objects are an "or" relationship.

The nouns appearing in this article are explained below.

Micro-application: that is, the target application in the embodiment of this application. Micro-application can be regarded as a collection composed of services, and is used to implement specific business logic through calls between services. Unlike traditional applications that can only run on a specific operating system, the services of micro-apps can be services on different operating systems, that is, micro-apps support heterogeneous operating systems and can run across platforms. Unlike traditional applications that need to be downloaded before use and bound to devices, micro-apps adopt a subscription mechanism and are bound to users. This microapp can be used. Different from traditional applications that need to download and install the application installation package before running, for example, before running an Android application, you need to download the apk package. Before running a micro application, you only need to download the corresponding application script. The engine executes the application script to realize application functions. Compared with traditional applications, application scripts have a lower code volume, so they occupy less storage space and are conducive to dynamic deployment and updates.

Service: As the smallest unit in the running process of micro-applications, it is used to achieve specific tasks. For example, the screen capture service is used to realize the screen capture function of the device, and the screen projection service is used to realize the screen projection of the display screen between devices, and so on. Moreover, the service invoked during the running of the micro-application may be a service on the current device or a service on other devices. For example, during the running of the micro-app, you can obtain the device screenshots of other devices by calling the screenshot service on other devices, and display the device screenshots of other devices by calling the image display service. Different from the traditional application installation process, all the services used in the running process need to be pre-installed locally. Since the business logic of the micro-application is dynamically assembled during the running process, the services in the micro-application support dynamic deployment, that is, during the running process Based on the business logic executed by the current device, the service corresponding to the business logic is dynamically deployed to the current device. Correspondingly, when the application function of the same micro-application is implemented by multiple devices, since the business logic of different devices may be different, the services deployed on different devices may also be different, that is, the services in the micro-application have the characteristics of differential deployment. In a possible implementation, the services constituting the micro-application may include static services and dynamic services, where static services refer to services provided by the host application and need to be pre-installed in the device, while dynamic services refer to services that support dynamic deployment The service can be dynamically deployed in the device during the running of the micro application.

In addition, it should be noted that in the embodiment of the present application, the shared and shared objects are resources, and the aforementioned services are only one type of resources. Therefore, resources in this application include file resources, hardware resources and service resources. File resources are resources that exist in the form of files, such as pictures, videos, audios, word documents, and table files. Hardware resources refer to the hardware capabilities of the device, such as the camera's ability to take pictures and record images, and the computing power of the CPU (Central Processing Unit, central processing unit). Usually, such resources usually need to be encapsulated with a layer of software interface before they can be used. Service resources are the screen capture service, screen projection service, local search service, navigation service, etc. mentioned above.

The implementation environment of the embodiment of the present application is introduced below.

Please refer to FIG. 1 , which shows a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application. 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 are logged in with the first user account 110, the third terminal 121, and the fourth terminal 122 A second user account 120 is logged in, and the implementation environment further includes a server 130 .

In this embodiment of the application, the target application 140 is bound to the first user account 110 and the second user account 120 respectively, that is, any terminal under the first user account 110 or the second user account 120 subscribes to the target application 140 , then other terminals under the first user account 110 or the second user account 120 also subscribe to the target application 140 , so 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 can be regarded as a collection of various resources. The resources can be file resources such as pictures, files, and videos, or service resources such as screenshot services and screen projection services, or can be the camera's ability to take pictures and the computing power of the CPU. Capabilities and other hardware resources are not limited in this embodiment of the present application.

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

The first user account 110 also includes other terminals. The embodiment of the present application only uses the first terminal 111 and the second terminal 112 as examples. Similarly, the second user account 120 also includes other terminals. The embodiment of the present application only The third terminal 121 and the fourth terminal 122 are used as examples for illustration. The device types of the first terminal 111, the second terminal 112, the third terminal 121 and the fourth terminal 122 are the same or different. (Moving Picture Experts Group Audio Layer III, MP3) player, Moving Picture Experts Group Audio Layer IV (MP4) player, laptop computer, desktop computer, smart home, smart wearable Equipment and so on at least one.

The first terminal 111 , the second terminal 112 , the third terminal 121 , 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 multiple 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 , sharing group management 133 and resource gateway management 134 . The user management 131 is used to manage user account information, and the device group management 132 is used to manage all device information corresponding to the user account. The sharing group management 133 is used to manage devices or user accounts in the sharing group when sharing resources. The resource gateway management 134 is used to manage the mapping relationship between the device and the resource gateway, and is used to realize the resource calling of the application.

In the embodiment of the present application, sharing or sharing of resources can be realized between different terminals and different users. Among them, sharing means that the sharing party shares resources with the shared party, and the shared party can call the resources 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 It may be any two terminals among the first terminal 111 , the second terminal 112 , the third terminal 121 and the fourth terminal 122 . Exemplarily, description is made by taking the first terminal 111 as the sharing party and the third terminal 121 as the shared party as an example. As the shared party, the third terminal 121 can call the resource corresponding to the target application 140 in the sharing party's first terminal 111 .

In another possible implementation manner, the sharing party and the shared party may be different users. As an example, the first user account 110 is used as the sharer, and the second user account 120 is used as the shared party for illustration. Any terminal under the second user account 120 can call resources corresponding to the target application 140 in all terminals under the first user account 110, for example, a third terminal 121 under the second user account 120 can call resources under the first user account 110. Resources corresponding to the target application 140 in the first terminal 111 and the second terminal 112 .

Among them, sharing means that multiple sharing members are associated together to form a sharing group, and all sharing members in the same group can call resources of other members mutually. In a possible implementation manner, the sharing group members may be terminals, for example, the sharing members may be at least two terminals among the first terminal 111 , the second terminal 112 , the third terminal 121 and the fourth terminal 122 . Exemplarily, the first terminal 111 , the second terminal 112 and the third terminal 121 form a sharing group, and all terminals can mutually invoke resources corresponding to the target application 140 in other terminals. For example, the first terminal 111 may call the second terminal 112 and the third terminal 121 and include its own resources corresponding to the target application 140 , and the same is true for the second terminal 112 and the third terminal 121 .

In another possible implementation manner, the members of the sharing group may also be different users. Exemplarily, 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 to say, all terminals in the sharing group The members are the first terminal 111 , the second terminal 112 , the third terminal 121 and the fourth terminal 122 , and all terminals can call resources corresponding to the target application 140 in other terminals. For example, the first terminal 111 can call the second terminal 112, the third terminal 121, the fourth terminal 122 and resources corresponding to the target application 140 in itself; the second terminal 112 can call the first terminal 111, the third terminal 121, The fourth terminal 122 also includes its own resources corresponding to the target application 140 . Similarly, the same is true for 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 TV, a personal computer (Personal Computer, PC), a smart wearable device, a smart home, etc., which are not limited in this 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 be different devices of different users, which is not limited in this embodiment of the present application. Please refer to FIG. 2, which shows a flowchart of a resource interaction method provided by an exemplary embodiment of the present application, the method including:

Step 210, in response to a resource interaction trigger operation on the target application, the resource interaction initiating device generates resource interaction data.

In this embodiment of the present application, the resource interaction initiating device subscribes to a target application, and the resource interaction initiating device generates resource interaction data when receiving a user's resource interaction trigger operation on the target application.

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

Optionally, the target application may be a photo album application, a multi-device screenshot application, a game viewing application, a collaborative drawing board application, etc., which is not limited in this embodiment of the present application.

In a possible implementation manner, the resource interaction trigger operation may be a sharing operation.

Optionally, the sharing operation may be a click operation, a long press operation, etc. of a share button on the target application interface, which is not limited in this embodiment of the present application.

It should be noted that sharing means that the way of resource interaction is one-way. The device was unable to invoke the resource of an interactive participating device.

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

Optionally, the sharing operation may be a click operation, a long press operation, etc. on the share button of the target application interface, which is not limited in this embodiment of the present application.

It should be noted that sharing means that resource interaction is bidirectional, that is, the resource interaction initiating device shares the interaction resources with the interaction participating devices, and the interaction participating device and the resource interaction initiating device can call each other's resources.

Regarding the resource interaction data, the resource interaction data carries identification information, which at least includes a target application identification, so that the resource interaction initiating device and the interaction participating device can perform resource interaction. The resource interaction data generated under different resource interaction trigger operations are different, that is to say, the resource interaction initiating device generates different resource interaction data when the target application is respectively subjected to a sharing operation and a sharing operation.

In step 220, the interaction participating device acquires resource interaction data.

Regarding the manner of obtaining resource interaction data, in a possible embodiment manner, the resource interaction initiating device may send the resource interaction data, and the interaction participating device may obtain 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 it from the resource interaction initiating device.

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

In this embodiment of the present application, the resource interaction data includes identification information for determining the target application and the target interaction device, and the interaction participating 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 more, which is not limited in this embodiment of the present application.

Optionally, the target interaction devices may be different devices under the same user, or different devices under 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. In the embodiments of the full application, for the convenience of expression, the target interaction device is used as an example for illustration.

Step 240, after the interaction participating device determines the target application and the target interaction device based on the resource interaction data, it sends a resource call request through the target application.

After the interaction participating device determines the target application and the target interaction device, it sends a resource invocation request to the resource interaction initiating device. The resource invocation request is used to invoke the target interaction resource on the target interaction device. The target interaction resource is determined according to the business logic of the target application, that is, the resources needed to realize the application function of the target application.

Step 250, in response to the resource invocation request of the interaction participating device, the resource interaction initiating device provides the target interaction resource to the interaction participating device.

After receiving the resource invocation request of the interaction participant device, the resource interaction initiating device provides the target interaction resource to the interaction participant device. The target interaction resource may be a file resource, a hardware resource, a service resource, etc., which is not limited in this embodiment of the present application.

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

Optionally, the hardware resource may be a camera's photographing capability, imaging capabilities, various sensor capabilities, hardware computing capabilities, etc., which are not limited in this embodiment of the present application.

Optionally, the service resource may be a screenshot service, a local search service, a video playback service, a navigation service, a screen projection service, etc., which are 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 a photo album application, its corresponding target interactive resources are pictures and videos, which are one type of file resources; , which is a type of hardware resource; if the target application is a screen capture service application, its corresponding target interaction resource is a screen capture service, which is a type of service resource.

Step 260, the interaction participating device invokes the target interaction resource on the target interaction device through the target application.

The interaction participating device invokes the target interaction resource at the target interaction device through its target application.

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

To sum up, in the embodiment of this application, based on the sharing or sharing operation of 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 obtained resource interaction data, and then from A target interaction resource at the target interaction device is invoked by the target application. Compared with related technologies, in the embodiment of the present application, the object to be shared and shared is not the target application itself, but the resource corresponding to the target application. By sharing the resources corresponding to the target application with other devices, other devices can call the corresponding resources through the target application, thereby realizing the target application function. Through this mechanism, the target application can not only use the resources of the current device, but also call the resources of other devices, realize the distributed call of resources, and then realize more types of application functions.

Optionally, determining the target application and the target interaction device based on the resource interaction data includes:

Based on the resource interaction data, determine the target application through the application manager, and start the target application, and the application manager is used to manage the resource interaction of different applications;

Based on the resource interaction data, the target interaction device is determined through the application manager and the device selector.

Optionally, when the resource interaction trigger operation is a sharing operation, the resource interaction data includes the target application identifier and the sharing party identifier;

Based on the resource interaction data, determine the target interaction device through the application manager and device selector, including:

Based on the sharing party identifier, the target interactive device is determined through the application manager and the device selector.

Optionally, based on the sharing party identifier, the target interactive device is determined through the application manager and the device selector, including:

In the case that the sharing party ID is a device ID, the application manager determines the device represented by the device ID as a candidate interactive device; or,

In the case that the sharing party ID is the user ID, at least one device ID corresponding to the user ID is acquired through the application manager, and the device represented by the device ID is determined as a candidate interactive device;

Determine the target interactive device from the candidate interactive devices through the device selector.

Optionally, the target interaction device is determined from candidate interaction devices through a device selector, including:

Acquiring the device selection policy of the target application; using a device selector, determining a candidate interactive device conforming to the device selection policy as a target interactive device; or,

A device selection list is displayed based on the candidate interaction devices; and a candidate interaction device selected in the device selection list is determined as a target interaction device through a device selector.

Optionally, the resource interaction data also includes a sharing instance identifier;

Invoking the target interaction resource at the target interaction device through the target application, including:

Based on the shared instance identifier, the target application invokes the target interactive resource at the target interactive device, and the target interactive device is used to verify the authority of the shared instance identifier and provide the target interactive resource when the shared instance identifier passes the authority verification.

Optionally, when the resource interaction trigger operation is a sharing operation, the resource interaction data includes a target application identifier and a sharing group identifier;

Based on the shared group identifier, determine the target interaction device through the application manager and the device selector;

Methods also include:

The target interaction resource is provided to the target interaction device.

Optionally, based on the shared group identifier, the target interaction device is determined through the application manager and the device selector, including:

Join the sharing group represented by the sharing group identifier through the application manager;

determining, by the application manager, candidate interactive devices in the sharing group;

Optionally, the application manager determines the candidate interactive devices in the sharing group, including:

determining, by the application manager, the device characterized by the device identification as a candidate interactive device, where the device identification is included in the sharing group; or,

In the case that the sharing group contains the user identifier, at least one device identifier corresponding to the user identifier is acquired through the application manager, and the device represented by the device identifier is determined as a candidate interactive device.

Optionally, the method also includes:

In response to the exit operation, exit the sharing group through the application manager, and send an exit message to the server, and the server is used to update the sharing group based on the exit message, and synchronize the update result to the target interactive device;

In the case of receiving the disbandment message of the sharing group, exit the sharing group through the application manager;

In the case of receiving the removal message, the application manager exits the sharing group, and the removal message is used to indicate that the sharing group is removed.

Optionally, calling the target interaction resource at the target interaction device through the target application includes:

Obtaining a target resource gateway address of the target interactive device based on the device identifier of the target interactive device, where the target resource gateway address is the gateway address of the resource gateway in the target interactive device, and the resource gateway is used to manage resource calls in the device;

Based on the address of the target resource gateway, the target application accesses the target resource gateway to obtain the target interaction resource.

Optionally, obtain resource interaction data, including:

Parse the resource interaction data from the graphics code; or,

Resource interaction data parsed from interaction links; or,

Receive resource interaction data through near field communication.

Optionally, the target interaction resources include at least one of file resources, hardware resources and service resources.

Optionally, generating resource interaction data in response to resource interaction trigger operations on the target application, including:

In response to a resource interaction trigger operation on the target application, resource interaction data is generated through an application manager, and the application manager is used to manage resource interaction of different applications;

In response to the resource invocation request of the interactive participating device, provide the interactive participating device with the target interactive resource, including:

In response to the resource invocation request of the interactive participating device, the target interaction resource is provided to the interactive participating device through the resource gateway, and the resource gateway is used to manage resource invocation in the device.

Optionally, in response to a resource interaction trigger operation on the target application, the resource interaction data is generated by the application manager, including:

In response to the sharing operation on the target application, resource interaction data including the target application identifier and the sharing party identifier are generated through the application manager.

Optionally, in response to the sharing operation on the target application, the resource interaction data including the target application identifier and the sharing party identifier is generated through the application manager, including:

In response to the device-level sharing operation on the target application, generate resource interaction data including the target application identifier and the device identifier through the application manager;

In response to the user-level sharing operation on the target application, the resource interaction data including the target application ID and the user ID are generated through the application manager, and the user ID is used to represent the user corresponding to the sharing party.

In response to the resource invocation request of the interactive participating device, perform permission verification on the sharing instance identifier contained in the resource invocation request;

In the case that the sharing instance identifier passes the authority verification, the target interaction resource is provided to the interaction participating device.

Optionally, the method also includes:

In response to a sharing cancellation operation on the target application, the sharing instance identifier is deleted.

In response to the sharing operation on the target application, generate resource interaction data including the target application identifier and the sharing group identifier through the application manager;

Methods also include:

The target interaction resource at the interaction participating device is invoked by the target application.

Optionally, the method also includes:

In response to the device-level sharing operation on the target application, sending a first sharing group creation request to the server, the first sharing group creation request includes a device identifier, and the server is used to create a sharing group composed of devices based on the first sharing group creation request;

In response to the user-level sharing operation on the target application, a second sharing group creation request is sent to the server, the second sharing group creation request includes a user identifier, and the server is used to create a sharing group composed of users based on the second sharing group creation request.

Optionally, the method also includes:

In response to the sharing group disbanding operation, a sharing group disbanding instruction is sent to the server, so that the server disbands the sharing group based on the sharing group disbanding instruction, and deletes the sharing group identifier.

Optionally, the method also includes:

In response to the removal operation, a removal instruction is sent to the server, so that the server updates the sharing group based on the removal instruction, and synchronizes the update result to the sharing parties in the sharing group, and the removal instruction includes the interactive participation device to be removed.

Optionally, the method also includes:

The exit message sent by the server is received, and the exit message is triggered by an interactive participating device that actively exits the sharing group.

Optionally, the method also includes:

When the gateway address of the resource gateway is updated, a gateway address update message is sent to the server, so that the server can synchronize the updated gateway address to the device selector of other devices, and the device selector stores the information between the device identifier and the gateway address. Mapping relations.

Optionally, after the resource interaction data is generated, the method includes:

generating graphical code based on resource interaction data; or,

generating interaction links based on resource interaction data; or,

Send resource interaction data through near field communication.

In the embodiment of the present application, the target application is determined by the application manager, the target interaction device is determined by the application manager and the device selector, and the target interaction resource on the target interaction device is invoked by the resource gateway. The resource interaction method is introduced below by taking the resource interaction initiating device and the interaction participating device as examples. Please refer to FIG. 3 , which shows a flow chart of a resource interaction method provided by another exemplary embodiment of the present application, and the method includes:

Step 310, in response to a resource interaction trigger operation on the target application, the resource interaction initiating device generates resource interaction data through an application manager, and 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 to manage applications and implement resource interaction between the resource interaction initiating device and the interaction participating devices.

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

Regarding the form of the application manager, in a possible implementation manner, the application manager may be a super application, and the super application may be a client software that manages various applications. Users can subscribe or unsubscribe applications in the super application. The user may also select a target application in the super application, and perform a sharing operation or sharing operation on the target application. Exemplarily, 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 that the user has subscribed to. With application A as the target application, the user clicks on application A43, and the resource interaction initiating device receives the user's trigger operation on application A43 and enters the application details interface 42. The application details interface 42 includes a share button 421 and a share button 422. Or by clicking the sharing button 422, the super application generates resource interaction data.

In another possible implementation manner, the application manager can be implemented in the application icon option. Exemplarily, as shown in FIG. 5 , with application A as the target application, the user presses and holds the icon of application A52, and the resource interaction initiating device receives the user's trigger operation on application A52, and an operation option interface 51 pops up, and the operation option interface 51 includes The sharing button 511 and the sharing button 512 , through the click operation of the sharing button 511 and the sharing button 512 , the super application generates resource interaction data.

In another possible implementation manner, it is embedded in the application in the form of a plug-in. Exemplarily, as shown in FIG. 6 , with application A as the target application, when the user opens application A62, the resource interaction initiating device receives the user's trigger operation on application A62, and the interface of application A62 pops up a sharing and sharing operation interface 61, sharing and sharing The operation interface 61 includes a sharing button 611 and a sharing button 612 , and by clicking on the sharing button 611 or the sharing button 612 , the super application generates resource interaction data.

In step 311, the resource interaction initiating device generates a graphic code based on the resource interaction data; or, generates an interaction link based on the resource interaction data; or, sends the resource interaction data through near field communication.

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

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

Exemplarily, as shown in FIG. 7 , take the photo album application as the target application and the application manager as the super application as an example. The user 76 clicks the photo album application 711 on the application list interface 71 of the super application, and the resource interaction initiating device receives the trigger operation of the user 76 on the photo album application 711, and enters the application details interface 72, which includes the sharing button 721 and the sharing button 722 . The user 76 clicks the sharing button 721 , and the resource interaction initiating device receives the trigger operation of the sharing button 721 by the user 76 , generates resource interaction data through the super application, and displays the sharing mode interface 73 . The user clicks the two-dimensional code sharing button 731, and the resource interaction initiating device receives the user's trigger operation on the two-dimensional code sharing button 731, and generates a two-dimensional code 74, which contains resource interaction data.

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

Optionally, the interactive link may be a text message link, a WeChat link, etc., which is not limited in this embodiment of the present application.

Exemplarily, as shown in FIG. 8 , take the game spectator application as the target application and the application manager as the super application as an example. The user 86 clicks the game spectator application 811 on the application list interface 81 of the super application, and the resource interaction initiating device receives the trigger operation of the user 86 on the game spectator application 811, and enters the application details interface 82, which includes a share button 821 and a share button 821. Key 823. The user 86 clicks the sharing button 821 , and the resource interaction initiating device receives the trigger operation of the user 86 on the sharing button 821 , generates resource interaction data through the super application, and displays the sharing mode interface 83 . The user 86 clicks the SMS sharing button 831, and the resource interaction initiating device receives the trigger operation of the user 86 on the SMS sharing button 831, and generates a SMS link 84, which contains resource interaction data.

In another possible implementation manner, after the user performs a resource interaction trigger operation on the target application, the resource interaction initiating device sends an NFC (Near Field Communication, near field communication) signal, and the NFC signal carries resource interaction data.

Exemplarily, as shown in FIG. 9 , take a multi-device screen capture application as a target application, and an application manager 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, and the resource interaction initiating device receives the trigger operation of the user 94 on the multi-device screenshot application, and enters the application details interface 92, which includes a share button 921 and Share button 922 . The user 94 clicks the sharing button 921 , and the resource interaction initiating device receives the trigger operation of the user 94 on the sharing button 921 , generates resource interaction data through the super application, and displays the sharing mode interface 93 . The user 94 clicks the touch share button 931 , and the resource interaction initiating device receives the trigger operation of the user 94 on the touch share button 931 , and at the same time sends out an NFC signal, which contains resource interaction data.

In step 312, the interaction participating device parses the graphic code to obtain the resource interaction data; or, parses the interaction link to obtain the resource interaction data; or, receives the resource interaction data through near-field communication.

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.

Exemplarily, as shown in FIG. 7, the resource interaction initiating device generates a two-dimensional code 74, which contains resource interaction data, and the user 77 interacts with the scan control in the application list interface 75 of the super application in the device. 751 scans the two-dimensional code 74, and the interactive participation device parses the two-dimensional code 74 to obtain resource interaction data.

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.

Exemplarily, 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, and the short message link 84 contains resource interaction data. The interaction participation device receives the SMS link 84 , and when the user 87 clicks the SMS link 84 , the interaction participation device parses the SMS link 84 to obtain resource interaction data.

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

Exemplarily, as shown in Figure 9, the resource interaction initiating device generates resource interaction data through the super application, and sends out an NFC signal, which contains the resource interaction data, and the interaction participating device receives the NFC signal sent by the resource interaction initiating device. To resource interaction data.

Step 313 , based on the resource interaction data, the interaction participating device determines the target application through the application manager, and starts the target application. The application manager is used to manage resource interaction of different applications.

In this embodiment of the present application, the interaction participating device is deployed with an application manager, and the application manager is used to manage subscribed applications in the interactive participating device. Since the resource interaction data carries identification information, wherein the identification information includes at least the target application identification, the interaction participation device determines the 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 device. application.

Exemplarily, as shown in FIG. 7, the interaction participating device parses the resource interaction data from the two-dimensional code 74, and based on the target application identifier in the resource interaction data, determines that the target application is the photo album application 78 through the super application of the interaction participating device. And launch photo album application 78.

Exemplarily, as shown in FIG. 8, the interaction participating device parses the resource interaction data from the SMS link 84, and based on the target application identifier in the resource interaction data, determines that the target application is the game viewing application 85 through the super application of the interaction participating device, and The game viewing application 85 is started.

Exemplarily, as shown in FIG. 9, the interaction participating device receives the NFC signal sent by the resource interaction initiating device, obtains resource interaction data from the NFC signal, and determines the resource interaction data based on the target application identifier in the resource interaction data through the super application of the interaction participating device. The target application is the multi-device screenshot application 95, and the multi-device screenshot application 95 is started.

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

In this embodiment of the present application, the 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 the application device group management sub-module, the device selection policy sub-module and the gateway conversion sub-module. The application device group management sub-module is used to manage the device group range where the target application is currently running, that is to say, the device range where the target application can call resources.

In addition, it should be noted that the device group scope of the application device group management submodule is not fixed. In a possible implementation manner, in a default state, the device group scope of the application device group management submodule is the current device or the devices under the current user account. The default state indicates that the current device or the device under the current user account does not interact with other devices. Exemplarily, when the interaction participant device does not perform resource interaction with the resource interaction initiator device, the device group scope of the application device group management submodule of the interaction participant device is the interaction participant device.

In another possible implementation, in the case of resource interaction, the device group range of the application device group management submodule will change, and the device group range is set through the application manager. In the case of resource interaction, the target application’s running device includes not only the current device or the device under the current user account, but also the device that interacts with it or the device under the user account, so the device group of the application device group management submodule Ranges are subject to change. Since the application manager is used to manage the resource interaction of the application, the range of the device can be determined through the application manager, so the range of the device group of the application device group management submodule can be determined through the application manager. Exemplarily, when the interaction participating device and the resource interaction initiating device perform resource interaction, the device group scope of the application device group management submodule is set as the interaction participating device and the resource interaction initiating device through the application manager.

The device selection strategy sub-module is used to provide multiple device selection strategies, that is, to determine the target interactive devices from the range of device groups managed by the application device group management sub-module and form a list of target interactive devices.

Optionally, the device selection policy may be selecting all devices, selecting the current device, selecting other devices, etc., which is not limited in this embodiment of the present application. Wherein, selecting other devices refers to selecting all devices other than the current device.

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

In a possible implementation, the target application interface has a device selection interface, and the device selection interface has buttons for different device selection strategies, such as selecting all device buttons, selecting the current device button, selecting other device buttons, or selecting a specific device button, etc. , the user clicks different device selection strategy buttons according to their own needs. When the interactive participating device receives the user's trigger operation on the device selection strategy button, the device selection strategy sub-module manages from the application device group management sub-module according to the user's device selection strategy. Target interactive devices are determined in the range of the device group and a list of target interactive devices is formed.

In this embodiment of the application, by adjusting the range of device groups managed by the application device group management sub-module and the device selection policy provided by the device selection policy sub-module, the application developers do not need to perceive the equipment and do not need to modify the application. Under such circumstances, the direct sharing of resources between different devices and different users is realized.

The gateway converting submodule converts the target interactive device list obtained from the device selection policy submodule into a corresponding target gateway address list.

Exemplarily, as shown in FIG. 10 , the device selector 1003 includes three submodules, which are respectively a device selection policy submodule 1004 , a gateway conversion submodule 1005 , and an application device group management submodule 1006 . When the interaction participating device obtains the resource interaction data, based on the target application identifier of the resource interaction data, the target application 1002 is determined through the application manager 1001, and at the same time, the range of device groups managed by the application device group management submodule 1006 is set through the application manager 1001. The scope of the device group is all the devices currently running on the target application, including not only resource interaction initiating devices and interaction participating devices, but also other devices. These devices can belong to the same user or to different users. Further, the target application 1002 transmits its own device selection policy to the device selection policy submodule 1004, such as selecting all devices. Select the target interactive device in , and generate a list of target interactive devices.

Step 315: After the interaction participating device determines the target application and the target interaction device based on the resource interaction data, it sends a resource call request through the target application.

Step 315 is the same as step 240, which will not be repeated in this embodiment of the present application.

Step 316: In response to the resource invocation 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 to manage resource invocation in the device.

A resource gateway is deployed in the resource interaction initiating device. When the resource interaction initiating device receives a resource invocation request from the resource interaction initiating device, it invokes the target interaction resource of the local target application through the resource gateway and provides it to the interaction participating device through the resource gateway.

The resource gateway is a unified entry gateway for invoking resources on the target interactive device, which supports access to different types of resources.

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

Optionally, the resource gateway provides an HTTP (Hyper Text Transfer Protocol, hypertext transfer protocol) server to support calling services on the device through the Restful API. The service may be a screenshot service, a screen projection service, and the like.

Step 317, when the gateway address of the resource gateway is updated, the resource interaction initiating device sends a gateway address update message to the server, so that the server can synchronize the updated gateway address to the device selector of other devices, and the device selector stores the device The mapping relationship between the identifier and the gateway address.

In a possible implementation, since unused applications correspond to different resources, when subscribing to a new application or unsubscribing an application on the resource interaction initiating device, the resource interaction initiating device automatically updates the gateway address of the resource gateway, and sends The resource gateway management on the side synchronizes its updated gateway address. In order to ensure the consistency of resource sharing and resource sharing, the resource gateway management will synchronize the updated gateway address to the device selector of other devices. The mapping relationship between the device and the gateway address is stored in the device selector.

Step 318, based on the device identifier of the target interaction device, the interaction participant device obtains the address of the target resource gateway of the target interaction device. The target resource gateway address is the gateway address of the resource gateway in the target interaction device, and the resource gateway is used to manage resource calls in the device.

In the embodiment of this application, resource gateway management is deployed on the server side, which is used to manage the mapping relationship between target interactive devices and resource gateways. That is to say, when we need to call the resources on the target interactive device, we need to query the access address of the resource gateway at the target interactive device through the resource gateway management first, and then we can call the resources at the target interactive device. Since the device selector stores the mapping relationship between the device identifier and the gateway address, the gateway conversion submodule in the device selector of the interactive participating device obtains the target interactive device and gateway address from the resource gateway management based on the device identifier of the target interactive device. The corresponding relationship of resource gateways is converted one by one to generate the target resource gateway address, and the target resource gateway address is fed back to the target application.

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

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

Exemplarily, as shown in FIG. 10 , the device selection policy submodule 1004 transfers the target interaction device list to the gateway conversion submodule 1005, and the gateway conversion submodule 1005 obtains the correspondence between the target interaction device and the resource gateway from the resource gateway management 1007 on the server side. Relationships are converted one by one to generate the target resource gateway address, and the gateway conversion submodule 1005 feeds back the generated target resource gateway address to the target application 1002 .

Step 319, based on the address of the target resource gateway, the interaction participant device accesses the target resource gateway through the target application to obtain the target interaction resource.

Based on the address of the target resource gateway, the interaction participating device accesses the resource gateway in the target interaction device through the target application to obtain the target interaction resource.

In the embodiment of the present application, the target application is determined by the application manager, the target interaction device is determined by the application manager and the device selector, and the target interaction resource at the target interaction device is invoked by the resource gateway, thereby realizing the distributed invocation of resources, and further enabling Realize more types of application functions.

In a possible implementation manner, when the resource interaction trigger operation is a sharing operation, the resource interaction data includes the target application ID, the sharing party ID, and the sharing instance ID, the target application ID is used to determine the target application, and the sharing party ID is used to determine The target interaction device, the shared instance ID is used to obtain the target interaction resource. The resource sharing method is introduced below, as shown in FIG. 11 , which shows a resource interaction method provided by another exemplary embodiment of the present application, and the method is applied to a device that initiates resource interaction, that is, a sharing party. It should be noted that the resource interaction initiating device is one of the sharing parties, and for the convenience of description, the sharing party is taken as an example of the resource interaction initiating device for illustration.

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

In this embodiment of the present application, 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 a target application identifier and a device identifier, wherein the device identifier is used to represent the device corresponding to the sharing party. The target application identifier and the device application identifier are unique, so different target applications correspond to different target application identifiers, and different devices correspond to different target interaction device identifiers.

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

In this embodiment of the application, the user-level sharing operation means that both the sharing party and the shared party are users, and there may be one device or multiple devices under the user account. In this case, the resource interaction data generated by the resource interaction initiating device through the application manager includes a target application identifier and a user identifier, where the user identifier is used to represent user account information. The target application identifier and the user identifier are unique, so 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 the user account information corresponding to the sharing party, not the user account information corresponding to the shared party.

Step 1103, in response to the resource invocation request of the interaction participating 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 present application, the resource interaction data further includes a sharing instance identifier, which is used to represent an event that the shared party invokes the sharing party's resources. The sharing instance ID is unique, so the event that the shared party invokes the resource of the sharing party corresponds to a different sharing instance ID.

After the interaction participant device determines the target application and the target interaction device based on the target application identifier and device identifier or user identifier in the resource interaction data, it sends a call request to the resource interaction initiating device, and the call request is used to call the target interaction device. Target interaction resource. Since the calling request includes the sharing instance identifier, before the interaction participant device calls the target interaction resource at the target interaction device, the resource interaction initiating device needs to verify the authority of the sharing instance identifier. The authority check is used to verify 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.

Step 1104, in the case that the shared instance ID passes the authority verification, 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 after passing the permission verification of the sharing instance identifier.

In another possible implementation manner, if the resource interaction initiating device fails to pass the authority check on the sharing instance ID, it cannot provide the target interaction resource to the interaction participating device.

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 has finished sharing resources with the shared party, and based on the user canceling the sharing, the sharing party deletes the sharing instance identifier. For example, the user cancels the sharing operation of the target application, the resource interaction initiating device receives the user's sharing cancellation operation of the target application, the resource interaction initiating device deletes the sharing instance identifier, and the interaction participating device cannot call the resources of the resource interaction initiating device.

In another possible implementation manner, when the sharing party shares resources with the shared party, the user cancels the sharing, and the sharing party deletes the sharing instance identifier. For example, when a resource interaction device shares resources with an interaction participating device, the user cancels the sharing operation of the target application, and the resource interaction initiating device receives the user's share cancellation operation on the target application, the resource interaction initiating device deletes the sharing instance identifier, and the interaction Participating devices cannot invoke the resources of the resource interaction initiating device.

Exemplarily, as shown in Figure 8, the target application is the game viewing application, the application manager is a super application, and the device-level sharing operation of the game viewing is taken as an example. In this case, the sharing party is the device that initiates resource interaction , the shared party is an interactive participating device. The user 86 clicks the game spectator application 811 on the application list interface 81 of the super application, and the resource interaction initiating device receives the trigger operation of the user 86 on the game spectator application 811, and enters the application details interface 82, which includes a share button 821 and a share button 821. Key 823. The user 86 clicks the share button 823 , and the resource interaction initiating device receives the trigger operation of the user 86 on the share button 823 , generates resource interaction data through the super application, and displays the sharing mode interface 83 . The user 86 clicks the SMS sharing button 831, and the resource interaction initiating device receives the user's trigger operation on the SMS sharing button 831, and generates a SMS link 84, which contains resource interaction data, and the resource interaction data includes game spectator application identification, device The ID refers to the ID of the device that initiated the resource interaction and the ID of the sharing instance. The resource interaction initiating device sends the text message link 84 to the interactive participating device, the user 87 clicks on the text message link 84, and the interactive participating device obtains the resource interaction data by analyzing the text message link 84, and determines that the game spectator application is the target application through the application identification, resource interaction The initiating device is the target interactive device, and then sends a resource call request to the resource interaction initiating device. The resource invoking request includes the sharing instance identifier, that is, the interactive participating device needs to call the resource of the resource interaction initiating device, that is, the projection service. The resource interaction initiating device receives the resource invocation request of the interactive participating device, and performs permission verification on the sharing instance identifier contained in the resource invoking request, that is, the resources provided by the resource interaction initiating device for the interactive participating devices are screencasting services, and the resources provided by the interactive participating devices The required resources are also for screencasting services. The two are the same. The resource interaction initiator device passes the permission verification on the sharing instance ID, and the interactive participant device calls the resources of the interactive participant device. party game.

Exemplarily, as shown in FIG. 12 , during the game process in the resource interaction initiation device of the interactive participation device, the user 86 clicks the game viewing application 811 on the application list interface 81 of the super application again, and the resource interaction initiation device receives the user 86's response to the game. The trigger operation of the game viewing application 811 enters the cancel interface 1201, which includes the cancel sharing button 1202, the user clicks the cancel sharing button 1202, the resource interaction initiating device receives the trigger operation of the user 86 on the cancel sharing button 1202, and enters the application details Interface 82, delete the shared instance identifier at the same time. When the user 87 clicks on the SMS link 84 received before, because the resource interaction initiating device deletes the sharing instance identifier, the interactive participating device cannot call the resource interaction initiating device's screencasting service, and its game viewing application 85 displays a black screen.

The resource sharing method is introduced below, as shown in FIG. 13 , which shows a resource interaction method provided by another exemplary embodiment of the present application, and the method is applied to an interaction participating device, that is, a shared party. It should be noted that the interactive participating device is one of the shared parties. For the convenience of identification, the shared party is an interactive participating device as an example for illustration.

Step 1301, the interaction participating device acquires resource interaction data, which is generated by the resource interaction initiating device when receiving a sharing operation on a target application, and the resource interaction data includes a target application ID and a sharing party ID.

The interaction participating device acquires resource interaction data from the resource interaction initiating device. The resource interaction data includes a target application identifier and a sharer identifier. The target application identifier is used to determine the target application, and the sharing party identifier is used to determine the target interactive device. In this embodiment of the present application, the target interaction device is the 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 resource interaction initiating device and the interaction participating device share in a device-level sharing manner, the sharing party identifier is a device identifier.

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

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

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

In the embodiment of the present application, the sharing party ID may be a device ID or a user ID. In these two cases, the methods for determining the target interaction device are different, which will be introduced below.

Step 1303, when the sharing party ID is the device ID, the interaction participating device determines the device represented by the device ID 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 a device identifier, the application manager in the interaction participating device configures the range of device groups managed by the application device group management submodule in the device selector through the device identifier. The range of the device group includes all devices of the sharing party, and the devices within the range of the device group are determined as candidate interactive devices. For example, in the embodiment of the present application, the sharing party is only the resource interaction initiating device, so the device scope is the resource interaction initiating device, and the resource interaction initiating device is the candidate interaction device.

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

Step 1304, when the sharing party ID is the user ID, the interaction participating device acquires at least one device ID corresponding to the user ID through the application manager, and determines the device represented by the device ID as a candidate interaction device.

In the embodiment of the present application, a user management module and a device management module are deployed on the server side. The user management module is used to manage all user account information, and the device management module is used to manage device information under each user account. The user ID is used to represent the user account information, and the device ID is used to represent the corresponding device information under the user account. The number of devices under the user account can be one or more, and different devices correspond to different device IDs.

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

In addition, it should be noted that, step 1303 and step 1304 can be selected to be executed, which is not limited in this embodiment of the present application.

In step 1305, the interaction participating device acquires the device selection policy of the target application; through the device selector, the selected interactive device conforming to the device selection policy is determined as the target interaction device.

When the sharing party and the shared party are device-level sharing, based on the user's trigger operation on the target application device selection interface, the interactive participating devices obtain the device selection policy of the target application, and transfer the device selection policy to the device selection policy of the device selector The sub-module, the device selection policy sub-module selects target interactive devices from the range of device groups managed by the application device group management sub-module, that is, candidate interactive devices, based on the device selection policy.

In step 1306, the interaction participating device displays a device selection list based on the candidate interaction devices; through the device selector, the candidate interaction device selected in the device selection list is determined as the target interaction device.

When the sharing party and the shared party are user-level sharing, based on the user's trigger operation on the target application device selection interface, the interactive participating device obtains the device selection policy of the target application, and transfers the device selection policy to the device selection policy of the device selector The sub-module, the device selection policy sub-module selects target interactive devices from the range of device groups managed by the application device group management sub-module, that is, the device selection list (that is, candidate interactive devices) based on the device selection policy. It should be noted that, at this time, the interactive participating device is any device under the user account of the shared party.

In addition, it should be noted that, step 1305 and step 1306 can be selected to be executed, which is not limited in this embodiment of the present application.

Step 1307, based on the shared instance ID, the interactive participating device invokes the target interactive resource at the target interactive device through the target application, and the target interactive device is used to verify the authorization of the shared instance ID, and provide the target interactive resource when the shared instance ID passes the authorization verification .

The interaction participating device determines the target application and the target interactive device based on the target application ID and the sharing party ID in the resource interaction data, and sends a resource call request to the target interactive device, that is, the resource interaction initiating device. The resource call request includes the sharing instance ID, the resource The interaction initiating device performs authorization verification on the sharing instance ID. After the sharing instance ID passes the authorization verification of the resource interaction initiating device, it provides the target interaction resource to the interaction participating device. That is to say, the interaction participating device can call the resources of the interaction initiating device through the target application. resource.

Exemplarily, as shown in Figure 14, it shows a schematic diagram of the principle of resource sharing at the device level. The target application is the photo album application, the sharing party is the resource interaction initiation device mobile phone A, and the shared party is the interaction participating device mobile phone B as an example. .

The mobile phone A generates resource interaction data through the first application manager 1401, and the resource interaction data includes target application identifiers, device identifiers and sharing instance identifiers. Mobile phone B acquires the resource interaction data, determines the target application as the photo album application 1404 through the second application manager 1402 based on the target application identifier, and starts the photo album application 1404 . At the same time, based on the device identifier, the second application manager 1402 sets the device group range of the application device group management submodule in the device selector 1405 to mobile phone A, and determines it as a candidate device. Based on the device selection policy selected by the user on the device selection interface of the photo album application 1404 to select all devices, it is determined that the candidate device mobile phone A is the target interaction device. Further, the target resource gateway address of the target interactive device mobile phone A is obtained from the resource gateway management 1406 through the device selector 1405 , and the target resource gateway address is fed back to the album application 1404 . Further, a resource call request is sent to the target interactive device mobile phone A, the resource interaction request includes the sharing instance identifier, and the target interactive device mobile phone A provides the photo resource corresponding to the photo album application to mobile phone B after passing the permission verification of the sharing instance identifier. 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.

Exemplarily, as shown in FIG. 15 , it shows a schematic diagram of user-level shared resource interaction. Take the photo album application as the target application, the sharing party is user A, and the shared party is user B as an example. The account of user A includes mobile phone A and mobile phone B, and the account of user B includes mobile phone C.

Any device under the account of user A generates resource interaction data through its application manager. For example, mobile phone A under the account of user A generates resource interaction data through the first application manager 1501. The resource interaction data includes target application identification, user identification and Share instance ID. Any device under the account of user B obtains the resource interaction identifier. For example, mobile phone C under the account of user B obtains the resource interaction data, and based on the target application identifier, the second application manager 1502 determines that the target application is the photo album application 1505, and starts The photo album application 1505 simultaneously queries the user management module 1507 and the device management module 1508 of the server through the second application manager 1502 for a device list under the account of user A based on the user ID, and the device list includes mobile phone A and 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, mobile phone A and mobile phone B as candidates equipment. Based on the device selection strategy of the user in the device selection interface of the photo album application 1505 is to select all devices, the candidate devices mobile phone A and mobile phone B are determined as target interaction devices. Further, the target resource gateway addresses of the target interaction devices mobile phone A and mobile phone 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 call request to the target interactive device mobile phone A and mobile phone B, and the resource interaction request includes the sharing instance identifier, and the target interactive device mobile phone A and mobile phone B provide the mobile phone C with The photo resource corresponding to the photo album application. Mobile phone C traverses the

resource gateways

1503 and 1504 in the target resource gateway address through the album application 1505, and calls the photo resource corresponding to the album application 1505.

In this embodiment of the application, based on the target application ID, the sharing party ID, and the sharing instance ID, the interaction participating device can call the resource corresponding to the target application at the resource interaction initiating device to realize resource sharing between the resource interaction initiating device and the interaction participating device. Enriched resource sharing methods.

In another possible implementation manner, the resource interaction trigger operation is a sharing operation, and the resource interaction data includes a target application identifier and a sharing group identifier, the target application identifier is used to determine the target application, and the sharing group identifier is used to determine the sharing group. The resource sharing method is introduced below, as shown in FIG. 16 , which shows a resource interaction method provided by another exemplary embodiment of the present application, and the method is applied to a device that initiates resource interaction, that is, a sharing group owner. It should be noted that the resource interaction initiating device is one of the sharing group owners. For the convenience of expression, the sharing group owner is taken as the resource interaction initiating device as an example for illustration.

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

In this embodiment of the present application, based on the user's sharing operation on the target application, the resource interaction initiating device generates resource interaction data through the application manager, and the resource interaction data includes the target application identifier and the sharing group identifier.

Wherein, sharing means that multiple devices or users are associated together to form a sharing group, and devices or users in the same sharing group can call resources of other devices or users each other. The device or user who creates the sharing group is called the sharing group owner. Only after the sharing group owner creates the sharing group, other devices or users can join the sharing group. The sharing operation refers to the operation of creating a sharing group, and the sharing group identifier is used to represent 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 is unique, and different sharing groups have different sharing group IDs. In this embodiment of the application, the resource interaction initiating device is a sharing group owner.

Exemplarily, as shown in FIG. 17 , the collaborative drawing board application is taken as the target application, the application manager is the super application, and the resource interaction initiating device is the shared group owner as an example for illustration.

The user 1708 clicks the collaborative drawing board application 1704 on the application list interface 1701 of the super application, and the resource interaction initiating device receives the user's trigger operation on the collaborative drawing board application 1704, and enters the application details interface 1702, which includes the sharing button 1705 and the sharing button 1706 , the user 1708 clicks the sharing button 1706, the resource interaction initiating device receives the user 1708's trigger operation on the sharing button 1706, generates resource interaction data through the super application, the resource interaction data includes the target application ID and the sharing group ID, and displays the sharing group Create an interface 1703 , and at this time, the resource interaction initiating device is the 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 sharing group creation request to the server, the first sharing group creation request includes the device identifier, and the server is used to create a resource based on the first sharing group creation request. A sharing group consisting of devices.

In the embodiment of the present application, the sharing group management is deployed on the server side, and the sharing group management is used to manage the creation of the sharing group and the joining and exiting of the sharing group members. Therefore, when the resource interaction initiating device receives the user's device-level sharing operation on the target application, it sends a sharing group creation request to the sharing group management. The sharing group creation request includes the device identifier of the resource interaction initiating device, and the sharing group management is based on the creation request. Create a sharing group, and the device that initiates the resource interaction is the sharing group owner.

In this embodiment of the application, device-level sharing means that all members of the 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 used to create a second sharing group creation request based on the second sharing group creation request A sharing group made up of users.

In this embodiment of the application, when the resource interaction initiating device receives the user's user-level sharing operation on the target application, it sends a sharing group creation request to the sharing group management, and the sharing group creation request includes the user account corresponding to the resource interaction initiating device The user ID of the sharing group management creates a sharing group based on the creation request, and the user who belongs to the resource interaction initiating device is the sharing group owner. The sharing group includes all devices under the user account.

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

Step 1604, in response to the resource invocation request of the interaction participant device, the resource interaction initiating device provides the interaction participant device with the target interaction resource through the resource gateway, and the resource gateway is used to manage resource invocation in the device.

After the interaction participating device determines the target application based on the target application identifier and the sharing group identifier in the resource interaction data and joins the sharing group, it sends a resource call request to the target interactive device in the sharing group, and the resource call request is used to call the target interactive device. The target interaction resource of the target interaction device in the shared group, that is, the resource interaction initiation device provides the target interaction resource to the interaction participant device through the resource gateway after receiving the resource invocation request.

Step 1605, the resource interaction initiating device invokes the target interaction resource on the interaction participating device through the target application.

In the embodiment of the present application, since the devices in the sharing group can call resources of all devices, the resource interaction initiating device can also call the target interaction resource on the interaction participating device through the target application.

The resource sharing method is introduced below, as shown in FIG. 18 , which shows a resource interaction method provided by another exemplary embodiment of the present application, which is applied to an interactive participating device. It should be noted that the interactive participating device is One of the sharing members, for the convenience of expression, the sharing member is an interactive participating device as an example for illustration.

Step 1801, the interaction participating device acquires resource interaction data, which is generated by the resource interaction initiating device upon receiving a sharing operation on a target application, and the resource interaction data includes a target application ID and a sharing group ID.

The interaction participating device acquires resource interaction data from the resource interaction initiating device, and the resource interaction data includes a target application identifier and a sharing group identifier. The sharing group identifier is used to represent the sharing group to be joined by the interactive participating device.

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

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

In the embodiment of the present application, based on the sharing group identifier in the resource interaction data, the interaction participating device joins the sharing group corresponding to the sharing group identifier through the application manager. It should be noted that the interactive participating device joins the sharing group as a sharing member, which is functionally different from the sharing group owner role. First, sharing members need to get the consent of the sharing group owner to join the sharing group. Second, the sharing group owner has the right to remove the sharing members from the sharing group, while the sharing members only have the right to actively withdraw from the sharing group. Third, the sharing group owner has Dismiss the permission of the sharing group, but the sharing members do not have the permission.

In a possible implementation manner, the interactive participating device can only join one sharing group as a sharing member. For example, after the interactive participating device joins the first sharing group represented by the first sharing group identifier through the application manager, when it passes through the When the application manager joins the second sharing group represented by the second sharing group identifier, it needs to exit the first sharing group, otherwise it cannot join the second sharing group.

Exemplarily, as shown in FIG. 19 , the cooperative drawing board application is taken as the target application, and the super application is the application manager for illustration. The resource interaction initiation device 1901 creates a sharing group 1902 as a sharing group owner, generates resource interaction data, and sends the resource interaction data to the interaction participating device 1903 through an NFC signal. The interaction participation device 1903 obtains the resource interaction data through the NFC signal, and joins the sharing group 1902 as a sharing member through the sharing group identifier in the resource interaction data, but the interaction participation device 1903 has already joined a sharing group before, because the collaborative sketchpad application interface will The sharing group selection interface 1904 pops up, the sharing group selection interface 1904 includes a join sharing group button 1905 and a quit joining sharing group button 1906, the user clicks the join sharing group button 1905, and the interactive participating device 1903 receives the user's trigger on the join sharing group button 1905 operation, it will automatically exit the shared group it has joined, and join the shared group 1902 as a shared member 1903 at the same time.

In another possible implementation manner, as a sharing member, an interaction participating device may join multiple sharing groups at the same time, and resource interaction between sharing groups does not interfere with each other. For example, after the interactive participating device joins the first sharing group represented by the first sharing group through the application manager, it may also join the second sharing group represented by the second sharing group identifier through the application manager. The first sharing group Resource interaction with the second sharing group does not interfere with each other.

In the embodiment of the present application, the members in the sharing group may be devices or users. In these two cases, the methods for determining the target interaction device are different, which will be introduced below.

Step 1804, in the case that the sharing group contains the device identifier, the interaction participant device determines, through the application manager, the device represented by the device identifier as a candidate interaction device.

In a possible implementation manner, the members of the sharing group are devices, and different devices correspond to different device identifiers, and the application manager in the interactive participating device configures the application device group manager in the device selector according to the device identifiers in the sharing group. The scope of the device group managed by the module, the scope of the equipment group includes all the equipment in the sharing group, and the equipment within the scope of the equipment group is determined as the candidate equipment.

Step 1805, if the sharing group contains the user ID, the interaction participating device acquires at least one device ID corresponding to the user ID through the application manager, and determines the device represented by the device ID as a candidate interaction device.

In a possible implementation, the members of the sharing group are users, the user ID is used to represent the user account information, the device ID is used to represent the corresponding device information under the user account, and the number of devices under the user account can be one or more , different devices correspond to different device IDs.

In this embodiment of the application, the application manager in the interactive participating device queries the user management and device management on the server side for the list of devices under the user account corresponding to the user ID through the user ID. Further, the application manager configures the device group range managed by the application device group management submodule in the device selector. The device group range is a list of devices under all user accounts in the sharing group, and the device list includes devices under all user accounts in the sharing group. All devices, and determine all devices in the device list as candidate interaction devices.

In step 1806, the interaction participating device acquires the device selection policy of the target application; through the device selector, a candidate interaction device conforming to the device selection policy is determined as the target interaction device.

For step 1806, refer to step 1305, which will not be repeated in this embodiment of the present application.

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

For step 1807, refer to step 1306, which will not be repeated in this embodiment of the present application.

Step 1808, the interaction participant device provides the target interaction resource to the target interaction device.

Step 1809, the interaction participating device invokes the target interaction resource on the target interaction device through the target application.

From step 1808 to step 1809, since the devices in the shared group can call the resources of all devices, the interaction participating device can provide the target interaction resource to the target interaction device, and at the same time, the interaction participating device can also call the target interaction resource at the target interaction device through the target application. resource.

Exemplarily, as shown in Figure 20, take the collaborative drawing board application as the target application as an example, take the application manager as the super application, the resource interaction initiating device as the sharing group owner, and the interaction participating device as the sharing group member as an example to interact with the shared resources. Be explained.

The user 2007 clicks the start button 2009 on the application details page 2003 of the collaborative drawing board application of the resource interaction initiating device 2001, and the resource interaction initiating device 2001 receives the user 2007's trigger operation on the starting button 2009, and displays the operation interface 2004 of the collaborative drawing board application. The user 2008 clicks the start button 2010 on the application details page 2005 of the collaborative drawing board application of the interactive participating device 2002, and the interactive participating device 2002 receives the trigger operation of the starting button 2010 by the user 2008, and displays the operation interface 2006 of the collaborative drawing board application. Since the resource interaction initiating device 2001 and the interaction participating device 2002 are in a shared group, the resource interaction initiating device 2001 and the interaction participating device 2002 can call each other's drawing data synchronization service, that is, the resource interaction initiating device 2001 and the interactive participating device The content of the collaborative sketchpad application on the device 2002 can be synchronized with each other in real time. For example, the operation interface 2004 of the collaborative sketchpad application of the resource interaction initiating device 2001 can display the content of the collaborative sketchpad application of the interactive participating device 2002, and at the same time, the content of the collaborative sketchpad application of the interactive participating device 2002 The operation interface 2006 can also display the content of the resource interaction initiating device 2001 in collaboration with the sketchpad application.

Exemplarily, as shown in Figure 21, which shows a schematic diagram of the principle of device-level shared resource interaction, the target application is the photo album application, mobile phone A is the sharing group owner, and mobile phone B and mobile phone C are sharing members. group as an example. Since mobile phone A, mobile phone B, and mobile phone C are all in a shared group, mobile phone A, mobile phone B, and mobile phone C can call each other's resources. The following only uses mobile phone B to call the resources of mobile phone A and mobile phone C as an example. .

Mobile phone A sends a sharing group creation request to the sharing group management 2108 on the server side through the first application manager 2101 and creates a sharing group. The sharing group owner of the sharing group is mobile phone A. Resource interaction data identified by the sharing group. Mobile phone B and mobile phone C obtain resource interaction data, and determine the target application as the photo album application based on the target application identification 2106, join the sharing group based on the sharing group identification, mobile phone B and mobile phone C, and obtain the device list under the sharing group from the sharing group management 2108, At this time, the device list in the sharing group management 2108 includes mobile phone A, mobile phone B and mobile phone C. Taking mobile phone B calling the resources of members in the sharing group as an example, mobile phone B obtains the device list of the current sharing group from the sharing group management 2108 through the second application manager 2102, and uses the device group management submodule in the device selector 2103 The scope of the device group is set to the device list of the sharing group, and at this time, all the devices on the device list of the sharing group, that is, mobile phone A, mobile phone B, and mobile phone C are candidate devices. Based on the device selection strategy of the user in the device selection interface of the photo album application 2106 is to select all devices, the candidate devices mobile phone A, mobile phone B, and mobile phone C are determined as target interactive devices. Further, the target resource gateway addresses of the target interactive devices mobile phone A, mobile phone B, and mobile phone C are obtained from the resource gateway management 2109 through the device selector 2103 , and the target resource gateway addresses are fed back to the album application 2106 . 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 the photo resources in mobile phone A, mobile phone B, and mobile phone C. In addition, mobile phone B also provides mobile phone A and mobile phone C with photo resources corresponding to the photo album application. In addition, it should be noted that any mobile phone in the sharing group can view the photos in all mobile phones, namely mobile phone A, mobile phone B, and mobile phone C, by opening the photo album application.

Exemplarily, as shown in 22, which shows a schematic diagram of the principle of user-level shared resource interaction, the target application is an album application, user A is the sharing group owner, and user B and user C are sharing members as an example. . The devices under the account of user A are mobile phone A and mobile phone B, the devices under the account of user B are mobile phone C, and the devices under the account of user D are mobile phone D and mobile phone E. Each mobile phone corresponds to a different device ID. Among them, any mobile phone under the account of user A, user B, and user C in the sharing group can call the resources of mobile phones under other user accounts. The following uses the mobile phone C under the account of user B to call the resources of mobile phones under other user accounts as an example. Be explained.

The mobile phone A under the account of user A sends a sharing group creation request to the sharing group management 2210 on the server side through the first application manager 2201 and creates a sharing group. Resource interaction data including target application ID and sharing group ID. User B and user C obtain resource interaction data, and determine the target application as the photo album application based on the target application identification 2114, identify user B and user C based on the sharing group to join the sharing group, and obtain the user list under the sharing group from the sharing group management 2210, At this time, 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, members of the sharing group, that is, user A, user B, and user C traverse the user IDs in the user list through their respective application managers, query all devices through the user management 2211 and device management 2212 on the server side, and generate a complete device list. 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 user B's account obtains the aforementioned device list through the second application manager 2202, and sets the device group scope device of the application device group management submodule in the device selector 2203 as the aforementioned device list, and at the same time, the device list on the device list All devices mobile phone A, mobile phone B, mobile phone C, mobile phone D and mobile phone E are determined as candidate devices. Based on the device selection strategy of the user in the device selection interface of the photo album application 2206 is to select all devices, the candidate devices mobile phone A, mobile phone B, mobile phone C, mobile phone D and mobile phone E are determined as target interactive devices. Further, obtain target resource gateway addresses of target interactive devices mobile phone A, mobile phone B, mobile phone C, mobile phone D, and mobile phone E from resource gateway management 2213 through device selector 2203 , and feed back the target resource gateway addresses to album application 2206 . 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 photo resources in mobile phones A, mobile phone B, mobile phone C, mobile phone D and mobile phone E. In addition, mobile phone C also provides photo resources corresponding to its own album application to mobile phone A, mobile phone B, mobile phone D and mobile phone E. It should be noted that any mobile phone under the accounts of user A, user B, and user C who are members of the sharing group can open the photo album application to view photos of all mobile phones, namely mobile phone A, mobile phone B, mobile phone C, mobile phone D, and mobile phone E.

In the embodiment of this application, the resource interaction initiating device creates a sharing group, and based on the sharing group identifier, the interaction participating device joins the sharing group. Since the resource interaction initiating device and the interaction participating device belong to the same sharing group, they can call each other's target application corresponding resources, realize resource sharing, and enrich the way of resource interaction.

In addition, in this embodiment of the application, the sharing group owner can dissolve the sharing group. In response to the sharing group disbanding operation, the resource interaction initiating device sends a sharing group disbanding instruction to the server, so that the server disbands the sharing group and deletes the sharing group identifier based on the sharing disbanding instruction. The interactive participating device exits the sharing group through the application manager when receiving the sharing group disbanding message.

In the embodiment of the present application, based on the user's sharing group disbanding operation, the resource interaction initiating device sends a sharing group disbanding instruction to the sharing group manager on the server side, and the sharing group manager disbands the sharing group after receiving the sharing disbanding instruction, and deletes the sharing group ID. The interactive participating device obtains the sharing group dissolution message through the sharing group management, and exits the sharing group through the application manager.

Exemplarily, as shown in FIG. 23 , taking the collaborative drawing board application as an example, the disbanding of the sharing group by the sharing group owner is explained, wherein the resource interaction initiating device is the sharing group owner, and the interaction participating devices are sharing members.

The user 2310 clicks the disband sharing group button 2305 on the collaborative drawing board application sharing group interface 2301, and the resource interaction initiating device 2303 receives the user 2310's trigger operation on the disbanding sharing group button 2305, and a dialog box 2306 pops up on the collaborative drawing board application sharing group interface 2301, and the user 2310 Click the OK button 2307, the resource interaction initiating device 2303 sends a sharing group disbanding instruction to the sharing group management, the sharing group management disbands the sharing group after receiving the disbanding instruction, and deletes the sharing group logo, and the collaborative drawing board application returns to the application details interface 2302. The interaction participating device 2304 receives the disbanding instruction, and exits the sharing 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 call each other's drawing data synchronization service. When they start the collaborative drawing board application, they can only view to the content of your collaborative sketchpad application.

In this embodiment of the application, the sharing group owner can also remove the sharing group members. In response to the removal operation, the resource interaction initiating device sends a removal instruction to the server, so that the server updates the sharing group based on the removal instruction, and synchronizes the update result to the sharing parties in the sharing group. The removal instruction includes the interactive participation to be removed equipment. The interactive participating device exits the sharing group through the application manager when receiving the removal message, where the removal message is used to indicate that the sharing group is removed.

In this embodiment of the application, based on the user's removal operation, the resource interaction initiating device sends a removal instruction to the sharing group management on the server side. The removal instruction includes the device or user to be removed. For example, the device to be removed is The interactive participating device, that is, the removal instruction includes the interactive participating device to be removed. After the sharing group management receives the removal instruction, remove the device to be removed from the device or user list of the sharing management group, update the device list or user list at the same time, and synchronize the updated results to all members of the sharing group . The interactive participating device obtains the removal message through the sharing group management, and exits the sharing group through the application processor.

Exemplarily, as shown in Figure 24, taking the collaborative drawing board application as the target application as an example, the removal of shared members by the sharing group owner is described, where the resource interaction initiating device is the sharing group owner, and the interactive participating device is the shared member.

The user 2409 clicks the user kick button 2408 on the collaborative drawing board application sharing group interface 2403, and the resource interaction initiating device 2401 receives the trigger operation of the user 2409 on the user kicking button 2408, and a dialog box 2404 pops up on the collaborative drawing board application sharing group interface 2403, and the user 2409 Click the OK button 2405, the resource interaction initiating device 2401 sends a removal instruction to the sharing group management, the removal instruction includes the device to be removed, that is, the interactive participating device, and the sharing group management will add it to the device list after receiving the removal instruction Remove the participating devices and synchronize the updated device list to other members of the sharing group. At the same time, the sharing group interface 2403 is used to update the members of the sharing group in collaboration with the drawing board. The interaction participating 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 call each other's drawing data synchronization service. When they start the collaborative drawing board application, they can only view Apply the content to your own collaborative sketchpad.

In this embodiment of the application, sharing members may also voluntarily withdraw from the sharing group. In response to the exit operation, the interactive participating device exits the sharing group through the application manager, and sends an exit message to the server, and the server is used to update the sharing group based on the exit message, and synchronize the update 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 an interaction participating device that actively exits the sharing group.

In this embodiment of the application, based on the user's exit operation, the interactive participating device exits the sharing group through the application manager, and sends an exit message to the sharing group management on the server side. After receiving the exit message, the sharing group management removes the interactive participating device from the sharing group Delete from the device list managed by the group, update the device list at the same time, and synchronize the updated results to all members of the sharing group. The resource interaction initiating device receives the exit message sent by the interaction participating device through the sharing group management.

Exemplarily, as shown in FIG. 25 , taking the collaborative drawing board application as an example, the sharing member withdraws from the sharing group is described, wherein the resource interaction initiating device is the sharing group owner, and the interaction participating device is the sharing member quitting the sharing group.

The user 2510 clicks the exit sharing group button 2509 on the collaborative drawing board application sharing group interface 2503, and the interactive participating device 2502 receives the user 2510's trigger operation on the exit sharing group button 2509, and a dialog box 2504 pops up on the collaborative drawing board application sharing group interface 2503, and the user 2510 Click the OK button 2505, and the interactive participating device 2502 exits the sharing group through the application manager, and sends an exit message to the sharing group management. The list is synchronized to other members of the sharing group. At the same time, the collaborative drawing board application of the interactive participation device 2502 returns to the application details interface 2506 . The resource interaction initiating device 2501 receives the exit message sent by the interaction participating device 2502 through sharing 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 each other's drawing data synchronization service. When they start the collaborative drawing board application, they can only view Apply the content to your own collaborative sketchpad.

The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

Please refer to FIG. 26, which shows a structural block diagram of a resource interaction device provided by an exemplary embodiment of the present application, and the device includes:

The acquisition module 2601 is configured to acquire resource interaction data, the resource interaction data is generated by the resource interaction initiating device when receiving a resource interaction trigger operation for the target application, and the resource interaction trigger operation includes at least a sharing operation and a sharing operation A sort of;

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

The invoking module 2603 is used for invoking the target interaction resources on the target interaction device through the target application.

Optionally, the determining module 2602 includes:

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

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

Optionally, the second determining unit is configured to:

Based on the sharing party identifier, the target interaction device is determined by the application manager and the device selector.

Optionally, the second determining unit is further configured to:

If the sharing party ID is a device ID, the application manager determines the device represented by the device ID as a candidate interactive device; or,

When the sharing party ID is a user ID, at least one device ID corresponding to the user ID is acquired through the application manager, and the device represented by the device ID is determined as a candidate interactive device;

The target interaction device is determined from the candidate interaction devices by the device selector.

Optionally, the second determining unit is further configured to:

Obtaining a device selection policy of the target application; using the device selector, determining the candidate interaction device conforming to the device selection policy as the target interaction device; or,

Displaying a device selection list based on the candidate interaction devices; determining the candidate interaction device selected in the device selection list as the target interaction device through the device selector.

Optionally, the calling module 2603 is configured to:

Based on the sharing instance identifier, the target interaction resource is obtained from the target interaction device through the target application, and the target interaction device is used to verify the authority of the sharing instance identifier, and The target interaction resource is provided when authorization verification is passed.

Optionally, the second determining unit is further configured to:

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

Optionally, the device also includes:

A providing module, configured to provide the target interaction resource to the target interaction device.

Optionally, the second determining unit is further configured to:

In the case that the sharing group contains a device identifier, the application manager determines the device represented by the device identifier as the candidate interaction device;

If the sharing group includes the user identifier, at least one device identifier corresponding to the user identifier is acquired through the application manager, and the device represented by the device identifier is determined as the candidate interaction device.

Optionally, the second determining unit is further configured to:

Optionally, the device also includes:

A first exit module, configured to, in response to an exit operation, exit the sharing group through the application manager, and send an exit message to a server, and the server is used to update the sharing group based on the exit message, and update The result is synchronized to the target interaction device;

A second exit module, configured to exit the sharing group through the application manager when a sharing group disbandment message is received;

A third exit module, configured to exit the sharing group through the application manager when a removal message is received, where the removal message is used to indicate that the sharing group is removed.

Optionally, call module 2603 for:

Obtain a target resource gateway address of the target interactive device based on the device identifier 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 in a management device resource call;

Optionally, the obtaining module 2601 is configured to:

Obtaining the resource interaction data by parsing the graphics code; or,

Obtaining the resource interaction data by parsing the interaction link; or,

The resource interaction data is received through near field communication.

Please refer to FIG. 27, which shows a structural block diagram of a resource interaction device provided by an exemplary embodiment of the present application, and the device includes:

The first generation module 2701 is configured to generate resource interaction data in response to a resource interaction trigger operation on the target application;

The providing module 2702 is configured to provide a target interaction resource to the interaction participation device in response to a resource invocation request of the interaction participation device, and the resource invocation request is determined by the interaction participation device based on the resource interaction data to determine a target application and a target After interacting with the device, it is sent through the target application.

Optionally, the generating module 2701 includes:

a generating unit, configured to generate the resource interaction data through an application manager in response to a resource interaction trigger operation on the target application, and the application manager is used to manage resource interaction of different applications;

Optionally, the providing module 2702 includes:

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

Optionally, the generating unit is configured to:

In response to the sharing operation on the target application, the application manager generates the resource interaction data including the target application identifier and the sharing party identifier.

Optionally, the generating unit is also used for:

In response to the device-level sharing operation on the target application, generating the resource interaction data including the target application identifier and the device identifier through the application manager;

In response to a user-level sharing operation on the target application, the resource interaction data including the target application identifier and a user identifier is generated by the application manager, and the user identifier is used to represent a user corresponding to the sharing party.

Optionally, the providing unit is used for:

In response to the resource invocation request of the interaction participating device, perform permission verification on the sharing instance identifier included in the resource invocation request;

In the case that the shared instance identifier passes the authorization check, the target interaction resource is provided to the interaction participating device.

Optionally, the device also includes:

Remove modules for:

Optionally, the generating unit is also used for:

In response to the sharing operation on the target application, generating the resource interaction data including the target application identifier and the sharing group identifier through the application manager;

Optionally, the device also includes:

A calling module, configured to call the target interaction resource at the interaction participating device through the target application.

Optionally, the device also includes:

The first sending module is used for:

In response to the device-level sharing operation on the target application, sending a first sharing group creation request to a server, where the first sharing group creation request includes a device identifier, and the server is configured to create a request based on the first sharing group Create a sharing group consisting of devices;

The second sending module is used for:

In response to the user-level sharing operation on the target application, sending a second sharing group creation request to the server, where the second sharing group creation request includes a user identifier, and the server is configured to create a second sharing group based on the second sharing group creation request Create a sharing group consisting of users.

Optionally, the device also includes:

The third sending module is used for:

In response to the sharing group disbanding operation, sending a sharing group disbanding instruction to the server, so that the server disbands the sharing group based on the sharing group disbanding instruction, and deletes the sharing group identifier.

Optionally, the device also includes:

The fourth sending module is used for:

In response to the removal operation, send a removal instruction to the server, so that the server updates the sharing group based on the removal instruction, and synchronizes the update result to the sharing parties in the sharing group, and the removal instruction includes The interactive participating device to be removed.

Optionally, the device also includes:

Receiver module for:

An exit message sent by the server is received, and the exit message is triggered by an interactive participating device that actively exits the sharing group.

Optionally, the device also includes:

Update modules for:

When the gateway address of the resource gateway is updated, send a gateway address update message to the server, so that the server will synchronize the updated gateway address to the device selector of other devices, and the device selector stores the device identifier The mapping relationship with the gateway address.

Optionally, the device also includes:

Second build module for:

generating a graphical code based on said resource interaction data; or,

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

The resource interaction data is sent by means of near field communication.

It should be noted that the device provided by the above-mentioned embodiment is only illustrated by the division of the above-mentioned functional modules. In practical applications, the above-mentioned function distribution can be completed by different functional modules according to the needs, that is, the internal structure of the device is divided into Different functional modules to complete all or part of the functions described above. In addition, the device provided by the above embodiment and the method embodiment belong to the same idea, and its specific implementation process is detailed in the method embodiment, and will not be repeated here.

Please refer to FIG. 28 , which shows a structural block diagram of a terminal 2800 provided by an exemplary embodiment of the present application. The terminal 2800 in this application may include one or more of the following components: a processor 2810 and a memory 2820 , where the processor 2810 is electrically connected to the memory 2820 .

Processor 2810 may include one or more processing cores. The processor 2810 uses various interfaces and lines to connect various parts of the entire terminal 2800, and executes the terminal by running or executing instructions, programs, code sets or instruction sets stored in the memory 2820, and calling data stored in the memory 2820. 2800's various functions and processing data. Optionally, the processor 2810 may adopt at least one of Digital Signal Processing (Digital Signal Processing, DSP), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA), and Programmable Logic Array (Programmable Logic Array, PLA). implemented in the form of hardware. The processor 2810 may integrate one or a combination of a CPU, a Graphics Processing Unit (GPU), a modem, and the like. Among them, the CPU mainly processes the operating system, user interface and application programs, etc.; the GPU is used for rendering and drawing the content that needs to be displayed on the touch screen; the modem is used for processing wireless communication. It can be understood that, the above modem may not be integrated into the processor 2810, but implemented by a communication chip alone.

The memory 2820 may include random access memory (Random Access Memory, RAM), and may also include read-only memory (Read-Only Memory, ROM). Optionally, the memory 2820 includes a non-transitory computer-readable storage medium. The memory 2820 may be used to store instructions, programs, codes, 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 and instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.) , the instruction etc. that are used to realize above-mentioned each method embodiment, this operating system can be Andrews (Android) system (comprising the system based on the depth development of Android system), the IOS system developed by Apple Inc. (comprising the system based on the depth development of IOS system) or other systems. The data storage area can also store data created by the terminal 2800 during use (such as phonebook, audio and video data, chat record data) and the like.

In this embodiment of the present application, at least one instruction is stored in the memory 2820, and the at least one instruction is used by the processor 2810 to execute the resource interaction method shown in the above-mentioned embodiments.

In this embodiment of the present application, the terminal 2800 may further include an NFC component, and the NFC component is configured to receive and send an NFC signal, so that the terminal 2800 can process the NFC signal through the processor 2810 .

Optionally, the terminal 2800 further includes a camera for scanning the graphic code, so that the processor can parse the graphic code to obtain resource interaction data.

Optionally, the terminal 2800 may further include a touch display screen, which may be a capacitive touch display screen, and the capacitive touch screen screen is used to receive a user's touch operation on or near it using any suitable object such as a finger or a touch pen. , and display the user interface of each application. The touch screen is usually set on the front panel of the terminal 2800. Touch screens can be designed as full screens, curved screens or special-shaped screens. The touch display screen can also be designed as a combination of a full screen and a curved screen, or a combination of a special-shaped screen and a curved screen, which is not limited in this embodiment of the present application.

In addition, those skilled in the art can understand that the structure of the terminal 2800 shown in the above drawings does not constitute a limitation on the terminal 2800, and the terminal may include more or less components than those shown in the figure, or combine some components, or different component arrangements. For example, the terminal 2800 also includes components such as a radio frequency circuit, a photographing component, a sensor (not including a temperature sensor), an audio circuit, a wireless fidelity (Wireless Fidelity, WiFi) component, a power supply, and a Bluetooth component, which will not be repeated here.

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

According to one aspect of the present application, a computer program product is provided, the computer program product includes computer instructions, the computer instructions are stored in a computer-readable storage medium; the processor of the terminal reads the computer instructions from the computer-readable storage medium The processor executes the computer instruction, so that the terminal executes the resource interaction method provided in various optional implementation manners of the foregoing aspect.

Other embodiments of the present application will be readily 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 modification, use or adaptation of the application, these modifications, uses or adaptations follow the general principles of the application and include common knowledge or conventional technical means in the technical field not disclosed in the application . The specification and examples are to be considered exemplary only, with a true scope and spirit of the application indicated by the following claims.

It should be understood that the present application is not limited to the precise constructions which have been described above and shown in the accompanying drawings, and 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

A resource interaction method, the method comprising:

Acquiring resource interaction data, the resource interaction data is generated by the resource interaction initiating device when receiving a resource interaction trigger operation for the target application, the resource interaction trigger operation includes at least one of a sharing operation and a sharing operation;

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

A target interaction resource at the target interaction device is invoked by the target application.
The method according to claim 1, wherein said determining the target application and the target interaction device based on the resource interaction data comprises:

Based on the resource interaction data, an application manager is used to determine the target application and start the target application, and the application manager is used to manage resource interaction of different applications;

Based on the resource interaction data, the target interaction device is determined by the application manager and the device selector.
The method according to claim 2, wherein, when the resource interaction trigger 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:

Based on the sharing party identifier, the target interaction device is determined by the application manager and the device selector.
The method according to claim 3, wherein the determining the target interaction device through the application manager and the device selector based on the sharing party identifier comprises:

If the sharing party ID is a device ID, the application manager determines the device represented by the device ID as a candidate interactive device; or,

When the sharing party ID is a user ID, at least one device ID corresponding to the user ID is acquired through the application manager, and the device represented by the device ID is determined as a candidate interactive device;

The target interaction device is determined from the candidate interaction devices by the device selector.
The method according to claim 4, wherein said determining the target interaction device from the candidate interaction devices by the device selector comprises:

Obtaining a device selection policy of the target application; using the device selector, determining the candidate interaction device conforming to the device selection policy as the target interaction device; or,

Displaying a device selection list based on the candidate interaction devices; determining the candidate interaction device selected in the device selection list as the target interaction device through the device selector.
The method according to claim 3, wherein the resource interaction data further includes a sharing instance identifier;

The invoking the target interaction resource at the target interaction device through the target application includes:

Based on the sharing instance identifier, the target application invokes the target interaction resource at the target interaction device, and the target interaction device is used to perform permission verification on the sharing instance identifier, and The target interaction resource is provided when authorization verification is passed.
The method according to claim 2, wherein, when the resource interaction trigger operation is a sharing operation, the resource interaction data includes a target application identifier and a sharing group identifier;

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

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

The method also includes:

The target interaction resource is provided to the target interaction device.
The method according to claim 7, wherein said determining said target interaction device by said application manager and said device selector based on said sharing group identity comprises:

join the sharing group represented by the sharing group identifier through the application manager;

determining, by the application manager, candidate interactive devices in the sharing group;

The target interaction device is determined from the candidate interaction devices by the device selector.
The method according to claim 8, wherein the determining the candidate interactive devices in the sharing group by the application manager comprises:

In the case that the sharing group contains a device identifier, the application manager determines the device represented by the device identifier as the candidate interaction device; or,

In the case that the sharing group contains the user identifier, at least one device identifier corresponding to the user identifier is acquired through the application manager, and the device represented by the device identifier is determined as the candidate interactive device.
The method according to claim 8, wherein said determining the target interaction device from the candidate interaction devices by the device selector comprises:

Obtaining a device selection policy of the target application; using the device selector, determining the candidate interaction device conforming to the device selection policy as the target interaction device; or,

Displaying a device selection list based on the candidate interaction devices; determining the candidate interaction device selected in the device selection list as the target interaction device through the device selector.
The method according to claim 8, wherein the method further comprises:

In response to an exit operation, exiting the sharing group through the application manager, and sending an exit message to a server, the server is configured to update the sharing group based on the exit message, and synchronize the update result to the target interaction equipment;

Exiting the sharing group through the application manager when receiving the sharing group disbanding message;

Exiting the sharing group through the application manager when receiving a remove message, where the remove message is used to indicate that the sharing group is removed.
The method according to any one of claims 1 to 11, wherein the invoking the target interaction resource at the target interaction device through the target application comprises:

Obtain a target resource gateway address of the target interactive device based on the device identifier 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 in a management device resource call;

Based on the address of the target resource gateway, the target application accesses the target resource gateway to obtain the target interaction resource.
The method according to any one of claims 1 to 11, wherein said acquiring resource interaction data comprises:

Obtaining the resource interaction data by parsing the graphics code; or,

Obtaining the resource interaction data by parsing the interaction link; or,

The resource interaction data is received through near field communication.
The method according to any one of claims 1 to 11, wherein the target interaction resources include at least one of file resources, hardware resources and service resources.
A resource interaction method, the method comprising:

generating resource interaction data in response to a resource interaction trigger operation on the target application;

Responding to the resource invocation request of the interaction participation device, providing the interaction participation device with a target interaction resource, the resource invocation request is determined by the interaction participation device based on the resource interaction data to determine the target application and the target interaction device, through the sent by the target application.
The method according to claim 15, wherein the generating resource interaction data in response to a resource interaction trigger operation on the target application comprises:

In response to a resource interaction trigger operation on the target application, generating the resource interaction data through an application manager, the application manager is used to manage resource interaction of different applications;

The responding to the resource call request of the interactive participating device, providing the target interactive resource to the interactive participating device includes:

In response to the resource invocation request of the interaction participating device, the target interaction resource is provided to the interaction participating device through a resource gateway, and the resource gateway is used to manage resource invocation in the device.
The method according to claim 16, wherein the generating the resource interaction data by an application manager in response to the resource interaction trigger operation on the target application comprises:

In response to the sharing operation on the target application, the application manager generates the resource interaction data including the target application identifier and the sharing party identifier.
The method according to claim 17, wherein in response to the sharing operation on the target application, generating the resource interaction data including the target application identifier and the sharing party identifier through the application manager includes:

In response to the device-level sharing operation on the target application, generating the resource interaction data including the target application identifier and the device identifier through the application manager;

In response to the user-level sharing operation on the target application, the application manager generates the resource interaction data including the target application identifier and a user identifier, and the user identifier is used to represent a user corresponding to the sharing party.
The method according to claim 18, wherein the resource interaction data further includes a sharing instance identifier;

The responding to the resource call request of the interactive participating device, providing the target interactive resource to the interactive participating device includes:

In response to the resource invocation request of the interaction participating device, perform permission verification on the sharing instance identifier contained in the resource invocation request;

In the case that the shared instance identifier passes the authorization check, the target interaction resource is provided to the interaction participating device.
The method according to claim 19, wherein said method further comprises:

In response to a sharing cancellation operation on the target application, the sharing instance identifier is deleted.
The method according to claim 16, wherein the generating the resource interaction data by an application manager in response to the resource interaction trigger operation on the target application comprises:

In response to the sharing operation on the target application, generating the resource interaction data including the target application identifier and the sharing group identifier through the application manager;

The method also includes:

Invoking the target interaction resource at the interaction participating device through the target application.
The method according to claim 21, wherein said method further comprises:

In response to the device-level sharing operation on the target application, sending a first sharing group creation request to a server, where the first sharing group creation request includes a device identifier, and the server is configured to create a request based on the first sharing group Create a sharing group consisting of devices;

In response to the user-level sharing operation on the target application, sending a second sharing group creation request to the server, where the second sharing group creation request includes a user identifier, and the server is configured to create a second sharing group based on the second sharing group creation request Create a sharing group consisting of users.
The method according to claim 21, wherein said method further comprises:

In response to the sharing group disbanding operation, sending a sharing group disbanding instruction to the server, so that the server disbands the sharing group based on the sharing group disbanding instruction, and deletes the sharing group identifier.
The method according to claim 21, wherein said method further comprises:

In response to the removal operation, send a removal instruction to the server, so that the server updates the sharing group based on the removal instruction, and synchronizes the update result to the sharing parties in the sharing group, and the removal instruction includes The interactive participating device to be removed.
The method according to claim 21, wherein said method further comprises:

An exit message sent by the server is received, and the exit message is triggered by an interactive participating device that actively exits the sharing group.
The method according to claim 16, wherein the method further comprises:

When the gateway address of the resource gateway is updated, send a gateway address update message to the server, so that the server will synchronize the updated gateway address to the device selector of other devices, and the device selector stores the device identifier The mapping relationship with the gateway address.
The method according to any one of claims 15 to 26, wherein, after generating the resource interaction data, the method comprises:

generating a graphical code based on the resource interaction data; or,

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

The resource interaction data is sent by means of near field communication.
The method according to any one of claims 15 to 26, wherein the target interaction resources include at least one of file resources, hardware resources and service resources.
A resource interaction device, the device comprising:

An acquisition module, configured to acquire resource interaction data, the resource interaction data is generated by the resource interaction initiating device when it receives a resource interaction trigger operation for the target application, and the resource interaction trigger operation includes at least one of a sharing operation and a sharing operation kind;

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

A calling module, configured to use the target application to call the target interaction resource on the target interaction device.
A resource interaction device, the device comprising:

A first generation module, configured to generate resource interaction data in response to a resource interaction trigger operation on the target application;

A providing module, configured to provide a target interaction resource to the interaction participation device in response to a resource invocation request of the interaction participation device, and the resource invocation request is determined by the interaction participation device based on the resource interaction data to determine a target application and a target interaction device, sent through the target application.
A terminal, the terminal includes a processor and a memory, at least one program is stored in the memory, and the at least one program is loaded and executed by the processor to implement the resource according to any one of claims 1 to 14 An interaction method, or, implement the resource interaction method as claimed in any one of claims 15 to 28.
A computer-readable storage medium, at least one program is stored in the readable storage medium, and the at least one program is loaded and executed by a processor to implement the resource interaction method according to any one of claims 1 to 14, or Realizing the resource interaction method as claimed in any one of claims 15 to 28.
A computer program product, the computer program product includes computer instructions, the computer instructions are stored in a computer-readable storage medium; the processor of the terminal reads the computer instructions from the computer-readable storage medium, and the processing The computer executes the computer instructions, so that the terminal executes the resource interaction method according to any one of claims 1 to 14, or implements the resource interaction method according to any one of claims 15 to 28.