WO2013123905A1 - 数据帧发送、接收方法、站点及接入点 - Google Patents

数据帧发送、接收方法、站点及接入点 Download PDF

Info

Publication number
WO2013123905A1
WO2013123905A1 PCT/CN2013/071816 CN2013071816W WO2013123905A1 WO 2013123905 A1 WO2013123905 A1 WO 2013123905A1 CN 2013071816 W CN2013071816 W CN 2013071816W WO 2013123905 A1 WO2013123905 A1 WO 2013123905A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
data frame
address
sta
downlink data
Prior art date
Application number
PCT/CN2013/071816
Other languages
English (en)
French (fr)
Inventor
陈晨
戴志巍
伍天宇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2013123905A1 publication Critical patent/WO2013123905A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0061—Error detection codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information

Definitions

  • the present invention relates to wireless communication technologies, and in particular, to a data frame transmission and reception method, a station, and an access point.
  • the application scenarios based on the IEEE 802.11ah standard mainly include the following: Sensors and meters scenes, sensor and meter data backhaul (Backhaul Sensor and Meter data) scenarios and extended range wireless LANs (Extended Range Wi-Fi ) scene.
  • the first application scenario mainly includes specific applications such as smart grid, environmental/agricultural monitoring, industrial process sensors, medical, home/office automation and home sensors.
  • the analysis shows that the first application scenario is characterized in that the source nodes of the uplink data are stations (STA, STA), and the destination nodes are access points (APs); likewise, the source nodes of the downlink data are For the AP, the destination nodes are all STAs.
  • each service uses a traditional frame structure.
  • the overhead of the frame header is obviously large, and some overhead is Unnecessary, this creates a waste of resources.
  • the present invention provides a data frame transmission and reception method, a station, and an access point for conserving data frame overhead in a sensor service.
  • An aspect of the present invention provides a data frame sending method, including:
  • the access point AP generates a downlink data frame, where the downlink data frame includes a frame check sequence FCS domain and a maximum of two address domains, and the FCS domain or the at most two address domains carry the downlink data frame. Address information;
  • An aspect of the present invention provides an access point, including:
  • a first generating module configured to generate a downlink data frame, where the downlink data frame includes a frame check sequence FCS a domain and a maximum of two address domains, where the FCS domain or the at most two address domains carry receiver address information of the downlink data frame;
  • the first sending module is configured to send the downlink data frame to the station STA, so that the STA determines whether to obtain valid data in the downlink data frame according to the receiver address information of the downlink data frame.
  • An aspect of the present invention provides a data frame receiving method, including:
  • the STA receives the downlink data frame sent by the AP, and the downlink data frame includes a frame check sequence FCS domain and a maximum of two address domains.
  • An aspect of the present invention provides a site, including:
  • a first receiving module configured to receive a downlink data frame sent by the access point AP, where the downlink data frame includes a frame check sequence FCS domain and a maximum of two address domains;
  • a first acquiring module configured to acquire receiver address information of the downlink data frame carried in the FCS domain or in at most two address domains;
  • the first determining module is configured to determine, according to the received receiver address information of the downlink data frame, whether to obtain valid data in the downlink data frame.
  • Another aspect of the present invention provides a data frame sending method, including:
  • the STA generates an uplink data frame, where the uplink data frame includes one or two address domains, and the one or two address domains carry address information of the STA;
  • Yet another aspect of the present invention provides a site, including:
  • a second generating module configured to generate an uplink data frame, where the uplink data frame includes one or two address domains, where the one or two address domains carry address information of the STA;
  • the second sending module is configured to send the uplink data frame to the access point AP, so that the AP determines, according to the address information of the STA, whether to obtain valid data in the uplink data frame.
  • Another aspect of the present invention provides a data frame receiving method, including:
  • the access point AP receives an uplink data frame sent by the station STA, where the uplink data frame includes one or Two addresses i or;
  • Another aspect of the present invention provides an access point, including:
  • a second receiving module configured to receive an uplink data frame sent by the STA, where the uplink data frame includes one or two address fields;
  • a second acquiring module configured to acquire address information of the STA carried in the one or two address domains
  • a second determining module configured to determine, according to the obtained address information of the STA, whether to obtain valid data in the uplink data frame.
  • the data frame sending and receiving method, the station, and the access point are provided by the access point device, and the access point device generates a downlink data frame including an FCS domain and a maximum of two address domains, and encapsulates the receiving in the FCS domain or the maximum of two address domains.
  • the address information of the user is then sent to the site device, and the site device determines whether to receive the downlink data frame according to the address information of the receiver encapsulated in the FCS domain or the maximum of two address domains in the downlink data frame.
  • the downlink data frame in the technical solution of the present invention contains less address domain information, reduces the number of bits occupied by the downlink data frame, and reduces the overhead of the downlink data frame.
  • a data frame sending and receiving method a station, and an access point
  • the site device generates an uplink data frame including one or two address domains, and encapsulates address information of the site device in one or two address domains.
  • the access point device determines whether to effectively receive the uplink data frame according to the address information of the STA encapsulated in one or two address domains in the uplink data frame.
  • the uplink data frame in the technical solution of the present invention contains less address domain information, reduces the number of bits occupied by the uplink data frame, and reduces the overhead of the uplink data frame.
  • FIG. 1 is a flowchart of a data frame sending method according to an embodiment of the present invention
  • 2A is a schematic structural diagram of a downlink data frame provided by an embodiment
  • 2B is another schematic structural diagram of a downlink data frame according to an embodiment of the present invention.
  • 2C is a schematic structural diagram of still another downlink data frame according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a data frame receiving method according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a data frame sending method according to another embodiment of the present invention
  • FIG. 5A is a schematic structural diagram of an uplink data frame according to an embodiment
  • FIG. 5B is another schematic structural diagram of an uplink data frame according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a data frame receiving method according to another embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of an AP according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a STA according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a STA according to another embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of an AP according to another embodiment of the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention.
  • the embodiments are a part of the embodiments of the invention, and not all of the embodiments.
  • FIG. 1 is a flowchart of a data frame sending method according to an embodiment of the present invention. As shown in FIG. 1, the method of this embodiment includes:
  • Step 101 The AP generates a downlink data frame, where the downlink data frame includes a Frame Check Sequence (FCS) domain and a maximum of two address domains, where the FCS domain or the maximum of two address domains carry downlink data frames. Receiver address information.
  • FCS Frame Check Sequence
  • This embodiment is applicable to all services in which the source node of the downlink data frame is an AP, and the destination node is a STA.
  • various services under the sensor (Sensor) application scenario in the IEEE 802.11ah standard are taken as an example for description.
  • the AP optimizes the structure of the downlink data frame according to the characteristics that the source node of the downlink data frame is the AP and the destination node is the STA, and optimizes the downlink data frame to a frame that includes at most two address domains.
  • the structure is to maximize the overhead of saving downlink data frames while ensuring reliable communication.
  • the source node of the downlink data frame is the AP, and the destination node is the STA. Therefore, if the STA determines that the received data frame is downlink, the source node of the downlink data frame is the STA.
  • the AP that the STA accesses refers to the AP in the basic service set where the STA is located.
  • the STA determines that the source node of the received downlink data frame is an AP, and determines that the source address of the downlink data frame is an address of the AP. For an STA, the address of the AP is stored after the AP is successfully accessed. Therefore, the address of the AP may not be carried in the downlink data frame.
  • Frame control in existing downlink data frames The combination of "To DS and From DS" in the (Frame Control, FC) field can indicate the direction of the data frame.
  • the transmitting node since there is no forwarding of the downlink data frame in the sensor service, the transmitting node is not involved in the forwarding process. And the address information of the receiving node.
  • the downlink data frame includes the source node, the destination node, and the address information of the sending node and the receiving node in the forwarding process, and carries the address information through the four address domains.
  • the AP of this embodiment can generate a downlink data frame including only the recipient address information of the downlink data frame.
  • the receiver of the downlink data frame is a STA that accesses the AP.
  • the receiver address information of the downlink data frame may be encapsulated into the FCS field of the downlink data frame, or may be separately encapsulated in one address field of the downlink data frame.
  • the AP If the receiver address information of the downlink data frame is encapsulated in the FCS domain, the AP generates a downlink data frame without the address field.
  • the AP generates a downlink data frame that includes at most two address domains, which reduces the number of address domains compared with the prior art, reduces the number of bits occupied by the downlink data frame, and further reduces the downlink data frame. Overhead.
  • Step 102 The AP sends the downlink data frame to the STA, so that the STA determines whether to obtain valid data in the downlink data frame according to the receiver address information of the downlink data frame.
  • the AP After the AP generates a downlink data frame including only the receiver address information of the downlink data frame, the AP transmits the downlink data frame to the STA.
  • the STA determines whether to obtain valid data in the downlink data frame according to the receiver address information encapsulated in the downlink data frame.
  • the STA may first receive the entire downlink data frame, and then parse the downlink data frame, and obtain the receiver address information of the downlink data frame encapsulated in the FCS domain or the maximum two address domains of the downlink data frame, and then obtain the address information according to the acquired address information. Determine if you are the recipient of the downstream data frame. If the judgment result is yes, the STA acquires valid data in the downlink data frame; if the judgment result is no, the STA discards the downlink data frame.
  • the STA may also receive a part of the downlink data frame, for example, receiving a frame header portion including the FCS domain and the maximum of two address domains, and then parsing the received portion, and obtaining the receiver address information of the downlink data frame, and It is determined according to the obtained address information whether it is the receiver of the downlink data frame. If the judgment result is yes, the STA continues to receive the downlink data frame and further parses and obtains valid data in the downlink data; if the judgment result is no, the STA abandons the reception and deletion of the downlink data frame. In addition to the parts that have been received.
  • the AP generates a downlink data frame that includes only the receiver address information of the downlink data frame according to the characteristics of the downlink data frame, so that the downlink data frame only needs to include at most two address domains, compared with the prior art.
  • the number of address domains is reduced, the number of bits occupied by downlink data frames is reduced, and the overhead of downlink data frames is reduced.
  • the structure of the downlink data frame generated by the AP is as shown in FIG. 2A.
  • the downlink data frame includes: an FC domain, a Duration field, a Sequence Control field, and a QoS Control field. Domain), High Throughput Control Domain (HT Control Domain), Frame Body Domain (Frame Body Domain), and FCS Domain.
  • the FCS domain encapsulates the recipient address information of the downlink data frame.
  • the receiver address information of the downlink data frame may be the MAC address of the receiver.
  • OBSS Overlap Basic Service Set
  • BSS Basic Service Set
  • the recipient address information of the downlink data frame may also be the Association Identifier (AID) of the receiver.
  • the FC domain encapsulates the downlink identifier, which can be represented, for example, by a combination of "To DS and From DS".
  • Duration field Duration value is used for network allocation vector (NAV) calculation;
  • Sequence Control field used to reassemble frame fragments and filter repeated frames
  • QoS Control field used to identify the communication class or communication flow to which the frame belongs and many other QoS-related frame information
  • HT control field used to achieve related high throughput Control
  • Frame Body field Also known as the data field, responsible for passing the upper payload between workstations.
  • the receiver address information of the downlink data frame is encapsulated into the FCS domain as a factor, that is, the AP generates a data frame structure without the address domain, which is greatly reduced compared with the prior art.
  • the overhead of the data frame The STA can obtain the receiver address information by checking the FCS domain, and then compare with its own address information to confirm whether it is the receiver of the downlink data frame.
  • the downlink data frame generated by the AP includes: FC i or, address 1 or (Address 1 ), Duration i or, Sequence Control i or QoS Control field, HT control domain, Frame Body domain, and FCS domain.
  • the address field is encapsulated with the recipient address information of the downlink data frame.
  • the receiver address information of the downlink data frame may be the MAC address of the receiver.
  • the recipient address information of the downlink data frame may also be the AID of the recipient.
  • the address-domain is associated with the Receiver Address/Receiving Station Address (RA) in the prior art.
  • the FC domain is encapsulated with a downlink identifier, which can be represented, for example, by a combination of "To DS and From DS".
  • the FCS field is the same as the FCS field of the downlink data frame in the prior art.
  • the functions of the Duration field, the Sequence Control field, the QoS Control field, the HT control field, and the Frame Body field are the same as those in the structure shown in FIG. 2A, and will not be described in detail.
  • the receiver address information of the downlink data frame is encapsulated in the address field as a factor, that is, the AP generates a data frame structure including only one address field, which is related to the prior art. It greatly reduces the overhead of data frames.
  • the STA can obtain the address information of the receiver by checking the address field, and then compare with its own address information to confirm whether it is the receiver of the downlink data frame.
  • the downlink data frame includes: FC i or address i or address 2 i or ( Address 2 ), Duration ⁇ , Sequence Control field, QoS Control domain, HT control domain, Frame Body domain, and FCS domain.
  • the address field is encapsulated with the recipient address information of the downlink data frame.
  • the receiver address information of the downlink data frame may be the MAC address of the receiver.
  • the recipient address information of the downlink data frame may also be the AID of the receiver.
  • the identifier can be a Basic Service Set Identifier (BSSID) or a Short Network ID (ShortNetID).
  • BSSID Basic Service Set Identifier
  • ShortNetID Short Network ID
  • ShortNetID is an abbreviated indication of BSSID.
  • the STAs in different BSSs may use the same AID. Therefore, in the case where the OBSS exists and the AP and the STA cannot identify the BSS in other manners, the STA cannot be encapsulated only according to the address in the domain.
  • the recipient's AID identifies whether or not it is the recipient. Based on this, in the structure, the AP encapsulates the identifier of the basic service set of the receiver through the address two domain, so that the STA can simultaneously encapsulate the receiver's AID according to the identity and address of the basic service set encapsulated in the address two domain. Identify if you are the recipient.
  • the FC domain is encapsulated with a downlink identifier, which can be represented, for example, by a combination of "To DS and From DS".
  • the FCS domain is the same as the FCS domain of the downlink data frame in the prior art.
  • the work of the Duration field, the Sequence Control field, the QoS Control field, the HT control field, and the Frame Body field is the same as that in the structure shown in FIG. 2A, and details are not described herein again.
  • the receiver address information of the downlink data frame is encapsulated in the address one domain as a factor, and the identifier of the basic service set of the receiver is encapsulated in the address two domain, that is, the AP.
  • a data frame structure including only two address domains is generated, which greatly reduces the overhead of data frames compared with the prior art.
  • the STA can obtain the address information of the receiver or the address of the receiver and the identifier of the basic service set by checking the address field or the address field and the address field at the same time, and then only according to the address information or according to the address information and the basic information.
  • the identity of the service set confirms whether it is the recipient of the downstream data frame.
  • the AP is optimized for the frame structure of the IEEE 802.1 lah Sensor service. Therefore, the AP needs to know the service type supported by the STA, that is, the service type of the downlink data frame needs to be known.
  • the STA can provide the supported service type to the AP during the association with the AP. Based on this, the AP can also carry the service type of its corresponding service in the downlink data frame.
  • the AP may encapsulate the service type identifier of the service corresponding to the downlink data frame by using the FC domain.
  • an AP can use the value of a combination of type and type (subtype) in the FC domain as the service type identifier to indicate the service type.
  • the AP may also carry the service type identifier of the service corresponding to the downlink data frame by extending the new domain in the downlink data frame.
  • the AP may extend a service type identifier field in the downlink data frame, and encapsulate the service type identifier in the service type identifier field.
  • the downlink data frame may further include a service type identifier field, where the service type identifier field encapsulates the service type identifier of the service corresponding to the downlink data frame.
  • the service type identification field occupies a very small number of bits, which is much smaller than the number of bits occupied by the address domain. Therefore, although the downlink configuration data increases the service type identification field, the overall overhead.
  • FIG. 3 is a flowchart of a data frame receiving method according to an embodiment of the present invention. As shown in FIG. 3, the method of this embodiment includes:
  • Step 301 The STA receives a downlink data frame sent by the AP, where the downlink data frame includes an FCS domain and a maximum of two address domains.
  • Step 302 The STA acquires receiver address information of a downlink data frame carried in an FCS domain or a maximum of two address domains.
  • the present embodiment is applicable to downlink data frames of various services in which the source node is an AP and the destination node is a STA, for example, a downlink data frame of various services in a sensor application scenario in a standard of a wireless local area network.
  • the STA in this embodiment cooperates with the AP to receive a downlink data frame or a partial downlink data frame (mainly referred to as a frame header portion of the downlink data frame) that is optimized and compressed by the AP.
  • the downlink data frame after AP optimization and compression includes an FCS domain and a maximum of two address domains.
  • the maximum of two address domains includes three cases: an address domain, an address domain, and two address domains.
  • the AP may encapsulate the receiver address information of the downlink data frame in one of the address domains, or encapsulate the receiver address information of the downlink data frame as a factor in the FCS domain;
  • the AP encapsulates the receiver address information of the downlink data frame as a factor in the FCS domain.
  • the STA parses the received downlink data frame or part of the downlink data frame, obtains the FCS domain and the maximum of two address domains included in the downlink data frame, and then acquires the downlink data frame from the FCS domain or the maximum of two address domains. Receiver address information.
  • Step 303 The STA determines, according to the received receiver address information of the obtained downlink data frame, whether to obtain valid data in the downlink data frame.
  • the STA determines whether to obtain valid data in the downlink data frame according to the received receiver address information of the obtained downlink data frame, and mainly compares the receiver address information of the downlink data frame with the address information of the downlink data frame. Process, but not limited to this. For example, in the case where the OBSS exists and the STA cannot identify each BSS by other means, the STA also needs to identify the basic service set in which the receiver of the downlink data frame acquired from the downlink data frame is located and the basic service set in which the UE is located. The IDs are compared to determine if they belong to the same basic service set.
  • the address information used in this embodiment may be a MAC address or an AID.
  • the process of the STA acquiring the valid data in the downlink data frame is related to the manner in which the STA receives the data frame. If the STA receives the data frame and then parses the entire data frame, the STA continues to parse the received data frame after determining that it is the receiver of the data frame. Valid data. If the STA only receives part of the data frame instead of all when the data frame arrives, and parses the received partial data frame and determines whether it is the receiver of the data frame, the STA determines that it is the After receiving the data frame, the data frame continues to be received, and then the entire data frame is parsed to obtain valid data therein.
  • the STA cooperates with the AP, so that the AP can perform optimal compression on the downlink data frame.
  • the downlink data frame in this embodiment includes at most two address domains, which reduces the address domain compared with the prior art.
  • the number of bits reduces the number of bits occupied by the downlink data frame and reduces the overhead of the downlink data frame.
  • the STA obtains the receiver address information of the downlink data frame and determines whether to obtain the valid data in the downlink data frame according to the received receiver address information of the downlink data frame. The following describes the specific implementation structure of the downlink data frame.
  • the FCS domain encapsulates the receiver address information of the downlink data frame, and the FC
  • the STA parses the FC i or Duration I or the Sequence Control i or the QoS Control i or the HT control i or the Frame Body field and the FCS domain respectively included in the downlink data frame.
  • the receiver address information of the downlink data frame is obtained from the FCS domain, and the downlink identifier is obtained from the FC domain.
  • the STA based on the downlink identifier, the STA identifies that the source node of the downlink data frame is an AP, that is, the address of the default AP is the source address of the downlink data frame.
  • the process of determining, by the STA, whether the receiver is the receiver according to the receiver address information of the downlink data frame includes: if the receiver address information is the receiver's MAC address, or the receiver address information is AID, and there is no OBSS condition, or the receiver address The information is AID.
  • the STA directly compares the obtained receiver address information with its own address information (such as a MAC address or an AID); If the two address information are the same, the valid data in the downlink data frame is parsed. If the comparison result is that the two address information are different, the downlink data frame is discarded.
  • its own address information such as a MAC address or an AID
  • the FC domain, the address domain, the Duration domain, the Sequence Control domain, the QoS Control domain, the HT control domain, the Frame Body domain, and the FCS domain are included, where the address field is encapsulated with a downlink.
  • Receiver address information of the data frame, the FC domain is encapsulated with the downlink identifier, and the STA will include the FC domain, the address-domain, the Duration field, the Sequence Control domain, the QoS Control domain, the HT control domain, and the frame of the downlink data frame.
  • the body domain and the FCS domain are respectively parsed, and the receiver address information of the downlink data frame is obtained from the address domain, and the downlink identifier is obtained from the FC domain.
  • the STA based on the downlink identifier, the STA identifies that the source node of the downlink data frame is an AP, that is, the address of the default AP is the source address of the downlink data frame.
  • the process of determining, by the STA, whether the receiver is the receiver according to the receiver address information of the downlink data frame includes: if the receiver address information is the receiver's MAC address, or the receiver address information is AID, and there is no OBSS condition, or the receiver address The information is AID.
  • the STA directly compares the obtained receiver address information with its own address information (such as a MAC address or an AID); If the two address information are the same, parsing and obtaining the valid in the downlink data frame Data; if the comparison result is that the two address information are not the same, the downlink data frame is discarded.
  • its own address information such as a MAC address or an AID
  • the downlink data frame includes: an FC domain, an address domain, an address field, a Duration field, a Sequence Control field, a QoS Control field, an HT control domain, a Frame Body domain, and an FCS domain, where address one is The receiver address information of the downlink data frame is encapsulated in the domain, and the identifier of the basic service set where the receiver of the downlink data frame is encapsulated in the address 2 domain, and the downlink identifier is encapsulated in the FC domain, the STA includes the downlink data frame.
  • the FC domain, the address domain, the address 2 domain, the Duration field, the Sequence Control domain, the QoS Control domain, the HT control domain, the Frame Body domain, and the FCS domain are respectively parsed, and the receiver address of the downlink data frame is obtained from the address domain.
  • the information is obtained from the address two domain to obtain the identifier of the basic service set of the receiver, and obtain the downlink identifier from the FC domain.
  • the STA based on the downlink identifier, the STA identifies that the source node of the downlink data frame is an AP, that is, the address of the default AP is the source address of the downlink data frame.
  • the process of determining, by the STA, whether the receiver is the receiver according to the receiver address information of the downlink data frame includes: if the receiver address information is the receiver's MAC address, or the receiver address information is the AID, and there is no OBSS condition, or the receiver address The information is AID.
  • the STA directly compares the obtained receiver address information with its own address information (such as a MAC address or an AID); If the two address information are the same, the valid data in the downlink data frame is parsed. If the comparison result is that the two address information are different, the downlink data frame is discarded.
  • the STA separately identifies the identifier of the basic service set of the receiver and the AID of the receiver and the identifier of the basic service set. Compared with the AID of the STA, if the comparison result is that the identifier of the basic service set of the receiver is the same as the identifier of the basic service set of the STA, and the AID of the receiver is the same as the AID of the STA itself, the parsing is performed in the downlink data frame. Valid data, conversely, discarding downstream data frames.
  • the STA when the STA parses the FC domain, the STA also includes the service type identifier of the service corresponding to the downlink data frame from the FC domain. If the downlink data frame further includes a service type identifier field, and the service type identifier field encapsulates the service type identifier of the service corresponding to the downlink data frame, in the foregoing process, when the STA parses the downlink data frame, the STA further includes The service type identifier field in the downlink data frame is parsed, and the service type identifier of the service corresponding to the downlink data frame is obtained from the service type identifier field. In this way, the STA can determine whether the obtained service type identifier is consistent with the identifier of the service type supported by the STA, so as to further determine whether the receiver of the downlink data frame is the receiver.
  • the downlink continues in the process of effectively receiving the downlink data frame.
  • the processing of the data frame mainly refers to further parsing the downlink data frame and obtaining valid data therein (ie,
  • FIG. 4 is a flowchart of a data frame sending method according to another embodiment of the present invention. As shown in FIG. 4, the method in this embodiment includes:
  • Step 401 The STA generates an uplink data frame, where the uplink data frame includes one or two address domains, and the one or two address domains carry address information of the STA.
  • This embodiment is applicable to various services in which the source node of the uplink data frame is the STA, and the destination node is the AP, for example, various services in the sensor application scenario in the standard of the wireless local area network.
  • the destination node of the uplink data frame is an AP, and if the AP successfully receives an uplink data frame, it can be determined that the destination node of the uplink data frame must be an AP, so the uplink data frame may not be carried.
  • the address information of the destination node Based on this, the STA optimizes the structure of the uplink data frame according to the characteristics that the source node of the uplink data frame is the STA and the destination node is the AP, and optimizes the uplink data frame to include one or two address domains. In the case of ensuring communication reliability, the overhead of uplink data frames is saved to the utmost extent.
  • the destination node AP itself of the uplink data frame may be defaulted.
  • the STA can indicate the direction of the data frame by the combination of "To DS and From DS" in the FC field in the uplink data frame, that is, whether the data frame is uplink or downlink.
  • the address information of the transmitting node and the receiving node in the forwarding process is not involved.
  • the uplink data frame includes the source node, the destination node, and the address information of the sending node and the receiving node in the forwarding process, and carries the address information through the four address domains.
  • the STA of this embodiment may generate an uplink data frame including address information of a sender (ie, the STA) of the uplink data frame.
  • the receiver of the uplink data frame is the AP accessed by the STA.
  • the STA may encapsulate its address information in an address field in the uplink data frame.
  • the STA encapsulates its address information in the address field; if the uplink data frame includes two address fields, the STA encapsulates its address information in one of the address domains, and the STA The identity of the basic service set is encapsulated in another address domain.
  • Step 402 The STA sends the uplink data frame to the AP, so that the AP determines whether to obtain valid data in the uplink data frame according to the address information of the STA in the uplink data frame. After forming the uplink data frame, the STA sends the uplink data frame to the AP. After receiving the uplink data frame, the AP determines whether it is the receiver of the uplink data frame according to the address information of the STA encapsulated in one or two address domains of the uplink data frame. If it is determined that it is the receiver of the uplink data frame, It will parse the valid data in the uplink data frame.
  • the process of determining whether the receiver is the receiver of the uplink data frame or whether to obtain the valid data in the uplink data according to the address information of the STA mainly refers to determining whether the STA is the STA accessing the AP according to the address information of the STA. If the determination result is yes, the parsing further obtains valid data in the uplink data frame sent by the STA.
  • the AP may first receive the entire uplink data frame, and then parse the uplink data frame to obtain the address information of the STA encapsulated in an address field of the uplink data frame, and then determine, according to the obtained address information, whether the uplink data frame is by itself.
  • the associated STA sends, that is, determines whether it is the receiver of the uplink data frame. If the judgment result is yes, the AP parses the valid data in the received uplink data frame; if the judgment result is no, the AP discards the uplink data frame.
  • the AP may also receive a part of the uplink data frame, for example, only receiving a header portion including one or two address fields, and then parsing the received part, and obtaining the address information of the STA that sends the uplink data frame, and
  • the STA that sends the uplink data frame is determined to be the STA associated with the uplink data frame, that is, whether it is the receiver of the uplink data frame. If the judgment result is yes, the AP continues to receive the uplink data frame, and then further parses and obtains valid data in the uplink data frame; if the judgment result is no, the AP relinquishes the reception of the uplink data frame and discards the already received portion. .
  • the STA generates an uplink data frame that does not include the address information of the AP according to the characteristics of the AP of the uplink data frame, and reduces the number of address domains included in the uplink data frame, thereby reducing the occupation of the uplink data frame.
  • the number of bits reduces the overhead of the upstream data frame.
  • the structure of the uplink data frame generated by the STA is as shown in FIG. 5A, and the uplink data frame includes:
  • FC domain address three domain (address3), Duration domain, Sequence Control domain, QoS Control domain, HT control domain, Frame Body domain, and FCS domain.
  • the address three domain encapsulates the address information of the STA that transmits the uplink data frame.
  • the address information of the STA may be the MAC address of the STA.
  • the address information of the STA may also be the AID of the STA.
  • the uplink identifier is encapsulated in the FC domain, for example, by a combination of "To DS and From DS".
  • the Duration field Duration value is used for network allocation vector (NAV) calculation; Sequence Control field: used to reassemble frame fragments and filter repeated frames; QoS Control field: used to identify the communication category or communication stream to which the frame belongs and Many other QoS-related frame information; HT control domain: used to implement related high throughput control; Frame Body domain: also known as data field, responsible for transferring upper layer payloads between workstations; FCS domain: ie, cyclic redundancy Code verification, used to detect the integrity of the frame.
  • the uplink data frame includes only one address field, and the address information of the STA is encapsulated as a factor in the address field, which greatly reduces the overhead of the data frame compared with the prior art.
  • the AP checks the address field to obtain the address information of the STA, and then determines whether the STA is its associated STA, and determines whether it is the receiver of the uplink data frame.
  • the uplink data frame includes: FC i or address 3 i or address 4 i or (Address 4), Duration i or Sequence Control field, QoS Control Domain, HT Control Domain, Frame Body Domain, and FCS Domain.
  • the address three domain is encapsulated with address information of a STA that transmits an uplink data frame.
  • the address information of the STA may be the MAC address of the STA.
  • the address information of the STA may also be the AID of the STA.
  • the identifier of the basic service set where the STA is located is encapsulated in the address four domain.
  • the identifier can be BSSID or ShortNetID.
  • the STAs in different BSSs may use the same AID. Therefore, when the OBSS exists and the AP and the STA cannot identify the BSS in other manners, the AP cannot be encapsulated only according to the address three domains.
  • the STA's AID identifies whether it is a recipient. Based on this, in the structure, the STA encapsulates the identifier of the basic service set in which the STA is located by using the address four domain, so that the AP can simultaneously identify the basic service set encapsulated in the address four domain and the AID of the STA encapsulated in the address three domain. Whether you are the recipient.
  • the FC domain is encapsulated with an uplink identifier, which can be represented, for example, by a combination of "To DS and From DS".
  • the Duration field, the Sequence Control field, the QoS Control field, the HT control field, the Frame Body field, and the FCS domain are similar to the prior art, and are not described here.
  • the uplink data frame includes two address fields, and the address information of the STA is encapsulated in the address three domain, and the identifier of the basic service set where the STA is located is encapsulated in the address four domain, and the address domain is compared with the prior art. The number of bits is still reduced, greatly reducing the overhead of uplink data frames.
  • the AP can obtain the address information of the STA or the STA by checking the address three domain or simultaneously detecting the address three domain and the address four domain. The address information and the identifier of the basic service set, and then confirm whether it is the receiver of the uplink data frame only according to the address information or according to the address information and the identifier of the basic service set.
  • the STA is optimized for the frame structure of the IEEE 802.1 lah Sensor service. Therefore, the STA needs to know the type of service it supports, that is, the service type of the uplink data frame needs to be known.
  • the STA may provide the supported service type to the AP during the association with the AP. Alternatively, the STA may carry the supported service type in the uplink data frame.
  • the STA may encapsulate the service type identifier of the corresponding service of the uplink data frame by using the FC domain.
  • a STA may indicate a service type by using a group value of a combination of "type" and "subtype” in the FC domain as a service type identifier.
  • the STA may also carry the service type identifier corresponding to the uplink data frame by extending the new domain in the uplink data frame.
  • the STA may extend a service type identification field in the uplink data frame and encapsulate the service type identifier in the service type identification field.
  • the uplink data frame may further include a service type identifier field, where the service type identifier field encapsulates the service type identifier of the service corresponding to the uplink data frame.
  • the number of bits occupied by the service type identifier field is very small, which is much smaller than the number of bits occupied by the address field. Therefore, although the uplink structure data increases the service type identifier field, the overhead of the data frame.
  • FIG. 6 is a flowchart of a data frame receiving method according to another embodiment of the present invention. As shown in FIG. 6, the method in this embodiment includes:
  • Step 601 The AP receives an uplink data frame sent by the STA, where the uplink data frame includes one or two addresses i or .
  • Step 602 The AP acquires address information of the STA carried in one or two address domains.
  • the embodiment is used for receiving uplink data frames of various services, where the source node is a STA, and the destination node is an AP, for example, an uplink data frame of various services in a sensor application scenario in the IEEE 802.11ah standard.
  • the AP in this embodiment cooperates with the STA to receive an uplink data frame or a partial uplink data frame (mainly referred to as a frame header portion of the uplink data frame) that is optimized and compressed by the STA.
  • the uplink data frame after STA-optimized compression includes an address field or two address fields. Wherein, when the uplink data frame includes an address field, the STA encapsulates its address information in the address field; when the uplink data frame includes two address fields, the STA encapsulates its address information in one of the address domains. Based on this, the AP parses the received uplink data frame or part of the uplink data frame, and obtains the address information of the STA encapsulated in the address field in the uplink data frame.
  • Step 603 The AP determines, according to the obtained address information of the STA, whether to obtain the uplink data frame. valid data.
  • the process of determining, by the AP, the valid data in the uplink data frame according to the obtained address information of the STA is mainly that the AP associates the sender of the uplink data frame, that is, the address information of the STA, with all the locally stored information.
  • the process of comparing the address information of the STA to determine whether it is the receiver of the uplink data frame is not limited thereto.
  • the AP also needs to identify the basic service set in which the STA is obtained from the uplink data frame and the identity of the basic service set in which the STA is located. Compare to determine if they belong to the same basic service set.
  • the address information used in this embodiment may be a MAC address or an AID.
  • the process of the AP acquiring the valid data in the uplink data frame is related to the manner in which the AP receives the data frame. If the AP receives the data frame first and then parses the entire data frame, the AP further determines the valid data frame after determining that it is the receiver of the data frame. data. If the AP only receives part of the data frame instead of all when the data frame arrives, and parses the received partial data frame and determines whether it is the receiver of the data frame, the AP determines that it is the After receiving the data frame, the uplink data frame is continuously received, and then the entire data frame is parsed to obtain valid data therein.
  • the AP cooperates with the STA, so that the STA can perform optimal compression on the uplink data frame.
  • the uplink data frame in this embodiment includes only one or two address domains, and the address is reduced compared with the prior art.
  • the number of domains reduces the number of bits occupied by the uplink data frame and reduces the overhead of the uplink data frame.
  • the AP obtains the address information of the STA in the uplink data frame and obtains the valid data in the uplink data frame according to the obtained address information of the STA according to the specific implementation structure of the uplink data frame. If the uplink data frame is as shown in FIG. 5A, That is, the FC domain, the address three domain, the Duration domain, the Sequence Control domain, the QoS Control domain, the HT control domain, the Frame Body domain (frame body domain), and the FCS domain, where the address three domain is encapsulated with the STA that sends the uplink data frame.
  • the FC domain is encapsulated with an uplink identifier
  • the AP will include the FC domain, the address three domain, the Duration field, the Sequence Control domain, the QoS Control domain, the HT control domain, the Frame Body domain, and the FCS included in the uplink data frame.
  • the domain is parsed separately, and the address information of the STA is obtained from the address three domain, and the uplink identifier is obtained from the FC domain.
  • the AP identifies that the destination node of the uplink data frame is an AP, that is, the address of the default AP is the destination address of the uplink data frame.
  • the process of determining whether the receiver is the receiver includes: if the address information of the STA is the MAC address of the STA, or the address information of the STA is the AID, and there is no overlapping basic service set (OBSS), or the address information of the STA is the AID, though If there is an overlapping basic service set (OBSS), but the STA and the STA can identify each BSS in the OBSS by other means, the AP directly directly obtains the address information of the acquired STA and the locally stored address information of the STA (for example, a MAC address or an AID).
  • the comparison is performed; if the comparison result is that the two address information are the same, the valid data in the uplink data frame is obtained; if the comparison result is that the two address information are not the same, the uplink data frame is discarded.
  • the downlink data frame includes: an FC domain, an address three domain, an address four domain, a Duration field, a Sequence Control domain, a QoS Control domain, an HT control domain, a Frame Body domain, and an FCS domain, where address three
  • the address information of the STA that sends the uplink data frame is encapsulated in the domain, and the identifier of the basic service set where the STA is located is encapsulated in the address four domain.
  • the uplink identifier is encapsulated in the FC domain, and the AP will include the FC domain included in the uplink data frame.
  • the address three domain, the address four domain, the Duration field, the sequence control domain, the QoS control domain, the HT control domain, the frame body domain, and the FCS domain are respectively parsed, and the address information of the STA is obtained from the address three domain, and is obtained from the address four domain.
  • the identifier of the basic service set where the STA is located and obtains the uplink identifier from the FC domain. Then, based on the uplink identifier, the AP identifies that the destination node of the uplink data frame is an AP, that is, the address of the default AP is the destination address of the uplink data frame.
  • the process of determining whether the AP is the receiver according to the address information of the STA includes: If the address information of the STA is a MAC address, or the address information of the STA is an AID, and there is no overlapping basic service set (OBSS), or the address information of the STA For the AID, although there is an overlapping basic service set (OBSS), but the AP and the STA can identify each BSS in the OBSS by other means, the AP directly obtains the address information of the acquired STA and the locally stored address information of the STA (for example, The MAC address or the AID is compared. If the comparison result is the same as the two address information, the valid data in the uplink data frame is obtained.
  • OBSS overlapping basic service set
  • the uplink data frame is discarded.
  • the STA's address information is AID
  • there is an overlapping basic service set (OBSS) the STA and the STA cannot identify each BSS in the OBSS by other means
  • the AP respectively sets the identity of the basic service set of the STA and the AID of the STA and the AP itself.
  • the identifier of the basic service set is compared with the associated AID of each STA. If the comparison result is that the identifier of the basic service set of the AP itself is the same as the identifier of the basic service set where the STA is located, and the AID of the STA is associated with the AP. If the AID of an STA is the same, the valid data in the uplink data frame is obtained. Otherwise, the uplink data frame is discarded.
  • the AP when the AP parses the FC domain, the AP also includes obtaining from the FC domain.
  • the uplink data frame corresponds to the service type identifier of the service.
  • the uplink data frame further includes a service type identifier field, and the service type identifier field encapsulates the service type identifier of the service corresponding to the uplink data frame
  • the AP when the AP parses the uplink data frame, the AP further includes The service type identifier field in the uplink data frame is parsed, and the service type identifier of the service corresponding to the uplink data frame is obtained from the service type identifier field.
  • the AP can also determine whether the obtained service type identifier is consistent with the identifier of the service type supported by the STA that is already known, so as to further determine whether the receiver of the uplink data frame is the one.
  • the valid data in the uplink data frame or the downlink data frame mainly refers to the content in the Frame Body field in the uplink data frame or the downlink data frame.
  • the above method of the embodiment of the present invention is applied to a wireless local area network system, and mainly includes an AP and a STA.
  • FIG. 7 is a schematic structural diagram of an AP according to an embodiment of the present invention. As shown in FIG. 7, the AP7 of this embodiment includes: a first generating module 71 and a first sending module 72.
  • the first generation module 71 is configured to generate a downlink data frame, where the downlink data frame includes an FCS domain and a maximum of two address domains, where the FCS domain or the maximum of two address domains carries a receiver address of a downlink data frame. information.
  • the first sending module 72 is connected to the first generating module 71, and configured to send the downlink data frame generated by the first generating module 71 to the STA, so that the STA determines whether to acquire the downlink data frame according to the receiver address information of the downlink data frame. Valid data.
  • the function modules of the AP7 can be used to perform the process of the data frame sending method shown in FIG. 1.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the structure of the downlink data frame generated by the first generation module 71 in this embodiment mainly includes: FC i or Duration I or Sequence Control i or QoS Control i or HT Control field.
  • FC i or Duration I or Sequence Control i or QoS Control i or HT Control field Frame Body domain and FCS domain.
  • the FCS domain encapsulates the receiver address information of the downlink data frame, and the FC domain encapsulates the downlink identifier.
  • Another structure of the downlink data frame generated by the first generation module 71 in this embodiment is as shown in FIG. 2B, and mainly includes: FC i or, address i or duration, duration i or , Sequence Control i or QoS Control field, HT Control domain, Frame Body domain, and FCS domain.
  • the address field is encapsulated with the receiver address information of the downlink data frame
  • the FC domain is encapsulated with the downlink identifier.
  • FIG. 2C Another structure of the downlink data frame generated by the first generation module 71 in this embodiment is as shown in FIG. 2C, and mainly includes: an FC domain, an address domain, an address field, a Duration field, a Sequence Control field, a QoS Control field, and an HT. Control domain, Frame Body domain, and FCS domain.
  • the address field is encapsulated Receiver address information of the downlink data frame
  • the FC domain is encapsulated with a downlink identifier, and the address of the basic service set of the receiver in which the downlink data frame is encapsulated in the address 2 domain.
  • the structure of the downlink data frame generated by the first generation module 71 may further include: an FC domain, an address two domain, a Duration field, a Sequence Control domain, a QoS Control domain, an HT Control domain, a Frame Body domain, and an FCS domain.
  • the FCS domain encapsulates the receiver address information of the downlink data frame
  • the FC domain encapsulates the downlink identifier
  • the address 2 domain encapsulates the identifier of the basic service set of the receiver of the downlink data frame.
  • the identifier of the basic service set where the receiver of the downlink data frame is located may be the basic service set identifier.
  • BSSID or short network number ShortNetID.
  • the receiver address information of the downlink data frame may be the recipient's MAC address or AID.
  • the downlink data frame may further carry a service type identifier that identifies a service corresponding to the downlink data frame.
  • the frame control domain is encapsulated with a service type identifier that identifies a service corresponding to the downlink data frame.
  • the downlink data frame may further include a service type identifier field, where the service type identifier field encapsulates the service type identifier of the service corresponding to the downlink data frame.
  • the AP in this embodiment generates a downlink data frame including only the receiver address information of the downlink data frame according to the characteristics of the downlink data frame, so that the downlink data frame only needs to include at most two address domains, which is reduced compared with the prior art.
  • the number of address domains reduces the number of bits occupied by downlink data frames and reduces the overhead of downlink data frames.
  • FIG. 8 is a schematic structural diagram of a STA according to an embodiment of the present invention. As shown in FIG. 8, the STA8 of this embodiment includes: a first receiving module 80, a first obtaining module 81, and a first determining module 82.
  • the first receiving module 80 is configured to receive a downlink data frame sent by the AP, where the downlink data frame includes an FCS domain and a maximum of two address domains.
  • the first obtaining module 81 is connected to the first receiving module 80, and is configured to obtain the address information of the downlink data frame carried in the FCS domain or the maximum of two address domains in the downlink data frame received by the first receiving module 80.
  • the receiver address information of the downlink data frame may be the recipient's MAC address or AID.
  • the first determining module 82 is connected to the first obtaining module 81, and is configured to determine whether to obtain valid data in the downlink data frame according to the receiver address information of the downlink data frame obtained by the first acquiring module 81.
  • the result of the downlink data frame includes: an FC domain, a Duration field, a Sequence Control domain, a QoS Control domain, an HT Control domain, a Frame Body domain, and an FCS domain; and the FCS domain is encapsulated with downlink data.
  • Receiver address information of the frame, and the downlink identifier is encapsulated in the FC domain.
  • the first obtaining module 81 is specifically configured to parse the FC domain, the Duration domain, the Sequence Control domain, the QoS Control domain, the HT Control domain, the Frame Body domain, and the FCS domain respectively, and obtain the receiver address of the downlink data frame from the FCS domain.
  • Information obtaining the downlink identity from the FC domain.
  • the method includes: an FC domain, an address domain, a Duration domain, a Sequence Control domain, a QoS Control domain, an HT Control domain, a Frame Body domain, and an FCS domain; There is receiver address information of the downlink data frame, and the FC domain is encapsulated with a downlink identifier.
  • the first obtaining module 81 is specifically configured to parse the Sequence Control domain, the QoS Control domain, the HT Control domain, the Frame Body domain, and the FCS domain, and obtain the receiver address information of the downlink data frame from the address domain, from the FC domain. Get the downlink ID.
  • the method includes: an FC domain, an address domain, an address field, a Duration field, a Sequence Control field, a QoS Control field, an HT Control field, a Frame Body field, and an FCS domain;
  • the receiver address information of the downlink data frame is encapsulated in a domain
  • the downlink identifier is encapsulated in the FC domain
  • the first obtaining module 81 obtains the receiver address of the downlink data frame from the address domain in addition to the FC domain, the address domain, the Duration domain, the Sequence Control domain, the QoS Control domain, the HT Control domain, the Frame Body domain, and the FCS domain.
  • the information is used to obtain the identifier of the basic service set of the receiver of the downlink data frame from the address two domain.
  • the first obtaining module 81 is further configured to obtain the service type identifier of the service corresponding to the downlink data frame from the FC domain.
  • the first obtaining module 81 is further configured to parse the service type identifier domain, and the slave service The type identifier field obtains the service type identifier of the service corresponding to the downlink data frame.
  • the first determining module 82 is specifically configured to compare the receiver address information of the downlink data frame acquired by the first acquiring module 81 with the address information of the STA8 itself, and if the comparison result is the same as the two address information, obtain the downlink data frame. Valid data, if the comparison result is that the two address information are different, the downlink data frame is discarded.
  • the function modules of the STA8 in this embodiment can be used to perform the process of the data frame receiving method shown in FIG. 3.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the STA of this embodiment cooperates with the AP provided by the embodiment of the present invention, so that the AP can perform optimized compression on the downlink data frame.
  • the STA receives the downlink data frame that includes at most two address domains, compared with the prior art. The number of address domains is reduced, the number of bits occupied by downlink data frames is reduced, and the overhead of downlink data frames is reduced.
  • FIG. 9 is a schematic structural diagram of a STA according to another embodiment of the present invention. As shown in FIG. 9, the STA9 of this embodiment includes: a second generation module 91 and a second transmission module 92.
  • the second generation module 91 is configured to generate an uplink data frame, where the uplink data frame includes one or two address domains, and the one or two address domains carry address information of the STA9.
  • the address information of the STA9 may be the MAC address or AID of the STA.
  • the second sending module 92 is connected to the second generating module 91, and configured to send the uplink data frame generated by the second generating module 91 to the AP, so that the AP determines, according to the address information of the STA9, whether to obtain valid data in the uplink data frame. .
  • the structure of the uplink data frame generated by the second generation module 91 is as shown in FIG. 5A, and mainly includes: an FC domain, an address three domain, a Duration domain, a Sequence Control domain, a QoS Control domain, an HT control domain, and a Frame Body domain. And FCS domain.
  • the address three domain encapsulates the address information of the STA that sends the uplink data frame
  • the FC domain encapsulates the uplink identifier.
  • the other structure of the uplink data frame generated by the second generation module 91 is as shown in FIG. 5B, and mainly includes: an FC domain, an address three domain, an address four domain, a Duration domain, a Sequence Control domain, a QoS Control domain, and an HT control. Domain, Frame Body domain, and FCS domain.
  • the address in the address three domain is encapsulated with the address information of the STA that sends the uplink data frame, the FC domain encapsulates the uplink identifier, and the address four domain carries the identifier of the basic service set where the STA9 is located.
  • the identifier of the basic service set where STA9 is located may be BSSID or ShortNetID.
  • the frame control domain is further encapsulated with a service type identifier that identifies a service corresponding to the uplink data frame.
  • the uplink data frame may further include: a service type identifier field, where the service type identifier field encapsulates a service type identifier of a service corresponding to the uplink data frame.
  • the function modules of the STA9 can be used to execute the process of the data frame sending method shown in FIG. 4, and the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the STA in this embodiment generates an uplink data frame that does not include the address information of the AP according to the characteristics of the AP in the uplink data frame, and reduces the number of address domains included in the uplink data frame, thereby reducing the occupation of the uplink data frame.
  • the number of bits reduces the overhead of the upstream data frame.
  • FIG. 10 is a schematic structural diagram of an AP according to another embodiment of the present invention.
  • the AP 10 of the example includes: a second receiving module 1000, a second obtaining module 1001, and a second determining module 1002.
  • the second receiving module 1000 is configured to receive an uplink data frame sent by the STA, where the uplink data frame includes one or two address domains.
  • the second obtaining module 1001 is connected to the second receiving module 1000, and is configured to obtain address information of the STA carried in one or two address domains in the uplink data frame received by the second receiving module 1000.
  • the address information of the STA may be a MAC address or an AID of the STA.
  • the second determining module 1002 is connected to the second obtaining module 1001, and is configured to determine, according to the address information of the STA acquired by the second acquiring module 1001, whether to obtain valid data in the uplink data frame.
  • the method includes: an FC domain, an address three domain, a Duration field, a Sequence Control domain, a QoS Control domain, an HT control domain, a Frame Body domain, and an FCS domain;
  • the address information of the STA that sends the uplink data frame is encapsulated, and the uplink identifier is encapsulated in the FC domain.
  • the second obtaining module 1001 is specifically configured to parse the FC domain, the address three domain, the Duration domain, the Sequence Control domain, the QoS Control domain, the HT control domain, the Frame Body domain, and the FCS domain respectively, and obtain the STA from the address three domain. Address information, obtaining an uplink identifier from the FC domain.
  • the method includes: an FC domain, an address three domain, an address four domain, a Duration field, a Sequence Control domain, a QoS Control domain, an HT control domain, a Frame Body domain, and an FCS domain;
  • the address field of the STA that sends the uplink data frame is encapsulated in the three domains
  • the uplink identifier is encapsulated in the FC domain
  • the identifier of the basic service set where the STA is located is encapsulated in the address four domain.
  • the second obtaining module 1001 is specifically configured to parse the FC domain, the address three domain, the address four domain, the Duration domain, the Sequence Control domain, the QoS Control domain, the HT control domain, the Frame Body domain, and the FCS domain, and the slave address three domains.
  • the address information of the STA is obtained, and the identifier of the basic service set of the STA is obtained from the address four domain, and the uplink identifier is obtained from the FC domain.
  • the second obtaining module 1001 is further configured to obtain the service type identifier of the service corresponding to the uplink data frame from the FC domain.
  • the second obtaining module 1001 is further configured to parse the service type identifier domain, and the slave service The type identifier field obtains the service type identifier of the service corresponding to the uplink data frame.
  • the function modules of the AP10 in this embodiment can be used to perform the process of the data frame receiving method shown in FIG. 6.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the AP cooperates with the STA provided by the embodiment of the present invention to enable the STA to perform optimal compression on the uplink data frame.
  • the AP in this embodiment receives the uplink data frame including only one or two address domains, and the existing AP. Compared with the technology, the number of address domains is reduced, the number of bits occupied by uplink data frames is reduced, and the overhead of uplink data frames is reduced.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本发明提供一种数据帧发送、接收方法、站点及接入点。其中，一种数据帧发送方法包括：AP生成下行数据帧，所述下行数据帧包括FCS域和最多两个地址域，所述FCS域或最多两个地址域中携带有下行数据帧的接收者地址信息；AP将下行数据帧发送给STA，以使STA根据下行数据帧的接收者的地址信息确定是否获取下行数据帧中的有效数据。本发明技术方案通过减少数据帧中包括的地址域的个数，减少了数据帧占用的比特数，降低了数据帧的开销。

Description

数据帧发送、 接收方法、 站点及接入点 技术领域 本发明涉及无线通信技术， 尤其涉及一种数据帧发送、 接收方法、 站点及 接入点。 背景技术 基于 IEEE 802.11ah标准的应用场景主要有以下几种： 传感器（Sensors )和 计量表（ meters )场景，传感器和计量表数据回传 ( Backhaul Sensor和 Meter data ) 场景和扩展范围无线局域网（Extended range Wi-Fi )场景。 其中， 第一种应用场 景主要包括智能电网、 环境 /农业监测、 工业工序传感器、 医疗、 家庭 /办公自动 化和家用传感器等具体应用。
经分析发现， 第一种应用场景的特点是其上行数据的源节点均为站点 ( Station, STA ), 目的节点均为接入点 （ Access Point, AP ); 同样， 其下行数 据的源节点均为 AP, 目的节点均为 STA。 在 IEEE 802.1 lah标准中， 各业务均 是使用传统的帧结构， 但是对于第一种应用场景中业务的上下行数据使用传统 的帧结构， 帧头的开销显然是很大的， 而且有些开销是不必要的， 这就造成了 资源浪费。 发明内容 本发明提供一种数据帧发送、 接收方法、 站点及接入点， 用以在传感器业 务中节约数据帧的开销。
本发明一方面提供一种数据帧发送方法， 包括：
接入点 AP生成下行数据帧， 所述下行数据帧包括帧校验序列 FCS域和最 多两个地址域， 所述 FCS域或所述最多两个地址域中携带有所述下行数据帧的 接收者地址信息；
所述 AP将所述下行数据帧发送给站点 STA, 以使所述 STA根据所述下行 数据帧的接收者地址信息确定是否获取所述下行数据帧中的有效数据。
本发明一方面提供一种接入点， 包括：
第一生成模块，用于生成下行数据帧，所述下行数据帧包括帧校验序列 FCS 域和最多两个地址域， 所述 FCS域或所述最多两个地址域中携带有所述下行数 据帧的接收者地址信息；
第一发送模块， 用于将所述下行数据帧发送给站点 STA, 以使所述 STA根 据所述下行数据帧的接收者地址信息确定是否获取所述下行数据帧中的有效数 据。
本发明一方面提供一种数据帧接收方法， 包括：
站点 STA接收接入点 AP发送的下行数据帧， 所述下行数据帧包括帧校验 序列 FCS域和最多两个地址域；
所述 STA获取所述 FCS域或最多两个地址域中携带的所述下行数据帧的接 收者地址信息；
所述 STA根据获取的所述下行数据帧的接收者地址信息， 确定是否获取所 述下行数据帧中的有效数据。
本发明一方面提供一种站点， 包括：
第一接收模块， 用于接收接入点 AP发送的下行数据帧， 所述下行数据帧包 括帧校验序列 FCS域和最多两个地址域；
第一获取模块， 用于获取所述 FCS域或最多两个地址域中携带的所述下行 数据帧的接收者地址信息；
第一确定模块， 用于根据获取的所述下行数据帧的接收者地址信息， 确定 是否获取所述下行数据帧中的有效数据。
本发明又一方面提供一种数据帧发送方法， 包括：
站点 STA生成上行数据帧， 所述上行数据帧包括一个或两个地址域， 所述 一个或两个地址域中携带有所述 STA的地址信息；
所述 STA将所述上行数据帧发送给接入点 AP,以使所述 AP根据所述 STA 的地址信息确定是否获取所述上行数据帧中的有效数据。
本发明又一方面提供一种站点， 包括：
第二生成模块， 用于生成上行数据帧， 所述上行数据帧包括一个或两个地 址域， 所述一个或两个地址域中携带有所述 STA的地址信息；
第二发送模块， 用于将所述上行数据帧发送给接入点 AP, 以使所述 AP根 据所述 STA的地址信息确定是否获取所述上行数据帧中的有效数据。
本发明又一方面提供一种数据帧接收方法， 包括：
接入点 AP接收站点 STA发送的上行数据帧， 所述上行数据帧包括一个或 两个地址 i或；
所述 AP获取所述一个或两个地址域中携带的所述 STA的地址信息； 所述 AP根据获取的所述 STA的地址信息， 确定是否获取所述上行数据帧 中的有效数据。
本发明又一方面提供一种接入点， 包括：
第二接收模块， 用于接收站点 STA发送的上行数据帧， 所述上行数据帧包 括一个或两个地址域；
第二获取模块， 用于获取所述一个或两个地址域中携带的所述 STA的地址 信息；
第二确定模块， 用于根据获取的所述 STA的地址信息， 确定是否获取所述 上行数据帧中的有效数据。
本发明一方面提供的数据帧发送、 接收方法、 站点及接入点， 接入点设备 生成包括 FCS域和最多两个地址域的下行数据帧， 在 FCS域或最多两个地址域 中封装接收者的地址信息， 然后发送给站点设备， 站点设备根据下行数据帧中 FCS 域或最多两个地址域中封装的接收者的地址信息确定是否有效接收下行数 据帧。 与现有技术相比， 本发明技术方案中的下行数据帧包含的地址域信息较 少， 减少了下行数据帧占用的比特数， 降低了下行数据帧的开销。
本发明又一方面提供的数据帧发送、 接收方法、 站点及接入点， 站点设备 生成包括一个或两个地址域的上行数据帧， 在一个或两个地址域中封装该站点 设备的地址信息， 然后发送给接入点设备， 接入点设备根据上行数据帧中一个 或两个地址域中封装的 STA的地址信息确定是否有效接收上行数据帧。 与现有 技术相比， 本发明技术方案中的上行数据帧包含的地址域信息较少， 减少了上 行数据帧占用的比特数， 降低了上行数据帧的开销。 附图说明
图 1为本发明一实施例提供的数据帧发送方法的流程图；
图 2A为一实施例提供的下行数据帧的一种结构示意图；
图 2B为本发明一实施例提供的下行数据帧的另一种结构示意图;
图 2C为本发明一实施例提供的下行数据帧的又一种结构示意图;
图 3为本发明一实施例提供的数据帧接收方法的流程图；
图 4为本发明另一实施例提供的数据帧发送方法的流程图； 图 5A为一实施例提供的上行数据帧的一种结构示意图；
图 5B为本发明一实施例提供的上行数据帧的另一种结构示意图;
图 6为本发明另一实施例提供的数据帧接收方法的流程图；
图 7为本发明一实施例提供的 AP的结构示意图；
图 8为本发明一实施例提供的 STA的结构示意图；
图 9为本发明另一实施例提供的 STA的结构示意图；
图 10为本发明另一实施例提供的 AP的结构示意图。 具体实施方式 为使本发明实施例的目的、 技术方案和优点更加清楚， 下面将结合本发明 实施例中的附图， 对本发明实施例中的技术方案进行清楚、 完整地描述， 显然， 所描述的实施例是本发明一部分实施例， 而不是全部的实施例。
图 1为本发明一实施例提供的数据帧发送方法的流程图。 如图 1所示， 本 实施例的方法包括：
步骤 101、 AP 生成下行数据帧， 所述下行数据帧包括帧校验序列 （Frame Check Sequence, FCS )域和最多两个地址域， 所述 FCS域或最多两个地址域中 携带有下行数据帧的接收者地址信息。
本实施例适用于下行数据帧的源节点均为 AP,目的节点均为 STA的各种业 务。 在本发明各实施例中， 以 IEEE 802.11ah标准中的传感器 （Sensor )应用场 景下的各种业务为例进行说明。
在本实施例中， AP根据下行数据帧的源节点均为 AP、 目的节点均为 STA 的特性， 对下行数据帧的结构进行优化压缩， 将下行数据帧优化为最多包括两 个地址域的帧结构， 以在保证通信可靠的情况下， 最大程度上地节省下行数据 帧的开销。
其中， 由于下行数据帧的源节点均为 AP, 目的节点均为 STA, 故对于 STA 来说只要确定接收到的数据帧是下行链路的， 即可默认该下行数据帧的源节点 即为 STA所接入的 AP。 其中， STA所接入的 AP是指 STA所在基本服务集中 的 AP。 STA确定接收到的下行数据帧的源节点为 AP相当于确定出该下行数据 帧的源地址为 AP的地址。对于 STA来说， 在其成功接入 AP后会存储 AP的地 址，故下行链路数据帧中可以不用携带 AP的地址。 而现有下行数据帧中帧控制 ( Frame Control, FC )域中 "To DS和 From DS"的组合可以表示数据帧的方向， 另外， 由于在传感器业务中， 下行数据帧不存在转发的情况， 也就不涉及 转发过程中发送节点和接收节点的地址信息。
在现有技术中， 下行数据帧会包括源节点、 目的节点以及转发过程中发送 节点、 接收节点的地址信息， 并通过四个地址域来携带这些地址信息。
基于上述，本实施例的 AP可以生成仅包括下行数据帧的接收者地址信息的 下行数据帧。 其中， 下行数据帧的接收者为接入该 AP的一个 STA。在本实施例 中， 下行数据帧的接收者地址信息可以被封装到下行数据帧的 FCS域中， 也可 以单独封装在下行数据帧中的一个地址域中。
其中， 如果下行数据帧的接收者地址信息被封装在 FCS域中， 则 AP会生 成没有地址域的下行数据帧。
在本实施例中， AP生成最多包含两个地址域的下行数据帧， 与现有技术相 比减少了地址域的个数， 减少了下行数据帧占用的比特数， 进而降低了下行数 据帧的开销。
步骤 102、 AP将下行数据帧发送给 STA, 以使 STA根据下行数据帧的接收 者地址信息确定是否获取下行数据帧中的有效数据。
当 AP生成仅包括下行数据帧的接收者地址信息的下行数据帧后，将下行数 据帧发送给 STA。
STA会根据下行数据帧中封装的接收者地址信息， 确定是否获取该下行数 据帧中的有效数据。
其中， STA可以先接收整个下行数据帧， 然后对下行数据帧进行解析， 获 取下行数据帧的 FCS域或最多两个地址域中封装的下行数据帧的接收者地址信 息， 然后根据获取的地址信息判断自己是否为该下行数据帧的接收者。 如果判 断结果为是， STA获取该下行数据帧中的有效数据； 如果判断结果为否， STA 丟弃该下行数据帧。
另外， STA也可以先接收部分下行数据帧， 例如接收包括 FCS域和最多两 个地址域等帧头部分， 然后对接收到的部分进行解析， 从中获取该下行数据帧 的接收者地址信息， 并根据获取的地址信息判断自己是否为该下行数据帧的接 收者。 如果判断结果为是， STA继续接收该下行数据帧并进一步解析获取该下 行数据中的有效数据； 如果判断结果为否， STA放弃对下行数据帧的接收并删 除已经接收到的部分。
在本实施例中， AP根据下行数据帧的特点， 生成仅包括下行数据帧的接收 者地址信息的下行数据帧， 使得下行数据帧最多只需包括两个地址域， 与现有 技术相比， 减少了地址域的个数， 减少了下行数据帧占用的比特数， 降低了下 行数据帧的开销。
其中， AP生成的下行数据帧的一种结构如图 2A所示， 该下行数据帧包括： FC域、 时长域（ Duration域） 、 序列控制域（ Sequence Control域） 、 服务质量 控制域（ QoS Control域）、 高吞吐率控制域（ HT Control域）、 帧主体域（ Frame Body域）和 FCS域。
在该结构中， FCS 域中封装有该下行数据帧的接收者地址信息。 其中， 下 行数据帧的接收者地址信息可以是该接收者的 MAC地址。 另外，如果在不存在 重叠基本服务集（ Overlap Basic Service Set, OBSS )的情况下，或者在存在 OBSS 但 STA和 AP能够识别出其中每个基本服务集 ( Basic Service Set, BSS ) 的情 况下， 下行数据帧的接收者地址信息还可以是该接收者的关联标识符 ( Association Identifier, AID ) 。
在该结构中 , FC域中封装下行链路标识，例如可以通过 "To DS和 From DS" 组合取值为 01来表示。
在该结构中， Duration域： Duration值用于网络分配向量（NAV )计算；
Sequence Control域： 用于重组帧片段以及过滤重复帧； QoS Control域： 用于标 识帧所属的通信类别或通信流以及许多其他与 QoS相关的帧信息； HT控制域： 用于实现相关高吞吐率控制； Frame Body域： 也称为数据字段， 负责在工作站 之间传递上层有效载荷。
在图 2A所示结构中， 没有地址域， 下行数据帧的接收者地址信息作为因子 封装到 FCS域里面， 即 AP生成了无地址域的数据帧结构， 与现有技术相比极 大的减少了数据帧的开销。而 STA可以通过检验 FCS域，获取接收者地址信息， 然后与自己的地址信息进行比较， 即可确认自己是否为该下行数据帧的接收者。
进一步， AP生成的下行数据帧的另一种结构如图 2B所示， 该下行数据帧 包括： FC i或、地址一或（ Address 1 )、 Duration i或、 Sequence Control i或、 QoS Control 域、 HT控制域、 Frame Body域和 FCS域。
在该结构中， 地址一域中封装有下行数据帧的接收者地址信息。 其中， 下 行数据帧的接收者地址信息可以是该接收者的 MAC地址。 另外，如果在不存在 OBSS的情况下， 或者在存在 OBSS但 STA和 AP能够识别出其中每个 BSS的 情况下， 下行数据帧的接收者地址信息还可以是该接收者的 AID。 在该结构中， 地址一域与现有技术中的接收地址 ( Receiver Address/Receiving Station Address, RA ) 。
在该结构中 , FC域中封装有下行链路标识， 例如可以通过 "To DS和 From DS" 组合取值为 01来表示。
在该结构中， FCS域与现有技术中下行数据帧的 FCS域相同。
在该结构中， Duration域、 Sequence Control域、 QoS Control域、 HT控制 域以及 Frame Body域的功能与图 2A所示结构中的相同， 不再详细赘述。
在图 2B所示结构中， 仅包括一个地址域， 下行数据帧的接收者地址信息作 为因子封装在地址一域里面， 即 AP生成了仅包括一个地址域的数据帧结构， 与 现有技术相比极大的减少了数据帧的开销。 而 STA可以通过检验地址一域， 获 取接收者地址信息， 然后与自己的地址信息进行比较， 即可确认自己是否为该 下行数据帧的接收者。
进一步， AP生成的下行数据帧的又一种结构如图 2C所示， 该下行数据帧 包括： FC i或、 地址一 i或、 地址二 i或（ Address2 ) 、 Duration ^, Sequence Control 域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域。
在该结构中， 地址一域中封装有下行数据帧的接收者地址信息。 其中， 下 行数据帧的接收者地址信息可以是该接收者的 MAC地址。 另外， 下行数据帧的 接收者地址信息还可以是该接收者的 AID。
地址二域中封装有下行数据帧的接收者所在基本服务集的标识。 该标识可 以是基本服务集标识符 （Basic Service Set Identifier, BSSID ) 或短网络标识 ( ShortNetID ) 。 其中， ShortNetID是对 BSSID的缩略指示。
其中， 在 OBSS存在的情况下， 不同 BSS中的 STA可能使用相同的 AID, 故在 OBSS存在且 AP和 STA无法通过其他方式识别出其中的 BSS的情况下， STA无法仅根据地址一域中封装的接收者的 AID识别出自己是否为接收者。 基 于此， 在该结构中， AP通过地址二域封装接收者所在基本服务集的标识， 使得 STA 可以同时根据地址二域中封装的基本服务集的标识和地址一域中封装的接 收者的 AID识别出自己是否为接收者。
在该结构中， FC域中封装有下行链路标识， 例如可以通过 "To DS和 From DS" 组合取值为 01来表示。 在该结构中， FCS域与现有技术中下行数据帧的 FCS域相同。
在该结构中， Duration域、 Sequence Control域、 QoS Control域、 HT控制 域以及 Frame Body域的工作与 2A所示结构中的相同， 在此不再赘述。
在图 2C所示结构中， 仅包括两个地址域， 下行数据帧的接收者地址信息作 为因子封装在地址一域里面， 而接收者所在基本服务集的标识封装在地址二域 里面， 即 AP生成了仅包括两个地址域的数据帧结构， 与现有技术相比极大的减 少了数据帧的开销。 而 STA可以通过检验地址一域或者同时检测地址一域和地 址二域， 获取接收者地址信息或者接收者地址信息和所在基本服务集的标识， 然后仅根据地址信息或者同时根据地址信息和所在基本服务集的标识确认自己 是否为该下行数据帧的接收者。
其中， AP是针对 IEEE 802.1 lah的 Sensor业务的帧结构进行优化的，故 AP 需要获知 STA支持的业务类型，即需要获知下行数据帧的业务类型。其中， STA 可以在与 AP关联过程中， 将所支持的业务类型提供给 AP。基于此， AP还可以 在下行数据帧中携带其对应业务的业务类型。
优选的， AP可以通过 FC域来封装该下行数据帧对应业务的业务类型标识。 例如， AP可以通过 FC域中的 "类型 （type )和子类型 （subtype ) " 的组合的 某组取值作为业务类型标识， 来表示业务类型。
优选的， AP还可以通过在下行数据帧中扩展新的域来携带下行数据帧对应 业务的业务类型标识。例如， AP可以在下行数据帧中扩展一个业务类型标识域， 将业务类型标识封装在该业务类型标识域中。 即在上述各结构中， 下行数据帧 还可以包括一业务类型标识域， 该业务类型标识域中封装有下行数据帧对应业 务的业务类型标识。 其中， 业务类型标识域所占的比特数非常少， 其远小于地 址域占用的比特数， 故虽然下行构造数据增加了业务类型标识域， 但从总体上 的开销。
图 3为本发明一实施例提供的数据帧接收方法的流程图。 如图 3所示， 本 实施例的方法包括：
步骤 301、 STA接收 AP发送的下行数据帧， 所述下行数据帧包括 FCS域 和最多两个地址域。
步骤 302、 STA获取 FCS域或最多两个地址域中携带的下行数据帧的接收 者地址信息。 本实施例适用于接收源节点均为 AP,目的节点均为 STA的各种业务的下行 数据帧， 例如无线局域网的标准中传感器应用场景下的各种业务的下行数据帧。
本实施例的 STA与 AP相配合， 接收经过 AP优化压缩的下行数据帧或部 分下行数据帧（主要是指下行数据帧的帧头部分）。 经过 AP优化压缩后的下行 数据帧包括 FCS域和最多两个地址域。 其中， 所述最多两个地址域包括不包括 地址域、 包括一个地址域和包括两个地址域三种情况。 其中， 在下行数据帧包 括地址域时 , AP可以将下行数据帧的接收者地址信息封装在其中一个地址域中 , 也可以将下行数据帧的接收者地址信息作为因子封装在 FCS域中； 在下行数据 帧不包括地址域时， AP将下行数据帧的接收者地址信息作为因子封装在 FCS域 中。 基于此， STA对接收到的下行数据帧或部分下行数据帧进行解析， 获取下 行数据帧包括的 FCS域和最多两个地址域， 然后从 FCS域或最多两个地址域中 获取下行数据帧的接收者地址信息。
步骤 303、 STA根据获取的下行数据帧的接收者地址信息，确定是否获取所 述下行数据帧中的有效数据。
在本实施例中， STA根据获取的下行数据帧的接收者地址信息， 确定是否 获取下行数据帧中的有效数据的过程主要是将下行数据帧的接收者地址信息和 本身的地址信息进行比较的过程， 但不限于此。 例如， 在 OBSS存在且 STA无 法通过其他方式识别出各 BSS的情况下， STA还需要根据从下行数据帧中获取 的下行数据帧的接收者所在的基本服务集的标识和本身所在基本服务集的标识 进行比较， 确定是否属于同一基本服务集。
其中， 本实施例所使用的地址信息可以是 MAC地址， 也可以是 AID。
其中， STA获取下行数据帧中的有效数据的过程与 STA接收数据帧的方式 有关。 如果在有数据帧到达时， STA会将整个数据帧接收下来， 然后再进行解 析处理， 则 STA在确定出自己是该数据帧的接收者后， 继续对接收到的数据帧 进行解析， 获取其中的有效数据。 如果在有数据帧到达时， STA仅接收该数据 帧的部分而不是全部， 并对接收到的部分数据帧进行解析并判断自己是否为该 数据帧的接收者， 则 STA在确定出自己是该数据帧的接收者后， 继续接收完该 数据帧， 然后再对整个数据帧进行解析， 获取其中的有效数据。
在本实施例中， STA与 AP相配合， 使得 AP可以对下行数据帧进行优化压 缩， 本实施例中的下行数据帧最多包括两个地址域， 与现有技术相比， 减少了 地址域的个数， 减少了下行数据帧占用的比特数， 降低了下行数据帧的开销。 其中， 根据下行数据帧的具体实现结构， STA获取下行数据帧的接收者地 址信息以及根据获取的下行数据帧的接收者地址信息， 确定是否获取下行数据 帧中的有效数据的操作有所不同， 下面结合下行数据帧的具体实现结构进行说 明。
如果下行数据帧如图 2A所示，即包括 FC域、 Duration域、 Sequence Control 域、 QoS Control域、 HT控制域、 Frame Body域， FCS域中封装有下行数据帧 的接收者地址信息， 而 FC域中封装下行链路标识， 则 STA会对下行数据帧包 括的 FC i或、 Duration i或、 Sequence Control i或、 QoS Control i或、 HT控制 i或、 Frame Body域和 FCS域分别进行解析， 从 FCS域中获取下行数据帧的接收者地址信 息， 从 FC域中获取下行链路标识。 然后， STA基于下行链路标识， 识别出下行 数据帧的源节点为 AP, 即默认 AP的地址为该下行数据帧的源地址。 STA根据 下行数据帧的接收者地址信息确定自己是否为接收者的过程包括： 如果接收者 地址信息为接收者的 MAC地址， 或者接收者地址信息为 AID, 且不存在 OBSS 情况， 或者接收者地址信息为 AID, 虽存在 OBSS但 AP和 STA可以通过其他 方式识别出 OBSS中各个 BSS, 则 STA直接将获取的接收者地址信息与自己的 地址信息 (例如 MAC地址或 AID )进行比较； 如果比较结果为两个地址信息相 同， 则解析获取该下行数据帧中的有效数据； 如果比较结果为两个地址信息不 相同， 则丟弃下行数据帧。
如果下行数据帧如图 2B所示，即包括 FC域、地址一域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域， 其中， 地址 一域中封装有下行数据帧的接收者地址信息， FC域中封装有下行链路标识， 则 STA会对下行数据帧包括的 FC域、 地址一域、 Duration域、 Sequence Control 域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域分别进行解析， 从地 址一域中获取下行数据帧的接收者地址信息， 从 FC域中获取下行链路标识。 然 后， STA基于下行链路标识， 识别出下行数据帧的源节点为 AP, 即默认 AP的 地址为该下行数据帧的源地址。 STA根据下行数据帧的接收者地址信息确定自 己是否为接收者的过程包括： 如果接收者地址信息为接收者的 MAC地址， 或者 接收者地址信息为 AID, 且不存在 OBSS情况， 或者接收者地址信息为 AID, 虽存在 OBSS但 AP和 STA可以通过其他方式识别出 OBSS中各个 BSS,则 STA 直接将获取的接收者地址信息与自己的地址信息 (例如 MAC地址或 AID )进行 比较； 如果比较结果为两个地址信息相同， 则解析获取该下行数据帧中的有效 数据； 如果比较结果为两个地址信息不相同， 则丟弃下行数据帧。
如果下行数据帧如图 2C所示，即包括： FC域、地址一域、地址二域、 Duration 域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域， 其中， 地址一域中封装有下行数据帧的接收者地址信息， 地址二域中封装有下 行数据帧的接收者所在基本服务集的标识， FC域中封装有下行链路标识，则 STA 会对下行数据帧包括的 FC域、地址一域、地址二域、 Duration域、 Sequence Control 域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域分别进行解析， 从地 址一域中获取下行数据帧的接收者地址信息， 从地址二域中获取接收者所在基 本服务集的标识，从 FC域中获取下行链路标识。然后， STA基于下行链路标识， 识别出下行数据帧的源节点为 AP,即默认 AP的地址为该下行数据帧的源地址。 STA根据下行数据帧的接收者地址信息确定自己是否为接收者的过程包括： 如 果接收者地址信息为接收者的 MAC地址， 或者接收者地址信息为 AID,且不存 在 OBSS情况， 或者接收者地址信息为 AID, 虽存在 OBSS但 AP和 STA可以 通过其他方式识别出 OBSS中各个 BSS, 则 STA直接将获取的接收者地址信息 与自己的地址信息 (例如 MAC地址或 AID )进行比较； 如果比较结果为两个地 址信息相同， 则解析获取该下行数据帧中的有效数据； 如果比较结果为两个地 址信息不相同， 则丟弃下行数据帧。 如果接收者地址信息为 AID, 存在 OBSS 且 AP和 STA无法通过其他方式识别出 OBSS中各个 BSS, 则 STA分别将接收 者所在基本服务集的标识和接收者的 AID与自己所在基本服务集的标识和自己 的 AID进行比较，如果比较结果为接收者所在基本服务集的标识与 STA所在基 本服务集的标识相同， 且接收者的 AID与 STA自己的 AID也相同， 则解析获 取下行数据帧中的有效数据， 反之， 丟弃下行数据帧。 型标识， 则在上述过程中， STA在对 FC域进行解析时， 还包括从 FC域中获取 下行数据帧对应业务的业务类型标识。 如果下行数据帧还包括业务类型标识域， 且所述业务类型标识域中封装有下行数据帧对应业务的业务类型标识， 则在上 述过程中， STA在对下行数据帧进行解析时， 还包括对下行数据帧中的业务类 型标识域进行解析， 从业务类型标识域中获取下行数据帧对应业务的业务类型 标识。 这样 STA还可以判断获取的业务类型标识与自己支持的业务类型的标识 是否一致， 以进一步判断自己是否该下行数据帧的接收者。
在此说明， 上述各实施例中， 在有效接收下行数据帧的过程中继续对下行 数据帧进行处理主要是指进一步解析下行数据帧， 获取其中的有效数据 （即
Frame Body域中的内容） 的过程。
图 4为本发明另一实施例提供的数据帧发送方法的流程图。 如图 4所示， 本实施例的方法包括：
步骤 401、 STA生成上行数据帧， 所述上行数据帧包括一个或两个地址域， 所述一个或两个地址域中携带有所述 STA的地址信息。
本实施例适用于上行数据帧的源节点均为 STA,目的节点均为 AP的各种业 务， 例如在无线局域网的标准中传感器应用场景下的各种业务。
在本实施例中， 上行数据帧的目的节点均为 AP, 对 AP来说如果有效接收 某一上行数据帧就可以确定该上行数据帧的目的节点一定是 AP, 故上行数据帧 中可以不用携带目的节点的地址信息。 基于此， STA根据上行数据帧的源节点 均为 STA、 目的节点均为 AP的特性， 对上行数据帧的结构进行优化压缩， 将上 行数据帧优化为包括一个或两个地址域的结构， 以在保证通信可靠性的情况下， 最大程度的节省上行数据帧的开销。
在一个 BSS中， 对 AP来说， 只要确定接收到的数据帧是上行链路的， 即 可默认该上行数据帧的目的节点 AP本身。 而 STA可以通过上行数据帧中 FC 域中 "To DS和 From DS" 的组合可以表示数据帧的方向， 即可以表明数据帧是 上行链路的还是下行链路的。
另外， 由于在传感器业务中， 上行数据帧不存在转发的情况， 也就不涉及 转发过程中发送节点和接收节点的地址信息。
在现有技术中， 上行数据帧会包括源节点、 目的节点以及转发过程中发送 节点、 接收节点的地址信息， 并通过四个地址域来携带这些地址信息。
基于上述， 本实施例的 STA可以生成仅包括上行数据帧的发送者 （即该 STA ) 的地址信息的上行数据帧。 其中， 上行数据帧的接收者为该 STA接入的 AP。 在本实施例中， STA可以将其地址信息封装在上行数据帧中的一个地址域 中。
如果上行数据帧仅包括一个地址域， 则 STA将其地址信息封装在该地址域 中； 如果上行数据帧包括两个地址域， 则 STA将其地址信息封装在其中一个地 址域中， 而将 STA所在基本服务集的标识封装在另一个地址域中。
步骤 402、 STA将上行数据帧发送给 AP, 以使 AP根据上行数据帧中 STA 的地址信息确定是否获取上行数据帧中的有效数据。 在形成上行数据帧后， STA将该上行数据帧发送给 AP。 AP接收到上行数 据帧后， 会根据上行数据帧的一个或两个地址域中封装的 STA的地址信息确定 自己是否该上行数据帧的接收者， 如果确定自己是该上行数据帧的接收者， 则 会解析获取上行数据帧中的有效数据。 对 AP来说， 根据 STA的地址信息确定 是否为上行数据帧的接收者或是否获取上行数据中的有效数据的过程主要是指 根据 STA的地址信息确定该 STA是否是接入该 AP的 STA,如果确定结果为是， 则进一步解析获取该 STA发送的上行数据帧中的有效数据。
其中， AP可以先接收整个上行数据帧， 然后对上行数据帧进行解析， 获取 上行数据帧的一个地址域中封装的 STA的地址信息， 然后根据获取的地址信息 判断该上行数据帧是否是由自己所关联的 STA发送的， 即判断自己是否为该上 行数据帧的接收者。如果判断结果为是， 则 AP解析获取接收到的上行数据帧中 的有效数据； 如果判断结果为否， AP丟弃该上行数据帧。
另外， AP也可以先接收部分上行数据帧， 例如仅接收包括一个或两个地址 域等帧头部分， 然后对接收到的部分进行解析， 从中获取发送该上行数据帧的 STA的地址信息， 并根据获取的地址信息判断发送该上行数据帧的 STA是否是 自己所关联的 STA, 即判断自己是否为该上行数据帧的接收者。 如果判断结果 为是， 则 AP继续接收完该上行数据帧， 然后进一步解析获取上行数据帧中的有 效数据； 如果判断结果为否， AP放弃对上行数据帧的接收并丟弃已经接收到的 部分。
在本实施例中， STA根据上行数据帧的目的节点均为 AP的特性，生成不包 括 AP的地址信息的上行数据帧， 减少了上行数据帧包括的地址域个数， 减少了 上行数据帧占用的比特数， 降低了上行数据帧的开销。
其中， STA生成的上行数据帧的一种结构如图 5A所示，该上行数据帧包括：
FC域、 地址三域 ( address3 ) 、 Duration域、 Sequence Control域、 QoS Control 域、 HT控制域、 Frame Body域和 FCS域。
在该结构中， 地址三域中封装有发送该上行数据帧的 STA的地址信息。 其 中， STA的地址信息可以是 STA的 MAC地址。 另外， 如果不存在 OBSS的情 况下，或者在存在 OBSS但 STA和 AP能够识别出其中每个 BSS的情况下， STA 的地址信息还可以是 STA的 AID。
在该结构中， FC域中封装上行链路标识，例如可以通过" To DS和 From DS" 组合取值为 10来表示。 在该结构中， Duration域： Duration值用于网络分配向量（NAV )计算； Sequence Control域： 用于重组帧片段以及过滤重复帧； QoS Control域： 用于标 识帧所属的通信类别或通信流以及许多其他与 QoS相关的帧信息； HT控制域： 用于实现相关高吞吐率控制； Frame Body域： 也称为数据字段， 负责在工作站 之间传递上层有效载荷； FCS域： 即循环冗余校验码， 用于检测帧的完整性。
在图 5A所示结构中，上行数据帧仅包括一个地址域， STA的地址信息作为 因子封装在该地址域中， 与现有技术相比极大地减少了数据帧的开销。 而 AP通 过检验该地址域， 获取 STA的地址信息， 然后判断该 STA是否是自己关联的 STA, 即可确定自己是否是该上行数据帧的接收者。
进一步， STA生成的上行数据帧的另一种结构如图 5B所示， 该上行数据帧 包括： FC i或、 地址三 i或、 地址四 i或 (Address4)、 Duration i或、 Sequence Control 域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域。
在该结构中，地址三域中封装有发送上行数据帧的 STA的地址信息。其中， STA的地址信息可以是该 STA的 MAC地址。 另夕卜， STA的地址信息还可以是 该 STA的 AID。
地址四域中封装有 STA所在基本服务集的标识。 该标识可以是 BSSID或 ShortNetID。
其中， 在 OBSS存在的情况下， 不同 BSS中的 STA可能使用相同的 AID, 故在 OBSS存在且 AP和 STA无法通过其他方式识别出其中的 BSS的情况下， AP无法仅根据地址三域中封装的 STA的 AID识别出自己是否为接收者。 基于 此， 在该结构中， STA通过地址四域封装 STA所在基本服务集的标识， 使得 AP可以同时根据地址四域中封装的基本服务集的标识和地址三域中封装的 STA 的 AID识别出自己是否为接收者。
在该结构中 , FC域中封装有上行链路标识， 例如可以通过 "To DS和 From DS" 组合取值为 10来表示。
在该结构中， Duration域、 Sequence Control域、 QoS Control域、 HT控制 域、 Frame Body域以及 FCS域与现有技术相类似， 在此不再赘述。
在图 5B所示结构中， 上行数据帧包括两个地址域， STA的地址信息封装在 地址三域中， STA所在基本服务集的标识封装在地址四域中， 与现有技术相比 地址域的个数仍有所减少，极大地降低了上行数据帧的开销。 而 AP可以通过检 验地址三域或者同时检测地址三域和地址四域， 获取 STA的地址信息或者 STA 的地址信息和所在基本服务集的标识， 然后仅根据地址信息或者同时根据地址 信息和所在基本服务集的标识确认自己是否为该上行数据帧的接收者。
其中， STA是针对 IEEE 802.1 lah的 Sensor业务的帧结构进行优化的， 故 STA需要获知其所支持的业务类型， 即需要获知上行数据帧的业务类型。 其中， STA可以在与 AP关联过程中， 将所支持的业务类型提供给 AP。 或者， STA可 以在上行数据帧中携带所支持的业务类型。
优选的， STA可以通过 FC域来封装该上行数据帧对应业务的业务类型标 识。 例如， STA可以通过 FC域中的 "类型 （type )和子类型 （subtype ) " 的组 合的某组取值作为业务类型标识， 来表示业务类型。
优选的， STA还可以通过在上行数据帧中扩展新的域来携带上行数据帧对 应业务的业务类型标识。 例如， STA可以在上行数据帧中扩展一个业务类型标 识域， 将业务类型标识封装在该业务类型标识域中。 即在上述各结构中， 上行 数据帧还可以包括一业务类型标识域， 该业务类型标识域中封装有上行数据帧 对应业务的业务类型标识。 其中， 业务类型标识域所占的比特数非常少， 其远 小于地址域占用的比特数， 故虽然上行构造数据增加了业务类型标识域， 但从 数据帧的开销。
图 6为本发明另一实施例提供的数据帧接收方法的流程图。 如图 6所示， 本实施例的方法包括：
步骤 601、 AP接收 STA发送的上行数据帧， 所述上行数据帧包括一个或两 个地址 i或。
步骤 602, AP获取一个或两个地址域中携带的 STA的地址信息。
本实施例用于接收源节点均为 STA,目的节点均为 AP的各种业务的上行数 据帧， 例如 IEEE 802.11ah标准中传感器应用场景下的各种业务的上行数据帧。
本实施例的 AP与 STA相配合， 接收经 STA优化压缩的上行数据帧或部分 上行数据帧 （主要是指上行数据帧的帧头部分） 。 经过 STA优化压缩后的上行 数据帧包括一个地址域或两个地址域。 其中， 在上行数据帧包括一个地址域时， STA将其地址信息封装在该地址域中； 在上行数据帧包括两个地址域时， STA 将其地址信息封装在其中一个地址域中。 基于此， AP对接收到的上行数据帧或 部分上行数据帧进行解析，获取上行数据帧中地址域中封装的 STA的地址信息。
步骤 603、 AP根据获取的 STA的地址信息， 确定是否获取上行数据帧中的 有效数据。
在本实施例中， AP根据获取的 STA的地址信息，确定是否获取该上行数据 帧中的有效数据的过程主要是 AP将上行数据帧的发送者， 即 STA的地址信息 和本地存储的所有关联 STA的地址信息进行比较， 判断自己是否为该上行数据 帧的接收者的过程， 但不限于此。 例如， 例如， 在 OBSS存在且 STA和 AP无 法通过其他方式识别出各 BSS的情况下， AP还需要根据从上行数据帧中获取的 STA所在的基本服务集的标识和本身所在基本服务集的标识进行比较， 确定是 否属于同一基本服务集。
其中， 本实施例所使用的地址信息可以是 MAC地址， 也可以是 AID。
其中， AP获取上行数据帧中的有效数据的过程与 AP接收数据帧的方式有 关。 如果在有数据帧到达时， AP先将整个数据帧接收下来， 然后再进行解析处 理，则 AP在确定出自己是该数据帧的接收者后，进一步对上行数据帧进行解析， 获取其中的有效数据。 如果在有数据帧到达时， AP仅接收该数据帧的部分而不 是全部， 并对接收到的部分数据帧进行解析并判断自己是否为该数据帧的接收 者， 则 AP在确定出自己是该数据帧的接收者后， 继续接收完该上行数据帧， 然 后再对对整个数据帧进行解析， 获取其中的有效数据。
在本实施例中， AP与 STA相配合， 使得 STA可以对上行数据帧进行优化 压缩， 本实施例中的上行数据帧仅包括一个或两个地址域， 与现有技术相比， 减少了地址域的个数， 减少了上行数据帧占用的比特数， 降低了上行数据帧的 开销。
其中，根据上行数据帧的具体实现结构， AP获取上行数据帧中 STA的地址 信息以及根据获取的 STA的地址信息， 确定是否获取上行数据帧中的有效数据 如果上行数据帧如图 5A所示， 即包括 FC域、 地址三域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域（帧主体域） 和 FCS域， 其中， 地址三域中封装有发送上行数据帧的 STA的地址信息， FC 域中封装有上行链路标识， 则 AP会对上行数据帧包括的 FC域、 地址三域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域 和 FCS域分别进行解析， 从地址三域中获取 STA的地址信息， 从 FC域中获取 上行链路标识。 然后， AP基于上行链路标识， 识别出上行数据帧的目的节点为 AP, 即默认 AP的地址为该上行数据帧的目的地址。 AP根据 STA的地址信息 确定自己是否为接收者的过程包括：如果 STA的地址信息为 STA的 MAC地址， 或者 STA的地址信息为 AID, 且不存在重叠基本服务集（OBSS )情况， 或者 STA的地址信息为 AID, 虽存在重叠基本服务集（OBSS )但^和 STA可以 通过其他方式识别出 OBSS中各个 BSS, 则 AP直接将获取的 STA的地址信息 与本地存储的所关联的 STA的地址信息 （例如 MAC地址或 AID )进行比较； 如果比较结果为两个地址信息相同， 则获取上行数据帧中的有效数据； 如果比 较结果为两个地址信息不相同， 则丟弃上行数据帧。
如果下行数据帧如图 5B所示，即包括： FC域、地址三域、地址四域、 Duration 域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域， 其中， 地址三域中封装有发送上行数据帧的 STA的地址信息， 地址四域中封装 有 STA所在基本服务集的标识， FC域中封装有上行链路标识， 则 AP会对上行 数据帧包括的 FC域、 地址三域、 地址四域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域分别进行解析， 从地址三 域中获取 STA的地址信息，从地址四域中获取 STA所在基本服务集的标识，从 FC域中获取上行链路标识。 然后， AP基于上行链路标识， 识别出上行数据帧 的目的节点为 AP, 即默认 AP的地址为该上行数据帧的目的地址。 AP根据 STA 的地址信息确定自己是否为接收者的过程包括： 如果 STA的地址信息为 MAC 地址， 或者 STA的地址信息为 AID, 且不存在重叠基本服务集（OBSS )情况， 或者 STA的地址信息为 AID, 虽存在重叠基本服务集（OBSS )但 AP和 STA 可以通过其他方式识别出 OBSS中各个 BSS, 则 AP直接将获取的 STA的地址 信息与本地存储的所关联的 STA的地址信息 (例如 MAC地址或 AID )进行比 较； 如果比较结果为两个地址信息相同， 则获取上行数据帧中的有效数据； 如 果比较结果为两个地址信息不相同， 则丟弃上行数据帧。 如果 STA的地址信息 为 AID, 存在重叠基本服务集（OBSS )且^和 STA无法通过其他方式识别 出 OBSS中各个 BSS, 则 AP分别将 STA所在基本服务集的标识和 STA的 AID 与 AP本身所在基本服务集的标识和本地存储的所关联的各 STA的 AID进行比 较， 如果比较结果为 AP本身所在基本服务集的标识与 STA所在基本服务集的 标识相同， 且 STA的 AID与 AP所关联的某个 STA的 AID也相同， 则获取上 行数据帧中的有效数据， 反之， 丟弃上行数据帧。
进一步，如果上行数据帧的 FC域中还封装有上行数据帧对应业务的业务类 型标识， 则在上述过程中， AP在对 FC域进行解析时， 还包括从 FC域中获取 上行数据帧对应业务的业务类型标识。 如果上行数据帧还包括业务类型标识域， 且所述业务类型标识域中封装有上行数据帧对应业务的业务类型标识， 则在上 述过程中， AP在对上行数据帧进行解析时， 还包括对上行数据帧中的业务类型 标识域进行解析， 从业务类型标识域中获取上行数据帧对应业务的业务类型标 识。 这样 AP还可以判断获取的业务类型标识与已经获知的 STA所支持的业务 类型的标识是否一致， 以进一步判断自己是否该上行数据帧的接收者。
在此说明， 在上述各实施例中， 所述上行数据帧或下行数据帧中的有效数 据主要是指上行数据帧或下行数据帧中 Frame Body域中的内容。
本发明实施例的上述方法应用在无线局域网系统中， 主要有 AP与 STA组 成。
图 7为本发明一实施例提供的 AP的结构示意图。如图 7所示， 本实施例的 AP7包括： 第一生成模块 71和第一发送模块 72。
其中， 第一生成模块 71 , 用于生成下行数据帧， 所述下行数据帧包括 FCS 域和最多两个地址域， 所述 FCS域或最多两个地址域中携带有下行数据帧的接 收者地址信息。
第一发送模块 72, 与第一生成模块 71连接， 用于将第一生成模块 71生成 的下行数据帧发送给 STA, 以使 STA根据下行数据帧的接收者地址信息确定是 否获取下行数据帧中的有效数据。
本实施例 AP7的各功能模块可用于执行图 1所示数据帧发送方法的流程， 其具体工作原理不再赘述， 详见方法实施例的描述。
其中， 本实施例第一生成模块 71生成的下行数据帧的一种结构如图 2A所 示，主要包括： FC i或、 Duration i或、 Sequence Control i或、 QoS Control i或、 HT Control 域、 Frame Body域和 FCS域。 其中， FCS域中封装有下行数据帧的接收者地址 信息， FC域中封装下行链路标识。
本实施例第一生成模块 71生成的下行数据帧的又一种结构如图 2B所示， 主要包括： FC i或、 地址一 i或、 Duration i或、 Sequence Control i或、 QoS Control 域、 HT Control域、 Frame Body域和 FCS域。 其中， 地址一域中封装有下行数 据帧的接收者地址信息， FC域中封装有下行链路标识。
本实施例第一生成模块 71生成的下行数据帧的又一种结构如图 2C所示， 主要包括： FC域、地址一域、地址二域、 Duration域、 Sequence Control域、 QoS Control域、 HT Control域、 Frame Body域和 FCS域。 其中， 地址一域中封装有 下行数据帧的接收者地址信息， FC域中封装有下行链路标识， 地址二域中封装 有下行数据帧的接收者所在基本服务集的标识。
其中， 第一生成模块 71生成的下行数据帧的结构还可以包括： FC域、 地 址二域、 Duration域、 Sequence Control域、 QoS Control域、 HT Control域、 Frame Body域和 FCS域。 其中， FCS域中封装有下行数据帧的接收者地址信息， FC 域中封装下行链路标识， 地址二域中封装有下行数据帧的接收者所在基本服务 集的标识。
其中， 下行数据帧的接收者所在基本服务集的标识可以为基本服务集标识
BSSID或短网络号 ShortNetID。
其中， 下行数据帧的接收者地址信息可以是接收者的 MAC地址或 AID。 进一步， 下行数据帧中还可以携带标识下行数据帧对应业务的业务类型标 识。 例如， 帧控制域中封装有标识下行数据帧对应业务的业务类型标识。 或者， 下行数据帧还可以包括业务类型标识域， 该业务类型标识域封装有下行数据帧 对应业务的业务类型标识。
本实施例的 AP, 根据下行数据帧的特点， 生成仅包括下行数据帧的接收者 地址信息的下行数据帧， 使得下行数据帧最多只需包括两个地址域， 与现有技 术相比， 减少了地址域的个数， 减少了下行数据帧占用的比特数， 降低了下行 数据帧的开销。
图 8为本发明一实施例提供的 STA的结构示意图。 如图 8所示， 本实施例 的 STA8包括： 第一接收模块 80、 第一获取模块 81和第一确定模块 82。
其中， 第一接收模块 80, 用于接收 AP发送的下行数据帧， 所述下行数据 帧包括 FCS域和最多两个地址域。
第一获取模块 81 , 与第一接收模块 80连接， 用于获取第一接收模块 80接 收到的下行数据帧中的 FCS域或最多两个地址域中携带的下行数据帧的接收者 地址信息。 其中， 下行数据帧的接收者地址信息可以是接收者的 MAC地址或 AID。
第一确定模块 82, 与第一获取模块 81连接， 用于根据第一获取模块 81获 取的下行数据帧的接收者地址信息， 确定是否获取下行数据帧中的有效数据。
其中， 如果下行数据帧的结果如图 2A所示， 即包括： FC域、 Duration域、 Sequence Control域、 QoS Control域、 HT Control域、 Frame Body域和 FCS域； 且 FCS域中封装有下行数据帧的接收者地址信息， FC域中封装下行链路标识。 则第一获取模块 81具体用于对 FC域、 Duration域、 Sequence Control域、 QoS Control域、 HT Control域、 Frame Body域和 FCS域分别进行解析， 从 FCS域 中获取下行数据帧的接收者地址信息， 从 FC域中获取下行链路标识。
如果下行数据帧的结果如图 2B所示， 即包括： FC域、 地址一域、 Duration 域、 Sequence Control域、 QoS Control域、 HT Control域、 Frame Body域和 FCS 域； 且地址一域中封装有下行数据帧的接收者地址信息， FC域中封装有下行链 路标识。 则第一获取模块 81具体用于对 Sequence Control域、 QoS Control域、 HT Control域、 Frame Body域和 FCS域分别进行解析 , 从地址一域中获取下行 数据帧的接收者地址信息， 从 FC域中获取下行链路标识。
如果下行数据帧的结果如图 2C所示， 即包括： FC域、 地址一域、 地址二 域、 Duration域、 Sequence Control域、 QoS Control域、 HT Control域、 Frame Body 域和 FCS域； 且地址一域中封装有下行数据帧的接收者地址信息， FC域中封装 有下行链路标识， 地址二域中封装有下行数据帧的接收者所在基本服务集的标 识。 则第一获取模块 81除了对 FC域、地址一域、 Duration域、 Sequence Control 域、 QoS Control域、 HT Control域、 Frame Body域和 FCS域， 从地址一域中获 取下行数据帧的接收者地址信息， 从 FC域中获取下行链路标识之外， 还用于对 地址二域进行解析， 从地址二域中获取下行数据帧的接收者所在基本服务集的 标识。
进一步，如果下行数据帧的 FC域中还封装有标识下行数据帧对应业务的业 务类型标识， 则第一获取模块 81还用于从 FC域中获取下行数据帧对应业务的 业务类型标识。
另外， 如果下行数据帧还包括业务类型标识域， 且业务类型标识域中封装 有下行数据帧对应业务的业务类型标识， 则第一获取模块 81还用于对业务类型 标识域进行解析， 从业务类型标识域中获取下行数据帧对应业务的业务类型标 识。
其中， 第一确定模块 82具体用于将第一获取模块 81获取的下行数据帧的 接收者地址信息和 STA8本身的地址信息进行比较，如果比较结果为两个地址信 息相同， 获取下行数据帧中的有效数据， 如果比较结果为两个地址信息不相同， 将下行数据帧丟弃。
本实施例 STA8的各功能模块可用于执行图 3所示数据帧接收方法的流程， 其具体工作原理不再赘述， 详见方法实施例的描述。 本实施例的 STA, 与本发明实施例提供的 AP相配合， 使得 AP可以对下行 数据帧进行优化压缩， 本实施例 STA接收最多包括两个地址域的下行数据帧， 与现有技术相比， 减少了地址域的个数， 减少了下行数据帧占用的比特数， 降 低了下行数据帧的开销。
图 9为本发明另一实施例提供的 STA的结构示意图。 如图 9所示， 本实施 例的 STA9包括： 第二生成模块 91和第二发送模块 92。
其中， 第二生成模块 91 , 用于生成上行数据帧， 所述上行数据帧包括一个 或两个地址域，所述一个或两个地址域中携带有 STA9的地址信息。其中， STA9 的地址信息可以是 STA的 MAC地址或 AID。
第二发送模块 92, 与第二生成模块 91连接， 用于将第二生成模块 91生成 的上行数据帧发送给 AP, 以使 AP根据 STA9的地址信息确定是否获取该上行 数据帧中的有效数据。
其中， 第二生成模块 91生成的上行数据帧的一种结构如图 5A所示， 主要 包括： FC域、 地址三域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域。 其中， 地址三域中封装有发送该上行数 据帧的 STA的地址信息， FC域中封装上行链路标识。
其中， 第二生成模块 91生成的上行数据帧的又一种结构如图 5B所示， 主 要包括： FC域、 地址三域、 地址四域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域。 其中， 地址三域中封装有发 送该上行数据帧的 STA的地址信息， FC域中封装上行链路标识，地址四域中携 带有 STA9所在基本服务集的标识。
其中， STA9所在基本服务集的标识可以为 BSSID或 ShortNetID。
进一步， 帧控制域中还封装有标识上行数据帧对应业务的业务类型标识。 或者， 上行数据帧还可以包括： 业务类型标识域， 所述业务类型标识域中 封装有上行数据帧对应业务的业务类型标识。
本实施例 STA9的各功能模块可用于执行图 4所示数据帧发送方法的流程， 其具体工作原理不再赘述， 详见方法实施例的描述。
本实施例的 STA,根据上行数据帧的目的节点均为 AP的特性，生成不包括 AP的地址信息的上行数据帧， 减少了上行数据帧包括的地址域个数， 减少了上 行数据帧占用的比特数， 降低了上行数据帧的开销。
图 10为本发明另一实施例提供的 AP的结构示意图。如图 10所示， 本实施 例的 AP10包括：第二接收模块 1000、第二获取模块 1001和第二确定模块 1002。 其中， 第二接收模块 1000, 用于接收 STA发送的上行数据帧， 所述上行数 据帧包括一个或两个地址域。
第二获取模块 1001 , 与第二接收模块 1000 连接， 用于获取第二接收模块 1000接收到的上行数据帧中一个或两个地址域中携带的 STA的地址信息。其中， STA的地址信息可以是 STA的 MAC地址或 AID。
第二确定模块 1002, 与第二获取模块 1001 连接， 用于根据第二获取模块 1001获取的 STA的地址信息， 确定是否获取上行数据帧中的有效数据。
进一步， 如果上行数据帧的结构如图 5A所示， 即包括： FC域、 地址三域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域 和 FCS域； 且地址三域中封装有发送该上行数据帧的 STA的地址信息， FC域 中封装上行链路标识。 则第二获取模块 1001 具体用于对 FC 域、 地址三域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域 和 FCS域分别进行解析， 从地址三域中获取 STA的地址信息， 从 FC域中获取 上行链路标识。
如果上行数据帧的结构如图 5B所示， 即包括： FC域、 地址三域、 地址四 域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body 域和 FCS域； 且地址三域中封装有发送该上行数据帧的 STA的地址信息， FC 域中封装上行链路标识， 地址四域中封装有 STA所在基本服务集的标识。 则第 二获取模块 1001具体用于对 FC域、地址三域、地址四域、 Duration域、 Sequence Control域、 QoS Control域、 HT控制域、 Frame Body域和 FCS域进行解析， 从 地址三域中获取 STA的地址信息，从地址四域中获取 STA所在基本服务集的标 识， 从 FC域中获取上行链路标识。
更进一步， 如果 FC域还封装有上行数据帧对应业务的业务类型标识， 则第 二获取模块 1001还用于从 FC域中获取上行数据帧对应业务的业务类型标识。
或者， 如果上行数据帧还包括业务类型标识域， 且业务类型标识域中封装 有上行数据帧对应业务的业务类型标识， 则第二获取模块 1001还用于对业务类 型标识域进行解析， 从业务类型标识域中获取上行数据帧对应业务的业务类型 标识。
本实施例 AP10的各功能模块可用于执行图 6所示数据帧接收方法的流程， 其具体工作原理不再赘述， 详见方法实施例的描述。 在实施例的 AP, 与本发明实施例提供的 STA相配合， 使得 STA可以对上 行数据帧进行优化压缩，本实施例的 AP接收仅包括一个或两个地址域的上行数 据帧， 与现有技术相比， 减少了地址域的个数， 减少了上行数据帧占用的比特 数， 降低了上行数据帧的开销。
本领域普通技术人员可以理解： 实现上述各方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成。 前述的程序可以存储于一计算机可读取 存储介质中。 该程序在执行时， 执行包括上述各方法实施例的步骤； 而前述的 存储介质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。

Claims

权利要求
1、 一种数据帧发送方法， 其特征在于， 包括：
接入点 AP生成下行数据帧， 所述下行数据帧包括帧校验序列 FCS域和最 多两个地址域， 所述 FCS域或所述最多两个地址域中携带有所述下行数据帧的 接收者地址信息；
所述 AP将所述下行数据帧发送给站点 STA, 以使所述 STA根据所述下行 数据帧的接收者地址信息确定是否获取所述下行数据帧中的有效数据。
2、 根据权利要求 1所述的数据帧发送方法， 其特征在于， 所述下行数据帧 包括帧控制域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率控制域、 帧 主体域和所述 FCS域，所述 FCS域中封装有所述下行数据帧的接收者地址信息。
3、 根据权利要求 1所述的数据帧发送方法， 其特征在于， 所述下行数据帧 包括帧控制域、 地址一域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率 控制域、 帧主体域和所述 FCS域； 所述地址一域中封装有所述下行数据帧的接 收者的地址信息。
4、 根据权利要求 2或 3所述的数据帧发送方法， 其特征在于， 所述下行数 据帧还包括： 地址二域； 所述地址二域中封装有所述下行数据帧的接收者所在 基本服务集的标识。
5、 一种数据帧接收方法， 其特征在于， 包括：
站点 STA接收接入点 AP发送的下行数据帧， 所述下行数据帧包括帧校验 序列 FCS域和最多两个地址域；
所述 STA获取所述 FCS域或最多两个地址域中携带的所述下行数据帧的接 收者地址信息；
所述 STA根据获取的所述下行数据帧的接收者地址信息， 确定是否获取所 述下行数据帧中的有效数据。
6、 根据权利要求 5所述的数据帧接收方法， 其特征在于， 所述下行数据帧 包括帧控制域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率控制域、 帧 主体域和所述 FCS域，所述 FCS域中封装有所述下行数据帧的接收者地址信息； 所述 STA获取所述 FCS域或最多两个地址域中携带的所述下行数据帧的接 收者地址信息包括：
所述 STA对所述帧控制域、 时长域、 序列控制域、 服务质量控制域、 高吞 吐率控制域、 帧主体域和所述 FCS域分别进行解析；
7、 根据权利要求 5所述的数据帧接收方法， 其特征在于， 所述下行数据帧 包括帧控制域、 地址一域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率 控制域、 帧主体域和所述 FCS域； 所述地址一域中封装有所述下行数据帧的接 收者的地址信息；
所述 STA获取所述 FCS域或最多两个地址域中携带的所述下行数据帧的接 收者地址信息包括：
所述 STA对所述帧控制域、 地址一域、 时长域、 序列控制域、 服务质量控 制域、 高吞吐率控制域、 帧主体域和所述 FCS域分别进行解析；
所述 STA从所地址一域中获取所述下行数据帧的接收者地址信息。
8、 根据权利要求 6或 7所述的数据帧接收方法， 其特征在于， 所述下行数 据帧还包括： 地址二域， 所述地址二域中封装有所述下行数据帧的接收者所在 基本服务集的标识；
所述方法还包括：
所述 STA对所述地址二域进行解析， 从所述地址二域中获取所述下行数据 帧的接收者所在基本服务集的标识。
9、根据权利要求 6或 7或 8所述的数据帧接收方法，其特征在于，所述 STA 根据获取的所述下行数据帧的接收者地址信息， 确定是否获取所述下行数据帧 中的有效数据包括：
所述 STA将获取的所述下行数据帧的接收者地址信息和所述 STA本身的地 址信息进行比较；
如果比较结果为两个地址信息相同， 所述 STA获取所述下行数据帧中的有 效数据；
如果比较结果为两个地址信息不相同， 所述 STA将所述下行数据帧丟弃。
10、 一种数据帧发送方法， 其特征在于， 包括：
站点 STA生成上行数据帧， 所述上行数据帧包括一个或两个地址域， 所述 一个或两个地址域中携带有所述 STA的地址信息；
所述 STA将所述上行数据帧发送给接入点 AP,以使所述 AP根据所述 STA 的地址信息确定是否获取所述上行数据帧中的有效数据。
11、 根据权利要求 10所述的数据帧发送方法， 其特征在于， 所述上行数据 帧包括帧控制域、 地址三域、 时长域、 序列控制域、 服务质量控制域、 高吞吐 率控制域、 帧主体域和帧校验序列 FCS域， 所述地址三域中封装有所述 STA的 地址信息。
12、 根据权利要求 11所述的数据帧发送方法， 其特征在于， 所述上行数据 帧还包括地址四域， 所述地址四域封装有所述 STA所在基本服务集的标识。
13、 一种数据帧接收方法， 其特征在于， 包括：
接入点 AP接收站点 STA发送的上行数据帧， 所述上行数据帧包括一个或 两个地址 i或；
所述 AP获取所述一个或两个地址域中携带的所述 STA的地址信息； 所述 AP根据获取的所述 STA的地址信息， 确定是否获取所述上行数据帧 中的有效数据。
14、 根据权利要求 13所述的数据帧接收方法， 其特征在于， 所述上行数据 帧包括帧控制域、 地址三域、 时长域、 序列控制域、 服务质量控制域、 高吞吐 率控制域、 帧主体域和帧校验序列 FCS域， 所述地址三域中封装有所述 STA的 地址信息；
所述 AP获取所述一个或两个地址域中携带的所述 STA的地址信息包括： 所述 AP对所述帧控制域、 地址三域、 时长域、 序列控制域、 服务质量控制 域、 高吞吐率控制域、 帧主体域和 FCS域分别进行解析；
所述 AP从所述地址三域中获取所述 STA的地址信息。
15、 根据权利要求 14所述的数据帧接收方法， 其特征在于， 所述上行数据 帧还包括地址四域， 所述地址四域封装有所述 STA所在基本服务集的标识； 所述 AP获取所述一个或两个地址域中携带的所述 STA的地址信息包括： 所述 AP对所述帧控制域、 地址三域、 地址四域、 时长域、 序列控制域、 服 务质量控制域、 高吞吐率控制域、 帧主体域和 FCS域分别进行解析；
所述 AP从所述地址三域中获取所述 STA的地址信息， 从所述地址四域中 获取所述 STA所在基本服务集的标识。
16、 一种接入点 AP, 其特征在于， 包括：
第一生成模块，用于生成下行数据帧，所述下行数据帧包括帧校验序列 FCS 域和最多两个地址域， 所述 FCS域或所述最多两个地址域中携带有所述下行数 据帧的接收者地址信息；
第一发送模块， 用于将所述下行数据帧发送给站点 STA, 以使所述 STA根 据所述下行数据帧的接收者地址信息确定是否获取所述下行数据帧中的有效数 据。
17、 根据权利要求 16所述的 AP, 其特征在于， 所述下行数据帧包括帧控 制域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率控制域、 帧主体域和 所述 FCS域， 所述 FCS域中封装有所述下行数据帧的接收者地址信息。
18、 根据权利要求 16所述的 AP, 其特征在于， 所述下行数据帧包括帧控 制域、 地址一域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率控制域、 帧主体域和所述 FCS域； 所述地址一域中封装有所述下行数据帧的接收者地址 信息。
19、 根据权利要求 17或 18所述的 AP, 其特征在于， 所述下行数据帧还包 括： 地址二域； 所述地址二域中封装有所述下行数据帧的接收者所在基本服务 集的标识。
20、 一种站点 STA, 其特征在于， 包括：
第一接收模块， 用于接收接入点 AP发送的下行数据帧， 所述下行数据帧包 括帧校验序列 FCS域和最多两个地址域；
第一获取模块， 用于获取所述 FCS域或最多两个地址域中携带的所述下行 数据帧的接收者地址信息；
第一确定模块， 用于根据获取的所述下行数据帧的接收者地址信息， 确定 是否获取所述下行数据帧中的有效数据。
21、 根据权利要求 20所述的 STA, 其特征在于， 所述下行数据帧包括帧控 制域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率控制域、 帧主体域和 所述 FCS域， 所述 FCS域中封装有所述下行数据帧的接收者地址信息；
所述第一获取模块具体用于对所述帧控制域、 时长域、 序列控制域、 服务 质量控制域、 高吞吐率控制域、 帧主体域和所述 FCS域分别进行解析， 从所述 FCS域中获取所述下行数据帧的接收者的地址信息。
22、 根据权利要求 20所述的 STA, 其特征在于， 所述下行数据帧包括帧控 制域、 地址一域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率控制域、 帧主体域和所述 FCS域； 所述地址一域中封装有所述下行数据帧的接收者地址 信息；
所述第一获取模块具体用于对所述帧控制域、 地址一域、 时长域、 序列控 制域、 服务质量控制域、 高吞吐率控制域、 帧主体域和所述 FCS域分别进行解 析， 从所地址一域中获取所述下行数据帧的接收者地址信息。
23、 根据权利要求 21或 22所述的 STA, 其特征在于， 所述下行数据帧还 包括： 地址二域， 所述地址二域中封装有所述下行数据帧的接收者所在基本服 务集的标识；
所述第一获取模块还用于对所述地址二域进行解析， 从所述地址二域中获 取所述下行数据帧的接收者所在基本服务集的标识。
24、 根据权利要求 20或 21或 22所述的 STA, 其特征在于， 所述第一确定 模块具体用于将获取的所述下行数据帧的接收者地址信息和所述 STA本身的地 址信息进行比较， 如果比较结果为两个地址信息相同， 获取所述下行数据帧中 的有效数据， 如果比较结果为两个地址信息不相同， 将所述下行数据帧丟弃。
25、 一种站点 STA, 其特征在于， 包括：
第二生成模块， 用于生成上行数据帧， 所述上行数据帧包括一个或两个地 址域， 所述一个或两个地址域中携带有所述 STA的地址信息；
第二发送模块， 用于将所述上行数据帧发送给接入点 AP, 以使所述 AP根 据所述 STA的地址信息确定是否获取所述上行数据帧中的有效数据。
26、 根据权利要求 25所述的 STA, 其特征在于， 所述上行数据帧包括帧控 制域、 地址三域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率控制域、 帧主体域和帧校验序列 FCS域， 所述地址三域中封装有所述 STA的地址信息。
27、 根据权利要求 26所述的 STA, 其特征在于， 所述上行数据帧还包括地 址四域， 所述地址四域封装有所述 STA所在基本服务集的标识。
28、 一种接入点 AP, 其特征在于， 包括：
第二接收模块， 用于接收站点 STA发送的上行数据帧， 所述上行数据帧包 括一个或两个地址域；
第二获取模块， 用于获取所述一个或两个地址域中携带的所述 STA的地址 信息；
第二确定模块， 用于根据获取的所述 STA的地址信息， 确定是否获取所述 上行数据帧中的有效数据。
29、 根据权利要求 28所述的 AP, 其特征在于， 所述上行数据帧包括帧控 制域、 地址三域、 时长域、 序列控制域、 服务质量控制域、 高吞吐率控制域、 帧主体域和帧校验序列 FCS域， 所述地址三域中封装有所述 STA的地址信息； 所述第二获取模块具体用于对所述帧控制域、 地址三域、 时长域、 序列控 制域、 服务质量控制域、 高吞吐率控制域、 帧主体域和 FCS域分别进行解析， 从所述地址三域中获取所述 STA的地址信息。
30、 根据权利要求 29所述的 AP, 其特征在于， 所述上行数据帧还包括地 址四域， 所述地址四域封装有所述 STA所在基本服务集的标识；
所述第二获取模块具体用于对所述帧控制域、 地址三域、 地址四域、 时长 域、 序列控制域、 服务质量控制域、 高吞吐率控制域、 帧主体域和 FCS域分别 进行解析， 从所述地址三域中获取所述 STA的地址信息， 从所述地址四域中获 取所述 STA所在基本服务集的标识。
PCT/CN2013/071816 2012-02-23 2013-02-25 数据帧发送、接收方法、站点及接入点 WO2013123905A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210042407.1A CN103297171B (zh) 2012-02-23 2012-02-23 数据帧发送、接收方法、站点及接入点
CN201210042407.1 2012-02-23

Publications (1)

Publication Number Publication Date
WO2013123905A1 true WO2013123905A1 (zh) 2013-08-29

Family

ID=49005022

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/071816 WO2013123905A1 (zh) 2012-02-23 2013-02-25 数据帧发送、接收方法、站点及接入点

Country Status (2)

Country Link
CN (1) CN103297171B (zh)
WO (1) WO2013123905A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103687041B (zh) * 2013-12-17 2016-09-21 中国人民解放军国防科学技术大学 一种无线自组织网络中避免发送冲突的可进化调度方法
US9955333B2 (en) * 2014-08-20 2018-04-24 Qualcomm, Incorporated Secure wireless wake-up companion
US10383053B2 (en) * 2015-05-06 2019-08-13 Qualcomm Incorporated Techniques for performing an intra-frame operation based at least in part on identifiers in a wireless local area network physical layer header
CA3001440A1 (en) * 2015-10-16 2017-04-20 Sony Corporation Communication device and communication method
CN108234093B (zh) * 2016-12-14 2021-02-12 华为技术有限公司 控制信息指示方法及网元
CN112203341B (zh) * 2020-09-01 2024-04-09 深圳市科思科技股份有限公司 数据识别方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1411302A (zh) * 2001-09-28 2003-04-16 株式会社东芝 基站设备和终端设备
CN1794687A (zh) * 2006-01-06 2006-06-28 中国人民解放军理工大学 分簇结构无线传感器网络数据链路层的自适应休眠方法
CN101656644A (zh) * 2008-08-18 2010-02-24 清华大学 接入点装置、移动终端、无线通信系统及其控制方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478382A (zh) * 2003-06-18 2009-07-08 日本电信电话株式会社 无线分组通信方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1411302A (zh) * 2001-09-28 2003-04-16 株式会社东芝 基站设备和终端设备
CN1794687A (zh) * 2006-01-06 2006-06-28 中国人民解放军理工大学 分簇结构无线传感器网络数据链路层的自适应休眠方法
CN101656644A (zh) * 2008-08-18 2010-02-24 清华大学 接入点装置、移动终端、无线通信系统及其控制方法

Also Published As

Publication number Publication date
CN103297171A (zh) 2013-09-11
CN103297171B (zh) 2016-10-05

Similar Documents

Publication Publication Date Title
TWI764893B (zh) 用於建立無線資源控制連接的方法和裝置
US10412652B2 (en) Apparatus and method for routing data packet to user equipment in LTE-WLAN aggregation system
JP4518183B2 (ja) 無線通信システム、無線通信装置、無線通信方法及びプログラム
JP5746425B2 (ja) メディアアクセス制御の制御交換のための装置および方法
CN109005562B (zh) 传输数据的方法、装置和系统
WO2017206186A1 (zh) 中继传输的方法和装置
US20130235790A1 (en) Systems and methods for establishing a connection setup through relays
WO2013123905A1 (zh) 数据帧发送、接收方法、站点及接入点
JP6698771B2 (ja) 効果的なアクセスポイント発見のためのシステムおよび方法
US20070014288A1 (en) Apparatus and method for point-to-point emulation in a broadband wireless communication system
CN110505714B (zh) 多链接通信方法、设备和终端
WO2010121416A1 (zh) 中继链路中处理数据的方法、中继节点和系统
WO2014117517A1 (zh) 多制式网络融合的方法、设备及系统
WO2013091510A1 (zh) 传输数据帧的方法和装置
WO2013120422A1 (zh) 通信方法、站点设备及接入点设备
CN102369752B (zh) 一种数据传输的方法、装置
CN114071510A (zh) 一种通信方法及装置
US20190132427A1 (en) Base station, method, and device for data transmission
WO2014186935A1 (zh) 数据传输方法、装置及系统
WO2010003275A1 (zh) 无线网络中处理协议数据单元的方法和装置
WO2014156967A1 (ja) 通信システム、中継装置及び通信方法
US8315192B2 (en) Method and system for configuring a media access control header to reduce a header overhead
WO2010088834A1 (zh) 基于Wi-Fi和WiMAX的双模通信方法、设备及系统
WO2022242749A1 (zh) 数据传输方法、通信装置、计算机可读存储介质和芯片
WO2012059049A1 (zh) 一种数据传输方法、设备及系统

Legal Events

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

Ref document number: 13752349

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13752349

Country of ref document: EP

Kind code of ref document: A1