WO2024250239A1 - 无线通信的方法、发送端设备和接收端设备 - Google Patents

无线通信的方法、发送端设备和接收端设备 Download PDF

Info

Publication number
WO2024250239A1
WO2024250239A1 PCT/CN2023/099195 CN2023099195W WO2024250239A1 WO 2024250239 A1 WO2024250239 A1 WO 2024250239A1 CN 2023099195 W CN2023099195 W CN 2023099195W WO 2024250239 A1 WO2024250239 A1 WO 2024250239A1
Authority
WO
WIPO (PCT)
Prior art keywords
field
uhr
identification
ppdu
sig
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.)
Ceased
Application number
PCT/CN2023/099195
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.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp 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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to CN202380098981.5A priority Critical patent/CN121336481A/zh
Priority to PCT/CN2023/099195 priority patent/WO2024250239A1/zh
Publication of WO2024250239A1 publication Critical patent/WO2024250239A1/zh
Priority to US19/406,913 priority patent/US20260089245A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • 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 signalling, i.e. of overhead other than pilot signals
    • 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/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/323—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the physical layer [OSI layer 1]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames

Definitions

  • the embodiments of the present application relate to the field of communications, and specifically to a perception method, a transmitting device, and a receiving device.
  • multi-user detection can be achieved through null data physical layer protocol data unit (NDP) feedback report polling (NDP Feedback Report Poll, NFRP) and high efficiency (HE) trigger frame (TB) based feedback NDP (HE TB feedback NDP).
  • NDP null data physical layer protocol data unit
  • NFRP NDP Feedback Report Poll
  • HE high efficiency trigger frame
  • the access point device sends NFRP frames to one or more site devices, triggering the site devices to send HE TB feedback NDP.
  • the access point device parses the HE TB feedback NDP to learn the site devices that need to participate in the subsequent multi-user uplink transmission, and then reasonably allocates resources to these site devices in the subsequent trigger frames, thereby completing the multi-user uplink transmission.
  • the present application provides a wireless communication method, a transmitting device and a receiving device, which are conducive to improving the flexibility of multi-user detection.
  • a method for wireless communication comprising: a transmitting device sends an ultra-high reliability UHR physical layer protocol data unit PPDU, the UHR PPDU includes an identification field, and the identification field is used to indicate identification information of the transmitting device.
  • a method for wireless communication comprising: a receiving device receives one or more ultra-high reliability UHR physical layer protocol data units PPDU, the UHR PPDU includes an identification field, and the identification field is used to indicate identification information of a sending device of the UHR PPDU.
  • a transmitting end device for executing the method in the above-mentioned first aspect or its various implementation modes.
  • the sending end device includes a functional module for executing the method in the above-mentioned first aspect or its various implementation modes.
  • a receiving device for executing the method in the above-mentioned second aspect or its various implementation modes.
  • the receiving end device includes a functional module for executing the method in the above-mentioned second aspect or its various implementation modes.
  • a transmitting end device comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its implementation manners.
  • a receiving end device comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect or its implementation manner.
  • a chip for implementing the method in any one of the first to second aspects or their respective implementations.
  • the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method in any one of the first to second aspects or their respective implementations.
  • a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to second aspects or any of their implementations.
  • a computer program product comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above or in each of their implementations.
  • a computer program which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects or in each of their implementations.
  • the receiving device can identify the identity of the sending device through the identification field in the UHR PPDU sent by the sending device, so as to realize MU detection. Therefore, it is not necessary to bind with the NFRP Trigger frame.
  • MU detection can be completed through the identification field in a certain uplink or downlink UHR PPDU, thereby expanding the use time and scenario of MU detection, improving the flexibility of MU detection, and realizing the function of multi-user detection in different scenarios. .
  • FIG1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.
  • Figure 2 is a schematic diagram of the format of an EHT MU PPDU.
  • Figure 3 is a schematic diagram of the format of an EHT TB PPDU.
  • Figure 4 is a schematic diagram of the MU UL uplink detection process.
  • Figure 5 is a schematic frame format diagram of an NFRP Trigger frame.
  • Figure 6 is a format diagram of the Common Info field in the NFRP Trigger frame.
  • Figure 7 is a format diagram of the User Info List field in the NFRP Trigger frame.
  • FIG8 shows a format of HE TB feedback NDP.
  • FIG. 9 is a schematic interaction diagram of a wireless communication method 200 according to an embodiment of the present application.
  • FIG 10 is a schematic format diagram of a UHR MU PPDU or UHR ER PPDU carrying an identification field provided according to an embodiment of the present application.
  • FIG 11 is a schematic format diagram of a UHR TB PPDU carrying an identification field provided according to an embodiment of the present application.
  • Figure 12 is a schematic format diagram of a UHR MU PPDU or UHR ER PPDU carrying an identification field and a conversion time field provided according to an embodiment of the present application.
  • Figure 13 is a schematic format diagram of a UHR TB PPDU carrying an identification field and a conversion time field provided according to an embodiment of the present application.
  • Figure 14 is a schematic format diagram of another UHR MU PPDU or UHR ER PPDU carrying an identification field provided according to an embodiment of the present application.
  • FIG. 15 is a schematic format diagram of another UHR TB PPDU carrying an identification field provided according to an embodiment of the present application.
  • FIG 16 is a schematic format diagram of another UHR MU PPDU or UHR ER PPDU carrying an identification field and a conversion time field provided according to an embodiment of the present application.
  • FIG 17 is a schematic format diagram of another UHR TB PPDU carrying an identification field and a conversion time field provided according to an embodiment of the present application.
  • FIG18 is a schematic format diagram of an identification field provided according to an embodiment of the present application.
  • FIG. 19 is a schematic format diagram of another identification field provided according to an embodiment of the present application.
  • FIG20 is a schematic format diagram of another identification field provided according to an embodiment of the present application.
  • FIG. 21 is a schematic format diagram of another identification field provided according to an embodiment of the present application.
  • Figure 22 is a schematic format diagram of another identification field provided according to an embodiment of the present application.
  • Figure 23 is a schematic format diagram of control information of carrying an identification field through the U-SIG field of the UHR MU PPDU provided according to an embodiment of the present application.
  • Figure 24 is a schematic format diagram of the control information of carrying the identification field through the U-SIG field of the UHR TB PPDU provided according to an embodiment of the present application.
  • Figure 25 is a schematic format diagram of the control information of carrying the identification field through the U-SIG field of the UHR ER PPDU provided according to an embodiment of the present application.
  • Figure 26 is a schematic format diagram of control information of carrying an identification field through the Common field in the UHR-SIG field of the UHR TB PPDU provided according to an embodiment of the present application.
  • Figures 27 to 34 are flow charts of PHY receiving PPDU of a receiving device according to an embodiment of the present application.
  • 35 to 40 are schematic diagrams of usage scenarios of the MU detection method according to an embodiment of the present application.
  • Figure 41 is a schematic block diagram of a transmitting end device provided according to an embodiment of the present application.
  • Figure 42 is a schematic block diagram of a receiving device provided according to an embodiment of the present application.
  • Figure 43 is a schematic block diagram of a communication device provided according to an embodiment of the present application.
  • Figure 44 is a schematic block diagram of a chip provided according to an embodiment of the present application.
  • Figure 45 is a schematic block diagram of a communication system provided according to an embodiment of the present application.
  • WLAN Wireless Local Area Networks
  • WiFi Wireless Fidelity
  • the communication system 100 may include an access point (AP) 110 and a station (STA) 120 that accesses a network through the access point 110.
  • AP access point
  • STA station
  • AP is also called AP STA, which means that in a sense, AP is also a STA.
  • STA is also called non-AP STA.
  • the communication in the communication system 100 may be communication between an AP and a non-AP STA, communication between a non-AP STA and a non-AP STA, or communication between a STA and a peer STA, wherein a peer STA may refer to a device that communicates with a STA on a peer-to-peer basis, for example, a peer STA may be an AP or a non-AP STA.
  • AP is equivalent to a bridge connecting wired network and wireless network. Its main function is to connect various wireless network clients together and then connect the wireless network to Ethernet.
  • AP devices can be terminal devices with WiFi chips (such as mobile phones) or network devices (such as routers).
  • the role of STA in the communication system is not absolute.
  • the mobile phone when a mobile phone is connected to a router, the mobile phone is a non-AP STA.
  • the mobile phone plays the role of an AP.
  • APs and non-AP STAs can be devices used in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.
  • IoT Internet of Things
  • non-AP STA can support 802.11be.
  • Non-AP STA can also support various current and future 802.11 family wireless local area networks (WLAN) standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.
  • WLAN wireless local area networks
  • the AP may be a device supporting the 802.11be standard.
  • the AP may also be a device supporting various current and future 802.11 family WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.
  • STA can be a mobile phone (Mobile Phone), tablet computer (Pad), computer, virtual reality (VR) device, augmented reality (AR) device, wireless device in industrial control (industrial control), set-top box, wireless device in self-driving, vehicle-mounted communication equipment, wireless device in remote medical, wireless device in smart grid (smart grid), wireless device in transportation safety (transportation safety), wireless device in smart city (smart city) or wireless device in smart home (smart home), wireless communication chip/ASIC/SOC/etc. that supports WLAN or WiFi technology.
  • the frequency bands supported by WLAN technology may include but are not limited to: low frequency bands (eg, 2.4 GHz, 5 GHz, 6 GHz) and high frequency bands (eg, 60 GHz).
  • low frequency bands eg, 2.4 GHz, 5 GHz, 6 GHz
  • high frequency bands eg, 60 GHz
  • Figure 1 exemplarily shows an AP STA and two non-AP STAs.
  • the communication system 100 may include multiple AP STAs and other numbers of non-AP STAs, which is not limited to the embodiments of the present application.
  • the device with communication function in the network/system in the embodiment of the present application can be called a communication device.
  • the communication device may include an access point 110 and a site 120 with communication function, and the access point 110 and the site 120 may be the specific devices described above, which will not be repeated here; the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller and a gateway, which is not limited in the embodiment of the present application.
  • the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.
  • corresponding may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.
  • pre-defined can be implemented by pre-storing corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including access points and stations), and the present application does not limit the specific implementation method.
  • pre-defined can refer to what is defined in the protocol.
  • Association Identifier (AID) is used to identify the terminal after it establishes an association with an access point.
  • Unassociation Identifier is used to identify terminals that are not associated with an access point.
  • MAC Media Access Control
  • Transmission Opportunity refers to a period of time during which a terminal with the transmission opportunity can actively initiate one or more transmissions.
  • EHT extremely high throughput
  • IEEE 802.11be defines two types of EHT PPDU in EHT PHY: EHT multi-user (MU) PPDU and EHT trigger-based PPDU.
  • FIG. 2 is a schematic diagram of the format of an EHT MU PPDU. As shown in Figure 2, the EHT MU PPDU may include the following fields:
  • L-STF Legacy Short Training field
  • L-LTF Legacy Long Training field
  • Legacy SIGNAL field (L-SIG), a variable waveform, is used to carry the information required to parse the PPDU;
  • L-SIG Repeated L-SIG is a repetition of L-SIG.
  • U-SIG Universal Signal field
  • the EHT-SIG field (EHT SIGNAL field), a variable waveform, is used to carry information related to downlink (DL) MU transmission.
  • EHT-STF EHT Short Training field
  • fixed waveform used for receiver automatic gain control.
  • EHT-LTF EHT Long Training field
  • Data field variable waveform, used to carry data.
  • the Packet Extension (PE) field a variable waveform, is used to extend the duration of the PPDU, leaving more processing and response time for the receiver.
  • FIG. 3 is a schematic diagram of the format of an EHT TB PPDU. Unlike the EHT MU PPDU, the EHT TB PPDU does not include the EHT-SIG field, and the meanings of other fields are similar to those of the corresponding fields in the EHT MU PPDU.
  • NDP null data physical layer protocol data unit
  • a MU UL detection mechanism is defined in IEEE 802.11ax, which enables the AP to detect Non-AP STAs that need to allocate resources before sending Trigger frames.
  • the MU UL detection mechanism in IEEE 802.11ax also defines two related frame structures: NDP Feedback Report Poll (NFRP) Trigger frame and High Efficiency (HE) TB feedback NDP.
  • NFRP NDP Feedback Report Poll
  • HE High Efficiency
  • FIG 4 is a schematic diagram of the MU UL uplink detection process.
  • the AP sends a NFRP Trigger frame to one or more Non-AP STAs, triggering the Non-AP STAs to send HE TB feedback NDP.
  • the AP can learn which Non-AP STAs need to participate in the subsequent MU UL transmission by parsing the HE TB feedback NDP, and then reasonably allocate resources to these Non-AP STAs in the subsequent Trigger frames, thereby completing the MU UL transmission.
  • FIG5 is a schematic frame format diagram of an NFRP Trigger frame.
  • FIG6 is a format diagram of the Common Info field in the NFRP Trigger frame.
  • the uplink bandwidth (UL BW) field indicates the bandwidth of the NDP feedback report response.
  • the uplink space-time block code (STBC), LDPC Extra Symbol Segment, Pre-Forward Error Correction (Pre-FEC) padding factor (Pre-FEC Padding Factor), PE disambiguation (PE disambiguity), uplink spatial reuse (UL Spatial Reuse) and Doppler (Doppler) fields are reserved.
  • the Number Of HE-LTF Symbols and Midamble Periodicity field indicates the number of HE-LTF symbols present in the NDP feedback report response and is set to 1.
  • the Guard Interval (GI) and HE-LTF Type (GI And HE-LTF Type) fields are set to 2.
  • Figure 7 is a schematic diagram of the format of the User Info List field in the NFRP Trigger frame, where the first AID (Staring AID) field defines the first AID in the AID range that is planned to respond to the NFRP trigger frame.
  • first AID Starting AID
  • Feedback Type field indicates the type of feedback information carried by HE TB feedback NDP.
  • Uplink Target Receive Power field Indicates the expected received signal power measured at the AP's antenna connector and averaged over the antenna.
  • Number of Spatially Multiplexed Users field indicates the number of STAs multiplexed on the same group of subcarriers in the same RU, encoded as the number of STAs - 1.
  • HE TB feedback NDP is used to carry NDP feedback report information.
  • Figure 8 shows a format of HE TB feedback NDP. Among them, different RU_TONE_SET_INDEX in the HE-LTF field is used to identify the AID and feedback information (FEEDBACK_STATUS) of different Non-AP STAs. The specific corresponding relationship is shown in Table 1.
  • Table 1 HE-LTF subcarrier mapping relationship table in HE TB feedback NDP
  • HELTF k is the value of the general HE-LTF sequence on subcarrier k;
  • the capable subcarriers corresponding to a user constitute a subcarrier set.
  • a subcarrier set can correspond to a subcarrier set index, namely, RU_TONE_SET_INDEX.
  • the subcarrier sets ⁇ –113,–77,–41,6,42,78 ⁇ , ⁇ –112,–76,–40,7,43,79 ⁇ in Table 1 all correspond to a subcarrier set index, namely, a RU_TONE_SET_INDEX.
  • a Non-AP STA such as AID
  • the subcarrier mapping relationship of 20MHz is expanded by 1 times and 3 times respectively, so that more Non-AP STAs (AIDs) can be mapped.
  • the 20MHz subcarrier mapping relationship is expanded by 1 times and 3 times respectively, so that more Non-AP STAs (AIDs) can be mapped.
  • each RU_TONE_SET_INDEX corresponds to two Non-AP STAs (AIDs), and these two Non-AP STAs are distinguished by different pre-assigned precoding matrices.
  • the PE field is at the end of the PPDU and is used to provide additional receive processing time.
  • the PE field if present, should be transmitted at the same average power as the data field and should not cause significant power leakage outside the spectrum used by the data field. Other than this, the contents of the PE field are arbitrary.
  • the possible values of the PE field in HE PPDU are: 0, 4, 8, 12, 16 ⁇ s.
  • the possible values of the PE field in the EHT PPDU are: 0, 4, 8, 12, 16, 20 ⁇ s.
  • the PE field with a duration of 20 ⁇ s is only used in the following cases:
  • At least one participating STA uses EHT MU PPDU modulated with 4096-QAM;
  • EHT MU PPDU greater than 2 ⁇ 996tones in the allocated Resource Unit (RU) or Multiple RU (MRU);
  • the duration of the PE field is determined by the pre-FEC filling factor value in the last orthogonal frequency-division multiplexing (OFDM) symbol of the Data field and the transmit vector (TXVECTOR) parameter NOMINAL_PACKET_PADDING.
  • OFDM orthogonal frequency-division multiplexing
  • the method for selecting the duration of the PE field in HE PPDU and EHT PPDU can be as shown in Tables 2 and 3.
  • Table 2 HE PE value table
  • an OFDM symbol can contain multiple subcarriers in the frequency domain, some of which are data subcarriers used to carry data, some are pilot subcarriers used for phase and frequency tracking, and some are unused subcarriers, including DC subcarriers, guard subcarriers, and null subcarriers.
  • the number, position, and content of pilot subcarriers in an OFDM symbol of a specific RU size can be is predefined.
  • Table 4 Location of pilot subcarriers in 242-tone RU
  • the pilot mapping matrix used by the pilot subcarrier on the nth symbol is Determined according to the following formula (1):
  • mod means modulus
  • the pilot mapping matrix used by the subcarriers on the nth symbol is Determine according to the following formula (2):
  • mod means modulus
  • the pilot mapping matrix used by the subcarrier on the nth symbol is determined according to the following formula (3):
  • mod means modulus
  • the pilot mapping matrix used by the subcarrier on the nth symbol is determined according to the following formula (4):
  • mod means modulus
  • the pilot mapping matrix used by the subcarrier on the nth symbol is determined according to the following formula (5):
  • mod means modulus
  • the pilot mapping matrix used by the pilot subcarrier in each OFDM symbol is different, and the subscript of the pilot mapping matrix used is increased as the number of symbols n increases, and the subscript of the pilot mapping matrix is used cyclically.
  • HE TB feedback NDP must be used in combination with NFRP Trigger frame within AP's TXOP, that is, AP must take the lead to complete the MU UL detection function, and Non-AP STA can only cooperate passively. This limits the timing of using the MU UL detection function. If the AP cannot compete for the TXOP in time, or the TXOP is occupied by other Non-AP STAs or APs, the MU UL detection cannot be completed in time, resulting in the inability to perform MU UL transmission in time, causing a large average delay jitter for the uplink service.
  • FIG. 9 is a schematic interaction diagram of a wireless communication method 200 according to an embodiment of the present application. As shown in FIG. 9 , the method 200 includes the following contents:
  • one or more transmitting devices send a UHR PPDU, which includes an identification field, which is used to indicate the identification information (or identity information) of the transmitting device of the UHR PDDU (for example, the AID, UID or MAC address of the transmitting device), or in other words, the identification field is used by the receiving device to identify the transmitting device.
  • an identification field which is used to indicate the identification information (or identity information) of the transmitting device of the UHR PDDU (for example, the AID, UID or MAC address of the transmitting device), or in other words, the identification field is used by the receiving device to identify the transmitting device.
  • the receiving device can receive UHR PPDU sent by one or more sending devices, and identify the sending devices of the one or more UHR PPDUs according to the identification field in the UHR PPDU.
  • the receiving device identifies the transmitting device of the UHR PPDU through the identification field in the received UHR PPDU, that is, the receiving device identifies the transmitting device at the physical layer.
  • the UHR PPDU can be used in a MU detection scenario, or in other words, the identification field is used for MU detection.
  • the receiving device can identify the transmitting device through the identification field in the UHR PPDU sent by the transmitting device, thereby knowing that the transmitting device has a transmission requirement. Or detect UHR PDDUs from different sending devices.
  • the transmitting device may be an access point device, and the receiving device may be a station device.
  • the embodiment of the present application can be used for UL MU detection. That is, the access point device can identify or detect different site devices according to the identification field.
  • a site device can send a UHR PPDU to an access point device.
  • the UHR PPDU includes an identification field for indicating the identification information of the site device.
  • the access point device can identify the site device by parsing the UHR PPDU, thereby learning that the site device has an uplink transmission requirement. Furthermore, the access point device can allocate resources to the site device with an uplink transmission requirement, thereby completing MU UL transmission.
  • the transmitting device may be a station device, and the receiving device may be an access point device.
  • the embodiment of the present application can be used for DL MU detection. That is, the site device can identify or detect different access point devices according to the identification field.
  • the access point device can send a UHR PPDU to the site device.
  • the UHR PPDU includes an identification field for indicating the identification information of the access point device.
  • the site device can identify the access point device by parsing the UHR PPDU, thereby knowing that the access point device has a downlink transmission requirement.
  • the UHR PPDU may be a PPDU used to carry data to be transmitted.
  • the transmitting device may carry an identification field in the PPDU carrying the data to be transmitted to indicate its own identification information, thereby realizing MU detection.
  • the receiving device can implement MU detection by receiving the identification field in the PPDU (which can be an uplink PPDU or a downlink PPDU) carrying the data to be transmitted. Therefore, when the receiving device does not obtain a TXOP, MU detection can also be implemented by receiving the PPDU carrying data, which expands the use time and scenarios of MU detection, increases the flexibility of MU detection, and can implement the MU detection function in different scenarios.
  • PPDU which can be an uplink PPDU or a downlink PPDU
  • MU detection can also be implemented by receiving the PPDU carrying data, which expands the use time and scenarios of MU detection, increases the flexibility of MU detection, and can implement the MU detection function in different scenarios.
  • the identification field is an optional field.
  • the UHR PPDU sent by the transmitting device may carry the identification field.
  • the UHR PPDU may not carry the identification field.
  • the UHR PPDU when MU detection based on the UHR PPDU carrying the identification field is enabled, the UHR PPDU carries the identification field; otherwise, the UHR PPDU does not carry the identification field.
  • the duration of the identification field is a fixed value.
  • the duration of the identification field can be an integer value greater than 0, such as 12, 16, 20, 24, 28, 32 ⁇ s, etc.
  • the duration of the identification field is variable, for example, by indicating the duration of the identification field in other fields in the UHR PPDU.
  • the average power used to transmit the identification field is the same as the average power used to transmit the data field in the UHR PPDU. That is, the identification field needs to be transmitted at the same average power as the data field.
  • the power used to transmit the identification field should not cause significant power leakage outside the spectrum used by the data field.
  • the identification field may explicitly indicate identification information of the sending device.
  • the identification field may carry the AID, UID or MAC address of the sending device or other identification that can identify the identity of the sending device.
  • the identification field may also implicitly indicate the identification information of the transmitting end device.
  • the resource used to transmit the identification field is used to implicitly indicate the identification information of the transmitting end device.
  • the subcarrier used to transmit the identification field is used to indicate the identification information of the transmitting end device.
  • the transmitting device can indicate the identification information of the transmitting device by sending the subcarrier set used for the identification field.
  • the receiving device can determine the identification information of the transmitting device based on the subcarrier set of the received identification field. For example, the receiving device can determine the transmitting device that sent the identification field by detecting which subcarriers have energy and/or the value of the subcarriers with energy in the identification field of the UHR PPDU.
  • the subcarrier set may be indicated by RU_TONE_SET_INDEX, and each RU_TONE_SET_INDEX corresponds to identification information of a transmitting end device, such as an AID.
  • the correspondence between the identification information of the transmitting end device and the subcarrier set is predefined.
  • the number of subcarriers that may be included in a subcarrier set is greater than 1 and does not exceed the total number of subcarriers.
  • one transmitting end device may correspond to one subcarrier set or multiple subcarrier sets, such as 2 subcarrier sets.
  • the identification field is represented by different subcarriers in the multiple subcarrier sets.
  • the carrier set transmission can indicate different status information of the transmitting end device. Therefore, when a transmitting end device corresponds to multiple subcarrier sets, the subcarrier set used by the transmission identification field can be used to indicate the status information of the transmitting end device in addition to the identification information of the transmitting end device.
  • the first transmitting device corresponds to a first subcarrier set (corresponding to state 0) and a second subcarrier set (corresponding to state 1)
  • the second transmitting device corresponds to a third subcarrier set (corresponding to state 0) and a fourth subcarrier set (corresponding to state 1).
  • the receiving device detects that the identification field has energy on the first subcarrier set, it can be determined that the first transmitting device has sent a UHR PPDU carrying the identification field, and the state of the first transmitting device is state 0; or, if the receiving device detects that the identification field has energy on the second subcarrier set, it can be determined that the first transmitting device has sent a UHR PPDU carrying the identification field, and the state of the first transmitting device is state 1; or,
  • the receiving device detects that the identification field has energy on the third subcarrier set, it can be determined that the second transmitting device has sent a UHR PPDU carrying the identification field, and the state of the second transmitting device is state 0; or, if the receiving device detects that the identification field has energy on the fourth subcarrier set, it can be determined that the second transmitting device has sent a UHR PPDU carrying the identification field, and the state of the second transmitting device is state 1.
  • the first transmitting end device corresponds to the first subcarrier set
  • the second transmitting end device corresponds to the second subcarrier set
  • the third transmitting end device corresponds to the third subcarrier set
  • the fourth transmitting end device corresponds to the fourth subcarrier set.
  • the receiving end device detects that the identification field has energy on the first subcarrier set, it can be determined that the first transmitting end device has sent a UHR PPDU carrying the identification field, or, if the receiving end device detects that the identification field has energy on the second subcarrier set, it can be determined that the second transmitting end device has sent a UHR PPDU carrying the identification field, or, if the receiving end device detects that there is energy on the third subcarrier set, it can be determined that the third transmitting end device has sent a UHR PPDU carrying the identification field, or, if the receiving end device detects that the identification field has energy on the fourth subcarrier set, it can be determined that the fourth transmitting end device has sent a UHR PPDU carrying the identification field.
  • the UHR PPDU may include a PE field, or may not include a PE field.
  • the UHR PPDU includes a PE field, and the identification field is located before the PE field.
  • the UHR PPDU does not include the PE field, and the identification field is located at the end of the UHR PPDU.
  • the PE field has the function of providing additional processing time for the receiving device
  • the identification terminal may have the function of providing additional processing time for the receiving device.
  • the UHR PPDU also includes a conversion time field, which is used to reserve time for the receiving device of the UHR PPDU to convert from a receiving state to a sending state.
  • the conversion time field may precede the identification field.
  • the duration of the conversion time field is variable.
  • a signal may be sent in the conversion time field, such as random data, or no signal may be sent. This application does not limit this.
  • the conversion time field may be present when the identification field is included in the UHR PPDU. For example, when the duration of the identification field is 0, the duration of the conversion time field is also 0; when the duration of the identification field is greater than 0, the duration of the conversion time field is also greater than 0.
  • the receiving device switches from the receiving state to the sending state within the duration reserved by the conversion time field, and sends an identification field carrying identification information indicating the receiving device, so that other receiving devices can identify themselves.
  • the identification field sent by the receiving device is time-aligned with the identification field sent by the sending device.
  • the receiving device can switch from the receiving state to the sending state during the conversion time, and then simultaneously send an identification field aligned with the identification field of the sending device to indicate the identification information of the receiving device. In this case, the role of the receiving device is converted to a sending device.
  • the identification field and the conversion time field can be independent fields.
  • the identification field and the conversion time field can be fields at the same level as the existing fields in the UHR PPDU, or the conversion time field can also be a subfield of the identification field.
  • the present application does not specifically limit the position and hierarchical relationship of the identification field and the conversion time field in the UHR PPDU.
  • the following format design only takes the identification field and the conversion time field as independent fields as an example, but the present application is not limited to this.
  • the identification field may also be called the identity field, user identity field, user identification field, user identification extended (UIE) field, etc.
  • the following format design takes the UIE field as an example, but the present application is not limited to this.
  • the conversion time field can also be replaced by other similar names, such as a conversion interval field, a reserved time field, a reserved interval field, etc.
  • Example 1 the format design of the UHR PPDU carrying the identification field is described in detail.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • an identification field may be added to an existing UHR PPDU to indicate the identification information of the transmitting device of the UHR PPDU, or a new UHR PPDU carrying an identification field may be defined for MU detection. This application does not To be limited.
  • existing fields in the UHR PPDU can be used as identification fields, for example, reserved fields in the UHR PPDU can be used as identification fields, or new fields can be added to the UHR PPDU to be used as identification fields. This application does not limit this.
  • the present application does not limit the position of the identification field in the UHR PPDU, as long as the transmitting device and the receiving device have the same understanding of the position of the identification field in the UHR PPDU.
  • the identification field can be carried at the end of the UHR PPDU, or before the PE field in the UHR PPDU, or before or after an existing field in the UHR PPDU, etc.
  • the UHR PPDU is a UHR MU PPDU, a UHR TB PPDU or a UHR Extended Range (ER) PPDU.
  • an identification field is added to the UHR MU PPDU, the UHR TB PPDU or the UHR ER PPDU to indicate the identification information of the transmitting device of the UHR PPDU.
  • the UHR MU PPDU, UHR TB PPDU or UHR ER PPDU carrying an identification field may also be referred to as UHR MU PPDU, UHR TB PPDU or UHR ER PPDU, or the UHR MU PPDU, UHR TB PPDU or UHR ER PPDU carrying an identification terminal may be renamed, and the present application does not limit this.
  • UHR MU PPDU, UHR TB PPDU or UHR ER PPDU carrying an identification field is still referred to as UHR MU PPDU, UHR TB PPDU or UHR ER PPDU as an example, but the present application is not limited to this.
  • UHR PPDU includes an identification field but does not include a PE field, wherein the identification field is carried at the end of the UHR PPDU.
  • the identification field has both the function of identifying the sending end device (or the function of multi-user identity identification) and the function of the PE field, that is, it can be used to increase the processing time of the receiving end device.
  • FIG10 is a schematic format diagram of a UHR MU PPDU or UHR ERP PDU carrying an identification field according to an embodiment of the present application.
  • the UHR MU PPDU or UHR ER PPDU does not include a PE field, and the identification field is carried at the end of the UHR MU PPDU or UHR ER PPDU.
  • the identification field has both the function of identifying the transmitting device (or the function of multi-user identity identification) and the function of the PE field, that is, it can be used to increase the processing time of the receiving device.
  • the UHR MU PPDU or UHR ER PPDU may also include the following fields:
  • L-STF used for PPDU discovery and preliminary time and frequency synchronization.
  • L-LTF used for preliminary channel estimation and further time-frequency alignment.
  • L-SIG used to carry the information required to parse PPDU.
  • U-SIG used to carry the information required to parse PPDU.
  • UHR-SIG used to carry information related to DL MU transmission.
  • UHR-STF On the one hand, it is used to assist the receiving end device to perform preliminary time and frequency synchronization, and on the other hand, it assists the receiving end device to detect the reliability of the PE field.
  • UHR-LTF used by the receiving device to perform channel estimation.
  • Data used to carry data.
  • FIG11 is a schematic format diagram of a UHR TB PPDU carrying an identification field provided according to an embodiment of the present application.
  • the UHR TB PPDU may not include a PE field, and the identification field is carried at the end of the UHR TB PPDU.
  • the identification field has the function of identifying the transmitting device (or the function of multi-user identity recognition), and also has the function of the PE field, that is, it can be used to increase the processing time of the receiving device.
  • the PPDU format shown in Figure 10 is different from the PPDU format shown in Figure 10 in that the PPDU format shown in Figure 11 does not include the UHR-SIG field, and the meanings of other fields are similar to the meanings of the corresponding fields in the format shown in Figure 10. For the sake of brevity, they will not be repeated here.
  • Example 1-2 The UHR PPDU includes an identification field and a conversion time field, but does not include a PE field, wherein the identification field is carried at the end of the UHR PPDU and the conversion time field is located before the identification field.
  • the identification field has both the function of identifying the sending end device (or the function of multi-user identity recognition) and the function of the PE field, that is, it can be used to increase the processing time of the receiving end device.
  • the conversion time field is used to reserve time for the receiving end device to convert from the receiving state to the sending state.
  • FIG12 is a schematic format diagram of a UHR MU PPDU or UHR ER PPDU carrying an identification field and a conversion time field according to an embodiment of the present application.
  • the UHR MU PPDU or UHR ER PPDU does not include a PE field, the identification field is carried at the end of the UHR MU PPDU or UHR ER PPDU, and the conversion time field is before the identification field.
  • the identification field has the function of identifying the sending end device (or the function of multi-user identification), and also has the function of the PE field, that is, it can be used to increase the processing time of the receiving end device. The time reserved for the conversion from the receiving state to the sending state.
  • the PPDU format shown in FIG. 12 is different from the PPDU format shown in FIG. 10 in that the PPDU format shown in FIG. 12 includes a conversion time field, while the PPDU format shown in FIG. 10 does not include a conversion time field.
  • the meanings of the other fields in FIG. 12 except the identification field and the conversion time field refer to the description of the corresponding fields in the PPDU format shown in FIG. 10, and for the sake of brevity, they are not repeated here.
  • the UHR TB PPDU does not include a PE field
  • the identification field is carried at the end of the UHR MU PPDU or UHR ER PPDU
  • the conversion time field is before the identification field.
  • the identification field has both the function of identifying the transmitting device (or the function of multi-user identity identification) and the function of the PE field, that is, it can be used to increase the processing time of the receiving device.
  • the conversion time field is used to reserve time for the receiving device to convert from a receiving state to a sending state.
  • the PPDU format shown in FIG13 is different from the PPDU format shown in FIG11 in that the PPDU format shown in FIG13 includes a conversion time field, while the PPDU format shown in FIG11 does not include a conversion time field.
  • the meanings of the other fields in FIG13 except the identification field and the conversion time field refer to the description of the corresponding fields in the PPDU format shown in FIG10, and for the sake of brevity, they are not repeated here.
  • the receiving end device switches from the receiving state to the sending state within the duration reserved by the conversion time field, and sends an identification field carrying identification information indicating the receiving end device, so that other receiving end devices can identify themselves.
  • the identification field sent by the receiving end device is time-aligned with the identification field sent by the sending end device.
  • UHR PPDU includes an identification field and a PE field, wherein the PE field is carried at the end of the UHR PPDU and the identification field is located before the PE field.
  • the identification field has the function of identifying the sending end device (or the function of multi-user identity recognition), and the PE field is used to increase the processing time of the receiving end device.
  • FIG14 is a schematic format diagram of another UHR MU PPDU or UHR ER PPDU carrying an identification field according to an embodiment of the present application.
  • the UHR MU PPDU or UHR ER PPDU includes a PE field, which is carried at the end of the UHR MU PPDU or UHR ER PPDU, and the identification field is before the PE field.
  • the identification field has the function of identifying the transmitting device (or the function of multi-user identity recognition), and the PE field is used to increase the processing time of the receiving device.
  • the PPDU format shown in FIG14 is different from the PPDU format shown in FIG10 in that the PPDU format shown in FIG14 includes a PE field, while the PPDU format shown in FIG10 does not include a PE field.
  • the meanings of the other fields in FIG14 except the identification field refer to the description of the corresponding fields in the PPDU format shown in FIG10, and for the sake of brevity, they are not repeated here.
  • Fig. 15 is a schematic format diagram of another UHR TB PPDU carrying an identification field provided according to an embodiment of the present application.
  • the UHR TB PPDU includes a PE field, the PE field is carried at the end of the UHR MU PPDU or UHR ER PPDU, and the identification field is before the PE field.
  • the PPDU format shown in FIG15 is different from the PPDU format shown in FIG11 in that the PPDU format shown in FIG15 includes a PE field, while the PPDU format shown in FIG11 does not include a PE field.
  • the meanings of the other fields in FIG15 except the identification field refer to the description of the corresponding fields in the PPDU format shown in FIG10, and for the sake of brevity, they are not repeated here.
  • UHR PPDU includes an identification field, a conversion time field and a PE field, wherein the PE field is carried at the end of the UHR PPDU, the identification field is located before the PE field, and the conversion time field is located before the identification field.
  • the identification field has the function of identifying the sending end device (or the function of multi-user identification), the PE field is used to increase the processing time of the receiving end device, and the conversion time field is used to reserve time for the receiving end device to convert from the receiving state to the sending state.
  • FIG16 is a schematic format diagram of another UHR MU PPDU or UHR ER PPDU carrying an identification field and a conversion time field provided according to an embodiment of the present application.
  • the UHR MU PPDU or UHR ER PPDU includes a PE field, which is located at the end of the UHR MU PPDU or UHR ER PPDU, and the identification field and the conversion time field are carried before the PE field.
  • the identification field has the function of identifying the transmitting device (or the function of multi-user identity identification), and the PE field is used to increase the processing time of the receiving device.
  • the conversion time field is used to reserve time for the receiving device to convert from a receiving state to a sending state.
  • the PPDU format shown in FIG16 is different from the PPDU format shown in FIG13 in that the PPDU format shown in FIG16 includes a PE field, while the PPDU format shown in FIG13 does not include a PE field.
  • the meanings of the other fields in FIG16 except the identification field and the conversion time field refer to the description of the corresponding fields in the PPDU format shown in FIG10, and for the sake of brevity, they are not repeated here.
  • FIG17 is a schematic format diagram of another UHR TB PPDU carrying an identification field and a conversion time field according to an embodiment of the present application.
  • the UHR TB PPDU includes a PE field, the PE field is located at the end of the UHR MU PPDU or the UHR ER PPDU, and the identification field and the conversion time field are carried before the PE field.
  • the PPDU format shown in FIG17 is different from the PPDU format shown in FIG14 in that the PPDU format shown in FIG17 includes a PE field, while the PPDU format shown in FIG14 does not include a PE field.
  • the meanings of the other fields in FIG17 except the identification field and the conversion time field refer to the description of the corresponding fields in the PPDU format shown in FIG10, and for the sake of brevity, they are not repeated here.
  • the duration of the UIE field is a variable duration.
  • the length of the UIE field can also be a fixed length, similarly, the length of the conversion time field can also be a fixed length, and the present application does not limit this.
  • Example 2 the format design of the identification field in UHR PPDU is explained.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the identification field includes one or more identification subfields, and the one or more identification subfields are used to indicate identification information of the transmitting device.
  • the subcarriers used by the one or more identification subfields are used to indicate identification information of the transmitting end device.
  • the multiple identification subfields may be used to indicate identification information of a transmitting end device.
  • a transmitting end device may use the same subcarrier set to transmit different identification subfields to improve transmission reliability.
  • the multiple identification subfields are all used to indicate the identification information of the transmitting end device.
  • the multiple identification subfields may be used to indicate identification information of different transmitting end devices. For example, a transmitting end device sends an identification subfield, and the subcarrier used by the transmitting end device to send the identification subfield is used to indicate the identification information of the transmitting end device, that is, the multiple identification subfields may be sent using different subcarrier sets, so that the identification field can accommodate more users to send identification subfields, thereby enabling detection of more users.
  • the identification field may include only one or more identification subfields.
  • the identification field may include part of the fields in the UHR modulated field (UHR modulated field), such as UHR-STF or UHR-LTF, and/or part or all of the fields in the pre-UHR modulated field (Pre-UHR modulated field), such as L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, UHR-SIG, etc.
  • UHR modulated field such as UHR-STF or UHR-LTF
  • Pre-UHR modulated field such as L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, UHR-SIG, etc.
  • the UHR modulation field may include a UHR-STF, one or more UHR-LTFs, and a data field and a PE field (if present).
  • the Pre-UHR modulated field may include L-STF, L-LTF, L-SIG, RL-SIG, and U-SIG.
  • the Pre-UHR modulated field may include L-STF, L-LTF, L-SIG, RL-SIG, and U-SIG.
  • Pre-UHR modulated field may include L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG.
  • the Pre-UHR modulated field may include L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and UHR-SIG.
  • the duration of the identification subfield is a fixed value.
  • the duration of the identification subfield may be an integer value greater than 0, such as 12, 16, 20, 24, 28, 32 ⁇ s, etc.
  • the duration of the identification subfield is variable, for example, by indicating the duration of the identification subfield in other fields in the UHR PPDU.
  • the average power used to transmit the identification subfield is the same as the average power used to transmit the data field in the UHR PPDU. That is, the identification subfield needs to be transmitted at the same average power as the data field.
  • the power used to transmit the identification subfield should not cause significant power leakage outside the spectrum used by the data field.
  • the identification subfield may also be called an identity subfield, a user identity subfield, a user identification subfield, a UIE subfield, etc.
  • the following format design uses the UIE subfield as an example for explanation, but the present application is not limited to this.
  • Embodiment 2-1 The identification field only includes one or more identification subfields.
  • one or more identification subfields are used to identify the transmitting device.
  • Figure 18 is a schematic format diagram of an identification field provided according to an embodiment of the present application. As shown in Figure 18, the identification field only includes one or more identification subfields and does not carry other fields, which is conducive to reducing the overhead of UHR PPDU.
  • the subcarrier used for transmitting the identification subfield is used to indicate identification information of a transmitting end device that sends the identification subfield, such as an AID, a UID, or a MAC address.
  • the multiple identification subfields may indicate identification information of the same transmitting device.
  • a transmitting device uses the same subcarrier set to send the multiple identification subfields to improve transmission reliability.
  • the multiple identification subfields all indicate the one transmitting device, or may also indicate identification information of different transmitting devices. That is, different identification subfields may be sent by different transmitting devices. For example, different transmitting devices use different subcarrier sets to send corresponding identification subterminals, which is equivalent to increasing the number of user identifiers that can be carried in an identification field.
  • Embodiment 2-2 The identification field includes one or more identification subfields and UHR-STF.
  • one or more identification subfields are used to identify the transmitting device, and UHR-STF is used to assist the receiving device in performing preliminary time and frequency synchronization and automatic gain control, and to assist the receiving device in detecting the reliability of the PE field (when the PE field exists).
  • FIG19 is a schematic format diagram of another identification field provided according to an embodiment of the present application.
  • the identification field includes one or more identification subfields and a UHR-STF.
  • one or more identification subfields are used to identify the identity of the transmitting device, and the UHR-STF is used to assist the receiving device in performing preliminary time-frequency synchronization and automatic gain control, and in the case where the PE field exists, the receiving device is assisted in detecting the reliability of the PE field.
  • the receiving end device can realize user identity recognition and automatic gain control, which is conducive to improving the success rate of MU detection.
  • the identification field includes UHR-STF, one or more UHR-LTFs, and one or more identification subfields.
  • the one or more identification subfields are used by the receiving device to identify the transmitting device at the PHY layer
  • the UHR-STF is used to assist the receiving device in performing preliminary time and frequency synchronization and automatic gain control, and to assist the receiving device in detecting the reliability of the PE field (when the PE field exists)
  • the UHR-LTF is used for channel estimation and to assist the receiving device in performing fine time and frequency synchronization.
  • Fig. 20 is a schematic format diagram of another identification field provided according to an embodiment of the present application. As shown in Fig. 20, the identification field includes one UHR-STF, one or more UHR-LTFs and one or more identification subfields.
  • one or more identification subfields are used for identification of the transmitting device.
  • the UHR-STF is used to assist the receiving device in preliminary time-frequency synchronization and automatic gain control, and to assist the receiving device in detecting the reliability of the PE field when the PE field exists.
  • the UHR-LTF is used for channel estimation and to assist the receiving device in fine time-frequency synchronization.
  • the receiving end device can implement user identity recognition, automatic gain control and channel estimation, which is conducive to improving the success rate of MU detection.
  • the identification field includes L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, UHR-STF and one or more identification subfields. That is, the identification field includes the pre-UHR modulated fileld of the complete UHR TB PPDU, or in other words, the identification field includes the complete UHR evolved version of the HE TB feedback NDP, namely L-STF, L-LTF, L-SIG, RL-SIG, U-SIG.
  • FIG. 21 is a schematic format diagram of another identification field provided according to an embodiment of the present application.
  • the identification field includes L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, UHR-STF and one or more identification subfields.
  • the functions of the above-mentioned fields are as follows:
  • the identification subfield is used to identify the sending device
  • L-STF used for PPDU discovery and preliminary time and frequency synchronization.
  • L-LTF used for preliminary channel estimation and further time-frequency alignment.
  • L-SIG used to carry the information required to parse PPDU.
  • U-SIG used to carry the information required to parse PPDU.
  • UHR-STF used to assist the receiving device in performing preliminary time and frequency synchronization and automatic gain control, and to assist the receiving device in detecting the reliability of the PE field.
  • the identification field in the embodiment 2-4 is equivalent to containing a complete NDP, which is not only conducive to improving the success rate of MU detection, but also easy to implement because the format of the identification field is a universal PPDU format.
  • the identification field includes L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, UHR-SIG, UHR-STF and one or more identification subfields. That is, the identification field includes a complete UHR MU PPDU or a pre-UHR modulated fileld of a UHR ER PPDU, or a complete UHR evolved version of an EHT NDP, namely, L-STF, L-LTF, L-SIG, RL-SIG, U-SIG and UHR-SIG.
  • FIG 22 is a schematic format diagram of another identification field provided according to an embodiment of the present application.
  • the identification field includes L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, UHR-SIG, UHR-STF and one or more identification subfields.
  • the functions of the above-mentioned fields are as follows:
  • the identification subfield is used to identify the sending device
  • L-STF used for PPDU discovery and preliminary time and frequency synchronization.
  • L-LTF used for preliminary channel estimation and further time-frequency alignment.
  • L-SIG used to carry the information required to parse PPDU.
  • U-SIG used to carry the information required to parse PPDU.
  • UHR-SIG used to carry information related to DL MU transmission.
  • UHR-STF is used to assist the receiving end equipment to perform preliminary time and frequency synchronization and automatic gain control, and to assist the receiving end equipment to detect Test the reliability of the PE field.
  • the identification field in the embodiment 2-5 is equivalent to containing a complete NDP, which is not only beneficial to improving the success rate of MU detection, but also easy to implement because the format of the identification field is a universal PPDU format.
  • UHR PPDU design in the above-mentioned embodiment 1 can be implemented alone, or it can also be implemented in combination with the format design of the identification field in the above-mentioned embodiment 2.
  • the identification field in the UHR PPDU in the aforementioned embodiments 1-1 and 1-3 may adopt the format design of the identification field in the embodiment 2-1.
  • the identification field in the UHR PPDU shown in Figures 10, 11, 14 and 15 may only include one or more identification fields.
  • the identification field in the UHR PPDU in the aforementioned embodiments 1-1, 1-2, 1-3 and 1-4 may be designed in the format of the identification field in the embodiment 2-2.
  • the identification field in the UHR PPDU shown in Figures 10 to 17 may include one or more identification fields and a UHR-STF.
  • the identification field in the UHR PPDU in the aforementioned embodiments 1-1, 1-2, 1-3 and 1-4 may be designed in the format of the identification field in the embodiment 2-3.
  • the identification field in the UHR PPDU shown in Figures 10 to 17 may include one UHR-STF, one or more UHR-LTFs and one or more identification subfields.
  • the identification field in the UHR PPDU in the aforementioned embodiments 1-2 and embodiments 1-4 may be designed in the format of the identification field in the embodiments 2-4.
  • the identification field in the UHR PPDU in the aforementioned embodiments 1-2 and 1-4 may adopt the format design of the identification field in the embodiment 2-5.
  • the identification field in the UHR PPDU shown in Figures 12, 13, 16 and 17 may only include one or more identification fields.
  • the UHR PPDU carrying the conversion time field can support the device receiving the UHR PPDU to complete the TX/RX conversion during the conversion time and send a UIE field separately.
  • some training sequences can be carried in the UIE field. Therefore, the UIE format design carrying the training sequence can be applicable to the UIE field in the UHR PPDU in Examples 1-2 and 1-4.
  • Example 3 the design of the identification subfield is described.
  • the identification subfield may explicitly indicate identification information of the sending device.
  • the identification subfield may carry the AID, UID or MAC address of the sending device or other identification that can identify the identity of the sending device.
  • the identification subfield may also implicitly indicate the identification information of the transmitting end device.
  • the resource used to transmit the identification subfield is used to implicitly indicate the identification information of the transmitting end device.
  • the subcarrier used to transmit the identification subfield is used to indicate the identification information of the transmitting end device.
  • the subcarrier set used by the transmission identification subfield corresponds to the identification information of the transmitting device, or in other words, the transmitting device and the subcarrier set used by the transmission identification subfield have a corresponding relationship, so the transmitting device can indicate the identification information of the transmitting device by sending the subcarrier set used by the identification subfield.
  • the receiving device can determine the identification information of the transmitting device based on the subcarrier set of the received identification subfield. For example, the receiving device can determine the transmitting device that sent the identification field by detecting which subcarriers the identification subfield of the UHR PPDU has energy on and/or the value of the subcarrier with energy.
  • the subcarrier set may be indicated by RU_TONE_SET_INDEX, and each RU_TONE_SET_INDEX corresponds to identification information of a transmitting end device, such as an AID.
  • the correspondence between the identification information of the transmitting end device and the subcarrier set is predefined.
  • a subcarrier set may include multiple subcarriers.
  • one transmitting end device may correspond to one subcarrier set or multiple subcarrier sets, such as 2 subcarrier sets.
  • the identification subfield can be sent through different subcarrier sets in the multiple subcarrier sets to indicate different status information of the transmitting end device. Therefore, when a transmitting end device corresponds to multiple subcarrier sets, the subcarrier set used to transmit the identification subfield can be used to indicate the status information of the transmitting end device in addition to the identification information of the transmitting end device.
  • the following describes a specific implementation of the identification subfield for indicating the identification information of the transmitting end device in conjunction with a specific embodiment.
  • Embodiment 3-1 One transmitting end device corresponds to two subcarrier sets, or in other words, one transmitting end device is identified by two subcarrier sets.
  • two subcarrier sets corresponding to a transmitting end device are respectively used to identify different status information of the transmitting end device.
  • the first transmitting device corresponds to a first subcarrier set (corresponding to state 0) and a second subcarrier set (corresponding to state 1)
  • the second transmitting device corresponds to a third subcarrier set (corresponding to state 0) and a fourth subcarrier set (corresponding to state 1).
  • the receiving device detects that the identification subfield has energy on the first subcarrier set, it can be determined that the transmitting device is the first transmitting device, and the state of the first transmitting device is state 0; or, if the receiving device detects that the identification subfield has energy on the second subcarrier set, it can be determined that the transmitting device is the first transmitting device, and the state of the first transmitting device is state 1; or,
  • the receiving device detects that the identification subfield has energy on the third subcarrier set, it can be determined that the transmitting device is the second transmitting device, and the state of the second transmitting device is state 0; or, if the receiving device detects that the identification subfield has energy on the fourth subcarrier set, it can be determined that the transmitting device is the second transmitting device, and the state of the second transmitting device is state 1.
  • the present application does not limit the bandwidth of the identification subfield.
  • the maximum bandwidth of the identification subfield is 160 MHz or 320 MHz.
  • the bandwidth of the identification subfield can be 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz or 320 MHz.
  • the correspondence between the subcarrier set and the transmitting end device may be as shown in Table 1.
  • the bandwidth of the identification subfield is 40MHz
  • the receiving device detects that the identification subfield has energy on the -241, -205, -169, -122, -86 and -50 subcarriers, and no energy on other subcarriers
  • the 320 MHz can be represented by four 80 MHz subcarrier set indexes (i.e., RU-TONE-SET-INDEX), wherein RU-TONE-SET-INDEX 1-72 is mapped to the first 80 MHz (i.e., the lowest 80 MHz), RU-TONE-SET-INDEX 73-144 is mapped to the second 80 MHz, RU-TONE-SET-INDEX 145-216 is mapped to the third 80 MHz, and RU-TONE-SET-INDEX 217-288 is mapped to the fourth 80 MHz (i.e., the highest 80 MHz).
  • RU-TONE-SET-INDEX subcarrier set indexes
  • Embodiment 3-2 One transmitting end device may correspond to one subcarrier set, or in other words, one transmitting end device may be identified by one subcarrier set. Compared with Embodiment 3-1, Embodiment 3-2 may indicate a greater number of transmitting end devices by using the same number of subcarrier sets.
  • the first transmitting device corresponds to the first subcarrier set
  • the second transmitting device corresponds to the second subcarrier set
  • the third transmitting device corresponds to the third subcarrier set
  • the fourth transmitting device corresponds to the fourth subcarrier set.
  • the receiving device detects that the identification subfield has energy on the first subcarrier set, it can be determined that the transmitting device of the identification subfield is the first transmitting device, or, if the receiving device detects that the identification subfield has energy on the second subcarrier set, it can be determined that the transmitting device of the identification subfield is the second transmitting device, or, if the receiving device detects that the identification subfield has energy on the third subcarrier set, it can be determined that the transmitting device of the identification subfield is the third transmitting device, or, if the receiving device detects that the identification subfield has energy on the fourth subcarrier set, it can be determined that the transmitting device of the identification subfield is the fourth transmitting device.
  • the present application does not limit the bandwidth of the identification subfield.
  • the maximum bandwidth of the identification subfield is 160 MHz or 320 MHz.
  • the bandwidth of the identification subfield can be 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz or 320 MHz.
  • the correspondence between the subcarrier set and the transmitting end device may be as shown in Table 1.
  • the correspondence between the subcarrier set and the transmitting end device can be as shown in Table 6.
  • the subcarrier mapping relationship of 20MHz is expanded by 1 times and 3 times respectively, so that more users can be mapped.
  • the bandwidth of the identification subfield is 40MHz
  • Embodiment 3 and the various embodiments in Embodiment 2 can be implemented in combination.
  • the identification subfield in Embodiment 2-1, Embodiment 2-2, Embodiment 2-3, Embodiment 2-4 and Embodiment 2-5 can adopt the design in Embodiment 3-1, or, can also adopt the design in Embodiment 3-2.
  • the UHR PPDU may also carry control information of the identification field, for example, the UHR PPDU Whether to include identification fields, configuration information of identification fields, etc.
  • the configuration information of the identification field includes at least one of the following:
  • the purpose or type of the identification field may include, but is not limited to, being used only for MU identification (or MU detection), being used for MU identification, and increasing the processing time of the receiving end device.
  • the number of users multiplexed on a group of subcarriers in the same RU may refer to the number of users multiplexed on the same set of subcarriers in the same RU.
  • the existing fields in the UHR PPDU can be used to carry the control information of the identification field.
  • the reserved fields in the UHR PPDU can be used to carry the control information of the identification field, or a new field can be added to the UHR PPDU to carry the control information of the identification field, which is not limited in the present application.
  • the UHR PPDU may include a control field for indicating whether the UHR PPDU includes the identification field and/or configuration information of the identification field.
  • control field can be implemented by using existing fields in the UHR PPDU, such as using a reserved field, or a new field can be added to the UHR PPDU.
  • control field includes but is not limited to at least one of the following fields:
  • An identification field (e.g., UIE existence) is used to indicate whether the identification field and/or the conversion time field exist in the UHR PPDU;
  • a first quantity field used to indicate the quantity of identification subfields included in the identification field
  • a purpose field (or type field), used to indicate the purpose or type of the identification field
  • the second quantity field is used to indicate the number of users multiplexed on a group of subcarriers in the same RU.
  • the identification presence field is used to indicate whether the identification field and/or transition time field exist in the UHR PPDU.
  • the Flags Present field may be 1 bit.
  • the identification existence field takes a value of 1 to indicate existence, and takes a value of 0 to indicate non-existence.
  • the identification existence field takes a value of 0 to indicate existence, and takes a value of 1 to indicate non-existence.
  • the identification field may also be used to indicate whether the end of the UHR PPDU is an identification field or a PE field.
  • the value of the identification field is 1, indicating that the end of the UHR PPDU is the identification field, and the value of 0 indicates that the end of the UHR PPDU is the PE field.
  • a value of 0 in the identification field indicates that the end of the UHR PPDU is the identification field, and a value of 1 indicates that the end of the UHR PPDU is the PE field.
  • the UHR PPDU when the identification field indicates that the end of the UHR PPDU is the PE field, it can be considered that the UHR PPDU does not include the identification field; when the identification field indicates that the end of the UHR PPDU is the identification field, it can be considered that the UHR PPDU includes the identification field.
  • the first quantity field can be 1 bit, 2 bits, or more bits.
  • the number of bits occupied by the first quantity field can be determined by the maximum number of identification subfields that the identification field can carry, or by the number of types of identification subfields that the identification field can carry.
  • the first quantity field can be 2 bits.
  • the identification field can carry 2 identification subfields or 4 identification subfields
  • the first quantity field can be 1 bit, indicating the two quantities respectively. For example, a value of 1 indicates that 2 identification subfields are carried, and a value of 0 indicates that 4 identification subfields are carried. Alternatively, a value of 1 indicates that 4 identification subfields are carried, and a value of 0 indicates that 2 identification subfields are carried.
  • the purpose field may be 1 bit, 2 bits, or more bits.
  • the number of bits occupied by the purpose field may be determined by the maximum number of purposes of the identification field.
  • the purpose field may be 1 bit if the purpose of the identification field includes only for MU identification (or MU detection) and for MU identification and increasing the processing time of the receiving end device.
  • the second quantity field may be 1 bit, 2 bits, or more bits.
  • the number of bits occupied by the second quantity field may be determined by the maximum number of users that can be multiplexed in the same subcarrier set in the same RU.
  • the second number field can be 2 bits.
  • the second number field can be 1 bit.
  • Embodiment 4 a specific manner of carrying the control information of the identification field is described.
  • Example 4-1 UHR PPDU includes a U-SIG field, and the control information of the identification field is carried in the U-SIG field.
  • the UHR PPDU includes a U-SIG field
  • the U-SIG field includes a control field
  • the control field may
  • the method may include at least one of an identification existence field, a first quantity field, a purpose field, and a second quantity field.
  • the UHR PPDU includes a U-SIG field
  • the U-SIG field includes at least one of an identification presence field, a first quantity field, a purpose field, and a second quantity field.
  • the UHR PPDU can be a UHR MU PPDU, a UHR TB PPDU or a UHR ER PPDU.
  • FIG. 23 is a schematic format diagram of a control information of carrying an identification field through the U-SIG field of a UHR MU PPDU according to an embodiment of the present application.
  • the U-SIG field includes the following fields:
  • An identification field exists, used to indicate whether the identification field and/or the conversion time field exists in the UHR PPDU;
  • a first quantity field used to indicate the quantity of identification subfields included in the identification field
  • a purpose field (or type field), used to indicate the purpose or type of the identification field
  • the second quantity field is used to indicate the number of devices multiplexed on a group of subcarriers in the same RU.
  • the U-SIG field also includes the following fields:
  • Physical layer version identifier (PHY Version Identifier): used to indicate different PHY versions.
  • Bandwidth used to indicate the bandwidth of PPDU.
  • Uplink/Downlink (UL/DL): used to indicate whether the PPDU is sent in the uplink or downlink direction.
  • TXOP used to indicate the duration of TXOP and the value of the network allocation vector (NAV).
  • Validate A reserved field used for validation.
  • PPDU Type and Compression Mode used to indicate the type of PPDU.
  • Punctured Channel Information used to indicate the setting position and mode of PPDU punching.
  • UHR-SIG Modulation and Coding Scheme used to indicate the modulation and coding method of the UHR-SIG field.
  • Cyclic Redundancy Check A check code used to indicate the CRC check of B0-B41 in the U-SIG field.
  • Tail Field used to terminate the grid of the convolutional decoder.
  • FIG. 24 is a schematic format diagram of a control information of carrying an identification field through the U-SIG field of the UHR TB PPDU according to an embodiment of the present application.
  • the U-SIG field includes the following fields:
  • An identification field exists, used to indicate whether the identification field and/or the conversion time field exists in the UHR PPDU;
  • a first quantity field used to indicate the quantity of identification subfields included in the identification field
  • a purpose field (or type field), used to indicate the purpose or type of the identification field
  • the second quantity field is used to indicate the number of devices multiplexed on a group of subcarriers in the same RU.
  • the UHR-SIG field further includes the following fields:
  • Physical layer version identifier (PHY Version Identifier): used to indicate different PHY versions.
  • Bandwidth used to indicate the bandwidth of PPDU.
  • Uplink/Downlink (UL/DL): used to indicate whether the PPDU is sent in the uplink or downlink direction.
  • TXOP used to indicate the duration of TXOP and the value of the network allocation vector (NAV).
  • Disregard A reserved field used to indicate disregard.
  • Validate A reserved field used for validation.
  • PPDU Type and Compression Mode used to indicate the type of PPDU.
  • Spatial Reuse 1 Indicates whether PSR spatial multiplexing is allowed within the subband of the PPDU during transmission of the PPDU. If allowed, this value is used to determine the transmit power limit of the PSRT PPDU.
  • Spatial Reuse 2 Indicates whether PSR spatial multiplexing is allowed within the subband of the PPDU during transmission of the PPDU. If allowed, this value is used to determine the transmit power limit of the PSRT PPDU.
  • CRC used to indicate the CRC check code for B0-B41 in the U-SIG field.
  • Tail Field used to terminate the grid of the convolutional decoder.
  • FIG. 25 is a schematic format diagram of a control information of carrying an identification field through the U-SIG field of the UHR ER PPDU according to an embodiment of the present application.
  • the U-SIG field includes the following fields:
  • An identification field exists, used to indicate whether the identification field and/or the conversion time field exists in the UHR PPDU;
  • a first quantity field used to indicate the quantity of identification subfields included in the identification field
  • a purpose field (or type field), used to indicate the purpose or type of the identification field
  • the second quantity field is used to indicate the number of devices multiplexed on a group of subcarriers in the same RU.
  • the UHR-SIG field further includes the following fields:
  • Physical layer version identifier (PHY Version Identifier): used to indicate different PHY versions.
  • Bandwidth used to indicate the bandwidth of PPDU.
  • Uplink/Downlink (UL/DL): used to indicate whether the PPDU is sent in the uplink or downlink direction.
  • TXOP used to indicate the duration of TXOP and the value of the network allocation vector (NAV).
  • Disregard A reserved field used to indicate disregard.
  • Validate A reserved field used for validation.
  • CRC used to indicate the CRC check code for B0-B41 in the U-SIG field.
  • Tail Field used to terminate the grid of the convolutional decoder.
  • the number of bits occupied by the above-mentioned identification field, first quantity field, purpose field and second quantity field, as well as their positions in the U-SIG field are only examples, but the present application is not limited to this.
  • the purpose field may also be 1 bit, and the purpose field may also be located before the first quantity field, etc.
  • Example 4-2 UHR PPDU includes a UHR-SIG field, and the control information of the identification field is carried in the UHR-SIG field.
  • the UHR PPDU includes a UHR-SIG field
  • the UHR-SIG field includes a control field
  • the control field may include at least one of an identification presence field, a first quantity field, a purpose field, and a second quantity field.
  • the UHR PPDU includes a UHR-SIG field
  • the UHR-SIG field includes at least one of an identification presence field, a first quantity field, a purpose field, and a second quantity field.
  • the UHR-SIG field includes a common field (Common field) and a user-specific field (User Specific field), and the control information of the identification field can be carried in the Common field, or, can also be carried in the User Specific field.
  • Common field Common field
  • User Specific field User Specific field
  • the UHR PPDU can be a UHR MU PPDU.
  • FIG26 is a schematic format diagram of a control information of carrying an identification field through the Common field in the UHR-SIG field of the UHR MU PPDU according to an embodiment of the present application.
  • the Common field of the UHR-SIG field includes the following fields:
  • An identification field exists, used to indicate whether the identification field and/or the conversion time field exists in the UHR PPDU;
  • a first quantity field used to indicate the quantity of identification subfields included in the identification field
  • a purpose field (or type field), used to indicate the purpose or type of the identification field
  • the second quantity field is used to indicate the number of devices multiplexed on a group of subcarriers in the same RU.
  • the UHR-SIG field Common field further includes the following fields:
  • Spatial Reuse Used to indicate whether spatial multiplexing mode is allowed during the transmission of this PPDU.
  • GI+LTF Size used to indicate the duration of GI and the type of UHR-LTF.
  • LDPC Extra Symbol Segment used to indicate whether the LDPC extra symbol segment appears.
  • Pre-FEC Padding Factor used to indicate the value of the pre-FEC padding factor.
  • PE Disambiguity used to indicate the value of PE Disambiguity.
  • Number of Non-OFDMA Users Used to indicate the number of all Non-OFDMA users.
  • Example 4-3 Implicitly indicating whether the UHR PPDU includes an identification field
  • the UHR PPDU includes two repeated UHR-STFs, which are used to indicate that the identification field is included in the UHR PPDU.
  • Example 4-4 Indicating that the UHR PPDU includes an identification field through an identification symbol
  • the identification symbol is carried in the Pre-UHR modulated field of the UHR PPDU, or, it may also be carried in the UHR modulated field in the UHR PPDU.
  • the identifier is carried in a first field in the UHR PPDU, and the first field may include at least one of the following fields:
  • the receiving device can know as early as possible that the UHR PPDU includes an identification field, so that the state can be switched during the transition time. In this way, the receiving device can send an identification field or identification subfield that is aligned with the identification field or identification subfield sent by the transmitting device.
  • identification symbol used to identify the identification field included in the UHR PPDU can be one or more, and this application does not limit this.
  • the pilot mapping matrix used by the subcarriers on the identifier is used to indicate that the UHR PPDU includes the identifier field.
  • pilot mapping matrix used by the subcarriers on the identification symbol when the pilot mapping matrix used by the subcarriers on the identification symbol is determined according to the first method, it indicates that the UHR PPDU includes an identification field.
  • pilot mapping matrix used by the subcarriers on the identification symbol is determined according to the second method, it indicates that the UHR PPDU does not include an identification field, wherein the first method and the second method are different, and the pilot mapping matrix used by the subcarriers on the non-identification symbol is determined according to the second method.
  • the second method may be a predefined method. For example, determining the pilot mapping matrix based on the second method may include determining the pilot mapping matrix based on formulas (1) to (5). That is, the second method may be the method shown in the aforementioned formulas (1) to (5).
  • the symbol can be considered as an identification symbol, that is, the UHR PPDU includes an identification field.
  • the receiving device can determine whether the UHR PPDU includes an identification field by detecting whether the pilot mapping matrix used by the subcarriers on the symbol occupied by the first field in the UHR PPDU is determined based on a predefined method. For example, when the pilot mapping matrix used by the subcarriers on the symbol occupied by the first field is different from the pilot mapping matrix determined according to the predefined method, it can be considered that the UHR PPDU includes an identification field; otherwise, it is determined that the UHR PPDU does not include an identification field.
  • the following describes a method for determining a pilot mapping matrix used to identify subcarriers on a symbol in conjunction with a specific embodiment.
  • the calculation method of the pilot mapping matrix used for the subcarriers on the identification symbol illustrated below is only an example, but the present application is not limited to this. As long as the pilot mapping matrix used for the subcarriers on the identification symbol is different from the pilot mapping matrix determined based on a predefined method, it can play an identification role.
  • Method 1 Based on the first method, the pilot mapping matrix used for the subcarriers on the identification symbol is determined to be a first pilot mapping matrix, and based on the second method, the pilot mapping matrix for the subcarriers on the identification symbol is determined to be a second pilot mapping matrix, and the values of the elements in the first pilot mapping matrix are the opposite of the values of the corresponding elements in the first pilot mapping matrix.
  • the transmitting device can indicate that the UHR PPDU includes an identification field by setting the value of the pilot mapping matrix used by the subcarrier on a symbol to the opposite of the value of the pilot mapping matrix determined based on a predefined method.
  • the receiving device can determine that the UHR PPDU includes an identification field when the value of the pilot mapping matrix used by the subcarrier on a symbol is the opposite of the value of the pilot mapping matrix determined based on a predefined method.
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (1).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • the corresponding pilot mapping matrix represents the pilot subcarrier in the 242-tone RU, It means that for non-pilot subcarriers in the 242-tone RU, the corresponding pilot mapping matrix value is 0.
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (2).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • the corresponding pilot mapping matrix Indicates a subcarrier set determined based on the first method
  • the corresponding pilot mapping matrix Indicates that for non-pilot subcarriers in the 484-tone RU, the corresponding pilot mapping matrix value is 0.
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (3).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (4).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (5).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • the corresponding pilot mapping matrix, 0 means that for non-pilot subcarriers in the 4 ⁇ 996-tone RU, the corresponding pilot mapping matrix value is 0.
  • Method 2 Based on the first method, the pilot mapping matrix of the subcarriers on the identification symbol is determined to be the first pilot mapping matrix, and based on the second method, the pilot mapping matrix of the subcarriers on the first symbol is determined to be the first pilot mapping matrix, and the identification symbol and the first symbol are adjacent symbols.
  • the transmitting device can set the pilot mapping matrix used by the subcarriers on one symbol to be the same as that of the adjacent symbols.
  • the same pilot mapping matrix is used to indicate the subcarrier index on the UHR PPDU including an identification field.
  • the receiving device can determine that the UHR PPDU includes an identification field when the pilot mapping matrix used by the subcarriers on two adjacent symbols is the same as the pilot mapping matrix used by the subcarriers on adjacent symbols.
  • the first symbol is the previous symbol adjacent to the identification symbol, or it may be the next symbol adjacent to the identification symbol, which is not limited in the present application.
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (1).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • the corresponding pilot mapping matrix represents the pilot subcarrier in the 242-tone RU, It means that for non-pilot subcarriers in the 242-tone RU, the corresponding pilot mapping matrix value is 0.
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (2).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • the corresponding pilot mapping matrix Indicates a subcarrier set determined based on the first method
  • the corresponding pilot mapping matrix Indicates that for non-pilot subcarriers in the 484-tone RU, the corresponding pilot mapping matrix value is 0.
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (3).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (4).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • the corresponding pilot mapping matrix, 0 means that for non-pilot subcarriers in the 2 ⁇ 996-tone RU, the corresponding pilot mapping matrix value is 0.
  • determining the pilot precoding matrix used for the subcarrier on identifier symbol n based on the second step includes: determining the pilot precoding matrix used for the subcarrier on identifier symbol n according to the aforementioned formula (5).
  • determining the pilot mapping matrix of the subcarrier on the identifier symbol n based on the first method may include:
  • the pilot mapping matrix of the subcarrier at identifier n is determined according to the following formula:
  • the corresponding pilot mapping matrix, 0 means that for non-pilot subcarriers in the 4 ⁇ 996-tone RU, the corresponding pilot mapping matrix value is 0.
  • the pilot mapping matrix of the subcarrier at identification symbol n is the same as the pilot mapping matrix of the subcarrier at the previous symbol (i.e., symbol n-1) determined based on the second method, or the pilot mapping matrix of the subcarrier at identification symbol n can also be the same as the pilot mapping matrix of the subcarrier at the next symbol (i.e., symbol n+1) determined based on the second method.
  • the implementation method is similar and will not be repeated here.
  • the method 200 further includes:
  • the physical layer PHY of the receiving device sends a first primitive to the station management entity (SME) or the media access control MAC sublayer management entity (MLME) of the receiving device, and the first primitive is used to indicate the detection result of the transmitting device obtained by the PHY of the receiving device from one or more UHR PPDUs.
  • SME station management entity
  • MLME media access control MAC sublayer management entity
  • the detection result of the transmitting device includes at least one of the following:
  • the number information of transmitting devices can be determined based on the number of UHR PPDUs or identification fields. For example, when all identification subfields in the identification field of a UHR PPDU are sent by the same transmitting device, the number of transmitting devices can be determined based on the number of UHR PPDUs or identification fields. Alternatively, it can be determined based on the number of identification subfields. For example, when different identification subfields in the identification field of the UHR PPD are sent by different transmitting devices, the number of transmitting devices can be determined based on the number of identification subfields in the UHR PPDU.
  • the identification list of the transmitting device can be determined based on the subcarrier set used by the identification field or identification subfield in the UHR PPDU.
  • the state information of the transmitting end device may be determined based on the subcarrier set used by the identification field or identification subfield in the UHR PPDU.
  • the subcarrier set used can be used to indicate different status information of the transmitting end device. Therefore, the status information of the transmitting end device can be determined according to the subcarrier set used by the identification field or identification subfield in the UHR PPDU.
  • the purpose of the identification field may be obtained from the purpose field in the aforementioned embodiments.
  • the PHY of the receiving device may define at least one of the following transmit vector parameters and receive vector parameters:
  • UIE_NUM_USER used to indicate the number of users (i.e., the number of transmitting devices) detected from the identification field (receive vector parameter);
  • UIE_USER_INDEX used to indicate the list of user (i.e., sending device) identifications detected from the identification field, such as AID, UID, or MAC address (receive vector parameter);
  • UIE_STATUS used to indicate the status list of the user detected from the identification field (receive vector parameter);
  • UIE_PRESENT used to indicate whether the UIE field (send vector parameter) exists in the PPDU
  • NUM_UIE_SUBFIELD used to indicate the number of UIE subfields included in the UIE field (send vector parameter);
  • UIE_TONE_SET_INDEX used to indicate the subcarrier set (i.e. tone set) used by the UIE field (send vector parameter);
  • UIE_TYPE used to indicate the purpose or type of the UIE field (send vector parameter and receive vector parameter);
  • NUMBER_OF_SPATIALLY_MULTIPLEXED_USERS is used to indicate the number of users multiplexed on the same subcarrier set (transmission vector parameter).
  • the above-mentioned sending vector parameters and receiving vector parameters may exist when the UHR PPDU is a UHR MU PPDU, a UHR TB PPDU or a UHR ER PPDU.
  • the first primitive is also called PHY-UI EPORT.indication primitive (PHY-UI EPORT.indication), or detection result indication primitive, etc. This application does not specifically limit the naming of the first primitive.
  • the primitive parameters of the first primitive are as follows:
  • UIE_NUM_USER represents the number of users detected from the UIE field.
  • UIE_USER_INDEX represents a list of user identification information detected by the receiving device, and its length is equal to the value of UIE_NUM_USER.
  • the identification information here may be AID, UID or MAC address or a symbol used to identify the user. When the value of UIE_NUM_USER parameter is 0, this parameter does not exist.
  • UIE_STATUS is used to indicate a list of detected user statuses, wherein the i-th status in the list corresponds to the identification information of the i-th user in USER_INDEX.
  • UIE_TYPE used to indicate the purpose of the UIE field.
  • the first primitive is generated when the PHY of the receiving device successfully receives the identification field and completes the detection of the transmitting device of the identification field, and is used to report the detection result of the transmitting device to the MLME or SME of the receiving device.
  • the SME or MLME of the receiving device obtains the detection result of the sending device through the first primitive.
  • the receiving process shown in Figures 27 and 28 can be applicable to the UHR PPDU format design in Example 1-1, that is, the UHR PPDU can include the UIE field but not the PE field.
  • FIG27 is a schematic diagram of a first primitive receiving process according to an embodiment of the present application.
  • the UHR PPDU may be a UHR MU PPDU and a UHR ER PPDU, and the specific execution process is as follows:
  • the PHY of the receiving device When the PHY of the receiving device receives the L-STF field of UHR MU PPDU and UHR ER PPDU, it needs to measure the traditional received signal strength indication (Received Signal Strength Indication, RSSI) (RSSI_LEGACY) and inform MAC through PHY-CCA.indication primitive (PHY-CCA.indication) that the primary channel is busy. At this time, the receiving device enters carrier sensing (CS) or clear channel assessment (CCA) state.
  • RSSI Received Signal Strength Indication
  • the PHY receives the subsequent training sequence field and signaling field, and reports the L-SIG, U-SIG, UHR-SIG and RSSI to the MAC of the receiving device in the form of RXVECTOR through the PHY-RXSTART.indication primitive. Then, the PHY of the receiving device receives the data field, decodes and descrambles the data field, restores the Physical Layer Protocol Service Unit (PPSU) and reports it to the MAC of the receiving device through the PHY-DATA.indication primitive. At this time, the receiving device enters the receiving state (Rx state).
  • Rx state receiving state
  • the receiving device The PHY of the end device needs to report the multi-user detection results to the MAC of the receiving device through the PHY-UIE report.
  • indication primitive PHY-UIEREPORT.indication
  • the PHY of the receiving device needs to inform the MAC of the receiving device through the PHY-receive end.
  • indication primitive PHY-RXEND.indication
  • RXVECTOR After the Signal Extension field that there is no error in the reception, and use the PHY-CCA.
  • indication primitive (PHY-CCA.inciation) to inform the MAC of the receiving device that the channel is idle at this time.
  • FIG28 is a schematic diagram showing another first primitive receiving process according to an embodiment of the present application.
  • the UHR PPDU may be a UHR TB PPDU, and the UHR PPDU may adopt the format design in Embodiment 1-1, that is, the UHR PPDU may include a UIE field but not a PE field.
  • the specific execution process is as follows:
  • the PHY of the receiving device When the PHY of the receiving device receives the L-STF field of the UHR TB PPDU, it needs to measure the traditional RSSI (RSSI_LEGACY) and inform the MAC through the PHY-CCA.indication primitive (PHY-CCA.indication) that the primary channel is busy. At this time, the receiving device enters the CS or CCA state.
  • RSSI_LEGACY traditional RSSI
  • PHY-CCA.indication primitive PHY-CCA.indication
  • the PHY receives the subsequent training sequence field and signaling field, and reports the L-SIG, U-SIG, UHR-SIG and RSSI to the MAC of the receiving device in the form of RXVECTOR through the PHY-RXSTART.indication primitive. Then, the PHY of the receiving device receives the data field, decodes and descrambles the data field, restores the physical layer protocol service unit (Physical Layer Protocol Service Unit, PPSU) and reports it to the MAC of the receiving device through the PHY-DATA.indication primitive. At this time, the receiving device enters the receiving state (Rx state).
  • Rx state receiving state
  • the PHY of the receiving device needs to report the multi-user detection results to the MAC of the receiving device through the PHY-UIE report.indication primitive after receiving the UIE field. If the Signal Extension field exists, the PHY of the receiving device needs to inform the MAC of the receiving device that there is no error in reception through the PHY-RXEND.indication primitive (PHY-RXEND.indication) in the form of RXVECTOR after the Signal Extension field, and use the PHY-CCA.indication primitive (PHY-CCA.inciation) to inform the MAC of the receiving device that the channel is idle at this time.
  • PHY-RXEND.indication PHY-RXEND.indication
  • PHY-CCA.inciation PHY-CCA.inciation
  • the receiving process shown in Figures 29 and 30 can be applicable to the UHR PPDU format design in Example 1-2, that is, the UHR PPDU can include a conversion time field and a UIE field, but does not include a PE field.
  • FIG29 is a schematic diagram showing another first primitive receiving process according to an embodiment of the present application.
  • the UHR PPDU may be a UHR MU PPDU and a UHR ER PPDU, and the specific execution process is as follows:
  • the PHY of the receiving device When the PHY of the receiving device receives the L-STF field of UHR MU PPDU and UHR ER PPDU, it needs to measure the traditional RSSI (RSSI_LEGACY) and inform MAC through the PHY-CCA.indication primitive (PHY-CCA.indication) that the primary channel is busy. At this time, the receiving device enters the CS or CCA state.
  • RSSI_LEGACY the traditional RSSI
  • PHY-CCA.indication primitive PHY-CCA.indication
  • the PHY receives the subsequent training sequence field and signaling field, and reports L-SIG, U-SIG, UHR-SIG and RSSI to the MAC of the receiving device in the form of RXVECTOR through the PHY-RXSTART.indication primitive. Then, the PHY of the receiving device receives the data field, decodes and descrambles the data field, restores the Physical Layer Protocol Service Unit (PPSU) and reports it to the MAC of the receiving device through the PHY-DATA.indication primitive. At this time, the receiving device enters the receiving state (Rx state).
  • Rx state receiving state
  • the receiving device needs to receive this field. If the UIE field exists, the PHY of the receiving device needs to report the multi-user detection results to the MAC of the receiving device through the PHY-UIE report. indication primitive (PHY-UIEREPORT.indication) after receiving the UIE field. If the signal extension (Signal Extension) field exists, the PHY of the receiving device needs to inform the MAC of the receiving device of the reception without error through the PHY-receive end. indication primitive (PHY-RXEND.indication) in the form of RXVECTOR after the Signal Extension field, and use the PHY-CCA. indication primitive (PHY-CCA.inciation) to inform the MAC of the receiving device that the channel is idle at this time.
  • FIG30 is a schematic diagram showing another first primitive receiving process according to an embodiment of the present application.
  • the UHR PPDU may be a UHR MU PPDU and a UHR ER PPDU.
  • the specific execution process is as follows:
  • the PHY of the receiving device When the PHY of the receiving device receives the L-STF field of the UHR TB PPDU, it needs to measure the traditional RSSI (RSSI_LEGACY) and inform the MAC through the PHY-CCA.indication primitive (PHY-CCA.indication) that the primary channel is busy. At this time, the receiving device enters the CS or CCA state.
  • RSSI_LEGACY traditional RSSI
  • PHY-CCA.indication primitive PHY-CCA.indication
  • the PHY receives the subsequent training sequence field and signaling field, and reports L-SIG, U-SIG, UHR-SIG and RSSI to the MAC of the receiving device in the form of RXVECTOR through the PHY-RXSTART.indication primitive. Then, the PHY of the receiving device receives the data field, decodes and descrambles the data field, restores the Physical Layer Protocol Service Unit (PPSU) and reports it to the MAC of the receiving device through the PHY-DATA.indication primitive. At this time, the receiving device enters the receiving state (Rx state).
  • Rx state receiving state
  • the receiving device needs to receive this field. If the UIE field exists, the PHY of the receiving device needs to report the multi-user detection results to the MAC of the receiving device through the PHY-UIE report. indication primitive (PHY-UIEREPORT.indication) after receiving the UIE field. If the Signal Extension field exists, the PHY of the receiving device needs to report the multi-user detection results to the MAC of the receiving device through the PHY-UIE report. indication primitive (PHY-UIEREPORT.indication).
  • the receiving process shown in Figures 31 and 32 can be applicable to the UHR PPDU format design in Examples 1-3, that is, the UHR PPDU can include a UIE field and a PE field.
  • FIG31 is a schematic diagram of a first primitive receiving process according to an embodiment of the present application.
  • the UHR PPDU may be a UHR MU PPDU and a UHR ER PPDU, and the specific execution process is as follows:
  • the PHY of the receiving device When the PHY of the receiving device receives the L-STF field of UHR MU PPDU and UHR ER PPDU, it needs to measure the traditional received signal strength indication (Received Signal Strength Indication, RSSI) (RSSI_LEGACY) and inform MAC through PHY-CCA.indication primitive (PHY-CCA.indication) that the primary channel is busy. At this time, the receiving device enters carrier sensing (CS) or clear channel assessment (CCA) state.
  • RSSI Received Signal Strength Indication
  • the PHY receives the subsequent training sequence field and signaling field, and reports the L-SIG, U-SIG, UHR-SIG and RSSI to the MAC of the receiving device in the form of RXVECTOR through the PHY-RXSTART.indication primitive. Then, the PHY of the receiving device receives the data field, decodes and descrambles the data field, restores the physical layer protocol service unit (Physical Layer Protocol Service Unit, PPSU) and reports it to the MAC of the receiving device through the PHY-DATA.indication primitive. At this time, the receiving device enters the receiving state (Rx state).
  • Rx state receiving state
  • the PHY of the receiving device needs to report the multi-user detection results to the MAC of the receiving device through the PHY-UIE report.indication primitive after receiving the UIE field. If the PE field exists, the PHY of the receiving device needs to receive this field. If the Signal Extension field exists, the PHY of the receiving device needs to inform the MAC of the receiving device that there is no error in reception through the PHY-RXEND.indication primitive (PHY-RXEND.indication) in the form of RXVECTOR after the Signal Extension field, and use the PHY-CCA.indication primitive (PHY-CCA.inciation) to inform the MAC of the receiving device that the channel is idle at this time.
  • PHY-RXEND.indication PHY-RXEND.indication
  • PHY-CCA.inciation PHY-CCA.inciation
  • FIG32 is a schematic diagram showing another first primitive receiving process according to an embodiment of the present application.
  • the UHR PPDU may be a UHR TB PPDU.
  • the specific execution process is as follows:
  • the PHY of the receiving device When the PHY of the receiving device receives the L-STF field of the UHR TB PPDU, it needs to measure the traditional RSSI (RSSI_LEGACY) and inform the MAC through the PHY-CCA.indication primitive (PHY-CCA.indication) that the primary channel is busy. At this time, the receiving device enters the CS or CCA state.
  • RSSI_LEGACY traditional RSSI
  • PHY-CCA.indication primitive PHY-CCA.indication
  • the PHY receives the subsequent training sequence field and signaling field, and reports the L-SIG, U-SIG, UHR-SIG and RSSI to the MAC of the receiving device in the form of RXVECTOR through the PHY-RXSTART.indication primitive. Then, the PHY of the receiving device receives the data field, decodes and descrambles the data field, restores the physical layer protocol service unit (Physical Layer Protocol Service Unit, PPSU) and reports it to the MAC of the receiving device through the PHY-DATA.indication primitive. At this time, the receiving device enters the receiving state (Rx state).
  • Rx state receiving state
  • the PHY of the receiving device needs to report the multi-user detection results to the MAC of the receiving device through the PHY-UIE report.indication primitive after receiving the UIE field. If the PE field exists, the PHY of the receiving device needs to receive this field. If the Signal Extension field exists, the PHY of the receiving device needs to inform the MAC of the receiving device that there is no error in reception through the PHY-RXEND.indication primitive (PHY-RXEND.indication) in the form of RXVECTOR after the Signal Extension field, and use the PHY-CCA.indication primitive (PHY-CCA.inciation) to inform the MAC of the receiving device that the channel is idle at this time.
  • PHY-RXEND.indication PHY-RXEND.indication
  • PHY-CCA.inciation PHY-CCA.inciation
  • the receiving process shown in Figures 33 and 34 can be applicable to the UHR PPDU format design in Examples 1-4, that is, the UHR PPDU can include a conversion time field, a UIE field and a PE field.
  • FIG33 is a schematic diagram showing another first primitive receiving process according to an embodiment of the present application.
  • the UHR PPDU may be a UHR MU PPDU and a UHR ER PPDU, and the specific execution process is as follows:
  • the PHY of the receiving device When the PHY of the receiving device receives the L-STF field of UHR MU PPDU and UHR ER PPDU, it needs to measure the traditional RSSI (RSSI_LEGACY) and inform MAC through the PHY-CCA.indication primitive (PHY-CCA.indication) that the primary channel is busy. At this time, the receiving device enters the CS or CCA state.
  • RSSI_LEGACY the traditional RSSI
  • PHY-CCA.indication primitive PHY-CCA.indication
  • the PHY receives the subsequent training sequence field and signaling field, and reports L-SIG, U-SIG, UHR-SIG and RSSI to the MAC of the receiving device in the form of RXVECTOR through the PHY-RXSTART.indication primitive. Then, the PHY of the receiving device receives the data field, decodes and descrambles the data field, restores the Physical Layer Protocol Service Unit (PPSU) and reports it to the MAC of the receiving device through the PHY-DATA.indication primitive. At this time, the receiving device enters the receiving state (Rx state).
  • Rx state receiving state
  • the receiving device must receive this field. If the UIE field is present, the receiving device's PHY It is necessary to report the multi-user detection results to the MAC of the receiving device through the PHY-UIE report. indication primitive (PHY-UIEREPORT.indication) after receiving the UIE field. If the PE field exists, the PHY of the receiving device needs to receive this field. If the Signal Extension field exists, the PHY of the receiving device needs to inform the MAC of the receiving device through the PHY-receive end. indication primitive (PHY-RXEND.indication) in the form of RXVECTOR after the Signal Extension field that there is no error in the reception, and use the PHY-CCA. indication primitive (PHY-CCA.inciation) to inform the MAC of the receiving device that the channel is idle at this time.
  • indication primitive PHY-RXEND.indication
  • FIG34 is a schematic diagram showing another first primitive receiving process according to an embodiment of the present application.
  • the UHR PPDU may be a UHR MU PPDU and a UHR ER PPDU.
  • the specific execution process is as follows:
  • the PHY of the receiving device When the PHY of the receiving device receives the L-STF field of the UHR TB PPDU, it needs to measure the traditional RSSI (RSSI_LEGACY) and inform the MAC through the PHY-CCA.indication primitive (PHY-CCA.indication) that the primary channel is busy. At this time, the receiving device enters the CS or CCA state.
  • RSSI_LEGACY traditional RSSI
  • PHY-CCA.indication primitive PHY-CCA.indication
  • the PHY receives the subsequent training sequence field and signaling field, and reports L-SIG, U-SIG, UHR-SIG and RSSI to the MAC of the receiving device in the form of RXVECTOR through the PHY-RXSTART.indication primitive. Then, the PHY of the receiving device receives the data field, decodes and descrambles the data field, restores the Physical Layer Protocol Service Unit (PPSU) and reports it to the MAC of the receiving device through the PHY-DATA.indication primitive. At this time, the receiving device enters the receiving state (Rx state).
  • Rx state receiving state
  • the receiving device needs to receive this field. If the UIE field exists, the PHY of the receiving device needs to report the multi-user detection results to the MAC of the receiving device through the PHY-UIE report. indication primitive (PHY-UIEREPORT.indication) after receiving the UIE field. If the PE field exists, the PHY of the receiving device needs to receive this field. If the Signal Extension field exists, the PHY of the receiving device needs to inform the MAC of the receiving device of the reception without error through the PHY-receive end. indication primitive (PHY-RXEND.indication) in the form of RXVECTOR after the Signal Extension field, and use the PHY-CCA. indication primitive (PHY-CCA.inciation) to inform the MAC of the receiving device that the channel is idle at this time.
  • indication primitive PHY-RXEND.indication
  • FIG35 shows a UL MU detection method of UHR PPDU according to an embodiment of the present application.
  • the AP may be a receiving device, and the transmitting device may include three Non-AP STAs (STA1, STA2, and STA3).
  • the UHR PPDU format may be designed in the format of Embodiment 1-1 and Embodiment 1-3.
  • the specific detection process is as follows:
  • STA1, STA2 and STA3 can actively send UHR MU PPDU or UHR ER PPDU including an identification field, wherein the UIE field in the uplink UHR MU PPDU or UHR ER PPDU sent by STA1 indicates the identification information of STA1, the UIE field in the uplink UHR MU PPDU or UHR ER PPDU sent by STA2 indicates the identification information of STA2, and the UIE field in the uplink UHR MU PPDU or UHR ER PPDU sent by STA3 indicates the identification information of STA3.
  • the AP can receive three UHR MU PPDUs or UHR ER PPDUs that are overlapped together.
  • the AP detects the subcarriers used by the UIE field in the UHR MU PPDU or UHR ER PPDU (for example, detecting which subcarriers have energy and/or the values of the subcarriers with energy), thereby detecting that the overlapped UIE field includes the UIE fields sent by STA 1, STA 2, and STA 3, thereby realizing UL MU detection on the AP side.
  • FIG36 shows a DL MU detection method of UHR PPDU provided according to an embodiment of the present application.
  • the STA may be a receiving device
  • the transmitting device may include three APs (AP1, AP2, and AP3)
  • the UHR PPDU format may be designed using the formats in Embodiments 1-1 and 1-3.
  • the specific detection process is as follows:
  • AP1, AP2 and AP3 can actively send UHR MU PPDU or UHR ER PPDU including an identification field, wherein the UIE field in the UHR MU PPDU or UHR ER PPDU sent by AP1 indicates the identification information of AP1, the UIE field in the UHR MU PPDU or UHR ER PPDU sent by AP2 indicates the identification information of AP2, and the UIE field in the UHR MU PPDU or UHR ER PPDU sent by AP3 indicates the identification information of AP3.
  • the STA can receive three UHR MU PPDUs or UHR ER PPDUs that are overlapped together, and by detecting the subcarriers used by the UIE field in the UHR MU PPDU or UHR ER PPDU (for example, detecting which subcarriers have energy and/or the values of the subcarriers with energy), it can detect that the overlapped UIE field includes the UIE fields sent by AP1, AP2 and AP3, thereby realizing DLMU detection on the STA side.
  • FIG. 37 shows another UL MU detection method of UHR PPDU provided according to an embodiment of the present application.
  • the AP may be a receiving device, and the transmitting device may include three Non-AP STAs (STA1, STA2, and STA3).
  • the UHR PPDU format may be designed in the format of Embodiment 1-1 and Embodiment 1-3.
  • the specific detection process is as follows:
  • the AP first sends a trigger frame including a random access resource unit (RA-RU), that is, the trigger frame includes the RU resources that need to be competed for.
  • RA-RU random access resource unit
  • STA1, STA2, and STA3 can simultaneously send UHR TBPPDUs including the UIE field, where the UIE field in the UHR TB PPDU sent by STA1 indicates the identification information of STA1, and the UIE field in the UHR TB PPDU sent by STA2 indicates the identification information of STA1.
  • the UIE field in the UHR TB PPDU indicates the identification information of STA2, and the UIE field in the UHR TB PPDU sent by STA3 indicates the identification information of STA3.
  • the AP can receive the aliased UHR TB PPDU, and by detecting the subcarriers used by the UIE field in the UHR TB PPDU (for example, detecting which subcarriers have energy and/or the values of the subcarriers with energy), it can detect that the aliased UIE field includes the UIE fields sent by STA 1, STA 2, and STA 3, thereby realizing UL MU detection on the AP side.
  • FIG38 shows another UL MU detection method of UHR PPDU provided in accordance with an embodiment of the present application.
  • the AP may be a receiving device, and the transmitting device may include three Non-AP STAs (STA1, STA2, and STA3).
  • the UHR PPDU format may be designed in the format of Embodiments 1-2 and 1-4.
  • the specific detection process is as follows:
  • STA 1 can send UHR MU PPDU or UHR ER PPDU containing a UIE field (denoted as UIE-1 field).
  • UIE-1 field is used to identify the identification information of STA1.
  • STA 2 and STA 3 After receiving the PPDU, STA 2 and STA 3 determine whether the PPDU contains the UIE field. For example, STA 2 and STA 3 can determine that the PPDU contains the UIE field according to the method described in the aforementioned embodiment 4, and can provide multi-user detection.
  • STA 2 and STA 3 perform state transitions (for example, switching from the receiving state to the sending state) during the transition time, and then simultaneously send UIE fields aligned with the UIE-1 field, which are the UIE-2 field for indicating the identification information of STA 2 and the UIE-3 field for indicating the identification information of STA 3.
  • the AP side will receive the preamble and data part of the PPDU of STA 1 and the aliased UIE-1 field, UIE-2 field, and UIE-3 field.
  • the AP can detect the aliased UIE field containing the UIE fields of STA 1, STA 2, and STA 3 by detecting the subcarrier used by the UIE field, thereby completing the UL MU detection on the AP side.
  • FIG39 shows another MU detection method of UHR PPDU provided according to an embodiment of the present application.
  • STA3 may be a receiving device, and the transmitting device may include AP, STA1, and STA2.
  • the UHR PPDU format may be designed in the format of Embodiments 1-2 and 1-4.
  • the specific detection process is as follows:
  • the AP can send UHR MU PPDU or UHR ER PPDU containing the UIE field (that is, the UIE-0 field), where the UIE-0 field is used to identify the AP's identification information.
  • STA 1 and STA 2 After receiving the PPDU, STA 1 and STA 2 determine whether the PPDU contains the UIE field. For example, STA 1 and STA 2 can determine that the PPDU contains the UIE field according to the method described in the aforementioned embodiment 4, and can provide multi-user detection.
  • STA1 and STA 2 perform state transitions (for example, switching from a receiving state to a transmitting state) during the transition time, and then simultaneously send UIE fields aligned with the UIE-0 field, which are respectively the UIE-1 field for indicating identification information of STA 1 and the UIE-2 field for indicating identification information of STA2.
  • STA3 will receive the preamble and data part of the PPDU sent by the AP and the aliased UIE-0 field, UIE-1 field, and UIE-2 field.
  • STA3 can detect the UIE field containing the UIE fields of AP, STA 1, and STA 2 in the aliased UIE field by detecting the subcarrier used by the UIE field in the UIE field, thereby completing the UL MU detection on the STA3 side.
  • FIG40 shows another MU detection method of UHR PPDU provided according to an embodiment of the present application.
  • the AP may be a receiving device, and the transmitting device may include STA1, STA2, and STA3.
  • the UHR PPDU format may be designed in the format of Embodiment 1-2 and Embodiment 1-4.
  • the specific detection process is as follows:
  • the AP first uses a Trigger frame to trigger STA 1 to send a UHR TB PPDU.
  • the UHR TB PPDU contains a UIE field (denoted as UIE-1 field).
  • the UIE-1 field is used to identify STA1’s identification information.
  • STA 2 and STA 3 After receiving the PPDU, STA 2 and STA 3 determine whether the PPDU contains the UIE field. For example, STA 2 and STA 3 can determine that the PPDU contains the UIE field according to the method described in the aforementioned embodiment 4, and can provide multi-user detection.
  • STA 2 and STA 3 perform state transitions (for example, switching from the receiving state to the sending state) during the transition time, and then simultaneously send UIE fields aligned with the UIE-1 field, which are the UIE-2 field for indicating the identification information of STA 2 and the UIE-3 field for indicating the identification information of STA 3.
  • the AP side will receive the preamble and data part of the PPDU of STA 1 and the aliased UIE-1 field, UIE-2 field, and UIE-3 field.
  • the AP can detect the subcarrier used by the UIE field to detect that the aliased UIE field includes the UIE fields of STA 1, STA 2, and STA 3, thereby completing the UL MU detection on the AP side.
  • the receiving device can identify the identity of the transmitting device through the identification field in the UHR PPDU sent by the transmitting device, thereby realizing MU detection.
  • the UHR PPDU provided in the embodiment of the present application does not need to be bound to the NFRP Trigger frame for use.
  • MU detection can also be completed through the identification field in a certain uplink or downlink PPDU, thereby expanding the use time and scenario of MU detection, and realizing the function of multi-user detection in different scenarios.
  • FIG41 shows a schematic block diagram of a transmitting end device 400 according to an embodiment of the present application.
  • the transmitting end device 400 includes:
  • the communication unit 410 is used to send an ultra-high reliability UHR physical layer protocol data unit PPDU, and the UHR PPDU includes an identification field, and the identification field is used to indicate the identification information of the sending device.
  • the subcarrier used by the identification field is used to indicate identification information of the transmitting device.
  • the UHR PPDU is an ultra-high reliability multi-user physical layer protocol data unit UHR MU PPDU, an ultra-high reliability trigger frame based physical layer protocol data unit UHR TB PPDU, or an ultra-high reliability extended range physical layer protocol data unit UHR ER PPDU.
  • the UHR PPDU does not include a packet extension PE field, and the identification field is carried at the end of the UHR PPDU.
  • the UHR PPDU includes a PE field, and the identification field precedes the PE field.
  • the UHR PPDU also includes a conversion time field, which is used to reserve time for the receiving device of the UHR PPDU to convert from a receiving state to a sending state.
  • the conversion time field precedes the identification field.
  • the identification field includes one or more identification subfields, and the one or more identification subfields are used to indicate identification information of the transmitting device.
  • the identification field further includes an ultra high reliability short training field UHR-STF.
  • the identification field further includes one or more ultra high reliability long training fields UHR-LTF.
  • the identification field also includes a legacy preamble field.
  • the legacy preamble field includes the following fields:
  • the legacy preamble field includes the following fields:
  • the subcarriers used by the one or more identification subfields are used to indicate identification information of the transmitting device.
  • the identification information of the transmitting end device corresponds to two subcarrier sets, and the subcarrier used by the identification subfield belongs to one of the two subcarrier sets.
  • the subcarriers used by the identification subfield belong to different subcarrier sets in the two subcarrier sets and respectively represent different status information of the transmitting end device.
  • the bandwidth of the identification subfield is 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz or 320 MHz.
  • the 320 MHz is represented using 4 80 MHz subcarrier set indices, wherein subcarrier set indices 1-72 are mapped to the first 80 MHz, subcarrier set indices 73-144 are mapped to the second 80 MHz, subcarrier set indices 145-216 are mapped to the third 80 MHz, and subcarrier set indices 217-288 are mapped to the fourth 80 MHz.
  • the identification information of the transmitting end device corresponds to a subcarrier set, and the subcarrier used by the identification subfield belongs to the subcarrier set.
  • the correspondence between the identification information of the transmitting end device and the subcarrier set is predefined.
  • the UHR PPDU also includes a control field for indicating whether the UHR PPDU includes the identification field and/or configuration information of the identification field.
  • the configuration information of the identification field includes at least one of the following:
  • control field includes at least one of the following fields:
  • An identification field exists, used to indicate whether the identification field exists in the UHR PPDU;
  • a first quantity field used to indicate the quantity of identification subfields included in the identification field
  • a purpose field used to indicate the purpose of the identification field
  • the second quantity field is used to indicate the number of devices multiplexed on a group of subcarriers in the same RU.
  • the UHR PPDU includes a U-SIG field
  • the control field is carried in the U-SIG field.
  • the UHR PPDU includes a UHR-SIG field, and the control field is carried in the UHR-SIG field.
  • the UHR PPDU includes two repeated UHR-STFs, which are used to indicate that the identification field is included in the UHR PPDU.
  • the UHR PPDU includes an identification symbol, and the identification symbol is used to indicate that the UHR PPDU includes the identification field.
  • the identifier is carried in at least one of the following fields in the UHR PPDU:
  • the pilot mapping matrix of the subcarriers on the identification symbol is used to indicate that the identification field is included in the UHR PPDU.
  • the pilot mapping matrix of the subcarriers on the identification symbol is determined according to a first method, the first method is different from a second method, the second method is used to determine the pilot mapping matrix of the subcarriers on the non-identification symbol, and the second method is a predefined method.
  • the pilot mapping matrix used for the subcarriers on the identification symbol is determined to be a first pilot mapping matrix based on the first method, and the pilot mapping matrix used for the subcarriers on the identification symbol is determined to be a second pilot mapping matrix based on the second method, and the values of the elements in the first pilot mapping matrix are the opposite of the values of the corresponding elements in the first pilot mapping matrix.
  • the pilot mapping matrix used for the subcarriers on the identification symbol is determined to be a first pilot mapping matrix based on the first method
  • the pilot mapping matrix used for the subcarriers on the first symbol is determined to be a first pilot mapping matrix based on the second method
  • the identification symbol and the first symbol are adjacent symbols.
  • the average power used to transmit the identification field is the same as the average power used to transmit the data field in the UHR PPDU.
  • the duration of the identification field is a fixed value, or the duration of the identification field is variable.
  • the transmitting device is an access point device or a site device.
  • the communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system on chip.
  • the processing unit may be one or more processors.
  • the sending device 400 may correspond to the sending device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the sending device 400 are respectively for realizing the corresponding processes of the sending device in the method 200 shown in Figures 9 to 40, which will not be repeated here for the sake of brevity.
  • FIG42 is a schematic block diagram of a receiving end device according to an embodiment of the present application.
  • the receiving end device 500 shown in FIG42 includes:
  • the communication unit 510 is used to receive one or more ultra-high reliability UHR physical layer protocol data units PPDU, and the UHR PPDU includes an identification field, and the identification field is used to indicate the identification information of the sending device of the UHR PPDU.
  • the subcarrier used by the identification field is used to indicate identification information of the transmitting device of the UHR PPDU.
  • the UHR PPDU is an ultra-high reliability multi-user physical layer protocol data unit UHR MU PPDU, an ultra-high reliability trigger frame based physical layer protocol data unit UHR TB PPDU, or an ultra-high reliability extended range physical layer protocol data unit UHR ER PPDU.
  • the UHR PPDU does not include a packet extension PE field, and the identification field is carried at the end of the UHR PPDU.
  • the UHR PPDU includes a PE field, and the identification field precedes the PE field.
  • the UHR PPDU also includes a conversion time field, which is used to reserve time for the receiving device of the UHR PPDU to convert from a receiving state to a sending state.
  • the conversion time field precedes the identification field.
  • the identification field includes one or more identification subfields, and the one or more identification subfields are used to indicate identification information of the transmitting device.
  • the identification field further includes an ultra high reliability short training field UHR-STF.
  • the identification field further includes one or more ultra high reliability long training fields UHR-LTF.
  • the identification field also includes a legacy preamble field.
  • the legacy preamble field includes the following fields:
  • the legacy preamble field includes the following fields:
  • the subcarriers used by the one or more identification subfields are used to indicate the identification information of the transmitting end device. interest.
  • the identification information of the transmitting end device corresponds to two subcarrier sets, and the subcarrier used by the identification subfield belongs to one of the two subcarrier sets.
  • the subcarriers used by the identification subfield belong to different subcarrier sets in the two subcarrier sets and respectively represent different status information of the transmitting end device.
  • the bandwidth of the identification subfield is 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz or 320 MHz.
  • the 320 MHz is represented using 4 80 MHz subcarrier set indices, wherein subcarrier set indices 1-72 are mapped to the first 80 MHz, subcarrier set indices 73-144 are mapped to the second 80 MHz, subcarrier set indices 145-216 are mapped to the third 80 MHz, and subcarrier set indices 217-288 are mapped to the fourth 80 MHz.
  • the identification information of the transmitting end device corresponds to a subcarrier set, and the subcarrier used by the identification subfield belongs to the subcarrier set.
  • the correspondence between the identification information of the transmitting end device and the subcarrier set is predefined.
  • the UHR PPDU also includes a control field for indicating whether the UHR PPDU includes the identification field and/or configuration information of the identification field.
  • the configuration information of the identification field includes at least one of the following:
  • control field includes at least one of the following fields:
  • An identification field exists, used to indicate whether the identification field exists in the UHR PPDU;
  • a first quantity field used to indicate the quantity of identification subfields included in the identification field
  • a purpose field used to indicate the purpose of the identification field
  • the second quantity field is used to indicate the number of devices multiplexed on a group of subcarriers in the same RU.
  • the UHR PPDU includes a U-SIG field
  • the control field is carried in the U-SIG field.
  • the UHR PPDU includes a UHR-SIG field, and the control field is carried in the UHR-SIG field.
  • the UHR PPDU includes two repeated UHR-STFs, which are used to indicate that the identification field is included in the UHR PPDU.
  • the UHR PPDU includes an identification symbol, and the identification symbol is used to indicate that the UHR PPDU includes the identification field.
  • the identifier is carried in at least one of the following fields in the UHR PPDU:
  • the pilot mapping matrix of the subcarriers on the identification symbol is used to indicate that the identification field is included in the UHR PPDU.
  • the pilot mapping matrix of the subcarriers on the identification symbol is determined according to a first method, the first method is different from a second method, the second method is used to determine the pilot mapping matrix of the subcarriers on the non-identification symbol, and the second method is a predefined method.
  • the pilot mapping matrix used for the subcarriers on the identification symbol is determined to be a first pilot mapping matrix based on the first method, and the pilot mapping matrix used for the subcarriers on the identification symbol is determined to be a second pilot mapping matrix based on the second method, and the values of the elements in the first pilot mapping matrix are the opposite of the values of the corresponding elements in the first pilot mapping matrix.
  • the pilot mapping matrix used for the subcarriers on the identification symbol is determined to be a first pilot mapping matrix based on the first method
  • the pilot mapping matrix used for the subcarriers on the first symbol is determined to be a first pilot mapping matrix based on the second method
  • the identification symbol and the first symbol are adjacent symbols.
  • the receiving device further includes:
  • a processing unit is used to send a first primitive to a site management entity SME or a media access control MAC sublayer management entity MLME at a physical layer PHY, wherein the first primitive is used to indicate a detection result of a transmitting device obtained from one or more UHR PPDUs.
  • the detection result of the transmitting device includes at least one of the following:
  • the first primitive successfully receives the identification field and completes the identification at the PHY of the receiving device.
  • the detection result of the sending end device is generated when the sending end device detects the sending end device of the identification field, and is used to report the detection result of the sending end device to the MLME or SME of the receiving end device.
  • the SME or MLME of the receiving device obtains the detection result of the sending device through the first primitive.
  • the average power used to transmit the identification field is the same as the average power used to transmit the data field in the UHR PPDU.
  • the duration of the identification field is a fixed value, or the duration of the identification field is variable.
  • the transmitting device is an access point device or a site device.
  • the receiving device is a site device or an access point device.
  • the communication unit may be a communication interface or a transceiver, or an input/output interface of a communication chip or a system on chip.
  • the processing unit may be one or more processors.
  • the receiving device 500 may correspond to the receiving device in the method embodiment of the present application, and the above-mentioned and other operations and/or functions of each unit in the receiving device 500 are respectively for implementing the corresponding processes of the receiving device in the method 200 shown in Figures 9 to 40, which will not be repeated here for the sake of brevity.
  • Fig. 43 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application.
  • the communication device 600 shown in Fig. 43 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 600 may further include a memory 620.
  • the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
  • the memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .
  • the communication device 600 may further include a transceiver 630 , and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include an antenna, and the number of the antennas may be one or more.
  • the communication device 600 may specifically be a receiving device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the receiving device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
  • the communication device 600 may specifically be a transmitting end device of an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the transmitting end device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
  • Fig. 44 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 700 shown in Fig. 44 includes a processor 710, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.
  • the chip 700 may further include a memory 720.
  • the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .
  • the chip 700 may further include an input interface 730.
  • the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740.
  • the processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
  • the chip can be applied to the sending end device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the sending end device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the chip can be applied to the receiving device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the receiving device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • FIG45 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application.
  • the communication system 900 includes a terminal device 910 and a network device 920 .
  • the sending end device 910 can be used to implement the corresponding functions implemented by the sending end device in the above method
  • the receiving end device 920 can be used to implement the corresponding functions implemented by the receiving end device in the above method.
  • the sending end device 910 can be used to implement the corresponding functions implemented by the sending end device in the above method
  • the receiving end device 920 can be used to implement the corresponding functions implemented by the receiving end device in the above method.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in software form.
  • the above processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the various methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor can be a microprocessor or the processor can also be any conventional
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory can be a random access memory (RAM), which is used as an external cache.
  • RAM Direct Rambus RAM
  • SRAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • DDR SDRAM Double Data Rate SDRAM
  • ESDRAM Enhanced SDRAM
  • SLDRAM Synchlink DRAM
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.
  • An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the sending end device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the sending end device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the computer-readable storage medium can be applied to the receiving device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the receiving device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
  • An embodiment of the present application also provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the sending end device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the sending end device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the computer program product can be applied to the receiving device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the receiving device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the sending device in the embodiments of the present application.
  • the computer program runs on a computer, the computer executes the corresponding processes implemented by the sending device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.
  • the computer program can be applied to the receiving device in the embodiments of the present application.
  • the computer program runs on the computer, the computer executes the corresponding processes implemented by the receiving device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one place or distributed over multiple network units. It is necessary to select some or all of the units to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art.
  • the computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

Landscapes

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

Abstract

一种无线通信的方法、发送端设备和接收端设备，该方法包括：发送端设备发送超高可靠性UHR物理层协议数据单元PPDU，所述UHR PPDU包括标识字段，所述标识字段用于指示所述发送端设备的标识信息。

Description

无线通信的方法、发送端设备和接收端设备 技术领域
本申请实施例涉及通信领域，具体涉及一种感知方法、发送端设备和接收端设备。
背景技术
在多用户(Multiple-User，MU)探测场景中，可以通过空数据物理层协议数据单元(null data physical layer protocol data unit，NDP)反馈报告轮询(NDP Feedback Report Poll，NFRP)和高效率(High Efficiency，HE)基于触发帧(Trigger based，TB)反馈(feedback)NDP(HE TB feedback NDP)实现多用户的探测。具体地，接入点设备发送NFRP帧给一个或多个站点设备，触发站点设备发送HE TB feedback NDP，接入点设备通过解析HE TB feedback NDP获知需要参与后续的多用户上行传输的站点设备，进而在后续的触发帧中合理给这些站点设备分配资源，从而完成多用户上行传输。
但是，上述多用户探测的方式尚有进一步改进的空间。
发明内容
本申请提供了一种无线通信的方法、发送端设备和接收端设备，有利于提升多用户探测的灵活性。
第一方面，提供了一种无线通信的方法，包括：发送端设备发送超高可靠性UHR物理层协议数据单元PPDU，所述UHR PPDU包括标识字段，所述标识字段用于指示所述发送端设备的标识信息。
第二方面，提供了一种无线通信的方法，包括：接收端设备接收一个或多个超高可靠性UHR物理层协议数据单元PPDU，所述UHR PPDU包括标识字段，所述标识字段用于指示所述UHR PPDU的发送端设备的标识信息。
第三方面，提供了一种发送端设备，用于执行上述第一方面或其各实现方式中的方法。
具体地，该发送端设备包括用于执行上述第一方面或其各实现方式中的方法的功能模块。
第四方面，提供了一种接收端设备，用于执行上述第二方面或其各实现方式中的方法。
具体地，该接收端设备包括用于执行上述第二方面或其各实现方式中的方法的功能模块。
第五方面，提供了一种发送端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面或其各实现方式中的方法。
第六方面，提供了一种接收端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面或其各实现方式中的方法。
第七方面，提供了一种芯片，用于实现上述第一方面至第二方面中的任一方面或其各实现方式中的方法。具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行如上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第八方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第九方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
第十方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第二方面中的任一方面或其各实现方式中的方法。
通过上述技术方案，接收端设备可以通过发送端设备发送的UHR PPDU中的标识字段识别发送端设备的身份，从而可以实现MU探测。因此，不需要与NFRP Trigger帧绑定使用，在接收端设备未获得TXOP的情况下也可以通过某个上行或下行UHR PPDU中的标识字段完成MU探测，从而扩展了MU探测的使用时机和使用场景，提升了MU探测的灵活性，可以在不同的场景中实现多用户检测的功能。。
附图说明
图1是本申请实施例提供的一种通信系统架构的示意性图。
图2是一种EHT MU PPDU的格式示意图。
图3是一种EHT TB PPDU的格式示意图。
图4是一种MU UL上行探测过程的示意性图。
图5是一种NFRP Trigger帧的示意性帧格式图。
图6是NFRP Trigger帧中的公共信息(Common Info)字段的格式示意图。
图7是NFRP Trigger帧中的用户信息列表(User Info List)字段的格式示意图。
图8示出了一种HE TB feedback NDP的格式。
图9是根据本申请实施例的无线通信的方法200的示意性交互图。
图10是根据本申请实施例提供的一种携带标识字段的UHR MU PPDU或UHR ER PPDU的示意性格式图。
图11是根据本申请实施例提供的一种携带标识字段的UHR TB PPDU的示意性格式图。
图12是根据本申请实施例提供的一种携带标识字段和转换时间字段的UHR MU PPDU或UHR ER PPDU的示意性格式图。
图13是根据本申请实施例提供的一种携带标识字段和转换时间字段的UHR TB PPDU的示意性格式图。
图14是根据本申请实施例提供的另一种携带标识字段的UHR MU PPDU或UHR ER PPDU的示意性格式图。
图15是根据本申请实施例提供的另一种携带标识字段的UHR TB PPDU的示意性格式图。
图16是根据本申请实施例提供的另一种携带标识字段和转换时间字段的UHR MU PPDU或UHR ER PPDU的示意性格式图。
图17是根据本申请实施例提供的另一种携带标识字段和转换时间字段的UHR TB PPDU的示意性格式图。
图18是根据本申请实施例提供的一种标识字段的示意性格式图。
图19是根据本申请实施例提供的另一种标识字段的示意性格式图。
图20是根据本申请实施例提供的又一种标识字段的示意性格式图。
图21是根据本申请实施例提供的又一种标识字段的示意性格式图。
图22是根据本申请实施例提供的又一种标识字段的示意性格式图。
图23是根据本申请实施例提供的一种通过UHR MU PPDU的U-SIG字段携带标识字段的控制信息的示意性格式图。
图24是根据本申请实施例提供的一种通过UHR TB PPDU的U-SIG字段携带标识字段的控制信息的示意性格式图。
图25是根据本申请实施例提供的一种通过UHR ER PPDU的U-SIG字段携带标识字段的控制信息的示意性格式图。
图26是根据本申请实施例提供的一种通过UHR TB PPDU的UHR-SIG字段中的Common field携带标识字段的控制信息的示意性格式图。
图27至图34是根据本申请实施例的接收端设备的PHY接收PPDU的流程图。
图35至图40是本申请实施例的MU探测方法的使用场景的示意性图。
图41是根据本申请实施例提供的一种发送端设备的示意性框图。
图42是根据本申请实施例提供的一种接收端设备的示意性框图。
图43是根据本申请实施例提供的一种通信设备的示意性框图。
图44是根据本申请实施例提供的一种芯片的示意性框图。
图45是根据本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。针对本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)或其他通信系统等。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括接入点(Access Point，AP)110，以及通过接入点110接入网络的站点(STATION，STA)120。
在一些场景中，AP或称AP STA，即在某种意义上来说，AP也是一种STA。
在一些场景中，STA或称非AP STA(non-AP STA)。
通信系统100中的通信可以是AP与non-AP STA之间的通信，也可以是non-AP STA与non-AP STA之间的通信，或者STA和peer STA之间的通信，其中，peer STA可以指与STA对等通信的设备，例如，peer STA可能为AP，也可能为non-AP STA。
AP相当于一个连接有线网和无线网的桥梁，主要作用是将各个无线网络客户端连接到一起，然后将无线网络接入以太网。AP设备可以是带有WiFi芯片的终端设备(如手机)或者网络设备(如路由器)。
应理解，STA在通信系统中的角色不是绝对的，例如，在一些场景中，手机连接路由的时候，手机是non-AP STA，手机作为其他手机的热点的情况下，手机充当了AP的角色。
AP和non-AP STA可以是应用于车联网中的设备，物联网(Internet Of Things，IoT)中的物联网节点、传感器等，智慧家居中的智能摄像头，智能遥控器，智能水表电表等，以及智慧城市中的传感器等。
在一些实施例中，non-AP STA可以支持802.11be制式。non-AP STA也可以支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等多种当前以及未来的802.11家族的无线局域网(wireless local area networks，WLAN)制式。
在一些实施例中，AP可以为支持802.11be制式的设备。AP也可以为支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等多种当前以及未来的802.11家族的WLAN制式的设备。
在本申请实施例中，STA可以是支持WLAN或WiFi技术的手机(Mobile Phone)、平板电脑(Pad)、电脑、虚拟现实(Virtual Reality，VR)设备、增强现实(Augmented Reality，AR)设备、工业控制(industrial control)中的无线设备、机顶盒、无人驾驶(self driving)中的无线设备、车载通信设备、远程医疗(remote medical)中的无线设备、智能电网(smart grid)中的无线设备、运输安全(transportation safety)中的无线设备、智慧城市(smart city)中的无线设备或智慧家庭(smart home)中的无线设备、无线通信芯片/ASIC/SOC/等。
WLAN技术可支持频段可以包括但不限于：低频段(例如2.4GHz、5GHz、6GHz)、高频段(例如60GHz)。
图1示例性地示出了一个AP STA和两个non-AP STA，可选地，该通信系统100可以包括多个AP STA以及包括其它数量的non-AP STA，本申请实施例对此不做限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的接入点110和站点120，接入点110和站点120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、网关等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
本申请实施例中，"预定义"可以通过在设备(例如，包括接入点和站点)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。
为便于理解本申请实施例的技术方案，以下对本申请相关术语进行说明。
关联标识符(Association Identifier，AID)，用于标识跟接入点建立关联后的终端。
非关联标识符(Unassociation Identifier，UID)，用于标识未与接入点建立关联的终端。
媒体访问控制(Medium Access Control，MAC)。即媒体访问控制地址的简称。
传输机会(Transmission Opportunity，TXOP)，指的是一段时间，在该时间段内，拥有该传输机会的终端可以主动发起一次或多次传输。
以下，对本申请相关的极高吞吐量(Extremely high throughput，EHT)物理层协议数据单元(Physical Layer Protocol Data Unit)进行说明。
IEEE 802.11be在EHT PHY中定义了两种EHT PPDU：EHT多用户(Multiple-User，MU)PPDU和EHT基于触发帧(Trigger based)PPDU。
图2是一种EHT MU PPDU的格式示意图。如图2所示，EHT MU PPDU可以包括如下字段：
传统短训练字段(Legacy Short Training field，L-STF)，固定波形，用于PPDU发现以及初步的时频同步；
传统长训练字段(Legacy Long Training field，L-LTF)，固定波形，用于初步的信道估计以及进一步的时频同步；
传统信号字段(Legacy SIGNAL field，L-SIG)，可变波形，用于携带解析PPDU所需的信息；
重复传统信号字段(Repeated L-SIG，RL-SIG)是L-SIG的重复；
通用信号字段(Universal SIGNAL field，U-SIG)，可变波形，用于携带解析EHT PPDU所需的信息。
EHT-SIG字段(EHT SIGNAL field)，可变波形，用于携带下行(Downlink，DL)MU传输相关的信息。
EHT-STF(EHT Short Training field)，固定波形，用于接收机自动增益控制。
EHT-LTF(EHT Long Training field)，可变波形，用于信道估计。
数据(Data)字段：可变波形，用于携带数据。
包拓展(Packet Extension，PE)字段，可变波形，用于拉长PPDU的时长，给接收机留出更多的的处理和响应时间。
图3是一种EHT TB PPDU的格式示意图。与EHT MU PPDU不同的是，EHT TB PPDU不包括EHT-SIG字段，其他字段的含义和EHT MU PPDU中的对应字段的含义相似。
以下，对空数据物理层协议数据单元(null data physical layer protocol data unit，NDP)反馈报告(Feedback Report)机制进行说明。
在IEEE 802.11ax中定义了一套MU UL探测机制，这个机制使得AP能够在发送Trigger帧之前探测需要分配资源的Non-AP STA。
IEEE 802.11ax中的MU UL探测机制还定义了两个相关的帧结构：NDP反馈报告轮询(NDP Feedback Report Poll，NFRP)Trigger帧和高效率(High Efficiency，HE)TB feedback NDP。
图4是一种MU UL上行探测过程的示意性图。如图4所示，AP发送NFRP Trigger帧至一个或多个Non-AP STA，触发Non-AP STA发送HE TB feedback NDP，AP通过解析HE TB feedback NDP就可以得知有哪些Non-AP STA需要参与后续的MU UL传输，进而在后续的Trigger帧中合理分配资源给这些Non-AP STA，从而完成MU UL传输。
图5是一种NFRP Trigger帧的示意性帧格式图。图6是NFRP Trigger帧中的公共信息(Common Info)字段的格式示意图。其中，上行带宽(UL BW)字段：表示NDP反馈报告响应的带宽。上行空时分组码(Space Time Block Code，STBC)、LDPC额外符号分段(LDPC Extra Symbol Segment)、预前向纠错(Pre-Forward Error Correction，Pre-FEC)填充因子(Pre-FEC Padding Factor)、PE消歧(PE disambiguity)、上行空间重用(UL Spatial Reuse)和多普勒(Doppler)字段被保留。
HE-LTF符号数和训练序列周期性(Number Of HE-LTF Symbols和Midamble Periodicity)字段指示NDP反馈报告响应中存在的HE-LTF符号数，并设置为1。
保护间隔(Guard Interval，GI)和HE-LTF类型(GI And HE-LTF Type)字段设置为2。
触发帧相关公共信息(Trigger Dependent Common Info)字段不存在。
图7是NFRP Trigger帧中的用户信息列表(User Info List)字段的格式示意图。其中，第一个AID(Staring AID)字段:定义了计划响应NFRP触发帧的AID范围的第一个AID。
反馈类型(Feedback Type)字段：指示HE TB feedback NDP所携带的反馈信息的类型。
上行目标接收功率(UL Target Receive Power)字段：表示预期的在AP的天线连接器处测量并在天线上平均的接收信号功率。
空分复用用户数(Number Of Spatially Multiplexed Users)字段：表示在同一RU中复用在同一组子载波上的STA数量，编码为STA数-1。
HE TB feedback NDP用于携带NDP feedback report信息，图8示出了一种HE TB feedback NDP的格式。其中，HE-LTF字段中的不同RU_TONE_SET_INDEX用于标识不同Non-AP STA的AID以及反馈信息(FEEDBACK_STATUS)，具体对应关系如表1所示。
表1：HE TB feedback NDP中HE-LTF子载波映射关系表


在HE TB feedback NDP中仅能使用4xHE-LTF类型的HE-LTF字段，且需要满足下面的公式：
其中，HELTFk是通用HE-LTF序列的在子载波k上的取值；
是表2中用户u(也称为STAu)所发送的HE TB feedback NDP中的HE-LTF字段所在的有能量的子载波的索引。
其中，一个用户对应的有能力的子载波组成一个子载波集合，一个子载波集合可以对应一个子载波集合索引，即RU_TONE_SET_INDEX，例如，表1中的子载波集合{–113,–77,–41,6,42,78}、{–112,–76,–40,7,43,79}等均对应一个子载波集合索引，即一个RU_TONE_SET_INDEX，当NFRP Trigger帧中的Number Of Spatially Multiplexed Users字段取值为0时，每个RU_TONE_SET_INDEX对应一个Non-AP STA(例如AID)。
当BW为20MHz时，对于使用RU_TONE_SET_INDEX＝1的Non-AP STA来说，反馈信息 FEEDBACK_STATUS＝1对应HE-LTF所在的第-113、-77、-41、6、42和78子载波上有能量，其他子载波都没有能量；反馈信息FEEDBACK_STATUS＝0对应HE-LTF所在的第-112、-76、–40、7、43和79子载波上有能量，其他子载波都没有能量。当BW为40MHz或80MHz时，将20MHz的子载波映射关系分别扩展1倍和3倍，从而可以映射更多的Non-AP STA(AID)。
当BW为40MHz或80MHz时，将20MHz的子载波映射关系分别扩展1倍和3倍，从而可以映射更多的Non-AP STA(AID)。
例如，当BW为40MHz时，对于使用RU_TONE_SET_INDEX＝1的Non-AP STA来说，反馈信息FEEDBACK_STATUS＝1对应HE-LTF所在的第-241(即-113-128)、-205(即-77-128)、-169(即-41-128)、-122(即6-128)、-86(即42-128)和-50(即78-128)子载波上有能量，其他子载波都没有能量；反馈信息FEEDBACK_STATUS＝0对应HE-LTF所在的第-240(即-112-128)、-204(即-76-128)、–168(即-40-128)、-121(即7-128)、-85(即43-128)和-49(即79-128)子载波上有能量，其他子载波都没有能量。
当NFRP Trigger帧中的Number Of Spatially Multiplexed Users字段取值为1时，每个RU_TONE_SET_INDEX对应两个Non-AP STA(AID)，这两个Non-AP STA通过预先分配好的不同的预编码矩阵来区分。
以下，对本申请相关的PE字段进行说明。
PE字段在PPDU的末尾，用于提供额外的接收处理时间。PE字段(如果存在)应以与数据字段相同的平均功率传输，并且不应在数据字段使用的频谱之外造成明显的功率泄漏。除此之外，PE字段的内容是任意的。
在一些场景中，HE PPDU中的PE字段的时长的可能取值为：0、4、8、12、16μs。
在一些场景中，EHT PPDU中的PE字段的时长的可能取值为：0、4、8、12、16、20μs。
在一些场景中，持续时间为20μs的PE字段仅在以下情况下使用：
至少有一个参与STA使用4096-QAM调制的EHT MU PPDU；
分配的资源单元(Resource Unit，RU)或多资源单元(Multiple RU，MRU)中存在一个大于2×996tone的320MHz的EHT MU PPDU；
EHT TB PPDU。
PE字段的持续时间由Data字段的最后一个正交频分复用(Orthogonal frequency-division multiplexing，OFDM)符号中的pre-FEC填充因子值和发送矢量(TXVECTOR)参数NOMINAL_PACKET_PADDING决定。
在一些场景中，HE PPDU和EHT PPDU中的PE字段的时长的选择方法可以如表2和表3所示。
表2：HE PE取值表
表3：EHT PE取值表
以下，对本申请相关的导频子载波进行说明。
在一些场景中，一个OFDM符号在频域上可以包含多个子载波，有的是数据子载波，用于携带数据，有的是导频子载波，用于相位和频率追踪，有的是未使用子载波，包括直流子载波，保护子载波和空子载波。其中，导频子载波在一个特定大小的RU的OFDM符号中的数量、位置和内容可以 是预定义的。
以242-tone RU举例来说，不同带宽的PPDU中的每个242-tone RU中的导频子载波的位置可以如下表4所示。
表4：242-tone RU中的导频子载波的位置
对于242-tone RU来说，第n个符号上的导频子载波所使用的导频映射矩阵根据如下公式(1)确定：
其中，mod表示取模，表示242-tone RU中的导频子载波，表示对于242-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
对于484-tone RU，第n个符号上的子载波所使用的导频映射矩阵根据如下公式(2)确定：
其中，mod表示取模，表示484-tone RU中的导频子载波，表示对于484-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
对于996-tone RU，第n个符号上的子载波所使用的导频映射矩阵根据如下公式(3)确定：
其中，mod表示取模，表示996-tone RU中的导频子载波，表示对于996-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
对于2×996-tone RU，第n个符号上的子载波所使用的导频映射矩阵根据如下公式(4)确定：
其中，mod表示取模，表示2×996-tone RU中的导频子载波，表示对于2×996-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
对于4×996-tone RU，第n个符号上的子载波所使用的导频映射矩阵根据如下公式(5)确定：
其中，mod表示取模，表示4×996-tone RU中的导频子载波，表示对于4×996-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在上述公式中，Ψm(其中，m＝0,1,…,7)的取值是预定义的，例如Ψm的定义如下表5所示：
表5
从上述公式可知，每个OFDM符号中的导频子载波所使用的导频映射矩阵是不同的，随着符号数n的增加而递增所使用的导频映射矩阵的下标，并且循环使用导频映射矩阵的下标。
从前文中的NDP Feedback Report机制可知，HE TB feedback NDP必须在AP的TXOP内与NFRP Trigger帧组合使用，即，必须由AP主导才能完成MU UL探测功能，Non-AP STA只能被动配合，这就使得MU UL探测功能的使用时机受到了限制，如果AP不能及时竞争到TXOP，或者，TXOP被其他Non-AP STA或AP占用，那么就无法及时完成MU UL探测，从而导致无法及时进行MU UL传输，给上行业务造成较大的平均时延的时延抖动。
因此，上述多用户探测方式尚有改进的空间。
为便于理解本申请实施例的技术方案，以下通过具体实施例详述本申请的技术方案。以上相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。本申请实施例包括以下内容中的至少部分内容。
图9是根据本申请实施例的无线通信的方法200的示意性交互图，如图9所示，该方法200包括如下内容：
S210，一个或多个发送端设备(例如，发送端设备#1，发送端设备#2，…，发送端设备#n)发送UHR PPDU，该UHR PPDU包括标识字段，该标识字段用于指示UHR PDDU的发送端设备的标识信息(或者说，身份信息)(例如发送端设备的AID，UID或MAC地址)，或者说，标识字段用于接收端设备识别发送端设备。
对应地，接收端设备可以接收一个或多个发送端设备发送的UHR PPDU，根据该UHR PPDU中的标识字段识别该一个或多个UHR PPDU的发送端设备。
因此，在本申请实施例中，接收端设备通过接收的UHR PPDU中的标识字段识别该UHR PPDU的发送端设备，也即，接收端设备在物理层进行发送端设备的识别。
在一些实施例中，该UHR PPDU可以用于MU探测场景中，或者说，标识字段用于MU探测。
例如，在MU探测场景中，接收端设备可以通过发送端设备发送的UHR PPDU中的标识字段识别该发送端设备，从而可以获知该发送端设备有传输需求。即，接收端设备可以根据该标识字段识别 或探测不同发送端设备的UHR PDDU。
在一些实施例中，发送端设备可以是接入点设备，接收端设备可以是站点设备。
即，本申请实施例可以用于UL MU探测。即，接入点设备可以根据该标识字段识别或探测不同的站点设备。
例如，在UL MU探测场景中，站点设备可以向接入点设备发送UHR PPDU，该UHR PPDU中包括标识字段，用于指示该站点设备的标识信息，接入点设备可以通过解析该UHR PPDU可以识别该站点设备，从而可以获知该站点设备有上行传输需求。进一步地，接入点设备可以为有上行传输需求的站点设备分配资源，从而完成MU UL传输。
在一些实施例中，发送端设备可以是站点设备，接收端设备可以是接入点设备。
即，本申请实施例可以用于DL MU探测。即，站点设备可以根据该标识字段识别或探测不同的接入点设备。
例如，在DL MU探测场景中，接入点设备可以向站点设备发送UHR PPDU，该UHR PPDU中包括标识字段，用于指示该接入点设备的标识信息，站点设备可以通过解析该UHR PPDU识别该接入点设备，从而可以获知该接入点设备有下行传输需求。
在一些实施例中，该UHR PPDU可以是用于承载待传输数据的PPDU。
即，发送端设备可以在承载待传输数据的PPDU中携带标识字段来指示自身的标识信息，从而实现MU探测。
对应地，接收端设备可以通过接收携带待传输数据的PPDU(可以是上行PPDU或下行PPDU)中的标识字段实现MU探测，因此，在接收端设备未获得TXOP的情况下，也可以通过接收承载数据的PPDU来实现MU探测，扩展了MU探测的使用时机和使用场景，增加了MU探测的灵活性，可以在不同场景中实现MU探测的功能。
在一些实施例中，所述标识字段是可选字段。
例如，在MU探测场景中，发送端设备发送的UHR PPDU中可以携带该标识字段，在其他不需要接收端设备识别发送端设备身份的场景中，该UHR PPDU中可以不携带该标识字段。
又例如，在使能基于携带该标识字段的UHR PPDU进行MU探测的情况下，UHR PPDU中携带标识字段，否则，该UHR PPDU不携带标识字段。
在一些实施例中，所述标识字段的时长为固定值。例如，标识字段的时长可以大于0的一个整数值，例如12，16，20，24，28，32μs等。
在一些实施例中，所述标识字段的时长是可变的，例如通过UHR PPDU中的其他字段中指示该标识字段的时长。
在一些实施例中，传输所述标识字段所使用的平均功率和传输所述UHR PPDU中的数据字段所使用的平均功率相同。也即，标识字段需要以与数据字段相同的平均功率传输。
在一些实施例中，用于传输所述标识字段的功率不应在数据字段使用的频谱之外造成明显的功率泄露。
在一些实施例中，所述标识字段可以显式指示发送端设备的标识信息，例如标识字段中可以携带发送端设备的AID，UID或MAC地址或其他能够标识所述发送端设备的身份的标识。
在另一些实施例中，所述标识字段也可以隐式指示发送端设备的标识信息。例如，传输标识字段所使用的资源用于隐式指示发送端设备的标识信息。具体例如，传输所述标识字段所使用的子载波用于指示所述发送端设备的标识信息。
在一些实施例中，传输标识字段所使用的子载波集合和发送端设备的标识信息具有对应关系，或者说，发送端设备和传输标识字段所使用的子载波集合具有对应关系，因此，发送端设备可以通过发送标识字段所使用的子载波集合指示该发送端设备的标识信息。对应地，接收端设备可以根据接收标识字段的子载波集合确定发送端设备的标识信息。例如，接收端设备通过检测UHR PPDU的标识字段在哪些子载波上有能量和/或有能量的子载波上的取值，从而可以确定发送该标识字段的发送端设备。
在一些实施例中，子载波集合可以通过RU_TONE_SET_INDEX指示，每个RU_TONE_SET_INDEX对应一个发送端设备的标识信息，例如AID。
在一些实施例中，所述发送端设备的标识信息和子载波集合的对应关系是预定义的。
在一些实施例中，一个子载波集合中可以包括的子载波数大于1，并且不超过子载波的总数。
应理解，本申请并不限定发送端设备所对应的子载波集合的数量，例如一个发送端设备可以对应一个子载波集合，也可以对应多个子载波集合，例如2个子载波集合。
可选地，在一个发送端设备对应多个子载波集合时，标识字段通过该多个子载波集合中的不同子 载波集合发送可以表示发送端设备的不同状态信息。因此，当一个发送端设备对应多个子载波集合时，传输标识字段所使用的子载波集合除了可以用于指示发送端设备的标识信息之外，还可以指示发送端设备的状态信息。
在一些具体实施例中，第一发送端设备对应第一子载波集合(对应状态0)和第二子载波集合(对应状态1)，第二发送端设备对应第三子载波集合(对应状态0)和第四子载波集合(对应状态1)。
若接收端设备检测到标识字段在第一子载波集合上有能量，则可以确定第一发送端设备发送了携带标识字段的UHR PPDU，并且第一发送端设备的状态为状态0；或者，若接收端设备检测到标识字段在第二子载波集合上有能量，则可以确定第一发送端设备发送了携带标识字段的UHR PPDU，并且第一发送端设备的状态为状态1；或者，
若接收端设备检测到标识字段在第三子载波集合上有能量，则可以确定第二发送端设备发送了携带标识字段的UHR PPDU，并且第二发送端设备的状态为状态0；或者，若接收端设备检测到标识字段在第四子载波集合上有能量，则可以确定第二发送端设备发送了携带标识字段的UHR PPDU，并且第二发送端设备的状态为状态1。
在另一些具体实施例中，第一发送端设备对应第一子载波集合，第二发送端设备对应第二子载波集合，第三发送端设备对应第三子载波集合，第四发送端设备对应第四子载波集合。若接收端设备检测到标识字段在第一子载波集合上有能量，则可以确定第一发送端设备发送了携带标识字段的UHR PPDU，或者，若接收端设备检测到标识字段在第二子载波集合上有能量，则可以确定第二发送端设备发送了携带标识字段的UHR PPDU，或者，若接收端设备检测到第三子载波集合上有能量，则可以确定第三发送端设备发送了携带标识字段的UHR PPDU，或者，若接收端设备检测到标识字段在第四子载波集合上有能量，则可以确定第四发送端设备发送了携带标识字段的UHR PPDU。
在一些实施例中，所述UHR PPDU可以包括PE字段，或者，也可以不包括PE字段。
在一个具体实施例中，UHR PPDU包括PE字段，标识字段位于PE字段之前。
在另一个具体实施例中，UHR PPDU不包括PE字段，标识字段位于UHR PPDU的末尾。
可选地，在UHR PPDU包括PE字段时，PE字段具有为接收端设备提供额外的处理时间的功能，在UHR PPDU不包括PE字段时，标识终端可以具有为接收端设备提供额外的处理时间的功能。
在一些实施例中，所述UHR PPDU还包括转换时间字段，用于为所述UHR PPDU的接收端设备由接收状态转换为发送状态预留时间。
在一些实施例中，转换时间字段可以位于标识字段之前。
在一些实施例中，该转换时间字段的时长是可变的，例如，转换时间字段中可以发送信号，例如发送随机数据，或者，也可以不发送任何信号，本申请对此不作限定。
在一些实施例中，转换时间字段可以在UHR PPDU中包括标识字段时存在。例如，当标识字段的时长为0时，该转换时间字段的时长也为0；当标识字段的时长大于0时，该转换时间字段的时长也大于0。
可选地，接收端设备在转换时间字段所预留的时长内从接收状态切换为发送状态，发送一个携带用于指示该接收端设备的标识信息的标识字段，用于其他接收端设备识别自身。可选地，该接收端设备发送的标识字段和发送端设备发送的标识字段的时间对齐。例如，接收端设备可以在转换时间期间从接收状态切换为发送状态，然后同时发送与发送端设备的标识字段对齐的标识字段，用于指示该接收端设备的标识信息，此情况下，该接收端设备的角色转换为一个发送端设备。
需要说明的是，在UHR PPDU中，所述标识字段和所述转换时间字段可以是独立的字段，例如，标识字段和转换时间字段可以是与UHR PPDU中的已有字段处于同一等级的字段，或者，转换时间字段也可以为标识字段的子字段，本申请对于这标识字段和转换时间字段在UHR PPDU中的位置以及层级关系不作具体限定，以下格式设计中仅以标识字段和转换时间字段为独立的字段为例进行说明，但本申请并不限于此。
需要说明的是，本申请对于该标识字段的命名不作具体限定，例如，标识字段也可以称为身份字段，用户身份字段，用户标识字段，用户标识扩展(User Identifying Extended，UIE)字段等，以下格式设计中以UIE字段为例进行说明，但本申请并不限于此。
还需要说明的是，本申请对于所述转换时间字段的命名不作具体限定，所述转换时间字段也可以替换为其他类似命名，例如转换间隔字段，预留时间字段，预留间隔字段等。
以下，在实施例1中，详细说明携带标识字段的UHR PPDU的格式设计。
实施例1：
在一些实施例中，可以在已有UHR PPDU中新增标识字段，用于指示UHR PPDU的发送端设备的标识信息，或者，也可以新定义一种携带标识字段的UHR PPDU，用于MU探测，本申请对此不 作限定。
在一些实施例中，可以利用UHR PPDU中的已有字段作为标识字段，例如利用UHR PPDU中的预留字段作为标识终端，或者，也可以在UHR PPDU中新增字段用作标识字段，本申请对此不作限定。
需要说明的是，本申请并不限定标识字段在UHR PPDU中的位置，只要发送端设备和接收端设备对于所述标识字段在UHR PPDU中的位置的理解一致即可，例如，该标识字段可以携带在UHR PPDU的末尾，或者，携带在UHR PPDU中的PE字段之前，或者，携带在UHR PPDU中的某个已有字段之前或之后等。
在一些实施例中，所述UHR PPDU为UHR MU PPDU、UHR TB PPDU或UHR扩展距离(Extended Range，ER)PPDU。例如，在UHR MU PPDU、UHR TB PPDU或UHR ER PPDU中新增标识字段，用于指示该UHR PPDU的发送端设备的标识信息。
需要说明的是，在本申请实施例中，携带标识字段的UHR MU PPDU、UHR TB PPDU或UHR ER PPDU也可以称为UHR MU PPDU、UHR TB PPDU或UHR ER PPDU，或者，也可以对携带标识终端的UHR MU PPDU、UHR TB PPDU或UHR ER PPDU重新命名，本申请对此不作限定，以下，以携带携带标识字段的UHR MU PPDU、UHR TB PPDU或UHR ER PPDU仍称为UHR MU PPDU、UHR TB PPDU或UHR ER PPDU为例进行说明，但本申请并不限于此。
实施例1-1：UHR PPDU包括标识字段，不包括PE字段，其中，标识字段携带在UHR PPDU的末尾。
在该实施例1-1中，可以认为标识字段既具有标识发送端设备的功能(或者说，多用户身份识别的功能)，也具有PE字段的功能，即可以用于增加接收端设备的处理时间。
图10是根据本申请实施例提供的一种携带标识字段的UHR MU PPDU或UHR ERPPDU的示意性格式图。其中，该UHR MU PPDU或UHR ER PPDU不包括PE字段，标识字段携带在UHR MU PPDU或UHR ER PPDU的末尾。标识字段既具有标识发送端设备的功能(或者说，多用户身份识别的功能)，也具有PE字段的功能，即可以用于增加接收端设备的处理时间。
如图10所示，该UHR MU PPDU或UHR ER PPDU还可以包括如下字段：
L-STF：用于PPDU发现以及初步的时频同步。
L-LTF：用于初步的信道估计以及进一步的时频对齐。
L-SIG：用于携带解析PPDU所需的信息。
RL-SIG：L-SIG的重复。
U-SIG：用于携带解析PPDU所需的信息。
UHR-SIG：用于携带DL MU传输相关的信息。
UHR-STF：一方面用于辅助接收端设备进行初步时频同步，另一方面辅助接收端设备检测PE字段的可靠性。
UHR-LTF：用于接收端设备进行信道估计。
Data：用于携带数据。
图11是根据本申请实施例提供的一种携带标识字段的UHR TB PPDU的示意性格式图，该UHR TB PPDU可以不包括PE字段，标识字段携带在UHR TB PPDU的末尾。此情况下，该标识字段具有标识发送端设备的功能(或者说，多用户身份识别的功能)，也具有PE字段的功能，即可以用于增加接收端设备的处理时间。
应理解，图10所示的PPDU格式与图10所示的PPDU格式不同的是，图11所示的PPDU格式不包括UHR-SIG字段，其他字段的含义和图10所示格式中的对应字段的含义相似，为了简洁，这里不再赘述。
实施例1-2：UHR PPDU包括标识字段和转换时间字段，不包括PE字段，其中，标识字段携带在UHR PPDU的末尾，转换时间字段位于标识字段之前。
在该实施例1-2中，可以认为该标识字段既具有标识发送端设备的功能(或者说，多用户身份识别的功能)，也具有PE字段的功能，即可以用于增加接收端设备的处理时间。转换时间字段用于为接收端设备由接收状态转换为发送状态预留时间。
图12是根据本申请实施例提供的一种携带标识字段和转换时间字段的UHR MU PPDU或UHR ER PPDU的示意性格式图。其中，该UHR MU PPDU或UHR ER PPDU不包括PE字段，标识字段携带在UHR MU PPDU或UHR ER PPDU的末尾，转换时间字段在标识字段之前。
在该示例中，该标识字段既具有标识发送端设备的功能(或者说，多用户身份识别的功能)，也具有PE字段的功能，即可以用于增加接收端设备的处理时间。转换时间字段用于为接收端设备由接 收状态转换为发送状态预留时间。
应理解，图12所示的PPDU格式与图10所示的PPDU格式不同的是：图12所示的PPDU格式包括转换时间字段，图10所示的PPDU格式不包括转换时间字段。图12中除标识字段和转换时间字段之外的其他字段的含义参考图10所示PPDU格式中的对应字段的描述，为了简洁，这里不再赘述。
图13是根据本申请实施例提供的一种携带标识字段和转换时间字段的UHR TB PPDU的示意性格式图。其中，该UHR TB PPDU不包括PE字段，标识字段携带在UHR MU PPDU或UHR ER PPDU的末尾，转换时间字段在标识字段之前。在该示例中，该标识字段既具有标识发送端设备的功能(或者说，多用户身份识别的功能)，也具有PE字段的功能，即可以用于增加接收端设备的处理时间。转换时间字段用于为接收端设备由接收状态转换为发送状态预留时间。
应理解，图13所示的PPDU格式与图11所示的PPDU格式不同的是：图13所示的PPDU格式包括转换时间字段，图11所示的PPDU格式不包括转换时间字段。图13中除标识字段和转换时间字段之外的其他字段的含义参考图10所示PPDU格式中的对应字段的描述，为了简洁，这里不再赘述。
可选地，在该实施例1-2中，接收端设备在转换时间字段所预留的时长内从接收状态切换为发送状态，发送一个携带用于指示该接收端设备的标识信息的标识字段，用于其他接收端设备识别自身。可选地，该接收端设备发送的标识字段和发送端设备发送的标识字段的时间对齐。
实施例1-3：UHR PPDU包括标识字段和PE字段，其中，PE字段携带在UHR PPDU的末尾，标识字段位于PE字段之前。
在该实施例1-3中，该标识字段具有标识发送端设备的功能(或者说，多用户身份识别的功能)，PE字段用于增加接收端设备的处理时间。
图14是根据本申请实施例提供的另一种携带标识字段的UHR MU PPDU或UHR ER PPDU的示意性格式图。其中，该UHR MU PPDU或UHR ER PPDU包括PE字段，PE字段携带在UHR MU PPDU或UHR ER PPDU的末尾，标识字段在PE字段之前。该标识字段具有标识发送端设备的功能(或者说，多用户身份识别的功能)，PE字段用于增加接收端设备的处理时间。
应理解，图14所示的PPDU格式与图10所示的PPDU格式不同的是：图14所示的PPDU格式包括PE字段，图10所示的PPDU格式不包括PE字段。图14中除标识字段之外的其他字段的含义参考图10所示PPDU格式中的对应字段的描述，为了简洁，这里不再赘述。
图15是根据本申请实施例提供的另一种携带标识字段的UHR TB PPDU的示意性格式图。其中，该UHR TB PPDU包括PE字段，PE字段携带在UHR MU PPDU或UHR ER PPDU的末尾，标识字段在PE字段之前。
应理解，图15所示的PPDU格式与图11所示的PPDU格式不同的是：图15所示的PPDU格式包括PE字段，图11所示的PPDU格式不包括PE字段。图15中除标识字段之外的其他字段的含义参考图10所示PPDU格式中的对应字段的描述，为了简洁，这里不再赘述。
实施例1-4：UHR PPDU包括标识字段、转换时间字段和PE字段，其中，PE字段携带在UHR PPDU的末尾，标识字段位于PE字段之前，转换时间字段位于标识字段之前。
在该实施例1-4中，该标识字段具有标识发送端设备的功能(或者说，多用户身份识别的功能)，PE字段用于增加接收端设备的处理时间。转换时间字段用于为接收端设备由接收状态转换为发送状态预留时间。
图16是根据本申请实施例提供的另一种携带标识字段和转换时间字段的UHR MU PPDU或UHR ER PPDU的示意性格式图。其中，该UHR MU PPDU或UHR ER PPDU包括PE字段，PE字段位于UHR MU PPDU或UHR ER PPDU的末尾，标识字段和转换时间字段携带在PE字段之前。其中，该标识字段具有标识发送端设备的功能(或者说，多用户身份识别的功能)，PE字段用于增加接收端设备的处理时间。转换时间字段用于为接收端设备由接收状态转换为发送状态预留时间。
应理解，图16所示的PPDU格式与图13所示的PPDU格式不同的是：图16所示的PPDU格式包括PE字段，图13所示的PPDU格式不包括PE字段。图16中除标识字段和转换时间字段之外的其他字段的含义参考图10所示PPDU格式中的对应字段的描述，为了简洁，这里不再赘述。
图17是根据本申请实施例提供的另一种携带标识字段和转换时间字段的UHR TB PPDU的示意性格式图。其中，该UHR TB PPDU包括PE字段，PE字段位于UHR MU PPDU或UHR ER PPDU的末尾，标识字段和转换时间字段携带在PE字段之前。
应理解，图17所示的PPDU格式与图14所示的PPDU格式不同的是：图17所示的PPDU格式包括PE字段，图14所示的PPDU格式不包括PE字段。图17中除标识字段和转换时间字段之外的其他字段的含义参考图10所示PPDU格式中的对应字段的描述，为了简洁，这里不再赘述。
需要说明的是，图10至图17所示例的UHR PPDU格式中仅以UIE字段的时长为可变时长作为 示例，但本申请并不限于此，UIE字段的时长也可以是固定时长，类似地，转换时间字段的长度可以也可以是固定时长，本申请对此不作限定。
以下，在实施例2中，说明UHR PPDU中标识字段的格式设计。
实施例2：
在本申请一些实施例中，所述标识字段包括一个或多个标识子字段，所述一个或多个标识子字段用于指示发送端设备的标识信息。
在一些实施例中，所述一个或多个标识子字段所使用的子载波用于指示发送端设备的标识信息。
在一些实施例中，当所述标识字段包括多个标识子字段时，所述多个标识子字段可以用于指示一个发送端设备的标识信息，例如，一个发送端设备可以使用相同的子载波集合传输不同的标识子字段来提高传输的可靠性。此情况下，该多个标识子字段均用于指示该一个发送端设备的标识信息。
在一些实施例中，当所述标识字段包括多个标识子字段时，该多个标识子字段可以用于指示不同的发送端设备的标识信息。例如一个发送端设备发送一个标识子字段，该发送端设备发送该标识子字段所使用的子载波用于指示该发送端设备的标识信息，即，该多个标识子字段可以是使用不同的子载波集合发送的，这样，该标识字段可以容纳更多用户进行标识子字段的发送，从而能够实现更多用户的探测。
在一些实施例中，所述标识字段可以仅包括一个或多个标识子字段。
在另一些实施例中，标识字段可以包括UHR调制字段(UHR modulated field)中的部分字段，例如UHR-STF或UHR-LTF等，和/或，前UHR调制字段(Pre-UHR modulated field)中的部分或全部字段，例如L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、UHR-SIG等。
在一些实施例中，UHR调制字段可以包括UHR-STF、一个或多个UHR-LTF和数据字段和PE字段(如果存在)。
在一些实施例中，Pre-UHR modulated field可以包括L-STF、L-LTF、L-SIG、RL-SIG、U-SIG。
例如，对于UHR TB PPDU，Pre-UHR modulated field可以包括L-STF、L-LTF、L-SIG、RL-SIG、U-SIG。
在一些实施例中，Pre-UHR modulated field可以包括L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、UHR-SIG。
例如，对于UHR MU PPDU或UHR ER PPDU，Pre-UHR modulated field可以包括L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、UHR-SIG。
在一些实施例中，所述标识子字段的时长为固定值。例如，标识子字段的时长可以大于0的一个整数值，例如12，16，20，24，28，32μs等。
在一些实施例中，所述标识子字段的时长是可变的，例如通过UHR PPDU中的其他字段中指示该标识子字段的时长。
在一些实施例中，传输所述标识子字段所使用的平均功率和传输所述UHR PPDU中的数据字段所使用的平均功率相同。也即，标识子字段需要以与数据字段相同的平均功率传输。
在一些实施例中，用于传输所述标识子字段的功率不应在数据字段使用的频谱之外造成明显的功率泄露。
需要说明的是，本申请对于该标识子字段的命名不作具体限定，例如，标识子字段也可以称为身份子字段，用户身份子字段，用户标识子字段，UIE子字段等，以下格式设计中以UIE子字段为例进行说明，但本申请并不限于此。
实施例2-1：标识字段仅包括一个或多个标识子字段。
在该实施例2-2中，一个或多个标识子字段用于发送端设备的身份识别。
图18是根据本申请实施例提供的一种标识字段的示意性格式图。如图18所示，标识字段仅包括一个或多个标识子字段，不携带其他字段，有利于降低UHR PPDU的开销。
在一些实施例中，传输标识子字段所使用的子载波用于指示发送该标识子字段的发送端设备的标识信息，例如AID、UID或MAC地址等。
在一些实施例中，当标识字段包括多个标识子字段时，该多个标识子字段可以指示同一个发送端设备的标识信息，例如，一个发送端设备使用相同的子载波集合发送该多个标识子字段，用于提升传输的可靠性，此情况下，该多个标识子字段均指示该一个发送端设备，或者，也可以指示不同的发送端设备的标识信息，即不同的标识子字段可以是不同的发送端设备发送的，例如，不同的发送端设备使用不同的子载波集合发送对应的标识子终端，相当于增加了一个标识字段中可承载的用户标识的数量。
实施例2-2：标识字段包括一个或多个标识子字段以及UHR-STF。
在该实施例2-2中，一个或多个标识子字段用于发送端设备的身份识别，UHR-STF用于辅助接收端设备进行初步时频同步和自动增益控制，以及用于辅助接收端设备检测PE字段的可靠性(在PE字段存在的情况下)。
图19是根据本申请实施例提供的另一种标识字段的示意性格式图。如图19所示，标识字段包括一个或多个标识子字段和一个UHR-STF。其中，一个或多个标识子字段进行发送端设备的身份识别，该UHR-STF用于辅助接收端设备进行初步时频同步和自动增益控制，以及在PE字段存在的情况下，辅助接收端设备检测PE字段的可靠性。
因此，基于该实施例2-2中的标识字段的格式设计，接收端设备可以实现用户身份识别以及自动增益控制，有利于提高MU探测的成功率。
实施例2-3：标识字段包括UHR-STF、一个或多个UHR-LTF以及一个或多个标识子字段。
在该实施例2-3中，该一个或多个标识子字段用于接收端设备在PHY层识别出发送端设备，UHR-STF用于辅助接收端设备进行初步时频同步和自动增益控制，以及用于辅助接收端设备检测PE字段的可靠性(在PE字段存在的情况下)，UHR-LTF用于信道估计以及用于辅助接收端设备进行精细的时频同步。
图20是根据本申请实施例提供的又一种标识字段的示意性格式图。如图20所示，标识字段包括一个UHR-STF、一个或多个UHR-LTF以及一个或多个标识子字段。
其中，一个或多个标识子字段用于发送端设备的身份识别。该UHR-STF用于辅助接收端设备进行初步时频同步和自动增益控制，以及在PE字段存在的情况下辅助接收端设备检测PE字段的可靠性。UHR-LTF用于信道估计以及用于辅助接收端设备进行精细时频同步。
因此，基于该实施例2-3中的标识字段的格式设计，接收端设备可以实现用户身份识别、自动增益控制和信道估计，有利于提高MU探测的成功率。
实施例2-4：标识字段包括L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、UHR-STF以及一个或多个标识子字段。即，标识字段包括完整的UHR TB PPDU的pre-UHR modulated fileld，或者说，该标识字段包括HE TB feedback NDP的完整UHR演进版本，即L-STF、L-LTF、L-SIG、RL-SIG、U-SIG。
图21是根据本申请实施例提供的又一种标识字段的示意性格式图。如图21所示，标识字段包括L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、UHR-STF以及一个或多个标识子字段。其中，上述各个字段的功能如下：
标识子字段，用于进行发送端设备的身份识别；
L-STF：用于PPDU发现以及初步的时频同步。
L-LTF:用于初步的信道估计以及进一步的时频对齐。
L-SIG：用于携带解析PPDU所需的信息。
RL-SIG：L-SIG的重复。
U-SIG：用于携带解析PPDU所需的信息。
UHR-STF：用于辅助接收端设备进行初步时频同步和自动增益控制，以及用于辅助接收端设备检测PE字段的可靠性。
因此，该实施例2-4中的标识字段相当于包含一个完整的NDP，不仅有利于提高MU探测的成功率，而且由于标识字段的格式为通用PPDU格式，所以易于实现。
实施例2-5：标识字段包括L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、UHR-SIG、UHR-STF以及一个或多个标识子字段。即，标识字段包括完整的UHR MU PPDU或UHR ER PPDU的pre-UHR modulated fileld，或者说，一个EHT NDP的完整UHR演进版本，即L-STF、L-LTF、L-SIG、RL-SIG、U-SIG和UHR-SIG。
图22是根据本申请实施例提供的又一种标识字段的示意性格式图。如图22所示，标识字段包括L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、UHR-SIG、UHR-STF以及一个或多个标识子字段。其中，上述各个字段的功能如下：
标识子字段，用于进行发送端设备的身份识别；
L-STF：用于PPDU发现以及初步的时频同步。
L-LTF:用于初步的信道估计以及进一步的时频对齐。
L-SIG：用于携带解析PPDU所需的信息。
RL-SIG：L-SIG的重复。
U-SIG：用于携带解析PPDU所需的信息。
UHR-SIG：用于携带DL MU传输相关的信息。
UHR-STF用于辅助接收端设备进行初步时频同步和自动增益控制，以及用于辅助接收端设备检 测PE字段的可靠性。
因此，该实施例2-5中的标识字段相当于包含一个完整的NDP，不仅有利于提高MU探测的成功率，而且由于标识字段的格式为通用PPDU格式，所以易于实现。
需要说明的是，上述实施例1中的UHR PPDU设计可以单独实施，或者，也可以与上述实施例2中的标识字段的格式设计结合实施。
在一些实施例中，前述实施例1-1和实施例1-3中的UHR PPDU中的标识字段可以采用该实施例2-1中的标识字段的格式设计。例如，图10、图11、图14和图15所示的UHR PPDU中的标识字段可以仅包括一个或多个标识字段。
在一些实施例中，前述实施例1-1、实施例1-2、实施例1-3和实施例1-4中的UHR PPDU中的标识字段可以采用该实施例2-2中的标识字段的格式设计。例如，图10至图17所示的UHR PPDU中的标识字段可以包括一个或多个标识字段以及一个UHR-STF。
在一些实施例中，前述实施例1-1、实施例1-2、实施例1-3和实施例1-4中的UHR PPDU中的标识字段可以采用该实施例2-3中的标识字段的格式设计。例如，图10至图17所示的UHR PPDU中的标识字段可以包括一个UHR-STF、一个或多个UHR-LTF以及一个或多个标识子字段。
在一些实施例中，前述实施例1-2和实施例1-4中的UHR PPDU中的标识字段可以采用该实施例2-4中的标识字段的格式设计。
在一些实施例中，前述实施例1-2和实施例1-4中的UHR PPDU中的标识字段可以采用该实施例2-5中的标识字段的格式设计。例如，图12、图13、图16和图17所示的UHR PPDU中的标识字段可以仅包括一个或多个标识字段。
携带转换时间字段的UHR PPDU可以支持接收到该UHR PPDU的设备在转换时间期间完成TX/RX的转换并单独发送一个UIE字段，为了提高单独发送的UIE字段的接收成功概率，可以在UIE字段中携带一些训练序列，因此，携带训练序列的UIE格式设计可以适用于实施例1-2和实施例1-4中的UHR PPDU中的UIE字段。
以下，在实施例3中，说明标识子字段的设计。
在一些实施例中，所述标识子字段可以显式指示发送端设备的标识信息，例如标识子字段中可以携带发送端设备的AID，UID或MAC地址或其他能够标识所述发送端设备的身份的标识。
在另一些实施例中，所述标识子字段也可以隐式指示发送端设备的标识信息。例如，传输标识子字段所使用的资源用于隐式指示发送端设备的标识信息。具体例如，传输所述标识子字段所使用的子载波用于指示所述发送端设备的标识信息。
在一些实施例中，传输标识子字段所使用的子载波集合和发送端设备的标识信息具有对应关系，或者说，发送端设备和传输标识子字段所使用的子载波集合具有对应关系，因此，发送端设备可以通过发送标识子字段所使用的子载波集合指示该发送端设备的标识信息。对应地，接收端设备可以根据接收标识子字段的子载波集合确定发送端设备的标识信息。例如，接收端设备在检测UHR PPDU的标识子字段在哪些子载波上有能量和/或有能量的子载波上的取值，从而可以确定发送该标识字段的发送端设备。
在一些实施例中，子载波集合可以通过RU_TONE_SET_INDEX指示，每个RU_TONE_SET_INDEX对应一个发送端设备的标识信息，例如AID。
在一些实施例中，所述发送端设备的标识信息和子载波集合的对应关系是预定义的。
在一些实施例中，一个子载波集合中可以包括多个子载波。
应理解，本申请并不限定发送端设备所对应的子载波集合的数量，例如一个发送端设备可以对应一个子载波集合，也可以对应多个子载波集合，例如2个子载波集合。
可选地，在一个发送端设备对应多个子载波集合时，标识子字段通过该多个子载波集合中的不同子载波集合发送可以表示发送端设备的不同状态信息。因此，当一个发送端设备对应多个子载波集合时，传输标识子字段所使用的子载波集合除了可以用于指示发送端设备的标识信息之外，还可以指示发送端设备的状态信息。
以下，结合具体实施例，说明标识子字段用于指示发送端设备的标识信息的具体实现。
实施例3-1：一个发送端设备对应两个子载波集合，或者说，一个发送端设备通过两个子载波集合标识。
在一些实施例中，一个发送端设备对应的两个子载波集合分别用于标识该发送端设备不同的状态信息。
在一些具体实施例中，第一发送端设备对应第一子载波集合(对应状态0)和第二子载波集合(对应状态1)，第二发送端设备对应第三子载波集合(对应状态0)和第四子载波集合(对应状态1)。
若接收端设备检测到标识子字段在第一子载波集合上有能量，则可以确定发送端设备是第一发送端设备，并且第一发送端设备的状态为状态0；或者，若接收端设备检测到标识子字段在第二子载波集合上有能量，则可以确定发送端设备是第一发送端设备，并且第一发送端设备的状态为状态1；或者，
若接收端设备检测到标识子字段在第三子载波集合上有能量，则可以确定发送端设备是第二发送端设备，并且第二发送端设备的状态为状态0；或者，若接收端设备检测到标识子字段在第四子载波集合上有能量，则可以确定发送端设备是第二发送端设备，并且第二发送端设备的状态为状态1。
应理解，本申请并不限定标识子字段的带宽，例如，该标识子字段的最大带宽为160MHz或320MHz，具体例如，标识子字段的带宽可以为20MHz、40MHz、80MHz、80+80MHz、160MHz或320MHz。
在一些实施例中，当标识子字段的带宽为20MHz，40MHz、80MHz、80+80MHz或160MHz时，子载波集合和发送端设备的对应关系可以如表1所示。
例如，当标识子字段的带宽为20MHz时，若接收端设备检测到标识子字段在第-113、-77、-41、6、42和78子载波上有能量，其他子载波都没有能量，则可以确定发送端设备为RU_TONE_SET_INDEX＝1对应的设备，或者，若接收端设备检测到标识子字段在第–111,–75,–39,8,44,80子载波上有能量，其他子载波都没有能量，则可以确定发送端设备为RU_TONE_SET_INDEX＝2对应的设备。
又例如，当标识子字段的带宽为40MHz时，若接收端设备检测到标识子字段在第-241、-205、-169、-122、-86和-50子载波上有能量，其他子载波都没有能量，则可以确定发送端设备为RU_TONE_SET_INDEX＝1对应的设备，或者，若接收端设备检测到标识子字段在第-240、-204、–168、-121、-85和-49子载波上有能量，其他子载波都没有能量，则可以确定发送端设备为RU_TONE_SET_INDEX＝2对应的设备。
在一些实施例中，所述标识子字段的带宽为320MHz时，该320MHz可以使用4个80MHz的子载波集合索引(即RU-TONE-SET-INDEX)表示，其中，RU-TONE-SET-INDEX 1-72映射到第一个80MHz(即最低80MHz)，RU-TONE-SET-INDEX73-144映射到第二个80MHz，RU-TONE-SET-INDEX145-216映射到第三个80MHz，RU-TONE-SET-INDEX 217-288映射到第四个80MHz(即最高80MHz)。
实施例3-2：一个发送端设备可以对应一个子载波集合，或者说，一个发送端设备通过一个子载波集合标识。该实施例3-2相对于实施例3-1，通过相同数量的子载波集合可以指示更多数量的发送端设备。
在一些实施例中，第一发送端设备对应第一子载波集合，第二发送端设备对应第二子载波集合，第三发送端设备对应第三子载波集合，第四发送端设备对应第四子载波集合。若接收端设备检测到标识子字段在第一子载波集合上有能量，则可以确定该标识子字段的发送端设备为第一发送端设备，或者，若接收端设备检测到标识子字段在第二子载波集合上有能量，则可以确定该标识子字段的发送端设备为第二发送端设备，或者，若接收端设备检测到标识子字段在第三子载波集合上有能量，则可以确定该标识子字段的发送端设备为第三发送端设备，或者，若接收端设备检测到标识子字段在第四子载波集合上有能量，则可以确定该标识子字段的发送端设备为第四发送端设备。
应理解，本申请并不限定标识子字段的带宽，例如，该标识子字段的最大带宽为160MHz或320MHz，具体例如，标识子字段的带宽可以为20MHz、40MHz、80MHz、80+80MHz、160MHz或320MHz。
在一些实施例中，，子载波集合和发送端设备的对应关系可以如表1所示。
在一些具体实施例中，当标识子字段的带宽为20MHz，40MHz、80MHz、80+80MHz、160MHz或320MHz时，当一个子载波集合包括6个子载波，子载波集合和发送端设备的对应关系可以如表6所示。
表6


基于表6中的对应关系，当标识子字段的带宽为20MHz时，若接收端设备检测到标识子字段在第-113、-77、-41、6、42和78子载波上有能量，其他子载波都没有能量，则可以确定发送端设备为RU_TONE_SET_INDEX＝1对应的设备，或者，若接收端设备检测到标识子字段在第–112,–76,–40,7,43,79子载波上有能量，其他子载波都没有能量，则可以确定发送端设备为RU_TONE_SET_INDEX＝2对应的设备。当BW为40MHz或80MHz时，将20MHz的子载波映射关系分别扩展1倍和3倍，从而可以映射更多的用户。例如，当标识子字段的带宽为40MHz时，若接收端设备检测到标识子字段在第-241、-205、-169、-122、-86和-50子载波上有能量，其他子载波都没有能量，则可以确定发送端设备为RU_TONE_SET_INDEX＝1对应的设备，或者，若接收端设备检测到标识子字段在第-240、-204、–168、-121、-85和-49子载波上有能量，其他子载波都没有能量，则可以确定发送端设备为RU_TONE_SET_INDEX＝2对应的设备。
应理解，上述实施例3中的各个实施例和实施例2中的各个实施例可以结合实施，例如，实施例2-1、实施例2-2、实施例2-3、实施例2-4和实施例2-5中的标识子字段可以采用实施例3-1中的设计，或者，也可以采用实施例3-2中的设计。
在本申请一些实施例中，所述UHR PPDU中还可以携带标识字段的控制信息，例如该UHR PPDU 是否包括标识字段，标识字段的配置信息等。
在一些实施例中，所述标识字段的配置信息包括以下中的至少之一：
所述标识字段中包括的标识子字段的数量，所述标识字段的用途或类型，同一个资源单元RU中复用在一组子载波(或者说，一个子载波集合)上的用户的数量。
在一些实施例中，标识字段的用途或类型可以包括但不限于仅用于MU识别(或MU探测)，用于MU识别以及增加接收端设备的处理时间。
在一些实施例中，同一个RU中复用在一组子载波上的用户的数量可以指同一个RU中复用在同一个子载波集合上的用户的数量。
在本申请一些实施例中，可以利用UHR PPDU中的已有字段携带标识字段的控制信息。例如，利用UHR PPDU中的预留字段携带标识字段的控制信息，或者，也可以在UHR PPDU中新增字段用于携带标识字段的控制信息，本申请对此不作限定。
在一些实施例中，所述UHR PPDU中可以包括控制字段，用于指示所述UHR PPDU中是否包括所述标识字段和/或所述标识字段的配置信息。
在一些实施例中，控制字段可以利用UHR PPDU中的已有字段实现，例如利用预留字段实现，或者，也可以在UHR PPDU中新增字段实现。
在一些实施例中，所述控制字段包括但不限于以下中的至少一个字段：
标识存在(例如UIE存在)字段，用于指示所述UHR PPDU中是否存在所述标识字段和/或转换时间字段；
第一数量字段，用于指示所述标识字段中包括的标识子字段的数量；
用途字段(或称，类型字段)，用于指示所述标识字段的用途或类型；
第二数量字段，用于指示同一个RU中复用在一组子载波上的用户的数量。
在一些实施例中，标识存在字段用于指示UHR PPDU的中是否存在标识字段和/或转换时间字段。
在一些实施例中，标识存在字段可以是1比特。
作为一个具体示例，标识存在字段取值为1指示存在，取值为0指示不存在。
作为另一个具体示例，标识存在字段取值为0指示存在，取值为1指示不存在。
在另一些实施例中，标识存在字段也可以用于指示UHR PPDU的末尾是标识字段还是PE字段。
例如，标识存在字段取值为1指示UHR PPDU的末尾是标识字段，取值为0指示UHR PPDU的末尾是PE字段。
又例如，标识存在字段取值为0指示UHR PPDU的末尾是标识字段，取值为1指示UHR PPDU的末尾是PE字段。
可选地，对于前述实施例1-1和实施例1-2，在标识存在字段指示UHR PPDU的末尾是PE字段时，可以认为UHR PPDU不包括标识字段，在标识存在字段指示UHR PPDU的末尾是标识字段时，可以认为UHR PPDU包括标识字段。
在一些实施例中，第一数量字段可以为1比特，2比特，或更多比特，例如，该第一数量字段所占的比特数可以由标识字段可携带的标识子字段的最大数量决定，或者，由标识字段可携带的标识子字段的数量的种类数决定。
例如，若标识字段最多可携带4个标识子字段，则该第一数量字段可以是2比特。
又例如，标识字段可携带2个标识子字段或4个标识子字段，则该第一数量字段可以是1比特，分别指示这两种数量。例如取值为1表示携带2个表示子字段，取值为0表示携带4个标识子字段。或者，取值为1表示携带4个表示子字段，取值为0表示携带2个标识子字段。
在一些实施例中，用途字段可以为1比特，2比特，或更多比特，例如，该用途字段所占的比特数可以由标识字段的用途的最大数量决定。例如，若标识字段的用途包括仅用于MU识别(或MU探测)和用于MU识别以及增加接收端设备的处理时间，则用途字段可以为1比特。
在一些实施例中，第二数量字段可以为1比特，2比特，或更多比特，例如，该第二数量字段所占的比特数可以由同一个RU中可复用在同一个子载波集合中的用户的最大数量决定。
例如，若同一个RU中可复用在同一个子载波集合中的设备的最大数量为4，则该第二数量字段可以是2比特。
又例如，若同一个RU中可复用在同一个子载波集合中的设备的最大数量为2，则该第二数量字段可以是1比特。
以下，在实施例4中，说明标识字段的控制信息的具体承载方式。
实施例4-1：UHR PPDU包括U-SIG字段，标识字段的控制信息携带在所述U-SIG字段中。
在一些实施例中，UHR PPDU包括U-SIG字段，U-SIG字段包括控制字段，其中，控制字段可 以包括标识存在字段、第一数量字段、用途字段和第二数量字段中的至少一个字段。
在另一些实施例中，UHR PPDU包括U-SIG字段，U-SIG字段中包括标识存在字段、第一数量字段、用途字段和第二数量字段中的至少一个字段。
在该实施例4-1中，该UHR PPDU可以为UHR MU PPDU、UHR TB PPDU或UHR ER PPDU。
图23是根据本申请实施例提供的一种通过UHR MU PPDU的U-SIG字段携带标识字段的控制信息的示意性格式图。如图23所示，该U-SIG字段包括如下字段：
标识存在字段，用于指示所述UHR PPDU中是否存在所述标识字段和/或转换时间字段；
第一数量字段，用于指示所述标识字段中包括的标识子字段的数量；
用途字段(或称类型字段)，用于指示所述标识字段的用途或类型；
第二数量字段，用于指示同一个RU中复用在一组子载波上的设备的数量。
在一些实施例中，所述U-SIG字段还包括如下字段：
物理层版本标识(PHY Version Identifier)：用于指示不同的PHY版本。
带宽(Bandwidth)：用于指示PPDU的带宽。
上行/下行(Uplink/Downlink，UL/DL)：用于指示PPDU的发送方向是上行还是下行。
TXOP：用于指示TXOP的时长信息和网络分配向量(Network Allocation Vecto，NAV)的取值。
验证(Validate)：用于验证的保留字段。
PPDU类型和压缩模式(PPDU Type And Compression Mode)：用于指示PPDU的类型。
信道打孔信息(Punctured Channel Information)：用于指示PPDU打孔的设置位置和模式。
UHR-SIG调制编码方案(Modulation and Coding Scheme，MCS)：用于指示UHR-SIG字段的调制编码方式。
UHR-SIG符号数(Number Of UHR-SIG Symbols)：用于指示UHR-SIG字段的符号数量。
循环冗余码校验(Cyclical Redundancy Check，CRC)：用于指示对U-SIG字段中B0-B41进行CRC的校验码。
尾部(Tail):用于终止卷积解码器的网格的字段。
图24是根据本申请实施例提供的一种通过UHR TB PPDU的U-SIG字段携带标识字段的控制信息的示意性格式图。如图24所示，该U-SIG字段包括如下字段：
标识存在字段，用于指示所述UHR PPDU中是否存在所述标识字段和/或转换时间字段；
第一数量字段，用于指示所述标识字段中包括的标识子字段的数量；
用途字段(或称类型字段)，用于指示所述标识字段的用途或类型；
第二数量字段，用于指示同一个RU中复用在一组子载波上的设备的数量。
在一些实施例中，如图24所示，所述UHR-SIG字段还包括如下字段：
物理层版本标识(PHY Version Identifier)：用于指示不同的PHY版本。
带宽(Bandwidth)：用于指示PPDU的带宽。
上行/下行(Uplink/Downlink，UL/DL)：用于指示PPDU的发送方向是上行还是下行。
TXOP：用于指示TXOP的时长信息和网络分配向量(Network Allocation Vecto，NAV)的取值。
忽略(Disregard)：用于指示忽略的保留字段。
验证(Validate)：用于验证的保留字段。
PPDU类型和压缩模式(PPDU Type And Compression Mode)：用于指示PPDU的类型。
空间复用1(Spatial Reuse 1)：表示在该PPDU的传输过程中，该PPDU的子带内是否允许PSR空间复用，如果允许，该值用于确定PSRT PPDU的发射功率限值。
空间复用2(Spatial Reuse 2)：表示在该PPDU的传输过程中，该PPDU的子带内是否允许PSR空间复用，如果允许，该值用于确定PSRT PPDU的发射功率限值。
CRC：用于指示对U-SIG字段中的B0-B41进行CRC的校验码。
尾部(Tail):用于终止卷积解码器的网格的字段。
图25是根据本申请实施例提供的一种通过UHR ER PPDU的U-SIG字段携带标识字段的控制信息的示意性格式图。如图25所示，该U-SIG字段包括如下字段：
标识存在字段，用于指示所述UHR PPDU中是否存在所述标识字段和/或转换时间字段；
第一数量字段，用于指示所述标识字段中包括的标识子字段的数量；
用途字段(或称类型字段)，用于指示所述标识字段的用途或类型；
第二数量字段，用于指示同一个RU中复用在一组子载波上的设备的数量。
在一些实施例中，如图25所示，所述UHR-SIG字段还包括如下字段：
物理层版本标识(PHY Version Identifier)：用于指示不同的PHY版本。
带宽(Bandwidth)：用于指示PPDU的带宽。
上行/下行(Uplink/Downlink，UL/DL)：用于指示PPDU的发送方向是上行还是下行。
TXOP：用于指示TXOP的时长信息和网络分配向量(Network Allocation Vecto，NAV)的取值。
忽略(Disregard)：用于指示忽略的保留字段。
验证(Validate)：用于验证的保留字段。
CRC：用于指示对U-SIG字段中B0-B41进行CRC的校验码。
尾部(Tail):用于终止卷积解码器的网格的字段。
应理解，上述标识字段、第一数量字段、用途字段和第二数量字段的具体实现参考前述实施例的相关描述，为了简洁，这里不再赘述。
需要说明的是，上述标识字段、第一数量字段、用途字段和第二数量字段所占的比特数，以及在U-SIG字段中的位置仅为示例，但本申请并不限于此，例如，用途字段也可以是1比特，用途字段也可以位于第一数量字段之前等。
实施例4-2：UHR PPDU包括UHR-SIG字段，标识字段的控制信息携带在UHR-SIG字段中。
在一些实施例中，UHR PPDU包括UHR-SIG字段，UHR-SIG字段包括控制字段，其中，控制字段可以包括标识存在字段、第一数量字段、用途字段和第二数量字段中的至少一个字段。
在另一些实施例中，UHR PPDU包括UHR-SIG字段，UHR-SIG字段中包括标识存在字段、第一数量字段、用途字段和第二数量字段中的至少一个字段。
在一些实施例中，UHR-SIG字段包括公共字段(Common field)和用户特定字段(User Specific field)，标识字段的控制信息可以携带在Common field字段中，或者，也可以携带在User Specific field中。
在该实施例4-2中，该UHR PPDU可以为UHR MU PPDU。
图26是根据本申请实施例提供的一种通过UHR MU PPDU的UHR-SIG字段中的Common field携带标识字段的控制信息的示意性格式图。如图26所示，该UHR-SIG字段的Common field包括如下字段：
标识存在字段，用于指示所述UHR PPDU中是否存在所述标识字段和/或转换时间字段；
第一数量字段，用于指示所述标识字段中包括的标识子字段的数量；
用途字段(或称类型字段)，用于指示所述标识字段的用途或类型；
第二数量字段，用于指示同一个RU中复用在一组子载波上的设备的数量。
在一些实施例中，如图26所示，所述UHR-SIG字段Common field还包括如下字段：
空间复用(Spatial Reuse)：用于指示在传输这个PPDU的过程中是否允许空间复用模式。
GI+LTF尺寸(GI+LTF Size)：用于指示GI的时长和UHR-LTF的类型。
UHR-LTF符号数(Number Of UHR-LTF Symbols)：用于指示UHR-LTF的符号数量。
LDPC额外符号分段(LDPC Extra Symbol Segment)：用于指示LDPC额外符号分段是否出现。
前FEC填充因子(Pre-FEC Padding Factor)：用于指示FEC前填充因子的取值。
PE消歧(PE Disambiguity)：用于指示PE Disambiguity的取值。
Non-OFDMA用户的数量(Number Of Non-OFDMA Users)：用于指示全部Non-OFDMA用户的数量。
实施例4-3：隐式指示UHR PPDU中是否包括标识字段
在一些实施例中，所述UHR PPDU中包括两个重复的UHR-STF，用于指示所述UHR PPDU中包括所述标识字段。
实施例4-4：通过标识符号指示UHR PPDU中包括标识字段
在一些实施例中，所述标识符号携带在所述UHR PPDU的Pre-UHR modulated field中，或者，也可以携带在UHR PPDU中的UHR modulated field中。
在一些实施例中，所述标识符号携带在所述UHR PPDU中的第一字段中，该第一字段可以包括如下至少一个字段：
L-SIG、RL-SIG、UHR-STF、UHR-LTF、U-SIG、UHR-SIG、数据字段。
通过在Pre-UHR modulated field携带标识符号，可以使得接收端设备尽早知道该UHR PPDU中包括标识字段，从而，可以在转换时间期间进行状态的切换，这样，该接收端设备可以发送一个和发送端设备发送的标识字段或标识子字段对齐的标识字段或标识子字段。
应理解，用于标识UHR PPDU中包括标识字段的标识符号可以是一个，或者，也可以是多个，本申请对此不作限定。
在一些实施例中，标识符号上的子载波所使用的导频映射矩阵用于指示UHR PPDU中包括标识 字段。
例如，所述标识符号上的子载波所使用的导频映射矩阵根据第一方式确定时，表示UHR PPDU中包括标识字段，当标识符号上的子载波所使用的导频映射矩阵根据第二方式确定时，表示UHR PPDU中不包括标识字段，其中，所述第一方式和第二方式不同，非标识符号上的子载波所使用的导频映射矩阵根据第二方式确定。
在一些实施例中，第二方式可以是预定义方式，例如，基于第二方式确定导频映射矩阵可以包括基于公式(1)至公式(5)确定导频映射矩阵。即第二方式可以是前述公式(1)至公式(5)所示的方式。
例如，当UHR PPDU中第一字段所占用的一个符号上的子载波所使用的导频映射矩阵基于非预定义方式确定时，可以认为该符号为标识符号，即，该UHR PPDU中包括标识字段。
对应地，接收端设备可以通过检测UHR PPDU中的第一字段所占用的符号上的子载波所使用的导频映射矩阵是否基于预定义方式确定，来确定该UHR PPDU中是否包括标识字段，例如，当第一字段所占用的符号上的子载波所使用的导频映射矩阵与根据预定义方式确定的导频映射矩阵不同时，可以认为该UHR PPDU中包括标识字段，否则，确定该UHR PPDU不包括标识字段。
以下，结合具体实施例，说明标识符号上的子载波所使用的导频映射矩阵的确定方式。
需要说明的是，以下所示例的标识符号上的子载波所使用的导频映射矩阵的计算方式仅为示例，但本申请并不限于此，只要保证标识符号上的子载波所使用的导频映射矩阵和基于预定义方式确定的导频映射矩阵不同，起到能够标识作用即可。
方式1：基于所述第一方式确定所述标识符号上的子载波所使用的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定所述标识符号上的子载波子载波的导频映射矩阵为第二导频映射矩阵，所述第一导频映射矩阵中的元素的取值为第一导频映射矩阵中的对应元素的取值的相反数。
也就是说，发送端设备可以通过将一个符号上的子载波所使用的导频映射矩阵的取值设置为基于预定义方式确定的导频映射矩阵的取值的相反数来指示UHR PPDU中包括标识字段。
对应地，接收端设备可以在一个符号上的子载波所使用的导频映射矩阵的取值为基于预定义方式确定的导频映射矩阵的取值的相反数时，确定UHR PPDU包括标识字段。
在一些实施例中，对于242-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(1)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：
其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵，表示242-tone RU中的导频子载波，表示对于242-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在一些实施例中，对于484-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(2)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：
其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵，表示对于484-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在一些实施例中，对于996-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(3)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：
其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵，表示对于996-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在一些实施例中，对于2×996-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(4)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：

其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵， 表示对于2×996-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在一些实施例中，对于4×996-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(5)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：
其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵，0表示对于4×996-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
方式2：基于所述第一方式确定所述标识符号上的子载波子载波的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定第一符号上的子载波子载波的导频映射矩阵也为第一导频映射矩阵，所述标识符号和所述第一符号为相邻符号。
也就是说，发送端设备可以通过将一个符号上的子载波所使用的导频映射矩阵设置为与相邻符号 上的子载波索使用的导频映射矩阵相同来指示UHR PPDU中包括标识字段。
对应地，接收端设备可以在相邻两个符号上的子载波所使用的导频映射矩阵和相邻符号上的子载波所使用的导频映射矩阵相同时，确定UHR PPDU包括标识字段。
在一些实施例中，第一符号是标识符号相邻的上一个符号，或者，也可以是标识符号相邻的后一个符号，本申请对此不作限定。
在一些实施例中，对于242-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(1)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：
其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵，，表示242-tone RU中的导频子载波，表示对于242-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在一些实施例中，对于484-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(2)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：
其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵，表示对于484-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在一些实施例中，对于996-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(3)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：
其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵，表示对于996-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在一些实施例中，对于2×996-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(4)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：

其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵，0表示对于2×996-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在一些实施例中，对于4×996-tone RU，基于第二确定标识符号n上的子载波所使用的导频预编码矩阵包括：根据前述公式(5)确定标识符号n上的子载波所使用的导频预编码矩阵。
对应地，基于第一方式确定标识符号n上的子载波的导频映射矩阵可以包括：
根据如下公式确定标识符号n上的子载波的导频映射矩阵：
其中，表示基于第一方式确定的子载波集合对应的导频映射矩阵，0表示对于4×996-tone RU中的非导频子载波，对应的导频映射矩阵取值为0。
在上述示例中，标识符号n上的子载波的导频映射矩阵和基于第二方式确定的上一个符号(即符号n-1)上的子载波的导频映射矩阵相同，或者，标识符号n上的子载波的导频映射矩阵也可以和基于第二方式确定的下一个符号(即符号n+1)上的子载波的导频映射矩阵相同，实现方式类似，这里不再赘述。
在一些实施例中，Ψm(m＝0,1,2…,7)的取值可以是预定义的，例如如前述表5所示。
在本申请一些实施例中，所述方法200还包括：
所述接收端设备的物理层PHY向所述接收端设备的站点管理实体(Station Management Entity，SME)或媒体接入控制MAC子层管理实体(MAC子层管理实体(MAC sublayer management entity，MLME)发送第一原语，所述第一原语用于指示接收端设备的PHY从一个或多个UHR PPDU获取的发送端设备的探测结果。
在一些实施例中，所述发送端设备的探测结果包括以下中的至少之一：
从所述标识字段探测到的发送端设备的数量；
从所述标识字段探测到的发送端设备的标识列表；
从所述标识字段探测到的发送端设备的状态信息；
所述标识字段的用途。
在一些实施例中，发送端设备的数量信息可以是根据UHR PPDU或标识字段的数量确定的，例如在一个UHR PPDU的标识字段中的所有标识子字段均由同一个发送端设备发送的情况下，可以根据UHR PPDU或标识字段的数量确定发送端设备的数量，或者，也可以是根据标识子字段的数量确定的，例如，在UHR PPD的标识字段中的不同的标识子字段由不同的发送端设备发送的情况下，可以根据UHR PPDU中的标识子字段的数量确定发送端设备的数量。
在一些实施例中，发送端设备的标识列表可以是根据UHR PPDU中的标识字段或标识子字段所使用的子载波集合确定的。
在一些实施例中，发送端设备的状态信息可以是根据UHR PPDU中的标识字段或标识子字段所使用的子载波集合确定的。例如，在前述实施例3-1中，一个发送端设备对应两个子载波集合，不同 的子载波集合可以用于指示发送端设备的不同状态信息，因此，可以根据UHR PPDU中的标识字段或标识子字段所使用的子载波集合确定发送端设备的状态信息。
在一些实施例中，标识字段的用途可以是从前述实施例中的用途字段获取的。
在一些实施例中，接收端设备的PHY可以定义如下发送矢量参数和接收矢量参数中的至少之一：
UIE_NUM_USER，用于指示从标识字段探测到的用户数(即发送端设备的数量)(接收矢量参数)；
UIE_USER_INDEX，用于指示从标识字段探测到的用户(即发送端设备)的标识列表，例如AID，UID或MAC地址等(接收矢量参数)；
UIE_STATUS，用于指示从标识字段探测到的用户的状态列表(接收矢量参数)；
UIE_PRESENT，用于指示PPDU中是否存在UIE字段(发送矢量参数)；
NUM_UIE_SUBFIELD，用于指示UIE字段中包括的UIE子字段的数量(发送矢量参数)；
UIE_TONE_SET_INDEX，用于指示UIE字段所使用的子载波集合(即tone set)(发送矢量参数)；
UIE_TYPE，用于指示UIE字段的用途或类型(发送矢量参数和接收矢量参数)；
NUMBER_OF_SPATIALLY_MULTIPLEXED_USERS，用于指示复用在同一个子载波集合上的用户数(发送矢量参数)。
在一些实施例中，上述发送矢量参数和接收矢量参数可以是在UHR PPDU为UHR MU PPDU、UHR TB PPDU或UHR ER PPDU的情况下存在。
在一些实施例中，第一原语或称PHY-UIE上报.指示原语(PHY-UIEREPORT.indication)，或探测结果指示原语等，本申请对于该第一原语的命名不作具体限定。
在一些实施例中，第一原语(PHY-UIEREPORT.indication)的原语参数如下：
PHY-UIEREPORT.indication(
UIE_NUM_USER,
UIE_USER_INDEX,
UIE_STATUS,
UIE_TYPE
)
其中，UIE_NUM_USER表示从UIE字段中探测到的用户的数量。
UIE_USER_INDEX表示接收端设备所探测到用户的标识信息的列表，长度等于UIE_NUM_USER的取值。这里的标识信息可能是AID、UID或MAC地址或用于标识用户身份的符号。当UIE_NUM_USER参数的取值为0时，该参数不存在。
UIE_STATUS，用于指示所探测到用户的状态的列表，其中，列表中的第i个状态与USER_INDEX中的第i个用户的标识信息对应。
UIE_TYPE，用于指示UIE字段的用途。
在一些实施例中，所述第一原语在所述接收端设备的PHY成功接收所述标识字段并完成所述标识字段的发送端设备的探测时生成，用于向所述接收端设备的MLME或SME上报所述发送端设备的探测结果。
在一些实施例中，所述接收端设备的SME或MLME通过所述第一原语获取所述发送端设备的探测结果。
以下，结合图27至图34，说明第一原语的接收流程。
图27和图28所示的接收流程可以适用于实施例1-1中的UHR PPDU格式设计，即，即UHR PPDU可以包括UIE字段，不包括PE字段。
图27示出了根据本申请实施例的一种第一原语的接收流程的示意性图。在图27的示例中，该UHR PPDU可以为UHR MU PPDU和UHR ER PPDU，具体执行流程如下：
当接收端设备的PHY接收到UHR MU PPDU和UHR ER PPDU的L-STF字段后，需要测量传统接收的信号强度指示(Received Signal Strength Indication，RSSI)(RSSI_LEGACY)并通过PHY-CCA.指示原语(PHY-CCA.indication)来告知MAC此时主信道(primary channel)繁忙(busy)，此时，接收端设备进入载波监听(carrier sensing，CS)或空闲信道评估(Clear Channel Assessment，CCA)状态。
然后，PHY接收后续的训练序列字段和信令字段，并将L-SIG、U-SIG、UHR-SIG和RSSI通过PHY-接收开始.指示原语(PHY-RXSTART.indication)以RXVECTOR的形式上报给接收端设备的MAC。然后，接收端设备的PHY接收数据字段，解码解扰该数据字段后还原物理层协议服务单元(Physical Layer Protocol Service Unit，PPSU)并通过PHY-数据.指示原语(PHY-DATA.indication)上报给接收端设备的MAC，此时，接收端设备进入接收状态(Rx state)。如果UIE字段存在，接收 端设备的PHY需要在接收UIE字段之后通过PHY-UIE上报.指示原语(PHY-UIEREPORT.indication)将多用户的探测结果上报给接收端设备的MAC。如果信号扩展(Signal Extension)字段存在，接收端设备的PHY需要在Signal Extension字段之后通过PHY-接收结束.指示原语(PHY-RXEND.indication)以RXVECTOR的形式告知接收端设备的MAC接收没有错误，并且用过PHY-CCA.指示原语(PHY-CCA.inciation)告知接收端设备的MAC此时信道空闲。
图28示出了根据本申请实施例的另一种第一原语的接收流程的示意性图。在图28的示例中，该UHR PPDU可以为UHR TB PPDU，该UHR PPDU可以采用实施例1-1中的格式设计，即UHR PPDU可以包括UIE字段，不包括PE字段。具体执行流程如下：
当接收端设备的PHY接收到UHR TB PPDU的L-STF字段后，需要测量传统RSSI(RSSI_LEGACY)并通过PHY-CCA.指示原语(PHY-CCA.indication)来告知MAC此时主信道(primary channel)繁忙(busy)，此时，接收端设备进入CS或CCA状态。
然后，PHY接收后续的训练序列字段和信令字段，并将L-SIG、U-SIG、UHR-SIG和RSSI通过PHY-接收开始.指示原语(PHY-RXSTART.indication)以RXVECTOR的形式上报给接收端设备的MAC。然后，接收端设备的PHY接收数据字段，解码解扰该数据字段后还原物理层协议服务单元(Physical Layer Protocol Service Unit，PPSU)并通过PHY-数据.指示原语(PHY-DATA.indication)上报给接收端设备的MAC，此时，接收端设备进入接收状态(Rx state)。如果UIE字段存在，接收端设备的PHY需要在接收UIE字段之后通过PHY-UIE上报.指示原语(PHY-UIEREPORT.indication)将多用户的探测结果上报给接收端设备的MAC。如果信号扩展(Signal Extension)字段存在，接收端设备的PHY需要在Signal Extension字段之后通过PHY-接收结束.指示原语(PHY-RXEND.indication)以RXVECTOR的形式告知接收端设备的MAC接收没有错误，并且用过PHY-CCA.指示原语(PHY-CCA.inciation)告知接收端设备的MAC此时信道空闲。
图29和图30所示的接收流程可以适用于实施例1-2中的UHR PPDU格式设计，即，即UHR PPDU可以包括转换时间字段和UIE字段，不包括PE字段。
图29示出了根据本申请实施例的又一种第一原语的接收流程的示意性图。在图29的示例中，该UHR PPDU可以为UHR MU PPDU和UHR ER PPDU，具体执行流程如下：
当接收端设备的PHY接收到UHR MU PPDU和UHR ER PPDU的L-STF字段后，需要测量传统RSSI(RSSI_LEGACY)并通过PHY-CCA.指示原语(PHY-CCA.indication)来告知MAC此时主信道(primary channel)繁忙(busy)，此时，接收端设备进入CS或CCA状态。
然后，PHY接收后续的训练序列字段和信令字段，并将L-SIG、U-SIG、UHR-SIG和RSSI通过PHY-接收开始.指示原语(PHY-RXSTART.indication)以RXVECTOR的形式上报给接收端设备的MAC。然后，接收端设备的PHY接收数据字段，解码解扰该数据字段后还原物理层协议服务单元(Physical Layer Protocol Service Unit，PPSU)并通过PHY-数据.指示原语(PHY-DATA.indication)上报给接收端设备的MAC，此时，接收端设备进入接收状态(Rx state)。
如果转换时间字段存在，接收端设备需要接收该字段。如果UIE字段存在，接收端设备的PHY需要在接收UIE字段之后通过PHY-UIE上报.指示原语(PHY-UIEREPORT.indication)将多用户的探测结果上报给接收端设备的MAC。如果信号扩展(Signal Extension)字段存在，接收端设备的PHY需要在Signal Extension字段之后通过PHY-接收结束.指示原语(PHY-RXEND.indication)以RXVECTOR的形式告知接收端设备的MAC接收没有错误，并且用过PHY-CCA.指示原语(PHY-CCA.inciation)告知接收端设备的MAC此时信道空闲。
图30示出了根据本申请实施例的又一种第一原语的接收流程的示意性图。在图30的示例中，该UHR PPDU可以为UHR MU PPDU和UHR ER PPDU。具体执行流程如下：
当接收端设备的PHY接收到UHR TB PPDU的L-STF字段后，需要测量传统RSSI(RSSI_LEGACY)并通过PHY-CCA.指示原语(PHY-CCA.indication)来告知MAC此时主信道(primary channel)繁忙(busy)，此时，接收端设备进入CS或CCA状态。
然后，PHY接收后续的训练序列字段和信令字段，并将L-SIG、U-SIG、UHR-SIG和RSSI通过PHY-接收开始.指示原语(PHY-RXSTART.indication)以RXVECTOR的形式上报给接收端设备的MAC。然后，接收端设备的PHY接收数据字段，解码解扰该数据字段后还原物理层协议服务单元(Physical Layer Protocol Service Unit，PPSU)并通过PHY-数据.指示原语(PHY-DATA.indication)上报给接收端设备的MAC，此时，接收端设备进入接收状态(Rx state)。
如果转换时间字段存在，接收端设备需要接收该字段。如果UIE字段存在，接收端设备的PHY需要在接收UIE字段之后通过PHY-UIE上报.指示原语(PHY-UIEREPORT.indication)将多用户的探测结果上报给接收端设备的MAC。如果信号扩展(Signal Extension)字段存在，接收端设备的PHY 需要在Signal Extension字段之后通过PHY-接收结束.指示原语(PHY-RXEND.indication)以RXVECTOR的形式告知接收端设备的MAC接收没有错误，并且用过PHY-CCA.指示原语(PHY-CCA.inciation)告知接收端设备的MAC此时信道空闲。
图31和图32所示的接收流程可以适用于实施例1-3中的UHR PPDU格式设计，即，即UHR PPDU可以包括UIE字段和PE字段。
图31示出了根据本申请实施例的一种第一原语的接收流程的示意性图。在图31的示例中，该UHR PPDU可以为UHR MU PPDU和UHR ER PPDU，具体执行流程如下：
当接收端设备的PHY接收到UHR MU PPDU和UHR ER PPDU的L-STF字段后，需要测量传统接收的信号强度指示(Received Signal Strength Indication，RSSI)(RSSI_LEGACY)并通过PHY-CCA.指示原语(PHY-CCA.indication)来告知MAC此时主信道(primary channel)繁忙(busy)，此时，接收端设备进入载波监听(carrier sensing，CS)或空闲信道评估(Clear Channel Assessment，CCA)状态。
然后，PHY接收后续的训练序列字段和信令字段，并将L-SIG、U-SIG、UHR-SIG和RSSI通过PHY-接收开始.指示原语(PHY-RXSTART.indication)以RXVECTOR的形式上报给接收端设备的MAC。然后，接收端设备的PHY接收数据字段，解码解扰该数据字段后还原物理层协议服务单元(Physical Layer Protocol Service Unit，PPSU)并通过PHY-数据.指示原语(PHY-DATA.indication)上报给接收端设备的MAC，此时，接收端设备进入接收状态(Rx state)。如果UIE字段存在，接收端设备的PHY需要在接收UIE字段之后通过PHY-UIE上报.指示原语(PHY-UIEREPORT.indication)将多用户的探测结果上报给接收端设备的MAC。如果PE字段存在，接收端设备的PHY需要接收该字段。如果信号扩展(Signal Extension)字段存在，接收端设备的PHY需要在Signal Extension字段之后通过PHY-接收结束.指示原语(PHY-RXEND.indication)以RXVECTOR的形式告知接收端设备的MAC接收没有错误，并且用过PHY-CCA.指示原语(PHY-CCA.inciation)告知接收端设备的MAC此时信道空闲。
图32示出了根据本申请实施例的另一种第一原语的接收流程的示意性图。在图32的示例中，该UHR PPDU可以为UHR TB PPDU。具体执行流程如下：
当接收端设备的PHY接收到UHR TB PPDU的L-STF字段后，需要测量传统RSSI(RSSI_LEGACY)并通过PHY-CCA.指示原语(PHY-CCA.indication)来告知MAC此时主信道(primary channel)繁忙(busy)，此时，接收端设备进入CS或CCA状态。
然后，PHY接收后续的训练序列字段和信令字段，并将L-SIG、U-SIG、UHR-SIG和RSSI通过PHY-接收开始.指示原语(PHY-RXSTART.indication)以RXVECTOR的形式上报给接收端设备的MAC。然后，接收端设备的PHY接收数据字段，解码解扰该数据字段后还原物理层协议服务单元(Physical Layer Protocol Service Unit，PPSU)并通过PHY-数据.指示原语(PHY-DATA.indication)上报给接收端设备的MAC，此时，接收端设备进入接收状态(Rx state)。如果UIE字段存在，接收端设备的PHY需要在接收UIE字段之后通过PHY-UIE上报.指示原语(PHY-UIEREPORT.indication)将多用户的探测结果上报给接收端设备的MAC。如果PE字段存在，接收端设备的PHY需要接收该字段。如果信号扩展(Signal Extension)字段存在，接收端设备的PHY需要在Signal Extension字段之后通过PHY-接收结束.指示原语(PHY-RXEND.indication)以RXVECTOR的形式告知接收端设备的MAC接收没有错误，并且用过PHY-CCA.指示原语(PHY-CCA.inciation)告知接收端设备的MAC此时信道空闲。
图33和图34所示的接收流程可以适用于实施例1-4中的UHR PPDU格式设计，即，即UHR PPDU可以包括转换时间字段、UIE字段和PE字段。
图33示出了根据本申请实施例的又一种第一原语的接收流程的示意性图。在图33的示例中，该UHR PPDU可以为UHR MU PPDU和UHR ER PPDU，具体执行流程如下：
当接收端设备的PHY接收到UHR MU PPDU和UHR ER PPDU的L-STF字段后，需要测量传统RSSI(RSSI_LEGACY)并通过PHY-CCA.指示原语(PHY-CCA.indication)来告知MAC此时主信道(primary channel)繁忙(busy)，此时，接收端设备进入CS或CCA状态。
然后，PHY接收后续的训练序列字段和信令字段，并将L-SIG、U-SIG、UHR-SIG和RSSI通过PHY-接收开始.指示原语(PHY-RXSTART.indication)以RXVECTOR的形式上报给接收端设备的MAC。然后，接收端设备的PHY接收数据字段，解码解扰该数据字段后还原物理层协议服务单元(Physical Layer Protocol Service Unit，PPSU)并通过PHY-数据.指示原语(PHY-DATA.indication)上报给接收端设备的MAC，此时，接收端设备进入接收状态(Rx state)。
如果转换时间字段存在，接收端设备需要接收该字段。如果UIE字段存在，接收端设备的PHY 需要在接收UIE字段之后通过PHY-UIE上报.指示原语(PHY-UIEREPORT.indication)将多用户的探测结果上报给接收端设备的MAC。如果PE字段存在，接收端设备的PHY需要接收该字段。如果信号扩展(Signal Extension)字段存在，接收端设备的PHY需要在Signal Extension字段之后通过PHY-接收结束.指示原语(PHY-RXEND.indication)以RXVECTOR的形式告知接收端设备的MAC接收没有错误，并且用过PHY-CCA.指示原语(PHY-CCA.inciation)告知接收端设备的MAC此时信道空闲。
图34示出了根据本申请实施例的又一种第一原语的接收流程的示意性图。在图34的示例中，该UHR PPDU可以为UHR MU PPDU和UHR ER PPDU。具体执行流程如下：
当接收端设备的PHY接收到UHR TB PPDU的L-STF字段后，需要测量传统RSSI(RSSI_LEGACY)并通过PHY-CCA.指示原语(PHY-CCA.indication)来告知MAC此时主信道(primary channel)繁忙(busy)，此时，接收端设备进入CS或CCA状态。
然后，PHY接收后续的训练序列字段和信令字段，并将L-SIG、U-SIG、UHR-SIG和RSSI通过PHY-接收开始.指示原语(PHY-RXSTART.indication)以RXVECTOR的形式上报给接收端设备的MAC。然后，接收端设备的PHY接收数据字段，解码解扰该数据字段后还原物理层协议服务单元(Physical Layer Protocol Service Unit，PPSU)并通过PHY-数据.指示原语(PHY-DATA.indication)上报给接收端设备的MAC，此时，接收端设备进入接收状态(Rx state)。
如果转换时间字段存在，接收端设备需要接收该字段。如果UIE字段存在，接收端设备的PHY需要在接收UIE字段之后通过PHY-UIE上报.指示原语(PHY-UIEREPORT.indication)将多用户的探测结果上报给接收端设备的MAC。如果PE字段存在，接收端设备的PHY需要接收该字段。如果信号扩展(Signal Extension)字段存在，接收端设备的PHY需要在Signal Extension字段之后通过PHY-接收结束.指示原语(PHY-RXEND.indication)以RXVECTOR的形式告知接收端设备的MAC接收没有错误，并且用过PHY-CCA.指示原语(PHY-CCA.inciation)告知接收端设备的MAC此时信道空闲。
以下，结合图35至图40，说明根据本申请实施例的UHR PPDU的MU探测方法。
图35示出了根据本申请实施例提供的UHR PPDU的一种UL MU探测方法，在该示例中，AP可以是接收端设备，发送端设备可以包括三个Non-AP STA(STA1、STA2和STA3)，UHR PPDU格式可以采用实施例1-1和实施例1-3中的格式设计。具体探测流程如下：
STA1、STA2和STA3可以主动发送包括标识字段的UHR MU PPDU或者UHR ER PPDU，其中，STA1发送的上行UHR MU PPDU或者UHR ER PPDU中的UIE字段指示了STA1的标识信息，STA2发送的上行UHR MU PPDU或者UHR ER PPDU中的UIE字段指示了STA2的标识信息，STA3发送的上行UHR MU PPDU或者UHR ER PPDU中的UIE字段指示了STA3的标识信息。
对应地，AP可以接收到混叠在一起的三个UHR MU PPDU或者UHR ER PPDU，AP通过检测UHR MU PPDU或者UHR ER PPDU中的UIE字段所使用的子载波(例如检测哪些子载波上有能量和/或有能量的子载波上的取值)，从而探测出混叠的UIE字段中分别包括STA 1、STA 2和STA 3发送的UIE字段，从而可以实现AP侧的UL MU探测。
图36示出了根据本申请实施例提供的UHR PPDU的一种DL MU探测方法，在该示例中，STA可以是接收端设备，发送端设备可以包括三个AP(AP1、AP2和AP3)，UHR PPDU格式可以采用实施例1-1和实施例1-3中的格式设计。具体探测流程如下：
AP1、AP2和AP3可以主动发送包括标识字段的UHR MU PPDU或者UHR ER PPDU，其中，AP1发送的UHR MU PPDU或者UHR ER PPDU中的UIE字段指示了AP1的标识信息，AP2发送的UHR MU PPDU或者UHR ER PPDU中的UIE字段指示了AP2的标识信息，AP3发送的UHR MU PPDU或者UHR ER PPDU中的UIE字段指示了AP3的标识信息。
对应地，STA可以接收到混叠在一起的三个UHR MU PPDU或者UHR ER PPDU，通过检测UHR MU PPDU或者UHR ER PPDU中的UIE字段所使用的子载波(例如检测哪些子载波上有能量和/或有能量的子载波上的取值)，从而探测出混叠的UIE字段中分别包括AP1、AP2和AP3发送的UIE字段，从而可以实现STA侧的DLMU探测。
图37示出了根据本申请实施例提供的UHR PPDU的另一种UL MU探测方法，在该示例中，AP可以是接收端设备，发送端设备可以包括三个Non-AP STA(STA1、STA2和STA3)，UHR PPDU格式可以采用实施例1-1和实施例1-3中的格式设计。具体探测流程如下：
AP首先发送包括随机接入资源单元(Random Access RU，RA-RU)的触发帧，即触发帧中包括需要竞争的RU资源，在一些情况下，STA1、STA2和STA3可以同时发送包括UIE字段的UHR TBPPDU，其中，STA1发送的UHR TB PPDU中的UIE字段指示了STA1的标识信息，STA2发送的 UHR TB PPDU中的UIE字段指示了STA2的标识信息，STA3发送的UHR TB PPDU中的UIE字段指示了STA3的标识信息。
对应地，AP可以接收到混叠在一起的UHR TB PPDU，通过检测UHR TB PPDU中的UIE字段所使用的子载波(例如检测哪些子载波上有能量和/或有能量的子载波上的取值)，从而探测出混叠的UIE字段中分别包括STA 1、STA 2和STA 3发送的UIE字段，从而可以实现AP侧的UL MU探测。
图38示出了根据本申请实施例提供的UHR PPDU的另一种UL MU探测方法，在该示例中，AP可以是接收端设备，发送端设备可以包括三个Non-AP STA(STA1、STA2和STA3)，UHR PPDU格式可以采用实施例1-2和实施例1-4中的格式设计。具体探测流程如下：
STA 1可以发送含有UIE字段(记为UIE-1字段)的UHR MU PPDU或UHR ER PPDU，该UIE-1字段用于标识STA1的标识信息。
STA 2和STA 3在接收到该PPDU后，判断该PPDU中是否包含UIE字段。例如，STA2和STA3可以根据前述实施例4中所述的方式，确定PPDU中包含UIE字段，可以提供多用户检测。
进一步地，STA 2和STA 3在转换时间期间进行状态转换(例如从接收状态切换为发送状态)，然后同时发送与UIE-1字段对齐的UIE字段，分别为用于指示STA 2的标识信息的UIE-2字段以及用于指示STA 3的标识信息的UIE-3字段。
对应地，AP侧会接收到STA 1的PPDU的前导和数据部分以及混叠在一起的UIE-1字段、UIE-2字段和UIE-3字段。AP可以通过检测UIE字段所使用的子载波，从而探测出混叠的UIE字段中包含STA 1、STA 2和STA 3的UIE字段，从而完成了在AP侧的UL MU探测。
图39示出了根据本申请实施例提供的UHR PPDU的另一种MU探测方法，在该示例中，STA3可以是接收端设备，发送端设备可以包括AP、STA1和STA2，UHR PPDU格式可以采用实施例1-2和实施例1-4中的格式设计。具体探测流程如下：
AP可以发送含有UIE字段(即为UIE-0字段)的UHR MU PPDU或UHR ER PPDU，该，该UIE-0字段用于标识AP的标识信息。
STA 1和STA 2在接收到该PPDU后，判断该PPDU中是否包含UIE字段。例如，STA1和STA2可以根据前述实施例4中所述的方式，确定PPDU中包含UIE字段，可以提供多用户检测。
进一步地，STA1和STA 2在转换时间期间进行状态转换(例如从接收状态切换为发送状态)，然后同时发送与UIE-0字段对齐的UIE字段，分别为用于指示STA 1的标识信息的UIE-1字段以及用于指示STA2的标识信息的UIE-2字段。
对应地，STA3侧会接收到AP发送的PPDU的前导和数据部分以及混叠在一起的UIE-0字段、UIE-1字段和UIE-2字段。STA3可以通过检测UIE字段中的UIE字段所使用的子载波，从而探测出混叠的UIE字段中含有AP、STA 1和STA 2的UIE字段，从而完成了在STA3侧的UL MU探测。
图40示出了根据本申请实施例提供的UHR PPDU的又一种MU探测方法，在该示例中，AP可以是接收端设备，发送端设备可以包括STA1、STA2和STA3，UHR PPDU格式可以采用实施例1-2和实施例1-4中的格式设计。具体探测流程如下：
AP首先Trigger帧触发STA 1发送UHR TB PPDU，该UHR TB PPDU中发送含有UIE字段(记为UIE-1字段)，该UIE-1字段用于标识STA1的标识信息。
STA 2和STA 3在接收到该PPDU后，判断该PPDU中是否包含UIE字段。例如，STA2和STA3可以根据前述实施例4中所述的方式，确定PPDU中包含UIE字段，可以提供多用户检测。
进一步地，STA 2和STA 3在转换时间期间进行状态转换(例如从接收状态切换为发送状态)，然后同时发送与UIE-1字段对齐的UIE字段，分别为用于指示STA 2的标识信息的UIE-2字段以及用于指示STA 3的标识信息的UIE-3字段。
对应地，AP侧会接收到STA 1的PPDU的前导和数据部分以及混叠在一起的UIE-1字段、UIE-2字段和UIE-3字段。AP可以通过检测UIE字段所使用的子载波，从而探测出混叠的UIE字段中包括STA 1，STA 2和STA 3的UIE字段，从而完成了在AP侧的UL MU探测。
综上，在本申请实施例中，接收端设备可以通过发送端设备发送的UHR PPDU中的标识字段识别发送端设备的身份，从而可以实现MU探测。本申请实施例所提供的UHR PPDU，不需要与NFRP Trigger帧绑定使用，在AP未获得TXOP的情况下也可以通过某个上行或下行的PPDU中的标识字段完成MU探测，从而扩展了MU探测的使用时机和使用场景，可以在不同的场景中实现多用户检测的功能。
上文结合图9至图40，详细描述了本申请的方法实施例，下文结合图41至图7，详细描述本申请的装置实施例，应理解，装置实施例与方法实施例相互对应，类似的描述可以参照方法实施例。
图41示出了根据本申请实施例的发送端设备400的示意性框图。如图41所示，该发送端设备400包括：
通信单元410，用于发送超高可靠性UHR物理层协议数据单元PPDU，所述UHR PPDU包括标识字段，所述标识字段用于指示所述发送端设备的标识信息。
在一些实施例中，所述标识字段所使用的子载波用于指示所述发送端设备的标识信息。
在一些实施例中，所述UHR PPDU为超高可靠性多用户物理层协议数据单元UHR MU PPDU、超高可靠性基于触发帧的物理层协议数据单元UHR TB PPDU或超高可靠性扩展距离物理层协议数据单元UHR ER PPDU。
在一些实施例中，所述UHR PPDU不包括包扩展PE字段，所述标识字段携带在所述UHR PPDU的尾部。
在一些实施例中，所述UHR PPDU包括PE字段，所述标识字段在所述PE字段之前。
在一些实施例中，所述UHR PPDU还包括转换时间字段，用于为所述UHR PPDU的接收端设备由接收状态转换为发送状态预留时间。
在一些实施例中，所述转换时间字段在所述标识字段之前。
在一些实施例中，所述标识字段包括一个或多个标识子字段，所述一个或多个标识子字段用于指示所述发送端设备的标识信息。
在一些实施例中，所述标识字段还包括超高可靠性短训练字段UHR-STF。
在一些实施例中，所述标识字段还包括一个或多个超高可靠性长训练字段UHR-LTF。
在一些实施例中，所述标识字段还包括传统前导字段。
在一些实施例中，所述传统前导字段包括以下字段：
传统短训练字段L-STF、传统长训练字段L-LTF、传统信号L-SIG、重复传统信号RL-SIG、统一信号U-SIG。
在一些实施例中，所述传统前导字段包括以下字段：
L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、超高可靠性信号UHR-SIG。
在一些实施例中，所述一个或多个标识子字段所使用的子载波用于指示所述发送端设备的标识信息。
在一些实施例中，所述发送端设备的标识信息对应两个子载波集合，所述标识子字段所使用的子载波属于所述两个子载波集合中的一个。
在一些实施例中，所述标识子字段所使用的子载波属于所述两个子载波集合中的不同子载波集合分别表示所述发送端设备不同的状态信息。
在一些实施例中，所述标识子字段的带宽为20MHz、40MHz、80MHz、80+80MHz、160MHz或320MHz。
在一些实施例中，所述320MHz使用4个80MHz的子载波集合索引表示，其中，子载波集合索引1-72映射到第一个80MHz，子载波集合索引73-144映射到第二个80MHz，子载波集合索引145-216映射到第三个80MHz，子载波集合索引217-288映射到第四个80MHz。
在一些实施例中，所述发送端设备的标识信息对应一个子载波集合，所述标识子字段所使用的子载波属于所述一个子载波集合。
在一些实施例中，所述发送端设备的标识信息和子载波集合的对应关系是预定义的。
在一些实施例中，所述UHR PPDU还包括控制字段，用于指示所述UHR PPDU中是否包括所述标识字段和/或所述标识字段的配置信息。
在一些实施例中，所述标识字段的配置信息包括以下中的至少之一：
所述标识字段中包括的标识子字段的数量，所述标识字段的用途，同一个资源单元RU中复用在一组子载波上的设备的数量。
在一些实施例中，所述控制字段包括以下中的至少一个字段：
标识存在字段，用于指示所述UHR PPDU中是否存在所述标识字段；
第一数量字段，用于指示所述标识字段中包括的标识子字段的数量；
用途字段，用于指示所述标识字段的用途；
第二数量字段，用于指示同一个RU中复用在一组子载波上的设备的数量。
在一些实施例中，所述UHR PPDU包括U-SIG字段，所述控制字段携带在所述U-SIG字段中。
在一些实施例中，所述UHR PPDU包括UHR-SIG字段，所述控制字段携带在所述UHR-SIG字 段中。
在一些实施例中，所述UHR PPDU中包括两个重复的UHR-STF，用于指示所述UHR PPDU中包括所述标识字段。
在一些实施例中，所述UHR PPDU中包括标识符号，所述标识符号用于指示所述UHR PPDU中包括所述标识字段。
在一些实施例中，所述标识符号携带在所述UHR PPDU中的如下至少一个字段中：
L-SIG、RL-SIG、UHR-STF、UHR-LTF、U-SIG、UHR-SIG、数据字段。
在一些实施例中，所述标识符号上的子载波的导频映射矩阵用于指示所述UHR PPDU中包括所述标识字段。
在一些实施例中，所述标识符号上的子载波的导频映射矩阵根据第一方式确定，所述第一方式和第二方式不同，所述第二方式用于确定非标识符号上的子载波的导频映射矩阵，所述第二方式是预定义方式。
在一些实施例中，基于所述第一方式确定所述标识符号上的子载波所使用的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定所述标识符号上的子载波所使用的导频映射矩阵为第二导频映射矩阵，所述第一导频映射矩阵中的元素的取值为第一导频映射矩阵中的对应元素的取值的相反数。
在一些实施例中，基于所述第一方式确定所述标识符号上的子载波所使用的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定第一符号上的子载波所使用的导频映射矩阵也为第一导频映射矩阵，所述标识符号和所述第一符号为相邻符号。
在一些实施例中，用于传输所述标识字段的平均功率和用于传输所述UHR PPDU中的数据字段的平均功率相同。
在一些实施例中，所述标识字段的时长为固定值，或者，所述标识字段的时长是可变的。
在一些实施例中，所述发送端设备为接入点设备或站点设备。
可选地，在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的发送端设备400可对应于本申请方法实施例中的发送端设备，并且发送端设备400中的各个单元的上述和其它操作和/或功能分别为了实现图9至图40所示方法200中发送端设备的相应流程，为了简洁，在此不再赘述。
图42是根据本申请实施例的接收端设备的示意性框图。图42所示的接收端设备500包括：
通信单元510，用于备接收一个或多个超高可靠性UHR物理层协议数据单元PPDU，所述UHR PPDU包括标识字段，所述标识字段用于指示所述UHR PPDU的发送端设备的标识信息。
在一些实施例中，所述标识字段所使用的子载波用于指示所述UHR PPDU的发送端设备的标识信息。
在一些实施例中，所述UHR PPDU为超高可靠性多用户物理层协议数据单元UHR MU PPDU、超高可靠性基于触发帧的物理层协议数据单元UHR TB PPDU或超高可靠性扩展距离物理层协议数据单元UHR ER PPDU。
在一些实施例中，所述UHR PPDU不包括包扩展PE字段，所述标识字段携带在所述UHR PPDU的尾部。
在一些实施例中，所述UHR PPDU包括PE字段，所述标识字段在所述PE字段之前。
在一些实施例中，所述UHR PPDU还包括转换时间字段，用于为所述UHR PPDU的接收端设备由接收状态转换为发送状态预留时间。
在一些实施例中，所述转换时间字段在所述标识字段之前。
在一些实施例中，所述标识字段包括一个或多个标识子字段，所述一个或多个标识子字段用于指示所述发送端设备的标识信息。
在一些实施例中，所述标识字段还包括超高可靠性短训练字段UHR-STF。
在一些实施例中，所述标识字段还包括一个或多个超高可靠性长训练字段UHR-LTF。
在一些实施例中，所述标识字段还包括传统前导字段。
在一些实施例中，所述传统前导字段包括以下字段：
传统短训练字段L-STF、传统长训练字段L-LTF、传统信号L-SIG、重复传统信号RL-SIG、统一信号U-SIG。
在一些实施例中，所述传统前导字段包括以下字段：
L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、超高可靠性信号UHR-SIG。
在一些实施例中，所述一个或多个标识子字段所使用的子载波用于指示所述发送端设备的标识信 息。
在一些实施例中，所述发送端设备的标识信息对应两个子载波集合，所述标识子字段所使用的子载波属于所述两个子载波集合中的一个。
在一些实施例中，所述标识子字段所使用的子载波属于所述两个子载波集合中的不同子载波集合分别表示所述发送端设备不同的状态信息。
在一些实施例中，所述标识子字段的带宽为20MHz、40MHz、80MHz、80+80MHz、160MHz或320MHz。
在一些实施例中，所述320MHz使用4个80MHz的子载波集合索引表示，其中，子载波集合索引1-72映射到第一个80MHz，子载波集合索引73-144映射到第二个80MHz，子载波集合索引145-216映射到第三个80MHz，子载波集合索引217-288映射到第四个80MHz。
在一些实施例中，所述发送端设备的标识信息对应一个子载波集合，所述标识子字段所使用的子载波属于所述一个子载波集合。
在一些实施例中，所述发送端设备的标识信息和子载波集合的对应关系是预定义的。
在一些实施例中，所述UHR PPDU还包括控制字段，用于指示所述UHR PPDU中是否包括所述标识字段和/或所述标识字段的配置信息。
在一些实施例中，所述标识字段的配置信息包括以下中的至少之一：
所述标识字段中包括的标识子字段的数量，所述标识字段的用途，同一个资源单元RU中复用在一组子载波上的设备的数量。
在一些实施例中，所述控制字段包括以下中的至少一个字段：
标识存在字段，用于指示所述UHR PPDU中是否存在所述标识字段；
第一数量字段，用于指示所述标识字段中包括的标识子字段的数量；
用途字段，用于指示所述标识字段的用途；
第二数量字段，用于指示同一个RU中复用在一组子载波上的设备的数量。
在一些实施例中，所述UHR PPDU包括U-SIG字段，所述控制字段携带在所述U-SIG字段中。
在一些实施例中，所述UHR PPDU包括UHR-SIG字段，所述控制字段携带在所述UHR-SIG字段中。
在一些实施例中，所述UHR PPDU中包括两个重复的UHR-STF，用于指示所述UHR PPDU中包括所述标识字段。
在一些实施例中，所述UHR PPDU中包括标识符号，所述标识符号用于指示所述UHR PPDU中包括所述标识字段。
在一些实施例中，所述标识符号携带在所述UHR PPDU中的如下至少一个字段中：
L-SIG、RL-SIG、UHR-STF、UHR-LTF、U-SIG、UHR-SIG、数据字段。
在一些实施例中，所述标识符号上的子载波的导频映射矩阵用于指示所述UHR PPDU中包括所述标识字段。
在一些实施例中，所述标识符号上的子载波的导频映射矩阵根据第一方式确定，所述第一方式和第二方式不同，所述第二方式用于确定非标识符号上的子载波的导频映射矩阵，所述第二方式是预定义方式。
在一些实施例中，基于所述第一方式确定所述标识符号上的子载波所使用的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定所述标识符号上的子载波所使用的导频映射矩阵为第二导频映射矩阵，所述第一导频映射矩阵中的元素的取值为第一导频映射矩阵中的对应元素的取值的相反数。
在一些实施例中，基于所述第一方式确定所述标识符号上的子载波所使用的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定第一符号上的子载波所使用的导频映射矩阵也为第一导频映射矩阵，所述标识符号和所述第一符号为相邻符号。
在一些实施例中，所述接收端设备还包括：
处理单元，用于在物理层PHY向站点管理实体SME或媒体接入控制MAC子层管理实体MLME发送第一原语，所述第一原语用于指示从所述一个或多个UHR PPDU获取的发送端设备的探测结果。
在一些实施例中，所述发送端设备的探测结果包括以下中的至少之一：
从所述标识字段探测到的发送端设备的数量；
从所述标识字段探测到的发送端设备的标识列表；
从所述标识字段探测到的发送端设备的状态信息；
所述标识字段的用途。
在一些实施例中，所述第一原语在所述接收端设备的PHY成功接收所述标识字段并完成所述标 识字段的发送端设备的探测时生成，用于向所述接收端设备的MLME或SME上报所述发送端设备的探测结果。
在一些实施例中，所述接收端设备的SME或MLME通过所述第一原语获取所述发送端设备的探测结果。
在一些实施例中，用于传输所述标识字段的平均功率和用于传输所述UHR PPDU中的数据字段的平均功率相同。
在一些实施例中，所述标识字段的时长为固定值，或者，所述标识字段的时长是可变的。
在一些实施例中，所述发送端设备为接入点设备或站点设备。
在一些实施例中，所述接收端设备为站点设备或接入点设备。
可选地，在一些实施例中，上述通信单元可以是通信接口或收发器，或者是通信芯片或者片上系统的输入输出接口。上述处理单元可以是一个或多个处理器。
应理解，根据本申请实施例的接收端设备500可对应于本申请方法实施例中的接收端设备，并且接收端设备500中的各个单元的上述和其它操作和/或功能分别为了实现图9至图40所示方法200中接收端设备的相应流程，为了简洁，在此不再赘述。
图43是本申请实施例提供的一种通信设备600示意性结构图。图43所示的通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图43所示，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，如图43所示，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600具体可为本申请实施例的接收端设备，并且该通信设备600可以实现本申请实施例的各个方法中由接收端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备600具体可为本申请实施例的发送端设备，并且该通信设备600可以实现本申请实施例的各个方法中由发送端设备实现的相应流程，为了简洁，在此不再赘述。
图44是本申请实施例的芯片的示意性结构图。图44所示的芯片700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图44所示，芯片700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该芯片700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的发送端设备，并且该芯片可以实现本申请实施例的各个方法中由发送端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的接收端设备，并且该芯片可以实现本申请实施例的各个方法中由接收端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图45是本申请实施例提供的一种通信系统900的示意性框图。如图45所示，该通信系统900包括终端设备910和网络设备920。
其中，该发送端设备910可以用于实现上述方法中由发送端设备实现的相应的功能，以及该接收端设备920可以用于实现上述方法中由接收端设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规 的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的发送端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由发送端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的接收端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由接收端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的发送端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由发送端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的接收端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由接收端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的发送端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由发送端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的接收端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由接收端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际 的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (83)

  1. 一种无线通信的方法，其特征在于，包括：
    发送端设备发送超高可靠性UHR物理层协议数据单元PPDU，所述UHR PPDU包括标识字段，所述标识字段用于指示所述发送端设备的标识信息。
  2. 根据权利要求1所述的方法，其特征在于，所述标识字段所使用的子载波用于指示所述发送端设备的标识信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述UHR PPDU为超高可靠性多用户物理层协议数据单元UHR MU PPDU、超高可靠性基于触发帧的物理层协议数据单元UHR TB PPDU或超高可靠性扩展距离物理层协议数据单元UHR ER PPDU。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述UHR PPDU不包括包扩展PE字段，所述标识字段携带在所述UHR PPDU的尾部。
  5. 根据权利要求1-3中任一项所述的方法，其特征在于，所述UHR PPDU包括PE字段，所述标识字段在所述PE字段之前。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述UHR PPDU还包括转换时间字段，用于为所述UHR PPDU的接收端设备由接收状态转换为发送状态预留时间。
  7. 根据权利要求6所述的方法，其特征在于，所述转换时间字段在所述标识字段之前。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述标识字段包括一个或多个标识子字段，所述一个或多个标识子字段用于指示所述发送端设备的标识信息。
  9. 根据权利要求8所述的方法，其特征在于，所述标识字段还包括超高可靠性短训练字段UHR-STF。
  10. 根据权利要求9所述的方法，其特征在于，所述标识字段还包括一个或多个超高可靠性长训练字段UHR-LTF。
  11. 根据权利要求8-10中任一项所述的方法，其特征在于，所述标识字段还包括传统前导字段。
  12. 根据权利要求11所述的方法，其特征在于，所述传统前导字段包括以下字段：
    传统短训练字段L-STF、传统长训练字段L-LTF、传统信号L-SIG、重复传统信号RL-SIG、统一信号U-SIG。
  13. 根据权利要求11所述的方法，其特征在于，所述传统前导字段包括以下字段：
    L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、超高可靠性信号UHR-SIG。
  14. 根据权利要求8-13中任一项所述的方法，其特征在于，所述一个或多个标识子字段所使用的子载波用于指示所述发送端设备的标识信息。
  15. 根据权利要求8-14中任一项所述的方法，其特征在于，所述发送端设备的标识信息对应两个子载波集合，所述标识子字段所使用的子载波属于所述两个子载波集合中的一个。
  16. 根据权利要求15所述的方法，其特征在于，所述标识子字段所使用的子载波属于所述两个子载波集合中的不同子载波集合分别表示所述发送端设备不同的状态信息。
  17. 根据权利要求15或16所述的方法，其特征在于，所述标识子字段的带宽为20MHz、40MHz、80MHz、80+80MHz、160MHz或320MHz。
  18. 根据权利要求17所述的方法，其特征在于，所述320MHz使用4个80MHz的子载波集合索引表示，其中，子载波集合索引1-72映射到第一个80MHz，子载波集合索引73-144映射到第二个80MHz，子载波集合索引145-216映射到第三个80MHz，子载波集合索引217-288映射到第四个80MHz。
  19. 根据权利要求8-14中任一项所述的方法，其特征在于，所述发送端设备的标识信息对应一个子载波集合，所述标识子字段所使用的子载波属于所述一个子载波集合。
  20. 根据权利要求15或19所述的方法，其特征在于，所述发送端设备的标识信息和子载波集合的对应关系是预定义的。
  21. 根据权利要求1-20中任一项所述的方法，其特征在于，所述UHR PPDU还包括控制字段，用于指示所述UHR PPDU中是否包括所述标识字段和/或所述标识字段的配置信息。
  22. 根据权利要求21所述的方法，其特征在于，所述标识字段的配置信息包括以下中的至少之一：
    所述标识字段中包括的标识子字段的数量，所述标识字段的用途，同一个资源单元RU中复用在一组子载波上的设备的数量。
  23. 根据权利要求21或22所述的方法，其特征在于，所述控制字段包括以下中的至少一个字段：
    标识存在字段，用于指示所述UHR PPDU中是否存在所述标识字段；
    第一数量字段，用于指示所述标识字段中包括的标识子字段的数量；
    用途字段，用于指示所述标识字段的用途；
    第二数量字段，用于指示同一个RU中复用在一组子载波上的设备的数量。
  24. 根据权利要求21-23中任一项所述的方法，其特征在于，所述UHR PPDU包括U-SIG字段，所述控制字段携带在所述U-SIG字段中。
  25. 根据权利要求21-23中任一项所述的方法，其特征在于，所述UHR PPDU包括UHR-SIG字段，所述控制字段携带在所述UHR-SIG字段中。
  26. 根据权利要求1-25中任一项所述的方法，其特征在于，所述UHR PPDU中包括两个重复的UHR-STF，用于指示所述UHR PPDU中包括所述标识字段。
  27. 根据权利要求1-26中任一项所述的方法，其特征在于，所述UHR PPDU中包括标识符号，所述标识符号用于指示所述UHR PPDU中包括所述标识字段。
  28. 根据权利要求27所述的方法，其特征在于，所述标识符号携带在所述UHR PPDU中的如下至少一个字段中：
    L-SIG、RL-SIG、UHR-STF、UHR-LTF、U-SIG、UHR-SIG、数据字段。
  29. 根据权利要求27或28所述的方法，其特征在于，所述标识符号上的子载波的导频映射矩阵用于指示所述UHR PPDU中包括所述标识字段。
  30. 根据权利要求29所述的方法，其特征在于，所述标识符号上的子载波的导频映射矩阵根据第一方式确定，所述第一方式和第二方式不同，所述第二方式用于确定非标识符号上的子载波的导频映射矩阵，所述第二方式是预定义方式。
  31. 根据权利要求30所述的方法，其特征在于，基于所述第一方式确定所述标识符号上的子载波所使用的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定所述标识符号上的子载波所使用的导频映射矩阵为第二导频映射矩阵，所述第一导频映射矩阵中的元素的取值为第一导频映射矩阵中的对应元素的取值的相反数。
  32. 根据权利要求30所述的方法，其特征在于，基于所述第一方式确定所述标识符号上的子载波所使用的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定第一符号上的子载波所使用的导频映射矩阵也为第一导频映射矩阵，所述标识符号和所述第一符号为相邻符号。
  33. 根据权利要求1-32中任一项所述的方法，其特征在于，用于传输所述标识字段的平均功率和用于传输所述UHR PPDU中的数据字段的平均功率相同。
  34. 根据权利要求1-33中任一项所述的方法，其特征在于，所述标识字段的时长为固定值，或者，所述标识字段的时长是可变的。
  35. 根据权利要求1-34中任一项所述的方法，其特征在于，所述发送端设备为接入点设备或站点设备。
  36. 一种无线通信的方法，其特征在于，包括：
    接收端设备接收一个或多个超高可靠性UHR物理层协议数据单元PPDU，所述UHR PPDU包括标识字段，所述标识字段用于指示所述UHR PPDU的发送端设备的标识信息。
  37. 根据权利要求36所述的方法，其特征在于，所述标识字段所使用的子载波用于指示所述UHR PPDU的发送端设备的标识信息。
  38. 根据权利要求36或37所述的方法，其特征在于，所述UHR PPDU为超高可靠性多用户物理层协议数据单元UHR MU PPDU、超高可靠性基于触发帧的物理层协议数据单元UHR TB PPDU或超高可靠性扩展距离物理层协议数据单元UHR ER PPDU。
  39. 根据权利要求36-38中任一项所述的方法，其特征在于，所述UHR PPDU不包括包扩展PE字段，所述标识字段携带在所述UHR PPDU的尾部。
  40. 根据权利要求36-38中任一项所述的方法，其特征在于，所述UHR PPDU包括PE字段，所述标识字段在所述PE字段之前。
  41. 根据权利要求36-40中任一项所述的方法，其特征在于，所述UHR PPDU还包括转换时间字段，用于为所述UHR PPDU的接收端设备由接收状态转换为发送状态预留时间。
  42. 根据权利要求41所述的方法，其特征在于，所述转换时间字段在所述标识字段之前。
  43. 根据权利要求36-42中任一项所述的方法，其特征在于，所述标识字段包括一个或多个标识子字段，所述一个或多个标识子字段用于指示所述发送端设备的标识信息。
  44. 根据权利要求43所述的方法，其特征在于，所述标识字段还包括超高可靠性短训练字段UHR-STF。
  45. 根据权利要求44所述的方法，其特征在于，所述标识字段还包括一个或多个超高可靠性长 训练字段UHR-LTF。
  46. 根据权利要求43-45中任一项所述的方法，其特征在于，所述标识字段还包括传统前导字段。
  47. 根据权利要求46所述的方法，其特征在于，所述传统前导字段包括以下字段：
    传统短训练字段L-STF、传统长训练字段L-LTF、传统信号L-SIG、重复传统信号RL-SIG、统一信号U-SIG。
  48. 根据权利要求46所述的方法，其特征在于，所述传统前导字段包括以下字段：
    L-STF、L-LTF、L-SIG、RL-SIG、U-SIG、超高可靠性信号UHR-SIG。
  49. 根据权利要求43-48中任一项所述的方法，其特征在于，所述一个或多个标识子字段所使用的子载波用于指示所述发送端设备的标识信息。
  50. 根据权利要求43-49中任一项所述的方法，其特征在于，所述发送端设备的标识信息对应两个子载波集合，所述标识子字段所使用的子载波属于所述两个子载波集合中的一个。
  51. 根据权利要求50所述的方法，其特征在于，所述标识子字段所使用的子载波属于所述两个子载波集合中的不同子载波集合分别表示所述发送端设备不同的状态信息。
  52. 根据权利要求50或51所述的方法，其特征在于，所述标识子字段的带宽为20MHz、40MHz、80MHz、80+80MHz、160MHz或320MHz。
  53. 根据权利要求52所述的方法，其特征在于，所述320MHz使用4个80MHz的子载波集合索引表示，其中，子载波集合索引1-72映射到第一个80MHz，子载波集合索引73-144映射到第二个80MHz，子载波集合索引145-216映射到第三个80MHz，子载波集合索引217-288映射到第四个80MHz。
  54. 根据权利要求43-49中任一项所述的方法，其特征在于，所述发送端设备的标识信息对应一个子载波集合，所述标识子字段所使用的子载波属于所述一个子载波集合。
  55. 根据权利要求49或54所述的方法，其特征在于，所述发送端设备的标识信息和子载波集合的对应关系是预定义的。
  56. 根据权利要求36-55中任一项所述的方法，其特征在于，所述UHR PPDU还包括控制字段，用于指示所述UHR PPDU中是否包括所述标识字段和/或所述标识字段的配置信息。
  57. 根据权利要求56所述的方法，其特征在于，所述标识字段的配置信息包括以下中的至少之一：
    所述标识字段中包括的标识子字段的数量，所述标识字段的用途，同一个资源单元RU中复用在一组子载波上的设备的数量。
  58. 根据权利要求56或57所述的方法，其特征在于，所述控制字段包括以下中的至少一个字段：
    标识存在字段，用于指示所述UHR PPDU中是否存在所述标识字段；
    第一数量字段，用于指示所述标识字段中包括的标识子字段的数量；
    用途字段，用于指示所述标识字段的用途；
    第二数量字段，用于指示同一个RU中复用在一组子载波上的设备的数量。
  59. 根据权利要求56-58中任一项所述的方法，其特征在于，所述UHR PPDU包括U-SIG字段，所述控制字段携带在所述U-SIG字段中。
  60. 根据权利要求56-58中任一项所述的方法，其特征在于，所述UHR PPDU包括UHR-SIG字段，所述控制字段携带在所述UHR-SIG字段中。
  61. 根据权利要求36-60中任一项所述的方法，其特征在于，所述UHR PPDU中包括两个重复的UHR-STF，用于指示所述UHR PPDU中包括所述标识字段。
  62. 根据权利要求36-61中任一项所述的方法，其特征在于，所述UHR PPDU中包括标识符号，所述标识符号用于指示所述UHR PPDU中包括所述标识字段。
  63. 根据权利要求62所述的方法，其特征在于，所述标识符号携带在所述UHR PPDU中的如下至少一个字段中：
    L-SIG、RL-SIG、UHR-STF、UHR-LTF、U-SIG、UHR-SIG、数据字段。
  64. 根据权利要求62或63所述的方法，其特征在于，所述标识符号上的子载波的导频映射矩阵用于指示所述UHR PPDU中包括所述标识字段。
  65. 根据权利要求64所述的方法，其特征在于，所述标识符号上的子载波的导频映射矩阵根据第一方式确定，所述第一方式和第二方式不同，所述第二方式用于确定非标识符号上的子载波的导频映射矩阵，所述第二方式是预定义方式。
  66. 根据权利要求65所述的方法，其特征在于，基于所述第一方式确定所述标识符号上的子载波所使用的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定所述标识符号上的子载波所使 用的导频映射矩阵为第二导频映射矩阵，所述第一导频映射矩阵中的元素的取值为第一导频映射矩阵中的对应元素的取值的相反数。
  67. 根据权利要求65所述的方法，其特征在于，基于所述第一方式确定所述标识符号上的子载波所使用的导频映射矩阵为第一导频映射矩阵，基于所述第二方式确定第一符号上的子载波所使用的导频映射矩阵也为第一导频映射矩阵，所述标识符号和所述第一符号为相邻符号。
  68. 根据权利要求36-67中任一项所述的方法，其特征在于，所述方法还包括：
    所述接收端设备的物理层PHY向所述接收端设备的站点管理实体SME或媒体接入控制MAC子层管理实体MLME发送第一原语，所述第一原语用于指示从所述一个或多个UHR PPDU获取的发送端设备的探测结果。
  69. 根据权利要求68所述的方法，其特征在于，所述发送端设备的探测结果包括以下中的至少之一：
    从所述标识字段探测到的发送端设备的数量；
    从所述标识字段探测到的发送端设备的标识列表；
    从所述标识字段探测到的发送端设备的状态信息；
    所述标识字段的用途。
  70. 根据权利要求68或69所述的方法，其特征在于，所述第一原语在所述接收端设备的PHY成功接收所述标识字段并完成所述标识字段的发送端设备的探测时生成，用于向所述接收端设备的MLME或SME上报所述发送端设备的探测结果。
  71. 根据权利要求70所述的方法，其特征在于，所述接收端设备的SME或MLME通过所述第一原语获取所述发送端设备的探测结果。
  72. 根据权利要求36-71中任一项所述的方法，其特征在于，用于传输所述标识字段的平均功率和用于传输所述UHR PPDU中的数据字段的平均功率相同。
  73. 根据权利要求36-72中任一项所述的方法，其特征在于，所述标识字段的时长为固定值，或者，所述标识字段的时长是可变的。
  74. 根据权利要求36-73中任一项所述的方法，其特征在于，所述发送端设备为接入点设备或站点设备。
  75. 根据权利要求36-74中任一项所述的方法，其特征在于，所述接收端设备为站点设备或接入点设备。
  76. 一种发送端设备，其特征在于，包括：
    通信单元，用于发送超高可靠性UHR物理层协议数据单元PPDU，所述UHR PPDU包括标识字段，所述标识字段用于指示所述发送端设备的标识信息。
  77. 一种接收端设备，其特征在于，包括：
    通信单元，用于接收一个或多个超高可靠性UHR物理层协议数据单元PPDU，所述UHR PPDU包括标识字段，所述标识字段用于指示所述UHR PPDU的发送端设备的标识信息。
  78. 一种发送端设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至35中任一项所述的方法。
  79. 一种接收端设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求36至75中任一项所述的方法。
  80. 一种芯片，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至35中任一项所述的方法，或如权利要求36至75至任一项所述的方法。
  81. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至35中任一项所述的方法，或如权利要求36至75至任一项所述的方法。
  82. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至35中任一项所述的方法，或如权利要求36至75至任一项所述的方法。
  83. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至35中任一项所述的方法，或如权利要求36至75至任一项所述的方法。
PCT/CN2023/099195 2023-06-08 2023-06-08 无线通信的方法、发送端设备和接收端设备 Ceased WO2024250239A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202380098981.5A CN121336481A (zh) 2023-06-08 2023-06-08 无线通信的方法、发送端设备和接收端设备
PCT/CN2023/099195 WO2024250239A1 (zh) 2023-06-08 2023-06-08 无线通信的方法、发送端设备和接收端设备
US19/406,913 US20260089245A1 (en) 2023-06-08 2025-12-02 Method for wireless communication and transmitting device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/099195 WO2024250239A1 (zh) 2023-06-08 2023-06-08 无线通信的方法、发送端设备和接收端设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/406,913 Continuation US20260089245A1 (en) 2023-06-08 2025-12-02 Method for wireless communication and transmitting device

Publications (1)

Publication Number Publication Date
WO2024250239A1 true WO2024250239A1 (zh) 2024-12-12

Family

ID=93794786

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/099195 Ceased WO2024250239A1 (zh) 2023-06-08 2023-06-08 无线通信的方法、发送端设备和接收端设备

Country Status (3)

Country Link
US (1) US20260089245A1 (zh)
CN (1) CN121336481A (zh)
WO (1) WO2024250239A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230023324A1 (en) * 2022-09-30 2023-01-26 Juan Fang Apparatus, system, and method of communicating an extended range (er) physical layer (phy) protocol data unit (ppdu)
US20230087449A1 (en) * 2022-12-01 2023-03-23 Qinghua Li Modulation and coding scheme design for extended range applications
TW202316905A (zh) * 2021-10-08 2023-04-16 美商內數位專利控股公司 用於在無線區域網路中設定之多個存取點多鏈路裝置中之協調操作的方法及設備
US20230148403A1 (en) * 2022-11-30 2023-05-11 Juan Fang Preamble for extended range (er) ppdu transmission over wide channel bandwidths

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TW202316905A (zh) * 2021-10-08 2023-04-16 美商內數位專利控股公司 用於在無線區域網路中設定之多個存取點多鏈路裝置中之協調操作的方法及設備
US20230023324A1 (en) * 2022-09-30 2023-01-26 Juan Fang Apparatus, system, and method of communicating an extended range (er) physical layer (phy) protocol data unit (ppdu)
US20230148403A1 (en) * 2022-11-30 2023-05-11 Juan Fang Preamble for extended range (er) ppdu transmission over wide channel bandwidths
US20230087449A1 (en) * 2022-12-01 2023-03-23 Qinghua Li Modulation and coding scheme design for extended range applications

Also Published As

Publication number Publication date
CN121336481A (zh) 2026-01-13
US20260089245A1 (en) 2026-03-26

Similar Documents

Publication Publication Date Title
US12167469B2 (en) Random access resource unit allocation for a multiple BSSID network
US20250125840A1 (en) Wireless communication method and wireless communication terminal for signaling multi-user packet
US12407475B2 (en) Method for transmitting and receiving data in wireless communication system, and wireless communication terminal
US20230269055A1 (en) Wireless communication method using trigger information, and wireless communication terminal
US20230319884A1 (en) Wireless communication method using multiple links, and wireless communication terminal using same
US12082170B2 (en) Methods and apparatus for supporting prioritized transmission opportunity (TXOP) sharing
EP4277175A1 (en) Method for transmitting/receiving data in wireless communication system, and wireless communication terminal
US20230276415A1 (en) Method and wireless communication terminal for transmitting and receiving data in wireless communication system
JP2024177401A (ja) 無線通信システムにおいてデータを送受信するための方法及び無線通信端末
CN116601927A (zh) 定义触发帧中忽略比特的比特源及释放冗余波束成形比特
JP7667318B2 (ja) 物理レイヤプロトコルデータユニットを伝送するための方法、トリガフレームを伝送するための方法、及び装置
JP2022549399A (ja) マルチユーザ送信における送信パラメータ値を選択するための方法および装置
US20250203456A1 (en) Wireless communication method supporting trigger frame and wireless communication terminal using same
KR102445918B1 (ko) 무선 통신 방법 및 무선 통신 단말
US12193037B2 (en) Methods and apparatus for supporting wireless medium sharing
US20250132881A1 (en) Wireless communication method supporting plurality of ppdu formats, and wireless communication terminal using same
WO2024250239A1 (zh) 无线通信的方法、发送端设备和接收端设备
KR20220047108A (ko) 축약 ba 구성 및 시그널링 기법
KR20220111151A (ko) 축약 ba 구성 및 시그널링 기법

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: 23940125

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023940125

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2023940125

Country of ref document: EP

Effective date: 20260108

ENP Entry into the national phase

Ref document number: 2023940125

Country of ref document: EP

Effective date: 20260108

ENP Entry into the national phase

Ref document number: 2023940125

Country of ref document: EP

Effective date: 20260108

ENP Entry into the national phase

Ref document number: 2023940125

Country of ref document: EP

Effective date: 20260108

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112025026498

Country of ref document: BR

WWW Wipo information: withdrawn in national office

Ref document number: 2023940125

Country of ref document: EP