Method for sending an acknowledgement to an ingress mesh point in a mesh network and a medium access control frame format

Abstract

The present invention relates to a method for confirming the delivery of a data packet in a mesh network by sending an acknowledgement (ACK) to an ingress mesh point (IMP). A mesh network comprises a plurality of mesh points that are wirelessly linked together. A data packet sent by a station (STA) is received by an IMP. A MAC frame is generated for transmission of the data packet and the frame is forwarded to an egress mesh point (EMP) in order to provide a service by the mesh network. The MAC frame includes a field comprising an IMP address and an EMP address. When the EMP, (or optionally an intermediate mesh point), receives a data packet successfully, the EMP or the intermediate mesh point sends an ACK to the IMP or preceding mesh point.

Description

FIELD OF INVENTION

The present invention relates to wireless communication systems. More particularly, the present invention relates to a method for sending an acknowledgement (ACK) to an ingress mesh point (IMP) in a mesh network and a medium access control (MAC) frame format.

BACKGROUND

A mesh wireless local area network (WLAN) is a wireless network comprising two or more mesh points interconnected via wireless links. The mesh network typically serves one or more wireless stations (STAs) within the operating range of the mesh network. A mesh point is any entity within the mesh network which contains a MAC and physical layer (PHY) interface to a wireless medium and supports WLAN mesh services. An IMP is a mesh point through which data enters the mesh WLAN and an egress mesh point (EMP) is a mesh point through which data exits the mesh WLAN. Data sent by a STA is routed from the IMP to the EMP through the mesh WLAN.

IEEE 802.11 standards are one of the standards defining the wireless protocol for a mesh WLAN. Current IEEE 802.11 standards define an acknowledged mode that allows for more reliable data delivery at the lower layers. However, the current acknowledgement mechanism does not work in a mesh network since multiple hops are required over the mesh network before the data is delivered to the destination.

In a mesh WLAN, a communication between an IMP and an EMP can be required. As shown in FIG. 2, a prior art MAC frame does not contain IMP MAC address during the multi-hop transmissions. Therefore, the EMP is unable to identify and communicate with the IMP. There is no mechanism or frame format for sending an acknowledgement between the IMP and the EMP in the mesh WLAN. This seriously limits the reliability of the data delivery. Since there is no ACK mechanism between the IMP and the EMP, the IMP cannot know if the data through the mesh network has been correctly received by the EMP.

SUMMARY

The present invention relates to a method for confirming the delivery of a data packet in a mesh network by sending an ACK to an IMP. The mesh network comprises a plurality of mesh points that are wirelessly linked together. A data packet sent by a STA is received by an IMP. A MAC frame is generated for transmission of the data packet and the frame is forwarded to an EMP in order to provide a service by the mesh network. The MAC frame includes a field comprising an IMP address and an EMP address. When the EMP, (or optionally an intermediate mesh point), receives a data packet successfully, the EMP or the intermediate mesh point sends an ACK to the IMP or preceding mesh point.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding of the invention may be had from the following description of a preferred embodiment, given by way of example and to be understood in conjunction with the accompanying drawing wherein:

FIG. 1 is a diagram of a mesh WLAN in which the present invention is implemented;

FIG. 2 is a diagram of a prior art MAC frame;

FIG. 3 is a signaling diagram for transmission of data and acknowledgement between an IMP, an EMP and intervening mesh points in accordance with the present invention;

FIG. 4 is a diagram of a mesh MAC frame in accordance with the present invention; and

FIG. 5 is a flow diagram of a process for sending an ACK to the IMP in accordance with the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereafter, the terminology “station” (STA) includes but is not limited to a user equipment, a wireless transmit/receive unit (WTRU), a fixed or mobile subscriber unit, a pager, or any other type of device capable of operating in a wireless environment. When referred to hereafter, the terminology “mesh point” includes but is not limited to a Node-B, a base station, a site controller, an access point or any other type of interfacing device in a wireless environment.

The present invention is applicable to any wireless mesh networks including, but not limited to, IEEE 802.11, IEEE 802.11s, IEEE 802.15, IEEE 802.15.5.

FIG. 1 is a diagram of an exemplary mesh WLAN 100 comprising eight (8) mesh points 104₁-104₈. In this example, mesh point 104₄ is an IMP for the STA 102 and mesh point 104₂ is an EMP for the data sent by the STA 102.

Data sent by the STA 102 is routed from one mesh point 104₄ to another mesh point 104₂ through the intermediate mesh points in the mesh WLAN 100 for the Internet access. Multiple data paths can be established within the mesh WLAN 100. As an example, two different data paths from the IMP mesh point 104₄ to the EMP mesh point 104₂ are illustrated by the solid lines designated “A” and “B” in FIG. 1.

As aforementioned with reference to FIG. 2, a drawback with the prior art 802.11 MAC frame format is that the IMP address is not included in the MAC frame in a multi-hop transmission. The present invention solves this problem by including the IMP address in the MAC frame 400. Referring to FIG. 4, a diagram of a mesh MAC frame 200 in accordance with the present invention is shown. The MAC frame 200 includes a MAC header 204, a frame body 212 and a frame check sequence (FCS) field 214. This aspect of the MAC frame format is same to the one in prior art, which guarantees backward compatibility. The MAC header 204 includes a frame control, a duration/ID, address 1, address 2, address 3, a sequence control and address 4. These elements are well known to those of skill in the art.

In accordance with the present invention, however, the MAC header 204 further includes a mesh control field 202. The mesh control field 202 comprises an IMP address field 206 and an EMP address field 208. The receiving mesh point recognizes the IMP 104₄ and the EMP 104₂ with the mesh control field 202 and may send an ACK to the IMP 104₄ or other intermediate mesh point in accordance with the IMP address field 206. It should be noted that the MAC frame format in FIG. 4 is provided as an example and the mesh control field 202 may be included in any location in the MAC frame 200 and the length of the IMP and EMP address fields may vary.

A routing function is available in each mesh point, which allows the mesh point, based on the EMP address included in the mesh control field 202, to know which path used to route the data. When the IMP 104₄ receives an ACK, the IMP 104₄ can discard the related data in its queue. If the IMP 104₄ receives a non-acknowledgement (NACK), the IMP 104₄ re-transmits the data. To avoid any buffer overflow, the IMP 104₄ should discard the data from its queue after a certain amount of time (time-out) if the IMP 104₄ does not receive ACK nor NACK from the EMP 104₂.

FIG. 3 is a signaling diagram for transmission along data path “B” of a data packet and an ACK between an IMP (in this example mesh point 104₄), an EMP (in this example mesh point 104₂) and intermediate mesh points 104₇, 104₈, 104₆, 104₃, (not all of which are shown in FIG. 3 for convenience), in accordance with the present invention. The data packet is forwarded from the IMP 104₄ to the EMP 104₂ through the intermediate mesh points 104₇, 104₈, 104₆, 104₃. As will be explained in detail hereinafter, the MAC frame 200 contains both IMP 104₄ and EMP 104₂ addresses in the IMP address field 206 and the EMP address field 208. When the intermediate mesh points 104₇, 104₈, 104₆, 104₃ and the EMP 104₂ receive a data packet successfully, the intermediate mesh points 104₇, 104₈, 104₆, 104₃ and the EMP 104₂ send an ACK to either the preceding intermediate mesh point or the IMP 104₄. It should be noted that FIG. 3 is an example and zero or any number of intermediate mesh points may exist between the IMP 104₄ and the EMP 104₂. Additionally, the intermediate mesh points used to send the ACK may be same mesh points via which the data packet is forwarded or may be different mesh points.

The acknowledgement mechanism of the present invention supports both single and multiple-hop data delivery over a mesh WLAN. The acknowledgement mechanism operates in four modes: 1) EMP-to-IMP data acknowledgement for more reliable data transfer, (e.g., FTP, HTTP); 2) single-hop data acknowledgement for reliable data transfer; 3) combined EMP-to-IMP and single-hop data acknowledgement for very-reliable data transfer, (e.g., signaling); and 4) no acknowledgement for high-throughput, packet-loss resilient, delay sensitive data transfer, (e.g., video/audio streaming).

In the first mode, (EMP-to-IMP acknowledgement), the acknowledgement is done through all the paths. Whenever the EMP receives a packet sent by the IMP, the EMP sends back an ACK to the originator using the IMP address included in the received packet.

In the second mode, (single hop acknowledgement), the acknowledgement is done at every hop between the transmitting mesh point and the next immediate receiving mesh point.

The third mode, (combined EMP-to-IMP acknowledgement and single hop acknowledgement), combines the first mode and the second mode.

In the fourth mode, no acknowledgement is required between the IMP and the EMP. Although this impacts the reliability of the data delivery, it reduces the delay in transmission.

The Frame Control field in this invention can be used not only to specify whether the Ingress and Egress addresses are contained in the packet, but also to inform which sort of acknowledgement mode is to be used for this packet. A new frame subtype for the frame subtype information element in the frame control field 210 (shown in FIG. 4) is also defined for indicating that the MAC frame 200 includes the IMP address field 206 and the EMP address field 208. The frame control field 210 may also inform which acknowledgement mode among the four modes stated above is to be used for this data packet.

For the first and third mode among the four modes stated above, the MAC frame format allows for an EMP-to-IMP ACK to be transmitted through another path different from the one used for transmission of the data packet. To reduce the delay of transmission, the sender does not need to wait for the ACK to be received before sending the next frame, (i.e., sending and acknowledging can be asynchronous). In this case the bulk ACK can be used to reduce traffic on the network. An ACK can also be sent purposely via different paths depending on the traffic level in order to reduce contention of ACKs with data. This mechanism could be used for delay sensitive and error tolerant applications such as voice application.

FIG. 5 is a flow diagram of a process 300 for sending an ACK to the IMP in accordance with the present invention. A MAC frame is generated by attaching a MAC header to a data packet (step 302). The MAC header includes fields for an IMP address and an EMP address. The MAC frame is forwarded to the EMP either directly or via one or more intermediate mesh points (step 304). The intermediate mesh point, if there is any, and the EMP sends an ACK for successful reception of the data packet to the IMP (step 306).

Although the features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the present invention.

Claims

1. A method for routing a data packet using a mesh network having at least an ingress mesh point and an egress mesh point, the method comprising: receiving, by a wireless mesh point of the mesh network, a data packet that includes a Media Access Control (MAC) frame including control information with a plurality of addresses and a flag, the flag indicating whether the MAC frame is in one of: (1) a first format in which the MAC frame includes a first address of the ingress mesh point and a second address of the egress mesh point or (2) a second format in which the MAC frame does not include the second address of the egress mesh point; andon condition that the flag indicates that the MAC frame is in the first format: reading, by the wireless mesh point, at least the second address of the egress mesh point, androuting, by the wireless mesh point, the data packet based on the second address of the egress mesh point.

2. The method of claim 1, wherein the ingress mesh point is a first network entity through which the data packet enters the mesh network and the egress mesh point is a second network entity through which the data packet exits the mesh network.

3. The method of claim 1, wherein the first format includes: the first address of the ingress mesh point;the second address of the egress mesh point;a third address of a source of the data packet; anda fourth address of a destination of the data packet.

4. The method of claim 1, wherein the second format includes: an address of a destination of the data packet.

5. The method of claim 1, wherein the first format contains six addresses and the second format contains less than six addresses.

6. The method of claim 1, wherein respective ones of the addresses contained in the MAC frame are located in fixed positions with respect to the first and second formats.

7. A mesh point, comprising: a receiver and a processor configured to:receive a data packet that includes control information with a plurality of addresses and a flag, the flag indicating whether the data packet is in one of: (1) a first format in which the data packet includes a first address of an ingress mesh point and a second address of an egress mesh point or (2) a second format in which the data packet does not include the second address of the egress mesh point; andon condition that the flag indicates that the data packet is in the first format, route the data packet based on at least the second address of the egress mesh point.

8. The mesh point of claim 7, wherein the processor is configured to process the control information including any of: the first address of the ingress mesh point through which the data packet enters a mesh network or the second address of the egress mesh point through which the data packet exits the mesh network.

9. The mesh point of claim 7, wherein the processor is configured to process the control information including any of: (1) the first address of the ingress mesh point; (2) the second address of the egress mesh point (3) a third address of a source of the data packet; or (4) a fourth address of a destination of the data packet.

10. The mesh point of claim 7, wherein the processor is configured to process respective ones of the addresses contained in the data packet that are located in fixed positions with respect to the first and second formats.

11. An ingress mesh point, comprising: a transmit/receiver unit and a processor configured to: receive a data packet with a Media Access Control (MAC) frame that includes control information including a plurality of addresses, the plurality of addresses including a first address of an ingress mesh point and a second address of an egress mesh point and;set, in the MAC frame, at least a first additional address of a destination of the data packet and a second additional address of a source of the data packet;set a flag indicating that the data packet is in a format which includes the first and second addresses; androute the data packet based on at least the second address of the egress mesh point.

12. The ingress mesh point of claim 11, wherein the ingress mesh point is a first network entity through which the data packet enters a mesh network and the egress mesh point is a second network entity through which the data packet exits the mesh network.

13. The ingress mesh point of claim 11, wherein the format includes: the first address of the ingress mesh point;the second address of the egress mesh point;a third address of the source of the data packet; anda fourth address of the destination of the data packet.