Data transmission method and apparatus, communication device, and storage medium

Abstract

The embodiment of the present application provides a data transmission method, wherein, in the case that a first link between a first node and a second node supports transmission of a data packet of a first MTU length, the first node transmits the data packet based on the first MTU length on the first link, and the second node is used for unloading the data packet transmitted on the first link. The embodiment of the present application also provides a data transmission device, a communication device and a storage medium.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a data transmission method and apparatus, communication equipment, and storage medium. Background Technology

[0002] With the development of electronic technology, the processor architecture of electronic devices is becoming more and more complex. Various high-speed transceivers can be integrated into electronic devices, such as wireless Fidelity radio frequency communication and modems for 4G and 5G mobile communication technologies.

[0003] Currently, the peak communication rate requirement for 5G systems is 20 Gbit / s downlink and 10 Gbit / s uplink. Moreover, when these rates are applied to electronic devices, it is desirable for the power consumption of the electronic devices to be within an acceptable range, which has become one of the challenges in the design of electronic device chips. Summary of the Invention

[0004] This application provides a data transmission method and apparatus, a communication device, and a storage medium.

[0005] The technical solution of this application is implemented as follows:

[0006] In a first aspect, embodiments of this application provide a data transmission method applied to a first node, the method comprising:

[0007] When the first link between the first node and the second node supports the transmission of data packets with a first maximum transmission unit (MTU) length, data packets are transmitted on the first link based on the first MTU length, and the second node is used to offload the data packets transmitted on the first link.

[0008] Secondly, embodiments of this application provide a data transmission apparatus applied to a first node, the apparatus comprising:

[0009] The sending unit is configured to transmit data packets on the first link based on the first MTU length, provided that the first link between the first node and the second node supports the transmission of data packets with a first maximum transmission unit (MTU) length; the second node is used to offload the data packets transmitted on the first link.

[0010] Thirdly, embodiments of this application provide a communication device, including a processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to perform the method described in the first aspect above.

[0011] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect. Attached Figure Description

[0012] Figure 1 A schematic diagram of a data transmission principle provided in an embodiment of this application;

[0013] Figure 2 This is a schematic diagram of a data packet structure provided in an embodiment of this application;

[0014] Figure 3 A schematic diagram illustrating the principle of TSO data segmentation provided in this application embodiment;

[0015] Figure 4 A schematic diagram illustrating the principle of GSO data segmentation provided in this application embodiment;

[0016] Figure 5 A schematic diagram of a data receiving principle provided in an embodiment of this application;

[0017] Figure 6 This application provides a schematic diagram of an LRO data receiving principle.

[0018] Figure 7 This application provides a schematic diagram of a GRO data receiving principle.

[0019] Figure 8 A schematic diagram of an air interface protocol stack structure provided in an embodiment of this application;

[0020] Figure 9 A schematic flowchart of a data transmission method provided in this application embodiment. Figure 1 ;

[0021] Figure 10A A schematic flowchart of a data transmission method provided in this application embodiment. Figure 2 ;

[0022] Figure 10B A schematic flowchart of a data transmission method provided in this application embodiment. Figure 3 ;

[0023] Figure 11A A schematic flowchart of a data transmission method provided in this application embodiment. Figure 4 ;

[0024] Figure 11B A schematic flowchart of a data transmission method provided in this application embodiment. Figure 5 ;

[0025] Figure 12A schematic flowchart of a data transmission method provided in this application embodiment. Figure 6 ;

[0026] Figure 13 A schematic flowchart of a data transmission method provided in this application embodiment. Figure 7 ;

[0027] Figure 14 This is a schematic diagram of the structural composition of a data transmission device 1400 provided in an embodiment of this application;

[0028] Figure 15 This is a schematic structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0029] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0030] It should be understood that the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that the "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. The "predefined" or "predefined rule" mentioned in the embodiments of this application can be implemented by pre-saving corresponding codes, tables, or other methods that can be used to instruct relevant information in the device. This application does not limit the specific implementation method. For example, a predefined rule can refer to one defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0031] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0032] When sending or receiving large data packets at the application layer, the large data packets will be segmented into multiple smaller packets that do not exceed the Maximum Transmission Unit (MTU) when passing through the operating system kernel protocol stack.

[0033] refer to Figure 1 The diagram illustrates the data transmission principle. Application layer data, after passing through the Transmission Control Protocol (TCP) stack, is segmented into multiple data packets conforming to TCP processing requirements, with a TCP header added to each packet. Furthermore, these multiple data packets with added TCP headers, when passing through the Internet Protocol (IP) stack, are also segmented and have IP headers added. These multiple data packets with added IP headers, when passing through the Ethernet protocol stack, are segmented or merged, resulting in multiple data packets with added Ethernet headers. After this processing, the data packets are sent to other devices in the network via the network card driver and the network card itself.

[0034] MTU refers to the maximum load at the data link layer, which is set by the hardware network interface card (NIC). (See reference) Figure 2 As shown, the MTU typically includes the IP header and TCP header, but excludes Ethernet header and trailer data. Understandably, the size of data packets sent by a network interface card (NIC) is limited to the MTU.

[0035] Combination Figure 1 As can be seen, segmentation operations consume significant CPU resources. Offload technology can optimize these segmentation and merging processes. In practical applications, offload operations can be performed through the network interface card (NIC), and most electronic devices currently support this NIC offload technology.

[0036] TCP Segmentation Offload (TSO) is a technique that uses the network interface card (NIC) to segment large data packets, thereby reducing CPU load. TSO requires the NIC to support segmentation functionality. (See reference...) Figure 3 The diagram illustrates a TSO data segmentation principle. Application layer data packets passing through the TCP, IP, and Ethernet protocol stacks can be segmented without further segmentation, only requiring header appending. However, when passing through the hardware network interface card (NIC), the NIC segments the data packets using its hardware functionality. Hardware-based segmentation is more efficient.

[0037] Another segmented offload technique is Generic Segmentation Offload (GSO), in which GSO can perform segmentation without hardware support. (See reference) Figure 4The diagram illustrates a GSO data segmentation principle. Application layer data packets can pass through the TCP, IP, and Ethernet protocol stack without being segmented; only header addition is performed. Before the data packets with added TCP, IP, and Ethernet headers enter the network interface card (NIC), the NIC driver performs segmentation.

[0038] The GSO process includes: first, checking if the network interface card (NIC) supports TSO (Transmission of Separate Segments). If the NIC supports TSO, it uses its hardware segmentation capability to perform segmentation; if the NIC does not support TSO, segmentation is delayed until just before the data is pushed to the NIC. In other words, if the hardware NIC does not support segmentation, GSO can be used for segmentation. GSO allows data packets to cross the IP and data link layers, segmenting them before they leave the protocol stack and enter the NIC driver. Furthermore, GSO is more efficient than TSO in TCP retransmission situations. Whether using TCP or UDP, each segmented packet has a TCP / UDP header appended, so if a segment is lost, the entire TCP / UDP packet does not need to be sent. Secondly, CPU consumption along the path is reduced, so GSO can be considered an improvement over TSO.

[0039] The above describes the data packet sending process. The following describes the data packet receiving process.

[0040] refer to Figure 5 The diagram illustrates a data reception principle. Typically, the network interface card (NIC) sends multiple data packets to its driver. The NIC driver then forwards these packets to the Ethernet protocol stack. The Ethernet protocol stack removes the Ethernet headers from the data packets and sends them to the IP protocol stack. The IP protocol stack then removes the IP headers from the data packets and sends them to the TCP protocol stack. Finally, the TCP protocol stack removes the TCP headers from the received data packets and merges the header-removed data to obtain the complete data.

[0041] In practical applications, refer to Figure 6 The diagram illustrates an LRO (Large Receive Offload) data reception principle. To reduce CPU resource consumption, the network interface card (NIC) can merge multiple data packets into a single large packet and deliver it to a higher layer. This merging process is known as Large Receive Offload (LRO) technology. Similar to TSO (Transmit-Side Offload) technology, LRO processing is performed by the NIC hardware.

[0042] LRO technology heavily relies on the network interface card (NIC) and can lead to errors in the merged data packets. Therefore, Generic Receive Offload (GRO) technology was introduced. (See reference) Figure 7As shown, GRO technology can perform the merging operation in the network card driver, preserving the entropy information of each data packet (such as quintuple information).

[0043] Currently, when electronic devices use high-speed IP transceivers, such as those using Wi-Fi 7 RF modules or 5G modems to transmit IP packets, they generally use the default MTU to interact with nodes in the network (such as base stations, core networks, or Wi-Fi access nodes). The default MTU is usually 1500 bytes, or slightly smaller than 1500 bytes to reduce network transmission fragmentation. Therefore, communication efficiency is not high at peak 5G or Wi-Fi speeds.

[0044] Taking a typical 5G terminal device implementation as an example, the operating system layer (TCP, IP), the network card driver layer, and the network card itself all process small packets. Each data packet requires processing resources from the CPU and the network card's hardware and software accelerators, increasing the processing load on the CPU or network card hardware and software accelerators. Furthermore, referencing... Figure 8 As shown, the air interface protocol stack of a 5G modem typically includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Media Access Control (MAC) layer. These protocol stacks process small packets, consuming the modem's CPU and hardware / software accelerator resources. Similarly, the SDAP, PDCP, RLC, and MAC processing at the network-side base station, as well as the base station's transport layer protocol processing, also consume small packets, thus consuming the base station's user plane CPU and hardware / software accelerator resources.

[0045] For example, when the downlink peak rate of a 5G modem is 20 Gbit / s, with an MTU of 1500 bytes, the electronic device needs to process approximately 1666 data packets per ms. Specifically, this is calculated as 20,000,000,000 / 8 / 1500 / 1000 = 1,666 (if the communication method is TCP, the typical uplink TCP ACK count is 833; for downlink peak TCP traffic, the electronic device needs to process 1666 + 833 = 2499 data packets per ms). The application processor (AP) and all protocol layers of the modem together need to process 2499 * 8 = 19992 packet headers of a commonly used MTU size.

[0046] Based on existing standards and users' communication needs for peak communication rates, AP, Modem protocol stack processing unit, Wi-Fi protocol stack processing unit (or other short-range high-speed IP data transceiver units), and 4G / 5G / 6G base station protocol stack processing unit all have core needs to reduce the number of data packets processed, reduce power consumption, and reduce costs under peak traffic requirements. Base stations also have a core need to improve the efficiency of user plane data packet header processing.

[0047] Based on this, embodiments of this application provide a data transmission method. This data transmission method can be applied to various types of communication architectures, such as cellular communication architectures (including 4G, 5G, and future communication architectures), WiFi communication architectures, sidelink transmission architectures, and non-cellular 5G new wireless network architectures (DECT-2020NR), etc. Embodiments of this application impose limitations on this.

[0048] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0049] One embodiment of this application provides a data transmission method, referencing... Figure 9 As shown, the data transmission method provided in this application includes the following steps.

[0050] Step 110: If the first link between the first node and the second node supports the transmission of data packets of the first MTU length, the first node transmits data packets on the first link based on the first MTU length; the second node is used to offload the data packets transmitted on the first link.

[0051] It should be understood that data packet transmission can traverse multiple nodes. For example, in a cellular communication network architecture, when a terminal device needs to upload video data to an application server, the video data is first sent by the terminal device to the base station. The base station then sends the video data to the UPF (User-Defined Frame) network element in the core network, and the UPF network element then uploads the video data to the application server. In a WiFi communication architecture, the terminal device can send video data to a router, and the router can then send the video data to an external application server.

[0052] In this embodiment, the first node and the second node can be any two different nodes in the data packet transmission path. Optionally, the first node and the second node can be two adjacent nodes in the data packet transmission path. For example, in a cellular communication network architecture, the first node can be a terminal device, and the second node can be a base station. Furthermore, the first node can also be two non-adjacent nodes in the data packet transmission path. For example, the first node can be a terminal device, and the second node can be a UPF. This application does not limit the first node and the second node.

[0053] During data packet transmission, the data packet passes through a first node and a second node. The path taken by the data packet from the first node to the second node, or vice versa, is called the first link. It can be understood that the first link may include other nodes besides the first and second nodes. That is, the first link can be a part or all of the links in the data packet transmission path. For example, the first link can be a link consisting of a terminal device and a base station. The first link can also be a link consisting of a terminal, a base station, and a UPF network element.

[0054] In practical applications, due to hardware limitations and communication environment constraints, the maximum MTU length supported by each node during data packet transmission may differ. Each node needs to offload data packets during transmission to transmit them at the default MTU length. This can lead to excessive data packet processing by each node, resulting in excessive power consumption.

[0055] In this embodiment, if it is determined that the first link between the first node and the second node supports the transmission of data packets with a first MTU length, the first node can directly transmit data packets to the next node in the first link with the first MTU length. When the data packet is about to leave the first link after being transmitted through the first link to the second node, the second node can offload the data packet transmitted through the first link.

[0056] In other words, the length of data packets transmitted on the first link is no greater than the first MTU length. Nodes on the first link, except for the second node, do not need to offload data packets whose length is no greater than the first MTU length transmitted on the first link. The second node in the first link only offloads data packets transmitted on the first link when the data packet needs to leave the first link.

[0057] In some embodiments, the first MTU length can be greater than the default MTU length. That is, the first MTU length can be greater than the data payload exceeding the 1500 bytes limit of the IEEE 802.3 standard. For example, the first MTU length can be the maximum length of a message that the PDCP layer can transmit, or the length of a jumbo frame: 9000 bytes. This application does not impose any limitations on this.

[0058] It should be noted that 4G / 5G air interface transmission requires the transmission of relatively large signaling plane messages. Therefore, the maximum message size that the LTE PDCP layer can transmit is defined as 8188 bytes, while the maximum data packet size that the 5G PDCP layer can transmit is defined as 9000 bytes. The first node can use the maximum transmission size of 9000 bytes from the PDCP layer as the first MTU length. Furthermore, the MTU typically does not include the SDAP header; therefore, the first MTU length can be 9000 bytes minus the number of bytes occupied by the SDAP header.

[0059] In some embodiments, the first MTU length can be predefined, such as the maximum length that the protocol stack can handle, or the maximum length of an application layer data packet. The first MTU length can also be determined through negotiation among multiple nodes in the first link, and this application embodiment does not impose any restrictions on this.

[0060] It should be understood that the second node can be located at the junction of the first link and other links, the next node of the second node (which is not in the first link), or the next segment of the link supporting data packet transmission, whose MTU length is different from that of the first MTU length. In the embodiments of this application, the second node can offload data packets transmitted on the first link based on the next node of the second node or the MTU length supported by the next segment of the link, so that the length of the data packets after data offloading can meet the transmission requirements of the next node of the second node.

[0061] Optionally, the second node offloads data packets transmitted on the first link, which may include: the second node offloading data packets transmitted on the first link based on the second MTU length.

[0062] The second MTU length can be the MTU length supported by the third link between the second and fourth nodes. Alternatively, the second MTU length can be the maximum MTU length supported by the next node after the second node in the data packet transmission path, or it can be the default MTU length mentioned in the above embodiments. This application does not impose any limitations on this.

[0063] It should be noted that the third link between the second and fourth nodes can be a path in the data packet transmission path that is located after the first link.

[0064] It should be understood that the second MTU length differs from the first MTU length. The length of data packets transmitted on the first link is no greater than the first MTU length. However, the second node needs to continue transmitting data packets received on the first link to the next node. If the MTU length supported by the next node differs from the first MTU length, the second node needs to perform data offloading processing on the data packets received on the first link.

[0065] Optionally, the second MTU length is smaller than the first MTU length. That is, the second node can offload data packets transmitted on the first link based on the smaller MTU length. This data offloading can refer to splitting data packets, breaking down packets with larger MTU lengths into packets with smaller MTU lengths. For example, data offloading can include any one of GSO, GRO, TSO, and LRO, and this embodiment of the application does not limit this.

[0066] For example, in a scenario where a terminal device uploads video data to an application server, under a cellular communication network architecture, the transmission path of the video data can include a path consisting of the terminal device, a base station, a UPF network element, and the application server. The base station and UPF network element support the transmission of data packets with a first MTU length, while the application server does not support the transmission of data packets with a first MTU length, only those smaller than the first MTU length. Based on this, the communication link between the terminal device, the base station, and the UPF network element can constitute a first link. When the terminal device uploads video data, it can offload the video data into data packets with a length no greater than the first MTU length and send them to the base station. The base station then forwards the first MTU length data packets to the UPF network element. In this way, the UPF network element can offload the received first MTU length data packets to obtain a data packet size that meets the application server's requirements. Therefore, the terminal device can send larger data packets, transferring the offloading operation to the UPF network element in the first link. This reduces the workload of the terminal device in offloading data, thereby reducing the terminal device's power consumption and chip cost.

[0067] Understandably, in a wireless network, when a first link exists in the data packet transmission path that supports the transmission of data packets with larger MTU lengths, nodes on that link can directly transmit data packets with larger MTU lengths. Before the data packet leaves the first link, the last node in the first link can offload the data packet, reducing the larger MTU length data packet to a smaller MTU length data packet. This significantly reduces the number of packet headers processed (e.g., reducing the number of packet headers from the terminal device application layer to the base station, or from the terminal device application layer to the core network device), lowers the CPU processing power requirements, power consumption, and area under peak rate conditions, and effectively utilizes existing IP network hardware and software processing resources.

[0068] In summary, if the first node determines that the first link between the first and second nodes supports the transmission of the first MTU length, the first node can transmit data packets directly at the first MTU length without offloading them. Only after the data packets have been transmitted through the first link to the second node will the second node offload them. This allows the data offloading operation from the first node to be transferred to the second node, thus reducing CPU processing power requirements, power consumption, and area while maintaining the existing communication rate.

[0069] In one embodiment of this application, the first link between the first node and the second node supports the transmission of data packets with a first MTU length, which may include: the maximum MTU length supported by each node in the first link is greater than or equal to the first MTU length.

[0070] It should be understood that the maximum MTU length supported by each node in the first link can be different. As long as the maximum MTU length supported by each node in the first link is greater than the first MTU length, it can be considered that the first link supports the transmission of data packets with the first MTU length. The first MTU length is greater than the default MTU length.

[0071] In one embodiment of this application, prior to step 110 described above, the following steps may also be included:

[0072] The first node negotiates the first MTU length with the other nodes in the first link.

[0073] In this embodiment, the first node can negotiate with other nodes in the first link to determine the first MTU length supported by the first link. Specifically, the first node can exchange information with other nodes in the first link at least once to negotiate and determine the first MTU length supported by the first link.

[0074] There are several ways for the first node to negotiate the first MTU length with other nodes on the first link. Two of them are described in detail below.

[0075] In one embodiment of this application, reference is made to Figure 10A As shown, in the data transmission method provided in this application embodiment, before the first node transmits data packets based on the first MTU length on the first link in step 110, the following steps can be performed:

[0076] Step 120A: The first node receives capability information sent by the neighboring nodes of the first node in the first link. The capability information is used to indicate the maximum MTU length supported by the sending neighboring nodes.

[0077] Step 130A: The first node determines the first MTU length between itself and its neighboring nodes based on the maximum MTU length supported by the neighboring nodes.

[0078] It should be understood that two adjacent nodes on the first link can send capability information to each other. Each node can use the capability information to inform its adjacent nodes of the maximum MTU length it supports for transmission.

[0079] There are several ways to indicate the maximum MTU length using capability information.

[0080] In one possible implementation, the capability information may include an indication field that directly carries the maximum MTU length supported by the node for transmission. For example, a value of 1500 in the indication field indicates that the node sending the capability information supports a maximum MTU length of 1500 bytes. A value of 9000 in the indication field indicates that the node sending the capability information supports a maximum MTU length of 9000 bytes.

[0081] In another possible implementation, the value of the indicator field in the capability information can include N different values, each corresponding to one of the N MTU lengths supported by the node. For example, the maximum MTU length supported by each node can include two cases: either 9000 bytes or 1500 bytes. When the indicator field is set to the first value (e.g., 0 or 1), it indicates that the current node supports a maximum MTU length of 9000 bytes; when the indicator field is set to the second value (e.g., 1 or 0), it indicates that the current node supports a maximum MTU length of 1500 bytes.

[0082] In another possible implementation, if a node sends capability information, it indicates that the maximum MTU length supported by the node is A bytes (e.g., 9000 bytes / 1500 bytes); if a node does not send capability information, it indicates that the maximum MTU length supported by the node is B bytes (e.g., 1500 bytes / 9000 bytes). Taking node 1 as an example, if node 1 supports a maximum MTU length of 9000 bytes, then node 1 can send capability information to other nodes in the first link. After receiving the capability information sent by node 1, other nodes can determine that the maximum MTU length supported by node 1 is 9000 bytes. This application does not limit the method of indicating capability information.

[0083] In this embodiment of the application, each node can determine the first MTU length for data packet transmission with neighboring nodes based on its own maximum supported MTU length and the maximum supported MTU length of neighboring nodes.

[0084] It should be noted that the first node in the first link can receive capability information sent by its neighboring nodes and determine the first MTU length for data packet transmission between the first node and its neighboring nodes based on this capability information. Similarly, the second node in the first link can also receive capability information sent by its neighboring nodes and determine the first MTU length for data packet transmission between the second node and its neighboring nodes based on this capability information. Furthermore, other nodes in the first link besides the first and second nodes can also receive capability information sent by their neighboring nodes to determine the first MTU length for data packet transmission with their neighboring nodes.

[0085] In some embodiments, each node in the first link may use the smaller of its own maximum supported MTU length and the maximum supported MTU length of its neighboring nodes as the first MTU length for data packet transmission with its neighboring nodes.

[0086] For example, the first link includes nodes A, B, and C. Node A supports a maximum MTU length of 9000 bytes, node B supports a maximum MTU length of 9000 bytes, and node C supports a maximum MTU length of 3000 bytes. Node B is located between nodes A and C. Node A can receive capability information sent by node B, node B can receive capability information sent by both nodes A and C, and node C can receive capability information sent by node B. Nodes A and B can determine that the first MTU length between them is 9000 bytes, and nodes B and C can determine that the first MTU length for data packets transmitted between them is 3000 bytes.

[0087] It should be noted that the first MTU length supported by the first link in this embodiment may include the first MTU length for data packet transmission between adjacent nodes in the first link.

[0088] In another embodiment of this application, reference is made to Figure 10B As shown, in the data transmission method provided in this application embodiment, before the first node transmits data packets based on the first MTU length on the first link in step 110, the following steps can be performed:

[0089] Step 120B: The first node receives capability information sent by each node in the first link except the first node. The capability information is used to indicate the maximum MTU length that the node sending the capability information supports for transmission.

[0090] Step 130B: The first node determines the first MTU length based on the maximum MTU length supported by each node for transmission;

[0091] Step 140B: The first node sends indication information to each node in the first link other than itself, the indication information being used to indicate the length of the first MTU.

[0092] It should be understood that each node in the first link can send capability information to each other. Each node can use this capability information to inform other nodes of the maximum MTU length it supports for transmission. In other words, the first node can receive capability information sent by all other nodes in the first link, and determine the maximum MTU length that each of the other nodes in the first link supports for transmission based on the capability information sent by each node.

[0093] Optionally, the first node may also send its maximum supported MTU length to other nodes on the first link via capability information to facilitate the determination of the first MTU length.

[0094] The capability information can indicate the maximum MTU length in various ways. For example, the indication field in the capability information can directly carry the maximum MTU length that the node supports for transmission. The value of the indication field in the capability information can include N different values, each corresponding to one of the N MTU lengths that the node supports for transmission. Alternatively, if the node sends capability information, it indicates that the maximum MTU length that the node supports for transmission is A bytes; if the node does not send capability information, it indicates that the maximum MTU length that the node supports for transmission is B bytes. It should be noted that the specific indication method of the capability information is the same as in the above embodiment, and for the sake of simplicity, it will not be repeated here.

[0095] Optionally, the first node may proactively request each node in the first link to send capability information, i.e., proactively query the capabilities of each node. Additionally, each node on the first link may also proactively send capability information to other nodes to inform them of the maximum MTU length that each node supports for transmission. This application embodiment does not impose any limitations on this.

[0096] In this embodiment, the first node can determine the first MTU length supported by the first link based on its own maximum supported MTU length and the maximum supported MTU lengths of other nodes on the first link. The first MTU length can be the minimum of the maximum supported MTU lengths of all nodes on the first link. In other words, the minimum of the maximum supported MTU lengths of all nodes on the first link can be determined as the first MTU length supported by the first link.

[0097] For example, refer to Figure 11A As shown, in a cellular communication network architecture, the maximum MTU length supported by the terminal device, base station, and UPF network element is 9000 bytes. The first node can be the terminal device, and the second node can be the UPF network element. The UPF network element can send capability information to the base station, informing it that the maximum MTU length it supports is 9000 bytes. Furthermore, the base station can send capability information to the terminal device, informing it that the maximum MTU length supported by both the base station and the UPF network element is 9000 bytes. Since the maximum MTU length supported by the terminal device, base station, and UPF is 9000 bytes, the terminal device can determine that the first MTU length supported by the link formed between the terminal device and the base station is 9000 bytes. In other words, a maximum data packet of 9000 bytes can be transmitted between the terminal device, base station, and UPF network element.

[0098] Optionally, each node in the first link can send capability information via broadcast signaling or via dedicated signaling; this application embodiment does not impose any restrictions on this.

[0099] For example, refer to Figure 11A As shown, in a cellular communication network architecture, the UPF (User-Generated Function) network element can send capability information to the base station via dedicated signaling, informing the base station of the maximum MTU (Mean Transmission Unit) length supported by the UPF network element. This capability information can be proactively sent by the UPF network element to the base station, or it can be queried and sent by the base station. Furthermore, after receiving the capability information, the base station can send a broadcast message (e.g., a system message, a synchronization signal block, etc., which is not limited in this embodiment), carrying both the maximum MTU length supported by the base station and the maximum MTU length supported by the UPF network element in the broadcast message.

[0100] In summary, nodes can transmit the maximum MTU length they support through broadcast signaling. This allows each node to determine the first MTU length supported by the first link based on the capability information sent by other nodes. Consequently, nodes in the network can flexibly deploy data offloading schemes according to the actual network conditions. It is understandable that as long as a node in the network has the capability to transmit data with a larger MTU length, the data offloading function can be transferred to other nodes in the network, achieving flexible offloading and improving network communication performance.

[0101] In step 140B, after the first node determines the first MTU length, it can also send indication information to other nodes on the first link to inform other nodes on the first link of the first MTU length for data packet transmission on the first link.

[0102] Optionally, the indication information can be sent via dedicated signaling between nodes, or it can be sent using other signaling between nodes (such as random access messages, initial registration messages, etc.). This application embodiment does not impose any restrictions on this.

[0103] For example, in a cellular communication network architecture, a terminal device, a base station, and a UPF network element constitute a first link, wherein the maximum MTU length supported by the terminal device, base station, and UPF network element is 9000 bytes. After the terminal device determines that the first link supports a first MTU length of 9000 bytes, it can send an initial registration message to the base station, which may instruct it to register with the UPF network element. The base station can send this initial registration message to the UPF network element. The initial registration message may include the aforementioned instruction information to facilitate confirmation between the base station and the UPF network element regarding whether to use the first MTU length for data transmission on the first link.

[0104] In some embodiments, after receiving the indication information, other nodes on the first link may use the first MTU length indicated in the indication information to transmit data packets.

[0105] In other embodiments, after receiving the indication information, other nodes on the first link can determine whether they support the first MTU length carried in the indication information.

[0106] For example, other nodes on the first link can determine whether to support the first MTU length indicated by the indication information by combining their own hardware and software capabilities. If the current node has a light load and can transmit an MTU length greater than the first MTU length, then the node can determine that it supports the first MTU length indicated in the indication information. If the current node has a heavy load and can transmit an MTU length less than the negotiated MTU length, then the node can determine that it does not support the negotiated MTU length carried in the negotiation information.

[0107] In some embodiments, if a node on the first link supports transmitting the first MTU length, it can send an acknowledgment message to the first node; if the node does not support transmitting the first MTU length, it can send a rejection message to the first node.

[0108] It should be understood that if all other nodes on the first link send back confirmation messages, the negotiation is successful. If any other node on the first link sends back a rejection message, the first node can consider the negotiation to have failed and renegotiate. During renegotiation, the first node can reduce the first MTU length and renegotiate again.

[0109] Optionally, confirmation / rejection information can also be sent via dedicated signaling between nodes, or other signaling between nodes (such as random access response messages, initial registration acceptance messages) can be reused. This application embodiment does not impose any restrictions on this.

[0110] For example, in a cellular communication network architecture, the terminal device, base station, and UPF network element constitute the first link, wherein the maximum MTU length supported by the terminal device, base station, and UPF network element is 9000 bytes. (Reference) Figure 11A As shown, after receiving the initial registration message carrying indication information, if the UPF network element agrees with the first MTU length indicated in the indication information, it carries an acknowledgment message in the initial registration acceptance message and sends the initial registration acceptance message carrying the acknowledgment message to the terminal device through the base station. In this way, the first link formed by the terminal device, the base station, and the UPF network element can transmit data based on the first MTU length.

[0111] In summary, in the data transmission method provided by the embodiments of this application, nodes can negotiate the first MTU length used when transmitting data on the first link through broadcast signaling and dedicated channel signaling, so as to flexibly arrange the network data offloading scheme according to the actual situation of the current network.

[0112] In one embodiment of this application, the second node in step 110 is used to offload the data packets transmitted on the first link, which can be achieved in the following way:

[0113] The second node is used to offload data packets transmitted on the first link based on the second MTU length, where the first MTU length is an integer multiple of the second MTU length.

[0114] The second MTU length is less than the first MTU length. The second MTU length can be the default MTU length in the above embodiments.

[0115] It should be understood that the first node can transmit data packets on the first link with a larger first MTU length. The second node can offload data packets from the first link based on a smaller second MTU length. The first node can transfer the data offloading operation to the second node, reducing the amount of data packet header processing and computation on the first node.

[0116] Optionally, the first MTU can be an integer multiple of the second MTU length. It is understood that since other nodes outside the first link need to offload data packets according to the default second MTU length, the first MTU length is preferably chosen as an integer multiple of the default MTU length (i.e., the second MTU length). This avoids packet fragmentation during data packet transmission between nodes.

[0117] In one embodiment of this application, reference is made to... Figure 12 As shown, step 110, which involves transmitting data packets on the first link based on the first MTU length, may include:

[0118] Step 1101: Unload the received data packet to obtain a first data packet, the length of which is not greater than the length of the first MTU;

[0119] Step 1102: Send the first data packet on the first link.

[0120] It should be understood that the data packets received by the first node can be data packets generated by the first node. For example, when the first node is a terminal device, the terminal device can acquire video data through an image acquisition device to obtain the aforementioned data packets. The data packets received by the first node can also be data packets sent to it by other nodes besides those in the first link. For example, when the first node is a base station, the data packets received by the first node can be data packets sent to it by a terminal device. This application embodiment does not limit the type of data packets received.

[0121] The length of the data packet received by the first node can be greater than or less than the first MTU length. This application embodiment does not impose any restrictions on this.

[0122] Since the first link supports the transmission of data packets with a first MTU length, if the data packet received by the first node is larger than the first MTU length, the first node can offload the received data packet based on the first MTU length. In other words, the first node can split the received data packet so that the length of each split data packet is less than or equal to the first MTU length.

[0123] Optionally, the first node can offload the received data packet into N first data packets, wherein the length of the first N-1 first data packets is equal to the length of the first MTU, and the length of the Nth first data packet is less than the length of the first MTU.

[0124] Optionally, the first node can uniformly offload the received data packet into N first data packets, wherein the N first data packets have the same length and are all less than or equal to the length of the first MTU. This application embodiment does not limit the method by which the first node offloads the received data packets.

[0125] For example, in a scenario where a terminal device uploads video data to an application server, the terminal device is the first node, the UPF network element is the second node, and the terminal device, base station, and UPF network element constitute the first link. The terminal device can offload the collected video data according to a first MTU length to obtain first data packets. The length of each first data packet is less than or equal to the first MTU length. Further, the terminal device can send the first data packets on the first link; specifically, the terminal device can send the first data packets to the base station. The base station then forwards the first data packets to the UPF network element. Before sending the first data packets to the application server, the UPF network element offloads the received first data packets according to a second MTU length. The length of the offloaded data packets is less than the second MTU length. In other words, the terminal device can delegate the operation of offloading data packets to the second MTU length to the UPF network element in the network.

[0126] Based on the above embodiments, in one embodiment of this application, reference is made to... Figure 13 As shown, in step 110, transmitting data packets based on the first MTU length on the first link can also be achieved in the following ways:

[0127] Step 1103: The first node receives the second data packet on the first link. The length of the second data packet is not greater than the length of the first MTU.

[0128] It should be understood that the first node can send data packets on the first link, and can also receive data packets on the first link. For details on how the first node sends data packets on the first link, please refer to steps 1101 and 1102 of the above embodiment; for brevity, they will not be repeated here.

[0129] In this embodiment, the first node can receive the second data packet on the first link. It should be understood that since the first link can support the transmission of data packets of the first MTU length, the length of the second data packet transmitted on the first link can be less than or equal to the first MTU length.

[0130] The first node can also form a second link with the third node. The third node is different from all the nodes in the first link. That is, the third node is not any node in the first link. The first node can form a second link with other nodes besides those in the first link.

[0131] For example, in a cellular communication network architecture, the first link may include a link consisting of an application server, a UPF network element, and a base station. The second link may include a link consisting of a base station and a terminal device. The base station can be the first node, the application server the second node, and the terminal device the third node.

[0132] It should be noted that the second link can support the transmission of data packets with a third MTU length. This means that the maximum MTU length supported by each node in the second link is greater than the third MTU length.

[0133] The length of the third MTU may differ from the length of the first MTU supported by the first link. The length of the third MTU may be greater than or less than the length of the first MTU, and this embodiment does not impose any restrictions on this.

[0134] In addition, the length of the third MTU can be the same as or different from the length of the second MTU in the above embodiments. This application does not limit this.

[0135] Based on the above embodiments, in one embodiment of this application, reference is made to... Figure 13 As shown, the data transmission method provided in this application embodiment may further include the following steps:

[0136] Step 150: The first node offloads data from the second data packet based on the third MTU length to obtain the third data packet;

[0137] Step 160: The first node sends the third data packet on the second link.

[0138] It should be understood that the first node can send the data received on the first link to the third node through the second link.

[0139] For example, in a cellular communication network architecture, the first link may include a link consisting of an application server, a UPF network element, and a base station. The second link may include a link consisting of a base station and a terminal device. The base station can be the first node, the application server the second node, and the terminal device the third node. The base station can send data from the application server in the first link to the terminal device on the second link.

[0140] Because the MTU length supported by the second link is the third MTU length, and the third MTU length is different from the first MTU length supported by the first link, the first node needs to offload the second data packet after receiving it on the first link to obtain a data packet that meets the transmission requirements of the second link before it can be transmitted on the second link.

[0141] It should be understood that after receiving the second data packet, the first node can offload the second data packet based on the third MTU length. In other words, the first node can merge and / or unpack the second data packet, and the length of the third data packet obtained after unloading is less than or equal to the third MTU length.

[0142] In summary, the data transmission method provided in this application embodiment can increase the MTU length of each node in the first link, further improve the processing performance of the CPU and various hardware and software message accelerators, and even increase the processing performance gain while reducing the power consumption and chip cost of each node.

[0143] The data transmission method provided in the embodiments of this application will be described in detail below with reference to specific application scenarios.

[0144] Figure 11B This paper illustrates a scenario where a terminal device sends data to a core network UPF element. In this scenario, the UPF element supports a maximum MTU length of 1500 bytes, while the base station and terminal device support a maximum MTU length of 9000 bytes. The base station can carry the capability information of the base station and the UPF element in broadcast messages (such as master information blocks, system information, etc.) to inform the terminal device of the maximum MTU lengths supported by the base station and the UPF element, respectively.

[0145] After receiving the broadcast message, the terminal device can determine that it and the base station can form a first link. Specifically, in the first link, the terminal device can transmit data packets with the base station using a 9000-byte MTU length, and the base station and the UPF network element can transmit data packets using a 1500-byte MTU length.

[0146] Furthermore, the terminal device can send registration information to the base station, which can then forward the registration information to the UFP network element. The registration information can carry the negotiated MTU size determined by the terminal device. Here, the terminal device negotiates the MTU length for data transmission with the base station and the core network UFP network element using the registration information. The UFP network element can send a registration acceptance message to the base station, informing the base station and terminal device of the negotiated MTU length.

[0147] Finally, the terminal device can send data packets based on the negotiated MTU length. Specifically, the base station can offload data packets sent by the terminal device based on a 1500-byte MTU length.

[0148] It should be noted that, when the data transmission method provided in this application is applied to a 4G / 5G communication architecture, the MTU size is still limited by the maximum packet size of IP data packets and the PDCP signaling plane. In future communication architectures, if the PDCP maximum packet size limit is removed (PDCP transmission is not only for the signaling plane), the maximum packet size of PDCP transmission can be the same as that of the application layer, further reducing the requirements of node CPU and hardware / software accelerators for data packet processing at peak rates.

[0149] It should be noted that the processing method provided in this application embodiment can be implemented by software or by a hardware data packet accelerator in the node, and this application embodiment does not limit it.

[0150] It should be understood that, in the embodiments of this application, without changing the hardware implementation of each node, the processing performance of the CPU of each major node can be improved by simply modifying the software implementation. In addition, the power consumption and chip cost of some nodes will also be reduced.

[0151] Furthermore, by improving the software and the hardware of the nodes to support massive MTU data transmission and data offloading, the processing performance of the CPU and various hardware and software message accelerators can be further improved (from 6 times to 43 times), and the power consumption and chip cost of some nodes will also be reduced.

[0152] In summary, the data transmission method provided in this application embodiment can effectively utilize existing network nodes, such as base stations, core networks, and router hardware, to support the transmission of giant MTU data packets and data offloading functions. By increasing the MTU length, the CPU processing power requirements, power consumption, and area under peak rate conditions can be effectively reduced, and existing network hardware and software processing resources can be effectively utilized.

[0153] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with the prior art, and the resulting technical solutions should also fall within the protection scope of this application.

[0154] One embodiment of this application also provides a data transmission device applied to a first node, see reference. Figure 14 As shown, the data transmission device 1400 may include:

[0155] The sending unit 1401 is configured to transmit data packets based on the first MTU length on the first link when the first link between the first node and the second node supports the transmission of data packets with a first maximum transmission unit (MTU) length, and the second node is used to offload the data packets transmitted on the first link.

[0156] Optionally, the first link between the first node and the second node supports the transmission of data packets with a first maximum transmission unit (MTU) length, including: the maximum MTU length supported by each node in the first link is greater than or equal to the first MTU length.

[0157] Optionally, the data transmission apparatus 1400 may further include a negotiation unit, wherein the negotiation unit is configured to negotiate the first MTU length with other nodes in the first link.

[0158] Optionally, the negotiation unit is further configured to receive capability information sent by neighboring nodes of the first node in the first link, the capability information being used to indicate the maximum MTU length supported by the node sending the capability information; and to determine the first MTU length based on the maximum MTU length supported by the neighboring nodes.

[0159] Optionally, the negotiation unit is further configured to receive capability information sent by each node in the first link other than the first node; and determine the first MTU length based on the maximum MTU length supported by each node for transmission.

[0160] The transmitting unit 1401 is further configured to transmit indication information to each node in the first link other than the first node, the indication information being used to indicate the length of the first MTU.

[0161] Optionally, the second node is further configured to offload data packets transmitted on the first link based on a second MTU length, wherein the first MTU length is an integer multiple of the second MTU length.

[0162] Optionally, the data transmission device 1400 may further include an offloading unit configured to offload the received data packet to obtain a first data packet, wherein the length of the first data packet is not greater than the length of the first MTU.

[0163] The sending unit 1401 is also configured to send the first data packet on the first link.

[0164] Optionally, the receiving unit is further configured to receive a second data packet on the first link, wherein the length of the second data packet is not greater than the length of the first MTU.

[0165] Optionally, the second link between the first node and the third node supports the transmission of data packets with a third MTU length, and the offloading unit is further configured to offload the second data packet based on the third MTU length to obtain the third data packet;

[0166] The sending unit 1401 is also configured to send the third data packet on the second link.

[0167] Figure 15 This is a schematic structural diagram of a communication device 1500 provided in an embodiment of this application. The communication device can be a first node. The communication device can also be a chip used for data transmission, such as a modem, a WiFi radio frequency module, a high-speed data transceiver, etc., and this embodiment of the application does not impose any limitations on this.

[0168] Figure 15 The communication device 1500 shown includes a processor 1510, which can call and run computer programs from memory to implement the data transmission method provided in the embodiments of this application.

[0169] Optionally, such as Figure 15 As shown, the communication device 1500 may further include a memory 1520. The processor 1510 can retrieve and run computer programs from the memory 1520 to implement the methods described in this embodiment.

[0170] The memory 1520 can be a separate device independent of the processor 1510, or it can be integrated into the processor 1510.

[0171] Optionally, such as Figure 15 As shown, the communication device 1500 may also include a transceiver 1530, and the processor 1510 may control the transceiver 1530 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0172] The transceiver 1530 may include a transmitter and a receiver. The transceiver 1530 may further include an antenna, and the number of antennas may be one or more.

[0173] Optionally, the communication device 1500 may specifically be the first node in the embodiments of this application, and the communication device 1500 may implement the corresponding processes implemented by the first node in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0174] This application also provides a computer storage medium, specifically a computer-readable storage medium. Computer instructions are stored thereon, and when the computer storage medium is located in a data transmission device, these computer instructions, when executed by a processor, implement any step of the data transmission method described in this application.

[0175] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0176] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0177] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or at least two units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0178] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0179] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0180] It should be noted that the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0181] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data transmission method, characterized in that, Applied to the first node, including: When the first link between the first node and the second node supports the transmission of data packets with a first maximum transmission unit (MTU) length, data packets are transmitted on the first link based on the first MTU length, and the second node is used to offload data packets transmitted on the first link based on the second MTU length, wherein the first MTU length is an integer multiple of the second MTU length. Wherein, the first MTU length is the maximum length of the PDCP layer transmission message, or the first MTU length is the length of the giant frame.

2. The method according to claim 1, characterized in that, The first link between the first node and the second node supports the transmission of data packets with a first maximum transmission unit (MTU) length, including: The maximum MTU length supported by each node in the first link is greater than or equal to the first MTU length.

3. The method according to claim 2, characterized in that, The first node negotiates the first MTU length with the other nodes in the first link.

4. The method according to claim 3, characterized in that, The first node negotiates the first MTU length with other nodes in the first link, including: The first node receives capability information sent by its neighboring nodes in the first link, the capability information being used to indicate the maximum MTU length that the node sending the capability information supports for transmission; The first node determines the first MTU length based on the maximum MTU length supported by the adjacent nodes.

5. The method according to claim 3, characterized in that, The first node negotiates the first MTU length with other nodes in the first link, including: The first node receives capability information sent by each node in the first link other than itself. The first node determines the first MTU length based on the maximum MTU length supported by each node for transmission; The first node sends indication information to each node in the first link other than itself, the indication information being used to indicate the length of the first MTU.

6. The method according to any one of claims 1-5, characterized in that, The transmission of data packets based on the first MTU length on the first link includes: The received data packet is unloaded to obtain a first data packet, the length of which is not greater than the length of the first MTU. The first data packet is sent on the first link.

7. The method according to any one of claims 1-5, characterized in that, The transmission of data packets based on the first MTU length on the first link includes: A second data packet is received on the first link, and the length of the second data packet is not greater than the length of the first MTU.

8. The method according to claim 7, characterized in that, The second link between the first node and the third node supports the transmission of data packets with a third MTU length, and the method further includes: Based on the third MTU length, the second data packet is offloaded to obtain the third data packet; The third data packet is sent on the second link.

9. A data transmission device, characterized in that, Applied to the first node, the device includes: The sending unit is configured to transmit data packets on the first link based on the first MTU length, provided that the first link between the first node and the second node supports the transmission of data packets with a first maximum transmission unit (MTU) length; the second node is configured to offload data packets transmitted on the first link based on a second MTU length, wherein the first MTU length is an integer multiple of the second MTU length. Wherein, the first MTU length is the maximum length of the PDCP layer transmission message, or the first MTU length is the length of the giant frame.

10. A communication device, characterized in that, It includes a processor and a memory for storing computer programs, the processor for calling and running the computer programs stored in the memory to perform the method as described in any one of claims 1-8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1-8.

Images