Method and apparatus for calling service, device, and storage medium

Abstract

The present application relates to the technical field of the Internet of Things, and discloses a method and apparatus for calling a service, a device, and a storage medium. The method comprises: generating a service calling instruction, the service calling instruction comprising a service identifier and a path input parameter value; sending the service calling instruction to a second terminal; and receiving a service calling response sent by the second terminal, the service calling response being used for indicating an execution result of the second terminal executing the service calling instruction. The service identifier is used for indicating services for a plurality of peer functional entities in the second terminal. Each functional entity among the plurality of peer functional entities corresponds to a respective path parameter value, and the path input parameter value is a subset of the path parameter values. The path input parameter value is determined from among the path parameter values, and then a corresponding service calling instruction is generated, so that a plurality of service sets corresponding to the plurality of peer functional entities can become a service for the plurality of peer functional entities.

Description

Service calling method, device, equipment and storage medium Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to a service calling method, apparatus, device and storage medium. Background Art

[0002] With the development of Internet of Things (IoT) technology, many IoT devices are equipped with intelligent control service functions. For example, in-vehicle devices provide window closing / opening services.

[0003] In the related art, specific services are provided for specific IoT devices or functional entities in IoT devices. For example, one service is provided for a vehicle with four windows, and another service is provided for a vehicle with six windows; or four services are provided for each of the four windows of the same vehicle.

[0004] The services provided by the above method are difficult to accurately define for uncertain IoT devices or functional entities in IoT devices. For example, the service for a vehicle with four windows cannot be simultaneously applicable to a vehicle with six windows. In other words, the services provided by the above method are fixed in a certain form and lack universality.

[0005] Summary of the Invention

[0006] The present invention provides a method, apparatus, device, and storage medium for invoking a service. The technical solution is as follows:

[0007] According to one aspect of the present application, a method for invoking a service is provided, the method being executed by a first terminal, the method comprising:

[0008] Generate a service call instruction, wherein the service call instruction includes a service identifier and a path input parameter value;

[0009] Sending the service calling instruction to the second terminal;

[0010] receiving a service call response sent by the second terminal, where the service call response is used to indicate an execution result of the service call instruction executed by the second terminal;

[0011] The service identifier is used to indicate services for multiple peer functional entities in the second terminal, each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value.

[0012] According to one aspect of the present application, a method for invoking a service is provided, the method being executed by a second terminal, the method comprising:

[0013] receiving a service call instruction sent by the first terminal, wherein the service call instruction includes a service identifier and a path input parameter value;

[0014] Sending a service call response to the first terminal, where the service call response is used to indicate the execution result of the service call instruction executed by the second terminal;

[0015] The service identifier is used to indicate services for multiple peer functional entities in the second terminal, each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value.

[0016] According to one aspect of the present application, a device for invoking a service is provided, the device comprising:

[0017] A generating module, configured to generate a service calling instruction, wherein the service calling instruction includes a service identifier and a path input parameter value;

[0018] A sending module, configured to send the service calling instruction to the second terminal;

[0019] a receiving module, configured to receive a service call response sent by the second terminal, wherein the service call response is used to indicate an execution result of the service call instruction executed by the second terminal;

[0020] The service identifier is used to indicate services for multiple peer functional entities in the second terminal, each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value.

[0021] According to one aspect of the present application, a device for invoking a service is provided, the device comprising:

[0022] A receiving module, configured to receive a service call instruction sent by the first terminal, wherein the service call instruction includes a service identifier and a path input parameter value;

[0023] a sending module, configured to send a service call response to the first terminal, wherein the service call response is used to indicate an execution result of the service call instruction executed by the second terminal;

[0024] The service identifier is used to indicate services for multiple peer functional entities in the second terminal, each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value.

[0025] According to one aspect of the present application, a terminal device is provided, which includes: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the service calling method described in the above aspect.

[0026] According to one aspect of the present application, a computer-readable storage medium is provided, in which executable instructions are stored. The executable instructions are loaded and executed by the processor to implement the service calling method described in the above aspect.

[0027] According to one aspect of the present application, a computer program product is provided, which includes computer instructions, the computer instructions are stored in a computer-readable storage medium, a processor of a communication device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the communication device executes to implement the service calling method described in the above aspect.

[0028] According to one aspect of the present application, a computer program is provided. When the computer program product is run on a processor of a communication device, the communication device is enabled to execute and implement the service calling method as described in the above aspect.

[0029] The technical solutions provided by the embodiments of the present application include at least the following beneficial effects:

[0030] A service call instruction including a service identifier and a path input parameter value is generated by the first terminal to call a service in the second terminal. The service identifier is used to indicate a service in the second terminal for multiple peer functional entities. Each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value. Since each of the multiple peer functional entities corresponds to its own path parameter value, by determining the path input parameter value from the path parameter value and then generating the corresponding service call instruction, multiple services corresponding to the multiple peer functional entities can be integrated into a service for the multiple peer functional entities, thereby implementing the call of a common service by determining the path input parameter value. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0032] FIG1 shows a schematic diagram of a service invocation system provided by some exemplary embodiments of the present application;

[0033] FIG2 is a flow chart showing a method for invoking a service provided by some exemplary embodiments of the present application;

[0034] FIG3 is a flow chart showing a method for invoking a service provided in some exemplary embodiments of the present application;

[0035] FIG4 is a flow chart showing a method for invoking a service provided by some exemplary embodiments of the present application;

[0036] FIG5 is a schematic diagram showing a flow chart of a method for invoking a service provided in some exemplary embodiments of the present application;

[0037] FIG6 shows a schematic diagram of an interactive interface provided by some exemplary embodiments of the present application;

[0038] FIG7 is a flow chart showing a method for invoking a service provided by some exemplary embodiments of the present application;

[0039] FIG8 is a flow chart showing a method for invoking a service provided by some exemplary embodiments of the present application;

[0040] FIG9 shows a schematic diagram of a display interface provided by some exemplary embodiments of the present application;

[0041] FIG10 is a flow chart showing a method for invoking a service provided in some exemplary embodiments of the present application;

[0042] FIG11 is a flow chart showing a method for invoking a service provided by some exemplary embodiments of the present application;

[0043] FIG12 is a flow chart showing a method for invoking a service provided in some exemplary embodiments of the present application;

[0044] FIG13 is a flow chart showing a method for invoking a service provided by some exemplary embodiments of the present application;

[0045] FIG14 is a flow chart showing a method for invoking a service provided by some exemplary embodiments of the present application;

[0046] FIG15 shows a structural block diagram of a service invoking device provided by some exemplary embodiments of the present application;

[0047] FIG16 shows a structural block diagram of a service-invoked device provided by some exemplary embodiments of the present application;

[0048] FIG17 shows a schematic structural diagram of a terminal device provided in some exemplary embodiments of the present application. DETAILED DESCRIPTION

[0049] To make the objectives, technical solutions, and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail herein, with examples shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are merely examples of devices and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0050] The terms used in the examples of this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms "a," "the," and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0051] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present application, these information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0052] FIG1 shows a schematic diagram of a service invocation system 10 provided by an exemplary embodiment of the present application. The service invocation system 10 includes a first terminal 11 and a second terminal 12 .

[0053] The first terminal 11 / second terminal 12 in this application is also called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, and user device. The mobile terminal includes but is not limited to: handheld devices, wearable devices, vehicle-mounted devices and Internet of Things devices, such as: mobile phones, tablet computers, e-book readers, laptop computers, desktop computers, televisions, game consoles, mobile Internet devices (MID), augmented reality (AR) terminals, virtual reality (VR) terminals and mixed reality (MR) terminals, wearable devices, handles, electronic tags, controllers, wireless terminals in industrial control (Industrial Control), wireless terminals in self-driving (Self Driving), wireless terminals in remote medical (Remote Medical), wireless terminals in smart grid (Smart Grid), wireless terminals in transportation safety (Transportation Safety), wireless terminals in smart city (Smart City), wireless terminals in smart home (Smart Home), wireless terminals in remote medical surgery (Remote Medical Surgery), cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLAN) phones, etc. Loop (WLL) stations, personal digital assistants (PDA), TV set-top boxes (STB), customer premises equipment (CPE), etc.

[0054] The first terminal 11 and the second terminal 12 in this application can be the same terminal or different terminals. In the embodiments of this application, the first terminal 11 and the second terminal 12 are different terminals. For example, the first terminal 11 is a mobile phone and the second terminal 12 is an in-vehicle device.

[0055] In some embodiments, the first terminal 11 and the second terminal 12 can communicate via a network or via a Universal Serial Bus (USB), etc., which is not limited in this application. In some embodiments, the first terminal 11 and / or the second terminal 12 are used to interact with the user. The first terminal 11 sends a service call instruction to the second terminal 12, causing the second terminal 12 to call a service based on the received service call instruction. As shown in Figure 1, the user 13 configures the first terminal 11 so that the first terminal 11 generates a corresponding service call instruction, which is then sent by the first terminal 11 to the second terminal 12.

[0056] The technical solutions provided in the embodiments of the present application can also be applied to machine type communication (MTC), long term evolution technology for machine-to-machine communication (LTE-M), device-to-device (D2D) network, machine-to-machine (M2M) network, IoT network or other networks. Among them, the IoT network may include, for example, the Internet of Vehicles. Among them, the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other devices (Vehicle to X, V2X, X can represent anything), for example, the V2X may include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian communication (V2P) or vehicle to network (V2N) communication, etc.

[0057] Those skilled in the art will appreciate that the number of the first terminals 11 or second terminals 12 can be greater or lesser. For example, there can be only one first terminal 11 or second terminal 12, or there can be dozens, hundreds, or even more of the first terminals 11 or second terminals 12. The embodiments of this application do not limit the number or device type of the first terminals 11 or second terminals 12. In some embodiments, one first terminal 11 can correspond to one or more second terminals 12. In some embodiments, one second terminal 12 can correspond to one or more first terminals 11.

[0058] In the embodiment of the present application, an example is given in which the second terminal 12 is a vehicle-mounted device and the vehicle-mounted device provides a window closing service.

[0059] An onboard device is a terminal device used to control a vehicle. Vehicle control is achieved by invoking services corresponding to various vehicle functional entities within the onboard device. Optionally, different vehicle functional entities may correspond to different services, or each vehicle functional entity may correspond to a single service. However, in this case, service development is required for each vehicle functional entity. Alternatively, different vehicle functional entities may correspond to the same service, for example, by integrating multiple services corresponding to multiple equivalent vehicle functional entities into a common service.

[0060] Specifically, the multiple peer functional entities of the vehicle can be classified into at least one of the following:

[0061] Door locks: interior lock, exterior lock, trunk lock, front hood lock, ...;

[0062] Car windows: windows in different working states, windows in different positions, windows in different modes, etc.;

[0063] Doors: doors in different working states, doors in different positions, doors in different modes, etc.;

[0064] Wipers: wipers in different working states, wipers in different working modes, etc.;

[0065] Headlights: high beam, low beam, turn signal, hazard warning light, position light, rear fog light, ...;

[0066] Exterior rearview mirror: exterior rearview mirror, exterior rearview mirror at different angles, ….

[0067] In the related art, for a vehicle including four windows (including the left front window, the left rear window, the right front window, and the right rear window), the on-board equipment will provide four window closing services, including the left front window closing service, the left rear window closing service, the right front window closing service, and the right rear window closing service. Although the left front window, the left rear window, the right front window, and the right rear window of the vehicle all belong to the peer functional entities of the vehicle, it is still necessary to develop corresponding services for each functional entity. That is, the services provided in the related art are not universal for the peer functional entities of the vehicle. In order to solve the problems existing in the above-mentioned technology, an embodiment of the present application provides a method for calling a service. FIG2 shows a flowchart of the method for calling a service provided by an exemplary embodiment of the present application. Exemplarily, the method is executed by the first terminal 11 shown in FIG1 , and the method includes:

[0068] Step 120: Generate a service call instruction;

[0069] The service call instruction is used to instruct the second terminal to execute the corresponding service according to the service call instruction. Exemplarily, the service call instruction is used to instruct the vehicle-mounted device to execute the service of closing the left front window.

[0070] In some embodiments, the service call instruction includes a service identifier and a path input parameter value.

[0071] The service identifier is used to indicate the service for multiple peer functional entities in the second terminal. In some embodiments, the second terminal includes at least one service, and at least one service includes the service for multiple peer functional entities. Exemplarily, the left front window, the left rear window, the right front window, and the right rear window belong to peer functional entities, and the service for multiple peer functional entities includes the window closing service. Optionally, the service identifier is an identifier including numbers. Exemplarily, the service identifier "1000" corresponds to the window closing service. Optionally, the service identifier is an identifier including letters. Exemplarily, the service identifier "A" corresponds to the window closing service. Optionally, the service identifier is a mixed identifier including numbers and letters. Exemplarily, the service identifier "A1" corresponds to the window closing service. The embodiment of the present application does not limit the form of expression of the service identifier.

[0072] In some embodiments, the multiple peer functional entities refer to functional entities of the same type controlled by the second terminal. Optionally, the functional entity is a device, and the multiple peer functional entities are multiple devices of the same type, such as vehicles or air conditioners produced by different manufacturers. Optionally, the functional entity is a component in the device, and the multiple peer functional entities are multiple components of the same type, such as different doors and windows of the same vehicle.

[0073] In some embodiments, each functional entity in a plurality of peer functional entities corresponds to its own path parameter value. Exemplarily, the left front window, the left rear window, the right front window, and the right rear window correspond to path parameter value 1, path parameter value 2, path parameter value 3, and path parameter value 4, respectively. Optionally, the path parameter value is a parameter value including text. Exemplarily, the path parameter value 1 corresponding to the left front window is "left front". Optionally, the path parameter value is a parameter value including numbers. Exemplarily, the path parameter value 1 corresponding to the left front window is "1". Optionally, the path parameter value is a mixed parameter value including text and numbers. Exemplarily, the path parameter value 1 corresponding to the left front window is "left 1". In the embodiments of the present application, there is no limitation on the form of expression of the path parameter value. The path input parameter value is a subset of the path parameter value. Exemplarily, assuming that the path parameter values ​​include "left front, left rear, right front, right rear", the path input parameter value can be "left front", "left rear", "right front", "right rear", "left front, left rear", "left front, right front", "left rear, right rear", "right front, right rear", "left front, left rear, right front", "left front, left rear, right rear", "left front, right front, right rear", "left front, right front, right rear", "left rear, right front, right rear", "left front, left rear, right front, right rear".

[0074] Step 140: Sending a service call instruction to the second terminal;

[0075] In some embodiments, the first terminal sends a service identifier and a path input parameter value to the second terminal. The path input parameter value is used to instruct the second terminal to execute a service for a functional entity corresponding to the path input parameter value among multiple peer functional entities. For example, if the path input parameter value is "left front," the in-vehicle device is instructed to execute a service for closing the left front window; if the path input parameter value is "left front, right rear," the in-vehicle device is instructed to execute a service for closing both the left front window and the right rear window.

[0076] Step 160: Receive a service call response sent by the second terminal;

[0077] The service call response is used to indicate the execution result of the service call instruction executed by the second terminal.

[0078] In some embodiments, the service call response includes a path output parameter value and an execution result output parameter value. The path output parameter value is the path parameter value corresponding to at least one functional entity among the multiple peer functional entities for which the service is being executed. For example, if the in-vehicle device executes a service for closing the left front window, the path output parameter value is "left front"; if the in-vehicle device executes a service for closing both the left front window and the right rear window, the path output parameter value is "left front, right rear". The execution result output parameter value is used to indicate whether the second terminal successfully executed the service call instruction or failed.

[0079] It is worth noting that, in a possible embodiment, the first terminal includes a service calling instruction, and the above step 120 is an optional step.

[0080] In summary, the method provided in this embodiment generates a service call instruction including a service identifier and a path input parameter value through a first terminal, and calls a service in a second terminal. The service identifier is used to indicate a service for multiple peer functional entities in the second terminal, and each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value. Since each of the multiple peer functional entities corresponds to its own path parameter value, by determining the path input parameter value from the path parameter value and then generating the corresponding service call instruction, multiple services corresponding to multiple peer functional entities can be integrated into a service for multiple peer functional entities, thereby realizing the call of a common service by determining the path input parameter value.

[0081] In some embodiments, the first terminal establishes a communication connection with the second terminal to obtain the service of the second terminal. As shown in FIG3 , before the above step 120, the following steps are also included:

[0082] Step 100: Obtain services of the second terminal;

[0083] The service includes services for multiple peer functional entities.

[0084] In some embodiments, the first terminal obtains all services of the second terminal. In some embodiments, the first terminal obtains part of the services of the second terminal, and the part of the services includes services for multiple peer functional entities. Optionally, the part of the services is a service that the first terminal is authorized to use / call, and the first terminal is a terminal authorized to use the part of the services. Exemplarily, the first terminal is authorized to use the service for closing the car window, but is denied to use the service for closing the door lock, then the part of the services is the service for closing the car window. Optionally, the part of the services is a service that the first terminal supports using / calling. Exemplarily, the first terminal supports using the service for closing the car window, but does not support using the service for closing the door lock, then the part of the services is the service for closing the car window. In some embodiments, the first terminal only obtains services for multiple peer functional entities.

[0085] In some embodiments, the first terminal obtains the service of the second terminal in advance. In some embodiments, the first terminal obtains the service of the second terminal in real time.

[0086] Step 110: parse the services for the multiple peer functional entities and determine the path parameter value corresponding to each of the multiple peer functional entities.

[0087] In some embodiments, the first terminal determines services for multiple peer functional entities from the acquired services. By parsing the services for the multiple peer functional entities, the path parameter values ​​corresponding to each of the multiple peer functional entities are determined. For example, the first terminal obtains a window-closing service for vehicle windows from an in-vehicle device. Assuming that there are four peer functional entities, namely, the left front window, the left rear window, the right front window, and the right rear window, the window-closing service for the vehicle windows is parsed to determine that the path parameter values ​​include "left front, left rear, right front, and right rear."

[0088] In some embodiments, the path parameter value is determined by the path parameter information. As shown in FIG4 , the above step 110 can be replaced by the following sub-steps:

[0089] Step 111: parse services for multiple peer functional entities to obtain path parameter information;

[0090] In some embodiments, services for multiple peer functional entities carry path parameter information. The path parameter information is obtained by parsing the services for multiple peer functional entities. The path parameter information includes description information of the path parameter and / or a parameter structure of the path parameter.

[0091] In some embodiments, the description information of the path parameter is used to describe multiple peer functional entities corresponding to the path parameter. Optionally, the description information of the path parameter is used to describe the attributes of multiple peer functional entities. Exemplarily, the description information of the path parameter for the vehicle window is "vehicle component". Optionally, the description information of the path parameter is used to describe the names of multiple peer functional entities. Exemplarily, the description information of the path parameter for the vehicle window is "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, right rear window of the vehicle". Optionally, the description information of the path parameter is used to describe the functions of multiple peer functional entities.

[0092] In some embodiments, a parameter structure for a path parameter is used to indicate the structure of path parameter values ​​corresponding to multiple peer functional entities. Optionally, the parameter structure for a path parameter is used to indicate the order in which the path parameter values ​​corresponding to the multiple peer functional entities are arranged. For example, the parameter structure for a path parameter for a vehicle window indicates that the path parameter values ​​for the vehicle window are arranged in a front-to-back and left-to-right order.

[0093] Step 112: Based on the path parameter information, determine the path parameter value corresponding to each functional entity in the plurality of peer functional entities.

[0094] In some embodiments, based on the description information of the path parameters, the path parameter values ​​corresponding to each of the multiple peer functional entities are determined. For example, if the description information of the path parameters for vehicle windows is "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, right rear window of the vehicle," then the path parameter values ​​for the vehicle windows are determined to include "left front, left rear, right front, right rear."

[0095] In some embodiments, a path parameter value corresponding to each of the plurality of peer functional entities is determined based on a parameter structure of the path parameter. For example, if the parameter structure of the path parameter for a vehicle window indicates that the path parameter values ​​for the vehicle window are ordered from front to back and from left to right, the path parameter values ​​for the vehicle window are determined to include "front left, rear left, front right, rear right."

[0096] In summary, the method provided in this embodiment uses a first terminal to parse services for multiple peer functional entities and determine the path parameter value corresponding to each of the multiple peer functional entities, thereby enabling the multiple peer functional entities to implement different services using their corresponding path parameter values.

[0097] In some embodiments, the first terminal generates a corresponding service call instruction by interacting with the user. As shown in FIG5 , after the above step 110 and before step 120, the following steps are also included:

[0098] Step 113: Generate an interactive interface for services of multiple peer functional entities based on the path parameter values.

[0099] In some embodiments, based on the number of path parameter values, an interactive interface for services of multiple peer functional entities is generated. For example, assuming the number of path parameter values ​​is four, an interactive interface including four path parameter values ​​is generated. For example, as shown in FIG6 , an interactive interface 20 including a first path parameter value 21, a second path parameter value 22, a third path parameter value 23, and a fourth path parameter value 24 is generated.

[0100] In some embodiments, based on the names of the path parameter values, interactive interfaces for services of multiple peer functional entities are generated. For example, assuming that the names of the path parameter values ​​include "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, and right rear window of the vehicle," an interactive interface based on the names of the path parameter values ​​is generated. For example, as shown in FIG6 , the generated interactive interface 20 includes a first path parameter value 21 corresponding to the name "left front," a second path parameter value 22 corresponding to the name "left rear," a third path parameter value 23 corresponding to the name "right front," and a fourth path parameter value 24 corresponding to the name "right rear."

[0101] In some embodiments, an interactive interface for services of multiple peer functional entities is generated based on attributes of the path parameter value.

[0102] In some embodiments, when the first terminal has an interactive interface for interacting with the user, as shown in FIG7 , the above step 120 may be replaced by the following sub-steps:

[0103] Step 121: In response to a setting operation on at least one of the path parameter values, a service calling instruction is generated.

[0104] In some embodiments, the setting operation for at least one of the path parameter values ​​includes at least one of single-click, double-click, left-right swipe, up-down swipe, long-press, hover, facial recognition, and voice recognition. It is worth noting that the setting operation includes but is not limited to the aforementioned operations. Those skilled in the art will appreciate that any operation capable of implementing the aforementioned functions falls within the scope of protection of the embodiments of this application.

[0105] In some embodiments, when the first terminal has an interactive interface for interacting with the user, the interactive interface includes a selection control for selecting a corresponding path parameter value. The user causes the selection control for the corresponding path parameter value to respond by performing at least one of a single click, a double click, a left-right slide, an up-down slide, a long press, a hover, facial recognition, and voice recognition, thereby causing the first terminal to generate a service call instruction corresponding to the selected path parameter value. For example, as shown in FIG6 , the user selects the first path parameter value 21, thereby causing the first terminal to generate a service call instruction corresponding to the first path parameter value 21.

[0106] In some embodiments, the first terminal determines a path input parameter value in response to a setting operation for at least one of the path parameter values. The path input parameter value is the set path parameter value for at least one of the path parameter values. Optionally, the path input parameter value is a set of at least one path parameter value generated based on a user selection. For example, assuming that the path parameter values ​​include "left front, left back, right front, right back", if the user selects "left front", the path input parameter value is "left front"; if the user selects "left back", the path input parameter value is "left back"; if the user selects "right front", the path input parameter value is "right front"; if the user selects "right back", the path input parameter value is "right back"; if the user selects "left front, left back", the path input parameter value is "left front, left back"; if the user selects "left front, right front", the path input parameter value is "left front, right front"; if the user selects "left front, right back", the path input parameter value is "left front, right back"; if the user selects "left back, right front", the path input parameter value is "left back, right front"; if the user selects If the user selects "left rear, right rear", the path input parameter value is "left rear, right rear"; if the user selects "right front, right rear", the path input parameter value is "right front, right rear"; if the user selects "left front, left rear, right front", the path input parameter value is "left front, left rear, right front"; if the user selects "left front, left rear, right rear", the path input parameter value is "left front, left rear, right rear"; if the user selects "left front, right front, right rear", the path input parameter value is "left front, right front, right rear"; if the user selects "left rear, right front, right rear", the path input parameter value is "left rear, right front, right rear"; if the user selects "left front, left rear, right front, right rear", the path input parameter value is "left front, left rear, right front, right rear".

[0107] In some embodiments, a service call instruction is generated based on a path input parameter value.

[0108] To sum up, the method provided in this embodiment generates an interactive interface for services of multiple peer functional entities based on path parameter values, and generates a service call instruction in response to a setting operation for at least one of the path parameter values, so that the user can determine the service call instruction that needs to be generated through the path parameter values ​​in a targeted manner.

[0109] In some embodiments, as shown in FIG8 , the method further includes the following steps:

[0110] Step 220: Display the response result of the service call instruction.

[0111] In some embodiments, the first terminal displays a response result of the service call instruction through a display interface. The response result is used to indicate the success or failure of executing the service call instruction. For example, as shown in Figure 9, a response result 31 of the service call instruction is displayed on the display interface 30, such as "Execution Successful", indicating that the service call instruction was successfully executed.

[0112] In some embodiments, the response result of the service call instruction is displayed based on a path output parameter value and an execution result output parameter value. The path output parameter value is the path parameter value corresponding to at least one functional entity among multiple peer functional entities where the service is being executed. For example, if the in-vehicle device executes a service for closing the left front window, the path output parameter value is "left front"; if the in-vehicle device executes a service for closing the left front window and the right rear window, the path output parameter value is "left front, right rear". The execution result output parameter value is used to indicate whether the second terminal successfully executed the service call instruction or failed.

[0113] In some embodiments, as shown in FIG10 , the above step 220 further includes the following sub-steps:

[0114] Step 221: Compare the path output parameter value and the path input parameter value to obtain a comparison result;

[0115] In some embodiments, the comparison result indicates whether the path output parameter value and the path input parameter value are consistent or inconsistent. For example, assuming the path output parameter value is "left front, right front" and the path input parameter value is "left front, left back, right front", then the path output parameter value and the path input parameter value are inconsistent. For example, assuming the path output parameter value is "left front, right front" and the path input parameter value is "left front, right front", then the path output parameter value and the path input parameter value are consistent. If the comparison result is consistent, continue to step 222.

[0116] In some embodiments, based on the comparison results, it is determined whether the path output parameter value and the path input parameter value are consistent or inconsistent. Optionally, if the path output parameter value and the path input parameter value are consistent, step 222 is continued. Optionally, if the path output parameter value and the path input parameter value are inconsistent, it is confirmed that the second terminal has not responded to the service call instruction sent by the first terminal. In some embodiments, if the path output parameter value and the path input parameter value are inconsistent, the process continues to wait for the path output parameter value and the path input parameter value to be consistent. For example, assume that after sending service call instruction 1, the first terminal continuously sends service call instruction 2. Service call instruction 1 carries path input parameter value 1 of "left front" and service call instruction 2 carries path input parameter value 2 of "right rear". If the path output parameter value 1 received by the first terminal is "right rear", it means that the second terminal has responded to the service call instruction 2 sent by the first terminal. The first terminal then continues to wait for the received path output parameter value 2 to be "left front", indicating that the second terminal has responded to the service call instruction 1 sent by the first terminal.

[0117] In some embodiments, when the path output parameter value and the path input parameter value are inconsistent, the path output parameter value and the path input parameter value are waited for to be consistent based on the waiting time. In some embodiments, when the waiting time of the first terminal is less than or equal to the waiting threshold, it is determined that the execution of the service call instruction is successful. Exemplarily, if the first terminal receives the path output parameter value corresponding to the path input parameter value within the waiting threshold, it means that the second terminal responds to the service call instruction sent by the first terminal. In some embodiments, when the waiting time of the first terminal is greater than the waiting threshold, it is determined that the execution of the service call instruction fails. Exemplarily, assuming that after the first terminal sends the service call instruction, the parameters change due to an error in the second terminal or the network, the first terminal cannot receive the path output parameter value corresponding to the path input parameter value within the waiting threshold, which means that the second terminal does not respond to the service call instruction sent by the first terminal.

[0118] Step 222: If the comparison result is consistent, the response result of the service call instruction is displayed based on the parameter value of the execution result.

[0119] In some embodiments, when the comparison results are consistent, it is determined that the execution of the service call instruction is successful.

[0120] In summary, the method provided in this embodiment, by displaying the response result of the service call instruction, indicates to the user whether the service call instruction is executed successfully or failed, which helps the user further understand the performance of the second terminal response service, thereby helping to improve the performance of the second terminal response service.

[0121] It is worth noting that in the embodiment of the present application, step 100, step 110, step 111, step 112, step 113, step 220, step 221, and step 222 are optional. In different embodiments, one or more of these steps may be omitted or replaced.

[0122] Step 100 can be implemented as an independent embodiment; step 110 can be implemented as an independent embodiment; step 111 and step 112 can be implemented as independent embodiments; step 113 can be implemented as an independent embodiment; step 220 can be implemented as an independent embodiment; step 221 and step 222 can be implemented as independent embodiments.

[0123] Step 100 and step 110 can be implemented as independent embodiments; step 100, step 111 and step 112 can be implemented as independent embodiments; step 100 and step 113 can be implemented as independent embodiments; step 100 and step 220 can be implemented as independent embodiments; step 100, step 221 and step 222 can be implemented as independent embodiments; step 100, step 110, step 111 and step 112 can be implemented as independent embodiments; step 100, step 110 and step 113 can be implemented as independent embodiments; step 100, step 110 and step 220 can be implemented as independent embodiments; step 100, step 110, step 111 and step 112 can be implemented as independent embodiments; step 100, step 110 and step 113 can be implemented as independent embodiments; step 100, step 110 and step 220 can be implemented as independent embodiments; step 100, step 110, step Step 221 and step 222 can be implemented as independent embodiments; step 100, step 111, step 112 and step 113 can be implemented as independent embodiments; step 100, step 111, step 112 and step 220 can be implemented as independent embodiments; step 100, step 111, step 112, step 221 and step 222 can be implemented as independent embodiments; step 100, step 113 and step 220 can be implemented as independent embodiments; step 100, step 113, step 221 and step 222 can be implemented as independent embodiments; step 100, step 220, step 221 and step 222 can be implemented as independent embodiments; step 100, step 110, step 111, step 112 and step 113 can be implemented as independent embodiments; step 100, step 110, step 111, step 112 and step 220 can be implemented as independent embodiments; step 100, step 110, step 111, step 112, step 221 and step 222 can be implemented as independent embodiments; step 100, step 111, step 112, step 113 and step 220 can be implemented as independent embodiments; step 100, step 111, step 112, step 113, step 221 and step 222 can be implemented as independent embodiments; step 100, step 113, step 220, step Step 221 and step 222 can be implemented as independent embodiments; step 100, step 110, step 111, step 112, step 113 and step 220 can be implemented as independent embodiments; step 100, step 110, step 111, step 112, step 113, step 221 and step 222 can be implemented as independent embodiments; step 100, step 111, step 112, step 113, step 220, step 221 and step 222 can be implemented as independent embodiments; step 100, step 110, step 111, step 112, step 113, step 220, step 221 and step 222 can be implemented as independent embodiments.

[0124] Step 110, step 111 and step 112 can be implemented as independent embodiments; step 110 and step 113 can be implemented as independent embodiments; step 110 and step 220 can be implemented as independent embodiments; step 110, step 221 and step 222 can be implemented as independent embodiments; step 111, step 112 and step 113 can be implemented as independent embodiments; step 111, step 112 and step 220 can be implemented as independent embodiments; step 111, step 111 2. Step 221 and step 222 can be implemented as independent embodiments; step 113 and step 220 can be implemented as independent embodiments; step 113, step 221 and step 222 can be implemented as independent embodiments; step 220, step 221 and step 222 can be implemented as independent embodiments; step 110, step 111, step 112 and step 113 can be implemented as independent embodiments; step 110, step 111, step 112 and step 220 can be implemented as independent embodiments to implement; Step 110, Step 111, Step 112, Step 221 and Step 222 can be implemented as independent embodiments; Step 111, Step 112, Step 113 and Step 220 can be implemented as independent embodiments; Step 111, Step 112, Step 113, Step 221 and Step 222 can be implemented as independent embodiments; Step 113, Step 220, Step 221 and Step 222 can be implemented as independent embodiments; Step 110, Step 111, Step 112, Step 113, Step 221 and Step 222 can be implemented as independent embodiments; 2. Step 113 and step 220 can be implemented as independent embodiments; step 110, step 111, step 112, step 113, step 221 and step 222 can be implemented as independent embodiments; step 111, step 112, step 113, step 220, step 221 and step 222 can be implemented as independent embodiments; step 110, step 111, step 112, step 113, step 220, step 221 and step 222 can be implemented as independent embodiments.

[0125] FIG11 shows a flow chart of a method for invoking a service provided by an exemplary embodiment of the present application. Exemplarily, the method is executed by the second terminal 12 shown in FIG1 , and the method includes:

[0126] Step 320: Receive a service call instruction sent by the first terminal;

[0127] The service call instruction is used to instruct the second terminal to execute the corresponding service according to the service call instruction. Exemplarily, the service call instruction is used to instruct the vehicle-mounted device to execute the service of closing the left front window. In some embodiments, the service call instruction includes a service identifier and a path input parameter value.

[0128] The service identifier is used to indicate the service for multiple peer functional entities in the second terminal. In some embodiments, the second terminal includes at least one service, and at least one service includes the service for multiple peer functional entities. Exemplarily, the left front window, the left rear window, the right front window, and the right rear window belong to peer functional entities, and the service for multiple peer functional entities includes the window closing service. Optionally, the service identifier is an identifier including numbers. Exemplarily, the service identifier "1000" corresponds to the window closing service. Optionally, the service identifier is an identifier including letters. Exemplarily, the service identifier "A" corresponds to the window closing service. Optionally, the service identifier is a mixed identifier including numbers and letters. Exemplarily, the service identifier "A1" corresponds to the window closing service. The embodiment of the present application does not limit the form of expression of the service identifier.

[0129] In some embodiments, the multiple peer functional entities refer to functional entities of the same type controlled by the second terminal. Optionally, the functional entity is a device, and the multiple peer functional entities are multiple devices of the same type, such as vehicles or air conditioners produced by different manufacturers. Optionally, the functional entity is a component in the device, and the multiple peer functional entities are multiple components of the same type, such as different doors and windows of the same vehicle.

[0130] In some embodiments, each functional entity in a plurality of peer functional entities corresponds to its own path parameter value. Exemplarily, the left front window, the left rear window, the right front window, and the right rear window correspond to path parameter value 1, path parameter value 2, path parameter value 3, and path parameter value 4, respectively. Optionally, the path parameter value is a parameter value including text. Exemplarily, the path parameter value 1 corresponding to the left front window is "left front". Optionally, the path parameter value is a parameter value including numbers. Exemplarily, the path parameter value 1 corresponding to the left front window is "1". Optionally, the path parameter value is a mixed parameter value including text and numbers. Exemplarily, the path parameter value 1 corresponding to the left front window is "left 1". In the embodiments of the present application, there is no limitation on the form of expression of the path parameter value. The path input parameter value is a subset of the path parameter value. Exemplarily, assuming that the path parameter values ​​include "left front, left rear, right front, right rear", the path input parameter value can be "left front", "left rear", "right front", "right rear", "left front, left rear", "left front, right front", "left rear, right rear", "right front, right rear", "left front, left rear, right front", "left front, left rear, right rear", "left front, right front, right rear", "left front, right front, right rear", "left rear, right front, right rear", "left front, left rear, right front, right rear".

[0131] Step 340: Send a service call response to the first terminal.

[0132] The service call response is used to indicate the execution result of the service call instruction executed by the second terminal. Optionally, the service call response includes a path output parameter value and an execution result output parameter value.

[0133] The path out parameter value is the path parameter value corresponding to at least one functional entity among the multiple peer functional entities that is performing the service. For example, if the vehicle-mounted device is performing a service for closing the left front window, the path out parameter value is "Left Front"; if the vehicle-mounted device is performing a service for closing both the left front window and the right rear window, the path out parameter value is "Left Front, Right Rear".

[0134] The execution result parameter value is used to indicate whether the second terminal executes the service call instruction successfully or fails.

[0135] In summary, the method provided in this embodiment calls a service in a second terminal by receiving a service call instruction including a service identifier and a path input parameter value generated by a first terminal. The service identifier is used to indicate a service in the second terminal for multiple peer functional entities, and each of the multiple peer functional entities corresponds to its own path parameter value, which is a subset of the path parameter value. Since each of the multiple peer functional entities corresponds to its own path parameter value, by determining the path input parameter value from the path parameter value and then generating the corresponding service call instruction, multiple services corresponding to multiple peer functional entities can be integrated into a service for multiple peer functional entities, thereby enabling the call of a common service by determining the path input parameter value.

[0136] In some embodiments, as shown in FIG12 , the above step 320 may further include the following steps:

[0137] Step 310: Initialize services for multiple peer functional entities and determine the path parameter value corresponding to each of the multiple peer functional entities.

[0138] In some embodiments, the second terminal initializes services for multiple peer functional entities and determines path parameter values ​​corresponding to each of the multiple peer functional entities. For example, the in-vehicle device includes a window-closing service for vehicle windows. Assuming there are four peer functional entities, namely, the left front window, the left rear window, the right front window, and the right rear window, the window-closing service is initialized to determine that the path parameter values ​​include "left front, left rear, right front, and right rear."

[0139] In some embodiments, the path parameter value is determined by path parameter information. In some embodiments, services for multiple peer functional entities are parsed to obtain the path parameter information. In some embodiments, the services for multiple peer functional entities carry the path parameter information. The path parameter information is determined by initializing the services for the multiple peer functional entities. The path parameter information includes description information of the path parameter and / or a parameter structure of the path parameter.

[0140] In some embodiments, the description information of the path parameter is used to describe multiple peer functional entities corresponding to the path parameter. Optionally, the description information of the path parameter is used to describe the attributes of multiple peer functional entities. Exemplarily, the description information of the path parameter for the vehicle window is "vehicle component". Optionally, the description information of the path parameter is used to describe the names of multiple peer functional entities. Exemplarily, the description information of the path parameter for the vehicle window is "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, right rear window of the vehicle". Optionally, the description information of the path parameter is used to describe the functions of multiple peer functional entities.

[0141] In some embodiments, a parameter structure for a path parameter is used to indicate the structure of path parameter values ​​corresponding to multiple peer functional entities. Optionally, the parameter structure for a path parameter is used to indicate the order in which the path parameter values ​​corresponding to the multiple peer functional entities are arranged. For example, the parameter structure for a path parameter for a vehicle window indicates that the path parameter values ​​for the vehicle window are arranged in a front-to-back and left-to-right order.

[0142] In some embodiments, based on the path parameter information, a path parameter value corresponding to each functional entity in a plurality of peer functional entities is determined.

[0143] In some embodiments, based on the description information of the path parameters, the path parameter values ​​corresponding to each of the multiple peer functional entities are determined. For example, if the description information of the path parameters for vehicle windows is "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, right rear window of the vehicle," then the path parameter values ​​for the vehicle windows are determined to include "left front, left rear, right front, right rear."

[0144] In some embodiments, a path parameter value corresponding to each of the plurality of peer functional entities is determined based on a parameter structure of the path parameter. For example, if the parameter structure of the path parameter for a vehicle window indicates that the path parameter values ​​for the vehicle window are ordered from front to back and from left to right, the path parameter values ​​for the vehicle window are determined to include "front left, rear left, front right, rear right."

[0145] In summary, the method provided in this embodiment initializes services for multiple peer functional entities and determines the path parameter value corresponding to each of the multiple peer functional entities, so that the multiple peer functional entities can implement different services through their corresponding path parameter values.

[0146] In some embodiments, as shown in FIG13 , the above step 320 may further include the following steps:

[0147] Step 330: Execute the service call instruction.

[0148] In some embodiments, a service call instruction is executed based on a path input parameter value.

[0149] The path input parameter value is at least one path parameter value set for the path parameter value. Optionally, the path input parameter value is a set of at least one path parameter value generated based on the user's selection. Exemplarily, assuming that the path parameter values ​​include "left front, left back, right front, right back", if the user selects "left front", the path input parameter value is "left front"; if the user selects "left back", the path input parameter value is "left back"; if the user selects "right front", the path input parameter value is "right front"; if the user selects "right back", the path input parameter value is "right back"; if the user selects "left front, left back", the path input parameter value is "left front, left back"; if the user selects "left front, right front", the path input parameter value is "left front, right front"; if the user selects "left front, right back", the path input parameter value is "left front, right back"; if the user selects "left back, right front", the path input parameter value is "left back, right front"; if the user selects If the user selects "left rear, right rear", the path input parameter value is "left rear, right rear"; if the user selects "right front, right rear", the path input parameter value is "right front, right rear"; if the user selects "left front, left rear, right front", the path input parameter value is "left front, left rear, right front"; if the user selects "left front, left rear, right rear", the path input parameter value is "left front, left rear, right rear"; if the user selects "left front, right front, right rear", the path input parameter value is "left front, right front, right rear"; if the user selects "left rear, right front, right rear", the path input parameter value is "left rear, right front, right rear"; if the user selects "left front, left rear, right front, right rear", the path input parameter value is "left front, left rear, right front, right rear".

[0150] In some embodiments, the second terminal parses the service call instruction to determine the path input parameter value carried in the service call instruction. For example, assuming that the path input parameter value carried in the service call instruction includes "left front, left rear", the service call instruction is parsed to determine that the path input parameter value includes "left front, left rear".

[0151] In summary, the method provided in this embodiment enables the second terminal to call a service according to the user's targeted needs by executing the service call instruction based on the path parameter value.

[0152] It is worth noting that in the embodiment of the present application, step 310 and step 330 are optional, and in different embodiments, one or more of these steps may be omitted or replaced.

[0153] Step 310 can be implemented as an independent embodiment; step 330 can be implemented as an independent embodiment; step 310 and step 330 can be implemented as independent embodiments.

[0154] FIG14 shows a flow chart of a method for invoking a service provided by an exemplary embodiment of the present application. Exemplarily, the method is jointly executed by the first terminal 11 and the second terminal 12 shown in FIG1 , and the method includes:

[0155] Step 41: The second terminal generates a service;

[0156] In some embodiments, the second terminal generates a service corresponding to the at least one functional entity based on the at least one functional entity, wherein the service includes services for multiple peer functional entities.

[0157] Step 42: The second terminal initializes services for multiple peer functional entities and determines path parameter values;

[0158] For a specific implementation, please refer to the above step 310 .

[0159] Step 43: The first terminal establishes a connection with the second terminal;

[0160] The first terminal and the second terminal are connected via a network or a USB.

[0161] Step 44: The first terminal sends a query request;

[0162] The query request is used to request a query for services for multiple peer functional entities in the second terminal. Optionally, the query request is a query request for all services in the second terminal. Optionally, the query request is a query request for some services in the second terminal, where the some services include services for multiple peer functional entities.

[0163] Optionally, the partial service is a service that the first terminal is authorized to use / call, and the first terminal is a terminal authorized to use the partial service. For example, the first terminal is authorized to use the service for closing the window but is denied the service for closing the door lock, and the partial service is the service for closing the window.

[0164] Optionally, the partial service is a service supported / called by the first terminal. For example, the first terminal supports the service for closing car windows but does not support the service for closing door locks, and the partial service is the service for closing car windows.

[0165] Step 45: The second terminal receives the query request;

[0166] Optionally, the second terminal receives a query request for all services in the second terminal.

[0167] Optionally, the second terminal receives a query request for some services in the second terminal, where the some services include services for multiple peer functional entities.

[0168] Step 46: The second terminal sends a service;

[0169] Optionally, when the query request is a query request for all services in the second terminal, the second terminal sends all services to the first terminal.

[0170] Optionally, in a case where the query request is a query request for a portion of services in the second terminal, the second terminal sends the portion of services to the first terminal, where the portion of services includes services for a plurality of peer functional entities.

[0171] Step 47: The first terminal receives the service;

[0172] For a specific implementation, please refer to the above step 100.

[0173] Step 48: The first terminal parses services for multiple peer functional entities and determines path parameter values;

[0174] For a specific implementation, please refer to the above step 110 .

[0175] Step 49: The first terminal generates an interactive interface based on the path parameter value;

[0176] For a specific implementation, see the above step 113 .

[0177] Step 50: The first terminal receives the path input parameter value set by the user;

[0178] In some embodiments, when there is an interactive interface on the first terminal for interacting with the user, the interactive interface includes a selection control for selecting a corresponding path parameter value. The user makes the selection control of the corresponding path parameter value respond by performing at least one of single-clicking, double-clicking, sliding left and right, sliding up and down, long pressing, hovering, facial recognition, and voice recognition, thereby causing the first terminal to generate a service call instruction corresponding to the selected path parameter value.

[0179] Step 51: The first terminal generates a service call instruction in response to the setting operation;

[0180] For a specific implementation, please refer to the above step 120.

[0181] Step 52: The first terminal sends a service call instruction;

[0182] For a specific implementation, please refer to the above step 140.

[0183] Step 53: The second terminal receives the service call instruction;

[0184] For a specific implementation, please refer to the above step 320.

[0185] Step 54: The second terminal executes the service call instruction;

[0186] For a specific implementation, please refer to the above step 330.

[0187] Step 55: The second terminal sends a service call response;

[0188] For a specific implementation, please refer to the above step 340.

[0189] Step 56: The first terminal receives the service call response;

[0190] For a specific implementation, please refer to the above step 160 .

[0191] Step 57: The first terminal displays a response result of the service call instruction.

[0192] For a specific implementation, please refer to the above step 220.

[0193] FIG15 shows a schematic diagram of a service invocation device provided by some exemplary embodiments of the present application, the device comprising:

[0194] Generating module 1510 is configured to generate a service call instruction. The service call instruction is configured to instruct the service-called device to execute the corresponding service according to the service call instruction. For example, the service call instruction is configured to instruct the vehicle-mounted device to execute a service to close the left front window. In some embodiments, the service call instruction includes a service identifier and a path input parameter.

[0195] The service identifier is used to indicate a service for multiple peer functional entities in a service-called device. In some embodiments, the service-called device includes at least one service, and at least one service includes the service for multiple peer functional entities. Exemplarily, the left front window, the left rear window, the right front window, and the right rear window belong to peer functional entities, and the service for multiple peer functional entities includes a window closing service. Optionally, the service identifier is an identifier including numbers. Exemplarily, the service identifier "1000" corresponds to a window closing service. Optionally, the service identifier is an identifier including letters. Exemplarily, the service identifier "A" corresponds to a window closing service. Optionally, the service identifier is a mixed identifier including numbers and letters. Exemplarily, the service identifier "A1" corresponds to a window closing service. The embodiment of the present application does not limit the form of expression of the service identifier.

[0196] In some embodiments, the multiple peer functional entities refer to functional entities of the same type controlled by the service invoked device. Optionally, the functional entity is a device, and the multiple peer functional entities are multiple devices of the same type, such as vehicles or air conditioners produced by different manufacturers. Optionally, the functional entity is a component of the device, and the multiple peer functional entities are multiple components of the same type, such as different doors and windows of the same vehicle.

[0197] In some embodiments, each functional entity in a plurality of peer functional entities corresponds to its own path parameter value. Exemplarily, the left front window, the left rear window, the right front window, and the right rear window correspond to path parameter value 1, path parameter value 2, path parameter value 3, and path parameter value 4, respectively. Optionally, the path parameter value is a parameter value including text. Exemplarily, the path parameter value 1 corresponding to the left front window is "left front". Optionally, the path parameter value is a parameter value including numbers. Exemplarily, the path parameter value 1 corresponding to the left front window is "1". Optionally, the path parameter value is a mixed parameter value including text and numbers. Exemplarily, the path parameter value 1 corresponding to the left front window is "left 1". In the embodiments of the present application, there is no limitation on the form of expression of the path parameter value. The path input parameter value is a subset of the path parameter value. Exemplarily, assuming that the path parameter values ​​include "left front, left rear, right front, right rear", the path input parameter value can be "left front", "left rear", "right front", "right rear", "left front, left rear", "left front, right front", "left rear, right rear", "right front, right rear", "left front, left rear, right front", "left front, left rear, right rear", "left front, right front, right rear", "left front, right front, right rear", "left rear, right front, right rear", "left front, left rear, right front, right rear".

[0198] The sending module 1520 is configured to send a service call instruction to the service-called device. In some embodiments, the service-calling device sends a service identifier and a path input parameter value to the service-called device. The path input parameter value is used to instruct the service-called device to execute a service for a functional entity corresponding to the path input parameter value among multiple peer functional entities. For example, if the path input parameter value is "left front", the vehicle-mounted device is instructed to execute a service for closing the left front window; if the path input parameter value is "left front, right rear", the vehicle-mounted device is instructed to execute a service for closing the left front window and the right rear window.

[0199] The receiving module 1530 is configured to receive a service call response sent by the service called device. The service call response is used to indicate the execution result of the service call instruction executed by the service called device. Optionally, the service call response includes a path output parameter value and an execution result output parameter value.

[0200] The path out parameter value is the path parameter value corresponding to at least one functional entity among the multiple peer functional entities that is performing the service. For example, if the vehicle-mounted device is performing a service for closing the left front window, the path out parameter value is "Left Front"; if the vehicle-mounted device is performing a service for closing both the left front window and the right rear window, the path out parameter value is "Left Front, Right Rear".

[0201] The execution result parameter value is used to indicate whether the service-called device executes the service call instruction successfully or unsuccessfully.

[0202] In some embodiments, the service calling device establishes a communication connection with the service called device to obtain the service of the service called device.

[0203] The receiving module 1530 is further configured to obtain the service of the service-called device, which includes services for multiple peer functional entities.

[0204] In some embodiments, the service calling device obtains all services of the service called device.

[0205] In some embodiments, the service calling device obtains part of the services of the service called device, and the part of the services includes services for multiple peer functional entities. Optionally, the part of the services is a service that the service calling device is authorized to use / call, and the service calling device is a terminal authorized to use the part of the services. Exemplarily, the service calling device is authorized to use the service for closing the windows, but is denied to use the service for closing the door locks, then the part of the services is the service for closing the windows. Optionally, the part of the services is a service that the service calling device supports to use / call. Exemplarily, the service calling device supports to use the service for closing the windows, but does not support to use the service for closing the door locks, then the part of the services is the service for closing the windows.

[0206] In some embodiments, the service calling device only obtains services for multiple peer functional entities.

[0207] In some embodiments, the service calling device obtains the service of the service called device in advance. In some embodiments, the service calling device obtains the service of the service called device in real time.

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

[0209] The parsing module 1540 is configured to parse services for multiple peer functional entities and determine a path parameter value corresponding to each of the multiple peer functional entities.

[0210] In some embodiments, the service invoking device determines services for multiple peer functional entities from the acquired services. By parsing the services for the multiple peer functional entities, the path parameter values ​​corresponding to each of the multiple peer functional entities are determined. For example, the service invoking device obtains a window-closing service for vehicle windows from an in-vehicle device. Assuming that there are four peer functional entities, namely, the left front window, the left rear window, the right front window, and the right rear window, the window-closing service for the vehicle windows is parsed to determine that the path parameter values ​​include "left front, left rear, right front, and right rear."

[0211] In some embodiments, the path parameter value is determined by path parameter information.

[0212] Parsing module 1540 is further configured to parse services for multiple peer functional entities to obtain path parameter information. In some embodiments, services for multiple peer functional entities carry path parameter information. Path parameter information is obtained by parsing services for multiple peer functional entities. The path parameter information includes path parameter description information and / or a path parameter parameter structure.

[0213] In some embodiments, the description information of the path parameter is used to describe multiple peer functional entities corresponding to the path parameter. Optionally, the description information of the path parameter is used to describe the attributes of multiple peer functional entities. Exemplarily, the description information of the path parameter for the vehicle window is "vehicle component". Optionally, the description information of the path parameter is used to describe the names of multiple peer functional entities. Exemplarily, the description information of the path parameter for the vehicle window is "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, right rear window of the vehicle". Optionally, the description information of the path parameter is used to describe the functions of multiple peer functional entities.

[0214] In some embodiments, a parameter structure for a path parameter is used to indicate the structure of path parameter values ​​corresponding to multiple peer functional entities. Optionally, the parameter structure for a path parameter is used to indicate the order in which the path parameter values ​​corresponding to the multiple peer functional entities are arranged. For example, the parameter structure for a path parameter for a vehicle window indicates that the path parameter values ​​for the vehicle window are arranged in a front-to-back and left-to-right order.

[0215] The parsing module 1540 is further configured to determine a path parameter value corresponding to each functional entity in the plurality of peer functional entities based on the path parameter information.

[0216] In some embodiments, based on the description information of the path parameters, the path parameter values ​​corresponding to each of the multiple peer functional entities are determined. For example, if the description information of the path parameters for vehicle windows is "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, right rear window of the vehicle," then the path parameter values ​​for the vehicle windows are determined to include "left front, left rear, right front, right rear."

[0217] In some embodiments, a path parameter value corresponding to each of the plurality of peer functional entities is determined based on a parameter structure of the path parameter. For example, if the parameter structure of the path parameter for a vehicle window indicates that the path parameter values ​​for the vehicle window are ordered from front to back and from left to right, the path parameter values ​​for the vehicle window are determined to include "front left, rear left, front right, rear right."

[0218] In some embodiments, the service calling device generates a corresponding service calling instruction by interacting with the user.

[0219] The generating module 1510 is further configured to generate an interactive interface for services of multiple peer functional entities based on the path parameter values.

[0220] In some embodiments, based on the number of path parameter values, an interactive interface for services of multiple peer functional entities is generated. For example, assuming the number of path parameter values ​​is four, an interactive interface including four path parameter values ​​is generated. For example, as shown in FIG6 , an interactive interface 20 including a first path parameter value 21, a second path parameter value 22, a third path parameter value 23, and a fourth path parameter value 24 is generated.

[0221] In some embodiments, based on the names of the path parameter values, interactive interfaces for services of multiple peer functional entities are generated. For example, assuming that the names of the path parameter values ​​include "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, and right rear window of the vehicle," an interactive interface based on the names of the path parameter values ​​is generated. For example, as shown in FIG6 , the generated interactive interface 20 includes a first path parameter value 21 corresponding to the name "left front," a second path parameter value 22 corresponding to the name "left rear," a third path parameter value 23 corresponding to the name "right front," and a fourth path parameter value 24 corresponding to the name "right rear."

[0222] In some embodiments, an interactive interface for services of multiple peer functional entities is generated based on attributes of the path parameter value.

[0223] In some embodiments, when the service calling device has an interactive interface for interacting with the user,

[0224] The generating module 1510 is further configured to generate a service calling instruction in response to a setting operation on at least one of the path parameter values.

[0225] In some embodiments, the setting operation for at least one of the path parameter values ​​includes at least one of single-click, double-click, left-right swipe, up-down swipe, long-press, hover, facial recognition, and voice recognition. It is worth noting that the setting operation includes but is not limited to the aforementioned operations. Those skilled in the art will appreciate that any operation capable of implementing the aforementioned functions falls within the scope of protection of the embodiments of this application.

[0226] In some embodiments, when the service invocation device has an interactive interface for interacting with the user, the interactive interface includes a selection control for selecting a corresponding path parameter value. The user causes the selection control for the corresponding path parameter value to respond by performing at least one of a single click, a double click, a left-right slide, an up-down slide, a long press, a hover, facial recognition, and voice recognition, thereby causing the service invocation device to generate a service invocation instruction corresponding to the selected path parameter value. For example, as shown in FIG6 , the user selects the first path parameter value 21, thereby causing the service invocation device to generate a service invocation instruction corresponding to the first path parameter value 21.

[0227] In some embodiments, the service calling apparatus determines a path input parameter value in response to a setting operation for at least one of the path parameter values. The path input parameter value is the set path parameter value for at least one of the path parameter values. Optionally, the path input parameter value is a set of at least one path parameter value generated based on a user selection. For example, assuming that the path parameter values ​​include "left front, left back, right front, right back", if the user selects "left front", the path input parameter value is "left front"; if the user selects "left back", the path input parameter value is "left back"; if the user selects "right front", the path input parameter value is "right front"; if the user selects "right back", the path input parameter value is "right back"; if the user selects "left front, left back", the path input parameter value is "left front, left back"; if the user selects "left front, right front", the path input parameter value is "left front, right front"; if the user selects "left front, right back", the path input parameter value is "left front, right back"; if the user selects "left back, right front", the path input parameter value is "left back, right front"; if the user selects If the user selects "left rear, right rear", the path input parameter value is "left rear, right rear"; if the user selects "right front, right rear", the path input parameter value is "right front, right rear"; if the user selects "left front, left rear, right front", the path input parameter value is "left front, left rear, right front"; if the user selects "left front, left rear, right rear", the path input parameter value is "left front, left rear, right rear"; if the user selects "left front, right front, right rear", the path input parameter value is "left front, right front, right rear"; if the user selects "left rear, right front, right rear", the path input parameter value is "left rear, right front, right rear"; if the user selects "left front, left rear, right front, right rear", the path input parameter value is "left front, left rear, right front, right rear".

[0228] In some embodiments, a service call instruction is generated based on a path input parameter value.

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

[0230] Display module 1550 is configured to display the response result of the service call instruction. In some embodiments, the service call device displays the response result of the service call instruction via a display interface. The response result indicates the success or failure of executing the service call instruction. For example, as shown in FIG9 , a response result 31 of the service call instruction is displayed on display interface 30, such as "Executed Successfully," indicating that the service call instruction was successfully executed.

[0231] In some embodiments, the response result of the service call instruction is displayed based on a path output parameter value and an execution result output parameter value. The path output parameter value is the path parameter value corresponding to at least one functional entity among multiple peer functional entities where the service is executed. For example, if the vehicle-mounted device executes a service for closing the left front window, the path output parameter value is "left front"; if the vehicle-mounted device executes a service for closing the left front window and the right rear window, the path output parameter value is "left front, right rear". The execution result output parameter value is used to indicate whether the service-invoking device successfully or failed to execute the service call instruction.

[0232] Display module 1550 is further configured to compare the path output parameter value with the path input parameter value to obtain a comparison result. In some embodiments, the comparison result is used to indicate whether the path output parameter value and the path input parameter value are consistent or inconsistent. For example, assuming that the path output parameter value is "left front, right front" and the path input parameter value is "left front, left back, right front", then the path output parameter value is inconsistent with the path input parameter value. For example, assuming that the path output parameter value is "left front, right front" and the path input parameter value is "left front, right front", then the path output parameter value is consistent with the path input parameter value. If the comparison result is consistent, step 222 is continued.

[0233] In some embodiments, based on the comparison results, it is determined whether the path output parameter value and the path input parameter value are consistent or inconsistent. Optionally, if the path output parameter value and the path input parameter value are consistent, the process proceeds to step 222. Optionally, if the path output parameter value and the path input parameter value are inconsistent, it is confirmed that the service-invoked device has not responded to the service invocation instruction sent by the service-invoking device. In some embodiments, if the path output parameter value and the path input parameter value are inconsistent, the process continues to wait for the path output parameter value and the path input parameter value to be consistent. For example, assume that the service-invoking device sends service invocation instruction 1 and then subsequently sends service invocation instruction 2. Service invocation instruction 1 carries path input parameter value 1 of "left front" and service invocation instruction 2 carries path input parameter value 2 of "right rear". If the path output parameter value 1 received by the service-invoking device is "right rear", it indicates that the service-invoked device has responded to the service invocation instruction 2 sent by the service-invoking device. The service-invoking device then continues to wait for the received path output parameter value 2 to be "left front", indicating that the service-invoked device has responded to the service invocation instruction 1 sent by the service-invoking device.

[0234] In some embodiments, when the path output parameter value and the path input parameter value are inconsistent, the path output parameter value and the path input parameter value are waited for to be consistent based on the waiting time.

[0235] In some embodiments, if the waiting time of the service calling device is less than or equal to the waiting threshold, the execution of the service calling instruction is determined to be successful. Exemplarily, if the service calling device receives a path output parameter value corresponding to the path input parameter value within the waiting threshold, it indicates that the service called device has responded to the service calling instruction sent by the service calling device.

[0236] In some embodiments, if the waiting time of the service calling device exceeds a waiting threshold, it is determined that the execution of the service calling instruction has failed. For example, if, after the service calling device sends the service calling instruction, a parameter changes due to an error in the service called device or a network error, the service calling device is unable to receive a path output parameter value corresponding to the path input parameter value within the waiting threshold, indicating that the service called device has not responded to the service calling instruction sent by the service calling device.

[0237] The display module 1550 is further configured to display the response result of the service call instruction based on the parameter value of the execution result when the comparison result is consistent.

[0238] In some embodiments, when the comparison results are consistent, it is determined that the execution of the service call instruction is successful.

[0239] In some embodiments, the execution result reference value determined based on the comparison result is compared with the execution result output parameter value.

[0240] It should be noted that the device provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0241] Regarding the device in this embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method and will not be elaborated here.

[0242] In some embodiments, the above-mentioned generation module 1510, analysis module 1540, and display module 1550 are optional. In some embodiments, the generation module 1510 can be implemented as an embodiment alone. In some embodiments, the analysis module 1540 can be implemented as an embodiment alone. In some embodiments, the display module 1550 can be implemented as an embodiment alone. In some embodiments, the generation module 1510 and the analysis module 1540 can be implemented as an embodiment alone. In some embodiments, the generation module 1510 and the display module 1550 can be implemented as an embodiment alone. In some embodiments, the analysis module 1540 and the display module 1550 can be implemented as an embodiment alone. In some embodiments, the generation module 1510, the analysis module 1540, and the display module 1550 can be implemented as an embodiment alone.

[0243] In some embodiments, the generation module 1510 and the sending module 1520 may be combined into a single module, such as a generation and sending module. In some embodiments, the generation module 1510 and the receiving module 1530 may be combined into a single module, such as a generation and receiving module. In some embodiments, the generation module 1510 and the parsing module 1540 may be combined into a single module, such as a generation and parsing module. In some embodiments, the generation module 1510 and the display module 1550 may be combined into a single module, such as a generation and display module. In some embodiments, the sending module 1520 and the receiving module 1530 may be combined into a single module, such as a transceiver module. In some embodiments, the sending module 1520 and the parsing module 1540 may be combined into a single module, such as a sending and parsing module. In some embodiments, the sending module 1520 and the display module 1550 may be combined into a single module, such as a sending and display module. In some embodiments, the receiving module 1530 and the parsing module 1540 may be combined into a single module, such as a receiving and parsing module. In some embodiments, the receiving module 1530 and the display module 1550 can be combined into a single module, such as a receiving and display module. In some embodiments, the parsing module 1540 and the display module 1550 can be combined into a single module, such as a parsing and display module.

[0244] In some embodiments, the generation module 1510, the sending module 1520, and the receiving module 1530 can be combined into a single module, such as a generation and transceiver module. In some embodiments, the generation module 1510, the sending module 1520, and the parsing module 1540 can be combined into a single module, such as a generation, sending, and parsing module. In some embodiments, the generation module 1510, the sending module 1520, and the display module 1550 can be combined into a single module, such as a generation, sending, and display module. In some embodiments, the generation module 1510, the receiving module 1530, and the parsing module 1540 can be combined into a single module, such as a generation, receiving, and parsing module. In some embodiments, the generation module 1510, the receiving module 1530, and the display module 1550 can be combined into a single module, such as a generation, receiving, and display module. In some embodiments, the generation module 1510, the parsing module 1540, and the display module 1550 can be combined into a single module, such as a generation, parsing, and display module. In some embodiments, the sending module 1520, the receiving module 1530, and the parsing module 1540 can be combined into a single module, such as a receiving and parsing module. In some embodiments, the sending module 1520, the receiving module 1530, and the display module 1550 can be combined into a single module, such as a receiving and display module. In some embodiments, the receiving module 1530, the parsing module 1540, and the display module 1550 can be combined into a single module, such as a receiving, parsing, and display module.

[0245] In some embodiments, the generation module 1510, the sending module 1520, the receiving module 1530, and the parsing module 1540 can be combined into a single module, such as a generation, transceiver, and parsing module. In some embodiments, the generation module 1510, the sending module 1520, the receiving module 1530, and the display module 1550 can be combined into a single module, such as a generation, transceiver, and display module. In some embodiments, the generation module 1510, the receiving module 1530, the parsing module 1540, and the display module 1550 can be combined into a single module, such as a generation, transceiver, and display module. In some embodiments, the sending module 1520, the receiving module 1530, the parsing module 1540, and the display module 1550 can be combined into a single module, such as a generation, transceiver, and parsing module. In some embodiments, the generation module 1510, the sending module 1520, the receiving module 1530, the parsing module 1540, and the display module 1550 can be combined into a single module, such as a generation, transceiver, and parsing module.

[0246] It is worth noting that each of the above modules may include one or more modules. If each of the above modules includes multiple modules, different modules are used to perform different operations. For example, the first receiving module is used to receive a service call response sent by the service-called device. The second receiving module is used to obtain the service of the service-called device. This embodiment of the present application is not limited to this.

[0247] FIG16 shows a schematic diagram of a service-invoked device provided by some exemplary embodiments of the present application, the device comprising:

[0248] Receiving module 1610 is configured to receive a service invocation instruction sent by a service invoking device. The service invocation instruction is configured to instruct the service-invoked device to execute the corresponding service according to the service invocation instruction. Exemplarily, the service invocation instruction is configured to instruct the vehicle-mounted device to execute a service to close the left front window. In some embodiments, the service invocation instruction includes a service identifier and a path input parameter.

[0249] The service identifier is used to indicate a service for multiple peer functional entities in a service-called device. In some embodiments, the service-called device includes at least one service, and at least one service includes the service for multiple peer functional entities. Exemplarily, the left front window, the left rear window, the right front window, and the right rear window belong to peer functional entities, and the service for multiple peer functional entities includes a window closing service. Optionally, the service identifier is an identifier including numbers. Exemplarily, the service identifier "1000" corresponds to a window closing service. Optionally, the service identifier is an identifier including letters. Exemplarily, the service identifier "A" corresponds to a window closing service. Optionally, the service identifier is a mixed identifier including numbers and letters. Exemplarily, the service identifier "A1" corresponds to a window closing service. The embodiment of the present application does not limit the form of expression of the service identifier.

[0250] In some embodiments, the multiple peer functional entities refer to functional entities of the same type controlled by the service invoked device. Optionally, the functional entity is a device, and the multiple peer functional entities are multiple devices of the same type, such as vehicles or air conditioners produced by different manufacturers. Optionally, the functional entity is a component of the device, and the multiple peer functional entities are multiple components of the same type, such as different doors and windows of the same vehicle.

[0251] In some embodiments, each functional entity in a plurality of peer functional entities corresponds to its own path parameter value. Exemplarily, the left front window, the left rear window, the right front window, and the right rear window correspond to path parameter value 1, path parameter value 2, path parameter value 3, and path parameter value 4, respectively. Optionally, the path parameter value is a parameter value including text. Exemplarily, the path parameter value 1 corresponding to the left front window is "left front". Optionally, the path parameter value is a parameter value including numbers. Exemplarily, the path parameter value 1 corresponding to the left front window is "1". Optionally, the path parameter value is a mixed parameter value including text and numbers. Exemplarily, the path parameter value 1 corresponding to the left front window is "left 1". In the embodiments of the present application, there is no limitation on the form of expression of the path parameter value. The path input parameter value is a subset of the path parameter value. Exemplarily, assuming that the path parameter values ​​include "left front, left rear, right front, right rear", the path input parameter value can be "left front", "left rear", "right front", "right rear", "left front, left rear", "left front, right front", "left rear, right rear", "right front, right rear", "left front, left rear, right front", "left front, left rear, right rear", "left front, right front, right rear", "left front, right front, right rear", "left rear, right front, right rear", "left front, left rear, right front, right rear".

[0252] The sending module 1620 is used to send a service call response to the service calling device. The service call response is used to indicate the execution result of the service call instruction executed by the service called device. Optionally, the service call response includes a path output parameter value and an execution result output parameter value.

[0253] The path out parameter value is the path parameter value corresponding to at least one functional entity among the multiple peer functional entities that is performing the service. For example, if the vehicle-mounted device is performing a service for closing the left front window, the path out parameter value is "Left Front"; if the vehicle-mounted device is performing a service for closing both the left front window and the right rear window, the path out parameter value is "Left Front, Right Rear".

[0254] The execution result parameter value is used to indicate whether the service-called device executes the service call instruction successfully or unsuccessfully.

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

[0256] The determination module 1630 is configured to initialize services for multiple peer functional entities and determine a path parameter value corresponding to each of the multiple peer functional entities.

[0257] In some embodiments, a service-invoked device initializes services for multiple peer functional entities and determines path parameter values ​​corresponding to each of the multiple peer functional entities. For example, the in-vehicle device includes a window-closing service for vehicle windows. Assuming that the in-vehicle device includes four peer functional entities, namely, the left front window, the left rear window, the right front window, and the right rear window, the path parameter values ​​are determined to include "left front, left rear, right front, and right rear" by initializing the window-closing service for the vehicle windows.

[0258] In some embodiments, the path parameter value is determined by path parameter information.

[0259] In some embodiments, services for multiple peer functional entities are parsed to obtain path parameter information.

[0260] In some embodiments, the services for the multiple peer functional entities carry path parameter information. The path parameter information is determined by initializing the services for the multiple peer functional entities.

[0261] The path parameter information includes description information of the path parameter and / or parameter structure of the path parameter.

[0262] In some embodiments, the description information of the path parameter is used to describe multiple peer functional entities corresponding to the path parameter. Optionally, the description information of the path parameter is used to describe the attributes of multiple peer functional entities. Exemplarily, the description information of the path parameter for the vehicle window is "vehicle component". Optionally, the description information of the path parameter is used to describe the names of multiple peer functional entities. Exemplarily, the description information of the path parameter for the vehicle window is "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, right rear window of the vehicle". Optionally, the description information of the path parameter is used to describe the functions of multiple peer functional entities.

[0263] In some embodiments, a parameter structure for a path parameter is used to indicate the structure of path parameter values ​​corresponding to multiple peer functional entities. Optionally, the parameter structure for a path parameter is used to indicate the order in which the path parameter values ​​corresponding to the multiple peer functional entities are arranged. For example, the parameter structure for a path parameter for a vehicle window indicates that the path parameter values ​​for the vehicle window are arranged in a front-to-back and left-to-right order.

[0264] In some embodiments, based on the path parameter information, a path parameter value corresponding to each functional entity in a plurality of peer functional entities is determined.

[0265] In some embodiments, based on the description information of the path parameters, the path parameter values ​​corresponding to each of the multiple peer functional entities are determined. For example, if the description information of the path parameters for vehicle windows is "left front window of the vehicle, left rear window of the vehicle, right front window of the vehicle, right rear window of the vehicle," then the path parameter values ​​for the vehicle windows are determined to include "left front, left rear, right front, right rear."

[0266] In some embodiments, a path parameter value corresponding to each of the plurality of peer functional entities is determined based on a parameter structure of the path parameter. For example, if the parameter structure of the path parameter for a vehicle window indicates that the path parameter values ​​for the vehicle window are ordered from front to back and from left to right, the path parameter values ​​for the vehicle window are determined to include "front left, rear left, front right, rear right."

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

[0268] The execution module 1640 is used to execute the service call instruction.

[0269] In some embodiments, a service call instruction is executed based on a path input parameter value. The path input parameter value is a set for at least one of the path parameter values. Optionally, the path input parameter value is a set of at least one path parameter value generated based on the user's selection. Exemplarily, assuming that the path parameter values ​​include "left front, left back, right front, right back", if the user selects "left front", the path input parameter value is "left front"; if the user selects "left back", the path input parameter value is "left back"; if the user selects "right front", the path input parameter value is "right front"; if the user selects "right back", the path input parameter value is "right back"; if the user selects "left front, left back", the path input parameter value is "left front, left back"; if the user selects "left front, right front", the path input parameter value is "left front, right front"; if the user selects "left front, right back", the path input parameter value is "left front, right back"; if the user selects "left back, right front", the path input parameter value is "left back, right front"; if the user selects If the user selects "left rear, right rear", the path input parameter value is "left rear, right rear"; if the user selects "right front, right rear", the path input parameter value is "right front, right rear"; if the user selects "left front, left rear, right front", the path input parameter value is "left front, left rear, right front"; if the user selects "left front, left rear, right rear", the path input parameter value is "left front, left rear, right rear"; if the user selects "left front, right front, right rear", the path input parameter value is "left front, right front, right rear"; if the user selects "left rear, right front, right rear", the path input parameter value is "left rear, right front, right rear"; if the user selects "left front, left rear, right front, right rear", the path input parameter value is "left front, left rear, right front, right rear".

[0270] In some embodiments, the service invoked device parses the service invocation instruction to determine the path input parameter values ​​carried in the service invocation instruction. For example, assuming that the path input parameter values ​​carried in the service invocation instruction include "left front, left rear", the service invocation instruction is parsed to determine that the path input parameter values ​​include "left front, left rear".

[0271] It should be noted that the device provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0272] Regarding the device in this embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method and will not be elaborated here.

[0273] In some embodiments, the above-mentioned determination module 1630 and execution module 1640 are optional. In some embodiments, the determination module 1630 can be implemented as a single embodiment. In some embodiments, the execution module 1640 can be implemented as a single embodiment. In some embodiments, the determination module 1630 and the execution module 1640 can be implemented as a single embodiment.

[0274] In some embodiments, the receiving module 1610 and the sending module 1620 may be combined into a single module, such as a transceiver module. In some embodiments, the receiving module 1610 and the determining module 1630 may be combined into a single module, such as a receiving and determining module. In some embodiments, the receiving module 1610 and the executing module 1640 may be combined into a single module, such as a receiving and executing module. In some embodiments, the sending module 1620 and the determining module 1630 may be combined into a single module, such as a sending and determining module. In some embodiments, the sending module 1620 and the executing module 1640 may be combined into a single module, such as a sending and executing module. In some embodiments, the determining module 1630 and the executing module 1640 may be combined into a single module, such as a determining and executing module.

[0275] In some embodiments, the receiving module 1610, the sending module 1620, and the determining module 1630 can be combined into a single module, such as a transceiver and determining module. In some embodiments, the receiving module 1610, the sending module 1620, and the executing module 1640 can be combined into a single module, such as a transceiver and executing module. In some embodiments, the sending module 1620, the determining module 1630, and the executing module 1640 can be combined into a single module, such as a sending, determining, and executing module.

[0276] In some embodiments, the receiving module 1610 , the sending module 1620 , the determining module 1630 , and the executing module 1640 may be combined into a single module, such as a transceiver, determining, and executing module.

[0277] It is worth noting that each of the above modules includes one or more. In the case where each of the above modules includes multiple modules, different modules are used to perform different operations. Exemplarily, the first receiving module is used to receive a service identifier sent by the service calling device. The second receiving module is used to receive a path input parameter value. This embodiment of the present application is not limited to this.

[0278] In related technologies, closing car windows includes multiple services. Among them, the closing left front window service can be described as:

[0279] In some embodiments, the service can be used by the device corresponding to the second terminal, and can also be used across devices. Service calls only need to complete service access through a unified call interface. The unified service definition format is shown in Table 1 below:

[0280] Table 1

[0281] In some embodiments, because services are designed for multi-terminal, multi-vehicle interconnected scenarios, a unified service model is required for terminals and vehicles from different manufacturers. Related solutions struggle to accurately define services for variable vehicle control components. For example, if a vehicle has multiple doors / windows, including four, five, or six, it's difficult to define a unified opening / closing service for doors / windows in different locations. Furthermore, once a single service model is fixed, it becomes difficult to expand.

[0282] The present application provides a method for calling a service. The method includes:

[0283] Add a path parameter to the service model to indicate the path of the service. For example, the service of closing the car window is defined as follows:

[0284] In some embodiments, the service name only represents a type of general operation. The specific meaning of the operation is determined by the service name and the path parameter value. The path parameter value is included in the path input parameter value, indicating the functional entity targeted to the callee. If the path input parameter value selects "left rear", it means that the instruction closes the left rear window. The path parameter value is also included in the path output parameter value, indicating to the caller the functional entity corresponding to the execution result. If the path output parameter value is "left rear", it indicates the execution result of closing the left rear window. The path input parameter value of the service call instruction should be consistent with the path output parameter value of its corresponding execution result.

[0285] In some embodiments, the path parameter value may also indicate multiple peer functional entities.

[0286] In some embodiments, the path parameter value is described through description information (description field). The description information indicates the function of the path parameter value and includes the optional range of the path.

[0287] In some embodiments, the service model can be adaptively defined based on the vehicle conditions using the above path parameter values. For example, for a 6-door car, the window closing service can be defined as follows:

[0288] Figure 17 shows a schematic structural diagram of a terminal device (including an in-vehicle device) provided by an exemplary embodiment of the present application. The terminal device includes: a processor 1701, a receiver 1702, a transmitter 1703, a memory 1704 and a bus 1705.

[0289] The processor 1701 includes one or more processing cores. The processor 1701 executes various functional applications and information processing by running software programs and modules.

[0290] The receiver 1702 and the transmitter 1703 may be implemented as a communication component, which may be a communication chip.

[0291] The memory 1704 is connected to the processor 1701 via a bus 1705 .

[0292] The memory 1704 may be used to store at least one instruction, and the processor 1701 may be used to execute the at least one instruction to implement each step in the above method embodiment.

[0293] In addition, the memory 1704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof. Volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, and programmable read-only memory (PROM).

[0294] In an exemplary embodiment, a computer-readable storage medium is further provided, in which at least one program is stored. The at least one program is loaded and executed by a processor to implement the service calling method provided by each of the above method embodiments.

[0295] In an exemplary embodiment, a computer program product is further provided. When the computer program product is run on a processor of a communication device, the communication device executes the service calling method provided by each of the above method embodiments.

[0296] In an exemplary embodiment, a computer program is also provided, which includes computer instructions, the computer instructions are stored in a computer-readable storage medium, a processor obtains the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to implement the service calling method provided by the above-mentioned various method embodiments.

[0297] Those skilled in the art will appreciate that in one or more of the above examples, the functions described in the embodiments of the present application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0298] The above description is merely an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A method for calling a service, characterized in that: The method is performed by a first terminal, and includes: Generate a service call instruction, wherein the service call instruction includes a service identifier and a path input parameter value; Sending the service calling instruction to the second terminal; receiving a service call response sent by the second terminal, where the service call response is used to indicate an execution result of the service call instruction executed by the second terminal; The service identifier is used to indicate services for multiple peer functional entities in the second terminal, each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value.

2. The method according to claim 1, characterized in that The generating of the service calling instruction comprises: The service calling instruction is generated in response to a setting operation on at least one of the path parameter values.

3. The method according to claim 2, characterized in that The generating the service calling instruction in response to the setting operation for at least one of the path parameter values ​​comprises: In response to a setting operation on at least one of the path parameter values, determining the path input parameter value; Based on the path input parameter value, the service call instruction is generated.

4. The method according to any one of claims 1 to 3, characterized in that: The service call response includes a path output parameter value and an execution result output parameter value; The path output parameter value is a path parameter value corresponding to at least one functional entity among the multiple peer functional entities that executes the service, and the execution result output parameter value is used to indicate whether the second terminal executes the service call instruction successfully or fails.

5. The method according to claim 4, characterized in that The method further comprises: The response result of the service call instruction is displayed, and the response result is used to indicate the success or failure of executing the service call instruction.

6. The method according to claim 5, characterized in that The response result of the service call instruction is displayed based on the path parameter value and the execution result parameter value.

7. The method according to claim 6, characterized in that The display of the response result of the service call instruction includes: Compare the path output parameter value with the path input parameter value to obtain a comparison result; When the comparison result is consistent, the response result of the service call instruction is displayed based on the parameter value of the execution result.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: Acquire a service of the second terminal, the service including the service for multiple peer functional entities; The services for the multiple peer functional entities are parsed to determine the path parameter value corresponding to each functional entity in the multiple peer functional entities.

9. The method according to claim 8, characterized in that The parsing of the services for the multiple peer functional entities to determine the path parameter value corresponding to each functional entity in the multiple peer functional entities includes: Parsing the services for the multiple peer functional entities to obtain path parameter information, wherein the path parameter information includes description information of the path parameters and / or a parameter structure of the path parameters; Based on the path parameter information, a path parameter value corresponding to each functional entity in the multiple peer functional entities is determined.

10. The method according to claim 9, characterized in that The method further comprises: Based on the path parameter value, an interactive interface for the service of multiple peer functional entities is generated.

11. A method for invoking a service, characterized in that: The method is performed by a second terminal, and the method includes: Receiving a service call instruction sent by the first terminal, wherein the service call instruction includes a service identifier and a path input parameter value; Sending a service call response to the first terminal, where the service call response is used to indicate the execution result of the service call instruction executed by the second terminal; The service identifier is used to indicate services for multiple peer functional entities in the second terminal, each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value.

12. The method according to claim 11, characterized in that The service call response includes a path output parameter value and an execution result output parameter value; The path output parameter value is a path parameter value corresponding to at least one functional entity among the multiple peer functional entities that executes the service, and the execution result output parameter value is used to indicate whether the second terminal executes the service call instruction successfully or fails.

13. The method according to claim 12, characterized in that The method further comprises: Execute the service calling instruction.

14. The method according to claim 13, characterized in that The executing the service calling instruction comprises: Based on the path input parameter value, execute the service call instruction.

15. The method according to any one of claims 11 to 14, characterized in that: The method further comprises: Initialize the service for the multiple peer functional entities, and determine the path parameter value corresponding to each functional entity in the multiple peer functional entities.

16. A service calling device, characterized in that: The device comprises: A generating module, used to generate a service calling instruction, wherein the service calling instruction includes a service identifier and a path input parameter value; A sending module, used for sending the service calling instruction to the service called device; A receiving module, used for receiving a service call response sent by the service called device, wherein the service call response is used for indicating the execution result of the service called device executing the service call instruction; The service identifier is used to indicate a service for multiple peer functional entities in the service-called device, each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value.

17. A service called device, characterized in that: The device comprises: A receiving module, used to receive a service calling instruction sent by a service calling device, wherein the service calling instruction includes a service identifier and a path input parameter value; A sending module, used for sending a service calling response to the service calling device, wherein the service calling response is used for indicating the execution result of the service called device executing the service calling instruction; The service identifier is used to indicate a service for multiple peer functional entities in the service-called device, each of the multiple peer functional entities corresponds to its own path parameter value, and the path input parameter value is a subset of the path parameter value.

18. A terminal device, characterized in that: The terminal device comprises: a processor and a memory, wherein the memory stores at least one program; the processor is used to execute the at least one program in the memory to implement the service calling method as described in any one of claims 1 to 15.

19. A vehicle-mounted device, characterized in that: The vehicle-mounted device includes: a processor and a memory, wherein the memory stores at least one program; the processor is used to execute the at least one program in the memory to implement the service calling method as described in any one of claims 1 to 15.

20. A service calling system, characterized in that: The service calling system includes a first terminal and a second terminal; wherein the first terminal is configured to implement the service calling method described in any one of claims 1 to 10, and the second terminal is configured to implement the service calling method described in any one of claims 11 to 15.

21. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one program, and the at least one program is loaded and executed by a processor to implement the service calling method according to any one of claims 1 to 15.

22. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. A processor obtains the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to implement the service calling method as described in any one of claims 1 to 15.

23. A computer program, characterized in that The computer program includes computer instructions, which are stored in a computer-readable storage medium. The processor obtains the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to implement the service calling method as described in any one of claims 1 to 15.

Images