Service remote operation method and apparatus

Abstract

The embodiment of the present specification provides a service remote operation method and device, wherein a service remote operation method comprises: receiving an access request of a remote operation entrance sent by a first terminal of an access user; calling a second terminal of an associated user in a trusted relationship with the access user to perform identity verification on the associated user; after the verification passes, activating a remote operation permission of a target service of the associated user to the access user, and receiving a service operation instruction submitted by the access user based on the remote operation permission and sent by the first terminal; calling a third-party verification interface to verify the service operation instruction, and obtaining an instruction execution result of the service operation instruction to return to the second terminal.

Description

TECHNICAL FIELD

[0001] The present document relates to the technical field of data processing, and in particular to a service remote operation method and device. BACKGROUND

[0002] The Internet product is constantly updated, and the elderly group is not familiar with and worried about the Internet product, which leads to the use obstacle of the elderly group to the Internet product becoming a "social problem". The safe and convenient use of online payment and Internet services such as government and people's livelihood is closely related to the improvement of the life quality of the elderly group. The inadaptation of the elderly group to the Internet product brings many changes to the life of the elderly group, and thus the elderly group is repelled by the Internet product and the life quality is reduced. SUMMARY

[0003] One or more embodiments of the present specification provide a service remote operation method applied to a server, comprising: receiving an access request of a remote operation portal sent by a first terminal of an access user. Calling a second terminal of an associated user in a trusted relationship with the access user to perform identity verification on the associated user. After the verification is passed, activating the remote operation permission of the target service of the associated user to the access user, and receiving the service operation instruction submitted by the access user based on the remote operation permission sent by the first terminal. Calling a third-party verification interface to verify the service operation instruction, and obtaining the instruction execution result of the service operation instruction to return to the second terminal.

[0004] One or more embodiments of the present specification provide another service remote operation method applied to a first terminal, comprising: generating an access request to a server according to an access instruction submitted by an access user to a remote operation portal. Obtaining a service operation instruction submitted by the access user based on the remote operation permission of a target service. Send the service operation instruction to the server; wherein the remote operation permission is activated after identity verification of an associated user in a trusted relationship with the access user and verification is passed.

[0005] One or more embodiments of the present specification provide a service remote operation apparatus running on a server, comprising: an access request receiving module configured to receive an access request of a remote operation portal sent by a first terminal of an access user. An identity verification module configured to call a second terminal of an associated user establishing a trusted relationship with the access user to verify the identity of the associated user. An operation instruction receiving module configured to activate a remote operation permission of a target service of the associated user to the access user after verification, and receive a service operation instruction submitted by the access user based on the remote operation permission sent by the first terminal. An operation instruction verification module configured to call a third-party verification interface to verify the service operation instruction, and obtain an instruction execution result of the service operation instruction to return to the second terminal.

[0006] One or more embodiments of the present specification provide another service remote operation apparatus running on a first terminal, comprising: an access request sending module configured to generate an access request to a server according to an access instruction of a remote operation portal submitted by an access user. An operation instruction obtaining module configured to obtain a service operation instruction submitted by the access user based on a remote operation permission of a target service; the remote operation permission is activated after verifying the identity of an associated user establishing a trusted relationship with the access user and passing the verification. An operation instruction sending module configured to send the service operation instruction to the server.

[0007] One or more embodiments of the present specification provide a service remote operation device, comprising: a processor; and a memory configured to store computer executable instructions which, when executed, cause the processor to: receive an access request of a remote operation portal sent by a first terminal of an access user. Call a second terminal of an associated user establishing a trusted relationship with the access user to verify the identity of the associated user. After verification, activate a remote operation permission of a target service of the associated user to the access user, and receive a service operation instruction submitted by the access user based on the remote operation permission sent by the first terminal. Call a third-party verification interface to verify the service operation instruction, and obtain an instruction execution result of the service operation instruction to return to the second terminal.

[0008] One or more embodiments of the present specification provide another service remote operation device, comprising: a processor; and a memory configured to store computer executable instructions which, when executed, cause the processor to: generate an access request according to an access instruction submitted by an access user for a remote operation portal and send the access request to a server. Obtain a service operation instruction submitted by the access user based on a remote operation permission of a target service. Send the service operation instruction to the server; wherein the remote operation permission is activated after identity verification of an associated user in a trusted relationship with the access user is passed.

[0009] One or more embodiments of the present specification provide a storage medium for storing computer executable instructions which, when executed by a processor, implement the following processes: receiving an access request for a remote operation portal sent by a first terminal of an access user. Calling a second terminal of an associated user in a trusted relationship with the access user to verify the identity of the associated user. After verification, the target service remote operation permission of the associated user is activated to the access user, and the service operation instruction submitted by the access user based on the remote operation permission is received. The third-party verification interface is called to verify the service operation instruction, and the instruction execution result of the service operation instruction is returned to the second terminal.

[0010] One or more embodiments of the present specification provide another storage medium for storing computer executable instructions which, when executed by a processor, implement the following processes: generating an access request according to an access instruction submitted by an access user for a remote operation portal and sending the access request to a server. Obtain a service operation instruction submitted by the access user based on a remote operation permission of a target service. Send the service operation instruction to the server; wherein the remote operation permission is activated after identity verification of an associated user in a trusted relationship with the access user is passed. BRIEF DESCRIPTION OF DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the one or more embodiments of the present specification or the prior art, the drawings needed in the embodiment or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments described in the present specification, and those skilled in the art can also obtain other drawings according to these drawings without creative labor;

[0012] Figure 1 A service remote operation method processing flowchart is provided for one or more embodiments of the present specification;

[0013] Figure 2A page diagram of an identity verification page provided for one or more embodiments of the present specification;

[0014] Figure 3 A service remote operation method processing timing diagram applied to a pension query scene provided for one or more embodiments of the present specification;

[0015] Figure 4 Another service remote operation method processing flowchart provided for one or more embodiments of the present specification;

[0016] Figure 5 A service remote operation device diagram provided for one or more embodiments of the present specification;

[0017] Figure 6 Another service remote operation device diagram provided for one or more embodiments of the present specification;

[0018] Figure 7 A structural diagram of a service remote operation equipment provided for one or more embodiments of the present specification;

[0019] Figure 8 Another structural diagram of a service remote operation equipment provided for one or more embodiments of the present specification. DETAILED DESCRIPTION

[0020] In order to make the person skilled in the art better understand the technical scheme in one or more embodiments of the present specification, the technical scheme in one or more embodiments of the present specification will be described clearly and completely in conjunction with the drawings in one or more embodiments of the present specification. Obviously, the described embodiments are only part of the embodiments of the present specification, not all embodiments. Based on one or more embodiments of the present specification, all other embodiments obtained by those skilled in the art without creative labor should belong to the protection scope of the present document.

[0021] An embodiment of a service remote operation method provided by the present specification:

[0022] Referring to Figure 1 , a service remote operation method processing flowchart provided by the present embodiment is shown, referring to Figure 2 , a page diagram of an identity verification page provided by the present embodiment is shown, referring to Figure 3 , a service remote operation method processing timing diagram applied to a pension query scene provided by the present embodiment is shown.

[0023] Referring to Figure 1 , the service remote operation method provided by the present embodiment is applied to a server, and specifically includes steps S102 to S108.

[0024] Step S102: Receive the access request for the remote operation entry sent by the first terminal of the accessing user.

[0025] The remote operation method provided in this embodiment, in cooperation with the first terminal of the accessing user, receives the application from the first terminal to remotely operate the associated user, pushes an identity verification reminder to the second terminal of the associated user to verify the identity of the associated user, and activates the remote operation permission of the associated user for the target service to the accessing user after successful verification. On this basis, it obtains the service operation instructions of the accessing user for the target service, calls a third-party verification interface to verify the service operation instructions, and after successful verification, obtains the instruction execution result of the service operation instructions and returns it to the second terminal. By guiding the other party to remote operation, one party eliminates the other party's obstacles to using the application service and security concerns. The introduction of a third-party verification interface helps users reduce financial and privacy risks during remote operation, helps users better adapt to and integrate into the smart society, and improves the user experience.

[0026] In practical application scenarios, some users, due to unfamiliarity with internet applications and concerns about the security of application operations, may be unable to find the corresponding application services they need. This includes elderly users, illiterate users, and users with operational difficulties. In such cases, if these users do not have family or friends familiar with internet applications to accompany them, the use of internet applications can be guided remotely by such family or friends to complete the target service. In this process, these users are called associated users. Associated users are those who receive remote assistance from other users to complete the target service (such as application password retrieval or pension inquiry services). The terminal device used by the associated user is the second terminal, while the user who remotely assists the associated user in completing the target service is the accessing user, and the terminal device used by the accessing user is the first terminal.

[0027] The target service includes at least one of the following: a main application service and a sub-application service within the main application; the main application is installed on both the first terminal of the accessing user and the second terminal of the associated user. The main application refers to the application installed on the terminal. Optionally, the main application includes the application that runs the target service. The main application service refers to the related services provided by the application, such as application login service and application password retrieval service. The sub-application refers to the sub-application or subprogram (such as a mini-program) carried within the main application. The sub-application service refers to the related services provided by the sub-application or subprogram, such as pension inquiry service, food delivery ordering service, and movie ticket ordering service.

[0028] In practical applications, elderly users are often unfamiliar with the services offered by applications installed on their terminals. Coupled with concerns about internet security and operational difficulties, they are unable to complete the target service via the internet. This embodiment addresses this issue by configuring an access point within the main application to allow elderly users to perform operations remotely. Specifically, a remote operation entry point is configured within the main application installed on the user's first terminal. In practice, not only is a remote operation entry point configured within the main application installed on the user's first terminal, but it can also be configured within the main application installed on the associated user's second terminal. The associated user's second terminal can then initiate a remote operation request by triggering the remote operation entry point, inviting the user to assist in remotely operating the target service.

[0029] Specifically, after receiving a remote operation request initiated by the second terminal through the remote operation entry, a remote operation reminder is sent to the first terminal. The accessing user can see the remote operation request initiated by the associated user for the target service by viewing the remote operation reminder. The accessing user submits an access command by triggering the remote operation entry configured in the main application installed on the first terminal, generates an access request based on the access command, and sends it to the server. The server receives the access request sent by the accessing user's first terminal through the remote operation entry.

[0030] Step S104: Call the second terminal of the associated user who has established a trusted relationship with the accessing user to verify the identity of the associated user.

[0031] The trusted relationship described in this embodiment refers to the reliable relationship between the accessing user and the associated user for remote operation of the target service. In practical applications, in order to improve the security and privacy of remote operation, if both users are registered users of the main application, a trusted relationship between them can be established by verifying the user association relationship between the two users before they perform remote operation of the target service.

[0032] It should be noted that trusted relationships are not limited to being established between the accessing user and the associated user. Trusted relationships can be established between any two users of the registered main application. Therefore, the user who establishes a trusted relationship with the accessing user can be one or more users. Similarly, the user who establishes a trusted relationship with the associated user can be one or more users.

[0033] In one optional implementation of this embodiment, the trusted relationship between the accessing user and the associated user is established in the following manner:

[0034] Based on the request to establish a trusted relationship between the accessing user and the associated user, the identity information and relationship credentials collected and uploaded by the first terminal are obtained;

[0035] Based on the identity information and the relationship certificate, a confirmation reminder for the establishment request is generated and sent to the second terminal;

[0036] The system receives a confirmation request submitted by the second terminal after the confirmation reminder is triggered, and calls the third-party verification interface to verify the user association relationship between the accessing user and the associated user.

[0037] If the verification is successful, a trusted relationship is established between the accessing user and the associated user and stored.

[0038] If the verification fails, no action will be taken.

[0039] After a trusted relationship is established, remote operation permissions for services within the main application of the associated user are granted to the accessing user.

[0040] Specifically, during the establishment of a trusted relationship, the accessing user can submit a request to the server to establish a trusted relationship with the associated user through a first terminal. Then, the first terminal obtains the identity information (such as name and identity identifier) ​​and relationship credentials (such as family member information pictures and family member relationship pictures) uploaded by the accessing user, and sends the identity information and relationship credentials to the server. The server generates a confirmation reminder for the establishment request based on the identity information and relationship credentials and sends it to the second terminal to consult whether the associated user confirms and agrees to establish a trusted relationship with the accessing user. After the confirmation reminder is triggered, a third-party verification interface is called to verify the user association relationship between the accessing user and the associated user in the user association relationship data. After the verification is passed, the trusted relationship between the accessing user and the associated user is established and stored. After the trusted relationship is established, the accessing user is granted remote operation permissions for all services within the associated user's main application.

[0041] For example, if the accessing user is the daughter and the associated user is the father, after the father triggers the confirmation reminder and submits a confirmation request, a third-party verification interface (which stores identity information and other data) is called to verify whether the father-daughter relationship between the daughter and the father is genuine. If the verification is genuine, a trusted relationship between the daughter and the father is established and stored. Based on this trusted relationship, the privacy of the associated user is protected and the associated user is prevented from being defrauded.

[0042] It should be added that, during the process of establishing a trusted relationship, since the target service has not yet been accessed, the user who submits the request to establish a trusted relationship with the associated user can also be called the applicant user. In this case, the trusted relationship is established in the following way: based on the request to establish a trusted relationship between the applicant user and the associated user, the identity information and relationship credentials collected and uploaded by the applicant user's user terminal are obtained.

[0043] A confirmation notification for the establishment request is generated based on the identity information and relationship credentials and sent to the second terminal;

[0044] Receive confirmation requests submitted by the second terminal after the confirmation reminder is triggered, and call a third-party verification interface to verify the user association relationship between the requesting user and the associated user;

[0045] If the verification is successful, a trusted relationship is established between the applicant user and the associated user and stored.

[0046] If the verification fails, no action will be taken.

[0047] After a trusted relationship is established, remote operation permissions for services within the main application of the associated user are granted to the requesting user. Since the requesting user may not necessarily access the target service of the associated user after the trusted relationship is established, the requesting user includes, but is not limited to, users who access the service.

[0048] In specific implementation, after receiving the access request for the remote operation portal sent by the first terminal of the accessing user, in order to protect the data privacy of the associated user, the associated user who has established a trusted relationship with the accessing user is identified, and the second terminal of the associated user is invoked to verify the identity of the associated user, such as collecting the biometric information of the associated user and verifying the biometric information of the associated user; here, the biometric information includes iris information, fingerprint information, and facial image information.

[0049] In practical applications, the associated users who have established a trusted relationship with the accessing user may be one or more. Therefore, in determining the associated users with whom the accessing user has established a trusted relationship, the server can retrieve a list of candidate associated users and return it to the first terminal. The first terminal receives the list of associated users, and the accessing user selects an associated user from this list to remotely operate on the target service and submits it to the server. The server retrieves the associated user selected by the accessing user from the list and then verifies the identity of the selected associated user. Specifically, during the process of selecting and sending associated users to the server for identity verification, the first terminal performs the following operations:

[0050] Receive the list of associated users returned by the server, which represents the candidate associated users with whom the accessing user has established a trusted relationship.

[0051] The system retrieves the associated users selected by the accessing user from the associated user list who are remotely operating the target service and submits them to the server for identity verification of the associated users.

[0052] Accordingly, in one optional implementation of this embodiment, the server performs the following operations during the process of calling the second terminal of an associated user with whom the accessing user has established a trusted relationship to verify the identity of the associated user:

[0053] Find a list of associated users of the candidate associated users who have established a trusted relationship with the accessing user, and return it to the first terminal;

[0054] Obtain the associated users selected by the accessing user from the associated user list who are remotely operating the target service, as submitted by the first terminal.

[0055] The second terminal is invoked to verify the identity of the associated user.

[0056] For example, if the user is the daughter, and the candidate associated users who can establish a trusted relationship with the daughter include the father, mother, grandfather, and grandmother, then the associated user list will display the father, mother, grandfather, and grandmother. The associated user list is returned to the first terminal. The daughter selects the father as the associated user from the associated user list to perform remote operations on the target service. After the server obtains that the associated user is the father, it calls the second terminal to verify the father's identity.

[0057] During this process, the second terminal is invoked to verify the identity of the associated user. This can involve collecting and verifying the biometric information of the associated user. After searching for a list of associated users who have established a trusted relationship with the accessing user, and returning to the first terminal, the associated users selected by the accessing user from the associated user set for remote operation of the target service are obtained. Based on the invocation of the second terminal to verify the identity of the associated user, in an optional implementation of this embodiment, the following operations are performed during the invocation of the second terminal to verify the identity of the associated user:

[0058] Determine additional information for the identity verification;

[0059] Based on the additional information, the target service, and the trusted relationship between the accessing user and the associated user, an identity verification reminder is generated and sent to the second terminal;

[0060] If the identity verification reminder is triggered, the biometric information collected and uploaded by the second terminal through the information collection interface configured on the identity verification page is obtained;

[0061] Determine whether the biometric information matches the biometric information of the associated user;

[0062] If the match is found, the identity verification is confirmed to be successful; if the match is not found, the identity verification is confirmed to be unsuccessful.

[0063] Specifically, additional information can be determined based on the service type of the target service. For example, for query services, the additional information could be set to "Online queries are now available," and for payment services, it could be set to "Online payments are now available." This additional information can be generated by the server, set by the user, or omitted altogether to enhance user experience and reduce security concerns among associated users. After determining the additional information, an identity verification reminder can be generated and sent to the second terminal based on the additional information, the target service, and the trusted relationship between the user and associated users. If the identity verification reminder is triggered, an identity verification page is returned to the second terminal. Biometric information is collected and uploaded through the information collection interface configured on the identity verification page. The system then determines whether the collected and uploaded biometric information matches the associated user's biometric information. If they match, the identity verification is successful; otherwise, it fails.

[0064] For example, after the identity verification reminder sent to the second terminal is triggered, a response is returned to the second terminal as follows: Figure 2 The identity verification page shown. Figure 2 The 201 area contains the additional information "You can now check online," and the 202 control is the information collection interface. By triggering the 202 control, a facial image is collected and uploaded to the server. If the facial image matches the facial image of the associated user, the identity verification is confirmed.

[0065] It should be added that, in the process of generating identity verification reminders, one or more of the following can be used to generate comprehensive identity verification reminders to be sent to associated users: additional information, target service, and the trusted relationship between the accessing user and the associated user.

[0066] Step S106: After verification, activate the remote operation permission of the associated user for the target service for the accessing user, and receive the service operation instruction submitted by the accessing user based on the remote operation permission sent by the first terminal.

[0067] Based on the identity verification of the associated user by the second terminal that establishes a trusted relationship with the accessing user, if the verification is successful, the remote operation permission of the associated user for the target service is activated for the accessing user. The accessing user can perform remote operations on the associated user's target service based on the remote operation permission. The first terminal obtains the service operation instructions generated during the remote operation and sends the service operation instructions to the server. If the verification fails, no processing is performed. Correspondingly, the server receives the service operation instructions submitted by the accessing user based on the remote operation permission sent by the first terminal.

[0068] It should be noted that, after the trusted relationship between the accessing user and the associated user is established, the accessing user is granted remote operation permissions for the services within the associated user's main application. These remote operation permissions represent remote operation permissions for all services within the main application. However, in the actual process of remotely operating the associated user's target service, in addition to granting the accessing user remote operation permissions for the services within the associated user's main application, it is also necessary to call the second terminal of the associated user with whom the trusted relationship has been established to verify the associated user's identity. After the identity verification is successful, the remote operation permissions for the associated user's target service are activated. Based on this, the accessing user can remotely operate the associated user's target service, and then the server receives the service operation instructions submitted by the accessing user based on the remote operation permissions for the target service from the first terminal.

[0069] Step S108: Call a third-party verification interface to verify the service operation instruction, and return the instruction execution result of the service operation instruction to the second terminal.

[0070] As described above, after the identity verification of the associated user is passed, the remote operation permission of the associated user for the target service is activated for the accessing user, and the service operation instruction submitted by the accessing user based on the remote operation permission is received from the first terminal. On this basis, a third-party verification interface is called to verify the service operation instruction to verify whether the service operation instruction conforms to the preset rules, so as to avoid security risks in the remote operation process, prevent data leakage and financial loss, and improve the user experience. After the verification is passed, the instruction execution result of the service operation instruction is obtained and returned to the second terminal.

[0071] In specific implementation, this embodiment allows associated users to access the target service by inviting other users to perform the operation on their behalf. During actual execution, the associated user verifies their identity, while the accessing user performs the operation on the target service. In this approach, the compliance of the operation is verified by checking the service operation instructions generated by the accessing user during the remote operation of the target service, thus improving operational security. Specifically, a third-party verification interface is called to verify the service operation instructions, reducing financial and privacy risks during remote operation. In one optional implementation of this embodiment, the service operation instructions are verified in the following way:

[0072] Determine the instruction category of the service operation instruction;

[0073] The service operation instructions are verified according to the corresponding verification strategy based on the instruction category.

[0074] Specifically, service operation instructions may fall into multiple categories, such as transaction instructions involving funds or query instructions involving user privacy data. For each type of instruction, there is a corresponding verification strategy. Therefore, the instruction category of the service operation instruction is first determined, and then the service operation instruction is verified according to the corresponding verification strategy based on the instruction category.

[0075] In the specific process of verifying service operation commands based on command categories and corresponding verification strategies, the command categories of service operation commands are divided into two types: a first type of operation command and a second type of operation command. Corresponding verification strategies are set for each type of operation command. In an optional implementation of this embodiment, the following operations are performed during the process of verifying service operation commands based on command categories and corresponding verification strategies:

[0076] If the instruction category is a first type of operation instruction, then the instruction parameters carried by the service operation instruction are validated.

[0077] If the instruction category is the second type of operation instruction, then the matching of the service operation instruction with the preset rules is verified.

[0078] When the instruction category is a first-class operation instruction, such as a transaction service operation instruction, the parameter verification of the instruction parameters carried by the service operation instruction includes: detecting whether the instruction parameters carried by the service operation instruction exceed the upper limit; if so, determining that the verification fails; if not, calculating the total instruction parameters carried by the service operation instruction within the detection period; detecting whether the total instruction parameters exceed the upper limit; if so, determining that the verification fails; if not, determining that the verification passes.

[0079] The instruction parameter here refers to the transaction funds carried by the transaction service operation instruction. If the transaction funds exceed the single limit, the total transaction funds carried by the service operation instruction within the detection period are calculated. If the total transaction funds do not exceed the limit, the verification is confirmed to be successful. If the total transaction funds exceed the limit, the verification is confirmed to be unsuccessful. The detection period includes 1 day, 1 week, and 1 month, which are not specifically limited here.

[0080] When the instruction category is a second type of operation instruction, such as a query service operation instruction, the verification of the matching between the service operation instruction and the preset rules includes: detecting whether the service operation instruction matches the preset rules; if yes, determining that the verification has passed; if no, determining that the verification has failed, and calculating the total number of invalid entries; after the total number of invalid entries reaches the threshold, returning a permission freeze request to the server to freeze the remote operation permissions of the accessing user for the target service of the associated user.

[0081] The preset rules here refer to the pre-defined rules that check whether the user privacy data query or other data query involved in the query service operation command conforms to the preset rules and is compliant. If compliant, the verification is confirmed to be passed; if not, the verification is confirmed to be failed, and the total number of invalid commands is calculated. When the total number of invalid commands exceeds the limit, it means that the accessing user's violation operation has reached the limit. The third-party verification interface can return a permission freeze request to the server to freeze the accessing user's remote operation permissions for the target service of the associated user.

[0082] In practical application scenarios, the target services include a first specific category of services and a second specific category of services. The first specific category of services includes, for example, application login services and application password retrieval services. The second specific category of services includes, for example, movie ticket purchase services, utility bill payment services, and pension inquiry services.

[0083] Optionally, for the first specific category of service, the service operation instruction is executed and the obtained instruction execution result is returned to the second terminal; specifically, the service operation instruction execution process is performed by the server, and the obtained instruction execution result is returned to the second terminal; for the second specific category of service, the service data of the target service obtained after the third-party server executes the service operation instruction is obtained and synchronized to the second terminal; specifically, the service operation instruction execution process is performed by the third-party server corresponding to the target service, the third-party server returns the obtained instruction execution result to the server, and then the server synchronizes it to the second terminal.

[0084] In the specific execution process, after the trusted relationship is established, the accessing user can obtain remote operation permissions for services within the main application of the associated user. However, if the user association between the accessing user and the associated user is terminated (e.g., the accessing user is the daughter and the associated user is the father, and the father and daughter sever their father-daughter relationship), or if the accessing user requests to terminate the trusted relationship or the associated user requests to terminate the trusted relationship, the trusted relationship between the accessing user and the associated user can be terminated, and the remote operation permissions for services within the main application of the target service can be disabled. In an optional implementation provided in this embodiment, the trusted relationship is terminated in the following way:

[0085] Receive a request from the first terminal or the second terminal to terminate the trusted relationship;

[0086] Based on the termination request, the trusted relationship is terminated, and remote operation permissions for services within the main application running the target service are disabled.

[0087] The following description uses the application of a remote service operation method provided in this embodiment in a pension inquiry scenario as an example to further illustrate the remote service operation method provided in this embodiment. (See also...) Figure 3The remote operation method for pension inquiry scenarios includes the following steps.

[0088] Step S306: Find a list of associated users of candidate associated users who have established a trusted relationship with the accessing user.

[0089] Previously, the first terminal generated an access request and sent it to the server based on the access command submitted by the user for the remote operation entry.

[0090] Step S308: Return the list of associated users to the first terminal.

[0091] The first terminal obtains the associated users selected by the accessing user from the associated user set for remote operation of the pension inquiry service, and submits them to the server.

[0092] Step S312: Determine additional information for identity verification.

[0093] Step S314: Generate an identity verification reminder based on additional information, pension inquiry service, and the trusted relationship between the accessing user and associated users.

[0094] Step S316: Send the identity verification reminder to the second terminal.

[0095] The second terminal triggers an identity verification reminder, displays an identity verification page, collects biometric information through the information collection interface configured on the identity verification page, and uploads the biometric information to the server.

[0096] Step S318: Obtain the biometric information collected and uploaded by the second terminal through the information collection interface configured on the identity verification page.

[0097] Step S320: Determine whether the biometric information matches the biometric information of the associated user;

[0098] If a match is found, the identity verification is confirmed to be successful, and steps S322, S328 to S330, and S334 to S336 are executed.

[0099] If there is no match, no action is taken.

[0100] Step S322: Activate remote operation permissions for the associated user's pension inquiry service to the accessing user.

[0101] The first terminal obtains the service operation instructions submitted by the user with remote operation permissions based on the pension inquiry service, and sends the service operation instructions to the server.

[0102] The server obtains the service operation instruction sent by the first terminal, synchronizes it with the third-party verification interface to determine the instruction category of the service operation instruction, and verifies the service operation instruction according to the corresponding verification strategy based on the instruction category.

[0103] If the instruction category is the first type of operation instruction, the third-party verification interface verifies the instruction parameters carried by the service operation instruction; if the instruction category is the second type of operation instruction, the third-party verification interface verifies the matching of the service operation instruction with the preset rules.

[0104] After successful verification, the third-party verification interface returns the verification result to the server.

[0105] Step S328: Obtain the service data for the pension query service obtained by the execution of service operation instructions from the third-party server.

[0106] Step S330: Synchronize the obtained pension inquiry service data to the second terminal.

[0107] The first terminal submits a request to the server to terminate the trusted relationship.

[0108] Step S334: Destroy the trusted relationship based on the termination request.

[0109] Step S336: Disable remote operation permissions for services within the main application running the pension inquiry service.

[0110] In addition to the pension inquiry service provided above, other services in the main application or within the main application can also be remotely operated in the same way, such as application login service, application password retrieval service, food delivery ordering service, housing provident fund inquiry service, and lottery viewing service.

[0111] In summary, the remote operation method for services provided in this embodiment first receives an access request for a remote operation entry sent by the first terminal of the accessing user, searches for a list of associated users who have established a trusted relationship with the accessing user, returns to the first terminal, and obtains the associated users selected by the accessing user in the list of associated users to perform remote operations on the target service.

[0112] Next, additional information for identity verification is determined. Based on the additional information, the target service and / or the trusted relationship between the accessing user and the associated user, an identity verification reminder is generated and sent to the second terminal. If the identity verification reminder is detected to be triggered, the biometric information collected and uploaded by the second terminal through the information collection interface configured on the identity verification page is obtained. It is determined whether the biometric information matches the biometric information of the associated user. If they match, the identity verification is determined to be successful. If they do not match, the identity verification is determined to be unsuccessful.

[0113] Finally, if identity verification is successful, remote operation permissions for the target service of the associated user are activated, and service operation instructions submitted by the user based on remote operation permissions are received from the first terminal. A third-party verification interface is invoked to determine the instruction category of the service operation instruction. Based on the instruction category, the service operation instruction is verified according to the corresponding verification strategy, and the instruction execution result is returned to the second terminal. A request to revoke the trusted relationship is received from either the first or second terminal, and the trusted relationship is revoked based on the revocation request. Remote operation permissions for services within the main application running the target service are also disabled.

[0114] By enabling remote operation by accessing users, this eliminates barriers and security concerns associated with internet applications, introduces third-party verification interfaces, reduces financial and privacy risks during remote operation, helps associated users better adapt to and integrate into the smart society, and improves the user experience.

[0115] The implementation process of the remote operation method for the pension inquiry scenario provided above is executed by the server. The implementation process of the remote operation method for the pension inquiry scenario provided in the following method embodiments is executed by the first terminal. The two cooperate with each other during the execution process. Therefore, please refer to the corresponding content of the following method embodiments to read the above implementation process.

[0116] Another embodiment of the remote operation method for this service is provided in this specification:

[0117] In the above embodiments, a service remote operation method is provided and applied to a server. In conjunction with this, this embodiment also provides another service remote operation method and applied to a first terminal. The following description is in conjunction with the accompanying drawings.

[0118] Reference Figure 4 It shows a flowchart of a remote operation method for a service provided in this embodiment, with reference to... Figure 2 It shows a schematic diagram of an identity verification page provided in this embodiment, with reference to... Figure 3 This diagram illustrates the timing sequence of a remote operation method for pension inquiry scenarios provided in this embodiment.

[0119] Reference Figure 4 The remote operation method for services provided in this embodiment is applied to a first terminal and specifically includes steps S402 to S406.

[0120] Step S402: Based on the access instruction submitted by the user for the remote operation entry point, generate an access request and send it to the server.

[0121] The remote operation method for services provided in this embodiment, by cooperating with the server, generates an access request and sends it to the server based on the access instruction submitted by the user for the remote operation entry point, obtains the service operation instruction submitted by the user based on the remote operation permission of the target service, and then sends the service operation instruction to the server. This allows one party to help the other party with remote operation guidance, eliminate the other party's obstacles to using the application service and security concerns, help users better adapt to and integrate into the smart society, and improve the user experience.

[0122] In practical application scenarios, some users, due to unfamiliarity with internet applications and concerns about the security of application operations, may be unable to find the corresponding application services they need. This includes elderly users, illiterate users, and users with operational difficulties. In such cases, if these users do not have family or friends familiar with internet applications to accompany them, the use of internet applications can be guided remotely by such family or friends to complete the target service. In this process, these users are called associated users. Associated users are those who receive remote assistance from other users to complete the target service (such as application password retrieval or pension inquiry services). The terminal device used by the associated user is the second terminal, while the user who remotely assists the associated user in completing the target service is the accessing user, and the terminal device used by the accessing user is the first terminal.

[0123] The target service includes at least one of the following: a main application service and a sub-application service within the main application; the main application is installed on both the first terminal of the accessing user and the second terminal of the associated user. The main application refers to the application installed on the terminal. Optionally, the main application includes the application that runs the target service. The main application service refers to the related services provided by the application, such as application login service and application password retrieval service. The sub-application refers to the sub-application or subprogram (such as a mini-program) carried within the main application. The sub-application service refers to the related services provided by the sub-application or subprogram, such as pension inquiry service, food delivery ordering service, and movie ticket ordering service.

[0124] In practical applications, elderly users are often unfamiliar with the services offered by applications installed on their terminals. Coupled with concerns about internet security and operational difficulties, they are unable to complete the target service via the internet. This embodiment addresses this issue by configuring an access point within the main application to allow elderly users to perform operations remotely. Specifically, a remote operation entry point is configured within the main application installed on the user's first terminal. In practice, not only is a remote operation entry point configured within the main application installed on the user's first terminal, but it can also be configured within the main application installed on the associated user's second terminal. The associated user's second terminal can then initiate a remote operation request by triggering the remote operation entry point, inviting the user to assist in remotely operating the target service.

[0125] Specifically, after receiving a remote operation request initiated by the second terminal through the remote operation entry, the server sends a remote operation reminder to the first terminal. The accessing user can see the remote operation request initiated by the associated user for the target service by viewing the remote operation reminder. The accessing user submits an access command by triggering the remote operation entry configured in the main application installed on the first terminal, generates an access request based on the access command, and sends it to the server. The server receives the access request sent by the accessing user's first terminal through the remote operation entry.

[0126] Based on this, in order to protect the data privacy of associated users, associated users who have established a trusted relationship with the accessing user are identified, and the second terminal of the associated user is invoked to verify the identity of the associated user, such as collecting the biometric information of the associated user and verifying the biometric information of the associated user; here, biometric information includes iris information, fingerprint information, and facial image information.

[0127] The trusted relationship refers to the reliable relationship between the accessing user and the associated user for remote operation of the target service. In practical applications, in order to improve the security and privacy of remote operation, if both users are registered users of the main application, a trusted relationship between them can be established by verifying the user association relationship between the two users before they perform remote operation of the target service.

[0128] It should be noted that trusted relationships are not limited to being established between the accessing user and the associated user. Trusted relationships can be established between any two users of the registered main application. Therefore, the user who establishes a trusted relationship with the accessing user can be one or more users. Similarly, the user who establishes a trusted relationship with the associated user can be one or more users.

[0129] The trusted relationship between the accessing user and the associated user is established in the following way:

[0130] Based on the request to establish a trusted relationship between the accessing user and the associated user, the identity information and relationship credentials collected and uploaded by the first terminal are obtained;

[0131] Based on the identity information and the relationship certificate, a confirmation reminder for the establishment request is generated and sent to the second terminal of the associated user;

[0132] The system receives a confirmation request submitted by the second terminal after the confirmation reminder is triggered, and calls a third-party verification interface to verify the user association relationship between the accessing user and the associated user.

[0133] If the verification is successful, a trusted relationship is established between the accessing user and the associated user and stored.

[0134] If the verification fails, no action will be taken.

[0135] Specifically, during the establishment of a trusted relationship, the accessing user can submit a request to the server to establish a trusted relationship with the associated user through a first terminal. Then, the first terminal obtains the identity information (such as name and identity identifier) ​​and relationship credentials (such as family member information pictures and family member relationship pictures) uploaded by the accessing user, and sends the identity information and relationship credentials to the server. The server generates a confirmation reminder for the establishment request based on the identity information and relationship credentials and sends it to the second terminal to consult whether the associated user confirms and agrees to establish a trusted relationship with the accessing user. After the confirmation reminder is triggered, the server calls a third-party verification interface to verify the user association relationship between the accessing user and the associated user in the user association relationship data. After the verification is successful, the trusted relationship between the accessing user and the associated user is established and stored. After the trusted relationship is established, the server grants the accessing user remote operation permissions for all services within the associated user's main application.

[0136] For example, if the accessing user is the daughter and the associated user is the father, after the father triggers the confirmation reminder and submits a confirmation request, the server calls a third-party verification interface (which stores identity information and other data) to verify whether the father-daughter relationship between the daughter and the father is genuine. If the verification is genuine, a trusted relationship between the daughter and the father is established and stored. Based on this trusted relationship, the privacy of the associated user is protected and the associated user is prevented from being defrauded.

[0137] It should be added that, during the process of establishing a trusted relationship, since the target service has not yet been accessed, the user who submits the request to establish a trusted relationship with the associated user can be called the applicant user. In this case, the trusted relationship is established in the following way: based on the request to establish a trusted relationship between the applicant user and the associated user, the identity information and relationship credentials collected and uploaded by the applicant user's user terminal are obtained.

[0138] A confirmation notification for the establishment request is generated based on the identity information and relationship credentials and sent to the associated user's second terminal;

[0139] Receive confirmation requests submitted by the second terminal after the confirmation reminder is triggered, and call a third-party verification interface to verify the user association relationship between the requesting user and the associated user;

[0140] If the verification is successful, a trusted relationship is established between the applicant user and the associated user and stored.

[0141] If the verification fails, no action will be taken.

[0142] After a trusted relationship is established, remote operation permissions for services within the main application of the associated user are granted to the requesting user. Since the requesting user may not necessarily access the target service of the associated user after the trusted relationship is established, the requesting user includes, but is not limited to, users who access the service.

[0143] In practical applications, there may be one or more associated users who have established a trusted relationship with the accessing user. Therefore, in determining the associated users who have established a trusted relationship with the accessing user, the server can search for a list of associated users who are candidate associated users and return it to the first terminal. The first terminal receives the list of associated users, and the associated users selected by the accessing user from the list of associated users to perform remote operations on the target service are submitted to the server. The server obtains the associated users selected by the accessing user from the list of associated users and then verifies the identities of the selected associated users. In an optional implementation provided in this embodiment, the first terminal performs the following operations during the process of selecting associated users and sending them to the server for identity verification:

[0144] Receive the list of associated users returned by the server that are candidate associated users who have established a trusted relationship with the accessing user;

[0145] The server retrieves the associated users selected by the accessing user from the associated user list who are remotely operating the target service and submits them to the server for identity verification of the associated users.

[0146] Accordingly, during the process of calling the second terminal of the associated user who has established a trusted relationship with the accessing user to verify the identity of the associated user, the server performs the following operations:

[0147] Find a list of associated users who are candidate associated users with whom the accessing user has established a trusted relationship, and return it to the first terminal;

[0148] Retrieve the associated users selected by the first terminal's access user from the associated user list who are remotely operating the target service;

[0149] The second terminal is invoked to verify the identity of the associated user.

[0150] For example, if the user is the daughter, and the candidate associated users who can establish a trusted relationship with the daughter include the father, mother, grandfather, and grandmother, then the associated user list will display the father, mother, grandfather, and grandmother. The associated user list is returned to the first terminal. The daughter selects the father as the associated user from the associated user list to perform remote operations on the target service. After the server obtains that the associated user is the father, it calls the second terminal to verify the father's identity.

[0151] During this process, the server invokes the second terminal to verify the identity of the associated user, which can actually collect the biometric information of the associated user and verify the biometric information. Based on receiving the list of associated users who have established a trusted relationship with the accessing user from the server, obtaining the associated users selected by the accessing user from the set of associated users who remotely operate on the target service, and submitting them to the server for identity verification of the associated users, in an optional implementation of this embodiment, the server performs the following operations during the process of invoking the second terminal to verify the identity of the associated user:

[0152] Determine additional information for the identity verification;

[0153] Based on the additional information, the target service, and the trusted relationship between the accessing user and the associated user, an identity verification reminder is generated and sent to the associated user's second terminal.

[0154] If the identity verification reminder is triggered, the biometric information collected and uploaded by the second terminal through the information collection interface configured on the identity verification page is obtained;

[0155] Determine whether the biometric information matches the biometric information of the associated user;

[0156] If the match is found, the identity verification is confirmed to be successful; if the match is not found, the identity verification is confirmed to be unsuccessful.

[0157] Specifically, additional information can be determined based on the service type of the target service. For example, for query services, the additional information could be set to "Online queries are now available," and for payment services, it could be set to "Online payments are now available." This additional information can be generated by the server, set by the user, or omitted altogether to enhance user experience and reduce security concerns among associated users. After determining the additional information, an identity verification reminder can be generated and sent to the second terminal based on the additional information, the target service, and the trusted relationship between the user and associated users. If the identity verification reminder is triggered, an identity verification page is returned to the second terminal. Biometric information is collected and uploaded through the information collection interface configured on the identity verification page. The system then determines whether the collected and uploaded biometric information matches the associated user's biometric information. If they match, the identity verification is successful; otherwise, it fails.

[0158] For example, after the identity verification reminder sent to the second terminal is triggered, a response is returned to the second terminal as follows: Figure 2 The identity verification page shown. Figure 2 The 201 area contains the additional information "You can now check online," and the 202 control is the information collection interface. By triggering the 202 control, a facial image is collected and uploaded to the server. If the facial image matches the facial image of the associated user, the identity verification is confirmed.

[0159] It should be added that, in the process of generating identity verification reminders, the server can generate a comprehensive identity verification reminder and send it to the associated user based on one or more of the following three factors: additional information, target service, and the trusted relationship between the accessing user and the associated user.

[0160] Step S404: Obtain the service operation instruction submitted by the accessing user based on the remote operation permission of the target service.

[0161] The remote operation permission is activated after verifying the identity of the associated user who has established a trusted relationship with the accessing user, and the verification is successful. As described above, the server calls the second terminal of the associated user who has established a trusted relationship with the accessing user to verify the identity of the associated user. Based on this, if the verification is successful, the server activates the remote operation permission for the associated user's target service for the accessing user. The accessing user can perform remote operations on the associated user's target service based on the remote operation permission, and the first terminal obtains the service operation instructions generated during the remote operation.

[0162] It should be noted that after the aforementioned server establishes a trusted relationship between the accessing user and the associated user, it grants the accessing user remote operation permissions for the services within the associated user's main application. These remote operation permissions represent remote operation permissions for all services within the main application. However, in the actual process of remotely operating the associated user's target service, in addition to granting the accessing user remote operation permissions for the services within the associated user's main application, the server also needs to call the second terminal of the associated user with whom the trusted relationship has been established to verify the associated user's identity. After the identity verification is successful, the server activates the remote operation permissions for the associated user's target service. Based on this, the accessing user can remotely operate the associated user's target service, and then the server receives the service operation instructions submitted by the accessing user based on the remote operation permissions for the target service from the first terminal.

[0163] Step S406: Send the service operation instruction to the server.

[0164] As described above, the server activates remote operation permissions for the target service of the associated user for the accessing user. The accessing user can perform remote operations on the target service of the associated user based on the remote operation permissions. The first terminal obtains the service operation instructions generated during the remote operation and sends the service operation instructions to the server. Correspondingly, the server receives the service operation instructions submitted by the accessing user based on the remote operation permissions sent by the first terminal, calls a third-party verification interface to verify the service operation instructions, and verifies whether the service operation instructions meet the preset rules to avoid security risks during the remote operation, prevent data leakage and financial loss, and improve the user experience. After the verification is successful, the server obtains the instruction execution result of the service operation instructions and returns it to the second terminal.

[0165] In practical implementation, this embodiment allows associated users to access the target service by inviting other users to perform the operation on their behalf. During actual execution, the associated user verifies their identity, while the accessing user performs the operation on the target service. In this approach, the compliance of the operation is verified by checking the service operation instructions generated by the accessing user during the remote operation of the target service, thus improving operational security. Specifically, the server calls a third-party verification interface to verify the service operation instructions, thereby reducing financial and privacy risks during remote operation. The third-party verification interface verifies the service operation instructions in the following way:

[0166] Determine the instruction category for the service operation command;

[0167] Service operation commands are validated according to the corresponding validation strategy based on the command category.

[0168] Specifically, service operation instructions may fall into multiple categories, such as transaction instructions involving funds or query instructions involving user privacy data. For each type of instruction, there is a corresponding verification strategy. In this regard, the server first determines the instruction category of the service operation instruction, and then verifies the service operation instruction according to the corresponding verification strategy based on the instruction category.

[0169] In the specific process of verifying service operation commands based on command categories and corresponding verification policies, the command categories are divided into two types: Category 1 and Category 2. Corresponding verification policies are set for each type of command. Specifically, during the server's verification of service operation commands based on command categories and corresponding verification policies, the following operations are performed:

[0170] If the instruction category is a Class 1 operation instruction, then the instruction parameters carried by the service operation instruction are validated.

[0171] If the instruction category is the second type of operation instruction, then the matching between the service operation instruction and the preset rules is verified.

[0172] Specifically, when the instruction category is a first-class operation instruction, such as a transaction service operation instruction, the parameter verification of the instruction parameters carried by the service operation instruction includes: detecting whether the instruction parameters carried by the service operation instruction exceed the upper limit; if so, determining that the verification fails; if not, calculating the total instruction parameters carried by the service operation instruction within the detection period; detecting whether the total instruction parameters exceed the upper limit; if so, determining that the verification fails; if not, determining that the verification passes.

[0173] The instruction parameter here refers to the transaction funds carried by the transaction service operation instruction. If the transaction funds exceed the single limit, the total transaction funds carried by the service operation instruction within the detection period are calculated. If the total transaction funds do not exceed the limit, the verification is confirmed to be successful. If the total transaction funds exceed the limit, the verification is confirmed to be unsuccessful. The detection period includes 1 day, 1 week, and 1 month, which are not specifically limited here.

[0174] When the instruction category is a second type of operation instruction, such as a query service operation instruction, the verification of the matching between the service operation instruction and the preset rules includes: detecting whether the service operation instruction matches the preset rules; if yes, determining that the verification has passed; if no, determining that the verification has failed, and calculating the total number of invalid instructions; after the total number of invalid instructions reaches the threshold, returning a permission freeze request to the server to freeze the remote operation permissions of the accessing user for the target service of the associated user.

[0175] The preset rules here refer to the pre-defined rules that check whether the user privacy data query or other data query involved in the query service operation command conforms to the preset rules and is compliant. If compliant, the verification is confirmed to be passed; if not, the verification is confirmed to be failed, and the total number of invalid commands is calculated. When the total number of invalid commands exceeds the limit, it means that the accessing user's violation operation has reached the limit. The third-party verification interface can return a permission freeze request to the server to freeze the accessing user's remote operation permissions for the target service of the associated user.

[0176] In practical application scenarios, the target services include a first specific category of services and a second specific category of services. The first specific category of services includes, for example, application login services and application password retrieval services. The second specific category of services includes, for example, movie ticket purchase services, utility bill payment services, and pension inquiry services.

[0177] For the first specific category of service, the service operation instructions are executed and the results are returned to the second terminal. Specifically, the service operation instruction execution process is performed by the server, which then returns the results to the second terminal. For the second specific category of service, the service data of the target service obtained by the third-party server after executing the service operation instructions is acquired and synchronized to the second terminal. Specifically, the service operation instruction execution process is performed by the third-party server corresponding to the target service, which returns the results to the server, which then synchronizes them to the second terminal.

[0178] In the specific execution process, after the trusted relationship is established, the accessing user can obtain remote operation permissions for services within the main application of the associated user. However, if the user association between the accessing user and the associated user is terminated (e.g., the accessing user is the daughter and the associated user is the father, and the father and daughter sever their father-daughter relationship), or if the accessing user requests to terminate the trusted relationship or the associated user requests to terminate the trusted relationship, the server can terminate the trusted relationship between the accessing user and the associated user, and simultaneously disable remote operation permissions for services within the main application of the target service. Specifically, the trusted relationship is terminated in the following way:

[0179] Receive a request from the first terminal or the second terminal to terminate the trusted relationship;

[0180] The trusted relationship is terminated based on the termination request, and remote operation permissions for services within the main application running the target service are disabled.

[0181] The following description uses the application of a remote service operation method provided in this embodiment in a pension inquiry scenario as an example to further illustrate the remote service operation method provided in this embodiment. (See also...) Figure 3 The remote operation method for pension inquiry scenarios includes the following steps.

[0182] Step S302: Generate an access request based on the access instruction submitted by the user for the remote operation entry point.

[0183] Step S304: Send an access request to the server.

[0184] The server retrieves a list of associated users who are candidate users with whom the accessing user has established a trusted relationship, and returns this list of associated users to the first terminal.

[0185] Step S310: Obtain the associated users selected by the accessing user from the associated user list who are remotely operating the pension inquiry service, and submit them to the server.

[0186] The server determines additional information for identity verification, and generates an identity verification reminder based on the additional information, the pension inquiry service, and the trusted relationship between the accessing user and the associated user, and sends the identity verification reminder to the second terminal.

[0187] The second terminal triggers an identity verification reminder, displays an identity verification page, collects biometric information through the information collection interface configured on the identity verification page, and uploads the biometric information to the server.

[0188] The server obtains the biometric information collected and uploaded by the second terminal through the information collection interface configured on the identity verification page, and determines whether the biometric information matches the biometric information of the associated user. If they do not match, no action is taken; if they match, the identity verification is confirmed to be successful. The server then activates the remote operation permission for the associated user's pension inquiry service for the accessing user.

[0189] Step S324: Obtain the service operation instructions submitted by the user with remote operation permissions based on the pension inquiry service.

[0190] Step S326: Send the service operation command to the server.

[0191] The server obtains the service operation instruction sent by the first terminal, synchronizes it with the third-party verification interface to determine the instruction category of the service operation instruction, and verifies the service operation instruction according to the corresponding verification strategy based on the instruction category.

[0192] If the instruction category is the first type of operation instruction, the third-party verification interface verifies the instruction parameters carried by the service operation instruction; if the instruction category is the second type of operation instruction, the third-party verification interface verifies the matching of the service operation instruction with the preset rules.

[0193] After successful verification, the third-party verification interface returns the verification result to the server;

[0194] The server obtains the pension query service data obtained from the execution of service operation instructions by the third-party server, and synchronizes the obtained pension query service data to the second terminal.

[0195] Step S332: Submit a request to the server to terminate the trusted relationship.

[0196] The server terminates the trusted relationship based on the termination request and disables remote operation permissions for services within the main application running the pension query service.

[0197] In addition to the pension inquiry service provided above, other services in the main application or within the main application can also be remotely operated in the same way, such as application login service, application password retrieval service, food delivery ordering service, housing provident fund inquiry service, and lottery viewing service.

[0198] In summary, the remote operation method for services provided in this embodiment first generates an access request and sends it to the server based on the access instruction submitted by the user for the remote operation entry point. Second, it receives a list of associated users who have established a trusted relationship with the user and is returned by the server. It then obtains the associated user selected by the user from the list of associated users to perform remote operation on the target service and submits it to the server to call the second terminal to verify the identity of the associated user. Finally, it obtains the service operation instruction submitted by the user based on the remote operation permission of the target service and sends the service operation instruction to the server.

[0199] By enabling remote operation by accessing users, this eliminates barriers and security concerns associated with internet applications, introduces third-party verification interfaces, reduces financial and privacy risks during remote operation, helps associated users better adapt to and integrate into the smart society, and improves the user experience.

[0200] This specification provides an embodiment of a remote operation device for services, as follows:

[0201] In the above embodiments, a service remote operation method applied to a server is provided, and correspondingly, a service remote operation device running on a server is also provided, which will be described below with reference to the accompanying drawings.

[0202] Reference Figure 5 The diagram illustrates a remote operation device for services provided in this embodiment.

[0203] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0204] This embodiment provides a remote operation device for services, which runs on a server and includes:

[0205] The access request receiving module 502 is configured to receive access requests for remote operation entry sent by the first terminal of the accessing user;

[0206] The identity verification module 504 is configured to call the second terminal of the associated user who has established a trusted relationship with the accessing user to verify the identity of the associated user;

[0207] The operation instruction receiving module 506 is configured to, after verification, activate the remote operation permission of the associated user for the target service to the accessing user, and receive the service operation instruction submitted by the accessing user based on the remote operation permission sent by the first terminal.

[0208] The operation instruction verification module 508 is configured to call a third-party verification interface to verify the service operation instruction, and obtain the instruction execution result of the service operation instruction and return it to the second terminal.

[0209] Another embodiment of the remote operation device provided in this manual is as follows:

[0210] In the above embodiments, a service remote operation method applied to a first terminal is provided, and correspondingly, a service remote operation device running on the first terminal is also provided, which will be described below with reference to the accompanying drawings.

[0211] Reference Figure 6 The diagram illustrates a remote operation device for services provided in this embodiment.

[0212] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0213] This embodiment provides a remote operation device for services, which operates on a first terminal and includes:

[0214] The access request sending module 602 is configured to generate an access request and send it to the server based on the access command submitted by the accessing user for the remote operation entry point;

[0215] The operation instruction acquisition module 604 is configured to acquire the service operation instruction submitted by the accessing user based on the remote operation permission of the target service; the remote operation permission is activated after the identity verification of the associated user who has established a trusted relationship with the accessing user is performed and the verification is successful.

[0216] The operation instruction sending module 606 is configured to send the service operation instruction to the server.

[0217] This specification provides an example of a remote operation device for services, as follows:

[0218] Corresponding to the above-described method for remotely operating a server, based on the same technical concept, one or more embodiments of this specification also provide a remote service operation device for executing the aforementioned remote service operation method. Figure 7 This is a schematic diagram of the structure of a service remote operation device provided for one or more embodiments of this specification.

[0219] This embodiment provides a remote operation device for services, including:

[0220] like Figure 7 As shown, the service remote operation device can vary significantly due to differences in configuration or performance. It may include one or more processors 701 and memory 702, and the memory 702 may store one or more application programs or data. The memory 702 may be temporary or persistent storage. The application programs stored in the memory 702 may include one or more modules (not shown), each module may include a series of computer-executable instructions from the service remote operation device. Furthermore, the processor 701 may be configured to communicate with the memory 702 and execute the series of computer-executable instructions in the memory 702 on the service remote operation device. The service remote operation device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input / output interfaces 705, one or more keyboards 706, etc.

[0221] In one specific embodiment, the servicing remote operation device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the servicing remote operation device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0222] Receive access requests for remote operation entry points sent by the user's first terminal;

[0223] The system invokes a second terminal of an associated user with whom the accessing user has established a trusted relationship to verify the identity of the associated user.

[0224] After verification, the remote operation permission of the associated user for the target service is activated for the accessing user, and the service operation instruction submitted by the accessing user based on the remote operation permission is received from the first terminal.

[0225] The service operation instruction is verified by calling a third-party verification interface, and the execution result of the service operation instruction is returned to the second terminal.

[0226] Another example of remote device operation provided in this manual is as follows:

[0227] Corresponding to the above-described service remote operation method applied to a first terminal, based on the same technical concept, one or more embodiments of this specification also provide a service remote operation device, which is used to execute the service remote operation method provided above. Figure 8 This is a schematic diagram of the structure of a service remote operation device provided for one or more embodiments of this specification.

[0228] This embodiment provides a remote operation device for services, including:

[0229] like Figure 8 As shown, the service remote operation device can vary significantly due to differences in configuration or performance. It may include one or more processors 801 and memory 802, and the memory 802 may store one or more application programs or data. The memory 802 may be temporary or persistent storage. The application programs stored in the memory 802 may include one or more modules (not shown), each module may include a series of computer-executable instructions in the service remote operation device. Furthermore, the processor 801 may be configured to communicate with the memory 802 and execute the series of computer-executable instructions in the memory 802 on the service remote operation device. The service remote operation device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0230] In one specific embodiment, the servicing remote operation device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the servicing remote operation device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0231] Based on the access command submitted by the user for the remote operation entry point, an access request is generated and sent to the server;

[0232] Obtain the service operation instructions submitted by the accessing user based on the remote operation permissions of the target service;

[0233] Send the service operation command to the server;

[0234] The remote operation permission is activated after the identity of the associated user who has established a trusted relationship with the accessing user is verified and the verification is successful.

[0235] This specification provides an example of a storage medium as follows:

[0236] In accordance with the above-described method for remote operation of a server, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0237] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0238] Receive access requests for remote operation entry points sent by the user's first terminal;

[0239] The system invokes a second terminal of an associated user with whom the accessing user has established a trusted relationship to verify the identity of the associated user.

[0240] After verification, the remote operation permission of the associated user for the target service is activated for the accessing user, and the service operation instruction submitted by the accessing user based on the remote operation permission is received from the first terminal.

[0241] The service operation instruction is verified by calling a third-party verification interface, and the execution result of the service operation instruction is returned to the second terminal.

[0242] It should be noted that the embodiments concerning storage media in this specification and the embodiments concerning remote operation methods for services in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

[0243] Another embodiment of the storage medium provided in this specification is as follows:

[0244] In accordance with the above-described method for remote operation of services applied to a first terminal, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0245] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0246] Based on the access command submitted by the user for the remote operation entry point, an access request is generated and sent to the server;

[0247] Obtain the service operation instructions submitted by the accessing user based on the remote operation permissions of the target service;

[0248] Send the service operation command to the server;

[0249] The remote operation permission is activated after the identity of the associated user who has established a trusted relationship with the accessing user is verified and the verification is successful.

[0250] It should be noted that the embodiments concerning storage media in this specification and the embodiments concerning remote operation methods for services in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

[0251] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0252] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0253] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0254] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0255] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0256] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0257] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0258] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0259] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0260] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0261] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0262] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0263] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0264] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0265] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0266] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A method for remotely operating a service, applied to a server, comprising: Receive access requests for remote operation entry points sent by the user's first terminal; The access request is sent after the associated user invites the accessing user to perform remote operation on the target service of the associated user. The system invokes the second terminal of the associated user who has established a trusted relationship with the accessing user to verify the identity of the associated user. After verification, the remote operation permission for the target service is activated for the accessing user, and the service operation instruction submitted by the accessing user based on the remote operation permission is received from the first terminal. The service operation instruction is verified by calling a third-party verification interface, and the execution result of the service operation instruction is returned to the second terminal.

2. The service remote operation method according to claim 1, wherein the trusted relationship is established in the following manner: Based on the request to establish a trusted relationship between the accessing user and the associated user, the identity information and relationship credentials collected and uploaded by the first terminal are obtained; Based on the identity information and the relationship certificate, a confirmation reminder for the establishment request is generated and sent to the second terminal; The system receives a confirmation request submitted by the second terminal after the confirmation reminder is triggered, and calls the third-party verification interface to verify the user association relationship between the accessing user and the associated user. If the verification is successful, a trusted relationship is established between the accessing user and the associated user and stored.

3. The service remote operation method according to claim 2, after the trusted relationship is established, granting the accessing user remote operation permission for the services within the main application of the associated user; in, The main application includes the application that runs the target service.

4. The remote operation method for services according to claim 1, wherein the main application installed on the first terminal and the main application installed on the second terminal are configured with remote operation entry points; The target service includes at least one of the following: main application service, sub-application service within the main application.

5. The remote service operation method according to claim 1, wherein calling the second terminal of the associated user who has established a trusted relationship with the accessing user to verify the identity of the associated user includes: Find a list of associated users of the candidate associated users who have established a trusted relationship with the accessing user, and return it to the first terminal; Obtain the associated users selected by the accessing user from the associated user list who are remotely operating the target service, as submitted by the first terminal. The second terminal is invoked to verify the identity of the associated user.

6. The remote operation method for services according to claim 5, wherein the step of invoking the second terminal to verify the identity of the associated user includes: Determine additional information for the identity verification; Based on the additional information, the target service, and / or the trusted relationship between the accessing user and the associated user, an identity verification reminder is generated and sent to the second terminal; If the identity verification reminder is triggered, the biometric information collected and uploaded by the second terminal through the information collection interface configured on the identity verification page is obtained; Determine whether the biometric information matches the biometric information of the associated user; If a match is found, the identity verification is confirmed to be successful.

7. The remote operation method for services according to claim 1 further includes: Receive a request from the first terminal or the second terminal to terminate the trusted relationship; Based on the termination request, the trusted relationship is terminated, and remote operation permissions for services within the main application running the target service are disabled.

8. The remote service operation method according to claim 1, wherein the step of returning the execution result of the service operation instruction to the second terminal includes: The service operation instructions are executed and the execution results are returned to the second terminal. or, The service data of the target service obtained by the third-party server after executing the service operation instruction is acquired and synchronized to the second terminal.

9. The remote service operation method according to claim 1, wherein verifying the service operation instruction includes: Determine the instruction category of the service operation instruction; The service operation instructions are verified according to the corresponding verification strategy based on the instruction category.

10. The service remote operation method according to claim 9, wherein verifying the service operation instruction based on the instruction category and the corresponding verification strategy includes: If the instruction category is a first type of operation instruction, then the instruction parameters carried by the service operation instruction are validated. If the instruction category is the second type of operation instruction, then the matching of the service operation instruction with the preset rules is verified.

11. A method for remotely operating a service, applied to a first terminal accessing a user, comprising: An access request is generated based on the access command submitted by the user for the remote operation entry point and sent to the server; The access request is sent after the associated user invites the accessing user to perform remote operation on the target service of the associated user. Obtain the service operation instructions submitted by the accessing user based on the remote operation permissions of the target service; Send the service operation command to the server; The server verifies the service operation instruction and obtains the instruction execution result, then returns it to the second terminal of the associated user. The remote operation permission is activated after the second terminal of the associated user, which has established a trusted relationship with the accessing user, verifies the identity of the associated user and the verification is successful.

12. The service remote operation method according to claim 11, wherein the trusted relationship is established in the following manner: Based on the request to establish a trusted relationship between the accessing user and the associated user, the identity information and relationship credentials collected and uploaded by the first terminal are obtained; Based on the identity information and the relationship certificate, a confirmation reminder for the establishment request is generated and sent to the second terminal of the associated user; The system receives a confirmation request submitted by the second terminal after the confirmation reminder is triggered, and calls a third-party verification interface to verify the user association relationship between the accessing user and the associated user. If the verification is successful, a trusted relationship is established between the accessing user and the associated user and stored.

13. The service remote operation method according to claim 12, after the trusted relationship is established, granting the accessing user remote operation permission for the services within the main application of the associated user; in, The main application includes the application that runs the target service.

14. The service remote operation method according to claim 11, wherein the main application installed on the first terminal and the main application installed on the second terminal of the associated user are configured with remote operation entry points; The target service includes at least one of the following: main application service, sub-application service within the main application.

15. The service remote operation method according to claim 11, after the step of generating an access request and sending it to the server based on the access instruction submitted by the accessing user for the remote operation entry point, and before the step of obtaining the service operation instruction submitted by the accessing user based on the remote operation permission of the target service, further includes: Receive the list of associated users returned by the server that are candidate associated users who have established a trusted relationship with the accessing user; The server retrieves the associated users selected by the accessing user from the associated user list who are remotely operating the target service and submits them to the server for identity verification of the associated users.

16. The remote operation method for services according to claim 15, wherein verifying the identity of the associated user includes: Determine additional information for the identity verification; Based on the additional information, the target service, and / or the trusted relationship between the accessing user and the associated user, an identity verification reminder is generated and sent to the associated user's second terminal. If the identity verification reminder is triggered, the biometric information collected and uploaded by the second terminal through the information collection interface configured on the identity verification page is obtained; Determine whether the biometric information matches the biometric information of the associated user; If a match is found, the identity verification is confirmed to be successful.

17. A remote operation device for services, operating on a server, comprising: The access request receiving module is configured to receive access requests for remote operation entry points sent by the first terminal of the accessing user; The access request is sent after the associated user invites the accessing user to perform remote operation on the target service of the associated user. The identity verification module is configured to invoke the second terminal of the associated user who has established a trusted relationship with the accessing user to verify the identity of the associated user; The operation instruction receiving module is configured to activate the remote operation permission of the target service to the accessing user after the verification is passed, and to receive the service operation instruction submitted by the accessing user based on the remote operation permission sent by the first terminal. The operation instruction verification module is configured to call a third-party verification interface to verify the service operation instruction, and obtain the instruction execution result of the service operation instruction and return it to the second terminal.

18. A service remote operation device, operating on a first terminal of an accessing user, comprising: The access request sending module is configured to generate an access request and send it to the server based on the access instruction submitted by the accessing user for the remote operation entry point; The access request is sent after the associated user invites the accessing user to perform remote operation on the target service of the associated user. The operation instruction acquisition module is configured to acquire service operation instructions submitted by the accessing user based on the remote operation permissions of the target service. The remote operation permission is activated after the second terminal of the associated user, who has established a trusted relationship with the accessing user, verifies the identity of the associated user and the verification is successful. The operation instruction sending module is configured to send the service operation instruction to the server; The server verifies the service operation instruction and obtains the instruction execution result, returning it to the second terminal of the associated user.

19. A service remote operation device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Receives an access request for a remote operation entry sent by the first terminal of the accessing user; the access request is sent after the associated user invites the accessing user to perform remote operation on the target service of the associated user; The system invokes the second terminal of the associated user who has established a trusted relationship with the accessing user to verify the identity of the associated user. After verification, the remote operation permission for the target service is activated for the accessing user, and the service operation instruction submitted by the accessing user based on the remote operation permission is received from the first terminal. The service operation instruction is verified by calling a third-party verification interface, and the execution result of the service operation instruction is returned to the second terminal.

20. A service remote operation device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: The access request is generated by the user's first terminal based on the access instruction submitted by the user for the remote operation entry and sent to the server; the access request is sent after the associated user invites the user to perform remote operation on the associated user's target service. Obtain the service operation instructions submitted by the accessing user based on the remote operation permissions of the target service; Send the service operation command to the server; The server verifies the service operation instruction and obtains the instruction execution result, then returns it to the second terminal of the associated user. The remote operation permission is activated after the second terminal of the associated user, which has established a trusted relationship with the accessing user, verifies the identity of the associated user and the verification is successful.

21. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Receives an access request for a remote operation entry sent by the first terminal of the accessing user; the access request is sent after the associated user invites the accessing user to perform remote operation on the target service of the associated user; The system invokes the second terminal of the associated user who has established a trusted relationship with the accessing user to verify the identity of the associated user. After verification, the remote operation permission for the target service is activated for the accessing user, and the service operation instruction submitted by the accessing user based on the remote operation permission is received from the first terminal. The service operation instruction is verified by calling a third-party verification interface, and the execution result of the service operation instruction is returned to the second terminal.

22. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: The access request is generated by the user's first terminal based on the access instruction submitted by the user for the remote operation entry and sent to the server; the access request is sent after the associated user invites the user to perform remote operation on the associated user's target service. Obtain the service operation instructions submitted by the accessing user based on the remote operation permissions of the target service; Send the service operation command to the server; The server verifies the service operation instruction and obtains the instruction execution result, then returns it to the second terminal of the associated user. The remote operation permission is activated after the second terminal of the associated user, which has established a trusted relationship with the accessing user, verifies the identity of the associated user and the verification is successful.

Images