Vehicle forced sleep control method and device and computer program product

Abstract

The invention discloses a vehicle forced dormancy control method and device and a computer program product, and the method comprises the steps: judging whether to switch from an ON gear to an OFF gear or not when the power state of a whole vehicle network is in the OFF gear, and if yes, starting a dormancy monitoring timer by a main node of the whole vehicle network; if not, further judging whether the whole vehicle network is awakened from the dormant state, and if yes, starting a dormant monitoring timer and an abnormal awakening counter; according to the states of the dormancy monitoring timer and the abnormal wake-up counter, the main node judges whether the whole vehicle has a power shortage risk or not in combination with the current function scene of the whole vehicle; if it is judged that the whole vehicle has the power shortage risk, the main node sends a forced dormancy request message to a network segment where an abnormal node is located, and when execution of the forced dormancy request message fails, dormancy awakening abnormity reminding is sent out. By actively monitoring the dormant state of the whole vehicle network, the efficiency of dealing with the power shortage of the whole vehicle is greatly improved.

Description

Technical Field

[0001] The present invention relates to the field of intelligent driving technology, and in particular to a vehicle forced sleep control method, device, and computer program product. Background Art

[0002] With the continuous development of intelligent and connected vehicles, vehicles are becoming increasingly versatile, and the number of functional scenarios that can be implemented in the vehicle's OFF mode is also increasing. If the nodes responsible for these functional scenarios have flaws in their sleep / wakeup strategies, resulting in failure to properly enter low-power mode when the vehicle is in OFF mode or repeated abnormal wakeups when the vehicle is in OFF mode, these nodes may request network connections, causing abnormal sleep of the entire vehicle network and the risk of battery loss. Summary of the Invention

[0003] The technical problem to be solved by the embodiments of the present invention is to provide a vehicle forced sleep control method, device and computer program product to avoid the risk of vehicle power loss caused by nodes not sleeping or abnormal wake-up in OFF gear.

[0004] To solve the above technical problems, the present invention provides a vehicle forced sleep control method, comprising the following steps:

[0005] When the power state of the vehicle network is switched to OFF, it is determined whether it is switched from ON to OFF. If so, the master node of the vehicle network starts the sleep monitoring timer; if not, it is further determined whether the vehicle network is awakened from the sleep state. If so, the sleep monitoring timer and abnormal awakening counter are started;

[0006] The master node determines whether the vehicle is at risk of power shortage based on the status of the sleep monitoring timer and the abnormal wakeup counter and the current functional scenario of the vehicle;

[0007] If it is determined that the vehicle is at risk of low power, the master node sends a forced sleep request message to the network segment where the abnormal node is located, and issues a sleep wake-up abnormality reminder when the forced sleep request message fails to execute.

[0008] Preferably, after the master node sends the forced sleep request message to the network segment where the abnormal node is located, the method further includes:

[0009] If the entire vehicle network has only one level one network, after receiving the forced sleep request message, the slave node first determines whether the node ID in the data field of the forced sleep request message points to itself. If it points to itself, the slave node shields its own unnecessary wake-up sources and enters the sleep process; if it does not point to itself, the forced sleep request message is ignored.

[0010] Preferably, after the master node sends the forced sleep request message to the network segment where the abnormal node is located, the method further includes:

[0011] If there is a secondary network in the vehicle network, after receiving the forced sleep request message, the secondary gateway node first determines whether the forced sleep request message is directed to itself. If it is directed to itself, it further determines whether the abnormality is itself or the connected secondary network node, and performs corresponding operations based on the judgment result; if the secondary gateway node determines that the forced sleep request message is not directed to itself, or is not directed to any node in the secondary network, it ignores the forced sleep request message.

[0012] Preferably, the further determining whether the abnormality is in itself or in the connected secondary network node, and performing corresponding operations according to the determination result, specifically includes:

[0013] If it is an abnormality itself, it will shield its own unnecessary wake-up sources and enter the sleep process; if it is not an abnormality itself, the secondary gateway node will forward the forced sleep message to the secondary network. After the abnormal node in the secondary network receives the forced sleep message, it will shield its own unnecessary wake-up sources and enter the sleep process.

[0014] Preferably, after executing the operations related to the forced sleep request message, the slave node replies with a forced sleep response message to the master node; if the execution fails or the execution result is not fed back, the master node continues to send the forced sleep request message or issues a sleep wake-up exception reminder.

[0015] Preferably, the master node determines whether the vehicle is at risk of power shortage based on the status of the sleep monitoring timer and the abnormal wakeup counter, in combination with the current functional scenario of the vehicle, specifically including:

[0016] When the sleep monitoring timer reaches the sleep monitoring duration threshold, the master node combines the relevant signals sent by the vehicle communication box TBOX, the vehicle control unit VCU, and the battery management system BMS to determine whether the current vehicle is in a functional scenario where it remains awake for a long time; if so, it is determined that there is no risk of low power for the entire vehicle; if not, it is determined that there is a risk of low power for the entire vehicle;

[0017] When the abnormal wake-up counter reaches the abnormal wake-up number threshold, the master node determines that the vehicle is at risk of power shortage.

[0018] Preferably, the functional scenario at least includes: the vehicle is currently undergoing an over-the-air (OTA) upgrade or charging.

[0019] The present invention also provides a vehicle forced sleep control device, comprising:

[0020] The monitoring module is configured to, when the power state of the vehicle network is in the OFF position, determine whether it is switched from the ON position to the OFF position, and if so, start the sleep monitoring timer; if not, further determine whether the vehicle network is awakened from the sleep state, and if so, start the sleep monitoring timer and the abnormal awakening counter;

[0021] a judgment module, communicatively connected to the monitoring module, and configured to judge whether the vehicle has a risk of low power according to the states of the sleep monitoring timer and the abnormal wakeup counter, in combination with the current functional scenario of the vehicle;

[0022] a forced sleep execution module, which is in communication with the judgment module and is configured to send a forced sleep request message to the network segment where the abnormal node is located when the judgment module determines that the vehicle is at risk of low power;

[0023] The reminder module is in communication with the forced sleep execution module and is configured to issue a sleep awakening abnormality reminder when the forced sleep request message fails to execute.

[0024] The present invention also provides a vehicle forced sleep control device, comprising:

[0025] one or more processors;

[0026] Memory;

[0027] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to execute the vehicle forced sleep control method.

[0028] The present invention also provides a computer program product, comprising computer instructions, wherein the computer instructions instruct a computer device to execute operations corresponding to the method.

[0029] The implementation of the present invention has the following beneficial effects: By actively monitoring the sleep state of the entire vehicle network and immediately issuing a forced sleep command upon detecting an anomaly, the present invention enables the abnormal node to automatically execute defined operations and enter a sleep, low-power mode without human intervention. This proactive strategy not only greatly improves the efficiency of responding to vehicle power outages, but also effectively avoids processing delays caused by human factors. This invention not only enhances the vehicle's power management capabilities and reduces the risk of power outages, but also improves the user experience, providing a strong guarantee for the safe and reliable operation of smart vehicles. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0031] Figure 1 The figure is a flow chart of a vehicle forced sleep control method according to an embodiment of the present invention.

[0032] Figure 2 This is a schematic diagram of a specific flow chart of a vehicle forced sleep control method according to an embodiment of the present invention.

[0033] Figure 3 This is a schematic diagram of the definition of a forced sleep request message in an embodiment of the present invention.

[0034] Figure 4 Schematic diagram of the primary and secondary networks of a vehicle in an embodiment of the present invention.

[0035] Figure 5 4 is a schematic diagram of the definition of a forced sleep response message in an embodiment of the present invention. DETAILED DESCRIPTION

[0036] The following descriptions of the embodiments refer to the accompanying drawings to illustrate specific embodiments in which the present invention may be implemented.

[0037] Please refer to Figure 1 As shown, the first embodiment of the present invention provides a vehicle forced sleep control method, comprising the following steps:

[0038] When the power state of the vehicle network is in the OFF position, it is determined whether it is switched from the ON position to the OFF position. If so, the master node of the vehicle network starts the sleep monitoring timer; if not, it is further determined whether the vehicle network is awakened from the sleep state. If so, the sleep monitoring timer and the abnormal awakening counter are started;

[0039] The master node determines whether the vehicle is at risk of power shortage based on the status of the sleep monitoring timer and the abnormal wakeup counter and the current functional scenario of the vehicle;

[0040] If it is determined that the vehicle is at risk of low power, the master node sends a forced sleep request message to the network segment where the abnormal node is located, and issues a sleep wake-up abnormality reminder when the forced sleep request message fails to execute.

[0041] Through the above steps, it can be seen that the present invention can effectively monitor the sleep and wake-up status of the entire vehicle network when the power state of the entire vehicle is switched to OFF, and accurately determine whether there is a risk of power outage. By sending a forced sleep request message to the abnormal node through the master node, the abnormal node can be quickly put into a sleep state to reduce energy consumption. When the forced sleep request fails to execute, a sleep wake-up abnormality reminder is issued in time to ensure vehicle safety. This method can significantly improve the power management level and energy-saving effect of the vehicle, effectively prevent battery power loss caused by abnormal node wake-up, and ensure the normal use of the vehicle.

[0042] Specifically, please combine Figure 2 As shown, in this embodiment, the master node of the vehicle network can be a gateway, or a central domain controller or other vehicle control unit with processing capabilities and communication interfaces. The following describes the embodiment of the present invention using the gateway as the master node as an example.

[0043] In an ignition cycle, when the power state of the vehicle network is in the OFF position, it is first determined whether the vehicle power is switched from the ON position to the OFF position. If so, the gateway, as the master node, starts the sleep monitoring timer Timer; if not, it is necessary to further determine whether the vehicle network is awakened from the sleep state. If so, the master node simultaneously starts the sleep monitoring timer Timer and the vehicle network abnormal wake-up counter Counter.

[0044] It's understandable that the sleep monitoring timer (Timer) primarily monitors the duration of time the vehicle should not be awakened in the OFF gear. For example, under normal circumstances, such as non-OTA upgrades or charging, leaving the vehicle awake for an extended period in the OFF gear may lead to excessive battery drain. The vehicle network abnormal wakeup counter (Counter) counts the number of frequent abnormal wakeups within a short period of time. Even if each wakeup lasts only a short time, frequent wakeups within a short period of time can accelerate battery drain. Therefore, considering both time and frequency can comprehensively reflect whether the vehicle is using power appropriately in the OFF gear, enabling more accurate and timely assessment and response to various situations that could lead to battery drain.

[0045] When the sleep monitoring timer reaches T1 (such as 20 minutes, configurable), the master node combines the relevant signals sent by the vehicle communication box TBOX, vehicle control unit VCU, battery management system BMS and other nodes to determine whether the current vehicle is performing an over-the-air download technology OTA upgrade or vehicle charging and other functional scenarios that require a long time to be implemented in the OFF position. If the vehicle is performing one of these functional scenarios, then even if the sleep monitoring timer has reached T1, the master node will not determine that the entire vehicle is at risk of low power, because these functional scenarios themselves require the vehicle to remain awake for a certain period of time to complete. On the contrary, if the vehicle is not in the functional scenarios mentioned above, that is, the vehicle is not performing OTA upgrades or charging and other operations that require a long time to remain awake, then the master node will determine that the entire vehicle is at risk of low power. This is because in this case, the unnecessary wake-up of the vehicle may consume too much power, thereby increasing the risk of battery low power.

[0046] At the same time, when the abnormal wake-up counter Counter reaches a certain number N1 (such as 20 times, configurable), the master node will also determine that the vehicle is at risk of low power.

[0047] It is understood that the sleep monitoring duration threshold T1 is a configurable parameter and needs to be greater than the time it takes for the vehicle power to switch from ON to OFF, or for the vehicle network to enter sleep after being awakened in OFF mode, under normal circumstances, with a certain margin. The abnormal wakeup count threshold N1 is also a configurable parameter and needs to be able to cover some special operating conditions (such as frequent door opening and closing) caused by users frequently waking up the network, with a certain margin.

[0048] After the master node determines that the vehicle is at risk of power shortage, it sends a forced sleep request message to the network segment where the abnormal node is located. Figure 3 As shown, the forced sleep request message contains the Autosar E2E communication protection field, the node ID and the forced sleep signal.

[0049] After the master node sends a forced sleep request message to the network segment where the abnormal node is located, the slave node's corresponding processing varies depending on the vehicle network layer, as described below:

[0050] (1) If the vehicle network only has a first-level network

[0051] If the entire vehicle network has only one level one network, then after receiving the forced sleep request message from the node, it first determines whether the node ID in the data field of the forced sleep request message (the node ID indicates the target recipient of the message and is consistent with the physical addressing address of the node during diagnosis) points to itself. If it points to itself, the node needs to first shield its own non-essential wake-up sources, and then enter low power mode according to the sleep process; if it does not point to itself, the forced sleep request message is ignored.

[0052] It should be noted that local wake-up sources related to basic vehicle functions such as vehicle entry, starting, and charging are necessary wake-up sources, and the rest are non-essential wake-up sources.

[0053] (2) If the vehicle network has a secondary network

[0054] like Figure 4 As shown, if the vehicle network has a secondary network, that is, the vehicle network has a master node and slave nodes (including a primary network node, a secondary gateway node and a secondary network node). The secondary gateway node connects the master node and the secondary network node.

[0055] After receiving the forced sleep message, the secondary gateway node needs to first determine whether the node ID in the forced sleep request message data field points to itself. If it points to itself, it needs to further determine whether the abnormality is itself or the connected secondary network node.

[0056] The secondary gateway node determines whether it is abnormal by whether it receives the network management message from the secondary network node during the non-sleep period and when it wakes up abnormally. If the secondary gateway node does not receive the network management message from the secondary network node, it is determined that it is abnormal. The secondary gateway node first blocks its own unnecessary wake-up sources and then enters the low-power mode according to the sleep process. If the secondary gateway node receives the network management message from the secondary network node, it is determined that it is not abnormal. The secondary gateway node forwards the forced sleep message to the secondary network. After receiving the forced sleep message, the abnormal node in the secondary network performs the same operation (i.e., first blocks its own unnecessary wake-up sources and then enters the low-power mode according to the sleep process). If the forced sleep request message is not for any node in the secondary network, the secondary gateway node will ignore the forced sleep request message.

[0057] The above process ensures that in the entire vehicle network, whether it is the main node, the first-level network node or the second-level network node, it can be effectively forced to sleep when an abnormal wake-up occurs, thereby reducing the energy consumption of the entire vehicle and reducing the risk of battery depletion.

[0058] After receiving the forced sleep request message and executing the relevant operations, each slave node needs to reply to the master node with a forced sleep response message within a certain time T2 (such as 1s, configurable). The definition of the forced sleep response message is as follows: Figure 5 As shown, the forced sleep response message contains the Autosar E2E communication protection field, the execution result signal, and the execution failure reason signal. If the execution is successful, the master node will no longer send the forced sleep request message. If the slave node fails to execute or does not provide feedback on the execution result, the master node will continue to send forced sleep request messages up to N2 times (e.g., 3 times, configurable). If all slave nodes fail to execute or do not provide feedback, the master node will report the node's sleep wakeup exception N3 times (e.g., 1 time, configurable) to the TBOX and instrument cluster. The TBOX will notify the owner of the vehicle's low battery risk via SMS or app reminders via the TSP backend. The instrument cluster will display a text reminder indicating that the vehicle is at risk of low battery, requiring the owner to intervene to prevent it.

[0059] When the vehicle is re-awakened by the network or local system, or the vehicle power is turned back on, the forced sleep control process is terminated. When the sleep monitoring timer and abnormal wakeup counter reach the threshold, the timing and counting will be restarted after the corresponding operation is performed.

[0060] It should also be noted that in order to avoid driving safety problems caused by the accidental sending of forced sleep request messages during driving, the master node needs to perform functional safety design for the entire link from the generation of the message at the application layer to the sending of the message at the bottom layer to meet the ASIL-B and above functional safety levels, so as to ensure timely detection and response when potential safety risks arise.

[0061] The forced sleep control in the embodiments of the present invention can be turned on and off through diagnostic configuration. That is, vehicle manufacturers or maintenance personnel can configure the vehicle's forced sleep strategy based on actual needs using diagnostic tools. For example, in certain specific circumstances (such as vehicle maintenance and testing), it may be necessary to temporarily disable the forced sleep strategy; however, under normal driving conditions, the strategy should be enabled to ensure driving safety. This configurability provides greater flexibility and convenience, allowing the forced sleep strategy to better adapt to different usage scenarios and needs.

[0062] Corresponding to the vehicle forced sleep control method described in the first embodiment of the present invention, the second embodiment of the present invention further provides a vehicle forced sleep control device, comprising:

[0063] The monitoring module is configured to, when the power state of the vehicle network is in the OFF position, determine whether it is switched from the ON position to the OFF position, and if so, start the sleep monitoring timer; if not, further determine whether the vehicle network is awakened from the sleep state, and if so, start the sleep monitoring timer and the abnormal awakening counter;

[0064] a judgment module, communicatively connected to the monitoring module, and configured to judge whether the vehicle has a risk of low power according to the states of the sleep monitoring timer and the abnormal wakeup counter, in combination with the current functional scenario of the vehicle;

[0065] a forced sleep execution module, which is in communication with the judgment module and is configured to send a forced sleep request message to the network segment where the abnormal node is located when the judgment module determines that the vehicle is at risk of low power;

[0066] The reminder module is in communication with the forced sleep execution module and is configured to issue a sleep awakening abnormality reminder when the forced sleep request message fails to execute.

[0067] Corresponding to the vehicle forced sleep control method described in the first embodiment of the present invention, the third embodiment of the present invention further provides a vehicle forced sleep control device, comprising:

[0068] one or more processors;

[0069] Memory;

[0070] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to execute the vehicle forced sleep control method.

[0071] Corresponding to the vehicle forced sleep control method described in the aforementioned embodiment 1 of the present invention, the fourth embodiment of the present invention further provides a computer program product, including computer instructions, which instruct a computer device to execute operations corresponding to the method.

[0072] Preferably, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor. The processor is the control center of the device, and various parts of the device are connected using various interfaces and lines.

[0073] The memory mainly includes a program storage area and a data storage area, wherein the program storage area can store an operating system, an application program required for at least one function, etc., and the data storage area can store related data, etc. In addition, the memory can be a high-speed random access memory, or a non-volatile memory, such as a plug-in hard disk, a smart memory card (SmartMedia Card, SMC), a secure digital (Secure Digital, SD) card, and a flash card, etc., or the memory can also be other volatile solid-state storage devices.

[0074] It should be noted that the above-mentioned device may include but is not limited to a processor and a memory, which can be understood by those skilled in the art.

[0075] For the working principle and process of the above embodiment, please refer to the description of the above embodiment of the present invention, which will not be repeated here.

[0076] It can be seen from the above description that compared with the prior art, the beneficial effect of the present invention is that: the present invention actively monitors the sleep state of the entire vehicle network, and once an abnormality is found, it immediately issues a forced sleep instruction, so that the abnormal node can automatically execute the defined operations and enter the sleep low-power mode without human intervention. This proactive strategy not only greatly improves the efficiency of dealing with vehicle power outages, but also effectively avoids processing delays caused by human factors. The present invention not only enhances the power management capabilities of the entire vehicle and reduces the risk of power outages, but also improves the user experience, providing a strong guarantee for the safe and reliable operation of smart vehicles.

[0077] The above disclosure is merely a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.

Claims

1. A vehicle forced sleep control method, characterized in that: The following steps are involved: When the power state of the vehicle network is in the OFF position, it is determined whether it is switched from the ON position to the OFF position. If so, the master node of the vehicle network starts the sleep monitoring timer; if not, it is further determined whether the vehicle network is awakened from the sleep state. If so, the sleep monitoring timer and the abnormal awakening counter are started; The master node determines whether the vehicle is at risk of power shortage based on the status of the sleep monitoring timer and the abnormal wakeup counter and the current functional scenario of the vehicle; If it is determined that the vehicle is at risk of low power, the master node sends a forced sleep request message to the network segment where the abnormal node is located, and issues a sleep wake-up abnormality reminder when the forced sleep request message fails to execute.

2. The method according to claim 1, characterized in that After the master node sends a forced sleep request message to the network segment where the abnormal node is located, the method further includes: If the entire vehicle network has only one level one network, after receiving the forced sleep request message, the slave node first determines whether the node ID in the data field of the forced sleep request message points to itself. If it points to itself, the slave node shields its own unnecessary wake-up sources and enters the sleep process; if it does not point to itself, the forced sleep request message is ignored.

3. The method according to claim 1, characterized in that After the master node sends a forced sleep request message to the network segment where the abnormal node is located, the method further includes: If there is a secondary network in the vehicle network, after receiving the forced sleep request message, the secondary gateway node first determines whether the forced sleep request message is directed to itself. If it is directed to itself, it further determines whether the abnormality is itself or the connected secondary network node, and performs corresponding operations based on the judgment result; if the secondary gateway node determines that the forced sleep request message is not directed to itself, or is not directed to any node in the secondary network, it ignores the forced sleep request message.

4. The method according to claim 3, characterized in that The further determination of whether the abnormality is in itself or in the connected secondary network node, and performing corresponding operations according to the determination result, specifically includes: If it is an abnormality itself, it will shield its own unnecessary wake-up sources and enter the sleep process; if it is not an abnormality itself, the secondary gateway node will forward the forced sleep message to the secondary network. After the abnormal node in the secondary network receives the forced sleep message, it will shield its own unnecessary wake-up sources and enter the sleep process.

5. The method according to any one of claims 2 to 4, characterized in that: After executing the operations related to the forced sleep request message, the slave node replies with a forced sleep response message to the master node; if the execution fails or no execution result is fed back, the master node continues to send forced sleep request messages or issues a sleep wake-up exception reminder.

6. The method according to claim 1, characterized in that The master node determines whether the vehicle has a power shortage risk based on the status of the sleep monitoring timer and the abnormal wakeup counter, combined with the current functional scenario of the vehicle, specifically including: When the sleep monitoring timer reaches the sleep monitoring duration threshold, the master node combines the relevant signals sent by the vehicle communication box TBOX, the vehicle control unit VCU, and the battery management system BMS to determine whether the current vehicle is in a functional scenario where it remains awake for a long time; if so, it is determined that there is no risk of low power for the entire vehicle; if not, it is determined that there is a risk of low power for the entire vehicle; When the abnormal wake-up counter reaches the abnormal wake-up number threshold, the master node determines that the vehicle is at risk of power shortage.

7. The method according to claim 6, characterized in that The functional scenario at least includes: the vehicle is currently undergoing an over-the-air (OTA) upgrade or charging.

8. A vehicle forced sleep control device, characterized in that: include: The monitoring module is configured to, when the power state of the vehicle network is in the OFF position, determine whether it is switched from the ON position to the OFF position, and if so, start the sleep monitoring timer; if not, further determine whether the vehicle network is awakened from the sleep state, and if so, start the sleep monitoring timer and the abnormal awakening counter; a judgment module, communicatively connected to the monitoring module, and configured to judge whether the vehicle has a risk of low power according to the states of the sleep monitoring timer and the abnormal wakeup counter, in combination with the current functional scenario of the vehicle; a forced sleep execution module, which is in communication with the judgment module and is configured to send a forced sleep request message to the network segment where the abnormal node is located when the judgment module determines that the vehicle is at risk of low power; The reminder module is in communication with the forced sleep execution module and is configured to issue a sleep awakening abnormality reminder when the forced sleep request message fails to execute.

9. A vehicle forced sleep control device, characterized in that: include: one or more processors; Memory; One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to execute the vehicle forced sleep control method according to any one of claims 1 to 7.

10. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions instruct a computer device to perform operations corresponding to the method according to any one of claims 1 to 7.

Images