CN112711247A - Interface display method, interface display device and electronic equipment - Google Patents
Interface display method, interface display device and electronic equipment Download PDFInfo
- Publication number
- CN112711247A CN112711247A CN202011568186.2A CN202011568186A CN112711247A CN 112711247 A CN112711247 A CN 112711247A CN 202011568186 A CN202011568186 A CN 202011568186A CN 112711247 A CN112711247 A CN 112711247A
- Authority
- CN
- China
- Prior art keywords
- interface
- identifier
- diagnostic protocol
- model
- display
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
- G05B23/0221—Preprocessing measurements, e.g. data collection rate adjustment; Standardization of measurements; Time series or signal analysis, e.g. frequency analysis or wavelets; Trustworthiness of measurements; Indexes therefor; Measurements using easily measured parameters to estimate parameters difficult to measure; Virtual sensor creation; De-noising; Sensor fusion; Unconventional preprocessing inherently present in specific fault detection methods like PCA-based methods
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application discloses an interface display method, an interface display device, electronic equipment and a computer readable storage medium. The interface display method comprises the following steps: loading a diagnostic protocol; analyzing the diagnostic protocol, and judging whether the diagnostic protocol has a preset identifier; if the identifier exists, mapping to obtain a corresponding interface display interface based on the identifier, wherein the identifier is used for representing an interface generation action; and calling the interface display interface to output the interface configured by the interface display interface. By the aid of the method and the device, the diagnostic protocol can predict the interface to be displayed, and display errors are reduced.
Description
Technical Field
The present application relates to a vehicle diagnostic technology, and in particular, to an interface display method, an interface display apparatus, an electronic device, and a computer-readable storage medium.
Background
Current automotive diagnostic protocols do not define the layout and functionality of the client interface displayed by the diagnostic program. At present, the display of the interface related to the diagnostic program is independently controlled by the diagnostic program, and the configurator of the diagnostic protocol cannot predict the mode of the interface to be displayed. That is, in the prior art, the diagnostic protocol cannot be associated with the client interface, and cannot predict the interface layout and functions related to the diagnostic process, which may cause that the display of the client interface cannot be well matched with the diagnostic protocol, and a display error is easily caused.
Disclosure of Invention
The application provides an interface display method, an interface display device, an electronic device and a computer readable storage medium, which can enable a diagnostic protocol to predict an interface to be displayed and reduce the occurrence of display errors.
In a first aspect, the present application provides an interface display method, including:
loading a diagnostic protocol;
analyzing the diagnosis protocol, and judging whether the diagnosis protocol has a preset identifier;
if the identifier exists, mapping to obtain a corresponding interface display interface based on the identifier, wherein the identifier is used for representing an interface generating action;
and calling the interface display interface to output the interface configured by the interface display interface.
Optionally, before obtaining the corresponding interface display interface based on the identifier mapping, the interface display method further includes:
setting at least one interface model based on the function and appearance layout of an interface required by a user, wherein the function and/or appearance layout corresponding to different interface models is different;
the diagnostic protocol is configured according to the at least one interface model such that each identifier in the diagnostic protocol corresponds to an interface model.
Optionally, the configuring the diagnostic protocol according to the at least one interface model so that each identifier in the diagnostic protocol corresponds to one interface model includes:
configuring a corresponding handle for each interface model, wherein the handle is used for indicating the type of the interface model, the number of parameters of the interface model and the parameter type of the interface model;
and inserting an identifier into a target position in the diagnostic protocol, wherein the identifier corresponds to a handle specified by a user, and the target position is a position in the diagnostic protocol, which needs to output a display interface.
Optionally, the handle includes a general structure, the general structure includes general parameters, a use type of the general parameters, and an input type of the general parameters, and the general structure is configured to configure the number of parameters of the interface model and the parameter type of the interface model.
Optionally, a parameter in the handle for indicating the type of the interface model is a modality identification parameter, and the interface display method further includes:
determining a modal identification parameter transmitted into the interface display interface;
if the modal identification parameter is a preset first numerical value, determining that the interface output based on the interface display interface is a modal interface;
and if the modal identification parameter is a preset second numerical value, determining that the interface output based on the interface display interface is a non-modal interface.
Optionally, the handle corresponding to each of the at least one interface model is stored in a preset database.
In a second aspect, the present application provides an interface display apparatus, comprising:
a loading unit for loading a diagnostic protocol;
the analysis unit is used for analyzing the diagnosis protocol and judging whether the diagnosis protocol has a preset identifier or not;
a mapping unit, configured to map, if the identifier exists, the identifier to obtain a corresponding interface display interface, where the identifier is used to indicate an interface generation action;
and the calling unit is used for calling the interface display interface so as to output the interface configured by the interface display interface.
Optionally, the interface display device further includes:
the interface management system comprises a setting unit, a processing unit and a display unit, wherein the setting unit is used for setting at least one interface model based on the function and appearance layout of an interface required by a user, and the function and/or appearance layout corresponding to different interface models is different;
and a configuration unit, configured to configure the diagnostic protocol according to the at least one interface model, so that each identifier in the diagnostic protocol corresponds to one interface model.
Optionally, the configuration unit includes:
a handle configuration unit, configured to configure, for each interface model, a corresponding handle for the interface model, where the handle is used to indicate a type of the interface model, a number of parameters of the interface model, and a parameter type of the interface model;
and the identifier configuration unit is used for inserting an identifier into a target position in the diagnostic protocol, wherein the identifier corresponds to a handle specified by a user, and the target position is a position in the diagnostic protocol, which is required to output a display interface.
Optionally, the handle includes a general structure, the general structure includes general parameters, a use type of the general parameters, and an input type of the general parameters, and the general structure is configured to configure the number of parameters of the interface model and the parameter type of the interface model.
Optionally, a parameter in the handle for indicating a type of the interface model is a modality identification parameter, and the interface display apparatus further includes:
a parameter determining unit, configured to determine a modal identification parameter transmitted to the interface display interface;
an interface type determining unit, configured to determine that the interface output based on the interface display interface is a modal interface if the modal identification parameter is a preset first numerical value, and determine that the interface output based on the interface display interface is a non-modal interface if the modal identification parameter is a preset second numerical value.
Optionally, the handle corresponding to each of the at least one interface model is stored in a preset database.
In a third aspect, the present application provides an electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method according to the first aspect when executing the computer program.
In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method of the first aspect.
In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by one or more processors, performs the steps of the method of the first aspect as described above.
Compared with the prior art, the application has the beneficial effects that: the user can configure identifiers used for representing interface generation actions in the diagnosis protocol in advance, and configure interface display interfaces mapped by the identifiers in advance, so that after the diagnosis protocol is loaded and analyzed, once the identifiers are judged to exist in the diagnosis protocol, the corresponding interface display interfaces can be obtained based on the mapping of the identifiers, and the interfaces configured by the interface display interfaces can be output by calling the interface display interfaces. The process enables the diagnostic protocol to be associated with the interface to be displayed in the diagnostic process, so that the interface display operation of part of the diagnostic functions can be controlled by the diagnostic protocol; that is, the diagnostic protocol can predict the interface to be displayed, and display errors are reduced. It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart illustrating an implementation of an interface display method provided in an embodiment of the present application;
FIG. 2 is a schematic configuration flow diagram of a diagnostic protocol provided in an embodiment of the present application;
fig. 3 is a block diagram of an interface display device according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
The current diagnostic protocol of the automobile can only store diagnostic data, such as diagnostic instructions that the diagnostic program needs to send to the vehicle, and related algorithms for how to analyze data returned by the vehicle after the vehicle returns the data to the diagnostic program, and cannot define the layout and functions of a client interface displayed by the diagnostic program. At present, the display of the interface related to the diagnostic program is independently controlled by the diagnostic program, and the configurator of the diagnostic protocol cannot predict the mode of the interface to be displayed. That is, in the prior art, the diagnostic protocol cannot be associated with the client interface, and cannot predict the interface layout and functions related to the diagnostic process, which may cause that the display of the client interface cannot be well matched with the diagnostic protocol, and a display error is easily caused. Based on this, the embodiment of the application provides an interface display method, an interface display device, an electronic device, and a computer-readable storage medium, which can enable a diagnostic protocol to predict an interface to be displayed and reduce the occurrence of display errors. In order to explain the technical solutions proposed in the embodiments of the present application, the following description will be given by way of specific examples.
An interface display method provided in an embodiment of the present application is described below. The interface display method can be applied to electronic equipment capable of loading a diagnosis protocol and displaying a diagnosis interface, such as diagnosis equipment. Referring to fig. 1, the interface display method includes:
In the embodiment of the application, after the electronic device establishes connection with the vehicle, it can be considered that the current user is ready to use the electronic device to perform diagnosis operation on the vehicle. At this point, the diagnostic program in the electronic device may begin loading diagnostic protocols in preparation for subsequent possible diagnostic operations.
102, analyzing the diagnosis protocol, and judging whether the diagnosis protocol has a preset identifier;
in this embodiment of the application, the electronic device may start to analyze the diagnostic protocol after the diagnostic protocol is loaded, so as to obtain various pieces of information carried by the diagnostic protocol. The information concerned by the embodiment of the application is a preset identifier. Based on this, after the diagnostic protocol is resolved, whether the diagnostic protocol has a preset identifier can be judged.
And 103, if the identifier exists, obtaining a corresponding interface display interface based on the identifier mapping.
In this embodiment, in the case that the preset identifier exists in the diagnostic protocol, the electronic device may obtain, based on the identifier mapping, an interface display interface corresponding to the identifier. The identifier may be considered a predefined field in the diagnostic protocol that may be used to indicate that an operation should exist or be represented in the location for the display of a boundary (i.e., interface generation). Specifically, the interface display interface is a C + + interface. If no identifier exists in the diagnostic protocol, it is considered that no special interface display operation is involved in the diagnostic process, which is not the case in the focus of the embodiments of the present application.
And 104, calling the interface display interface to output the interface configured by the interface display interface.
In the embodiment of the application, after the interface display interface corresponding to the identifier read in the diagnostic protocol is acquired, the electronic device can call the interface display interface to output the interface configured by the interface display interface.
Referring to fig. 2, fig. 2 is a schematic diagram illustrating a configuration flow of a diagnostic protocol. Obviously, the configuration operation of the diagnostic protocol should be completed before step 103. The configuration flow of the diagnostic protocol is explained and illustrated below:
in the embodiment of the present application, when a user performs various diagnostic operations, particularly diagnostic operations of a specific function, such as Electronic Control Unit (ECU) flashing, using a diagnostic protocol, a specific interface needs to be output for display. Therefore, a plurality of interface models can be set in advance according to the needs of the user, wherein the function and/or appearance layout realized by different interface models is different. For example, the function of the interface model a is to display information, which takes the appearance layout of UI 1; the function of the interface model B is to input information, but the appearance layout adopted by the interface model B is also UI 1; the interface model C also functions to display information, but takes the appearance layout UI 2. That is, two different interface models having the same function and the same layout are not set.
In the embodiment of the present application, after a plurality of interface models are set based on the function and appearance layout of the interface required by the user, the diagnostic protocol can be configured according to the set interface models. Specifically, an identifier may be inserted at each position in the diagnostic protocol where an interface needs to be output for display, and the identifier is correspondingly associated with a certain interface model, so that when the diagnostic protocol is loaded and the identifier is read, the subsequent electronic device may call the corresponding interface model through the mapped interface display interface.
For example, when the diagnostic protocol is configured according to the interface model, a corresponding handle may be configured for each interface model. Moreover, each interface model and the corresponding handle can be stored in a preset database for the user to look up and call. The handle is used for indicating the type of the interface model, the number of parameters of the interface model and the type of the parameters of the interface model. The handle can be considered to resemble a signature. For the identifiers inserted at each target position in the diagnostic protocol, a handle specified by a user must be uniquely associated based on the needs of the user, so that when the mapped interface display interface is called, the application of the interface model is realized through the handle associated with the identifier. It should be noted that the target position refers to a position in the diagnostic protocol where the display interface needs to be output. For example, if the ECU configured in the diagnostic protocol writes a special function of the diagnostic operation, and a specific type of display interface needs to be output (the interface model used is interface model a), a position of an output display interface (for example, after a specific data is read) may be selected as a target position within the range of the ECU configured in the diagnostic protocol, and an identifier is inserted into the target position and is associated with a handle corresponding to the display interface a.
In some embodiments, the handle includes a general structure, the general structure includes general parameters, a use type of the general parameters, and an input type of the general parameters, and the general structure is configured to configure the number of parameters of the interface model and the parameter type of the interface model. An example of this general structure is given below:
the first half of the general structure is an initialization process, which is not described herein. There are three members of the generic structure, which are explained and illustrated below:
in the above example, in consideration of the uncertainty of the parameter type of the parameter required by the interface, for example, some parameters required by the interface may be a string type, and some parameters required by the interface may be an integer (int) type, so that a general data type "otxgenerraltype" needs to be defined in the structure body to store a specific parameter "m _ RealData" (which may be an input parameter or an output parameter) required by the interface; it can be considered that "m _ RealData" is a parameter related to the displayed interface.
In the above example, "otxSTRING m _ strDataType" is used to indicate the representation form, i.e. the usage type, of the parameter in the displayed interface, and may be defined by a predefined macro, for example, a predefined macro "tlle" indicates that the parameter can be used as an interface TITLE, a predefined macro "MESSAGE" indicates that the parameter can be used as a MESSAGE, a predefined macro "BUTTON" indicates that the parameter can be used as a virtual BUTTON, a predefined macro "CHOICE" indicates that the parameter can be used as an option, and the like, and is not limited herein.
In the above example, "otxINT 32 m _ iType" is used to indicate the input and output type of the parameter in the displayed interface, for example, "0" indicates that the parameter is an input parameter, and "1" indicates that the parameter is an output parameter, and the like, and is not limited herein.
In some embodiments, the parameter in the handle for indicating the type of the interface model is a modality identification parameter otxBOOL bModel. The modality identification parameter otxBOOL bModel is one of the interface parameters. The user may configure in the diagnostic protocol whether the interface to be displayed is a modal interface or a modeless interface. By way of example only, based on the generic structure set forth above, the interface display interface to which the identifier is mapped may be:
void OpenScreen(otxBOOL bModel,vector<otxScreenArg>&vArgs)
wherein, otxBOOL bModel is a modal identification parameter. The electronic device may first determine a modality identification parameter that is transmitted to the interface display interface based on the diagnostic protocol, determine that the interface output based on the interface display interface is a modal interface if the modality identification parameter is a preset first value (e.g., bmode ═ true), and determine that the interface output based on the interface display interface is a non-modal interface if the modality identification parameter is a preset second value (e.g., bmode ═ false); the "vector < otxScreenArg > & vrgs" points to the general structure "otxScreenArg" indicated above. It can be considered that the parenthesized content in the interface display interface (i.e. otxBOOL bModel, vector < otxScreenArg > & vArgs) is the handle corresponding to the mapped identifier.
As can be seen from the above, according to the embodiment of the application, a user may configure identifiers used for representing interface generation actions in a diagnostic protocol in advance, and configure interface display interfaces corresponding to the identifiers in advance, so that after the diagnostic protocol is loaded and analyzed, once it is determined that the identifiers exist in the diagnostic protocol, the corresponding interface display interfaces may be obtained based on mapping of the identifiers, and the interfaces configured by the interface display interfaces may be output by calling the interface display interfaces. The process enables the diagnostic protocol to be associated with the interface to be displayed in the diagnostic process, so that the interface display operation of part of the diagnostic functions can be controlled by the diagnostic protocol; that is, the diagnostic protocol can predict the interface to be displayed, and display errors are reduced.
Corresponding to the interface display method provided above, the embodiment of the present application further provides an interface display apparatus. As shown in fig. 3, the interface display apparatus 300 includes:
a loading unit 301 for loading a diagnostic protocol;
an analyzing unit 302, configured to analyze the diagnostic protocol and determine whether the diagnostic protocol has a preset identifier;
a mapping unit 303, configured to obtain, if the identifier exists, a corresponding interface display interface based on the identifier mapping;
the invoking unit 304 is configured to invoke the interface display interface to output an interface configured by the interface display interface.
Optionally, the interface display device 300 further includes:
the interface management system comprises a setting unit, a processing unit and a display unit, wherein the setting unit is used for setting at least one interface model based on the function and appearance layout of an interface required by a user, and the function and/or appearance layout corresponding to different interface models is different;
and a configuration unit, configured to configure the diagnostic protocol according to the at least one interface model, so that each identifier in the diagnostic protocol corresponds to one interface model.
Optionally, the configuration unit includes:
a handle configuration unit, configured to configure, for each interface model, a corresponding handle for the interface model, where the handle is used to indicate a type of the interface model, a number of parameters of the interface model, and a parameter type of the interface model;
and the identifier configuration unit is used for inserting an identifier into a target position in the diagnostic protocol, wherein the identifier corresponds to a handle specified by a user, and the target position is a position in the diagnostic protocol, which is required to output a display interface.
Optionally, the handle includes a general structure, the general structure includes general parameters, a use type of the general parameters, and an input type of the general parameters, and the general structure is configured to configure the number of parameters of the interface model and the parameter type of the interface model.
Optionally, a parameter in the handle for indicating the type of the interface model is a modality identification parameter, and the interface display apparatus 300 further includes:
a parameter determining unit, configured to determine a modal identification parameter transmitted to the interface display interface;
an interface type determining unit, configured to determine that the interface output based on the interface display interface is a modal interface if the modal identification parameter is a preset first numerical value, and determine that the interface output based on the interface display interface is a non-modal interface if the modal identification parameter is a preset second numerical value.
Optionally, the handle corresponding to each of the at least one interface model is stored in a preset database.
Therefore, through the scheme of the application, the user can configure the identifier for representing the interface generating action in the diagnostic protocol in advance, and configure the interface display interface corresponding to each identifier in advance, so that after the diagnostic protocol is loaded and analyzed, once the identifier is judged to exist in the diagnostic protocol, the corresponding interface display interface can be obtained based on the identifier mapping, and the interface configured by the interface display interface can be output by calling the interface display interface. The process enables the diagnostic protocol to be associated with the interface to be displayed in the diagnostic process, so that the interface display operation of part of the diagnostic functions can be controlled by the diagnostic protocol; that is, the diagnostic protocol can predict the interface to be displayed, and display errors are reduced.
Corresponding to the interface display method provided above, an embodiment of the application further provides an electronic device. Referring to fig. 4, an electronic device 4 in the embodiment of the present application includes: a memory 401, one or more processors 402 (only one shown in fig. 4), and computer programs stored on the memory 401 and executable on the processors. Wherein: the memory 401 is used for storing software programs and units, and the processor 402 executes various functional applications and interface displays by running the software programs and units stored in the memory 401, so as to acquire resources corresponding to the preset events. Specifically, the processor 402, by running the above-mentioned computer program stored in the memory 401, implements the steps of:
loading a diagnostic protocol;
analyzing the diagnosis protocol, and judging whether the diagnosis protocol has a preset identifier;
if the identifier exists, obtaining a corresponding interface display interface based on the identifier mapping;
and calling the interface display interface to output the interface configured by the interface display interface.
Assuming that the above is the first possible implementation manner, in a second possible implementation manner provided on the basis of the first possible implementation manner, before the corresponding interface display interface is obtained based on the identifier mapping, the processor 402 further implements the following steps when running the computer program stored in the memory 401:
setting at least one interface model based on the function and appearance layout of an interface required by a user, wherein the function and/or appearance layout corresponding to different interface models is different;
the diagnostic protocol is configured according to the at least one interface model such that each identifier in the diagnostic protocol corresponds to an interface model.
In a third possible implementation form based on the first possible implementation form, the configuring the diagnostic protocol according to the at least one interface model so that each identifier in the diagnostic protocol corresponds to one interface model includes:
configuring a corresponding handle for each interface model, wherein the handle is used for indicating the type of the interface model, the number of parameters of the interface model and the parameter type of the interface model;
and inserting an identifier into a target position in the diagnostic protocol, wherein the identifier corresponds to a handle specified by a user, and the target position is a position in the diagnostic protocol, which needs to output a display interface.
In a fourth possible embodiment based on the third possible embodiment, the handle includes a general structure, the general structure includes general parameters, a use type of the general parameters, and an input type of the general parameters, and the general structure is configured to configure the number of parameters of the interface model and the parameter type of the interface model.
In a fifth possible implementation manner provided as the basis of the third possible implementation manner, the parameter in the handle for indicating the type of the interface model is a modality identification parameter, and the processor 402 further implements the following steps when executing the computer program stored in the memory 401:
determining a modal identification parameter transmitted into the interface display interface;
if the modal identification parameter is a preset first numerical value, determining that the interface output based on the interface display interface is a modal interface;
and if the modal identification parameter is a preset second numerical value, determining that the interface output based on the interface display interface is a non-modal interface.
In a sixth possible implementation manner provided on the basis of the third possible implementation manner, handles corresponding to the at least one interface model are stored in a preset database.
It should be understood that in the embodiments of the present Application, the Processor 402 may be a Central Processing Unit (CPU), and the Processor may be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Therefore, through the scheme of the application, the user can configure the identifier for representing the interface generating action in the diagnostic protocol in advance, and configure the interface display interface corresponding to each identifier in advance, so that after the diagnostic protocol is loaded and analyzed, once the identifier is judged to exist in the diagnostic protocol, the corresponding interface display interface can be obtained based on the identifier mapping, and the interface configured by the interface display interface can be output by calling the interface display interface. The process enables the diagnostic protocol to be associated with the interface to be displayed in the diagnostic process, so that the interface display operation of part of the diagnostic functions can be controlled by the diagnostic protocol; that is, the diagnostic protocol can predict the interface to be displayed, and display errors are reduced.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned functions may be distributed as different functional units and modules according to needs, that is, the internal structure of the apparatus may be divided into different functional units or modules to implement all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of external device software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described system embodiments are merely illustrative, and for example, the division of the above-described modules or units is only one logical functional division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The integrated unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. The computer program includes computer program code, and the computer program code may be in a source code form, an object code form, an executable file or some intermediate form. The computer-readable storage medium may include: any entity or device capable of carrying the above-described computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer readable Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signal, telecommunication signal, software distribution medium, etc. It should be noted that the computer readable storage medium may contain other contents which can be appropriately increased or decreased according to the requirements of the legislation and the patent practice in the jurisdiction, for example, in some jurisdictions, the computer readable storage medium does not include an electrical carrier signal and a telecommunication signal according to the legislation and the patent practice.
The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. An interface display method, comprising:
loading a diagnostic protocol;
analyzing the diagnostic protocol, and judging whether the diagnostic protocol has a preset identifier;
if the identifier exists, mapping to obtain a corresponding interface display interface based on the identifier, wherein the identifier is used for representing an interface generation action;
and calling the interface display interface to output the interface configured by the interface display interface.
2. The interface display method of claim 1, wherein prior to said deriving the corresponding interface display interface based on the identifier mapping, the interface display method further comprises:
setting at least one interface model based on the function and appearance layout of an interface required by a user, wherein the function and/or appearance layout corresponding to different interface models is different;
configuring the diagnostic protocol in accordance with the at least one interface model such that each identifier in the diagnostic protocol corresponds to an interface model.
3. The interface display method of claim 2, wherein said configuring the diagnostic protocol such that each identifier in the diagnostic protocol corresponds to an interface model according to the at least one interface model comprises:
configuring a corresponding handle for each interface model, wherein the handle is used for indicating the type of the interface model, the number of parameters of the interface model and the type of the parameters of the interface model;
and inserting an identifier into a target position in the diagnostic protocol, wherein the identifier corresponds to a handle specified by a user, and the target position is a position in the diagnostic protocol where a display interface is required to be output.
4. The interface display method according to claim 3, wherein the handle includes a generic structure, the generic structure includes generic parameters, a usage type of the generic parameters, and an input type of the generic parameters, and the generic structure is configured to configure the number of parameters of the interface model and the parameter type of the interface model.
5. The interface display method of claim 3, wherein the parameter in the handle indicating the type of the interface model is a modality identification parameter, the interface display method further comprising:
determining modal identification parameters transmitted into the interface display interface;
if the modal identification parameter is a preset first numerical value, determining that the interface output based on the interface display interface is a modal interface;
and if the modal identification parameter is a preset second numerical value, determining that the interface output based on the interface display interface is a non-modal interface.
6. The interface display method according to claim 3, wherein handles corresponding to the at least one interface model are stored in a predetermined database.
7. An interface display device, comprising:
a loading unit for loading a diagnostic protocol;
the analysis unit is used for analyzing the diagnostic protocol and judging whether the diagnostic protocol has a preset identifier or not;
the mapping unit is used for mapping the identifier to obtain a corresponding interface display interface if the identifier exists, wherein the identifier is used for representing an interface generating action;
and the calling unit is used for calling the interface display interface so as to output the interface configured by the interface display interface.
8. The interface display apparatus of claim 7, further comprising:
the interface management system comprises a setting unit, a processing unit and a display unit, wherein the setting unit is used for setting at least one interface model based on the function and appearance layout of an interface required by a user, and the function and/or appearance layout corresponding to different interface models is different;
a configuration unit, configured to configure the diagnostic protocol according to the at least one interface model, so that each identifier in the diagnostic protocol corresponds to one interface model.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of any of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011568186.2A CN112711247B (en) | 2020-12-25 | 2020-12-25 | Interface display method, interface display device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011568186.2A CN112711247B (en) | 2020-12-25 | 2020-12-25 | Interface display method, interface display device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112711247A true CN112711247A (en) | 2021-04-27 |
| CN112711247B CN112711247B (en) | 2022-09-20 |
Family
ID=75545411
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011568186.2A Active CN112711247B (en) | 2020-12-25 | 2020-12-25 | Interface display method, interface display device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112711247B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5737711A (en) * | 1994-11-09 | 1998-04-07 | Fuji Jukogyo Kabuishiki Kaisha | Diagnosis system for motor vehicle |
| CN102981501A (en) * | 2012-11-30 | 2013-03-20 | 重庆邮电大学 | Automobile ECU (Electronic Control Unit) fault diagnosis information matching method based on XML (Extensive Makeup Language) |
| CN103197930A (en) * | 2013-03-27 | 2013-07-10 | 北京经纬恒润科技有限公司 | Method for generating automobile diagnostic software automatically |
| CN105302113A (en) * | 2015-10-28 | 2016-02-03 | 武汉锐科控制系统有限公司 | Configurable and extensible automobile diagnosis system and diagnosis method |
| CN107135210A (en) * | 2017-04-25 | 2017-09-05 | 广西金奔腾汽车科技有限公司 | A kind of simulative automobile communications protocol resolver and its analytic method |
| CN109213132A (en) * | 2018-11-26 | 2019-01-15 | 重庆长安汽车股份有限公司 | A kind of method, device and equipment that UDS diagnostic interface software generates |
| CN109800040A (en) * | 2018-12-21 | 2019-05-24 | 深圳市元征科技股份有限公司 | A kind of diagnostic program interface display method, device and vehicle diagnostic equipment |
| CN110018681A (en) * | 2019-04-23 | 2019-07-16 | 浙江合众新能源汽车有限公司 | Modular UDS diagnosis service configuration method |
| CN110223415A (en) * | 2019-05-20 | 2019-09-10 | 上海星融汽车科技有限公司 | Diagnostic method and its system based on the identification of vehicle electrically controlling module software information |
| CN110597239A (en) * | 2019-10-22 | 2019-12-20 | 上海星融汽车科技有限公司 | Diagnosis method for displaying vehicle diagnosis function nodes on same interface |
-
2020
- 2020-12-25 CN CN202011568186.2A patent/CN112711247B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5737711A (en) * | 1994-11-09 | 1998-04-07 | Fuji Jukogyo Kabuishiki Kaisha | Diagnosis system for motor vehicle |
| CN102981501A (en) * | 2012-11-30 | 2013-03-20 | 重庆邮电大学 | Automobile ECU (Electronic Control Unit) fault diagnosis information matching method based on XML (Extensive Makeup Language) |
| CN103197930A (en) * | 2013-03-27 | 2013-07-10 | 北京经纬恒润科技有限公司 | Method for generating automobile diagnostic software automatically |
| CN105302113A (en) * | 2015-10-28 | 2016-02-03 | 武汉锐科控制系统有限公司 | Configurable and extensible automobile diagnosis system and diagnosis method |
| CN107135210A (en) * | 2017-04-25 | 2017-09-05 | 广西金奔腾汽车科技有限公司 | A kind of simulative automobile communications protocol resolver and its analytic method |
| CN109213132A (en) * | 2018-11-26 | 2019-01-15 | 重庆长安汽车股份有限公司 | A kind of method, device and equipment that UDS diagnostic interface software generates |
| CN109800040A (en) * | 2018-12-21 | 2019-05-24 | 深圳市元征科技股份有限公司 | A kind of diagnostic program interface display method, device and vehicle diagnostic equipment |
| CN110018681A (en) * | 2019-04-23 | 2019-07-16 | 浙江合众新能源汽车有限公司 | Modular UDS diagnosis service configuration method |
| CN110223415A (en) * | 2019-05-20 | 2019-09-10 | 上海星融汽车科技有限公司 | Diagnostic method and its system based on the identification of vehicle electrically controlling module software information |
| CN110597239A (en) * | 2019-10-22 | 2019-12-20 | 上海星融汽车科技有限公司 | Diagnosis method for displaying vehicle diagnosis function nodes on same interface |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112711247B (en) | 2022-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3301575B1 (en) | Using an element in a first model to call a portion of a second model | |
| AU2018310287A1 (en) | Smart contract processing method and apparatus | |
| CN109491671B (en) | Diagnostic software downloading method and device, terminal equipment and storage medium | |
| CN113065656A (en) | Rule engine configuration method and device, server and readable storage medium | |
| CN109558507A (en) | Threedimensional model rendering method and system | |
| CN111143087A (en) | Interface calling method and device, storage medium and server | |
| CN111552267B (en) | Vehicle diagnosis method and device and vehicle diagnosis equipment | |
| CN111813095A (en) | Vehicle diagnosis method, device and medium | |
| CN111694572A (en) | Code format conversion method, device, computer equipment and storage medium | |
| US11392353B2 (en) | Method for generating source code using service-based communication | |
| CN112729868A (en) | Vehicle diagnosis method, device, equipment and medium | |
| CN114780326B (en) | Cross-platform calibration test method, device and equipment | |
| CN111291443B (en) | Automatic generation method, device and equipment for I/O module model of vehicle control unit software | |
| CN114895935A (en) | Method and device for flashing vehicle ECU, electronic equipment and storage medium | |
| CN117077599B (en) | Method and device for generating field programmable gate array view | |
| CN112711247B (en) | Interface display method, interface display device and electronic equipment | |
| CN116107669A (en) | Operator registration method, device and equipment of deep learning framework and storage medium | |
| CN111324787A (en) | Block chain data display method and device in block chain browser | |
| CN112764729B (en) | Application software development method, device, computer equipment and readable storage medium | |
| CN115599401A (en) | Publishing method, device, equipment and medium of user-defined model | |
| CN113935847A (en) | Online process risk processing method, device, server and medium | |
| CN113626022A (en) | Object model creating method and device, storage medium and electronic equipment | |
| CN111240972A (en) | Model verification device based on source code | |
| CN111258628A (en) | Rule file comparison method and device, readable storage medium and terminal equipment | |
| CN111401020A (en) | Interface loading method and system and computing equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |