Remote service invocation method, device, system, storage medium

Abstract

Embodiments of the present application provide a remote service calling method, device and system based on a calling device or a target device, the remote service calling method based on the calling device comprising: sending a remote service calling request to the target device, the remote service calling request comprising a calling device ID, a calling application ID and target service information; receiving permission information calling instructions sent by the target device, the permission information calling instructions comprising the calling application ID and the target service information; and sending corresponding permission information to the target device according to the permission information calling instructions, the permission information being used to reflect whether the calling application has calling permission for the target service. According to the scheme, only one authorization needs to be performed at the calling device end, and corresponding permission information is sent to the target device for authentication, and remote service calling can be implemented after the target device is authenticated, thereby avoiding user authorization operations on multiple devices multiple times, simplifying the authorization operation process, and thus improving user experience.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of permission verification, and particularly relates to a remote service calling method, device, system and storage medium. BACKGROUND

[0002] With the continuous development of intelligent terminals, users have more and more intelligent electronic devices, such as smart phones, smart televisions and smart watches. When a user uses a certain intelligent electronic device, the user wants to call a certain target service of another electronic device, for example, when a smart phone is used for a WeChat video call, the smart phone calls the camera of a smart television to take a picture. However, the android system has a complete application permission management mechanism, for example, when an application calls a camera, a recording device or other system services or devices related to user privacy, the user needs to authorize. However, the existing android application permission management mechanism has the following defects when distributed cross-device calling is performed.

[0003] The user needs to authorize at the calling end and the called end, the authorization action is cumbersome, and the user experience is greatly reduced. SUMMARY

[0004] The remote service calling method, device, system and storage medium provided by the embodiments of the present application can only need to authorize once at the calling device end and send corresponding permission information to the target device for authentication during the process of sending a remote service calling request to the target device, and the remote service calling can be realized after the target device authentication is passed, thereby avoiding the user authorization operation on multiple devices multiple times, simplifying the authorization operation process, and improving the user experience.

[0005] The embodiments of the present application provide a remote service calling method based on a calling device, which comprises the following steps.

[0006] Sending a remote service calling request to a target device, wherein the remote service calling request comprises a calling device ID, a calling application ID and target service information;

[0007] Receiving a permission information calling instruction sent by the target device, wherein the permission information calling instruction comprises the calling application ID and the target service information;

[0008] According to the permission information calling instruction, corresponding permission information is sent to the target device, and the permission information is used to reflect whether the calling application has the calling permission of the target service.

[0009] Further, before the step of sending a remote service calling request to a target device, the method further comprises the following steps.

[0010] In response to the remote service invocation request, it is determined whether the invocation application is first requested to invoke the target service, and if so, a permission determination process is performed, and if not, the process of sending the remote service invocation request to the target device is performed;

[0011] The permission determination process includes:

[0012] The permission information is determined based on the user and saved locally.

[0013] Further, the process of determining the permission information based on the user and saving the permission information locally includes:

[0014] An authorization determination interface is generated to facilitate the user to select whether the invocation application has the invocation permission of the target service based on the authorization determination interface.

[0015] The embodiment of the application also provides a remote service invocation method based on a target device, including:

[0016] A remote service invocation request sent by an invocation device is received, and the remote service invocation request includes an invocation device ID, an invocation application ID and target service information;

[0017] A permission information invocation instruction is sent to the invocation device, and the permission information invocation instruction includes the invocation application ID and the target service information;

[0018] Permission information sent by the invocation device is received, and the permission information is used to reflect whether the invocation application has the invocation permission of the target service;

[0019] Based on the permission information, it is determined whether the invocation application has the invocation permission of the target service, and if so, the invocation of the target service by the invocation application in the invocation device is performed.

[0020] Further, before the permission information invocation instruction is sent to the invocation device, it further includes:

[0021] A distributed user ID is allocated as an invocation subject ID according to the invocation device ID and the invocation application ID, and the distributed user ID is used to identify the device and the application;

[0022] The type of the invocation subject ID is determined, if the type of the invocation subject ID is a distributed user ID, the process of sending the permission information invocation instruction to the invocation device is performed, and if the type of the invocation subject ID is a local ID, a local invocation permission check is performed.

[0023] Further, in the process of determining whether the calling application has the calling permission of the target service based on the permission information, if not, the calling of the target service by the calling application in the calling device is rejected, and calling failure information is returned to the calling device.

[0024] The embodiment of the application further provides a calling device, which comprises a processor and a memory, wherein the memory is used to store at least one instruction, and the instruction is loaded and executed by the processor to implement the remote service calling method based on the calling device.

[0025] The embodiment of the application further provides a target device, which comprises a processor and a memory, wherein the memory is used to store at least one instruction, and the instruction is loaded and executed by the processor to implement the remote service calling method based on the target device.

[0026] The embodiment of the application further provides a system, which comprises at least one calling device and at least one target device.

[0027] The embodiment of the application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the remote service calling method based on the calling device or the remote service calling method based on the target device.

[0028] Through the above technical solution, the calling device sends a remote service calling request to the target device, and the remote service calling request comprises a calling device ID, a calling application ID and target service information. The target device can identify the calling device, the calling application and the target service through the received remote service calling request. In the process of sending the remote service calling request by the calling device to the target device, only one authorization is needed on the calling device side, and the corresponding permission information is sent to the target device for authentication, and the remote service calling can be realized after the authentication of the target device is passed, thereby avoiding the user's multiple authorization operations on multiple devices, simplifying the authorization operation process, and only one authorization is needed on the calling device side. The target device requests the corresponding permission information of the calling subject on the calling device side for authentication, and the user only needs to select on the authorization determination interface displayed on the calling device when the calling subject first requests to call the target service, so that the permission verification method in the application can not only identify the calling subject through the calling subject ID in the cross-device calling, but also provide a distributed authentication interface to authenticate the cross-device calling subject, thereby improving the user experience. BRIEF DESCRIPTION OF DRAWINGS

[0029] In order to make the technical solutions in the embodiments of the present application or the prior art clearer, the accompanying drawings needed in the embodiments or prior art description will be briefly introduced. Obviously, the accompanying drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 A remote service calling method flowchart based on a calling device provided by the embodiment of the present application is shown in the figure.

[0031] Figure 2 A transfer call service authorization confirmation diagram provided by the embodiment of the present application is shown in the figure.

[0032] Figure 3 A remote service calling method flowchart based on a target device provided by the embodiment of the present application is shown in the figure.

[0033] Figure 4 A transfer call service diagram provided by the smart TV provided by the embodiment of the present application is shown in the figure.

[0034] Figure 5 A connection interaction diagram of the calling device and the target device provided by the embodiment of the present application is shown in the figure.

[0035] Figure 6 An interaction diagram of the calling device and the target device provided by the embodiment one of the present application is shown in the figure.

[0036] Figure 7 An interaction diagram of the calling device and the target device provided by the embodiment two of the present application is shown in the figure.

[0037] Figure 8 An interaction diagram of the calling device and the target device provided by the embodiment three of the present application is shown in the figure.

[0038] Figure 9 A structure diagram of the calling device provided by the embodiment of the present application is shown in the figure.

[0039] Figure 10 A structure diagram of the target device provided by the embodiment of the present application is shown in the figure.

[0040] Figure 11 A structure diagram of the distributed system provided by the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0041] In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0042] The following briefly describes the cross-device authentication process in the prior art:

[0043] When distributed cross-device calling is performed, a proxy service is added on the called device, for example, a device A calls a certain service on a device B, and a proxy service is added on the device B. The device B checks the permission of the proxy service, thereby indirectly authenticating the application initiating the cross-device calling.

[0044] According to the cross-device authentication process in the prior art, it can be determined that:

[0045] When cross-device calling is performed in the prior art, the target device B provides a proxy service for the calling device A, and the target device B authenticates the calling device A. Here, the calling entity that the target device B can recognize for target service calling is the calling device A, but the calling subject cannot be recognized as which calling application in the calling device.

[0046] According to the cross-device authentication process in the prior art, it can also be determined that:

[0047] When cross-device calling is performed in the prior art, in the case that the calling device A requests to call a certain service of the target device B, the calling device A needs to be authorized locally once. When the target device receives the target service calling request sent by the calling device A, the target device provides a proxy service for the calling device A, so that the user authorizes the calling device A, and provides the corresponding target service in the case that the target device B authenticates the calling device A.

[0048] In order to avoid the above defects in the prior art, the embodiments of the present application provide the following technical solutions to overcome the above defects in the prior art, as follows:

[0049] Figure 1 A remote service calling method based on a calling device provided by the embodiments of the present application is shown in FIG. 1, which includes the following steps. Figure 1

[0050] Step 101: sending a remote service calling request to a target device;

[0051] Step 102: receiving a permission information calling instruction sent by the target device; ​

[0052] Step 103: according to the permission information, sending the corresponding permission information to the target device according to the instruction.

[0053] Regarding step 101

[0054] In a plurality of running devices (such as devices running the Android system), when a user wants to call a target service of another device through an application in a device, a remote service call request can be sent to the device; wherein the calling device can be regarded as a calling device, the application sending the remote service call request can be regarded as a calling application, the called device can be regarded as a target device, and the target service can be a system service or a third-party developed service that can be remotely called. The remote service call request sent by the calling device to the target device includes a calling device ID, a calling application ID, and target service information. For example, when a user uses the "Changlian" application in a Huawei smart phone to make a video call with a friend at home, the user selects the "call transfer service" on the smart TV at home to realize the transfer of pictures and sound; that is, the Huawei Changlian APP in the smart phone can send a remote service call request to the smart TV to call the "call transfer service" on the smart TV, and the remote service call request includes the smart phone ID, the Changlian ID, and information for identifying the "call transfer service".

[0055] It should be noted that in the case of the first call of the target service by the calling application, the user needs to authorize the calling of the target service by the calling application. Therefore, before sending the remote service call request to the target device, in response to the remote service call request, it is determined whether it is the first request of the calling application to call the target service, and if so, the permission determination process is performed. The permission determination process includes generating an authorization determination interface on the interface of the calling application of the calling device, so as to enable the user to select whether the calling application has the calling permission of the target service based on the authorization determination interface.

[0056] In an embodiment, it can be further limited to the case where the calling application calls the target service for the first time and the required permission of the called service is of a dangerous level (such as calling a camera, microphone device service, etc.). The user needs to authorize the calling of the target service by the calling application. Similarly, before sending the remote service call request to the target device, in response to the remote service call request, it is determined whether it is the first request of the calling application to call the target service with a dangerous level of permission, and if so, the permission determination process is performed. The permission determination process includes generating an authorization determination interface on the interface of the calling application of the calling device, so as to enable the user to select whether the calling application has the calling permission of the target service based on the authorization determination interface.

[0057] For example, as Figure 2As shown, in the case that the "Smooth Connection" APP of the calling device (smartphone) first requests to call the "call transfer service" of the target device (smart TV), an authorization determination interface U2 is generated on the "Smooth Connection" APP interface U1, and the user is prompted to confirm the authorization on the authorization determination interface U2, such as "Do you allow the Smooth Connection to call the call transfer service of the smart TV" to facilitate the user to authorize the "call transfer service" request of the "Smooth Connection" APP. After the user clicks the "Always allow" button on the authorization determination interface, the authorization operation is completed, that is, the "Smooth Connection" APP on the smartphone has the calling permission of the "call transfer service" of the smart TV, in other words, the "Smooth Connection" APP on the smartphone has the permission to access the camera and microphone of the smart TV. If the user clicks the "Prohibit" button on the authorization determination interface, the authorization is refused, that is, the "Smooth Connection" APP on the smartphone does not have the calling permission of the "call transfer service" of the smart TV.

[0058] Regarding step 102

[0059] After the target device receives the remote service calling request sent by the calling device, in order to confirm whether the calling application in the calling device that applies for the remote service calling request has the corresponding calling permission, the target device will apply for the calling permission information from the calling device. The calling device receives the permission information calling instruction sent by the target device, and the permission information calling instruction includes the calling application ID and the target service information. For example, the "Smooth Connection" APP on the smartphone calls the "call transfer service" of the smart TV, and the smart TV will apply for the permission information of whether the "Smooth Connection" APP on the smartphone can access the camera and microphone of the smart TV. The smartphone receives the calling instruction of the permission information of whether the "Smooth Connection" APP can access the camera and microphone of the smart TV sent by the smart TV, and the calling instruction of the permission information further includes the application ID (the ID of the "Smooth Connection" APP) and the target service information (the "call transfer service" of the smart TV).

[0060] Regarding step 103

[0061] The calling device sends the corresponding permission information to the target device according to the permission information calling instruction after receiving the permission information calling instruction sent by the target device. Specifically, the calling device identifies the corresponding calling application according to the calling application ID in the permission information calling instruction and determines the permission type according to the target service information in the permission information calling instruction after receiving the permission information calling instruction and the target service information sent by the target device. Further, the calling device queries the permission information of the calling application about the permission type in the locally stored permission data, wherein the permission information is used to reflect whether the calling application has the calling permission of the target service. The calling device sends the queried permission information to the target device. For example, the smartphone receives the permission information calling instruction about whether the "Changlian" APP can access the camera and microphone of the smart TV sent by the smart TV, the permission information calling instruction further includes the application ID (the ID of the "Changlian" APP) and the target service information (the "transfer call service" of the smart TV), the calling application is identified as the "Changlian" APP according to the application ID, the permission type includes the smart TV camera calling permission and the smart TV microphone calling permission according to the target service information, further, the calling device queries the permission information of the "Changlian" APP about the smart TV camera calling permission and the smart TV microphone calling permission in the locally stored permission data, and sends the queried permission information to the smart TV.

[0062] Figure 3 The method for remotely calling the service of the target device provided by the embodiment of the application is shown in the flowchart of the method for remotely calling the service of the target device based on the target device as shown in the figure, and the method comprises the following steps. Figure 3

[0063] Step 201: receiving the remote service calling request sent by the calling device;

[0064] Step 202: sending the permission information calling instruction to the calling device;

[0065] Step 203: receiving the permission information sent by the calling device;

[0066] Step 204: determining whether the calling application has the calling permission of the target service based on the permission information, and if yes, performing the calling of the target service by the calling application in the calling device.

[0067] Regarding step 201

[0068] ​The target device receives a remote service call request sent by the calling device, which includes the calling device ID, the calling application ID and target service information. For example, when a user uses a Huawei smartphone to make a video call with a friend using the "Changlian" application at home, the user selects the "call transfer service" on the smart TV at home to realize the transfer of pictures and sound; that is, the Huawei Changlian APP in the smartphone sends a remote service call request to the smart TV to call the "call transfer service" on the smart TV, which includes the smart phone ID, the Changlian ID and the information for identifying the "call transfer service".

[0069] After the target device receives the remote service call request sent by the calling device, a distributed user ID (DUID) is assigned as the calling subject ID according to the device ID (device ID) and the calling application ID (User ID, UID) in the remote service call request. The target service call is initiated according to the remote service call request, and the distributed user ID (DUID) is included in the initiated target service call to indicate the calling subject of the call.

[0070] Further, after the target service end receives the target service call, it is necessary to determine whether the calling subject has the calling permission of the target service, wherein the type of the calling subject ID needs to be determined first. If the type of the calling subject ID is a distributed user ID (DUID), it is determined that the target service call is a cross-device remote service call, and a permission information calling instruction needs to be sent to the calling device to determine whether the calling subject has the calling permission of the target service. If the type of the calling subject ID is a local ID, it is determined that the target call is a local call, and the local calling permission is checked.

[0071] Since the calling subject ID type of the target service call request received by the target service end of the target device during the ongoing cross-device remote service call is a distributed user ID (DUID), a permission information calling instruction needs to be sent to the calling device, that is, step 202 is entered.

[0072] Regarding step 202

[0073] As described in step 201, to determine whether the calling subject has the calling right of the target service of the target device, the right information calling instruction needs to be sent to the calling device, and specifically, the right information calling instruction needs to specify the calling subject and the target service. However, in the target device, the calling subject ID is a distributed user ID (DUID), and the calling device cannot identify which calling application in the calling device corresponds to the distributed user ID. Therefore, when the target device sends the right information calling instruction to the calling device, the calling subject ID recognizable by the calling device needs to be included. Since the distributed user ID (DUID) is allocated by the device ID (device ID) and the calling application ID (UID) of the calling device, and the calling action of the right information calling instruction is the interaction between the target device and the calling device, the device ID does not need to be emphasized, and only the calling application needs to be specified. Therefore, the calling application ID can be included in the right information calling instruction. Further, the calling device also needs to be informed of the target service corresponding to the right information calling. Therefore, the target service information also needs to be included in the right information calling instruction. In summary, the target device sends the right information calling instruction to the calling device, and the right information calling instruction includes the calling application ID and the target service information.

[0074] Regarding steps 203-204

[0075] After the calling device receives the right information calling instruction sent by the target device, the corresponding right information is queried and sent to the target device. The target device receives the right information sent by the calling device, and authenticates the right information to determine whether the calling application (calling subject) in the calling device has the calling right of the target service in the target device. After authentication, if the calling application has the calling right of the target service, the calling of the target service in the target device by the calling application in the calling device is performed. For example, if the authentication of the "smooth connection" application in the smart phone by the smart TV is successful, the "call transfer service" called by the "smooth connection" application is successful, as shown in the following figure. Figure 4 Further, the calling success result can be fed back to the calling device. After authentication, if the calling application does not have the calling right of the target service, the calling of the target service in the target device by the calling application in the calling device is rejected, and the calling failure result is fed back to the calling device.

[0076] Compared with the authentication manner of cross-device calling in the prior art, through the cross-device calling and authentication manner of steps 101-103 and steps 201-204, when the calling application (APP) in the calling device requests a target service of the target device, the remote service calling request is sent to the target device, and the remote service calling request includes the calling device ID, the calling application ID and the target service information. The target device can determine the calling subject through the calling device ID and the calling application ID in the remote service calling request, and further assign a distributed user ID as the calling subject ID according to the calling device ID and the calling application ID.

[0077] When the target device authenticates the calling subject, the permission information of the calling subject about calling the target service stored in the calling device is called, and the received permission information is authenticated, without the need for the user to perform an authorization operation on the target device again.

[0078] Figure 5 An interaction schematic diagram of the calling device and the target device provided by the embodiment of the application is shown in FIG. 1. Figure 5 As shown in FIG. 1, the permission verification process of cross-device remote service calling is completely described in combination with the interaction between the calling device and the target device, wherein the device D1 and the device D2 are in a distributed scenario, and the device D1 and the device D2 are both devices running an Android system, the device D1 is a calling device, the device D2 is a target device, the APP D10 on the device D1 calls a target service D20 on the device D2, wherein the target service D20 can be a system service or a service developed by a third party and available for remote calling.

[0079] As shown in FIG. 2, the distributed scenario in which the device D1 and the device D2 are located provides a distributed execution framework service (DEFS) and a distributed permission management service (DPMS), the DEFS is used to provide a cross-device communication and calling agent, and provide an interface for the device D1 to call the target service of the device D2, and the DPMS provides a distributed permission verification (authentication) interface for an Android native permission management service (PMS) in each device. Figure 5 In combination with the remote service calling method based on the calling device and the target device and the authentication manner of cross-device calling in the prior art, the comparison is as follows:

[0080]

[0081] ​Firstly, in the prior art, the different applications of the calling subject cannot be distinguished in the cross-device call processing, that is, the calling application cannot be further distinguished on the basis of the calling device, so that the authorization cannot be performed for different applications in the same calling device.

[0082] However, in the technical solution claimed in the present application, when the calling application (APP) D10 in the calling device requests the target service D20 of the target device, the calling device and the target device can communicate with each other through the DEFS provided by the distributed scenario in which the calling device and the target device are located. Specifically, the calling device sends a remote service call request to the DEFS (D22) of the target device through the DEFS (D12) of the calling device, and the remote service call request includes the calling device ID, the calling application ID and the target service information. The target device can determine the calling subject through the calling device ID and the calling application ID in the remote service call request, and can further assign a distributed user ID as the calling subject ID according to the calling device ID and the calling application ID.

[0083] Secondly, in the prior art, two authorization confirmations are required in the cross-device call processing, that is, when the calling application in the calling device requests the target service of the target device, the user needs to perform an authorization confirmation on the calling device, and the permission information after the authorization confirmation is stored locally on the calling device. After the target device receives the target service call request of the calling device, the target device performs an authorization confirmation again, and the permission information after the authorization confirmation is stored locally on the target device. Further, the target service call can be implemented only after the authorization is completed on both the calling device and the target device, and the process is relatively complicated. Moreover, in the above permission verification process of the prior art, there is an illegal calling infringement. Specifically, since the calling device and the target device each store the permission information about a target service call request, if the permission is cancelled on the calling device, the target device does not change the permission information state, and when the calling device sends the same target service call request to the target device, the target device is still in the authorized state, and at this time, the illegal calling infringement occurs.

[0084] However, in the technical solution claimed in the present application, the user authorization confirmation is only performed at the calling device end, and the authorized permission information is stored at the calling device end, and when the target device needs to be authenticated, the corresponding permission information stored in the calling device is requested to perform authentication. Among them, the permission information of the calling device is used as the only standard to avoid the problem that the permission information about the same target service call in the calling device and the target device is different. When the target device authenticates the calling subject, the permission information of the calling subject about the calling target service stored in the calling device is called, and the received permission information is authenticated, without the need for the user to perform an authorization operation again at the target device end.

[0085] Specifically, the following several embodiments respectively illustrate the process of APP (D10) on device 1 calling the target service on device 2 across devices under different authorization conditions.

[0086] Embodiment one

[0087] The authorization state type corresponding to this embodiment: the "smooth connection" APP (D10) in the smart phone calls the "call transfer service" of the smart TV for the first time, which is used for authorization of the calling operation.

[0088] Figure 6 The interaction schematic diagram of the calling device and the target device provided by the embodiment one of the present application is shown as follows: Figure 6 As shown in the figure, the cross-device calling process in the embodiment one is realized through a plurality of steps shown in the figure, and specifically, the embodiment formed by the plurality of steps is as follows:

[0089] Step S001: the user opens the "smooth connection" APP (D10) on the smart phone, and selects to use the "call transfer service" of the smart TV.

[0090] Step S002: the "smooth connection" APP (D10) calls the PMS (D11) interface of the smart phone to request the permissions required for calling the "call transfer service" of the smart TV.

[0091] Step S003: the PMS (D11) determines whether the request information is the first request of the "smooth connection" APP (D10) to call the "call transfer service" of the smart TV in response to the request information of the "smooth connection" APP (D10) to call the "call transfer service" of the smart TV, and the PMS (D11) generates an authorization determination interface U2 on the interface U1 of the "smooth connection" APP (D10) of the smart phone in the case that the request information is the first request of the "smooth connection" APP (D10) to call the "call transfer service" and the permission level required for calling the "call transfer service" (the calling permissions of the two devices are both dangerous level) is dangerous level, as shown in 2.

[0092] Step S004: After the user clicks the "Always Allow" button on the authorization confirmation interface, the authorization operation is completed, the PMS (D11) obtains the operation result (authorization result) of the user on the authorization confirmation interface U2, and stores the authorization result as the permission information of the "Transfer Call Service" requested by the "Chuanglian" APP (D10) to call the smart TV in the local corresponding database.

[0093] Step S005: In the case where "Chuanglian" obtains the permission information of the "Transfer Call Service" of the smart TV through the PMS (D11) interface, "Chuanglian" further sends the smart phone ID (device ID), "Chuanglian" ID (APP ID) and information for identifying the "Transfer Call Service" (target service) (remote service call request) to DEFS (D12) to call the DEFS (D12) interface of the smart phone to communicate with the smart TV.

[0094] Step S006: DEFS (D12) sends the remote service call request to the smart TV, wherein the remote service call request sent to the smart TV includes the smart phone ID (device ID), "Chuanglian" ID (APP ID) and information for identifying the "Transfer Call Service" (target service).

[0095] Step S007: After the DEFS (D22) of the smart TV receives the remote service call request sent by the smart phone, a distributed user ID is allocated in the resource pool of the reserved distributed user ID (DUID) of the smart TV according to the smart phone ID and "Chuanglian" ID in the remote service call request.

[0096] Step S008: The DEFS (D22) of the smart TV sends the allocated distributed user ID as the calling subject ID in this cross-device call operation, and sends the target service call request of the calling subject to the target service (D20) of the smart TV, wherein the target service call request contains the calling subject ID, and at this time the calling subject ID is the DUID allocated according to the smart phone ID and "Chuanglian" ID.

[0097] Step S009: After receiving the target service call request, the target service calls the android PMS (D21) native authentication interface of the smart TV to perform permission verification according to the DUID, so as to determine whether the "Chuanglian" APP (D10) has the calling permission of the "Transfer Call Service" of the smart TV.

[0098] Step S010: The PMS (D21) of the smart TV identifies that the calling subject ID type in the target service calling request is a DUID, and determines that the target service calling request of the calling subject is a cross-device remote service calling request.

[0099] Step S011: In the case where it is determined that the target service calling request of the calling subject is a cross-device remote service calling request, the interface of the DPMS (D23) of the smart TV is directly called to request authentication.

[0100] Step S012: After the DPMS (D23) of the smart TV receives the authentication request of whether the calling subject has the calling right of the target service, the DPMS (D13) of the smart phone is requested to call the DEFS (D12) of the smart phone to request the "ChangLian" right information of calling the "call transfer service", specifically, the DEFS (D23) of the smart TV communicates with the smart phone by calling the DEFS (D12) of the smart phone, and sends the calling instruction of the right information to the DEFS (D12) of the smart phone, wherein the right information calling instruction sent to the DEFS (D12) of the smart phone includes the "ChangLian" ID and the information for identifying the "call transfer service".

[0101] Step S013: The DEFS (D12) of the smart phone sends the received right information calling instruction to the DPMS (D13) of the smart phone, and the DPMS (D13) of the smart phone requests the PMS (D11) of the smart phone to request the right information of the "ChangLian" calling the "call transfer service" of the smart TV according to the right information calling instruction.

[0102] Step S014: The PMS (D11) of the smart phone feeds back the queried right information of the "ChangLian" calling the "call transfer service" of the smart TV to the DPMS (D13) of the smart phone.

[0103] Step S015: The DPMS (D13) of the smart phone further sends the right information of the "ChangLian" calling the "call transfer service" of the smart TV to the DEFS (D22) of the smart TV through the DEFS (D12) of the smart phone, and the DEFS (D22) of the smart TV further feeds back the right information of the "ChangLian" calling the "call transfer service" of the smart TV to the DPMS (D23) of the smart TV, so as to realize the synchronization of the calling right of the "ChangLian" APP between the smart phone and the smart TV.

[0104] Step S016: The DPMS (D23) of the smart TV authenticates the permission information of the "Smooth Link" calling the "call transfer service" of the smart TV to determine whether the "Smooth Link" has the calling permission of calling the "call transfer service" of the smart TV. Since the user has authorized before, the authentication result is that the "Smooth Link" has the calling permission of calling the "call transfer service" of the smart TV, and it is determined that the authentication is passed, and the authentication result is further sent to the PMS (D21) of the smart TV.

[0105] Step S017: In the case where the authentication of the "Smooth Link" calling the "call transfer service" of the smart TV by the DPMS (D23) is passed, the PMS of the smart TV further feeds back the authentication result to the target service (D20) of the smart TV.

[0106] Step S018: The target service (D20) executes the call transfer service after obtaining the information that the authentication is passed, and the calling is successful this time.

[0107] Step S019: The target service (D20) sends the calling success result to the DEFS (D22) of the smart TV.

[0108] Step S020: Further, the DEFS (D22) of the smart TV sends the calling success result to the DEFS (D12) of the smart phone.

[0109] Step S021: The DEFS (D12) of the smart phone feeds back the calling success result to the calling application "Smooth Link" (D10).

[0110] Embodiment Two

[0111] The corresponding authorized state type of this embodiment: the "Smooth Link" APP (D10) in the smart phone is not calling the "call transfer service" of the smart TV for the first time, and the user's previous authorization has not been cancelled.

[0112] Figure 7 The interaction schematic diagram of the calling device and the target device provided by the embodiment two of the application is shown in the figure. Figure 7 As shown in the figure, the cross-device calling flow in the embodiment two is implemented through a plurality of steps shown in the figure, and the embodiment formed by the plurality of steps is as follows:

[0113] Step S031: The user opens the "Smooth Link" APP (D10) on the smart phone, and selects to use the "call transfer service" of the smart TV.

[0114] Step S032: The "Smooth Link" APP (D10) calls the PMS (D11) interface of the smart phone to request the permission required for calling the "call transfer service" of the smart TV.

[0115] Step S033: PMS (D11) determines whether the request information is the first request of "Smooth Union" APP (D10) to call "Transfer Call Service" on the smart TV in response to the request information of "Transfer Call Service" called by "Smooth Union" APP (D10). PMS (D11) does not need to request user authorization in the case of determining that the request information is not the first request of "Smooth Union" APP (D10) and calling "Transfer Call Service".

[0116] Step S034: "Smooth Union" APP directly sends smart phone ID (device ID), "Smooth Union" ID (APP ID) and information for identifying "Transfer Call Service" (target service) to DEFS (D12).

[0117] Step S035: DEFS (D12) of the smart phone sends a remote service call request to the smart TV, wherein the remote service call request sent to the smart TV includes smart phone ID (device ID), "Smooth Union" ID (APP ID) and information for identifying "Transfer Call Service" (target service).

[0118] Step S036: DEFS (D22) of the smart TV receives the remote service call request sent by the smart phone, allocates a distributed user ID in the resource pool of reserved distributed user ID (DUID) of the smart TV according to the smart phone ID and "Smooth Union" ID in the remote service call request, and takes the allocated distributed user ID as the calling subject ID in the cross-device call operation.

[0119] Step S037: Further, DEFS (D22) of the smart TV sends a target service call request of the calling subject to the target service (D20) of the smart TV, wherein the target service call request includes the calling subject ID, and the calling subject ID is the DUID allocated according to the smart phone ID and "Smooth Union" ID.

[0120] Step S038: The target service (D20) performs permission verification according to the DUID calling the native authentication interface of the android PMS (D21) of the smart TV after receiving the target service call request, to determine whether the "Smooth Union" APP has the calling permission of calling "Transfer Call Service" on the smart TV.

[0121] Step S039: PMS (D21) of the smart TV identifies that the calling subject ID type in the target service call request is DUID, and further determines that the target service call request of the calling subject is a cross-device remote service call request.

[0122] Step S040: If it is determined that the target service call request of the calling subject is a cross-device remote service call request, directly call the DPMS(D23) interface of the smart TV to request authentication.

[0123] Step S041: After the DPMS (D23) of the smart TV receives an authentication request to determine whether the calling entity has the permission to call the target service, it requests a cross-device call to the DPMS (D13) of the smartphone to request the calling entity "Changlian" regarding permission information for calling the "Call Transfer Service". Specifically, the DPMS (D23) calls the DEFS (D22) interface of the smart TV to communicate with the smartphone and sends the permission information call instruction to the DEFS (D12) of the smartphone. The permission information call instruction sent to the DEFS (D12) of the smartphone includes the "Changlian" ID and information used to identify the "Call Transfer Service".

[0124] Step S042: The smartphone's DEFS (D12) sends the received permission information call instruction to the smartphone's DPMS (D13). The smartphone's DPMS (D13) requests permission information from the smartphone's PMS (D11) to allow "Changlian" to call the smart TV's "Call Transfer Service" according to the permission information call instruction.

[0125] Step S043: The smartphone's PMS (D11) sends the queried permission information for "Changlian" to call the smart TV's "Call Transfer Service" back to the smartphone's DPMS (D13).

[0126] Step S044: The smartphone's DPMS (D13) further sends the permission information for "Changlian" to call the smart TV's "Call Transfer Service" to the smart TV's DEFS (D22) via the smartphone's DEFS (D12). The smart TV's DEFS (D22) then feeds back the permission information for "Changlian" to call the smart TV's "Call Transfer Service" to the smart TV's DPMS (D23), thereby synchronizing the access permissions for the "Changlian" APP (D10) between the smartphone and the smart TV.

[0127] Step S045: The DPMS (D23) of the smart TV authenticates the permission information of "Changlian" to call the "Call Transfer Service" of the smart TV to determine whether "Changlian" has the permission to call the "Call Transfer Service". Since the user has previously granted authorization and the authorization has not been revoked, the authentication result is that "Changlian" has the permission to call the "Call Transfer Service" of the smart TV, and the authentication is deemed successful. The authentication result is sent to the PMS (D21) of the smart TV.

[0128] Step S046: In the case that the DPMS (D23) authenticates the permission information of the "call transfer service" of the smart TV successfully, the PMS (D21) of the smart TV also feeds back the authentication passing information to the target service (D20) of the smart TV.

[0129] Step S047: The target service (D20) executes the call transfer service after obtaining the authentication passing information, and the current call is successful.

[0130] Step S048: The target service (D20) sends the call success result to the DEFS (D22) of the smart TV.

[0131] Step S049: Further, the DEFS (D22) of the smart TV sends the call success result to the DEFS (D12) of the smart phone.

[0132] Step S050: The DEFS (D12) of the smart phone feeds back the call success result to the calling application "Smooth Connection" (D10).

[0133] Embodiment Three

[0134] The corresponding authorized state type of the embodiment is that the "Smooth Connection" APP (D10) in the smart phone is not the first time to call the "call transfer service" of the smart TV, and the previous authorization has been cancelled.

[0135] Figure 8 The interaction schematic diagram of the calling device and the target device provided by the embodiment three of the application is shown. Figure 8 As shown in the figure, the cross-device calling flow in the embodiment three is implemented through a plurality of steps shown in the figure, and the embodiment formed by the plurality of steps is as follows:

[0136] Step S061: The user cancels the permission of the "Smooth Connection" APP (D10) to call the "call transfer service" of the smart TV in the related settings of the smart phone.

[0137] Step S062: The user opens the "Smooth Connection" APP (D10) on the smart phone, and selects to use the "call transfer service" of the smart TV.

[0138] Step S063: The "Smooth Connection" APP (D10) calls the PMS (D11) interface of the smartphone to request the permission required for calling the "Call Transfer Service" of the smart TV. The PMS (D11) determines whether the request information is the first request for calling the "Call Transfer Service" of the smart TV by the "Smooth Connection" APP (D10) in response to the request information for calling the "Call Transfer Service" of the smart TV by the "Smooth Connection" APP (D10). If the PMS (D11) determines that the request information is not the first request for calling the "Call Transfer Service" by the "Smooth Connection" APP (D10), the "Smooth Connection" directly sends the smartphone ID (device ID), the "Smooth Connection" ID (APP ID) and the information for identifying the "Call Transfer Service" (target service) to the DEFS (D12) without requesting the user authorization.

[0139] Step S064: The DEFS (D11) of the smartphone sends the remote service calling request to the smart TV, wherein the remote service calling request sent to the smart TV includes the smartphone ID (device ID), the "Smooth Connection" ID (APP ID) and the information for identifying the "Call Transfer Service" (target service).

[0140] Step S065: After the DEFS (D12) of the smart TV receives the remote service calling request sent by the smartphone, the DEFS (D12) allocates a distributed user ID in the resource pool of the reserved distributed user ID (DUID) of the smart TV according to the smartphone ID and the "Smooth Connection" ID in the remote service calling request, and takes the allocated distributed user ID as the calling subject ID in the cross-device calling operation.

[0141] Step S066: The DEFS (D22) of the smart TV sends the target service calling request of the calling subject to the target service (D20) of the smart TV, wherein the target service calling request includes the calling subject ID, which is the DUID allocated according to the smartphone ID and the "Smooth Connection" ID.

[0142] Step S067: After receiving the target service calling request, the target service (D20) calls the android PMS (D21) native authentication interface of the smart TV to perform the permission verification according to the DUID, so as to determine whether the "Smooth Connection" APP (D10) has the calling permission of the "Call Transfer Service" of the smart TV.

[0143] Step S068: Further, the PMS (D21) of the smart TV identifies that the calling subject ID type in the target service calling request is a DUID, and further determines that the target service calling request of the calling subject is a cross-device remote service calling request.

[0144] Step S069: In the case where it is determined that the target service calling request of the calling subject is a cross-device remote service calling request, the DPMS (D23) interface of the smart TV is directly called to request authentication.

[0145] Step S070: After the DPMS (D23) of the smart TV receives the authentication request of whether the calling subject has the calling right of the target service, the DPMS (D13) of the smart phone is requested to request the "Changlian" right information of the calling "call transfer service" of the calling subject, specifically, the DEFS (D22) interface of the smart TV is called by the DPMS (D23) to communicate with the smart phone, and the calling instruction of the right information is sent to the DEFS (D12) of the smart phone, wherein the right information calling instruction sent to the DEFS (D12) of the smart phone includes the "Changlian" ID and the information for identifying the "call transfer service".

[0146] Step S071: The DEFS (D12) of the smart phone sends the received right information calling instruction to the DPMS (D13) of the smart phone, and the DPMS (D13) of the smart phone requests the PMS (D11) of the smart phone to request the right information of the "Changlian" calling the "call transfer service" of the smart TV according to the right information calling instruction.

[0147] Step S072: The PMS (D11) of the smart phone feeds back the queried right information of the "Changlian" calling the "call transfer service" of the smart TV to the DPMS (D13) of the smart phone.

[0148] Step S073: The DPMS (D13) of the smart phone further sends the right information of the "Changlian" calling the "call transfer service" of the smart TV to the DEFS (D22) of the smart TV through the DEFS (D12) of the smart phone. Further, the DEFS (D22) of the smart TV feeds back the right information of the "Changlian" calling the "call transfer service" of the smart TV to the DPMS (D23) of the smart TV, so as to realize the synchronization of the calling right of the "Changlian" APP (D10) between the smart phone and the smart TV.

[0149] Step S074: The DPMS (D23) of the smart TV authenticates the permission information of the "call transfer service" of the smart TV called by "Smooth Link", to determine whether "Smooth Link" has the calling permission of the "call transfer service" of the smart TV. Since the user has cancelled the authorization, the authentication result is that "Smooth Link" does not have the calling permission of the "call transfer service" of the smart TV, and it is determined that the authentication fails. The authentication result is sent to the PMS (D21) of the smart TV.

[0150] Step S075: In the case that the authentication of the permission information of the "call transfer service" of the smart TV called by "Smooth Link" fails in the DPMS (D23), the PMS (D21) of the smart TV further feeds back the authentication failure information to the target service (D20) of the smart TV.

[0151] Step S076: The target service (D20) rejects to execute the call transfer service after obtaining the authentication failure information, and the calling fails.

[0152] Step S077: The target service (D20) sends the calling failure result to the DEFS (D22) of the smart TV.

[0153] Step S078: Further, the DEFS (D22) of the smart TV sends the calling failure result to the DEFS (D12) of the smart phone.

[0154] Step S079: The DEFS (D12) of the smart phone feeds back the calling failure to the calling application "Smooth Link" (D10).

[0155] After the calling failure, if the user wants to realize the target service calling again, the user can adjust the permission information of "Smooth Link" APP (D10) about calling the "call transfer service" of the smart TV in the corresponding setting of the smart phone, that is, manually authorize. After the manual authorization is completed, when "Smooth Link" applies to call the "call transfer service" of the smart TV again, the authorization state type of embodiment two is met, and the calling can be successfully called after the authentication in the smart TV is passed.

[0156] The embodiment of the application further provides a calling device, such as Figure 9 The calling device provided by the embodiment of the application is shown in the structural schematic diagram of the calling device. The calling device includes a processor 10A and a memory 20A. The memory 20A is used to store at least one instruction. The instruction is loaded and executed by the processor 10A, and the following remote service calling method based on the calling device is realized:

[0157] sending a remote service calling request to a target device, the remote service calling request including a calling device ID, a calling application ID and target service information;

[0158] receiving a permission information calling instruction sent by the target device, the permission information calling instruction comprising the calling application ID and the target service information;

[0159] sending corresponding permission information to the target device according to the permission information calling instruction, the permission information being used to reflect whether the calling application has the calling permission of the target service.

[0160] Further, before the sending of the remote service calling request to the target device, the method further comprises:

[0161] in response to the remote service calling request, determining whether the calling application is the first to request calling the target service, and if so, performing a permission determination process, and if not, performing the process of sending the remote service calling request to the target device;

[0162] the permission determination process comprises:

[0163] determining the permission information based on a user and saving the permission information in the local.

[0164] Further, the process of determining the permission information based on a user and saving the permission information in the local comprises:

[0165] generating an authorization determination interface to facilitate the user to select whether the calling application has the calling permission of the target service based on the authorization determination interface.

[0166] The embodiment of the application also provides a remote service calling control device based on a target device, like Figure 10 The embodiment of the application shown in the structural schematic diagram of the remote service calling control device based on a target device, the target device comprising: a processor 10B and a memory 20B, the memory 20B being used to store at least one instruction, the instruction being loaded and executed by the processor 10B to realize the following remote service calling method based on a target device:

[0167] receiving a remote service calling request sent by a calling device, the remote service calling request comprising a calling device ID, a calling application ID and target service information;

[0168] sending a permission information calling instruction to the calling device, the permission information calling instruction comprising the calling application ID and the target service information;

[0169] receiving permission information sent by the calling device, the permission information being used to reflect whether the calling application has the calling permission of the target service;

[0170] determine whether the calling application has the calling permission of the target service based on the permission information, and if yes, execute the calling of the target service by the calling application in the calling device.

[0171] Further, before the permission information calling instruction is sent to the calling device, the method further comprises:

[0172] allocate a distributed user ID as the calling subject ID according to the calling device ID and the calling application ID, the distributed user ID being used for identifying the device and the application;

[0173] determine the type of the calling subject ID, if the type of the calling subject ID is the distributed user ID, execute the process of sending the permission information calling instruction to the calling device, and if the type of the calling subject ID is the local ID, execute the local calling permission verification.

[0174] Further, in the process of determining whether the calling application has the calling permission of the target service based on the permission information, if no, reject the calling of the target service by the calling application in the calling device and return a calling failure information to the calling device.

[0175] The embodiment of the application further provides a distributed system, and as shown in Figure 11 The embodiment of the application provides a structure schematic diagram of the distributed system, the distributed system can comprise a plurality of devices (D1, D2, D3, D4, D5, Dn), wherein the plurality of devices comprise at least one calling device and at least one target device. The login account of the plurality of devices can be the same account (such as using the same Huawei account).

[0176] The embodiment of the application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to realize the remote service calling method based on the calling device or the remote service calling method based on the target device.

[0177] It should be noted that the devices involved in the embodiment of the application can include but are not limited to a personal computer (PC), a personal digital assistant (PDA), a wireless handheld device, a tablet computer, a mobile phone, an MP3 player, an MP4 player, etc.

[0178] It can be understood that the application can be an application program (nativeApp) installed on the terminal, or can also be a web program (webApp) of a browser on the terminal, and the embodiment of the application does not limit this.

[0179] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, and will not be described here.

[0180] In several embodiments provided by the present application, it should be understood that the disclosed system, device and method can be implemented by other manners. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0181] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0182] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of hardware plus software functional unit.

[0183] The integrated unit realized in the form of software functional unit can be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, including a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes a variety of program code storage media, such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0184] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0185] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and are not intended to limit the present application; although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that the technical solutions recorded in the above embodiments can be modified, or some or all of the technical features can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for remote service invocation based on a calling device, characterized in that, include: The calling device sends a remote service call request to the target device, the remote service call request including the calling device ID, the calling application ID, and the target service information; The calling application is an application with video call functionality, and the target service includes calling the camera and / or calling the microphone; The calling device receives a permission information calling instruction sent by the target device, the permission information calling instruction including the calling application ID and the target service information; The permission information retrieval instruction is used to determine whether the calling application has permission information to access the camera and microphone of the target device; The calling device sends corresponding permission information to the target device according to the permission information calling instruction, and the permission information includes whether the calling application has the calling permission for the target service.

2. The method according to claim 1, characterized in that, The method further includes: The calling device executes the calling application's call to the camera and / or microphone in the target device.

3. The method according to claim 1, characterized in that, Before sending the remote service call request to the target device, the method further includes: In response to the remote service call request, determine whether it is the first time the calling application has requested to call the target service. If yes, execute the permission determination process; otherwise, execute the process of sending the remote service call request to the target device. The permission determination process includes: The user determines the permission information and saves the permission information locally.

4. The method according to claim 3, characterized in that, The process of determining the permission information based on the user and saving the permission information locally includes: An authorization confirmation interface is generated so that users can select whether the application has the permission to call the target service based on the authorization confirmation interface.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: The calling device obtains a successful call result; and / or, The calling application of the calling device obtains a successful call result.

6. A method for remote service invocation based on a target device, characterized in that, include: Receive a remote service call request sent by the calling device, wherein the remote service call request includes the calling device ID, the calling application ID, and the target service information; The target service information is information used to identify the target service; the calling device ID is the ID of the calling device; the calling application is an application with video call function; and the target service includes calling the camera and / or calling the microphone. Send a permission information invocation instruction to the invocation device, the permission information invocation instruction including the invocation application ID and the target service information; Receive permission information sent by the calling device, the permission information including whether the calling application has the permission to call the target service; Based on the permission information, determine whether the calling application has the permission to call the target service. If so, execute the call to the target service by the calling application in the calling device.

7. The method according to claim 6, characterized in that, Before sending the permission information invocation instruction to the invocation device, the method further includes: The calling entity ID is obtained based on the calling device ID and the calling application ID; Determine the type of the calling entity ID. If the type of the calling entity ID is a distributed user ID, then execute the process of sending the permission information calling instruction to the calling device. If the type of the calling entity ID is a local ID, then execute the local calling permission verification.

8. The method according to claim 7, characterized in that, In the process of determining whether the calling application has the permission to call the target service based on the permission information, if not, the calling application in the calling device is rejected from calling the target service and a call failure message is returned to the calling device.

9. The method according to any one of claims 6-8, characterized in that, The target device sends a message to the calling device indicating that the call was successful.

10. A calling device, characterized in that, The calling device includes a processor and a memory, the memory being used to store at least one instruction, which, when loaded and executed by the processor, implements the remote service invocation method based on the calling device as described in any one of claims 1-5.

11. A target device, characterized in that, The target device includes a processor and a memory, the memory being used to store at least one instruction, which, when loaded and executed by the processor, implements the remote service invocation method based on the target device as described in any one of claims 6-9.

12. A distributed system, characterized in that, include: At least one calling device as described in claim 10, and at least one target device as described in claim 11.

13. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the remote service invocation method based on the invoking device as described in any one of claims 1-5 or the remote service invocation method based on the target device as described in any one of claims 6-9.

Images