CN114937452A

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

Info

Publication number: CN114937452A
Application number: CN202210523067.8A
Authority: CN
Inventors: 杨俊拯
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2022-05-13
Filing date: 2022-05-13
Publication date: 2022-08-23
Also published as: WO2023216620A1

Abstract

The application discloses 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 comprises the following steps: acquiring a label and a target service of target equipment according to a first input to calling equipment; acquiring the address of the target equipment from the server according to the label; confirming target equipment from at least one piece of equipment to be adjusted according to the address; and executing the target service on the target device. The service calling method, the service calling system, the calling device, the target device and the non-volatile computer-readable storage medium can perform first input on the calling device, and the calling target device executes the target service, so that the target device can be controlled through the first input even under the condition that the target device is difficult to receive or cannot receive the first input, and control by a user is facilitated.

Description

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

Technical Field

The present application relates to the field of communications technologies, and in particular, to a service invocation method, a service invocation system, an invocation device, a target device, and a non-volatile computer-readable storage medium.

Background

Some devices can be conveniently controlled through voice control. In the related art, the control is mainly performed through a voice module of the target device. When the user is far from the target device, voice control is difficult.

Disclosure of Invention

The embodiment of the application provides a service calling method, a service calling system, calling equipment, target equipment and a nonvolatile computer readable storage medium.

The service calling method of the embodiment of the application comprises the following steps: acquiring a label and a target service of target equipment according to a first input to calling equipment; acquiring the address of the target equipment from a server according to the label; confirming the target equipment from at least one equipment to be regulated according to the address; and executing the target service on the target device.

The service calling system of the embodiment of the application comprises: the system comprises a calling device, a target device and a server. The calling device is configured to: acquiring a label and a target service of the target equipment according to a first input, acquiring an address of the target equipment from the server according to the label, and confirming the target equipment from at least one piece of equipment to be adjusted according to the address; the target device is used for executing the target service.

The embodiment of the present application further provides a service invoking method, including: acquiring a label and a target service of target equipment according to a first input to calling equipment; acquiring the address of the target equipment from a server according to the label; and confirming the target equipment from at least one piece of equipment to be adjusted according to the address so as to enable the target equipment to execute the target service.

The calling device of the embodiment of the application comprises: the analysis module is used for acquiring a label and a target service of the target equipment according to the first input; the first acquisition module is used for acquiring the address of the target equipment from the server according to the label; the confirming module is used for confirming the target equipment from at least one piece of equipment to be adjusted according to the address; and the calling module is used for calling the target equipment to execute the target service.

The embodiment of the present application further provides a service invoking method, including: acquiring service definition information according to a target service input by calling equipment; acquiring an identifier of an installation package corresponding to the target service from a server according to the service definition information; searching whether the target equipment has an installation package corresponding to the target service or not according to the identification; and when the installation package exists in the target equipment, installing the installation package and executing the target service.

The target device of the embodiment of the application comprises: the second acquisition module is used for acquiring service definition information according to the target service input by the calling equipment; a third obtaining module, configured to obtain, from a server according to the service definition information, an identifier of an installation package corresponding to the target service; the determining module is used for searching whether the target equipment has an installation package corresponding to the target service according to the identifier; and the execution module is used for installing the installation package and executing the target service when the installation package exists in the target equipment.

A non-transitory computer-readable storage medium containing a computer program of embodiments of the present application, which, when executed by one or more processors, causes the processors to implement the quality of the service invocation method of embodiments of the present application. The service calling method comprises the following steps: acquiring a label and a target service of target equipment according to a first input to calling equipment; acquiring the address of the target equipment from a server according to the label; confirming the target equipment from at least one piece of equipment to be adjusted according to the address; and executing the target service on the target device.

The service calling method, the service calling system, the calling device, the target device and the non-volatile computer-readable storage medium can perform first input on the calling device, and the calling target device executes the target service, so that the target device can be controlled through the first input even under the condition that the target device is difficult to receive or cannot receive the first input, and control by a user is facilitated.

Additional aspects and advantages of embodiments of the present 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 present application.

Drawings

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

FIG. 1 is a flow diagram illustrating a method for service invocation in some embodiments of the present application;

FIG. 2 is a schematic block diagram of a service invocation system in accordance with certain embodiments of the present application;

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

FIG. 4 is a schematic flow chart diagram of a service invocation method in some embodiments of the present application;

FIG. 5 is a schematic diagram of an application scenario of a service invocation system in some embodiments of the present application; (ii) a

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

FIG. 7 is a schematic flow chart diagram of a service invocation method in some embodiments of the present application;

FIG. 8 is a flow diagram illustrating a method of service invocation in some embodiments of the present application;

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

FIG. 10 is a schematic flow chart diagram of a method of service invocation in some embodiments of the present application;

FIG. 11 is a flow diagram illustrating a method of service invocation in some embodiments of the present application;

FIG. 12 is a schematic flow chart diagram of a service invocation method in accordance with certain embodiments of the present application;

FIG. 13 is a schematic flow chart diagram of a service invocation method in accordance with certain embodiments of the present application;

FIG. 14 is a schematic flow chart diagram of a service invocation method in accordance with certain embodiments of the present application;

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

FIG. 16 is a schematic flow chart diagram of a service invocation method in accordance with certain embodiments of the present application;

FIG. 17 is a schematic flow chart diagram of a service invocation method in accordance with certain embodiments of the present application;

FIG. 18 is a schematic diagram of an application scenario of a service invocation system in accordance with certain embodiments of the present application;

FIG. 19 is a schematic flow chart diagram of a service invocation method in accordance with certain embodiments of the present application;

FIG. 20 is a schematic flow chart diagram of a service invocation method in accordance with certain embodiments of the present application;

FIG. 21 is a schematic diagram of the calling device of some embodiments of the present application;

FIG. 22 is a schematic flow chart diagram of a service invocation method in accordance with certain embodiments of the present application;

FIG. 23 is a schematic block diagram of a target device according to certain embodiments of the present application;

FIG. 24 is a schematic diagram of a connection between a computer-readable storage medium and a processor according to some embodiments of the present application.

Detailed Description

Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below by referring to the drawings are exemplary only for the purpose of explaining the embodiments of the present application, and are not to be construed as limiting the embodiments of the present application.

Referring to fig. 1, a service invocation method according to an embodiment of the present application includes the following steps:

01: acquiring a label and a target service of the target device 30 according to a first input to the calling device 10;

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

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

04: the target service is executed on the target device 30.

Referring to fig. 2 and fig. 3, the present disclosure provides a service invocation system 100, and the service invocation method can be applied to the service invocation system 100. The service invocation system 100 includes an invocation device 10, a target device 30, and a server. Invoking device 10 is to: the method comprises the steps of obtaining a label and a target service of the target device 30 according to the first input, obtaining an address of the target device 30 from a server according to the label, and confirming the target device 30 from at least one device to be adjusted according to the address. The target device 30 is used to perform a target service.

The 30 tag of the target device may include at least one of the name, device type, identification information, and the like of the target device 30. For example, the target device 30 is a smart watch, the smart watch is associated with the calling device 10 by the same account number, and in a device list stored by the associated account number, the name of the smart watch is "my watch", the device type is "XX model smart watch", and the identification information is "serial number XXXX". That is, in the device list stored in the associated account, the smart watch may be uniquely and correspondingly determined according to at least one item of information of the name "my watch", the device type "XX model smart watch", and the identification information "serial number XXXX", and information used for determining the smart watch is a tag of the smart watch. Accordingly, the 30 tag of the target device may include at least one of the name, device type, identification information, etc. of the target device 30 for uniquely determining the corresponding target device 30.

In some embodiments, the first input includes, but is not limited to, voice input, text input, key input, and the like. Correspondingly, the calling device 10 is an electronic device having an interface capable of receiving a first input. The invoking device 10 is an electronic device such as a mobile phone, a tablet computer, a notebook computer, a desktop computer, an intelligent watch, an intelligent robot, and the like, which is not limited herein. For example, the first input is a voice input and the calling device 10 is a mobile phone provided with a voice recognition module 11. For another example, the first input is a text input, and the calling device 10 is a tablet computer with a handwriting input module. Not to be taken as an example herein.

The first input is used to control the target device 30 to perform the target service. The target device 30 may include, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a desktop computer, a smart watch, a smart robot, and other electronic devices. The target service may include, without limitation, opening or closing a specified application on the target device 30, opening or closing a specified function on the target device 30, and the like.

The tag of the target device 30 is used to acquire the address of the target device 30 from the server. Referring to fig. 3, in some embodiments, the calling device 10 and at least one to-be-called device access the internet, and the cloud server 20 stores account information registered by the calling device 10, where the account information includes a tag of the to-be-called device associated with the calling device 10. After the to-be-dispatched device accesses the internet, the address information of the to-be-dispatched device is stored in the cloud server 20, and the address information corresponds to the tag of the to-be-dispatched device. 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 called associated with the calling device 10 according to 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. In the case where the call target device 30 is required to execute the target service, the call device 10 transmits a request for calling 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 is associated with the device to be called by subscribing to the same service. For example, the invoking device 10 and the device to be invoked both subscribe to the "find device location" service, the device to be invoked subscribing to the "find device location" service appears in the device list corresponding to the "find device location" service, and the invoking device 10 may be selectively associated with the device to be invoked in the device list.

Referring to fig. 3, in one embodiment, the calling device 10 is a mobile phone, the devices to be called include a watch 1, a watch 2 and a robot, the target device 30 is a watch, the mobile phone, the watch 1, the watch 2 and the robot all access the internet, and the first input is a voice input. The user inputs a voice "help me find watch 1 position" to the mobile phone. The handset determines from the voice input that the tag of the target device 30 is "watch 1" and the target service is "find device location". The mobile phone obtains the address of the watch 1 through the cloud server 20, and sends a call request corresponding to the service of finding the device location to the watch 1, so that the watch executes the service of finding the location. For example, watch 1 launches a "find device location" application upon a call request, which plays the sound "i am here" through the speaker of watch 1 to perform a "find device location" service. In this way, when the wristwatch 1 is far from the user and it is difficult to recognize the input voice of the user, the user can make the wristwatch 1 execute the target service by performing voice input to the mobile phone, so as to remotely control the wristwatch 1 to execute the target service. Alternatively, in the case where the wristwatch 1 does not have the voice recognition function, the wristwatch 1 may be caused to perform the target service by performing voice input to the cellular phone, so that the user can control the device without the voice input interface by voice.

Similarly, in the case where the target device 30 does not support reception or has difficulty in receiving the first input, the calling device 10 may be subjected to the first input, and the calling target device 30 may execute the target service by recognizing the target device 30 and the corresponding target service that the first input wants to control, by the calling device 10.

In summary, the service invocation method and the service invocation system 100 according to the embodiments of the present application can perform the first input to the invocation device 10 and the invocation target device 30 to execute the target service, so that the target device 30 can be controlled by the first input even when the target device 30 is difficult to receive or cannot receive the first input, thereby facilitating the control of the user.

Referring to FIG. 4, in some embodiments, the first input includes a speech input. 01: acquiring the tag and target service of the target device 30 according to the first input to the calling device 10, including:

011: converting the voice input into character information;

012: acquiring preset semantic configuration; and

013: and analyzing the text information according to the semantic configuration to acquire the label and the target service of the target equipment 30.

Referring to fig. 2 and 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 execute the method in 011, and the text parsing module 12 is used to execute the methods in 012 and 013. That is, the voice recognition module 11 is used to convert the voice input into text information. The character analysis module 12 is used for acquiring preset semantic configuration; and analyzing the text information according to the semantic configuration to obtain the label and the target service of the target device 30.

In some scenarios, the user may simply just say that the voice mentions the device's tag and target service, but the user's semantics are not intended to request the target device 30 to perform the target service. The calling device 10 can recognize the user's voice, and resolve whether the user's voice input is a service request, i.e., resolve whether the content of the user's voice input is a request for the target device 30 to perform a target service. If the service request is a service request, the tag and the target service of the target device 30 corresponding to the service request are obtained.

Referring to fig. 2 and 5, in some embodiments, the calling device 10 further includes a device management module 13. After the text parsing module 12 obtains the tag of the target device 30, the device management module 13 is invoked 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 acquired by the text parsing module 12 into a service call URL (URL), and the device management module 13 connects to the service gateway 31 of the target device 30 through the service call URL to call the target device 30.

Referring to fig. 6, in some embodiments, the semantic configuration includes an intent slot including a first variable characterizing a tag of the target device 30 and a second variable characterizing the target service, an intent dictionary including synonyms of the first variable and the second variable including a preset sentence pattern, an intent dictionary including an intent corpus, and an intent reply. The intent reply includes an operation performed when the matching of the text information and the intent corpus is successful.

Referring to fig. 7, in some embodiments, 013: parsing the text information according to the semantic configuration to obtain the tag and the target service of the target device 30 includes:

0131: matching the text information with the intention corpus; and

0132: after the matching is successful, the variable value of the intended slot is obtained to obtain the tag and the target service of the target device 30.

Referring to fig. 2 and 5, in some embodiments, the text parsing module 12 is further configured to perform the methods of 0131 and 0132. That is, the text parsing module 12 is further configured to match the text information with the intention corpus; and after the matching is successful, obtaining the variable value of the intended slot position to obtain the label and the target service of the target device 30.

Referring to FIG. 6, in some embodiments, the intention dictionary includes a primary word and a synonym of the primary word. One variable of the intent slot corresponds to one intent dictionary. The intention corpus is preset as a sentence consisting of a mood prefix, a main word in the intention dictionary or a synonym of the main word, and a mood suffix. Wherein the mood prefix precedes a primary word or a synonym of the primary word in the intent dictionary and the mood suffix precedes the primary word or the synonym of the primary word in the intent dictionary. When matching the text information with the intention corpus, the matching of the text information and the intention corpus can be determined only if the text information is matched with the prefix of the mood, the main word in the intention dictionary or the synonym of the main word, and the suffix of the mood; or matching the text information with the composition in the intention dictionary or the synonym of the main word, and determining that the matching of the text information and the intention corpus is successful when the text information is matched with one of the prefix and the suffix of the mood. And may be set according to an application scenario, which is not limited herein.

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

For example, the main word of the first dictionary includes "watch", and synonyms corresponding to the main word "watch" in the first dictionary include "wristwatch", "electronic watch", "mechanical watch". The primary word of the second dictionary comprises "find", and the synonyms corresponding to the primary word "find" in the second dictionary comprise "find", "search". The preset tone prefixes include "please", "help me" and "help". The preset tone suffixes include "good doing", "can doing" and "go". The text information is 'please help me find the position of the watch 1', the text information is matched with the intention corpus, in the text information, 'please' and 'help me' can be matched with a preset mood prefix, 'finding' can be matched with a second dictionary, 'watch' can be matched with a first dictionary, and then the text information and the intention corpus can be determined to be successfully matched. After the matching is successful, the tag of the target device 30 is obtained according to a first variable "watch" corresponding to the main word of the first dictionary: the watch 1 searches for and obtains target service according to a second variable corresponding to a main word of a second dictionary: a "lookup" service.

For another example, the main words of the first dictionary further include "TV" and "sound", the synonyms corresponding to the main word "TV" in the first dictionary include "color TV" and "TV", and the synonyms corresponding to the main word "sound" include "loudspeaker" and "music player". The main word of the second dictionary also comprises 'start', and synonyms corresponding to the main word 'start' in the second dictionary comprise 'start', 'open' and 'open'. Is the text message "do it turn on tv and sound? "matching the text information with the intention corpus, wherein in the text information," open "can be matched with the second dictionary," television "and" stereo "can be matched with the first dictionary," good "can be matched with the mood suffix, and then the text information and the intention corpus can be determined to be successfully matched. After the matching is successful, the tag of the target device 30 is obtained according to the first variables "television" and "audio" corresponding to the main word of the first dictionary: "television" and "sound", acquiring the target service according to a second variable "start" corresponding to the main word of the second dictionary: "start" the service. In this case, the target device 30 includes both a television and a stereo, and the "start-up" service is ultimately performed on both the television and the stereo.

The intent reply includes an operation performed when the matching of the text information and the intent corpus is successful. Referring to fig. 5, in one embodiment, the predetermined intention is returned as: and when the matching of the text information and the intention corpus is successful, calling the target equipment 30 from at least one piece of equipment to be adjusted according to the address of the target equipment 30. For example, when the matching of the text information and the intention corpus is successful, the text parsing module 12 calls the device 10 management module to send a call request to the target device 30.

In certain embodiments, 02: acquiring the address of the target device 30 from the server according to the tag, including:

021: whether the account numbers of the target equipment and the calling equipment are related or not is confirmed at the server; and

022: and under the condition that the target equipment is associated with the account of the calling equipment, acquiring the address of the target equipment.

Referring to FIG. 2, in some embodiments, the calling device 10 is also configured to perform the methods of 021 and 022. That is, the calling device 10 is further configured to determine, at the server, whether the target device is associated with the account of the calling device; and acquiring the address of the target equipment under the condition that the account of the target equipment is associated with the account of the calling equipment.

The account number may be a mobile phone number, an ID of a calling device, a registered account number corresponding to a service, and the like, which is not limited herein. Under the condition that the target equipment is associated with the account number of the calling equipment, the address of the target equipment is obtained, the target equipment can be ensured to be called by the calling equipment under the same associated account number, the calling equipment for calling is ensured to be trusted equipment, and therefore the target equipment can be prevented from being called illegally by equipment with potential safety hazards.

Referring to fig. 8, in some embodiments, 04: executing a target service on the target device 30, comprising:

041: acquiring service definition information according to a target service;

042: acquiring an identifier of an installation package corresponding to a target service from a server according to service definition information;

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

044: when the installation package exists in the target device 30, the installation package is installed and the target service is executed.

Referring to fig. 2 and 9, in some embodiments, the target device 30 includes a service management module 32 and a service lifecycle management module 33. The service management module 32 is used for executing the

methods

041, 042 and 043, and the service lifecycle management module 33 is used for executing the methods 044. That is, the service management module 32 is configured to obtain service definition information according to a target service; acquiring an identifier of an installation package corresponding to a target service from a server according to service definition information; and searching whether the target device 30 has an installation package corresponding to the target service according to the identifier. The service management module 32 is configured to install the installation package when the installation package exists in the target device 30, and execute the target service.

In some embodiments, to reduce the storage footprint of the target device 30, the target service is stored locally to 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 a target service according to the calling request, installs an installation package corresponding to the target service, executes the target service, and unloads the target service after the execution of the target service is completed. For example, if the target service is a "find" service, execution of the "find" service by target device 30 may initiate a "find" procedure that invokes the speaker of target device 30 to sound "i am here". Generally, the frequency of use of the "lookup" service is low, so that in order to avoid the "lookup" program occupying the space of the target device 30, the target device 30 does not store the "lookup" program, and the "lookup" program is installed only through the installation package corresponding to the "lookup" service when the "lookup" service needs to be executed.

In some embodiments, the service definition information includes at least one of a service tag, a service ID, a service invocation protocol, a service participation, and a service participation. From the service definition information, an installation package corresponding to the service can be specified. For example, for a service, there exists a unique corresponding installation package identifier for the service ID of the service, 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 executing the service.

Referring to fig. 9, in an embodiment, the cloud server 20 stores service definition information corresponding to a plurality of services that have been registered. The invocation request sent by the invoking device 10 to the target device 30 includes the target service that needs to be executed at the target device 30. The target device 30 requests to invoke the cloud server 20 to search the service definition information corresponding to the target service from the plurality of service definition information.

In yet another embodiment, the invocation request sent by the invoking 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 041: and acquiring 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 the service definition information corresponding to the target service from the plurality of service definition information. The target device 30 obtains the service definition information according to the call request, and executes the method in 042 after performing basic verification on the service definition information: and acquiring the identifier of the installation package corresponding to the target service from the server according to the service definition information. The basic check includes checking integrity and validity of a service ID, a service invocation protocol, service participation, or service participation, which are not listed here.

Referring to fig. 2 and 9, in some embodiments, the cloud server 20 includes a service gateway 21, a service pack 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 the service definition information to the service definition management module 23. The service definition management module 23 queries the service definition information corresponding to the request stored in the service definition management module 23 according to the request for acquiring the service definition information, 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 calling device 10 sends the request to the service gateway 21, 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 identifier. 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 for obtaining the service definition information to the service gateway 21, the service gateway 21 forwards the request for obtaining the service definition information to the service definition management module 23 to obtain the service definition information; after the service gateway 21 acquires the service definition information, sending a request for acquiring an identifier to the service package management module 22 according to the service definition information, so as to acquire the identifier of the installation package corresponding to the target service from the service package management module 22; finally, the service gateway 21 returns the service definition information and the identifier of the installation package corresponding to the target service to the target device 30.

In another embodiment, the target device 30 sends a request for obtaining the identifier to the service gateway 21 according to the service definition information, the service gateway 21 forwards the request for obtaining the identifier to the service package management module 22, queries the installation package corresponding to the service definition information included in the request for obtaining the identifier through the service package paradigm module, returns the identifier of the installation package corresponding to the service definition information to the service gateway 21, and then the service gateway 21 returns the identifier to the target device 30.

The target device 30 searches whether the target device 30 locally has an installation package corresponding to the target service according to the identifier of the installation package corresponding to the target service, installs the installation package when the installation package exists in the target device 30, and executes the target service.

Referring to fig. 10, in some embodiments, 04: executing a target service on the target device 30, comprising:

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

046: and installing the installation package and executing the target service.

Referring to fig. 2 and 9, in some embodiments, the service management module 32 is further configured to perform the method of 045, and the service life cycle management module 33 is further configured to perform the method of 046. That is, the service management module 32 is configured to acquire the installation package corresponding to the target service from the server when the installation package does not exist in the target device 30.

When the installation package does not exist in the target device 30, the service management module 32 sends an installation package obtaining request to the cloud server 20, where the installation package obtaining request includes an identifier 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, and the service package management module 22 queries a corresponding installation package file according to the identifier of the installation package, returns the installation package file to the service gateway 21, and transmits the installation package file to the target device 30 through the service gateway 21. Or the service package management module 22 returns the address of the installation package file corresponding to the identifier query of the installation package to the service gateway 21, the service gateway 21 returns the address of the installation package file to the target device 30, and 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.

Referring to fig. 11, in some embodiments, 04: executing the target service on the target device 30, further comprising:

047: subscribing to a target service in a server;

045: obtaining an installation package corresponding to a target service from a server, comprising:

0451: after the installation package in the server is updated, acquiring the updated installation package from the server;

046: installing the installation package and executing the target service, including:

0461: and installing the updated installation package and executing the target service.

Referring to fig. 2 and 9, in some embodiments, the service management module 32 is further configured to perform the methods of 047 and 0451, and the service life cycle management module 33 is further configured to perform the method of 0461. That is, the service management module 32 is configured to subscribe to a target service in the server; and after the installation package in the server is updated, acquiring the updated installation package from the server. The service lifecycle 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 further 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 of the target device 30, the service gateway 21 forwards the installation package acquisition request to the service package management module 22 to acquire the latest installation package, and pulls up the service subscription management module 24 to increase the subscription relationship with the target device 30, so that the target device 30 subscribes to the target service.

In some embodiments, in the case that 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 management module 24 sends an installation package synchronization request to the target device 30 subscribed to the target service, the installation package synchronization request includes information of the updated installation package, for example, address information of an updated installation package file, and the target device 30 downloads the updated installation package from the server according to the information of the updated installation package.

Referring to fig. 12, in some embodiments, the service calling method further includes:

06: and reserving the subscription and/or installation package according to a preset reservation strategy.

Referring to fig. 2 and 9, in some embodiments, the service life cycle management module 33 is further configured to perform the method of 06. That is, the service lifecycle management module 33 is further configured to reserve the subscription and/or installation package according to a preset reservation policy.

In some embodiments, to reduce the storage space usage of the target device 30, whether to reserve the installation package is selected according to a preset reservation policy. For example, the preset reservation policy is set to: detecting the use frequency of a target service; in the case that the target service usage frequency is high, the installation package is retained, so that the target device 30 can install the installation package in time and execute the target service; in the case that the target service usage frequency is low, the installation package is deleted, and the target device 30 acquires the installation package of the target service from the cloud server 20 again the next time the target device 30 is called.

Similarly, in some embodiments, in a case that the frequency of the target device 30 being called is high, or in a case that the update frequency of the target service is high, the subscription relationship between the target device 30 and the target service is preserved, so as to reduce the links of the target device 30 to be called subsequently, and improve the response speed; in the case that the frequency of the target device 30 being called is low, the subscription relationship between the target device 30 and the target service is cancelled, so that the target device 30 is prevented from frequently updating the installation package even in the case that the frequency of the being called is low.

Referring to fig. 13, in some embodiments, the service invocation method further includes:

07: and unloading the target service from the target device 30 according to the preset unloading strategy.

Referring to fig. 2 and 9, in some embodiments, the service lifecycle management module 33 is further configured to perform the method of 07. That is, the service lifecycle management module 33 is further configured to offload the target service from the target device 30 according to a preset offload policy.

In some embodiments, the preset offloading policy is set to: after the target service is executed for the preset time period, the target service is unloaded from the target device 30. For example, if the preset duration is immediate uninstallation, the target service is uninstalled immediately after the target service is executed. For another example, if the preset time is 2 hours, the target service is unloaded if the target service is not called again and executed within 2 hours after the target service is executed. In this way, the memory space occupation of the target device 30 can be saved.

Referring to fig. 2 and 3, in some embodiments, the target service includes an offload service, and the execution of the offload service at the target device 30 can offload other services local to the target device 30, for example, offload other target services that are executed completely.

For example, the target service includes an offload service and a lookup service. In an application scenario, where the target device 30 is a wristwatch 1, the wristwatch 1 has completed execution of the lookup service, and the user inputs a voice to the invoking device 10: "help me to unload the search program of watch 1". Referring to fig. 1, the invoking device 10 executes the service invoking methods of 01, 02, and 03 according to the voice input of the user, that is, the invoking device 10 obtains the tag and the target service of the target device 30 according to the first input, obtains the address of the target device 30 from the server according to the tag, and confirms the target device 30 from at least one device to be invoked according to the address. The target device 30 executes the service invocation method in 04, i.e., the target device 30 executes the target service. The calling device 10 obtains the label of the target device 30 as "watch 1", and the target service is an "uninstall" service, specifically, a "search program for uninstalling the watch 1". The calling device 10 encapsulates the address of the wristwatch 1 and the parameter of the "unload" service as a calling URL, and sends a call request for the unload service to the wristwatch 1. The watch 1 executes the "uninstall" service according to the call request of the uninstall service, uninstalling the local "find" program.

Referring to fig. 14, in some embodiments, the service invocation method further includes:

08: the target service is registered in the server.

Referring to fig. 2 and 15, in some embodiments, the cloud server 20 is configured to perform the method of 08. That is, the cloud server 20 is used to register the target service.

Referring to fig. 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 an installation package of the service from the cloud server 20 to locally install and execute the service on the target device 30. In some embodiments, the developer adds the tags of the registered services to the intent dictionary, enables the calling device 10 to perform a text information parsing according to the intent dictionary, and matches the service tags in the text information with the tags of the registered services in the intent dictionary to obtain the target service.

Referring to fig. 15, in some embodiments, the developer registers the target service, including uploading an installation package of the target service to the cloud server 20 and uploading service definition information of the target service to the cloud server 20. Referring to fig. 16, in some embodiments, 08: registering the target service in the server, comprising:

081: storing the installation package and outputting the identifier of the installation package according to the installation package uploading request;

082: receiving a registration service definition request, the registration service definition request including service definition information associated with the identifier; and

083: service definition information is saved.

Referring to fig. 2 and 15, in some embodiments, the cloud server 20 includes a service pack management module 22, a service gateway 21, and a service definition management module 23. Service package management module 22 is used to execute the method in 081, service gateway 21 is used to execute the method in 082, and service definition management module 23 is used to execute the method in 083. That is, the service package management module 22 is configured to store the installation package and output an identifier of the installation package according to the installation package uploading request. The service gateway module is configured to receive a registration service definition request. The service definition management module 23 is used for saving service definition information.

Referring to fig. 15, in some embodiments, a developer sends an installation package upload request corresponding to a target service to a service gateway, where the installation package upload request includes an installation package file. The service gateway forwards the installation package uploading request to the service package management module 22, the service package management module 22 stores the installation package file to a file warehouse of the cloud server 20 according to the installation package uploading request, and outputs information of the installation package in the cloud server 20, the information of the installation package includes an address of the installation package file, an identifier of the installation package and the like, the service package management module 22 returns the identifier of the installation package to the service gateway, and the identifier of the installation package is returned to developers through the service gateway.

And the developer associates the service definition information of the target service with the identifier of the installation package of the target service and sends a registration service definition request to the service gateway, wherein the registration service definition request comprises 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.

Referring to fig. 9, after the target service is registered, the service package management module 22 stores installation package information, and the service definition management module 23 stores service definition information. When the target device 30 initiates a request for obtaining the service definition information to 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 definition information to the target device 30 through the service gateway. When the target device 30 initiates a request for obtaining the installation package to 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 address information of the installation package to the target device 30 through the service gateway, so that the target device 30 downloads the installation package according to the address information of the installation package.

Referring to fig. 17, in some embodiments, the service invocation method further includes:

09: and updating the target service in the server.

Referring to fig. 2 and 18, in some embodiments, the cloud server 20 is configured to execute the method of 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 the 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 latest installation package of the service from the cloud server 20.

Referring to fig. 19, in some embodiments, 09: updating a target service in a server, comprising:

091: storing the updated installation package and outputting the identification of the updated installation package according to the new installation package uploading request;

092: receiving an update service definition request, wherein the update service definition request comprises service definition information associated with the updated identifier of the installation package; and

093: and saving the service definition information associated with the updated identifier of the installation package.

Referring to fig. 2 and 18, in some embodiments, the service pack management module 22 is further configured to execute the method in 091, the service gateway module is further configured to execute the method in 092, and the service definition management module 23 is further configured to execute the method in 093. That is, the service package management module 22 is further configured to store the updated installation package and output an identifier of the updated installation package according to the new installation package uploading request. The service gateway module is further configured to receive an update service definition request. The service definition management module 23 is further configured to store service definition information associated with the identifier of the updated installation package.

Referring to fig. 18, in some embodiments, the developer sends a new installation package upload request corresponding to the updated target service to the service gateway, where the new installation package upload request includes a new installation package file. The service gateway forwards the new installation package uploading request to the service package management module 22, the service package management module 22 stores the new installation package file to the file warehouse of the cloud server 20 according to the new installation package uploading request, and outputs information of the new installation package in the cloud server 20, the information of the new installation package includes an address of the new installation package file, an identifier of the new installation package, and the like, the service package management module 22 returns the identifier of the new installation package to the service gateway, and the identifier of the new installation package is returned to developers through the service gateway.

The service package management module 22 also calls a service package synchronization processing request including information of the new installation package through the service subscription management module 24 according to 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 module 32 of the target device 30 updates the information of the installation package of the target service, and after the update is successful, the target device 30 returns a response to the cloud server 20. In this manner, 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 identification of the new installation package of the new target service, and sends an update service definition request to the service gateway, wherein the update service definition request comprises the service definition information associated with the identification of the updated installation package. The service gateway forwards the update service definition request to the service definition management module 23, and the service definition management module 23 stores the service definition information associated with the identifier of the updated installation package in the cloud server 20.

Referring to fig. 20 and fig. 21, the present embodiment further provides a service invoking method and invoking equipment 200. The service calling method comprises the following steps:

0101: acquiring a label and a target service of a target device according to a first input to the calling device 200;

0102: acquiring the address of the target equipment from the server according to the label; and

0103: and confirming the target equipment from at least one piece of equipment to be adjusted according to the address so as to enable the target equipment to execute the target service.

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

Referring to fig. 2 and 21, in some embodiments, the calling device 200 may participate in 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 configured to execute the service calling method executed by the calling device 10 in the above embodiment, and will not be described herein again.

Referring to fig. 22 and 23, the present invention further provides a service invoking method and a target device 300. The service calling method comprises the following steps:

0201: acquiring service definition information according to a target service input by calling equipment;

0202: acquiring an identifier of an installation package corresponding to a target service from a server according to service definition information;

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

0204: when the installation package exists in the target device 300, the installation package is installed and the target service is executed.

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

Referring to fig. 2, fig. 3 and fig. 23, in some embodiments, the target device 300 may participate in forming the service invocation system 100, as a device to be invoked in the service invocation system 100, and becomes the target device 30 in fig. 2 when the target device 300 is invoked. In the calling system, the target device 300 may be configured to execute the service calling method executed by the target device 30 in the foregoing embodiment, and details are not described here.

Referring to fig. 24, the present application further provides a non-volatile computer-readable storage medium 400 containing a computer program 401. One or more non-transitory computer-readable storage media 400 embodying a computer program 401 that, when executed by one or more processors 402, causes the processors 402 to perform the service invocation methods of any of the embodiments described above, e.g., implementing one or more of

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, the computer program 401, when executed by the one or more processors 402, causes the processors 402 to perform the steps of:

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

04: the target service is executed on the target device 30.

In the description of the present specification, reference to the description of "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples" or "some examples", etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is 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 particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Moreover, various embodiments or examples and features of various embodiments or examples described in this specification can be combined and brought together by those skilled in the art without contradiction.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.

Although embodiments of the present application have been shown and described above, it is to be understood that the above embodiments are exemplary and not to be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.

Claims

1. A service invocation method, characterized by comprising:

acquiring a label and a target service of target equipment according to a first input to calling equipment;

acquiring the address of the target equipment from a server according to the label;

confirming the target equipment from at least one piece of equipment to be adjusted according to the address; and

executing the target service on the target device.

2. The service invocation method according to claim 1, wherein the executing the target service on the target device comprises:

acquiring service definition information according to the target service;

acquiring an identifier of an installation package corresponding to the target service from the server according to the service definition information;

searching whether the target equipment has an installation package corresponding to the target service or not according to the identifier; and

and when the installation package exists in the target equipment, installing the installation package and executing the target service.

3. The service invocation method according to claim 2, wherein the executing the target service on the target device further comprises:

when the installation package does not exist in the target equipment, acquiring the installation package corresponding to the target service from the server; and

and installing the installation package and executing the target service.

4. The service invocation method according to claim 3, wherein said executing the target service on the target device further comprises:

subscribing to the target service in the server;

the obtaining of the installation package corresponding to the target service from the server includes:

after the installation package in the server is updated, acquiring the updated installation package from the server;

the installing the installation package and executing the target service comprises:

and installing the updated installation package and executing the target service.

5. The service invocation method according to claim 4, further comprising:

and reserving the subscription and/or the installation package according to a preset reservation strategy.

6. The service invocation method according to claim 1, wherein the target service comprises an offload service and a lookup service.

7. The service invocation method according to claim 1, further comprising:

and unloading the target service from the target equipment according to a preset unloading strategy.

8. The service invocation method according to claim 1, wherein said first input comprises a voice input; the obtaining of the tag and the target service of the target device according to the first input to the calling device includes:

converting the voice input into text information;

acquiring preset semantic configuration; and

and analyzing the text information according to the semantic configuration to acquire the label of the target equipment and the target service.

9. The service invocation method according to claim 8, wherein the semantic configuration includes an intent slot, an intent dictionary, an intent corpus, and an intent reply, wherein the intent slot includes a first variable and a second variable, wherein the first variable characterizes a tag of the target device, wherein the second variable characterizes the target service, wherein the intent dictionary includes synonyms of the first variable and the second variable, and wherein the intent corpus includes a preset sentence pattern; the analyzing the text information according to the semantic configuration to obtain the label of the target device and the target service comprises:

matching the text information with the intention corpus; and

and after the matching is successful, obtaining a variable value of the intention slot position so as to obtain the label of the target equipment and the target service.

10. The service invocation method according to claim 1, further comprising:

registering the target service in the server.

11. The service invocation method according to claim 10, wherein the registering the target service in the server comprises:

according to an installation package uploading request, storing the installation package and outputting an identifier of the installation package;

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

and saving the service definition information.

12. The service invocation method according to claim 10, characterized in that the target service in the server is updated.

13. The service invocation method according to claim 12, wherein said updating the target service in the server comprises:

storing the updated installation package and outputting the identifier of the updated installation package according to the new installation package uploading request;

receiving an update service definition request, wherein the update service definition request comprises service definition information associated with the updated identifier of the installation package; and

and saving the service definition information associated with the updated identifier of the installation package.

14. The service invocation method according to claim 1, wherein the obtaining the address of the target device from the server according to the tag comprises:

confirming whether the target equipment is associated with the account number of the calling equipment or not at the server; and

and acquiring the address of the target equipment under the condition that the account of the target equipment is associated with the account of the calling equipment.

15. A service calling system is characterized by comprising calling equipment, target equipment and a server;

the calling device is configured to: acquiring a label and a target service of the target equipment according to a first input, acquiring an address of the target equipment from the server according to the label, and confirming the target equipment from at least one piece of equipment to be adjusted according to the address;

the target device is used for executing the target service.

16. A service invocation method, characterized by comprising:

acquiring the address of the target equipment from a server according to the label; and

and confirming the target equipment from at least one piece of equipment to be adjusted according to the address so as to enable the target equipment to execute the target service.

17. An invoking device, comprising:

the analysis module is used for acquiring the label and the target service of the target equipment according to the first input;

the first acquisition module is used for acquiring the address of the target equipment from the server according to the label;

the confirming module is used for confirming the target equipment from at least one equipment to be regulated according to the address; and

and the calling module is used for calling the target equipment to execute the target service.

18. A service invocation method, characterized by comprising:

acquiring service definition information according to a target service input by calling equipment;

acquiring an identifier of an installation package corresponding to the target service from a server according to the service definition information;

searching whether the target equipment has an installation package corresponding to the target service or not according to the identification; and

19. A target device, comprising:

the second acquisition module is used for acquiring service definition information according to the target service input by the calling equipment;

a third obtaining module, configured to obtain, from a server according to the service definition information, an identifier of an installation package corresponding to the target service;

the determining module is used for searching whether the target equipment has an installation package corresponding to the target service according to the identifier; and

and the execution module is used for installing the installation package and executing the target service when the installation package exists in the target equipment.

20. A non-transitory computer readable storage medium containing a computer program which, when executed by one or more processors, causes the processors to implement the service invocation method of any of claims 1-14.