Automobile diagnosis service method and system based on modular uds protocol

Abstract

This disclosure provides a method and system for automotive diagnostic services based on a modular UDS protocol, relating to the field of automotive UDS development technology, including a host computer, PCAN, and an electronic control unit (ECU). The ECU includes a network layer and a session layer. The host computer sends diagnostic messages to the ECU via PCAN. After receiving the diagnostic message from the host computer, the ECU distinguishes the network protocol control information type of the diagnostic message, determines whether the current network state of the network layer allows receiving the diagnostic message frame, and determines whether the addressing mode, session mode, and security level are equal to the ECU's configuration information. If the network layer allows reception, the session layer determines whether the ECU supports the service. After the session layer confirms the response type to be sent, the network layer sends one or more frames according to the protocol type. This disclosure enables rapid iteration when adding or removing UDS services, reducing code modifications.

Description

Technical Field

[0001] This disclosure relates to the field of automotive UDS development technology, specifically to automotive diagnostic service methods and systems based on modular UDS protocols. Background Technology

[0002] The statements in this section are merely background information relating to this disclosure and do not necessarily constitute prior art.

[0003] With the rapid development of the automotive industry, automobiles are no longer simple combinations of mechanical parts. The electronic and electrical functions of automobiles are becoming increasingly complex, such as vehicle networking, smart cockpits, and driver assistance functions. As a result, the manifestations of automobile faults are becoming more complex and diverse. In order to facilitate fault diagnosis of the electronic control units of various functional modules, new energy vehicles have added diagnostic systems based on the UDS protocol. The UDS protocol enables information exchange between the diagnostic host computer and various functional modules, thereby realizing the diagnosis of various functional modules of the automobile.

[0004] Existing methods for modular UDS diagnostics are all developed at the system control level of the host computer, but there are no diagnostic testing methods for the execution level of the lower-level computer. Therefore, when adding or removing UDS services, rapid iteration cannot be achieved. It is necessary to re-edit the program and code, which involves a lot of changes and slows down the efficiency of the entire system. Summary of the Invention

[0005] To address the aforementioned issues, this disclosure proposes a vehicle diagnostic service method and system based on the modular UDS protocol. It clarifies the diagnostic and testing service process of the lower-level machine under the UDS protocol, allowing for rapid addition or reduction of UDS services when needed, thus minimizing code modifications.

[0006] According to some embodiments, the present disclosure adopts the following technical solutions:

[0007] The automotive diagnostic service system based on the modular UDS protocol includes a host computer, PCAN, and an electronic control unit (ECU); the ECU includes a network layer and a session layer.

[0008] The host computer sends diagnostic messages to the electronic control unit (ECU) via PCAN. After receiving the diagnostic message from the host computer, the ECU distinguishes the network protocol control information type of the diagnostic message, determines whether the current network status of the network layer allows the reception of the diagnostic message frame, and determines whether the addressing mode, session mode, and security level are equal to the ECU configuration information. If the network layer allows reception, the session layer determines whether the ECU supports the service. After the session layer confirms the response type to be sent, the network layer sends one or more frames according to the protocol type.

[0009] Furthermore, the ECU service configuration includes service identification code, sub-function support flag, session support status, function addressing support status, and secure access support status.

[0010] Furthermore, the network protocol control information types include single frames, first frames, consecutive frames, and flow control frames.

[0011] Furthermore, the network status includes the current network status, continuous frame waiting status, flow control frame waiting status, frame sequence number verification status, and transmitted frame sequence number.

[0012] Furthermore, the response types to be sent include positive responses and negative responses. The session layer determines whether the electronic control unit (ECU) supports sending diagnostic message services; and determines whether the addressing mode, session mode, and security level are equal to the ECU configuration information. If they do not match, a negative response is sent; if they match, a positive response is sent.

[0013] Furthermore, in the determination of the addressing mode, the addressing mode is divided into functional addressing and physical addressing. Functional addressing is communication between the host computer and all electronic control units (ECUs), while physical addressing is communication between the host computer and a specific electronic control unit (ECU).

[0014] Furthermore, after receiving the diagnostic message sent by the host computer, the electronic control unit (ECU) starts the diagnostic session timeout timer, sets the timeout threshold, and the host computer needs to send the next frame message within the set threshold.

[0015] According to some embodiments, the present disclosure adopts the following technical solutions:

[0016] The method for an automotive diagnostic service system based on the modular UDS protocol includes:

[0017] The host computer sends a diagnostic message to the electronic control unit (ECU) via PCAN. After receiving the diagnostic message from the host computer, the ECU first performs the following reception and processing at the network layer:

[0018] Upon receiving a diagnostic message, the diagnostic session timeout is started. The addressing mode of the diagnostic message is distinguished and the network protocol control information type of the diagnostic message is identified. It is determined whether the current network status supports receiving the identified diagnostic message information type. If it supports receiving, the network status is cleared. It is determined whether the message length conforms to the network protocol control information type. If it does, the diagnostic message is received and the next step of processing is performed.

[0019] According to some embodiments, the present disclosure adopts the following technical solutions:

[0020] The session layer's receive processing includes:

[0021] Determine if the network layer reception status is normal. If normal, start the diagnostic message session timeout timer.

[0022] The system queries whether the ECU service configuration supports the request. If it does, it determines whether the service configuration supports the current addressing mode, session mode, current security level, and whether the suppression flag is suppressed under a positive response. If it determines that the suppression is not supported, it sends a positive response diagnostic message and starts the diagnostic session timeout countdown.

[0023] Compared with the prior art, the beneficial effects of this disclosure are as follows:

[0024] This disclosure provides a method and system for automotive diagnostic services based on the modular UDS protocol, clarifies the development process of the lower-level machine of the UDS protocol, allows for the rapid addition of UDS services when the lower-level machine needs to be added, and enables rapid iteration when UDS services need to be added or removed, thereby reducing the amount of code modification.

[0025] The system provides a host computer, PCAN, and an electronic control unit (ECU) (used for developing lower-level electronic control units). The ECU includes a network layer and a session layer. The host computer sends diagnostic messages to the ECU via PCAN. After receiving the diagnostic message from the host computer, the ECU distinguishes the network protocol control information type of the diagnostic message, determines whether the current network status of the network layer allows the reception of the diagnostic message frame, and determines whether the addressing mode, session mode, and security level are equal to the ECU configuration information. If the network layer allows reception, the session layer determines whether the ECU supports the service. After the session layer confirms the response type to be sent, the network layer sends one or more frames according to the protocol type.

[0026] This disclosure allows for modular configuration of the UDS service, enabling modular programming of the network layer and session layer transmission processes for diagnostic message reception and transmission. This allows for rapid iteration when adding or removing UDS services, minimizing code modifications and avoiding risks of unforeseen consequences caused by scattered code and excessive modifications. Furthermore, the standardized UDS protocol and modular programs are easier to port. Attached Figure Description

[0027] The accompanying drawings, which form part of this disclosure, are used to provide a further understanding of this disclosure. The illustrative embodiments of this disclosure and their descriptions are used to explain this disclosure and do not constitute an undue limitation of this disclosure.

[0028] Figure 1 This is a flowchart of the network layer receiving and processing according to an embodiment of the present disclosure;

[0029] Figure 2 This is a flowchart of the session layer processing according to an embodiment of the present disclosure;

[0030] Figure 3 This is a flowchart illustrating the network layer message transmission process according to an embodiment of the present disclosure. Detailed Implementation

[0031] The present disclosure will be further described below with reference to the accompanying drawings and embodiments.

[0032] It should be noted that the following detailed descriptions are illustrative and intended to provide further explanation of this disclosure. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0033] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments according to this disclosure. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms “comprising” and / or “including” are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0034] Example 1

[0035] One embodiment of this disclosure provides an automotive diagnostic service system based on the modular UDS protocol, including a host computer, PCAN, and an electronic control unit (ECU); the ECU includes a network layer and a session layer.

[0036] The host computer sends diagnostic messages to the electronic control unit (ECU) via PCAN. After receiving the diagnostic message from the host computer, the ECU distinguishes the network protocol control information type of the diagnostic message, determines whether the current network status of the network layer allows the reception of the diagnostic message frame, and determines whether the addressing mode, session mode, and security level are equal to the ECU configuration information. If the network layer allows reception, the session layer determines whether the ECU supports the service. After the session layer confirms the response type to be sent, the network layer sends one or more frames according to the protocol type.

[0037] As one embodiment, the electronic control unit (ECU) service configuration includes a service identification code, a sub-function support flag, a session support status, a function addressing support status, and a secure access support status.

[0038] Network protocol control information types include single frames, first frames, consecutive frames, and flow control frames.

[0039] Network status includes current network status, continuous frame waiting status, flow control frame waiting status, frame sequence number verification status, and transmitted frame sequence number.

[0040] The response types to be sent include positive and negative responses. The session layer determines whether the electronic control unit (ECU) supports the diagnostic message service to be sent; and whether the addressing mode, session mode, and security level are equal to the ECU configuration information. If they do not match, a negative response is sent; if they match, a positive response is sent.

[0041] In determining the addressing mode, the addressing mode is divided into functional addressing and physical addressing. Functional addressing is communication between the host computer and all electronic control units (ECUs), while physical addressing is communication between the host computer and a specific electronic control unit (ECU).

[0042] After receiving the diagnostic message sent by the host computer, the Electronic Control Unit (ECU) starts the diagnostic session timeout timer and sets the timeout threshold. The host computer needs to send the next frame message within the set threshold.

[0043] In one embodiment, after receiving a diagnostic message from the host computer, the ECU distinguishes the network protocol control information type of the diagnostic message and determines whether the current network status allows receiving the message frame. If the network layer allows reception, the session layer then makes a judgment. The session layer first determines whether the ECU supports the service; then it determines whether the addressing mode, session mode, security level, etc., are equal to the ECU configuration information. If they do not match, a negative response is sent; if they do, a positive response is sent. After the session layer confirms that a response needs to be sent, the network layer determines the network protocol control information type of the message to be sent and sends one or more frames according to the protocol type.

[0044] Furthermore, the host computer sends diagnostic messages to the electronic control unit (ECU) via PCAN. After receiving the diagnostic messages from the host computer, the ECU first performs the following reception and processing at the network layer:

[0045] Upon receiving a diagnostic message, the diagnostic session timeout is started. The addressing mode of the diagnostic message is distinguished and the network protocol control information type of the diagnostic message is identified. It is determined whether the current network status supports receiving the identified diagnostic message information type. If it supports receiving, the network status is cleared. It is determined whether the message length conforms to the network protocol control information type. If it does, the diagnostic message is received and the next step of processing is performed.

[0046] The reception process at the session layer includes: determining whether the network layer reception status is normal; if normal, initiating the diagnostic message session timeout countdown.

[0047] The system queries whether the ECU service configuration supports the request. If it does, it determines whether the service configuration supports the current addressing mode, session mode, current security level, and whether the suppression flag is suppressed under a positive response. If it determines that the suppression is not supported, it sends a positive response diagnostic message and starts the diagnostic session timeout countdown.

[0048] Among them, such as Figure 1 As shown, the ECU is an electronic control unit, and the network layer receiving and processing flow is as follows:

[0049] Step 1: After receiving the diagnostic message, start the diagnostic session timeout timer, with a timeout period of 5 seconds; the host computer needs to send the next frame message within 5 seconds.

[0050] Step 2: Differentiate the diagnostic message addressing mode. Addressing modes are divided into functional addressing and physical addressing; functional addressing is used for communication between the host computer and all ECUs; physical addressing is used for communication between the host computer and a specific ECU.

[0051] Step 3: Identify the network protocol control information type of the diagnostic message. The network protocol control information types are divided into single frame, first frame, continuous frame, and flow control frame.

[0052] Step 4: Determine whether the current network status supports receiving diagnostic messages of the type in Step 3. If yes, proceed to Step 5; otherwise, ignore the diagnostic message frame.

[0053] Step 5: Clear the network status, which includes the current network status, continuous frame waiting status, flow control frame waiting status, frame sequence number verification status, and transmitted frame sequence number, etc.

[0054] Step 6: Determine whether the length of the message conforms to the network protocol control information type. If yes, proceed to step 7; otherwise, proceed to step 8.

[0055] Step 7: Receive the diagnostic message in this frame.

[0056] Step 8: Ignore the diagnostic message in this frame and upload the error information.

[0057] like Figure 2 As shown, the process of receiving and processing diagnostic messages at the session layer includes:

[0058] Step 1) Determine if the network layer reception status is normal. If yes, proceed to step 2); otherwise, start the diagnostic session timeout timer.

[0059] Step 2) Check if the requested ECU service configuration is supported. If yes, proceed to step 3); otherwise, return a negative code: service is not supported, and start the diagnostic session timeout timer.

[0060] Step 3) Determine whether the service configuration supports the current addressing method. If yes, proceed to step 4); otherwise, start the diagnostic session timeout timer.

[0061] Step 4) Determine if the service configuration supports the current session mode. If yes, proceed to Step 5); otherwise, return a negative code: Activation session not supported, and start the diagnostic session timeout timer. The session modes are divided into default session, programming session, and extended session.

[0062] Step 5) Determine if the service configuration supports the current security level. If yes, proceed to step 6); otherwise, return a negative code: security access denied, and start the diagnostic session timeout timer.

[0063] Step 6) Determine whether the positive response suppression flag is suppressed. If yes, proceed to step 7); otherwise, proceed to step 8.

[0064] Step 7) Do not send a positive response message, start the diagnostic session timeout timer.

[0065] Step 8) Send an affirmative response message to start the diagnostic session timeout timer.

[0066] The above ECU service configuration includes: service identification code, sub-function support flag, session support status, function addressing support status, and secure access support status.

[0067] like Figure 3 As shown, the steps in the network layer's diagnostic message processing flow include:

[0068] Step 1. Determine whether the network protocol control information type of the sent message is multi-frame. If yes, proceed to step 3; otherwise, proceed to step 2.

[0069] Step 2. Send the message according to the single-frame data format.

[0070] Step 3. Send the message according to the first frame data format.

[0071] Step 4. Update the network status and start the network layer timeout timer.

[0072] Step 5. Determine if flow control information has been received. If yes, proceed to step 7; otherwise, proceed to step 6.

[0073] Step 6. Determine if the network layer timer has expired. If yes, exit the sending procedure; otherwise, proceed to step 5.

[0074] Step 7. Determine if all messages have been sent. If yes, proceed to step 8; otherwise, proceed to step 9.

[0075] Step 8. Clear network status.

[0076] Step 9. Continue sending the remaining messages according to the flow control information.

[0077] Example 2

[0078] One embodiment of this disclosure provides a method for an automotive diagnostic service system based on the modular UDS protocol, comprising:

[0079] The host computer sends a diagnostic message to the electronic control unit (ECU) via PCAN. After receiving the diagnostic message from the host computer, the ECU first performs the following reception and processing at the network layer:

[0080] Upon receiving a diagnostic message, the diagnostic session timeout is started. The addressing mode of the diagnostic message is distinguished and the network protocol control information type of the diagnostic message is identified. It is determined whether the current network status supports receiving the identified diagnostic message information type. If it supports receiving, the network status is cleared. It is determined whether the message length conforms to the network protocol control information type. If it does, the diagnostic message is received and the next step of processing is performed.

[0081] The session layer's receive processing includes:

[0082] Determine if the network layer reception status is normal. If normal, start the diagnostic message session timeout timer.

[0083] The system queries whether the ECU service configuration supports the request. If it does, it determines whether the service configuration supports the current addressing mode, session mode, current security level, and whether the suppression flag is suppressed under a positive response. If it determines that the suppression is not supported, it sends a positive response diagnostic message and starts the diagnostic session timeout countdown.

[0084] Among them, such as Figure 1 As shown, the ECU is an electronic control unit, and the network layer receiving and processing flow is as follows:

[0085] Step 1: After receiving the diagnostic message, start the diagnostic session timeout timer, with a timeout period of 5 seconds; the host computer needs to send the next frame message within 5 seconds.

[0086] Step 2: Differentiate the diagnostic message addressing mode. Addressing modes are divided into functional addressing and physical addressing; functional addressing is used for communication between the host computer and all ECUs; physical addressing is used for communication between the host computer and a specific ECU.

[0087] Step 3: Identify the network protocol control information type of the diagnostic message. The network protocol control information types are divided into single frame, first frame, continuous frame, and flow control frame.

[0088] Step 4: Determine whether the current network status supports receiving diagnostic messages of the type in Step 3. If yes, proceed to Step 5; otherwise, ignore the diagnostic message frame.

[0089] Step 5: Clear the network status, which includes the current network status, continuous frame waiting status, flow control frame waiting status, frame sequence number verification status, and transmitted frame sequence number, etc.

[0090] Step 6: Determine whether the length of the message conforms to the network protocol control information type. If yes, proceed to step 7; otherwise, proceed to step 8.

[0091] Step 7: Receive the diagnostic message in this frame.

[0092] Step 8: Ignore the diagnostic message in this frame and upload the error information.

[0093] like Figure 2 As shown, the process of receiving and processing diagnostic messages at the session layer includes:

[0094] Step 1) Determine if the network layer reception status is normal. If yes, proceed to step 2); otherwise, start the diagnostic session timeout timer.

[0095] Step 2) Check if the requested ECU service configuration is supported. If yes, proceed to step 3); otherwise, return a negative code: service is not supported, and start the diagnostic session timeout timer.

[0096] Step 3) Determine whether the service configuration supports the current addressing method. If yes, proceed to step 4); otherwise, start the diagnostic session timeout timer.

[0097] Step 4) Determine if the service configuration supports the current session mode. If yes, proceed to Step 5); otherwise, return a negative code: Activation session not supported, and start the diagnostic session timeout timer. The session modes are divided into default session, programming session, and extended session.

[0098] Step 5) Determine if the service configuration supports the current security level. If yes, proceed to step 6); otherwise, return a negative code: security access denied, and start the diagnostic session timeout timer.

[0099] Step 6) Determine whether the positive response suppression flag is suppressed. If yes, proceed to step 7); otherwise, proceed to step 8.

[0100] Step 7) Do not send a positive response message, start the diagnostic session timeout timer.

[0101] Step 8) Send an affirmative response message to start the diagnostic session timeout timer.

[0102] The above ECU service configuration includes: service identification code, sub-function support flag, session support status, function addressing support status, and secure access support status.

[0103] like Figure 3 As shown, the steps in the network layer's diagnostic message processing flow include:

[0104] Step 1. Determine whether the network protocol control information type of the sent message is multi-frame. If yes, proceed to step 3; otherwise, proceed to step 2.

[0105] Step 2. Send the message according to the single-frame data format.

[0106] Step 3. Send the message according to the first frame data format.

[0107] Step 4. Update the network status and start the network layer timeout timer.

[0108] Step 5. Determine if flow control information has been received. If yes, proceed to step 7; otherwise, proceed to step 6.

[0109] Step 6. Determine if the network layer timer has expired. If yes, exit the sending procedure; otherwise, proceed to step 5.

[0110] Step 7. Determine if all messages have been sent. If yes, proceed to step 8; otherwise, proceed to step 9.

[0111] Step 8. Clear network status.

[0112] Step 9. Continue sending the remaining messages according to the flow control information.

[0113] Example 3

[0114] One embodiment of this disclosure provides an electronic device, including: a processor, a memory, and a computer program; wherein the processor is connected to the memory, the computer program is stored in the memory, and when the electronic device is running, the processor executes the computer program stored in the memory to cause the electronic device to perform the method described thereon.

[0115] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0116] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0117] While the specific embodiments of this disclosure have been described above in conjunction with the accompanying drawings, this is not intended to limit the scope of protection of this disclosure. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solutions of this disclosure are still within the scope of protection of this disclosure.

Claims

1. An automotive diagnostic service system based on the modular UDS protocol, characterized in that, It includes a host computer, PCAN, and an electronic control unit (ECU); the ECU includes a network layer and a session layer. The host computer sends diagnostic messages to the electronic control unit (ECU) via PCAN. After receiving the diagnostic messages from the host computer, the ECU first performs reception processing at the network layer. The specific process is as follows: after receiving the diagnostic message, it starts the diagnostic session timeout count, distinguishes the addressing mode of the diagnostic message and identifies the network protocol control information type of the diagnostic message, determines whether the current network status of the network layer supports receiving the identified diagnostic message information type. If it supports receiving, it clears the network status, determines whether the message length conforms to the network protocol control information type, and if it does, it receives the diagnostic message and proceeds to the next step of processing. After the network layer allows reception, the session layer determines whether the electronic control unit (ECU) supports the service, and then determines whether the addressing mode, session mode, and security level are equal to the ECU configuration information. After the session layer confirms the response type to be sent, the network layer sends one or more frames according to the protocol type.

2. The automotive diagnostic service system based on the modular UDS protocol as described in claim 1, characterized in that, The service configuration of the electronic control unit (ECU) includes the service identification code, sub-function support flag, session support status, function addressing support status, and security access support status.

3. The automotive diagnostic service system based on the modular UDS protocol as described in claim 1, characterized in that, The network protocol control information types include single frames, first frames, consecutive frames, and flow control frames.

4. The automotive diagnostic service system based on the modular UDS protocol as described in claim 1, characterized in that, The network status includes the current network status, continuous frame waiting status, flow control frame waiting status, frame sequence number verification status, and transmitted frame sequence number.

5. The automotive diagnostic service system based on the modular UDS protocol as described in claim 1, characterized in that, The response types that need to be sent include positive responses and negative responses. The session layer determines whether the electronic control unit (ECU) supports sending diagnostic message services. It also checks whether the addressing mode, session mode, and security level are equal to the configuration information of the electronic control unit (ECU). If they do not match, a negative response is sent; if they match, a positive response is sent.

6. The automotive diagnostic service system based on the modular UDS protocol as described in claim 5, characterized in that, In the determination of the addressing mode, the addressing mode is divided into functional addressing and physical addressing. Functional addressing is communication between the host computer and all electronic control units (ECUs), while physical addressing is communication between the host computer and a specific electronic control unit (ECU).

7. The automotive diagnostic service system based on the modular UDS protocol as described in claim 1, characterized in that, After receiving the diagnostic message sent by the host computer, the electronic control unit (ECU) starts the diagnostic session timeout timer and sets the timeout threshold. The host computer needs to send the next frame message within the set threshold.

8. A method for an automotive diagnostic service system based on the modular UDS protocol as described in any one of claims 1-7, characterized in that, include: The host computer sends a diagnostic message to the electronic control unit (ECU) via PCAN. After receiving the diagnostic message from the host computer, the ECU first performs the following reception and processing at the network layer: Upon receiving a diagnostic message, the diagnostic session timeout is started. The addressing mode of the diagnostic message is distinguished and the network protocol control information type of the diagnostic message is identified. It is determined whether the current network status supports receiving the identified diagnostic message information type. If it supports receiving, the network status is cleared. It is determined whether the message length conforms to the network protocol control information type. If it does, the diagnostic message is received and the next step of processing is performed.

9. As described in claim 8, characterized in that, The reception process at the session layer includes: determining whether the network layer reception status is normal; if normal, initiating the diagnostic message session timeout countdown. The system queries whether the ECU service configuration supports the request. If it does, it determines whether the service configuration supports the current addressing mode, session mode, current security level, and whether the suppression flag is suppressed under a positive response. If it determines that the suppression is not supported, it sends a positive response diagnostic message and starts the diagnostic session timeout countdown.

10. An electronic device, characterized in that, include: The electronic device includes a processor, a memory, and a computer program; wherein the processor is connected to the memory, the computer program is stored in the memory, and when the electronic device is running, the processor executes the computer program stored in the memory to cause the electronic device to perform the method as described in any one of claims 8-9.

Images