Data retransmission method, system, device and cluster
By sending a keep-alive message to the second device before the automatic retransmission timer timed out, and obtaining a confirmation message to determine the next data packet number to be sent, the data retransmission delay problem caused by the network card queue failure of the first device is solved. Improve communication efficiency.
Patent Information
- Application Number
- CN202410940310.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-15
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2044-07-15
AI Technical Summary
When the network card queue of the first device fails, data retransmission requires waiting for queue reset and automatic retransmission timer to time out, resulting in delay.
Data retransmission is initiated in advance by sending a keep-alive message to the second device before the automatic retransmission timer timed out, and acknowledge message is obtained to determine the next packet number to be sent.
Reduces data retransmission delay, improves communication efficiency, and avoids waiting time for timer timeout.
Smart Images

Figure CN118487725B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communications, and in particular to a data retransmission method, system, device and cluster. Background Art
[0002] The first device and the second device can transmit messages via the Transmission Control Protocol (TCP). If a queue in the network card in the first device fails, the queue in the network card in the first device can be reset. However, during the queue reset process, data between the first device and the second device cannot be transmitted.
[0003] In the case of a queue failure in the first device, the time for starting the first device to retransmit data needs to consider not only the time for resetting the queue of the first device, but also the time of the automatic retransmission timer of the first device. That is, if the time of the automatic retransmission timer of the first device is greater than the time consumed by the queue reset, then even after the queue in the first device is reset, it is necessary to wait until the automatic retransmission timer of the first device times out before automatic retransmission is performed. Summary of the invention
[0004] The present application provides a data retransmission method, system, device and cluster, which can start data retransmission before the automatic retransmission timer times out.
[0005] In a first aspect, a data retransmission method is provided, which is applied to a first device and includes:
[0006] Sending a first data packet to the second device through the network card, wherein the source address of the first data packet is a first source address, the destination address of the first data packet is a first destination address, and the packet sequence number of the first data packet is a first packet sequence number;
[0007] Starting an automatic retransmission timer to reset the queue in the network card;
[0008] After the queue in the first device is reset, and before the automatic retransmission timer times out, sending a keep-alive message to the second device multiple times, wherein the source address of the keep-alive message is the first source address, the destination address of the keep-alive message is the first destination address, and the keep-alive message includes the first packet sequence number;
[0009] receiving a first confirmation message sent by the second device multiple times, wherein the first confirmation message is sent by the second device when the second device receives a keep-alive message, and the first confirmation message includes the first packet sequence number;
[0010] The first data packet is repeatedly sent to the second device through the network card based on the first packet sequence numbers in multiple first confirmation messages.
[0011] Because before the automatic retransmission timer times out, the keep-alive message can be sent to the second device multiple times, after the second device receives the keep-alive message from the first device, it will send a second confirmation message to the first device. The first device can learn the packet sequence number of the next data packet to be sent from the second confirmation message, and immediately start automatic retransmission. Therefore, it is necessary to wait until the automatic retransmission timer times out before automatic retransmission can be performed.
[0012] In some possible designs, before sending the first data packet to the second device through the network card, the method further includes:
[0013] A second data packet is sent to a second device through the network card, and a second confirmation message sent by the second device based on the second data packet is received, wherein the second data packet includes a second packet sequence number, the second confirmation message includes a first packet sequence number, and the second packet sequence number is equal to the first packet sequence number minus the load length of the second data packet.
[0014] In some possible designs, before sending the keep-alive message to the second device multiple times, the method further includes:
[0015] Obtaining the first source address, the first destination address, and the first packet sequence number;
[0016] The keep-alive message is generated based on the first source address, the first destination address, and the first packet sequence number.
[0017] In some possible designs, obtaining the first source address, the first destination address, and the first packet sequence number includes:
[0018] Acquire the first source address and the first destination address from the first data packet;
[0019] According to the first source address and the first destination address, a hash table is searched to obtain the first packet sequence number;
[0020] The keep-alive message is generated based on the first source address, the first destination address, and the first packet sequence number.
[0021] In some possible designs, after receiving the second confirmation message, the method further includes:
[0022] Obtain the first source address and the first destination address from the second data packet, and obtain the first packet sequence number from the second confirmation message;
[0023] The first source address, the first destination address, and the first packet sequence number are associated and stored in the hash table.
[0024] In some possible designs, the payload in the keep-alive message has a length of zero.
[0025] In some possible designs, the keep-alive message is sent four times.
[0026] In a second aspect, a data retransmission system is provided.
[0027] A first device, used to send a first data packet to a second device through a network card, wherein a source address of the first data packet is a first source address, a destination address of the first data packet is a first destination address, and a packet sequence number of the first data packet is a first packet sequence number;
[0028] The first device is further used to start an automatic retransmission timer to reset the queue in the network card;
[0029] The first device is further configured to send a keep-alive message to the second device multiple times after the queue in the first device is reset and before the automatic retransmission timer times out, wherein the source address of the keep-alive message is the first source address, the destination address of the keep-alive message is the first destination address, and the keep-alive message includes the first packet sequence number;
[0030] The second device is configured to send a first confirmation message to the first device multiple times when receiving multiple keep-alive messages, wherein the first confirmation message includes the first packet sequence number;
[0031] The first device is further configured to repeatedly send the first data packet to the second device through the network card based on first packet sequence numbers in multiple first confirmation messages.
[0032] According to a third aspect, a computing device is provided, comprising a processor and a memory, wherein the memory is used to store instructions, and when the instructions are executed by the processor, they are used to implement the method described in any one of the first aspects.
[0033] In a fourth aspect, a computing device cluster is provided, comprising at least one computing device, wherein the computing device comprises a processor and a memory, wherein the memory is used to store instructions, and when the instructions are executed by the processor, they are used to implement the method as described in any one of the first aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the background technology, the drawings required for use in the embodiments of the present invention or the background technology will be described below.
[0035] Figure 1 It is a structural diagram of a data retransmission system provided by the present application;
[0036] Figure 2 It is a flowchart of a data retransmission method provided by the present application;
[0037] Figure 3 It is a structural schematic diagram of a computing device provided by this application. DETAILED DESCRIPTION
[0038] The embodiments of the present invention are described below in conjunction with the accompanying drawings in the embodiments of the present invention. The terms used in the implementation mode of the present invention are only used to explain the specific embodiments of the present invention, and are not intended to limit the present invention.
[0039] See also Figure 1 , Figure 1 Schematic diagram of the structure of a data retransmission system provided by this application. Figure 1 As shown, the data retransmission system of the present application includes: a first device 110 and a second device 120.
[0040] The first device 110 can be any one of a terminal or a computing device. Among them, the terminal includes a personal computer, a smart phone, a wearable device, a handheld processing device, a tablet computer, a mobile notebook, an augmented reality (AR) device, a virtual reality (VR) device, an intelligent conference device, etc., which are not specifically limited here. The computing device can be a bare metal server (BMS), a virtual machine, a container or a storage device. BMS refers to a general physical server, such as an ARM server or an X86 server; a virtual machine refers to a complete computer system with complete hardware system functions and running in a completely isolated environment simulated by software. The work that can be done in a physical computer can be achieved in a virtual machine. When creating a virtual machine in a computing device, part of the hard disk and memory capacity of the physical machine needs to be used as the hard disk and memory capacity of the virtual machine. Each virtual machine has an independent basic input / output system (BIOS), hard disk, and operating system, and can be operated like a physical machine. A container is a portable software unit that combines an application and all its dependencies into a single software package that is not restricted by the underlying host operating system. This eliminates the need to build a complex environment, simplifying the process from application development to deployment.
[0041] The second device 120 can be any one of a terminal or a computing device. For an introduction to the terminal and the computing device, please refer to the relevant description. The first device 110 and the second device 120 can be the same type of device or different types of devices. For example, when the first device 110 and the second device 120 are the same type of devices, the first device 110 and the second device 120 can both be terminals or can both be computing devices; when the first device 110 and the second device 120 are different types of devices, the first device can be a terminal and the second device can be a computing device; or, the first device can be a computing device and the second device can be a terminal.
[0042] See also Figure 2 , Figure 2 is a flow chart of a data retransmission method provided by this application. Figure 2 As shown, the data retransmission method of the present application may include:
[0043] S101: A first device sends a first data packet to a second device via a network card. Correspondingly, the second device receives the first data packet sent by the first device.
[0044] The first data packet may be any data packet in a data stream. A data stream is a series of continuous data packets sent by a first device to a second device. For example, if a data stream to be sent by a first device to a second device includes 100 data packets, then the first data packet may be any data packet in the data stream.
[0045] The first data packet includes a first source address, a first destination address, and a first packet sequence number. The first source address includes one or more of a source MAC address, a source IP address, and a source port number. The first destination address includes one or more of a destination MAC address, a destination IP address, and a destination port number. The first packet sequence number is the sequence number of the first data packet in the data stream.
[0046] S102: The second device sends a first confirmation message to the first device based on the first data packet. Correspondingly, the first device receives the first confirmation message sent by the second device based on the first data packet.
[0047] The first confirmation message is used to indicate that the second device successfully receives the first data packet sent by the first device. The first confirmation message includes a second source address, a second destination address, and a second packet sequence number. Among them, the second source MAC address includes one or more of the source MAC address, the source IP address, and the source port number. The second destination address includes one or more of the destination MAC address, the destination IP address, and the destination port number. The source address of the first confirmation message is the destination address of the first data packet, and the destination address of the first confirmation message is the source address of the first data packet. The second packet sequence number is equal to the first packet sequence number plus the payload length of the first data packet. The second packet sequence number is used to indicate the sequence number of the data packet expected to be received.
[0048] S103: The first device obtains the first source address and the first destination address from the first data packet, and obtains the second packet sequence number from the first confirmation message.
[0049] S104: The first device associates and stores the first source address, the first destination address, and the second packet sequence number in a hash table.
[0050] The hash table can be used to store multiple records, each record includes a key and a value. The key is used to store the source address and the destination address, and the value is used to store the packet sequence number. The number of records in the hash table can be the same as or close to the number of queues in the network card. Therefore, after obtaining the first source address and the first destination address of the first data packet and obtaining the second packet sequence number from the first confirmation message, the first source address and the first destination address can be used as the key and the second packet sequence number can be used as the value to store in a record of the hash table.
[0051] Since resources are limited, the number of records maintained in the hash table is also limited. Assuming that the maximum number of records in the hash table is set to m, if the number of records in the hash table is less than m, then the first source address and the first destination address can be directly used as keys and the second packet sequence number can be used as values to store them in a record in the hash table; if the number of records in the hash table is equal to m, then delete the record with the longest time from the current time, and then use the first source address and the first destination address as keys and the second packet sequence number as values to store them in the record in the hash table. In addition, you can also set a priority level for each record in the hash table, then delete the record with the lowest priority level, and then use the first source address and the first destination address as keys and the second packet sequence number as values to store them in the record in the hash table.
[0052] S105: The first device sends a second data packet to the second device via the network card. Correspondingly, the second device receives the second data packet sent by the first device.
[0053] The second data packet includes the next data packet of the first data packet in the data stream. The first packet sequence number in the first data packet is 50, and the payload length of the first data packet is 15, then the second packet sequence number in the second data packet is 65.
[0054] The second data packet includes the first source address, the first destination address, and the second packet sequence number. For the introduction of the first source address, the first destination address, and the second packet sequence number, please refer to the above.
[0055] S106: The first device starts an automatic retransmission timer to reset the queue in the network card.
[0056] After the first device sends the second data packet, it starts the automatic retransmission timer. The length of time for the automatic retransmission timer depends on the specific protocol implementation and network conditions. In the TCP protocol, this time is usually dynamically calculated based on the round-trip time (RTT). For example, an initial value can be set for the automatic retransmission time, and it will be dynamically adjusted with each transmission. The initial value may be between 4 and 10 minutes, but in practice it is rarely necessary to have such a long time because TCP will adjust this initial value according to network conditions. Alternatively, the automatic retransmission time is a preset fixed value. If the sender does not receive an acknowledgment within the timeout period, it will retransmit the data. This time needs to be slightly longer than the average round-trip time for data transmission.
[0057] During this time limit, if the network card fails, the queue in the network card needs to be reset. During the reset period, the communication between the first device and the second device will be interrupted, so the second data packet sent by the first device to the second device will be lost. Since the reset time may be shorter than the automatic retransmission time, the network card has been reset before the automatic retransmission timer expires. However, the automatic retransmission timer has not expired and has not triggered retransmission.
[0058] S107: After the queue in the first device is reset, and before the automatic retransmission timer times out, the first device sends keep-alive messages to the second device multiple times.
[0059] The source address of the keep-alive message is the first source address, the destination address is the first destination address, and the keep-alive message includes a second packet sequence number. Before sending the keep-alive message to the second device multiple times, it is necessary to generate a keep-alive message. Specifically, the process of generating the keep-alive message can be: obtaining the first source address and the first destination address from the second data packet, and searching the hash table according to the first source address and the first destination address to obtain the second packet sequence number. Then, the keep-alive message is generated with the first source address, the first destination address, and the second packet sequence number. Since the keep-alive message is due to triggering the second device to send the second confirmation message, the keep-alive message does not need to carry unnecessary messages, thereby reducing the consumption of transmission bandwidth. Therefore, the length of the load in the keep-alive message can be zero. Of course, the load in the keep-alive message can also be used to carry some messages.
[0060] The first device sends a keep-alive message to the second device multiple times. The multiple times can be 2 times, 3 times, 4 times, 5 times or more times, which can be set as needed. In addition, the time interval for sending the keep-alive message can be set as needed, for example, it can be set to an interval of 10 milliseconds, 20 milliseconds, 100 milliseconds, 200 milliseconds, 1 second, 2 seconds, etc., which is not specifically limited here.
[0061] S108: The second device sends a second confirmation message to the first device multiple times. Correspondingly, the first device receives the second confirmation message sent multiple times by the second device.
[0062] The second confirmation message is sent by the second device after receiving the keep-alive message. When the first device sends the same number of keep-alive messages to the second device, the second device sends the same number of second confirmation messages to the first device. The second confirmation message includes the second packet sequence number. Therefore, after receiving the second confirmation message, the first device can determine that the second data packet needs to be retransmitted.
[0063] S109: The first device repeatedly sends the second data packet to the second device via the network card based on the second packet sequence number in the second confirmation message. Accordingly, the second device receives the second data packet repeatedly sent by the first device via the network card based on the second packet sequence number in the second confirmation message.
[0064] After receiving the plurality of second confirmation messages, the first device determines from the second confirmation message that the sequence number of the data packet to be retransmitted is the second data packet corresponding to the second packet sequence number. Therefore, the first device repeatedly sends the second data packet to the second device through the network card based on the second packet sequence number in the second confirmation message.
[0065] Because before the automatic retransmission timer times out, the keep-alive message can be sent to the second device multiple times, after the second device receives the keep-alive message from the first device, it will send a second confirmation message to the first device. The first device can learn the packet sequence number of the next data packet to be sent from the second confirmation message, and immediately start automatic retransmission. Therefore, it is necessary to wait until the automatic retransmission timer times out before automatic retransmission can be performed.
[0066] See also Figure 3 , Figure 3 4 is a schematic diagram of a computing device provided by the present application. The computing device 400 includes: one or more processing units 410 , a communication interface 420 and a memory 430 .
[0067] The processing unit 410, the communication interface 420 and the memory 430 are interconnected via a bus 440. Optionally, the computing device 400 may also include an input / output interface 450, which is connected to an input / output device for receiving parameters set by a user, etc. The computing device 400 can be used to implement part or all of the functions of the device embodiment or system embodiment in the above-mentioned embodiment of the present application; the processing unit 410 can also be used to implement part or all of the operation steps of the method embodiment in the above-mentioned embodiment of the present application. For example, the specific implementation of the various operations performed by the computing device 400 can refer to the specific details in the above-mentioned embodiment, such as the processing unit 410 is used to perform part or all of the steps in the above-mentioned method embodiment or part or all of the operations in the above-mentioned method embodiment. For another example, in the embodiment of the present application, the computing device 400 can be used to implement part or all of the functions of one or more components in the above-mentioned device embodiment, and the communication interface 420 can be specifically used for the communication functions necessary to implement the functions of these devices and components, and the processing unit 410 can be specifically used for the processing functions necessary to implement the functions of these devices and components, etc.
[0068] Figure 3 The computing device 400 may include one or more processing units 410, and the multiple processing units 410 may provide processing capabilities in a coordinated manner in a parallel connection manner, a serial connection manner, a serial-parallel connection manner, or any connection manner, or the multiple processing units 410 may constitute a processor sequence or a processor array, or the multiple processing units 410 may be divided into a main processor and an auxiliary processor, or the multiple processing units 410 may have different architectures such as a heterogeneous computing architecture. In addition, Figure 3 The computing device 400 shown in the figure, and the related structural description and functional description are exemplary and non-limiting. In some exemplary embodiments, the computing device 400 may include Figure 3More or fewer components may be shown, or some components may be combined or separated, or may have a different arrangement of components.
[0069] The processing unit 410 may have a variety of specific implementation forms. For example, the processing unit 410 may include a central processing unit (CPU), a graphic processing unit (GPU), a neural-network processing unit (NPU), a tensor processing unit (TPU) or a data processing unit (DPU), etc., and the embodiment of the present application does not specifically limit it. The processing unit 410 may also be a single-core processor or a multi-core processor. The processing unit 410 may be a combination of a CPU and a hardware chip. The above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. The processing unit 410 may also be implemented using a logic device with built-in processing logic alone, such as an FPGA or a digital signal processor (DSP). The communication interface 420 may be a wired interface or a wireless interface for communicating with other modules or devices. The wired interface may be an Ethernet interface, a local interconnect network (LIN), etc., and the wireless interface may be a cellular network interface or a wireless local area network interface, etc.
[0070] The memory 430 may be a non-volatile memory, such as a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The memory 430 may also be a volatile memory, which may be a random access memory (RAM) used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous connection dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). The memory 430 may also be used to store program codes and data, so that the processing unit 410 calls the program codes stored in the memory 430 to execute some or all of the operation steps in the above method embodiment, or to execute the corresponding functions in the above device embodiment. Figure 3 Show more or fewer components, or have different component configurations.
[0071] The bus 440 may be a peripheral component interconnect express (PCIe) bus, an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The bus 440 may be divided into an address bus, a data bus, a control bus, etc. In addition to the data bus, the bus 440 may also include a power bus, a control bus, and a status signal bus, etc. However, for the sake of clarity, Figure 3 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0072] The present application also provides a system, which includes multiple computing devices, and the structure of each computing device can refer to the structure of the computing device described above. The functions or operations that can be implemented by the system can refer to the specific implementation steps in the above method embodiment and / or the specific functions described in the above device embodiment, which will not be repeated here.
[0073] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one network site, computer, server or data center to another network site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer, or it can be a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape, etc.), an optical medium (e.g., a DVD, etc.), or a semiconductor medium (e.g., a solid-state hard disk), etc.
[0074] In the above embodiments, the description of each embodiment has different emphases. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
Claims
1. A data retransmission method, characterized in that: Applied to a first device, comprising: Sending a first data packet to the second device through the network card, wherein the source address of the first data packet is a first source address, the destination address of the first data packet is a first destination address, and the packet sequence number of the first data packet is a first packet sequence number; Starting an automatic retransmission timer to reset the queue in the network card; After the queue in the first device is reset, and before the automatic retransmission timer times out, sending a keep-alive message to the second device multiple times, wherein the source address of the keep-alive message is the first source address, the destination address of the keep-alive message is the first destination address, and the keep-alive message includes the first packet sequence number; receiving a first confirmation message sent by the second device multiple times, wherein the first confirmation message is sent by the second device when the second device receives a keep-alive message, and the first confirmation message includes the first packet sequence number; The first data packet is repeatedly sent to the second device based on the first packet sequence numbers in multiple first confirmation messages through the network card.
2. The method according to claim 1, characterized in that Before sending the first data packet to the second device through the network card, the method further includes: A second data packet is sent to a second device through the network card, and a second confirmation message sent by the second device based on the second data packet is received, wherein the second data packet includes a second packet sequence number, the second confirmation message includes a first packet sequence number, and the second packet sequence number is equal to the first packet sequence number minus the load length of the second data packet.
3. The method according to claim 2, characterized in that Before sending the keep-alive message to the second device multiple times, the method further includes: Obtaining the first source address, the first destination address, and the first packet sequence number; The keep-alive message is generated based on the first source address, the first destination address, and the first packet sequence number.
4. The method according to claim 3, characterized in that Acquiring the first source address, the first destination address, and the first packet sequence number includes: Acquire the first source address and the first destination address from the first data packet; According to the first source address and the first destination address, a hash table is searched to obtain the first packet sequence number; The keep-alive message is generated based on the first source address, the first destination address, and the first packet sequence number.
5. The method according to claim 4, characterized in that After receiving the second confirmation message, the method further includes: Obtain the first source address and the first destination address from the second data packet, and obtain the first packet sequence number from the second confirmation message; The first source address, the first destination address, and the first packet sequence number are associated and stored in the hash table.
6. The method according to any one of claims 1 to 5, characterized in that: The payload length in the keep-alive message is zero.
7. The method according to any one of claims 1 to 5, characterized in that: The keep-alive message is sent 4 times.
8. A data retransmission system, characterized in that: A first device, used to send a first data packet to a second device through a network card, wherein a source address of the first data packet is a first source address, a destination address of the first data packet is a first destination address, and a packet sequence number of the first data packet is a first packet sequence number; The first device is further used to start an automatic retransmission timer to reset the queue in the network card; The first device is further configured to send a keep-alive message to the second device multiple times after the queue in the first device is reset and before the automatic retransmission timer times out, wherein the source address of the keep-alive message is the first source address, the destination address of the keep-alive message is the first destination address, and the keep-alive message includes the first packet sequence number; The second device is configured to send a first confirmation message to the first device multiple times when receiving multiple keep-alive messages, wherein the first confirmation message includes the first packet sequence number; The first device is further configured to repeatedly send the first data packet to the second device through the network card based on first packet sequence numbers in multiple first confirmation messages.
9. A computing device, characterized in that The method comprises a processor and a memory, wherein the memory is used to store instructions, and when the instructions are executed by the processor, they are used to implement the method according to any one of claims 1 to 7.
10. A computing device cluster, characterized in that: The method comprises at least one computing device, wherein the computing device comprises a processor and a memory, wherein the memory is used to store instructions, and when the instructions are executed by the processor, they are used to implement the method according to any one of claims 1 to 7.
