[go: up one dir, main page]

WO2025160822A1 - 数据传输方法、通信设备及通信系统 - Google Patents

数据传输方法、通信设备及通信系统

Info

Publication number
WO2025160822A1
WO2025160822A1 PCT/CN2024/075017 CN2024075017W WO2025160822A1 WO 2025160822 A1 WO2025160822 A1 WO 2025160822A1 CN 2024075017 W CN2024075017 W CN 2024075017W WO 2025160822 A1 WO2025160822 A1 WO 2025160822A1
Authority
WO
WIPO (PCT)
Prior art keywords
channel
data frame
frame
obss
qos
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/CN2024/075017
Other languages
English (en)
French (fr)
Inventor
董贤东
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaomi Mobile Software Co Ltd
Original Assignee
Beijing Xiaomi Mobile Software Co Ltd
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 Beijing Xiaomi Mobile Software Co Ltd filed Critical Beijing Xiaomi Mobile Software Co Ltd
Priority to CN202480000325.1A priority Critical patent/CN120731568A/zh
Priority to PCT/CN2024/075017 priority patent/WO2025160822A1/zh
Publication of WO2025160822A1 publication Critical patent/WO2025160822A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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
    • H04L1/1607—Details of the supervisory signal

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a data transmission method, communication equipment, and communication system.
  • UHR ultra-high reliability
  • SNR signal-to-noise ratio
  • the embodiments of the present disclosure provide a data transmission method, a communication device, and a communication system to further improve the mechanism for a device to transmit data in a primary channel and a secondary channel.
  • an embodiment of the present disclosure provides a data transmission method, the method comprising:
  • the first device transmits data on the primary channel;
  • the first device After the OBSS TXOP time ends, the first device performs channel state sensing or listening;
  • the quality of service QoS data frames that were not successfully transmitted within the OBSS TXOP time are retransmitted.
  • an embodiment of the present disclosure further provides a communication device, wherein the communication device is a first device, the first device is a site device or an access point device, and the first device includes:
  • a first processing module is configured to transmit data on a primary channel within an OBSS TXOP time sensed by a primary channel;
  • a second processing module is configured to sense or monitor the channel status after the OBSS TXOP time ends;
  • the third processing module is used to retransmit the quality of service QoS data frame that was not successfully transmitted within the OBSS TXOP time according to the perceived channel status.
  • an embodiment of the present disclosure further provides a communication device, wherein the communication device is a first device, and the first device is a site device or an access point device, including:
  • processors one or more processors
  • the first device is used to execute the data transmission method described in the embodiment of the present disclosure.
  • An embodiment of the present disclosure further provides a communication system, including a first device, which is a site device or an access point device; wherein the first device is configured to implement the data transmission method described in the embodiment of the present disclosure.
  • the embodiment of the present disclosure further provides a storage medium storing instructions.
  • the instructions When the instructions are executed on a communication device, the communication device executes the data transmission method as described in the embodiment of the present disclosure.
  • the first device transmits data on the primary channel; after the OBSS TXOP time ends, the first device senses or listens to the channel status; and based on the sensed channel status, the quality of service QoS data frames that have not been successfully transmitted within the OBSS TXOP time are retransmitted, thereby improving the device's mechanism for retransmitting data that has not been successfully transmitted on the secondary channel, improving system throughput, reducing communication delay, and meeting UHR requirements.
  • FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure
  • FIG2 is one of exemplary interaction diagrams of a method provided according to an embodiment of the present disclosure.
  • FIG3 is a second exemplary interaction diagram of a method provided according to an embodiment of the present disclosure.
  • FIG4 is a third exemplary interaction diagram of a method provided according to an embodiment of the present disclosure.
  • FIG5 is a schematic diagram of a channel transmission method according to an embodiment of the present disclosure.
  • FIG6 is a second schematic diagram of channel transmission of the data transmission method provided in an embodiment of the present disclosure.
  • FIG7 is a flow chart of a data transmission method according to an embodiment of the present disclosure.
  • FIG8 is a schematic structural diagram of a first device proposed in an embodiment of the present disclosure.
  • FIG9 is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure.
  • FIG10 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure.
  • the embodiments of the present disclosure provide a data transmission method, a communication device, and a communication system.
  • an embodiment of the present disclosure provides a data transmission method, the method comprising:
  • the first device transmits data on the primary channel;
  • the first device After the OBSS TXOP time ends, the first device performs channel state sensing or listening;
  • the quality of service QoS data frames that were not successfully transmitted within the OBSS TXOP time are retransmitted.
  • the mechanism for the device to retransmit data that has not been successfully transmitted in the secondary channel is improved, thereby increasing the system throughput, reducing the communication delay, and meeting the UHR requirements.
  • the method includes:
  • the first device senses that the primary channel is busy and switches to the first channel to transmit a first data frame; wherein the first data frame includes a sequence number and a transmission identifier TID;
  • the sequence number (SNS) is used to identify the order of the first data frame during transmission, allowing the receiver of the first data frame to confirm and receive the first data frame in sequence.
  • the traffic identifier (TID) is used to identify each quality of service (QoS) data frame in the first data frame. In this way, the receiver of the first data frame can determine the successfully received QoS data frame based on the SNS and TID of the first data frame.
  • the first device receives a block acknowledgment (BA) frame fed back by the receiving end of the first data frame received on the first channel; wherein the BA frame includes a bitmap identification bit, which identifies whether each QoS data frame of the first data frame is correctly received.
  • BA block acknowledgment
  • a BA frame is a frame sent by the receiving end to the transmitting end to confirm the successful transmission of a series of frames.
  • the receiving end of the first data frame sends a BA frame to the first device to feedback the successfully received QoS data frames.
  • the receiving end of the first data frame uses the bitmap flag in the BA frame to indicate whether each QoS data frame in the first data frame was correctly received.
  • retransmitting the QoS data frame that was not successfully transmitted within the OBSS TXOP time according to the sensed channel state includes:
  • the first device senses that the channel state of the primary channel is idle, and retransmits the QoS data frame that was not successfully transmitted on the primary channel;
  • the retry bit of the media access control MAC frame header of the unsuccessfully transmitted QoS data frame is set to the first parameter value, and the serial number SN setting value of the unsuccessfully transmitted QoS data frame is the same as the setting value in the first channel.
  • the QoS data frames that were not successfully transmitted are retransmitted.
  • This mechanism can avoid retransmission when the channel is busy, increasing the probability of successful retransmission.
  • the retry bit in the MAC frame header of the unsuccessfully transmitted QoS data frame is set to the first parameter value, and the sequence number SN setting value remains the same as the setting value for the first transmission. This setting helps the device and network work better together and ensures that the retransmitted data frames are correctly processed.
  • retransmitting the unsuccessfully transmitted QoS data frame on the primary channel includes:
  • the main channel is in the OBSS TXOP busy state, switching to the first channel or the second channel for transmission; the second channel is pre-negotiated between the first device and the receiving end of the first data frame.
  • the device can make intelligent decisions based on the real-time channel conditions. If the primary channel is busy, switching to another pre-negotiated channel helps avoid channel conflicts and improve the success rate of data transmission.
  • the switching to the first channel or the second channel transmission includes:
  • the retry bit of the MAC frame header of the unsuccessfully transmitted QoS data frame is set to the first parameter value, and the SN setting value of the unsuccessfully transmitted QoS data frame is the same as the setting value in the first channel.
  • the device can intelligently select an idle backup channel to minimize channel conflicts and maximize data transmission success rates. Furthermore, by setting the retry bit and sequence number (SN) in the MAC header of unsuccessfully transmitted QoS data frames to the same as those used for the primary channel, consistency of transmission parameters is ensured during retransmissions. This is crucial for the receiver to correctly receive and process data frames.
  • SN retry bit and sequence number
  • retransmitting the QoS data frame that is not successfully transmitted within the OBSS TXOP time includes:
  • the receiving end that receives the first data frame sends a clear-to-send CTS frame to retransmit the QoS data frame that was not successfully transmitted.
  • the use of the RTS/CTS mechanism can help avoid collisions and conflicts, improve network stability, and reduce the probability of possible collisions by notifying the receiving end in advance of the upcoming data transmission.
  • an embodiment of the present disclosure further provides a communication device, wherein the communication device is a first device, the first device is a site device or an access point device, and the above-mentioned first device includes at least one of a first processing module, a second processing module, and a third processing module; wherein the above-mentioned first device is used to execute an optional implementation method of the first aspect.
  • an embodiment of the present disclosure further provides a communication device, wherein the communication device is a first device, including:
  • processors one or more processors
  • the first device is used to execute an optional implementation of the first aspect.
  • an embodiment of the present disclosure further provides a communication system, including a first device, which is a site device or an access point device; wherein the first device is configured to execute the optional implementation method described in the first aspect.
  • an embodiment of the present disclosure further provides a storage medium storing instructions, which, when executed on a communication device, enables the communication device to execute the optional implementation method described in the first aspect.
  • an embodiment of the present disclosure proposes a program product.
  • the program product is executed by a communication device
  • the communication device executes the method described in the optional implementation manner of the first aspect.
  • an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation manner of the first aspect.
  • an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.
  • the first device, communication system, storage medium, program product, computer program, chip, or chip system described above are all used to perform the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.
  • the embodiments of the present disclosure provide a data transmission method, a communication device, and a communication system.
  • the terms data transmission method, signal transmission method, wireless frame transmission method, etc. can be used interchangeably, and the terms information processing system, communication system, etc. can be used interchangeably.
  • each step in an embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined.
  • a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged.
  • the optional implementation methods in a certain embodiment can be arbitrarily combined.
  • the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
  • plurality refers to two or more.
  • the terms "at least one of”, “one or more”, “a plurality of”, “multiple”, etc. can be used interchangeably.
  • descriptions such as “at least one of A and B,” “A and/or B,” “A in one case, B in another case,” or “in response to one case A, in response to another case B” may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.
  • a or B and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.
  • prefixes such as “first” and “second” in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects.
  • the description object please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes.
  • the description object is a "field”
  • the ordinal number before the "field” in the "first field” and the "second field” does not limit the position or order between the "fields”.
  • “First” and “second” do not limit whether the "fields” they modify are in the same message, nor do they limit the order of the "first field” and the "second field”.
  • the description object is a "level”
  • the ordinal number before the "level” in the “first level” and the “second level” does not limit the priority between the "levels”.
  • the number of description objects is not limited by the ordinal number and can be one or more. Taking “first device” as an example, the number of "devices" can be one or more.
  • the objects modified by different prefixes can be the same or different.
  • the description object is "device”
  • the "first device” and the “second device” can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information”, then the "first information” and the “second information” can be the same information or different information, and their contents can be the same or different.
  • “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
  • terms such as “in response to", “in response to determining", “in the case of", “at the time of", “when!, “if", “if", etc. can be used interchangeably.
  • terms such as “greater than”, “greater than or equal to”, “not less than”, “more than”, “more than or equal to”, “not less than”, “higher than”, “higher than or equal to”, “not less than”, and “above” can be replaced with each other, and terms such as “less than”, “less than or equal to”, “not greater than”, “less than”, “less than or equal to”, “not more than”, “lower than”, “lower than or equal to”, “not higher than”, and “below” can be replaced with each other.
  • devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as “equipment”, “device”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, “subject”, etc.
  • obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
  • data, information, etc. may be obtained with the user's consent.
  • each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.
  • FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.
  • a communication system 100 includes a first device 101 and a second device 102.
  • the first device can be a station (STA) or an access point (AP); the second device can be a STA or an AP.
  • STA station
  • AP access point
  • the second device can be a STA or an AP.
  • the first device 101 is a STA
  • the second device 102 is an AP
  • the first device 101 is an AP
  • the second device 102 is a STA.
  • the first device 101 and the second device 102 include, for example, wireless communication chips, wireless sensors, or wireless communication terminals that support WiFi communication functions.
  • the wireless communication terminals include, for example, mobile phones, wearable devices, IoT devices that support WiFi communication functions, cars with WiFi communication functions, smart cars, tablet computers, computers with wireless transceiver functions, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in self-driving, At least one of wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, and wireless terminal devices in smart homes, but not limited thereto.
  • the first device 101 and the second device 102 may be terminal devices or network devices with wireless fidelity (WiFi) chips.
  • the first device 101 may support multiple WLAN standards such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11a, 802.11bf, and 802.11bn, as well as support the next generation 802.11 protocol, but is not limited thereto.
  • the first device 101 and the second device 102 can be access points for mobile terminals to enter a wired network.
  • the AP is equivalent to a bridge connecting a wired network and a wireless network. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet.
  • the AP can be a terminal device or a network device with a wireless fidelity chip.
  • the AP can support multiple WLAN standards such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a, 802.11bf, 802.11bn, and support the next generation 802.11 protocol, but is not limited to this.
  • the AP and STA may be devices supporting multiple connections, for example, they may be represented as a multi-connection access point device (Access Point Multi-Link Device, AP MLD) and a multi-connection site device (Non-Access Point Multi-Link Device, Non-AP MLD), respectively;
  • AP MLD may represent an access point supporting multi-connection communication functions, and non-AP MLD may represent a site supporting multi-connection communication functions.
  • the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure.
  • Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.
  • the following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto.
  • the entities shown in FIG1 are illustrative only.
  • the communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 .
  • the number and form of the entities are arbitrary, and the entities may be physical or virtual.
  • the connection relationships between the entities are illustrative only.
  • the entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.
  • a basic service set (BSS) is a fundamental component of a WLAN.
  • a BSS network consists of station devices with some association within a specific coverage area.
  • IBSS independent basic service set
  • Another more common scenario is that in a BSS network, there is only one central station dedicated to managing the BSS, called an access point device, and all other STAs in the network are associated with it.
  • Other stations in the BSS network that are not central stations are called terminals, also called non-AP STAs.
  • STAs Terminals and non-AP STAs are collectively referred to as STAs.
  • STAs When describing STAs, there is no need to distinguish between APs and non-AP STAs. In the same BSS network, due to distance, transmission power, etc., a STA cannot detect other STAs that are farther away from it, and the two are each other's hidden nodes.
  • FIG2 is an interactive diagram of a data transmission method according to an embodiment of the present disclosure. As shown in FIG2 , the method includes:
  • Step 201 During the OBSS TXOP time sensed by the primary channel, the first device 101 transmits data on the primary channel.
  • channels are typically divided into primary channels and secondary channels (also known as auxiliary channels or non-primary channels).
  • the primary channel represents the main communication channel of the BSS to which the current device is connected.
  • a secondary channel can contain one or more sub-channels. For example, if the basic bandwidth unit is 20 MHz, when the channel bandwidth is 20 MHz, there is only one primary channel with a bandwidth of 20 MHz. When the channel bandwidth is greater than 20 MHz, one channel with a bandwidth of 20 MHz is the primary channel, and the remaining one or more 20 MHz channels are secondary channels.
  • the primary 20 MHz channel is the common channel of operation for stations that are members of the basic service set (BSS). Stations in the BSS can compete for channels on the primary 20 MHz channel to seize channel resources.
  • BSS basic service set
  • the primary channel is, for example, the primary 20 MHz channel in FIG5 ; wherein the secondary channel may include one or more sub-channels, for example, the 20 MHz secondary channel and the 40 MHz secondary channel in FIG5 .
  • An Overlapping Basic Service Set consists of two or more BSSs with overlapping coverage areas.
  • OBSS interference OBSS busy state
  • T1 and T2 Time periods
  • PPDUs Physical Layer Protocol Data Units
  • the primary channel is in an OBSS busy state.
  • OBSS busy state to fully utilize channel resources, communication can be switched to a secondary channel to improve communication system throughput and maximize channel resource utilization. For example, communication can be switched to a 20 MHz secondary channel during time period T1, or to a 40 MHz secondary channel during time period T2.
  • the AP and STA can send PPDUs to each other.
  • the primary and secondary channels can be aggregated for communication to improve the system throughput; as an example, as shown in Figure 6, during the transmission of each frame, the primary channel and at least one secondary channel can be aggregated for transmission.
  • a Transmission Opportunity indicates a period of time on the primary channel during which a device is authorized to continuously transmit data.
  • An OBSS TXOP indicates a device's opportunity to transmit on the primary channel within the OBSS. Therefore, when the primary channel is busy, to fully utilize channel resources, the device can switch to a secondary channel for communication and transmit data within the OBSS TXOP duration perceived by the primary channel. In other words, the communication duration on the secondary channel equals the OBSS TXOP duration perceived by the primary channel.
  • Step 202 After the OBSS TXOP time ends, the first device 101 performs channel status perception or listening.
  • the first device After the OBSS TXOP period ends, the first device (AP or STA) completes data exchange on the secondary channel and then switches to the primary channel for communication. After switching to the primary channel, the first device needs to sense (or listen) whether there is other data being transmitted on the primary channel before sending data, for example, through a carrier sense mechanism.
  • the first device performs channel sensing or listening after a medium synchronization delay. That is, the first device waits for a period of time after switching to the primary channel to ensure that there is no activity on the primary channel from other devices, to prevent interference caused by multiple devices listening on the same channel at the same time.
  • Step 203 Retransmit the QoS data frames that are not successfully transmitted within the OBSS TXOP time based on the perceived channel status.
  • QoS data frames are used to provide differentiated quality of service for different service flows, including but not limited to voice, video, and real-time application data.
  • the first device retransmits QoS data frames that were not successfully transmitted within the OBSS TXOP time based on the perceived channel status.
  • the embodiment of the present disclosure improves the data transmission mechanism of the device in the primary and secondary channels.
  • the first device senses that the primary channel is busy, it switches to the primary channel to transmit the first data frame, receives the BA frame fed back by the receiving end of the first data frame on the first channel, and determines the QoS data frame that was not successfully received in the first data frame through the bitmap identification bit of the BA frame.
  • the OBSS TXOP time ends, it switches to the primary channel for perception or listening, and retransmits the QoS data frame that was not successfully transmitted within the OBSS TXOP time according to the perceived channel status, so that the first device can quickly access the channel for transmission, thereby reducing the delay and meeting the UHR requirements.
  • the first device senses that the primary channel is busy and switches to the first channel to transmit a first data frame; wherein the first data frame includes a sequence number and a transmission identifier TID;
  • the sequence number space (SNS) is used to identify the order of the first data frame during transmission, allowing the receiver of the first data frame to confirm and receive the first data frame in sequence.
  • the traffic identifier (TID) is used to identify each quality of service (QoS) data frame in the first data frame. In this way, the receiver of the first data frame can determine which QoS data frame has been successfully received based on the SNS and TID of the first data frame.
  • the first device receives a block acknowledgment (BA) frame fed back by a receiving end of the first data frame received on the first channel; wherein the BA frame includes a bitmap identification bit, which identifies whether each QoS data frame of the first data frame is correctly received.
  • BA block acknowledgment
  • a BA frame is a frame sent by the receiving end to the transmitting end to confirm the successful transmission of a series of frames.
  • the receiving end of the first data frame sends a BA frame to the first device to feedback the successfully received QoS data frames.
  • the receiving end of the first data frame uses the bitmap flag in the BA frame to indicate whether each QoS data frame in the first data frame was correctly received.
  • FIG3 shows an optional implementation of the embodiment of the present disclosure, including the following steps:
  • Step 301 The first device 101 senses that the primary channel is busy and switches to the primary channel to transmit a first data frame; wherein the first data frame includes a sequence number and a TID.
  • the first device After the first device detects that the primary channel is busy, it switches to the primary channel to transmit the first data frame.
  • the first data frame includes a sequence number (SN) for identifying the order of the first data frame during transmission, and a TID for identifying each QoS data frame in the first data frame. In this way, the receiver of the first data frame can determine the successfully received QoS data frame based on the SN and TID of the first data frame.
  • Step 302 The BA frame fed back by the receiving end 102 of the first data frame is received on the first channel; wherein the BA frame includes a bitmap identification bit to identify whether each QoS data frame of the first data frame is correctly received.
  • the first device receives a BA frame fed back by a receiving end of the first data frame on the first channel; wherein the BA frame includes a bitmap identification bit, which identifies whether each QoS data frame of the first data frame is correctly received.
  • a BA frame is a frame sent by the receiving end to the transmitting end to confirm the successful transmission of a series of frames.
  • the receiving end of the first data frame sends a BA frame to the first device to feedback the successfully received QoS data frames.
  • the receiving end of the first data frame uses the bitmap flag in the BA frame to indicate whether each QoS data frame in the first data frame was correctly received.
  • Step 303 During the OBSS TXOP time sensed by the primary channel, the first device 101 transmits data on the secondary channel.
  • the first device when the primary channel is in the OBSS busy state, in order to make full use of channel resources, the first device may switch to the secondary channel communication and perform data transmission within the OBSS TXOP time perceived by the primary channel, thereby improving the system throughput.
  • Step 304 After the OBSS TXOP time ends, the first device 101 performs channel status perception or listening.
  • the first device After the OBSS TXOP period ends, the first device (AP or STA) completes data exchange on the secondary channel and switches to the primary channel. After switching to the primary channel, the first device needs to listen to see if there is other data being transmitted on the primary channel before sending data, for example, through a carrier sense mechanism. The first device performs channel sensing or listening after a synchronization delay. That is, the first device waits for a period of time after switching to the primary channel to ensure that there is no activity on the primary channel from other devices, preventing interference caused by multiple devices listening on the same channel at the same time.
  • Step 305 The first device 101 senses that the channel state of the primary channel is idle, and retransmits the unsuccessfully transmitted QoS data frame on the primary channel;
  • the duration of communication on the first channel by the first device is limited to the OBSS TXOP duration, it may not be possible to fully transmit all QoS data frames that require retransmission within the OBSS TXOP duration, resulting in some QoS data frames not being retransmitted on the first channel.
  • the retry bit of the Media Access Control (MAC) frame header of the QoS data frame that was not successfully transmitted is set to the first parameter value, and the SN setting value of the QoS data frame that was not successfully transmitted is the same as the setting value in the first channel.
  • MAC Media Access Control
  • the first device completes data exchange on the secondary channel and switches to the primary channel for channel sensing or listening. If the first device senses that the channel state of the primary channel is idle, the first device retransmits the unsuccessfully transmitted QoS data frame on the primary channel, and the retry bit of the unsuccessfully transmitted QoS data frame is set to a first parameter value. For example, when the retry bit is set to "1", the QoS data frame is identified as a retransmitted frame; when the retry bit is set to "0", the QoS data frame is identified as not a retransmitted frame.
  • the SN value of the unsuccessfully transmitted QoS data frame is set to the same value as the SN value set in the first channel. This helps the receiver to correctly place the retransmitted frames in the correct order and avoid out-of-order transmission. In addition, maintaining the same SN value can also simplify the retransmission mechanism and reduce the complexity of the processing logic.
  • the first device if the first device senses that the main channel is in an OBSS TXOP busy state, it switches to the first channel or the second channel for transmission; the second channel is pre-negotiated between the first device and the receiver of the first data frame.
  • the primary channel When the primary channel is in the OBSS TXOP busy state, it indicates that other BSS devices are using the primary channel for communication, making it unsuitable to retransmit unsuccessfully transmitted QoS data frames on the primary channel. Therefore, when the primary channel is in the OBSS TXOP busy state, the first device can choose to switch to the primary channel for retransmission or to switch to other secondary channels pre-negotiated with the receiving end for retransmission. For example, the first device and the receiving end can negotiate multiple secondary channels through specific management frames during the initialization phase or the association phase. Management frames include, but are not limited to, Association Request frames and Association Response frames.
  • the switching to the first channel or the second channel transmission includes:
  • the retry bit of the MAC frame header of the unsuccessfully transmitted QoS data frame is set to the first parameter value, and the SN setting value of the unsuccessfully transmitted QoS data frame is the same as the setting value in the first channel.
  • the QoS data frame that was not successfully transmitted is retransmitted on the first channel, and the retry bit of the QoS data frame that was not successfully transmitted is set to the first parameter value. For example, when the retry bit is set to "1", the QoS data frame is identified as a retransmission frame; when the retry bit is set to "0", the QoS data frame is not identified as a retransmission frame.
  • the SN setting value of the QoS data frame that was not successfully transmitted is the same as its SN setting value in the first channel.
  • the QoS data frame that was not successfully transmitted is retransmitted on the second channel, and the retry bit of the QoS data frame that was not successfully transmitted is set to the first parameter value. For example, when the retry bit is set to "1", the QoS data frame is identified as a retransmission frame; when the retry bit is set to "0", the QoS data frame is identified as not a retransmission frame.
  • the SN setting value of the QoS data frame that was not successfully transmitted is the same as its SN setting value in the first channel.
  • FIG4 shows an optional implementation of the embodiment of the present disclosure, including the following steps:
  • Step 401 During the OBSS TXOP time sensed by the primary channel, the first device 101 transmits data on the primary channel.
  • the first device when the main channel is in the OBSS busy state, in order to make full use of the channel resources, the first device can switch to the first channel communication and perform data transmission within the OBSS TXOP time perceived by the main channel, thereby improving the system throughput.
  • Step 402 After the OBSS TXOP time ends, the first device 101 performs channel status perception or listening.
  • the first device After the OBSS TXOP period ends, the first device (AP or STA) completes data exchange on the secondary channel and switches to the primary channel. After switching to the primary channel, the first device needs to listen to see if there is other data being transmitted on the primary channel before sending data, for example, through a carrier sense mechanism. The first device performs channel sensing or listening after a synchronization delay. That is, the first device waits for a period of time after switching to the primary channel to ensure that there is no activity on the primary channel from other devices, preventing interference caused by multiple devices listening on the same channel at the same time.
  • Step 403 Send a request to send (RTS) frame on the retransmission channel to the receiving end 102 that sent the first data frame.
  • RTS request to send
  • the first device in order to ensure that the receiving end of the first data frame has switched to the main channel or the secondary channel, the first device first sends an RTS frame to the receiving end of the first data frame for detection before sending the unsuccessfully transmitted QoS data frame to the receiving end of the first data frame on the retransmission channel to inquire whether the receiving end of the first data frame has switched to the main channel or the secondary channel and is ready to receive QoS data, thereby improving the reliability of communication.
  • Step 404 The receiving end that receives the first data frame sends a Clear to Send (CTS) frame to retransmit the QoS data frame that was not successfully transmitted.
  • CTS Clear to Send
  • the first device after receiving a CTS frame from the receiving end of the first data frame on a retransmission channel, the first device retransmits the unsuccessfully transmitted QoS data frame.
  • the CTS frame reply from the receiving end of the first data frame indicates that the receiving end is ready to receive data, which helps ensure that the QoS data frame can be successfully transmitted during retransmission and improves communication reliability.
  • the names of information, etc. are not limited to the names described in the embodiments, and terms such as “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “codepoint”, “bit”, “data”, “program”, and “chip” can be used interchangeably.
  • terms such as “moment”, “time point”, “time”, and “time position” can be replaced with each other, and terms such as “duration”, “period”, “time window”, “window”, and “time” can be replaced with each other.
  • wireless access scheme and waveform can be used interchangeably.
  • terms such as “certain”, “preset”, “preset”, “setting”, “indicated”, “a certain”, “any”, and “first” can be interchangeable.
  • “Specific A”, “preset A”, “preset A”, “setting A”, “indicated A”, “a certain A”, “any A”, and “first A” can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.
  • the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values (for example, comparison with a predetermined value), but is not limited thereto.
  • not expecting to receive can be interpreted as not receiving on time domain resources and/or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send” can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.
  • step 201 can be implemented as an independent embodiment
  • step 202 can be implemented as an independent embodiment
  • step 203 can be implemented as an independent embodiment
  • step 301 can be implemented as an independent embodiment
  • step 302 can be implemented as an independent embodiment
  • step 303 can be implemented as an independent embodiment
  • step 304 can be implemented as an independent embodiment
  • step 305 can be implemented as an independent embodiment
  • step 401 can be implemented as an independent embodiment
  • step 402 can be implemented as an independent embodiment
  • step 403 can be implemented as an independent embodiment
  • step 404 can be implemented as an independent embodiment
  • the combination of step 201 and step 202 can be implemented as an independent embodiment
  • the combination of step 202 and step 203 can be implemented as an independent embodiment
  • the combination of step 301 and step 302 can be implemented as an independent embodiment
  • the combination of step 303 and step 304 can be implemented as an independent embodiment
  • the combination of step 304 and step 305 can be implemented as an independent embodiment
  • the combination of step 304 and step 305 can be implemented as an
  • FIG7 is a flow chart showing a data transmission method according to an embodiment of the present disclosure.
  • the above method includes:
  • Step 701 During the overlapping basic service set transmission opportunity OBSS TXOP time perceived by the main channel, the first device transmits data on the first channel.
  • the method includes:
  • the first device senses that the primary channel is busy and switches to the first channel to transmit a first data frame; wherein the first data frame includes a sequence number and a transmission identifier TID;
  • Step 702 After the OBSS TXOP time ends, the first device performs channel status perception or listening.
  • Step 703 Retransmit the quality of service (QoS) data frames that are not successfully transmitted within the OBSS TXOP time based on the perceived channel status.
  • QoS quality of service
  • retransmitting a QoS data frame that is not successfully transmitted within the OBSS TXOP time according to the sensed channel state includes:
  • the first device senses that the channel state of the primary channel is idle, and retransmits the QoS data frame that was not successfully transmitted on the primary channel;
  • the retry bit of the media access control MAC frame header of the unsuccessfully transmitted QoS data frame is set to the first parameter value, and the serial number SN setting value of the unsuccessfully transmitted QoS data frame is the same as the setting value in the first channel.
  • retransmitting the unsuccessfully transmitted QoS data frame on the primary channel includes:
  • the main channel is in the OBSS TXOP busy state, switching to the first channel or the second channel for transmission; the second channel is pre-negotiated between the first device and the receiving end of the first data frame.
  • the switching to the first channel or the second channel transmission includes:
  • the retry bit of the MAC frame header of the unsuccessfully transmitted QoS data frame is set to the first parameter value, and the SN setting value of the unsuccessfully transmitted QoS data frame is the same as the setting value in the first channel.
  • retransmitting the QoS data frame that is not successfully transmitted within the OBSS TXOP time includes:
  • the receiving end that receives the first data frame sends a clear-to-send CTS frame to retransmit the QoS data frame that was not successfully transmitted.
  • step 701 may be implemented as an independent embodiment
  • step 702 may be implemented as an independent embodiment
  • step 703 may be implemented as an independent embodiment
  • the combination of step 701 and step 702 may be implemented as an independent embodiment
  • the combination of step 702 and step 703 may be implemented as an independent embodiment, but the present invention is not limited thereto.
  • the embodiments of the present disclosure further provide an apparatus for implementing any of the above methods.
  • an apparatus comprising units or modules for implementing each step performed by a terminal in any of the above methods.
  • another apparatus comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.
  • a network device e.g., an access network device, a core network function node, a core network device, etc.
  • the division of the units or modules in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated.
  • the units or modules in the device can be called by the processor to perform software operations.
  • the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory.
  • the processor calls the instructions stored in the memory to implement any of the above methods or realize the functions of each unit or module of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory inside the device or a memory outside the device.
  • CPU central processing unit
  • microprocessor a microprocessor
  • the unit or module in the device can be implemented in the form of a hardware circuit, and the functions of some or all of the units or modules can be realized by designing the hardware circuit.
  • the above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above units or modules are realized by designing the logical relationship of the components in the circuit; for another example, in another implementation, the above hardware circuit can be implemented by a programmable logic device (PLD).
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • the processor is a circuit with signal processing capabilities.
  • the processor may be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP).
  • the processor may implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable.
  • the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules.
  • it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as the Neural Network Processing Unit (NPU), the Tensor Processing Unit (TPU), the Deep Learning Processing Unit (DPU), etc.
  • FIG8 is a schematic diagram of the structure of a first device according to an embodiment of the present disclosure.
  • the first device 800 may include at least one of a first processing module 801 , a second processing module 802 , and a third processing module 803 .
  • the first processing module 801 is configured to transmit data on the primary channel within the OBSS TXOP time sensed by the primary channel.
  • the second processing module 802 is configured to sense or monitor the channel status after the OBSS TXOP time expires.
  • the third processing module 803 is configured to retransmit Quality of Service (QoS) data frames that were not successfully transmitted within the OBSS TXOP time based on the sensed channel status.
  • QoS Quality of Service
  • the first processing module 801 is configured to execute at least one of the communication steps (e.g., step 201, step 303, step 401, and step 701, but not limited thereto) performed by the first device 101 in any of the above methods, which are not described in detail here.
  • the second processing module 802 is configured to execute at least one of step 202, step 304, step 402, and step 702.
  • the third processing module 803 is configured to execute at least one of step 203, step 305, and step 703.
  • Figure 9 is a schematic diagram of the structure of a terminal 900 (e.g., user equipment) proposed in an embodiment of the present disclosure.
  • Terminal 900 can be a chip, chip system, or processor that supports a network device implementing any of the above methods, or a chip, chip system, or processor that supports a terminal implementing any of the above methods.
  • Terminal 900 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.
  • terminal 900 includes one or more processors 901.
  • Processor 901 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit.
  • the baseband processor can be used to process communication protocols and communication data
  • the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data.
  • Terminal 900 is used to perform any of the above methods.
  • the terminal 900 further includes one or more memories 902 for storing instructions.
  • the memories 902 may be located outside the terminal 900.
  • the terminal 900 further includes one or more transceivers 904.
  • the transceiver 904 performs at least one of the communication steps such as sending and/or receiving in the above method (for example, step 201, step 203, step 301, step 302, step 303, step 305, step 401, step 403, step 404, step 701, step 703, but not limited thereto), and the processor 901 performs at least one of the other steps (for example, step 202, step 304, step 402, step 702, but not limited thereto).
  • the transceiver may include a receiver and/or a transmitter.
  • the receiver and the transmitter may be separate or integrated.
  • the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc. may be interchangeable, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. may be interchangeable, and the terms receiver, receiving unit, receiver, receiving circuit, etc. may be interchangeable. Replace each other.
  • terminal 900 may include one or more interface circuits 903.
  • interface circuit 903 is connected to memory 902.
  • Interface circuit 903 may be configured to receive signals from memory 902 or other devices, and may be configured to send signals to memory 902 or other devices.
  • interface circuit 903 may read instructions stored in memory 902 and send the instructions to processor 901.
  • the terminal 900 described in the above embodiment may be a communication device such as a user device, but the scope of the terminal 900 described in the present disclosure is not limited thereto, and the structure of the terminal 900 may not be limited by FIG. 9 .
  • the communication device may be an independent device or may be part of a larger device.
  • the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
  • FIG10 is a schematic diagram of the structure of a chip 1000 according to an embodiment of the present disclosure. If the terminal 900 is a chip or a chip system, reference may be made to the schematic diagram of the structure of the chip 1000 shown in FIG10 , but the present disclosure is not limited thereto.
  • the chip 1000 includes one or more processors 1001 , and the chip 1000 is configured to execute any of the above methods.
  • chip 1000 further includes one or more 1003.
  • interface circuit 1003 is connected to memory 1002.
  • Interface circuit 1003 can be used to receive signals from memory 1002 or other devices, and interface circuit 1003 can be used to send signals to memory 1002 or other devices.
  • interface circuit 1003 can read instructions stored in memory 1002 and send the instructions to processor 1001.
  • the interface circuit 1003 executes at least one of the communication steps such as sending and/or receiving in the above method (for example, step 201, step 203, step 301, step 302, step 303, step 305, step 401, step 403, step 404, step 701, step 703, but not limited to these), and the processor 1001 executes at least one of the other steps (for example, step 202, step 304, step 402, step 702, but not limited to these).
  • interface circuit interface circuit
  • transceiver pin transceiver
  • the chip 1000 further includes one or more memories 1002 for storing instructions. Alternatively, all or part of the memory 1002 may be external to the chip 1000.
  • the present disclosure also provides a storage medium having instructions stored thereon.
  • the terminal 900 executes any of the above methods.
  • the storage medium is an electronic storage medium.
  • the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices.
  • the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.
  • the present disclosure also provides a program product, which, when executed by the terminal 900, enables the terminal 900 to perform any of the above methods.
  • the program product is a computer program product.
  • the present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例涉及一种数据传输方法、通信设备及通信系统。所述数据传输方法包括：在主信道感知的重叠基本服务集传输机会OBSS TXOP时间内，第一设备在第一次信道进行数据传输；所述OBSS TXOP时间结束后，所述第一设备进行信道状态感知或侦听；根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的服务质量QoS数据帧进行重传，从而完善了设备对次信道下未能成功传输的数据进行重传的机制，提高了系统吞吐量，减小了通信时延，适用UHR需求。

Description

数据传输方法、通信设备及通信系统 技术领域
本公开涉及通信技术领域，尤其涉及一种数据传输方法、通信设备及通信系统。
背景技术
目前，Wi-Fi技术所研究的内容例如超高可靠性(Ultra High Reliability，UHR)，其愿景为提高无线局域网(Wireless Local Area Networks，WLAN)连接的可靠性、减少延迟、提高可管理性、在不同信噪比(Signal to Noise Ratio，SNR)级别下增加吞吐量并降低设备级功耗等。
在UHR中，为了提高系统的吞吐量以及减小通信时延，当主信道感知到繁忙时，设备可切换至次信道进行通信，而对于未能在次信道中成功传输的数据帧，需要在主信道或次信道进行重传。因此，需要进一步完善设备在主信道下、次信道下进行数据传输的机制，以满足UHR的传输需求。
发明内容
本公开实施例提供了一种数据传输方法、通信设备及通信系统，以提供进一步完善设备在主信道下、次信道下进行数据传输的机制。
一方面，本公开实施例提供了一种数据传输方法，所述方法包括：
在主信道感知的重叠基本服务集传输机会OBSS TXOP时间内，第一设备在第一次信道进行数据传输；
所述OBSS TXOP时间结束后，所述第一设备进行信道状态感知或侦听；
根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的服务质量QoS数据帧进行重传。
另一方面，本公开实施例还提供了一种通信设备，所述通信设备为第一设备，所述第一设备为站点设备或接入点设备，所述第一设备包括：
第一处理模块，用于在主信道感知的OBSS TXOP时间内，在第一次信道进行数据传输；
第二处理模块，用于所述OBSS TXOP时间结束后，进行信道状态感知或侦听；
第三处理模块，用于根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的服务质量QoS数据帧进行重传。
另一方面，本公开实施例还提供了一种通信设备，所述通信设备为第一设备，所述第一设备为站点设备或接入点设备，包括：
一个或多个处理器；
其中，所述第一设备用于执行实现本公开实施例中所述的数据传输方法。
本公开实施例还提供了一种通信系统，包括第一设备，所述第一设备为站点设备或接入点设备；其中，所述第一设备被配置为实现本公开实施例中所述的数据传输方法。
本公开实施例还提供了一种存储介质，所述存储介质存储有指令，当所述指令在通信设备上运行时，使得所述通信设备执行如本公开实施例中所述的数据传输方法。
本公开实施例中，在主信道感知的重叠基本服务集传输机会OBSS TXOP时间内，第一设备在第一次信道进行数据传输；所述OBSS TXOP时间结束后，所述第一设备进行信道状态感知或侦听；根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的服务质量QoS数据帧进行重传，从而完善了设备对次信道下未能成功传输的数据进行重传的机制，提高了系统吞吐量，减小了通信时延，适用UHR需求。
本公开实施例附加的方面和优点将在下面的描述中部分给出，这些将从下面的描述中变得明显，或通过本公开的实践了解到。
附图说明
为了更清楚地说明本公开实施例中的技术方案，以下对实施例描述所需的附图进行介绍，以下 附图仅仅是本公开的一些实施例，不对本公开的保护范围造成具体限制。
图1为根据本公开实施例提供的通信系统的架构的一个示例性示意图；
图2为根据本公开实施例提供的方法的一个示例性交互示意图之一；
图3为根据本公开实施例提供的方法的一个示例性交互示意图之二；
图4为根据本公开实施例提供的方法的一个示例性交互示意图之三；
图5为本公开实施例提供的数据传输方法的信道传输示意图之一；
图6为本公开实施例提供的数据传输方法的信道传输示意图之二；
图7为本公开实施例提供的数据传输方法的流程示意图；
图8为本公开实施例提出的第一设备的结构示意图；
图9为本公开实施例提出的终端的结构示意图；
图10为本公开实施例提出的芯片的结构示意图。
具体实施方式
本公开实施例提出了一种数据传输方法、通信设备及通信系统。
第一方面，本公开实施例提出了一种数据传输方法，所述方法包括：
在主信道感知的重叠基本服务集传输机会OBSS TXOP时间内，第一设备在第一次信道进行数据传输；
所述OBSS TXOP时间结束后，所述第一设备进行信道状态感知或侦听；
根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的服务质量QoS数据帧进行重传。
在上述实施例中，完善了设备对次信道下未能成功传输的数据进行重传的机制，提高了系统吞吐量，减小了通信时延，适用UHR需求。
结合第一方面的一些实施例，在一些实施例中，所述在主信道感知的OBSS TXOP时间内，第一设备在次信道进行数据传输之前，所述方法包括：
第一设备感知所述主信道繁忙，切换至所述第一次信道传输第一数据帧；其中，所述第一数据帧包括序列号以及传输标识TID；
在所述第一次信道接收所述第一数据帧的接收端反馈的块确认BA帧；其中，所述BA帧包括位图bitmap标识位，标识所述第一数据帧的每个QoS数据帧是否被正确接收。
在上述实施例中，序列号(sequence number space，SNS)用于标识第一数据帧在传输过程中的顺序，用于第一数据帧的接收端确认和按序接收第一数据帧。传输标识(Traffic Identifier，TID)用于标识第一数据帧的每个服务质量(Quality of Service，QoS数据帧)。这样，第一数据帧的接收端可根据第一数据帧的SNS和TID确定成功接收的QoS数据帧。
在上述实施例中，第一设备在所述第一次信道接收所述第一数据帧的接收端反馈的块确认(block ACK，BA)帧；其中，所述BA帧包括位图bitmap标识位，标识所述第一数据帧的每个QoS数据帧是否被正确接收。
其中，BA帧为接收端向发送端发送的帧，用于确认接收端接收到一系列帧的成功传输。第一数据帧的接收端通过发送BA帧向第一设备反馈成功接收的QoS数据帧。例如，第一数据帧的接收端通过BA帧的位图bitmap标识位标识第一数据帧的每个QoS数据帧是否被正确接收。
结合第一方面的一些实施例，在一些实施例中，所述根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的QoS数据帧进行重传，包括：
所述第一设备感知所述主信道的信道状态为空闲，在所述主信道对未成功传输的QoS数据帧进行重传；
其中，所述未成功传输的QoS数据帧的媒体访问控制MAC帧头的retry比特位设置为第一参数值，且未成功传输的QoS数据帧的序列号SN设置值与在所述第一次信道中的设置值相同。
在上述实施例中，针对主信道的信道状态为空闲的情况，对未成功传输的QoS数据帧进行重传。这样的机制可以避免在信道繁忙的情况下进行重传，提高重传的成功概率。此外，将未成功传输的QoS数据帧的MAC帧头的retry比特位设置为第一参数值，并保持序列号SN设置值与第一次传输时的设置值相同。这样的设置有助于设备和网络更好地协同工作，确保重传的数据帧得到正确处理。
结合第一方面的一些实施例，在一些实施例中，所述在所述主信道对未成功传输的QoS数据帧进行重传，包括：
感知到所述主信道处于OBSS TXOP繁忙状态，切换到所述第一次信道或第二次信道传输；所述第二次信道为所述第一设备与所述第一数据帧的接收端预先协商的。
在上述实施例中，通过感知主信道的繁忙状态，设备可以根据实时的信道状况做出智能决策。如果主信道繁忙，切换到预先协商的其他信道，有助于避免信道冲突和提高数据传输成功率。
结合第一方面的一些实施例，在一些实施例中，所述切换到所述第一次信道或第二次信道传输，包括：
感知到所述第一次信道或第二次信道处于空闲状态，在所述第一次信道或第二次信道对未成功传输的QoS数据帧进行重传；
其中，所述未成功传输的QoS数据帧的MAC帧头的retry比特位设置为第一参数值，且未成功传输的QoS数据帧的SN设置值与在所述第一次信道中的设置值相同。
在上述实施例中，通过感知第一次信道或第二次信道的空闲状态，设备可以智能地选择一个空闲的备用信道，以最大程度地避免信道冲突和提高数据传输成功率。此外，通过设置未成功传输的QoS数据帧的MAC帧头的retry比特位和序列号SN与第一次信道相同，确保了在重传过程中传输参数的一致性。这对于接收端正确接收和处理数据帧非常重要。
结合第一方面的一些实施例，在一些实施例中，所述对所述OBSS TXOP时间内未成功传输的QoS数据帧进行重传，包括：
在重传信道上向发送所述第一数据帧的接收端发送请求发送RTS帧；
接收到所述第一数据帧的接收端发送清除发送CTS帧，对未成功传输的QoS数据帧进行重传。
在上述实施例中，使用RTS/CTS机制可以帮助避免碰撞和冲突，提高网络的稳定性。通过提前通知接收端即将进行数据传输，减少了可能的碰撞概率。
第二方面，本公开实施例还提供了一种通信设备，所述通信设备为第一设备，所述第一设备为站点设备或接入点设备，上述第一设备包括第一处理模块、第二处理模块、第三处理模块中的至少一者；其中，上述第一设备用于执行第一方面的可选实现方式。
第三方面，本公开实施例还提供了一种通信设备，所述通信设备为第一设备，包括：
一个或多个处理器；
其中，所述第一设备用于执行第一方面的可选实现方式。
第四方面，本公开实施例还提供了一种通信系统，包括第一设备，所述第一设备为站点设备或接入点设备；其中，所述第一设备被配置为执行如第一方面所述的可选实现方式。
第五方面，本公开实施例还提供了一种存储介质，所述存储介质存储有指令，当所述指令在通信设备上运行时，使得所述通信设备执行如第一方面所述的可选实现方式。
第六方面，本公开实施例提出了程序产品，上述程序产品被通信设备执行时，使得上述通信设备执行如第一方面的可选实现方式所描述的方法。
第七方面，本公开实施例提出了计算机程序，当其在计算机上运行时，使得计算机执行如第一方面的可选实现方式所描述的方法。
第八方面，本公开实施例提供了一种芯片或芯片系统。该芯片或芯片系统包括处理电路，被配置为执行根据上述第一方面、第二方面的可选实现方式所描述的方法。
可以理解地，上述第一设备、通信系统、存储介质、程序产品、计算机程序、芯片或芯片系统均用于执行本公开实施例所提出的方法。因此，其所能达到的有益效果可以参考对应方法中的有益效果，此处不再赘述。
本公开实施例提出了数据传输方法、通信设备及通信系统。在一些实施例中，数据传输方法与信号发送方法、无线帧发送方法等术语可以相互替换，信息处理系统、通信系统等术语可以相互替换。
本公开实施例并非穷举，仅为部分实施例的示意，不作为对本公开保护范围的具体限制。在不矛盾的情况下，某一实施例中的每个步骤均可以作为独立实施例来实施，且各步骤之间可以任意组 合，例如，在某一实施例中去除部分步骤后的方案也可以作为独立实施例来实施，且在某一实施例中各步骤的顺序可以任意交换，另外，某一实施例中的可选实现方式可以任意组合；此外，各实施例之间可以任意组合，例如，不同实施例的部分或全部步骤可以任意组合，某一实施例可以与其他实施例的可选实现方式任意组合。
在各本公开实施例中，如果没有特殊说明以及逻辑冲突，各实施例之间的术语和/或描述具有一致性，且可以互相引用，不同实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
本公开实施例中所使用的术语只是为了描述特定实施例的目的，而并非作为对本公开的限制。
在本公开实施例中，“多个”是指两个或两个以上。
在一些实施例中，“至少一者(至少一项、至少一个)(at least one of)”、“一个或多个(one or more)”、“多个(a plurality of)”、“多个(multiple)等术语可以相互替换。
在一些实施例中，“A、B中的至少一者”、“A和/或B”、“在一情况下A，在另一情况下B”、“响应于一情况A，响应于另一情况B”等记载方式，根据情况可以包括以下技术方案：在一些实施例中A(与B无关地执行A)；在一些实施例中B(与A无关地执行B)；在一些实施例中从A和B中选择执行(A和B被选择性执行)；在一些实施例中A和B(A和B都被执行)。当有A、B、C等更多分支时也类似上述。
在一些实施例中，“A或B”等记载方式，根据情况可以包括以下技术方案：在一些实施例中A(与B无关地执行A)；在一些实施例中B(与A无关地执行B)；在一些实施例中从A和B中选择执行(A和B被选择性执行)。当有A、B、C等更多分支时也类似上述。
本公开实施例中的“第一”、“第二”等前缀词，仅仅为了区分不同的描述对象，不对描述对象的位置、顺序、优先级、数量或内容等构成限制，对描述对象的陈述参见权利要求或实施例中上下文的描述，不应因为使用前缀词而构成多余的限制。例如，描述对象为“字段”，则“第一字段”和“第二字段”中“字段”之前的序数词并不限制“字段”之间的位置或顺序，“第一”和“第二”并不限制其修饰的“字段”是否在同一个消息中，也不限制“第一字段”和“第二字段”的先后顺序。再如，描述对象为“等级”，则“第一等级”和“第二等级”中“等级”之前的序数词并不限制“等级”之间的优先级。再如，描述对象的数量并不受序数词的限制，可以是一个或者多个，以“第一装置”为例，其中“装置”的数量可以是一个或者多个。此外，不同前缀词修饰的对象可以相同或不同，例如，描述对象为“装置”，则“第一装置”和“第二装置”可以是相同的装置或者不同的装置，其类型可以相同或不同；再如，描述对象为“信息”，则“第一信息”和“第二信息”可以是相同的信息或者不同的信息，其内容可以相同或不同。
在一些实施例中，“包括A”、“包含A”、“用于指示A”、“携带A”，可以解释为直接携带A，也可以解释为间接指示A。
在一些实施例中，“响应于……”、“响应于确定……”、“在……的情况下”、“在……时”、“当……时”、“若……”、“如果……”等术语可以相互替换。
在一些实施例中，“大于”、“大于或等于”、“不小于”、“多于”、“多于或等于”、“不少于”、“高于”、“高于或等于”、“不低于”、“以上”等术语可以相互替换，“小于”、“小于或等于”、“不大于”、“少于”、“少于或等于”、“不多于”、“低于”、“低于或等于”、“不高于”、“以下”等术语可以相互替换。
在一些实施例中，装置和设备可以解释为实体的、也可以解释为虚拟的，其名称不限定于实施例中所记载的名称，在一些情况下也可以被理解为“设备(equipment)”、“设备(device)”、“电路”、“网元”、“节点”、“功能”、“单元”、“部件(section)”、“系统”、“网络”、“芯片”、“芯片系统”、“实体”、“主体”等。
在一些实施例中，获取数据、信息等可以遵照所在地国家的法律法规。
在一些实施例中，可以在得到用户同意后获取数据、信息等。
此外，本公开实施例的表格中的每一元素、每一行、或每一列均可以作为独立实施例来实施，任意元素、任意行、任意列的组合也可以作为独立实施例来实施。
图1是根据本公开实施例示出的通信系统的架构示意图。
如图1所示，通信系统100包括第一设备101、第二设备102。其中，第一设备可以为站点设备(Station，STA)或接入点设备(Access Point，AP)；第二设备可以为STA或AP。例如，当第一设备101为STA时，第二设备102为AP；当第一设备101为AP时，第二设备102为STA。
在一些实施例中，第一设备101、第二设备102例如包括支持WiFi通讯功能的无线通讯芯片、无线传感器或无线通信终端。可选地，无线通信终端例如手机(mobile phone)、可穿戴设备、支持WiFi通讯功能的物联网设备、具备WiFi通讯功能的汽车、智能汽车、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、 远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备中的至少一者，但不限于此。
具体地，第一设备101、第二设备102可以是带有无线保真(WiFi)芯片的终端设备或者网络设备。可选的，第一设备101可以支持802.11ax、802.11be、802.11ac、802.11n、802.11g、802.11b及802.11a、、802.11bf、802.11bn等多种WLAN制式，以及支持下一代802.11协议，但不限于此。
在一些实施例中，第一设备101、第二设备102可以是移动终端进入有线网络的接入点。AP相当于一个连接有线网和无线网的桥梁，其主要作用是将各个无线网络客户端连接到一起，然后将无线网络接入以太网。具体地，AP可以是带有无线保真芯片的终端设备或者网络设备。可选的，AP可以支持802.11ax、802.11be、802.11ac、802.11n、802.11g、802.11b及802.11a、802.11bf、802.11bn等多种WLAN制式，以及支持下一代802.11协议，但不限于此。
可选地，在本公开实施例中，AP和STA可以为支持多连接的设备，例如，可以被分别表示为多连接入点设备(Access Point Multi-Link Device，AP MLD)和多连接站点设备(Non-Access Point Multi-Link Device，Non-AP MLD)；AP MLD可以表示支持多连接通信功能的接入点，non-AP MLD可以表示支持多连接通信功能的站点。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提出的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提出的技术方案对于类似的技术问题同样适用。
下述本公开实施例可以应用于图1所示的通信系统100、或部分主体，但不限于此。图1所示的各主体是例示，通信系统可以包括图1中的全部或部分主体，也可以包括图1以外的其他主体，各主体数量和形态为任意，各主体可以是实体的也可以是虚拟的，各主体之间的连接关系是例示，各主体之间可以不连接也可以连接，其连接可以是任意方式，可以是直接连接也可以是间接连接，可以是有线连接也可以是无线连接。
本公开各实施例可以应用于无线局域网(Wireless Local Area Network，WLAN)，例如采用802.11系列协议的局域网。在WLAN中，基本服务集(BSS，Basic Service Set)是一个WLAN的基本组成部分。BSS网络是由某一特定覆盖区域之内具有某种关联的站点设备组成。关联的一种情形是站点在一个自组网络中相互直接通信，这被称为独立BSS(IBSS，Independent Basic Service Set)。另一种更常见的情形是在BSS网络中只有一个具有专职管理BSS的中央站点被称为接入点设备，而在该网络中的其它STA都与它相关联。在BSS网络中的不是中央站点的其它站点被称之为终端，也称之为non-AP STA，终端和non-AP STA统称之为STA。当描述STA时不需要区分AP和non-AP STA。在同一个BSS网络中，由于距离、发送功率等原因，一个STA无法检测离其较远的其他STA，两者互为对方的隐藏节点。
图2是根据本公开实施例示出的数据传输方法的交互示意图。如图2所示，上述方法包括：
步骤201，在主信道感知的OBSS TXOP时间内，第一设备101在第一次信道进行数据传输。
在WLAN中，信道通常分为主信道和次信道(secondary channel或non-primary channel，或称为辅助信道、非主信道)；主信道表示当前设备所连接的BSS的主要通信信道。其中，次信道可以包含一个或多个子信道。例如，若以20MHz为基本带宽单位进行划分，当信道带宽为20MHz时，仅具有一个带宽为20MHz的主信道；当信道带宽大于20MHz时，包含一个带宽为20MHz的信道为主信道，其余的一个或多个20MHz信道为辅助信道。主20MHz信道为属于一个BSS中的成员的公共操作信道(The common channel of operation for stations that are members of the basic service set)，BSS中的站点可在主20MHz信道上进行信道竞争，以抢占信道资源。
作为示例，如图5所示，主信道例如图5中主20MHz信道；其中，次信道可以包含一个或多个子信道，例如图5中20MHz次信道和40MHz次信道。
重叠基本服务集(Overlapping Basic Service Set，OBSS)包括两个及两个以上的BSS的覆盖范围重叠部分，在信道上进行信道竞争的过程，若主信道处于OBSS繁忙状态(OBSS干扰)，如图中T1时间段与T2时间段所示，例如被与WLAN处于同一OBSS中的其他设备所占据，其他设备在主信道上发送物理层协议数据单元(Physical Protocol Data Unit，PPDU)，则该主信道处于OBSS繁忙状态。若主信道处于OBSS繁忙状态，为了能够充分利用信道资源，则可切换到次信道通信，以提高通信系统吞吐量，实现信道资源利用最大化。例如，在T1时间段切换到20MHz次信道通信，或在T2时间段切换到40MHz次信道通信。
若主信道处于空闲状态，如图中T3时间段所示，则AP与STA之间可以互相发送PPDU。
此外，当在主信道进行通信(次信道繁忙)，当次信道空闲时，则可聚合主次信道进行通信提高系统的吞吐量；作为示例，如图6所示，在传输每个帧的过程中，可以聚合主信道和至少一个次信道传输。
其中，传输机会(Transmission Opportunity，TXOP)表示在主信道上的一段时间内，某一设备有权进行连续的数据传输，OBSS TXOP表示设备在OBSS中获得主信道上的传输机会。因此，当主信道处于OBSS繁忙状态时，为了充分利用信道资源，设备可切换到次信道通信，并在主信道感知的OBSS TXOP时间内进行数据传输，即在次信道的通信时长为主信道感知的OBSS TXOP时长。
步骤202，所述OBSS TXOP时间结束后，所述第一设备101进行信道状态感知或侦听。
在OBSS TXOP时间结束后，第一设备(AP或STA)在次信道完成数据交互，再切换至主信道进行通信。在切换至主信道后，第一设备在发送数据前需要感知(sensing，或侦听：listening)主信道上有没有其他数据在传输，例如通过载波侦听(carrier sense)机制实现。其中，第一设备在同步时延(Medium Synchronization delay)之后进行信道感知或侦听，即第一设备在切换至主信道后等待一段时间，以确保主信道上没有其他设备的活动，防止在同一时刻多个设备在相同信道上进行侦听导致干扰。
步骤203，根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的QoS数据帧进行重传。
其中，服务质量(Quality of Service，QoS)数据帧用于提供不同服务流之间的差异化服务质量，包括但不限于语音、视频和实时应用的数据。第一设备根据所感知的信道状态，对OBSS TXOP时间内未成功传输的QoS数据帧进行重传。
这样，在UHR中，本公开实施例完善设备在主次信道中的数据传输机制，当第一设备感知主信道繁忙时，切换至第一次信道传输第一数据帧，在第一次信道接收第一数据帧的接收端反馈的BA帧，通过BA帧的bitmap标识位，确定第一数据帧中未被成功接收的QoS数据帧，并在OBSS TXOP时间结束后，切换至主信道进行感知或侦听，根据感知的信道状态，对OBSS TXOP时间内未成功传输的QoS数据帧进行重传，使得第一设备能够快速接入信道进行传输，从而减小时延，适用UHR需求。
在一些实施例中，在步骤201之前，第一设备感知所述主信道繁忙，切换至所述第一次信道传输第一数据帧；其中，所述第一数据帧包括序列号以及传输标识TID；
其中，序列号(sequence number space，SNS)用于标识第一数据帧在传输过程中的顺序，用于第一数据帧的接收端确认和按序接收第一数据帧。传输标识(Traffic Identifier，TID)用于标识第一数据帧的每个服务质量(Quality of Service，QoS数据帧)。这样，第一数据帧的接收端可根据第一数据帧的SNS和TID确定成功接收的QoS数据帧。
在一些实施例中，第一设备在所述第一次信道接收所述第一数据帧的接收端反馈的块确认(block ACK，BA)帧；其中，所述BA帧包括位图bitmap标识位，标识所述第一数据帧的每个QoS数据帧是否被正确接收。
其中，BA帧为接收端向发送端发送的帧，用于确认接收端接收到一系列帧的成功传输。第一数据帧的接收端通过发送BA帧向第一设备反馈成功接收的QoS数据帧。例如，第一数据帧的接收端通过BA帧的位图bitmap标识位标识第一数据帧的每个QoS数据帧是否被正确接收。
作为示例，参见图3，图3示出了本公开实施例的一个可选实现方式，包括以下步骤：
步骤301，第一设备101感知所述主信道繁忙，切换至所述第一次信道传输第一数据帧；其中，所述第一数据帧包括序列号以及TID。
其中，第一设备感知主信道繁忙后，切换至第一次信道传输第一数据帧，第一数据帧包括用于标识第一数据帧在传输过程中的顺序的序列号SN，以及用于标识第一数据帧的每个QoS数据帧的TID。这样，第一数据帧的接收端可根据第一数据帧的SN和TID确定成功接收的QoS数据帧。
步骤302，在所述第一次信道接收所述第一数据帧的接收端102反馈的BA帧；其中，所述BA帧包括bitmap标识位，标识所述第一数据帧的每个QoS数据帧是否被正确接收。
在一些实施例中，第一设备在所述第一次信道接收所述第一数据帧的接收端反馈的BA帧；其中，所述BA帧包括位图bitmap标识位，标识所述第一数据帧的每个QoS数据帧是否被正确接收。
其中，BA帧为接收端向发送端发送的帧，用于确认接收端接收到一系列帧的成功传输。第一数据帧的接收端通过发送BA帧向第一设备反馈成功接收的QoS数据帧。例如，第一数据帧的接收端通过BA帧的位图bitmap标识位标识第一数据帧的每个QoS数据帧是否被正确接收。
步骤303，在主信道感知的OBSS TXOP时间内，第一设备101在次信道进行数据传输。
在一些实施例中，当主信道处于OBSS繁忙状态时，为了充分利用信道资源，第一设备可切换到次信道通信，并在主信道感知的OBSS TXOP时间内进行数据传输，提高系统的吞吐量。
步骤304，所述OBSS TXOP时间结束后，所述第一设备101进行信道状态感知或侦听。
其中，在OBSS TXOP时间结束后，第一设备(AP或STA)在次信道完成数据交互，切换至主信道。在切换至主信道后，第一设备在发送数据前需要侦听主信道上有没有其他数据在传输，例如通过载波侦听机制实现。其中，第一设备在同步时延之后进行信道感知或侦听，即第一设备在切换至主信道后等待一段时间，以确保主信道上没有其他设备的活动，防止在同一时刻多个设备在相同信道上进行侦听导致干扰。
步骤305，所述第一设备101感知所述主信道的信道状态为空闲，在所述主信道对未成功传输的QoS数据帧进行重传；
在一些实施例中，由于第一设备在第一次信道进行通信的时长限制为OBSS TXOP时长，则在OBSS TXOP时长内可能无法完全覆盖所有需要重传的QoS数据帧，导致部分QoS数据帧无法在第一次信道中得到重传。若将TID映射到多个链路，以便在一个链路上传输QoS数据帧，然后在一个链路上进行重传，则会引入复杂性和额外的系统开销。因此，对于超过OBSS TXOP时间还未成功传输的QoS数据帧如何进行重传，需要加以定义。
其中，所述未成功传输的QoS数据帧的媒体访问控制(Media Access Control，MAC)帧头的retry比特位设置为第一参数值，且未成功传输的QoS数据帧的SN设置值与在所述第一次信道中的设置值相同。
在一些实施例中，在OBSS TXOP时间结束后，第一设备在次信道完成数据交互，切换至主信道进行信道感知或侦听。若第一设备感知主信道的信道状态为空闲，则在主信道对未成功传输的QoS数据帧进行重传，且未成功传输的QoS数据帧的retry比特位设置为第一参数值，例如retry比特位设置为“1”时，标识该QoS数据帧为重传帧；retry比特位设置为“0”时，标识该QoS数据帧不为重传帧。
其中，未成功传输的QoS数据帧的SN设置值与其在第一次信道中的SN设置值相同，有助于接收端正确的将重传帧放入正确的顺序，避免乱序。此外，保持SN设置值相同还可以简化重传机制，减少处理逻辑的复杂性。
在一些实施例中，若第一设备感知到主信道处于OBSS TXOP繁忙状态，切换到所述第一次信道或第二次信道传输；所述第二次信道为所述第一设备与所述第一数据帧的接收端预先协商的。
其中，当主信道处于OBSS TXOP繁忙状态时，表示其他BSS设备正在使用主信道进行通信，不适合在主信道对未成功传输的QoS数据帧进行重传。因此，在主信道处于OBSS TXOP繁忙状态，第一设备既可选择切换到第一次信道进行重传，又可以切换到与接收端预先协商的其他次信道进行重传。例如，第一设备与接收端可以在初始化阶段或关联阶段通过特定的管理帧协商多个次信道。其中，管理帧包括但不限于关联请求(Association Request)帧和关联响应(Association Response)帧。
在一些实施例中，所述切换到所述第一次信道或第二次信道传输，包括：
感知到所述第一次信道或第二次信道处于空闲状态，在所述第一次信道或第二次信道对未成功传输的QoS数据帧进行重传；
其中，所述未成功传输的QoS数据帧的MAC帧头的retry比特位设置为第一参数值，且未成功传输的QoS数据帧的SN设置值与在所述第一次信道中的设置值相同。
其中，若第一设备感知第一次信道的信道状态为空闲，则在第一次信道对未成功传输的QoS数据帧进行重传，且未成功传输的QoS数据帧的retry比特位设置为第一参数值，例如retry比特位设置为“1”时，标识该QoS数据帧为重传帧；retry比特位设置为“0”时，标识该QoS数据帧不为重传帧。其中，未成功传输的QoS数据帧的SN设置值与其在第一次信道中的SN设置值相同。
其中，若第一设备感知第一设备感知第一次信道的信道状态为繁忙，第二次信道的信道状态为空闲，则在第二次信道对未成功传输的QoS数据帧进行重传，且未成功传输的QoS数据帧的retry比特位设置为第一参数值，例如retry比特位设置为“1”时，标识该QoS数据帧为重传帧；retry比特位设置为“0”时，标识该QoS数据帧不为重传帧。其中，未成功传输的QoS数据帧的SN设置值与其在第一次信道中的SN设置值相同。
作为示例，参见图4，图4示出了本公开实施例的一个可选实现方式，包括以下步骤：
步骤401，在主信道感知的OBSS TXOP时间内，第一设备101在第一次信道进行数据传输。
其中，当主信道处于OBSS繁忙状态时，为了充分利用信道资源，第一设备可切换到第一次信道通信，并在主信道感知的OBSS TXOP时间内进行数据传输，提高系统的吞吐量。
步骤402，所述OBSS TXOP时间结束后，所述第一设备101进行信道状态感知或侦听。
其中，在OBSS TXOP时间结束后，第一设备(AP或STA)在次信道完成数据交互，切换至主信道。在切换至主信道后，第一设备在发送数据前需要侦听主信道上有没有其他数据在传输，例如通过载波侦听机制实现。其中，第一设备在同步时延之后进行信道感知或侦听，即第一设备在切换至主信道后等待一段时间，以确保主信道上没有其他设备的活动，防止在同一时刻多个设备在相同信道上进行侦听导致干扰。
步骤403，在重传信道上向发送所述第一数据帧的接收端102发送请求发送(Request to Send，RTS)帧。
在一些实施例中，为了确保第一数据帧的接收端已切换至主信道或次信道，第一设备在重传信道上向发送第一数据帧的接收端发送未成功传输的QoS数据帧前，先向第一数据帧的接收端发送RTS帧进行检测，以询问第一数据帧的接收端是否已切换至主信道或次信道，并准备好接收QoS数据，提高通信的可靠性。
步骤404，接收到所述第一数据帧的接收端发送清除发送(Clear to Send，CTS)帧，对未成功传输的QoS数据帧进行重传。
在一些实施例中，第一设备在重传信道上接收第一数据帧的接收端回复的CTS帧后，对未成功传输的QoS数据帧进行重传。其中，第一数据帧的接收端回复CTS帧表示接收端已经准备好接收数据，有助于确保QoS数据帧在重传时能够成功传输，提高通信的可靠性。
在一些实施例中，信息等的名称不限定于实施例中所记载的名称，“信息(information)”、“消息(message)”、“信号(signal)”、“信令(signaling)”、“报告(report)”、“配置(configuration)”、“指示(indication)”、“指令(instruction)”、“命令(command)”、“信道”、“参数(parameter)”、“域”、“字段”、“符号(symbol)”、“码点(codepoint)”、“比特(bit)”、“数据(data)”、“程序(program)”、“码片(chip)”等术语可以相互替换。
在一些实施例中，“时刻”、“时间点”、“时间”、“时间位置”等术语可以相互替换，“时长”、“时段”、“时间窗口”、“窗口”、“时间”等术语可以相互替换。
在一些实施例中，无线接入方案(wireless access scheme)、波形(waveform)等术语可以相互替换。
在一些实施例中，“特定(certain)”、“预定(preseted)”、“预设”、“设定”、“指示(indicated)”、“某一”、“任意”、“第一”等术语可以相互替换，“特定A”、“预定A”、“预设A”、“设定A”、“指示A”、“某一A”、“任意A”、“第一A”可以解释为在协议等中预先规定的A，也可以解释为通过设定、配置、或指示等得到的A，也可以解释为特定A、某一A、任意A、或第一A等，但不限于此。
在一些实施例中，判定或判断可以通过以1比特表示的值(0或1)来进行，也可以通过以真(true)或者假(false)表示的真假值(布尔值(boolean))来进行，也可以通过数值的比较(例如，与预定值的比较)来进行，但不限于此。
在一些实施例中，“不期待接收”可以解释为不在时域资源和/或频域资源上接收，也可以解释为在接收到数据等后，不对该数据等执行后续处理；“不期待发送”可以解释为不发送，也可以解释为发送但是不期待接收方对发送的内容做出响应。
本公开实施例所涉及的数据传输方法可以包括前述步骤以及实施例中的至少一者。例如，步骤201可以作为独立实施例来实施，步骤202可以作为独立实施例来实施、步骤203可以作为独立实施例来实施、步骤301可以作为独立实施例来实施、步骤302可以作为独立实施例来实施、步骤303可以作为独立实施例来实施，步骤304可以作为独立实施例来实施、步骤305可以作为独立实施例来实施、步骤401可以作为独立实施例来实施、步骤402可以作为独立实施例来实施、步骤403可以作为独立实施例来实施、步骤404可以作为独立实施例来实施，步骤201与步骤202的结合可以作为独立实施例来实施，步骤202与步骤203的结合可以作为独立实施例来实施，步骤301与步骤302的结合可以作为独立实施例来实施，步骤303与步骤304的结合可以作为独立实施例来实施，步骤304与步骤305的结合可以作为独立实施例来实施，步骤401与步骤402的结合可以作为独立实 施例来实施，步骤403步骤404的结合可以作为独立实施例来实施，但不限于此。
在一些实施例中，可参见图2至图4所对应的说明书之前或之后记载的其他可选实现方式。
图7是根据本公开实施例示出的数据传输方法的流程示意图。
如图7所示，上述方法包括：
步骤701，在主信道感知的重叠基本服务集传输机会OBSS TXOP时间内，第一设备在第一次信道进行数据传输。
可选地，本公开实施例中，所述在主信道感知的OBSS TXOP时间内，第一设备在次信道进行数据传输之前，所述方法包括：
第一设备感知所述主信道繁忙，切换至所述第一次信道传输第一数据帧；其中，所述第一数据帧包括序列号以及传输标识TID；
在所述第一次信道接收所述第一数据帧的接收端反馈的块确认BA帧；其中，所述BA帧包括位图bitmap标识位，标识所述第一数据帧的每个QoS数据帧是否被正确接收。
步骤702，所述OBSS TXOP时间结束后，所述第一设备进行信道状态感知或侦听。
步骤703，根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的服务质量QoS数据帧进行重传。
可选地，本公开实施例中，所述根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的QoS数据帧进行重传，包括：
所述第一设备感知所述主信道的信道状态为空闲，在所述主信道对未成功传输的QoS数据帧进行重传；
其中，所述未成功传输的QoS数据帧的媒体访问控制MAC帧头的retry比特位设置为第一参数值，且未成功传输的QoS数据帧的序列号SN设置值与在所述第一次信道中的设置值相同。
可选地，本公开实施例中，所述在所述主信道对未成功传输的QoS数据帧进行重传，包括：
感知到所述主信道处于OBSS TXOP繁忙状态，切换到所述第一次信道或第二次信道传输；所述第二次信道为所述第一设备与所述第一数据帧的接收端预先协商的。
可选地，本公开实施例中，所述切换到所述第一次信道或第二次信道传输，包括：
感知到所述第一次信道或第二次信道处于空闲状态，在所述第一次信道或第二次信道对未成功传输的QoS数据帧进行重传；
其中，所述未成功传输的QoS数据帧的MAC帧头的retry比特位设置为第一参数值，且未成功传输的QoS数据帧的SN设置值与在所述第一次信道中的设置值相同。
可选地，本公开实施例中，所述对所述OBSS TXOP时间内未成功传输的QoS数据帧进行重传，包括：
在重传信道上向发送所述第一数据帧的接收端发送请求发送RTS帧；
接收到所述第一数据帧的接收端发送清除发送CTS帧，对未成功传输的QoS数据帧进行重传。
本公开实施例所涉及的数据传输方法可以包括前述步骤以及实施例中的至少一者。例如，步骤701可以作为独立实施例来实施，步骤702可以作为独立实施例来实施，步骤703可以作为独立实施例来实施；步骤701与步骤702的结合可以作为独立实施例来实施，步骤702与步骤703的结合可以作为独立实施例来实施，但不限于此。
在一些实施例中，可参见图7所对应的说明书之前或之后记载的其他可选实现方式。
本公开实施例还提出用于实现以上任一方法的装置，例如，提出一装置，上述装置包括用以实现以上任一方法中终端所执行的各步骤的单元或模块。再如，还提出另一装置，包括用以实现以上任一方法中网络设备(例如接入网设备、核心网功能节点、核心网设备等)所执行的各步骤的单元或模块。
应理解以上装置中各单元或模块的划分仅是一种逻辑功能的划分，在实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。此外，装置中的单元或模块可以以处理器调用软件 的形式实现：例如装置包括处理器，处理器与存储器连接，存储器中存储有指令，处理器调用存储器中存储的指令，以实现以上任一方法或实现上述装置各单元或模块的功能，其中处理器例如为通用处理器，例如中央处理单元(Central Processing Unit，CPU)或微处理器，存储器为装置内的存储器或装置外的存储器。或者，装置中的单元或模块可以以硬件电路的形式实现，可以通过对硬件电路的设计实现部分或全部单元或模块的功能，上述硬件电路可以理解为一个或多个处理器；例如，在一种实现中，上述硬件电路为专用集成电路(application-specific integrated circuit，ASIC)，通过对电路内元件逻辑关系的设计，实现以上部分或全部单元或模块的功能；再如，在另一种实现中，上述硬件电路为可以通过可编程逻辑器件(programmable logic device，PLD)实现，以现场可编程门阵列(Field Programmable Gate Array，FPGA)为例，其可以包括大量逻辑门电路，通过配置文件来配置逻辑门电路之间的连接关系，从而实现以上部分或全部单元或模块的功能。以上装置的所有单元或模块可以全部通过处理器调用软件的形式实现，或全部通过硬件电路的形式实现，或部分通过处理器调用软件的形式实现，剩余部分通过硬件电路的形式实现。
在本公开实施例中，处理器是具有信号处理能力的电路，在一种实现中，处理器可以是具有指令读取与运行能力的电路，例如中央处理单元(Central Processing Unit，CPU)、微处理器、图形处理器(graphics processing unit，GPU)(可以理解为微处理器)、或数字信号处理器(digital signal processor，DSP)等；在另一种实现中，处理器可以通过硬件电路的逻辑关系实现一定功能，上述硬件电路的逻辑关系是固定的或可以重构的，例如处理器为专用集成电路(application-specific integrated circuit，ASIC)或可编程逻辑器件(programmable logic device，PLD)实现的硬件电路，例如FPGA。在可重构的硬件电路中，处理器加载配置文档，实现硬件电路配置的过程，可以理解为处理器加载指令，以实现以上部分或全部单元或模块的功能的过程。此外，还可以是针对人工智能设计的硬件电路，其可以理解为ASIC，例如神经网络处理单元(Neural Network Processing Unit，NPU)、张量处理单元(Tensor Processing Unit，TPU)、深度学习处理单元(Deep learning Processing Unit，DPU)等。
图8是本公开实施例提出的第一设备的结构示意图。如图8所示，第一设备800可以包括：第一处理模块801、第二处理模块802、第三处理模块803中的至少一者。
在一些实施例中，上述第一处理模块801，用于在主信道感知的OBSS TXOP时间内，在第一次信道进行数据传输。上述第二处理模块802，用于所述OBSS TXOP时间结束后，进行信道状态感知或侦听。上述第三处理模块803，用于根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的服务质量QoS数据帧进行重传。
可选地，上述第一处理模块801用于执行以上任一方法中第一设备101执行的通信步骤(例如步骤201、步骤303、步骤401、步骤701，但不限于此)中的至少一者，此处不再赘述。第二处理模块802用于执行步骤202、步骤304、步骤402、步骤702中的至少一者。第三处理模块803用于执行执行步骤203、步骤305、步骤703中的至少一者。
图9是本公开实施例提出的终端900(例如用户设备等)的结构示意图。终端900可以是支持网络设备实现以上任一方法的芯片、芯片系统、或处理器等，还可以是支持终端实现以上任一方法的芯片、芯片系统、或处理器等。终端900可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
如图9所示，终端900包括一个或多个处理器901。处理器901可以是通用处理器或者专用处理器等，例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行程序，处理程序的数据。终端900用于执行以上任一方法。
在一些实施例中，终端900还包括用于存储指令的一个或多个存储器902。可选地，全部或部分存储器902也可以处于终端900之外。
在一些实施例中，终端900还包括一个或多个收发器904。在终端900包括一个或多个收发器904时，收发器904执行上述方法中的发送和/或接收等通信步骤(例如步骤201、步骤203、步骤301、步骤302、步骤303、步骤305、步骤401、步骤403、步骤404、步骤701、步骤703，但不限于此)中的至少一者，处理器901执行其他步骤(例如步骤202、步骤304、步骤402、步骤702，但不限于此)中的至少一者。
在一些实施例中，收发器可以包括接收器和/或发送器，接收器和发送器可以是分离的，也可以集成在一起。可选地，收发器、收发单元、收发机、收发电路等术语可以相互替换，发送器、发送单元、发送机、发送电路等术语可以相互替换，接收器、接收单元、接收机、接收电路等术语可以 相互替换。
在一些实施例中，终端900可以包括一个或多个接口电路903。可选地，接口电路903与存储器902连接，接口电路903可用于从存储器902或其他装置接收信号，可用于向存储器902或其他装置发送信号。例如，接口电路903可读取存储器902中存储的指令，并将该指令发送给处理器901。
以上实施例描述中的终端900可以是用户设备等通信设备，但本公开中描述的终端900的范围并不限于此，终端900的结构可以不受图9的限制。通信设备可以是独立的设备或者可以是较大设备的一部分。例如所述通信设备可以是：(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；(2)具有一个或多个IC的集合，可选地，上述IC集合也可以包括用于存储数据，程序的存储部件；(3)ASIC，例如调制解调器(Modem)；(4)可嵌入在其他设备内的模块；(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；(6)其他等等。
图10是本公开实施例提出的芯片1000的结构示意图。对于终端900可以是芯片或芯片系统的情况，可以参见图10所示的芯片1000的结构示意图，但不限于此。
芯片1000包括一个或多个处理器1001，芯片1000用于执行以上任一方法。
在一些实施例中，芯片1000还包括一个或多个1003。可选地，接口电路1003与存储器1002连接，接口电路1003可以用于从存储器1002或其他装置接收信号，接口电路1003可用于向存储器1002或其他装置发送信号。例如，接口电路1003可读取存储器1002中存储的指令，并将该指令发送给处理器1001。
在一些实施例中，接口电路1003执行上述方法中的发送和/或接收等通信步骤(例如步骤201、步骤203、步骤301、步骤302、步骤303、步骤305、步骤401、步骤403、步骤404、步骤701、步骤703，但不限于此)中的至少一者，处理器1001执行其他步骤(例如步骤202、步骤304、步骤402、步骤702，但不限于此)中的至少一者。
在一些实施例中，接口电路、接口、收发管脚、收发器等术语可以相互替换。
在一些实施例中，芯片1000还包括用于存储指令的一个或多个存储器1002。可选地，全部或部分存储器1002可以处于芯片1000之外。
本公开还提出存储介质，上述存储介质上存储有指令，当上述指令在终端900上运行时，使得终端900执行以上任一方法。可选地，上述存储介质是电子存储介质。可选地，上述存储介质是计算机可读存储介质，但不限于此，其也可以是其他装置可读的存储介质。可选地，上述存储介质可以是非暂时性(non-transitory)存储介质，但不限于此，其也可以是暂时性存储介质。
本公开还提出程序产品，上述程序产品被终端900执行时，使得终端900执行以上任一方法。可选地，上述程序产品是计算机程序产品。
本公开还提出计算机程序，当其在计算机上运行时，使得计算机执行以上任一方法。

Claims (10)

  1. 一种数据传输方法，其特征在于，所述方法包括：
    在主信道感知的重叠基本服务集传输机会OBSS TXOP时间内，第一设备在第一次信道进行数据传输；
    所述OBSS TXOP时间结束后，所述第一设备进行信道状态感知或侦听；
    根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的服务质量QoS数据帧进行重传。
  2. 根据权利要求1所述的数据传输方法，其特征在于，所述在主信道感知的OBSS TXOP时间内，第一设备在次信道进行数据传输之前，所述方法包括：
    第一设备感知所述主信道繁忙，切换至所述第一次信道传输第一数据帧；其中，所述第一数据帧包括序列号SN以及传输标识TID；
    在所述第一次信道接收所述第一数据帧的接收端反馈的块确认BA帧；其中，所述BA帧包括位图bitmap标识位，标识所述第一数据帧的每个QoS数据帧是否被正确接收。
  3. 根据权利要求2所述的数据传输方法，其特征在于，所述根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的QoS数据帧进行重传，包括：
    所述第一设备感知所述主信道的信道状态为空闲，在所述主信道对未成功传输的QoS数据帧进行重传；
    其中，所述未成功传输的QoS数据帧的媒体访问控制MAC帧头的retry比特位设置为第一参数值，且未成功传输的QoS数据帧的序列号SN设置值与在所述第一次信道中的设置值相同。
  4. 根据权利要求3所述的数据传输方法，其特征在于，所述在所述主信道对未成功传输的QoS数据帧进行重传，包括：
    感知到所述主信道处于OBSS TXOP繁忙状态，切换到所述第一次信道或第二次信道传输；所述第二次信道为所述第一设备与所述第一数据帧的接收端预先协商的。
  5. 根据权利要求4所述的数据传输方法，其特征在于，所述切换到所述第一次信道或第二次信道传输，包括：
    感知到所述第一次信道或第二次信道处于空闲状态，在所述第一次信道或第二次信道对未成功传输的QoS数据帧进行重传；
    其中，所述未成功传输的QoS数据帧的MAC帧头的retry比特位设置为第一参数值，且未成功传输的QoS数据帧的SN设置值与在所述第一次信道中的设置值相同。
  6. 根据权利要求2至5中任一项所述的数据传输方法，其特征在于，所述对所述OBSS TXOP时间内未成功传输的QoS数据帧进行重传，包括：
    在重传信道上向发送所述第一数据帧的接收端发送请求发送RTS帧；
    接收到所述第一数据帧的接收端发送清除发送CTS帧，对未成功传输的QoS数据帧进行重传。
  7. 一种通信设备，所述通信设备为第一设备，所述第一设备为站点设备或接入点设备，所述第一设备包括：
    第一处理模块，用于在主信道感知的OBSS TXOP时间内，在第一次信道进行数据传输；
    第二处理模块，用于所述OBSS TXOP时间结束后，进行信道状态感知或侦听；
    第三处理模块，用于根据所感知的信道状态，对所述OBSS TXOP时间内未成功传输的服务质量QoS数据帧进行重传。
  8. 一种通信设备，所述通信设备为第一设备，所述第一设备为站点设备或接入点设备，其特征在于，包括：
    一个或多个处理器；
    其中，所述第一设备用于执行权利要求1至6中任一项所述的数据传输方法。
  9. 一种通信系统，其特征在于，包括第一设备，所述第一设备为站点设备或接入点设备；其中， 所述第一设备被配置为实现权利要求1至6中任一项所述的数据传输方法。
  10. 一种存储介质，所述存储介质存储有指令，其特征在于，当所述指令在通信设备上运行时，使得所述通信设备执行如权利要求1至6中任一项所述的数据传输方法。
PCT/CN2024/075017 2024-01-31 2024-01-31 数据传输方法、通信设备及通信系统 Pending WO2025160822A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202480000325.1A CN120731568A (zh) 2024-01-31 2024-01-31 数据传输方法、通信设备及通信系统
PCT/CN2024/075017 WO2025160822A1 (zh) 2024-01-31 2024-01-31 数据传输方法、通信设备及通信系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/075017 WO2025160822A1 (zh) 2024-01-31 2024-01-31 数据传输方法、通信设备及通信系统

Publications (1)

Publication Number Publication Date
WO2025160822A1 true WO2025160822A1 (zh) 2025-08-07

Family

ID=96589095

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/075017 Pending WO2025160822A1 (zh) 2024-01-31 2024-01-31 数据传输方法、通信设备及通信系统

Country Status (2)

Country Link
CN (1) CN120731568A (zh)
WO (1) WO2025160822A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105393589A (zh) * 2013-09-29 2016-03-09 华为技术有限公司 一种数据传输的方法及设备
CN105813094A (zh) * 2016-04-08 2016-07-27 西安电子科技大学 无线局域网中txop机制冗余nav的截短方法
CN111787626A (zh) * 2015-12-08 2020-10-16 华为技术有限公司 一种数据传输保护方法及其装置
WO2020225473A1 (en) * 2019-05-07 2020-11-12 Nokia Technologies Oy Shared transmission opportunity
CN114258148A (zh) * 2020-09-21 2022-03-29 华为技术有限公司 无线局域网中的信道接入方法及相关装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105393589A (zh) * 2013-09-29 2016-03-09 华为技术有限公司 一种数据传输的方法及设备
CN111787626A (zh) * 2015-12-08 2020-10-16 华为技术有限公司 一种数据传输保护方法及其装置
CN105813094A (zh) * 2016-04-08 2016-07-27 西安电子科技大学 无线局域网中txop机制冗余nav的截短方法
WO2020225473A1 (en) * 2019-05-07 2020-11-12 Nokia Technologies Oy Shared transmission opportunity
CN114258148A (zh) * 2020-09-21 2022-03-29 华为技术有限公司 无线局域网中的信道接入方法及相关装置

Also Published As

Publication number Publication date
CN120731568A (zh) 2025-09-30

Similar Documents

Publication Publication Date Title
WO2025160822A1 (zh) 数据传输方法、通信设备及通信系统
WO2025166635A1 (zh) 设备省电管理方法、通信设备及通信系统
WO2025147913A1 (zh) 通信方法、通信设备及通信系统
WO2025160760A1 (zh) 信道控制方法、通信设备及通信系统
WO2025081385A1 (zh) 通信方法、接入点设备、第一站点设备及第二站点设备
WO2025086066A1 (zh) 媒介同步恢复方法、站点设备及接入点设备
WO2025156204A1 (zh) 通信方法、接入点设备及通信系统
WO2025086068A1 (zh) 通信方法、站点设备、接入点设备及通信系统
WO2025039123A1 (zh) 通信方法、接入点设备、站点设备及通信系统
WO2025160759A1 (zh) 通信方法、通信设备及通信系统
WO2025076654A1 (zh) 通信方法、接入点设备及站点设备
WO2025145287A1 (zh) 通信方法、通信设备及通信系统
WO2025039126A1 (zh) 通信方法、接入点设备、站点设备及通信设备
WO2025138175A1 (zh) 多ap协调方法、接入点设备及通信系统
WO2025189431A1 (zh) 数据帧传输方法、通信设备、站点设备及通信系统
WO2025076664A1 (zh) 低时延业务传输方法、通信设备以及通信系统
WO2025086070A1 (zh) 中继重传的方法和设备及通信系统
WO2025030509A1 (zh) 信道切换方法、接入点设备、站点设备及通信系统
WO2025086071A1 (zh) 中继重传的方法和设备及通信系统
WO2025102373A1 (zh) 通信方法、站点设备、接入点设备及通信系统
WO2025086101A1 (zh) 数据中继传输方法、通信设备及通信系统
WO2026000355A1 (zh) 通信方法、站点设备、接入点设备及通信系统
WO2025035364A1 (zh) 通信方法、接入点设备、站点设备及通信设备
WO2025184868A1 (zh) 通信方法、站点设备、接入点设备及通信系统
WO2025147914A1 (zh) 通信方法、通信设备及通信系统

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202480000325.1

Country of ref document: CN

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

Ref document number: 24920892

Country of ref document: EP

Kind code of ref document: A1

WWP Wipo information: published in national office

Ref document number: 202480000325.1

Country of ref document: CN