WO2022134667A1 - 参数反馈、更新、关联方法、通信节点、通信系统及介质 - Google Patents

参数反馈、更新、关联方法、通信节点、通信系统及介质 Download PDF

Info

Publication number
WO2022134667A1
WO2022134667A1 PCT/CN2021/118277 CN2021118277W WO2022134667A1 WO 2022134667 A1 WO2022134667 A1 WO 2022134667A1 CN 2021118277 W CN2021118277 W CN 2021118277W WO 2022134667 A1 WO2022134667 A1 WO 2022134667A1
Authority
WO
WIPO (PCT)
Prior art keywords
nav
link
parameter
access point
mld
Prior art date
Application number
PCT/CN2021/118277
Other languages
English (en)
French (fr)
Inventor
卢刘明
袁立权
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to KR1020237011711A priority Critical patent/KR20230065301A/ko
Priority to US18/246,591 priority patent/US20230371076A1/en
Priority to JP2023522471A priority patent/JP2023546847A/ja
Priority to EP21908669.1A priority patent/EP4207937A1/en
Publication of WO2022134667A1 publication Critical patent/WO2022134667A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H04L5/0035—Resource allocation in a cooperative multipoint environment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0073—Allocation arrangements that take into account other cell interferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/14—Multichannel or multilink protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • the present application relates to wireless communication networks, for example, to a parameter feedback, update, association method, communication node, communication system and medium.
  • a multi-link device For a multi-link device (MLD), if the attached sites are all access points (Access Point, AP), it is an access point multi-link device (AP MLD).
  • a station (Station, STA) of an access point (Non-AP) is a non-access point multi-link device (Non-AP MLD).
  • the STA in the non-access point multi-link device and the AP in the AP multi-link device can communicate through different links.
  • there are multi-link devices that do not support simultaneous transmission and reception of data Non-Simultaneous Transmit and Receive, NSTR).
  • NAV Network Allocation Vector
  • the present application provides a parameter feedback, update, and association method, a communication node, a communication system and a medium, so as to realize the feedback of NAV to a non-access point multi-link device and improve the reliability of multi-link communication.
  • the embodiment of the present application provides a parameter feedback method, which is applied to AP MLD, including:
  • a physical layer (Physical Layer, PHY) protocol data unit (Protocol Data Unit, PPDU) sent by the first station in the non-access point multi-link device through the first link record the location where the second link is located.
  • BSS Basic Service Set
  • the road device is connected to the second link through the first link, and the first link and the second link of the non-access point multi-link device do not support simultaneous transmission and reception;
  • the NAV update parameter is fed back to the non-access point multi-link device through the first link.
  • the embodiment of the present application also provides a parameter update method, which is applied to a non-access point multi-link device, including:
  • the first station After the first station sends the AP MLD through the first link to the AP MLD at the end of the specific frame interval, acquiring the NAV update on the second station in the non-access point multi-link device through the first link parameters, wherein the NAV update parameter is determined according to the network transmission and state update information about the NAV of the second site in the BSS where the second link is located;
  • the local NAV parameter is updated according to the NAV update parameter.
  • the embodiment of the present application also provides an association method, including:
  • Broadcast multi-link capability information where the broadcast multi-link capability information includes the AP MLD's support capability for feeding back NAV update parameters;
  • association request from a non-access point multi-link device, where the association request is used to determine the link connection relationship between the AP MLD and the non-access point multi-link device, the link's ability to support simultaneous transmission and reception, and the support capability of the station in the non-access point multi-link device for receiving NAV update parameters;
  • the embodiment of the present application also provides an association method, including:
  • the broadcast multi-link capability information includes the support capability of the AP MLD for feeding back NAV update parameters
  • An embodiment of the present application further provides a communication node, including: a memory, a processor, and a computer program stored in the memory and running on the processor, the processor implementing the above-mentioned parameter feedback method, Parameter update method or association method.
  • the embodiment of the present application also provides a communication system, including an access point multi-link device and a non-access point multi-link device;
  • the access point multi-link device is used to perform the above-mentioned parameter feedback method or the association method applied to the AP MLD;
  • the non-access point multi-link device is used to execute the above-mentioned parameter updating method or the association method applied to the non-access point multi-link device.
  • Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the program is executed by a processor, the above-mentioned parameter feedback method, parameter update method or association method is implemented.
  • FIG. 1 is a schematic diagram of a data transmission conflict between multi-link devices according to an embodiment
  • FIG. 3 is a schematic diagram of an AP MLD feeding back NAV update parameters to a non-access point multi-link device according to an embodiment
  • FIG. 5 is a schematic diagram of a MAC frame including NAV policy information provided by an embodiment
  • FIG. 6 is a schematic diagram of a NAV control frame including NAV policy information provided by an embodiment
  • FIG. 7 is a schematic diagram of an ACK frame including NAV policy information provided by an embodiment
  • FIG. 10 is a schematic diagram of an association process between an AP MLD and a non-access point multi-link device provided by an embodiment
  • FIG. 12 is a schematic diagram of a hardware structure of a communication node provided by an embodiment
  • FIG. 13 is a schematic structural diagram of a communication system according to an embodiment.
  • simultaneous transmission and reception refers to the simultaneous transmission and reception of data on the two links of the same MLD. If the isolation between the channels of different links in the MLD is low, it is easy to cause in-device coexistence interference. Therefore, many applications In the scenario, simultaneous sending and receiving of MLD devices on different links is not supported.
  • MLD devices There are two types of MLD devices: AP MLD and Non-AP MLD.
  • NAV is equivalent to a counter, which can be used to reflect the busyness and idleness of the channel.
  • Non-AP MLD devices can determine when data transmission can be performed according to NAV, thereby effectively avoiding conflicts with data being transmitted on the same link.
  • the second link cannot receive data during the process of sending data through the first link, that is, the second link cannot receive the NAV from the AP MLD and other networks. transmission control parameters, so the second link cannot determine an appropriate time for data transmission, resulting in data transmission conflicts with other stations in the BSS using the second link.
  • FIG. 1 is a schematic diagram of a data transmission conflict between multi-link devices according to an embodiment.
  • the AP MLD and the Non-AP MLD are connected through a first link and a second link, and the first link and the second link are NSTR links.
  • STA1 sending data to the AP MLD through the first link
  • STA2 cannot receive the data of the AP MLD, resulting in the loss of the NAV information of STA2 on the second link.
  • the NAV determines the transmission opportunity and transmits data immediately after obtaining the transmission opportunity, thereby colliding with the ongoing data transmission on the second link (ie, the data transmission between STA3 and AP2) at the AP2 side.
  • TA represents the sender
  • RA represents the receiver
  • RTS represents the Request To Send (RTS) frame
  • CTS represents the Clear To Send (CTS) frame
  • the dotted area represents that STA2 cannot be sent on the second chain
  • the blind area for receiving NAV on the road indicates that the data transmission on the first link has been completed, and STA2 can perform data transmission in this area; STA3 and STA2 belong to one BSS.
  • a parameter feedback method is provided, during the period when the Non-AP MLD device of the NSTR sends data to the AP MLD through the first link (that is, the period when the Non-AP MLD device is in the blind area of the second link) , record the network transmission and state update information about the NAV of the second site and feed back the NAV update parameters of the second site through the first link, so as to solve the problem of NAV loss and data transmission conflict caused by blind spots during multi-link communication.
  • FIG. 2 is a flowchart of a parameter feedback method provided by an embodiment.
  • the method provided in this embodiment can be applied to an AP MLD, and specifically can be applied to an access point, such as AP2 in FIG. 1 .
  • the method provided by this embodiment includes steps 110 , 120 and 130 .
  • step 110 during the period of receiving the physical layer protocol data unit PPDU sent by the first station in the non-access point multi-link device through the first link, record the information about all the information in the basic service set BSS where the second link is located.
  • the AP MLD may include multiple access points, and the Non-AP MLD may include multiple sites.
  • any link can send PPDU to AP MLD after obtaining a transmission opportunity, and this link is recorded as the first link, and the site corresponding to the first link is the first link.
  • a site other links in the link set (ie, the second link) do not support receiving data during the transmission of PPDUs by the first link.
  • the links in the link set are in the enabled state (that is, in the state of sending and receiving data).
  • the Non-AP MLD sends a PPDU to the AP MLD through the first link, which will trigger the AP MLD to record the network transmission and status update information of the second site of the second link.
  • the busy and idle status of the channel, the estimated transmission time, the length of the transmitted data, etc., the AP MLD can determine the NAV value of the data transmitted by the second station on the second link according to these information, and feed it back to the Non-AP MLD, thereby indicating the second station.
  • the station waits for a corresponding period of time before performing data transmission to avoid conflicts on the second link.
  • the access point that records the network transmission and status update information of the second link may be different from the access point that receives the PPDU of the first station. For example, in FIG. 1 , when STA1 sends a PPDU to AP1 through the first link, AP2 is triggered to record the network transmission and status update information of the second link.
  • a feedback status of the NAV update parameter of the second station is determined according to the network transmission and status update information, where the feedback status includes feedback or no feedback.
  • the AP MLD determines whether to feed back the NAV update parameter to the Non-AP MLD according to the recorded network transmission and status update information, and the NAV update parameter is used to instruct the Non-AP MLD to update the locally stored NAV. For example, AP MLD calculates the NAV update parameters of the second site according to the recorded network transmission and status update information. After the PPDU in the first link is sent, no matter whether the NAV of the second site is 0, AP MLD always updates the NAV to the second site. The update parameter is fed back to the Non-AP MLD; or, the AP MLD only feeds back the NAV update parameter to the Non-AP MLD when the NAV of the second site is greater than 0.
  • the access point that records the network transmission and status update information of the second link is different from the access point that receives the PPDU of the first station. In this case, the network transmission and status of the second link are recorded.
  • the access point updating the information may forward the NAV update parameters that need to be fed back to the Non-AP MLD through the first link.
  • step 130 when the feedback state is feedback, after a specific frame interval when the PPDU is received, the NAV update parameter is fed back to the Non-AP MLD through the first link.
  • the AP MLD when it is determined to feed back the NAV update parameters to the Non-AP MLD, after a specific frame interval after the PPDU transmission in the first link ends, the AP MLD feeds back the NAV update parameters through the first link to Non-AP MLD, so that when the second link cannot receive data, the feedback of NAV update parameters is realized by the first link, so that Non-AP MLD can be obtained in time during the enabling period of the NSTR link set
  • the NAV updates parameters reasonably determines the transmission timing of the second station on the second link, and effectively avoids conflicts with data transmissions being performed by other stations on the second link.
  • FIG. 3 is a schematic diagram of an AP MLD feeding back NAV update parameters to a non-access point multi-link device according to an embodiment.
  • STA1 sends a PPDU to AP1;
  • AP2 records the network transmission and status update information about STA2;
  • AP2 determines the NAV update parameters according to the recorded network transmission and status update information, and sets the The NAV update parameters are sent to AP1;
  • AP1 sends the NAV update parameters to STA1 through the first link;
  • STA1 sends the NAV update parameters to STA2; (6) STA2 updates the local NAV parameters according to the NAV update parameters.
  • STA2 can reasonably determine the time to send the RTS frame to AP2 through the second link, and avoid the time when STA3 in the same BSS sends data to AP2 through the second link, thereby avoiding data transmission on the second link. conflict.
  • step 112 is further included: generating NAV update parameters according to network transmission and state update information.
  • the network transmission and status update information includes the busy and idle status of the channel of the second link, the expected transmission time of data of other sites in the same BSS on the second link, the length of the transmitted data, etc.
  • the AP MLD records these information by recording
  • the NAV value of the data transmitted by the second station on the second link can be determined to instruct the second station to wait for a corresponding period of time before obtaining a transmission opportunity, thereby avoiding data transmission between different stations of the same BSS on the second link. conflict.
  • step 112 includes: setting the NAV update parameter to an initial value, and updating the NAV update parameter according to at least one of the following: in the case of sending a CTS frame to the third site through the BSS where the second link is located, according to The duration information indicated by the CTS frame updates the NAV update parameter; when the PPDU of the third site is received through the BSS where the second link is located, the NAV update parameter is updated according to the duration information indicated by the PPDU of the third site; after obtaining the second link When the transmission opportunity of the BSS where the path is located and the PPDU is sent to the third station through the BSS where the second link is located, the NAV update parameter is updated according to the duration information of the transmission opportunity or the duration information indicated by the PPDU sent to the third station.
  • the AP MLD generates NAV update parameters related to the second site in the process of being triggered to record network transmission and status update information, the initial value of the NAV update parameters is set to zero, and the PPDU on the first link sends the During this period, the NAV update parameter is assigned according to the data transmission situation of the second link and the BSS where it is located.
  • the NAV update parameters are also reduced in real time as time changes.
  • the assignment process includes at least one of the following:
  • AP MLD sends the CTS frame through the BSS where the second link is located to instruct the third site to send data, then assigns the duration information indicated by the CTS frame to the NAV update parameter;
  • the AP MLD receives the PPDU sent by the third site through the BSS where the second link is located, then assigns the duration information indicated on the PPDU to the NAV update parameter;
  • the AP MLD obtains the transmission opportunity on the second link, and sends the PPDU to the third site through the BSS where the second link is located or triggers the third site to send uplink data, then the duration information indicated by the PPDU or the duration of the transmission opportunity The information is assigned to the NAV update parameter.
  • step 130 includes:
  • the NAV update parameter is fed back to the Non-AP MLD through the first link; or, when the NAV update parameter is greater than 0, the NAV update parameter is fed back to the Non-AP MLD through the first link Feedback NAV update parameters.
  • the AP MLD calculates the NAV update parameter of the second site according to the recorded network transmission and status update information. After the PPDU in the first link is sent, in one case, no matter whether the NAV of the second site is 0, the AP MLD always feeds back the NAV update parameters to the Non-AP MLD; in another case, the AP MLD only feeds back the NAV update parameters to the Non-AP MLD when the NAV of the second site is greater than 0, and the second site The NAV is greater than 0, indicating that the second station needs to wait for a certain period of time before data transmission. If the NAV is equal to 0, the second station does not need to wait and can transmit data at any time after the PPDU is sent. In this case, no feedback is required. NAV, the second site also does not need to update the local NAV parameters.
  • step 130 includes: sequentially sending the NAV update parameter to the second site through the access point associated with the first link in the AP MLD and the first site.
  • the access point in the AP MLD used to record the network transmission and status update information of the second link is different from the access point that receives the PPDU of the first site.
  • the network of the second site is recorded.
  • the access point that transmits and status update information may forward the NAV update parameters that need to be fed back to the second site through the first link (the link from the access point receiving the PPDU of the first site to the first site).
  • the NAV update parameter is fed back through an acknowledgment reply frame, and the acknowledgment reply frame includes an Acknowledge (ACK) frame or a Block Acknowledge (BA) frame; or, the NAV update parameter is fed back through a NAV control frame, and the NAV control The frame is fed back after the first frame interval after the transmission of the PPDU of the first station is completed, or after the second frame interval after the completion of the transmission of the acknowledgement reply frame.
  • ACK Acknowledge
  • BA Block Acknowledge
  • FIG. 4 is a schematic diagram of feedback of NAV update parameters provided by an embodiment.
  • the AP MLD and the Non-AP MLD first negotiate the transmission capability of the NAV update parameters, for example, whether the AP MLD supports recording the network transmission and status update information of the second site, and whether it supports feeding back the NAV update to the Non-AP MLD. parameters, whether the Non-AP MLD supports receiving NAV update parameters through the first link, the connection relationship between the AP MLD and the Non-AP MLD, etc.
  • the Non-AP MLD sends the MAC layer protocol data unit (MAC Protocol Data Unit, MPDU) to the AP-MLD through the first link in the NSTR link set, that is, in the process of sending the MAC frame, the NAV policy ( NAV Policy) information to request the AP MLD to feed back the NAV update parameters corresponding to other links in the NSTR link set except the first link.
  • MAC Protocol Data Unit MPDU
  • NAV Policy NAV Policy
  • AP1 receives the preamble or MPDU frame header information of the PPDU where the MPDU is located, it immediately triggers AP2 to record the network transmission and status update information of the second link; after receiving the MPDU, AP2 feeds back the NAV update parameters to AP1, AP1 Then send an ACK frame or BLOCK ACK frame or NAV control frame containing the NAV update parameters to STA1 of the Non-AP MLD; STA1 immediately feeds back the NAV update parameters to STA2 after receiving the NAV update parameters, and STA2 updates the local NAV parameters according to the NAV update parameters.
  • FIG. 5 is a schematic diagram of a MAC frame including NAV policy information according to an embodiment.
  • the MAC frame header includes a frame control field (used to indicate which frame type), duration/ID field (used to indicate the expected transmission duration of the frame or the number of the frame), address field ( It is used to indicate the receiver or sender of the frame) and the NAV policy field; the frame body contains the transmitted valid data; the frame body can also include a frame check sequence (Frame Check Sequence, FCK).
  • the NAV policy field is used to indicate whether the Non-AP MLD requests the AP MLD to feed back NAV update parameters. For example, the NAV policy field has three values.
  • the first value indicates that the NAV update parameter is not fed back; the second value indicates that the NAV update parameter is fed back regardless of whether the NAV update parameter is 0; the third value indicates that the NAV update parameter is fed back when the NAV update parameter is 0.
  • the NAV policy field may have two values, the first value indicates that the NAV update parameter is not fed back, and the second value indicates that the NAV update parameter is fed back.
  • FIG. 6 is a schematic diagram of a NAV control frame including NAV policy information according to an embodiment.
  • the MAC header of the NAV control frame contains the frame control field, the duration/ID field and the address field; the frame body contains the NAV information field, which is updated by NAV_INFO (used to indicate the carried NAV update).
  • NAV_INFO used to indicate the carried NAV update.
  • the frame body also includes a frame check sequence.
  • FIG. 7 is a schematic diagram of an ACK frame including NAV policy information provided by an embodiment; as shown in FIG. 7 , the frame header of the ACK frame includes a frame control field, a duration/ID field, and an address field; the frame body includes Block acknowledgment BA information field (used to indicate whether the transmission of the data block is successful) and NAV information field.
  • the NAV information field is composed of NAV_INFO, at least one Per_NAV_INFO and at least one instance of STA_INFO; the frame body also includes a frame check sequence . In FIG. 6 and FIG. 7, the content of the NAV information field may be the same.
  • step 100 is further included: broadcasting multi-link capability information, wherein the multi-link capability information includes at least one of the following: at least one access point in the AP MLD supports or does not support carrying a NAV update parameters of other links; at least one access point in the AP MLD supports or does not support the operation parameters that carry the feedback NAV of other links other than the link where it is located.
  • the negotiation of the transmission capability of the NAV update parameter may be performed at the stage of establishing the MLD association, or may be performed during the process of initiating the multi-link operation at the first site after the MLD establishes the association.
  • the AP MLD broadcasts the multi-link capability through a beacon, for example, whether the access point in the Non-AP MLD supports carrying the NAV update parameters of the second site, and whether it supports carrying the operation parameters of the NAV feedback through the first link,
  • the operation parameter for feeding back the NAV is, for example, which of the following feedback modes is supported: 1) feedback through an acknowledgment reply frame, wherein the acknowledgment reply frame includes an ACK frame or a BA frame; 2) feedback through a NAV control frame.
  • the method further includes: Step 102: Receive an association request and determine at least one of the following information according to the association request: a site associated with each access point in the AP MLD in the Non-AP MLD; Link connection relationship between AP MLDs; links that do not support simultaneous transmission and reception; AP MLD’s ability to support feedback of NAV update parameters; non-AP MLD’s support ability for stations to receive NAV update parameters; feedback NAV operation parameters .
  • the Non-AP MLD selects a site as the STA (that is, the first site) that initiates the multi-link operation, and sends an association request to the AP MLD, where the association request specifies the associated sites in the Non-AP MLD (including The first site and the second site), may also indicate that the first link and the second link are NSTR links, and whether the associated site in the Non-AP MLD supports receiving NAV update parameters through the associated link; also It can be used to request to determine whether the access point in the AP MLD supports feedback of NAV update parameters of the stations in the Non-AP MLD; it can also be used to request to determine the related operation parameters, such as the operation parameters of feedback NAV.
  • the PPDU includes preamble or MPDUMPDU frame header information, and the preamble or MPDUMPDU frame header information is used to trigger recording of network transmission and status update information.
  • the AP MLD once the AP MLD receives the preamble or MPDU frame header information of the PPDU where the MPDU is located, it immediately triggers and records the network transmission and status update information of the second link.
  • the MPDU MPDU corresponding to the PPDU includes NAV policy indication information, and the NAV policy indication information is used to indicate at least one of the following: do not feed back the NAV update parameter; feed back the NAV update when the NAV update parameter is 0 or non-zero parameter; feedback the NAV update parameter when the NAV update parameter is greater than 0.
  • the NAV policy field has three values.
  • the first value indicates that the NAV update parameter is not fed back; the second value indicates that the NAV update parameter is fed back regardless of whether the NAV update parameter is 0 or not; the third value indicates that the NAV update parameter is fed back.
  • the NAV policy field may have two values, the first value indicates that the NAV update parameter is not fed back, and the second value indicates that the NAV update parameter is fed back.
  • the NAV control frame is used to indicate: the number of network transmissions and status update information carried; NAV value; and the target station corresponding to the network transmission and status update information.
  • the NAV control frame indicates the number of network transmission and status update information carried by NAV_INFO; the NAV value; at least one Per_NAV_INFO indicates the value of the NAV update parameter, and at least one STA_INFO indicates the target station corresponding to the NAV update parameter.
  • a parameter updating method is also provided, during the period when the Non-AP MLD device of the NSTR sends data to the AP MLD through the first link (that is, the period when the Non-AP MLD device is in the blind area of the second link) ), the NAV update parameter is received through the first link, and the local NAV parameter is updated accordingly as the basis for determining the timing of data transmission, so as to solve the problem of data transmission conflict in the multi-link communication process.
  • FIG. 8 is a flowchart of a parameter updating method provided by an embodiment.
  • the method provided in this embodiment can be applied to the Non-AP MLD, and specifically can be applied to the second site. As shown in FIG. 8 , the method provided by this embodiment includes steps 210 and 220 . For technical details not described in detail in this embodiment, reference may be made to any of the above-mentioned embodiments.
  • step 210 after the first station sends the AP MLD through the first link to the AP MLD at the end of the specific frame interval of the physical layer PPDU, obtain information about the first link in the non-access point multi-link device through the first link
  • the NAV update parameter of the second site wherein the NAV update parameter is determined according to the network transmission and state update information about the NAV of the second site in the BSS where the second link is located;
  • step 220 when the NAV update parameter is acquired, the local NAV parameter is updated according to the NAV update parameter.
  • the Non-AP MLD compares the NAV update parameter received through the first link with the local NAV parameter, and if the NAV update parameter is zero, the local NAV parameter can continue to be used; if the NAV update parameter is greater than the local NAV parameter, Then perform the corresponding update operation, for example, the NAV update parameter minus the transmission time of the NAV update parameter is converted to the value of the NAV unit, as the NAV parameter after the second site update; if the NAV update parameter is smaller than the local NAV parameter, you can Continue to use local NAV parameters.
  • step 220 includes: when the NAV update parameter is 0, using the local NAV parameter as the updated local NAV parameter; when the NAV update parameter is greater than the local NAV parameter, comparing the NAV update parameter with the local NAV parameter The difference between the NAV values corresponding to the transmission time of the NAV update parameter is used as the updated local NAV parameter; when the NAV update parameter is smaller than the local NAV parameter, the local NAV parameter is used as the updated local NAV parameter.
  • the NAV update parameters are sequentially sent to the second site through the access point associated with the first link in the AP MLD and the first site.
  • the NAV update parameters are obtained through an acknowledgment reply frame, and the acknowledgment reply frame includes an ACK frame or a BA frame; or, the NAV update parameter is obtained through a NAV control frame, and the NAV control frame is obtained at the No. 1 site after the PPDU transmission of the first site is completed. Acquired after one frame interval, or after the second frame interval after confirming the completion of the reply frame transmission.
  • it also includes:
  • Step 200 Receive multi-link capability information, where the multi-link capability information includes at least one of the following:
  • At least one access point in the AP MLD supports or does not support carrying NAV update parameters of links other than the link where it is located;
  • At least one access point in the AP MLD supports or does not support operating parameters that carry feedback NAVs for links other than the link where it is located.
  • it also includes:
  • Step 202 Send an association request, where the association request is used to request at least one of the following information: the site associated with each access point in the AP MLD in the Non-AP MLD; the link connection between the AP MLD and the Non-AP MLD Links that do not support simultaneous transmission and reception; AP MLD's ability to support feedback of NAV update parameters; Non-AP MLD's support ability of stations to receive NAV update parameters; Feedback of NAV operation parameters.
  • the PPDU includes preamble or MPDUMPDU frame header information, and the preamble or MPDUMPDU frame header information is used to trigger recording of network transmission and status update information.
  • the MPDU corresponding to the PPDU includes NAV policy indication information, and the NAV policy indication information is used to indicate at least one of the following: do not feed back the NAV update parameter; feed back the NAV update when the NAV update parameter is 0 or non-zero parameter; feedback the NAV update parameter when the NAV update parameter is greater than 0.
  • the NAV control frame is used to indicate: the number of network transmission and status update information carried; NAV value; and the target site corresponding to the network transmission and status update information.
  • an association method is also provided, which is applied to the AP MLD.
  • the AP MLD establishes the multi-link connection of the NSTR by broadcasting the multi-link capability information and responding to the association request of the Non-AP MLD.
  • the first link may be provided for feedback of NAV update parameters during the period when the link is in the dead zone.
  • FIG. 9 is a flowchart of an association method provided by an embodiment. As shown in FIG. 9 , the method provided by this embodiment includes steps 310 , 320 and 330 .
  • broadcast multi-link capability information includes the AP MLD's support capability for feeding back NAV update parameters
  • the multi-link capability information includes whether the AP MLD supports the NAV update parameter of the second station carrying the Non-AP MLD in the first link and/or the operation parameter of feeding back NAV, and the like. After receiving the broadcast, the Non-AP MLD can send an association request to the AP MLD.
  • step 320 an association request of the Non-AP MLD is received, where the association request is used to determine the link connection relationship between the AP MLD and the Non-AP MLD, the link's ability to support simultaneous transmission and reception, and the Non-AP MLD - Support capability of sites in AP MLD to receive NAV update parameters.
  • the Non-AP MLD selects a site as the STA (that is, the first site) that initiates the multi-link operation, and the first site can send an association request to the AP MLD, wherein the association request indicates that the Non-AP MLD Associated stations (including the first station and the second station), may also indicate that the first link and the second link are NSTR links, and whether the associated station in the Non-AP MLD supports receiving NAV through the associated link Update parameters; can also be used to request to determine whether the access point in the AP MLD supports feedback of the NAV update parameters of the stations in the Non-AP MLD; can also be used to request to determine related operation parameters, such as the operation parameters of feedback NAV.
  • step 330 send association response information to the non-access point multi-link device according to the association request.
  • the AP MLD sends association response information to the Non-AP MLD, and the association response information is used to confirm whether the related sites (the first site and the second site) in the MLD have been associated, and to confirm the function of the access point in the AP MLD Information (Capabilities Information), indicating whether the access point supports the feedback of NAV update parameters of stations in the Non-AP MLD; it can also be used to request the determination of related operation parameters, such as feedback of NAV operation parameters.
  • Capabilities Information Capabilities Information
  • FIG. 10 is a schematic diagram of an association process between an AP MLD and a non-access point multi-link device according to an embodiment.
  • STA1 is selected as the first site to initiate the multi-link operation;
  • AP1 broadcasts the multi-link capability information;
  • STA1 sends an association request to AP1;
  • AP1 sends an association response message to STA1, thereby completing AP MLD and Non-AP Association of MLD.
  • the feedback of the NAV update parameters can be implemented through the first link, thereby implementing the update of the local NAV parameters of the second site.
  • the method further includes: Step 340: Execute the above-mentioned parameter feedback method according to the association response information.
  • an association method is also provided, which is applied to Non-AP MLD.
  • the feedback NAV update parameter can be received through the first link, and the local NAV parameter can be updated accordingly.
  • FIG. 11 is a flowchart of an association method provided by another embodiment. As shown in FIG. 11 , the method provided by this embodiment includes steps 410 , 420 and 430 .
  • step 410 the multi-link capability information broadcast by the AP MLD is received, and the broadcast multi-link capability information includes the support capability of the AP MLD for feeding back NAV update parameters;
  • step 420 send an association request to the AP MLD according to the multi-link capability information, where the association request is used to determine the link connection relationship between the AP MLD and the non-access point multi-link device, The support capability of the link for simultaneous transmission and reception and the support capability of the station in the non-access point multi-link device to receive the NAV update parameter;
  • step 430 the association response information of the AP MLD is received.
  • it also includes:
  • Step 440 Execute the above-mentioned parameter updating method according to the association response information
  • the embodiment of the present application also provides a parameter feedback device.
  • the parameter feedback device includes:
  • the recording module is configured to, during the period of receiving the PPDU sent by the first site in the non-access point multi-link device Non-AP MLD through the first link, record the information about the non-AP MLD in the BSS where the second link is located.
  • a feedback state determination module configured to determine a feedback state about the NAV update parameter of the second site according to network transmission and state update information, and the feedback state includes feedback or no feedback;
  • the feedback module is configured to feed back the NAV update parameter to the Non-AP MLD through the first link after a specific frame interval after the PPDU reception ends when the feedback state is feedback.
  • the first link to feedback NAV to solve the problem of data transmission conflict in the process of multi-link communication.
  • it also includes:
  • the generating module is configured to generate NAV update parameters according to network transmission and state update information.
  • the generation module is set to:
  • the NAV update parameter is updated according to the duration information indicated by the CTS frame
  • the feedback module is set to:
  • the NAV update parameter is fed back to the Non-AP MLD through the first link; or,
  • the NAV update parameter is fed back to the Non-AP MLD through the first link.
  • the feedback module is set to:
  • the NAV update parameters are sequentially sent to the second site through the access point associated with the first link in the AP MLD and the first site.
  • the NAV update parameter is fed back through an acknowledgment reply frame, and the acknowledgment reply frame includes an ACK frame or a BA frame; or,
  • the NAV update parameter is fed back through the NAV control frame, and the NAV control frame is fed back after the first frame interval after the transmission of the PPDU of the first station is completed, or after the second frame interval after the completion of the transmission of the confirmation reply frame.
  • it also includes:
  • the broadcasting module is configured to broadcast multi-link capability information, wherein the multi-link capability information includes at least one of the following:
  • At least one access point in the AP MLD supports or does not support carrying NAV update parameters of links other than the link where it is located;
  • At least one access point in the AP MLD supports or does not support operating parameters that carry feedback NAVs for links other than the link where it is located.
  • it also includes:
  • a first association module configured to receive an association request and determine at least one of the following information according to the association request:
  • the PPDU includes preamble or MPDU frame header information, and the preamble or MPDU frame header information is used to trigger recording of network transmission and status update information.
  • the MPDU corresponding to the PPDU includes NAV policy indication information, and the NAV policy indication information is used to indicate at least one of the following:
  • the NAV control frame is used to indicate: the quantity of network transmission and status update information carried; NAV value; and the target site corresponding to the network transmission and status update information.
  • the parameter feedback device proposed in this embodiment and the parameter feedback method proposed in the foregoing embodiments belong to the same inventive concept, and the technical details not described in detail in this embodiment may refer to any of the foregoing embodiments.
  • the embodiment of the present application also provides a parameter updating device.
  • the parameter updating device includes:
  • the parameter receiving module is configured to obtain information about the second site in the Non-AP MLD through the first link after the first site sends the AP MLD to the AP MLD through a specific frame interval at the end of the physical layer PPDU NAV update parameters, wherein the NAV update parameters are determined according to network transmission and state update information about the NAV of the second site in the BSS where the second link is located;
  • the update module is configured to update the local NAV parameters according to the NAV update parameters when the NAV update parameters are obtained.
  • the first link to receive the NAV update parameters, and update the local NAV parameters accordingly, as the basis for determining the timing of data transmission, so as to solve the problem of data transmission conflicts in the multi-link communication process.
  • the update module is set to:
  • the local NAV parameter is used as the updated local NAV parameter
  • the difference between the NAV update parameter and the NAV value corresponding to the transmission time of the NAV update parameter is used as the updated local NAV parameter;
  • the local NAV parameter is used as the updated local NAV parameter.
  • the NAV update parameter is sequentially sent to the second station through the access point associated with the first link in the AP MLD and the first station.
  • the NAV update parameter is obtained through an acknowledgment reply frame, and the acknowledgment reply frame includes an ACK frame or a BA frame; or,
  • the NAV update parameter is obtained through the NAV control frame, and the NAV control frame is obtained after the first frame interval after the PPDU transmission of the first site is completed, or after the second frame interval after the confirmation reply frame transmission is completed. .
  • it also includes:
  • the broadcast receiving module is configured to receive multi-link capability information, wherein the multi-link capability information includes at least one of the following:
  • At least one access point in the AP MLD supports or does not support carrying NAV update parameters of links other than the link where it is located;
  • At least one access point in the AP MLD supports or does not support operating parameters that carry feedback NAVs for links other than the link in which it is located.
  • it also includes:
  • the second association module is configured to send an association request, where the association request is used to request at least one of the following information:
  • the PPDU includes preamble or MPDU frame header information, and the preamble or MPDU frame header information is used to trigger recording of the network transmission and status update information.
  • the MPDU corresponding to the PPDU includes NAV policy indication information, where the NAV policy indication information is used to indicate at least one of the following:
  • the NAV control frame is used to indicate: the quantity of network transmission and status update information carried; NAV value; and a target site corresponding to the network transmission and status update information.
  • the parameter updating apparatus proposed in this embodiment and the parameter updating method provided in the above-mentioned embodiments belong to the same inventive concept, and the technical details not described in detail in this embodiment may refer to any of the above-mentioned embodiments.
  • the embodiment of the present application also provides an association device.
  • the associated device includes:
  • a broadcast module configured to broadcast multi-link capability information, where the broadcast multi-link capability information includes the support capability of the AP MLD to feedback NAV update parameters;
  • a request receiving module configured to receive an association request of the Non-AP MLD, where the association request is used to determine the link connection relationship between the AP MLD and the Non-AP MLD, the link's ability to support simultaneous sending and receiving and the described The support capability of stations in Non-AP MLD to receive NAV update parameters;
  • a response module configured to send association response information to the Non-AP MLD according to the association request.
  • the association device in this embodiment establishes the multi-link connection of the NSTR by broadcasting the multi-link capability information and responding to the association request of the Non-AP MLD, so that the first link can be provided for use when the second link is in the blind area.
  • Feedback NAV update parameters For technical details not described in detail in this embodiment, reference may be made to any of the above-mentioned embodiments.
  • the association device is further configured to execute the parameter feedback method applied to the AP MLD in the foregoing embodiment according to the association response information.
  • association device proposed in this embodiment and the association method applied to AP MLD proposed in the above embodiment belong to the same inventive concept, and the technical details not described in detail in this embodiment may refer to any of the above embodiments.
  • the embodiment of the present application further provides another association device.
  • the associated device includes:
  • a broadcast receiving module configured to receive the multi-link capability information broadcast by the AP MLD, where the broadcast multi-link capability information includes the AP MLD's support capability for feeding back NAV update parameters;
  • a request module configured to send an association request to the AP MLD according to the multi-link capability information, where the association request is used to determine the link connection relationship between the AP MLD and the Non-AP MLD, and the link pair is simultaneously The support ability of sending and receiving and the support ability of the station in the Non-AP MLD to receive NAV update parameters;
  • the response receiving module is configured to receive the associated response information of the AP MLD.
  • the association device of this embodiment establishes a multi-link connection of the NSTR by sending an association request and receiving the association response information of the AP MLD, so that the NAV update parameters fed back through the first link can be received during the period when the second link is in the blind area. , and update the local NAV parameters accordingly.
  • the association device is further configured to execute the parameter update method applied to the Non-AP MLD in the above embodiment according to the association response information.
  • association device proposed in this embodiment and the method for updating parameters applied to Non-AP MLD proposed in the above embodiment belong to the same inventive concept, and the technical details not described in detail in this embodiment may refer to any of the above embodiments.
  • FIG. 12 is a schematic diagram of a hardware structure of a communication node provided by an embodiment.
  • the communication node provided by the present application includes a memory 52 , a processor 51 and A computer program stored in the memory and executable on the processor, when the processor 51 executes the program, the above-mentioned parameter feedback method, parameter update method or association method is implemented.
  • the communication node may also include a memory 52; the processor 51 in the communication node may be one or more, and one processor 51 is taken as an example in FIG. 12; the memory 52 is used to store one or more programs; the one or more Each program is executed by the one or more processors 51 , so that the one or more processors 51 implement the parameter feedback method, the parameter update method or the association method as described in the embodiments of the present application.
  • the communication node in the case of executing the parameter feedback method or the association method applied to the AP MLD, the communication node is the access point in the AP MLD; in the case of executing the parameter update method or the association method applied to the Non-AP MLD Below, the communication node is the site in the Non-AP MLD.
  • the communication node further includes: a communication device 53 , an input device 54 and an output device 55 .
  • the processor 51 , the memory 52 , the communication device 53 , the input device 54 and the output device 55 in the communication node may be connected by a bus or in other ways, and the connection by a bus is taken as an example in FIG. 12 .
  • the input device 54 may be used to receive input numerical or character information, and to generate key signal input related to user settings and function control of the communication node.
  • the output device 55 may include a display device such as a display screen.
  • the communication device 53 may include a receiver and a transmitter.
  • the communication device 53 is configured to transmit and receive information according to the control of the processor 51 .
  • the memory 52 may be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the parameter feedback methods described in the embodiments of the present application.
  • the memory 52 may include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program required for at least one function; the stored data area may store data created according to use of the communication node, and the like.
  • memory 52 may include high speed random access memory, and may also include nonvolatile memory, such as at least one magnetic disk storage device, flash memory device, or other nonvolatile solid state storage device.
  • memory 52 may further include memory located remotely relative to processor 51, which remote memory may be connected to the communication node through a network.
  • networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • FIG. 13 is a schematic structural diagram of a communication system according to an embodiment.
  • the system includes an access point multi-link device 610 and a non-access point multi-link device 620; the access point multi-link device 610 and the non-access point multi-link device 620 pass through the first link The first link and the second link of the non-access point multi-link device 620 do not support simultaneous transmission and reception; the access point multi-link device 610 is configured to perform the above-mentioned parameter feedback method or For example, the association method applied to the AP MLD; the non-access point multi-link device 620 is used to perform the above-mentioned parameter updating method or the association method applied to the non-access point multi-link device 620.
  • the association method applied to the AP MLD the non-access point multi-link device 620 is used to perform the above-mentioned parameter updating method or the association method applied to the non-access point multi-link device 620.
  • the access point multi-link device 610 records the network transmission and status update information about the NAV of the second site and feeds back the NAV update parameters of the second site through the first link, and the non-access point multi-link device 620 passes through the first link.
  • the router receives the NAV update parameters, and updates the local NAV parameters accordingly, as the basis for determining the data transmission timing, so as to solve the problems of NAV loss and data transmission conflicts caused by blind spots in the multi-link communication process.
  • the non-access point multi-link device 620 includes a first station and a second station; the access point multi-link device 610 includes an access point that records network transmission and status update information of the second link and For the access point that receives the PPDU of the first site, the NAV update parameter is fed back to the access point that records the network transmission and status update information of the second link through the access point that receives the PPDU of the first site, and the first site in turn. Second site.
  • access point multilink device 610 broadcasts multilink capabilities; non-access point multilink device 620 sends an association request to access point multilink device 610; access point multilink device 610 The association response information is sent to the non-access point multi-link device 620 according to the association request.
  • the association request of the non-access point multi-link device 620 is used to determine the link connection relationship between the AP MLD and the non-access point multi-link device, and the link's support capability for simultaneous transmission and reception. , the support capability of the AP MLD to feedback NAV update parameters and the support capability of the station in the non-access point multi-link device to receive NAV update parameters.
  • the access point multi-link device 610 generates the NAV update parameters according to the network transmission and status update information.
  • the access point multilink device 610 sets the NAV update parameter to an initial value, and updates the NAV update parameter according to at least one of the following:
  • the duration information indicated by the sent PPDU updates the NAV update parameter.
  • the access point multi-link device 610 feeds back the information to the non-access point multi-link device through the first link.
  • the access point multi-link device 610 sequentially sends the NAV update parameter to the first station through the access point associated with the first link in the AP MLD and the first station. Second site.
  • the NAV update parameter is fed back through an acknowledgment reply frame, and the acknowledgment reply frame includes an ACK frame or a BA frame; or, the NAV update parameter is fed back through a NAV control frame, and the NAV control frame is in the Feedback is performed after the first frame interval after the PPDU transmission of the first station is completed, or after the second frame interval after the completion of the acknowledgement reply frame transmission.
  • the access point multi-link device 610 also broadcasts multi-link capability information, wherein the multi-link capability information includes at least one of the following:
  • At least one access point in the AP MLD supports or does not support carrying NAV update parameters of links other than the link where it is located;
  • At least one access point in the AP MLD supports or does not support operating parameters that carry feedback NAVs for links other than the link where it is located.
  • the access point multi-link device 610 further receives an association request and determines at least one of the following information according to the association request:
  • the PPDU includes preamble or MPDU frame header information, and the preamble or MPDU frame header information is used to trigger recording of the network transmission and status update information.
  • the MPDU corresponding to the PPDU includes NAV policy indication information, where the NAV policy indication information is used to indicate at least one of the following:
  • the NAV control frame is used to indicate: the quantity of network transmission and status update information carried; NAV value; and a target site corresponding to the network transmission and status update information.
  • the non-access point multi-link device 620 obtains information about the non-access point through the first link after the first station sends the AP MLD to the AP MLD through a specific frame interval at the end of the physical layer PPDU.
  • NAV update parameters of the second site in the access point multi-link device wherein the NAV update parameters are determined according to network transmission and state update information about the NAV of the second site in the BSS where the second link is located;
  • the local NAV parameter is updated according to the NAV update parameter.
  • the non-access point multi-link device 620 uses the local NAV parameter as the updated local NAV parameter;
  • the difference between the NAV update parameter and the NAV value corresponding to the transmission time of the NAV update parameter is used as the updated local NAV parameter;
  • the local NAV parameter is used as the updated local NAV parameter.
  • the non-access point multi-link device 620 is further configured to receive multi-link capability information, where the multi-link capability information includes at least one of the following:
  • At least one access point in the AP MLD supports or does not support carrying NAV update parameters of links other than the link where it is located;
  • At least one access point in the AP MLD supports or does not support operating parameters that carry feedback NAVs for links other than the link where it is located.
  • the non-access point multi-link device 620 is further configured to send an association request, where the association request is used to request at least one of the following information:
  • An embodiment of the present application further provides a storage medium, where the storage medium stores a computer program, and when the computer program is executed by a processor, implements the parameter feedback method, the parameter update method, or the association method described in any of the embodiments of the present application .
  • the parameter feedback method includes: during the period of receiving the PPDU sent by the first station in the non-access point multi-link device through the first link, recording the information about the non-access point in the BSS where the second link is located.
  • the feedback state includes feedback or no feedback; if the feedback state is feedback, after a specific frame interval after the end of receiving the PPDU, the multi-link to the non-access point through the first link The device feeds back the NAV update parameter.
  • the parameter updating method includes: after the first station sends the AP MLD through the first link to the AP MLD at the end of the specific frame interval of the physical layer PPDU, acquiring information about the non-access point multi-link device through the first link
  • the NAV update parameter of the second site wherein the NAV update parameter is determined according to the network transmission and state update information about the NAV of the second site in the BSS where the second link is located; after the NAV update parameter is obtained
  • the local NAV parameters are updated according to the NAV update parameters.
  • the association method includes: broadcasting multi-link capability information, where the broadcast multi-link capability information includes the AP MLD's support capability for feeding back NAV update parameters; and receiving an association request from the Non-AP MLD, where the association request is used to determine the AP
  • the link connection relationship between the MLD and the non-access point multi-link device, the link's ability to support simultaneous transmission and reception, and the support capability of the station in the non-access point multi-link device to receive NAV update parameters send association response information to the non-access point multi-link device according to the association request.
  • the association method includes: receiving multi-link capability information broadcast by the AP MLD, where the broadcast multi-link capability information includes the AP MLD's support capability for feeding back NAV update parameters;
  • the AP MLD sends an association request, where the association request is used to determine the link connection relationship between the AP MLD and the non-access point multi-link device, the link's ability to support simultaneous transmission and reception, and the non-access point multi-link device.
  • the computer storage medium of the embodiments of the present application may adopt any combination of one or more computer-readable media.
  • the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium.
  • the computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any combination of the above. More specific examples (non-exhaustive list) of computer readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (Read Only Memory, ROM), Erasable Programmable Read Only Memory (EPROM), flash memory, optical fiber, portable CD-ROM, optical storage device, magnetic storage device, or any suitable combination of the above .
  • a computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in connection with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a propagated data signal in baseband or as part of a carrier wave, with computer-readable program code embodied thereon. Such propagated data signals may take a variety of forms including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device .
  • Program code embodied on a computer readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber cable, radio frequency (RF), etc., or any suitable combination of the foregoing.
  • suitable medium including but not limited to: wireless, wire, optical fiber cable, radio frequency (RF), etc., or any suitable combination of the foregoing.
  • Computer program code for carrying out the operations of the present application may be written in one or more programming languages, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional A procedural programming language, such as the "C" language or similar programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or Wide Area Network (WAN), or it may be connected to an external computer (eg use an internet service provider to connect via the internet).
  • LAN Local Area Network
  • WAN Wide Area Network
  • user terminal encompasses any suitable type of wireless user equipment, such as a mobile telephone, portable data processing device, portable web browser or vehicle mounted mobile station.
  • the various embodiments of the present application may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Embodiments of the present application may be implemented by the execution of computer program instructions by a data processor of a mobile device, eg in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source or object code.
  • ISA Instruction Set Architecture
  • the block diagrams of any logic flow in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, Read-Only Memory (ROM), Random Access Memory (RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD), etc.
  • Computer readable media may include non-transitory storage media.
  • Data processors may be any suitable for the local technical environment Type, such as but not limited to general-purpose computer, special-purpose computer, microprocessor, digital signal processor (Digital Signal Processing, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), programmable logic device (Field-Programmable Gate Array , FPGA) and processors based on multi-core processor architectures.
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • processors based on multi-core processor architectures.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种参数反馈、更新、关联方法、通信节点、通信系统及介质。该参数反馈在通过第一链路接收非接入点多链路设备中的第一站点发送的物理层协议数据单元PPDU的期间，记录第二链路所在基本服务集中关于非接入点多链路设备中第二站点的网络配置向量NAV的网络传输与状态更新信息，其中，接入点多链路设备与非接入点多链路设备通过第一链路和第二链路相连，非接入点多链路设备的第一链路和第二链路不支持同时收发；根据网络传输与状态更新信息确定关于第二站点的NAV更新参数的反馈状态，包括反馈或不反馈；在反馈状态为反馈的情况下，在PPDU接收结束的特定帧间隔后通过第一链路向非接入点多链路设备反馈NAV更新参数。

Description

参数反馈、更新、关联方法、通信节点、通信系统及介质 技术领域
本申请涉及无线通信网络，例如涉及一种参数反馈、更新、关联方法、通信节点、通信系统及介质。
背景技术
对于多链路设备(Multi-link Device，MLD)，如果附属的站点都是接入点(Access Point，AP)，则为接入点多链路设备(AP MLD)，如果附属的站点都是非接入点(Non-AP)的站点(Station，STA)，则为非接入点多链路设备(Non-AP MLD)。非接入点多链路设备中的STA与AP多链路设备中的AP可以通过不同的链路通信。在多链路通信系统中存在不支持数据同时收发(Non-Simultaneous Transmit and Receive，NSTR)的多链路设备，在不支持数据同时收发的链路集中的一条链路在发送数据的过程中，其他链路不能接收数据而造成网络配置向量(Network Allocation Vector，NAV)相关参数丢失，这种情况下，站点无法明确信道的忙闲状态和无线媒介的占用时间，从而导致与其他链路传输数据的冲突。目前没有有效的解决机制，能够保证站点获取到NAV相关参数。
发明内容
本申请提供一种参数反馈、更新、关联方法、通信节点、通信系统及介质，以实现向非接入点多链路设备反馈NAV，提高多链路通信的可靠性。
本申请实施例提供一种参数反馈方法，应用于AP MLD，包括：
在通过第一链路接收非接入点多链路设备中的第一站点发送的物理层(Physical Layer，PHY)协议数据单元(Protocol Data Unit，PPDU)的期间，记录第二链路所在的基本服务集(Basic Service Set，BSS)中关于所述非接入点多链路设备中的第二站点的NAV的网络传输与状态更新信息，其中，AP MLD与所述非接入点多链路设备通过所述第一链路和所述第二链路相连，所述非接入 点多链路设备的第一链路和所述第二链路不支持同时收发；
根据所述网络传输与状态更新信息确定关于所述第二站点的NAV更新参数的反馈状态，所述反馈状态包括反馈或不反馈；
在所述反馈状态为反馈的情况下，在所述PPDU接收结束的特定帧间隔后，通过所述第一链路向所述非接入点多链路设备反馈所述NAV更新参数。
本申请实施例还提供了一种参数更新方法，应用于非接入点多链路设备，包括：
在第一站点通过第一链路向AP MLD发送物理层PPDU结束的特定帧间隔后，通过所述第一链路获取关于所述非接入点多链路设备中的第二站点的NAV更新参数，其中，所述NAV更新参数根据第二链路所在的BSS中关于所述第二站点的NAV的网络传输与状态更新信息确定；
在获取到所述NAV更新参数的情况下，根据所述NAV更新参数更新本地NAV参数。
本申请实施例还提供了一种关联方法，包括：
广播多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈NAV更新参数的支持能力；
接收非接入点多链路设备的关联请求，所述关联请求用于确定AP MLD与所述非接入点多链路设备之间的链路连接关系、链路对同时收发的支持能力以及所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力；
根据所述关联请求向所述非接入点多链路设备发送关联应答信息。
本申请实施例还提供了一种关联方法，包括：
接收AP MLD广播的多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈NAV更新参数的支持能力；
根据所述多链路能力信息向所述AP MLD发送关联请求，所述关联请求用于确定AP MLD与所述非接入点多链路设备之间的链路连接关系、链路对同时收发的支持能力以及所述非接入点多链路设备中的站点对接收NAV更新参数的支持 能力。
本申请实施例还提供了一种通信节点，包括：存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现上述的参数反馈方法、参数更新方法或关联方法。
本申请实施例还提供了一种通信系统，包括接入点多链路设备和非接入点多链路设备；
所述接入点多链路设备用于执行上述的参数反馈方法或应用于AP MLD的关联方法；
所述非接入点多链路设备用于执行上述的参数更新方法或应用于非接入点多链路设备的关联方法。
本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该程序被处理器执行时实现上述的参数反馈方法、参数更新方法或关联方法。
附图说明
图1为一实施例提供的一种多链路设备之间传输数据冲突的示意图；
图2为一实施例提供的一种参数反馈方法的流程图；
图3为一实施例提供的一种AP MLD向非接入点多链路设备反馈NAV更新参数的示意图；
图4为一实施例提供的反馈NAV更新参数的示意图；
图5为一实施例提供的一种包含NAV策略信息的MAC帧的示意图；
图6为一实施例提供的一种包含NAV策略信息的NAV控制帧的示意图；
图7为一实施例提供的一种包含NAV策略信息的ACK帧的示意图；
图8为一实施例提供的一种参数更新方法的流程图；
图9为一实施例提供的一种关联方法的流程图；
图10为一实施例提供的一种AP MLD与非接入点多链路设备之间关联过程 的示意图；
图11为另一实施例提供的一种关联方法的流程图；
图12为一实施例提供的一种通信节点的硬件结构示意图；
图13为一实施例提供的一种通信系统的结构示意图。
具体实施方式
下面结合附图和实施例对本申请进行说明
在多链路通信中，同时收发是指在同一MLD的两条链路上分别同时收发数据，如果MLD中不同链路的信道之间隔离度低，容易引发设备内共存干扰，因此，很多应用场景中不支持MLD设备在不同链路上的同时收发。MLD设备分为两种：AP MLD以及Non-AP MLD。NAV相当于一个计数器，可用于反映信道的忙与闲，Non-AP MLD设备根据NAV可确定何时能够进行数据传输，从而有效避免与相同链路上正在传输的数据发生冲突。但是，对于NSTR的Non-AP MLD设备，由于在通过第一条链路发送数据的过程中，第二条链路不能接收数据，即第二条链路无法接收来自与AP MLD的NAV等网络传输控制参数，因此第二条链路无法确定合适的时间进行数据传输，导致与BSS中使用该第二条链路的其他站点的数据传输冲突。
图1为一实施例提供的一种多链路设备之间传输数据冲突的示意图。如图1所示，AP MLD与Non-AP MLD之间通过第一链路和第二链路连接，第一链路和第二链路为NSTR的链路。在STA1通过第一链路向AP MLD发送数据的过程中，STA2无法接收AP MLD的数据造成STA2在第二链路上的NAV信息丢失，STA2无法及时更新NAV，只能利用本地存储的错误的NAV确定传输机会并在获得传输机会后马上传输数据，从而与第二链路上正在进行的数据传输(即STA3与AP2之间的数据传输)在AP2端发生冲突。图1中，TA表示发送端，RA表示接收端；RTS表示发送请求(Request To Send，RTS)帧，CTS表示准许发送(Clear To send，CTS)帧；点状区域表示STA2无法在第二链路上接收 NAV的盲区；网格状区域表示第一链路上的数据传输已经完成，STA2在此区域内可以进行数据传输；STA3与STA2属于一个BSS。
在本申请实施例中，提供一种参数反馈方法，在NSTR的Non-AP MLD设备通过第一链路向AP MLD发送数据期间(即Non-AP MLD设备处于第二链路的盲区的期间)，记录关于第二站点NAV的网络传输与状态更新信息并通过第一链路来反馈第二站点的NAV更新参数，以解决多链路通信过程中由于盲区导致的NAV丢失以及数据传输冲突问题。
图2为一实施例提供的一种参数反馈方法的流程图。本实施例提供的方法可应用于AP MLD，具体可应用于接入点，例如图1中的AP2。如图2所示，本实施例提供的方法包括步骤110、120和130。
在步骤110中，在通过第一链路接收非接入点多链路设备中的第一站点发送的物理层协议数据单元PPDU的期间，记录第二链路所在的基本服务集BSS中关于所述非接入点多链路设备中的第二站点的网络配置向量NAV的网络传输与状态更新信息，其中，AP MLD与所述非接入点多链路设备通过所述第一链路和所述第二链路相连，所述非接入点多链路设备的第一链路和所述第二链路不支持同时收发；
本实施例中，AP MLD可以包含多个接入点，Non-AP MLD可以包含多个站点。在Non-AP MLD不支持同时收发的链路集中，任意一个链路获取传输机会后可向AP MLD发送PPDU，将该链路记为的第一链路，第一链路对应的站点为第一站点，该链路集中的其他链路(即第二链路)在第一链路发送PPDU期间不支持接收数据。该链路集中的链路处于已使能的状态(即处于收发数据状态)。Non-AP MLD通过第一链路向AP MLD发送PPDU，会触发AP MLD对第二链路的第二站点的网络传输与状态更新信息进行记录，网络传输与状态更新信息包括第二链路的信道的忙闲状态、预计传输时间、传输数据长度等，AP MLD根据这些信息可以确定关于第二站点在第二链路上传输数据的NAV值，以反馈给Non-AP MLD，从而指示第二站点等待相应的时长后再进行数据传输， 避免第二链路上的冲突。需要说明的是，记录第二链路的网络传输与状态更新信息的接入点与接收第一站点的PPDU的接入点可以不同。例如图1中，在STA1通过第一链路向AP1发送PPDU的情况下，触发AP2记录第二链路的网络传输与状态更新信息。
在步骤120中，根据所述网络传输与状态更新信息确定关于所述第二站点的NAV更新参数的反馈状态，所述反馈状态包括反馈或不反馈。
本实施例中，AP MLD根据记录的网络传输与状态更新信息确定是否向Non-AP MLD反馈NAV更新参数，NAV更新参数用于指示Non-AP MLD更新本地存储的NAV。例如，AP MLD根据记录的网络传输与状态更新信息计算第二站点的NAV更新参数，在第一链路中的PPDU发送结束后，无论第二站点的NAV是否为0，AP MLD总是将NAV更新参数反馈至Non-AP MLD；或者，AP MLD只在第二站点的NAV大于0的情况下向Non-AP MLD反馈NAV更新参数等。
在一实施例中，记录第二链路的网络传输与状态更新信息的接入点与接收第一站点的PPDU的接入点不同，这种情况下，记录第二链路的网络传输与状态更新信息的接入点可以将需要反馈的NAV更新参数通过第一链路转发至Non-AP MLD。
在步骤130中，在所述反馈状态为反馈的情况下，在所述PPDU接收结束的特定帧间隔后，通过所述第一链路向所述Non-AP MLD反馈所述NAV更新参数。
本实施例中，在确定向Non-AP MLD反馈NAV更新参数的情况下，在第一链路中的PPDU发送结束后的特定帧间隔后，AP MLD通过第一链路将NAV更新参数反馈至Non-AP MLD，从而在第二链路无法接收数据的情况下，借助第一链路实现了NAV更新参数的反馈，使Non-AP MLD在NSTR的链路集的使能期间，能够及时获取NAV更新参数，合理确定第二站点在第二链路上的传输时机，有效避免与在第二链路上其他站点正在进行的数据传输的冲突。
图3为一实施例提供的一种AP MLD向非接入点多链路设备反馈NAV更新参数的示意图。如图3所示，(1)STA1向AP1发送PPDU；(2)AP2记录关于STA2的网络传输与状态更新信息；(3)AP2根据记录的网络传输与状态更新信息确定NAV更新参数，并将NAV更新参数发送给AP1；(4)AP1通过第一链路将NAV更新参数发送给STA1；(5)STA1将NAV更新参数发送给STA2；(6)STA2根据NAV更新参数更新本地NAV参数。在此基础上，STA2可以合理确定通过第二链路向AP2发送RTS帧的时间，避开同一BSS中的STA3通过第二链路向AP2发送数据的时间，从而避免第二链路上数据传输的冲突。
在一实施例中，还包括步骤112：根据网络传输与状态更新信息生成NAV更新参数。
具体的，网络传输与状态更新信息包括第二链路的信道的忙闲状态、第二链路上同一BSS中的其他站点的数据的预计传输时间、传输数据长度等，AP MLD通过记录这些信息可以确定关于第二站点在第二链路上传输数据的NAV值，以指示第二站点等待相应的时长后才能获取传输机会，从而避免第二链路上同一BSS的不同站点之间数据传输的冲突。
在一实施例中，步骤112包括：将NAV更新参数设置为初始值，并根据以下至少之一更新NAV更新参数：在通过第二链路所在BSS向第三站点发送CTS帧的情况下，根据CTS帧指示的时长信息更新NAV更新参数；在通过第二链路所在BSS接收到第三站点的PPDU的情况下，根据第三站点的PPDU指示的时长信息更新NAV更新参数；在获取第二链路所在BSS的传输机会并通过第二链路所在BSS向第三站点发送PPDU的情况下，根据传输机会的时长信息或向第三站点发送的PPDU指示的时长信息更新NAV更新参数。
本实施例中，AP MLD在被触发记录网络传输与状态更新信息的过程中，生成第二站点相关的NAV更新参数，NAV更新参数的初始值设为零，在第一链路上的PPDU发送期间，根据第二链路及所在BSS的数据传输情况对NAV更新参数赋值。此外，在赋值的过程中，NAV更新参数随时间变化也在实时缩减。 赋值过程包括以下至少一种：
1)AP MLD通过第二链路所在BSS发送CTS帧指示第三站点发送数据，则把CTS帧所指示的时长信息赋值给NAV更新参数；
2)AP MLD通过第二链路所在BSS接收到第三站点发来的PPDU，则把该PPDU上指示的时长信息赋值给NAV更新参数；
3)AP MLD在第二链路上获取传输机会，并通过第二链路所在BSS发送PPDU给第三站点或触发第三站点发送上行数据，则把该PPDU指示的时长信息或传输机会的时长信息赋值给NAV更新参数。
在一实施例中，步骤130，包括：
在NAV更新参数为0或非0的情况下，通过第一链路向Non-AP MLD反馈NAV更新参数；或者，在NAV更新参数大于0的情况下，通过第一链路向Non-AP MLD反馈NAV更新参数。
本实施例中，AP MLD根据记录的网络传输与状态更新信息计算第二站点的NAV更新参数，在第一链路中的PPDU发送结束后，一种情况是，无论第二站点的NAV是否为0，AP MLD总是将NAV更新参数反馈至Non-AP MLD；另一种情况是，AP MLD只在第二站点的NAV大于0的情况下向Non-AP MLD反馈NAV更新参数，第二站点的NAV大于0，表明第二站点需要等待一定的时间后才能进行数据传输，如果NAV等于0，则第二站点无需等待，在PPDU发送完成后即可随时传输数据，这种情况下可以不反馈NAV，第二站点也无需更新本地NAV参数。
在一实施例中，步骤130，包括：将NAV更新参数依次通过AP MLD中与第一链路关联的接入点以及第一站点发送至第二站点。
本实施例中，AP MLD中用于记录第二链路的网络传输与状态更新信息的接入点与接收第一站点的PPDU的接入点不同，这种情况下，记录第二站点的网络传输与状态更新信息的接入点可以将需要反馈的NAV更新参数通过第一链路(从接收第一站点的PPDU的接入点到第一站点的链路)转发至第二站点。
在一实施例中，NAV更新参数通过确认回复帧反馈，确认回复帧包括确认(Acknowledge，ACK)帧或块确认(Block Acknowledge，BA)帧；或者，NAV更新参数通过NAV控制帧反馈，NAV控制帧在第一站点的PPDU传输完成后的第一帧间隔后反馈，或者在确认回复帧传输完成后的第二帧间隔后反馈。
图4为一实施例提供的反馈NAV更新参数的示意图。如图4所示，AP MLD与Non-AP MLD首先协商NAV更新参数的传输能力，例如，AP MLD是否支持记录第二站点的网络传输与状态更新信息、是否支持向Non-AP MLD反馈NAV更新参数、Non-AP MLD是否支持通过第一链路接收NAV更新参数、AP MLD与Non-AP MLD之间的连接关系等。在Non-AP MLD通过NSTR的链路集中的第一链路向AP-MLD发送MAC层协议数据单元(MAC Protocol Data Unit，MPDU)，即发送MAC帧的过程中，在MPDU中携带NAV策略(NAV Policy)信息，以请求AP MLD反馈在NSTR的链路集中除第一链路以外的其他链路对应的NAV更新参数。例如，AP1一旦接收到MPDU所在PPDU的前导码或MPDU帧头信息，就立即触发AP2记录第二链路的网络传输与状态更新信息；在MPDU接收结束后，AP2反馈NAV更新参数给AP1，AP1则发送包含NAV更新参数的ACK帧或BLOCK ACK帧或NAV控制帧给Non-AP MLD的STA1；STA1收到NAV更新参数后则立即反馈给STA2，STA2根据NAV更新参数更新本地NAV参数。
图5为一实施例提供的一种包含NAV策略信息的MAC帧的示意图。如图5所示，MAC帧头中包含了帧控制字段(用于指示是哪种帧类型)、时长/ID字段(用于指示所在帧的预计传输时长或所在帧的编号)、地址字段(用于指示该帧的接收方或发送方)以及NAV策略字段；帧体中包含传输的有效数据；帧体后还可包括帧校验序列(Frame Check Sequence，FCK)。NAV策略字段用于表示Non-AP MLD是否请求AP MLD反馈NAV更新参数。例如，NAV策略字段共有三种取值，第一种取值表示不反馈NAV更新参数；第二种取值表示不管NAV更新参数是否为0都反馈NAV更新参数；第三种取值表示当NAV更新参 数为0时不反馈NAV更新参数，而在NAV更新参数大于0时反馈NAV更新参数。或者，NAV策略字段可以有两种取值，第一种取值表示不反馈NAV更新参数，第二种取值表示反馈NAV更新参数。
图6为一实施例提供的一种包含NAV策略信息的NAV控制帧的示意图。如图6所示，NAV控制帧的MAC帧头中包含了帧控制字段、时长/ID字段以及地址字段；帧体中包含NAV信息域，NAV信息域是由NAV_INFO(用于指示携带的NAV更新参数的数量)以及至少一个Per_NAV_INFO(用于指示NAV更新参数的值)以及至少一个STA_INFO(用于指示NAV更新参数对应的站点)的实例所组成的；帧体后还包括帧校验序列。
图7为一实施例提供的一种包含NAV策略信息的ACK帧的示意图；如图7所示，ACK帧的帧头中包含了帧控制字段、时长/ID字段以及地址字段；帧体中包含块确认BA信息域(用于指示数据块的传输是否成功)以及NAV信息域，NAV信息域是由NAV_INFO、至少一个Per_NAV_INFO以及至少一个STA_INFO的实例所组成的；帧体后还包括帧校验序列。图6和图7中，NAV信息域的内容可以相同。
在一实施例中，还包括步骤100：广播多链路能力信息，其中，多链路能力信息包括以下至少之一：AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的NAV更新参数；AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的反馈NAV的操作参数。
本实施例中，NAV更新参数的传输能力的协商可以在MLD建立关联的阶段进行，也可以在MLD建立关联后、在第一站点发起多链路操作的过程中进行。AP MLD通过信标(Beacon)广播多链路能力，例如Non-AP MLD中的接入点是否支持携带第二站点的NAV更新参数，以及是否支持携带通过第一链路反馈NAV的操作参数，反馈NAV的操作参数例如为支持以下哪种反馈方式：1)通过确认回复帧反馈，其中，确认回复帧包括ACK帧或BA帧；2)通过NAV控制帧反馈。
在一实施例中，还包括：步骤102：接收关联请求并根据关联请求确定以下信息至少之一：AP MLD中的每个接入点在Non-AP MLD中关联的站点；AP MLD与Non-AP MLD之间的链路连接关系；不支持同时收发的链路；AP MLD对反馈NAV更新参数的支持能力；Non-AP MLD中的站点对接收NAV更新参数的支持能力；反馈NAV的操作参数。
本实施例中，Non-AP MLD选择一个站点作为发起多链路操作的STA(即第一站点)，并向AP MLD发送关联请求，其中，关联请求指明Non-AP MLD中关联的站点(包括第一站点与第二站点)，还可指示第一链路与第二链路是NSTR的链路，以及Non-AP MLD中关联的站点是否支持接收通过关联的链路接收NAV更新参数；还可用于请求确定AP MLD中的接入点是否支持反馈Non-AP MLD中的站点的NAV更新参数；还可用于请求确定相关的操作参数，例如反馈NAV的操作参数。
在一实施例中，PPDU中包括前导码或MPDUMPDU帧头信息，前导码或MPDUMPDU帧头信息用于触发记录网络传输与状态更新信息。
本实施例中，AP MLD一旦接收到MPDU所在PPDU的前导码或MPDU帧头信息，就立即触发记录第二链路的网络传输与状态更新信息。
在一实施例中，PPDU对应的MPDUMPDU中包括NAV策略指示信息，NAV策略指示信息用于指示以下至少之一：不反馈NAV更新参数；在NAV更新参数为0或非0的情况下反馈NAV更新参数；在NAV更新参数大于0的情况下反馈NAV更新参数。
本实施例中，NAV策略字段共有三种取值，第一种取值表示不反馈NAV更新参数；第二种取值表示不管NAV更新参数是否为0都反馈NAV更新参数；第三种取值表示当NAV更新参数为0时不反馈NAV更新参数，而在NAV更新参数大于0时反馈NAV更新参数。或者，NAV策略字段可以有两种取值，第一种取值表示不反馈NAV更新参数，第二种取值表示反馈NAV更新参数。
在一实施例中，NAV控制帧用于指示：携带的网络传输与状态更新信息的 数量；NAV值；网络传输与状态更新信息对应的目标站点。
本实施例中，NAV控制帧通过NAV_INFO指示携带的网络传输与状态更新信息的数量；NAV值；通过至少一个Per_NAV_INFO指示NAV更新参数的值，通过至少一个STA_INFO指示NAV更新参数对应的目标站点。
在本申请实施例中，还提供一种参数更新方法，在NSTR的Non-AP MLD设备通过第一链路向AP MLD发送数据期间(即Non-AP MLD设备处于第二链路的盲区的期间)，通过第一链路接收NAV更新参数，据此更新本地NAV参数，作为数据传输时机的确定依据，以解决多链路通信过程中的数据传输冲突问题。
图8为一实施例提供的一种参数更新方法的流程图。本实施例提供的方法可应用于Non-AP MLD，具体可应用于第二站点。如图8所示，本实施例提供的方法包括步骤210和220。未在本实施例中详尽描述的技术细节可参见上述任意实施例。
在步骤210中，在第一站点通过第一链路向AP MLD发送物理层PPDU结束的特定帧间隔后，通过所述第一链路获取关于所述非接入点多链路设备中的第二站点的NAV更新参数，其中，所述NAV更新参数根据第二链路所在的BSS中关于所述第二站点的NAV的网络传输与状态更新信息确定；
在步骤220中，在获取到所述NAV更新参数的情况下，根据所述NAV更新参数更新本地NAV参数。
本实施例中，Non-AP MLD将通过第一链路接收的NAV更新参数与本地NAV参数比较，如果NAV更新参数为零，则可继续采用本地NAV参数；如果NAV更新参数大于本地NAV参数，则进行相应的更新操作，例如，将NAV更新参数减去NAV更新参数的传输时间后折算为NAV单位的值，作为第二站点更新后的NAV参数；如果NAV更新参数小于本地NAV参数，则可继续采用本地NAV参数。
在一实施例中，步骤220，包括：在NAV更新参数为0的情况下，将本地 NAV参数作为更新后的本地NAV参数；在NAV更新参数大于本地NAV参数的情况下，将NAV更新参数与NAV更新参数的传输时间对应的NAV值的差值作为更新后的本地NAV参数；在NAV更新参数小于本地NAV参数的情况下，将本地NAV参数作为更新后的本地NAV参数。
在一实施例中，NAV更新参数依次通过AP MLD中与第一链路关联的接入点以及第一站点发送至第二站点。
在一实施例中，NAV更新参数通过确认回复帧获取，确认回复帧包括ACK帧或BA帧；或者，NAV更新参数通过NAV控制帧获取，NAV控制帧在第一站点的PPDU传输完成后的第一帧间隔后获取，或者在确认回复帧传输完成后的第二帧间隔后获取。
在一实施例中，还包括：
步骤200：接收多链路能力信息，其中，多链路能力信息包括以下至少之一：
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的NAV更新参数；
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的反馈NAV的操作参数。
在一实施例中，还包括：
步骤202：发送关联请求，关联请求用于请求以下信息至少之一：AP MLD中的每个接入点在Non-AP MLD中关联的站点；AP MLD与Non-AP MLD之间的链路连接关系；不支持同时收发的链路；AP MLD对反馈NAV更新参数的支持能力；Non-AP MLD中的站点对接收NAV更新参数的支持能力；反馈NAV的操作参数。
在一实施例中，PPDU中包括前导码或MPDUMPDU帧头信息，前导码或MPDUMPDU帧头信息用于触发记录网络传输与状态更新信息。
在一实施例中，PPDU对应的MPDU中包括NAV策略指示信息，NAV策略指示信息用于指示以下至少之一：不反馈NAV更新参数；在NAV更新参数 为0或非0的情况下反馈NAV更新参数；在NAV更新参数大于0的情况下反馈NAV更新参数。
在一实施例中，NAV控制帧用于指示：携带的网络传输与状态更新信息的数量；NAV值；网络传输与状态更新信息对应的目标站点。
在本申请实施例中，还提供一种关联方法，应用于AP MLD，AP MLD通过广播多链路能力信息并应答Non-AP MLD的关联请求，建立NSTR的多链路连接，从而在第二链路处于盲区的期间可提供第一链路用于反馈NAV更新参数。未在本实施例中详尽描述的技术细节可参见上述任意实施例。
图9为一实施例提供的一种关联方法的流程图，如图9所示，本实施例提供的方法包括步骤310、320和330。
在步骤310中，广播多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈NAV更新参数的支持能力；
本实施例中，多链路能力信息包括AP MLD是否支持在第一链路中携带Non-AP MLD的第二站点的NAV更新参数和/或反馈NAV的操作参数等。Non-AP MLD接收到广播后，可向AP MLD发送关联请求。
在步骤320中，接收Non-AP MLD的关联请求，所述关联请求用于确定AP MLD与所述Non-AP MLD之间的链路连接关系、链路对同时收发的支持能力以及所述Non-AP MLD中的站点对接收NAV更新参数的支持能力。
本实施例中，Non-AP MLD选择了一个站点作为发起多链路操作的STA(即第一站点)，通过第一站点可向AP MLD发送关联请求，其中，关联请求指明Non-AP MLD中关联的站点(包括第一站点与第二站点)，还可指示第一链路与第二链路是NSTR的链路，以及Non-AP MLD中关联的站点是否支持通过关联的链路接收NAV更新参数；还可用于请求确定AP MLD中的接入点是否支持反馈Non-AP MLD中的站点的NAV更新参数；还可用于请求确定相关的操作参数，例如反馈NAV的操作参数。
在步骤330中，根据所述关联请求向所述非接入点多链路设备发送关联应答信息。
本实施例中，AP MLD向Non-AP MLD发送关联应答信息，关联应答信息用于确认MLD中相关站点(第一站点与第二站点)是否已关联，并确认AP MLD中接入点的功能信息(Capabilities Information)，表明接入点是否支持反馈Non-AP MLD中的站点的NAV更新参数；还可用于请求确定相关的操作参数，例如反馈NAV的操作参数。
图10为一实施例提供的一种AP MLD与非接入点多链路设备之间关联过程的示意图。如图10所示，选择STA1作为发起多链路操作的第一站点；AP1广播多链路能力信息；STA1向AP1发送关联请求；AP1箱STA1发送关联应答消息，从而完成AP MLD与Non-AP MLD的关联。在此基础上，在第二链路处于盲区的期间可通过第一链路实现NAV更新参数的反馈，进而实现第二站点本地NAV参数的更新。
在一实施例中，还包括：步骤340：根据所述关联应答信息，执行上述的参数反馈方法。
在本申请实施例中，还提供一种关联方法，应用于Non-AP MLD，Non-AP MLD通过发送关联请求并接收AP MLD的关联应答信息，建立NSTR的多链路连接，从而在第二链路处于盲区的期间可通过第一链路接收反馈的NAV更新参数，据此更新本地NAV参数。未在本实施例中详尽描述的技术细节可参见上述任意实施例。
图11为另一实施例提供的一种关联方法的流程图，如图11所示，本实施例提供的方法包括步骤410、420和430。
在步骤410中，接收AP MLD广播的多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈NAV更新参数的支持能力；
在步骤420中，根据所述多链路能力信息向所述AP MLD发送关联请求， 所述关联请求用于确定AP MLD与所述非接入点多链路设备之间的链路连接关系、链路对同时收发的支持能力以及所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力；
在步骤430中，接收所述AP MLD的关联应答信息。
在一实施例中，还包括：
步骤440：根据所述关联应答信息，执行上述的参数更新方法
本申请实施例还提供一种参数反馈装置。参数反馈装置包括：
记录模块，设置为在通过第一链路接收非接入点多链路设备Non-AP MLD中的第一站点发送的PPDU的期间，记录第二链路所在的BSS中关于Non-AP MLD中的第二站点的NAV的网络传输与状态更新信息，其中，AP MLD与Non-AP MLD通过第一链路和第二链路相连，Non-AP MLD的第一链路和第二链路不支持同时收发；
反馈状态确定模块，设置为根据网络传输与状态更新信息确定关于第二站点的NAV更新参数的反馈状态，反馈状态包括反馈或不反馈；
反馈模块，设置为在反馈状态为反馈的情况下，在PPDU接收结束的特定帧间隔后，通过第一链路向Non-AP MLD反馈NAV更新参数。
本实施例的参数反馈装置，在NSTR的Non-AP MLD设备通过第一链路向AP MLD发送数据期间(即Non-AP MLD设备处于第二链路的盲区的期间)，通过第一链路来反馈NAV，以解决多链路通信过程中的数据传输冲突问题。
在一实施例中，还包括：
生成模块，设置为根据网络传输与状态更新信息生成NAV更新参数。
在一实施例中，生成模块设置为：
将NAV更新参数设置为初始值，并根据以下至少之一更新NAV更新参数：
在通过第二链路所在BSS向第三站点发送CTS帧的情况下，根据CTS帧指示的时长信息更新NAV更新参数；
在通过第二链路所在BSS接收到第三站点的PPDU的情况下，根据第三站点的PPDU指示的时长信息更新NAV更新参数；
在获取第二链路所在BSS的传输机会并通过第二链路所在BSS向第三站点发送PPDU的情况下，根据传输机会的时长信息或向第三站点发送的PPDU指示的时长信息更新NAV更新参数。
在一实施例中，反馈模块设置为：
在NAV更新参数为0或非0的情况下，通过第一链路向Non-AP MLD反馈NAV更新参数；或者，
在NAV更新参数大于0的情况下，通过第一链路向Non-AP MLD反馈NAV更新参数。
在一实施例中，反馈模块设置为：
将NAV更新参数依次通过AP MLD中与第一链路关联的接入点以及第一站点发送至第二站点。
在一实施例中，NAV更新参数通过确认回复帧反馈，确认回复帧包括ACK帧或BA帧；或者，
NAV更新参数通过NAV控制帧反馈，NAV控制帧在第一站点的PPDU传输完成后的第一帧间隔后反馈，或者在确认回复帧传输完成后的第二帧间隔后反馈。
在一实施例中，还包括：
广播模块，设置为广播多链路能力信息，其中，多链路能力信息包括以下至少之一：
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的NAV更新参数；
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的反馈NAV的操作参数。
在一实施例中，还包括：
第一关联模块，设置为接收关联请求并根据关联请求确定以下信息至少之一：
AP MLD中的每个接入点在Non-AP MLD中关联的站点；
AP MLD与Non-AP MLD之间的链路连接关系；
不支持同时收发的链路；
AP MLD对反馈NAV更新参数的支持能力；
Non-AP MLD中的站点对接收NAV更新参数的支持能力；
反馈NAV的操作参数。
在一实施例中，PPDU中包括前导码或MPDU帧头信息，前导码或MPDU帧头信息用于触发记录网络传输与状态更新信息。
在一实施例中，PPDU对应的MPDU中包括NAV策略指示信息，NAV策略指示信息用于指示以下至少之一：
不反馈NAV更新参数；
在NAV更新参数为0或非0的情况下反馈NAV更新参数；
在NAV更新参数大于0的情况下反馈NAV更新参数。
在一实施例中，NAV控制帧用于指示：携带的网络传输与状态更新信息的数量；NAV值；网络传输与状态更新信息对应的目标站点。
本实施例提出的参数反馈装置与上述实施例提出的参数反馈方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例。
本申请实施例还提供一种参数更新装置。所述参数更新装置包括：
参数接收模块，设置为在第一站点通过第一链路向AP MLD发送物理层PPDU结束的特定帧间隔后，通过所述第一链路获取关于所述Non-AP MLD中的第二站点的NAV更新参数，其中，所述NAV更新参数根据第二链路所在的BSS中关于所述第二站点的NAV的网络传输与状态更新信息确定；
更新模块，设置为在获取到所述NAV更新参数的情况下，根据所述NAV 更新参数更新本地NAV参数。
本实施例的参数更新装置，在NSTR的Non-AP MLD设备通过第一链路向AP MLD发送数据期间(即Non-AP MLD设备处于第二链路的盲区的期间)，通过第一链路来接收NAV更新参数，据此更新本地NAV参数，作为数据传输时机的确定依据，以解决多链路通信过程中的数据传输冲突问题。
在一实施例中，更新模块设置为：
在所述NAV更新参数为0的情况下，将所述本地NAV参数作为更新后的本地NAV参数；
在所述NAV更新参数大于本地NAV参数的情况下，将所述NAV更新参数与所述NAV更新参数的传输时间对应的NAV值的差值作为更新后的本地NAV参数；
在所述NAV更新参数小于本地NAV参数的情况下，将所述本地NAV参数作为更新后的本地NAV参数。
在一实施例中，所述NAV更新参数依次通过所述AP MLD中与所述第一链路关联的接入点以及所述第一站点发送至所述第二站点。
在一实施例中，NAV更新参数通过确认回复帧获取，所述确认回复帧包括ACK帧或BA帧；或者，
所述NAV更新参数通过NAV控制帧获取，所述NAV控制帧在所述第一站点的PPDU传输完成后的第一帧间隔后获取，或者在确认回复帧传输完成后的第二帧间隔后获取。
在一实施例中，还包括：
广播接收模块，设置为接收多链路能力信息，其中，所述多链路能力信息包括以下至少之一：
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的NAV更新参数；
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路 的反馈NAV的操作参数。
在一实施例中，还包括：
第二关联模块，设置为发送关联请求，所述关联请求用于请求以下信息至少之一：
AP MLD中的每个接入点在所述Non-AP MLD中关联的站点；
AP MLD与所述Non-AP MLD之间的链路连接关系；
不支持同时收发的链路；
所述AP MLD对反馈NAV更新参数的支持能力；
所述Non-AP MLD中的站点对接收NAV更新参数的支持能力；
反馈NAV的操作参数。
在一实施例中，PPDU中包括前导码或MPDU帧头信息，所述前导码或MPDU帧头信息用于触发记录所述网络传输与状态更新信息。
在一实施例中，所述PPDU对应的MPDU中包括NAV策略指示信息，所述NAV策略指示信息用于指示以下至少之一：
不反馈NAV更新参数；
在NAV更新参数为0或非0的情况下反馈NAV更新参数；
在NAV更新参数大于0的情况下反馈NAV更新参数。
在一实施例中，所述NAV控制帧用于指示：携带的网络传输与状态更新信息的数量；NAV值；网络传输与状态更新信息对应的目标站点。
本实施例提出的参数更新装置与上述实施例提出的参数更新方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例。
本申请实施例还提供一种关联装置。所述关联装置包括：
广播模块，设置为广播多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈NAV更新参数的支持能力；
请求接收模块，设置为接收Non-AP MLD的关联请求，所述关联请求用于 确定AP MLD与所述Non-AP MLD之间的链路连接关系、链路对同时收发的支持能力以及所述Non-AP MLD中的站点对接收NAV更新参数的支持能力；
应答模块，设置为根据所述关联请求向所述Non-AP MLD发送关联应答信息。
本实施例的关联装置，通过广播多链路能力信息并应答Non-AP MLD的关联请求，建立NSTR的多链路连接，从而在第二链路处于盲区的期间可提供第一链路用于反馈NAV更新参数。未在本实施例中详尽描述的技术细节可参见上述任意实施例。
在一实施例中，所述关联装置还用于根据所述关联应答信息，执行上述实施例中应用于AP MLD的参数反馈方法。
本实施例提出的关联装置与上述实施例提出的应用于AP MLD的关联方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例。
本申请实施例还提供另一种关联装置。所述关联装置包括：
广播接收模块，设置为接收AP MLD广播的多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈NAV更新参数的支持能力；
请求模块，设置为根据所述多链路能力信息向所述AP MLD发送关联请求，所述关联请求用于确定AP MLD与所述Non-AP MLD之间的链路连接关系、链路对同时收发的支持能力以及所述Non-AP MLD中的站点对接收NAV更新参数的支持能力；
应答接收模块，设置为接收所述AP MLD的关联应答信息。
本实施例的关联装置，通过发送关联请求并接收AP MLD的关联应答信息，建立NSTR的多链路连接，从而在第二链路处于盲区的期间可通过第一链路接收反馈的NAV更新参数，据此更新本地NAV参数。
在一实施例中，该关联装置还用于根据所述关联应答信息，执行上述实施 例应用于Non-AP MLD的参数更新方法。
本实施例提出的关联装置与上述实施例提出的应用于Non-AP MLD参数更新方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例。
本申请实施例还提供了一种通信节点，图12为一实施例提供的一种通信节点的硬件结构示意图，如图12所示，本申请提供的通信节点，包括存储器52、处理器51以及存储在存储器上并可在处理器上运行的计算机程序，处理器51执行所述程序时实现上述的参数反馈方法、参数更新方法或关联方法。
通信节点还可以包括存储器52；该通信节点中的处理器51可以是一个或多个，图12中以一个处理器51为例；存储器52用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器51执行，使得所述一个或多个处理器51实现如本申请实施例中所述的参数反馈方法、参数更新方法或关联方法。
需要说明的是，在执行参数反馈方法或应用于AP MLD的关联方法的情况下，通信节点为AP MLD中的接入点；在执行参数更新方法或应用于Non-AP MLD的关联方法的情况下，通信节点为Non-AP MLD中的站点。
通信节点还包括：通信装置53、输入装置54和输出装置55。
通信节点中的处理器51、存储器52、通信装置53、输入装置54和输出装置55可以通过总线或其他方式连接，图12中以通过总线连接为例。
输入装置54可用于接收输入的数字或字符信息，以及产生与通信节点的用户设置以及功能控制有关的按键信号输入。输出装置55可包括显示屏等显示设备。
通信装置53可以包括接收器和发送器。通信装置53设置为根据处理器51的控制进行信息收发通信。
存储器52作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述参数反馈方法对应的程序指令/模块。 存储器52可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据通信节点的使用所创建的数据等。此外，存储器52可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器52可进一步包括相对于处理器51远程设置的存储器，这些远程存储器可以通过网络连接至通信节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
在本申请实施例中，还提供一种关联系统。图13为一实施例提供的一种通信系统的结构示意图。如图13所示，该系统包括接入点多链路设备610和非接入点多链路设备620；接入点多链路设备610和非接入点多链路设备620通过第一链路和第二链路相连，非接入点多链路设备的620的第一链路和第二链路不支持同时收发；接入点多链路设备610用于执行上述的参数反馈方法或如应用于AP MLD的关联方法；非接入点多链路设备620用于执行上述的参数更新方法或应用于非接入点多链路设备620的关联方法。需要说明的是，未在本实施例中详尽描述的技术细节可参见上述任意实施例。
本实施例中，在非接入点多链路设备620通过第一链路向接入点多链路设备610发送数据期间(即Non-AP MLD设备处于第二链路的盲区的期间)，接入点多链路设备610记录关于第二站点NAV的网络传输与状态更新信息并通过第一链路来反馈第二站点的NAV更新参数，非接入点多链路设备620通过第一链路来接收NAV更新参数，并据此更新本地NAV参数，作为数据传输时机的确定依据，以解决多链路通信过程中由于盲区导致的NAV丢失以及数据传输冲突问题。
在一实施例中，非接入点多链路设备620包括第一站点和第二站点；接入点多链路设备610包括记录第二链路的网络传输与状态更新信息的接入点和接收第一站点的PPDU的接入点，NAV更新参数由记录第二链路的网络传输与状 态更新信息的接入点，依次经过接收第一站点的PPDU的接入点、第一站点反馈至第二站点。
在一实施例中，接入点多链路设备610广播多链路能力；非接入点多链路设备620向接入点多链路设备610发送关联请求；接入点多链路设备610根据所述关联请求向非接入点多链路设备620发送关联应答信息。
在一实施例中，非接入点多链路设备620的关联请求用于确定AP MLD与所述非接入点多链路设备之间的链路连接关系、链路对同时收发的支持能力、所述AP MLD对反馈NAV更新参数的支持能力以及所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力。
在一实施例中，接入点多链路设备610根据所述网络传输与状态更新信息生成所述NAV更新参数。
在一实施例中，接入点多链路设备610将所述NAV更新参数设置为初始值，并根据以下至少之一更新所述NAV更新参数：
在通过所述第二链路所在BSS向第三站点发送CTS帧的情况下，根据所述CTS帧指示的时长信息更新所述NAV更新参数；
在通过所述第二链路所在BSS接收到第三站点的PPDU的情况下，根据所述第三站点的PPDU指示的时长信息更新所述NAV更新参数；
在获取所述第二链路所在BSS的传输机会并通过所述第二链路所在BSS向所述第三站点发送PPDU的情况下，根据所述传输机会的时长信息或向所述第三站点发送的PPDU指示的时长信息更新所述NAV更新参数。
在一实施例中，接入点多链路设备610在所述NAV更新参数为0或非0的情况下，通过所述第一链路向所述非接入点多链路设备反馈所述NAV更新参数；或者，在所述NAV更新参数大于0的情况下，通过所述第一链路向所述非接入点多链路设备反馈所述NAV更新参数。
在一实施例中，接入点多链路设备610将所述NAV更新参数依次通过所述AP MLD中与所述第一链路关联的接入点以及所述第一站点发送至所述第二站 点。
在一实施例中，所述NAV更新参数通过确认回复帧反馈，所述确认回复帧包括ACK帧或BA帧；或者，所述NAV更新参数通过NAV控制帧反馈，所述NAV控制帧在所述第一站点的PPDU传输完成后的第一帧间隔后反馈，或者在确认回复帧传输完成后的第二帧间隔后反馈。
在一实施例中，接入点多链路设备610还广播多链路能力信息，其中，多链路能力信息包括以下至少之一：
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的NAV更新参数；
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的反馈NAV的操作参数。
在一实施例中，接入点多链路设备610还接收关联请求并根据所述关联请求确定以下信息至少之一：
AP MLD中的每个接入点在所述非接入点多链路设备中关联的站点；
AP MLD与所述非接入点多链路设备之间的链路连接关系；
不支持同时收发的链路；
所述AP MLD对反馈NAV更新参数的支持能力；
所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力；
反馈NAV的操作参数。
在一实施例中，PPDU中包括前导码或MPDU帧头信息，所述前导码或MPDU帧头信息用于触发记录所述网络传输与状态更新信息。
在一实施例中，PPDU对应的MPDU中包括NAV策略指示信息，所述NAV策略指示信息用于指示以下至少之一：
不反馈NAV更新参数；
在NAV更新参数为0或非0的情况下反馈NAV更新参数；
在NAV更新参数大于0的情况下反馈NAV更新参数。
在一实施例中，所述NAV控制帧用于指示：携带的网络传输与状态更新信息的数量；NAV值；网络传输与状态更新信息对应的目标站点。
在一实施例中，非接入点多链路设备620在第一站点通过第一链路向AP MLD发送物理层PPDU结束的特定帧间隔后，通过所述第一链路获取关于所述非接入点多链路设备中的第二站点的NAV更新参数，其中，所述NAV更新参数根据第二链路所在的BSS中关于所述第二站点的NAV的网络传输与状态更新信息确定；
在获取到所述NAV更新参数的情况下，根据所述NAV更新参数更新本地NAV参数。
在一实施例中，非接入点多链路设备620在所述NAV更新参数为0的情况下，将所述本地NAV参数作为更新后的本地NAV参数；
在所述NAV更新参数大于本地NAV参数的情况下，将所述NAV更新参数与所述NAV更新参数的传输时间对应的NAV值的差值作为更新后的本地NAV参数；
在所述NAV更新参数小于本地NAV参数的情况下，将所述本地NAV参数作为更新后的本地NAV参数。
在一实施例中，非接入点多链路设备620还用于接收多链路能力信息，其中，所述多链路能力信息包括以下至少之一：
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的NAV更新参数；
AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的反馈NAV的操作参数。
在一实施例中，非接入点多链路设备620还用于发送关联请求，所述关联请求用于请求以下信息至少之一：
AP MLD中的每个接入点在所述非接入点多链路设备中关联的站点；
AP MLD与所述非接入点多链路设备之间的链路连接关系；
不支持同时收发的链路；
所述AP MLD对反馈NAV更新参数的支持能力；
所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力；
反馈NAV的操作参数。
本申请实施例还提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中任一所述的参数反馈方法、参数更新方法或关联方法。
该参数反馈方法，包括：在通过第一链路接收非接入点多链路设备中的第一站点发送的PPDU的期间，记录第二链路所在的BSS中关于所述非接入点多链路设备中的第二站点的NAV的网络传输与状态更新信息，其中，AP MLD与所述非接入点多链路设备通过所述第一链路和所述第二链路相连，所述非接入点多链路设备的第一链路和所述第二链路不支持同时收发；根据所述网络传输与状态更新信息确定关于所述第二站点的NAV更新参数的反馈状态，所述反馈状态包括反馈或不反馈；在所述反馈状态为反馈的情况下，在所述PPDU接收结束的特定帧间隔后，通过所述第一链路向所述非接入点多链路设备反馈所述NAV更新参数。
该参数更新方法，包括：在第一站点通过第一链路向AP MLD发送物理层PPDU结束的特定帧间隔后，通过所述第一链路获取关于所述非接入点多链路设备中的第二站点的NAV更新参数，其中，所述NAV更新参数根据第二链路所在的BSS中关于所述第二站点的NAV的网络传输与状态更新信息确定；在获取到所述NAV更新参数的情况下，根据所述NAV更新参数更新本地NAV参数。
该关联方法，包括：广播多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈NAV更新参数的支持能力；接收Non-AP MLD的关联请求，所述关联请求用于确定AP MLD与所述非接入点多链路设备之间的链路连接关系、链路对同时收发的支持能力以及所述非接入点多链路设备中的站点对接收NAV 更新参数的支持能力；根据所述关联请求向所述非接入点多链路设备发送关联应答信息。
或者，该关联方法，包括：接收AP MLD广播的多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈NAV更新参数的支持能力；根据所述多链路能力信息向所述AP MLD发送关联请求，所述关联请求用于确定AP MLD与所述非接入点多链路设备之间的链路连接关系、链路对同时收发的支持能力以及所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力；接收所述AP MLD的关联应答信息。
本申请实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的任意组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质例如可以是，但不限于：电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机存取存储器(Random Access Memory，RAM)、只读存储器(Read Only Memory，ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式CD-ROM、光存储器件、磁存储器件、或者上述的任意合适的组合。计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于：电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不 限于：无线、电线、光缆、无线电频率(Radio Frequency，RF)等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言或其组合来编写用于执行本申请操作的计算机程序代码，所述程序设计语言包括面向对象的程序设计语言，诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言，诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络，包括局域网(Local Area Network，LAN)或广域网(Wide Area Network，WAN)，连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相 互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FPGA)以及基于多核处理器架构的处理器。

Claims (27)

  1. 一种参数反馈方法，应用于接入点多链路设备AP MLD，包括：
    在通过第一链路接收非接入点多链路设备中的第一站点发送的物理层协议数据单元PPDU的期间，记录第二链路所在的基本服务集BSS中关于所述非接入点多链路设备中的第二站点的网络配置向量NAV的网络传输与状态更新信息，其中，AP MLD与所述非接入点多链路设备通过所述第一链路和所述第二链路相连，所述非接入点多链路设备的第一链路和所述第二链路不支持同时收发；
    根据所述网络传输与状态更新信息确定关于所述第二站点的NAV更新参数的反馈状态，所述反馈状态包括反馈或不反馈；
    在所述反馈状态为反馈的情况下，在所述PPDU接收结束的特定帧间隔后，通过所述第一链路向所述非接入点多链路设备反馈所述NAV更新参数。
  2. 根据权利要求1所述的方法，还包括：
    根据所述网络传输与状态更新信息生成所述NAV更新参数。
  3. 根据权利要求2所述的方法，其中，根据所述网络传输与状态更新信息生成所述NAV更新参数，包括：
    将所述NAV更新参数设置为初始值，并根据以下至少之一更新所述NAV更新参数：
    在通过所述第二链路所在BSS向第三站点发送准许发送CTS帧的情况下，根据所述CTS帧指示的时长信息更新所述NAV更新参数；
    在通过所述第二链路所在BSS接收到第三站点的PPDU的情况下，根据所述第三站点的PPDU指示的时长信息更新所述NAV更新参数；
    在获取所述第二链路所在BSS的传输机会并通过所述第二链路所在BSS向所述第三站点发送PPDU的情况下，根据所述传输机会的时长信息或向所述第三站点发送的PPDU指示的时长信息更新所述NAV更新参数。
  4. 根据权利要求1所述的方法，其中，通过所述第一链路向所述非接入点多链路设备反馈所述NAV更新参数，包括：
    在所述NAV更新参数为0或非0的情况下，通过所述第一链路向所述非接 入点多链路设备反馈所述NAV更新参数；或者，
    在所述NAV更新参数大于0的情况下，通过所述第一链路向所述非接入点多链路设备反馈所述NAV更新参数。
  5. 根据权利要求1所述的方法，其中，通过所述第一链路向所述非接入点多链路设备反馈所述NAV更新参数，包括：
    将所述NAV更新参数依次通过所述AP MLD中与所述第一链路关联的接入点以及所述第一站点发送至所述第二站点。
  6. 根据权利要求5所述的方法，其中，所述NAV更新参数通过确认回复帧反馈，所述确认回复帧包括确认ACK帧或块确认BA帧；或者，
    所述NAV更新参数通过NAV控制帧反馈，所述NAV控制帧在所述第一站点的PPDU传输完成后的第一帧间隔后反馈，或者在确认回复帧传输完成后的第二帧间隔后反馈。
  7. 根据权利要求1所述的方法，还包括：
    广播多链路能力信息，其中，所述多链路能力信息包括以下至少之一：
    AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的NAV更新参数；
    AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的反馈NAV的操作参数。
  8. 根据权利要求1所述的方法，还包括：
    接收关联请求并根据所述关联请求确定以下信息至少之一：
    AP MLD中的每个接入点在所述非接入点多链路设备中关联的站点；
    AP MLD与所述非接入点多链路设备之间的链路连接关系；
    不支持同时收发的链路；
    所述AP MLD对反馈NAV更新参数的支持能力；
    所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力；
    反馈NAV的操作参数。
  9. 根据权利要求1所述的方法，其中，所述PPDU中包括前导码或MAC层协议数据单元MPDU帧头信息，所述前导码或MPDU帧头信息用于触发记录所述网络传输与状态更新信息。
  10. 根据权利要求1所述的方法，其中，所述PPDU对应的MPDU中包括NAV策略指示信息，所述NAV策略指示信息用于指示以下至少之一：
    不反馈NAV更新参数；
    在NAV更新参数为0或非0的情况下反馈NAV更新参数；
    在NAV更新参数大于0的情况下反馈NAV更新参数。
  11. 根据权利要求6所述的方法，其中，所述NAV控制帧用于指示：携带的网络传输与状态更新信息的数量；NAV值；网络传输与状态更新信息对应的目标站点。
  12. 一种参数更新方法，应用于非接入点多链路设备，包括：
    在第一站点通过第一链路向接入点多链路设备AP MLD发送物理层协议数据单元PPDU结束的特定帧间隔后，通过所述第一链路获取关于所述非接入点多链路设备中的第二站点的NAV更新参数，其中，所述NAV更新参数根据第二链路所在的基本服务集BSS中关于所述第二站点的NAV的网络传输与状态更新信息确定；
    在获取到所述NAV更新参数的情况下，根据所述NAV更新参数更新本地NAV参数。
  13. 根据权利要求12所述的方法，其中，根据所述NAV更新参数更新本地NAV参数，包括：
    在所述NAV更新参数为0的情况下，将所述本地NAV参数作为更新后的本地NAV参数；
    在所述NAV更新参数大于本地NAV参数的情况下，将所述NAV更新参数与所述NAV更新参数的传输时间对应的NAV值的差值作为更新后的本地NAV参数；
    在所述NAV更新参数小于本地NAV参数的情况下，将所述本地NAV参数作为更新后的本地NAV参数。
  14. 根据权利要求12所述的方法，其中，所述NAV更新参数依次通过所述AP MLD中与所述第一链路关联的接入点以及所述第一站点发送至所述第二站点。
  15. 根据权利要求12所述的方法，其中，所述NAV更新参数通过确认回复帧获取，所述确认回复帧包括确认ACK帧或块确认BA帧；或者，
    所述NAV更新参数通过NAV控制帧获取，所述NAV控制帧在所述第一站点的PPDU传输完成后的第一帧间隔后获取，或者在确认回复帧传输完成后的第二帧间隔后获取。
  16. 根据权利要求12所述的方法，还包括：
    接收多链路能力信息，其中，所述多链路能力信息包括以下至少之一：
    AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的NAV更新参数；
    AP MLD中的至少一个接入点支持或不支持携带所在链路以外的其他链路的反馈NAV的操作参数。
  17. 根据权利要求12所述的方法，还包括：
    发送关联请求，所述关联请求用于请求以下信息至少之一：
    AP MLD中的每个接入点在所述非接入点多链路设备中关联的站点；
    AP MLD与所述非接入点多链路设备之间的链路连接关系；
    不支持同时收发的链路；
    所述AP MLD对反馈NAV更新参数的支持能力；
    所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力；
    反馈NAV的操作参数。
  18. 根据权利要求12所述的方法，其中，所述PPDU中包括前导码或MAC层协议数据单元MPDU帧头信息，所述前导码或MPDU帧头信息用于触发记录 所述网络传输与状态更新信息。
  19. 根据权利要求12所述的方法，其中，所述PPDU对应的MPDU中包括NAV策略指示信息，所述NAV策略指示信息用于指示以下至少之一：
    不反馈NAV更新参数；
    在NAV更新参数为0或非0的情况下反馈NAV更新参数；
    在NAV更新参数大于0的情况下反馈NAV更新参数。
  20. 根据权利要求15所述的方法，其中，所述NAV控制帧用于指示：携带的网络传输与状态更新信息的数量；NAV值；网络传输与状态更新信息对应的目标站点。
  21. 一种关联方法，应用于接入点多链路设备AP MLD，包括：
    广播多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈网络配置向量NAV更新参数的支持能力；
    接收非接入点多链路设备的关联请求，所述关联请求用于确定AP MLD与所述非接入点多链路设备之间的链路连接关系、链路对同时收发的支持能力以及所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力；
    根据所述关联请求向所述非接入点多链路设备发送关联应答信息。
  22. 根据权利要求21所述的方法，还包括：
    根据所述关联应答信息，执行如权利要求1-11中任一项所述的参数反馈方法。
  23. 一种关联方法，应用于非接入点多链路设备，包括：
    接收接入点多链路设备AP MLD广播的多链路能力信息，所述广播多链路能力信息包括AP MLD对反馈NAV更新参数的支持能力；
    根据所述多链路能力信息向所述AP MLD发送关联请求，所述关联请求用于确定AP MLD与所述非接入点多链路设备之间的链路连接关系、链路对同时收发的支持能力以及所述非接入点多链路设备中的站点对接收NAV更新参数的支持能力；
    接收所述AP MLD的关联应答信息。
  24. 根据权利要求23所述的方法，还包括：
    根据所述关联应答信息，执行如权利要求12-20中任一项所述的参数更新方法。
  25. 一种通信节点，包括存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现如权利要求1-11中任一项所述的参数反馈方法或如权利要求12-20中任一项所述的参数更新方法或如权利要求21-22中任一项所述的关联方法或如权利要求23-24中任一项所述的关联方法。
  26. 一种通信系统，包括接入点多链路设备和非接入点多链路设备；
    所述接入点多链路设备用于执行如权利要求1-11中任一项所述的参数反馈方法或如权利要求21-22中任一项所述的关联方法；
    所述非接入点多链路设备用于执行如权利要求12-20中任一项所述的参数更新方法或如权利要求23-24中任一项所述的关联方法。
  27. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-11中任一项所述的参数反馈方法或如权利要求12-20中任一项所述的参数更新方法或如权利要求21-22中任一项所述的关联方法或如权利要求23-24中任一项所述的关联方法。
PCT/CN2021/118277 2020-12-22 2021-09-14 参数反馈、更新、关联方法、通信节点、通信系统及介质 WO2022134667A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020237011711A KR20230065301A (ko) 2020-12-22 2021-09-14 파라미터 피드백 방법, 업데이트 방법, 연관 방법, 통신 노드, 통신 시스템 및 매체
US18/246,591 US20230371076A1 (en) 2020-12-22 2021-09-14 Parameter feedback method, parameter update method, association method, communication node, communication system, and medium
JP2023522471A JP2023546847A (ja) 2020-12-22 2021-09-14 パラメータフィードバック、更新、関連方法、通信ノード、通信システムおよび媒体
EP21908669.1A EP4207937A1 (en) 2020-12-22 2021-09-14 Parameter feedback method, parameter update method, association method, communication node, communication system, and medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011529861.0A CN112714472A (zh) 2020-12-22 2020-12-22 参数反馈、更新、关联方法、通信节点、通信系统及介质
CN202011529861.0 2020-12-22

Publications (1)

Publication Number Publication Date
WO2022134667A1 true WO2022134667A1 (zh) 2022-06-30

Family

ID=75545217

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/118277 WO2022134667A1 (zh) 2020-12-22 2021-09-14 参数反馈、更新、关联方法、通信节点、通信系统及介质

Country Status (6)

Country Link
US (1) US20230371076A1 (zh)
EP (1) EP4207937A1 (zh)
JP (1) JP2023546847A (zh)
KR (1) KR20230065301A (zh)
CN (1) CN112714472A (zh)
WO (1) WO2022134667A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112714472A (zh) * 2020-12-22 2021-04-27 中兴通讯股份有限公司 参数反馈、更新、关联方法、通信节点、通信系统及介质
CN116506928B (zh) * 2021-05-26 2024-01-30 华为技术有限公司 通信方法及装置
CN115474209A (zh) * 2021-06-11 2022-12-13 华为技术有限公司 一种反馈方法及装置
CN115812337A (zh) * 2021-07-13 2023-03-17 北京小米移动软件有限公司 通信方法和通信装置
WO2023010455A1 (zh) * 2021-08-05 2023-02-09 Oppo广东移动通信有限公司 无线通信的方法及设备
CN115776683A (zh) * 2021-09-08 2023-03-10 华为技术有限公司 介质同步时延计时器设置方法及相关装置
WO2023060584A1 (zh) * 2021-10-15 2023-04-20 北京小米移动软件有限公司 网络分配矢量nav定时器的处理方法及相关装置
WO2023092411A1 (en) * 2021-11-25 2023-06-01 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Wireless communication methods and apparatuses
CN114126001B (zh) * 2022-01-25 2022-04-19 成都极米科技股份有限公司 传输软接入设备系统参数的方法、装置、设备和介质
AU2023203520B2 (en) 2022-04-24 2024-02-08 Huawei Technologies Co., Ltd. Multi-link communication setup method and related apparatus

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106941731A (zh) * 2016-01-04 2017-07-11 华为技术有限公司 无线通信系统中nav设置方法及相关设备
US20180317166A1 (en) * 2015-07-01 2018-11-01 Intel IP Corporation Determining two network allocation vector settings
CN110351323A (zh) * 2018-04-08 2019-10-18 北京京东尚科信息技术有限公司 一种应用系统的参数管理方法和装置
CN110574441A (zh) * 2017-04-14 2019-12-13 韦勒斯标准与技术协会公司 使用bss标识符的无线通信方法和使用该方法的无线通信终端
CN112714472A (zh) * 2020-12-22 2021-04-27 中兴通讯股份有限公司 参数反馈、更新、关联方法、通信节点、通信系统及介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180317166A1 (en) * 2015-07-01 2018-11-01 Intel IP Corporation Determining two network allocation vector settings
CN106941731A (zh) * 2016-01-04 2017-07-11 华为技术有限公司 无线通信系统中nav设置方法及相关设备
CN110574441A (zh) * 2017-04-14 2019-12-13 韦勒斯标准与技术协会公司 使用bss标识符的无线通信方法和使用该方法的无线通信终端
CN110351323A (zh) * 2018-04-08 2019-10-18 北京京东尚科信息技术有限公司 一种应用系统的参数管理方法和装置
CN112714472A (zh) * 2020-12-22 2021-04-27 中兴通讯股份有限公司 参数反馈、更新、关联方法、通信节点、通信系统及介质

Also Published As

Publication number Publication date
JP2023546847A (ja) 2023-11-08
CN112714472A (zh) 2021-04-27
EP4207937A1 (en) 2023-07-05
KR20230065301A (ko) 2023-05-11
US20230371076A1 (en) 2023-11-16

Similar Documents

Publication Publication Date Title
WO2022134667A1 (zh) 参数反馈、更新、关联方法、通信节点、通信系统及介质
US10826575B2 (en) Methods for transmitting a frame in a multi-user based wireless communication system
WO2021004382A1 (zh) 一种多链路通信方法及相关设备
US20220132611A1 (en) Multi-link communications of a wireless network
JP6392338B2 (ja) ワイヤレスネットワークにおいて応答インジケーション延期を動的に設定するためのシステム、方法、及びデバイス
JP6387132B2 (ja) 同時送受信ネットワークモードのための装置および方法
JP5607173B2 (ja) 無線通信装置のグループと同時に通信するための装置、システム及び方法
US20120207074A1 (en) Transmitting multiple group-addressed frames in a wireless network
JP2018526857A (ja) アソシエーション確立方法および装置
WO2021244090A1 (zh) 数据发送方法及装置、数据接收方法及装置
WO2020048369A1 (zh) 全双工数据传输方法和装置
WO2021008401A1 (zh) 通信方法、装置、计算机可读介质及电子设备
WO2016188245A1 (zh) 信道协商方法、站点及系统
WO2021047564A1 (zh) 一种数据发送和接收方法、装置和存储介质
WO2018014649A1 (zh) 一种组播数据传输的应答方法及装置、计算机存储介质
WO2021047468A1 (zh) 传输方法、装置及计算机可读存储介质
US9332536B1 (en) Method and apparatus for managing communication on a wireless channel
WO2022048583A1 (zh) 资源确定方法及装置、资源配置方法及装置、通信节点、存储介质
WO2021169836A1 (zh) 数据传输方法、装置和存储介质
WO2024067687A1 (zh) 信息传输方法、第一通信节点、第二通信节点及存储介质
WO2023088038A1 (zh) 侧行链路通信方法及相关装置
US20240031456A1 (en) Bluetooth message transmission method and apparatus, and bluetooth network
WO2023024106A1 (zh) 回复控制方法、装置、设备及存储介质
WO2023231707A1 (zh) 一种用于感知的方法和装置
WO2021248402A1 (zh) 终端连接方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21908669

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021908669

Country of ref document: EP

Effective date: 20230330

ENP Entry into the national phase

Ref document number: 20237011711

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2023522471

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE