WO2023216620A1

WO2023216620A1 - Service calling method and system, calling device, target device, and readable storage medium

Info

Publication number: WO2023216620A1
Application number: PCT/CN2022/143210
Authority: WO
Inventors: 杨俊拯
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-05-13
Filing date: 2022-12-29
Publication date: 2023-11-16
Also published as: CN114937452A

Abstract

A service calling method and system (100), a calling device (10), a target device (30), and a non-volatile computer-readable storage medium (400). The service calling method comprises: acquiring a label of a target device (30) and a target service according to a first input for a calling device (10); acquiring the address of the target device (30) from a server according to the label; according to the address, confirming the target device (30) from at least one device which is about to perform calling; and executing the target service on the target device (30).

Description

Service calling method and system, calling device, target device and readable storage medium

priority information

This application requests the priority and rights of the patent application with patent application number 202210523067.8, which was submitted to the State Intellectual Property Office of China on May 13, 2022, and the full text of which is incorporated herein by reference.

Technical field

The present application relates to the field of communication technology, and in particular to a service calling method, a service calling system, a calling device, a target device and a non-volatile computer-readable storage medium.

Background technique

Some devices can be conveniently controlled through voice control. In related technologies, control is mainly performed through the voice module of the target device itself. Voice control is difficult to perform when the user is far away from the target device.

Contents of the invention

The embodiment of the present application provides a service calling method, a service calling system, a calling device, a target device and a non-volatile computer-readable storage medium.

The service calling method in the embodiment of the present application includes: obtaining the label and target service of the target device according to the first input to the calling device; obtaining the address of the target device from the server according to the label; and obtaining the address of the target device from at least one device according to the address. Confirm the target device in the device to be adjusted; and execute the target service on the target device.

The service calling system in the embodiment of this application includes: calling device, target device and server. The calling device is configured to: obtain the label and target service of the target device according to the first input, obtain the address of the target device from the server according to the label, and obtain the address of the target device from at least one device to be called according to the address. The target device is confirmed in the device; the target device is used to execute the target service.

Embodiments of the present application also provide a service calling method, which includes: obtaining the label and target service of the target device according to the first input to the calling device; obtaining the address of the target device from the server according to the label; and according to the The address confirms the target device from at least one device to be adjusted, so that the target device performs the target service.

The calling device in the embodiment of the present application includes: a parsing module, used to obtain the tag and target service of the target device according to the first input; a first acquisition module, used to obtain the target device from the server according to the tag the address; and a confirmation module for confirming the target device from at least one device to be adjusted according to the address; and a calling module for calling the target device to perform the target service.

The embodiment of the present application also provides a service calling method, which includes: obtaining service definition information according to the target service input by the calling device; obtaining the identification of the installation package corresponding to the target service from the server according to the service definition information; The identifier searches whether the target device has an installation package corresponding to the target service; and when the installation package exists in the target device, installs the installation package and executes the target service.

The target device in the embodiment of the present application includes: a second acquisition module, used to acquire service definition information according to the target service input by the calling device; a third acquisition module, used to acquire the target service from the server according to the service definition information. The identification of the corresponding installation package; a determination module for searching whether the installation package corresponding to the target service exists in the target device according to the identification; and an execution module for finding the installation package in the target device. When, install the installation package and execute the target service.

An embodiment of the present application is a non-volatile computer-readable storage medium containing a computer program. When the computer program is executed by one or more processors, the processor realizes the quality of the service invocation method of the embodiment of the present application. The service calling method includes: obtaining the label and target service of the target device according to the first input to the calling device; obtaining the address of the target device from the server according to the label; and confirming from at least one device to be called according to the address. the target device; and executing the target service on the target device.

Additional aspects and advantages of embodiments of the application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the application.

Description of the drawings

The above and/or additional aspects and advantages of the present application will become apparent and readily understood from the description of the embodiments in conjunction with the following drawings, in which:

Figure 1 is a schematic flow chart of a service invoking method in some embodiments of the present application;

Figure 2 is a schematic structural diagram of a service invocation system in some embodiments of the present application;

Figure 3 is a schematic diagram of the application scenario of the service invocation system in some embodiments of the present application;

Figure 4 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 5 is a schematic diagram of the application scenario of the service invocation system of some embodiments of the present application;;

Figure 6 is a schematic diagram of the application scenario of the service invocation system in some embodiments of the present application;

Figure 7 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 8 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 9 is a schematic diagram of the application scenario of the service invocation system in some embodiments of the present application;

Figure 10 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 11 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 12 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 13 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 14 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 15 is a schematic diagram of the application scenario of the service invocation system in some embodiments of the present application;

Figure 16 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 17 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 18 is a schematic diagram of the application scenario of the service invocation system in some embodiments of the present application;

Figure 19 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 20 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 21 is a schematic structural diagram of a calling device according to certain embodiments of the present application;

Figure 22 is a schematic flowchart of a service invoking method in some embodiments of the present application;

Figure 23 is a schematic structural diagram of a target device according to certain embodiments of the present application;

Figure 24 is a schematic diagram of the connection relationship between a computer-readable storage medium and a processor in some embodiments of the present application.

Detailed ways

The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the embodiments of the present application and cannot be understood as limiting the embodiments of the present application.

A service calling method in an embodiment of the present application includes: obtaining the label and target service of the target device according to the first input to the calling device; obtaining the address of the target device from the server according to the label; and obtaining the address of the target device from at least one device to be called according to the address. Identify the target device; and execute the target service on the target device.

Among them, executing the target service on the target device includes: obtaining service definition information according to the target service; obtaining the identification of the installation package corresponding to the target service from the server according to the service definition information; and searching whether the target device has an installation package corresponding to the target service according to the identification. Installation package; and when the installation package exists in the target device, install the installation package and execute the target service.

Executing the target service on the target device also includes: obtaining the installation package corresponding to the target service from the server when the installation package does not exist in the target device; and installing the installation package and executing the target service.

Among them, executing the target service on the target device also includes: subscribing to the target service in the server; obtaining the installation package corresponding to the target service from the server, including: after the installation package in the server is updated, obtaining the updated installation package from the server. Installation package; install the installation package and execute the target service, including: install the updated installation package and execute the target service.

Among them, executing the target service on the target device also includes: retaining subscriptions and/or installation packages according to the preset retention policy.

Among them, the target services include uninstall service and search service.

The service calling method also includes: uninstalling the target service from the target device according to a preset uninstallation policy.

Among them, the first input includes voice input; obtaining the label and target service of the target device according to the first input to the calling device includes: converting the voice input into text information; obtaining a preset semantic configuration; and converting the text information according to the semantic configuration. Parse and obtain the tags and target services of the target device.

Among them, the semantic configuration includes an intent slot, an intent dictionary, an intent corpus, and an intent reply. The intent slot includes a first variable and a second variable. The first variable represents the label of the target device, the second variable represents the target service, and the intent dictionary includes the third variable. Synonyms of the first variable and the second variable, the intention corpus includes preset sentence patterns; parsing the text information according to the semantic configuration, obtaining the label and target service of the target device, including: matching the text information with the intention corpus; and after the matching is successful , obtain the variable value of the intent slot to obtain the tag of the target device and the target service.

Among them, the service calling method also includes: registering the target service in the server.

Among them, registering the target service in the server includes: saving the installation package and outputting the identification of the installation package according to the installation package upload request; receiving a registration service definition request, which includes the service definition information associated with the identification; and saving Service definition information.

Among them, the service calling method also includes: updating the target service in the server.

Among them, updating the target service in the server includes: saving the updated installation package and outputting the identification of the updated installation package according to the new installation package upload request; receiving an update service definition request, and the update service definition request includes and updates service definition information associated with the identity of the updated installation package; and save service definition information associated with the identity of the updated installation package.

Among them, obtaining the address of the target device from the server according to the tag includes: confirming on the server whether the target device is associated with the account of the calling device; and obtaining the address of the target device if the target device is associated with the account of the calling device.

A service calling system in an embodiment of the present application includes a calling device, a target device and a server; the calling device is used to: obtain the label and target service of the target device according to the first input, obtain the address of the target device from the server according to the label, and obtain the address of the target device from the server according to the label, and obtain the target device's address according to the first input. The address identifies the target device from at least one device to be deployed; the target device is used to perform the target service.

A service calling method in an embodiment of the present application includes: obtaining the label and target service of the target device according to the first input to the calling device; obtaining the address of the target device from the server according to the label; and obtaining the address of the target device from at least one device to be called according to the address. Confirm the target device in so that the target device performs the target service.

A calling device according to the embodiment of the present application, including: a parsing module, used to obtain the label and target service of the target device according to the first input; a first acquisition module, used to obtain the address of the target device from the server according to the label; a confirmation module , used to confirm the target device from at least one device to be adjusted according to the address; and a calling module, used to call the target device to perform the target service.

A service calling method in an embodiment of the present application includes: obtaining service definition information according to the target service input by the calling device; obtaining the identification of the installation package corresponding to the target service from the server according to the service definition information;

Find whether the installation package corresponding to the target service exists in the target device according to the identification; and if the installation package exists in the target device, install the installation package and execute the target service.

A target device according to an embodiment of the present application includes: a second acquisition module, used to acquire service definition information according to the target service input by the calling device; and a third acquisition module, used to acquire the corresponding target service from the server according to the service definition information. The identification of the installation package; the determination module is used to find whether the installation package corresponding to the target service exists on the target device according to the identification; and the execution module is used to install the installation package and execute the target service when the installation package exists in the target device.

An embodiment of the present application is a non-volatile computer-readable storage medium containing a computer program. When the computer program is executed by one or more processors, it causes the processor to implement any of the above service invocation methods.

Please refer to Figure 1. The service invoking method in the implementation of this application includes the following steps:

01: Obtain the tag and target service of the target device 30 according to the first input to the calling device 10;

02: Obtain the address of the target device 30 from the server according to the tag;

03: Confirm the target device 30 from at least one device to be adjusted according to the address; and

04: Execute the target service on the target device 30.

Please refer to Figure 2 and Figure 3. The embodiment of the present application provides a service invocation system 100. The service invocation method can be applied to the service invocation system 100. The service calling system 100 includes a calling device 10, a target device 30 and a server. The calling device 10 is configured to: obtain the label and target service of the target device 30 according to the first input, obtain the address of the target device 30 from the server according to the label, and confirm the target device 30 from at least one device to be adjusted according to the address. The target device 30 is used to execute target services.

The tag 30 of the target device may include at least one of the name, device type, identification information and other information of the target device 30 . For example, the target device 30 is a smart watch, and the smart watch is associated with the same account as the calling device 10. In the device list saved in the associated account, the name of the smart watch is "My Watch" and the device type is "XX Model Smart Watch." ", the identification information is "No. XXXX". That is, in the device list saved by the associated account, the smart watch can be uniquely determined based on at least one piece of information in the name "my watch", device type "XX model smart watch" and identification information "number XXXX". The information used to identify the smart watch is the tag of the smart watch. Correspondingly, the tag 30 of the target device may include at least one of the name, device type, identification information and other information of the target device 30 , for uniquely determining the corresponding target device 30 .

In some embodiments, the first input includes voice input, text input, key input, etc., which are not limited here. Correspondingly, the calling device 10 is an electronic device having an interface capable of receiving the first input. The calling device 10 is an electronic device such as a mobile phone, a tablet computer, a laptop computer, a desktop computer, a smart watch, a smart robot, etc., and is not limited here. For example, the first input is voice input, and the calling device 10 is a mobile phone equipped with the voice recognition module 11 . For another example, the first input is text input, and the calling device 10 is a tablet computer equipped with a handwriting input module. No examples are given here.

The first input is used to control the target device 30 to execute the target service. The target device 30 may include electronic devices such as mobile phones, tablet computers, laptops, desktop computers, smart watches, smart robots, etc., which are not limited here. The target service may include opening or closing a designated application on the target device 30, opening or closing a designated function on the target device 30, etc., which are not limited here.

The tag of the target device 30 is used to obtain the address of the target device 30 from the server. Please refer to Figure 3. In some embodiments, the calling device 10 and at least one device to be adjusted are connected to the Internet. The cloud server 20 stores the account information registered by the calling device 10. The account information includes the name of the device to be adjusted associated with the calling device 10. Label. After the device to be adjusted is connected to the Internet, the address information of the device to be adjusted is stored in the cloud server 20, and the address information corresponds to the label of the device to be adjusted. After obtaining the tag of the target device 30, the calling device 10 uploads the tag of the target device 30 to the cloud server 20. The cloud server 20 determines the target device 30 from a plurality of devices to be adjusted associated with the calling device 10 based on the tag of the target device 30. , and returns the address corresponding to the tag of the target device 30 to the calling device 10 . When it is necessary to call the target device 30 to execute the target service, the calling device 10 sends a request to call the target device 30 according to the address information corresponding to the tag of the target device 30 .

In one embodiment, the calling device 10 and the device to be called are associated by subscribing to the same service. For example, both the calling device 10 and the device to be adjusted subscribe to the "Find Device Location" service, and the device to be adjusted that subscribes to the "Find Device Location" service appears in the device list corresponding to the "Find Device Location" service. The calling device 10 can selectively Associate with the device to be adjusted in the device list.

Please refer to Figure 3. In one embodiment, the calling device 10 is a mobile phone. The devices to be called include watch 1, watch 2 and a robot. The target device 30 is a watch. The mobile phone, watch 1, watch 2 and robot are all connected to the Internet. One input is voice input. The user inputs the voice "Help me find the location of watch 1" into the mobile phone. Based on the voice input, the mobile phone determines that the label of the target device 30 is "Watch 1" and the target service is "Find Device Location". The mobile phone obtains the address of watch 1 through the cloud server 20 and sends a call request corresponding to the "find device location" service to watch 1, causing the watch to perform the "find location" service. For example, Watch 1 starts the "Find Device Location" application according to the call request, and the "Find Device Location" application plays the sound "I am here" through the speaker of Watch 1 to perform the "Find Device Location" service. In this way, when the watch 1 is far away from the user and it is difficult to recognize the user's input voice, the user can remotely control the watch 1 to perform the target service by making voice input to the mobile phone. Alternatively, when the watch 1 does not have a voice recognition function, the watch 1 can perform the target service through voice input to the mobile phone, so that the user can control the device without a voice input interface through voice.

Similarly, when the target device 30 does not support receiving the first input or is difficult to receive the first input, the first input can be made to the calling device 10, and the calling device 10 can identify the target device 30 that the first input wants to control and the corresponding target service. , calling the target device 30 to execute the target service.

In summary, the service invoking method and service invoking system 100 of the embodiment of the present application can make a first input to the invoking device 10 and call the target device 30 to execute the target service, so that when the target device 30 is difficult or unable to receive the first input, The target device 30 can still be controlled through the first input, which is convenient for the user to control.

Referring to Figure 4, in some embodiments, the first input includes voice input. 01: Obtain the tag and target service of the target device 30 according to the first input to the calling device 10, including:

011: Convert voice input into text information;

012: Get the default semantic configuration; and

013: Parse the text information according to the semantic configuration and obtain the label and target service of the target device 30 .

Please refer to FIG. 2 and FIG. 5 . In some embodiments, the calling device 10 includes a speech recognition module 11 and a text parsing module 12 . The speech recognition module 11 is used to perform the method in 011, and the text analysis module 12 is used to perform the methods in 012 and 013. That is, the speech recognition module 11 is used to convert speech input into text information. The text analysis module 12 is used to obtain the preset semantic configuration; and analyze the text information according to the semantic configuration to obtain the label and target service of the target device 30 .

In some scenarios, the user may just mention the label of the device and the target service by voice, but the user's semantics does not intend to request the target device 30 to perform the target service. The calling device 10 can recognize the user's voice and analyze whether the user's voice input is a service request, that is, analyze whether the content of the user's voice input is a request for the target device 30 to perform the target service. If it is a service request, obtain the tag and target service of the target device 30 corresponding to the service request.

Referring to FIG. 2 and FIG. 5 , in some embodiments, the calling device 10 further includes a device management module 13 . After obtaining the tag of the target device 30 , the text parsing module 12 calls the device management module 13 to obtain the address of the target device 30 from the cloud server 20 according to the tag of the target device 30 . In one embodiment, the device management module 13 assembles the address of the target device 30 returned by the cloud server 20 and the target service obtained by the text parsing module 12 into a service invocation URL (Uniform Resource Locator, URL). The device management module 13 uses the The service call URL connects to the service gateway 31 of the target device 30 to call the target device 30 .

Please refer to Figure 6. In some embodiments, the semantic configuration includes an intent slot, an intent dictionary, an intent corpus, and an intent reply. The intent slot includes a first variable and a second variable. The first variable represents the label of the target device 30. The second variable represents the target service, the intent dictionary includes synonyms of the first variable and the second variable, and the intent corpus includes preset sentence patterns. Intent replies include operations performed when text information and intended corpus are successfully matched.

Please refer to Figure 7. In some implementations, 013: parse the text information according to the semantic configuration and obtain the label and target service of the target device 30, including:

0131: Match textual information with intended corpus; and

0132: After successful matching, obtain the variable value of the intent slot to obtain the tag and target service of the target device 30 .

Please refer to Figure 2 and Figure 5. In some embodiments, the text parsing module 12 is also used to execute the methods in 0131 and 0132. That is, the text parsing module 12 is also used to match the text information with the intention corpus; and after successful matching, obtain the variable value of the intention slot to obtain the label and target service of the target device 30 .

Referring to Figure 6, in some embodiments, the intent dictionary includes a subject and synonyms of the subject. A variable in the intent slot corresponds to an intent dictionary. By default, the intent corpus is a sentence composed of a modal prefix, a subject in the intent dictionary or a synonym of the subject, and a modal suffix. Among them, the modal prefix is before the subject or the synonym of the subject in the intention dictionary, and the modal suffix is before the subject or the synonym of the subject in the intention dictionary. When matching the text information with the intended corpus, the text information can be successfully matched with the mood prefix, the subject in the intention dictionary or a synonym of the subject, and the mood suffix to determine whether the text information and the intention corpus are successfully matched; it can also be text When the information matches a component in the intent dictionary or a synonym of the subject, and the text information matches one of the modal prefixes and modal suffixes, it can be determined that the text information matches the intended corpus successfully. It can be set according to the application scenario and is not limited here.

In one embodiment, the intent slot includes a first variable and a second variable, the first variable represents the label of the target device 30 , and the second variable represents the target service. The intent dictionary includes a first dictionary and a second dictionary. The first dictionary includes device tags and synonyms of device tags. The second dictionary includes service tags and synonyms of service tags. The first variable corresponds to the first dictionary, and the second variable corresponds to the second dictionary.

For example, the subject of the first dictionary includes "watch", and the synonyms corresponding to the subject "watch" in the first dictionary include "wrist watch", "electronic watch", and "mechanical watch". The main word of the second dictionary includes "search", and the synonyms corresponding to the main word "find" in the second dictionary include "search", "find", and "search". The default tone prefixes include "please", "help me", and "help". The default mood suffixes include "ok", "can you", and "ok". The text message is "Please help me find the location of watch 1". Match the text message with the intended corpus. In the text message, "please" and "help me" can match the preset tone prefixes, and "find" can If it matches the second dictionary and "watch" can match the first dictionary, it can be determined that the text information and the intended corpus are successfully matched. After the matching is successful, the label of the target device 30: "Watch 1" is obtained according to the first variable "watch" corresponding to the main word of the first dictionary, and the target service is obtained according to the second variable "search" corresponding to the main word of the second dictionary. : "Find" service.

For another example, the subjects of the first dictionary also include "television" and "audio". The synonyms corresponding to the subject "television" in the first dictionary include "color TV" and "TV", and the synonyms corresponding to the subject "audio" include "loudspeaker". ","music player". The main word of the second dictionary also includes "start", and the synonyms corresponding to the main word "start" in the second dictionary include "turn on", "turn on" and "open". The text information is "Will you turn on the TV and stereo?". Match the text information with the intended corpus. In the text information, "turn on" can be matched with the second dictionary, and "TV" and "stereo" can be matched with the first dictionary. Matching, "How about" can match the mood suffix, then it can be determined that the text information and the intended corpus are successfully matched. After the matching is successful, the tags of the target device 30 are obtained: "TV" and "Audio" according to the first variables "TV" and "Audio" corresponding to the main words of the first dictionary, and according to the second variables "TV" and "Audio" corresponding to the main words of the second dictionary. Variable "start" gets the target service: "start" service. In this case, the target device 30 includes both a television and a stereo, and the "start" service will eventually be executed on both the television and the stereo.

Intent replies include operations performed when text information and intended corpus are successfully matched. Referring to FIG. 5 , in one embodiment, the preset intention reply is: when the text information and the intention corpus are successfully matched, the target device 30 is called from at least one device to be adjusted according to the address of the target device 30 . For example, when the text information successfully matches the intended corpus, the text parsing module 12 calls the device 10 management module to send a calling request to the target device 30 .

In some implementations, 02: Obtain the address of the target device 30 from the server according to the tag, including:

021: Confirm on the server whether the target device is associated with the account of the calling device; and

022: Obtain the address of the target device when the target device is associated with the account of the calling device.

Please refer to Figure 2. In some embodiments, the calling device 10 is also used to execute the methods in 021 and 022. That is, the calling device 10 is also used to confirm on the server whether the target device is associated with the account of the calling device; and if the target device is associated with the account of the calling device, obtain the address of the target device.

The account can be a mobile phone number, the ID of the calling device, the registered account corresponding to the service, etc. There are no restrictions here. When the target device is associated with the account of the calling device, obtaining the address of the target device can ensure that the target device is called by the calling device under the same associated account, and ensure that the calling device is a trusted device to avoid security risks. The device illegally makes calls to the target device.

Referring to Figure 8, in some embodiments, 04: executing the target service on the target device 30, including:

041: Obtain service definition information based on the target service;

042: Obtain the identification of the installation package corresponding to the target service from the server based on the service definition information;

043: Find whether the target device 30 has an installation package corresponding to the target service according to the identification; and

044: When the installation package exists in the target device 30, install the installation package and execute the target service.

Please refer to FIG. 2 and FIG. 9 . In some embodiments, the target device 30 includes a service management module 32 and a service life cycle management module 33 . The service management module 32 is used to execute the methods in 041, 042 and 043, and the service life cycle management module 33 is used to execute the method in 044. That is, the service management module 32 is used to obtain service definition information according to the target service; obtain the identification of the installation package corresponding to the target service from the server according to the service definition information; and search whether the installation package corresponding to the target service exists in the target device 30 according to the identification. . The service management module 32 is used to install the installation package when there is an installation package in the target device 30 and execute the target service.

In some embodiments, in order to reduce the storage space occupied by the target device 30, the target service is stored locally on the target device 30 in the form of an installation package. After the calling device 10 sends a calling request to the target device 30, the target device 30 obtains the target service according to the calling request, installs the installation package corresponding to the target service, executes the target service, and uninstalls the target service after completing the execution of the target service. For example, the target service is a "find" service. When the target device 30 executes the "find" service, the "find" program will be started. The "find" program calls the speaker of the target device 30 to emit the sound "I am here". Generally, the "find" service is used less frequently. In order to prevent the "find" program from occupying the space of the target device 30, the target device 30 does not save the "find" program and only responds through the "find" service when it is necessary to execute the "find" service. The installation package installs the "find" program.

In some implementations, the service definition information includes at least one of service tag, service ID, service invocation protocol, service input parameters, and service output parameters. According to the service definition information, the installation package corresponding to the service can be determined. For example, for a service, the service ID of the service has a unique corresponding installation package identifier, and the installation package corresponding to the installation package identifier is the installation package corresponding to the service. For example, the installation package is the installation package of the program that executes the service.

Referring to FIG. 9 , in one embodiment, the cloud server 20 stores service definition information corresponding to multiple registered services. The calling request sent by the calling device 10 to the target device 30 includes the target service that needs to be executed on the target device 30 . The target device 30 requests to call the cloud server 20 to search for service definition information corresponding to the target service from multiple service definition information.

In yet another embodiment, the calling request sent by the calling device 10 to the target device 30 includes service definition information. For example, the device management module 13 of the calling device 10 can execute the method in step 041: obtain service definition information according to the target service. Specifically, the device management module 13 of the calling device 10 requests the calling cloud server 20 to search for the service definition information corresponding to the target service from a plurality of service definition information. The target device 30 obtains the service definition information according to the call request, and after performing basic verification on the service definition information, executes the method in 042: obtain the identification of the installation package corresponding to the target service from the server according to the service definition information. Among them, basic verification includes verifying the integrity and legality of service ID, service invocation protocol, service input parameters, or service output parameters, etc., which are not listed here.

Referring to FIG. 2 and FIG. 9 , in some embodiments, the cloud server 20 includes a service gateway 21 , a service package management module 22 and a service definition management module 23 . The service gateway 21 of the cloud server 20 can forward the request for obtaining service definition information to the service definition management module 23 . According to the request to obtain service definition information, the service definition management module 23 queries the service definition information corresponding to the request stored in the service definition management module 23, and returns the service definition information to the service gateway 21. The service gateway 21 returns the service definition information to the device that sent the request to obtain the service definition information. For example, when the target device 30 sends the request to the service gateway 21, the service gateway 21 returns the service definition information to the target device 30; When the gateway 21 sends the request, the service gateway 21 returns the service definition information to the calling device 10 .

The service package management module 22 stores installation packages corresponding to one or more services, and each installation package has a unique corresponding installation package identification. The service package management module 22 can determine the installation package corresponding to the target service according to the service definition information, for example, determine the installation package corresponding to the target service according to the service ID corresponding to the target service.

In one embodiment, when the target device 30 sends a request to obtain service definition information to the service gateway 21, the service gateway 21 forwards the request to obtain the service definition information to the service definition management module 23 to obtain the service definition information; in the service gateway 21 After obtaining the service definition information, a request for obtaining the identification is sent to the service package management module 22 according to the service definition information, so as to obtain the identification of the installation package corresponding to the target service from the service package management module 22; finally, the service gateway 21 combines the service definition information with The identification of the installation package corresponding to the target service is also returned to the target device 30 .

In another embodiment, the target device 30 sends a request to obtain the identity to the service gateway 21 according to the service definition information. The service gateway 21 forwards the request to obtain the identity to the service package management module 22 and queries the request to obtain the identity through the service package example module. The installation package corresponding to the service definition information contained in the service gateway 21 returns the identification of the installation package corresponding to the service definition information, and then the service gateway 21 returns the identification to the target device 30 .

The target device 30 searches whether the installation package corresponding to the target service exists locally on the target device 30 according to the identification of the installation package corresponding to the target service. If the installation package exists in the target device 30, installs the installation package and executes the target service.

Please refer to Figure 10, in some implementations, 04: Execute the target service on the target device 30, including:

045: When the installation package does not exist in the target device 30, obtain the installation package corresponding to the target service from the server; and

046: Install the installation package and execute the target service.

Please combine Figure 2 and Figure 9. In some embodiments, the service management module 32 is also used to execute the method in 045, and the service life cycle management module 33 is also used to execute the method in 046. That is, the service management module 32 is used to obtain the installation package corresponding to the target service from the server when the installation package does not exist in the target device 30 .

When there is no installation package in the target device 30 , the service management module 32 sends an installation package acquisition request to the cloud server 20 , and the installation package acquisition request includes the identification of the installation package corresponding to the target service. The service gateway 21 forwards the installation package acquisition request to the service package management module 22. The service package management module 22 queries the corresponding installation package file according to the identification of the installation package, returns the installation package file to the service gateway 21, and sends the installation package file through the service gateway 21. transmitted to target device 30. Or the service package management module 22 queries the identification of the installation package and returns the address of the corresponding installation package file to the service gateway 21. The service gateway 21 returns the address of the installation package file to the target device 30. The target device 30 downloads the installation package according to the address of the installation package file. , to install the installation package and execute the target service.

Please refer to Figure 11. In some implementations, 04: executing the target service on the target device 30 also includes:

047: Subscribe to the target service in the server;

045: Obtain the installation package corresponding to the target service from the server, including:

0451: After the installation package in the server is updated, obtain the updated installation package from the server;

046: Install the installation package and execute the target services, including:

0461: Install the updated installation package and execute the target service.

Please combine Figure 2 and Figure 9. In some embodiments, the service management module 32 is also used to execute the methods in 047 and 0451, and the service life cycle management module 33 is also used to execute the method in 0461. That is, the service management module 32 is used to subscribe to the target service in the server; and after the installation package in the server is updated, obtain the updated installation package from the server. The service life cycle management module 33 is also used to install the updated installation package and execute the target service.

In some embodiments, the target device 30 subscribes to the target service in the cloud server 20 to ensure that the latest installation package of the target service can be obtained from the cloud server 20 when the target service needs to be executed. In some embodiments, the cloud server 20 also includes a service subscription management module 24. When the target device 30 does not subscribe to the target service, after receiving the installation package acquisition request from the target device 30 , the service gateway 21 forwards the installation package acquisition request to the service package management module 22 to obtain the latest installation package, and launches the service. The subscription management module 24 adds a subscription relationship with the target device 30 so that the target device 30 subscribes to the target service.

In some embodiments, when the target device 30 has subscribed to the target service, after the installation package of the target service in the server is updated, the service package management module 22 pulls up the service subscription management module 24 to perform installation package synchronization processing. The service subscription The management module 24 sends an installation package synchronization request to the target device 30 that has subscribed to the target service. The installation package synchronization request includes updated installation package information, such as the address information of the updated installation package file. The target device 30 performs the installation package synchronization request according to the updated installation package. Package information Download the updated installation package from the server.

Please refer to Figure 12. In some implementations, the service invocation method also includes:

06: Retain subscriptions and/or installation packages according to the preset retention policy.

Please combine Figure 2 and Figure 9. In some embodiments, the service life cycle management module 33 is also used to execute the method in 06. That is, the service life cycle management module 33 is also used to retain subscriptions and/or installation packages according to a preset retention policy.

In some embodiments, in order to reduce the storage space occupied by the target device 30, whether to retain the installation package is selected according to a preset retention policy. For example, the preset retention policy is set to: detect the frequency of use of the target service; when the frequency of use of the target service is high, retain the installation package so that the target device 30 can install the installation package in time and execute the target service; when the target service is used When the frequency of use is low, the installation package is deleted, and the next time the target device 30 is called, the target device 30 re-obtains the installation package of the target service from the cloud server 20 .

Similarly, in some embodiments, when the target device 30 is called more frequently, or when the target service is updated more frequently, the subscription relationship between the target device 30 and the target service is retained to reduce Subsequent calls to the link of the target device 30 improve the response speed; when the target device 30 is called less frequently, cancel the subscription relationship between the target device 30 and the target service to avoid the target device 30 being called less frequently. In this case, the installation package is still frequently updated.

Please refer to Figure 13. In some implementations, the service invocation method also includes:

07: Uninstall the target service from the target device 30 according to the preset uninstallation policy.

Please combine Figure 2 and Figure 9. In some embodiments, the service life cycle management module 33 is also used to execute the method in 07. That is, the service life cycle management module 33 is also used to uninstall the target service from the target device 30 according to the preset uninstall policy.

In some implementations, the preset uninstallation policy is set to: uninstall the target service from the target device 30 after the target service completes execution for a preset period of time. For example, if the default duration is immediate uninstallation, the target service will be uninstalled immediately after the execution of the target service is completed. For another example, if the default duration is 2 hours, if the target service is not called for execution again within 2 hours after completion, the target service will be uninstalled. In this way, the storage space occupied by the target device 30 can be saved.

Referring to FIG. 2 and FIG. 3 , in some embodiments, the target service includes an uninstall service. Executing the uninstall service on the target device 30 can uninstall other local services on the target device 30 , such as uninstalling other target services that have been completed.

For example, target services include uninstall service and lookup service. In one application scenario, the target device 30 is watch 1, watch 1 has completed the execution of the search service, and the user inputs a voice message to the calling device 10: "Help me uninstall the search program of watch 1." Please refer to Figure 1, the calling device 10 executes the service calling methods in 01, 02, and 03 according to the user's voice input, that is, the calling device 10 obtains the label and target service of the target device 30 according to the first input, and obtains it from the server according to the label. The address of the target device 30, and confirming the target device 30 from at least one device to be adjusted according to the address. The target device 30 executes the service invoking method in 04, that is, the target device 30 executes the target service. Among them, the label of the target device 30 obtained by the calling device 10 is "watch 1", and the target service is the "uninstall" service, specifically "uninstall the search program of watch 1". The calling device 10 encapsulates the address of the watch 1 and the parameters of the "uninstall" service into a calling URL, and sends a calling request to the watch 1 to uninstall the service. Watch 1 executes the "uninstall" service according to the call request of the uninstall service and uninstalls the local "find" program.

Please refer to Figure 14. In some implementations, the service invocation method also includes:

08: Register the target service in the server.

Please combine Figure 2 and Figure 15. In some implementations, the cloud server 20 is used to execute the method in 08. That is, the cloud server 20 is used to register the target service.

Referring to Figure 15, after the developer completes the opening of a certain service, the service is registered in the cloud server 20, so that when the calling device 10 calls the target device 30 to execute the service, the target device 30 can obtain the service from the cloud server 20 The installation package to install and execute the service locally on the target device 30. In some embodiments, developers add the labels of registered services to the intent dictionary, so that the calling device 10 can parse text information according to the intent dictionary, and compare the service labels in the text information with the registered services in the intent dictionary. Tags are matched to obtain the target service.

Referring to Figure 15, in some implementations, the developer registers the target service, including uploading the installation package of the target service to the cloud server 20, and uploading the service definition information of the target service to the cloud server 20. Please refer to Figure 16. In some implementations, 08: Register the target service in the server, including:

081: According to the installation package upload request, save the installation package and output the identification of the installation package;

082: Receive a registration service definition request, which contains service definition information associated with the identifier; and

083: Save service definition information.

Please refer to FIG. 2 and FIG. 15 . In some embodiments, the cloud server 20 includes a service package management module 22 , a service gateway 21 , and a service definition management module 23 . The service package management module 22 is used to execute the method in 081, the service gateway 21 is used to execute the method in 082, and the service definition management module 23 is used to execute the method in 083. That is, the service package management module 22 is configured to save the installation package and output the identification of the installation package according to the installation package upload request. The service gateway module is used to receive registration service definition requests. The service definition management module 23 is used to save service definition information.

Please refer to Figure 15. In some implementations, the developer sends an installation package upload request corresponding to the target service to the service gateway, and the installation package upload request includes the installation package file. The service gateway forwards the installation package upload request to the service package management module 22. The service package management module 22 saves the installation package file to the file warehouse of the cloud server 20 according to the installation package upload request, and outputs the information of the installation package in the cloud server 20. Installation The package information includes the address of the installation package file, the identification of the installation package, etc. The service package management module 22 returns the identification of the installation package to the service gateway, and returns the identification of the installation package to the developer through the service gateway.

The developer associates the service definition information of the target service with the identification of the installation package of the target service, and sends a registration service definition request to the service gateway. The registration service definition request includes the associated service definition information. The service gateway forwards the registration service definition request to the service definition management module 23 , and the service definition management module 23 saves the service definition information to the cloud server 20 .

Please refer to Figure 9. After completing the registration of the target service, the service package management module 22 saves the installation package information, and the service definition management module 23 saves the service definition information. When the target device 30 initiates a request to obtain service definition information from the cloud server 20, the service gateway can forward the request to the service definition management module 23, so that the service definition management module 23 responds to the request and sends the service to the target device 30 through the service gateway. Define information. When the target device 30 initiates a request to obtain the installation package from the cloud server 20, the service gateway can forward the request to the service package management module 22, so that the service package management module 22 responds to the request and sends the installation package to the target device 30 through the service gateway. address information, so that the target device 30 downloads the installation package according to the address information of the installation package.

Please refer to Figure 17. In some implementations, the service invocation method also includes:

09: Update the target service in the server.

Please combine Figure 2 and Figure 18. In some embodiments, the cloud server 20 is used to execute the method in 09. That is, the cloud server 20 is also used to update the target service.

After the developer updates the target program, the installation package and service definition information corresponding to the target service in the cloud server 20 need to be updated synchronously, so that when the calling device 10 calls the target device 30 to execute the service, the target device 30 can obtain the information from the cloud server 20 Get the latest installation package of the service.

Please refer to Figure 19. In some implementations, 09: Update the target service in the server, including:

091: According to the new installation package upload request, save the updated installation package and output the identification of the updated installation package;

092: Receive an update service definition request, the update service definition request includes service definition information associated with the identity of the updated installation package; and

093: Save the service definition information associated with the identity of the updated installation package.

Please combine Figure 2 and Figure 18. In some embodiments, the service package management module 22 is also used to execute the method in 091, the service gateway module is also used to execute the method in 092, and the service definition management module 23 is also used to execute method in 093. That is, the service package management module 22 is also configured to save the updated installation package and output the identification of the updated installation package according to the new installation package upload request. The service gateway module is also used to receive update service definition requests. The service definition management module 23 is also configured to save service definition information associated with the updated installation package identification.

Referring to Figure 18, in some implementations, the developer sends a new installation package upload request corresponding to the updated target service to the service gateway, and the new installation package upload request includes a new installation package file. The service gateway forwards the new installation package upload request to the service package management module 22. The service package management module 22 saves the new installation package file to the file warehouse of the cloud server 20 according to the new installation package upload request, and outputs it to the cloud server 20. The information of the new installation package includes the address of the new installation package file, the identification of the new installation package, etc. The service package management module 22 returns the identification of the new installation package to the service gateway, and sends the information to the service gateway through the service gateway. The identity of the new installation package is returned to the developer.

The service package management module 22 also calls the service package synchronization processing request through the service subscription management module 24 according to the information of the new installation package, and the service package synchronization processing request includes the information of the new installation package. The service subscription management module 24 initiates a service package synchronization processing request to the service gateway of the target device 30 that has subscribed to the target service. The service gateway of the target device 30 forwards the request to the service management module 32 of the target device 30. The service management of the target device 30 The module 32 updates the information of the installation package of the target service. After the update is successful, the target device 30 returns a response to the cloud server 20 . In this way, when the calling device 10 calls the target device 30 to execute the updated target service, the target device 30 can download and install the new installation package according to the information of the new installation package to execute the updated target service.

The developer associates the new service definition information of the new target service with the identity of the new installation package of the new target service, and sends an update service definition request to the service gateway. The update service definition request includes association with the identity of the updated installation package. service definition information. The service gateway forwards the update service definition request to the service definition management module 23 , and the service definition management module 23 saves the service definition information associated with the updated installation package identification to the cloud server 20 .

Referring to Figure 20 and Figure 21, the embodiment of the present application also provides a service invoking method and invoking device 200. Service calling methods include:

0101: Obtain the tag and target service of the target device according to the first input to the calling device 200;

0102: Obtain the address of the target device from the server based on the tag; and

0103: Confirm the target device from at least one device to be adjusted according to the address, so that the target device can perform the target service.

The calling device 200 includes a parsing module 201, a first acquisition module 202, a confirmation module 203 and a calling module 204. The parsing module 201 is used to execute the method in 0101, the first acquisition module 202 is used to execute the method in 0102, and the confirmation module 203 and the calling module are used to execute the method in 0103. That is, the parsing module 201 is used to obtain the tag and target service of the target device according to the first input to the calling device 200 . The first obtaining module 202 is used to obtain the address of the target device from the server according to the label. The confirmation module 203 is used to confirm the target device from at least one device to be adjusted according to the address. The calling module 204 is used to call the target device to execute the target service.

Please refer to FIG. 2 and FIG. 21 . In some embodiments, the calling device 200 can participate in forming the service calling system 100 as the calling device 10 in the service calling system 100 . In the calling system, the calling device 200 may be used to execute the service calling method executed by the calling device 10 in the above embodiment, which will not be described again here.

Please refer to Figure 22 and Figure 23. The embodiment of the present application also provides a service invocation method and a target device 300. Service calling methods include:

0201: Obtain service definition information based on the target service input by the calling device;

0202: Obtain the identification of the installation package corresponding to the target service from the server based on the service definition information;

0203: Find whether the target device 300 has an installation package corresponding to the target service according to the identification; and

0204: When the installation package exists in the target device 300, install the installation package and execute the target service.

The target device 300 includes a second acquisition module 301, a third acquisition module 302, a determination module 303 and an execution module 304. The second acquisition module 301 is used to execute the method in 0201, the third acquisition module 302 is used to execute the method in 0202, the determination module 303 module is used to execute the method in 0203, and the execution module 304 is used to execute the method in 0204. That is, the second obtaining module 301 is used to obtain service definition information according to the target service input by the calling device. The third obtaining module 302 is used to obtain the identification of the installation package corresponding to the target service from the server according to the service definition information. The determining module 303 is used to search whether the target device 30 has an installation package corresponding to the target service according to the identification. The execution module 304 is used to install the installation package and execute the target service when the installation package exists in the target device 30 .

Please combine Figure 2, Figure 3 and Figure 23. In some embodiments, the target device 300 can participate in forming the service invocation system 100 as a device to be deployed in the service invocation system 100. When the target device 300 is called, it becomes Figure 2 Target device 30 in . In the calling system, the target device 300 may be used to execute the service calling method executed by the target device 30 in the above embodiment, which will not be described again here.

Referring to Figure 24, an embodiment of the present application also provides a non-volatile computer-readable storage medium 400 containing a computer program 401. One or more non-volatile computer-readable storage media 400 containing a computer program 401 in an embodiment of the present application. When the computer program 401 is executed by one or more processors 402, the processor 402 can execute any of the above implementations. The service calling method in the way, for example, implement

steps

01, 02, 03, 04, 05, 07, 08, 09, 011, 012, 013, 0131, 0132, 021, 022, 041, 042, 043, 044, 045, 046 , 047, 0451, 0461, 081, 082, 083, 091, 092, 093, 0101, 0102, 0103, 0201, 0202 and 0203.

For example, when the computer program 401 is executed by one or more processors 402, the processors 402 are caused to perform the following steps:

02: Obtain the address of the target device 30 from the server according to the label;

04: Execute the target service on the target device 30.

In the description of this specification, reference to the description of the terms "one embodiment," "some embodiments," "illustrative embodiments," "examples," "specific examples," or "some examples" or the like is meant to be in conjunction with the description of the embodiment or Examples describe specific features, structures, materials, or characteristics that are included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples unless they are inconsistent with each other.

Any process or method descriptions in flowcharts or otherwise described herein may be understood to represent modules, segments, or portions of code that include one or more executable instructions for implementing the specified logical functions or steps of the process. , and the scope of the preferred embodiments of the present application includes additional implementations in which functions may be performed out of the order shown or discussed, including in a substantially simultaneous manner or in the reverse order, depending on the functionality involved, which shall It should be understood by those skilled in the technical field to which the embodiments of the present application belong.

Although the embodiments of the present application have been shown and described above, it can be understood that the above-mentioned embodiments are exemplary and cannot be construed as limitations of the present application. Those of ordinary skill in the art can make various modifications within the scope of the present application. The above-described embodiments are subject to changes, modifications, substitutions and variations.

Claims

A service calling method, which includes:

Obtain the label and target service of the target device according to the first input to the calling device;

Obtain the address of the target device from the server according to the tag;

Confirm the target device from at least one device to be adjusted based on the address; and

Execute the target service on the target device.
The service invoking method according to claim 1, wherein executing the target service on the target device includes:

Obtain service definition information according to the target service;

Obtain the identification of the installation package corresponding to the target service from the server according to the service definition information;

Find whether the target device has an installation package corresponding to the target service according to the identification; and

When the installation package exists in the target device, the installation package is installed and the target service is executed.
The service invoking method according to claim 2, wherein executing the target service on the target device further includes:

When the installation package does not exist in the target device, obtain the installation package corresponding to the target service from the server; and

Install the installation package and execute the target service.
The service invoking method according to claim 3, wherein executing the target service on the target device further includes:

Subscribe to the target service in the server;

Obtaining the installation package corresponding to the target service from the server includes:

After the installation package in the server is updated, obtain the updated installation package from the server;

Installing the installation package and executing the target service includes:

Install the updated installation package and execute the target service.
The service invoking method according to claim 4, further comprising:

The subscription and/or the installation package are retained according to the preset retention policy.
The service invoking method according to claim 1, wherein the target service includes an unloading service and a search service.
The service invoking method according to claim 1, further comprising:

Uninstall the target service from the target device according to a preset uninstallation policy.
The service calling method according to claim 1, wherein the first input includes voice input; and obtaining the tag of the target device and the target service according to the first input to the calling device includes:

Convert the voice input into text information;

Get the default semantic configuration; and

The text information is parsed according to the semantic configuration to obtain the label of the target device and the target service.
The service invoking method according to claim 8, wherein the semantic configuration includes an intention slot, an intention dictionary, an intention corpus and an intention reply, the intention slot includes a first variable and a second variable, the first variable A label characterizing the target device, the second variable characterizing the target service, the intent dictionary including synonyms of the first variable and the second variable, the intent corpus including a preset sentence pattern; Parse the text information according to the semantic configuration and obtain the label of the target device and the target service, including:

Match the text information with the intended corpus; and

After successful matching, obtain the variable value of the intent slot to obtain the label of the target device and the target service.
The service invoking method according to claim 1, further comprising:

Register the target service in the server.
The service invoking method according to claim 10, wherein registering the target service in the server includes:

According to the installation package upload request, save the installation package and output the identification of the installation package;

receiving a registration service definition request, the registration service definition request including service definition information associated with the identification; and

Save the service definition information.
The service invoking method according to claim 10, further comprising:

Update the target service in the server.
The service invoking method according to claim 12, wherein the updating the target service in the server includes:

According to the new installation package upload request, save the updated installation package and output the identification of the updated installation package;

Receive an update service definition request, the update service definition request including service definition information associated with the updated identification of the installation package; and

Save the service definition information associated with the updated identification of the installation package.
The service invoking method according to claim 1, wherein said obtaining the address of the target device from the server according to the tag includes:

Confirm on the server whether the accounts of the target device and the calling device are associated; and

When the target device is associated with the account of the calling device, the address of the target device is obtained.
A service calling system, which includes a calling device, a target device and a server;

The calling device is configured to: obtain the label and target service of the target device according to the first input, obtain the address of the target device from the server according to the label, and obtain the address of the target device from at least one device to be called according to the address. Confirm the target device in the device;

The target device is used to execute the target service.
A service calling method, which includes:

Obtain the label and target service of the target device according to the first input to the calling device;

Obtain the address of the target device from the server according to the tag; and

Confirm the target device from at least one device to be adjusted according to the address, so that the target device executes the target service.
A calling device, which includes:

A parsing module, used to obtain the tag of the target device and the target service according to the first input;

A first acquisition module, configured to acquire the address of the target device from the server according to the tag;

a confirmation module, configured to confirm the target device from at least one device to be adjusted according to the address; and

A calling module, configured to call the target device to execute the target service.
A service calling method, which includes:

Obtain service definition information based on the target service input by the calling device;

Obtain the identification of the installation package corresponding to the target service from the server according to the service definition information;

Find whether the target device has an installation package corresponding to the target service according to the identification; and

When the installation package exists in the target device, the installation package is installed and the target service is executed.
A target device that includes:

The second acquisition module is used to acquire service definition information according to the target service input by the calling device;

A third acquisition module, configured to acquire the identification of the installation package corresponding to the target service from the server according to the service definition information;

a determination module, configured to search whether the target device has an installation package corresponding to the target service according to the identification; and

An execution module, configured to install the installation package and execute the target service when the installation package exists in the target device.
A non-volatile computer-readable storage medium containing a computer program. When the computer program is executed by one or more processors, the processor implements the service call described in any one of claims 1 to 14. method.