WO2014131300A1 - 组播信息传输方法及设备 - Google Patents

组播信息传输方法及设备 Download PDF

Info

Publication number
WO2014131300A1
WO2014131300A1 PCT/CN2013/088706 CN2013088706W WO2014131300A1 WO 2014131300 A1 WO2014131300 A1 WO 2014131300A1 CN 2013088706 W CN2013088706 W CN 2013088706W WO 2014131300 A1 WO2014131300 A1 WO 2014131300A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
mid
information
sta
multicast group
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2013/088706
Other languages
English (en)
French (fr)
Inventor
杨浔
赵牧
姜艳平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to RU2015141698A priority Critical patent/RU2635888C2/ru
Priority to KR1020157026751A priority patent/KR20150120526A/ko
Priority to EP13876114.3A priority patent/EP2955942B1/en
Publication of WO2014131300A1 publication Critical patent/WO2014131300A1/zh
Priority to US14/836,682 priority patent/US20150365885A1/en
Anticipated expiration legal-status Critical
Priority to US15/698,563 priority patent/US20170374609A1/en
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0212Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0212Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0219Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower where the power saving management affects multiple terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/30Resource management for broadcast services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/11Allocation or use of connection identifiers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/40Connection management for selective distribution or broadcast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08User group management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. Transmission Power Control [TPC] or power classes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W74/00Wireless channel access
    • H04W74/002Transmission of channel access control information
    • H04W74/006Transmission of channel access control information in the downlink, i.e. towards the terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10Small scale networks; Flat hierarchical networks
    • H04W84/12WLAN [Wireless Local Area Networks]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08Access point devices
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to communication technologies, and in particular, to a multicast information transmission method and device. Background technique
  • STA sensor stations
  • these STAs can be placed on water meters, electricity meters, and gas meters, respectively.
  • These water, electricity, and gas meters can be subordinate to different or identical water, electricity, and gas retail companies.
  • Companies can send information to these water, electricity, and gas meters in the same or different cycles through wireless access points (Access Point, called AP), or update these water, electricity, and gas meters as needed.
  • AP wireless access Point
  • the above application scenarios show that in an 802.11ah scenario, each AP has the need to send multicast information of different periods and different contents to different STAs.
  • the STA initially works in the normal mode.
  • the STA receives each beacon frame (Beacon) that contains a Delivery Traffic Indication Map (DTIM).
  • DTIM Delivery Traffic Indication Map
  • DTIM Delivery Traffic Indication Map
  • FMS Flexible Multicast Service
  • the STA negotiates with the AP to determine the multicast period to be used.
  • the STA receives the multicast information according to the multicast period determined by the negotiation.
  • the AP uses the FMS ID of 8 bits in the beacon frame to identify the upcoming transmission.
  • the multicast information belongs to which multicast period.
  • the embodiment of the invention provides a method and a device for transmitting multicast information, which are used to alleviate the waste of resources of the STA.
  • a first aspect of the embodiments of the present invention provides a method for transmitting multicast information, including: an access point AP sends a multicast group association identifier MID to a station STA, where one multicast group has one or more MIDs, each of which The MID corresponds to a multicast group and a receiving period of STAs in the multicast group;
  • a transmit transmission indication mapping DTIM beacon frame to the STA, where the DTIM beacon frame includes the MID, and is used to indicate a multicast group that has multicast information sent to the STA;
  • the AP sends the multicast information of the multicast group, where the multicast information carries information about the MID or the associated MID, and the multicast information is received by the STA.
  • the method before the sending, by the AP, the MID of the multicast group to the STA, the method includes: receiving an information frame of the request MID sent by the STA, where sending the MID of the multicast group to the station STA includes: receiving The information frame of the requested MID is sent to the STA, and the MID of the multicast group where the STA is located is sent.
  • the information frame requesting the MID includes the MID request, and the AP sends the MID of the multicast group to the STA according to the MID request information unit before the AP sends the MID of the multicast group to the STA.
  • a second aspect of the embodiments of the present invention provides another method for transmitting multicast information, where the method includes: an AP sending a MID of a multicast group to a station STA, where each MID corresponds to a multicast group and the multicast group. The receiving period of the STA in the middle;
  • a DTIM beacon frame Transmitting, by the AP, a DTIM beacon frame to the STA, where a part of the virtual bitmap of the DTIM beacon frame includes MID indication information for one or more pages, and corresponding to the same multicast group in different pages Different MIDs, the different MIDs corresponding to the same receiving period of the STAs in the multicast group; the APs transmitting multicast information of the multicast group, where the multicast information carries the MID information or an association The MID information is received by the STA.
  • the method before the sending, by the AP, the MID of the multicast group to the station STA, the method includes: receiving an information frame of the request MID sent by the STA, and sending the MID of the multicast group to the STA of the station The method includes: sending, according to the received information frame of the request MID, the MID of the multicast group where the STA is located to the STA.
  • the information frame requesting the MID includes an MID request information unit; and before the AP sends the MID of the multicast group to the station STA, the AP generates the multicast to the STA according to the MID request information unit.
  • the MID of the group includes: receiving an information frame of the request MID sent by the STA, and sending the MID of the multicast group to the STA of the station The method includes: sending, according to the received information frame of the request MID, the MID of the multicast group where the STA is located to the STA.
  • the information frame requesting the MID includes an MID request information unit
  • an embodiment of the present invention further provides an embodiment of an access point that implements the foregoing method, where the access point includes:
  • a processor configured to generate a multicast group association identifier MID and send a transmission indication map DTIM beacon frame;
  • a transmitting circuit configured to send, by using an antenna, the multicast group association identifier MID, the transmission transmission indication mapping DTIM beacon frame, and multicast information of the multicast group;
  • One of the multicast groups has one or more MIDs, and each of the MIDs corresponds to a multicast group and a receiving period of STAs in the multicast group.
  • the DTIM beacon frame is used to indicate that there is multicast information to the STA.
  • the multicast group that is sent; the multicast information carries the MID or information associated with the MID, and the multicast information is received by the STA.
  • a method for receiving multicast group information includes: the station STA receives a multicast group association identifier MID sent by an access point AP, where one multicast group has one or more MIDs, and each The MID corresponds to a multicast group and a receiving period of the STA in the multicast group; the STA receives a transmit transmission indication mapping DTIM beacon frame sent by the AP, where the DTIM beacon frame includes the The MID is used to indicate the multicast group that has the multicast information sent to the STA; the STA receives the multicast information of the multicast group sent by the AP, where the multicast information carries the MID or Associate the information of the MID.
  • a method for receiving multicast group information comprising: receiving, by a station, a multicast group MID sent by an AP, where each of the MIDs corresponds to a multicast group and a receiving period of a STA in the multicast group;
  • a DTIM beacon frame sent by the AP where a part of the virtual bitmap of the DTIM beacon frame includes MID indication information for one or more pages, and corresponding to the same multicast in different pages Different MIDs of the group, where the different MIDs correspond to the same receiving period of the STAs in the multicast group;
  • the STA Receiving, by the STA, the multicast information of the multicast group sent by the AP, the multicast information carrying the MID information or the information associated with the MID, where the multicast information is used by the STA receive.
  • the access point includes:
  • a processor configured to generate a MID and a DTIM beacon frame of the multicast group, and a transmitting circuit, configured to send, by using an antenna, the multicast group association identifier MID, the transmission transmission indication map, a DTIM beacon frame, and a multicast group Multicast information; each of the MIDs corresponds to a multicast group and a receiving period of STAs in the multicast group; and a part of the virtual bitmap of the DTIM beacon frame includes MID indication information for one or more pages, Having different MIDs corresponding to the same multicast group in different pages, where the different MIDs correspond to the same receiving period of the STAs in the multicast group; the multicast information carries the MID information or the associated Information of the MID, the multicast information is received by the STA.
  • an embodiment of the present invention further has a STA, including:
  • the receiving circuit receives, by the antenna, the multicast group association identifier MID sent by the AP, the transmission transmission indication map DTIM, and the multicast information of the multicast group; wherein one multicast group has one or more MIDs, and each of the MIDs corresponds to one a multicast group and a receiving period of the STA in the multicast group, the DTIM beacon frame includes the MID, and is used to indicate a multicast group that has multicast information sent to the STA; The MID and DTIM cause the receiving circuit to receive multicast information of the multicast group.
  • the STA of another station includes: a receiving circuit, which receives, by using an antenna, a multicast group association identifier MID sent by the AP, and a transmission indication mapping DTIM and multicast information of the multicast group;
  • Each of the MIDs corresponds to a multicast group and a receiving period of STAs in the multicast group;
  • the partial virtual bitmap of the DTIM beacon frame includes MID indication information for one or more pages, on different pages. Having different MIDs corresponding to the same multicast group, the different MIDs corresponding to the same receiving period of the STAs in the multicast group, and a processor, configured to, according to the MID and the DTIM, the receiving circuit to receive the Multicast information of a multicast group.
  • the multicast information sending and receiving method and device provided by the embodiment of the present invention, by using a DTIM beacon frame to indicate a multicast group with multicast information, and the AP multicasting according to the multicast group with multicast information.
  • the size sequence of the medium receives the multicast information of the multicast group in the corresponding receiving interval, and solves the problem of all the multicast information after the STAs receive the beacon frame in the prior art, thereby alleviating the waste of resources of the STA. .
  • the multicast identity sending and receiving method and the device provided by the embodiment of the present invention use the AID as the multicast MID of the multicast group, and the AP sends the multicast MID of the multicast group where the STA is located to the STA, which solves the problem to a certain extent.
  • the number of multicast cycles supported by the FSM ID is limited, which causes the multicast application to be limited.
  • FIG. 1 is a flowchart of a method for sending multicast information according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for sending multicast information according to another embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for transmitting multicast information according to another embodiment of the present invention
  • FIG. 2 is a flowchart of a method for transmitting multicast information according to another embodiment of the present invention
  • Schematic diagram of the structure of the AID
  • FIG. 4 is a flowchart of a method for receiving multicast information according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a sequence of receiving multicast information according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of another sequence for receiving multicast information according to an embodiment of the present invention
  • FIG. 8 is a flowchart of a method for sending a multicast identifier according to an embodiment of the present invention.
  • FIG. 9 is a flowchart of a method for receiving a multicast identifier according to an embodiment of the present invention.
  • FIG. 10 is a schematic block diagram of an access point AP according to an embodiment of the present invention.
  • FIG. 11 is a schematic block diagram of an access point AP according to another embodiment of the present invention.
  • FIG. 12 is a schematic block diagram of a station STA according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a method for transmitting multicast information according to an embodiment of the present invention.
  • the execution subject of this embodiment is an AP, but is not limited thereto.
  • the method in this embodiment includes:
  • Step 101 Send a DTIM beacon frame to the STA, where the DTIM beacon frame is used to indicate a multicast group with multicast information.
  • Step 102 Send the multicast information of the multicast group with the multicast information sent in the preset sending interval, so that the STA receives the multicast information of the multicast group where the STA is located at the receiving interval corresponding to the multicast group where the STA is located.
  • the group with the multicast information transmission is sent in each preset sending interval.
  • the multicast information of the broadcast group the order of the multicast IDs may be in descending order, or from small to large.
  • the order of the multicast IDs to be sent by the AP is the same as the order of the multicast IDs that the STAs receive when they are received, either in descending order or in descending order.
  • each multicast group has a multicast ID, which is used to uniquely identify the multicast group.
  • These multicast IDs are associated identifiers AIDs used to identify multicast groups, and are called MIDs (Multicast AIDs).
  • the AP stores multicast information of each multicast group that has multicast information to be sent.
  • the AP first sends a beacon frame to the STA, where the type indication bit in the beacon frame indicates that the beacon frame is a DTIM beacon frame, the DTIM message.
  • the standard frame indicates on the one hand that the DTIM beacon frame will transmit multicast information, and on the other hand, indicates that there is a multicast group for multicast information transmission.
  • the AP sends the multicast information of the multicast groups in sequence according to the size of the MID of the multicast group that has the multicast information, so that the STA can correspond to the MID of the multicast group in which the multicast group belongs.
  • the multicast information of the multicast group in the receiving group is received in the receiving interval, and the multicast information of other multicast groups is not received, which solves the problem that all STAs need to receive the beacon frame after receiving the beacon frame in the prior art.
  • the problem of information is beneficial to alleviate the waste of resources caused by STAs, especially for STAs with low energy consumption requirements.
  • the method may further include sending, to the STA, a multicast ID of the multicast group where the STA is located.
  • the AP sends the multicast ID of the multicast group of the STA to the STA before sending the multicast information of the multicast group to the STA according to the order of the multicast IDs of the multicast groups that are sent by the multicast information.
  • the STA obtains the multicast ID of its own multicast group in advance, and then receives the multicast information of its own multicast group in the corresponding receiving interval according to the multicast ID of the multicast group.
  • the STA stores the received multicast ID of its own multicast group locally.
  • the MID that identifies a multicast group is not unique. In practice, multiple MIDs may be allowed to identify the same multicast group. Therefore, another method for transmitting multicast information provided by another embodiment of the present invention is shown in FIG. 2b as a flowchart of the method.
  • the execution subject of this embodiment is an AP, but is not limited thereto. As shown in FIG. 2b, the method in this embodiment includes:
  • the access point AP sends a multicast group association identifier MID to the station STA, where one multicast group has one or more MIDs, and each of the MIDs corresponds to one multicast group and a receiving period of STAs in the multicast group. ;
  • the AP sends a transmit transmission indication mapping DTIM beacon frame to the STA, where the DTIM beacon frame includes the MID, and is used to indicate that the multicast information is sent to the STA by the multicast group.
  • the AP sends the multicast information of the multicast group, where the multicast information carries the MID or information associated with the MID, and the multicast information is received by the STA.
  • the different MIDs corresponding to the same multicast group correspond to different periods for receiving multicast information
  • the information associated with the MID may be the MAC address of the multicast group.
  • the MID indicates that the multicast group has multicast information sent to the STA to wake up the STA to receive the multicast information.
  • the access point AP may send the multicast group association identifier MID to all or part of the STAs.
  • the STAs that belong to a multicast group may need to wake up to receive multicast information in different periods.
  • the period of receiving multicast information may also be referred to as a multicast listen interval.
  • STA-1 and STA 2 belong to multicast group A, but the period in which STA-1 and STA-2 need to receive multicast information is different.
  • STA-1 can receive multicast information in each DTIM wake-up, while STA-2 wakes up every 2 DTIMs. Therefore, assign MID-1 to STA-1 and MID-2 to STA-2.
  • STA-1 receives a packet in which DTIM finds MID-1, it receives the packet.
  • STA-2 receives data when it receives data in the DTIM indicating that MID-2 has data.
  • MID-1 and MID-2 correspond to multicast group A.
  • the preset sending interval may be an average sending duration of the multicast information.
  • the AP allocates a length of multicast information to each multicast group that has multicast information in the order of the MID of the multicast group that has the multicast information.
  • the average transmission time is used as the transmission interval, and the multicast information of the corresponding multicast group is transmitted in the allocated transmission interval, so that the multicast information of the multicast group is sequentially transmitted according to the order of the multicast ID.
  • the average duration of sending the multicast information may be a preset experience value.
  • the average transmission duration of the multicast information may be the size of the multicast information to be sent by each multicast group before the AP transmits the multicast information after determining the multicast group to which the multicast information is to be sent. The rate of transmission is calculated.
  • the foregoing sending interval may be a beacon frame interval (Beacon Interval in English), where the beacon frame interval refers to an interval between two beacon frames.
  • the beacon frame here includes a TIM beacon frame indicating that the bit is a Traffic Indication Map (TIM), and also includes a DTIM beacon frame.
  • the AP may send a TIM beacon frame before the next DTIM beacon frame after the current DTIM beacon frame, and the AP may send the multicast information of the multicast group after the current DTIM beacon frame. Transmitting multicast information of the multicast group after the current DTIM beacon frame and the TIM beacon frame between the current DTIM beacon frame and the next DTIM beacon frame, or transmitting within the beacon frame interval of the current DTIM beacon frame information.
  • the AP may indicate in the DTIM beacon frame all MIDs that need to receive multicast information before the next DTIM beacon frame.
  • Partial Virtual Bitmaps in existing DTIM beacon frames are only STAs that indicate unicast data. When MID is used to identify multicast groups, some virtual bitmaps in DTIM beacon frames can also be used. Indicates a multicast group with multicast information.
  • the DTIM contains information indicating the page, block, and sub-block to which the STA having the unicast information belongs, after the MID identifies the multicast group, the DTIM can also use the information to indicate the multicast with the multicast information. The page, block, and sub-block where the group is located.
  • the number of TIM beacon frames transmitted by the AP between two DTIM beacon frames can be adaptively determined. If the number of TIM beacon frames between two DTIM beacon frames is greater than or equal to the number of multicast groups with multicast information, the AP may send a multicast after each TIM beacon frame. Group multicast information, but is not limited to this.
  • the AP can simultaneously send multicast information of at least two multicast groups after one of the TIM beacon frames or the current DTIM beacon frame to ensure that the multicast information of each multicast group is Can be successfully sent to the STA.
  • the AP sends the MID of the multicast group where the STA is located before sending the multicast information of the multicast group to the STA according to the order of the MIDs of the multicast groups that are sent by the multicast information.
  • the STA is configured to enable the STA to know the MID of the multicast group in the multicast group.
  • the multicast information of the multicast group in the multicast group is received according to the MID of the multicast group.
  • the STA stores the received MID of the multicast group it is in locally.
  • the AP may actively initiate the allocation of the multicast ID, that is, the AP sends the multicast MID of the multicast group where the STA is located to the STA.
  • the STA may actively request the MID of the multicast group in which the STA is located.
  • An embodiment of the step 101 includes: the AP receives the information of the request MID sent by the STA, and the AP sends the MID of the multicast group where the STA is located to the STA according to the information of the received request MID.
  • the information of the request MID sent by the STA may be a multicast media access control (Media Access Control) (MAC) address or other information that can uniquely identify the multicast group to which the STA belongs.
  • the AP identifies the multicast group where the STA is located according to the request MID information sent by the STA, and then determines the MID of the multicast group where the STA is located.
  • the AP may allocate the MID to the STA in real time, or directly obtain the pre-assigned multicast ID.
  • a specific implementation manner in which the STA sends the information requesting the MID to the AP is: the STA encapsulates the information of the request MID in the request message and sends the information to the AP.
  • the specific manner of receiving the information of the request MID sent by the STA is: the AP receives the request message sent by the STA, where the request message includes the information of the requested multicast ID, and the AP specifically obtains the request from the request message. Multicast ID information.
  • the request message may be a new message.
  • a specific new request message may be a request message called a MID Request.
  • information frame 1 shown as: information frame 1 version information
  • MID request MID Request IE may contain less in the MID Request: version information, MID request (MID Request) And MID Request IE (Information Element, called IE).
  • the version information is used to indicate that the message belongs to a standard version information, and is a non-essential information field.
  • the MID request is used to indicate that the information is MID Request information, which is an information frame requesting MID.
  • the MID Request IE carries the specific requested information.
  • the MID Request IE is as follows, the information frame 2 is shown as: Information Frame 2
  • Multicast MAC address 1 Multicast MAC address 2
  • the MID request information element may include an ID of the IE, a length of the IE, a MAC address of a multicast group that wishes to obtain the MID, and a multicast listen interval that is desired to receive the multicast group data.
  • the MAC address of the multicast group that wants to obtain the MID and the period in which it wants to receive the multicast group data may be allowed to be multiple. That is, one STA is allowed to request the MID of multiple multicast groups in one request message.
  • the MAC address of the multicast group is required, and the AP allocates the MID according to the MAC address of the multicast group, and other information fields are optional.
  • the STA adds a cell unit (IE) in the existing control frame or the existing management frame or the existing data frame.
  • the information of the request MID is encapsulated in a new IE and sent to the AP.
  • a specific new IE is the MID Request IE or the information carried in the MID Request IE is included in the existing AID Request IE.
  • the newly added IE is placed in an existing message frame, and the newly added IE may be placed in an Association Request or a Reassociation Request or an AID Switch Request. in.
  • the specific manner of receiving the information of the request MID sent by the STA is: The AP receives the existing control frame or the existing management frame or the existing data frame sent by the STA, and the existing control frame or the existing management frame or the existing
  • the newly added IE in the data frame includes the information of the requested multicast ID, and the AP obtains the information of the requested MID from an existing IE or an existing IE or an existing IE in the existing data frame.
  • the AP sends the multicast ID of the multicast group where the STA is located to the STA.
  • the AP encapsulates the multicast ID of the multicast group where the STA is located in the newly added management frame or adds a new one.
  • the control frame is sent to the STA.
  • a specific new message frame can be called MID The message frame of the Response (MID reply), which is the MID of the multicast group sent by the access point AP to the station STA.
  • the MID information frame can be regarded as the MID Response because the MID is sent after the STA requests. Referring to the following specific embodiment, an MID information frame, information frame 3: information frame 3
  • the fields that IE can include in MID Response are: version information, MID reply, and MID Response IE.
  • the version information is used to indicate that the message belongs to a certain version of the version information, and the part of the bit is not required, for example, may be pre-negotiated by default or by a system setting.
  • the MID reply is used to indicate that the information is an information frame of the MID Response.
  • information frame 4 information frame 4
  • the information that the MID Response IE can contain: the ID of the IE, the length of the IE, the multicast MAC address, the MID corresponding to the allocated MID, the multicast listen interval allowed to receive the multicast information, the MID effective time, and the status information. . If the STA requests the MID of multiple multicast groups, the multicast MAC address in the IE, the MID corresponding to the allocated MID, the multicast listen interval allowed for receiving multicast information, the MID effective time, and the status information part may be Multiple.
  • the MID request information unit in the application includes: a MAC address of the multicast group or a period in which the STA receives the multicast information of the multicast group is necessary, because the AP receives the group according to the MAC address of the multicast group or the STA.
  • the MID of the multicast group is allocated periodically.
  • the MID corresponding to the corresponding multicast MAC address allocation may be one or more MIDs, or may be composed of a page indicating bitmap combined with the MID.
  • the page indicates that the bitmap identifies one or more pages to which the current MID is to be assigned.
  • the page here corresponds to the page in the TIM structure.
  • the AP may allocate the MID dispersed in the plurality of pages according to the period in which the STA is to receive the multicast information, so that the partial virtual bitmap in a DITM only indicates that the STA receives the data in one page. The situation, in order to meet the need for STAs to receive multicast information in different periods.
  • another method for transmitting multicast information according to an embodiment of the present invention includes
  • S2301 The AP sends the MID of the multicast group to the STA of the station, where each MID corresponds to one multicast group and a receiving period of the STA in the multicast group.
  • the AP sends a DTIM beacon frame to the STA, where a part of the virtual bitmap of the DTIM beacon frame includes MID indication information for one or more pages, and the same page is included in different pages.
  • a part of the virtual bitmap of the DTIM beacon frame includes MID indication information for one or more pages, and the same page is included in different pages.
  • Different MIDs of the broadcast group where the different MIDs correspond to the same receiving period of the STAs in the multicast group;
  • the AP sends the multicast information of the multicast group, where the multicast information carries the MID information or information associated with the MID, and the multicast information is received by the STA.
  • An example is as follows: When a partial virtual bitmap in DTIM indicates only one page and all four pages of the loop are looped according to the order of 1, 2, 3, 4, if STA-1 needs to receive each DTIM, and STA— 2 It needs to be received every other DTIM period, then it needs to allocate 4 MIDs to STA-1.
  • the 4 MIDs are mapped in 4 pages respectively, so that it can know whether there is data reception in each DTIM.
  • By assigning 2 MIDs to STA-2 the two MIDs are mapped in pages 1 and 3, respectively, to ensure that STA-2 can receive multicast information in the desired receiving period.
  • the page of the MID mapping can be different depending on the order in which the TIM bitmap indicates the loop of the page in DTIM.
  • MIDs corresponding to the same multicast group in the same cycle can be mapped to the same block and sub-block of different pages.
  • the MID effective time means that the specified MID is effective immediately or after a period of time, where the period of time may be several Beacon Intervals, or several Beacons containing TIMs, or several include DITM Beacon.
  • the AP allocates the MID of the multicast group in which the STA is located to the STA.
  • the AP adds an IE to the existing management frame or the existing control frame or the existing data frame.
  • the multicast ID of the multicast group in which the STA is located is encapsulated in the newly added IE and sent to the STA.
  • a specific new IE is the MID Response IE or the information in the MID Response IE is included in the existing AID Response IE.
  • Another specific method of including new IEs into existing message frames Add new IEs in Association Response or Reassociation Response and AID Switch Response.
  • the STA may send an acknowledgement (ACK) message to the AP, so that the AP can know in time whether the STA successfully receives the multicast of the STA.
  • the multicast ID of the group Based on this, after the AP sends the multicast ID of the multicast group where the STA is located to the STA, the AP includes: the AP receives the ACK message sent by the STA.
  • the AP needs to resend the multicast ID of the multicast group where the STA is located.
  • the AP may also initiate a logout process of the multicast ID. Based on this, the method in this embodiment further includes: the AP sends a multicast ID deregistration message to the STA, where the multicast ID deregistration message includes a logout indication indicating that the multicast ID of the multicast group where the STA is located is logged off.
  • the multicast ID logout message may further include a multicast ID that needs to be logged off (that is, a multicast ID of the multicast group where the STA is located).
  • the STA receives the multicast ID logout message sent by the AP, and learns that the multicast ID of the multicast group in which the AP is located needs to be logged off, and the association relationship with the multicast ID is released based on the multicast ID.
  • the STA may send an ACK message to the AP to notify the AP that the multicast ID deregistration message has been received.
  • the AP receives the ACK message sent by the STA. On the premise that an ACK message is sent, if the AP does not receive an ACK message within a certain period of time, it needs to resend the multicast ID logout message to the STA that has not received its ACK message.
  • An optional implementation manner in which the AP sends a multicast ID deregistration message to the STA includes: the AP encapsulates the multicast ID deregistration message in a newly added management frame or a newly added control by using a newly added management frame or a newly added control frame. The frame is sent to the STA.
  • Another optional implementation manner in which the AP sends a multicast ID deregistration message to the STA includes: the AP adds an IE to an existing management frame or a control frame or a data frame, and encapsulates the multicast ID deregistration message in the newly added IE. Send to the corresponding STA.
  • the process of deregistering the multicast ID may be initiated by the STA.
  • the STA when the STA needs to be disassociated with the multicast group, the STA sends a multicast ID logout request to the AP to request to release the group.
  • the method in this embodiment further includes: the AP receives the multicast ID deregistration request sent by the STA, and the optional multicast ID deregistration request includes the multicast ID of the multicast group where the STA is located, that is, the multicast ID that needs to be logged off.
  • the AP may also send an ACK message to the SAT after receiving the multicast ID deregistration request.
  • An optional implementation manner in which the STA sends a multicast ID deregistration request to the AP includes: the STA uses the request message, and encapsulates the multicast ID deregistration request in a request message and sends the request to the AP.
  • the specific implementation manner of the AP receiving the multicast ID cancellation request sent by the STA includes: receiving, by the AP, a request message sent by the STA, and acquiring the multicast ID cancellation request from the request message.
  • the request message here can also be a new message.
  • Another optional implementation manner in which the STA sends a multicast ID deregistration request to the AP includes: the STA adds an IE in an existing control frame or a management frame or a data frame, and encapsulates the multicast ID deregistration request in a new The IE is sent to the AP.
  • the specific implementation manner of the AP receiving the multicast ID deregistration request sent by the STA includes: the AP receiving an existing control frame or a management frame or a data frame sent by the STA, and new from the existing control frame or the management frame or the data frame.
  • the multicast ID logout request is obtained in the added IE.
  • the AP may also initiate a change of the multicast ID. Based on this, the method in this embodiment further includes: the AP sends a multicast ID change message to the STA, where the multicast ID change message includes the changed multicast ID of the multicast group where the STA is located.
  • the multicast ID change message may further include an original multicast ID of the multicast group where the STA is located. For a multicast group, the original multicast ID of the multicast group is the multicast ID to be changed, and the new multicast ID used by the multicast group is the changed multicast.
  • the STA receives the multicast ID change message sent by the AP to learn that the multicast ID needs to be changed and determines the changed multicast ID.
  • the STA may send an ACK message to the AP. If the AP does not receive the ACK message within a certain period of time, the AP needs to resend the multicast ID change message to the STA that has not received the ACK message.
  • An optional implementation manner of the AP sending the multicast ID change message to the STA includes: the AP uses the newly added management frame or the newly added control frame to encapsulate the MID change message in the newly added management frame or the newly added control frame. Sent to the STA.
  • a specific implementation method is that the AP can use MID Response to complete the MID change.
  • Another optional implementation manner in which the AP sends a multicast ID change message to the STA includes: the AP adds an IE to the existing management frame or the control frame or the data frame, and encapsulates the multicast ID change message in the newly added IE. Send to the corresponding STA.
  • a specific new IE is the MID Response IE or the information in the MID Response IE is included in the existing AID Response IE.
  • a specific one will add IE
  • the method included in the existing message frame is to add a new IE in the Association Response or Reassociation Response and or the AID Switch Response.
  • the change of the multicast ID may be initiated by the STA.
  • the STA may send a multicast ID change request to the AP, and then the receiving AP changes according to the multicast ID.
  • the multicast ID change message to be sent the multicast ID change message includes the changed multicast ID of the multicast group where the STA is located.
  • the AP sends a multicast ID change message to the STA.
  • the AP receives the multicast ID change request sent by the STA, and sends a multicast ID change message to the STA according to the multicast ID change request.
  • the multicast ID change request may include a MAC address, an IP address, or other information that can uniquely identify the STA.
  • the AP may re-assign a multicast ID to the STA according to the information carried in the multicast ID change request, and then send the re-assigned multicast ID to the STA as the changed multicast ID.
  • An optional implementation manner of the STA sending the multicast ID change request to the AP includes: the STA uses the newly added request message, and encapsulates the multicast ID change request in the newly added request message and sends the request to the AP.
  • the specific implementation manner of the AP receiving the multicast ID change request sent by the STA includes: the AP receives the newly added request message sent by the STA, and obtains the multicast ID change request from the newly added request message.
  • a specific new request message may be to use MID Request to complete the MID change.
  • Another optional implementation manner in which the STA sends a multicast ID change request to the AP includes: the STA adds an IE to the existing control frame or the management frame or the data frame, and encapsulates the multicast ID change request in the new The IE is sent to the AP.
  • the specific implementation manner of the AP receiving the multicast ID change request sent by the STA includes: the AP receiving an existing control frame or a management frame or a data frame sent by the STA, and new from the existing control frame or the management frame or the data frame.
  • the multicast ID change request is obtained in the added IE.
  • a specific new m is the MID Request IE or the information contained in the MID Request IE is included in the existing AID Request IE.
  • a specific method of including a new IE into an existing message frame is to add an association request in an Association Request and a Reassociation Request and or an AID Switch Request. IE.
  • the foregoing embodiments provide various implementations for the AP to send a multicast ID, a logout multicast ID, and a change multicast ID to the STA, and implement the management of the multicast ID, which has the advantage that the single-chip is easy to implement.
  • the multicast ID of each multicast group may be a MAC address or an FMS ID, but is not limited thereto.
  • the multicast ID of each multicast group is at least one association identifier (Association ID, called AID).
  • the AID here may be an AID other than the unicast AID in the AID space. Which specific AIDs are used as unicast AIDs, and which AIDs are used as multicast IDs can be determined by the AP itself. That is, as long as the AID as the multicast ID is different from the AID used for unicast.
  • the AP may send the multicast ID of the multicast group in which the STA is located to the STA.
  • the AP may map the multicast ID of the multicast group where the STA is located in an AID.
  • the AP maps the multicast ID of the multicast group where the STA is located in at least two AIDs.
  • the STA's AID is divided into different groups according to pages (in English), blocks (blocks in English), and sub-blocks (sub-blocks in English).
  • Figure 3 shows the structure of an AID that supports four Pages.
  • an AID structure that supports four Pages there can be 32 Blocks in a Page, and 8 Sub-blocks in a Block, and a Sub-block can support 8 STAs.
  • the AID of this structure can support up to 8192 STAs. Since the AID space is sufficient, in the embodiment, some of the AIDs are used as the multicast ID, so that there is no need to additionally set the multicast ID, so that there is no need to increase the beacon by carrying the set multicast ID. Frames facilitate compression of beacon frames.
  • the AP maps the multicast ID of the multicast group in which the STA is located in an AID.
  • the AP can map the multicast ID of the multicast group where the STA is located to any page in the AID. , Block and / or Sub-block.
  • the multicast IDs of multiple multicast groups can use the same AID.
  • the multicast IDs of these multicast groups can be arbitrarily allocated in different Pages, Blocks, and/or Sub-blocks.
  • the AP maps the multicast ID of the multicast group in which the STA is located in an AID.
  • the AP maps the multicast ID of the multicast group where the STA is located to the AID.
  • the multicast IDs of multiple multicast groups can also use the same AID.
  • the multicast IDs of these multicast groups can be allocated in pre-specified Page, Block, and/or Sub-block. In this way, the multicast IDs of all multicast groups belong to the same Page, Block or Sub-block, which is beneficial to management.
  • the AP maps the multicast ID of the multicast group in which the STA is located to at least two AIDs.
  • the specific implementation manner includes: the AP maps the multicast ID of the multicast group where the STA is located to at least two AIDs. In different Page, Block or Sub-block. Where multiple multicasts The multicast ID of the group may use the same at least two AIDs, and the multicast IDs of the multicast groups may be allocated in different Pages, Blocks, and/or Sub-blocks of the at least two AIDs.
  • the AP mapping the multicast ID of the multicast group in which the STA is located to the at least two AIDs includes: mapping, by the AP, the multicast ID of the multicast group where the STA is located in at least two The same Page, Block, and/or Sub-block in the AID.
  • the multicast IDs of multiple multicast groups can use the same at least two AIDs, and the multicast IDs of these multicast groups can be allocated in the same Page, Block, and/or Sub-block of the at least two AIDs.
  • the manner in which the AID is used as the multicast ID of the multicast group includes but is not limited to: (1) an AID corresponds to a multicast ID of one or more multicast groups, and the multicast ID or the multicast ID can be arbitrarily allocated. In different Page, Block and / or Sub-block.
  • An AID corresponds to the multicast ID of one or more multicast groups, and all AIDs used to identify the multicast ID of the multicast group use the same Page, Block, and/or Sub-block.
  • a multicast ID can be identified by multiple AIDs, which can use the same or different Page, Block, and/or Sub-block.
  • the multicast ID represented by the AID may be continuous or discontinuous.
  • the AID is used as the multicast ID of the multicast group.
  • the AID as the multicast ID can be specified by the AP, and the STA does not need to negotiate with the AP. It has strong implementation flexibility.
  • the AID as the multicast ID does not require the transmission period of the multicast information. It supports both the multicast information that is periodically sent and the multicast information that is randomly sent. It can be applied to more applications.
  • the AID resource and the FMS ID of the multicast ID are rich, which solves the problem that the multicast application is limited due to the limited number of multicast cycles supported by the FMS ID.
  • the manner in which the DTIM beacon frame is used to indicate a multicast group that has multicast information is: using a partial virtual bitmap in a DTIM beacon frame (in English, a partial virtual bitmap) ) Indicates a multicast group with multicast information to send.
  • a part of the virtual bitmap is used to indicate that the STA corresponding to the AID needs to receive the downlink data in the unicast case.
  • the AID is used as the multicast ID, so in the multicast situation.
  • the multicast group that has been sent by the multicast message may be indicated by a part of the virtual bitmap that already exists in the beacon frame.
  • the beacon frame identifies the multicast by using the AID corresponding to the multicast ID in the partial virtual bitmap for identifying the unicast data. group. For example, if the bit corresponding to an AID in a part of the virtual bitmap is 1, it means that the multicast group using the AID as the multicast ID has multicast information to be sent, if the bit corresponding to multiple AIDs in the partial virtual bitmap is 1 , indicates that multicast groups that use these AIDs as multicast IDs have multicast information to send. It can be seen that using the AID as the multicast ID can also notify the multicast group with multicast information transmission by using the existing bits in the beacon frame, and does not need to increase the beacon frame, which is beneficial to the compression of the beacon frame.
  • the AP sequentially sends the multicast group with the multicast information transmission at the sending interval according to the order of the multicast IDs of the multicast group that has the multicast information.
  • Multicast information and the STA receives the multicast information of its own multicast group at the corresponding receiving interval according to the multicast ID of the multicast group in which the multicast group is located in the multicast ID of the multicast group that has multicast information.
  • FIG. 4 is a flowchart of a method for receiving multicast information according to an embodiment of the present invention. As shown in FIG. 4, the method in this embodiment includes:
  • Step 401 The STA receives the DTIM beacon frame sent by the AP, and the DTIM beacon frame is used to indicate the multicast group with the multicast information.
  • Step 402 The STA receives, according to the order of the multicast IDs of the multicast group in which the STA is located, the multicast ID of the multicast group that is sent by the multicast group, and receives the sent by the AP in the receiving interval corresponding to the multicast group where the STA is located. Multicast information of the multicast group where the STA is located.
  • each multicast group has a multicast ID, which is used to uniquely identify the multicast group.
  • the AP stores multicast information of each multicast group that has multicast information.
  • the AP first sends a beacon frame to the STA, where the type indication bit in the beacon frame indicates that the beacon frame is a DTIM beacon frame, and the DTIM is passed through the DTIM.
  • the beacon frame informs the STA on the one hand that the multicast information will be sent after the DTIM beacon frame, and on the other hand informs the STA which multicast group or groups of multicast packets are sent.
  • the STA receives the DTIM beacon frame sent by the AP, parses the received beacon frame, learns the multicast group to which the multicast information is to be sent, and determines the location according to the multicast ID of the multicast group in which the multicast group is located. Whether the multicast group belongs to the multicast group with multicast information to be sent as indicated by the DTIM beacon frame. After the STA determines that the multicast group to which it belongs belongs to the multicast group to which the multicast information is to be sent as indicated by the DTIM beacon frame, the STA prepares to receive the multicast information sent by the AP.
  • the multicast information of the multicast groups is sequentially transmitted at each transmission interval according to the order of the multicast IDs of the multicast groups that have multicast information.
  • the processing mode that is compatible with the AP is to determine the order of the multicast ID of the multicast group in which the multicast group is located in the multicast ID of the multicast group that has the multicast information sent by the DTIM beacon frame.
  • the receiving interval corresponding to the multicast group is determined, and then the multicast information of the multicast group in the multicast group is received in the corresponding receiving interval, and the multicast information of other multicast groups is not received, thereby solving the existing In the technology, after receiving the DTIM beacon frame, the STA needs to receive all the multicast information after the DTIM beacon frame, which is beneficial to alleviating the waste of the STA caused by the STA, and is particularly suitable for STAs with low energy consumption requirements.
  • each receiving interval is an average sending duration of the multicast information.
  • the STA Based on the sequence of the multicast ID of the multicast group in which the STA is located, the STA receives the STAs sent by the AP in the receiving interval corresponding to the multicast group where the STA is located.
  • the multicast information of the multicast group is specifically as follows: The average length of the multicast information sent by the STA is based on the multicast ID of the multicast group in which the multicast group is located. , determine your own wake-up time, and then receive multicast information.
  • the STAs in the three multicast groups receive the corresponding multicast information is as shown in FIG. 5 .
  • the STAs in the first multicast group wake up to receive their own multicast information (that is, the multicast information of the first multicast group) after the DTIM beacon frame.
  • the STAs in the second multicast group are waiting for one multicast.
  • the average transmission time of the information wakes up and receives the multicast information of its own (ie, the multicast information of the second multicast group); the STAs in the third multicast group wake up and receive the broadcast after waiting for the average transmission duration of the two multicast information. Own multicast information (that is, multicast information of the third multicast group).
  • the average length of time that the STA waits for one multicast message may be one more waiting for one SIFS. For example, if the STA waits for the average transmission duration of two multicast messages, the total waiting duration is (the average transmission duration of 2 multicast messages + 2 SIFS).
  • the average duration of sending the multicast information may be a preset experience value.
  • the average transmission duration of the multicast information may be the size of the multicast information to be sent by each multicast group before the AP transmits the multicast information after determining the multicast group to which the multicast information is to be sent.
  • the sending rate is calculated and sent to the STA.
  • each receive interval is a beacon frame interval, where the beacon frame interval refers to the interval between two beacon frames.
  • the beacon frame here includes both TIM beacon frames and DTIM beacon frames.
  • the STAs in each multicast group with multicast information transmission may receive the current DTIM beacon frame after the next DTIM beacon frame before the TIM beacon frame according to the order of the multicast IDs of the multicast group in which the multicast group is located. Receive their multicast messages in sequence.
  • the multicast information of one or more multicast groups may be sent after the DTIM beacon frame or the TIM beacon frame. As shown in Figure 6, the multicast group whose multicast information is sent is the first multicast group, the second multicast group, and the third multicast group. The size of the multicast ID of the three multicast groups.
  • the STAs in the first multicast group wake up to receive their own multicast information after the current DTIM beacon frame, in order of the first multicast group, the second multicast group, and the third multicast group.
  • the second multicast group wakes up to receive its own multicast information after the first TIM beacon frame after the current DTIM beacon frame (multicast of the second multicast group)
  • the third multicast group wakes up to receive its own multicast information (ie, multicast information of the third multicast group) after the second TIM beacon frame after the current DTIM beacon frame. It is explained here that the number of TIM beacon frames transmitted by the AP between two DTIM beacon frames can be adaptively determined.
  • the multicast ID may be a MAC address or an FMS ID, etc., but is not limited thereto.
  • the multicast ID is at least one AID. That is, the multicast ID of the multicast group (including the multicast group where the STA is located) with the multicast information is at least one AID. Among them, which AIDs are used as unicast AIDs, and which AIDs are used as multicast IDs can be determined by the AP itself. That is, as long as the AID as the multicast ID is different from the AID used for unicast.
  • the manner in which the DTIM beacon frame is used to indicate the multicast group with multicast information transmission is: using a partial virtual bitmap in the DTIM beacon frame to indicate that the multicast information is sent.
  • Multicast group For example, if the bit corresponding to an AID in the partial virtual bitmap is 1, it means that the multicast group using the AID as the multicast ID has multicast information to be sent, if the bit corresponding to multiple AIDs in the partial virtual bitmap is 1 , indicates that multicast groups that use these AIDs as multicast IDs have multicast information to send. It can be seen that using the AID as the multicast ID can also notify the multicast group with multicast information transmission by using the existing bits in the beacon frame, and does not need to increase the beacon frame, which is beneficial to the compression of the beacon frame.
  • the method in this embodiment further includes: before step 401:
  • Step 400 The STA receives the multicast ID of the multicast group where the STA is sent by the AP.
  • the STA can obtain the multicast ID of the multicast group in the multicast group, and then receive the multicast information of the multicast group in the multicast group according to the multicast ID of the multicast group.
  • the AP may actively initiate the allocation of the multicast ID, that is, the AP sends the multicast ID of the multicast group where the STA is located to the STA.
  • the STA may receive the multicast ID of the multicast group where the STA is actively sent by the AP.
  • the STA may actively request the multicast ID of the multicast group in which the STA is located, and the STA receives the multicast ID of the multicast group where the STA is sent by the AP, and the STA sends the request multicast to the AP. ID information, and then the STA receives the multicast ID of the multicast group in which the STA is located according to the information of the request multicast ID.
  • the information of the requested multicast ID sent by the STA may be a MAC address of the STA, an IP address, or other information that can uniquely identify the STA.
  • the AP identifies the STA according to the information of the requested multicast ID sent by the STA, and then determines the multicast ID of the multicast group where the STA is located.
  • the AP may allocate the multicast ID to the STA in real time, or directly obtain the pre-assigned multicast ID.
  • An optional implementation manner in which the STA sends the information requesting the multicast ID to the AP includes: the STA encapsulates the information of the requested multicast ID in a request message and sends the information to the AP.
  • the request message may be a new message.
  • Another optional implementation manner in which the STA sends the information requesting the multicast ID to the AP includes: the STA adds an IE to the existing control frame or the existing management frame or the existing data frame, and the information of the request multicast ID is sent. The encapsulation is sent to the AP in the newly added IE.
  • An optional implementation manner of the STA receiving the multicast ID of the multicast group in which the STA is sent by the AP includes: the STA receives the newly added management frame or the newly added control frame sent by the AP, and the newly added management frame or the newly added control
  • the frame includes the multicast ID of the multicast group where the STA is located, and the STA obtains the multicast ID of the multicast group where the STA is located from the newly added management frame or the newly added control frame.
  • Another optional implementation manner in which the STA receives the multicast ID of the multicast group in which the STA is sent by the AP includes: the STA receives the existing management frame or the existing control frame or the existing data frame sent by the AP, and the existing management frame
  • the new IE in the existing control frame or the existing data frame includes the multicast ID of the multicast group where the STA is located.
  • the STA is specifically new from the received existing management frame or the existing control frame or the existing data frame.
  • the multicast ID of the multicast group where the STA is located is obtained in the IE.
  • the STA receives the group of the STA sent by the AP. After the multicast ID of the group is broadcast, an ACK message can be sent to the AP. In this way, the AP can know in time whether the STA receives the multicast ID of the multicast group where the STA is located. In the case that the STA is required to send an ACK message, if the AP does not receive the ACK message within a certain period of time, the AP needs to resend the multicast ID of the multicast group where the STA is located to the STA.
  • the AP may also initiate a multicast ID deregistration process, for example, the AP sends a multicast ID deregistration message to the STA, and carries a multicast indication in the multicast ID deactivation message indicating the multicast group where the STA is located. Logout instruction for ID logout.
  • the method in this embodiment further includes: the STA receives the multicast ID deregistration message sent by the AP, and learns that the association needs to be disassociated with the multicast group in which the AP is located, and thus the association relationship between the multicast group and the required multicast group is released.
  • the STA may send an ACK message to the AP to notify the AP that the multicast ID logout message has been received.
  • the AP receives the ACK message sent by the STA.
  • an ACK message is sent, if the AP does not receive an ACK message within a certain period of time, it needs to resend the multicast ID logout message to the STA that has not received its ACK message.
  • An optional implementation manner of the AP sending the multicast ID deregistration message to the STA includes: the AP uses the newly added management frame or the control frame, and encapsulates the multicast ID deregistration message in a newly added management frame or control frame and sends the message to the STA.
  • the STA receives the newly added management frame or control frame or data frame sent by the AP, and obtains the multicast ID logout message from the received new management frame or control frame or data frame.
  • Another optional implementation manner in which the AP sends a multicast ID deregistration message to the STA includes: the AP adds an IE to an existing management frame or a control frame or a data frame, and encapsulates the multicast ID deregistration message in the newly added IE. Send to the corresponding STA.
  • the STA receives the existing management frame or control frame or data frame sent by the AP, and obtains the multicast ID deregistration message from the received existing management frame or control frame or data frame.
  • the process of deregistering the multicast ID may be initiated by the STA.
  • the STA sends a multicast ID deregistration request to the AP, so that the AP is configured according to the group.
  • the broadcast ID logout request will log out the multicast ID of the multicast group it is in.
  • the AP receives the multicast ID deregistration request sent by the STA.
  • the multicast ID deregistration request may include a multicast ID of the multicast group where the STA is located, that is, a multicast ID that needs to be logged off.
  • the AP may also send an ACK message to the SAT after receiving the multicast ID deregistration request.
  • the STA receives the ACK message sent by the AP, so as to timely know that the AP receives the multicast ID deregistration request. Conducive to the timely cancellation of the multicast ID. If the AP is required to return an ACK message, if the STA does not receive the ACK message sent by the AP within a certain period of time, the STA needs to resend the multicast ID logout request to the AP.
  • An optional implementation manner in which the STA sends a multicast ID deregistration request to the AP includes: the STA encapsulates the multicast ID deregistration request in the newly added request message and sends the request to the AP by using the newly added request message.
  • Another optional implementation manner in which the STA sends a multicast ID deregistration request to the AP includes: the STA adds an IE in an existing control frame or a management frame or a data frame, and encapsulates the multicast ID deregistration request in a new The IE is sent to the AP.
  • the AP may also initiate a change of the multicast ID.
  • the AP sends a multicast ID change message to the STA, where the multicast ID change message includes the multicast ID of the changed multicast group.
  • the multicast ID change message may further include an original multicast ID of the multicast group where the STA is located.
  • the original multicast ID of the multicast group is a multicast ID that needs to be changed.
  • the new multicast ID of the multicast group refers to the changed multicast ID.
  • the method of this embodiment further includes: receiving, by the STA, a multicast ID change message sent by the AP, to learn that the multicast ID needs to be changed, and determining the changed multicast ID.
  • the STA updates the multicast ID of the multicast group where the STA is located according to the changed multicast ID of the multicast group in which the STA is included in the multicast ID change message.
  • the STA may send an ACK message to the AP.
  • the AP needs to resend the multicast ID change message to the STA that has not received its ACK message.
  • An optional implementation manner of the AP sending the multicast ID change message to the STA includes: the AP uses the newly added management frame or control frame, and encapsulates the multicast ID change message in a newly added management frame or control frame and sends the message to the STA.
  • the STA receives the newly added management frame or control frame sent by the AP, and obtains the multicast ID change message from the received new management frame or control frame.
  • Another optional implementation manner in which the AP sends a multicast ID change message to the STA includes: the AP adds an IE to the existing management frame or the control frame or the data frame, and encapsulates the multicast ID change message in the newly added IE. Send to the corresponding STA.
  • the STA receives the existing management frame or control frame or data frame sent by the AP, and obtains the multicast ID change message from the received existing management frame or the newly added IE in the control frame or the data frame.
  • the change of the multicast ID may also be initiated by the STA.
  • the method of this embodiment further includes: when the STA needs to change the multicast ID, the STA may send a multicast ID change request to the AP, and then receive a multicast ID change message sent by the AP according to the multicast ID change request. Accordingly, the AP receives the multicast ID change request sent by the STA, and transmits the changed multicast ID to the STA according to the multicast ID change request.
  • the multicast ID change request may include a MAC address, an IP address, or other information that can uniquely identify the STA.
  • the AP may re-assign a multicast ID to the STA according to the information carried in the multicast ID change request, and then send the re-assigned multicast ID to the STA as the changed multicast ID.
  • An optional implementation manner in which the STA sends a multicast ID change request to the AP includes: the STA uses the request message, and encapsulates the multicast ID change request in the request message and sends the request to the AP.
  • the request message here can also be a new message.
  • Another optional implementation manner in which the STA sends a multicast ID change request to the AP includes: the STA adds an IE in an existing control frame or a management frame or a data frame, and encapsulates the multicast ID change request in a new one. Sent to the AP in IE.
  • the foregoing embodiments provide various implementation manners for the STA to receive the multicast ID, the logout multicast ID, and the change multicast ID of the multicast group in which the STA is located, and implement the management of the multicast ID, which has the advantages of easy implementation. .
  • the STA receives the DTIM beacon frame from the AP, learns the multicast group that will send the multicast information according to the DTIM beacon frame, and then performs multicast according to the multicast group where the STA is located.
  • the ID is in the order of the multicast IDs of all the multicast groups that have multicast information to be sent, and receives the multicast information of the multicast group in the corresponding receiving interval.
  • the embodiment of the present invention further provides another method for receiving multicast information, where the method includes:
  • the station STA receives the multicast group association identifier MID sent by the access point AP, where one multicast group has one or more MIDs, and each of the MIDs corresponds to one multicast group and the STA in the multicast group. Receiving cycle
  • the STA receives a transmit transmission indication mapping DTIM beacon frame sent by the AP, where the DTIM beacon frame includes the MID, and is used to indicate that the multicast information is sent to the STA by the multicast group.
  • the STA receives multicast information of the multicast group sent by the AP, where the group The broadcast information carries the MID or information associated with the MID.
  • the STA sends an information frame requesting the MID to the AP, and the information frame of the MID is requested for the AP to generate the MID.
  • the information requesting the MID includes a MID request and a MID request information unit, wherein the MID request is used to indicate that the information frame is used for a MID request, and the MID request information unit is used by the AP to generate the sending to the STA MID of the multicast group.
  • the MID request information unit includes: a MAC address of the multicast group, a MAC address of the multicast group is used by the AP to allocate the MID; or a MAC address of the multicast group and the STA receives the multicast
  • the period of the group multicast information, the MAC address of the multicast group, and the period in which the STA receives the multicast information of the multicast group are used by the AP to allocate the MID.
  • the STA requests the information unit to carry the information in the MID request information unit by using the STA's association identifier AID.
  • the embodiment of the present invention further provides a method for receiving multicast group information, including: a station STA receives a multicast group MID sent by an AP, and each of the MIDs corresponds to one multicast group and a receiving period of STAs in the multicast group. ;
  • a DTIM beacon frame sent by the AP where a part of the virtual bitmap of the DTIM beacon frame includes MID indication information for one or more pages, and corresponding to the same multicast in different pages Different MIDs of the group, where the different MIDs correspond to the same receiving period of the STAs in the multicast group;
  • the STA Receiving, by the STA, the multicast information of the multicast group sent by the AP, the multicast information carrying the MID information or the information associated with the MID, where the multicast information is used by the STA receive.
  • the AID is used as the multicast ID.
  • the AID as the multicast ID can be specified by the AP, and the STA does not need to The AP performs the negotiation and has strong implementation flexibility.
  • the AID as the multicast ID does not require the multicast information transmission period. It supports both the multicast information that is periodically sent and the multicast information that is randomly sent. More application scenarios; Furthermore, the AID resources and FMS IDs of the multicast ID are rich, which solves the problem that the multicast application is limited due to the limited number of multicast cycles supported by the FMS ID.
  • An FMS mode has been proposed in the prior art. STAs working in FMS mode, can be The AP negotiates to listen to the period of the DTIM beacon frame so that there is no need to listen to every DTIM beacon frame.
  • the FMS mode can support up to 8 different periods and is identified by an FMS ID of 8 bits in length, which limits the flexibility of the application in practice.
  • the following embodiments of the present invention provide a multicast identifier sending method and a receiving method, which are used to solve the problem that the multicast application is limited due to the limited number of multicast periods supported by the FSM ID in the prior art.
  • FIG. 8 is a flowchart of a method for sending a multicast identifier according to an embodiment of the present invention.
  • the executive body of this embodiment is an AP. As shown in FIG. 8, the method in this embodiment includes:
  • Step 701 Determine a multicast identification ID of the multicast group where the STA is located, and map the multicast ID of the multicast group where the STA is located in the AID.
  • Step 702 Send the multicast ID of the multicast group where the STA is located to the STA.
  • An optional implementation manner of the AP determining the multicast ID of the multicast group in which the STA is located includes: The AP maps the multicast ID of the multicast group where the STA is located in an AID.
  • An alternative implementation manner in which the AP determines the multicast ID of the multicast group in which the STA is located includes: The AP maps the multicast ID of the multicast group where the STA is located in at least two AIDs.
  • an optional implementation manner in which an AP maps a multicast ID of a multicast group in which the STA is located in an AID includes, but is not limited to, the following:
  • the AP maps the multicast ID of the multicast group in which the STA resides to any Page, Block, and/or Sub-block in the AID.
  • the AP maps the multicast ID of the multicast group where the STA is located to the pre-specified Page, Block, and/or Sub-block in the AID.
  • the AP maps the multicast ID of the multicast group where the STA is located in at least two AIDs, including but not limited to the following:
  • the AP maps the multicast ID of the multicast group where the STA is located in different Pages, Blocks, and/or Sub-blocks of the at least two AIDs.
  • the AP maps the multicast ID of the multicast group where the STA is located in the same at least two AIDs.
  • the AP may actively initiate the allocation of the multicast ID, and the AP may actively send the multicast ID of the multicast group where the STA is located to the corresponding STA.
  • the STA may actively request the multicast ID of the multicast group in which the AP is located.
  • the method for the AP to send the multicast ID of the multicast group where the STA is located to the STA includes: receiving the STA Sending the information of the requesting multicast ID, and then sending the multicast ID of the multicast group where the STA is located to the STA according to the information of the requesting multicast ID.
  • An implementation manner of the AP receiving the information of the requesting multicast ID sent by the STA includes: receiving, by the AP, a request message sent by the STA, where the request message includes information requesting the multicast ID.
  • the request message may be a new message.
  • Another embodiment of the AP receiving the information of the requesting multicast ID sent by the STA includes: receiving, by the AP, an existing control frame or an existing management frame or an existing data frame sent by the STA, the existing control frame or an existing management frame or The newly added IE in the existing data frame includes information requesting the multicast ID.
  • the method for the AP to send the multicast ID of the multicast group in which the STA is located to the STA includes: the AP encapsulates the multicast ID of the multicast group where the STA is located in the newly added management frame or adds The control frame is sent to the STA.
  • the AP sends the multicast ID of the multicast group to which the STA is located to the STA.
  • the AP includes: adding an IE to the existing management frame or the existing control frame or the existing data frame.
  • the multicast ID of the multicast group in which the STA is located is encapsulated in the newly added IE and sent to the STA.
  • the AP further includes: the AP receives the ACK message sent by the STA. This helps to know in time whether the STA receives the multicast ID of the multicast group it is in. In the case that the STA is required to return an ACK message, if the AP does not receive the ACK message within a certain period of time, the AP needs to resend the multicast ID of the multicast group of the STA to the STA.
  • the AP may also initiate a logout process of the multicast ID. Based on this, the method in this embodiment further includes: the AP sends a multicast ID deregistration message to the STA, where the multicast ID deregistration message includes a logout indication indicating that the multicast ID of the multicast group where the STA is located is logged off.
  • the multicast ID deregistration message may further include a multicast ID that needs to be logged off, that is, a multicast ID of the multicast group where the STA is located.
  • An optional implementation manner of the AP sending the multicast ID deregistration message to the STA includes: the AP uses the newly added management frame or the control frame, and encapsulates the multicast ID deregistration message in a newly added management frame or control frame and sends the message to the STA.
  • Another optional implementation manner in which the AP sends a multicast ID deregistration message to the STA includes: the AP adds an IE to an existing management frame or a control frame or a data frame, and encapsulates the multicast ID deregistration message in the newly added IE. Send to the corresponding STA.
  • the AP may further include: the AP receives the multicast ID cancellation request sent by the STA, and performs the multicast of the STA according to the multicast ID cancellation request. The multicast ID of the group is logged off.
  • the AP may also initiate a change of the multicast ID. Based on this, the method in this embodiment further includes: the AP sends a multicast ID change message to the STA, where the multicast ID change message includes the changed multicast ID of the multicast group where the STA is located.
  • the multicast ID change message may further include a multicast ID that needs to be changed, that is, an original multicast ID of the multicast group where the STA is located.
  • the multicast ID that needs to be changed here is the original multicast ID of the multicast group
  • the changed multicast ID is the new multicast ID used by the multicast group.
  • the method for the AP to send the multicast ID change message to the STA includes: receiving, by the AP, a multicast ID change request sent by the STA, and sending a multicast ID change message to the STA according to the multicast ID change request.
  • An optional implementation manner of the AP sending the multicast ID change message to the STA includes: the AP uses the newly added management frame or control frame, and encapsulates the multicast ID change message in a newly added management frame or control frame and sends the message to the STA.
  • Another optional implementation manner in which the AP sends a multicast ID change message to the STA includes: the AP adds an IE to the existing management frame or the control frame or the data frame, and encapsulates the multicast ID change message in the newly added IE. Send to the corresponding STA.
  • the AID is used as the multicast ID of the multicast group, and the AP sends the multicast ID of the multicast group where the STA is located to the STA, so that the STA can learn the multicast of the multicast group.
  • the multicast ID of the group solves the problem that the multicast application is limited due to the limited number of multicast cycles supported by the FSM ID in the prior art by utilizing the rich feature of the AID resource.
  • the AID is used as the multicast ID of the multicast group.
  • the AID as the multicast ID can be specified by the AP, and the STA does not need to negotiate with the AP. It has strong implementation flexibility.
  • the AID as the multicast ID does not require the multicast information transmission period. It supports both the multicast information that is periodically sent and the multicast information that is sent randomly. It can be applied to more applications. Scenes.
  • FIG. 9 is a flowchart of a method for receiving a multicast identifier according to an embodiment of the present invention. As shown in Figure 9, The method of this embodiment includes:
  • Step 801 The STA receives the multicast identifier of the multicast group where the STA is sent by the AP, and the multicast ID of the multicast group where the STA is located is mapped in the AID.
  • Step 802 The STA records the multicast ID of the multicast group where the STA is located.
  • the AP may initiate the multicast ID assignment by using the AP, and the STA may receive the multicast identifier of the multicast group where the STA is sent by the STA. Identification ID.
  • the STA may initiate the allocation of the multicast ID by the STA, and the STA receives the multicast identifier ID of the multicast group where the STA is sent by the STA, where the STA sends the information requesting the multicast ID to the AP, and then receives the AP.
  • the multicast ID of the multicast group in which the STA is sent according to the information requesting the multicast ID.
  • An optional implementation manner in which the STA sends the information requesting the multicast ID to the AP includes: the STA encapsulates the information of the requested multicast ID in a request message and sends the information to the AP.
  • the request message can be a new message.
  • Another optional implementation manner in which the STA sends the information requesting the multicast ID to the AP includes: the STA adds an IE in the existing control frame or the existing management frame or the existing data frame, and encapsulates the information requesting the multicast ID in the STA.
  • the new IE is sent to the AP.
  • An implementation manner of the STA receiving the multicast identifier of the multicast group in which the STA is sent by the AP includes: the STA receives the newly added management frame or the newly added control frame sent by the AP, and the newly added management frame or the newly added control frame includes Multicast ID of the multicast group where the STA is located.
  • Another implementation manner in which the STA receives the multicast identifier ID of the multicast group in which the STA is sent by the STA includes: the STA receives the existing management frame or the existing control frame or the existing data frame sent by the AP, and the existing management frame or the existing management frame
  • the newly added IE in the control frame or the existing data frame includes the multicast ID of the multicast group where the STA is located.
  • the STA receives the multicast identifier of the multicast group where the STA is sent by the AP.
  • the ID is followed by: The STA sends an ACK message to the AP.
  • the AP may also initiate a logout process of the multicast ID. Based on this, the method in this embodiment further includes: receiving, by the STA, a multicast ID cancellation message sent by the AP, where the multicast ID multicast message includes a logout indication indicating that the multicast ID of the multicast group where the STA is located is logged off.
  • the STA may send an ACK message to the AP to notify the AP. A multicast ID logout message has been received.
  • An optional implementation manner of the AP sending the multicast ID deregistration message to the STA includes: the AP uses the newly added management frame or the control frame frame, and encapsulates the multicast ID deregistration message in a newly added management frame or control frame and sends the message to the STA. .
  • the STA receives the newly added management frame or control frame sent by the AP, and obtains the multicast ID logout message from the received new management frame or control frame.
  • the process of deregistering the multicast ID may also be initiated by the STA.
  • the method in this embodiment further includes: when the STA needs to be disassociated from the multicast group in which the UE is located, the STA sends a multicast ID deregistration request to the AP, so that the AP sets the multicast group where the STA is located according to the multicast ID deregistration request.
  • the multicast ID is logged off, thereby unlinking the multicast group.
  • An optional implementation manner in which the STA sends a multicast ID deregistration request to the AP includes: the STA encapsulates the multicast ID deregistration request in the newly added request message and sends the request to the AP by using the newly added request message.
  • Another optional implementation manner in which the STA sends a multicast ID deregistration request to the AP includes: the STA adds an IE in an existing control frame or a management frame or a data frame, and encapsulates the multicast ID deregistration request in a new The IE is sent to the AP.
  • the AP may also initiate a change of the multicast ID.
  • the method of this embodiment further includes: receiving, by the STA, a multicast ID change message sent by the AP, where the multicast ID change message includes the changed multicast ID of the multicast group where the STA is located.
  • the STA learns that the multicast ID needs to be changed according to the multicast ID change message, and determines the changed multicast ID, and then updates the group of the STA according to the changed multicast ID of the multicast group in which the STA includes the multicast ID change message.
  • the multicast ID of the broadcast group is a multicast ID change message sent by the AP.
  • the change of the multicast ID may also be initiated by the STA.
  • an embodiment of the STA receiving the multicast ID change message sent by the AP includes: when the STA needs to change the multicast ID, the STA may send a multicast ID change request to the AP, and then receive the AP according to the multicast ID change request. The multicast ID change message sent.
  • An optional implementation manner in which the STA sends a multicast ID change request to the AP includes: the STA uses the request message, and encapsulates the multicast ID change request in the request message and sends the request to the AP.
  • the request message here can also be a new message.
  • Another optional implementation manner in which the STA sends a multicast ID change request to the AP includes: the STA adds an IE in an existing control frame or a management frame or a data frame, and encapsulates the multicast ID change request in a new one. Sent to the AP in IE.
  • the foregoing embodiments provide various implementation manners for the STA to receive the multicast ID, the logout multicast ID, and the change multicast ID of the multicast group in which the STA is located, and implement the management of the multicast ID, which has the advantages of easy implementation. .
  • the AID is used as the multicast ID of the multicast group, and the STA receives the multicast ID of the multicast group where the STA is sent by the AP, and then utilizes the feature rich in the AID resource.
  • the problem that the multicast application is limited due to the limited number of multicast cycles supported by the FSM ID in the prior art is solved.
  • the AID is used as the multicast ID of the multicast group. Compared with the scheme of using the FMS ID in the prior art, the AID of the multicast ID can be specified by the AP, and the STA does not need to negotiate with the AP. Strong implementation flexibility;
  • the AID as the multicast ID does not require the transmission period of the multicast information, and supports both the multicast information that is periodically sent and the multicast information that is randomly sent, and can be applied to more applications. Scenes.
  • FIG. 10 is a schematic block diagram of an access point AP according to an embodiment of the present invention.
  • the access point 900 of FIG. 10 includes at least a processor 901, a memory 902, and a transmitting circuit 905.
  • the processor 901, the memory 902, and the receiving circuit 903 are connected by a bus system 904.
  • the access point 900 may further include a receiving circuit 903 and an antenna 906.
  • the processor 901 controls the access point 900.
  • the processor 901 may also be referred to as a central processing unit (CPU).
  • Memory 902 can include read only memory and random access memory and provides instructions and data to processor 901.
  • a portion of memory 902 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • receive circuitry 903 and transmit circuitry 905 can be coupled to antenna 906.
  • the various components of access point 900 are coupled together by a bus system 904, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like. However, for clarity of description, various buses are labeled as bus system 904 in the figure.
  • the method disclosed in the foregoing embodiment of the present invention may be applied to the processor 901 or by the processor.
  • the processor 901 is implemented with various functional circuits or devices.
  • the processor 901 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 901 or an instruction in a form of software.
  • the processor 901 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or a transistor logic device, Discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logic blocks of the disclosure of the embodiments of the invention may be implemented or controlled.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 902, and the processor 901 reads the information in the memory 902 and completes the steps of the above method in combination with the hardware thereof.
  • the processor 901 is configured to generate a multicast group association identifier MID and a transmission transmission indication map DTIM beacon frame.
  • the transmitting circuit 905 sends the multicast group association identifier MID, the transmission transmission indication map DTIM beacon frame, and the multicast information of the multicast group through the antenna;
  • One of the multicast groups has one or more MIDs, and each of the MIDs corresponds to a multicast group and a receiving period of STAs in the multicast group; the DTIM beacon frame includes the MID, and is used to indicate that there is a multicast.
  • the MID indicates that the multicast information is sent to the STA by the multicast group to wake up the STA to receive the multicast information.
  • the further receiving circuit 903 is configured to receive, by using the antenna, an information frame of the request MID sent by the STA; and the processor generates the multicast group associated identifier MID according to the information frame of the request MID.
  • the information of the request MID includes a MID request and an MID request information unit, where the MID request is used to indicate that the information frame is used for the MID request, and the MID request information unit includes: the MAC of the multicast group Address: the processor 905 assigns the MID to the MAC address of the multicast group.
  • the processor 905 carries the information in the MID request information unit through the AID request information unit of the STA.
  • the MID includes an MID reply information and an MID reply information unit, where the MID reply information indicates that the information frame is an MID reply frame, and the reply information unit carries the MID information of the multicast group to which the STA belongs, and further responds to the information unit carrying the information.
  • the MAC address of the multicast group the length of the period during which multicast information is allowed to be received, and when the MID is valid.
  • the information of the MID reply information unit of the processor 905 is carried by the reply information unit of the associated identifier of the AP.
  • FIG. 11 is a schematic block diagram of an access point AP according to another embodiment of the present invention.
  • the access point 1000 of Figure 11 includes at least a processor 1001, a memory 1002, and a transmit circuit 1005.
  • the processor 1001, the memory 1002, and the receiving circuit 1003 are connected by a bus system 1004.
  • the access point 1000 may further include a receiving circuit 1003, an antenna 1006, and the like.
  • the processor 1001 controls the access point 1000.
  • the processor 1001 may also be referred to as a central processing unit (CPU).
  • Memory 1002 can include read only memory and random access memory and provides instructions and data to processor 1001.
  • a portion of memory 1002 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • receiving circuit 1003 and transmitting circuit 1005 can be coupled to antenna 1006.
  • the various components of the access point 1000 are coupled together by a bus system 1004, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like. However, for clarity of description, various buses are labeled as bus system 1004 in the figure.
  • the method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1001 or implemented by the processor 1001 in conjunction with various functional circuits or devices.
  • the processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1001 or an instruction in a form of software.
  • the processor 1001 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logic blocks of the disclosure of the embodiments of the invention may be implemented or controlled.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1002.
  • the processor 1001 reads the information in the memory 1002 and combines the hardware to complete the steps of the above method.
  • the access point is implemented by the processor 1001, and the processor 1001 is configured to generate a multicast group MID and a DTIM beacon frame.
  • the transmitting circuit 1005 is configured to send the multicast group association identifier MID and the antenna through the antenna 1006. Transmitting a transmission indication mapping a DTIM beacon frame and multicast information of a multicast group; wherein each of the MIDs corresponds to a multicast group and a receiving period of STAs in the multicast group; and a partial virtual bit of the DTIM beacon frame
  • the figure includes MID indication information for one or more pages, and different MIDs corresponding to the same multicast group are included in different pages, and the different MIDs correspond to the same receiving period of STAs in the multicast group;
  • the multicast information carries the MID information or information associated with the MID, and the multicast information is received by the STA.
  • the receiving circuit 1003 is configured to receive, by using the antenna, an information frame of the request MID sent by the STA, where the processor
  • the information of the request MID includes a MID request and a MID request information element, where
  • the MID request is used to indicate that the information frame is used for the MID request, and the MID request information unit includes: a MAC address of the multicast group, and the processor 1001 assigns the MID to the MAC address of the multicast group.
  • the processor 905 carries the information in the MID request information element by the AID request information element of the STA.
  • the MID includes an MID reply information and an MID reply information unit, where the MID reply information indicates that the information frame is an MID reply frame, and the reply information unit carries the MID information of the multicast group to which the STA belongs, and further responds to the information unit carrying the information.
  • the information of the MID reply information unit of the processor 905 is carried by the reply information unit of the associated identifier of the AP.
  • the access point AP of the embodiment of the present invention can implement the steps or functions of the foregoing method embodiments.
  • the access point AP completes the multicast information sending method according to the specific process of the foregoing method embodiment. Therefore, the method in the above method embodiment can be completely implemented by an access point.
  • FIG. 12 is a schematic block diagram of a point STA in accordance with an embodiment of the present invention.
  • the site 1200 of FIG. 12 includes at least a processor 1201, a memory 1202, and a transmitting circuit 1205.
  • the processor 1201, the memory 1202, and the receiving circuit 1203 are connected by a bus system 1204.
  • the station 1200 may further include a receiving circuit 1203, an antenna 1206, and the like.
  • the processor 1001 controls the access point 1200.
  • the processor 1201 may also be referred to as a central processing unit (CPU).
  • Memory 1202 can include read only memory and random access memory and provides instructions and data to processor 1201.
  • a portion of the memory 1202 may also include a non- Volatile Random Access Memory (NVRAM).
  • receive circuitry 1203 and transmit circuitry 1205 can be coupled to antenna 1206.
  • the various components of the access point 1200 are coupled together by a bus system 1204, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like. However, for clarity of description, various buses are labeled as bus system 1204 in the figure.
  • the method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1201 or implemented by the processor 1201 in conjunction with various functional circuits or devices.
  • the processor 1201 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1201 or an instruction in a form of software.
  • the processor 1201 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware. Component.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logic blocks of the disclosure of the embodiments of the invention may be implemented or controlled.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 1202.
  • the processor 1201 reads the information in the memory 1202 and completes the steps of the above method in combination with hardware.
  • the station includes: a receiving circuit 1203, configured to receive, by using an antenna, a multicast group association identifier MID sent by an AP, a transmission indication indication mapping DTIM, and multicast information of a multicast group; wherein one multicast group has one or more The MID, each of the MIDs corresponds to a multicast group and a receiving period of the STAs in the multicast group, and the DTIM beacon frame includes the MID, and is used to indicate a group that has multicast information sent to the STA.
  • the processor 1021 is configured to wake up the STA according to the MID and the DTIM, so that the receiving circuit receives the multicast information of the multicast group.
  • the STA further comprising: a transmitting circuit 1025, configured to send, by using an antenna, an information frame that sends a request MID, where the request MID The information frame is used by the AP to generate the MID.
  • the site includes:
  • the receiving circuit receives, by the antenna, the multicast group association identifier MID sent by the AP, the transmission transmission indication mapping DTIM, and the multicast information of the multicast group;
  • Each of the MIDs corresponds to a multicast group and a receiving period of STAs in the multicast group;
  • the partial virtual bitmap of the DTIM beacon frame includes MID indication information for one or more pages, on different pages. Having different MIDs corresponding to the same multicast group, the different MIDs corresponding to the same receiving period of the STAs in the multicast group, and a processor, configured to, according to the MID and the DTIM, the receiving circuit to receive the Multicast information of a multicast group.
  • the manner in which the STA receives the MID and the DTIM in this embodiment is different from the previous implementation.
  • the multicast identity sending and receiving method and the device provided by the embodiment of the present invention use the MID as the multicast ID of the multicast group, and the AP sends the multicast MID of the multicast group where the STA is located to the STA, which solves the problem to a certain extent.

Landscapes

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

Abstract

本发明实施例提供一种组播信息传输方法及设备。接入点AP向站点STA发送组播组关联标示符MID,其中一个组播组具有一个或多个MID,每一个所述MID对应一个组播组及该组播组中STA的接收周期;所述AP向所述STA发送一发送传输指示映射DTIM信标帧,所述DTIM信标帧包含所述MID,用于指示有组播信息向所述STA发送的组播组;所述AP发送所述组播组的组播信息,所述组播信息携带有所述MID或关联所述MID的信息,所述组播信息由所述STA接收。本发明技术方案减轻了STA的资源浪费。

Description

组播信息传输方法及设备 技术领域
本发明涉及通信技术, 尤其涉及一种组播信息传输方法及设备。 背景技术
在 802.11ah的应用场景中最多能够支持 6000个传感器站点( Station, 筒 称为 STA )。 例如, 这些 STA可以分别设置在水表、 电表、 煤气表上, 而这 些水、 电、 煤气表可以隶属于不同或者相同的水、 电、 煤气零售公司, 这些 不同或相同的水、 电、煤气零售公司可以通过无线接入访问点( Access Point , 筒称为 AP ) , 以相同或者不同的周期分别发送信息给这些水、 电、 煤气表, 或者根据需要随时对这些水、 电、 煤气表进行更新。 以上应用场景说明, 在 802.11ah场景中, 各 AP有发送不同周期、 不同内容的组播信息给不同 STA 的需求。
现有技术中, STA最初工作在普通模式下, 在普通工作模式下, STA接 收每个包含发送传输指示映射( Delivery Traffic Indication Map,筒称为 DTIM ) 的信标帧(英文为 Beacon ) ,所述 DTIM用于指示当前有组播信息需要发送。 为了减少 STA 对信标帧的侦听次数, 提出一种灵活组播服务 ( Flexible Multicast Service, 筒称为 FMS )模式。 在 FMS模式下, STA预先与 AP协 商确定使用的组播周期, STA根据协商确定的组播周期来接收组播信息, 而 AP在信标帧中使用长度为 8比特的 FMS ID来标识即将发送的组播信息属于 哪个组播周期, 这种方式虽然减少了 STA侦听信标帧的次数, 但是, 一旦 STA接收信标帧, 同样需要接收该信标帧之后所有组播信息, 然后再从中筛 选出属于自己的组播信息。 由此可见, 无论 STA工作在哪种模式下, STA都 存在资源浪费的问题。 发明内容
本发明实施例提供一种组播信息传输方法及设备, 用以减轻 STA的资源 浪费。
本发明实施例的第一个方面提供一种组播信息发送方法, 包括: 接入点 AP向站点 STA发送组播组关联标示符 MID,其中一个组播组具有 一个或多个 MID,每一个所述 MID对应一个组播组及该组播组中 STA的接收 周期;
所述 AP向所述 STA发送一发送传输指示映射 DTIM信标帧,所述 DTIM 信标帧包含所述 MID,用于指示有组播信息向所述 STA发送的组播组;
所述 AP发送所述组播组的组播信息,所述组播信息携带有所述 MID或关 联所述 MID的信息, 所述组播信息由所述 STA接收。
作为一种具体的实施方式, 所述 AP向 STA发送组播组的 MID之前包括: 接收所述 STA发送的请求 MID的信息帧, 则所述向站点 STA发送组播 组的 MID包括:根据接收到的请求 MID的信息帧, 向该 STA发送该 STA所 在组播组的 MID。
进一步,作为一个实施例所述请求 MID的信息帧包括 MID请求则 AP向 站点 STA发送组播组的 MID之前所述 AP根据所述 MID请求信息单元生成 所述向 STA发送组播组的 MID。
本发明实施例的第二个方面,提供另一种组播信息发送方法,该方法包括: AP向站点 STA发送组播组的 MID,每一个所述 MID对应一个组播组及 该组播组中 STA的接收周期;
所述 AP向所述 STA发送 DTIM信标帧,所述 DTIM信标帧的部分虚拟位 图中包含对一个或多个页的 MID 指示信息,在不同的页中包含对应同一所述 组播组的不同 MID,所述不同的 MID对应所述组播组中 STA的同一接收周期; 所述 AP发送所述组播组的组播信息,所述组播信息携带有所述 MID信息 或关联所述 MID的信息, 所述组播信息由所述 STA接收。
作为第二方面一种具体的实现方式,所述 AP向站点 STA发送组播组的 MID之前包括:接收所述 STA发送的请求 MID的信息帧,则所述向站点 STA 发送组播组的 MID包括:根据接收到的请求 MID的信息帧,向该 STA发送该 STA所在组播组的 MID。 进一步,具体的一个例子中所述请求 MID的信息帧包括 MID请求信息单 元;则 AP向站点 STA发送组播组的 MID之前所述 AP根据所述 MID请求信 息单元生成所述向 STA发送组播组的 MID。
进一步本发明实施例还给出了实现上述方法的接入点的实施例,所述接 入点包括:
处理器, 用于生成组播组关联标示符 MID和发送传输指示映射 DTIM信 标帧;
发射电路, 用于通过天线发送所述组播组关联标示符 MID、 所述发送传 输指示映射 DTIM信标帧和组播组的组播信息;
其中一个组播组具有一个或多个 MID,每一个所述 MID对应一个组播组 及该组播组中 STA的接收周期; 所述 DTIM信标帧用于指示有组播信息向所 述 STA发送的组播组; 所述组播信息携带有所述 MID或关联所述 MID的信 息, 所述组播信息由所述 STA接收。
一种接收组播组信息的方法,其特征在与, 所述方法包括: 站点 STA接收接入点 AP发送的组播组关联标示符 MID,其中一个组播组 具有一个或多个 MID,每一个所述 MID 对应一个组播组及该组播组中所述 STA的接收周期; 所述 STA接收所述 AP发送的一发送传输指示映射 DTIM信标帧,所述 DTIM信标帧包含所述 MID,用于指示有组播信息向所述 STA发送的组播组; 所述 STA接收所述 AP发送的所述组播组的组播信息,其中所述组播信息 携带有所述 MID或关联所述 MID的信息。
再一种接收组播组信息的方法, 其特征在于, 包括: 站点 STA接收 AP发送的组播组 MID,每一个所述 MID对应一个组播组 及该组播组中 STA的接收周期;
所述 STA接收所述 AP发送的 DTIM信标帧,所述 DTIM信标帧的部分虚 拟位图中包含对一个或多个页的 MID 指示信息,在不同的页中包含对应同一 所述组播组的不同 MID,所述不同的 MID对应所述组播组中 STA的同一接收 周期;
所述 STA在唤醒时接收所述 AP发送的所述组播组的组播信息,所述组播 信息携带有所述 MID信息或关联所述 MID的信息,所述组播信息由所述 STA 接收。
本发明实施例还有另外一种的接入点,该接入点包括:
处理器,用于生成组播组的 MID和 DTIM信标帧; 发射电路,用于通过天线发送所述组播组关联标示符 MID、所述发送传输 指示映射 DTIM信标帧和组播组的组播信息;其中每一个所述 MID对应一个 组播组及该组播组中 STA的接收周期; 所述 DTIM信标帧的部分虚拟位图中 包含对一个或多个页的 MID 指示信息,在不同的页中包含对应同一所述组播 组的不同 MID,所述不同的 MID对应所述组播组中 STA的同一接收周期; 所 述组播信息携带有所述 MID信息或关联所述 MID的信息, 所述组播信息由 所述 STA接收。 进一步本发明实施例还有一种 STA,包括:
接收电路,通过天线接收 AP发送的组播组关联标示符 MID、 发送传输指 示映射 DTIM和组播组的组播信息; 其中一个组播组具有一个或多个 MID,每 一个所述 MID 对应一个组播组及该组播组中所述 STA 的接收周期, 所述 DTIM信标帧包含所述 MID,用于指示有组播信息向所述 STA发送的组播组; 处理器, 用于根据所述 MID和 DTIM使得所述接收电路接收所述组播组 的组播信息。
已经另一站点 STA,包括: 接收电路,通过天线接收 AP发送的组播组关联标示符 MID、 发送传输指 示映射 DTIM和组播组的组播信息;
其中每一个所述 MID对应一个组播组及该组播组中 STA的接收周期;所 述 DTIM信标帧的部分虚拟位图中包含对一个或多个页的 MID指示信息,在 不同的页中包含对应同一所述组播组的不同 MID,所述不同的 MID对应所述 组播组中 STA的同一接收周期; 处理器, 用于根据所述 MID和 DTIM使得所述接收电路接收所述组播组 的组播信息。
本发明实施例提供的组播信息发送、 接收方法及设备, 通过用 DTIM信 标帧指示有组播信息发送的组播组, AP按照有组播信息发送的组播组的组播 ID的大小顺序, 依次在发送间隔发送有组播信息发送的组播组的组播信息, 而 STA根据自己所在组播组的组播 ID在有组播信息发送的组播组的组播 ID 中的大小顺序, 在对应的接收间隔接收自己所在组播组的组播信息, 解决了 现有技术中各 STA接收信标帧之后所有组播信息的问题, 减轻了因此造成的 STA的资源浪费。
本发明实施例提供的组播标识发送、 接收方法及设备, 通过使用 AID作 为组播组的组播 MID, AP将 STA所在组播组的组播 MID发送给 STA,—定 程度上解决了现有技术中因 FSM ID所支持的组播周期数有限造成组播应用 受限的问题。 附图说明
图 1为本发明一实施例提供的组播信息发送方法的流程图;
图 2为本发明另一实施例提供的组播信息发送方法的流程图;
图 2b为本发明又一实施例提供的组播信息发送方法的流程图; 图 2c为本发明再一实施例提供的组播信息发送方法的流程图; 图 3为本发明一实施例提供的 AID的结构示意图;
图 4为本发明一实施例提供的组播信息接收方法的流程图;
图 5为本发明一实施例提供的一种接收组播信息顺序的示意图; 图 6为本发明一实施例提供的另一种接收组播信息顺序的示意图; 图 7为本发明另一实施例提供的组播信息接收方法的流程图;
图 8为本发明一实施例提供的组播标识发送方法的流程图;
图 9为本发明一实施例提供的组播标识接收方法的流程图;
图 10是本发明一实施例的接入点 AP的示意框图;
图 11是本发明另一实施例的接入点 AP的示意框图。
图 12是本发明一实施例的站点 STA的示意框图
具体实施方式 为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本发 明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于 本发明中的实施例, 本领域普通技术人员在没有作出创造性劳动前提下所获 得的所有其他实施例, 都属于本发明保护的范围。
图 1为本发明一实施例提供的组播信息发送方法的流程图。 本实施例的 执行主体为 AP, 但不限于此。 如图 1所示, 本实施例的方法包括:
步骤 101、 向 STA发送 DTIM信标帧, 该 DTIM信标帧用于指示有组播 信息发送的组播组。
步骤 102、 在每个预设发送间隔内发送上述有组播信息发送的组播组的 组播信息, 以使 STA在 STA所在组播组对应的接收间隔接收 STA所在组播 组的组播信息。
本发明各实施例中按照有组播信息发送的组播组的组播标识( Identifier , 筒称为 ID )的大小顺序, 依次在每个预设发送间隔内发送上述有组播信息发 送的组播组的组播信息,组播 ID 的大小顺序可以是从大到小的顺序, 也可以 是从小到大的顺序。 其中, AP发送时依据的组播 ID的大小顺序与 STA接收 时依据的组播 ID的大小顺序相同,要么都按照从大到小的顺序,要么都按照 从小到大的顺序。
在本实施例中, 每个组播组都有一个组播 ID, 用于唯一标识该组播组。 这些组播 ID是用于标识组播组的关联标示符 AID, 被称为 MID ( Multicast AID ) 。 AP上存储有每个有组播信息要发送的组播组的组播信息。 当 AP需 要向至少一个组播组中的 STA发送组播信息时, 首先向 STA发送信标帧, 在该信标帧中的类型指示位指示该信标帧为 DTIM信标帧, 该 DTIM信标帧 一方面指示该 DTIM信标帧之后将发送组播信息, 另一方面指示有组播信息 发送的组播组。 然后, AP按照有组播信息发送的组播组的 MID的大小顺序, 依次在各个发送间隔发送这些组播组的组播信息, 这样就可以使 STA根据自 己所在组播组的 MID在对应的接收间隔内接收自己所在组播组的组播信息, 而不接收其他组播组的组播信息,解决了现有技术中 STA在接收信标帧之后, 需要接收该信标帧后所有组播信息的问题,有利于减轻因此造成的 STA的资 源浪费, 尤其适用于有低能耗需求的 STA。
在上述事实例中步骤 101之前还可以包括向 STA发送 STA所在组播组 的组播 ID。
AP根据各有组播信息发送的组播组的组播 ID的大小顺序,向 STA发送 上述组播组的组播信息之前,可以将 STA所在组播组的组播 ID发送给 STA, 以使 STA预先获知自己自所在组播组的组播 ID,然后根据自己所在组播组的 组播 ID 在对应的接收间隔内接收自己所在组播组的组播信息。 其中, STA 会将接收到的自己所在组播组的组播 ID存储在本地。
进一步, 在一可选实施方式中, 标识一个组播组的 MID不是唯一的, 实 践中可以允许多个 MID标识同一个组播组。 因此, 本发明又一实施例提供的 组播信息发送的又一种方法, 参阅图 2b为方法的流程图。 本实施例的执行主 体为 AP, 但不限于此。 如图 2b所示, 本实施例的方法包括:
S2201 , 接入点 AP向站点 STA发送组播组关联标示符 MID,其中一个组 播组具有一个或多个 MID,每一个所述 MID 对应一个组播组及该组播组中 STA的接收周期;
S2203 , 所述 AP向所述 STA发送一发送传输指示映射 DTIM信标帧, 所述 DTIM信标帧包含所述 MID,用于指示有组播信息向所述 STA发送的组 播组;
S2205 , 所述 AP发送所述组播组的组播信息,所述组播信息携带有所述 MID或关联所述 MID的信息, 所述组播信息由所述 STA接收
在上述的的实施例中,对应于同一个组播组的不同 MID对应于不同的接 收组播信息的周期,关联所述 MID 的信息可以是组播组的 MAC地址。 在有 STA休眠的模式下, 及唤醒所述 STA接收所述组播信息 MID指示有组播信 息向所述 STA发送的组播组以唤醒所述 STA接收所述组播信息。 接入点 AP 可以向全部或者部分站点 STA发送组播组关联标示符 MID,根据系统需求.具 体实施中, 同属于一个组播组的 STA有可能需要以不同的周期唤醒接收组播 信息。 接收组播信息的周期也可以称为组播信息收听间隔 (multicast listen interval)。 使用不同的 MID来标识同一组播组中不同接收周期的 STA, 可以 实现灵活的提供周期不同的相同组播信息的发送。 举例说明如下: STA— 1与 STA 2都属于组播组 A, 但是 STA— 1与 STA— 2需要接收组播信息的周期不 同。 STA— 1可以在每个 DTIM唤醒接收组播信息, 而 STA— 2则每 2个 DTIM 唤醒接收一次。 因此分配 MID— 1给 STA— 1 , MID— 2给 STA— 2。 当 STA— 1接 收到 DTIM发现有 MID— 1的数据包时, 则接收该数据包。 而 STA— 2在接收 到 DTIM中标识 MID— 2有数据时接收数据。 其中 MID— 1和 MID— 2都对应于 组播组 A。 在一可选实施方式中, 预设发送间隔可以是组播信息的平均发送时长。 基于此, AP在向 STA发送 DTIM信标帧之后, 按照有组播信息发送的组播 组的 MID的大小顺序,顺序为每个有组播信息发送的组播组分配一段长度为 组播信息的平均发送时长的时间作为其发送间隔, 在所分配的发送间隔内发 送对应组播组的组播信息,做到按照组播 ID的大小顺序依序发送组播组的组 播信息。
可选的, 组播信息的发送平均时长可以是预先设定的经验值。 另外, 组 播信息的发送平均时长也可以是 AP在确定出有组播信息要发送的组播组后, 在发送组播信息之前, 根据每个组播组要发送的组播信息的大小以及发送速 率计算出的。
在一可选实施方式中, 上述发送间隔可以是信标帧间隔(英文为 Beacon Interval ) , 这里的信标帧间隔是指两个信标帧之间的间隔。 这里的信标帧包 括指示位为传输指示映射 ( Traffic Indication Map, 筒称为 TIM )的 TIM信标 帧, 也包括 DTIM信标帧。 在该实施方式中, AP在当前 DTIM信标帧之后下 一个 DTIM信标帧之前可以发送 TIM信标帧, 则 AP在当前 DTIM信标帧之 后发送组播组的组播信息具体可以为: AP 在当前 DTIM 信标帧以及当前 DTIM信标帧与下一个 DTIM信标帧之间的 TIM信标帧之后发送组播组的组 播信息, 或在当前 DTIM信标帧的信标帧间隔内发送信息。
AP可以在 DTIM信标帧中指示出在下一个 DTIM信标帧之前全部的需要 接收组播信息的 MID。 现有 DTIM信标帧中的部分虚拟位图(Partial Virtual Bitmap)只是指示出有单播数据的 STA, 当使用 MID标识组播组后, DTIM信 标帧中的部分虚拟位图也可以用来指示有组播信息的组播组。另外, 当 DTIM 中包含指示有单播信息的 STA所属的页, 块, 子块的信息时, 在启用 MID 标识组播组后, DTIM 中也可以使用这些信息来指示有组播信息的组播组所 在的页, 块和子块。 进一步在 TIM 中如何使用页、 块、 子块可以参阅 IEEE 802.11 ah的标准提案 Specification Framework for TGah。 AP在两个 DTIM信 标帧之间发送的 TIM信标帧的个数可以适应性确定。如果两个 DTIM信标帧 之间的 TIM信标帧的个数大于或等于有组播信息发送的组播组的个数, 优选 的, AP可以在每个 TIM信标帧之后发送一个组播组的组播信息, 但不限于 此。如果两个 DTIM信标帧之间的 TIM信标帧的个数小于有组播信息发送的 组播组的个数, 则 AP可以在其中某个 TIM信标帧或当前 DTIM信标帧之后 同时发送至少两个组播组的组播信息, 以保证每个组播组的组播信息都能成 功发送给 STA。
具体的实施中,在 S2201中, AP根据各有组播信息发送的组播组的 MID 的大小顺序, 向 STA发送上述组播组的组播信息之前, 可以将 STA所在组 播组的 MID发送给 STA, 以使 STA预先获知自己自所在组播组的 MID , 然 后根据自己所在组播组的 MID在对应的接收间隔内接收自己所在组播组的组 播信息。 其中, STA会将接收到的自己所在组播组的 MID存储在本地。
在一可选实施方式中, AP 可以主动发起组播 ID的分配, 即 AP主动向 STA发送该 STA所在组播组的组播 MID。
在另一可选实施方式中, STA可以主动向 AP请求其所在组播组的 MID。 则步骤 101的一种实施方式包括: AP接收 STA发送的请求 MID的信息, AP 根据接收到的请求 MID的信息, 向该 STA发送该 STA所在组播组的 MID。 其中, STA发送的请求 MID的信息可以是组播介质访问控制 (Media Access Control, 筒称为 MAC )地址或者其他能够唯一标识该 STA所属组播组的信 息。 AP根据 STA发送的请求 MID的信息识别该 STA所在的组播组, 然后 确定该 STA所在组播组的 MID。可选的, AP可以在接收到请求组播 ID的信 息后, 实时为该 STA分配 MID , 也可以直接获取预先分配好的组播 ID。
在该实施方式中, STA向 AP发送请求 MID的信息的一种具体实施方式 为: STA将上述请求 MID的信息封装在请求消息中发送给 AP。 对于 AP来 说, 接收 STA发送的请求 MID的信息的具体方式为: AP接收 STA发送的 请求消息, 该请求消息包括所述请求组播 ID的信息, AP具体从该请求消息 中获取所述请求组播 ID的信息。可选的,该请求消息可以是一个新增的消息。 一种具体的新增请求消息可以是被称为 MID Request ( MID请求) 的请求消 息。 参阅如下的具体实施例, 信息帧 1,所示: 信息帧 1 版本信息 MID请求 MID Request IE 在 MID Request中可以少包含: 版本信息、 MID请求( MID Request )以 及 MID Request IE ( Information Element, 筒称为 IE ) 。 其中版本信息用于 表明该消息隶属于某一个标准的版本信息, 为非必需的信息域。 MID请求用 于表明该信息是 MID Request 的信息, 为一个请求 MID 的信息帧。 MID Request IE ( MID请求信息单元 )携带具体的请求的信息。其中 MID Request IE如下实施例, 信息帧 2 , 所示: 信息帧 2
Element Element 组播 MAC地址 1 组播 MAC地址 2
组播 MAC地址 1 组播 MAC地址 2
ID 长度 期望接收周期 期望接收周期
MID请求信息单元可以包含该 IE的 ID、 该 IE的长度、 希望获得 MID 的组播组的 MAC 地址、 希望接收该组播组数据的周期 (multicast listen interval ) 。 其中希望获得 MID的组播组的 MAC地址、 希望接收该组播组数 据的周期可以允许有多个。 也就是说, 允许一个 STA在一个请求消息中请求 多个组播组的 MID。 在具体的实施中, 所述组播组的 MAC地址是必须的, AP根据所述组播组的 MAC地址分配所述 MID, 其他的信息域为可选。
在该实施方式中, STA向 AP发送请求组播 ID的信息的另一种具体实施 方式为: STA在已有控制帧或已有管理帧或已有数据帧中新增信元单元( IE ), 将所述请求 MID的信息封装在新增的 IE中发送给 AP。 一种具体的新增 IE 是 MID Request IE或者将 MID Request IE 中所携带信息包含在已有 AID Request IE中。另一种具体方法,将新增 IE置于已有消息帧中,具体可以是将新 增 IE 置于关联请求 ( Association Request ) 或重关联请求 ( Reassociation Request )或 AID转换请求 ( AID Switch Request ) 中。 对于 AP来说, 接收 STA发送的请求 MID的信息的具体方式为: AP接收 STA发送的已有控制帧 或已有管理帧或已有数据帧, 该已有控制帧或已有管理帧或已有数据帧中新 增的 IE中包括所述请求组播 ID的信息, AP从已有控制帧或已有管理帧或已 有数据帧中新增的 IE中获取所述请求 MID的信息。
在一可选实施方式中, AP向 STA发送 STA所在组播组的组播 ID的一 种具体实施方式为: AP将 STA所在组播组的组播 ID封装在新增的管理帧或 新增的控制帧中发送给该 STA。 一种具体的新增消息帧可以是被称为 MID Response ( MID回复)的消息帧, 该帧为接入点 AP向站点 STA发送组播组 的 MID,在本实施例中 MID信息帧可以看作是 MID Response,因为是在 STA 请求后发送 MID。 参阅如下的具体实施例, 一种 MID信息帧, 信息帧 3: 信息帧 3
MID Response
版本信息 MID回复
IE 在 MID Response 中可以包含的字段有: 版本信息、 MID 回复及 MID Response IE。 其中版本信息用于表示该消息隶属于某一个标准的版本信息, 该部分位非必需, 例如可以通过缺省或者系统设置的方式预先协商。 MID回 复用于表示该信息是 MID Response的信息帧。
参阅如下, MID Response IE的一种具体实施例, 信息帧 4: 信息帧 4
Figure imgf000012_0001
MID Response IE可以包含的信息:该 IE的 ID、 该 IE的长度、 组播 MAC 地址、 对应于所分配的 MID、 允许接收组播信息的周期长度(multicast listen interval ) 、 MID生效时间、 状态信息。 如果 STA请求多个组播组的 MID, 该 IE中的组播 MAC地址、 对应于所分配的 MID、 允许接收组播信息的周期 长度 ( multicast listen interval ) 、 MID生效时间、 状态信息部分可以有多个。 应用中所述 MID请求信息单元包括:所述组播组的 MAC地址或所述 STA接 收该组播组组播信息的周期是必须的, 因为 AP根据组播组的 MAC地址或 STA接收该组播组组播信息的周期分配 MID。 在实施中, 对应于相应的组播 MAC地址分配的 MID可以是一个或多个 MID, 也可以是由一个页指示位图再结合 MID组成的。 其中页指示位图标识 当前 MID所要分配到的一个或者多个页。 这里的页对应于 TIM结构中的页。 AP可以根据 STA所要接收组播信息的周期, 将分散在多个页中的 MID分配 给它,从而配合在一个 DITM中部分虚拟位图只指示一个页中 STA接收数据 的情况, 以满足 STA以不同的周期接收组播信息的需要。
参阅图 2c本发明实施例再一种组播信息发送方法,包括
S2301, AP向站点 STA发送组播组的 MID,每一个所述 MID对应一个组 播组及该组播组中 STA的接收周期;
S2303, 所述 AP向所述 STA发送 DTIM信标帧,所述 DTIM信标帧的部 分虚拟位图中包含对一个或多个页的 MID 指示信息,在不同的页中包含对应 同一所述组播组的不同 MID,所述不同的 MID对应所述组播组中 STA的同一 接收周期;
S2305, 所述 AP发送所述组播组的组播信息,所述组播信息携带有所述 MID信息或关联所述 MID的信息, 所述组播信息由所述 STA接收。
举例说明如下: 当 DTIM中部分虚拟位图只指示一个页并且全部 4个页 的循环是根据 1 , 2 , 3 , 4的顺序循环的时候,如果 STA— 1需要接收每个 DTIM, 而 STA— 2需要每隔一个 DTIM周期接收一次,则给 STA— 1需要分配 4个 MID , 该 4个 MID分别映射在 4个页中的,保证它在每个 DTIM都可以获知是否有 数据接收。 给 STA— 2只要分配 2个 MID , 这 2个 MID分别映射在页 1和 3 中, 则可以保证 STA— 2能够在希望的接收周期接收组播信息。 MID映射的页 可以才艮据 DTIM中 TIM位图指示页的循环出现的顺序不同而不同。 为了减少 IE的长度,可以将对应于同一周期同一组播组的 MID映射到不同页的相同块 和子块中。 在 MID分配时, 只需要用页指示位图指示当前 MID所要映射到 一个或多个页中, 另外可以使用部分 MID指示出映射的块和子块的位置。 进 一步说明, MID生效时间是指所指定的 MID是立即生效或在一段时间后生 效, 其中一段时间可以是若干个 Beacon Interval (信标间隔) , 或者若干个 包含 TIM的 Beacon后,或者若干个包含 DITM的 Beacon。当 AP成功为 STA 分配了 MID后, 其状态信息应标识出成功。 如果不成功, 状态信息应标识出 不成功还进一步可以标识出相应的错误原因。
在一可选实施方式中, AP向 STA分配 STA所在组播组的 MID的另一 种具体实施方式为: AP在已有管理帧或已有控制帧或已有数据帧中新增 IE, 将 STA所在组播组的组播 ID封装在所述新增的 IE中发送给该 STA。一种具 体的新增 IE是 MID Response IE或者将 MID Response IE中的信息包含在现 有 AID Response IE中。 另一种具体的将新增 IE包含到已有消息帧中的方法 是在关联回复 ( Association Response ) 和或重关联回复 ( Reassociation Response )中和或 AID转换请求回复( AID Switch Response )中加入新增 IE。
在一可选实施方式中, STA接收到 AP发送的其所在组播组的组播 ID后, 可以向 AP发送确认( ACK ) 消息, 以便于 AP能够及时获知 STA是否成功 接收到 STA所在组播组的组播 ID。 基于此, AP向 STA发送 STA所在组播 组的组播 ID之后包括: AP接收 STA发送的 ACK消息。可选的,在需要 STA 发送 ACK消息的前提下, 如果 AP在一定时间内未收到 ACK消息, 则需要 重新向 STA发送 STA所在组播组的组播 ID。
在一可选实施方式中, AP还可以发起的组播 ID的注销过程。 基于此, 本实施例的方法还包括: AP向 STA发送组播 ID注销消息, 该组播 ID注销 消息包括指示将 STA所在组播组的组播 ID注销的注销指示。 可选的, 该组 播 ID注销消息还可以包括需要注销的组播 ID (即 STA所在组播组的组播 ID )。 相应的, STA接收 AP发送的组播 ID注销消息, 以获知自己所在组播 组的组播 ID需要注销, 并基于此解除与该组播 ID之间的关联关系。可选的, STA接收到组播 ID注销消息之后, 可以向 AP发送 ACK消息, 以告知 AP 已经接收到组播 ID注销消息。 相应的, AP在向 STA发送组播 ID注销消息 之后, 接收 STA发送的 ACK消息。 在要求发送 ACK消息的前提下, 如果 AP在一定时间内没有收到 ACK消息,则需要重新发送组播 ID注销消息给相 应未收到其 ACK消息的 STA。
AP向 STA发送组播 ID注销消息的一种可选实施方式包括: AP使用新 增的管理帧或新增的控制帧,将组播 ID注销消息封装在新增的管理帧或新增 的控制帧中发送给 STA。
AP向 STA发送组播 ID注销消息的另一种可选实施方式包括: AP在已 有的管理帧或控制帧或数据帧中新增 IE, 将组播 ID注销消息封装在新增的 IE中发送给相应 STA。
在一可选实施方式中, 组播 ID的注销过程还可以由 STA主动发起, 例 如 STA在需要与所在组播组解除关联关系时, 向 AP发送组播 ID注销请求, 以请求解除与该组播组的关联。 基于此, 本实施例的方法还包括: AP接收 STA发送的组播 ID注销请求,可选的该组播 ID注销请求包括 STA所在组播 组的组播 ID, 即需要注销的组播 ID, 然后根据接收到的组播 ID注销请求, 将 STA所在组播组的组播 ID注销。 可选的, AP还可以在接收到组播 ID注 销请求后, 向 SAT发送 ACK消息。
其中, STA向 AP发送组播 ID注销请求的一种可选实施方式包括: STA 使用请求消息, 将组播 ID注销请求封装在请求消息中发送给 AP。 相应的, AP接收 STA发送的组播 ID注销请求的具体实施方式包括: AP接收 STA发 送的请求消息,从请求消息中获取所述组播 ID注销请求。 这里的请求消息也 可以是一新增消息。
其中, STA向 AP发送组播 ID注销请求的另一种可选实施方式包括: STA 在已有的控制帧或管理帧或数据帧中新增 IE, 将所述组播 ID注销请求封装 在新增的 IE中发送给 AP。 相应的, AP接收 STA发送的组播 ID注销请求的 具体实施方式包括: AP接收 STA发送的已有的控制帧或管理帧或数据帧, 从已有的控制帧或管理帧或数据帧中新增的 IE中获取所述组播 ID注销请求。
在一可选实施方式中, AP还可以发起的组播 ID的变更。 基于此, 本实 施例的方法还包括: AP向 STA发送组播 ID变更消息, 该组播 ID变更消息 包括 STA所在组播组的变更后的组播 ID。 可选的, 该组播 ID变更消息还可 以包括 STA所在组播组原来的组播 ID。对一个组播组来说,该组播组原来的 组播 ID是需要变更的组播 ID , 而该组播组使用的新组播 ID是变更后的组播
ID。 STA接收 AP发送的组播 ID变更消息, 以获知需要对组播 ID进行变更 并确定变更后的组播 ID。 可选的, STA在接收到 AP发送的组播 ID变更消 息后, 可以向 AP发送 ACK消息。 在要求发送 ACK消息的前提下, 如果 AP 在一定时间内没有收到 ACK消息, 则需要重新发送组播 ID变更消息给相应 未收到其 ACK消息的 STA。
AP向 STA发送组播 ID变更消息的一种可选实施方式包括: AP使用新 增的管理帧或新增的控制帧,将 MID变更消息封装在新增的管理帧或新增的 控制帧中发送给 STA。一种具体的实施方法是 AP可以使用 MID Response来 完成 MID的变更。
AP向 STA发送组播 ID变更消息的另一种可选实施方式包括: AP在已 有的管理帧或控制帧或数据帧中新增 IE, 将组播 ID变更消息封装在新增的 IE中发送给相应 STA。 一种具体的新增 IE是 MID Response IE或者将 MID Response IE中的信息包含在现有 AID Response IE中。 一种具体的将新增 IE 包含到已有消息帧中的方法是在关联回复 ( Association Response )和或重关 联回复 ( Reassociation Response ) 中和或 AID 转换请求回复 ( AID Switch Response ) 中力口入新增 IE。
在一可选实施方式中,组播 ID的变更还可以由 STA主动发起,例如 STA 在需要进行组播 ID的变更时, 可以向 AP发送组播 ID变更请求, 然后接收 AP根据组播 ID变更请求发送的组播 ID变更消息, 该组播 ID变更消息包括 STA所在组播组的变更后的组播 ID。 基于此, 上述 AP向 STA发送组播 ID 变更消息的一种实施方式包括: AP接收 STA发送的组播 ID变更请求, 根据 组播 ID变更请求, 向 STA发送组播 ID变更消息。 其中, 组播 ID变更请求 可以包括 STA的 MAC地址、 IP地址或其他可以唯一标识该 STA的信息。可 选的, AP可以根据组播 ID变更请求携带的信息, 重新为 STA分配一个组播 ID, 然后将重新分配的组播 ID作为变更后的组播 ID发送给 STA。
STA向 AP发送组播 ID变更请求的一种可选实施方式包括: STA使用新 增的请求消息,将组播 ID变更请求封装在所述新增的请求消息中发送给 AP。 相应的, AP接收 STA发送的组播 ID变更请求的具体实施方式包括: AP接 收 STA发送的新增的请求消息, 从新增的请求消息中获取所述组播 ID变更 请求。一种具体的新增请求消息可以是使用 MID Request来完成 MID的变更。
其中, STA向 AP发送组播 ID变更请求的另一种可选实施方式包括: STA 在已有的控制帧或管理帧或数据帧中新增 IE, 将所述组播 ID变更请求封装 在新增的 IE中发送给 AP。 相应的, AP接收 STA发送的组播 ID变更请求的 具体实施方式包括: AP接收 STA发送的已有的控制帧或管理帧或数据帧, 从已有的控制帧或管理帧或数据帧中新增的 IE中获取所述组播 ID变更请求。 一种具体的新增 m是 MID Request IE或者将 MID Request IE中所包含信息包 含在现有 AID Request IE中。 一种具体的将新增 IE包含到已有消息帧中的方 法是在关联请求 ( Association Request ) 和或重关联请求 ( Reassociation Request )和或 AID转换请求( AID Switch Request ) 中力口入新增 IE。
上述各实施方式给出了 AP向 STA发送组播 ID、 注销组播 ID和变更组 播 ID的多种实施方案, 实现了对组播 ID的管理, 具有筒单易于实现的优势。
基于上述各实施方式, 可选的, 上述各组播组(包括 STA所在组播组) 的组播 ID可以是 MAC地址, 也可以是 FMS ID, 但不限于此。 基于上述各实施方式, 可选的, 上述各组播组(包括 STA所在组播组) 的组播 ID为至少一个关联标识符 (Association ID , 筒称为 AID ) 。 这里的 AID可以是 AID空间中除作为单播 AID之外的 AID。 其中, 具体哪些 AID 作为单播 AID, 哪些 AID作为组播 ID使用可由 AP自行确定。 也就是说, 只 要作为组播 ID的 AID与用于单播的 AID不相同即可。
在组播组的组播 ID为 AID的基础上, AP向 STA发送 STA所在组播组 的组播 ID之前可以包括: AP将 STA所在组播组的组播 ID映射在一个 AID 中; 或者, AP将 STA所在组播组的组播 ID映射在至少两个 AID中。
现有技术中为了支持更多的 STA, STA的 AID依照页 (英文为 Page ) 、 块(英文为 Block )和子块(英文为 Sub-block )被划分为不同的组。 图 3所 示为支持 4个 Page的 AID的结构。 在支持 4个 Page的 AID结构中, 一个 Page里面可以有 32个 Block,而一个 Block有 8个 Sub-block,—个 Sub-block 可以支持 8个 STA。 这样, 这种结构的 AID最多可以支持 8192个 STA。 由 于, AID空间足够多, 在本实施方式中将其中一些 AID用作组播 ID使用, 这样就无需额外设定组播 ID , 这样就不需要因携带设定的组播 ID而增大信 标帧, 有利于信标帧的压缩。
基于上述 AID的实现结构, AP将 STA所在组播组的组播 ID映射在一 个 AID中的一种实施方式为: AP可以将 STA所在组播组的组播 ID映射在 所述 AID中任意 Page、 Block和 /或 Sub-block中。 其中, 多个组播组的组播 ID可以使用同一个 AID,这些组播组的组播 ID可以任意分配在不同的 Page、 Block和 /或 Sub-block中。
基于上述 AID的实现结构, AP将 STA所在组播组的组播 ID映射在一 个 AID中的另一种实施方式为: AP将 STA所在组播组的组播 ID映射在该 AID中预先指定的页、 块和 /或子块中。 同理, 多个组播组的组播 ID也可以 使用同一个 AID , 这些组播组的组播 ID可以分配在预先指定的 Page、 Block 和 /或 Sub-block 中。 这种方式可以实现所有组播组的组播 ID都属于同一个 Page, Block或 Sub-block中, 有利于管理。
基于上述 AID的实现结构, AP将 STA所在组播组的组播 ID映射在至 少两个 AID中的一种具体实施方式包括: AP将 STA所在组播组的组播 ID 映射在至少两个 AID中不同 Page、 Block或 Sub-block中。 其中, 多个组播 组的组播 ID可以使用相同的至少两个 AID , 这些组播组的组播 ID可以分配 在上述至少两个 AID的不同 Page、 Block和 /或 Sub-block中。
基于上述 AID的实现结构, AP将 STA所在组播组的组播 ID映射在至 少两个 AID中的另一种具体实施方式包括: AP将 STA所在组播组的组播 ID 映射在至少两个 AID中相同的 Page、 Block和 /或 Sub-block中。 同理, 多个 组播组的组播 ID可以使用相同的至少两个 AID , 这些组播组的组播 ID可以 分配在上述至少两个 AID的相同 Page、 Block和 /或 Sub-block中。
综上所述, 使用 AID作为组播组的组播 ID的方式包括但不限于: ( 1 )一个 AID对应于一个或者多个组播组的组播 ID, 这个或这些组播 ID可以任意分配在不同的 Page、 Block和 /或 Sub-block中。
( 2 )一个 AID对应于一个或者多个组播组的组播 ID, 所有用于标识组 播组的组播 ID的 AID都使用相同的 Page、 Block和 /或 Sub-block。
( 3 )一个组播 ID可以使用多个 AID来标识,这些 AID可以使用相同的 或者不同的 Page、 Block和 /或 Sub-block。
在此说明, 本发明各实施例中, 用 AID表示的组播 ID可以是连续的也 可以是不连续。
在上述各实施方式中,使用 AID作为组播组的组播 ID, 与现有技术中使 用 FMS ID的方案相比,作为组播 ID的 AID可以由 AP指定, STA不需要与 AP进行协商, 具有较强的实现灵活性; 另外, 作为组播 ID的 AID对组播信 息的发送周期没有要求, 既支持周期性发送的组播信息也支持随机发送的组 播信息,能够适用更多的应用场景;再者,作为组播 ID的 AID资源与 FMS ID 要丰富, 在一定程度上解决了因 FMS ID所支持的组播周期数有限造成组播 应用受限的问题。
基于上述, 在一可选实施方式中, 所述 DTIM信标帧用于指示有组播信 息发送的组播组的方式为: 使用 DTIM 信标帧中的部分虚拟位图 (英文为 partial virtual bitmap )指示有组播信息发送的组播组。 在现有技术中, 部分虚 拟位图是用于在单播情况下指示某个 AID对应的 STA需要接收下行数据的, 在本实施方式中, 由于使用 AID作为组播 ID,故在组播情况下可以用信标帧 中已经存在的部分虚拟位图来指示有组播消息发送的组播组,一种实施方式 为, 如果采用使用 AID作为组播组的组播 ID的方式, 即一个组播 ID对应多 个 AID , 则在 AP有该组播组的组播信息要发送时, 信标帧使用其用于标识 单播数据的部分虚拟位图中的对应于该组播 ID的 AID来标识该组播组。 例 如, 如果部分虚拟位图中对应某个 AID的位为 1 , 表示使用该 AID作为组播 ID的组播组有组播信息要发送,如果部分虚拟位图中对应多个 AID的位为 1 , 表示使用这些 AID作为组播 ID的组播组都有组播信息要发送。 由此可见, 使用 AID作为组播 ID还可以使用信标帧中已有的比特通知有组播信息发送 的组播组, 不需要增大信标帧, 有利于信标帧的压缩。
综上所述, 本发明实施例提供的组播信息发送方法, AP按照有组播信息 发送的组播组的组播 ID的大小顺序,依次在发送间隔发送有组播信息发送的 组播组的组播信息, 而 STA根据自己所在组播组的组播 ID在有组播信息发 送的组播组的组播 ID中的顺序,在对应的接收间隔接收自己所在组播组的组 播信息, 解决了现有技术中各 STA接收信标帧之后所有组播信息的问题, 减 轻了因此造成的 STA的资源浪费。
图 4为本发明一实施例提供的组播信息接收方法的流程图。如图 4所示, 本实施例的方法包括:
步骤 401、 STA接收 AP发送的 DTIM信标帧该 DTIM信标帧用于指示 有组播信息发送的组播组。
步骤 402、 STA根据 STA所在组播组的组播 ID在上述有组播信息发送 的组播组的组播 ID中的大小顺序, 在 STA所在组播组对应的接收间隔内接 收 AP发送的该 STA所在组播组的组播信息。
在本实施例中, 每个组播组都有一个组播 ID , 用于唯一标识该组播组。 AP上存储有每个有组播信息发送的组播组的组播信息。 当 AP需要向至少一 个组播组中的 STA发送组播信息时, 首先向 STA发送信标帧, 在该信标帧 中的类型指示位指示该信标帧为 DTIM信标帧, 通过该 DTIM信标帧一方面 告知 STA该 DTIM信标帧之后将发送组播信息, 另一方面告知 STA有组播 信息发送的是哪个或哪些组播组。 相应地, STA接收 AP发送的 DTIM信标 帧, 对接收到的信标帧进行解析, 获知有组播信息要发送的组播组, 并根据 自己所在组播组的组播 ID判断出自己所在组播组是否属于 DTIM信标帧指示 的有组播信息要发送的组播组。 当 STA确定自己所在组播组属于 DTIM信标 帧指示的有组播信息要发送的组播组后, 准备接收 AP发送的组播信息。 AP向 STA发送 DTIM信标帧之后, 按照有组播信息发送的组播组的组 播 ID的大小顺序,依次在各个发送间隔发送这些组播组的组播信息。对 STA 来说, 采用与 AP相适应的处理方式, 即确定自己所在组播组的组播 ID在 DTIM信标帧指示的有组播信息发送的组播组的组播 ID中的大小顺序, 然后 根据该大小顺序确定自己所在组播组对应的接收间隔, 然后在对应的接收间 隔内接收自己所在组播组的组播信息, 而不接收其他组播组的组播信息, 解 决了现有技术中 STA在接收 DTIM信标帧之后,需要接收该 DTIM信标帧后 所有组播信息的问题, 有利于减轻因此造成的 STA的资源浪费, 尤其适用于 有低能耗需求的 STA。
在一可选实施方式中, 每个接收间隔为组播信息的平均发送时长。 基于 此, STA根据 STA所在组播组的组播 ID在有组播信息发送的组播组的组播 ID中的大小顺序,在 STA所在组播组对应的接收间隔内接收 AP发送的 STA 所在组播组的组播信息的方式具体为: STA根据组播信息的平均发送时长, 按照自己所在组播组的组播 ID在有组播信息发送的组播组的组播 ID中的大 小顺序, 确定自己的唤醒时刻, 然后接收组播信息。 如图 5所示, 假设有 3 个组播组要发送组播信息, 分别为第一组播组、 第二组播组和第三组播组, 这三个组播组的组播 ID的大小顺序从大到小依次为第一组播组、第二组播组 和第三组播组, 则这三个组播组中的 STA接收相应组播信息的方式如图 5所 示。第一个组播组内的 STA在 DTIM信标帧后唤醒接收属于自己的组播信息 (即第一组播组的组播信息), 第二组播组内的 STA在等待 1个组播信息的 平均发送时长后唤醒接收属于自己的组播信息(即第二组播组的组播信息 ); 第三组播组内的 STA在等待 2个组播信息的平均发送时长后唤醒接收属于自 己的组播信息 (即第三组播组的组播信息) 。 可选的, STA每等待 1个组播 信息的平均发送时长, 还可以多等待 1个 SIFS。 例如, 如果 STA等待 2个组 播信息的平均发送时长, 则总的等待时长为 (2 个组播信息的平均发送时长 +2个 SIFS ) 。
可选的, 组播信息的发送平均时长可以是预先设定的经验值。 另外, 组 播信息的发送平均时长也可以是 AP在确定出有组播信息要发送的组播组后, 在发送组播信息之前, 根据每个组播组要发送的组播信息的大小以及发送速 率计算出并发送给 STA的。 在一可选实施方式中, 每个接收间隔为信标帧间隔, 这里的信标帧间隔 是指两个信标帧之间的间隔。这里的信标帧既包括 TIM信标帧,也包括 DTIM 信标帧。 有组播信息发送的各组播组中的 STA根据其所在组播组的组播 ID 的大小顺序, 可以在接收到当前 DTIM信标帧后, 下个 DTIM信标帧前 TIM 信标帧后顺序接收其组播消息。 其中, 在 DTIM信标帧或 TIM信标帧后可以 发送一个或者多个组播组的组播信息。 以图 6所示为例, 假设有组播信息发 送的组播组分别为第一组播组、 第二组播组和第三组播组, 这三个组播组的 组播 ID的大小顺序从大到小依次为第一组播组、 第二组播组和第三组播组, 则第一组播组内的 STA会在当前 DTIM信标帧后唤醒接收属于自己的组播信 息 (即第一组播组的组播信息) , 第二组播组在当前 DTIM信标帧后第一个 TIM信标帧后唤醒接收属于自己的组播信息 (第二组播组的组播信息) , 第 三组播组会在当前 DTIM信标帧后的第二个 TIM信标帧后唤醒接收属于自己 的组播信息(即第三组播组的组播信息)。 在此说明, AP在两个 DTIM信标 帧之间发送的 TIM信标帧的个数可以适应性确定。
在一可选实施方式中, 组播 ID可以是 MAC地址或 FMS ID等, 但不限 于此。
在一可选实施方式中, 组播 ID为至少一个 AID。 也就是说, 上述有组播 信息发送的组播组(包括 STA所在组播组) 的组播 ID为至少一个 AID。 其 中, 具体哪些 AID作为单播 AID , 哪些 AID作为组播 ID使用可由 AP 自行 确定。 也就是说, 只要作为组播 ID的 AID与用于单播的 AID不相同即可。
在组播 ID为 AID的基础上, DTIM信标帧用于指示有组播信息发送的组 播组的方式为: 使用 DTIM信标帧中的部分虚拟位图指示所述有组播信息发 送的组播组。 例如, 如果部分虚拟位图中对应某个 AID的位为 1 , 表示使用 该 AID作为组播 ID的组播组有组播信息要发送, 如果部分虚拟位图中对应 多个 AID的位为 1 , 表示使用这些 AID作为组播 ID的组播组都有组播信息 要发送。 由此可见, 使用 AID作为组播 ID还可以使用信标帧中已有的比特 通知有组播信息发送的组播组, 不需要增大信标帧, 有利于信标帧的压缩。
在一可选实施方式中, 如图 7所示, 本实施例的方法在步骤 401之前还 包括:
步骤 400、 STA接收 AP发送的该 STA所在组播组的组播 ID。 通过步骤 400 , STA可以预先获知自己自所在组播组的组播 ID , 然后根 据自己所在组播组的组播 ID 在对应的接收间隔内接收自己所在组播组的组 播信息。
在一可选实施方式中, 可由 AP主动发起组播 ID的分配, 即 AP主动向 STA发送该 STA所在组播组的组播 ID。 则 STA具体可以接收 AP主动发送 的该 STA所在组播组的组播 ID。
在一可选实施方式中,可由 STA主动向 AP请求其所在组播组的组播 ID, 贝^ STA接收 AP发送的该 STA所在组播组的组播 ID包括: STA向 AP发送 请求组播 ID的信息, 然后, STA接收 AP根据所述请求组播 ID的信息发送 的该 STA所在组播组的组播 ID。 其中, STA发送的请求组播 ID的信息可以 是 STA的 MAC地址、 IP地址或者其他能够唯一标识该 STA的信息。 AP根 据 STA发送的请求组播 ID的信息识别该 STA,然后确定该 STA所在组播组 的组播 ID。 可选的, AP可以在接收到请求组播 ID的信息后, 实时为该 STA 分配组播 ID , 也可以直接获取预先分配好的组播 ID。
其中, STA向 AP发送请求组播 ID的信息的一种可选实施方式包括: STA 将所述请求组播 ID的信息封装在请求消息中发送给 AP。 可选的, 该请求消 息可以是一新增的消息。
STA向 AP发送请求组播 ID的信息的另一种可选实施方式包括: STA在 已有控制帧或已有管理帧或已有数据帧中新增 IE, 将所述请求组播 ID的信 息封装在新增的 IE中发送给 AP。
其中, STA接收 AP发送的该 STA所在组播组的组播 ID的一种可选实 施方式包括: STA接收 AP发送的新增管理帧或新增控制帧, 该新增管理帧 或新增控制帧包括该 STA所在组播组的组播 ID , 则 STA具体从接收的新增 管理帧或新增控制帧中获取该 STA所在组播组的组播 ID。
STA接收 AP发送的该 STA所在组播组的组播 ID的另一种可选实施方 式包括: STA接收 AP发送的已有管理帧或已有控制帧或已有数据帧, 该已 有管理帧或已有控制帧或已有数据帧中新增的 IE中包括该 STA所在组播组 的组播 ID,该 STA具体从接收的已有管理帧或已有控制帧或已有数据帧中新 增的 IE中获取该 STA所在组播组的组播 ID。
在本实施例的一可选实施方式中, STA在接收 AP发送的该 STA所在组 播组的组播 ID之后, 可以向 AP发送 ACK消息。 这样, AP可以及时获知 STA是否接收到该 STA所在组播组的组播 ID。 在要求 STA发送 ACK消息 的情况下, 如果 AP在一定时间内没有接收到 ACK消息, 则 AP需要重新向 STA发送该 STA所在组播组的组播 ID。
在一可选实施方式中, AP还可以发起的组播 ID的注销过程, 例如 AP 向 STA发送组播 ID注销消息, 并在组播 ID注销消息中携带指示将 STA所 在组播组的组播 ID注销的注销指示。 基于此, 本实施例的方法还包括: STA 接收 AP发送的组播 ID注销消息,以获知需要与自己所在的组播组解除关联, 因此解除与需要该组播组之间的关联关系。可选的, STA接收到组播 ID注销 消息之后, 可以向 AP发送 ACK消息, 以告知 AP已经接收到组播 ID注销 消息。 相应的, AP在向 STA发送组播 ID注销消息之后, 接收 STA发送的 ACK消息。 在要求发送 ACK消息的前提下, 如果 AP在一定时间内没有收 到 ACK消息, 则需要重新发送组播 ID注销消息给相应未收到其 ACK消息 的 STA。
AP向 STA发送组播 ID注销消息的一种可选实施方式包括: AP使用新 增的管理帧或控制帧,将组播 ID注销消息封装在新增的管理帧或控制帧中发 送给 STA。 相应地, STA接收 AP发送的新增的管理帧或控制帧或数据帧, 从接收到的新增的管理帧或控制帧或数据帧中获取组播 ID注销消息。
AP向 STA发送组播 ID注销消息的另一种可选实施方式包括: AP在已 有的管理帧或控制帧或数据帧中新增 IE, 将组播 ID注销消息封装在新增的 IE中发送给相应 STA。 相应地, STA接收 AP发送的已有的管理帧或控制帧 或数据帧,从接收到的已有的管理帧或控制帧或数据帧中获取组播 ID注销消 息。
在一可选实施方式中, 组播 ID的注销过程还可以由 STA主动发起, 例 如 STA在需要与自己所在组播组解除关联关系时, 向 AP发送组播 ID注销 请求, 以使 AP根据组播 ID注销请求将对自己所在组播组的组播 ID注销。 相应地, AP接收 STA发送的组播 ID注销请求, 可选的, 该组播 ID注销请 求可以包括 STA所在组播组的组播 ID , 即需要注销的组播 ID。 可选的, AP 还可以在接收到组播 ID注销请求后, 向 SAT发送 ACK消息。 相应地, STA 接收 AP发送的 ACK消息, 以便于及时获知 AP接收到组播 ID注销请求, 有利于组播 ID的及时注销。 在要求 AP返回 ACK消息的情况下, 如果 STA 在一定时间内未接收到 AP发送的 ACK消息, 则需要重新向 AP发送上述组 播 ID注销请求。
其中, STA向 AP发送组播 ID注销请求的一种可选实施方式包括: STA 使用新增的请求消息,将组播 ID注销请求封装在所述新增的请求消息中发送 给 AP。
其中, STA向 AP发送组播 ID注销请求的另一种可选实施方式包括: STA 在已有的控制帧或管理帧或数据帧中新增 IE, 将所述组播 ID注销请求封装 在新增的 IE中发送给 AP。
在一可选实施方式中, AP还可以发起的组播 ID的变更,例如 AP向 STA 发送组播 ID变更消息,该组播 ID变更消息包括 STA所在组播组变更后的组 播 ID。 可选的, 该组播 ID变更消息还可以包括 STA所在组播组原来的组播 ID。其中,对于一组播组来说,该组播组原来的组播 ID是需要变更的组播 ID, 该组播组新的组播 ID是指变更后的组播 ID。则本实施例的方法还包括: STA 接收 AP发送的组播 ID变更消息, 以获知需要对组播 ID进行变更并确定变 更后的组播 ID。 然后, STA根据组播 ID变更消息包括的所述 STA所在组播 组的变更后的组播 ID , 更新 STA所在组播组的组播 ID。 可选的, STA在接 收到 AP发送的组播 ID变更消息后, 可以向 AP发送 ACK消息。 在要求发 送 ACK消息的前提下, 如果 AP在一定时间内没有收到 ACK消息, 则需要 重新发送组播 ID变更消息给相应未收到其 ACK消息的 STA。
AP向 STA发送组播 ID变更消息的一种可选实施方式包括: AP使用新 增的管理帧或控制帧,将组播 ID变更消息封装在新增的管理帧或控制帧中发 送给 STA。 相应地, STA接收 AP发送的新增的管理帧或控制帧, 从接收到 的新增的管理帧或控制帧中获取组播 ID变更消息。
AP向 STA发送组播 ID变更消息的另一种可选实施方式包括: AP在已 有的管理帧或控制帧或数据帧中新增 IE, 将组播 ID变更消息封装在新增的 IE中发送给相应 STA。 相应地, STA接收 AP发送的已有的管理帧或控制帧 或数据帧,从接收到的已有的管理帧或控制帧或数据帧中新增的 IE中获取组 播 ID变更消息。
在一可选实施方式中, 组播 ID的变更还可以由 STA主动发起。 基于此, 本实施例的方法还包括: STA在需要进行组播 ID的变更时, 可以向 AP发送 组播 ID变更请求,然后接收 AP根据组播 ID变更请求发送的组播 ID变更消 息。 相应地, AP接收 STA发送的组播 ID变更请求, 根据组播 ID变更请求, 向 STA发送变更后的组播 ID。其中,组播 ID变更请求可以包括 STA的 MAC 地址、 IP地址或其他可以唯一标识该 STA的信息。 可选的, AP可以才艮据组 播 ID变更请求携带的信息, 重新为 STA分配一个组播 ID, 然后将重新分配 的组播 ID作为变更后的组播 ID发送给 STA。
STA向 AP发送组播 ID变更请求的一种可选实施方式包括: STA使用请 求消息, 将组播 ID变更请求封装在所述请求消息中发送给 AP。 这里的请求 消息也可以是一个新增的消息。
STA向 AP发送组播 ID变更请求的另一种可选实施方式包括: STA在已 有的控制帧或管理帧或数据帧中新增 IE, 将所述组播 ID变更请求封装在新 增的 IE中发送给 AP。
上述各实施方式给出了 STA接收自己所在组播组的组播 ID、 注销组播 ID和变更组播 ID的多种实施方案, 实现了对组播 ID的管理, 具有筒单易于 实现的优势。
由上述可见, 本实施例提供的组播信息接收方法, STA接收 AP发送 DTIM信标帧, 根据 DTIM信标帧获知将要发送组播信息的组播组, 然后根 据 STA所在组播组的组播 ID在所有有组播信息要发送的组播组的组播 ID中 的大小顺序, 在对应的接收间隔内接收自己所在组播组的组播信息, 解决了 现有技术中各 STA接收信标帧之后所有组播信息的问题, 减轻了因此造成的 STA的资源浪费。
进一步本发明实施例还提供另一种组播信息接收方法, 方法包括:
S4201,站点 STA接收接入点 AP发送的组播组关联标示符 MID,其中一个 组播组具有一个或多个 MID,每一个所述 MID对应一个组播组及该组播组中 所述 STA的接收周期;
S4203,所述 STA接收所述 AP发送的一发送传输指示映射 DTIM信标帧, 所述 DTIM信标帧包含所述 MID,用于指示有组播信息向所述 STA发送的组 播组;
S4205,所述 STA接收所述 AP发送的所述组播组的组播信息,其中所述组 播信息携带有所述 MID或关联所述 MID的信息。 在具体的实施中, STA向 AP发送请求 MID的信息帧,请求 MID的信息 帧用于所述 AP生成所述 MID。
在一实施例中,请求 MID的信息包括 MID请求和 MID请求信息单元,其 中 MID请求用于指示该信息帧用于 MID请求,所述 MID请求信息单元用于所 述 AP生成所述向 STA发送组播组的 MID。 所述 MID请求信息单元包括:所 述组播组的 MAC地址,组播组的 MAC地址用于所述 AP分配所述 MID; 或者 所述组播组的 MAC地址和所述 STA接收该组播组组播信息的周期,组播组的 MAC地址和所述 STA接收该组播组组播信息的周期用于所述 AP分配所述 MID。
作为一种实现方式,所述 STA通过该 STA的关联标识符 AID请求信息单 元携带所述 MID请求信息单元中的信息。
本发明实施例还提供又一种接收组播组信息的方法,包括: 站点 STA接收 AP发送的组播组 MID,每一个所述 MID对应一个组播组 及该组播组中 STA的接收周期;
所述 STA接收所述 AP发送的 DTIM信标帧,所述 DTIM信标帧的部分虚 拟位图中包含对一个或多个页的 MID 指示信息,在不同的页中包含对应同一 所述组播组的不同 MID,所述不同的 MID对应所述组播组中 STA的同一接收 周期;
所述 STA在唤醒时接收所述 AP发送的所述组播组的组播信息,所述组播 信息携带有所述 MID信息或关联所述 MID的信息,所述组播信息由所述 STA 接收。
进一步,在本实施例提供的组播信息接收方法中,使用 AID作为组播 ID, 与现有技术中使用 FMS ID的方案相比,作为组播 ID的 AID可以由 AP指定, STA不需要与 AP进行协商, 具有较强的实现灵活性; 另外, 作为组播 ID的 AID对组播信息的发送周期没有要求, 既支持周期性发送的组播信息也支持 随机发送的组播信息, 能够适用更多的应用场景; 再者, 作为组播 ID的 AID 资源与 FMS ID要丰富,在一定程度上解决了因 FMS ID所支持的组播周期数 有限造成组播应用受限的问题。
现有技术中提出了一种 FMS模式。 工作在 FMS模式下的 STA, 可以与 AP协商收听 DTIM信标帧的周期, 这样就不需要收听每一个 DTIM信标帧。 但是, FMS模式最多可以支持 8种不同的周期,并使用长度为 8个比特的 FMS ID来标识, 这就限制了实际中应用的灵活度。 针对该问题, 本发明以下实施 例提供了一种组播标识发送方法及接收方法,用以解决现有技术中因 FSM ID 所支持的组播周期数有限造成组播应用受限的问题。
图 8为本发明一实施例提供的组播标识发送方法的流程图。 本实施例的 执行主体为 AP。 如图 8所示, 本实施例的方法包括:
步骤 701、 确定 STA所在组播组的组播标识 ID , 该 STA所在组播组的 组播 ID映射在 AID。
步骤 702、 将 STA所在组播组的组播 ID发送给 STA。
其中, AP确定站点 STA所在组播组的组播 ID的一种可选实施方式包括: AP将 STA所在组播组的组播 ID映射在一个 AID中。
AP确定站点 STA所在组播组的组播 ID的另一种可选实施方式包括: AP 将 STA所在组播组的组播 ID映射在至少两个 AID中。
基于上述, AP将 STA所在组播组的组播 ID映射在一个 AID中的可选 实施方式包括但不限于以下方式:
AP将 STA所在组播组的组播 ID映射在该 AID中任意 Page、 Block和 / 或 Sub-block中。
AP将 STA所在组播组的组播 ID映射在该 AID中预先指定的 Page、Block 和 /或 Sub-block中。
基于上述, AP将 STA所在组播组的组播 ID映射在至少两个 AID中的 可选实施方式包括但不限于以下方式:
AP将 STA所在组播组的组播 ID映射在上述至少两个 AID中不同 Page、 Block和 /或 Sub-block中。
AP将 STA所在组播组的组播 ID 映射在上述至少两个 AID 中相同的
Page. Block和 /或 Sub-block中。
在一可选实施方式中, 可由 AP主动发起组播 ID的分配, 则 AP可以主 动将 STA所在组播组的组播 ID发送给相应的 STA。
在一可选实施方式中,可由 STA主动向 AP请求其所在组播组的组播 ID。 则 AP将 STA所在组播组的组播 ID发送给该 STA的实施方式包括:接收 STA 发送的请求组播 ID的信息, 然后根据所述请求组播 ID的信息, 向该 STA发 送该 STA所在组播组的组播 ID。
其中, AP接收 STA发送的请求组播 ID的信息的一种实施方式包括: AP 接收 STA发送的请求消息, 该请求消息包括请求组播 ID的信息。 可选的, 该请求消息可以是一个新增的消息。
AP接收 STA发送的请求组播 ID的信息的另一种实施方式包括: AP接 收 STA发送的已有控制帧或已有管理帧或已有数据帧, 该已有控制帧或已有 管理帧或已有数据帧中新增的 IE中包括请求组播 ID的信息。
在一可选实施方式中, AP将 STA所在组播组的组播 ID发送给 STA的 一种实施方式包括: AP将 STA所在组播组的组播 ID封装在新增的管理帧或 新增的控制帧中发送给 STA。
在一可选实施方式中, AP将 STA所在组播组的组播 ID发送给 STA的 另一种实施方式包括: AP 在已有管理帧或已有控制帧或已有数据帧中新增 IE, 将 STA所在组播组的组播 ID封装在新增的 IE中发送给 STA。
在一可选实施方式中, AP将 STA所在组播组的组播 ID发送给 STA之 后还包括: AP接收 STA发送的 ACK消息。 这样有利于及时获知 STA是否 接收到其所在组播组的组播 ID。 在要求 STA返回 ACK消息的情况下, 如果 AP在一定时间内没有接收到 ACK消息, 则需要重新向 STA发送该 STA所 在组播组的组播 ID。
在一可选实施方式中, AP还可以发起的组播 ID的注销过程。 基于此, 本实施例的方法还包括: AP向 STA发送组播 ID注销消息, 该组播 ID注销 消息包括指示将所述 STA所在组播组的组播 ID注销的注销指示。 可选的, 该组播 ID注销消息还可以包括需要注销的组播 ID , 即 STA所在组播组的组 播 ID。
AP向 STA发送组播 ID注销消息的一种可选实施方式包括: AP使用新 增的管理帧或控制帧,将组播 ID注销消息封装在新增的管理帧或控制帧中发 送给 STA。
AP向 STA发送组播 ID注销消息的另一种可选实施方式包括: AP在已 有的管理帧或控制帧或数据帧中新增 IE, 将组播 ID注销消息封装在新增的 IE中发送给相应 STA。 在一可选实施方式中, AP将 STA所在组播组的组播 ID发送给 STA之 后还可以包括: AP接收 STA发送的组播 ID注销请求, 根据组播 ID注销请 求, 将 STA所在组播组的组播 ID注销。
在一可选实施方式中, AP还可以发起的组播 ID的变更。 基于此, 本实 施例的方法还包括: AP向 STA发送组播 ID变更消息, 该组播 ID变更消息 包括所述 STA所在组播组的变更后的组播 ID。 可选的, 该组播 ID变更消息 还可以包括需要变更的组播 ID , 即 STA所在组播组原来的组播 ID。 对一个 组播组来说, 这里需要变更的组播 ID是该组播组原来的组播 ID, 而变更后 的组播 ID是该组播组使用的新组播 ID。
可选的, AP向 STA发送组播 ID变更消息的一种实施方式包括: AP接 收 STA发送的组播 ID变更请求, 根据组播 ID变更请求, 向 STA发送组播 ID变更消息。
AP向 STA发送组播 ID变更消息的一种可选实施方式包括: AP使用新 增的管理帧或控制帧,将组播 ID变更消息封装在新增的管理帧或控制帧中发 送给 STA。
AP向 STA发送组播 ID变更消息的另一种可选实施方式包括: AP在已 有的管理帧或控制帧或数据帧中新增 IE, 将组播 ID变更消息封装在新增的 IE中发送给相应 STA。
上述各实施方式的详细描述可参见前述组播信息发送方法实施例的描 述, 在此不再赘述。
由上述可见, 本实施例提供的组播标识发送方法, 通过使用 AID作为组 播组的组播 ID, AP将 STA所在组播组的组播 ID发送给 STA, 使得 STA可 以获知自己所在组播组的组播 ID ,通过利用 AID资源丰富的特性,一定程度 上解决了现有技术中因 FSM ID所支持的组播周期数有限造成组播应用受限 的问题。 另夕卜, 本实施例使用 AID作为组播组的组播 ID, 与现有技术中使用 FMS ID的方案相比, 作为组播 ID的 AID可以由 AP指定, STA不需要与 AP进行协商, 具有较强的实现灵活性; 另外, 作为组播 ID的 AID对组播信 息的发送周期没有要求, 既支持周期性发送的组播信息也支持随机发送的组 播信息, 能够适用更多的应用场景。
图 9为本发明一实施例提供的组播标识接收方法的流程图。如图 9所示, 本实施例的方法包括:
步骤 801、 STA接收 AP发送的 STA所在组播组的组播标识 ID , 该 STA 所在组播组的组播 ID映射在 AID。
步骤 802、 STA记录 STA所在组播组的组播 ID。
在一可选实施方式中, 可由 AP发起组播 ID的分配, 则 STA接收 AP发 送的 STA所在组播组的组播标识 ID具体为: STA接收 AP主动发送的 STA 所在组播组的组播标识 ID。
在一可选实施方式中, 可由 STA发起组播 ID的分配, 则 STA接收 AP 发送的 STA所在组播组的组播标识 ID具体为: STA向 AP发送请求组播 ID 的信息, 然后接收 AP根据所述请求组播 ID的信息发送的 STA所在组播组 的组播 ID。
其中, STA向 AP发送请求组播 ID的信息的一种可选实施方式包括: STA 将所述请求组播 ID的信息封装在请求消息中发送给 AP。 可选的, 该请求消 息可以是一个新增的消息。
STA向 AP发送请求组播 ID的信息的另一种可选实施方式包括: STA在 已有控制帧或已有管理帧或已有数据帧中新增 IE, 将请求组播 ID的信息封 装在新增的 IE中发送给 AP。
其中, STA接收 AP发送的 STA所在组播组的组播标识 ID的一种实施 方式包括: STA接收 AP发送的新增管理帧或新增控制帧, 该新增管理帧或 新增控制帧包括 STA所在组播组的组播 ID。
STA接收 AP发送的 STA所在组播组的组播标识 ID的另一种实施方式 包括: STA接收 AP发送的已有管理帧或已有控制帧或已有数据帧, 该已有 管理帧或已有控制帧或已有数据帧中新增的 IE中包括 STA所在组播组的组 播 ID。
在一可选实施方式中, STA接收 AP发送的 STA所在组播组的组播标识
ID之后包括: STA向 AP发送 ACK消息。
在一可选实施方式中, AP还可以发起的组播 ID的注销过程。 基于此, 本实施例的方法还包括: STA接收 AP发送的组播 ID注销消息, 该组播 ID 组播消息包括指示将 STA所在组播组的组播 ID注销的注销指示。 可选的, STA接收到组播 ID注销消息之后, 可以向 AP发送 ACK消息, 以告知 AP 已经接收到组播 ID注销消息。
AP向 STA发送组播 ID注销消息的一种可选实施方式包括: AP使用新 增的管理帧或控制帧帧,将组播 ID注销消息封装在新增的管理帧或控制帧中 发送给 STA。 相应地, STA接收 AP发送的新增的管理帧或控制帧, 从接收 到的新增的管理帧或控制帧中获取组播 ID注销消息。
在一可选实施方式中, 组播 ID的注销过程还可以由 STA主动发起。 基 于此, 本实施例的方法还包括: STA在需要与自己所在组播组解除关联关系 时, 向 AP发送组播 ID注销请求, 以使 AP根据组播 ID注销请求, 将 STA 所在组播组的组播 ID注销, 从而解除与该组播组的关联。
其中, STA向 AP发送组播 ID注销请求的一种可选实施方式包括: STA 使用新增的请求消息,将组播 ID注销请求封装在所述新增的请求消息中发送 给 AP。
其中, STA向 AP发送组播 ID注销请求的另一种可选实施方式包括: STA 在已有的控制帧或管理帧或数据帧中新增 IE, 将所述组播 ID注销请求封装 在新增的 IE中发送给 AP。
在一可选实施方式中, AP还可以发起的组播 ID的变更。 则本实施例的 方法还包括: STA接收 AP发送的组播 ID变更消息, 该组播 ID变更消息包 括所述 STA所在组播组的变更后的组播 ID。 STA根据组播 ID变更消息获知 需要对组播 ID进行变更并确定变更后的组播 ID, 然后根据组播 ID变更消息 包括的 STA所在组播组的变更后的组播 ID ,更新 STA所在组播组的组播 ID。
在一可选实施方式中, 组播 ID的变更还可以由 STA主动发起。 基于此, STA接收 AP发送的组播 ID变更消息的一种实施方式包括: STA在需要进行 组播 ID的变更时,可以向 AP发送组播 ID变更请求, 然后接收 AP根据组播 ID变更请求发送的组播 ID变更消息。
STA向 AP发送组播 ID变更请求的一种可选实施方式包括: STA使用请 求消息, 将组播 ID变更请求封装在所述请求消息中发送给 AP。 这里的请求 消息也可以是一个新增的消息。
STA向 AP发送组播 ID变更请求的另一种可选实施方式包括: STA在已 有的控制帧或管理帧或数据帧中新增 IE, 将所述组播 ID变更请求封装在新 增的 IE中发送给 AP。 上述各实施方式给出了 STA接收自己所在组播组的组播 ID、 注销组播 ID和变更组播 ID的多种实施方案, 实现了对组播 ID的管理, 具有筒单易于 实现的优势。
上述各实施方式的详细描述可参见前述组播信息发送方法实施例的描 述, 在此不再赘述。
由上述可见, 本实施例提供的组播标识接收方法, 通过使用 AID作为组 播组的组播 ID, STA接收 AP发送的 STA所在组播组的组播 ID, 然后利用 AID资源丰富的特性, 一定程度上解决了现有技术中因 FSM ID所支持的组 播周期数有限造成组播应用受限的问题。 另外, 本实施例使用 AID作为组播 组的组播 ID, 与现有技术中使用 FMS ID的方案相比, 作为组播 ID的 AID 可以由 AP指定, STA不需要与 AP进行协商,具有较强的实现灵活性;另夕卜, 作为组播 ID的 AID对组播信息的发送周期没有要求, 既支持周期性发送的 组播信息也支持随机发送的组播信息, 能够适用更多的应用场景。
图 10是本发明一实施例的接入点 AP的示意框图。 图 10的接入点 900 至少包括处理器 901、 存储器 902和发射电路 905。 处理器 901、 存储器 902 和接收电路 903通过总线系统 904相连。 此外, 接入点 900还可以包括接收 电路 903及天线 906等, 处理器 901控制接入点 900, 处理器 901还可以称 为中央处理单元( Central Processing Unit, CPU )。 存储器 902可以包括只读 存储器和随机存取存储器, 并向处理器 901提供指令和数据。 存储器 902的 一部分还可以包括非易失性随机存取存储器 (NVRAM ) 。 具体的应用中, 接收电路 903和发射电路 905可以耦合到天线 906。 接入点 900的各个组件 通过总线系统 904耦合在一起, 其中总线系统 904除包括数据总线之外, 还 可以包括电源总线、 控制总线和状态信号总线等。 但是为了清楚说明起见, 在图中将各种总线都标为总线系统 904。
上述本发明实施例揭示的方法可以应用于处理器 901 中, 或者由处理器
901 配合各功能电路或者器件实现。 处理器 901可能是一种集成电路芯片, 具有信号的处理能力。在实现过程中,上述方法的各步骤可以通过处理器 901 中的硬件的集成逻辑电路或者软件形式的指令完成。 上述的处理器 901 可以 是通用处理器、 数字信号处理器 (DSP ) 、 专用集成电路(ASIC ) 、 现成可 编程门阵列(FPGA )或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、 分立硬件组件。 可以实现或者控制执行本发明实施例中的公开的各方法、 步 骤及逻辑框图。 通用处理器可以是微处理器或者该处理器也可以是任何常规 的处理器等。 结合本发明实施例所公开的方法的步骤可以直接体现为硬件译 码处理器执行完成, 或者用译码处理器中的硬件及软件模块组合执行完成。 软件模块可以位于随机存储器, 闪存、 只读存储器, 可编程只读存储器或者 电可擦写可编程存储器、 寄存器等本领域成熟的存储介质中。 该存储介质位 于存储器 902, 处理器 901读取存储器 902中的信息, 结合其硬件完成上述 方法的步骤。
本实施例中, 处理器 901用于生成组播组关联标示符 MID和发送传输指 示映射 DTIM信标帧;
发射电路 905通过天线发送所述组播组关联标示符 MID、 所述发送传输 指示映射 DTIM信标帧和组播组的组播信息;
其中一个组播组具有一个或多个 MID,每一个所述 MID对应一个组播组 及该组播组中 STA的接收周期; 所述 DTIM信标帧包含所述 MID,用于指示有 组播信息向所述 STA发送的组播组; 所述组播信息携带有所述 MID或关联所 述 MID的信息,所述组播信息由所述 STA接收。在有 STA休眠的模式下, 及 唤醒所述 STA接收所述组播信息 MID指示有组播信息向所述 STA发送的组 播组以唤醒所述 STA接收所述组播信息。
进一步接收电路 903 用于通过所述天线接收所述 STA发送的请求 MID 的信息帧;则所述处理器根据所述请求 MID 的信息帧生成所述组播组关联标 示符 MID。
在本实施例中,所述请求 MID的信息包括 MID请求和 MID请求信息单 元, 其中 MID请求用于指示该信息帧用于 MID请求, 所述 MID请求信息单 元包括:所述组播组的 MAC地址;所述处理器 905所述组播组的 MAC地址分 配所述 MID。
在具体的实施里中处理器 905将所述 MID请求信息单元中的信息通过 所述 STA的 AID请求信息单元携带。 在实施中所述 MID包含 MID回复信 息和 MID回复信息单元, 其中 MID回复信息表示该信息帧为 MID回复帧, 回复信息单元携带所述 STA所属组播组的 MID信息,进一步回复信息单元携 带所述组播组的 MAC地址,允许接收组播信息的周期长度,以及 MID生效时 间。处理器 905所述 MID 回复信息单元的信息通过所述 AP的关联标识符的 回复信息单元携带。
图 11是本发明另一实施例的接入点 AP的示意框图。图 11的接入点 1000 至少包括处理器 1001、 存储器 1002和发射电路 1005。 处理器 1001、 存储器 1002和接收电路 1003通过总线系统 1004相连。 此外, 接入点 1000还可以 包括接收电路 1003及天线 1006等, 处理器 1001控制接入点 1000, 处理器 1001还可以称为中央处理单元( Central Processing Unit, CPU )。存储器 1002 可以包括只读存储器和随机存取存储器, 并向处理器 1001提供指令和数据。 存储器 1002的一部分还可以包括非易失性随机存取存储器(NVRAM ) 。 具 体的应用中, 接收电路 1003和发射电路 1005可以耦合到天线 1006。 接入点 1000的各个组件通过总线系统 1004耦合在一起, 其中总线系统 1004除包括 数据总线之外, 还可以包括电源总线、 控制总线和状态信号总线等。 但是为 了清楚说明起见, 在图中将各种总线都标为总线系统 1004。
上述本发明实施例揭示的方法可以应用于处理器 1001中,或者由处理器 1001配合各功能电路或者器件实现。 处理器 1001可能是一种集成电路芯片, 具有信号的处理能力。在实现过程中,上述方法的各步骤可以通过处理器 1001 中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器 1001可以 是通用处理器、 数字信号处理器 (DSP ) 、 专用集成电路(ASIC ) 、 现成可 编程门阵列(FPGA )或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、 分立硬件组件。 可以实现或者控制执行本发明实施例中的公开的各方法、 步 骤及逻辑框图。 通用处理器可以是微处理器或者该处理器也可以是任何常规 的处理器等。 结合本发明实施例所公开的方法的步骤可以直接体现为硬件译 码处理器执行完成, 或者用译码处理器中的硬件及软件模块组合执行完成。 软件模块可以位于随机存储器, 闪存、 只读存储器, 可编程只读存储器或者 电可擦写可编程存储器、 寄存器等本领域成熟的存储介质中。 该存储介质位 于存储器 1002, 处理器 1001,读取存储器 1002中的信息, 结合其硬件完成上 述方法的步骤。
本发明实施的接入点,处理器 1001用于生成组播组的 MID和 DTIM信标 帧; 发射电路 1005用于通过天线 1006发送所述组播组关联标示符 MID、 所 述发送传输指示映射 DTIM信标帧和组播组的组播信息;其中每一个所述 MID 对应一个组播组及该组播组中 STA的接收周期; 所述 DTIM信标帧的部分虚 拟位图中包含对一个或多个页的 MID 指示信息,在不同的页中包含对应同一 所述组播组的不同 MID,所述不同的 MID对应所述组播组中 STA的同一接收 周期; 所述组播信息携带有所述 MID信息或关联所述 MID的信息, 所述组 播信息由所述 STA接收。 进一步还包括:接收电路 1003用于通过所述天线接收所述 STA发送的请 求 MID的信息帧;则所述处理器 1001才艮据所述请求 MID的信息帧生成所述组 播组关联标示符 MID。
进一步,所述请求 MID的信息包括 MID请求和 MID请求信息单元,其中
MID请求用于指示该信息帧用于 MID请求, 所述 MID请求信息单元包括:所 述组播组的 MAC地址,则所述处理器 1001所述组播组的 MAC地址分配所述 MID。
在具体的实施里中处理器 905将所述 MID请求信息单元中的信息通过 所述 STA的 AID请求信息单元携带。 在实施中所述 MID包含 MID回复信 息和 MID回复信息单元, 其中 MID回复信息表示该信息帧为 MID回复帧, 回复信息单元携带所述 STA所属组播组的 MID信息,进一步回复信息单元携 带所述组播组的 MAC地址,允许接收组播信息的周期长度,以及 MID生效时 间。处理器 905所述 MID 回复信息单元的信息通过所述 AP的关联标识符的 回复信息单元携带。
本发明实施例的接入点 AP 能够实现上述方法实施例的各步骤或功能。 接入点 AP按照上述方法实施例的具体流程完成组播信息发送方法。 因此上 述方法实施例中的方法完全可以由接入点实现。
进一步本发明实施例还给出一种站点 STA。图 12是本发明一实施例的点 STA的示意框图。 图 12的站点 1200至少包括处理器 1201、 存储器 1202和 发射电路 1205。 处理器 1201、 存储器 1202和接收电路 1203通过总线系统 1204相连。 此外, 站点 1200还可以包括接收电路 1203及天线 1206等, 处 理器 1001控制接入点 1200, 处理器 1201还可以称为中央处理单元(Central Processing Unit, CPU ) 。 存储器 1202可以包括只读存储器和随机存取存储 器, 并向处理器 1201提供指令和数据。 存储器 1202的一部分还可以包括非 易失性随机存取存储器(NVRAM ) 。 具体的应用中, 接收电路 1203和发射 电路 1205可以耦合到天线 1206。接入点 1200的各个组件通过总线系统 1204 耦合在一起,其中总线系统 1204除包括数据总线之外,还可以包括电源总线、 控制总线和状态信号总线等。 但是为了清楚说明起见, 在图中将各种总线都 标为总线系统 1204。
上述本发明实施例揭示的方法可以应用于处理器 1201中,或者由处理器 1201配合各功能电路或者器件实现。 处理器 1201可能是一种集成电路芯片, 具有信号的处理能力。在实现过程中,上述方法的各步骤可以通过处理器 1201 中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器 1201可以 是通用处理器、 数字信号处理器 (DSP ) 、 专用集成电路(ASIC ) 、 现成可 编程门阵列(FPGA )或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、 分立硬件组件。 可以实现或者控制执行本发明实施例中的公开的各方法、 步 骤及逻辑框图。 通用处理器可以是微处理器或者该处理器也可以是任何常规 的处理器等。 结合本发明实施例所公开的方法的步骤可以直接体现为硬件译 码处理器执行完成, 或者用译码处理器中的硬件及软件模块组合执行完成。 软件模块可以位于随机存储器, 闪存、 只读存储器, 可编程只读存储器或者 电可擦写可编程存储器、 寄存器等本领域成熟的存储介质中。 该存储介质位 于存储器 1202, 处理器 1201,读取存储器 1202中的信息, 结合其硬件完成上 述方法的步骤。 在本实施例中站点包括: 接收电路 1203,通过天线接收 AP发送的组播组关联标示符 MID、发送传 输指示映射 DTIM 和组播组的组播信息; 其中一个组播组具有一个或多个 MID,每一个所述 MID对应一个组播组及该组播组中所述 STA 的接收周期, 所述 DTIM信标帧包含所述 MID,用于指示有组播信息向所述 STA发送的组 播组; 处理器 1021, 用于根据所述 MID和 DTIM唤醒该 STA以使得所述接收 电路接收所述组播组的组播信息。 进一步还包括所述 STA还包括: 发射电路 1025,用于通过天线发送发送请求 MID的信息帧,所述请求 MID 的信息帧用于所述 AP生成所述 MID。
作为另一种具体的实现方式,仍参阅图 12,站点包括:
接收电路,通过天线接收 AP发送的组播组关联标示符 MID、 发送传输指 示映射 DTIM和组播组的组播信息;
其中每一个所述 MID对应一个组播组及该组播组中 STA的接收周期;所 述 DTIM信标帧的部分虚拟位图中包含对一个或多个页的 MID指示信息,在 不同的页中包含对应同一所述组播组的不同 MID,所述不同的 MID对应所述 组播组中 STA的同一接收周期; 处理器, 用于根据所述 MID和 DTIM使得所述接收电路接收所述组播组 的组播信息。
该实施例中 STA所接收到 MID和 DTIM的方式与上一实施有所不同。 本发明实施例提供的组播标识发送、 接收方法及设备, 通过使用 MID作 为组播组的组播 ID, AP将 STA所在组播组的组播 MID发送给 STA, —定 程度上解决了现有技术中因 FSM ID所支持的组播周期数有限造成组播应用 受限的问题
本领域普通技术人员可以意识到, 结合本文中所公开的实施例中描述的 各方法步骤和单元, 能够以电子硬件、 计算机软件或者二者的结合来实现, 为了清楚地说明硬件和软件的可互换性, 在上述说明中已经按照功能一般性 地描述了各实施例的步骤及组成。这些功能究竟以硬件还是软件方式来执行, 取决于技术方案的特定应用和设计约束条件。

Claims

权 利 要 求 书
1、 一种组播信息发送方法, 其特征在于, 所述方法包括: 接入点 AP向站点 STA发送组播组关联标示符 MID,其中一个组播组具有 一个或多个 MID,每一个所述 MID对应一个组播组及该组播组中 STA的接收 周期;
所述 AP向所述 STA发送一发送传输指示映射 DTIM信标帧,所述 DTIM 信标帧包含所述 MID,用于指示有组播信息向所述 STA发送的组播组;
所述 AP发送所述组播组的组播信息,所述组播信息携带有所述 MID或关 联所述 MID的信息, 所述组播信息由所述 STA接收。
2、 根据权利要求 1所述的组播信息发送方法, 其特征在于, 所述 AP向
STA发送组播组的 MID之前包括:
接收所述 STA发送的请求 MID的信息帧,
则所述向站点 STA发送组播组的 MID包括:
所述 AP根据接收到的所述请求 MID的信息帧, 向该 STA发送该 STA 所在组播组的 MID。
3、 根据权利要求 2 所述的组播信息发送方法, 其特征在于, 所述请求 MID的信息帧包括 MID请求信息单元;
贝^ AP向站点 STA发送组播组的 MID之前,所述 AP根据所述 MID请求 信息单元生成所述向 STA发送组播组的 MID。
4、根据权利要求 3所述的组播信息发送方法,其特征在于,所述 MID请求 信息单元包括:所述组播组的 MAC地址,所述 AP根据所述组播组的 MAC地 址分配所述 MID; 或者
所述组播组的 MAC地址和所述 STA接收该组播组组播信息的周期,所述 AP根据所述组播组的 MAC地址和所述 STA接收该组播组组播信息的周期分 配所述 MID。
5、根据权利要求 3-4任一权利要求所述的组播信息发送方法,其特征在于: 所述 MID请求信息单元中的信息通过所述 STA的 AID请求信息单元携 带。
6、 根据权利要求 2任一权利要求所述的组播信息发送方法,其特征在于: 该 STA所在组播组的 MID封装 MID回复帧中, 所述 MID回复帧包含 MID回复信息单元,所述 MID回复信息单元携带所述 STA所属组播组的 MID 信息。
7、 根据权利要求 6所述的组播信息发送方法, 其特征在于,所述 所述 MID回复信息单元携带所述组播组的 MAC地址,允许接收组播信息 的周期长度,以及 MID生效时间。
8、 根据权利要求 6所述的组播信息发送方法, 其特征在于,所述 MID回 复信息单元的信息通过所述 AP的关联标识符的回复信息单元携带。
9、 一种组播信息发送方法, 其特征在于, 包括:
AP向站点 STA发送组播组的 MID,每一个所述 MID对应一个组播组及 该组播组中 STA的接收周期;
所述 AP向所述 STA发送 DTIM信标帧,所述 DTIM信标帧的部分虚拟位 图中包含对一个或多个页的 MID 指示信息,在不同的页中包含对应同一所述 组播组的不同 MID,所述不同的 MID对应所述组播组中 STA的同一接收周期; 所述 AP发送所述组播组的组播信息,所述组播信息携带有所述 MID信息 或关联所述 MID的信息, 所述组播信息由所述 STA接收。
10、 根据权利要求 9 所述的组播信息发送方法, 其特征在于, 所述 AP 向站点 STA发送组播组的 MID之前包括:
接收所述 STA发送的请求 MID的信息帧,
则所述向站点 STA发送组播组的 MID包括:
所述 AP根据接收到的请求 MID的信息帧, 向该 STA发送该 STA所在 组播组的 MID。
11、 根据权利要求 10所述的组播信息发送方法, 其特征在于, 所述请求 MID的信息帧包括 MID请求信息单元;
贝^ AP向站点 STA发送组播组的 MID之前,所述 AP根据所述 MID请求 信息单元生成所述向 STA发送组播组的 MID。
12、根据权利要求 11所述的组播信息发送方法, 其特征在于, 所述 MID 请求信息单元包括:
所述组播组的 MAC地址,所述 AP根据所述组播组的 MAC地址分配所述 MID; 或者
所述组播组的 MAC地址和所述 STA接收该组播组组播信息的周期,所述 AP根据所述组播组的 MAC地址和所述 STA接收该组播组组播信息的周期分 配所述 MID
13、 根据权利要求 11-12任一权利要求所述的组播信息发送方法,其特征 在于:
所述 MID请求信息单元通过 AID关联标识符请求信息单元携带。
14、 根据权利要求 10-13任一权利要求所述的组播信息发送方法, 其特 征在于:
所述 AP将一个所述组播组的所述一个所述接收周期的 MID映射到不同 页的块和子块中以使得所述 STA以不同的周期接收组播信息。
15、 根据权利要求 10任一权利要求所述的组播信息发送方法,其特征在 于:
该 STA所在组播组的 MID封装 MID回复帧中, 所述 MID回复帧包含 MID回复信息单元,所述 MID回复信息单元携带所述 STA所属组播组的 MID 信息。
16、 根据权利要求 15所述的组播信息发送方法, 其特征在于,所述 所述 MID回复信息单元携带所述组播组的 MAC地址,允许接收组播信息 的周期长度,以及 MID生效时间。
17、根据权利要求 15所述的组播信息发送方法,其特征在于,所述 MID 回 复信息单元的信息通过所述 AP的关联标识符的回复信息单元携带。
18、 一种接入点,其特征在于,所述接入点包括:
处理器, 用于生成组播组关联标示符 MID和发送传输指示映射 DTIM信 标帧;
发射电路, 用于通过天线发送所述组播组关联标示符 MID、 所述发送传 输指示映射 DTIM信标帧和组播组的组播信息;
其中一个组播组具有一个或多个 MID,每一个所述 MID对应一个组播组 及该组播组中 STA的接收周期; 所述 DTIM信标帧包含所述 MID,用于指示有 组播信息向所述 STA发送的组播组; 所述组播信息携带有所述 MID或关联所 述 MID的信息, 所述组播信息由所述 STA接收。
19、 根据权利要求 18所述的接入点,其特征在于,所述接入点还包括: 接收电路, 用于通过所述天线接收所述 STA发送的请求 MID的信息帧; 则所述处理器根据所述请求 MID 的信息帧生成所述组播组关联标示符 MID。
20、 根据权利要求 19所述的接入点,其特征在于, 所述请求 MID的信息 帧包括 MID请求信息单元, 所述 MID请求信息单元包括所述组播组的 MAC 地址;
所述处理器根据所述组播组的 MAC地址分配所述 MID。
21、 一种接入点,其特征在于,所述接入点包括:
处理器,用于生成组播组的 MID和 DTIM信标帧; 发射电路,用于通过天线发送所述组播组关联标示符 MID、所述发送传输 指示映射 DTIM信标帧和组播组的组播信息;其中每一个所述 MID对应一个 组播组及该组播组中 STA的接收周期; 所述 DTIM信标帧的部分虚拟位图中 包含对一个或多个页的 MID 指示信息,在不同的页中包含对应同一所述组播 组的不同 MID,所述不同的 MID对应所述组播组中 STA的同一接收周期; 所 述组播信息携带有所述 MID信息或关联所述 MID的信息, 所述组播信息由 所述 STA接收。
22、 根据权利要求 21所述的接入点,其特征在于,所述接入点还包括: 接收电路, 用于通过所述天线接收所述 STA发送的请求 MID的信息帧; 则所述处理器根据所述请求 MID 的信息帧生成所述组播组关联标示符
MID。
23、 根据权利要求 22所述的接入点,其特征在于, 所述请求 MID的信息 帧包括 MID请求信息单元,所述 MID请求信息单元包括:所述组播组的 MAC 地址;
所述处理器根据所述组播组的 MAC地址分配所述 MID。
24、 一种接收组播组信息的方法,其特征在与, 所述方法包括:
站点 STA接收接入点 AP发送的组播组关联标示符 MID,其中一个组播组 具有一个或多个 MID,每一个所述 MID 对应一个组播组及该组播组中所述 STA的接收周期; 所述 STA接收所述 AP发送的一发送传输指示映射 DTIM信标帧,所述 DTIM信标帧包含所述 MID,用于指示有组播信息向所述 STA发送的组播组; 所述 STA接收所述 AP发送的所述组播组的组播信息,其中所述组播信息 携带有所述 MID或关联所述 MID的信息。
25、 根据权利要求 24所述的方法,其特征在于,所述方法还包括: 所述 STA向所述 AP发送请求 MID的信息帧,所述请求 MID的信息帧用 于所述 AP生成所述 MID。
26、 根据权利要求 24或 25所述的方法,其特征在于,所述方法还包括: 所述请求 MID的信息帧包括 MID请求信息单元, 所述 MID请求信息单 元用于所述 AP生成所述向 STA发送组播组的 MID。
27、根据权利要求 26所述的方法,其特征在于,所述 MID请求信息单元包 括:所述组播组的 MAC地址,所述组播组的 MAC地址用于所述 AP分配所述
MID; 或者
所述组播组的 MAC地址和所述 STA接收该组播组组播信息的周期,所述 组播组的 MAC地址和所述 STA接收该组播组组播信息的周期用于所述 AP 分配所述 MID。
28、 根据权利要求 24-27任一权利要求所述的方法,其特征在于: 所述 STA通过该 STA的关联标识符 AID请求信息单元携带所述 MID请 求信息单元中的信息。
29、 一种接收组播组信息的方法, 其特征在于, 包括: 站点 STA接收 AP发送的组播组 MID,每一个所述 MID对应一个组播组 及该组播组中 STA的接收周期;
所述 STA接收所述 AP发送的 DTIM信标帧,所述 DTIM信标帧的部分虚 拟位图中包含对一个或多个页的 MID 指示信息,在不同的页中包含对应同一 所述组播组的不同 MID,所述不同的 MID对应所述组播组中 STA的同一接收 周期;
所述 STA在唤醒时接收所述 AP发送的所述组播组的组播信息,所述组播 信息携带有所述 MID信息或关联所述 MID的信息,所述组播信息由所述 STA 接收。
所述 STA向所述 AP发送请求 MID的信息帧,所述请求 MID的信息帧用 于所述 AP生成所述 MID。
31、 根据权利要求 29或 30所述的方法,其特征在于,所述方法还包括: 所述请求 MID的信息帧包括 MID请求信息单元, 所述 MID请求信息单 元用于所述 AP生成所述向 STA发送组播组的 MID。
32、根据权利要求 31所述的,方法,其特征在于,所述 MID请求信息单元包 括:所述组播组的 MAC地址,所述组播组的 MAC地址用于所述 AP分配所述
MID; 或者
所述组播组的 MAC地址和所述 STA接收该组播组组播信息的周期,所述 组播组的 MAC地址和所述 STA接收该组播组组播信息的周期用于所述 AP 分配所述 MID。
33、 根据权利要求 29-31任一权利要求所述的方法,其特征在于: 所述 STA通过该 STA的关联标识符 AID请求信息单元携带所述 MID 请求信息单元中的信息。
34、 一种站点 STA,其特征在于,所述所述 STA包括: 接收电路,通过天线接收 AP发送的组播组关联标示符 MID、 发送传输指 示映射 DTIM和组播组的组播信息; 其中一个组播组具有一个或多个 MID,每 一个所述 MID 对应一个组播组及该组播组中所述 STA 的接收周期, 所述 DTIM信标帧包含所述 MID,用于指示有组播信息向所述 STA发送的组播组; 处理器, 用于根据所述 MID和 DTIM使得所述接收电路接收所述组播组 的组播信息。
35、 根据权利要求 34所述的 STA,其特征在与,所述 STA还包括: 发射电路,用于通过天线发送发送请求 MID的信息帧,所述请求 MID的信 息帧用于所述 AP生成所述 MID。
36、 一种站点 STA,其特征在于,所述所述 STA包括:
接收电路,通过天线接收 AP发送的组播组关联标示符 MID、 发送传输指 示映射 DTIM和组播组的组播信息;
其中每一个所述 MID对应一个组播组及该组播组中 STA的接收周期;所 述 DTIM信标帧的部分虚拟位图中包含对一个或多个页的 MID指示信息,在 不同的页中包含对应同一所述组播组的不同 MID,所述不同的 MID对应所述 组播组中 STA的同一接收周期;
处理器, 用于根据所述 MID和 DTIM使得所述接收电路接收所述组播组 的组播信息。
37、 根据权利要求 36所述的 STA,其特征在与,所述 STA还包括: 发射电路,用于通过天线发送发送请求 MID的信息帧,所述请求 MID的信 息帧用于所述 AP生成所述 MID。
PCT/CN2013/088706 2013-03-01 2013-12-06 组播信息传输方法及设备 Ceased WO2014131300A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
RU2015141698A RU2635888C2 (ru) 2013-03-01 2013-12-06 Способ и устройство передачи многоадресной информации
KR1020157026751A KR20150120526A (ko) 2013-03-01 2013-12-06 멀티캐스트 정보 전송 방법 및 장치
EP13876114.3A EP2955942B1 (en) 2013-03-01 2013-12-06 Multicast information transmission method and device
US14/836,682 US20150365885A1 (en) 2013-03-01 2015-08-26 Multicast information transmission method and device
US15/698,563 US20170374609A1 (en) 2013-03-01 2017-09-07 Multicast information transmission method and device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201310066677.0 2013-03-01
CN201310066677 2013-03-01
CN201310069902.6A CN104023316B (zh) 2013-03-01 2013-03-05 组播信息传输方法及设备
CN201310069902.6 2013-03-05

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/836,682 Continuation US20150365885A1 (en) 2013-03-01 2015-08-26 Multicast information transmission method and device

Publications (1)

Publication Number Publication Date
WO2014131300A1 true WO2014131300A1 (zh) 2014-09-04

Family

ID=51427513

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/088706 Ceased WO2014131300A1 (zh) 2013-03-01 2013-12-06 组播信息传输方法及设备

Country Status (6)

Country Link
US (2) US20150365885A1 (zh)
EP (1) EP2955942B1 (zh)
KR (1) KR20150120526A (zh)
CN (1) CN104023316B (zh)
RU (1) RU2635888C2 (zh)
WO (1) WO2014131300A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10069883B2 (en) * 2015-06-22 2018-09-04 Intel IP Corporation Apparatus, system and method of communicating in a multicast group
CN120825467A (zh) * 2025-09-16 2025-10-21 格创通信(浙江)有限公司 组播报文的发送方法、装置及设备

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9237481B2 (en) * 2012-07-09 2016-01-12 Intel Corporation Methods and arrangements for traffic indication map segmentation in wireless networks
US11553018B2 (en) * 2014-04-08 2023-01-10 Comcast Cable Communications, Llc Dynamically switched multicast delivery
KR20170003559A (ko) * 2014-05-09 2017-01-09 엘지전자 주식회사 무선랜에서 파워 세이브 모드 동작을 위한 방법 및 장치
CN105007568B (zh) * 2014-07-28 2018-10-23 魅族科技(中国)有限公司 一种组播消息帧的传输方法、相关设备及系统
US10075950B2 (en) * 2014-12-12 2018-09-11 Qualcomm Incorporated Traffic advertisement in neighbor aware network (NAN) data path
US20160174136A1 (en) * 2014-12-12 2016-06-16 Qualcomm Incorporated Traffic advertisement in neighbor aware network (nan) data path
US9949236B2 (en) 2014-12-12 2018-04-17 Qualcomm Incorporated Traffic advertisement in neighbor aware network (NAN) data path
US10820314B2 (en) 2014-12-12 2020-10-27 Qualcomm Incorporated Traffic advertisement in neighbor aware network (NAN) data path
US10827484B2 (en) 2014-12-12 2020-11-03 Qualcomm Incorporated Traffic advertisement in neighbor aware network (NAN) data path
CN111491395B (zh) * 2015-07-02 2024-04-09 华为技术有限公司 关联的建立方法及装置
US10736022B2 (en) * 2015-11-02 2020-08-04 Apple Inc. Proxy assisted NAN and access point concurrent operation
US20180124704A1 (en) * 2016-11-03 2018-05-03 Mediatek Inc. Method of Wake-up Signal Transmission and Reception
US10708859B2 (en) * 2016-11-28 2020-07-07 Texas Instruments Incorporated Methods and apparatus for efficient wakeup of wireless device
WO2018182312A1 (ko) * 2017-03-28 2018-10-04 엘지전자 주식회사 무선랜 시스템에서 패킷을 송신하는 방법 및 이를 이용한 송신 단말
US10917927B2 (en) 2017-05-12 2021-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Local identifier locator network protocol (ILNP) breakout
US11246095B2 (en) 2017-06-28 2022-02-08 Lg Electronics Inc. Method for transmitting or receiving frame in wireless LAN system and device therefor
CN109548119B (zh) * 2017-09-22 2022-07-15 珠海市魅族科技有限公司 无线局域网的通信方法、装置、接入点设备和站点设备
CN107992999B (zh) * 2017-11-27 2021-06-11 西北工业大学 一种面向个性化生产环境的多主体调度方法
US11375453B2 (en) * 2017-12-21 2022-06-28 Apple Inc. Power-efficient communication of group-addressed frames
US10834671B2 (en) * 2017-12-22 2020-11-10 Intel IP Corporation Group identification indication signaling
US20190132796A1 (en) * 2018-01-29 2019-05-02 Po-Kai Huang Wake-up frame indication
CN110446244A (zh) * 2018-05-03 2019-11-12 中兴通讯股份有限公司 一种唤醒控制方法及装置、计算机可读存储介质
EP3878214B1 (en) 2018-11-07 2024-04-03 Telefonaktiebolaget LM Ericsson (publ) Local identifier locator network protocol (ilnp) breakout
US11184849B2 (en) * 2019-09-17 2021-11-23 Cisco Technology, Inc. Use of target wake time to reduce delivery traffic indication message multicast
WO2022000421A1 (zh) * 2020-07-02 2022-01-06 北京小米移动软件有限公司 无线通信方法及装置、通信设备及存储介质
TWI756911B (zh) * 2020-11-10 2022-03-01 瑞昱半導體股份有限公司 WiFi STA分組方法和相關裝置
CN114513834B (zh) * 2020-11-17 2024-07-19 瑞昱半导体股份有限公司 WiFi AP及用于WiFi AP和WiFi STA的方法
CN115486199B (zh) * 2021-04-16 2026-04-17 北京小米移动软件有限公司 多连接下的通信方法和通信装置
US12284520B2 (en) * 2021-05-19 2025-04-22 Cisco Technology, Inc. Access point verification using crowd-sourcing
US12610000B2 (en) 2021-11-30 2026-04-21 Texas Instruments Incorporated Bluetooth low energy connection power consumption
CN117805515B (zh) * 2023-12-04 2024-11-12 湖南恩智测控技术有限公司 超级电容器充放电测试方法、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101707739A (zh) * 2002-05-18 2010-05-12 Lg电子株式会社 一种从网络接收mbms业务的方法
CN101835102A (zh) * 2010-05-19 2010-09-15 迈普通信技术股份有限公司 一种用于无线局域网的队列管理方法以及无线接入设备
WO2010124417A1 (zh) * 2009-04-28 2010-11-04 上海贝尔股份有限公司 无线通信系统中控制mbms业务接收的方法和装置

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7251235B2 (en) * 2002-06-12 2007-07-31 Conexant, Inc. Event-based multichannel direct link
JP4182058B2 (ja) * 2003-01-09 2008-11-19 ノキア コーポレイション ワイヤレス通信システムにおけるアクセスポイントの選択
RU2414098C2 (ru) * 2005-08-22 2011-03-10 Эл Джи Электроникс Инк. Способ обработки сообщений с управляющей информацией при многоточечном обслуживании
US20070201413A1 (en) * 2006-02-27 2007-08-30 Nokia Corporation Method and system to enhance energy savings in multicast transmissions in WLAN
US7916687B2 (en) * 2006-03-03 2011-03-29 Qualcomm Incorporated Standby time improvements
US20080049703A1 (en) * 2006-08-28 2008-02-28 Nokia Corporation Multicast-only data transmission mode for access points and virtual access points in a wireless network
US20080062923A1 (en) * 2006-09-12 2008-03-13 Aruba Wireless Networks System and method for reliable multicast over shared wireless media for spectrum efficiency and battery power conservation
US8295216B2 (en) * 2006-12-21 2012-10-23 Nokia Corporation Broadcast and multicast transmission techniques for powersave devices in wireless networks
CN101222388B (zh) * 2007-01-12 2013-01-16 华为技术有限公司 一种确定接入点存在广播/多播缓存帧的方法和系统
WO2008104095A1 (en) * 2007-02-27 2008-09-04 Thomson Licensing Method and apparatus for power management in wlan
US8170002B2 (en) * 2007-05-31 2012-05-01 Conexant Systems, Inc. Systems and methods for indicating buffered data at an access point with efficient beacon handling
US8233414B2 (en) * 2007-07-05 2012-07-31 Conexant Systems, Inc. Systems and methods for indicating buffered data at an access point using an embedded traffic indication map
JP5107189B2 (ja) * 2008-09-09 2012-12-26 株式会社エヌ・ティ・ティ・ドコモ 無線通信基地局、無線通信端末、無線通信システム及び無線通信方法
WO2011005004A2 (en) * 2009-07-07 2011-01-13 Lg Electronics Inc. Method and apparatus for indicating destination stations in wlan system supporting multi-user multiple input multiple output
CN102740354B (zh) * 2011-04-15 2015-04-15 华为终端有限公司 通知、获取待接收数据指示信息的方法及装置
CN107249198B (zh) * 2011-10-07 2021-04-09 英特尔公司 用于无线网络中的业务指示映射的方法和布置
CN104380832B (zh) * 2012-03-12 2018-06-29 新加坡科技研究局 压缩设备、解压缩设备、压缩方法和解压缩方法
CN103634126B (zh) * 2012-08-22 2017-12-22 华为技术有限公司 组播信息传输方法及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101707739A (zh) * 2002-05-18 2010-05-12 Lg电子株式会社 一种从网络接收mbms业务的方法
WO2010124417A1 (zh) * 2009-04-28 2010-11-04 上海贝尔股份有限公司 无线通信系统中控制mbms业务接收的方法和装置
CN101835102A (zh) * 2010-05-19 2010-09-15 迈普通信技术股份有限公司 一种用于无线局域网的队列管理方法以及无线接入设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2955942A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10069883B2 (en) * 2015-06-22 2018-09-04 Intel IP Corporation Apparatus, system and method of communicating in a multicast group
CN120825467A (zh) * 2025-09-16 2025-10-21 格创通信(浙江)有限公司 组播报文的发送方法、装置及设备

Also Published As

Publication number Publication date
CN104023316B (zh) 2017-11-17
RU2015141698A (ru) 2017-04-06
RU2635888C2 (ru) 2017-11-16
KR20150120526A (ko) 2015-10-27
EP2955942A4 (en) 2016-01-06
US20150365885A1 (en) 2015-12-17
US20170374609A1 (en) 2017-12-28
EP2955942B1 (en) 2020-02-05
EP2955942A1 (en) 2015-12-16
CN104023316A (zh) 2014-09-03

Similar Documents

Publication Publication Date Title
WO2014131300A1 (zh) 组播信息传输方法及设备
CN113382379B (zh) 无线通信方法和通信装置
CN106998582B (zh) 协商目标唤醒时间的方法、接入点和站点
CN103858362B (zh) 在无线通信系统中发送/接收多播数据的装置及其方法
CN115245041B (zh) 一种数据传输的方法及装置
CN102625460B (zh) 一种网络接入方法
WO2019061021A1 (zh) 一种数据传输方法以及相关设备
CN110121203A (zh) 通信方法和通信装置
WO2015058379A1 (zh) 传输信息的方法、装置和系统
JP6040465B2 (ja) マルチキャスト情報送信方法および装置
WO2013159648A1 (zh) 站点与接入点建立关联的方法及设备
US20220353813A1 (en) Scheduling method, access point, and station
WO2014032497A1 (zh) 一种组调度方法及装置
EP4277395A1 (en) Discontinuous reception control method and apparatus
WO2023011350A1 (zh) 通信方法及装置
US20240032142A1 (en) Sidelink transmission method and apparatus
WO2021134577A1 (zh) 一种数据传输方法及装置
WO2011134365A1 (zh) 资源配置参数的指示和更新方法、终端及基站
WO2014134942A1 (zh) 一种组播数据包传输方法及装置
WO2023050319A1 (zh) 无线通信的方法、终端设备和网络设备
CN106102183B (zh) 一种发送响应消息的方法及接入点、站点
WO2014000530A1 (zh) 站点工作模式转换方法和通信设备
CN115088308B (zh) 反馈信息接收方法及装置
WO2023060447A1 (zh) 信号发送方法、信号接收方法、装置、设备及存储介质
WO2020221323A1 (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: 13876114

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2013876114

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20157026751

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2015141698

Country of ref document: RU

Kind code of ref document: A