Mesh node devices

Mesh node device

This creation involves a wireless mesh network that includes multiple nodes (such as a wireless local area network (WLAN) mesh). In particular, this creation involves the sharing of time slot allocation scheduling information among mesh network nodes.

In an IEEE802.11 mesh network (such as a WLAN mesh), two or more nodes exchange data in a period called a time slot. The term "time slot" means multi-dimensional information, which may include, but is not limited to: timing information (such as start and duration), radio frequency (RF) information (such as the number of radios and channels used by nodes to exchange data), Quality of Service (QoS) information (such as the QoS required for data to be exchanged in a time slot), peer node information (such as the node identifier of each node involved in data transmission in a specific time slot), data exchange Direction (for example, one-way, two-way), etc.

In traditional non-mesh WLANs, the optional "scheduling" based on 802.11e HCCA is a single equation controlled by the AP in the Basic Service Set (BSS). In WLAN mesh, scheduling should be coordinated among multiple mesh points (MP) that provide WLAN mesh services.

It is hoped to introduce a mechanism in the nodes of the mesh network that allows nodes to report information about the time slot allocation schedule within the node, and allows nodes to request such scheduling information from other nodes. In order to achieve this new level of coordination, a method and device for exchanging scheduling related information in mesh nodes of a WLAN mesh is needed.

In the IEEE802.11 mesh network where the services between nodes are scheduled to the allocated time slots, by allowing nodes to share their own time slot allocation scheduling information with each other, effective time between multiple nodes is realized. Slot allocation. This enables each node to know the time slot availability of other nodes in advance, so that the node can allocate time slot resources efficiently and without conflict.

This creation provides a mechanism that allows nodes in a mesh network to report their internal time slot allocation schedule to other nodes in the network, and provides a mechanism that allows nodes in the mesh network to request all the data from other nodes. The mechanism of internal time slot allocation scheduling is described.

In the following, nodes include but are not limited to wireless transmit/receive unit (WTRU), user equipment (UE), mobile station, fixed or mobile base station, fixed or mobile access point (AP), fixed or mobile subscriber unit, paging Machine, or any type of device that can work in a wireless environment.

In a mesh network, each node internally keeps track of the time slot assigned to the node after conducting pre- and mutual negotiation with one or more peer nodes. In a specific time slot, the node sends data to and receives data from these peer nodes. The internal tracking record is hereinafter referred to as the "list of allocated time slots" and includes a list of time slots. Each node includes internal memory that stores the list of allocated time slots for that node.

A new information element (IE) 100 is needed to represent the list of allocated time slots. Figure 1 shows the preferred format of IE 100 based on this creation. The IE 100 includes an 8-bit element ID field 105, an 8-bit length field 110, and a variable-length element specific information field 115. According to this creation, the ID field 105 indicates that the IE 100 represents the "list of allocated time slots" IE. The length field 110 specifies the number of 8-bit bytes in the information field 115.

Figure 2 shows the new IE 100 about the information field 115 in more detail. The information field 115 of the list of allocated time slots IE 100 includes a list size sub-field 205, multiple information sub-fields corresponding to each time slot 2101, 2102,..., 210N, and a list size sub-field of the number of time slots Bit 215. Each time slot information sub-field 210 includes a timing information field 220, a radio frequency (RF) information field 225, a quality of service (QoS) information field 230, a peer node information field 235, and a direction field 240. As shown in Figure 2, the detailed sub-columns are related to time slot #1. In this way, the time slot 1 timing information field 220 indicates the start time and duration of the data exchange of time slot #1. The RF information field 225 indicates the radio channel used by the node for data exchange and the number of channels. The QoS information field 230 indicates the QoS required by the data to be exchanged in slot #1. The peer node information field 235 represents the node identifier of each node involved in data transmission in time slot #1. The direction field 240 indicates whether the exchange data in time slot #1 is one-way (that is, from one transmitter to one receiver) or two-way (that is, round-trip between all nodes involved).

Each node can request and report the list of allocated time slots for that node. Preferably, this is performed by adding the following two additional management message types: 1) "request message for the list of allocated time slots" and 2) response message for the list of allocated time slots. The response message of the list of allocated time slots preferably includes the list IE of allocated time slots in its main body.

This creation introduces an improvement to the existing management "action" frame. The category value "time slot report" is added to the action frame definition in the media access control (MAC) entity located in each mesh node. The time slot report action frame is transmitted by the node to transmit the time slot allocation information of the node to other nodes. The time slot report "category" is used in the management action frame to identify such a new category of messages. In this category, the aforementioned two messages are defined: "list request" and "list response". In the "list response" message, a new "list of allocated time slots" IE is defined.

Figure 3 shows an example mesh network 300 including two mesh nodes 305 and 310 according to the present authoring configuration. The node 305 includes a transmitter 315, a receiver 320, a processor 325, a memory 330, and an antenna 332. The node 310 includes a transmitter 335, a receiver 340, a processor 345, a memory 350, and an antenna 352. The processor 325 in the node 305 is configured to generate a request message 360 for the list of allocated time slots, and the request message 360 for the list of allocated time slots is transmitted by the transmitter 315 via the antenna 332 of the node 305. When the node 305 wants to send data to the node 310, the node 305 must know when the node 310 is free to receive data. Therefore, the node 305 requests the node 310 to provide the "allocated time slot" of the node 310 (e.g., the time slot when the node 310 is busy). Therefore, the node 305 can request the "list of allocated time slots" from the node 310, so that some free time slots can be allocated for data exchange with the node 310.

Each memory 330 and 350 keeps track of the time slot allocation schedule information related to the respective node 305, 310.

The memories 330 and 350 also keep track of the time slot allocation information of other nodes except the node where each memory is located. Therefore, each node can keep track of the time slot allocation of another node after sending a "request for a list of allocated time slots" and receiving a "response to a list of allocated time slots".

When the receiver 340 in the node 310 receives the request message 360 for the list of allocated time slots, the processor 325 obtains the IE 100 from the memory 350 and generates a list of the allocated time slots of the IE 100. A response message 365, the response message 365 of the list of allocated time slots is transmitted by the transmitter 335 via the antenna 352 of the node 310. Each processor 325 and 345 includes a MAC entity (not shown) that facilitates the generation of the request message 360 for the list of allocated time slots and the response message 365 for the list of allocated time slots.

This creation can be implemented in software, hardware, intermediary software, future system architecture, radio resource management or radio resource controller (RRC) in the data link layer and network layer. This creation can be applied to but not limited to IEEE802.11, IEEE802.11s, IEEE802.15, IEEE802.15.5, IEEE802.16 and other related mesh technologies.

Although the features and elements of this creation are described in a specific combination in the preferred embodiment, each feature or element can be used alone (in the absence of other features and elements of the preferred embodiment), Or use it in various situations with or without combining with other features and elements of this creation.

<p>RFRadio Frequency</p><p>QoSService quality</p><p>IDidentification</p>

Through the provided examples and combined icons, you can get a more detailed understanding of this creation from the following description, among which: Figure 1 shows the format of the information elements allocated by the time slot; Figure 2 shows the enhanced information based on this creation Element format; Figure 3 shows an example mesh network with two nodes configured according to this authoring.