Multi-link low-latency communication method, device, storage medium and electronic device

Abstract

The embodiment of the present invention provides a multi-link low-latency communication method, device, storage medium and electronic device, the method comprising: determining a low-latency service support link set between an access point multi-link device and a non-access point multi-link device; establishing a mapping between a low-latency service flow and one or more low-latency service support links in the low-latency service support link set; and transmitting the low-latency service flow on the one or more low-latency service support links. In the present invention, by real-time evaluation and determination of a low-latency service support link set, a mapping between a low-latency service flow and related links is established, and low-latency service transmission is achieved on one or more links in the low-latency service support link set, thereby meeting the low-latency service access requirements to a large extent.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of communications, and in particular, to a multi-link low-latency communication method, device, storage medium, and electronic device. Background Art

[0002] The next generation WIFI standard (IEEE 802.11be) proposes multi-link operation and communication technology. Figure 1 It is a structural diagram of the multi-link operation architecture in the related art, such as Figure 1 As shown, a multi-link device (MLD) has multiple attached stations (STAs). An MLD whose attached stations are all access points (APs) is an AP multi-link device (AP MLD), while an MLD whose attached stations are all non-access points (non-APs) is a non-AP multi-link device (Non-AP MLD). The STAs in the non-AP MLD can be associated with corresponding APs in the AP MLD, and each link can have its own communication channel. Without differentiated access to communication links based on service type and QoS requirements, the advantages of multi-link in carrying low-latency services will be difficult to realize.

[0003] The current Enhanced Distributed Channel Access (EDCA) mechanism of Wi-Fi (Wireless Fidelity) uses a contention-based channel access method, which cannot strictly guarantee the transmission requirements of low-latency services. Furthermore, the reliability and robustness of the hybrid coordination function (HCF) controlled channel access (HCCA) are greatly reduced if data transmission is interfered with by overlapping basic service sets (OBSS), resulting in its limited application.

[0004] To address the above issues, no effective solutions have been proposed so far. Summary of the Invention

[0005] Embodiments of the present invention provide a multi-link low-latency communication method, apparatus, storage medium, and electronic device to at least solve the problem in related arts that the WIFI channel access mechanism is difficult to meet the low-latency service access requirements.

[0006] According to one embodiment of the present invention, a multi-link low-latency communication method is provided, comprising: determining a low-latency service support link set between an access point multi-link device and a non-access point multi-link device; establishing a mapping between a low-latency service flow and one or more low-latency service support links in the low-latency service support link set; and transmitting the low-latency service flow on the one or more low-latency service support links.

[0007] In an exemplary embodiment, determining the low-latency service support link set between the access point multi-link device and the non-access point multi-link device includes: determining the low-latency service support links between the access point multi-link device and the non-access point multi-link device based on at least one of the following: channel access mode, channel environment, link load or performance statistics, admission control, low-latency service priority, and specific quality of service (QoS) type service access; and forming the determined low-latency service support links into the low-latency service support link set.

[0008] In an exemplary embodiment, determining the low-latency service support link between the access point multi-link device and the non-access point multi-link device includes: according to the QoS requirements and / or configuration parameters of the low-latency service, determining the low-latency service support link from multiple links between the access point multi-link device and the non-access point multi-link device according to at least one of the following selection rules: whether the priority, priority queue or channel access parameter corresponding to the low-latency service is supported; whether an admission control policy is adopted; whether the channel access method for optimizing the access of the low-latency service is adopted; whether the BSS load meets the access requirements of the low-latency service; whether the throughput meets the requirements of the low-latency service; whether the number of packet loss and / or retransmissions exceeds a preset threshold; whether the access of the specific QoS type service is restricted; whether the delay in the uplink or downlink direction meets the access requirements of the low-latency service.

[0009] In an exemplary embodiment, the type of delay parameter includes at least one of the following: access delay of all ACs (Access Controllers), access delay of a specific AC, transmission delay, BSS internal delay, BSS external delay, and achievable optimal delay; the value of the delay parameter is one of the following: average delay, maximum delay, and delay at a specific percentile.

[0010] In an exemplary embodiment, the channel access method for optimizing the low-latency service access includes: using different access time periods and / or access channels for the low-latency service type and other service types.

[0011] In an exemplary embodiment, after determining the low-latency service support link between the access point multi-link device and the non-access point multi-link device, the method further includes: monitoring the communication environment and related parameters involved in the selection rule in real time based on the current network status; if the communication environment and related parameters involved in the selection rule are updated, re-determining the current low-latency service support link; if the communication environment and related parameters involved in the selection rule are not updated, retaining the original low-latency service support link.

[0012] In an exemplary embodiment, establishing a mapping between a low-latency service flow and one or more low-latency service support links in the low-latency service support link set includes: establishing a mapping between the low-latency service flow and one or more low-latency service support links in the low-latency service support link set through negotiation between the access point multi-link device and the non-access point multi-link device.

[0013] In an exemplary embodiment, a mapping is established between the low-latency service flow and one or more low-latency service support links in the low-latency service support link set, including at least one of the following: establishing a mapping between the low-latency service flow and multiple working links, wherein the multiple working links are low-latency service support links in different time periods; establishing a mapping between the low-latency service flow and one or more specific low-latency service support links.

[0014] In an exemplary embodiment, a mapping is established between the low-latency service flow and multiple working links, including: mapping the low-latency service flow to all working links, and selecting one or more of the working links belonging to the low-latency service support links as the transmission links of the low-latency service flow according to different time periods.

[0015] In an exemplary embodiment, establishing a mapping between the low-latency service flow and a specific low-latency service support link includes mapping a traffic identifier TID of the low-latency service with one or more selected specific low-latency service support links.

[0016] In an exemplary embodiment, after establishing a mapping between the low-latency service flow and one or more low-latency service support links in the low-latency service support link set, it also includes: when the low-latency service support link set is updated, re-establishing the mapping between the low-latency service flow and one or more low-latency service support links through negotiation between the access point multi-link device and the non-access point multi-link device.

[0017] In an exemplary embodiment, a mapping is established between the low-latency service flow and the low-latency service support link through negotiation between the access point multi-link device and the non-access point multi-link device, including at least one of the following: for a downlink low-latency service flow, the access point multi-link device determines the low-latency service support link set, and negotiates with the non-access point multi-link device to determine the mapping between the low-latency service flow and the low-latency service support link; for an uplink low-latency service flow, the non-access point multi-link device determines the low-latency service support link set, and negotiates with the access point multi-link device to determine the mapping between the low-latency service and the low-latency service support link; or, the access point multi-link device determines the low-latency service support link set, and negotiates with the non-access point multi-link device to determine the mapping between the low-latency service and the low-latency service support link.

[0018] According to another embodiment of the present invention, a multi-link low-latency communication device is provided, including: a determination module for determining a low-latency service support link set between an access point multi-link device and a non-access point multi-link device; a mapping module for establishing a mapping between a low-latency service flow and one or more low-latency service support links in the low-latency service support link set; and a transmission module for transmitting the low-latency service flow on the one or more low-latency service support links.

[0019] According to yet another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.

[0020] According to another embodiment of the present invention, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.

[0021] In the above-mentioned embodiment of the present invention, by real-time evaluation and determination of the low-latency service support link set, a mapping between the low-latency service flow and the related links is established, and the transmission of low-latency services is realized on one or more links in the low-latency service support link set, thereby meeting the low-latency service access requirements to a large extent. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a structural diagram of a multi-link operation architecture in related art;

[0023] Figure 2 is a flow chart of a multi-link low-latency communication method according to an embodiment of the present invention;

[0024] Figure 3 is a structural block diagram of a multi-link low-latency communication device according to an embodiment of the present invention;

[0025] Figure 4 is a flow chart of a multi-link low-latency communication method according to an embodiment of the present invention;

[0026] Figure 5 is a schematic diagram of classifying communication link sets of multi-link devices according to an embodiment of the present invention;

[0027] Figure 6 is a flowchart of real-time evaluation and update of a low-latency service support link set according to an embodiment of the present invention;

[0028] Figure 7 Schematic diagram of the mapping and communication process of low-latency services and related links according to an embodiment of the present invention;

[0029] Figure 8 1 is a schematic diagram of the mapping and communication process between low-latency services and working links according to an embodiment of the present invention;

[0030] Figure 9 The figure is a schematic diagram of the mapping and communication process between low-latency services and low-latency support links according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and in combination with embodiments.

[0032] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0033] This embodiment provides a multi-link low-latency communication method, which can be run on a multi-link device (MLD). Figure 2 is a flow chart of a method according to an embodiment of the present invention, such as Figure 2 As shown, the process may include the following steps:

[0034] Step S202, determining a low-latency service support link set between the access point multi-link device and the non-access point multi-link device;

[0035] Step S204: establishing a mapping between a low-latency service flow and one or more low-latency service support links in the low-latency service support link set;

[0036] Step S206: Transmit the low-latency service flow on the one or more low-latency service support links.

[0037] In step S202 of this embodiment, the low-latency service support links between the access point multi-link device and the non-access point multi-link device may be determined based on at least one of the following: channel access mode, channel environment, link load or performance statistics, admission control, low-latency service priority, and specific quality of service (QoS) type service access; and the determined low-latency service support links are combined into the low-latency service support link set.

[0038] In step S202 of this embodiment, the low-latency service supporting link may be determined from multiple links between the access point multi-link device and the non-access point multi-link device according to the QoS requirements and / or configuration parameters of the low-latency service, according to at least one of the following selection rules: whether the priority, priority queue, or channel access parameter corresponding to the low-latency service is supported; whether an admission control policy is adopted; whether the channel access method for optimizing access to the low-latency service is adopted; whether the BSS load meets the access requirements of the low-latency service; whether the throughput meets the requirements of the low-latency service; whether the number of packet losses and / or retransmissions exceeds a preset threshold; whether access to the specific QoS type service is restricted; and whether the uplink or downlink latency meets the access requirements of the low-latency service. The latency parameter types may include one or more of the following: access latency of all ACs, access latency of a specific AC, transmission latency, BSS internal latency, BSS external latency, and achievable optimal latency. The various types of latency parameters may include average latency, maximum latency, and latency at a specific percentile.

[0039] In this embodiment, the channel access method for optimizing the low-latency service access may include: using different access time periods and / or access channels for the low-latency service type and other service types.

[0040] After step S202 of this embodiment, it may also include: real-time monitoring of the communication environment and related parameters involved in the selection rule according to the current network conditions; if the communication environment and related parameters involved in the selection rule are updated, re-determining the current low-latency service support link; if the communication environment and related parameters involved in the selected rule are not updated, continuing to retain the original low-latency service support link.

[0041] In step S204 of this embodiment, a mapping may be established between the low-latency service flow and one or more low-latency service support links in the low-latency service support link set through negotiation between the access point multi-link device and the non-access point multi-link device.

[0042] In this embodiment, a mapping is established between the low-latency service flow and one or more low-latency service support links in the low-latency service support link set, including at least one of the following: establishing a mapping between the low-latency service flow and multiple working links, wherein the multiple working links are low-latency service support links in different time periods; establishing a mapping between the low-latency service flow and one or more specific low-latency service support links.

[0043] In this embodiment, establishing a mapping between the low-latency service flow and multiple working links may include: mapping the low-latency service flow to all working links, and selecting one or more of the working links belonging to the low-latency service support links as the transmission links of the low-latency service flow according to different time periods.

[0044] In this embodiment, establishing a mapping between the low-latency service flow and a specific low-latency service support link may include: mapping the traffic identifier of the low-latency service with one or more selected specific low-latency service support links.

[0045] After step S204 of this embodiment, the method may further include: when the low-latency service support link set is updated, re-establishing the mapping between the low-latency service flow and the one or more low-latency service support links through negotiation between the access point multi-link device and the non-access point multi-link device.

[0046] In this embodiment, a mapping is established between the low-latency service flow and the low-latency service support link through negotiation between the access point multi-link device and the non-access point multi-link device, including at least one of the following: for a downlink low-latency service flow, the access point multi-link device determines the low-latency service support link set and negotiates with the non-access point multi-link device to determine the mapping between the low-latency service flow and the low-latency service support link; for an uplink low-latency service flow, the non-access point multi-link device determines the low-latency service support link set and negotiates with the access point multi-link device to determine the mapping between the low-latency service and the low-latency service support link; or, the access point multi-link device determines the low-latency service support link set and negotiates with the non-access point multi-link device to determine the mapping between the low-latency service and the low-latency service support link.

[0047] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0048] In this embodiment, a multi-link low-latency communication device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments. Details that have been described will not be repeated here. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0049] Figure 3 1 is a structural block diagram of a multi-link low-latency communication device according to an embodiment of the present invention. The device can be located in a multi-link device, for example, in an AP multi-link device or a non-AP multi-link device, or can be installed in conjunction with a multi-link device. Figure 3 As shown, the multi-link low-latency communication device 100 may include a determination module 10, a mapping module 20 and a transmission module 30.

[0050] The determination module 10 is configured to determine a low-latency service support link set between an access point multi-link device and a non-access point multi-link device.

[0051] The mapping module 20 is used to establish a mapping between a low-latency service flow and one or more low-latency service support links in the low-latency service support link set.

[0052] The transmission module 30 is used to transmit the low-latency service flow on the one or more low-latency service support links.

[0053] It should be noted that the above modules can be implemented through software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0054] In order to facilitate the understanding of the technical solution provided by the present invention, embodiments of the present invention will be described in detail below in conjunction with specific scenarios.

[0055] To address the problem that the current Wi-Fi channel access mechanism cannot meet the requirements for low-latency service access, this embodiment proposes a multi-link-based low-latency service transmission mechanism. For multiple links, links are differentiated according to the communication environment, access method, and policy. The low-latency service support link set is evaluated and determined in real time. By mapping low-latency service flows with related links, low-latency services are transmitted on one or more links in the low-latency service support link set.

[0056] Figure 4 is a flow chart of a multi-link low-latency communication method according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps:

[0057] Step S402: Determine a low-latency service support link set.

[0058] In step S402 of this embodiment, whether a link supports low-latency services (referred to as a low-latency service support link) is determined based on one or more conditions, such as the channel access method, the channel environment, link load or performance statistics, whether admission control is supported, whether low-latency service priority is supported, and whether access to services of a specific QoS (Quality of Service) type is restricted. All low-latency service support links of the current multi-link device (MLD) form a low-latency service support link set.

[0059] Figure 5 Schematic diagram of the classification and mutual relationship of MLD communication link sets according to an optional embodiment of the present invention, such as Figure 5 As shown in Figure 1, the communication links between an access point multi-link device (AP MLD) and a non-access point multi-link device (Non-AP MLD) can be divided into the following types:

[0060] Supported multilink set: indicates the set of communication links supported between two communicating MLD devices;

[0061] Low-latency service support link set: represents the link set that meets the specific low-latency service access conditions;

[0062] Enabled low-latency service support link set: indicates the set of links in the low-latency service support link set that have low-latency service access.

[0063] Low-latency service support link set corresponding to a specific service: indicates the set of low-latency service support links in the enabled low-latency service support link set that supports a specific low-latency service flow.

[0064] In this embodiment, step S402 may specifically include: determining, according to the QoS requirements and / or configuration parameters of the low-latency service, whether a link supporting the low-latency service is one of multiple links supported between a non-access point multi-link device (non-AP) MLD and an access point multi-link device (AP MLD) that requires access to the low-latency service, according to one or more of the following rules:

[0065] (1) Whether the priority, priority queue, and channel access parameters corresponding to low-latency services are supported;

[0066] (2) Whether a strict admission control strategy is adopted;

[0067] (3) Whether a channel access method that optimizes low-latency service access is adopted, including whether low-latency service types are distinguished from other service types in terms of access time and / or access channel. Distinguishing low-latency service types from other service types in terms of access time (or channel) means that low-latency service types and other service types use different access time periods (or sub-channels / auxiliary channels), and the access time periods (or sub-channels / auxiliary channels) are controllable or configurable;

[0068] (4) Whether the BSS load of the current link meets the access requirements of low-latency services;

[0069] (5) Whether the currently achievable throughput meets the requirements of low-latency services;

[0070] (6) Whether the number of packet losses and / or retransmissions within a specific time period exceeds a preset threshold;

[0071] (7) Whether to restrict access to services of specific QoS types;

[0072] (8) Whether the latency performance in the uplink or downlink direction meets the access requirements of low-latency services. The latency parameter types include one or more of the following: access latency of all ACs, access latency of specific ACs, transmission latency, BSS internal latency, BSS external latency, and optimal achievable latency. Various types of latency parameters may include average latency, maximum latency, and latency at a specific percentile.

[0073] In this embodiment, the multi-link device (MLD) may also update the low-latency service support link based on the current operating status of the network link.

[0074] Figure 6 is a schematic diagram of a real-time evaluation and update method of a low-latency service support link set according to an optional embodiment of the present invention, such as Figure 4As shown, the multi-link device set is updated based on changes in the channel access method, channel environment, link load or performance statistics, whether admission control is supported, whether a specific QoS type of service access is supported, etc., and may specifically include:

[0075] (1) selecting rules and related parameters from the low-latency service support link selection rule entries according to the QoS requirements and / or configuration parameters of the low-latency service;

[0076] (2) Determine the current low-latency service support link according to the communication environment and relevant parameters involved in the selected rules;

[0077] (3) The communication environment and related parameters involved in the selected rules are monitored in real time according to the current network conditions. If the communication environment and related parameters involved in the selected rules are updated, the current low-latency service support link is re-determined. If the communication environment and related parameters involved in the selected rules are not updated, the original low-latency service support link is retained.

[0078] Step S404: Implement mapping and communication between low-latency services and related links.

[0079] In step S402 of this embodiment, when a station (STA) of the MLD initiates a low-latency service access request, the current low-latency service support link is first determined according to the QoS requirements of the low-latency service and the network environment. If the current MLD does not have a low-latency service support link, the request is rejected; if the current MLD does have a low-latency service support link, the request is accepted. Mapping between service flows and low-latency service support links is performed using two methods: one is mapping between low-latency service flows and all working links, and the other is mapping between low-latency service flows and specific low-latency service support links. Regardless of which mapping method is used, during the low-latency service access process, low-latency service transmission is guaranteed in one or more links in the low-latency service support link set.

[0080] Figure 7 Schematic diagram of the mapping and communication mode of low-latency services and related links according to an optional embodiment of the present invention, such as Figure 7As shown, for a multi-link device (MLD), a low-latency service link selection module and a service flow-to-link mapping module can be integrated into the multi-link operation module to determine the low-latency service support link set and map low-latency services to related links. During the service flow access process, one or more mapped low-latency service support links are selected for transmission. For an access point multi-link device (AP MLD) and its associated non-access point multi-link device (Non-AP MLD), the low-latency service link selection module can be implemented in the AP MLD and / or Non-AP MLD, while the service flow-to-link mapping module is implemented in both the AP MLD and Non-AP MLD. The mapping of low-latency services to related links must be negotiated between the AP MLD and / or Non-AP MLD. For downlink low-latency service flows, the AP MLD determines the low-latency service support link set and negotiates with the Non-AP MLD to determine the mapping of low-latency services to related links. During the service flow access process, the AP MLD selects one or more mapped low-latency service support links for transmission. For uplink low-latency service flows, the Non-APMLD determines the low-latency service support link set and negotiates with the AP MLD to determine the mapping of low-latency services and related links, or the AP MLD determines the low-latency service support link set and negotiates with the Non-AP MLD to determine the mapping of low-latency services and related links, wherein the Non-AP MLD needs to report the communication environment and related parameters in the uplink direction; and during the service flow access process, the Non-AP MLD selects one or more mapped low-latency service support links for transmission. Figure 7 As shown, LINK2, LINK3, and LINK4 are low-latency service support links. Low-latency service flow 1 is transmitted on LINK3 and LINK4, while low-latency service flow 2 is transmitted on LINK2.

[0081] In this embodiment, the mapping and communication method of low-latency services and related links may specifically include mapping and communication of low-latency services and working links and mapping and communication of low-latency services and low-latency support links.

[0082] 1. Mapping and communication between low-latency services and working links.

[0083] Figure 8 Schematic diagram of the mapping and communication mode of low-latency services and working links according to an optional embodiment of the present invention, such as Figure 8 As shown, first, a mapping is performed between the low-latency service flow and all working links. During the communication process, only one or more links are selected from the low-latency service support link set for communication, and the selected communication link can be updated accordingly with the change of the low-latency service support link.

[0084] like Figure 8 As shown, in this embodiment, the low-latency service flow is first mapped to all working links, namely LINK1, LINK2, LINK3, and LINK4. In time period 1, only LINK3 and LINK4 are low-latency service support links, then only LINK3 and / or LINK4 are selected for transmission during the actual transmission of the low-latency service; in time period 2, only LINK2 and LINK3 are low-latency service support links, then only LINK2 and / or LINK3 are selected for transmission during the actual transmission of the low-latency service.

[0085] 2. Mapping and communication between low-latency services and low-latency support links.

[0086] Figure 9 Schematic diagram of the mapping and communication method between low-latency services and low-latency support links according to an embodiment of the present invention, such as Figure 9 As shown, first, mapping between low-latency service flows and specific low-latency service support links is performed, and one or more links in the low-latency service support link set in the MLD are selected for low-latency service access. Assuming that the traffic identifier of the low-latency service is TID, mapping (TID-LINK-MAPPING) between the TID and the selected low-latency service support link (LINK) is implemented; during the low-latency service access and communication process, if the low-latency service support link set is updated, mapping (TID-LINK-MAPPING) between the TID and the selected low-latency service support link (LINK) is performed again, and dynamic adjustment is made through the link mapping negotiation mechanism.

[0087] like Figure 9 As shown, in this embodiment, low-latency service flows are first mapped to specific low-latency links. For example, in time period 1, low-latency service flow 1 is mapped to LINK4, and low-latency service flow 2 is mapped to LINK3. However, when the low-latency service support link changes, the mapping is re-performed. For example, in time period 2, LINK2 and LINK3 are low-latency support links, then MLD1 and MLD2 determine through negotiation that low-latency service flow 1 is mapped to LINK2. After the negotiation is successful, low-latency service flow 2 is transmitted through LINK2.

[0088] In the above-mentioned embodiment of the present invention, a low-latency service transmission mechanism based on multiple links is provided. For multiple links, the links are distinguished according to the communication environment, access method and strategy, and the low-latency service support link set is evaluated and determined in real time. Through the mapping between the low-latency service flow and the related links, the low-latency service is transmitted on one or more links in the low-latency service support link set.

[0089] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.

[0090] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0091] An embodiment of the present invention further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0092] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0093] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0094] Obviously, those skilled in the art will appreciate that the various modules or steps of the present invention described above can be implemented using a general-purpose computing device, can be centralized on a single computing device, or can be distributed across a network of multiple computing devices. They can be implemented using program code executable by the computing device, and thus, can be stored in a storage device and executed by the computing device. In some cases, the steps shown or described herein can be performed in a different order than that shown, or can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0095] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A multi-link low-latency communication method, characterized in that: include: Determine a low-latency service support link set between an access point multi-link device and a non-access point multi-link device; Establishing a mapping between a low-latency service flow and one or more low-latency service support links in the low-latency service support link set; Transmitting the low-latency service flow on the one or more low-latency service support links; The step of determining the low-latency service support link set between the access point multi-link device and the non-access point multi-link device includes: Determining the low-latency service support link between the access point multi-link device and the non-access point multi-link device according to at least one of the following: channel access mode, channel environment, link load or performance statistics, admission control, low-latency service priority, and specific quality of service QoS type service access; wherein the channel access mode includes: a channel access mode using different access time periods for the low-latency service and other services; The determined low-latency service support links are formed into the low-latency service support link set.

2. The method according to claim 1, characterized in that: in, The determining of the low-latency service support link between the access point multi-link device and the non-access point multi-link device includes: According to the QoS requirements and / or configuration parameters of the low-latency service, the low-latency service support link is determined from multiple links between the access point multi-link device and the non-access point multi-link device according to at least one of the following selection rules: Whether the priority, priority queue or channel access parameters corresponding to the low-latency service are supported; Whether to adopt an entry strategy; Whether to adopt the channel access method that optimizes the low-latency service access; Whether the BSS load meets the access requirements of the low-latency service; Whether the throughput meets the requirements of the low-latency service; Whether the number of packet losses and / or retransmissions exceeds a preset threshold; Whether to restrict access to services of the specific QoS type; Whether the latency in the uplink or downlink direction meets the access requirements of low-latency services.

3. The method according to claim 2, characterized in that in, The type of delay parameter includes at least one of the following: access delay of all ACs, access delay of specific ACs, transmission delay, BSS internal delay, BSS external delay, and achievable optimal delay; the value of the delay parameter is one of the following: average delay, maximum delay, and delay of a specific percentile.

4. The method according to claim 2, characterized in that: in, The channel access method of optimizing the low-latency service access includes: Different access channels are used for the low-latency service and other services.

5. The method according to claim 2, characterized in that: After determining the low-latency service support link between the access point multi-link device and the non-access point multi-link device, the method further includes: The communication environment and related parameters involved in the selection rules are monitored in real time according to the current network conditions. If the communication environment and related parameters involved in the selection rules are updated, the current low-latency service support link is re-determined. If the communication environment and related parameters involved in the selected rules are not updated, the original low-latency service support link is retained.

6. The method according to claim 1, characterized in that Establishing a mapping between a low-latency service flow and one or more low-latency service support links in the low-latency service support link set includes: Through negotiation between the access point multi-link device and the non-access point multi-link device, a mapping is established between the low-latency service flow and one or more low-latency service support links in the low-latency service support link set.

7. The method according to claim 6, characterized in that Establishing a mapping between the low-latency service flow and one or more low-latency service support links in the low-latency service support link set includes at least one of the following: Establishing a mapping between the low-latency service flow and a plurality of working links, wherein each of the working links is a low-latency service support link in its corresponding time period; A mapping is established between the low-latency service flow and one or more specific low-latency service support links.

8. The method according to claim 7, characterized in that Establishing a mapping between the low-latency service flow and a plurality of working links, including: The low-latency service flow is mapped to all working links, and one or more working links belonging to the low-latency service support link are selected as the transmission link of the low-latency service flow according to different time periods.

9. The method according to claim 7, characterized in that: Establishing a mapping between the low-latency service flow and a specific low-latency service support link includes: The traffic identifier of the low-latency service is mapped with the selected one or more specific low-latency service supporting links.

10. The method according to claim 6, characterized in that After establishing a mapping between the low-latency service flow and one or more low-latency service support links in the low-latency service support link set, the method further includes: When the low-latency service support link set is updated, the mapping between the low-latency service flow and one or more low-latency service support links is re-established through negotiation between the access point multi-link device and the non-access point multi-link device.

11. The method according to claim 6, characterized in that Establishing a mapping between the low-latency service flow and the low-latency service support link through negotiation between the access point multi-link device and the non-access point multi-link device includes at least one of the following: For a downlink low-latency service flow, the access point multi-link device determines the low-latency service support link set, and negotiates with the non-access point multi-link device to determine a mapping between the low-latency service flow and the low-latency service support link; For the uplink low-latency service flow, the non-access point multi-link device determines the low-latency service support link set, and negotiates with the access point multi-link device to determine the mapping between the low-latency service and the low-latency service support link; or, the access point multi-link device determines the low-latency service support link set, and negotiates with the non-access point multi-link device to determine the mapping between the low-latency service and the low-latency service support link.

12. A multi-link low-latency communication device, characterized in that: include: A determination module, used to determine a low-latency service support link set between an access point multi-link device and a non-access point multi-link device; A mapping module, used to establish a mapping between a low-latency service flow and one or more low-latency service support links in the low-latency service support link set; A transmission module, configured to transmit the low-latency service flow on the one or more low-latency service support links; The determination module is further used to determine the low-latency service support link between the access point multi-link device and the non-access point multi-link device according to at least one of the following: channel access mode, channel environment, link load or performance statistics, admission control, low-latency service priority, and specific service quality QoS type service access; the determined low-latency service support link is formed into the low-latency service support link set; The channel access method includes: a channel access method using different access time periods for the low-latency service and other services.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 11 when executed by a processor.

14. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method described in any one of claims 1 to 11 are implemented.

Images