CN113452793A - Diagnostic service processing method and device, vehicle-mounted terminal and medium - Google Patents
Diagnostic service processing method and device, vehicle-mounted terminal and medium Download PDFInfo
- Publication number
- CN113452793A CN113452793A CN202110737131.8A CN202110737131A CN113452793A CN 113452793 A CN113452793 A CN 113452793A CN 202110737131 A CN202110737131 A CN 202110737131A CN 113452793 A CN113452793 A CN 113452793A
- Authority
- CN
- China
- Prior art keywords
- service
- diagnosis
- diagnostic
- target
- state
- 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.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
Abstract
The application discloses a diagnostic service processing method, a diagnostic service processing device, diagnostic service processing equipment and a diagnostic service processing medium, which are applied to the technical field of automobiles and used for solving the problems of higher complexity of service state acquisition and lower efficiency of service state change processing in the prior art. The method specifically comprises the following steps: the user subscribes the diagnosis state of the target diagnosis service to the diagnosis service center by calling the diagnosis service subscription API and inputting the service identifier and the state change processing mode of the target diagnosis service, and when the diagnosis service center detects that the diagnosis state of the target diagnosis service changes, the diagnosis service center pushes the current diagnosis state of the target diagnosis service to the user, so that the service state acquisition operation is simplified, the complexity of acquiring the service state is reduced, the convenience of acquiring the service state is improved, and the efficiency of service state change processing can be improved by executing the corresponding processing operation by the diagnosis client side by adopting the state change processing mode of the target diagnosis service.
Description
Technical Field
The present application relates to the field of automotive technologies, and in particular, to a diagnostic service processing method and apparatus, a vehicle-mounted terminal, and a medium.
Background
A Universal Diagnostic Services (UDS) is essentially a collection of Services, including 26 Diagnostic Services, and can be divided into six categories, i.e., Diagnostic and communication management, data transmission, storage data transmission, input/output control, routines, and upload/download.
In the automobile diagnosis process, a user generally needs to know the service states of some diagnosis services and perform different processing according to different service states, however, the current service state obtaining method is complex, and the efficiency of the user in processing the service state change is low.
Disclosure of Invention
The embodiment of the application provides a diagnostic service processing method, a diagnostic service processing device, a vehicle-mounted terminal and a medium, which are used for solving the problems of high service state acquisition complexity and low service state change processing efficiency in the prior art.
The technical scheme provided by the embodiment of the application is as follows:
on one hand, the embodiment of the application provides a diagnostic service processing method, which is applied to a diagnostic client in a vehicle-mounted terminal and comprises the following steps:
acquiring a service identifier and a state change processing mode of a target diagnosis service input by calling a diagnosis service subscription Application Program Interface (API);
sending a diagnosis service subscription request to a diagnosis service center based on a service identifier of a target diagnosis service, so that when the diagnosis service center detects that the diagnosis state of the target diagnosis service changes, the current diagnosis state of the target diagnosis service is pushed to a diagnosis client;
and receiving the current diagnosis state of the target diagnosis service pushed by the diagnosis service center, and executing corresponding processing operation by adopting a state change processing mode of the target diagnosis service when determining that the diagnosis state of the target diagnosis service changes based on the current diagnosis state of the target diagnosis service.
In one possible implementation, acquiring the service identifier and the state change handling mode of the target diagnostic service input by calling the diagnostic service subscription API includes:
displaying a command window in response to a call operation performed with respect to the diagnostic service subscription API;
based on the user operation executed in the command window, the service identifier and the state change processing mode of the target diagnosis service are acquired.
In a possible implementation manner, the acquiring a service identifier and a state change processing manner of a target diagnosis service based on a user operation executed in a command window includes:
acquiring a service identifier and a state change processing mode input in a command input box in a command window as a service identifier and a state change processing mode of a target diagnosis service; and/or the presence of a gas in the gas,
and acquiring the service identifier and the state change processing mode selected in the command selection frame in the command window as the service identifier and the state change processing mode of the target diagnosis service.
In a possible implementation manner, after obtaining the service identifier and the state change handling manner of the target diagnostic service input by calling the diagnostic service subscription API, the method further includes:
and performing associated storage on the service identifier and the state change processing mode of the target diagnosis service.
In a possible implementation manner, when the diagnostic service subscription request is sent to the diagnostic service center based on the service identifier of the target diagnostic service, the method further includes:
and acquiring a user identifier, carrying the user identifier in a diagnostic service subscription request, and sending the user identifier to a diagnostic service center.
On the other hand, an embodiment of the present application provides another diagnostic service processing method, which is applied to a diagnostic service center in a vehicle-mounted terminal, and includes:
receiving a diagnosis service subscription request sent by a diagnosis client; the diagnostic service subscription request is sent based on the service identifier of the target diagnostic service after the diagnostic client acquires the service identifier and the state change processing mode of the target diagnostic service input by calling the diagnostic service subscription API;
analyzing the subscription request of the diagnosis service to obtain a service identifier, and detecting whether the diagnosis state of the target diagnosis service corresponding to the service identifier changes;
when the change of the diagnosis state of the target diagnosis service is detected, the current diagnosis state of the target diagnosis service is pushed to the diagnosis client side, so that the diagnosis client side executes corresponding processing operation by adopting a state change processing mode of the target diagnosis service when determining that the diagnosis state of the target diagnosis service changes based on the current diagnosis state of the target diagnosis service.
In one possible embodiment, the diagnostic service subscription request also carries a user identification.
In a possible implementation manner, the diagnostic service processing method provided in the embodiment of the present application further includes:
and storing the service identification and the user identification in an associated manner.
In a possible implementation manner, detecting whether a diagnosis state of a target diagnosis service corresponding to a service identifier changes includes:
acquiring the current diagnosis state of the target diagnosis service from a diagnosis server corresponding to the service identifier;
determining whether the diagnostic state of the target diagnostic service has changed based on whether the current diagnostic state of the target diagnostic service is the same as the saved diagnostic state.
In one possible embodiment, pushing the current diagnostic status of the target diagnostic service to the diagnostic client includes:
and pushing the current diagnosis state of the target diagnosis service to a diagnosis client corresponding to the user identification.
On the other hand, an embodiment of the present application provides a diagnostic service processing apparatus, which is applied to a diagnostic client in a vehicle-mounted terminal, and includes:
the data acquisition unit is used for acquiring a service identifier and a state change processing mode of the target diagnosis service input by calling a diagnosis service subscription API;
the request sending unit is used for sending a diagnosis service subscription request to the diagnosis service center based on the service identifier of the target diagnosis service so as to enable the diagnosis service center to push the current diagnosis state of the target diagnosis service to the diagnosis client when monitoring that the diagnosis state of the target diagnosis service changes;
the state receiving unit is used for receiving the current diagnosis state of the target diagnosis service pushed by the diagnosis service center;
and the change processing unit is used for executing corresponding processing operation by adopting a state change processing mode of the target diagnosis service when determining that the diagnosis state of the target diagnosis service changes based on the current diagnosis state of the target diagnosis service.
In a possible implementation manner, when acquiring the service identifier and the state change processing manner of the target diagnostic service input by calling the diagnostic service subscription API, the data acquiring unit is specifically configured to:
displaying a command window in response to a call operation performed with respect to the diagnostic service subscription API;
based on the user operation executed in the command window, the service identifier and the state change processing mode of the target diagnosis service are acquired.
In a possible embodiment, when the service identifier and the state change handling manner of the target diagnostic service are acquired based on a user operation executed in the command window, the data acquisition unit is specifically configured to:
acquiring a service identifier and a state change processing mode input in a command input box in a command window as a service identifier and a state change processing mode of a target diagnosis service; and/or the presence of a gas in the gas,
and acquiring the service identifier and the state change processing mode selected in the command selection frame in the command window as the service identifier and the state change processing mode of the target diagnosis service.
In a possible implementation manner, the diagnostic service processing apparatus provided in an embodiment of the present application further includes:
and the association storage unit is used for associating and storing the service identifier and the state change processing mode of the target diagnosis service after the data acquisition unit acquires the service identifier and the state change processing mode of the target diagnosis service input by calling the diagnosis service subscription API.
In a possible implementation manner, when sending the diagnostic service subscription request to the diagnostic service center based on the service identifier of the target diagnostic service, the request sending unit is further configured to:
and acquiring a user identifier, carrying the user identifier in a diagnostic service subscription request, and sending the user identifier to a diagnostic service center.
On the other hand, an embodiment of the present application provides another diagnostic service processing apparatus, which is applied to a diagnostic service center in a vehicle-mounted terminal, and includes:
the request receiving unit is used for receiving a diagnosis service subscription request sent by a diagnosis client; the diagnostic service subscription request is sent based on the service identifier of the target diagnostic service after the diagnostic client acquires the service identifier and the state change processing mode of the target diagnostic service input by calling the diagnostic service subscription API;
the state detection unit is used for analyzing the diagnostic service subscription request to obtain a service identifier and detecting whether the diagnostic state of the target diagnostic service corresponding to the service identifier changes;
and the state pushing unit is used for pushing the current diagnosis state of the target diagnosis service to the diagnosis client when the state detection unit detects that the diagnosis state of the target diagnosis service changes, so that the diagnosis client executes corresponding processing operation by adopting a state change processing mode of the target diagnosis service when determining that the diagnosis state of the target diagnosis service changes based on the current diagnosis state of the target diagnosis service.
In one possible embodiment, the diagnostic service subscription request also carries a user identification.
In a possible implementation manner, the diagnostic service processing apparatus provided in an embodiment of the present application further includes:
and the association storage unit is used for associating and storing the service identifier and the user identifier.
In a possible implementation manner, when detecting whether a diagnosis state of a target diagnosis service corresponding to a service identifier changes, the state detection unit is specifically configured to:
acquiring the current diagnosis state of the target diagnosis service from a diagnosis server corresponding to the service identifier;
determining whether the diagnostic state of the target diagnostic service has changed based on whether the current diagnostic state of the target diagnostic service is the same as the saved diagnostic state.
In a possible implementation manner, when pushing the current diagnosis state of the target diagnosis service to the diagnosis client, the state pushing unit is specifically configured to:
and pushing the current diagnosis state of the target diagnosis service to a diagnosis client corresponding to the user identification.
On the other hand, an embodiment of the present application provides a vehicle-mounted terminal, including: the device comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the computer program to realize the diagnostic service processing method provided by the embodiment of the application.
On the other hand, the embodiment of the present application further provides a computer-readable storage medium, where computer instructions are stored, and when the computer instructions are executed by a processor, the diagnostic service processing method provided in the embodiment of the present application is implemented.
The beneficial effects of the embodiment of the application are as follows:
in the embodiment of the application, a user can subscribe the diagnosis state of the target diagnosis service to the diagnosis service center by calling the diagnosis service subscription API and inputting the service identifier and the state change processing mode of the target diagnosis service, and when the diagnosis service center detects that the diagnosis state of the target diagnosis service changes, the diagnosis service center pushes the current diagnosis state of the target diagnosis service to the user, so that the service state acquisition operation is simplified, the complexity of acquiring the service state is reduced, the convenience of acquiring the service state is improved, and the diagnosis client executes corresponding processing operation by adopting the state change processing mode of the target diagnosis service, so that the efficiency of service state change processing can be improved.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1a is a schematic diagram of a command window including a command input box according to an embodiment of the present application;
FIG. 1b is a diagram of a command window including a command selection box according to an embodiment of the present application;
FIG. 1c is a schematic diagram of a command window including a command input box and a command selection box according to an embodiment of the present application;
FIG. 2a is a schematic diagram of an internal communication connection of a vehicle-mounted terminal in an embodiment of the present application;
FIG. 2b is a schematic interactive flow chart of a diagnostic service processing method according to an embodiment of the present application;
FIG. 3 is a flowchart illustrating an embodiment of a diagnostic service processing method;
FIG. 4 is a functional block diagram of a diagnostic service processing apparatus according to an embodiment of the present disclosure;
FIG. 5 is a functional block diagram of another diagnostic service processing apparatus according to an embodiment of the present application;
fig. 6 is a schematic diagram of a hardware structure of the in-vehicle terminal in the embodiment of the present application.
Detailed Description
In order to make the purpose, technical solution and advantages of the present application more clearly and clearly understood, the technical solution in the embodiments of the present application will be described below in detail and completely with reference to the accompanying drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
To facilitate a better understanding of the present application by those skilled in the art, a brief description of the technical terms involved in the present application will be given below.
1. The vehicle-mounted terminal can be installed on an automobile, has the functions of positioning, communication, driving recording, telephone calling, voice broadcasting, audio and video playing, security alarm, remote safe oil cut-off, power-off safety protection and the like, is reserved with a plurality of RS-232 interfaces and RS485 interfaces, and can be externally connected with front-end equipment such as a price calculator, a camera, a microphone, an earphone and the like.
2. The diagnosis client is an application program which can be installed on terminal equipment such as a vehicle-mounted terminal, a computer and a mobile phone, provides diagnosis service for a user and supports user interaction. The present application will be described by taking as an example that the diagnosis client is installed in the vehicle-mounted terminal.
3. And the diagnosis server is a functional module which provides various services such as database service, calculation service and the like for the diagnosis client and is arranged on the vehicle-mounted terminal.
4. And the diagnosis service center is a functional module which is used for providing service state subscription service for the diagnosis client and is arranged on the vehicle-mounted terminal.
5. And the diagnosis service subscription API is an interface which is provided for the diagnosis client side to subscribe the service state of the diagnosis service.
6. And the command window is a window which is displayed to the user by the diagnosis client and used for inputting the service identification and the state change processing mode of the diagnosis service. In this application, at least one of the command input box and the command selection box is displayed on the command window, for example, as shown in fig. 1a, the command window may only include the command input box, as shown in fig. 1b, the command window may only include the command selection box, and as shown in fig. 1c, the command window may also include the command input box and the command selection box.
It should be noted that, the term "and/or" mentioned in the present application describes an association relationship of associated objects, which means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
After introducing the technical terms related to the present application, the following briefly introduces the application scenarios and design ideas of the embodiments of the present application.
At present, when a user needs to know service states of some diagnostic services, a corresponding service state notification scheme needs to be respectively agreed for each diagnostic service, so that complexity of service state acquisition is increased, and after the user knows the service states of the diagnostic services, the user needs to perform different processing according to different service states, so that efficiency of service state change processing is low.
For this purpose, in the embodiment of the present application, as shown in fig. 2a, a diagnosis client 111, a diagnosis service center 112, and a diagnosis server 112 in a vehicle-mounted terminal 110 are in communication connection through a local socket, the diagnosis client 111 provides a diagnosis service subscription API for a user, and the user can implement automatic processing of service state subscription and state change of a target diagnosis service by calling the diagnosis service subscription API and inputting a service identifier and a state change processing mode of the target diagnosis service that the user wants to subscribe to, specifically, the diagnosis client 111 obtains the service identifier and the state change processing mode of the target diagnosis service that are input by calling the diagnosis service subscription API, and sends a diagnosis service subscription request to the diagnosis service center 112 based on the service identifier of the target diagnosis service; when receiving a diagnostic service subscription request sent by the diagnostic client 111, the diagnostic service center 112 analyzes the diagnostic service subscription request to obtain a service identifier, obtains a current diagnostic state of the target diagnostic service from the diagnostic server 113 corresponding to the service identifier, detects whether the diagnostic state of the target diagnostic service changes based on the current diagnostic state of the target diagnostic service, and when detecting that the diagnostic state of the target diagnostic service changes, pushes the current diagnostic state of the target diagnostic service to the diagnostic client 111; when the diagnosis client 111 receives the current diagnosis state of the target diagnosis service pushed by the diagnosis service center 112, after determining that the diagnosis state of the target diagnosis service changes based on the current diagnosis state of the target diagnosis service, the diagnosis client executes corresponding processing operation by adopting a state change processing mode of the target diagnosis service.
Therefore, a user can subscribe the diagnosis state of the target diagnosis service to the diagnosis service center by calling the diagnosis service subscription API and inputting the service identifier and the state change processing mode of the target diagnosis service, and when the diagnosis service center detects that the diagnosis state of the target diagnosis service changes, the diagnosis service center pushes the current diagnosis state of the target diagnosis service to the user, so that the service state acquisition operation is simplified, the complexity of acquiring the service state is reduced, the convenience of acquiring the service state is improved, and the diagnosis client executes corresponding processing operation by adopting the state change processing mode of the target diagnosis service, so that the efficiency of service state change processing can be improved.
After introducing the application scenario and the design concept of the embodiment of the present application, the following describes in detail the technical solution provided by the embodiment of the present application.
Referring to fig. 2b, an interactive flow of the diagnostic service processing method provided in the embodiment of the present application is as follows:
step 201: the diagnosis client 111 acquires the service identification and the state change processing manner of the target diagnosis service input by calling the diagnosis service subscription API.
In practical applications, the diagnosis client 111 provides a diagnosis service subscription API for the user, and the user can input the service identifier and the state change processing mode of the target diagnosis service by calling the diagnosis service subscription API. Specifically, when monitoring that the user performs a call operation on the diagnostic service subscription API, the diagnostic client 111 displays a command window in response to the call operation performed on the diagnostic service subscription API, and obtains a service identifier and a state change processing mode of the target diagnostic service based on the user operation performed in the command window.
For example: assuming that the command window is a command window only including a command input box as shown in fig. 1a, when monitoring that a user performs a call operation on a diagnostic service subscription API, the diagnostic client 111 displays the command window as shown in fig. 1a in response to the call operation performed on the diagnostic service subscription API, and acquires a service identifier and a state change processing mode input in the command input box in the command window as a service identifier and a state change processing mode of a target diagnostic service.
For another example: assuming that the command window is a command window only including a command selection box as shown in fig. 1b, when monitoring that a user performs a call operation on a diagnostic service subscription API, the diagnostic client 111 displays the command window as shown in fig. 1b in response to the call operation performed on the diagnostic service subscription API, and acquires a service identifier and a state change processing mode selected in the command selection box in the command window as a service identifier and a state change processing mode of a target diagnostic service.
The following steps are repeated: assuming that the command window is a command window including a command input selection box and a command selection box as shown in fig. 1c, when monitoring a call operation performed by a user for a diagnostic service subscription API, the diagnostic client 111 displays the command window as shown in fig. 1c in response to the call operation performed for the diagnostic service subscription API, and acquires a service identifier and a state change processing manner input in the command input box in the command window and a service identifier and a state change processing manner selected in the command selection box in the command window as service identifiers and state change processing manners of the target diagnostic service.
Step 202: the diagnostic client 111 sends a diagnostic service subscription request to the diagnostic service center 112 based on the service identification of the target diagnostic service.
In practical application, in order to facilitate subsequent execution of corresponding processing operations on the target diagnostic service, after the diagnostic client 111 obtains the service identifier and the state change processing manner of the target diagnostic service, the service identifier and the state change processing manner of the target diagnostic service may be stored in an associated manner.
In this embodiment, in order to facilitate the diagnostic service center 112 to push the current diagnostic state of the target diagnostic service to the corresponding diagnostic client 111, after the diagnostic client 111 obtains the service identifier and the state change processing mode of the target diagnostic service, the diagnostic client 111 may further obtain the user identifier, and send the user identifier and the service identifier of the target diagnostic service to the diagnostic service center 112 through the local socket in the diagnostic service subscription request.
Step 203: after receiving the diagnostic service subscription request sent by the diagnostic client 111, the diagnostic service center 112 analyzes the diagnostic service subscription request to obtain a service identifier, and detects whether the diagnostic state of the target diagnostic service corresponding to the service identifier changes.
In practical application, the diagnostic service center 112 receives the diagnostic service subscription request sent by the diagnostic client 111, analyzes the diagnostic service subscription request, and after obtaining the service identifier and the user identifier, may further perform associated storage on the service identifier and the user identifier.
Further, the diagnosis service center 112 may obtain the current diagnosis state of the target diagnosis service from the diagnosis server 113 corresponding to the service identifier, and determine whether the diagnosis state of the target diagnosis service changes based on whether the current diagnosis state of the target diagnosis service is the same as the saved diagnosis state.
In specific implementation, when the diagnosis service center 112 obtains the current diagnosis state of the target diagnosis service from the diagnosis server 113 corresponding to the service identifier, the following manners may be adopted, but are not limited to:
the first mode is as follows: an active acquisition mode. Specifically, the diagnostic service center 112 may periodically send a status acquisition request to the diagnostic server 113 corresponding to the service identifier through a local socket; when receiving the state acquisition request sent by the diagnostic service center 112, the diagnostic server 113 carries the current diagnostic state of the target diagnostic service in a state acquisition response and returns the state acquisition response to the diagnostic service center 112 through a local socket; after receiving the state acquisition response, the diagnostic service center 112 analyzes the state acquisition response to obtain the current diagnostic state of the target diagnostic service.
The second mode is as follows: passive reception mode. Specifically, the diagnostic server 113 may report the current diagnostic state of the target diagnostic service to the diagnostic service center 112 through the local socket when determining that the diagnostic state of the target diagnostic service changes; the diagnosis service center 112 receives the current diagnosis state of the target diagnosis service reported by the diagnosis server 113.
Further, after acquiring the current diagnostic state of the target diagnostic service from the diagnostic server 113 corresponding to the service identifier, the diagnostic service center 112 may determine that the diagnostic state of the target diagnostic service has not changed when the current diagnostic state of the target diagnostic service is the same as the stored diagnostic state, and determine that the diagnostic state of the target diagnostic service has changed when the current diagnostic state of the target diagnostic service is different from the stored diagnostic state.
Step 204: when detecting that the diagnosis state of the target diagnosis service changes, the diagnosis service center 112 pushes the current diagnosis state of the target diagnosis service to the diagnosis client 111.
In practical applications, when the diagnosis service center 112 detects that the diagnosis state of the target diagnosis service changes, the current diagnosis state of the target diagnosis service may be pushed to the diagnosis client 111 corresponding to the user identifier stored in association with the service identifier of the target diagnosis service through the local socket.
Step 205: after receiving the current diagnostic state of the target diagnostic service pushed by the diagnostic service center 112, the diagnostic client 111 executes a corresponding processing operation in a state change processing mode of the target diagnostic service when determining that the diagnostic state of the target diagnostic service changes based on the current diagnostic state of the target diagnostic service.
In practical applications, after receiving the current diagnostic state of the target diagnostic service pushed by the diagnostic service center 112, the diagnostic client 111 may determine that the diagnostic state of the target diagnostic service has not changed when the current diagnostic state of the target diagnostic service is the same as the stored diagnostic state, and determine that the diagnostic state of the target diagnostic service has changed when the current diagnostic state of the target diagnostic service is different from the stored diagnostic state. Further, after determining that the diagnosis state of the target diagnosis service changes, the diagnosis client 111 may perform corresponding processing operations by using a state change processing manner stored in association with the service identifier of the target diagnosis service.
The following further describes the diagnostic service processing method provided in the embodiment of the present application in detail, with reference to fig. 3, a specific flow of the diagnostic service processing method provided in the embodiment of the present application is as follows:
step 301: when monitoring that the user performs a call operation for the diagnostic service subscription API, the diagnostic client 111 displays a command window in response to the call operation performed for the diagnostic service subscription API.
Step 302: the diagnosis client 111 acquires a service identifier and a state change processing manner of the target diagnosis service based on the user operation executed in the command window.
Step 303: the diagnosis client 111 stores the service identifier and the state change processing mode of the target diagnosis service in association with each other.
Step 304: the diagnosis client 111 obtains the user identifier and generates a diagnosis service subscription request based on the user identifier and the service identifier of the target diagnosis service.
Step 305: the diagnostic client 111 sends the diagnostic service subscription request to the diagnostic service center 112 through a local socket.
Step 306: after receiving the diagnostic service subscription request sent by the diagnostic client 111, the diagnostic service center 112 parses the diagnostic service subscription request to obtain a service identifier and a user identifier, and stores the service identifier and the user identifier in an associated manner.
Step 307: when the diagnosis server 113 determines that the diagnosis state of the target diagnosis service changes, it reports the current diagnosis state of the target diagnosis service to the diagnosis service center 112 through the local socket.
Step 308: when receiving the current diagnostic state of the target diagnostic service reported by the diagnostic server 113, the diagnostic service center 112 detects whether the diagnostic state of the target diagnostic service changes based on whether the current diagnostic state of the target diagnostic service is the same as the stored diagnostic state.
Step 309: when detecting that the diagnostic state of the target diagnostic service changes, the diagnostic service center 112 pushes the current diagnostic state of the target diagnostic service to the diagnostic client 111 through the local socket.
Step 310: after receiving the current diagnostic state of the target diagnostic service pushed by the diagnostic service center 112, the diagnostic client 111 executes a corresponding processing operation by using a state change processing mode stored in association with the service identifier of the target diagnostic service when determining that the diagnostic state of the target diagnostic service changes based on the current diagnostic state of the target diagnostic service.
Based on the foregoing embodiments, an embodiment of the present application provides a diagnostic service processing apparatus, which is applied to the diagnostic client 111 in the vehicle-mounted terminal 110, and referring to fig. 4, the diagnostic service processing apparatus 400 provided in the embodiment of the present application at least includes:
a data obtaining unit 401, configured to obtain a service identifier and a state change processing mode of a target diagnostic service input by calling a diagnostic service subscription API;
a request sending unit 402, configured to send a diagnostic service subscription request to the diagnostic service center 112 based on the service identifier of the target diagnostic service, so that when the diagnostic service center 112 monitors that the diagnostic state of the target diagnostic service changes, the current diagnostic state of the target diagnostic service is pushed to the diagnostic client 111;
a status receiving unit 403, configured to receive a current diagnostic status of the target diagnostic service pushed by the diagnostic service center 112;
and the change processing unit 404 is configured to, when determining that the diagnostic state of the target diagnostic service changes based on the current diagnostic state of the target diagnostic service, execute a corresponding processing operation in a state change processing manner of the target diagnostic service.
In a possible implementation manner, when acquiring the service identifier and the state change processing manner of the target diagnostic service input by calling the diagnostic service subscription API, the data acquisition unit 401 is specifically configured to:
displaying a command window in response to a call operation performed with respect to the diagnostic service subscription API;
based on the user operation executed in the command window, the service identifier and the state change processing mode of the target diagnosis service are acquired.
In a possible implementation manner, when acquiring the service identifier and the state change processing manner of the target diagnostic service based on the user operation executed in the command window, the data acquisition unit 401 is specifically configured to:
acquiring a service identifier and a state change processing mode input in a command input box in a command window as a service identifier and a state change processing mode of a target diagnosis service; and/or the presence of a gas in the gas,
and acquiring the service identifier and the state change processing mode selected in the command selection frame in the command window as the service identifier and the state change processing mode of the target diagnosis service.
In a possible implementation manner, the diagnostic service processing apparatus 400 provided in the embodiment of the present application further includes:
the association storage unit 405 is configured to, after the data obtaining unit 401 obtains the service identifier and the state change processing manner of the target diagnostic service input by calling the diagnostic service subscription API, perform association storage on the service identifier and the state change processing manner of the target diagnostic service.
In a possible implementation manner, when sending the diagnostic service subscription request to the diagnostic service center 112 based on the service identifier of the target diagnostic service, the request sending unit 402 is further configured to:
the user identifier is obtained and carried in the diagnostic service subscription request to be sent to the diagnostic service center 112.
Based on the foregoing embodiment, another diagnostic service processing apparatus is further provided in the embodiment of the present application, and is applied to the diagnostic service center 112 in the vehicle-mounted terminal 110, and referring to fig. 5, the diagnostic service processing apparatus 500 provided in the embodiment of the present application at least includes:
a request receiving unit 501, configured to receive a diagnostic service subscription request sent by the diagnostic client 111; the diagnostic service subscription request is sent based on the service identifier of the target diagnostic service after the diagnostic client 111 obtains the service identifier and the state change processing mode of the target diagnostic service input by calling the diagnostic service subscription API;
a state detection unit 502, configured to analyze the diagnostic service subscription request to obtain a service identifier, and detect whether a diagnostic state of a target diagnostic service corresponding to the service identifier changes;
the state pushing unit 503 is configured to, when the state detecting unit 502 detects that the diagnostic state of the target diagnostic service changes, push the current diagnostic state of the target diagnostic service to the diagnostic client 111, so that the diagnostic client 111 executes a corresponding processing operation in a state change processing manner of the target diagnostic service when determining that the diagnostic state of the target diagnostic service changes based on the current diagnostic state of the target diagnostic service.
In one possible embodiment, the diagnostic service subscription request also carries a user identification.
In a possible implementation manner, the diagnostic service processing apparatus 500 provided in the embodiment of the present application further includes:
an association storage unit 504, configured to store the service identifier and the user identifier in an association manner.
In a possible implementation manner, when detecting whether a diagnosis state of a target diagnosis service corresponding to a service identifier changes, the state detection unit 502 is specifically configured to:
acquiring the current diagnosis state of the target diagnosis service from the diagnosis server 113 corresponding to the service identifier;
determining whether the diagnostic state of the target diagnostic service has changed based on whether the current diagnostic state of the target diagnostic service is the same as the saved diagnostic state.
In a possible implementation manner, when pushing the current diagnosis state of the target diagnosis service to the diagnosis client 111, the state pushing unit 503 is specifically configured to:
and pushing the current diagnosis state of the target diagnosis service to the diagnosis client 111 corresponding to the user identifier.
It should be noted that the principle of solving the technical problem of the two diagnostic service processing apparatuses provided in the embodiment of the present application is similar to that of the diagnostic service processing method provided in the embodiment of the present application, and therefore, the implementation of the two diagnostic service processing apparatuses provided in the embodiment of the present application can refer to the implementation of the diagnostic service processing method provided in the embodiment of the present application, and repeated details are not described again.
After the diagnostic service processing method and apparatus provided in the embodiment of the present application are introduced, a brief description is given to the in-vehicle terminal 110 provided in the embodiment of the present application.
Referring to fig. 6, the vehicle-mounted terminal 110 provided in the embodiment of the present application at least includes: the system comprises a processor 601, a memory 602 and a computer program stored on the memory 602 and capable of running on the processor 601, wherein the processor 601 executes the computer program to realize the diagnostic service processing method provided by the embodiment of the application.
It should be noted that the in-vehicle terminal 110 shown in fig. 6 is only an example, and should not bring any limitation to the functions and the application range of the embodiment of the present application.
Vehicle-mounted terminal 110 provided in the embodiment of the present application may further include a bus 603 connecting different components (including processor 601 and memory 602). Bus 603 represents one or more of any of several types of bus structures, including a memory bus, a peripheral bus, a local bus, and so forth.
The Memory 602 may include readable media in the form of volatile Memory, such as Random Access Memory (RAM) 6021 and/or cache Memory 6022, and may further include Read Only Memory (ROM) 6023.
The memory 602 may also include a program means 6025 having a set (at least one) of program modules 6024, the program modules 6024 including, but not limited to: an operating subsystem, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
In-vehicle terminal 110 may also communicate with one or more external devices 604 (e.g., a keypad, a remote control, etc.), with one or more devices that enable a user to interact with in-vehicle terminal 110 (e.g., a cell phone, a computer, etc.), and/or with any device that enables in-vehicle terminal 110 to communicate with one or more other in-vehicle terminals 110 (e.g., a router, a modem, etc.). Such communication may be through an Input/Output (I/O) interface 605. Furthermore, in-vehicle terminal 110 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public Network such as the internet) via Network adapter 606. As shown in fig. 6, the network adapter 606 communicates with other modules of the in-vehicle terminal 110 through the bus 603. It should be understood that although not shown in FIG. 6, other hardware and/or software modules may be used in conjunction with in-vehicle terminal 110, including but not limited to: microcode, device drivers, Redundant processors, external disk drive Arrays, disk array (RAID) subsystems, tape drives, and data backup storage subsystems, to name a few.
The following describes a computer-readable storage medium provided by embodiments of the present application. The computer-readable storage medium provided by the embodiments of the present application stores computer instructions, and the computer instructions, when executed by the processor, implement the diagnostic service processing method provided by the embodiments of the present application. Specifically, the computer instructions may be built in or installed in the vehicle-mounted terminal 110, so that the vehicle-mounted terminal 110 may implement the diagnostic service processing method provided by the embodiment of the present application by executing the built-in or installed computer instructions.
In addition, the diagnostic service processing method provided by the embodiment of the present application can also be implemented as a program product, which includes program codes for causing the in-vehicle terminal 110 to execute the diagnostic service processing method provided by the embodiment of the present application when the program product can run on the in-vehicle terminal 110.
The program product provided by the embodiments of the present application may be any combination of one or more readable media, where the readable media may be a readable signal medium or a readable storage medium, and the readable storage medium may be, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof, and in particular, more specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a RAM, a ROM, an Erasable Programmable Read-Only Memory (EPROM), an optical fiber, a portable Compact disk Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The program product provided by the embodiment of the application can adopt a CD-ROM and comprises program codes, and can run on a computing device. However, the program product provided by the embodiments of the present application is not limited thereto, and in the embodiments of the present application, the readable storage medium may be any tangible medium that can contain or store a program, which can be used by or in connection with an instruction execution system, apparatus, or device.
It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such division is merely exemplary and not mandatory. Indeed, the features and functions of two or more units described above may be embodied in one unit, according to embodiments of the application. Conversely, the features and functions of one unit described above may be further divided into embodiments by a plurality of units.
Further, while the operations of the methods of the present application are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.
Claims (14)
1. A diagnosis service processing method is applied to a diagnosis client in a vehicle-mounted terminal, and comprises the following steps:
acquiring a service identifier and a state change processing mode of a target diagnosis service input by calling a diagnosis service subscription Application Program Interface (API);
sending a diagnosis service subscription request to a diagnosis service center based on the service identifier of the target diagnosis service, so that when the diagnosis service center detects that the diagnosis state of the target diagnosis service changes, the current diagnosis state of the target diagnosis service is pushed to the diagnosis client;
and receiving the current diagnosis state of the target diagnosis service pushed by the diagnosis service center, and executing corresponding processing operation by adopting a state change processing mode of the target diagnosis service when determining that the diagnosis state of the target diagnosis service changes based on the current diagnosis state of the target diagnosis service.
2. The diagnostic service processing method of claim 1, wherein obtaining the service identifier and the state change handling manner of the target diagnostic service input by calling a diagnostic service subscription API, comprises:
displaying a command window in response to a call operation performed with respect to the diagnostic service subscription API;
and acquiring the service identifier and the state change processing mode of the target diagnosis service based on the user operation executed in the command window.
3. The diagnostic service processing method of claim 2, wherein obtaining the service identifier and the state change processing mode of the target diagnostic service based on the user operation performed in the command window comprises:
acquiring a service identifier and a state change processing mode input in a command input box in the command window as a service identifier and a state change processing mode of the target diagnosis service; and/or the presence of a gas in the gas,
and acquiring the service identifier and the state change processing mode selected in the command selection frame in the command window as the service identifier and the state change processing mode of the target diagnosis service.
4. The diagnostic service processing method of any one of claims 1 to 3, further comprising, after acquiring the service identification and the state change handling manner of the target diagnostic service input by calling a diagnostic service subscription API,:
and performing associated storage on the service identifier and the state change processing mode of the target diagnosis service.
5. The diagnostic service processing method of any one of claims 1 to 3, wherein when sending a diagnostic service subscription request to a diagnostic service center based on the service identification of the target diagnostic service, further comprising:
and acquiring a user identifier, carrying the user identifier in the diagnostic service subscription request, and sending the user identifier to the diagnostic service center.
6. A diagnosis service processing method is characterized in that the diagnosis service processing method is applied to a diagnosis service center in a vehicle-mounted terminal and comprises the following steps:
receiving a diagnosis service subscription request sent by a diagnosis client; the diagnostic service subscription request is sent based on the service identifier of the target diagnostic service after the diagnostic client acquires the service identifier and the state change processing mode of the target diagnostic service input by calling a diagnostic service subscription Application Program Interface (API);
analyzing the diagnosis service subscription request to obtain the service identification, and detecting whether the diagnosis state of the target diagnosis service corresponding to the service identification changes;
and when the change of the diagnosis state of the target diagnosis service is detected, pushing the current diagnosis state of the target diagnosis service to the diagnosis client, so that the diagnosis client executes corresponding processing operation by adopting a state change processing mode of the target diagnosis service when determining that the diagnosis state of the target diagnosis service changes based on the current diagnosis state of the target diagnosis service.
7. The diagnostic service processing method as claimed in claim 6, wherein the diagnostic service subscription request further carries a user identification.
8. The diagnostic service processing method as set forth in claim 7, further comprising:
and storing the service identification and the user identification in an associated manner.
9. The diagnostic service processing method of any one of claims 6 to 8, wherein detecting whether a diagnostic state of the target diagnostic service corresponding to the service identifier changes comprises:
acquiring the current diagnosis state of the target diagnosis service from a diagnosis server corresponding to the service identifier;
determining whether the diagnostic state of the target diagnostic service has changed based on whether the current diagnostic state of the target diagnostic service is the same as the saved diagnostic state.
10. The diagnostic service processing method of claim 7 or 8, wherein pushing the current diagnostic state of the target diagnostic service to the diagnostic client comprises:
and pushing the current diagnosis state of the target diagnosis service to the diagnosis client corresponding to the user identification.
11. A diagnosis service processing apparatus applied to a diagnosis client in a vehicle-mounted terminal, comprising:
the data acquisition unit is used for acquiring a service identifier and a state change processing mode of the target diagnosis service input by calling a diagnosis service subscription Application Program Interface (API);
a request sending unit, configured to send a diagnostic service subscription request to a diagnostic service center based on the service identifier of the target diagnostic service, so that when the diagnostic service center detects that a diagnostic state of the target diagnostic service changes, the diagnostic service center pushes a current diagnostic state of the target diagnostic service to the diagnostic client;
the state receiving unit is used for receiving the current diagnosis state of the target diagnosis service pushed by the diagnosis service center;
and the change processing unit is used for executing corresponding processing operation by adopting a state change processing mode of the target diagnosis service when determining that the diagnosis state of the target diagnosis service changes based on the current diagnosis state of the target diagnosis service.
12. A diagnosis service processing apparatus applied to a diagnosis service center in a vehicle-mounted terminal, comprising:
the request receiving unit is used for receiving a diagnosis service subscription request sent by a diagnosis client; the diagnostic service subscription request is sent based on the service identifier of the target diagnostic service after the diagnostic client acquires the service identifier and the state change processing mode of the target diagnostic service input by calling a diagnostic service subscription Application Program Interface (API);
the state detection unit is used for analyzing the diagnostic service subscription request to obtain the service identifier and detecting whether the diagnostic state of the target diagnostic service corresponding to the service identifier changes;
and the state pushing unit is used for pushing the current diagnosis state of the target diagnosis service to the diagnosis client when the state detection unit detects that the diagnosis state of the target diagnosis service changes, so that the diagnosis client executes corresponding processing operation by adopting a state change processing mode of the target diagnosis service when determining that the diagnosis state of the target diagnosis service changes based on the current diagnosis state of the target diagnosis service.
13. A vehicle-mounted terminal characterized by comprising: memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the diagnostic service processing method according to any one of claims 1 to 10 when executing the computer program.
14. A computer-readable storage medium storing computer instructions which, when executed by a processor, implement the diagnostic service processing method of any one of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110737131.8A CN113452793A (en) | 2021-06-30 | 2021-06-30 | Diagnostic service processing method and device, vehicle-mounted terminal and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110737131.8A CN113452793A (en) | 2021-06-30 | 2021-06-30 | Diagnostic service processing method and device, vehicle-mounted terminal and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113452793A true CN113452793A (en) | 2021-09-28 |
Family
ID=77814356
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110737131.8A Pending CN113452793A (en) | 2021-06-30 | 2021-06-30 | Diagnostic service processing method and device, vehicle-mounted terminal and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113452793A (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2472854A1 (en) * | 2003-07-07 | 2005-01-07 | Snap-On Technologies, Inc. | Distributed expert diagnostic service and system |
| CN101026808A (en) * | 2006-02-21 | 2007-08-29 | 华为技术有限公司 | Media transmission request quene state notice method and system |
| CN102402218A (en) * | 2011-11-10 | 2012-04-04 | 浙江工业大学 | Intelligent industrial network monitoring system |
| CN103404113A (en) * | 2013-01-18 | 2013-11-20 | 华为技术有限公司 | Notice pushing method, device and system |
| CN104484735A (en) * | 2014-11-20 | 2015-04-01 | 上海富欣智能交通控制有限公司 | Rail transportation comprehensive maintenance management information publishing system |
| CN106412050A (en) * | 2016-09-26 | 2017-02-15 | 美的智慧家居科技有限公司 | Device, client and server in internet of things, and communication methods thereof |
| CN106407066A (en) * | 2016-09-26 | 2017-02-15 | 北京经纬恒润科技有限公司 | An end of line detection method and system for electronic products |
| CN106647304A (en) * | 2016-12-26 | 2017-05-10 | 美的智慧家居科技有限公司 | Household electrical appliance linkage control method, household electrical appliance, server, and system |
| CN108141727A (en) * | 2015-08-03 | 2018-06-08 | 康维达无线有限责任公司 | The mobile core network service exposure of user equipment |
| CN109460353A (en) * | 2018-09-30 | 2019-03-12 | 惠州市德赛西威汽车电子股份有限公司 | UDS auto-check system |
| CN109720348A (en) * | 2017-10-26 | 2019-05-07 | 丰田自动车株式会社 | Car-mounted device, information processing system and information processing method |
| CN109905476A (en) * | 2012-09-22 | 2019-06-18 | 谷歌有限责任公司 | The subscription informing mechanism of synchronization for distributions |
| CN111475263A (en) * | 2020-04-10 | 2020-07-31 | 上海移为通信技术股份有限公司 | Event processing method, device and storage medium |
| CN111614524A (en) * | 2019-02-26 | 2020-09-01 | 华为技术有限公司 | Multi-intelligent-device linkage control method, device and system |
| US10970150B1 (en) * | 2019-12-23 | 2021-04-06 | Atlassian Pty Ltd. | Incident detection and management |
-
2021
- 2021-06-30 CN CN202110737131.8A patent/CN113452793A/en active Pending
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050021294A1 (en) * | 2003-07-07 | 2005-01-27 | Trsar Dale A. | Distributed expert diagnostic service and system |
| CA2472854A1 (en) * | 2003-07-07 | 2005-01-07 | Snap-On Technologies, Inc. | Distributed expert diagnostic service and system |
| CN101026808A (en) * | 2006-02-21 | 2007-08-29 | 华为技术有限公司 | Media transmission request quene state notice method and system |
| CN102402218A (en) * | 2011-11-10 | 2012-04-04 | 浙江工业大学 | Intelligent industrial network monitoring system |
| CN109905476A (en) * | 2012-09-22 | 2019-06-18 | 谷歌有限责任公司 | The subscription informing mechanism of synchronization for distributions |
| CN103404113A (en) * | 2013-01-18 | 2013-11-20 | 华为技术有限公司 | Notice pushing method, device and system |
| CN104484735A (en) * | 2014-11-20 | 2015-04-01 | 上海富欣智能交通控制有限公司 | Rail transportation comprehensive maintenance management information publishing system |
| CN108141727A (en) * | 2015-08-03 | 2018-06-08 | 康维达无线有限责任公司 | The mobile core network service exposure of user equipment |
| CN106412050A (en) * | 2016-09-26 | 2017-02-15 | 美的智慧家居科技有限公司 | Device, client and server in internet of things, and communication methods thereof |
| CN106407066A (en) * | 2016-09-26 | 2017-02-15 | 北京经纬恒润科技有限公司 | An end of line detection method and system for electronic products |
| CN106647304A (en) * | 2016-12-26 | 2017-05-10 | 美的智慧家居科技有限公司 | Household electrical appliance linkage control method, household electrical appliance, server, and system |
| CN109720348A (en) * | 2017-10-26 | 2019-05-07 | 丰田自动车株式会社 | Car-mounted device, information processing system and information processing method |
| CN109460353A (en) * | 2018-09-30 | 2019-03-12 | 惠州市德赛西威汽车电子股份有限公司 | UDS auto-check system |
| CN111614524A (en) * | 2019-02-26 | 2020-09-01 | 华为技术有限公司 | Multi-intelligent-device linkage control method, device and system |
| US10970150B1 (en) * | 2019-12-23 | 2021-04-06 | Atlassian Pty Ltd. | Incident detection and management |
| CN111475263A (en) * | 2020-04-10 | 2020-07-31 | 上海移为通信技术股份有限公司 | Event processing method, device and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 荆伟: "基于车载以太网的音响诊断技术开发", 《中国优秀硕士论文全文数据库》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109446309B (en) | Question feedback method and device | |
| CN107273280A (en) | A kind of log processing method, device, electronic equipment and storage medium | |
| CN111198859B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN111597065B (en) | Method and device for collecting equipment information | |
| CN112181696B (en) | Abnormality information processing method, apparatus, and storage medium | |
| CN110881224B (en) | Network long connection method, device, equipment and storage medium | |
| CN113377590A (en) | Fault diagnosis method and device, vehicle-mounted terminal and medium | |
| CN111475230B (en) | Application function configuration method and device and electronic equipment | |
| CN110275701B (en) | Data processing method, device, medium and computing equipment | |
| CN113220342A (en) | Centralized configuration method and device, electronic equipment and storage medium | |
| CN113452793A (en) | Diagnostic service processing method and device, vehicle-mounted terminal and medium | |
| CN109388917B (en) | Hardware equipment authentication method, device, equipment and storage medium | |
| CN115515026A (en) | Ammeter data transmission system, method, device, equipment and medium | |
| CN115622963A (en) | Message detection method, device, equipment and medium based on industrial switch | |
| CN111198853A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN111274104B (en) | Data processing method, device, electronic equipment and computer readable storage medium | |
| CN113849356A (en) | Equipment testing method and device, electronic equipment and storage medium | |
| CN113986995A (en) | Request distribution method and device, storage medium and electronic equipment | |
| CN110996374B (en) | Wireless network control method, device, equipment and medium | |
| CN112416698A (en) | Monitoring system expansion method and device, storage medium and electronic equipment | |
| CN113377589A (en) | Fault diagnosis method and device, vehicle-mounted terminal and medium | |
| CN110602162B (en) | Terminal evidence obtaining method, device, equipment and storage medium | |
| CN113676547B (en) | Data processing method, data processing device, storage medium and electronic equipment | |
| CN113542103B (en) | Method and device for monitoring invitations of accounts in social communication group and mobile terminal | |
| CN111371586A (en) | Log data transmission method, device and 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 |