Packaging interface calling method and device, computer equipment and storage medium
The three-layer encapsulation interface system improves interoperability between OEM platforms and vehicle-side systems, enabling efficient interaction and integration.
Patent Information
- Application Number
- CN202411236970.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-04
- Publication Date
- 2024-12-13
AI Technical Summary
Existing technologies have not effectively addressed the challenge of interoperability between different OEM platforms and vehicle-side systems, resulting in inefficient software development and integration.
A method and device are introduced to encapsulate interface calling methods, devices, and systems are used to improve the interoperability between OEM platforms and vehicle-side systems by using a three-layer encapsulation interface system.
Enhances the interoperability between OEM platforms and vehicle-side systems, allowing for efficient interaction and integration.
Smart Images
Figure CN119135697A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, device, computer equipment and storage medium for calling an encapsulation interface. Background Art
[0002] Under the new E / E architecture, the design concept of service-oriented architecture has become a new technological trend. It divides the capabilities of the vehicle into services and splits them into smaller interfaces according to the atomic capabilities of the entire vehicle, so that they can call each other and expand and combine through established interface definitions.
[0003] With the development of the automotive industry, original equipment manufacturers (OEMs) have adopted a multi-product line strategy to meet the market's acceptance of vehicle models. Different product lines use different OEM platforms, and the vehicle-side atomic capability implementation technologies of different OEM platforms are also different.
[0004] In response to this situation, in traditional technology, different OEM platforms provide different packaging interfaces and software development kits (SDKs). Although this method can complete the interaction between different OEM platforms and the vehicle side, it has the problem of low applicability between the OEM platforms and the vehicle side. Summary of the invention
[0005] Based on this, it is necessary to provide a package interface calling method, device, computer equipment and storage medium that can improve applicability in response to the above technical problems.
[0006] In a first aspect, the present application provides a method for calling an encapsulation interface, comprising:
[0007] Obtaining a list of pending instructions sent by the message sender to the first encapsulation interface; the list of pending instructions includes a vehicle-side identifier and an interface identifier;
[0008] The list of instructions to be executed is encoded through the second encapsulation interface to obtain an instruction string;
[0009] Determine the to-be-executed instruction corresponding to the message sender according to the instruction character string through the third encapsulation interface;
[0010] Execute the pending instructions and feedback the execution results to the message sender.
[0011] In one embodiment, obtaining a list of instructions to be executed sent by a message sender to the first encapsulation interface includes:
[0012] Obtaining the to-be-executed instruction sent by the message sender to the first encapsulation interface;
[0013] Generate a vehicle-side identifier according to the instruction to be executed;
[0014] Generate a list of instructions to be executed based on the vehicle-side identifier and the interface identifier of the first encapsulation interface.
[0015] In one embodiment, the instruction list to be executed is encoded to obtain a converted instruction string, including:
[0016] Encoding the vehicle-side identifier in the list of instructions to be executed to obtain a coded identifier;
[0017] Generate a command string including an encoding identifier and an interface identifier.
[0018] In one embodiment, determining the to-be-executed instruction corresponding to the message sender according to the instruction character string includes:
[0019] Decode the command string to obtain the vehicle-side identifier;
[0020] According to the interface identifier and the vehicle-side identifier, the service identifier of the instruction to be executed is determined, wherein the service identifier includes a service sub-identifier; according to the service sub-identifier, it is determined that the message party sends the corresponding instruction to be executed.
[0021] In one embodiment, determining the service identifier of the instruction to be executed according to the interface identifier and the vehicle-side identifier includes:
[0022] Determine the command path information corresponding to the vehicle identifier;
[0023] Determine a service identifier of the instruction to be executed according to the path information of the instruction path information at the first preset path level;
[0024] The service sub-identifier in the service identifier is determined according to the path information of the instruction path information at the second preset path level; the first preset path level is higher than the second path level.
[0025] In one embodiment, feeding back the execution result to the message sender includes:
[0026] Encoding the execution result through the third encapsulation interface to determine a result character string of the execution result;
[0027] Determine an execution result list of the execution result according to the result character string through the second encapsulation interface;
[0028] The execution result list is sent to the message sender through the first encapsulation interface.
[0029] In a second aspect, the present application also provides a package interface calling device, including:
[0030] A list acquisition module, used to acquire a list of instructions to be executed sent by the message sender to the first encapsulation interface; the list of instructions to be executed includes a vehicle-side identifier and an interface identifier;
[0031] An encoding processing module, used for encoding the list of instructions to be executed through the second encapsulation interface to obtain an instruction string;
[0032] An instruction determination module, used to determine the to-be-executed instruction corresponding to the message sender according to the instruction character string through the third encapsulation interface;
[0033] The result feedback module is used to execute the pending instructions and feed back the execution results to the message sender.
[0034] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:
[0035] Obtaining a list of pending instructions sent by the message sender to the first encapsulation interface; the list of pending instructions includes a vehicle-side identifier and an interface identifier;
[0036] The list of instructions to be executed is encoded through the second encapsulation interface to obtain an instruction string;
[0037] Determine the to-be-executed instruction corresponding to the message sender according to the instruction character string through the third encapsulation interface;
[0038] Execute the pending instructions and feedback the execution results to the message sender.
[0039] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:
[0040] Obtaining a list of pending instructions sent by the message sender to the first encapsulation interface; the list of pending instructions includes a vehicle-side identifier and an interface identifier;
[0041] The list of instructions to be executed is encoded through the second encapsulation interface to obtain an instruction string;
[0042] Determine the to-be-executed instruction corresponding to the message sender according to the instruction character string through the third encapsulation interface;
[0043] Execute the pending instructions and feedback the execution results to the message sender.
[0044] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:
[0045] Obtaining a list of pending instructions sent by the message sender to the first encapsulation interface; the list of pending instructions includes a vehicle-side identifier and an interface identifier;
[0046] The list of instructions to be executed is encoded through the second encapsulation interface to obtain an instruction string;
[0047] Determine the to-be-executed instruction corresponding to the message sender according to the instruction character string through the third encapsulation interface;
[0048] Execute the pending instructions and feedback the execution results to the message sender.
[0049] The above-mentioned encapsulation interface calling method, device, computer equipment and storage medium obtain the list of pending instructions sent by the message sender to the first encapsulation interface; the list of pending instructions includes a vehicle-side identifier and an interface identifier; the list of pending instructions is encoded and processed through the second encapsulation interface to obtain an instruction string; the corresponding pending instructions of the message sender are determined according to the instruction string through the third encapsulation interface; the pending instructions are executed, and the execution results are fed back to the message sender. In this embodiment, the interaction between all message senders and the vehicle side can be realized through the three-layer encapsulation interface, which improves the applicability between the message sender and the vehicle side. BRIEF DESCRIPTION OF THE DRAWINGS
[0050] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. 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 paying creative work.
[0051] Figure 1 An application environment diagram of an encapsulation interface calling method provided in this embodiment;
[0052] Figure 2 A schematic diagram of the flow of the first encapsulation interface calling method provided in this embodiment;
[0053] Figure 3 A schematic diagram of a packaging interface provided in this embodiment;
[0054] Figure 4 A structural block diagram of a package interface calling device provided in this embodiment;
[0055] Figure 5 An internal structure diagram of a computer device provided in this embodiment;
[0056] Figure 6 This is a diagram of the internal structure of a computer device provided in this embodiment. DETAILED DESCRIPTION
[0057] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0058] The encapsulation interface calling method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. The vehicle terminal 100 obtains the list of pending instructions sent by the message sender 101 to the first encapsulation interface; the list of pending instructions includes a vehicle-side identifier and an interface identifier; the list of pending instructions is encoded through the second encapsulation interface to obtain an instruction string; the third encapsulation interface determines the pending instructions corresponding to the message sender according to the instruction string; executes the pending instructions, and feeds back the execution results to the message sender. Among them, the message sender can be either a terminal or a server. The terminal can be, but is not limited to, various personal computers, laptops, smart phones, tablets, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car-mounted devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The server can be implemented as an independent server or a server cluster consisting of multiple servers.
[0059] In an exemplary embodiment, Figure 2 As shown, a method for encapsulating interface calls is provided, which is applied to Figure 1 The vehicle-mounted terminal 100 in FIG. 1 is taken as an example to illustrate the method, which includes the following steps 201 to 204. Among them:
[0060] Step 201: Obtain a list of instructions to be executed sent by a message sender to a first encapsulation interface.
[0061] The list of instructions to be executed includes a vehicle-side identifier and an interface identifier. The message sender may be a platform for sending service instructions to the vehicle-mounted terminal, and the message sender may be a platform corresponding to the original equipment manufacturer. The encapsulation interface may be an application programming interface (API).
[0062] One optional implementation manner may be that the first encapsulation interface communicates with the message sender and receives a list of instructions to be executed sent by the message sender.
[0063] Another optional implementation method may be to obtain the instructions to be executed sent by the message sender to the first encapsulation interface; generate a vehicle-side identifier based on the instructions to be executed; and generate a list of instructions to be executed based on the vehicle-side identifier and the interface identifier of the first encapsulation interface.
[0064] Specifically, the first encapsulation interface receives the to-be-executed instructions sent by the message sender, generates a vehicle-side identifier based on the to-be-executed instructions, and simultaneously obtains the interface identifier of the first encapsulation interface, and uses the vehicle-side identifier and the interface identifier as a list of to-be-executed instructions.
[0065] Another optional implementation method may be that the message sender calls the corresponding vehicle-side capability interface through the vehicle-side identifier (Uniform Resource Identifier, URI) of the first-layer encapsulation interface, obtains the interface identifier of the vehicle-side capability interface, and receives the instructions to be executed (i.e., parameter values) in the format of a key-value pair (i.e., a linked list class ArrayList) to obtain the vehicle-side identifier, and then obtains a list of instructions to be executed that includes the vehicle-side identifier and the interface identifier.
[0066] It should be noted that the first encapsulation interface is mainly defined in a format that is easy for developers to understand and remember. The format and parameters of the first encapsulation interface are stable and can be applied to models of different OEM platforms. For example, the following Table 1-An example of an API interface encapsulated for developers is shown. Among them, the attributes defined by the encapsulation interface include APIName, interface description, interface unique identifier, service name, service identifier, vehicle-side uri is the unique identifier for the third-party APP to call the API, and the input and output parameters of the API interface.
[0067] Table 1 - Examples of API interfaces encapsulated for developers
[0068]
[0069] Step 202: Encode the list of instructions to be executed through the second encapsulation interface to obtain an instruction string.
[0070] Among them, the second encapsulation interface is used to solve the mapping of developers calling the first encapsulation interface to the third encapsulation interface of different platforms, playing a connecting role.
[0071] An optional implementation method may be that after the second encapsulation interface receives the first encapsulation interface format call and the incoming vehicle-side identifier and interface identifier, it converts the vehicle-side identifier, that is, the calling identification information of the second encapsulation interface continues to use the vehicle-side identifier transmitted by the first encapsulation interface; the parameter ArrayList corresponding to the interface identifier is converted into a 64-encoded (Base64) string, and the instruction string is determined according to the converted vehicle-side identifier and the converted interface identifier, and finally the converted vehicle-side identifier and instruction string are input into the third-layer encapsulation interface through inter-process communication (Binder).
[0072] In some embodiments, encoding is performed on the list of instructions to be executed to obtain a converted instruction string, including: encoding a vehicle-side identifier in the list of instructions to be executed to obtain an encoding identifier; and generating an instruction string including the encoding identifier and an interface identifier.
[0073] Specifically, the vehicle-side identifier in the list of instructions to be executed is encoded to obtain a coding identifier, and the instruction character string is determined based on the coding identifier and the interface identifier.
[0074] Step 203: Determine the to-be-executed instruction corresponding to the message sender according to the instruction character string through the third encapsulation interface.
[0075] Among them, the third encapsulation interface can be used to implement the service instructions of the message sender.
[0076] Specifically, the third encapsulation interface receives the instruction character string sent by the second encapsulation interface, and parses the instruction character string to determine the to-be-executed instruction corresponding to the message sender.
[0077] Step 204: execute the pending instruction and feedback the execution result to the message sender.
[0078] In some embodiments, the execution result is fed back to the message sender, including: encoding the execution result through a third encapsulation interface to determine a result string of the execution result; determining an execution result list of the execution result based on the result string through a second encapsulation interface; and sending the execution result list to the message sender through the first encapsulation interface.
[0079] Specifically, the third encapsulation interface returns the execution result to the second interface encapsulation, and the returned ArrayList is also packaged into a String type for transmission. When the second-layer interface encapsulation layer receives the data, it parses the String type data into an ArrayList.
[0080] For example, Figure 3Schematic diagram of the encapsulation interface, in which the third-party APP is the message sender, SDK is the software development kit located in the vehicle terminal, "the interface layer encapsulated by SDK to the third-party APP" is the first encapsulation interface, "the interface layer encapsulated by SDK to CSC APK" is the second encapsulation interface, and "the interface encapsulated by parsing SDK to CSC APK" is the third encapsulation interface.
[0081] It should be noted that in this embodiment, the definition of the first encapsulation interface is kept as stable as possible, and the API interfaces for developers on different platforms use a unified definition format. The second encapsulation interface is an abstract component mapping implementation for different platform API interfaces, which solves the conversion of the first encapsulation interface to the developer API consistency and the third encapsulation interface to specifically implement the link diversity. The third encapsulation interface implements the link separately, and according to the API call mapping rules agreed with the second encapsulation interface, parses the API called by the first encapsulation interface, converts it into a specific method for implementing the API instruction link on different platforms, and realizes the specific functions of the API.
[0082] The above encapsulation interface calling method obtains the list of pending instructions sent by the message sender to the first encapsulation interface; the list of pending instructions includes the vehicle-side identifier and the interface identifier; the list of pending instructions is encoded through the second encapsulation interface to obtain an instruction string; the corresponding pending instructions of the message sender are determined according to the instruction string through the third encapsulation interface; the pending instructions are executed, and the execution results are fed back to the message sender. In this embodiment, the interaction between all message senders and the vehicle-side can be realized through the three-layer encapsulation interface, which improves the applicability between the message sender and the vehicle-side.
[0083] In some embodiments, the to-be-executed instruction corresponding to the message sender is determined based on the instruction string, including: decoding the instruction string to obtain a vehicle-side identifier; determining the service identifier of the to-be-executed instruction based on the interface identifier and the vehicle-side identifier, wherein the service identifier includes a service sub-identifier; and determining, based on the service sub-identifier, that the message party sends the corresponding to-be-executed instruction.
[0084] In some embodiments, the service identifier of the instruction to be executed is determined based on the interface identifier and the vehicle-side identifier, including: determining the instruction path information corresponding to the vehicle identifier; determining the service identifier of the instruction to be executed based on the path information of the instruction path information at a first preset path level; determining the service sub-identifier in the service identifier based on the path information of the instruction path information at a second preset path level; the first preset path level is higher than the second path level.
[0085] Specifically, the instruction string is decoded to obtain the corresponding Byte array, which is then converted into a key-value pair parameter list in ArrayList format. At the same time, the vehicle identifier is parsed to determine the service sub-identifier, and the service sub-identifier is found through the service method configuration table in the third encapsulation interface, and the instruction to be executed corresponding to the service sub-identifier is executed.
[0086] For example, the vehicle identifier is val: / / Vehicle / static / Media / getMediaPlayStatus. Assuming that the first preset path level is level 3 and the second preset path level is level 4, the path information service_id under the first preset path level is Media, and the path information method_id under the second preset path level is getMediaPlayStatus. The specific implementation method of the service_id and method_id mapping API interface is searched in the service method configuration table stored in the third encapsulation interface.
[0087] This embodiment can realize the specific functions of the API more conveniently and accurately.
[0088] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0089] Based on the same inventive concept, the embodiment of the present application also provides a package interface calling device for implementing the package interface calling method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more package interface calling device embodiments provided below can refer to the limitations on the package interface calling method above, and will not be repeated here.
[0090] In an exemplary embodiment, Figure 4 As shown, a package interface calling device is provided, comprising: a list acquisition module 10, an encoding processing module 11, an instruction determination module 12 and a result feedback module 13, wherein:
[0091] A list acquisition module 10 is used to acquire a list of instructions to be executed sent by the message sender to the first encapsulation interface; the list of instructions to be executed includes a vehicle-side identifier and an interface identifier;
[0092] An encoding processing module 11 is used to encode the list of instructions to be executed through a second encapsulation interface to obtain an instruction string;
[0093] An instruction determination module 12, configured to determine the to-be-executed instruction corresponding to the message sender according to the instruction string through the third encapsulation interface;
[0094] The result feedback module 13 is used to execute the instructions to be executed and feed back the execution results to the message sender.
[0095] In some embodiments, Figure 4 The list acquisition module 10 is also used to obtain the instructions to be executed sent by the message sender to the first encapsulation interface; generate a vehicle-side identifier according to the instructions to be executed; and generate a list of instructions to be executed according to the vehicle-side identifier and the interface identifier of the first encapsulation interface.
[0096] In some embodiments, Figure 4 The encoding processing module 11 is also used to encode the vehicle-side identifier in the list of instructions to be executed to obtain a coding identifier; and generate an instruction string including the coding identifier and the interface identifier.
[0097] In some embodiments, Figure 4 The instruction determination module 12 is also used to decode the instruction string to obtain a vehicle-side identifier; determine the service identifier of the instruction to be executed based on the interface identifier and the vehicle-side identifier, where the service identifier includes a service sub-identifier; and determine, based on the service sub-identifier, that the message party sends the corresponding instruction to be executed.
[0098] In some embodiments, Figure 4 The instruction determination module 12 is also used to determine the instruction path information corresponding to the vehicle identifier; determine the service identifier of the instruction to be executed according to the path information of the instruction path information at the first preset path level; determine the service sub-identifier in the service identifier according to the path information of the instruction path information at the second preset path level; the first preset path level is higher than the second path level.
[0099] In some embodiments, Figure 4 The result feedback module 13 is also used to encode the execution result through the third encapsulation interface to determine the result string of the execution result; determine the execution result list of the execution result according to the result string through the second encapsulation interface; and send the execution result list to the message sender through the first encapsulation interface.
[0100] Each module in the encapsulation interface calling device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.
[0101] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 5 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store execution result data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a package interface calling method is implemented.
[0102] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 6As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a package interface calling method is implemented. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.
[0103] Those skilled in the art will understand that Figure 5 and Figure 6 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0104] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.
[0105] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.
[0106] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.
[0107] It should be noted that the data involved in this application (including but not limited to data used for analysis, stored data, displayed data, etc.) are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.
[0108] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.
[0109] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0110] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.
Claims
1. A method for calling an encapsulation interface, characterized in that: The method comprises: Obtaining a list of pending instructions sent by the message sender to the first encapsulation interface; the list of pending instructions includes a vehicle-side identifier and an interface identifier; Encoding the list of instructions to be executed through a second encapsulation interface to obtain an instruction string; Determining, through a third encapsulation interface, the to-be-executed instruction corresponding to the message sender according to the instruction character string; Execute the to-be-executed instruction, and feed back the execution result to the message sender.
2. The method according to claim 1, characterized in that: The obtaining of a list of instructions to be executed sent by the message sender to the first encapsulation interface includes: Obtaining the to-be-executed instruction sent by the message sender to the first encapsulation interface; Generate a vehicle-side identifier according to the instruction to be executed; The list of instructions to be executed is generated according to the vehicle-side identifier and the interface identifier of the first encapsulation interface.
3. The method according to claim 1, characterized in that The encoding process of the to-be-executed instruction list to obtain a converted instruction string includes: Encoding the vehicle-side identifier in the list of instructions to be executed to obtain a coded identifier; Generate an instruction string including the encoding identifier and the interface identifier.
4. The method according to claim 1, characterized in that: The step of determining, according to the instruction character string, the instruction to be executed corresponding to the message sender includes: Decoding the command character string to obtain a vehicle-side identifier; According to the interface identifier and the vehicle-side identifier, the service identifier of the instruction to be executed is determined, wherein the service identifier includes a service sub-identifier; according to the service sub-identifier, it is determined that the message party sends the corresponding instruction to be executed.
5. The method according to claim 4, characterized in that The determining, according to the interface identifier and the vehicle-side identifier, the service identifier of the instruction to be executed comprises: Determining instruction path information corresponding to the vehicle identifier; Determine the service identifier of the instruction to be executed according to the path information of the instruction path information at the first preset path level; The service sub-identifier in the service identifier is determined according to the path information of the instruction path information at a second preset path level; the first preset path level is higher than the second path level.
6. The method according to claim 1, characterized in that Feeding back the execution result to the message sender includes: Encoding the execution result through the third encapsulation interface to determine a result character string of the execution result; Determining an execution result list of the execution result according to the result character string through the second encapsulation interface; The execution result list is sent to the message sender through the first encapsulation interface.
7. A package interface calling device, characterized in that: The device comprises: A list acquisition module, used to acquire a list of instructions to be executed sent by the message sender to the first encapsulation interface; the list of instructions to be executed includes a vehicle-side identifier and an interface identifier; An encoding processing module, used for encoding the list of instructions to be executed through a second encapsulation interface to obtain an instruction string; An instruction determination module, used to determine the to-be-executed instruction corresponding to the message sender according to the instruction character string through a third encapsulation interface; The result feedback module is used to execute the instruction to be executed and feed back the execution result to the message sender.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.