WO2023222109A1

WO2023222109A1 - Network wakeup management method and apparatus, electronic device, and storage medium

Info

Publication number: WO2023222109A1
Application number: PCT/CN2023/095232
Authority: WO
Inventors: 揣孟洋; 李长龙; 周时莹; 梁贵友; 孔祥明; 李想; 王达; 张旭东; 刘晓东
Original assignee: 中国第一汽车股份有限公司
Priority date: 2022-05-20
Filing date: 2023-05-19
Publication date: 2023-11-23
Also published as: CN114978883A; CN114978883B

Abstract

The present application relates to the technical field of computers, and discloses a network wakeup management method and apparatus, an electronic device, and a storage medium. The method comprises: detecting a network mode of a network controller; in response to the network mode being a sleep mode, determining the type of a network wakeup request when the network wakeup request is received; and managing the network wakeup request on the basis of the type of the network wakeup request to obtain a corresponding wakeup management log, and storing the wakeup management log to a memory unit in the network controller.

Description

Management method, device, electronic device and storage medium for wake-on-LAN

This application claims priority to the Chinese patent application with application number 202210553092.0, which was submitted to the China Patent Office on May 20, 2022. The entire content of this application is incorporated into this application by reference.

Technical field

The present application relates to the field of computer technology, for example, to a management method, device, electronic device and storage medium for network wake-up.

Background technique

As the remote function of the car requires the vehicle to have the ability to respond to user needs when the power is turned off, more and more car controllers have the ability to sleep and wake up the Controller Area Network (Controller Area Network, CAN) bus, and once Occasional malfunctions in automobile components prevent the vehicle from sleeping, and large amounts of static current can cause the vehicle to quickly lose power and become unable to start. This type of fault is often difficult to troubleshoot, and every time a customer complains, no evidence can be found to prove the fault.

As the core of the vehicle network, the gateway is actually the node most capable of monitoring sleep and wake-up conditions on the network. However, the current gateway technology basically remains at the basic work of routing between network segments. In the development of some projects, component integration work may be added. However, the main job of the gateway is to route messages between different network segments. There is no In-depth exploration of the architectural advantages where it is located cannot solve the above-mentioned troubleshooting problems.

Contents of the invention

This application provides a management method, device, electronic device and storage medium for network wake-up, which can solve the problem of difficult vehicle troubleshooting.

In the first aspect, this application provides a management method for network wake-up, including:

Detect the network mode of the network controller;

In response to the network mode being the sleep mode, determining the type of the network wake-up request when receiving the network wake-up request;

Based on the type of the network wake-up request, the network wake-up request is managed to obtain a corresponding wake-up management log, and the wake-up management log is stored in a memory unit in the network controller.

In the second aspect, this application provides a management device for wake-on-network, including:

A detection module, set to detect the network mode of the network controller;

a determining module configured to determine the type of the network wake-up request when receiving a network wake-up request in response to the network mode being the sleep mode;

A management module configured to manage the network wake-up request to obtain a corresponding wake-up management log based on the type of the network wake-up request, and store the wake-up management log in a memory unit in the network controller.

In a third aspect, this application provides an electronic device, which includes:

at least one processor; and

a memory communicatively connected to the at least one processor; wherein,

The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor, so that the at least one processor can execute the network described in any embodiment of the present application. Awakening management methods.

In a fourth aspect, the present application provides a computer-readable storage medium that stores computer instructions, and the computer instructions are configured to enable the processor to implement the network wake-up described in any embodiment of the application when executed. management methods.

Description of the drawings

Figure 1 is a first flow diagram of a wake-on-network management method provided by an embodiment of the present application;

Figure 2 is a second flow diagram of a wake-on-network management method provided by an embodiment of the present application;

Figure 3 is a schematic structural diagram of a wake-on-network management device provided by an embodiment of the present application;

Figure 4 is a block diagram of an electronic device used to implement a wake-on-network management method according to an embodiment of the present application.

Detailed ways

It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that data so used are interchangeable under appropriate circumstances so that the embodiments of the invention described herein are capable of being implemented in sequences other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus that encompasses a series of steps or units and need not be limited to those explicitly listed. Those steps or elements may instead include other steps or elements not expressly listed or inherent to the process, method, product or apparatus.

FIG. 1 is a first flow diagram of a method for managing wake-on-network provided by an embodiment of the present application. This embodiment can be applied to the situation of managing wake-on-network. The method for managing wake-on-network provided by this embodiment can be executed by the management device for managing wake-on-network provided by the embodiment of this application. The device can be implemented by at least one of software and hardware, and be integrated into an electronic device that executes the method. in the device. This embodiment is introduced by taking the electronic device as a vehicle as an example. The execution subject that executes the network wake-up management method of the present application may be a microprocessor configured on the vehicle.

Referring to Figure 1, the method of this embodiment includes but is not limited to the following steps:

S110. Detect the network mode of the network controller.

Among them, the network controller refers to the control unit that monitors the network status of the vehicle, such as a gateway or other gateway-like components at the center of the network; the network mode refers to the connection status between the vehicle and the network, which can include sleep mode, pre-sleep mode and working mode.

In the embodiment of the present application, the network mode of the current network controller can be obtained in real time through the microprocessor configured on the vehicle, or the network controller actively reports its own network mode to the microprocessor.

Optionally, in order to monitor abnormal sleep and wake-up sources on the automotive network, the network control A controller (such as a gateway or other gateway-like components at the center of the network) needs to be customized to a certain extent. In addition to a separate log system with monitoring functions and an internal storage unit that is not lost when powered off, the network controller also needs Ability to analyze data and record faults.

S120. In response to the network mode being the sleep mode, determine the type of the network wake-up request when receiving the network wake-up request.

Among them, when the vehicle's nodes or components are in sleep mode, it only receives network wake-up requests from the Electronic Control Unit (Electronic Control Unit, ECU) node and does not send any messages. Multiple nodes of the vehicle adopt a distributed network management method. The vehicle nodes send network wake-up requests and their own network management status, and receive network wake-up requests and status from other ECU nodes on the Controller Area Network (Controller Area Network, CAN) bus. .

Among them, the types of network wake-up requests include local wake-up requests and remote wake-up requests.

In the embodiment of this application, when the network mode of the network controller is the sleep mode, when receiving a network wake-up request from the ECU node, it is necessary to first determine the type of the network wake-up request, and then perform different types of network wake-up requests. Wake-on-LAN management with different measures.

S130. Based on the type of the network wake-up request, manage the network wake-up request to obtain the corresponding wake-up management log, and store the wake-up management log in the memory unit in the network controller.

Among them, the wake-up management log is set to record information related to the network wake-up request. For example, the wake-up management log may include identification information of the wake-up source, the timestamp of the network wake-up request, and network management messages related to the network wake-up request.

Illustratively, this step is based on the type of the network wake-up request. The process of managing the network wake-up request and obtaining the corresponding wake-up management log can be implemented in the following two situations:

Case 1: When the type of network wake-up request is a local wake-up request, the first wake-up management log is generated.

(1) In response to the type of network wake-up request being a local wake-up request, determine the component that issues the local wake-up request from the network controller.

Among them, the local wake-up request may refer to the network where the wake-up source originates from the internal components of the network controller. Wake-up request, or battery power (such as KL15) hard wire wake-up or hardware sensor wake-up, etc. For example, the local wake-up request of the network controller may mean that the internal clock of the network controller wakes up the network controller at intervals, prompting the awakened network controller to detect the status of the battery power supply. If the battery power supply is at this time If the battery power is low, the battery power source replies a network wake-up request to the network controller, so that the battery power source wakes up the network controller and related vehicle nodes used to charge the battery power source. Therefore, battery power is due to the network controller's internal clock waking up and then sending a network wake-up request. Therefore, the hardware wake-up on battery power is also classified as a local wake-up request.

In the embodiment of this application, if the type of network wake-up request is a local wake-up request, it indicates that the internal components of the network controller have a need to wake up the network, and the component that issues the local wake-up request is determined from the network controller based on the attribute information of the local wake-up request. , where the attribute information may be the identification number of the local wakeup request.

(2) Determine the name of the component and the timestamp of the local wakeup request.

(3) Generate the first wake-up management log based on the name of the component and the timestamp of the local wake-up request.

For example, if the name of the component (i.e., the wake-up source) is a power management component, and the timestamp of the local wake-up request is 15:36 on March 16, 2022, the first wake-up management log can be: Local Wake-Power Management Component -202203161536.

Case 2: When the type of network wake-up request is a remote wake-up request, a second wake-up management log is generated.

(1) In response to the type of network wake-up request being a remote wake-up request, obtain the network interrupt message that causes the network controller to be interrupted due to the remote wake-up request, and record the current wake-up time point.

The remote wake-up request may refer to a network wake-up request originating from other ECU nodes on the CAN bus.

In the embodiment of this application, if the type of network wake-up request is a remote wake-up request, it indicates that other ECU nodes on the CAN bus have a need to wake up the network. At this time, since the remote wake-up request will cause the network controller to interrupt, it is necessary to obtain the network controller The interrupted network interruption message and the network interruption message's Identification number, and record the wake-up time point of the remote wake-up request.

(2) Determine the first controller that issues the remote wake-up request based on the network interrupt message.

In this embodiment of the present application, the first controller can be divided into self wake-up and CAN wake-up according to the network wake-up mode. Self-wake-up means that the first controller (i.e. ECU node) actively issues a network wake-up request. CAN wake-up means that the first controller is awakened by other controllers that wake up themselves or other CAN-wake-up controllers and issues a network wake-up request. A controller that wakes up by itself can cause multiple other controllers to wake up through CAN wake-up. Generally, when the sensitivity of the first controller (ie, the ECU node) is very good, the interruption of the network controller is generally due to the first controller's own wake-up. In an implementable embodiment, the first controller that issues the remote wake-up request can be determined through the first frame information of the network interrupt message.

(3) Generate a second wake-up management log based on the network interrupt message, the first controller, and the current wake-up time point.

For example, if the first controller (i.e., the wake-up source) is component A, the current wake-up time point is 15:36 on March 16, 2022, and the network interruption message is an a message, then the second wake-up management log can be : Remote wake-up-A component-a message-202203161536.

In the embodiment of the present application, if the sensitivity of the first controller (ie, the ECU node) is not good, the first controller that causes the network controller to interrupt may not be the controller that wakes up by itself, but the controller that wakes up from the CAN. Therefore, the first controller that sends the remote wake-up request determined in the above step (2) may be the controller that wakes up by itself, or it may be the controller that wakes up by CAN. Therefore, in order to determine whether the first controller is a controller that wakes up by itself or a CAN wake-up controller, before generating the second wake-up management log based on the network interrupt message, the first controller, and the current wake-up time point, it also includes: determining The network segment where the first controller is located; obtain the stable network management message of the network segment within the preset time (such as three minutes) after the current wake-up time point; determine the second controller that issues the remote wake-up request based on the stable network management message ; Determine whether the first controller and the second controller are the same controller; the first controller and the second controller are the same controller, and perform generation based on the network interrupt message, the first controller, and the current wake-up time point The second wake-up management log operation. Among them, the second controller must be the controller that wakes up by itself. this The advantage of this setting is that it can more accurately find the second controller that wakes itself up by issuing a remote wakeup request.

Exemplarily, determining the second controller that issued the remote wake-up request based on the stable network management message includes: determining multiple controllers with remote wake-up requests based on the stable network management message; and analyzing the wake-up reasons of the multiple controllers. Obtain analysis results; based on the analysis results, find out from multiple controllers the second controller whose wake-up reason is its own wake-up. Among them, the wake-up reasons include self-wake-up and CAN wake-up.

The technical solution provided by this embodiment first detects the network mode of the network controller through the microprocessor; if the network mode is the sleep mode, the type of the network wake-up request is determined when the network wake-up request is received; and then based on the type of the network wake-up request , manage the network wake-up request to obtain the corresponding wake-up management log, and store the wake-up management log to the memory unit in the network controller. When the network controller is in sleep mode, this application first analyzes the type of network wake-up request when receiving a network wake-up request, then performs different measures for network wake-up management for different types of network wake-up requests, and finally generates a wake-up management log. The network controller of this application captures controllers with network wake-up requests in sleep mode, and generates independent wake-up management logs and bus data for independent storage as evidence, which can solve the problem of difficult vehicle troubleshooting.

The following describes a wake-on-LAN management method provided by an embodiment of the present invention. FIG. 2 is a second flowchart of a wake-on-LAN management method provided by an embodiment of the present application. The embodiment of the present application is refined on the basis of the above-mentioned embodiment. This embodiment explains in detail the network management process when the network mode of the network controller is the pre-sleep mode and the working mode.

Referring to Figure 2, the method of this embodiment includes but is not limited to the following steps:

S210. Detect the network mode of the network controller.

For the relevant content of this step, please refer to step S110 in the embodiment of FIG. 1 and will not be described again here.

S220. If the network mode is the sleep mode, determine the type of the network wake-up request when receiving the network wake-up request; based on the type of the network wake-up request, manage the network wake-up request to obtain the corresponding wake-up management log, and store the wake-up management log to the memory unit in the network controller.

For relevant content of this step, please refer to steps S120-S130 in the embodiment of Figure 1, which will not be described again here.

S230. In response to the network mode being the pre-sleep mode, obtain residual network management messages on the controller area network (CAN) bus.

In this embodiment of the present application, the network mode of the network controller will be in the pre-sleep mode within a preset time (such as five minutes) after the vehicle power is turned off. When the network controller is in pre-sleep mode, it is only allowed to receive network wake-up requests from ECU nodes. Messages already in the sending buffer (Buffer) should stop immediately after being sent.

In this embodiment of the present application, when the network mode of the network controller is the pre-sleep mode, the network controller will actively monitor whether there are residual network management messages on the CAN bus, and if so, actively obtain the residual network management messages.

S240. Determine the identification code and timestamp of the remaining network management message.

In this embodiment of the present application, after the network controller obtains the residual network management message through the above-mentioned step S230, it then determines the identification code and timestamp of the residual network management message.

S250: Generate a sleep management log based on the residual network management message, the identification code of the residual network management message, and the timestamp of the residual network management message, and store the sleep management log in the memory unit.

Among them, the sleep management log is set to record the message information sent and received in the network when the network mode is pre-sleep mode.

For example, if the residual network management message is a b message, the identification code of the residual network management message is the B component, and the timestamp of the residual network management message is 15:36 on March 16, 2022, then the dormant management log It can be: pre-sleep mode-B component-b message-202203161536.

S260. In response to the network mode switching to the working mode, send the wake-up management log and the sleep management log to the server, so that the server can check whether the electronic device fails based on the wake-up management log and the sleep management log.

Among them, the network controller has the function of connecting to the server and uploading files. After the vehicle is powered on, it can also accept data retrieval from the server at any time to achieve remote troubleshooting capabilities. When the network server is in working mode, messages can be sent and received normally, but when the network server is in pre-sleep mode, messages are not allowed to be sent and received. Allow sending messages.

In the embodiment of the present application, when the network controller is in the sleep mode, the network controller records the wake-up management log and stores the wake-up management log to the memory unit in the network controller; when the network controller is in the pre-sleep mode, the network controller The controller records the hibernation management log and stores the hibernation management log to the memory unit in the network controller. When the network mode switches from the sleep mode or the pre-sleep mode to the working mode, the network controller can send the wake-up management log and the sleep management log to the server, so that the server can check whether the electronic device malfunctions based on the wake-up management log and the sleep management log.

It should be noted that S220 corresponds to the process of the network mode being in the sleep mode, and S230-S250 corresponds to the process of the network mode being in the pre-sleep mode. These two processes are independent of each other. The embodiment of the present application does not cover these two processes. The execution order of the two processes needs to be determined according to the actual situation. Therefore, the actual execution may be in the order introduced in the above embodiments of this application, or S230-S250 may be executed first, and then S220 may be executed.

The technical solution provided by this embodiment detects the network mode of the network controller; if the network mode is the sleep mode, the type of the network wake-up request is determined when receiving the network wake-up request; based on the type of the network wake-up request, the network wake-up request is processed Perform management to obtain the corresponding wake-up management log, and store the wake-up management log to the memory unit in the network controller; when the network mode is pre-sleep mode, obtain the residual network management messages on the CAN bus of the controller's local network; determine the remaining The identification code and timestamp of the network management message; generate a sleep management log based on the residual network management message, the identification code of the residual network management message, and the timestamp of the residual network management message, and store the sleep management log in the memory unit; When the network mode is switched to the working mode, the wake-up management log and the sleep management log are sent to the server, so that the server can check whether the electronic device is faulty based on the wake-up management log and the sleep management log. When the network controller is in sleep mode, this application captures controllers with network wake-up requests and generates wake-up management logs; when the network controller is in pre-sleep mode, it captures controllers that cause the network to be unable to sleep. Generate sleep management logs; store wake-up management logs, sleep management logs, and bus data independently as evidence, and upload wake-up management logs and sleep management logs to the server in a timely manner to facilitate developers to troubleshoot faulty controllers inside the vehicle. Can solve vehicle troubleshooting Difficult questions.

Figure 3 is a schematic structural diagram of a wake-on-network management device provided by an embodiment of the present application. As shown in Figure 3, the device 300 may include:

The detection module 310 is configured to detect the network mode of the network controller;

The determining module 320 is configured to determine the type of the network wake-up request when receiving a network wake-up request in response to the network mode being the sleep mode;

The management module 330 is configured to manage the network wake-up request to obtain a corresponding wake-up management log based on the type of the network wake-up request, and store the wake-up management log in a memory unit in the network controller.

Exemplarily, the above-mentioned management module 330 may include a first management unit and a second management unit;

The first management unit may be configured to: in response to the type of the network wake-up request being a local wake-up request, determine the component that issued the local wake-up request from the network controller; determine the name of the component and the and generating a first wakeup management log based on the name of the component and the timestamp of the local wakeup request.

The second management unit may be configured to: in response to the type of the network wake-up request being a remote wake-up request, obtain a network interruption message that causes the network controller to be interrupted due to the remote wake-up request, and record the current wake-up time point; determine the first controller that issues the remote wake-up request based on the network interruption message; generate a second wake-up management log based on the network interruption message, the first controller, and the current wake-up time point.

Exemplarily, the above-mentioned second management unit may be configured to: before generating a second wake-up management log based on the network interruption message, the first controller, and the current wake-up time point, determine the first control The network segment where the controller is located; obtain the stable network management message of the network segment within the preset time after the current wake-up time point; determine the second controller that issues the remote wake-up request based on the stable network management message ; Determine whether the first controller and the second controller are the same controller; the first controller and the second controller are the same controller, and execute the The first controller generates a second wake-up management log at the current wake-up time point.

Exemplarily, the above-mentioned second management unit may also be configured to: determine multiple controllers that have the remote wake-up request according to the stable network management message; analyze the wake-up reasons of the multiple controllers to obtain the analysis Result: Based on the analysis result, a second controller whose wake-up reason is its own wake-up is found from the plurality of controllers.

Exemplarily, the above-mentioned network wake-up management device may also include: a pre-sleep management module;

The pre-sleep management module is configured to obtain residual network management messages on the CAN bus of the controller local network in response to the network mode being the pre-sleep mode; determine the identification code and timestamp of the residual network management messages; A sleep management log is generated based on the residual network management message, the identification code of the residual network management message, and the timestamp of the residual network management message, and the sleep management log is stored in the memory unit.

Exemplarily, the above-mentioned wake-on-network management device may also include: a log sending module;

The log sending module is configured to send the wake-up management log and the sleep management log to the server in response to the network mode switching to the working mode, so that the server can send the wake-up management log and the sleep management log to the server according to the wake-up management log and the sleep management log. Manage logs to check whether electronic equipment malfunctions.

The wake-on-LAN management device provided in this embodiment can be applied to the wake-on-LAN management method provided in any of the above embodiments, and has corresponding functions and effects.

FIG. 4 shows a schematic structural diagram of an electronic device 10 that can be used to implement embodiments of the present application. Electronic devices are intended to refer to various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (eg, helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connection relationships, and their functions are only examples and are not intended to limit the scope of the present application.

As shown in FIG. 4 , the electronic device 10 includes at least one processor 11 and at least one processing unit 11 . A memory that is communicatively connected to the processor 11, such as a read-only memory (Read-Only Memory, ROM) 12, a random access memory (Random Access Memory, RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, The processor 11 can perform various appropriate actions and processes according to a computer program stored in the read-only memory (ROM) 12 or loaded from the storage unit 18 into the random access memory (RAM) 13 . In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via the bus 14. An input/output (I/O) interface 15 is also connected to the bus 14 .

Multiple components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc. etc.; and communication unit 19, such as network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices through computer networks such as the Internet and various telecommunications networks.

Processor 11 may be a variety of general or special purpose processing components having processing and computing capabilities. Examples of the processor 11 include, but are not limited to, a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU), various dedicated artificial intelligence (Artificial Intelligence, AI) computing chips, and various running machines. Processor of learning model algorithm, digital signal processor (Digital Signal Processing, DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the above-described methods and processes, such as the management method of network wake-up.

In some embodiments, the method for managing wake-on-LAN may be implemented as a computer program, which is tangibly included in a computer-readable storage medium, such as the storage unit 18 . In some embodiments, part or all of the computer program may be loaded or installed onto the electronic device 10 via at least one of the ROM 12 and the communication unit 19 . When the computer program is loaded into the RAM 13 and executed by the processor 11, at least one step of the above-described management method for wake-on-LAN may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the wake-on-LAN management method in any other suitable manner (eg, by means of firmware).

Various implementations of the systems and techniques described above may be implemented in digital electronic circuit systems, integrated circuit systems, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Implemented in Application Specific Standard Parts (ASSP), System on Chip (SOC), Complex Programmable Logic Device (CPLD), computer hardware, firmware, software, and their combinations . These various embodiments may include implementation in at least one computer program executable or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general purpose programmable processor. The processor is programmed to receive data and instructions from and transfer data and instructions to the storage system, the at least one input device, and the at least one output device.

Computer programs for implementing the methods of the present application may be written in any combination of at least one programming language. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer program causes the functions or operations specified in the flowcharts and block diagrams to be implemented. A computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this application, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. Computer-readable storage media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium may be a machine-readable signal medium. Examples of machine-readable storage media would include an electrical connection based on at least one wire, a portable computer disk, a hard disk, random access memory (RAM), read only memory (ROM), Erasable Programmable Read -Only Memory, EPROM), flash memory, optical fiber, portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing.

To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having a display device (e.g., a cathode ray tube (CRT) or liquid crystal) for displaying information to the user. A display (Liquid Crystal Display, LCD monitor); and a keyboard and pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and may be provided in any form, including Acoustic input, voice input or tactile input) to receive input from the user.

The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., A user's computer having a graphical user interface or web browser through which the user can interact with implementations of the systems and technologies described herein), or including such backend components, middleware components, or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communications network). Examples of communication networks include: Local Area Network (LAN), Wide Area Network (WAN), blockchain network, and the Internet.

Computing systems may include clients and servers. Clients and servers are generally remote from each other and typically interact over a communications network. The relationship of client and server is created by computer programs running on corresponding computers and having a client-server relationship with each other. The server can be a cloud server, also known as cloud computing server or cloud host. It is a host product in the cloud computing service system to solve the management problems that exist in traditional physical hosts and virtual private servers (VPS). It has the disadvantages of high difficulty and weak business scalability.

It should be understood that various forms of the process shown above may be used, with steps reordered, added or deleted. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders. As long as the desired results of the technical solution of this application can be achieved, this article will not go into details here. row restrictions.

Claims

A management method for network wake-up, including:

Detect the network mode of the network controller;

In response to the network mode being the sleep mode, determining the type of the network wake-up request when receiving the network wake-up request;

Based on the type of the network wake-up request, the network wake-up request is managed to obtain a corresponding wake-up management log, and the wake-up management log is stored in a memory unit in the network controller.
The management method of network wake-up according to claim 1, wherein said managing the network wake-up request to obtain a corresponding wake-up management log based on the type of the network wake-up request includes:

In response to the type of the network wake-up request being a local wake-up request, determine the component that issued the local wake-up request from the network controller;

Determine the name of the component and the timestamp of the local wake request;

A first wake management log is generated based on the name of the component and the timestamp of the local wake request.
The management method of network wake-up according to claim 1, wherein said managing the network wake-up request to obtain a corresponding wake-up management log based on the type of the network wake-up request includes:

In response to the type of the network wake-up request being a remote wake-up request, obtain a network interruption message that causes the network controller to be interrupted due to the remote wake-up request, and record the current wake-up time point;

Determine the first controller that issues the remote wakeup request based on the network interrupt message;

Generate a second wake-up management log based on the network interruption message, the first controller, and the current wake-up time point.
The management method of network wake-up according to claim 3, wherein before generating the second wake-up management log based on the network interruption message, the first controller, and the current wake-up time point, it further includes:

Determine the network segment where the first controller is located;

Obtain stable network management messages of the network segment within a preset time after the current wake-up time point;

Determine the second controller that issues the remote wakeup request based on the stable network management message;

Determine whether the first controller and the second controller are the same controller;

The first controller and the second controller are the same controller, and perform an operation of generating a second wake-up management log based on the network interruption message, the first controller, and the current wake-up time point.
The management method of network wake-up according to claim 4, wherein the determining the second controller that issues the remote wake-up request based on the stable network management message includes:

Determine multiple controllers that have the remote wakeup request according to the stable network management message;

Analyze the wake-up reasons of the multiple controllers to obtain analysis results;

Based on the analysis results, a second controller whose wake-up reason is its own wake-up is found from the plurality of controllers.
The management method for network wake-up according to claim 1, further comprising:

In response to the network mode being the pre-sleep mode, obtain residual network management messages on the CAN bus of the controller local network;

Determine the identification code and timestamp of the residual network management message;

A sleep management log is generated based on the residual network management message, the identification code of the residual network management message, and the timestamp of the residual network management message, and the sleep management log is stored in the memory unit.
The management method for network wake-up according to claim 6, further comprising:

In response to the network mode switching to the working mode, the wake-up management log and the sleep management log are sent to the server, so that the server checks whether the electronic device malfunctions according to the wake-up management log and the sleep management log. .
A management device for network wake-up, including:

The detection module (310) is configured to detect the network mode of the network controller;

Determining module (320), configured to determine the type of the network wake-up request when receiving a network wake-up request in response to the network mode being the sleep mode;

The management module (330) is configured to, based on the type of the network wake-up request, control the network wake-up request. Request management to obtain a corresponding wake-up management log, and store the wake-up management log into a memory unit in the network controller.
An electronic device including:

at least one processor (11); and

A memory communicatively connected to the at least one processor (11); wherein,

The memory stores a computer program executable by the at least one processor (11), the computer program is executed by the at least one processor (11), so that the at least one processor (11) can execute The management method of network wake-up according to any one of claims 1 to 7.
A computer-readable storage medium stores computer instructions, and the computer instructions are configured to enable a processor to implement the network wake-up management method described in any one of claims 1 to 7 when executed.