Task execution method, system and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a task execution method, system and device, electronic equipment and a storage medium, and relates to the technical field of near field communication. The method is applied to a first user terminal, and comprises the following steps: based on a near field communication mode, reading label data stored in a near field communication NFC label of target function equipment; wherein the label data comprises an application identifier and an equipment identifier of the target function equipment; under the condition that the specified application program represented by the read application identifier runs, determining a first account currently logging in the specified application program; and if it is determined that the first account has the permission to use the target function equipment based on the obtained equipment identifier and the read tag data contains task information, executing a task needing to be executed by the first account in tasks represented by the task information through the specified application program. In this way, the task execution efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of near field communication technology, and in particular to a task execution method, system, device, electronic device and storage medium. Background Art

[0002] With the continuous development of communication technology, certain devices with specific functions (referred to as functional devices) such as cameras, smart door locks, and network-attached storage devices (NAS) can now be remotely controlled and interconnected through IoT technology. Currently, the owner of a functional device can use a user terminal installed with an application (APP) to communicate with the functional device to complete a specific task. For example, if the functional device is a NAS device, the user terminal can use the application to transmit data between the device and the NAS.

[0003] However, every time a task needs to be performed, the owner of the functional device needs to manually open the application in the terminal device, and then enter the specified interface in the application to set and select the task to be performed. The above process involves many user operation steps, resulting in low efficiency in task execution. Summary of the Invention

[0004] The purpose of the embodiments of the present application is to provide a task execution method, system, device, electronic device, and storage medium to improve the efficiency of task execution. The specific technical solutions are as follows:

[0005] In a first aspect of an embodiment of the present application, a task execution method is provided, which is applied to a first user terminal. The method includes:

[0006] Reading tag data stored in an NFC (Near Field Communication) tag of a target functional device based on a near field communication method; wherein the tag data includes an application identifier and a device identifier of the target functional device;

[0007] When the designated application represented by the read application identifier is running, determining a first account currently logged into the designated application;

[0008] If it is determined based on the obtained device identification that the first account has the authority to use the target functional device, and the read tag data contains task information, the task required to be performed by the first account in the task represented by the task information is executed through the designated application.

[0009] In some embodiments, the method further comprises:

[0010] When running the designated application represented by the read application identifier, if it is determined based on the obtained device identifier that the first account has permission to use the target functional device, and the read tag data does not contain task information, displaying the task setting interface through the designated application;

[0011] Acquire task information of a task indicated by a task setting operation triggered by a user in the task setting interface;

[0012] Based on the near field communication method, the acquired task information is written into the NFC tag.

[0013] In some embodiments, if it is determined based on the acquired device identifier that the first account has permission to use the target functional device, and the read tag data includes task information, before executing, through the designated application, the task required to be executed by the first account in the task represented by the task information, the method further includes:

[0014] Sending a permission query request carrying the device identification of the target functional device and the account information of the first account to the server, so that the server determines whether the first account has the permission to use the target functional device and notifies the first user terminal.

[0015] In some embodiments, the method further comprises:

[0016] If the first account has permission to use the target functional device, displaying the homepage through the designated application;

[0017] If the first account does not have the permission to use the target functional device, an authorization request interface is displayed through the designated application; in response to the authorization request operation triggered by the user in the authorization request interface, an authorization request instruction carrying the device identification of the target functional device and the account information of the first account is sent to the server, so that the server forwards the authorization request instruction to the second user terminal logged in by the owner of the target functional device, and after receiving the authorization permission instruction returned by the second user terminal, it is recorded that the first account has the permission to use the target functional device.

[0018] In some embodiments, the sending a permission query request carrying the device identifier of the target functional device and the account information of the first account to the server, so that the server determines whether the first account has permission to use the target functional device and notifies the first user terminal, includes:

[0019] sending a permission query request carrying the device identifier of the target functional device and the account information of the first account to a server, so that the server determines whether the first account has permission to use the target functional device if the target functional device is currently bound, and notifies the first user terminal of the information; and sending a binding query instruction to the first user terminal if the target functional device is not currently bound;

[0020] The method further comprises:

[0021] When the binding inquiry instruction is received, a binding inquiry interface is displayed through the designated application; in response to the binding confirmation operation triggered by the user in the binding inquiry interface, a binding request carrying the device identification of the target functional device and the account information of the first account is sent to the server, so that the server records that the target functional device is currently bound to the first account.

[0022] In some embodiments, before determining the first account currently logged into the designated application, the method further includes:

[0023] Determining whether the designated application represented by the read application identifier is currently installed;

[0024] If the designated application is currently installed and is not running, the designated application is run.

[0025] In some embodiments, the tag data further includes: a download address of the designated application;

[0026] The method further comprises:

[0027] If the specified application is not currently installed, jump to the download interface of the specified application according to the download address; in response to a download operation triggered by the user in the download interface, download and install the specified application, and run the specified application after the installation is complete;

[0028] or,

[0029] If the designated application is not currently installed and the designated application belongs to the installation whitelist of the first user terminal, the designated application is downloaded and installed according to the download address, and the designated application is run after the installation is complete.

[0030] In some embodiments, when running a designated application represented by the read application identifier, determining the first account currently logged into the designated application includes:

[0031] When running the specified application represented by the read application identifier, determining whether there is a currently logged-in account;

[0032] If there is a currently logged-in account, determining the first account currently logged into the designated application;

[0033] If there is no currently logged-in account, a login interface is displayed through the designated application, and if the login is successful, the first account currently logged into the designated application is determined.

[0034] A second aspect of the embodiments of the present application provides a task execution method, applied to a server, the method comprising:

[0035] Upon receiving a permission query request sent by a first user terminal and carrying the device identifier of a target functional device and the account information of a first account, determining whether the first account has permission to use the target functional device; wherein the permission query request is sent by the first user terminal after reading tag data stored in a near-field communication (NFC) tag of the target functional device based on near-field communication and determining the first account currently logged into a designated application represented by an application identifier contained in the obtained tag data;

[0036] Notify the first user terminal of the judgment result indicating whether the first account has the authority to use the target functional device, so that when the first account has the authority to use the target functional device and the read tag data contains task information, the first user terminal executes the task required to be executed by the first account in the task represented by the task information through the designated application.

[0037] In some embodiments, the method further comprises:

[0038] Upon receiving the authorization request instruction sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, forwarding the authorization request instruction to the second user terminal logged in by the owner of the target functional device;

[0039] After receiving the authorization permission instruction returned by the second user terminal, it is recorded that the first account has the authority to use the target functional device.

[0040] In some embodiments, upon receiving a permission query request sent by a first user terminal and carrying a device identifier of a target functional device and account information of a first account, determining whether the first account has permission to use the target functional device includes:

[0041] Upon receiving a permission query request sent by a first user terminal and carrying the device identification of a target functional device and the account information of a first account, if the target functional device is currently bound, determining whether the first account has permission to use the target functional device;

[0042] The method further comprises:

[0043] Upon receiving a permission query request sent by a first user terminal and carrying a device identifier of a target functional device and account information of a first account, if the target functional device is not currently bound, sending a binding query instruction to the first user terminal;

[0044] When receiving the binding request sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, it is recorded that the target functional device is currently bound to the first account.

[0045] According to a third aspect of an embodiment of the present application, a task execution system is provided, the task execution system comprising: a first user terminal, and a server;

[0046] The first user terminal is used to implement any one of the task execution methods described in the first aspect above;

[0047] The server is used to implement any task execution method described in the second aspect above.

[0048] According to a fourth aspect of the present application, a task execution device is provided, which is applied to a first user terminal. The device includes:

[0049] A tag data reading module is used to read the tag data stored in the NFC tag of the target functional device based on the near field communication method; wherein the tag data includes the application identifier and the device identifier of the target functional device;

[0050] an account determination module, configured to determine, when running a designated application represented by the read application identifier, a first account currently logged into the designated application;

[0051] A task execution module is used to execute the task required to be performed by the first account in the task represented by the task information through the designated application if it is determined based on the obtained device identification that the first account has the authority to use the target functional device and the read tag data contains task information.

[0052] In some embodiments, the apparatus further comprises:

[0053] a task setting module configured to, when running a designated application represented by the read application identifier, display a task setting interface through the designated application if it is determined based on the obtained device identifier that the first account has permission to use the target functional device, and the read tag data does not contain task information;

[0054] A task information acquisition module, configured to acquire task information of a task indicated by a task setting operation triggered by a user in the task setting interface;

[0055] The task information writing module is used to write the acquired task information into the NFC tag based on the near field communication method.

[0056] In some embodiments, the apparatus further comprises:

[0057] A permission query request sending module is used to send a permission query request carrying the device identification of the target functional device and the account information of the first account to the server before executing the task required to be performed by the first account in the task represented by the task information through the designated application if it is determined based on the obtained device identification that the first account has the permission to use the target functional device, and the read tag data contains task information, so that the server can determine whether the first account has the permission to use the target functional device and notify the first user terminal.

[0058] In some embodiments, the apparatus further comprises:

[0059] a first display module, configured to display a homepage via the designated application if the first account has permission to use the target functional device;

[0060] The second display module is used to display an authorization request interface through the designated application if the first account does not have the authority to use the target functional device; in response to the authorization request operation triggered by the user in the authorization request interface, send an authorization request instruction carrying the device identification of the target functional device and the account information of the first account to the server, so that the server forwards the authorization request instruction to the second user terminal logged in by the owner of the target functional device, and after receiving the authorization permission instruction returned by the second user terminal, record that the first account has the authority to use the target functional device.

[0061] In some embodiments, the permission query request sending module is specifically configured to:

[0062] sending a permission query request carrying the device identifier of the target functional device and the account information of the first account to a server, so that the server determines whether the first account has permission to use the target functional device if the target functional device is currently bound, and notifies the first user terminal of the information; and sending a binding query instruction to the first user terminal if the target functional device is not currently bound;

[0063] The device further comprises:

[0064] The third display module is used to display a binding inquiry interface through the designated application upon receiving the binding inquiry instruction; in response to a binding confirmation operation triggered by the user in the binding inquiry interface, send a binding request carrying the device identification of the target functional device and the account information of the first account to the server, so that the server records that the target functional device is currently bound to the first account.

[0065] In some embodiments, the apparatus further comprises:

[0066] An installation determination module is configured to determine whether the designated application represented by the read application identifier is currently installed before determining the first account currently logged into the designated application;

[0067] The running module is used to run the specified application program when the specified application program is currently installed and is not running.

[0068] In some embodiments, the tag data further includes: a download address of the designated application;

[0069] The device further comprises:

[0070] A download module is used to jump to the download interface of the specified application according to the download address when the specified application is not currently installed; download and install the specified application in response to a download operation triggered by the user in the download interface, and run the specified application after the installation is complete; or, if the specified application is not currently installed and the specified application belongs to the installation whitelist of the first user terminal, download and install the specified application according to the download address, and run the specified application after the installation is complete.

[0071] In some embodiments, the account determination module is specifically configured to:

[0072] When running the specified application represented by the read application identifier, determining whether there is a currently logged-in account;

[0073] If there is a currently logged-in account, determining the first account currently logged into the designated application;

[0074] If there is no currently logged-in account, a login interface is displayed through the designated application, and if the login is successful, the first account currently logged into the designated application is determined.

[0075] According to a fifth aspect of the present application, a task execution device is provided, which is applied to a server. The device includes:

[0076] a permission query request receiving module, configured to, upon receiving a permission query request sent by a first user terminal and carrying a device identifier of a target functional device and account information of a first account, determine whether the first account has permission to use the target functional device; wherein the permission query request is sent by the first user terminal after reading tag data stored in a near-field communication (NFC) tag of the target functional device based on near-field communication and determining that the first account currently logged into the designated application represented by the application identifier contained in the obtained tag data;

[0077] The first notification module is used to notify the first user terminal of the judgment result indicating whether the first account has the permission to use the target functional device, so that when the first account has the permission to use the target functional device and the read tag data contains task information, the first user terminal executes the task required to be executed by the first account in the task represented by the task information through the designated application.

[0078] In some embodiments, the apparatus further comprises:

[0079] a forwarding module configured to, upon receiving an authorization request instruction sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, forward the authorization request instruction to a second user terminal logged in by the owner of the target functional device;

[0080] The permission recording module is used to record that the first account has the permission to use the target functional device after receiving the authorization permission instruction returned by the second user terminal.

[0081] In some embodiments, the permission query request receiving module is specifically configured to:

[0082] Upon receiving a permission query request sent by a first user terminal and carrying the device identification of a target functional device and the account information of a first account, if the target functional device is currently bound, determining whether the first account has permission to use the target functional device;

[0083] The device further comprises:

[0084] a binding query instruction sending module, configured to, upon receiving a permission query request sent by a first user terminal and carrying a device identifier of a target functional device and account information of a first account, send a binding query instruction to the first user terminal if the target functional device is not currently bound;

[0085] The binding recording module is configured to, upon receiving a binding request sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, record that the target functional device is currently bound to the first account.

[0086] According to a sixth aspect of the embodiments of the present application, an electronic device is provided, including:

[0087] Memory for storing computer programs;

[0088] The processor is used to implement any of the task execution methods described in the first aspect or any of the task execution methods described in the second aspect when executing the program stored in the memory.

[0089] Another aspect of the embodiments of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the task execution method described in any one of the first aspects or the task execution method described in any one of the second aspects.

[0090] In another aspect of the embodiments of the present application, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute any of the task execution methods described in the first aspect or any of the task execution methods described in the second aspect.

[0091] Beneficial effects of the embodiments of the present application:

[0092] Based on the task execution method provided in the embodiment of the present application, the first user terminal can read the tag data stored in the NFC tag of the target functional device based on the near field communication method. Accordingly, the first user terminal can determine whether the specified application represented by the application identifier is currently running based on the application identifier contained in the tag data. In the case of running the specified application, the first account currently logged into the specified application is determined. Furthermore, if the first account has the authority to use the target functional device and the read tag data contains task information, the first user terminal can execute the task required to be executed by the first account in the task represented by the task information through the specified application. In this way, it is possible to automatically read the task information of the task to be executed contained in the tag data of the NFC tag. Under the condition that the account currently logged into the specified application (i.e., the first account) has the authority to use the target functional device, the task required to be executed by the first account in the task represented by the read task information is automatically executed, realizing automation from reading task information to executing tasks. Compared with the process in which the user manually opens the specified application in the terminal device and then enters the specified interface in the specified application to set and select the task to be executed, the user's operation steps during the task execution process can be simplified, and the efficiency of task execution can also be improved.

[0093] Of course, it is not necessary to achieve all the advantages described above at the same time when implementing any product or method of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0094] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0095] Figure 1 A schematic diagram of the structure of a task execution system provided in an embodiment of the present application;

[0096] Figure 2 A first flow chart of the task execution method provided in an embodiment of the present application;

[0097] Figure 3 A second flow chart of the task execution method provided in an embodiment of the present application;

[0098] Figure 4 A schematic diagram of an interface for creating a task through a specified application provided in an embodiment of the present application;

[0099] Figure 5 A schematic diagram of an interface for specifying an application in the process of writing task information to an NFC tag provided in an embodiment of the present application;

[0100] Figure 6 A flowchart of a task setting provided in an embodiment of the present application;

[0101] Figure 7 A schematic diagram of an interface for specifying an application during an authorization request provided in an embodiment of the present application;

[0102] Figure 8 A schematic diagram of an interface displayed on a user terminal of an owner of a functional device provided in an embodiment of the present application;

[0103] Figure 9 A schematic diagram of different interfaces displayed on a user terminal after touching an NFC tag according to an embodiment of the present application;

[0104] Figure 10 A schematic diagram of a process for authorization by an owner of a functional device provided in an embodiment of the present application;

[0105] Figure 11 An interactive sequence diagram of a task execution system provided in an embodiment of the present application;

[0106] Figure 12 A flowchart of a first user terminal applying for authorization provided in an embodiment of the present application;

[0107] Figure 13 A flowchart of a first user terminal performing role determination provided in an embodiment of the present application;

[0108] Figure 14 A flowchart of a first user terminal downloading a specified application provided in an embodiment of the present application;

[0109] Figure 15 A schematic diagram of the overall functions of a task execution system provided in an embodiment of the present application;

[0110] Figure 16 An interaction sequence diagram of another task execution system provided in an embodiment of the present application;

[0111] Figure 17 An interactive architecture diagram of different roles provided in an embodiment of the present application;

[0112] Figure 18 A third flow chart of the task execution method provided in an embodiment of the present application;

[0113] Figure 19 A structural diagram of a task execution device provided in an embodiment of the present application;

[0114] Figure 20 A structural diagram of another task execution device provided in an embodiment of the present application;

[0115] Figure 21 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0116] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field based on this application are within the scope of protection of this application.

[0117] For some functional devices, such as cameras, smart door locks, and network-attached storage devices, their owners can use a user terminal installed with a designated application to communicate with the device to complete designated tasks. However, each time a task is required, the device owner must manually open the designated application on the terminal device, then access the application's designated interface to set up and select the desired task. This process involves numerous steps, resulting in inefficient task execution.

[0118] Functional devices refer to devices with specific functions. For any functional device, the user terminal can use the functions provided by the functional device to perform designated tasks.

[0119] For example, the functional device may be a Network Attached Storage (NAS) device. Accordingly, the network attached storage device (hereinafter referred to as a NAS device or network storage) can communicate with the user terminal via a local area network to provide the user terminal with functions such as data storage and downloading.

[0120] For another example, the functional device may be a camera. Accordingly, the camera may communicate with the user terminal via a local area network, and the user may view the video stream captured by the camera via the user terminal.

[0121] For each functional device, the manufacturer of the functional device may configure at least one NFC tag for the functional device.

[0122] Depending on how NFC tags are configured, they can be categorized as hardware-integrated and standalone. Hardware-integrated NFC tags are physically embedded directly within a functional device or affixed to its surface. Standalone NFC tags are physically separate from the functional device but establish a corresponding relationship with it through a logical association (e.g., the device identifier stored in the tag data).

[0123] The NFC tag of a functional device stores data related to the functional device (tag data).

[0124] The tag data stored in different NFC tags of a functional device may be the same.

[0125] For example, if the functional device is a camera, the tag data of multiple NFC tags of a camera can be the same, and the tag data of each NFC tag includes: the application identifier of the camera, the device identifier of the camera, and task information representing the task of viewing real-time video images. Accordingly, the owner of the camera can place multiple NFC tags in different places (such as home, company, or carry with him / her) so that the owner of the camera can view the real-time video images captured by the camera at any time by touching the tags. The specific process of executing the corresponding task by touching the tags will be described in subsequent embodiments.

[0126] In addition, the tag data stored in different NFC tags of a functional device may also be different.

[0127] For example, assuming that the functional device can be a NAS device, the tag data of multiple NFC tags of a NAS device can be different. For example, for two NFC tags (referred to as NFC tag 1 and NFC tag 2), the tag data of NFC tag 1 and the tag data of NFC tag 2 contain the same application identifier and the device identifier of the NAS device. However, the tag data of NFC tag 1 and the tag data of NFC tag 2 can contain different task information. For example, the task information contained in NFC tag 1 can represent the task of uploading photos from a mobile phone album to storage on the NAS device, while the task information contained in NFC tag 2 can represent the task of downloading specified data from the NAS device.

[0128] The specific contents of the tag data stored in the NFC tag will be described in subsequent embodiments.

[0129] The present application embodiment provides a task execution system, see Figure 1 , Figure 1 This is a schematic diagram of the structure of a task execution system provided in an embodiment of the present application. The task execution system includes: a user terminal 101 and a server 102. The user terminal 101 and the server 102 can communicate with each other. The following describes the interaction process between the user terminal 101 and the server 102 in conjunction with specific embodiments.

[0130] The user terminal 101 is an intelligent electronic device that supports the NFC function, such as a mobile phone or tablet computer that supports the NFC function.

[0131] The embodiment of the present application provides a task execution method, which can be applied to a first user terminal. Figure 2 , Figure 2 This is a flowchart of a first method for executing a task provided in an embodiment of the present application, the method comprising the following steps:

[0132] S201: Reading tag data stored in an NFC tag of a target functional device based on a near field communication method.

[0133] The tag data includes the application identifier and the device identifier of the target functional device.

[0134] S202: When the designated application represented by the read application identifier is running, determine a first account currently logged into the designated application.

[0135] S203: If it is determined based on the acquired device identifier that the first account has the authority to use the target functional device, and the read tag data contains task information, then the task required to be performed by the first account in the task represented by the task information is executed through a designated application.

[0136] Based on the task execution method provided in the embodiment of the present application, the first user terminal can read the tag data stored in the NFC tag of the target functional device based on the near field communication method. Accordingly, the first user terminal can determine whether the specified application represented by the application identifier is currently running based on the application identifier contained in the tag data. In the case of running the specified application, the first account currently logged into the specified application is determined. Furthermore, if the first account has the authority to use the target functional device and the read tag data contains task information, the first user terminal can execute the task required to be executed by the first account in the task represented by the task information through the specified application. In this way, it is possible to automatically read the task information of the task to be executed contained in the tag data of the NFC tag. Under the condition that the account currently logged into the specified application (i.e., the first account) has the authority to use the target functional device, the task required to be executed by the first account in the task represented by the read task information is automatically executed, realizing automation from reading task information to executing tasks. Compared with the process in which the user manually opens the specified application in the terminal device and then enters the specified interface in the specified application to set and select the task to be executed, the user's operation steps during the task execution process can be simplified, and the efficiency of task execution can also be improved.

[0137] The first user terminal refers to a user terminal used by the current user to touch the NFC tag to read the tag data.

[0138] With respect to step S201 , the user may touch the first user terminal to the NFC tag of the target functional device. Accordingly, the first user terminal may read the tag data stored in the NFC tag based on the near field communication method.

[0139] Near-field communication (NFC) is a short-range, high-frequency radio technology. Electronic devices that support NFC can communicate and exchange data with NFC tags within a 13.56MHz radio frequency range, typically within 10cm.

[0140] The target functional device is the functional device that the user currently needs to perform the task.

[0141] In one implementation, the tag data stored in the NFC tag of the target functional device includes: an application identifier and a device identifier of the target functional device. The application identifier represents an application (APP), that is, a designated application.

[0142] The designated application is an application developed by the manufacturer of the target functional device and used to manage the target functional device (such as binding, authorization, task execution, etc.) The specific process of managing the target functional device will be described in subsequent embodiments.

[0143] It's understandable that a single manufacturer might produce multiple functional devices simultaneously. For example, a manufacturer specializing in IoT services might produce cameras, NAS devices, and other functional devices. Accordingly, these multiple functional devices can all be managed within a single, designated application.

[0144] Accordingly, after purchasing the aforementioned functional device, the user can download and install an application (i.e., a designated application) on the first user terminal for managing the functional device. The user can then run the designated application on the first user terminal. Furthermore, the user can log in to the designated application and manage the target functional device (e.g., binding, authorization, executing tasks, etc.).

[0145] It is understandable that the first user terminal may have multiple different applications installed. In order to ensure that the first user terminal can distinguish different applications through the application identifiers of each application, the application identifiers of different applications are also different. For example, the application identifier of an application can be: the name of the application.

[0146] Regarding step S202, when the first user terminal reads the application identifier contained in the tag data stored in the NFC tag, the designated application may be in a running state. For example, if the first user terminal is a mobile phone, the user can first open the designated application in the mobile phone and then touch the NFC tag of the target functional device with the mobile phone.

[0147] Alternatively, when the first user terminal reads the application identifier contained in the tag data stored in the NFC tag, the designated application may also be in a non-running state. Accordingly, the first user terminal can run the designated application represented by the application identifier based on the application identifier contained in the read tag data. For example, taking the first user terminal as a mobile phone, the user can directly touch the NFC tag of the target functional device with the mobile phone without running the designated application in the mobile phone. Accordingly, the mobile phone can automatically open the designated application based on the application identifier contained in the read tag data.

[0148] Accordingly, when the designated application is in a running state, that is, when the designated application is running, the first user terminal can determine the first account currently logged into the designated application.

[0149] In one implementation, the first user terminal may obtain account information of an account (ie, the first account) currently logged into a designated application.

[0150] It is understood that for each user, the user can pre-register an account for logging into a designated application. Accordingly, the server can record the account information of the registered account. Subsequently, the user can log in to the pre-registered account in the designated application to manage the target functional device through the designated application.

[0151] Among them, the account information of an account may include at least one of the following: the account name customized by the user when registering the account, the mobile phone number used by the user when registering the account, and the unique account identifier assigned to the account by the server during the above registration process.

[0152] Regarding step S203, for a functional device, the account bound to the functional device is unique, that is, one functional device is bound to one account. Accordingly, the user to whom the account bound to a functional device belongs is the owner of the functional device.

[0153] A user's account can be bound to multiple functional devices. In other words, a user can be the owner of multiple functional devices simultaneously. The designated application logged into by the owner of a functional device will display the owner's account information and the functional devices bound to that account. Accordingly, the owner of a functional device has permission to use that functional device.

[0154] In one implementation, the owner of a functional device can authorize other users' accounts to use the functional device. Accordingly, users other than the owner whose accounts have permission to use the functional device are referred to as joiners.

[0155] For example, if the target functional device is a camera, and user A is the owner of the camera, user A can install the camera at the entrance of their home. Accordingly, user A can authorize the account of their family member (such as user B) so that user B (the joiner) can also view the video stream captured by the camera in the designated application logged into their own account.

[0156] For another example, let's assume the target functional device is a NAS device. User C is the owner of the NAS device and can install it in the company. Accordingly, User A can authorize the account of another company employee (e.g., User D) so that User D (the joiner) can also upload files to the NAS device for storage or download files needed for work from the NAS device by logging into a designated application with their own account.

[0157] That is, for a target functional device, there may be multiple accounts that have the authority to use the target functional device.

[0158] The tag data stored in the NFC tag of the target functional device also includes task information, wherein the task information may represent multiple tasks or one task.

[0159] In one implementation, for a target functional device, the task information included in the tag data of the NFC tag of the target functional device includes task data of at least one task, wherein the task data of one task can be created and written by any account logged in with permission to use the target functional device.

[0160] The task data for a task includes the account information of the account that created the task. Accordingly, after the user terminal reads the task information contained in the NFC tag data using near-field communication, it can match the account information of the account that created the task, contained in the task data of each task, with the account currently logged into the designated application to determine the task to be performed by that account.

[0161] In another implementation, for a target functional device, the task information included in the tag data of the NFC tag of the target functional device includes task data of at least one task, wherein the task data of one task may be created and written by an account bound to the target functional device.

[0162] In other words, only the account bound to the target functional device can write task information to the NFC tag of the target functional device. User terminals belonging to the specified application logged in to other accounts can read the tag data in the NFC tag, but cannot modify the tag data in the NFC tag.

[0163] If the first account has permission to use the target functional device and the task information represents only one task, the first user terminal may execute the task through a designated application.

[0164] In some embodiments, see Figure 3 , Figure 3 This is a second flowchart of the task execution method provided in an embodiment of the present application.

[0165] exist Figure 2 Based on this, the method also includes:

[0166] S204: When running the designated application represented by the read application identifier, if it is determined based on the obtained device identifier that the first account has permission to use the target functional device, and the read tag data does not contain task information, the task setting interface is displayed through the designated application.

[0167] S205: Acquire task information of the task indicated by the task setting operation triggered by the user in the task setting interface.

[0168] S206: Writing the acquired task information into the NFC tag based on the near field communication method.

[0169] In this embodiment of the present application, the tag data stored in the NFC tag of the target functional device does not contain task information, that is, the NFC tag of the target functional device does not have a task set for the first account to execute. In this case, when the specified application represented by the read application identifier is run, if the first account has permission to use the target functional device, the task setting interface is displayed through the specified application.

[0170] Accordingly, the user can trigger a task setting operation in the task setting interface to create a new task, and write the task information of the created task (ie, the task information of the task indicated by the task setting operation) into the NFC tag of the target functional device.

[0171] See also Figure 4 , Figure 4A schematic diagram of an interface for creating a task through a specified application provided in an embodiment of the present application.

[0172] Figure 4 In the example, taking the first user terminal as a mobile phone, when the tag data of the NFC tag of the target functional device (ie tag No. 2 in the figure) does not contain task information, the user can create a task in the task setting interface.

[0173] like Figure 4 As shown in the first screen from the left in the first row, users can tap the "Enter Task Name" field in the task settings interface (i.e., the Create Task interface) of a specific application and enter the name of the task being created in the text box. Additionally, users can set the task execution conditions by sliding the "Ask before running" slider. Specifically, the task execution conditions can be set to: Ask before running when an NFC tag is touched; or not ask before running when an NFC tag is touched.

[0174] In addition, users can jump to other interfaces by clicking.

[0175] For example, a designated application can jump to the task icon selection interface when detecting that the user clicks on the task icon in the create task interface. Figure 4 The second screen from the left in the first row is shown in the figure. Users can select a task icon based on the type of task they are creating, such as Backup, Music, Camera, or File. Users can also upload custom images as task icons.

[0176] For another example, the designated application can jump to the task execution interface when detecting that the user clicks the "Next" button in the task creation interface. Figure 4 As shown in the third screen from the left in the first row, users can set the corresponding execution operation for any task in the execution task interface. For example, for a task classified as backup, the corresponding execution operation (i.e., detailed task) can be set to "Back up photos and videos"; in addition, the task can also include execution operations such as "Perform folder backup" and "Back up application 1".

[0177] In addition, users can set a single touch to execute a single task, or they can set a single touch to execute multiple tasks. For example, users can select to execute tasks 1 to 7 with a single touch, and set the task category and detailed tasks for each task.

[0178] Furthermore, the designated application can jump to the task creation interface when detecting that the user clicks the "OK" button in the task execution interface. Figure 4As shown in the first screen from the left in the second row, users can set tasks to be executed when the task execution conditions are met in the task creation interface (such as backing up photos and videos, Task 2, Task 3).

[0179] In addition, if Figure 4 As shown in the second screen from the left in the second row, users can also click the Edit button in the task creation interface to manage multiple tasks (such as sorting, deleting, etc.).

[0180] Furthermore, the user can click the "Read Tag" button in the task creation interface. In response to the user's click operation, the designated application can display a pop-up window to prompt the user to bring the mobile phone close to the device's NFC tag. The user can touch the NFC tag with the mobile phone to instruct the designated application to write the task information of the created task to the NFC tag.

[0181] This makes the task creation process highly customizable. Users can choose from pre-set task templates or customize the triggering logic and sequence. Furthermore, it supports both single-touch task execution and multi-task execution, meeting diverse business needs.

[0182] Furthermore, to ensure task security, applications are designed to support a pre-task confirmation mechanism for operations involving sensitive data. This means that before executing a specific task, users can be requested for authorization. Only after obtaining explicit authorization can the task be executed, ensuring that the task is executed with the user's informed consent and safeguarding data security.

[0183] Correspondingly, the task information of the task indicated by the task setting operation triggered by the user in the task setting interface may be referred to as task information to be written.

[0184] The number of tasks indicated by the task setting operation triggered by the user may be multiple or one. If there are multiple tasks, the task information to be written may represent the multiple tasks and may also include the execution order of the multiple tasks. If there is only one task, the task information to be written may only represent the one task.

[0185] Correspondingly, the first user terminal may write the task information to be written into the NFC tag of the target functional device based on NFC technology.

[0186] See also Figure 5 , Figure 5 A schematic diagram of an interface for specifying an application in the process of writing task information into an NFC tag provided in an embodiment of the present application.

[0187] like Figure 5 As shown in the first screen from the left, Figure 4 After the user clicks the "Read Tag" button in the create task interface, the designated application can display a pop-up window prompting the user to bring the phone close to the device's NFC tag. That is, the designated application can pop up a pop-up window displaying "Mobile phone close to device NFC tag" to prompt the user to bring the phone (i.e., the first user terminal) close to the NFC tag of the target functional device.

[0188] like Figure 5 As shown in the second screen from the left, after the task information is successfully written into the NFC tag of the target functional device, "Read successful!" may be displayed to prompt the user that the writing has been completed.

[0189] Based on the above process, when the tag data of the NFC tag of the target functional device does not contain task information, the user of the account with permission to use the target functional device can set a task for the NFC tag through the task setting interface of the designated application. Accordingly, the first user terminal can obtain the task information of the task set by the user and write it to the NFC tag. Subsequently, after the user terminal reads the tag data of the NFC tag again, it can follow steps S201 to S203 above and, if the designated application is already running and has permission, execute the task represented by the task information written this time, and the task required to be performed by the account logged into the designated application.

[0190] When a task needs to be performed through a designated application of the first user terminal, in addition to the method provided in the embodiment of the present application, if the first account has permission to use the target functional device, the user can manually set and select the task to be performed in the designated interface of the designated application (such as the task execution interface) to execute the selected task through the designated application of the first user terminal.

[0191] Compared to this implementation, the task execution method provided in the embodiments of the present application eliminates the need for the user to manually set and select the task to be executed. Specifically, the first user terminal can read the task information of the task to be executed from the NFC tag and automatically execute the task required by the first account in the task represented by the read task information. This simplifies the steps required to execute the task, thereby improving the efficiency of task execution.

[0192] In one implementation, for each functional device's NFC tag, technicians can pre-set specific tasks on the tag before it leaves the factory, based on the device's capabilities. For example, if the target functional device is a NAS device, the pre-set task on the NFC tag could be to retrieve data stored in a specified folder on the NAS device.

[0193] It can be seen that the tasks preset in the NFC tag in this implementation method are fixed. Compared with this implementation method, the task execution method provided in the embodiment of the present application can write task information corresponding to user needs in the NFC tag of the functional device according to the actual needs of the user, that is, it realizes the dynamic customization function of the task represented by the task information stored in the NFC tag of the functional device, and can also improve the matching degree between the task represented by the task information stored in the NFC tag and the user needs, thereby improving the scenario applicability of the task execution method provided in the embodiment of the present application.

[0194] In addition, for the target functional device, any user with an account that has permission to use the target functional device can set a task represented by the task information stored in the NFC tag of the target functional device according to the above steps S204 to S206. In this way, multi-user collaborative task management for a single functional device can be achieved.

[0195] See also Figure 6 , Figure 6 A flowchart of a task setting provided in an embodiment of the present application.

[0196] First, the first user terminal touches the NFC tag to obtain the tag data stored in the NFC tag. The first user terminal can determine whether a task is set. If so, that is, the tag data contains task information, the corresponding task is executed.

[0197] If not, i.e., the tag data does not contain task information, the task setting interface (create task interface) is displayed through the designated application. The user can then set the task type and the execution operation. Accordingly, the task information of the task created according to the user's needs is written to the NFC tag, i.e., the first user terminal is touched to write to the NFC tag, and the process ends.

[0198] In some embodiments, before step S203, the method further includes:

[0199] Step 1: Sending a permission query request carrying the device identification of the target functional device and the account information of the first account to the server, so that the server determines whether the first account has the permission to use the target functional device and notifies the first user terminal.

[0200] In an embodiment of the present application, the first user terminal may send a permission query request to the server, where the permission query request carries: a device identifier of a target functional device and account information of the first account.

[0201] The device identification of the target functional device may be a unique serial number set for the target functional device when the target functional device leaves the factory. Accordingly, the device identifications of different functional devices are also different.

[0202] For each functional device, the server can record the correspondence between the device identifier of the functional device and the account information of the account that has permission to use the functional device (which can be referred to as a second correspondence). Accordingly, after receiving the permission query request sent by the first user terminal, the server can use the recorded second correspondence to determine whether the first account has permission to use the target functional device. Accordingly, the server can notify the first user terminal, that is, send the judgment result to the first user terminal.

[0203] Based on the above processing, the tag data of the target functional device's NFC tag stores the target functional device's device identification. After obtaining the target functional device's device identification, the first user terminal can request the server to determine whether the first account has permission to use the target functional device. Writing the device identification of a functional device to the NFC tag of that functional device enables the user terminal with NFC functionality to automatically read the functional device's device identification from the NFC tag and, therefore, automatically determine permission.

[0204] In one implementation, the user can manually input the device identification of the target functional device, or the user can open the code scanning interface of a specified application and scan the QR code on the target functional device so that the first user terminal can obtain the device identification of the target functional device.

[0205] Moreover, compared with the above-mentioned implementation method of obtaining the device identification of the target functional device, the task execution method provided in the embodiment of the present application can further simplify the user's operation and realize the system integration of NFC technology and functional devices.

[0206] In some embodiments, step 1 includes:

[0207] Send a permission query request carrying the device identification of the target functional device and the account information of the first account to the server, so that the server can determine whether the first account has the permission to use the target functional device when the target functional device is currently bound, and notify the first user terminal; and send a binding query instruction to the first user terminal when the target functional device is not currently bound.

[0208] The method also includes:

[0209] When a binding inquiry instruction is received, a binding inquiry interface is displayed through a specified application; in response to a binding confirmation operation triggered by the user in the binding inquiry interface, a binding request carrying the device identification of the target functional device and the account information of the first account is sent to the server, so that the server records that the target functional device is currently bound to the first account.

[0210] In an embodiment of the present application, after receiving the permission query request sent by the first user terminal, the server can determine whether the current target functional device has been bound.

[0211] Accordingly, if the target functional device is currently bound, the server can determine whether the first account has the authority to use the target functional device and notify the first user terminal. The process of performing the authority determination can refer to the above embodiment and will not be repeated here.

[0212] In the case that the target functional device is not currently bound, the server may send a binding query instruction to the first user terminal.

[0213] Upon receiving the binding query instruction, the first user terminal displays a binding query interface through a designated application. The binding query interface may display relevant information about the target functional device. For example, relevant information about a functional device may include: an image, model, device identifier, etc.

[0214] Furthermore, the user can trigger a binding confirmation operation in the binding query interface, for example, by clicking a preset button in the binding query interface. In response to the binding confirmation operation triggered by the user in the binding query interface, the first user terminal sends a binding request to the server. The binding request carries the device identifier of the target functional device and the account information of the first account.

[0215] The server can record that the target functional device is currently bound to the first account based on the received binding request, that is, the server records the correspondence between the device identification of the target functional device and the account information of the first account bound to the target functional device (which can be called a third correspondence).

[0216] Based on the above processing, it is possible to query the user who is currently touching the NFC tag of the target functional device with the first user terminal whether to bind the first account to the target functional device, even if the target functional device is not currently bound. It is understandable that when the target functional device leaves the factory, the target functional device is usually not bound. Accordingly, the owner of the target functional device can use the first user terminal logged into a specified application to touch the NFC tag of the target functional device to complete the above binding process. In this way, the binding of the target functional device can be automated.

[0217] In one implementation, a user can manually open a binding query interface within a designated application and manually enter the device ID of the target functional device. Accordingly, in response to the user triggering a binding confirmation operation within the binding query interface, the first user terminal sends a binding request to the server containing the device ID of the target functional device and the account information of the first account, so that the server records that the target functional device is currently bound to the first account.

[0218] Compared to the above-mentioned embodiment, the task execution method provided in the embodiment of the present application can further simplify the user's operation. After receiving the permission query request, it first determines the binding status of the target device, and then performs the above-mentioned permission determination. Accordingly, if the target functional device is not currently bound, the binding inquiry interface is automatically displayed on the first user terminal, and the relevant information of the target device that currently needs to be bound to the first account is automatically filled in, without the need for the user to fill it in manually. In this way, the user's operation can be further simplified, the efficiency of functional device binding can be improved, and efficient binding can be achieved based on the actual binding status of the target functional device.

[0219] In some embodiments, the method further comprises:

[0220] Step 1: If the first account has permission to use the target functional device, the home page is displayed through the designated application.

[0221] Step 2: If the first account does not have the authority to use the target functional device, an authorization request interface is displayed through a designated application; in response to the authorization request operation triggered by the user in the authorization request interface, an authorization request instruction carrying the device identifier of the target functional device and the account information of the first account is sent to the server, so that the server forwards the authorization request instruction to the second user terminal where the owner of the target functional device is logged in, and after receiving the authorization permission instruction returned by the second user terminal, it is recorded that the first account has the authority to use the target functional device.

[0222] In this embodiment of the present application, if the target functional device is currently bound, the first account has permission to use the target functional device, indicating that the current first account may be the account of the owner of the target functional device or the account of a subscriber of the target functional device. Accordingly, the homepage can be displayed through the designated application.

[0223] In one implementation, the homepages displayed by a designated application logged into the account of the owner of the target function device and the homepages displayed by a designated application logged into the account of the subscriber of the target function device may be different.

[0224] For example, the homepage displayed by a designated application logged into the target device's account may display account information of other subscribers of the target device. The homepage displayed by a designated application logged into the target device's account only displays account information of the subscriber.

[0225] Correspondingly, the homepage of the designated application may display relevant information of the target functional device (such as the device identification of the target functional device, the model of the target functional device, etc.).

[0226] In one implementation, the user can manage the target functional device through the homepage of a designated application. For example, if the target functional device is a NAS device, the user can trigger a task to upload the required stored data to the NAS device through the homepage of the designated application.

[0227] When the target function device is currently bound, if the first account does not have permission to use the target function device, the user to whom the first account belongs can request permission to use the target function device from the owner of the target function device through the authorization request interface displayed by the specified application.

[0228] The authorization request interface may display that the target functional device has been bound, and may also display relevant information about the target functional device, such as a picture, model, and device ID.

[0229] See also Figure 7 , Figure 7 A schematic diagram of an interface for specifying an application during an authorization request process provided in an embodiment of the present application.

[0230] like Figure 7 As shown in the first screen from the left, the authorization request interface for a specific application may prompt the user that the device has been bound. Accordingly, the authorization request interface may also display relevant information about the target device (such as a device image, device identifier (i.e., serial number), and model number).

[0231] The user can click the "Go to Join" button. Accordingly, the first user terminal sends an authorization request instruction carrying the device identification of the target functional device and the account information of the first account to the server in response to the authorization request operation triggered by the user in the authorization request interface. The designated application in the first user terminal can display an interface indicating successful sending. In addition, the user can be prompted to "quickly notify the device administrator to approve the application." The user can click the share button below to remind the owner of the target functional device to agree to the authorization through other applications (such as application 1 and application 2).

[0232] The user may trigger an authorization request operation in the authorization request interface, for example, by clicking a preset button in the authorization request interface. In response to the authorization request operation triggered by the user in the authorization request interface, the first user terminal sends an authorization request instruction carrying the device identifier of the target functional device and the account information of the first account to the server.

[0233] After receiving the authorization request instruction, the server may forward the authorization request instruction to the second user terminal logged in by the owner of the target functional device. That is, the second user terminal has a designated application installed, and the account logged in to the designated application (which may be referred to as the second account) is the account of the owner of the target functional device.

[0234] See also Figure 8 , Figure 8 A schematic diagram of an interface displayed on a user terminal of an owner of a functional device provided in an embodiment of the present application.

[0235] When the second user terminal is a mobile phone, the designated application can push a message to the phone's idle screen. Specifically, the phone's notification center can display a message stating "Designated Application" and "XXX has applied to join your device. Check it out!" prompting the target device owner to confirm authorization. Alternatively, the designated application can display a pop-up window stating "Applicant's nickname or default name has applied to join your network-attached storage device." The device owner can click the "Agree" or "Dismiss" button in the pop-up window to confirm authorization.

[0236] In this way, the owner of the functional device can obtain authorization request instructions from other users without opening a designated application, and real-time notification can be achieved, allowing the owner of the functional device to process requests from other users in a timely manner.

[0237] Accordingly, after the second user terminal receives the authorization request instruction forwarded by the server, the owner of the target functional device can choose to agree or ignore the authorization request instruction through the pending authorization interface displayed by the designated application installed in the second user terminal.

[0238] Among them, the authorization interface to be reviewed can display the account information of the user's account (ie, the first account) that triggered the authorization request instruction (such as the account name, the mobile phone number used by the user when registering the account, etc.).

[0239] After receiving the authorization instruction returned by the second user terminal, the server records that the first account has the permission to use the target functional device. Subsequently, when the account logged in to the designated application installed on a user terminal (including the first user terminal or other user terminals other than the first user terminal) is the first account, if the user terminal touches the NFC tag of the target functional device, the user group terminal can determine that the first account has the permission to use the target functional device according to the task execution method provided in the embodiment of the present application, and display the homepage through the designated application.

[0240] It is understandable that when the first account has the permission to use the target functional device, if the task currently required to be performed by the first account needs to be performed through a specified interface in a specified application, it can jump to the specified interface without displaying the home page.

[0241] If the task currently required to be performed by the first account does not need to be performed through a designated interface in a designated application, the homepage may be displayed, and the task currently required to be performed may be performed in the background of the designated application.

[0242] Based on the above process, after the first user terminal reads the tag data of the NFC tag of the target functional device, it can use the device identifier of the target functional device contained in the tag data to first determine the binding status of the target functional device. If the target functional device is not currently bound, the above binding process is performed. If the target functional device is currently bound and the first account does not have permission to use the target functional device, the above authorization request process is performed.

[0243] In addition, the designated application and server can integrate a remote push service. This means that a user requesting permission to use a target device can send an authorization request instruction to a second user terminal logged in by the target device's owner through a first user terminal and the server. After receiving the push notification, the target device's owner can choose to agree or deny authorization. Once the target device's owner agrees to the authorization, the first account will be authorized by the target device's owner.

[0244] In one implementation, the owner of the target functional device can directly enter the account information of the first account (such as the mobile phone number used by the user when registering the account or the account ID of the first account) in the account authorization interface of the designated application installed on the second user terminal. In response to the account authorization operation triggered by the owner of the target functional device in the account authorization interface, an account authorization instruction carrying the device ID of the target functional device and the account information of the first account is sent to the server, so that the server records that the first account has the authority to use the target functional device.

[0245] In the above implementation, only the owner of a functional device can add a member of the functional device, that is, only the owner of a functional device can authorize other accounts. The way to add members is single, and there are slightly more jump paths. The account that needs to be authorized cannot actively apply to join. Compared with the above embodiment, the task execution method provided by the embodiment of the present application can abandon the traditional active authorization method (the owner of the functional device enters the account information of the account to be authorized in the designated application for authorization). The account that needs to be authorized can actively request authorization, which reduces the redundant operations of the owner of the functional device and realizes a quick path from requesting authorization to obtaining authorization.

[0246] See also Figure 9 , Figure 9 A schematic diagram of different interfaces displayed on a user terminal after touching an NFC tag provided in an embodiment of the present application.

[0247] Taking the target functional device as a network attached storage device (NAS device) as an example, after touching the NFC tag of the target functional device, the following three situations may occur:

[0248] Case 1: When the target functional device is not currently bound, the first user terminal displays a binding inquiry interface through a designated application. Figure 9 As shown in the first screen from the left, the binding inquiry interface prompts the user to "Add a device." It also displays relevant information about the target device (such as a device image, device ID (i.e., serial number), and model number). The user can click the "Add" button below to confirm the binding.

[0249] Case 2: If the target functional device is currently bound and the first account has the permission to use the target functional device, the home page will be displayed through the specified application. Figure 9 As shown in the second screen from the left, the home page can display relevant information of the target functional device, such as the device diagram of the target functional device, the device name of the target functional device, the status of the target functional device (online), etc.

[0250] In addition, the homepage of a designated app also supports functions such as search, viewing albums, viewing files, viewing cameras, and offline downloads. It also displays the phone's backup data and the names of recently opened files. Users can also access the album, file, and device interfaces through the function bar at the bottom of the designated app.

[0251] Case 3: If the target functional device is currently bound and the first account does not have the permission to use the target functional device, the authorization request interface is displayed through the designated application. Figure 9As shown in the third screen from the left, the authorization request interface of the specified application can prompt the user that "the device has been bound". Accordingly, the authorization request interface can also display relevant information of the target functional device (such as the device image of the target functional device, the device identification of the target functional device (i.e., serial number), the device model of the target functional device, etc.). The user can click the "Go to Join" button, and accordingly, the first user terminal responds to the authorization request operation triggered by the user in the authorization request interface and sends an authorization request instruction carrying the device identification of the target functional device and the account information of the first account to the server.

[0252] Based on the task processing method provided in the embodiments of the present application, owners and participants of functional devices can directly wake up the target functional device and execute the corresponding task (such as starting the photo backup task first and then the music playback task) by touching the NFC tag when a task has been set in the touched NFC tag.

[0253] If no task is set in the touched NFC tag, the user can automatically jump to the task setting interface of the specified application by touching the NFC tag, avoiding the inefficient operation of manually searching for the task setting interface entrance in the specified application.

[0254] For external users of functional devices (i.e., non-owners and non-joiners), quick device pairing is supported. That is, by touching the NFC tag, an authorization request is quickly sent to the owner of the functional device, eliminating the need for the functional device owner (also known as the device administrator) to manually add the external user through complex operations within a designated application.

[0255] See also Figure 10 , Figure 10 A flowchart of authorization for an owner of a functional device provided in an embodiment of the present application.

[0256] After the first user terminal touches the NFC tag, it can obtain the tag data stored in the NFC tag. The tag data includes the application identifier and the device identifier of the target functional device. In other words, the device identifier is obtained.

[0257] Then, the first user terminal may send a permission query request carrying the device identification of the target functional device and the account information of the first account to the server.

[0258] The server can determine the device's binding status. Accordingly, if the target functional device is not currently bound, the server performs a binding operation. Specifically, it sends a binding query instruction to the first user terminal. Upon receiving the binding query instruction, the first user terminal displays a binding query interface through a designated application. In response to the user triggering a binding confirmation operation in the binding query interface, the server sends a binding request containing the device identifier of the target functional device and the account information of the first account to the server, so that the server records that the target functional device is currently bound to the first account. In other words, the device is activated, and the user becomes the device owner.

[0259] If the target functional device is currently bound and the first account does not have permission to use the target functional device, the server will display an authorization request interface through a designated application. The user can trigger an authorization request operation in the authorization request interface, and the first user terminal can send an authorization request instruction to the server containing the device identifier of the target functional device and the account information of the first account. In other words, the first user terminal sends a join request.

[0260] The server can forward the authorization request instruction to the second user terminal logged in by the owner of the target functional device, i.e., remotely push it to the device owner. Upon receiving the authorization permission instruction returned by the second user terminal, the server records that the first account has permission to use the target functional device. This means that the owner of the target functional device has agreed to join, and the process ends.

[0261] See also Figure 11 , Figure 11 An interactive sequence diagram of a task execution system provided in an embodiment of the present application.

[0262] Close to the phone, identify the tag means: users can use the phone to touch the NFC tag to obtain the tag data.

[0263] The designated application can obtain the device serial number (i.e., the device identifier of the target functional device) from the tag data. Then, the device serial number and account number are sent to the server. In other words, a permission query request is sent that carries the device identifier of the target functional device and the account information of the first account.

[0264] The server can query the database and return the current binding status of the device. That is, the server determines whether the target function is currently bound.

[0265] When the target functional device is currently bound and the first account does not have the authority to use the target functional device, an application to join is initiated, that is, the first user terminal responds to the authorization request operation triggered by the user in the authorization request interface, and sends an authorization request instruction carrying the device identification of the target functional device and the account information of the first account to the server.

[0266] The server initiates a push request via the remote push function, sending a push message to the second user terminal. Specifically, the server forwards the authorization request instruction to the second user terminal logged in by the owner of the target functional device. Accordingly, upon receiving the authorization permission instruction returned by the second user terminal, the server can record that the first account has permission to use the target functional device and return the request result to the designated application of the first user terminal.

[0267] In one implementation, the remote push function may be integrated into the server, or may be set up independently of the server.

[0268] See also Figure 12 , Figure 12 A flowchart of a first user terminal applying for authorization is provided in an embodiment of the present application.

[0269] The first user terminal can touch the NFC tag to actively join. That is, it obtains the device identifier of the target functional device contained in the tag data of the NFC tag, and sends a permission query request carrying the device identifier of the target functional device and the account information of the first account to the server, so that the server can determine whether the first account has the permission to use the target functional device if the target functional device is currently bound.

[0270] If the first account does not have permission to use the target functional device, it will prompt that it has been bound. Accordingly, the first user terminal can actively apply to join, that is, send an authorization request instruction carrying the device identifier of the target functional device and the account information of the first account to the server, and wait for the authorization instruction of the owner of the target functional device.

[0271] Based on the above processing, the user who triggers the authorization request instruction (also known as the non-device user) only needs to touch the NFC tag and trigger the authorization request instruction to complete the entire process of requesting the owner of the target functional device to authorize, realizing a one-click request method. This can simplify the operation process for non-device users and improve the user experience of non-device users. In particular, in family scenarios, it promotes the convenience of family sharing and using the target functional device.

[0272] In some embodiments, before step S202, the method further includes:

[0273] Step a: Determine whether the designated application represented by the read application identifier is currently installed.

[0274] Step b: If the specified application is currently installed and not running, run the specified application.

[0275] In the embodiment of the present application, the operating system of the first user terminal can determine whether the specified application represented by the read application identifier is currently installed based on the application identifier included in the read tag data.

[0276] If the specified application is currently installed and not running, run the specified application.

[0277] It is understood that, when the designated application is not running, the method steps involved in the embodiments of the present application can be processed by the operating system of the first user terminal, for example, reading the tag data stored in the near-field communication (NFC) tag of the target functional device and determining whether the designated application represented by the read application identifier is currently installed.

[0278] When a designated application is running, the method steps involved in the embodiment of the present application may be processed by the designated application installed in the first user terminal, for example, communicating with the server and determining the currently logged-in account.

[0279] In some embodiments, step S202 includes:

[0280] Step S2021: When running the designated application represented by the read application identifier, determine whether there is a currently logged-in account.

[0281] Step S2022: If there is a currently logged-in account, determine the first account currently logged into the designated application.

[0282] Step S2023: If there is no logged-in account, a login interface is displayed through the designated application, and if the login is successful, the first account currently logged into the designated application is determined.

[0283] In an embodiment of the present application, when running a designated application represented by the read application identifier, the first user terminal can determine whether there is a currently logged-in account.

[0284] It is understandable that, for a specified application, if the first account has been logged in historically, closing and then re-running the specified application generally does not change the login status of the first account.

[0285] If there is no logged-in account, a login interface is displayed through the designated application. Accordingly, the user can enter the account information of the account in the login interface, and the first user terminal responds to the login operation triggered by the user and sends a login instruction carrying the input account information to the server.

[0286] Accordingly, the server can verify the account information carried in the login instruction, and if the verification is successful, return a message indicating that the first user terminal has successfully logged in, so that the first user group terminal can determine the account currently logged in to the specified application (ie, the first account).

[0287] Based on the above processing, when a designated application is running on a first user terminal and no account is currently logged in, the first user terminal can jump to the login interface and notify the user to log in. Accordingly, if a logged-in account exists, the first user terminal can further determine whether the read tag data contains task information, and if so, specify the corresponding task.

[0288] See also Figure 13 , Figure 13 A flowchart of a first user terminal performing role determination provided in an embodiment of the present application.

[0289] The first user terminal can add a device by touching the NFC tag, that is, bind it with the functional device.

[0290] After reading the tag data stored in the NFC tag, it can determine whether there is an account logged in to the specified application. If not, jump to the login page.

[0291] If (an account has already logged into the specified application), the first account currently logged into the specified application is determined.

[0292] Then, determine the binding status of the current device. If so, that is, when the target functional device is currently bound, if the first account is the device owner, the home page (owner home page) can be displayed; if the first account is the device participant, the home page (participant home page) can be displayed; if the first account is not the device owner or the device participant, and the first account is a non-device user, the bound page (that is, the authorization request interface) will be displayed.

[0293] If not (the target functional device is not currently bound), the current device is added, that is, the binding inquiry interface is displayed.

[0294] Based on the above processing, role-based access control (RBAC) can be used to simplify the management process of functional devices by associating account permissions with roles, and trigger different processes based on the roles corresponding to the accounts.

[0295] In some embodiments, the tag data further includes: a download address of a specified application. Accordingly, the method further includes:

[0296] If the specified application is not currently installed, jump to the download interface of the specified application according to the download address; in response to the download operation triggered by the user in the download interface, download and install the specified application, and run the specified application after the installation is complete.

[0297] Alternatively, if the designated application is not currently installed and the designated application belongs to the installation whitelist of the first user terminal, the designated application is downloaded and installed according to the download address, and the designated application is run after the installation is complete.

[0298] In an embodiment of the present application, after the first user terminal touches the NFC tag, it can obtain the download address of the specified application contained in the tag data. Then, the first user terminal can jump to the download interface of the specified application according to the download address. For example, the first user terminal can open the local application market and enter the download interface of the specified application. Accordingly, the user can trigger the download operation in the download interface to cause the first user terminal to download and install the specified application, and run the specified application after the installation is complete.

[0299] If the specified application belongs to the installation whitelist of the first user terminal, it indicates that the specified application has obtained the user's permission. Accordingly, the first terminal can directly download the address, download and install the specified application, and run the specified application after the installation is complete.

[0300] Based on the above processing, the first user terminal can realize automatic download and installation of the specified application to automatic operation, simplifying the user's operation. In addition, before downloading the specified application, the user can be asked to determine whether to download according to the user's actual needs, which can further ensure the security of the user terminal.

[0301] In addition, users can download designated applications without going through the application market of the application terminal. In this way, it is possible to quickly download designated applications without launching any application, further simplifying the user's operation.

[0302] See also Figure 14 , Figure 14 A flowchart of a first user terminal downloading a specified application provided in an embodiment of the present application.

[0303] By touching the NFC tag, the first user terminal can obtain the application identifier and download address of the specified application contained in the tag data. The first user terminal then determines whether the specified application represented by the application identifier has been downloaded. If so, the application is launched. If not, the terminal can jump to the download interface of the specified application according to the download address, that is, open the application market.

[0304] Compared to the method where users manually open the application market in their mobile phones and enter the name of the application, the download method provided by the embodiment of the present application can further simplify the user's operation and realize the automation of the entire process from downloading the application, opening the application, and using the application to perform tasks.

[0305] See also Figure 15 , Figure 15 A schematic diagram of the overall functions of a task execution system provided in an embodiment of the present application.

[0306] A user terminal (such as a mobile phone) can obtain NFC tag data by touching an NFC tag, or write task information into the tag by touching the NFC tag. The NFC tag of a functional device stores data related to the functional device (tag data). Accordingly, the mobile phone can automatically download applications at the software level based on the tag data of the NFC tag. At the hardware level, it can also identify the device binding status. At the application function level, it can realize functions such as automated task execution and active application for joining.

[0307] Compared with using NFC technology to achieve a single function (such as payment, data transmission), the task execution method provided in the embodiment of the present application can use NFC technology to achieve a complete interactive process from downloading an application to using the application to perform a task, greatly simplifying user operations and improving the efficiency of task execution.

[0308] In addition, the task execution method provided by the embodiment of the present application realizes the integration of the task execution system and ensures the integrity of the software and hardware interaction process by combining software (specified applications) with hardware (NFC tags and functional devices). Without starting any application, near-field communication technology is used to implement a series of complete interactive solutions from application downloading, account login, functional device addition, management of functional devices, normal use of functional devices, and subsequent customization of tasks in NFC tags.

[0309] See also Figure 16 , Figure 16 An interaction sequence diagram of another task execution system provided in an embodiment of the present application.

[0310] Figure 16 In the example, the functional devices include: a network attached storage device (NAS device) and a camera. That is, the first account has the permission to use the NAS device and the camera.

[0311] Approaching the NAS device to identify the tag: Users can touch their phone to the NAS device's NFC tag to retrieve the tag data. A designated application can then retrieve task information from the tag data, which indicates the execution of the photo backup task. In other words, sending photos to the NAS device will allow the NAS device to back up the photos and notify the designated application that the photo backup task is complete.

[0312] In addition, if the read tag data does not contain task information, the task setting interface is displayed through the specified application, and the user can set the music playback task and write the task into the NFC tag.

[0313] Users can touch the camera's NFC tag with their phone to retrieve the tag data. A designated application can then retrieve task information from the tag data. This task information represents the task of capturing the live image. In other words, the designated application can forward this task to the camera, causing it to return the captured image.

[0314] See also Figure 17 , Figure 17 This is a diagram of the interaction architecture of different roles provided in an embodiment of the present application.

[0315] The initiator (non-device user) initiation method means: when the first account does not have the permission to use the target functional device, the first user terminal can touch the NFC tag, enter the application to join pop-up window (i.e., authorization request interface), and trigger the authorization request operation, waiting for the owner of the target functional device to agree (i.e., wait for approval), and successfully join.

[0316] The receiver (device owner) perception mode indicates that the device owner can perceive the authorization request operation of the initiator in two ways. One is: outside the application: mobile phone system notification, you can refer to Figure 8 The first screen from the left. Another way is: within the application: pop-up notification, you can refer to Figure 8 The second screen from the left in the middle. Accordingly, for the application notification, the device owner can choose to agree or ignore it. After agreeing, the user management logic can be reused to manage the joiner (such as permission switching, notes, and deletion). If ignored, the notification can be directly closed.

[0317] The initiator (non-device user) notification method means that the initiator can directly receive the result of whether the recipient has authorized the application through the application system notification. The initiator (non-device user) perception method means that if the device owner authorizes the application, the user can access the application's user homepage.

[0318] The receiver (device owner) notification mode means that the device owner can receive other messages through application system notifications. The receiver (device owner) perception mode means that the device owner can manage users, such as adding members (adding other participants).

[0319] Based on the same inventive concept, the embodiment of the present application provides a task execution method, which is applied to a server. Figure 18 , Figure 18 This is a third flow chart of a task execution method provided in an embodiment of the present application, which includes the following steps:

[0320] S1801: Upon receiving a permission query request sent by a first user terminal and carrying a device identifier of a target functional device and account information of a first account, determining whether the first account has permission to use the target functional device.

[0321] Among them, the permission query request is: sent by the first user terminal when it reads the tag data stored in the near field communication NFC tag of the target functional device based on the near field communication method, and determines the first account of the specified application represented by the application identifier contained in the tag data obtained by the current login.

[0322] S1802: Notify the first user terminal of the judgment result indicating whether the first account has the authority to use the target functional device, so that when the first account has the authority to use the target functional device and the read tag data contains task information, the first user terminal executes the task required to be executed by the first account in the task represented by the task information through the specified application.

[0323] Based on the task execution method provided in the embodiment of the present application, the first user terminal can read the tag data stored in the NFC tag of the target functional device based on the near field communication method. Accordingly, the first user terminal can determine whether the specified application represented by the application identifier is currently running based on the application identifier contained in the tag data. In the case of running the specified application, the first account currently logged into the specified application is determined. Furthermore, if the first account has the authority to use the target functional device and the read tag data contains task information, the first user terminal can execute the task required to be executed by the first account in the task represented by the task information through the specified application. In this way, it is possible to automatically read the task information of the task to be executed contained in the tag data of the NFC tag. Under the condition that the account currently logged into the specified application (i.e., the first account) has the authority to use the target functional device, the task required to be executed by the first account in the task represented by the read task information is automatically executed, realizing automation from reading task information to executing tasks. Compared with the process in which the user manually opens the specified application in the terminal device and then enters the specified interface in the specified application to set and select the task to be executed, the user's operation steps during the task execution process can be simplified, and the efficiency of task execution can also be improved.

[0324] In an embodiment of the present application, for each functional device, the server may record the correspondence between the device identifier of the functional device and the account information of an account that has permission to use the functional device. Accordingly, upon receiving a permission query request sent by a first user terminal, the server may use the recorded second correspondence to determine whether the first account has permission to use the target functional device. Accordingly, the server may notify the first user terminal, i.e., send the determination result to the first user terminal.

[0325] Based on the above processing, the tag data of the target functional device's NFC tag stores the target functional device's device identification. After obtaining the target functional device's device identification, the first user terminal can request the server to determine whether the first account has permission to use the target functional device. Writing the device identification of a functional device to the NFC tag of that functional device enables the user terminal with NFC functionality to automatically read the functional device's device identification from the NFC tag and, therefore, automatically determine permission.

[0326] In some embodiments, the method further comprises:

[0327] When receiving the authorization request instruction sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, the authorization request instruction is forwarded to the second user terminal logged in by the owner of the target functional device.

[0328] After receiving the authorization permission instruction returned by the second user terminal, it is recorded that the first account has the authority to use the target functional device.

[0329] In this embodiment of the present application, after receiving the authorization request instruction, the server may forward the authorization request instruction to the second user terminal logged in by the owner of the target functional device. That is, the second user terminal has a designated application installed, and the account logged in to the designated application (which may be referred to as the second account) is the account of the owner of the target functional device.

[0330] Based on the above process, the designated application and server can integrate remote push services. That is, a user requesting permission to use a target device can send an authorization request instruction to the second user terminal logged in by the owner of the target device through the first user terminal and the server. After receiving the push notification, the owner of the target device can choose to agree or deny the authorization. Once the owner of the target device agrees to the authorization, the first account will be authorized by the owner of the target device.

[0331] In some embodiments, step S1801 includes:

[0332] When receiving the permission query request sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, if the target functional device is currently bound, it is determined whether the first account has the permission to use the target functional device.

[0333] The method also includes:

[0334] When receiving the permission query request sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, if the target functional device is not currently bound, a binding query instruction is sent to the first user terminal.

[0335] When receiving a binding request sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, it is recorded that the target functional device is currently bound to the first account.

[0336] In an embodiment of the present application, the server can determine the binding status of the device. Accordingly, when the target functional device is not currently bound, the server performs a binding operation. That is, a binding query instruction is sent to the first user terminal. Upon receiving the binding query instruction, the first user terminal displays a binding query interface through a designated application; in response to a binding confirmation operation triggered by the user in the binding query interface, a binding request carrying the device identifier of the target functional device and the account information of the first account is sent to the server, so that the server records that the target functional device is currently bound to the first account.

[0337] Based on the above process, after the first user terminal reads the tag data of the NFC tag of the target functional device, it can use the device identifier of the target functional device contained in the tag data to first determine the binding status of the target functional device. If the target functional device is not currently bound, the above binding process is performed. If the target functional device is currently bound and the first account does not have permission to use the target functional device, the above authorization request process is performed.

[0338] Based on the same inventive concept, an embodiment of the present application provides a task execution device, which is applied to a first user terminal.

[0339] See also Figure 19 , Figure 19 This is a structural diagram of a task execution device provided in an embodiment of the present application. The device includes:

[0340] The tag data reading module 1901 is used to read the tag data stored in the NFC tag of the target functional device based on the near field communication method; wherein the tag data includes the application identifier and the device identifier of the target functional device;

[0341] An account determination module 1902 is configured to determine a first account currently logged into a designated application program when the designated application program represented by the read application identifier is running;

[0342] The task execution module 1903 is used to execute the task required to be performed by the first account in the task represented by the task information through the designated application if it is determined based on the obtained device identification that the first account has the authority to use the target functional device and the read tag data contains task information.

[0343] In some embodiments, the apparatus further comprises:

[0344] a task setting module configured to, when running a designated application represented by the read application identifier, display a task setting interface through the designated application if it is determined based on the obtained device identifier that the first account has permission to use the target functional device, and the read tag data does not contain task information;

[0345] A task information acquisition module, configured to acquire task information of a task indicated by a task setting operation triggered by a user in the task setting interface;

[0346] The task information writing module is used to write the acquired task information into the NFC tag based on the near field communication method.

[0347] In some embodiments, the apparatus further comprises:

[0348] A permission query request sending module is used to send a permission query request carrying the device identification of the target functional device and the account information of the first account to the server before executing the task required to be performed by the first account in the task represented by the task information through the designated application if it is determined based on the obtained device identification that the first account has the permission to use the target functional device, and the read tag data contains task information, so that the server can determine whether the first account has the permission to use the target functional device and notify the first user terminal.

[0349] In some embodiments, the apparatus further comprises:

[0350] a first display module, configured to display a homepage via the designated application if the first account has permission to use the target functional device;

[0351] The second display module is used to display an authorization request interface through the designated application if the first account does not have the authority to use the target functional device; in response to the authorization request operation triggered by the user in the authorization request interface, send an authorization request instruction carrying the device identification of the target functional device and the account information of the first account to the server, so that the server forwards the authorization request instruction to the second user terminal logged in by the owner of the target functional device, and after receiving the authorization permission instruction returned by the second user terminal, record that the first account has the authority to use the target functional device.

[0352] In some embodiments, the permission query request sending module is specifically configured to:

[0353] sending a permission query request carrying the device identifier of the target functional device and the account information of the first account to a server, so that the server determines whether the first account has permission to use the target functional device if the target functional device is currently bound, and notifies the first user terminal of the information; and sending a binding query instruction to the first user terminal if the target functional device is not currently bound;

[0354] The device further comprises:

[0355] The third display module is used to display a binding inquiry interface through the designated application upon receiving the binding inquiry instruction; in response to a binding confirmation operation triggered by the user in the binding inquiry interface, send a binding request carrying the device identification of the target functional device and the account information of the first account to the server, so that the server records that the target functional device is currently bound to the first account.

[0356] In some embodiments, the apparatus further comprises:

[0357] An installation determination module is configured to determine whether the designated application represented by the read application identifier is currently installed before determining the first account currently logged into the designated application;

[0358] The running module is used to run the specified application program when the specified application program is currently installed and is not running.

[0359] In some embodiments, the tag data further includes: a download address of the designated application;

[0360] The device further comprises:

[0361] A download module is used to jump to the download interface of the specified application according to the download address when the specified application is not currently installed; download and install the specified application in response to a download operation triggered by the user in the download interface, and run the specified application after the installation is complete; or, if the specified application is not currently installed and the specified application belongs to the installation whitelist of the first user terminal, download and install the specified application according to the download address, and run the specified application after the installation is complete.

[0362] In some embodiments, the account determination module is specifically configured to:

[0363] When running the specified application represented by the read application identifier, determining whether there is a currently logged-in account;

[0364] If there is a currently logged-in account, determining the first account currently logged into the designated application;

[0365] If there is no currently logged-in account, a login interface is displayed through the designated application, and if the login is successful, the first account currently logged into the designated application is determined.

[0366] Based on the same inventive concept, the embodiment of the present application provides a task execution device, which is applied to a server. Figure 20 , Figure 20 This is a structural diagram of another task execution device provided in an embodiment of the present application. The device includes:

[0367] The permission query request receiving module 2001 is configured to, upon receiving a permission query request sent by a first user terminal and carrying the device identifier of a target functional device and the account information of a first account, determine whether the first account has permission to use the target functional device; wherein the permission query request is sent by the first user terminal after reading tag data stored in a near-field communication (NFC) tag of the target functional device via near-field communication and determining that the first account currently logged into the specified application represented by the application identifier contained in the obtained tag data;

[0368] The first notification module 2002 is used to notify the first user terminal of the judgment result indicating whether the first account has the authority to use the target functional device, so that when the first account has the authority to use the target functional device and the read tag data contains task information, the first user terminal executes the task required to be executed by the first account in the task represented by the task information through the designated application.

[0369] In some embodiments, the apparatus further comprises:

[0370] a forwarding module configured to, upon receiving an authorization request instruction sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, forward the authorization request instruction to a second user terminal logged in by the owner of the target functional device;

[0371] The permission recording module is used to record that the first account has the permission to use the target functional device after receiving the authorization permission instruction returned by the second user terminal.

[0372] In some embodiments, the permission query request receiving module is specifically configured to:

[0373] Upon receiving a permission query request sent by a first user terminal and carrying the device identification of a target functional device and the account information of a first account, if the target functional device is currently bound, determining whether the first account has permission to use the target functional device;

[0374] The device further comprises:

[0375] a binding query instruction sending module, configured to, upon receiving a permission query request sent by a first user terminal and carrying a device identifier of a target functional device and account information of a first account, send a binding query instruction to the first user terminal if the target functional device is not currently bound;

[0376] The binding recording module is configured to, upon receiving a binding request sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, record that the target functional device is currently bound to the first account.

[0377] In the technical solution of this application, the operations involved in obtaining, storing, using, processing, transmitting, providing and disclosing user personal information are all carried out with the user's authorization.

[0378] The present application also provides an electronic device, such as Figure 21 Shown, including:

[0379] Memory 2101, used for storing computer programs;

[0380] The processor 2102 is configured to implement any of the steps of the above-mentioned task execution method when executing the program stored in the memory 2101 .

[0381] Furthermore, the electronic device may further include a communication bus and / or a communication interface, and the processor 2102, the communication interface, and the memory 2101 communicate with each other via the communication bus.

[0382] The communication bus mentioned in the electronic device mentioned above may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0383] The communication interface is used for communication between the above electronic device and other devices.

[0384] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage. Alternatively, the memory may be at least one storage device located away from the processor.

[0385] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0386] In another embodiment provided by the present application, a computer-readable storage medium is further provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned task execution methods are implemented.

[0387] In another embodiment provided by the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute any one of the task execution methods in the above embodiments.

[0388] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a solid-state drive (SSD).

[0389] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0390] Each embodiment in this specification is described in a related manner. Similar portions between the various embodiments can be referenced to each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system, device, electronic device, and computer-readable storage medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simple. For related portions, reference can be made to the descriptions of the method embodiments.

[0391] The above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application are included in the scope of protection of the present application.

Claims

1. A task execution method, characterized in that: Applied to a first user terminal, the method includes: Reading tag data stored in a near field communication (NFC) tag of a target functional device based on a near field communication (NFC) method; wherein the tag data includes an application identifier and a device identifier of the target functional device; When the designated application represented by the read application identifier is running, determining a first account currently logged into the designated application; If it is determined based on the obtained device identification that the first account has the authority to use the target functional device, and the read tag data contains task information, the task required to be performed by the first account in the task represented by the task information is executed through the designated application.

2. The method according to claim 1, characterized in that The method further comprises: When running the designated application represented by the read application identifier, if it is determined based on the obtained device identifier that the first account has permission to use the target functional device, and the read tag data does not contain task information, displaying the task setting interface through the designated application; Acquire task information of a task indicated by a task setting operation triggered by a user in the task setting interface; Based on the near field communication method, the acquired task information is written into the NFC tag.

3. The method according to claim 1, characterized in that Before executing, by the designated application, the task required to be executed by the first account in the task represented by the task information if it is determined based on the acquired device identifier that the first account has permission to use the target functional device and the read tag data contains task information, the method further includes: Sending a permission query request carrying the device identification of the target functional device and the account information of the first account to the server, so that the server determines whether the first account has the permission to use the target functional device and notifies the first user terminal.

4. The method according to claim 3, characterized in that The method further comprises: If the first account has permission to use the target functional device, displaying the homepage through the designated application; If the first account does not have the permission to use the target functional device, an authorization request interface is displayed through the designated application; in response to the authorization request operation triggered by the user in the authorization request interface, an authorization request instruction carrying the device identification of the target functional device and the account information of the first account is sent to the server, so that the server forwards the authorization request instruction to the second user terminal logged in by the owner of the target functional device, and after receiving the authorization permission instruction returned by the second user terminal, it is recorded that the first account has the permission to use the target functional device.

5. The method according to claim 3, characterized in that The sending of a permission query request carrying the device identifier of the target functional device and the account information of the first account to the server, so that the server determines whether the first account has permission to use the target functional device and notifies the first user terminal, includes: sending a permission query request carrying the device identifier of the target functional device and the account information of the first account to a server, so that the server determines whether the first account has permission to use the target functional device if the target functional device is currently bound, and notifies the first user terminal of the information; and sending a binding query instruction to the first user terminal if the target functional device is not currently bound; The method further comprises: When the binding inquiry instruction is received, a binding inquiry interface is displayed through the designated application; in response to the binding confirmation operation triggered by the user in the binding inquiry interface, a binding request carrying the device identification of the target functional device and the account information of the first account is sent to the server, so that the server records that the target functional device is currently bound to the first account.

6. The method according to any one of claims 1 to 5, characterized in that: Before determining the first account currently logged into the designated application, the method further includes: Determining whether the designated application represented by the read application identifier is currently installed; If the designated application is currently installed and is not running, the designated application is run.

7. The method according to claim 6, characterized in that The tag data further includes: a download address of the designated application; The method further comprises: If the specified application is not currently installed, jump to the download interface of the specified application according to the download address; in response to a download operation triggered by the user in the download interface, download and install the specified application, and run the specified application after the installation is complete; or, If the designated application is not currently installed and the designated application belongs to the installation whitelist of the first user terminal, the designated application is downloaded and installed according to the download address, and the designated application is run after the installation is complete.

8. The method according to claim 6, characterized in that The step of determining, when the designated application represented by the read application identifier is being run, the first account currently logged into the designated application includes: When running the specified application represented by the read application identifier, determining whether there is a currently logged-in account; If there is a currently logged-in account, determining the first account currently logged into the designated application; If there is no currently logged-in account, a login interface is displayed through the designated application, and if the login is successful, the first account currently logged into the designated application is determined.

9. A task execution method, characterized in that: Applied to a server, the method includes: Upon receiving a permission query request sent by a first user terminal and carrying the device identifier of a target functional device and the account information of a first account, determining whether the first account has permission to use the target functional device; wherein the permission query request is sent by the first user terminal after reading tag data stored in a near-field communication (NFC) tag of the target functional device based on near-field communication and determining the first account currently logged into a designated application represented by an application identifier contained in the obtained tag data; Notify the first user terminal of the judgment result indicating whether the first account has the authority to use the target functional device, so that when the first account has the authority to use the target functional device and the read tag data contains task information, the first user terminal executes the task required to be executed by the first account in the task represented by the task information through the designated application.

10. The method according to claim 9, characterized in that The method further comprises: Upon receiving the authorization request instruction sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, forwarding the authorization request instruction to the second user terminal logged in by the owner of the target functional device; After receiving the authorization permission instruction returned by the second user terminal, it is recorded that the first account has the authority to use the target functional device.

11. The method according to claim 9, characterized in that The step of determining whether the first account has permission to use the target functional device upon receiving the permission query request sent by the first user terminal and carrying the device identifier of the target functional device and the account information of the first account includes: Upon receiving a permission query request sent by a first user terminal and carrying the device identification of a target functional device and the account information of a first account, if the target functional device is currently bound, determining whether the first account has permission to use the target functional device; The method further comprises: Upon receiving a permission query request sent by a first user terminal and carrying a device identifier of a target functional device and account information of a first account, if the target functional device is not currently bound, sending a binding query instruction to the first user terminal; When receiving the binding request sent by the first user terminal and carrying the device identification of the target functional device and the account information of the first account, it is recorded that the target functional device is currently bound to the first account.

12. A task execution system, characterized in that: The task execution system includes: a first user terminal, and a server; The first user terminal is used to implement the method according to any one of claims 1 to 8; The server is used to implement the method described in any one of claims 9-11.

13. A task execution device, characterized in that: Applied to a first user terminal, the apparatus includes: A tag data reading module is used to read the tag data stored in the NFC tag of the target functional device based on the near field communication method; wherein the tag data includes the application identifier and the device identifier of the target functional device; an account determination module, configured to determine, when running a designated application represented by the read application identifier, a first account currently logged into the designated application; A task execution module is used to execute the task required to be performed by the first account in the task represented by the task information through the designated application if it is determined based on the obtained device identification that the first account has the authority to use the target functional device and the read tag data contains task information.

14. A task execution device, characterized in that: Applied to a server, the device includes: a permission query request receiving module, configured to, upon receiving a permission query request sent by a first user terminal and carrying a device identifier of a target functional device and account information of a first account, determine whether the first account has permission to use the target functional device; wherein the permission query request is sent by the first user terminal after reading tag data stored in a near-field communication (NFC) tag of the target functional device based on near-field communication and determining that the first account currently logged into the designated application represented by the application identifier contained in the obtained tag data; The first notification module is used to notify the first user terminal of the judgment result indicating whether the first account has the permission to use the target functional device, so that when the first account has the permission to use the target functional device and the read tag data contains task information, the first user terminal executes the task required to be executed by the first account in the task represented by the task information through the designated application.

15. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the method according to any one of claims 1 to 11 when executing a program stored in a memory.

16. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 11 is implemented.

Images