Method and apparatus for data distribution in a wired wireless network collaboration
Patent Information
- Application Number
- CN202610706707.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-05-21
- Publication Date
- 2026-08-18
AI Technical Summary
[0005]本申请实施例提供的有线无线网络协同的数据分配方法及装置,用以解决现有的方式在服务器同时具备有线与无线网络接口时,存在网络资源分配不合理,导致数据传输效率低下的问题
[0031] The wired-wireless network collaborative data allocation method and apparatus provided in this application obtains the data characteristics of the data to be transmitted; determines the data type of the data to be transmitted based on the data characteristics, whereby the data type indicates whether the data to be transmitted is high-priority or low-priority data; when the data type indicates that the data to be transmitted is high-priority data, obtains the current and historical status information of the wireless network; determines the allocation ratio of the data to be transmitted between the wired and wireless network cards based on the current and historical status information; and allocates the data to be transmitted to the wired and/or wireless network cards according to the allocation ratio. This method first distinguishes between high and low priority data based on the characteristics of the data to be transmitted, and further combines the dynamic changes in the current and historical status information of the wireless network for high-priority data. This breaks the limitation of single network interface transmission, realizes dynamic allocation of data between wired and wireless network cards, fully utilizes network resources, and thus improves the overall data transmission efficiency.
Smart Images

Figure CN122601600A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication network technology, and in particular to a data distribution method and apparatus for wired and wireless network collaboration. Background Technology
[0002] With the rapid development of information technology, the demand for data transmission is exploding across various fields, especially in application scenarios such as data centers, cloud computing, edge computing, and artificial intelligence, where the requirements for data transmission speed and efficiency are becoming increasingly stringent. As the core equipment for data transmission and processing, the network transmission performance of servers directly affects the operating efficiency and service quality of the entire system. In today's diversified server market, various types of servers, including enterprise-level data center servers, general-purpose servers, entry-level servers, and edge servers, all have an urgent need for efficient data transmission. Simultaneously, with the increasing maturity of wireless network technology, more and more servers are beginning to be equipped with both wired and wireless network cards to meet the data transmission needs of different network environments and application scenarios.
[0003] Currently, in server network transmission technology, wired and wireless network cards (NICs) typically operate independently. When transmitting data, a server can usually only choose to use either a wired or wireless NIC. The system generally determines which NIC to use based on pre-set network configurations or manual user selection; once selected, the entire data transmission task is handled solely by that NIC. Even if the server has both wired and wireless network interfaces, interface switching is performed based on network status to improve transmission efficiency.
[0004] However, existing methods still suffer from inefficient data transmission due to unreasonable allocation of network resources when the server has both wired and wireless network interfaces. Summary of the Invention
[0005] The data allocation method and apparatus for wired and wireless network collaboration provided in this application are used to solve the problem that in existing methods, when the server has both wired and wireless network interfaces, the network resource allocation is unreasonable, resulting in low data transmission efficiency.
[0006] In a first aspect, embodiments of this application provide a data allocation method for wired and wireless network collaboration, including:
[0007] Obtain the data characteristics of the data to be transmitted;
[0008] Based on the data characteristics, determine the data type of the data to be transmitted. The data type is used to indicate whether the data to be transmitted is high-priority or low-priority data.
[0009] When the data type indicates that the data to be transmitted is high-priority data, obtain the current status information and historical status information of the wireless network;
[0010] Based on current and historical status information, determine the allocation ratio of the data to be transmitted between the wired and wireless network cards.
[0011] According to the allocation ratio, the data to be transmitted is allocated to wired network cards and / or wireless network cards.
[0012] In one possible implementation, determining the allocation ratio of the data to be transmitted between the wired network card and the wireless network card based on current status information and historical status information includes: obtaining a preset allocation mapping table, which contains the correspondence between multiple historical status levels, multiple current status levels and multiple allocation ratios; determining the corresponding historical status level based on historical status information; determining the corresponding current status level based on current status information; and querying the allocation mapping table based on the historical status level and the current status level to obtain the allocation ratio.
[0013] In one possible implementation, the current status information includes the real-time signal strength of the wireless network, and the historical status information includes the stability level of the wireless network.
[0014] In one possible implementation, determining the data type of the data to be transmitted based on data characteristics includes: acquiring the real-time load of the wired network card and the wireless network card; determining a dynamic data threshold based on the real-time load; and determining the data type of the data to be transmitted based on the data characteristics and the dynamic data threshold. Wherein, if the data volume indicated by the data characteristics is greater than the dynamic data threshold, the data to be transmitted is determined to be high-priority data; if the data volume indicated by the data characteristics is less than or equal to the dynamic data threshold, the data to be transmitted is determined to be low-priority data.
[0015] In one possible implementation, allocating data to be transmitted to wired network cards and / or wireless network cards according to an allocation ratio includes: splitting the data to be transmitted into multiple data blocks; determining a first set of data blocks allocated to the wired network cards and a second set of data blocks allocated to the wireless network cards from the multiple data blocks according to the allocation ratio; transmitting the first set of data blocks through the wired network cards and transmitting the second set of data blocks through the wireless network cards to instruct the receiving end to reassemble the first set of data blocks and the second set of data blocks into data to be transmitted.
[0016] In one possible implementation, the method further includes: allocating the data to be transmitted to a wired network card when the data type indicates that the data to be transmitted is low-priority data.
[0017] In one possible implementation, when there are multiple data to be transmitted, the method further includes: acquiring data characteristics of each data to be transmitted, the data characteristics including data volume; allocating data to be transmitted with a data volume indicating large data volume to a wired network card, and allocating data to be transmitted with a data volume indicating small data volume to a wireless network card, wherein large data volume and small data volume are determined by a preset data volume threshold.
[0018] In one possible implementation, the method further includes: acquiring task type information for each piece of data to be transmitted, wherein the task type information indicates that the data to be transmitted is target data or other data to be transmitted, and the target data to be transmitted includes at least one of preset management data, configuration data and log data; and when the task type information indicates that the data to be transmitted is target data to be transmitted and the data volume indicates that it is small data, allocating the data to be transmitted to the wired network card.
[0019] In one possible implementation, the method further includes: using an application installed on the operating system to call a driver to bind the wired network card and the wireless network card to form a combined network interface; the wired network card and the wireless network card perform coordinated data transmission through the combined network interface.
[0020] Secondly, embodiments of this application provide a data distribution device for wired and wireless network collaboration, comprising:
[0021] The first acquisition module is used to acquire the data characteristics of the data to be transmitted;
[0022] The first determining module is used to determine the data type of the data to be transmitted based on the data characteristics. The data type is used to indicate whether the data to be transmitted is high-priority data or low-priority data.
[0023] The second acquisition module is used to acquire the current status information and historical status information of the wireless network when the data type indicates that the data to be transmitted is high-priority data.
[0024] The second determining module is used to determine the allocation ratio of the data to be transmitted between the wired network card and the wireless network card based on the current status information and historical status information.
[0025] The allocation module is used to allocate the data to be transmitted to the wired network card and / or wireless network card according to the allocation ratio.
[0026] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;
[0027] The memory stores the instructions that the computer executes;
[0028] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.
[0029] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed, are used to implement the first aspect and / or various possible implementations of the first aspect.
[0030] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed, implements the first aspect and / or various possible implementations of the first aspect.
[0031] The wired-wireless network collaborative data allocation method and apparatus provided in this application obtains the data characteristics of the data to be transmitted; determines the data type of the data to be transmitted based on the data characteristics, whereby the data type indicates whether the data to be transmitted is high-priority or low-priority data; when the data type indicates that the data to be transmitted is high-priority data, obtains the current and historical status information of the wireless network; determines the allocation ratio of the data to be transmitted between the wired and wireless network cards based on the current and historical status information; and allocates the data to be transmitted to the wired and / or wireless network cards according to the allocation ratio. This method first distinguishes between high and low priority data based on the characteristics of the data to be transmitted, and further combines the dynamic changes in the current and historical status information of the wireless network for high-priority data. This breaks the limitation of single network interface transmission, realizes dynamic allocation of data between wired and wireless network cards, fully utilizes network resources, and thus improves the overall data transmission efficiency. Attached Figure Description
[0032] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0033] Figure 1 A flowchart illustrating the wired-wireless network collaborative data allocation method provided in this application;
[0034] Figure 2 A diagram illustrating the implementation architecture of wireless and wired network collaboration provided in this application;
[0035] Figure 3 A detailed architecture diagram of the wireless network and wired network binding provided in this application;
[0036] Figure 4 A diagram illustrating the data allocation for the low-priority data provided in this application;
[0037] Figure 5 A diagram illustrating the data allocation corresponding to the high-priority data provided in this application;
[0038] Figure 6A schematic diagram illustrating the data allocation for the multiple data to be transmitted provided in this application;
[0039] Figure 7 A schematic diagram of the structure of the data distribution device for wired and wireless network collaboration provided in this application;
[0040] Figure 8 A schematic diagram of the structure of the electronic device provided in this application.
[0041] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0042] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0043] Data transmission technology is widely used in general-purpose servers, entry-level servers, edge servers, and electronic devices with multi-network access capabilities. It is particularly suitable for scenarios requiring improved efficiency in file transfer, data synchronization, business migration, and cross-system interaction under existing hardware conditions. In actual deployment, these devices typically possess both wired and wireless network cards (NICs) for communication, and data transmission and reception are accomplished through the operating system, network drivers, network management modules, and upper-layer business programs. Typical application environments include batch data replication within data centers, data backhaul between edge nodes and the central platform, database backup and recovery in enterprise office networks, log transmission in remote maintenance scenarios, and file exchange under multi-service concurrency.
[0044] In these scenarios, devices need to rely on wired networks for high stability and low transmission jitter, while also seeking the flexible access capabilities of wireless networks to adapt to usage conditions with limited cabling, fluctuating network environments, or high device mobility. As the scale of business data continues to grow, the transmitted objects are no longer limited to small files, but have expanded to different types of data sets, such as configuration files, log files, image files, database shards, model parameters, and system-level business data. These different data types exhibit significant differences in importance, real-time performance, and transmission fault tolerance. Therefore, in a device architecture with both wired and wireless network access, how to organize the transmission process based on data characteristics, business priorities, and network status has become a crucial application problem in server and edge device network transmission.
[0045] In existing technologies, the aforementioned devices typically employ a single network connection to complete communication when performing data transmission tasks, meaning that either a wired or wireless network undertakes the primary transmission task. Common implementations involve the user manually selecting which network interface card (NIC) to prioritize, or the operating system automatically determining the outbound path based on rules such as default routing, interface priority, and link connectivity. The basic working principle is that when the upper-layer service generates data to be transmitted, the network protocol stack directs the entire data stream to a specific interface based on the predetermined network selection result, and then completes the data transmission through that interface. For scenarios with high stability requirements, the system typically uses a wired network for extended periods; for scenarios where cabling is inconvenient or device locations change frequently, wireless networks may be relied upon more heavily.
[0046] However, this type of solution essentially still treats a single transmission task as something that can only be handled by a single network, failing to address the specific differences in data types and struggling to flexibly adjust transmission strategies based on real-time changes in the wireless network. Especially when high-priority and low-priority data coexist, existing solutions often fail to identify the importance of the data and cannot reflect differentiated processing logic in network selection, resulting in critical data being treated the same as ordinary data. When the wireless network's current signal strength is good but its historical performance is unstable, existing technologies typically lack the ability to combine current and historical data analysis, easily leading to the erroneous placement of important data in potentially unstable transmission links; conversely, even if the wireless network has available bandwidth, the system may conservatively and consistently choose a wired network, resulting in idle resources.
[0047] Furthermore, in scenarios involving large data volume transmission or multiple concurrent tasks, a single network path can easily become a bottleneck, manifesting as increased transmission latency, insufficient bandwidth utilization, severe task queuing, and slower response times for critical services. For older or cost-sensitive equipment, simply relying on hardware upgrades to increase bandwidth is unrealistic. Existing solutions lack a mechanism for fine-grained allocation based on data characteristics and network conditions under existing dual-network conditions. Therefore, it is difficult to balance transmission efficiency, stability, and resource utilization, and thus cannot meet the actual needs of complex business scenarios.
[0048] It is evident that the existing approach lacks a flexible data allocation mechanism when the server has both wired and wireless network interfaces. The wired and wireless network cards work independently and cannot coordinate resource utilization. It is also difficult to dynamically adjust the transmission path according to network conditions, resulting in uneven utilization of network resources and difficulty in improving overall transmission efficiency.
[0049] To address the aforementioned issues, this application provides a data allocation method and apparatus for wired and wireless network collaboration. When data is to be transmitted, data characteristics are first acquired and the data type is determined accordingly to distinguish between high-priority and low-priority data. This lays the foundation for subsequent differentiated transmission strategies, avoiding resource waste or transmission delays and making network resource allocation more targeted. When the data to be transmitted is indicated to be high-priority, the current and historical status information of the wireless network is further acquired. The current status information reflects the real-time situation of the wireless network, while the historical status information reveals its changing patterns and trends. Combining these two aspects allows for a more comprehensive and accurate assessment of the wireless network status, providing a reliable basis for the rational allocation of transmission tasks. Subsequently, based on the current and historical status information, the allocation ratio of the data to be transmitted between the wired and wireless network cards is determined, and the data is allocated to the wired and / or wireless network cards for transmission according to this ratio. By combining data type identification with wireless network status analysis, the transmission decision for high-priority data no longer relies on a fixed network or a single empirical rule, achieving targeted collaborative allocation and thus more rationally utilizing wired and wireless network resources, improving data transmission efficiency.
[0050] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.
[0051] The execution subject of the wired-wireless network collaborative data allocation method provided in this application embodiment can be a computing device such as a server or server cluster. The server can be a mobile phone, computer, tablet, or other device. For example, this method is applicable to device environments with wired network cards, wireless network cards, operating systems, and upper-layer data transmission service modules. This application embodiment does not impose any particular limitation on the implementation method of the execution subject, as long as the execution subject can obtain the data characteristics of the data to be transmitted; determine the data type of the data to be transmitted based on the data characteristics, where the data type indicates whether the data to be transmitted is high-priority or low-priority data; when the data type indicates that the data to be transmitted is high-priority data, obtain the current status information and historical status information of the wireless network; determine the allocation ratio of the data to be transmitted between the wired network card and the wireless network card based on the current status information and the historical status information; and allocate the data to be transmitted to the wired network card and / or the wireless network card according to the allocation ratio.
[0052] Figure 1 This is a flowchart illustrating the wired / wireless network collaborative data allocation method provided in this application. The executing entity of this method can be a server storing the wired / wireless network collaborative data allocation method or other servers; this embodiment does not impose any particular limitation. Figure 1 As shown, the method may include:
[0053] S101. Obtain the data characteristics of the data to be transmitted.
[0054] In this step, the data to be transmitted can refer to various types of data that will be transmitted over the network, including files, data streams, etc. For example, the data to be transmitted refers to data objects that have been generated by upper-layer business modules, file synchronization programs, database migration programs, log collection programs, or system management programs and are ready to be sent over the network to the target device or target server. This can be a complete file, or a file fragment, data block, message in a message queue, database page, image fragment, or business protocol payload.
[0055] Data characteristics refer to a set of information that characterizes the data transmission attributes, business attributes, and scheduling attributes of the data to be transmitted, such as data size, system resource requirements, and data integrity requirements. For example, these characteristics may include one or more of the following: data size, task type, task priority label, processing complexity, transmission latency requirements, estimated latency, whether it belongs to core management data, whether it belongs to log data, whether it belongs to database migration data, and the number of data blocks.
[0056] In some specific implementations, the executing entity can be a processor deployed in a server, edge device, or electronic device with dual network interface cards (NICs), or a network scheduling module running in operating system kernel mode or user mode. In a specific implementation, after detecting a new transmission task in the task queue, the processor reads the task identifier from the task description structure, and then calls the file system interface, business application interface, and network scheduling interface based on the task identifier to collect attributes of the object to be transmitted. For example, for file-related tasks, file size, creation time, extension, directory, owner identifier, and access permissions can be obtained by reading file system metadata, and further, based on the directory path or naming rules, it can be identified whether the file belongs to configuration data, log data, backup data, or image data; for business message-related tasks, the business domain to which it belongs can be determined by parsing the application layer protocol header, message topic, business tag field, session identifier, or interface name; for database migration tasks, a corresponding feature set can be formed by reading the migration task list, shard number, table name, transaction level, and recovery point marker.
[0057] In one possible embodiment, acquiring data characteristics is not limited to reading static metadata, but also includes limited parsing of the data content to be transmitted. The processor can read file headers, extensions, protocol fields, or service identifiers to identify specific categories such as compressed packages, configuration files, script files, binary images, structured logs, unstructured logs, and database export files. When the data to be transmitted has been split into multiple data blocks, the processor can further acquire the block sequence number, block size, checksum, and dependencies of each data block, thereby providing basic information for subsequent allocation and reassembly.
[0058] In another possible implementation, the device side can also set up a feature acquisition buffer. When a task enters the transmission process, the acquired data features are first written into the task context in key-value pairs, such as file size, latency constraint, business importance, and fault tolerance level fields, so that subsequent steps can directly call them without repeated acquisition. For missing feature items, this application embodiment allows inference based on common technical knowledge. For example, when the file is located in the system configuration directory and has a small file size, it can be inferred that it has high business importance; when the task originates from the scheduled backup module and has a large continuous data block, it can be inferred that its latency sensitivity is low.
[0059] Based on the above processing, this step achieves a structured understanding of the transmitted object, so that the device no longer regards all data as homogeneous traffic, but establishes a task attribute profile before transmission, providing input conditions for subsequent differentiated path decisions based on data type, thereby avoiding the problem in the existing technology where key data and ordinary data take the same single path due to a lack of data identification capabilities.
[0060] S102. Determine the data type of the data to be transmitted based on the data characteristics. The data type is used to indicate whether the data to be transmitted is high-priority data or low-priority data.
[0061] In this step, data type refers to the task priority classification result abstracted for network transmission scheduling, used to characterize the guarantee level of the data to be transmitted in path selection and resource allocation. Among them, high-priority data is generally larger in size, has higher resource requirements, higher processing complexity, and longer processing time, requiring resource optimization and accelerated transmission; low-priority data is usually smaller in size, has lower system resource requirements, lower processing complexity, and shorter processing time, such as server management data, log files, configuration files, and data that can be transmitted in parallel.
[0062] In some embodiments, explicit rules can be predefined to classify data into high-priority and low-priority categories. For example, the rule-based determination method can be set as follows: data smaller than a preset threshold (e.g., 10MB) with a simple transmission protocol and short expected processing time is classified as low-priority data; data larger than the preset threshold, requiring high bandwidth and other resources, and complex to process, is classified as high-priority data. For instance, daily log files generated by a server are typically small in size and are classified as low-priority data according to the rules; large video file transmissions, due to their large data volume, are classified as high-priority data.
[0063] In other embodiments, after the processor completes data feature acquisition, it inputs the features into the classification module, which then outputs the data type based on preset rules, a scoring model, or a trained machine learning classifier. For example, the rule-based determination method can also be configured with the following logic: when the file size exceeds a preset threshold, the data to be transmitted is identified as high-priority data; when the file size is small or the task is marked as a core configuration file, control command, management log, business switching script, or high-time-sensitivity database increment, the data to be transmitted is identified as low-priority data. The preset threshold can be configured based on device storage performance, link capacity, and business type. For example, 10MB, 50MB, or 100MB can be used as the file size dividing point. The purpose of setting the threshold is to effectively distinguish between small-volume but business-critical data and large-volume data with high latency tolerance, thereby avoiding additional latency caused by different priority data competing for path resources.
[0064] In one possible implementation, the classification module employs a scoring system, mapping file size, business tags, latency requirements, reliability level, fault tolerance, and data source to weighted scores, and calculating a comprehensive priority score. This score can be represented as a weighted sum of the weights of each feature and the normalized results of their corresponding feature values. Data is classified as high-priority when the score is greater than or equal to a preset high-priority threshold; otherwise, it is classified as low-priority. This approach is suitable for scenarios with multiple features and where a single rule is insufficient to cover complex business scenarios.
[0065] In another possible implementation, the classifier can be trained based on historical task samples. Input features include file type, size range, historical retransmission rate, service module identifier, latency requirements, resource requirements, etc., and the output is either high priority or low priority. Regardless of the implementation path, the output of this step is saved as a data type field in the task context and triggers subsequent processing branches. When the determination result is low priority data, in an exemplary implementation, the system can directly adopt a preset default path strategy, such as transmitting entirely through wired network cards, or using wireless network cards in a time-sharing manner when the current system load is high, to reduce the overhead of complex decision-making; when the determination result is high priority data, the next step is taken to further combine the wireless network status to generate a more prudent collaborative allocation strategy.
[0066] Based on the above analysis, this step establishes a clear correlation between network scheduling logic and data importance by determining priority before transmission decisions are made. This helps to identify the importance of data, avoid treating different data equally, and lay the foundation for balancing the stability of critical services with overall resource utilization.
[0067] S103. When the data type indicates that the data to be transmitted is high-priority data, obtain the current status information and historical status information of the wireless network.
[0068] In this step, "wireless network" can refer to a network built using wireless communication technologies, such as Wi-Fi, 4G / 5G networks, etc. "Current status information" can refer to a set of parameters reflecting the immediate availability of the wireless link at the current or near-current transmission time, and may include one or more of the following: wireless signal strength, current bandwidth, link latency, packet loss rate, jitter value, and connection stability. "Historical status information" can refer to a set of statuses obtained by statistically summarizing, aggregating, or extracting trends from the wireless network's performance within a preset time window (such as the past week from the current moment), and may include average signal strength, historical throughput, historical congestion level, historical availability, historical quality level, or historical status labels within the preset time window. Specifically, the current status information reflects whether the wireless network currently possesses the basic conditions to participate in high-priority data transmission, while the historical status information reflects whether the wireless network experiences short-term good performance but long-term instability.
[0069] In some embodiments, wireless network performance indicators can be collected in real time as current status information through the wireless network interface and accompanying monitoring software; relevant historical data can be retrieved from a database or log file storing historical data as historical status information. In one example, the operating system typically has the function of obtaining network status information. For example, in a Linux system, current information such as the connection status and signal strength of the wireless network can be obtained through relevant commands and interfaces; historical network performance data can be extracted from the system log.
[0070] In another example, after detecting that a data type field has high priority, the processor can invoke the wireless status acquisition module to initiate a status query request to the wireless network card driver interface. Simultaneously, it can extract real-time and historical parameters related to the current wireless connection from the operating system network statistics interface, network management daemon, access point feedback information, or the local performance database. Specifically, raw status data can be obtained by reading the received signal strength indicator, link rate, retry count, association status, roaming events, and error count reported by the wireless network card driver. This data, combined with periodic network probing results—such as round-trip latency, jitter, and packet loss rate measured based on heartbeat packets, service layer probe packets, or small-volume trial packets—forms the current status information.
[0071] For historical status information, a status log cache or performance database can be set up locally on the device to record the operating metrics of the wireless network over the past few minutes, hours, or days at a fixed time granularity. For example, the system records signal strength, throughput, and packet loss rate every 5 seconds, calculates the mean and variance every minute, and generates quality level labels every 15 minutes, thus forming historical status information at multiple time scales. When it is necessary to determine the allocation ratio for high-priority data later, the processor can read the historical statistical results of the most recent 5 minutes, 30 minutes, or 24 hours. It should be noted that the setting of the preset time window directly affects the ability of historical status information to represent stability. Shorter time windows are better at reflecting recent fluctuations, while longer time windows are better at identifying long-term unstable patterns. Therefore, in specific implementations, multiple time windows can be maintained simultaneously and used in combination.
[0072] In some possible implementations, historical state information can also be generated by a trend prediction module. This module calculates the slope of change, fluctuation amplitude, and stability score based on a continuously collected state sequence to determine whether the current wireless network is in a deteriorating trend, a recovery trend, or a stable plateau. Connection stability here can be quantified by the number of disconnections, reconnections, drastic rate changes, or signal drops per unit time.
[0073] By simultaneously including both current and historical states in the data collection, misjudgments based solely on signal strength at a single moment are avoided. For example, if a wireless network has a high signal strength at the current moment, but its historical packet loss rate and number of disconnections are high, it indicates insufficient stability and is not suitable for carrying too much high-priority data. Conversely, if both current and historical indicators are good, the wireless link can participate in more data sharing. This allows for a two-dimensional characterization of the wireless network's real-time capabilities and long-term reliability, providing a reliable basis for determining subsequent allocation ratios.
[0074] S104. Based on the current status information and historical status information, determine the allocation ratio of the data to be transmitted between the wired network card and the wireless network card.
[0075] The allocation ratio can refer to the proportional relationship between the wired and wireless network cards in terms of data volume, data block count, number of transmitted bytes, or traffic weight for the same data transmission task. Furthermore, the allocation ratio can be represented by a preset percentage range or by continuously changing dynamic weights, used to guide subsequent data segmentation and path scheduling.
[0076] In this step, wired and wireless network cards are the hardware devices that enable the server to connect to wired and wireless networks. Furthermore, a wired network card typically refers to an Ethernet interface on the device that offers high stability and low latency jitter, while a wireless network card typically refers to an interface that establishes a connection based on Wi-Fi or other wireless LAN protocols.
[0077] In some embodiments, a mapping table between current state information, historical state information, and allocation ratios can be preset. In specific implementations, the corresponding allocation ratio is determined by looking up the table. Alternatively, machine learning algorithms can be used to train a prediction model based on a large amount of historical network state data and corresponding optimal allocation ratio data. When new current and historical state information is obtained, it is input into the model to predict a suitable allocation ratio. For example, a neural network algorithm can be used to build a model to predict the data allocation ratio of wired and wireless networks under different network states.
[0078] In some other embodiments, the current quality score and historical stability score can be calculated based on the current and historical status information of the wireless network, respectively, and then the two scores can be fused according to preset weights to obtain the overall availability score Q of the wireless side. w This involves determining the allocation ratio between wired and wireless network cards based on the default high stability or real-time availability attributes of the wired network. For example, this can be achieved as follows: first, normalize signal strength, current bandwidth, latency, packet loss rate, and jitter; then, configure parameter weights according to the importance of high-priority services to obtain the current quality score; next, normalize and weight historical throughput, historical packet loss rate, historical availability, historical quality level, and historical fluctuation amplitude to obtain the historical stability score; finally, according to Q... w The allocation strategy is calculated by fusing α × current quality score + β × historical stability score, where α and β are weighting coefficients, and the sum of α and β can be set to 1. This formula aims to simultaneously consider the immediate availability and long-term stability of the wireless network. When α is large, the allocation strategy focuses more on current performance; when β is large, the allocation strategy focuses more on historical reliability. For high-priority data, to reduce the risk of critical services being exposed to unstable links, the value of β can be no less than α, or β can be automatically increased when significant historical fluctuations are detected.
[0079] Furthermore, after obtaining Q w Then, the processor can determine the final allocation ratio based on a segmented threshold strategy, a linear interpolation strategy, a fuzzy control strategy, or an adaptive optimization algorithm. For example, if Q... w If the data volume is below the first threshold, the wireless network is deemed unsuitable for carrying high-priority data, and the allocation ratio is set to 100% for wired network cards and 0% for wireless network cards; if Q... wIf the value is between the first and second thresholds, a conservative collaborative mode is adopted, for example, the wired network card undertakes 70% to 90% of the load, and the wireless network card undertakes 10% to 30%; if Q w If the threshold is exceeded, an enhanced collaborative mode is adopted, for example, the wired network card undertakes 40% to 60% of the workload, and the wireless network card undertakes 40% to 60% of the workload.
[0080] In one possible implementation, the allocation ratio is determined by considering both the volume of data to be transmitted and timeliness requirements. For high-priority data that is large in volume and requires high reliability, such as core shards in database migration or incremental updates of model parameters, a portion of the data blocks can be proportionally split and transmitted in parallel by the wireless network card, provided that the wired network card handles the main path, thereby improving overall throughput efficiency. In another possible implementation, the allocation ratio can be adjusted based on the current system load, wired link congestion level, and transmit buffer occupancy rate to avoid high-priority tasks queuing for too long on a single path due to local congestion of the wired network card.
[0081] Furthermore, in some embodiments, historical state information can be input into a preset machine learning model to obtain future state prediction information for the wireless network. Based on this future state prediction information, the allocation ratio can be adjusted to achieve dynamic and intelligent allocation of network resources, better adapting to the dynamic changes in the wireless network state. The preset machine learning model can be a model trained in advance using a large amount of historical wireless network state data and corresponding future state data, capable of predicting the future performance state of the wireless network based on the input historical state information. The future state prediction information is a prediction result about the performance of the wireless network over a future period obtained through the analysis of historical state information by the machine learning model, such as signal strength prediction or bandwidth usage trend prediction for a certain future period.
[0082] For example, historical state information of the wireless network can be extracted from a database or log file and preprocessed to ensure that the data format meets the input requirements of the machine learning model; the preprocessed historical state information is input into a preset machine learning model, and the model outputs future state prediction information after calculation and analysis; based on the future state prediction information, combined with data transmission needs and goals, the allocation ratio of the data to be transmitted between the wired network card and the wireless network card is adjusted.
[0083] Based on the above analysis, it can be seen that by mapping the current state and historical state of the wireless network to a calculable allocation ratio, the transmission strategy of high-priority data no longer depends on fixed network selection or a single empirical rule, but can achieve a dynamic balance between stability assurance and link utilization efficiency.
[0084] S105. According to the allocation ratio, the data to be transmitted is allocated to the wired network card and / or the wireless network card.
[0085] In this context, allocation can refer to the process of segmenting, mapping, queuing, sending, and, if necessary, reassembling the data to be transmitted, based on the aforementioned determined proportions, so that wired and wireless network cards participate in the transmission according to their respective data shares.
[0086] In some examples, when the allocation ratio indicates that only the wired network card is used, the processor maps all the data to be transmitted to the wired transmit queue; when the allocation ratio indicates that the wired network card and the wireless network card share the transmission, the processor first divides the data to be transmitted into multiple data blocks according to a predetermined granularity, then writes the different data blocks into the transmit buffers corresponding to the two network cards, and sends them out through their respective protocol stacks and driver paths.
[0087] Data blocks can be segmented into fixed sizes, such as 64KB, 256KB, or 1MB, or they can be adaptively segmented based on the total file size and the receiver's reassembly capability. The granularity of the segmentation affects parallelism, reassembly overhead, and retransmission efficiency. Smaller granularity facilitates fine-grained scheduling and fast retransmission, while larger granularity helps reduce scheduling frequency and protocol overhead. Therefore, in specific implementations, different granularities can be set according to task type. For example, for high-priority tasks requiring high reliability, the processor can allocate critical control headers, checksums, index information, or first and last data blocks to the wired network interface card (NIC), while distributing non-critical main data blocks proportionally to the wireless NIC. This ensures that even with fluctuations in wireless link performance, the receiver can still rely on the wired side's critical data for verification and recovery.
[0088] In practice, the processor can generate a block sequence number, transmission path identifier, task identifier, and checksum for each data block, and perform reassembly and integrity verification at the receiving end based on these identifiers. For example, when the allocation ratio is 80% wired network cards and 20% wireless network cards, the system can use a block-based allocation method, writing 4 out of every 5 data blocks to the wired transmission queue and 1 to the wireless transmission queue; it can also use a byte-range division method, sending the first 80% of the byte range via wired transmission and the last 20% via wireless transmission; or it can use a weighted round-robin method, allowing the two queues to continuously draw blocks and send them according to preset weights.
[0089] Furthermore, in some embodiments, the transmission rates, acknowledgment responses, retransmission counts, and queue backlog of the two network cards can be continuously monitored during transmission. When the wireless network status is detected to deteriorate below a safety threshold, untransmitted data blocks can be remapped to the wired network card, and data blocks that have been transmitted wirelessly but have timed out and not been acknowledged can also trigger retransmission or path switching, thus forming a dynamic adjustment mechanism during transmission. In addition, for high-priority data with extremely high reliability requirements, embodiments of this application also allow redundant transmission of a small number of critical data blocks, that is, the same critical data block is transmitted simultaneously through both the wired and wireless network cards, and the receiving end receives and deduplicates it according to the first-come-first-served principle.
[0090] In practical applications, wireless networks may experience issues such as excessive load or poor quality, making it difficult to guarantee normal data transmission. Instability in the wireless network status can lead to transmission interruptions, high latency, and data loss. Therefore, in some embodiments, the method may further include: acquiring real-time network load information of the wireless network; when the real-time network load information exceeds a preset load threshold, allocating all data to be transmitted to the wired network card. Alternatively, acquiring the Quality of Service (QoS) indicator information of the wireless network; when the QoS indicator information is lower than a preset QoS threshold, allocating all data to be transmitted to the wired network card.
[0091] Real-time network load information refers to information such as the amount of data transmission tasks undertaken by the wireless network at a specific moment and the network resource usage, covering indicators such as network bandwidth utilization, number of connected devices, and data traffic volume. A preset load threshold is a pre-set standard value for measuring the load level of the wireless network. When the real-time network load information reaches or exceeds this value, it indicates that the wireless network is under high load, which may affect data transmission efficiency and stability. In this embodiment, wireless network monitoring tools or software can be used to collect various load indicator data of the wireless network in real time, such as bandwidth usage and number of connected devices; the collected real-time load data is compared and analyzed with the preset load threshold; if the real-time load information exceeds the preset load threshold, the system automatically triggers an instruction to allocate all data to be transmitted to the wired network card for transmission.
[0092] The Quality of Service (QoS) metrics are used to measure the quality of service provided by the wireless network, including parameters such as network latency, packet loss rate, and jitter. These metrics reflect the performance of the wireless network during data transmission and have a significant impact on the reliability and real-time performance of data transmission. The preset QoS threshold is a pre-defined standard value for the acceptable QoS metrics. When the actual QoS metric is lower than this threshold, it means that the service quality of the wireless network cannot meet the normal data transmission requirements. In this embodiment, network performance testing tools or software modules can be used to periodically acquire QoS metric data of the wireless network, such as network latency and packet loss rate; the acquired QoS metric data is compared with the preset QoS threshold; if the QoS metric is lower than the preset threshold, the system automatically executes an instruction to transfer all data to be transmitted to the wired network card.
[0093] By monitoring wireless network load and QoS metrics in real time, and allocating all data to wired network cards when thresholds are exceeded, data transmission problems caused by high wireless network load or low service quality can be avoided, ensuring the stability and reliability of data transmission.
[0094] The wired-wireless network collaborative data allocation method provided in this application first extracts data features and classifies priorities of the data to be transmitted. Then, for high-priority data, it introduces a joint analysis mechanism of the current and historical states of the wireless network to further generate a dynamic allocation ratio for wired and wireless network cards. This ratio is then implemented as specific data segmentation and dual-path transmission control. This allows wired and wireless network cards to work collaboratively under existing hardware conditions, transforming data transmission decisions from the traditional fixed single-link selection method to a refined collaborative scheduling method that combines data importance and network stability. Therefore, this method reduces the probability of high-priority data being routed to unstable wireless links, causing latency jitter, packet loss, or increased retransmissions. Furthermore, it allows the wireless network to share some of the transmission load when it is available, alleviating the bottleneck of the wired single link, solving the problem of unreasonable network resource allocation in traditional methods, and improving the utilization rate of dual-network resources and overall transmission efficiency.
[0095] Based on the above embodiments, the method described in S104 for determining the allocation ratio of data to be transmitted between the wired network card and the wireless network card based on current state information and historical state information may include: obtaining a preset allocation mapping table, the allocation mapping table containing the correspondence between multiple historical state levels, multiple current state levels and multiple allocation ratios; determining the corresponding historical state level based on historical state information; determining the corresponding current state level based on current state information; and querying the allocation mapping table based on the historical state level and the current state level to obtain the allocation ratio.
[0096] In this embodiment, historical state information is used to characterize the performance of the wireless network within a preset time window, and current state information is used to characterize the real-time link status of the wireless network at the current moment. The allocation mapping table can be stored in memory and read by the processor when a transmission task is triggered. Each historical state level and current state level in the table can correspond to different discrete intervals, so as to convert continuous network state quantities into searchable level identifiers. The allocation ratio is used to indicate the proportion of data to be transmitted between the wired network card and the wireless network card, and the processor can generate the corresponding transmission scheduling result based on this ratio.
[0097] In its implementation, after acquiring historical status information, the processor can comprehensively evaluate it based on historical packet loss rate, historical latency fluctuation, historical throughput stability, or historical signal quality, and map the evaluation results to historical status levels. After acquiring current status information, the processor can determine the current status level based on current signal strength, current link latency, current bandwidth utilization, or current bit error rate. Subsequently, using the historical status level and the current status level as a joint index, the processor retrieves the allocation ratio matching this combination from the allocation mapping table and outputs it to the transmission control module to drive data splitting between the two types of network interface cards (NICs).
[0098] When the historical status level indicates high historical stability of the wireless network and the current status level indicates good current link quality, the allocation mapping table can output a higher proportion of wireless network cards to fully utilize wireless link resources. When the historical status level indicates significant historical fluctuations in the wireless network and the current status level is usable in the short term but uncertain, the allocation mapping table can output an allocation ratio biased towards wired network cards to reduce the transmission risk of critical data in the wireless link. This mapping table can also be pre-configured based on historical statistical data or updated by the network management module according to operational experience; this application embodiment does not limit this.
[0099] In some specific implementations, the allocation mapping table can be stored in various ways. First, a configuration file can be created in the local storage of the data transmission device (such as a processor), storing the allocation mapping table in a specific format (such as JSON or XML). The system reads this configuration file to retrieve the allocation mapping table upon startup. Second, a remote server can be set up to store and manage the allocation mapping table. The data transmission device connects to the remote server via a network to obtain the latest allocation mapping table in real time. Third, the allocation mapping table can be stored in a database, such as MySQL or Oracle. The data transmission device uses database queries to look up the corresponding allocation ratio in the database table based on the determined historical status level and the current status level.
[0100] By introducing a preset allocation mapping table, the allocation ratio is determined based on historical and current status levels, making data allocation more scientific, reasonable, and accurate. This allows for better adaptation to dynamic changes in wireless network status, reduces transmission deviations caused by wireless status fluctuations, and improves data transmission efficiency and stability.
[0101] Based on the above embodiments, the current status information may include the real-time signal strength of the wireless network, and the historical status information may include the stability level of the wireless network.
[0102] Real-time signal strength characterizes the availability of the wireless network link at the current moment, and can correspond to the received signal strength indication value, signal-to-noise ratio value, or normalized signal strength level received by the wireless network card. Stability level characterizes the continuous service capability of the wireless network within a preset historical time window, and is usually obtained by mapping statistics based on the number of connection interruptions, packet loss rate fluctuations, throughput jitter, and reconnection frequency.
[0103] In this embodiment, real-time signal strength can be collected in real time by the operating system's network statistics interface, wireless driver, or wireless network card firmware. The stability level can be calculated and written into a status table by the network management module based on historical sampling data for subsequent matching queries of allocation ratios. In practical applications, real-time signal strength can be represented by a numerical range or by a graded encoding, for example, real-time signal strength can be divided into 1, 2, 3, and 4 levels; the stability level can be represented by discrete labels such as "Good," "Normal," and "Worse." In practical applications, this indicator can also be quantified in other ways, and this embodiment does not limit this.
[0104] Furthermore, the stability level can be calculated as follows: acquire multiple historical operating parameters of the wireless network within a preset historical time period; calculate the historical stability score of the wireless network based on these parameters; and determine the stability level based on the historical stability score. The preset historical time period is a pre-defined time range used to define the time interval for acquiring historical operating parameters of the wireless network. This time period can be set according to actual needs, such as the past hour, day, or week. Different preset historical time periods reflect the historical operating status of the wireless network over different time spans. Historical operating parameters refer to various indicator data related to the operating status of the wireless network over a past period. Examples include signal strength fluctuations, data transmission rate changes, number of network connection interruptions, and packet loss rate. These parameters can reflect the operating status of the wireless network from different perspectives over a past period.
[0105] For example, based on specific application scenarios and requirements, the time range for obtaining historical operating parameters of the wireless network is defined; relevant operating parameters of the wireless network are collected within a preset historical period using network monitoring tools or built-in functions of the device; and multiple historical operating parameters are comprehensively calculated according to a pre-set calculation method. For instance, a weighted average method can be used, assigning different weights to each historical operating parameter, and then multiplying the value of each parameter by its corresponding weight and summing the results to obtain a historical stability score. Finally, based on the pre-set correspondence between score intervals and stability levels, the calculated historical stability score is compared with each score interval to determine the corresponding stability level of the wireless network.
[0106] In practical implementation, when data to be transmitted is determined to be high-priority data, the device first reads the current real-time signal strength of the wireless network, then reads the stability level formed within the corresponding historical window, and inputs both into the matching conditions of the allocation mapping table. Since real-time signal strength reflects the immediate quality of the wireless link, while the stability level reflects the link's continuous performance over a past period, the combination of the two can jointly constrain whether the wireless network card is suitable for carrying some high-priority data. For example, if the real-time signal strength is high and the stability level is high, the allocation weight of the wireless network card can be increased; if the real-time signal strength is high but the stability level is low, the allocation ratio of the wireless network card can be reduced, and more data can be allocated to the wired network card, thereby avoiding the impact of wireless link fluctuations on important data.
[0107] By limiting current state information to real-time signal strength and historical state information to stability levels, the system can simultaneously utilize the immediate availability and historical reliability of the wireless network for decision-making, making the allocation ratio more consistent with the actual operating conditions of the link. This approach reduces the misuse of unstable wireless links, improves the continuity and reliability of data transmission, and enhances the collaborative utilization efficiency of wired and wireless network cards. In scenarios with significant changes in wireless network status, this approach also reduces the risk of misjudging link quality due to a single instance of good signal strength, thereby improving overall transmission performance.
[0108] Based on the above embodiments, the method for determining the data type of the data to be transmitted according to data characteristics described in S102 may include: obtaining the real-time load of the wired network card and the wireless network card; determining a data dynamic threshold based on the real-time load; determining the data type of the data to be transmitted according to the data characteristics and the data dynamic threshold; wherein, if the data amount indicated by the data characteristics is greater than the data dynamic threshold, the data to be transmitted is determined to be high-priority data; if the data amount indicated by the data characteristics is less than or equal to the data dynamic threshold, the data to be transmitted is determined to be low-priority data.
[0109] Among them, real-time load characterizes the resource usage status of wired and wireless network cards at the current moment, reflecting the busy level of the network interface. Dynamic data thresholds serve as variable decision boundaries for classifying data to be transmitted; their values adjust with network load to adapt data type identification results to the current transmission environment. Data characteristics characterize the scale attributes of the data to be transmitted, typically including file size, data block size, or total task volume, allowing the processor to determine the data type.
[0110] In practical implementation, the device's network management module periodically collects the transmission rate, reception rate, bandwidth utilization, queue length, and buffer usage of the wired and wireless network cards, and inputs the results into the load calculation unit. The load calculation unit normalizes these parameters and then performs a weighted sum to obtain the load values for the wired and wireless network cards respectively. Based on the combined load of both, a dynamic data threshold is generated. When the combined load is high, the threshold can be lowered to identify larger amounts of data as high-priority data and trigger a more robust transmission strategy; when the combined load is low, the threshold can be raised to reduce the proportion of high-priority data and improve link utilization efficiency.
[0111] The size of the data to be transmitted can be obtained by the business program reading file attributes, message length or data fragmentation statistics before encapsulating the data packet, and then comparing it with the dynamic data threshold to output the corresponding data type result.
[0112] By acquiring the real-time load of the network interface card (NIC) and determining a dynamic data threshold accordingly, the data type to be transmitted can be determined. This makes data type judgment more flexible and aligned with actual network conditions, avoiding misjudgments caused by fixed thresholds under varying load conditions. This method can better optimize data distribution between wired and wireless NICs, improving network resource utilization efficiency while ensuring data transmission stability.
[0113] Based on the above embodiments, the method described in S105 for allocating data to be transmitted to wired network cards and / or wireless network cards according to the allocation ratio may include: splitting the data to be transmitted into multiple data blocks; determining a first set of data blocks allocated to the wired network cards and a second set of data blocks allocated to the wireless network cards from the multiple data blocks according to the allocation ratio; sending the first set of data blocks through the wired network cards and sending the second set of data blocks through the wireless network cards to instruct the receiving end to reassemble the first set of data blocks and the second set of data blocks into data to be transmitted.
[0114] In this embodiment, the data to be transmitted can be files, logs, images, database fragments, or business messages. When split into multiple data blocks, they can be divided according to fixed byte length, fixed page size, or logical boundaries to facilitate subsequent multi-path transmission. The first data block set and the second data block set can be allocated according to an allocation ratio, or mapped based on data block order and integrity requirements, so that data blocks in different sets can be unambiguously reassembled after transmission. It should be noted that, to ensure that the receiving end can recover the original data, each data block can carry a sequence number, offset, total block count identifier, or verification information. The receiving end uses this information to perform sorting, deduplication, and integrity verification, and then splices the data blocks into the data to be transmitted after confirming that all data blocks have been received.
[0115] Wired and wireless network interface cards (NICs) can be connected to the device's network interface controller, respectively. The operating system's network protocol stack or transmission module calls the corresponding transmission channels to complete data output. When the allocation ratio indicates that the wired link bears a larger load, a larger number of data blocks are allocated to the first data block set and transmitted via the wired NIC; when the wireless link has a higher carrying capacity, the number of data blocks in the second data block set is increased accordingly and transmitted via the wireless NIC. This method allows the same data to be transmitted to be distributed in parallel between the two types of network resources, thereby reducing the impact of single-link congestion on the overall transmission.
[0116] In some specific examples, dedicated data distribution software can be installed on the data sending device. This software is responsible for splitting the data to be transmitted into data blocks and distributing them to the wired and wireless network cards according to the allocation ratio. Alternatively, the operating system kernel can integrate related functions to automatically split and distribute the data to be transmitted during data transmission. Or, network devices such as wired and wireless routers can have built-in data splitting and distribution functions. When data passes through these network devices, the devices split the data into data blocks according to the allocation ratio and send them separately through the wired and wireless interfaces.
[0117] Through the aforementioned block-sharing, allocation, and reassembly mechanism, the data to be transmitted can be precisely mapped to the dual network channels according to the allocation ratio. After receiving data blocks from different network cards, the receiving end can reassemble them based on the identification information. This method makes the data allocation and transmission process clearer and more orderly, improves the utilization rate of dual network resources, reduces transmission queuing time, and improves the efficiency of large-volume data transmission while ensuring data recoverability.
[0118] Based on the above embodiments, the method may further include: when the data type indicates that the data to be transmitted is low-priority data, allocating the data to be transmitted to the wired network card.
[0119] In this embodiment, the wired network card is a wired communication interface located within the device, used to establish a connection with an external network via an Ethernet link and to undertake data transmission and reception tasks. In practical applications, the wired network card can be an integrated network controller or a plug-in expansion network card. Other models of this component can also be selected in practical applications, and this embodiment does not limit the choice.
[0120] In this embodiment, once the processor determines that the data to be transmitted is low-priority data based on its data type, it no longer performs proportional splitting between the wired and wireless network cards for that data. Instead, it directly binds the transmission task corresponding to the data to be transmitted to the wired network card, allowing the wired link to exclusively handle the transmission. If a buffer queue exists within the device, the data to be transmitted can be written to the transmission buffer first, and then the wired network card can read from the buffer and send it, thus reducing the sensitivity of upper-layer services to link switching.
[0121] In this embodiment, the data type identification result serves as the trigger condition for the transmission strategy. Once low-priority data is determined, the control module calls the transmission channel corresponding to the wired network card and sends the data to the target receiving end. Since wired network cards typically have stable link quality and low jitter levels, this type of data can be transmitted in a less interference-prone environment, thereby reducing retransmissions or delays caused by wireless signal fluctuations. By consistently allocating low-priority data to the wired network card, wireless network resources can be reserved for collaborative allocation scenarios involving high-priority data, thus improving the overall utilization efficiency of dual-network resources.
[0122] By explicitly allocating low-priority data to the wired network interface card (NIC), low-priority data can directly enter the wired transmission channel without complex ratio calculations, reducing path selection and scheduling overhead and minimizing uncertainties during transmission. This approach also prevents low-priority data from consuming wireless link resources, ensuring the transmission quality of high-priority data in the wireless network, thereby improving network resource utilization efficiency and the rationality of data transmission.
[0123] Based on the above embodiments, when there are multiple data to be transmitted, the method may further include: acquiring the data characteristics of each data to be transmitted, the data characteristics including the data volume; allocating the data to be transmitted with a data volume indicating large data volume to the wired network card, and allocating the data to be transmitted with a data volume indicating small data volume to the wireless network card, wherein large data volume and small data volume are determined by a preset data volume threshold.
[0124] In this embodiment, the wired network card and the wireless network card correspond to the wired communication interface and the wireless communication interface in the device, respectively. They can be managed uniformly by the operating system network stack and have independent transmission queues established for differentiated scheduling after classification.
[0125] In some examples, when multiple data sets are to be transmitted, the data volume information of each set is obtained using an appropriate method. For example, this can be obtained through data encapsulation header information or by using specialized data statistics tools. Then, the data volume of each set is compared to a pre-set data volume threshold. If the data volume is greater than the threshold, it is classified as large data; if it is less than or equal to the threshold, it is classified as small data. Finally, large data sets are assigned to wired network cards for transmission, while small data sets are assigned to wireless network cards.
[0126] Furthermore, the data volume threshold can be determined based on factors such as network bandwidth, network card performance differences, and service requirements. For example, this data volume threshold can be a fixed threshold set based on past network usage experience and the data volume characteristics of common services. Alternatively, it can be a dynamic threshold adjusted based on a preset dynamic adjustment mechanism, such as real-time monitoring of network load, data transmission success rate, and latency. If the wireless network load is found to be too high, the data transmission success rate to be low, and the latency to be high, it indicates that too much large data may be allocated to the wireless network card. In this case, the data volume threshold can be appropriately lowered to allocate more large data to the wired network card. Conversely, if the wireless network load is low and the wired network card resources are not fully utilized, the data volume threshold can be appropriately increased to increase the data volume transmitted by the wireless network card.
[0127] Furthermore, in specific implementation scenarios of this embodiment, multiple data to be transmitted may originate from different applications, i.e., there may be multiple concurrent applications with data to be transmitted. In this case, in order to allocate network resources more rationally to achieve efficient data transmission, the method may further include: obtaining the data volume of the data to be transmitted corresponding to each concurrent application; establishing a task queue based on the data volume of all data to be transmitted and the task priority of all concurrent applications; wherein, in the task queue, data to be transmitted with a large data volume and high task priority is preferentially allocated to the wired network card, and data with a small data volume and low task priority is preferentially allocated to the wireless network card.
[0128] It's important to further clarify that, firstly, it's necessary to obtain the amount of data to be transmitted for each concurrent application. This step can be achieved by monitoring the application's data transmission interface or by utilizing the system's data statistics functions. For example, in an operating system, network monitoring tools can be used to obtain information about the size of data that each application is transmitting or preparing to transmit.
[0129] Next, a task queue is established based on the total amount of data to be transmitted and the task priorities of all concurrent applications. The task priority setting can take into account factors such as the importance of the application and user needs. For example, video conferencing applications with high real-time requirements can have higher task priorities, while background update applications have relatively lower priorities.
[0130] The task queue is established according to certain rules. Specifically, data indicating large volume and high task priority is prioritized for transmission via wired network cards. This is because large volume transmission typically requires a more stable and high-speed network environment, where wired network cards excel, ensuring fast and stable transmission of large volumes. Conversely, data indicating small volume and low task priority is prioritized for transmission via wireless network cards. Wireless network cards offer high flexibility and are suitable for transmitting small amounts of data with less stringent real-time requirements, thus maximizing the utilization of wireless resources and improving the efficiency of the wireless network.
[0131] Finally, according to the established task queue, the data to be transmitted is sequentially allocated to the corresponding network cards for transmission, thereby optimizing the allocation of network resources and improving the overall data transmission efficiency and network performance.
[0132] In addition, in some examples, when there are multiple data to be transmitted, if all the data to be transmitted corresponds to large data, in order to improve the utilization of wired and wireless networks, it is necessary to allocate the data according to the data allocation method corresponding to the high-priority data in the above embodiments, instead of allocating all the data to the wired network card.
[0133] By acquiring the data volume of each data to be transmitted and dividing it into large and small data according to a preset threshold, and then allocating them to wired and wireless network cards for transmission respectively, data transmission efficiency can be improved and network resource allocation under multi-service concurrency conditions can be enhanced.
[0134] Based on the above embodiments, the method may further include: obtaining task type information for each piece of data to be transmitted, wherein the task type information indicates that the data to be transmitted is target data or other data to be transmitted, and the target data to be transmitted includes at least one of preset management data, configuration data and log data; when the task type information indicates that the data to be transmitted is target data to be transmitted and the data volume indicates that it is small data, the data to be transmitted is allocated to the wired network card.
[0135] Among them, the task type information is used to characterize the business category to which the data to be transmitted belongs, and can be obtained from the task identifier reported by the application, the type field in the file metadata, the description information generated by the business scheduling module, or the tag information issued by the management platform.
[0136] The target transmission data refers to the data set related to device management, parameter configuration, and operation records. Management data carries device control commands, status maintenance commands, or operation and maintenance information; configuration data carries system parameters, network parameters, or service parameters; and log data carries operation logs, audit logs, or fault records. Other transmission data refers to business files, media files, or ordinary synchronization data other than the target transmission data.
[0137] In this embodiment, when data to be transmitted exists, a suitable method is used to obtain the task type information for each piece of data to be transmitted. For example, the task type can be determined by adding identification information at the data source and reading the identification during data transmission; alternatively, the task type can be determined based on the source application or business module of the data. After obtaining the task type information, it is determined whether the data to be transmitted is the target data, and its data volume information is obtained (as described above), and it is determined whether the data volume indicates small data. If the task type information indicates that the data to be transmitted is the target data and the data volume indicates small data, then the data to be transmitted is allocated to the wired network card for transmission. In implementation, after receiving each piece of data to be transmitted, the processor can first read the corresponding task type information, and then perform a joint judgment with the data volume judgment result. When both conditions of target data transmission and small data are met simultaneously, a wired network card allocation instruction is directly generated, and the transmission request of the data to be transmitted is handed over to the wired communication interface for execution.
[0138] By acquiring the task type information of the data to be transmitted, when the data to be transmitted is the target data and the data volume is small, it is allocated to the wired network card for transmission, which ensures the stability and reliability of important small data transmission, is conducive to the normal operation of the system's key functions, and improves the overall management efficiency and operational stability of the system.
[0139] Based on the above embodiments, the method may further include: using an application installed on the operating system to call a driver to bind the wired network card and the wireless network card to form a combined network interface; the wired network card and the wireless network card perform coordinated data transmission through the combined network interface.
[0140] In this system, the application (e.g., APP) can be a network coordination control program installed in the operating system, and the driver (e.g., Driver) can be a network card driver or an extended driver that includes binding management functions. After receiving a transmission request from the upper layer, the application sends binding instructions and interface configuration parameters to the driver. The driver then reads the physical identifiers, link status, and address information of the wired and wireless network cards and maps them to a logically unified network interface. This unified network interface is presented as a unified communication endpoint in the operating system's network stack, allowing business programs to complete data transmission and reception without separately managing two physical interfaces. The wired and wireless network cards can be Ethernet adapters and wireless LAN adapters, respectively. Their interface speed, buffer capacity, and transmit / receive queues can all be uniformly coordinated by the driver. In practical applications, other models of this component can also be selected; this embodiment does not limit this.
[0141] After establishing a unified network interface, the driver allocates data to be transmitted according to a preset coordination strategy. This means some data frames are sent via the wired network card, while others are sent via the wireless network card. At the receiving end, data is reassembled according to sequence number marking, reassembly marking, or checksum information. The unified network interface can also dynamically adjust the transmission load of the two physical network cards based on link connectivity, bandwidth usage, and packet loss feedback to maintain continuity and consistency in the transmission process. When one link fails, the unified network interface can switch the data to be transmitted to the other link to continue transmission, thereby reducing the impact of a single-link failure on services.
[0142] In this way, applications in the operating system can use drivers to establish a logical binding relationship between wired and wireless network cards, and provide unified data transmission capabilities to the outside world using the unified network interface. This method enables dual network resources to work collaboratively in the same transmission task, improves bandwidth utilization, reduces transmission latency caused by single link congestion, and enhances data transmission efficiency and stability in complex network environments.
[0143] As can be seen from the above embodiments, the method of this application dynamically binds wired and wireless network cards and designs an intelligent data allocation algorithm based on network status (including current signal strength and historical performance) to achieve joint utilization of the two network resources, thereby maximizing data transmission efficiency. This method combines the collaborative binding of hardware resources (wired / wireless network cards) with software algorithms (network status detection, data task allocation), breaking through the bandwidth bottleneck of single network transmission in existing technologies. By dynamically adjusting the data allocation strategy, it adapts to the transmission needs of different task types (such as large data volumes, small data volumes, and concurrent tasks), thereby improving overall transmission efficiency without increasing hardware costs.
[0144] The following describes in detail a data allocation method for wired-wireless network collaboration through some embodiments. In some embodiments, Figure 2 The implementation architecture diagram of wireless network and wired network collaboration provided in this application is as follows: Figure 2 As shown, the system includes an upper-layer application OS (Operating System), an APP, and a network card driver to manage data communication; a processor to process and distribute data; and wired and wireless network cards to receive and send data. In this embodiment, a preset teaming software driver binds the wired and wireless network cards together. Then, by detecting the network environment, the processor rationally allocates data tasks to the wired and wireless network cards to accelerate transmission. The teaming software acts as the application layer, calling the driver to implement binding, triggering network detection, and executing data allocation logic; the driver acts as the driver layer, responding to APP calls and binding physical network cards to form a unified network interface; the processor performs data task allocation calculations, splitting, and scheduling; and the wired and wireless network cards are used to actually send and receive data.
[0145] As a further example, in practical applications, by installing a Teaming-enabled app in the OS, the driver can bind the wired and wireless network cards to form a bonded network interface, enabling collaborative communication between the wired and wireless network cards. For instance, in Windows or Linux systems, after installing the Teaming software, the driver layer integrates the MAC addresses, IP addresses, and other information of the two physical network cards (wired and wireless) to generate a logical bonded network interface.
[0146] Furthermore, Figure 3 The specific architecture diagram of the wireless network and wired network binding provided in this application is as follows: Figure 3 As shown, the execution entity is mainly divided into an application block and a hardware module. In the application block, an app that supports teaming is installed on the operating system. The app first bonds the wireless network card driver (i.e., the WIFI driver) and the wired network card driver (i.e., the LAN driver) together, thereby realizing the pairing and cooperation between the hardware wired network card and the wireless network card.
[0147] Based on the above embodiments, Figure 4 This is a data allocation diagram corresponding to the low-priority data provided in this application, as shown below. Figure 4As shown, this data allocation method is used to handle low-priority data (corresponding to small task data). This type of data is typically small in size, requires few resources (i.e., low demand on system resources), requires little effort (i.e., low processing complexity), and takes little time. Examples include server management data, log file configuration files, and parallel transmission. In this data allocation method, if small task data needs to be transmitted, after judgment by the upper-layer data, the processor will assign the task to the wired network card, allowing the wired network card to process this type of data independently and transmit it to the data receiving end.
[0148] Based on the above embodiments, Figure 5 A data allocation diagram corresponding to the high-priority data provided in this application is shown below. Figure 5 As shown, this data allocation method is used to handle high-priority data (corresponding to large task data). This type of data is large in size, requires many resources, involves significant effort, and is time-consuming, necessitating resource optimization and acceleration. Examples include database migration, system-level data interaction, or cross-platform data transfer scenarios involving large volumes of data transmission. In this data allocation method, when the data is considered large task data, the upper layer transmits this information to the processor. Throughout the system, Wi-Fi network detection generates two reports, which are provided to the processor as a data allocation reference: the current Wi-Fi network status and the historical Wi-Fi network status. The processor combines these three pieces of information—the current Wi-Fi network status, the historical Wi-Fi network status, and the task characteristics of the data (such as data size, concurrent tasks, etc.)—and, according to the designed algorithm, allocates the task data to the wired and wireless network cards according to a certain task ratio, thereby completing the data transmission / reception.
[0149] Furthermore, the designed algorithm can be determined based on the processor task allocation reference table shown in Table 1.
[0150] Table 1 Processor Task Allocation Reference Table
[0151]
[0152] As shown in Table 1, the historical status of the Wi-Fi network is preset to three levels: Good, Normal, and Worse; the current status of the Wi-Fi network is divided into four levels: 4, 3, 2, and 1, with higher numbers indicating stronger signals. The data processing task is assigned in increments of 10, and then, under the above three conditions, the processor allocates the data accordingly.
[0153] Based on the above embodiments, when there are multiple data to be transmitted (i.e., multi-task data), Figure 6 This application provides a data allocation diagram for multiple data items to be transmitted, as shown below. Figure 6As shown, for concurrent multi-application data that needs processing, large amounts of data should be distributed to the wired network, while smaller amounts should be distributed to the wireless network for accelerated synchronous transmission. If some of the data includes core management data, or core configuration files and log data (i.e., the target transmission data), then the data should be distributed to the wired network for transmission. Furthermore, if the multi-task data corresponds to large task data, then refer to... Figure 5 Data allocation method corresponding to the embodiment.
[0154] The wired-wireless network collaborative data allocation method provided in this application's embodiments, through the design of an APP enabling the bonding collaboration between wireless and wired network cards, and then through a newly developed network environment detection and data allocation algorithm, effectively and efficiently manages data allocation. Based on the detected real-time network environment, different data transmission processing tasks and different data transmission loads are assigned, improving the utilization rate of dual-network collaboration and accelerating data transmission processing. For single-application data, if the data is small, it is directly allocated to the wired network card; if the data is large, it is allocated between the wired and wireless network cards for acceleration, depending on the specific circumstances. For concurrent multi-application data requiring processing, large amounts of data are allocated to the wired network, while small amounts are allocated to the wireless network, accelerating synchronous transmission.
[0155] Figure 7 A schematic diagram of the structure of the wired and wireless network cooperative data distribution device provided in this application is shown below. Figure 7 As shown, the wired / wireless network collaborative data distribution device 70 provided in this embodiment includes:
[0156] The first acquisition module 701 is used to acquire the data characteristics of the data to be transmitted;
[0157] The first determining module 702 is used to determine the data type of the data to be transmitted based on the data characteristics. The data type is used to indicate whether the data to be transmitted is high-priority data or low-priority data.
[0158] The second acquisition module 703 is used to acquire the current status information and historical status information of the wireless network when the data type indicates that the data to be transmitted is high-priority data.
[0159] The second determining module 704 is used to determine the allocation ratio of the data to be transmitted between the wired network card and the wireless network card based on the current status information and historical status information.
[0160] The allocation module 705 is used to allocate the data to be transmitted to the wired network card and / or the wireless network card according to the allocation ratio.
[0161] In one possible implementation, the second determining module 704 can also be used to: obtain a preset allocation mapping table, which contains the correspondence between multiple historical state levels, multiple current state levels and multiple allocation ratios; determine the corresponding historical state level based on the historical state information; determine the corresponding current state level based on the current state information; and query the allocation mapping table based on the historical state level and the current state level to obtain the allocation ratio.
[0162] In one possible implementation, the first determining module 702 can also be used to: obtain the real-time load of the wired network card and the wireless network card; determine the data dynamic threshold based on the real-time load; determine the data type of the data to be transmitted according to the data characteristics and the data dynamic threshold; wherein, if the data amount indicated by the data characteristics is greater than the data dynamic threshold, the data to be transmitted is determined to be high-priority data; if the data amount indicated by the data characteristics is less than or equal to the data dynamic threshold, the data to be transmitted is determined to be low-priority data.
[0163] In one possible implementation, the allocation module 705 can also be used to: split the data to be transmitted into multiple data blocks; determine, according to the allocation ratio, a first set of data blocks allocated to the wired network card and a second set of data blocks allocated to the wireless network card from the multiple data blocks; send the first set of data blocks through the wired network card and send the second set of data blocks through the wireless network card to instruct the receiving end to reassemble the first set of data blocks and the second set of data blocks into the data to be transmitted.
[0164] In one possible implementation, the allocation module 705 can also be used to allocate the data to be transmitted to the wired network card when the data type indicates that the data to be transmitted is low-priority data.
[0165] In one possible implementation, the allocation module 705 can also be used to: acquire the data characteristics of each data to be transmitted, the data characteristics including the data volume; allocate the data to be transmitted with the data volume indicated as large to the wired network card, and allocate the data to be transmitted with the data volume indicated as small to the wireless network card, wherein large data and small data are determined by a preset data volume threshold.
[0166] In one possible implementation, the allocation module 705 can also be used to: obtain task type information for each piece of data to be transmitted, wherein the task type information indicates that the data to be transmitted is target data or other data, and the target data includes at least one of preset management data, configuration data and log data; when the task type information indicates that the data to be transmitted is target data and the data volume indicates that it is small data, the data to be transmitted is allocated to the wired network card.
[0167] In one possible implementation, the allocation module 705 can also be used to: bind the wired network card and the wireless network card by calling the driver through an application installed in the operating system to form a combined network interface; the wired network card and the wireless network card perform coordinated data transmission through the combined network interface.
[0168] The wired and wireless network collaborative data distribution device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.
[0169] Figure 8 A schematic diagram of the structure of the electronic device provided in this application. Figure 8 As shown, the electronic device 80 provided in this embodiment includes at least one processor 801 and a memory 802. Optionally, the device 80 further includes a communication component 803. The processor 801, memory 802, and communication component 803 are connected via a bus 804.
[0170] In a specific implementation, at least one processor 801 executes computer execution instructions stored in memory 802, causing at least one processor 801 to perform the above-described method.
[0171] The specific implementation process of processor 801 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.
[0172] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.
[0173] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.
[0174] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.
[0175] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.
[0176] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.
[0177] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.
[0178] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.
[0179] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.
[0180] The units described 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 can be selected to achieve the purpose of this embodiment according to actual needs.
[0181] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0182] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, 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 steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0183] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.
[0184] It should be understood that the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover but not exclude inclusion. For example, a product or device that includes a series of components is not necessarily limited to those components that are explicitly listed, but may include other components that are not explicitly listed or that are inherent to such product or device.
[0185] As used in this application, the term "module" means any known or subsequently developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code capable of performing the functions associated with that element.
[0186] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.
Claims
1. A data allocation method for wired and wireless network collaboration, characterized in that, include: Obtain the data characteristics of the data to be transmitted; Based on the data characteristics, the data type of the data to be transmitted is determined, and the data type is used to indicate whether the data to be transmitted is high-priority data or low-priority data; When the data type indicates that the data to be transmitted is high-priority data, obtain the current status information and historical status information of the wireless network; Based on the current status information and the historical status information, determine the allocation ratio of the data to be transmitted between the wired network card and the wireless network card; According to the allocation ratio, the data to be transmitted is allocated to the wired network card and / or the wireless network card.
2. The method according to claim 1, characterized in that, The step of determining the allocation ratio of the data to be transmitted between the wired network card and the wireless network card based on the current state information and the historical state information includes: Obtain a preset allocation mapping table, which contains the correspondence between multiple historical state levels, multiple current state levels and multiple allocation ratios; Based on the historical status information, the corresponding historical status level is determined; Based on the current status information, determine the corresponding current status level; Based on the historical status level and the current status level, the allocation mapping table is queried to obtain the allocation ratio.
3. The method according to claim 1, characterized in that, The current status information includes the real-time signal strength of the wireless network, and the historical status information includes the stability level of the wireless network.
4. The method according to claim 1, characterized in that, Determining the data type of the data to be transmitted based on the data characteristics includes: Get the real-time load of wired and wireless network cards; Based on the real-time load, determine the dynamic threshold of the data; The data type of the data to be transmitted is determined based on the data characteristics and the data dynamic threshold. Specifically, if the amount of data indicated by the data feature is greater than the data dynamic threshold, the data to be transmitted is determined to be high-priority data; if the amount of data indicated by the data feature is less than or equal to the data dynamic threshold, the data to be transmitted is determined to be low-priority data.
5. The method according to claim 1, characterized in that, The step of allocating the data to be transmitted to the wired network card and / or the wireless network card according to the allocation ratio includes: The data to be transmitted is split into multiple data blocks; Based on the allocation ratio, a first set of data blocks to be allocated to the wired network card and a second set of data blocks to be allocated to the wireless network card are determined from the plurality of data blocks; The first data block set is sent via the wired network card, and the second data block set is sent via the wireless network card, so as to instruct the receiving end to reassemble the first data block set and the second data block set into the data to be transmitted.
6. The method according to any one of claims 1-5, characterized in that, The method further includes: When the data type indicates that the data to be transmitted is low-priority data, the data to be transmitted is allocated to the wired network card.
7. The method according to any one of claims 1-5, characterized in that, When there are multiple data items to be transmitted, the method further includes: Obtain the data characteristics of each piece of data to be transmitted, including the data volume; Data to be transmitted that is indicated as large data volume is allocated to the wired network card, and data to be transmitted that is indicated as small data volume is allocated to the wireless network card, wherein the large data volume and the small data volume are determined by a preset data volume threshold.
8. The method according to claim 7, characterized in that, The method further includes: Obtain task type information for each piece of data to be transmitted. The task type information indicates that the data to be transmitted is target data or other data to be transmitted. The target data to be transmitted includes at least one of preset management data, configuration data, and log data. When the task type information indicates that the data to be transmitted is target data and the data volume indicates that it is small data, the data to be transmitted is allocated to the wired network card.
9. The method according to any one of claims 1-5, characterized in that, The method further includes: An application installed on the operating system calls the driver to bind the wired network card and the wireless network card, forming a combined network interface; the wired network card and the wireless network card perform coordinated data transmission through the combined network interface.
10. A data distribution device for wired and wireless network collaboration, characterized in that, include: The first acquisition module is used to acquire the data characteristics of the data to be transmitted; The first determining module is used to determine the data type of the data to be transmitted based on the data characteristics, wherein the data type is used to indicate whether the data to be transmitted is high-priority data or low-priority data. The second acquisition module is used to acquire the current status information and historical status information of the wireless network when the data type indicates that the data to be transmitted is high-priority data. The second determining module is used to determine the allocation ratio of the data to be transmitted between the wired network card and the wireless network card based on the current status information and the historical status information. The allocation module is used to allocate the data to be transmitted to the wired network card and / or the wireless network card according to the allocation ratio.