TW200525375A - Wireless LAN protocol stack - Google Patents

Abstract

Embodiments addressing MAC processing for efficient use of high throughput systems are disclosed. In one aspect, a protocol stack is disclosed comprising one or more of the following: an adaptation layer, a data link control layer, a physical layer, and a layer manager. In another aspect, physical layer feedback is used for adaptation layer processing. In one embodiment, physical layer feedback i; used for segmentation. In another embodiment, physical layer feedback is used for multicast mapping onto one or more unicast channels. In another aspect, a data unit for transmission from a first station to a second station comprises zero or more complete sub-data units, zero or one partial sub-data units from a prior transmission, and zero or one partial sub-data units to fill the data unit. In one embodiment, a pointer may be used to indicate the location of any complete sub-data units.

Description

% I 200525375 IX. Description of the invention: Claim priority under 35 USC §119 This patent application claims priority from the following US provisional patent applications: Provisional patent application number 60 / 511,750 filed on October 15, 2003, entitled "Method and Apparatus for Providing Interoperability and Backward Compatibility in Wireless Communication Systems"; provisional patent application number 60 / 511,904 filed on October 15, 2003, entitled "Method, Apparatus, and System for Medium Access Control in a High Performance Wireless LAN Environment "; provisional patent application number 60/5 1 3,239 filed on October 21, 2003, entitled" Peer-to-Peer Connections in ΜΙΜΟ WEAN System "; provisional patent application filed on December 1, 2003 Case No. 60 / 526,347, entitled "Method, Apparatus, and System for Sub-Network Protocol Stack for Very High Speed Wireless LAN"; provisional patent application No. 60 / 526,356 filed on December 1, 2003, entitled "Method , Apparatus, and System for Multiplexing

Protocol data Units in a High Performance Wireless LAN Environment "; provisional patent application number 60 / 532,791 filed on December 23, 2003, entitled" Wireless Communications Medium Access Control (MAC) Enhancements "; filed on February 18, 2004 Provisional Patent Application No. 60 / 545,963, entitled "Adaptive Coordination Function (ACF)"; Provisional Patent Application No. 60 / 576,545 filed on June 2, 2004, marked 96870.doc-6-200525375 entitled "Method and Apparatus for Robust Wireless Network "; provisional patent application number 60 / 586,841 filed on June 8, 2004, entitled" Method and Apparatus for Distribution Communication Resources Among Multiple Users "; and provisional patent filed on August 11, 2004 Patent application number 60 / 600,960, titled "Method, Apparatus, and System for Wireless Communications"; all their patent applications have been assigned to the same assignee as this patent application and are expressly incorporated by reference In this article. [Technical Field to which the Invention belongs] The present invention relates broadly to the field of communications, and in particular, the present invention relates to a stack of wireless local area network (LAN) protocols. [Prior Art] Wireless communication systems are widely deployed to provide various types of communication such as voice and data. A typical wireless data system or network provides multiple users access to one or more shared resources. The system can use various multiple access technologies, such as Frequency Division Multiplexing (FDM), Time Division Multiplexing (TDM), Code Division Multiplexing (CDM), and others. An example wireless network includes a cellular data system. The following are a few of these examples: (1) "TIA / EIA-95-B Mobile Station-Base for Dual-Mode Broadband Spread Spectrum Cellular System-TIA / EIA-95-B Mobile Station-Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular System (IS-95 standard); (2) named "3rd Generation Partnership 96870.doc 200525375"

Project; 3GPP) standards, and are specified in a set of documents, including document numbers 30, 325.21, 30, 325.212, 30, 325.213, and 30, 8 25.214 (Boundary-0, Xu 8 standards); (3) The standard proposed by the consortium named "3rd Generation Partnership Project 2" (3GPP2), and the "TR-45.5 Physical Layer Standard for the CDMA2000 Spread Spectrum System" (TR-45.5 Physical Layer Standard for cdma2000 Spread Spectrum Systems; IS-2000 standard); and (4) a high data rate (HDR) communication system that complies with the TIA / EIA / IS-856 standard (referred to as the IS-856 standard). Other examples of wireless systems include Wireless Local Area Networks (WLANs), such as the IEEE 802-11 standard (ie, 802.11 (a), (b), or (g)). The deployment of a Multiple Input Multiple Output (MIMO) WLAN including Orthogonal Frequency Division Multiplexing (OFDM) modulation technology can improve these networks. With the advancement of wireless system design, higher data transmission rates have become feasible. Higher data rates open up the possibilities of advanced applications, including voice, video, fast data transfer, and various other applications. However, various applications may have different data transfer requirements. Many types of data may have latency and throughput requirements, or require some Quality of Service (QoS) guarantee. Without resource management, system capacity may decrease and the system may not operate efficiently. The Medium Access Control (MAC) protocol is usually used to configure communication resources shared between several users. The MAC protocol 96870.doc 200525375 often interfaces higher layers to the physical layer used to transmit and receive data. In order to benefit from the increase in negative material transmission rate, the 'MAC protocol must be designed to use shared resources efficiently. Developed high-efficiency systems support multiple transmission rates, which can vary widely depending on the physical link characteristics. It is known that the% of different data application types must be different, and the data transmission rate supported by different user terminals in the system varies greatly. Therefore, it is necessary to develop queues to handle various types of traffic, as well as in various heterogeneous physical chains Progress on the road. Therefore, a technology for MAc processing using a high-throughput system with high efficiency is required. [Summary of the Invention] The specific embodiments disclosed in the present invention satisfy the requirements of this technology for MAC processing using a high-throughput system with high efficiency. In one aspect, a device includes a first layer for receiving one or more packets from one or more data streams, and for generating one or more packets from the one or more packets. -Layer protocol data unit (Protocol Data Unit; pDU). In another aspect, a second layer is deployed to receive one or more first layer PDUs from the first layer and generate one or more from the one or more first layer pDus. Layer 2 PDUs. In another aspect, a third layer is deployed to receive the one or more second layer PDUs and transmit the one or more second layer PDUs to a remote station. In another aspect, a layer of management deployment is used to receive the second layer of feedback and send the second layer of feedback to the first layer. A layer administrator can also receive feedback from any layer and pass that feedback to any other layer. In the __ item aspect, the feedback includes real-world feedback. In another aspect, a protocol stack is deployed, which includes an include logic that is used to check the headers from-or multiple packets and to classify the packets into headers in response to such checks =: = Material flow. In another aspect, the 1-contract stack can include on-demand mapping logic that maps classified packets. The multicast presentation == 亍 in response to entity layer feedback. In another aspect, a logic that is used to split and / or reassemble classified packets. This restructuring can be performed in response to entity layer feedback. In another aspect logic. This type of protocol stack may include one of the two categories of packets used for physical layer transfer. 'The present invention discloses a protocol stack, including a lower-to-Stop T: -regulation layer, a data link control layer, a Solid layers and layers. The present invention discloses a MAC sublayer protocol data unit that can be adjusted to include data from multiple data. Each feature and aspect will be further detailed below.

In the case of another worker, the physical layer feedback is used for the adjustment layer processing. In the case of _: Reality%, the entity layer feedback is used for segmentation. In another specific example, the physical layer feedback is used for multicast mapping to one or more unicast broadcasts. In another specific embodiment, it is optional—used for performing on-demand transport transmission. A combination of unicast, multicast, or broadcast channels in response to physical layer feedback corresponding to various channels. In another aspect, a shell material list TL for transmission from a first station to a second station CT includes zero or more complete child data units, from the former 96870.doc -10- 200525375 a transmission Zero or one local child data unit and zero or one local child data unit to fill the data unit. In a specific embodiment, an indicator is used to indicate the location of any complete child data unit. A partial lean unit can be inserted in a predetermined position. The local subdata unit can be combined with the local subdata unit that was saved first, or stored for later use. In a specific embodiment, a sub-data unit may be a MUX sub-layer protocol data unit (mux PDU). Various other aspects and specific embodiments have also been proposed. These aspects have the advantage of providing high-efficiency media access control, and are suitable for cooperating with the physical layer including high data transmission rate and low data transmission rate. [Embodiment] The present invention discloses a sub-network protocol stack, which supports the same efficiency, low latency, and high throughput operation of the physical layer with the extremely high bit rate of wireless LAN (or similar applications using the latest market-oriented transmission technology). The exemplary wlan supports a 20 MHz bandwidth in excess of 丨 00 Mbps (mimón bits per; million bits per second) bit rate. A method for multiplexing the protocol data unit (PDU) and the subnet control entity (MAC PDU) from multiple user data streams into m groups of data streams is described in conjunction with the protocol stack. Description with the protocol stack A method for multiplexing protocol data units (PDUs) and subnet control entities (MAC PDUs) from multiple user data streams into a single-byte data stream. This approach can support high-performance wireless LAN subnets operating at high efficiency, low latency, and high throughput with the physical layer of very high bit rates. 96870.doc -11-200525375 Subnet protocol stacks widely support high data transmission rates and high-bandwidth physical layer transmission mechanisms, including (but not limited to) · Transmission mechanisms based on OFDM modulation; single-carrier modulation technology; applicable System using multiple receive antennas and multiple transmit antennas operating at very high bandwidth efficiency (multiple input multiple output

(Multiple Input Multiple Output; ΜΙΜΟ) system (ΜΙΜΟ), including a Multiple Input Single Output (MISO) system), a system using multiple receive antennas and multiple transmit antennas in conjunction with space multiplexing technology, for In the same case, data is transmitted to or received from the user terminal, and a system using code division multiple access (CDMA) technology is used to allow multiple Users transmit simultaneously.

One or more exemplary embodiments described herein are proposed in the context of a wireless data communication system. Although there are many advantages to using the present a in this context, different specific embodiments of the present bow can also be incorporated in different environments or configurations. -In general, the various systems described in this article can be constructed using software-controlled processors, integrated circuits, or discrete logic. ^ The materials, instructions, commands, information, signals, symbols, and chips mentioned in this manual are beneficial to be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light and or particles, or any combination thereof. In addition, the six blocks in each block diagram may represent hardware or method steps. Method ㈣ is interchangeable, and will not depart from the materials of the present invention. The term "demonstration" in this article means "to be taken as an example, instance, or explanation." As used herein, as an "exemplary" description # Embodiments are not necessarily considered to be better or better than 96870.doc -12- 200525375 FIG. 1 illustrates an exemplary embodiment of a system 100 that includes a connection to One or more user terminal (UT) 106A-N access points (AP) 104. The AP and the UT communicate via a wireless local area network (WLAN) 120. In this exemplary embodiment, WLAN 120 is a high-speed MIMO OFDM system. However, WLAN 120 may be any wireless LAN. The access point 104 communicates with any external device or process via the network 102. Network 102 may be the Internet, an intranet, or any other wired, wireless, or optical network. The connection 110 carries the physical layer signal from the network to the access point 104. The device or process can be connected to the network 102 or as a UT (or connected to it via a connection) on the WLAN ι20. Examples of networks that can be connected to network 1 or WLAN 120 include telephones, personal digital assistants (pDA), various similar computers (laptops, personal computers, workstations, any type of terminal), video sfi devices (eg, Cameras, camcorders, web cameras, and almost any type of data device). The processing sequence may include voice, video, data communication, and so on. Various data streams have different transmission requirements, which can be adapted to various needs by using a variety of Quality of Service (QoS) technologies. System 100 was deployed using centralized AP 104. In this exemplary embodiment, 'all UTs 106 communicate with the AP. In an alternative embodiment, the system is modified to provide peer-to-peer communication between UTs, as known to those skilled in the art. Based on the clear statement, in this exemplary embodiment, the access of the physical layer transmission mechanism is controlled by the AP. In a specific embodiment, the AP 104 provides Ethernet adjustment. An example is shown in FIG. 24 96870.doc -13- 200525375. In this case, AP 10 04 can be used to deploy the IP router 2410 to provide a connection to network 102 (via Ethernet connection 110). For example, the illustrative example UT 106 shown in the figure is a mobile phone 106A, a personal digital assistant (PDA) 106B, a laptop 106C, a workstation 106D, a personal computer 106E, a video camera 106F, and a video projector 106G . Ethernet frames can be transmitted between the router and the UT 106 via the WLAN subnet 120 (as described in more detail below). Ethernet regulation and connection capabilities are known in the art. Figure 26 shows, for example, the Ethernet Tuning Protocol Stacks 2640 and 2650 for UT 106 and AP 104, respectively, as described in the detailed description of integrating each instance layer below. The UT protocol stack 2640 includes an upper layer 2610, an IP layer 2615, an Ethernet MAC layer 2620A, an adjustment layer 310A, a data link layer 320A, and a physical layer (PHY) 240A. The AP protocol stack 2650 includes a PHY 240B (connected to the UT PHY 240A via the RF link 120), a data link layer 320B, and a regulation layer 310B. The Ethernet MAC 2620B connects the regulation layer 310B to the Ethernet PHY 2625 'and the Ethernet PHY 2625 connects to the 110 wired network 102. In an alternative embodiment, the AP 104 provides ip adjustments, and Figure 25 shows an example thereof. In this case, AP 104 acts as a gateway router for the users of this group of connections (as described with reference to Figure 24). In this case, the ap 104 can deliver IP datagrams to and from the UT 106. IP adjustment and connection capabilities are known in the art. Figure 27 shows, for example, the IP protocol stacks 2740 and 2750 'for UT 106 and AP 104, respectively, as described in the detailed description of integrating each instance layer below. The υτ protocol stack 2740 includes an upper layer 2710, an IP layer 2720A, an adjustment layer 31〇a, a data chain 96870.doc -14- 200525375, a road layer 320A, and a physical layer (P) 240A. The AP protocol stack 2750 includes a PHY 240B (connected to the UT PHY 240A via the RF link 120), a data link layer 320B, and a regulation layer 310B. The IP layer 2720B connects the conditioning layer 310B to the Ethernet MAC 2725, and the Ethernet MAC 2725 connects to the Ethernet PHY 2730. The Ethernet PHY 2730 is connected to 110 wired network 102. FIG. 2 illustrates an exemplary embodiment of a wireless communication device. The wireless communication device may be configured as an access point 104 or a user terminal 106. Figure 2 illustrates the configuration of the access point 104. The transceiver 210 receives and transmits on the connection 110 according to the physical layer requirements of the network 102. Data received from or transmitted to a device or application connected to the network 102 is passed to the MAC processor 220. This material is referred to herein as the data stream 260. Data streams can have different characteristics and require different processing methods depending on the type of application to which the data stream is associated. For example, video or voice is characterized by a low-latency data stream (generally, video needs more traffic than voice needs). Many data applications are less affected by latency, but may have higher data integrity requirements (ie, voice may tolerate a packet loss, and file transfers generally do not tolerate packet loss). The MAC processor 220 receives and processes the data stream 260 to transmit the data stream on the physical layer. The MAC processor 220 receives and processes the data stream 260 to transmit the data stream on the physical layer. Internal control and signaling are also transmitted between the AP and the UT. The MAC Protocol Data Unit (MAC PDU) is transmitted to the wireless LAN transceiver 240 and receives the MAC PDU from the wireless LAN transceiver 240 on the connection 270. The following explains the conversion from data streams and commands to -MAC PDUs and vice versa. The following further explains that the feedback 280 corresponding to various MAC IDs is transmitted from the physical layer (PHY) 240 to the MAC processor 220 based on each of the 96870.doc -15- 200525375 purposes. The feedback 280 may include any physical layer information, including supported channel transmission rates (including multicast and unicast channels), modulation formats, and various other parameters. In an exemplary embodiment, the adjustment layer (ADAP) and the data link control layer (DLC) are executed in the MAC processor 220. The physical layer (PHY) is implemented on the wireless LAN transceiver 240. Those skilled in the art should know that any of the various configurations can be used to divide the functions. The MAC processor 220 may perform some or all of the processing on the physical layer. A wireless LAN transceiver may include a processor for performing MAC processing or a sub-portion thereof. Any number of processors, special-purpose hardware, or a combination can be deployed. The MAC processor 220 may be a general-purpose microprocessor, a digital signal processor (DSP), or a special-purpose processor. The MAC processor 220 may be connected with special-purpose hardware (not shown in detail in the figure) for supporting various tasks. Various applications can be executed on an external processor (for example, an external computer or through a network connection), or various applications can be executed on an additional processor (not shown) in the access point 104, or Various applications can be executed on the MAC processor 220 itself. The MAC processor 220 shown in the figure is connected to a memory 255. The memory 255 can be used to store data and instructions that can execute the various procedures and methods described herein. Those skilled in the art should know that the memory 255 may be composed of one or more types of memory components, and may be embodied in the MAC processor 220 in whole or in part. In addition to storing instructions and data capable of performing the functions described herein, memory 255 can also be used to store data associated with various queues (as described in detail in 96870.doc -16- 200525375 below). The memory 255 may include a UT proxy queue (as described below). The wireless LAN transceiver 240 may be any type of transceiver. In an exemplary embodiment, the wireless LAN transceiver 240 is an OFDM transceiver that can operate with a MIMO or MISO interface. OFDM, MIMO and MISO are techniques known to those skilled in the art. The joint application U.S. Patent Application No. 10 / 650,295 filed on August 27, 2003, entitled "FREQUENCY-INDEPENDENT SPATIAL-PROCIESSING FOR WIDEBAND MISO AND ΜΜΟ SYSTEMS" details various OFDM, MIMO and MISO transceivers. Assigned to the assignee of the present invention. The wireless LAN transceiver 240 shown in the figure is connected to the antenna 250 A-N. Any number of antennas can be supported in various embodiments. The antenna 250 is used for transmission and reception on the WLAN 120. The wireless LAN transceiver 240 may include a space processor connected to each antenna antenna 250. The space processor can process the data to be transmitted independently by each antenna. Examples of independent processing include channel-based evaluation, feedback from the UT, channel reversal, or various other techniques known in the art. This processing is performed using various known spatial processing techniques. Various types of transceivers of this type may use beam forming, beam steering, eigen-steering, or other space technologies to increase the transmission and reception throughput of a given user terminal. In a specific embodiment for transmitting OFDM symbols, the spatial processor may include multiple subspace processors for processing each OFDM subchannel or frequency bin. 0 96870.doc 17 200525375 In a demonstration In a sexual system, an AP may have N antennas, and an exemplary υτ may have M antennas. Therefore, there are M × N paths between the antenna of the AP and the antenna of the UT. Various space technologies using these multiple paths to improve throughput are known in the art. The negative material transmitted in the Space Time Transmit Diversity (STTD) system (also referred to herein as r diversity) is formatted, coded, and treated as a single, data stream using all antennas for transmission. Using M transmitting antennas and N receiving antennas, it is possible to form MI (M, N) independent channels. Spatial multiplexing utilizes these independent paths, and different data can be transmitted on each independent path. Various techniques for learning or adjusting channel characteristics between AP and UT are known to me. A unique preamble can be transmitted from each transmission antenna. These preambles can be received and measured on each receive antenna. Channel feedback can then be passed back to the transmitting device for use during transmission. Channel reversal is a technology that allows preprocessing and transmission, but it is computationally intensive. Eigen decomposition can be performed, and lookup tables can be used to determine the transmission rate. To avoid channel decomposition, an alternative technique uses leading feature import to simplify spatial processing. Pre-distortion (pre- (jistortion) technology is a known technology used to simplify receiver processing. Therefore, according to the current channel conditions, the entire system can provide different data transmission rates for transmission to various user terminals. Specifically In terms of performance, the performance of a particular link between the AP and each UT may be higher than the performance of more than one link that can be shared by υτ. The examples are further detailed below. The wireless LAN transceiver 240 may The spatial processing used by the physical link determines the supportable transmission rate. This information can be fed back on connection 280, 96870.doc -18- 200525375 for use in MAC processing, as described in detail below. Several antennas are deployed based on the data needs of the UT. For example, a high-definition video display may include, for example, four antennas based on high-bandwidth requirements, while a PDA may use two antennas. An exemplary access point may have Four antennas. The user terminal 106 can be deployed in a manner similar to the access point 104 shown in Figure 2. If the data stream 260 is not connected to a LAN transceiver (although the UT may include (Wireless or wireless transceiver), the data stream 260 is typically received or passed to one or more applications or processes running on the UT or a device connected to the UT. The higher-level connection to the AP 104 or UT 106 may be Any type. The items described in this article are just examples. Protocol Stack Figure 3 shows an exemplary subnet protocol stack 300. The subnet protocol stack 300 can be regarded as a LAN entity layer and network between very high bit rates. Interface between the MAC layer of the circuit layer or other networks (for example, the Ethernet MAc layer or the TCP / IP network layer). Various characteristic protocol stacks can be deployed to make full use of extremely efficient wireless LAN physical layer. The exemplary protocol stack can be designed to provide various advantages, examples include ... (a) Minimizing the throughput load consumed by the protocol; (b) Maximizing the encapsulation subnet data unit to become the physical layer Frame efficiency; (c) Minimizing end-to-end round-trip transmission delay caused by delay-sensitive transmission mechanisms (eg, TCp); (d) Providing highly reliable, sequential delivery of subnet lean units ; (E) provide support for existing networks Layers and applications, and provide full flexibility to adapt to future networks and applications; and seamless integration of existing network technologies. 96870.doc -19- 200525375 The protocol stack 300 has several thin sublayers, several modes of operation, and Facility for supporting interfaces of multiple external networks. Figure 3 shows the regulation layer 3o0, the data link control layer 320, and the physical layer 240. A layer manager 38o is interconnected to each sublayer to provide various The communication and control of functions are described below. Figure 3 illustrates an exemplary protocol stack 300 configuration. The dashed lines indicate exemplary configurations of components that can be deployed in the mac processor 220, as described above. Including the adjustment layer 310, the data link control layer 320, and the layer administrator 38. As described above, in this configuration, the physical layer 240 receives and transmits MAC protocol data units (PDUs) on the connection 270. The feedback connection 280 is directed to the layer manager "ο in order to provide physical layer information for use in the various functions described below. This example is merely illustrative. Those skilled in the art should understand that in this Within the scope of the invention, any number of components can be deployed and configured to include any combination of the described stacking functions. The adjustment layer 310 provides an interface to higher layers. For example, the adjustment layer can interface to the IP stack (for IP Conditioning), Ethernet mac (for Ethernet conditioning), or various other network layers. The data stream 260 may be received from one or more higher layers for MAC processing and transmitted on the physical layer 240. Data Stream 26 can also be received, processed, and recombined through the trajectory layer for delivery to one or more higher layers. The adjustment layer 3 10 includes the following functions: segmentation and reassembly 3 12, stream classification 3 14 and multicast mapping 3 16. Data stream classification function 3 丨 4 Check header packets (from data stream 260) received from the souther layer, map each packet to a user terminal or a multicast group MAC identifier (MAC ID ) And base Packets are classified based on quality of service (QoS) differential treatment. Multicast mapping function 96870.doc -20- 200525375 316 decides whether to use multicast MAC ID (called "MAC layer multicast") to transmit multicast usage Data, or transmitting multicast user data through multiple unicast MAC IDs (referred to as "Adjustment Layer Multicast"), examples are described in detail below. Segmentation and Reassembly (SAR) Function 3 12 Adjusts each higher-layer packet to become a protocol data unit (PDU) size suitable for Logical Link (LL) mode. The SAR function 312 is performed individually for each MAC ID. The data stream classification function 314 is a common function. The data link control layer 320 includes a logical link (LL) layer 330, a radio link control (RLC) layer 340, a system configuration control 3 50, a MUX function 360, and a common MAC function 370. The sub-blocks of each of these layers are shown in Figure 3 and will be described in detail below. The blocks shown in the figure are only examples. A subset of their functions and additional functions may be deployed in alternative embodiments. The physical layer 240 may be any type of physical layer, as described in the examples described above. An exemplary embodiment uses a MIMO OFDM physical layer. The following description contains exemplary parameters of this specific embodiment. The layer manager 380 (LM) interfaces with the adjustment layer 310, the data link control layer 320, and the physical layer 240 to manage QoS, admission control, and physical layer transmitter and receiver parameter control. Note that feedback from the physical layer 280 can be used in performing the functions described in this article. For example, in multicast mapping 316 or split and recombine 312, supported transmission rates applicable to various UTs can be used. Adjustment layer Data stream classification (FLCL) function 3 14 Checks the packet header 96870.doc -21-200525375 of the incoming packet, and maps it into a data stream. In the exemplary embodiment of performing IP adjustment, the following fields can be used for data flow classification: (a) IP source address and destination address; (b) IP source port and destination port; (c) IP DiffServ Code Point (DSCP; IP DiffServ code indicator); (d) Resource Reservation Protocol (RSVP) messages; and (e) Real-time Transport Control Protocol (RTC) messages and Real-time Transport Protocol (Real-time Transport Control Protocol) -time Transport Protocol; RTP) header. In an exemplary embodiment for performing Ethernet tuning, data flow classification may use 802.lp and 802.1q header fields. Ethernet traffic can also be classified using IP traffic, but this will cause layer violations. Those skilled in the art should understand that various other types of data stream classification can be deployed as alternatives. FLCL 314 determines whether an identified data stream 260 is mapped to an existing MAC ID, Logical Link (LL) mode, and data stream ID (as described in detail below). If the incoming packet is mapped to an existing data stream, FLCL forwards the packet for further processing to the segmentation and reassembly (SAR) function 3 12. If a new MAC ID is requested, a request is forwarded to the association control function 344 in radio link control (RLC) 340. If a new data stream with an existing MAC ID is identified, the QoS manager function 382 in the layer manager 380 determines the type of logical link mode required for the data stream. If a new LL mode is initialized, the request is forwarded to the LLC function 338 corresponding to the MAC ID in order to handle the mode negotiation. If a new data stream is built into the existing LL model, the request will be transferred to the LLC function 3 38. The joint application filed on November 26, 2003, US Patent 96870.doc -22- 200525375 Application No. 1 〇 / 723,346 entitled "QUALITY OF SERVICE SCHEDULER FOR A WIRELESS NETWORK" details the specific embodiment of maintaining the QoS queue, and this patent has been assigned to the assignee of the present invention. In the case of IP or Ethernet multicasting, the multicast mapping function 316 determines whether to map the packet to a multicast MAC ID in order to process the packet using MAC layer multicasting, or whether to process the packet. Processing becomes multiple unicast transmissions (referred to herein as "Adaptation Layer Multicast". If the packet is to be processed into multiple unicast transmissions, the multicast mapping function 3 16 will copy Multiple copies of the packet (each copy is used for each unicast MAC ID where the packet is to be transmitted) and forwarded to the segmentation and reassembly (SAR) function 3 12. Refer to the figure below 15 to Figure 16 to explain this aspect in detail. As described in the previous paragraph, the data flow classification function 3 14 maps a packet to a MAC ID, LL mode and data flow ID (if any). Segmentation and reassembly function 3 12 Divides higher-layer packets (ie, IP data elements or Ethernet frames) into multiple segments suitable for transmission over a logical link mode. Details will be described below with reference to FIGS. 17 to 18 The demonstration of this aspect In this example, a one-tuple adjustment layer header for each segment is added to allow the segments to be reorganized when they are sequentially passed to the corresponding SAR function in the receiver. Then, the adjustments Layer protocol data unit (PDU) is passed to the data link control layer 320 for processing in accordance with the classification parameters: MAC ID, LL mode and data flow ID. Data link control layer Figure 4 shows user data traveling through each layer Packet 410 (ie, IP data 96870.doc -23- 200525375 yuan, Ethernet frame or other packet). In this illustration, the exemplary field size and type will be described. Those familiar with this technology should understand Various other sizes, types, and configurations are considered to be within the scope of the present invention. As shown in the figure, the data packet 410 is divided into fragments at the adjustment layer 310. Each adjustment sub-layer PDU 430 carries its own fragment 420 In this example, the data packet 410 is divided into N fragments 420A-N. A conditioning sub-layer PDU 430 includes a packet payload 434 containing a corresponding fragment 420. A type field 432 (in this example In one Bytes) are attached to the conditioning sub-layer PDU 430. At the logical link (LL) layer 330, an LL header 442 (4 bytes in this example) is attached to the conditioning sub-layer containing the conditioning sub-layer. The packet carrying 434 of PDU 430. Exemplary information of the LL header 442 includes a data flow identification item, control information and serial number. The header 442 and the packet carrying 444 are used to calculate and append a CRC 446, thereby forming a Logical link sub-layer PDU (LL PDU) 440. In a similar manner, logical link control (LLC) 338 and radio link control (RLC) 340 (described in detail below) constitute LLC PDUs and RLC PDUs. LL PDU 440 and LLC PDU and RLC PDU are all placed in a queue (ie, a high QoS queue 362, a best effort queue 364, or a control message queue 366) to be served by the MUX function 360 . The MUX function 360 attaches a MUX header 452 to each LL PDU 440. An exemplary MUX header 452 may include a length and a type (in this example, the header 452 is 2 bytes). A similar header can be formed for each control PDU (ie, LLC PDU and RLC PDU). The LL PDU 440 (or, LLC or RLC PDU) constitutes a packet bearer 454. The header 452 and the packet bearer 454 96870.doc -24- 200525375 constitute the MUX sub-layer PDU (MPDU) 450 (MUX sub-layer PDU is also referred to as MUX PDU in this article). The MAC protocol allocates communication resources on the shared media in a series of MAC frames. The MAC scheduler 376 determines the physical layer burst size configured for one or more MAC IDs in each MAC frame (labeled as MAC frame f, where f indicates a certain special MAC frame). Please note that not all MAC IDs containing the data to be transmitted will be allocated in the space of any particular MAC frame. Any access control or scheduling mechanism can be deployed and is within the scope of the present invention. When performing a configuration operation for a MAC ID, the MUX function 360 corresponding to the MAC ID will constitute a MAC PDU 460, which includes one or more MUX PDUs 450 to be included in the MAC frame f. One or more MAC PDUs 460 of one or more configured MAC IDs are included in a MAC frame (ie, MAC frame 500 described in detail below with reference to FIG. 5). In an exemplary embodiment, an aspect allows transmission of a local MPDU 450, thereby allowing efficient packaging in a MAC PDU 460. This aspect will be explained in detail below. In this example, MUX function 360 maintains an untransmitted byte count of any local MPDU 450 left over from a previous transmission (identified by local MPDU 464). Their bytes 464 are transmitted before any new PDUs 466 (ie, LL PDUs or control PDUs) in the current frame. The header 462 (2 bytes in this example) includes a MUX indicator to point to the beginning of the first new MPDU (MPDU 466A in this example) to be transmitted in the current frame. The header 462 may also include a MAC address. MAC PDU 460 includes the MUX indicator 462, a possible local MUX PDU 464 at the beginning (left from the previous configuration), followed by zero or 96870.doc • 25-200525375 multiple full MUX PDUs 466A-N and A possible local MUX PDU 468 (from the current configuration) or other padding used to fill the configured portion of the physical layer burst. MAC PDU 460 is carried in the physical layer burst that has been configured for the MAC ID. Common MAC, MAC Frame, and Transmission Channel FIG. 5 illustrates an exemplary MAC frame 500. The common MAC function 370 manages the MAC frame 500 configuration between the following transmission channel segments. Broadcast, control, forward and reverse traffic (referred to as download link phase and upload link phase, respectively), and random access. The MAC frame function 372 can use various components to form a frame, which will be described in detail below. Exemplary functions, encoding, and transmission channel duration are detailed below. In this exemplary embodiment, time division duplex processing (TDD) —MAC frame is performed within a time interval of 2 ms (milliseconds). The MAC frame 500 is divided into five transmission channels (appearing in the order of 5 10-550 shown in the figure). Alternative sequences and different frame sizes can be deployed in alternative embodiments. The duration of the MAC frame 500 configuration can be quantized into a small common time interval. In an exemplary embodiment, quantization is performed in units of 800 ns (nanoseconds, which is also the cyclic prefix duration of short or long OFDM symbols, which will be described in detail below). Duration of MAC frame 500 configuration. The short OFDM symbol is 4.0 (microseconds) or 5 times 800 ns. The exemplary MAC provides five transmission channels in one MAC frame ... (a) Broadcast Channel (BCH) 510 for carrying Broadcast Control Channel (BCCH); (b) Control Channel (Control 96870.doc • 26- 200525375

Channel; CCH) 520, used to upload Frame Control Channel (FCCH) and Random Access Feedback Channel (RFCH); (c) Traffic Channel (Traffic Channel) TCH), which is used to carry user data and control information, and is subdivided into forward traffic channels (F0fWai> d Traffic Channel; F-TCH) 530 on the forward link, and (ii) reverse Reverse Traffic Channel (R-TCH) 540 on the link; and (d) random; #Random Access Channel (RCH) 550, used to carry the Access Request Channel (ARCH) ) (For UT access requirements). A pilot beacon is also transmitted in segment 510. The frame 500 of the download link phase includes fragments 510-530. The upload link phase includes fragments 540-550. Segment 560 indicates the start of a subsequent MAC frame. Broadcast Channel (BCH) The AP transmits the broadcast channel (BCH) and the pilot signal 510. The first part of BCH 510 contains common physical layer overhead, such as preamble signals, including timing and frequency acquisition preambles. In an exemplary embodiment, the pilot signal (beacon) is composed of the following two short OFDM symbols used by the UT for frequency and timing acquisition; followed by a common MIM used to evaluate the channel The leading 8 short OFDM symbols. The second part of BCH 5 10 is the data part. The BCH data section defines the MAC frame configuration for transmission channel segments: CCH 520, F_TCH 530, R-TCH 540, and rch 550, and also defines the CCH combination for subchannels. In this example, BCH 5 10 defines the coverage of wireless LAN 120, 96870.doc -27- 200525375 and will be transmitted in most of the rugged data transmission modes available. The length of the entire BCH is fixed. In an exemplary embodiment, the BCH defines the coverage of MIMO-WLAN and uses Binary Phase Shift Keying (BPSK) at a ratio of 1/4 yards in space time transmission diversity (Space Time Transmit Diversity; STTD) mode. In this example, the length of the BCH is fixed at 10 short OFDM symbols. Control Channel (CCH) Control Channel (CCH) 520 is transmitted by the AP and defines the combination of the remaining items of the MAC frame. The control channel function 374 of the common MAC function 370 generates a CCH. Exemplary specific embodiments of the CCH are described in detail below. The CCH 520 is transmitted in multiple sub-channels using a high-rugged transmission mode, each with a different data transmission rate. The first subchannel is the strongest and is expected to be decoded by all UTs. In an exemplary embodiment, a 1/4 code bpsk is used for the first CCH subchannel. Several other sub-channels can also be used, and the robustness of their sub-channels will diminish (and the efficiency will increase). In an exemplary embodiment, at most three additional subchannels will be used. Each UT will try to decode all subchannels in sequence until the decoding fails. The C C Η transmission channel segment of each frame is of variable length, and the length depends on the number of CCH messages in each sub-channel. Acknowledgment of reverse link random access bursts will be uploaded on the strongest (first) subchannel of cch. CC Η includes physical layer burst assignments for forward and reverse links. Assignments may be used to transfer data on the forward or reverse bond. Generally 96870.doc -28- 200525375 and Lu, a physical layer burst assignment includes ... (a) _MAC ID; (b) one is used to refer to the value of the configuration start time (in F-TCH or R_TCH) ); (C) the length of the configuration; ⑷ the length of the item added to the dedicated entity layer; ⑷ the transmission mode, ·, and (f) the encoding and modulation mechanism used for the entity layer burst. A MACID identification, a single υτ for multiple unicast transmissions or a set of UTs for multicast transmissions. In this exemplary embodiment, a unique broadcast MAC ID is also assigned for transmission to all UTs. In an exemplary embodiment, the penetration layer add-on includes a MIMO preamble composed of 0, 4 or 8 short OFDM symbols. In this example, the transmission mode is STTD or spatial multiplexing. Other exemplary types of assignments related to CCH include: an assignment related to the reverse key path for the dedicated input V from -υτ; or an assignment related to the υτ The assignment of a reverse link that transmits a buffer and link state information. The CCH can also define the unused portion of the frame. υτ can use their unused portions of the frame to perform noise floor (and interference) assessments and to measure pilot signals from nearby systems. The exemplary implementation of the control channel will be described in detail below. Example 0 Random Access Channel (RCH) Random Access Channel (RCH) 550 is a reverse link channel that the UT can use to transmit a random access cluster. The variable-length rch of each frame will be specified in the RCH. In an exemplary embodiment, the main characteristic mode (eigenmode) of the ratio 1/4 code BPSK will be used to transmit random access bursts. In this exemplary embodiment, two types of random access clusters are defined. A sliding correlator must be used to detect 96870.doc -29 · 200525375 When accessing the start of a burst, υτ will use a long burst for initial access. Once the UT registers with an AP, both ends of the link will complete a timing adjustment procedure. After timing adjustment, the UT can transmit its random access bursts by synchronizing with the time slot timing on the RCH. The UT then uses a short burst for random access. In an exemplary embodiment, a long burst is 4 short OFDM symbols, and a short burst is 2 short OFDM symbols. Forward Traffic Channel (F-TCH) The Forward Traffic Channel (F-TCH) 530 includes one or more physical layer bursts transmitted from the AP 104. Each burst will be directed to a special MAC ID in accordance with the instructions in the CCH assignment. Each burst includes a dedicated physical layer addition (for example, a preamble signal, if any), and a MAC PDU transmitted in accordance with the transmission mode and the coding and modulation mechanism indicated in the CCH assignment. F-TCH is of variable length. In an exemplary embodiment, the dedicated entity layer addition may include a dedicated MIMO preamble. In an exemplary embodiment, in the STTD mode, the performance of a spatial diversity channel of the same level will be 12 bits per short OFDM symbol (the ratio of 48 tones 1/2 code RPSK ) And 1344 bits per long OFDM symbol (a ratio of 192 tones of 7/8 codes 256 QAM). This translates to a factor of 33 (or 3-99 Mbps in this example) within the range of the peak physical layer data rate.

In this example, a spatial multiplexing mode of one to four parallel spatial channels may be used. Each spatial channel uses an appropriate coding and modulation mechanism. Its efficiency is between 12 bits per short OFDM symbol and 1344 bits per long OFDM 96870.doc -30- 200525375 symbol. Therefore, the peak physical layer data rate in the spatial multiplexing mode is between 3 and 395 Mbps. Due to space processing constraints, 'not all parallel spatial channels can operate at maximum efficiency', the most practical limit on peak physical layer data transfer rate is probably 240 Mbps, which in this example is between the lowest transfer rate and the highest 80 factor between transmission rates. Reverse Traffic Channel (R-TCH) The Reverse Traffic Channel (R-TCH) 540 includes a physical layer burst transmission transmitted from one or more UTs 106. According to the instructions in the CCH assignment, each burst is transmitted by a special UT. Each burst includes a preamble leading item

(pilot preamble), if any, and a MAC PDU transmitted in accordance with the transmission mode and the coding and modulation mechanism indicated in the ccH assignment. R-TCH is of variable length. In an exemplary embodiment, like F_Tch, the data transmission rate range in the STTD mode is 3 to 98 Mbps, and the data transmission rate range in the space multiplex mode is 3 to 395 Mbps, perhaps 240 Mbps is the most Practical limitations. In this exemplary embodiment, F-TCH 530, R-TCH 540, or both can use spatial multiplexing or code division multidirectional proximity technology, thereby allowing simultaneous transmission of MAC PDUs associated with different UTs. A field containing the MAC ID associated with the MAC PDU (ie, the sender on the upload link, or the intended recipient on the download link) can be included in the MAC PDU header. This field can be used to resolve the ambiguity of addressing semantics caused when using spatial multiplexing or CDMA. In an alternative embodiment, if the multiplexing system is strictly based on time-sharing technology, the addressing is included in the CCH message for a specific MAC ID in a MAC slot configured with a given time slot 96870.doc -31-200525375 Information 'so M AC ID is not needed in the MAC PDU header. Space multiplexing, code division multiplexing, time division multiplexing, and any other technique known in the art can be deployed. During the initial registration, each active UT is assigned a MAC ID. MAC ID assignment is handled by the Association Control (AC) function 344 of the RLC 340. A unique MAC ID is configured for broadcast transmissions on the forward link. Broadcast transmission is part of the Forward TransPort channel (F-TCH) and is assigned using the control channel (CCH) by using a unique broadcast MAC ID. In this example, a broadcast MAC ID configuration is used, and a system identification message is broadcasted every 16 frames. User information broadcasts can also use broadcast MAC IDs. A set of one or more MAC IDs can be configured for broadcast transmission on the forward link. The multicast transmission is part of the F-TCH 'and will be assigned using the CCH by using a specific multicast MAC ID assigned to a specific multicast group. A MAC ID is assigned to the group 111. The group is processed by the association control (AC) function 344 of the RLC 340. The common MAC 370 shown in FIG. 3 will now be explained again. The random 1 access control function 378 located at the AP processes the access burst authentication from the user. Along with # approval, the AP must immediately perform R-TCH configuration in order to obtain buffer status information from the UT. This request is forwarded to the scheduler 376. At UT, a random access manager decides when to transmit an access burst based on the data U in its MUX queue and its existing configuration. When the UT has a periodic configuration due to the existing LL connection, the existing R-TCH configuration can be used to provide burst status information. 96870.doc -32- 200525375 According to the information contained in the buffer and link status message received from υτ, the corresponding MUX function 360 located at AP will update the UT proxy server. The UT proxy server maintains the MUX function buffer status of the UT, and the scheduler 376 uses them to perform R-TCH configuration. The UT proxy server also maintains the maximum transmission rate from the AP to the UT on the F-TCH. The common MAC function 370 at the AP implements the scheduler 376 to arbitrate the configuration between the UTs while using each MAC frame with high efficiency. In order to limit the additions, a physical layer cluster is not configured for all active UTs in each frame. The scheduler 376 can use the following information to configure each MAC frame: 1. The nominal configuration of each MAC ID. It is possible that in any frame only a subset of the active UTs will be assigned a nominal configuration. For example, only every other frame or every fourth frame, etc. will provide a nominal configuration for some UTs. The nominal configuration is determined by the admission control function 384 in the layer administrator 380. In an exemplary embodiment, a nominal configuration is made in terms of the number of OFDM symbols. 2. Dedicated entity layer addition (for example, preamble signal) configuration. The Radio Resource Control (RRC) 342 in RLC 340 determines the necessary length and periodicity of the dedicated entity layer addition. In an exemplary embodiment, the dedicated entity layer addition includes a dedicated MIMO preamble. 3. Transmission mode and transmission rate. This is determined by RRC 342 for R_TCH and provided to scheduler 376. For F-TCH, this information is obtained from the UT's link and buffer status information, and is maintained on the UT proxy 96870.doc -33- 200525375. 4. Backlog of each MAC ID. The scheduler 376 can obtain this information from the following items: the MUX function 360 for each MAC ID of the forward link; and the UT proxy server for the reverse link. In addition, the scheduler configures the duration of the RCH and determines the duration of the CCH. Each assignment is transmitted on the CCH using one of the four encoding mechanisms (depending on the channel quality of the UT). Therefore, the duration of the CCH is a function of the number of assignments and the encoding mechanism used to transmit each assignment. According to the configuration determined by the scheduler, the MAC entity located at the AP will populate each assigned parameter in order to construct the BCH and CCH. The BCH defines the MAC frame configuration on the transmission channel segments: CCH, F-TCH, R-TCH, and RCH, and also defines the CCH combination on the sub-channels, as described above with reference to FIG. 5. Exemplary CCH is detailed below. In an exemplary embodiment, each assignment is transmitted on the CCH in one of up to four subchannels (each subchannel uses a different encoding and modulation mechanism depending on the channel quality of the UT). Multicast and broadcast assignments are transmitted using the strongest encoding mechanism (the first subchannel or subfragment). The MAC entity located on the UT reads the CCH in order to determine the forward link and reverse link configuration for the frame itself. At the transmitter, the MAC function transmits the MAC PDU associated with the specific MAC ID on the F-TCH (located at the AP) or R-TCH (located at the UT) to the physical layer of a specific MAC ID. At the receiver, the MAC function retrieves the MAC PDU corresponding to a MAC ID according to the CCH assignment and passes it to the MUX function of the MAC ID. 96870.doc -34- 200525375

MUX Hereinafter, the MUX function 360 will be described in detail with reference to FIGS. 19 to 23. At the receiver, the MUX function retrieves the PDU from a byte stream consisting of consecutive MAC PDUs and delivers it to the associated LL, LLC, or RLC entity. The path selection is based on the type field (logical channel) contained in the MUX PDU header. Radio Link Control (RLC) During system initialization, a radio link control (RLC) function 340 consisting of a system identification control function 346 is initialized. When the UT uses the MAC ID from the access pool to initiate access to the system, the RLC function assigns a new MAC ID to the UT. Then, if the UT joins a multicast group, it can be configured with an additional multicast MAC ID. When a new MAC ID is assigned to a UT, the RLC function initializes an instance of each of the following functions: Association Control (AC) Function 344, Radio Resource Control (RRC) 342, and Logical Link Control (LLC) ) 338. When a new multicast MAC ID is assigned, the RLC function initializes a new AC instance and an LLC for the LL multicast mode. In this exemplary embodiment, the AP uses a broadcast MAC ID to transmit a system identification parameter message every 16 MAC frames. The system identification parameter message contains the network and AP ID and the protocol version number. In addition, the system identification parameter message also contains a list of access MAC IDs used by the UT initial access system. The AC function 344 (a) provides UT authentication; (b) manages the registration (attach / detach) function of the UT (as for the multicast MAC ID, the AC function will manage the multicast 96870.doc -35- 200525375 group Attach / detach; and (c) Encryption key exchange for LL. An RRC instance 342 will be initialized at each UT. At the AP, one UT- RRC execution per role will be initialized. Individuals. RRC functions located at AP and UT can share forward and reverse link channel metrics (if required). RRC (a) manages the calibration of transmission and receive chains at AP and UT (spatial multiplexing) The transmission mode may require this calibration); (b) determine the transmission mode and transmission rate control for transmission to the UT, and provide the decision result to the MAC scheduler 376; (c) determine the dedicated entity layer additions (such as , The dedicated preamble required for the physical layer burst transmission on the R-TCH and the F-TCH) periodicity and length; (d) manage the power control of the transmission to and from a UT, and provide the power control To the PHY administrator; and (e) determine the timing adjustments for the R-TCH transmission from the UT. Link (LL) A conditioning layer PDU composed of user data fragments is provided to the DLC layer 320 along with the associated MAC ID, LL mode, and data flow ID (if any). The LL mode function 330 adds an LL Header and a 3-byte CRC calculated using the entire LL PDU. Several modes are supported in the exemplary embodiment. The approval 336 and negative approval 334 functions can be deployed. Accessible broadcast / multiple can also be deployed On-demand / unicast function 332. Based on the illustration, the four LL modes are listed below (Figure 23 details the mode format details in the MUX PDU). 1. Non-connection negative approval mode (mode 0). In In this case, the LL header is null. This mode can be used to transfer regulatory layer PDUs without obstacles. 96870.doc -36 · 200525375 LL mode 0 can implement the policy. Broadcast and multicast Sending the MAC ID only provides a non-connected negative acknowledgement (accessibility) mode. 2. A non-connected acknowledgement mode (mode 1). This mode is used to transmit PDUs at the regulation layer and does not need to be associated with the LL mode 3 connection. Built-in additions and delays. LL Mode 1 header includes The sequence number of the LL PDU that is lost, or the sequence number of the recognized PDU, because the modulation layer channel is expected to operate with a low random LL PDU loss probability mode and a low round-trip delay mode, so a simple Go-Back-N ARQ mechanism 3. Connection-oriented negative approval mode (mode 2). LL connection-oriented negative approval mode allows multiple data streams to be multiplexed by using a data stream ID. LL mode 2 can implement the principle of each data stream ID. The LL mode 2 header packet contains the data stream ID and 12-bit serial number. 4. Connection-oriented approval mode (mode 3). LL connection-oriented approval mode allows multiple data streams to be multiplexed by using a stream ID. LL mode 3 can implement the principle of each data stream ID. The LL Mode 3 header consists of a stream ID used to identify multiple streams transmitted over a reliable connection. A 12-bit sequence number identifies the LL PDU, and an ACK bit indicates the highest received sequence number. As discussed in LL mode 1, since the adjustment layer channel is expected to operate in a low random LL PDU loss possibility mode and a low round-trip delay mode, a simple Go-Back-N ARQ mechanism is used. However, a selective repeating ARQ mechanism can also be used. A logical link control (LLC) function 338 manages logical link mode control. When establishing a new LL mode, the LLC function provides mode negotiation, including: (a) QoS · guaranteed transmission rate; (b) mode setting; (c) mode deletion (mode 96870.doc -37- 200525375 teardown ); (e) mode reset; (f) assignment of data stream ID in LL modes 2 and 3. The mapping of the end-to-end data stream to an LL mode is determined by the QoS manager function 382 in the layer manager 38. The requirements for initializing a new ll mode or adding a data stream to an existing LL mode come from the adjustment layer 3 10, as described above. The system configuration control 350 manages the configuration of the TDD MAC frame, including the boot signal (Beacon), the content of the BCH, and the length of the RCH. Layer manager

QoS manager 382 interprets network QoS protocols, including RSVP and RTCP. If QoS is based on the traffic classification of the IP header, the QOS administrator will decide which traffic classifier to use to identify the different services (ie, IP source and destination addresses, IP source port And destination port). The QOS administrator assists the adjustment layer by mapping the data stream to the LL mode. The admission control function 384 receives a request from the LLC to allow a new data stream with a transmission rate requirement. The admission control function maintains a database of approved nominal configurations and a set of regulations and thresholds. The admission control function determines whether a data stream can be permitted, determines the nominal configuration of the data stream (in terms of the amount of transmission time configured per m MAC frames), and provides this information to the common MAC based on thresholds and regulations Scheduler in. The physical layer administrator uses the physical layer metrics collected at the AP and UT to control the transmitter and receiver parameters of the physical layer. Remote metrics can be obtained through RRC messages. Exemplary Procedures 96870.doc -38- 200525375 WLAN 120 operation is described using several procedures based on the various layer entities described above. These programs are not exhaustive, but rather exemplify the functions and components described in this article. FIG. 6 illustrates an exemplary method 600 for transmitting a forward link message transmission from an AP. In step 610, the RLC function (association control, radio resource control, or logical link control) at the AP places a message (RLC PDU) into the control message queue. Or the LL mode at the AP places an LLPDU into a high QoS queue or a best effort queue. In step 620, the scheduler configures F_TCH resources for transmitting PDUs in the three MUX queues. In step 640, the assignment is indicated on the CCH by the MAC. At step 650, the MAC transmission located at the AP is configured to send a message in the MAC PDU in the physical layer burst. FIG. 7 illustrates an exemplary method 700 for receiving a forward link message transmission at a UT. In step 710, the UT monitors the CCH. The UT identifies a configured burst directed to the UT. In step 720, the UT retrieves the MAC PDU according to the identification in the CCH. In step 730, the UT reassembles the data stream packet, the data stream packet including the segments extracted in the MAC PDU and processed in the MAC processor. FIG. 8 illustrates an exemplary method 800 for transmitting a reverse link message from a UT. In step 810, the RLC function (association control, radio resource control, or logical link control) at the UT places a message (RLC PDU) in the control message queue. Or the LL mode at the UT places an LL PDU in a high QOS queue or a best effort queue. In decision step 820, if the UT has an existing R-TCH configuration, proceed to step 870. Otherwise, proceed to step 830. In step 830, the UT transmits a short access burst on the RCH. At step 96870.doc -39- 200525375 840, the UT receives the RCH access burst approval and access grant configuration on the CCH. In step 850, the UT transmits a link and buffer status message to the AP. At step 860, the UT monitors whether the CCH has an R-TCH grant configuration. In step 870, a configuration is received (or already exists in decision step 820). The UT composes the MUX PDU into a frame to become a MAC PDU, and transmits the MAC PDU in the configured physical layer burst. FIG. 9 illustrates an exemplary method 900 for receiving a reverse link message transmission at an AP. In step 910, the AP receives and monitors the RCH. In step 920, the AP identifies a short access burst from the UT. At step 930, the scheduler configures an access grant. In step 940, the AP transmits acknowledgement and access grants on the CCH. In step 950, the AP receives the link and buffer status messages on the R-TCH in response to the access grant. In step 960, the AP uses the buffer status to update the UT proxy server. The scheduler has access to this information. In step 970, the scheduler configures R-TCH resources. In step 980, the AP receives the MAC PDU as configured. In step 990, the AP responds to one or more received MAC PDUs to perform reassembly of a data stream packet.

FIG. 10 illustrates an exemplary method 1000 for a UT to perform initial access and registration. In step 1010, the UT obtains the preamble from the frequency on the BCH to obtain the frequency and timing. In step 1020, the UT receives system identification information from the RLC broadcast message. In step 1030, the UT uses long bursts from the BCH to determine the RCH configuration for (non-time slotted) random access. In step 1040, the UT randomly selects a MAC ID from the set of starting MAC IDs. In step 1050, the UT transmits a long random access burst on the RCH using the starting MAC ID. In step 1060, the UT receives an acknowledgement, a MAC ID 96870.doc -40- 200525375 assignment in a subsequent MAC frame, and a timing adjustment. In step 1070, the association control function and the Ap association control function complete the authentication and key exchange sequence. Control message transmission on the forward and reverse links follows the low-level message transmission procedures previously described with reference to FIGS. 6 to 9. FIG. 11 illustrates an exemplary method 110 for an AP to perform initial access and registration. In step mo, the AP receives a long random access burst from υτ on the RCH. At step 112, the AP assigns a MAC ID to the vτ. The MAC ID pool is managed by the radio link control function. At step 113, Aρ assigns a timing adjustment to the UT. In step 1140, the AP transmits acknowledgement, MAC ID, and timing adjustment on the CCH. In step 1150, the AP associates the control function with 1;] [The association control function completes the authentication and key exchange sequence. Control message transmission on the forward link and reverse key path follows the low-level message transmission procedure previously described with reference to Figs. 6-9. FIG. 12 illustrates an exemplary method 120 for AP user data flow. In step 1210, the QOS administrator in the layer administrator fills the data flow classification parameters into the data flow classification function. A specific combination of parameters and values can indicate the arrival of a new data stream. Their parameters can include: IP DiffServ 〇〇 Center Point (DSCP), IP source address or IP port. Ethernet parameters can include: 802. IQ VLAN ID or 802.1 Ip priority order indication. The specific port value may indicate a control protocol message (for example, Rsvp or RTCP) to be forwarded to the QoS manager. In step 1215, the AP decides the admission parameters. When a packet arrives at the 8-1 > adjustment layer and is judged as a new data stream by the data stream classification, the data stream classification will cooperate with the administrator to determine the licensing parameters, including the need to configure 96670.doc -41-200525375 for the data stream. QoS category (high QoS or best work), LL mode and nominal transmission rate. In decision step 1220, the admission control in the tier administrator decides whether or not the data stream can be admitted based on their admission parameters. If not allowed, the program stops. Otherwise, proceed to step 1225. At step 1225, the data stream classification requires the LLC to build a new data stream. In this discussion, the case of high QoS, LL Mode 3 connection will be considered. At step 1230, the LLC located at the AP communicates with the LLC located at the UT to establish a connection (or, if an applicable connection already exists, a new stream ID is established). In this example, their LLC will attempt to establish an LL Mode 3 connection (or, if an applicable LL Mode 3 connection already exists, create a new data stream ID). At step 1235, the nominal transmission rate configured for the data stream is communicated to the scheduler. For LL mode 3, the nominal transmission rate is configured on the forward and reverse channels. In step 1240, the data stream is classified: classifying the packets of the data stream; identifying the MAC ID, LL mode, and data stream ID; implementing the data stream principle; and transmitting the conformed packets to the SAR function. At step 1245, the SAR splits the packet into fragments, and forwards the adjustment layer PDU along with the LL mode and data stream ID to the LL function of the MAC ID. At step 1250, the LL function appends the LL header and CRC, and places the LL PDU into the appropriate queue. In this example, the LL mode 3 function adds an LL header and a CRC, and places the LLPDU into the high QoS queue of the MUX. In step 1255, the MUX prepares the MUX PDU by attaching a MUX header for identifying the LL pattern and length. The MUX establishes a MUX indicator to indicate the number of bytes to the beginning of the first new MUX PDU. 96870.doc • 42- 200525375 In step 1260, the scheduler decides the F-TCH (physical layer burst) configured for the MAC ID. The scheduler knows the transmission mode (from RRC) and the transmission rate (from the UT proxy). Note that a reverse link configuration can also be included. In step 1265, the configuration is transmitted on the CCH. At step 1270, the MAC transmits a MAC PDU. The MAC PDU consists of the following: a MUX indicator, followed by a possible local MUX PDU at the beginning, followed by zero or more complete MUX PDUs, and finally a possible local at the end of the physical layer burst MUX PDU. FIG. 13 illustrates an exemplary method 1300 of a UT user data stream. At step 1310, the UT receives the configuration on the CCH. In step 1320, the UT receives the MAC PDU according to the configuration. At step 1330, the MUX located at the UT fetches the MUX PDU by using the MUX indicator and the length field in the MUX header, and prepares the LLPDU. In step 1340, the MUX transmits the LL PDU to the appropriate LL function (in this example, LL mode 3) according to the type field in the MUX header. At step 1350, LL mode 3 performs an ARQ receiver and calculates a CRC for each LL PDU. At step 1360, LL mode 3 located at the UT must transmit ACK / NAK to LL mode 3 ARQ located at the AP. The ACK / NAK is placed in a high QoS queue at UTMUX. Please note that other LL models may not include approval, as described above. In step 1370, the AP transmits the ACK / NAK on the R-TCH according to the configuration. As described above, the scheduler configures the R-TCH resource of the MAC ID according to the nominal configuration of the reverse link. ACK / NAK messages are transmitted in MAC PDUs on the reverse link entity layer burst from the UT. In step 13 80, the UT can transmit any other queued 96870.doc -43 · 200525375 reverse link data in the remaining configuration. Please refer to FIG. 3 again. As described above, the data stream 260 is received by the AP MAC processor 220, and the corresponding data and signal will go down through the adjustment layer 310, the data link control layer 32 and the physical layer. For transmission to the UT. The physical layer located at the UT 24 receives the MAC PDU, and the corresponding data and signal will travel upwards through the data link control layer 320 and the adjustment layer 3 1 0 of the UT MAC processor 220. The physical layer, the reorganized data stream system Levels to be passed to one or more higher levels (ie, various processing sequences including data, voice, video, etc.). For data streams originating from the UT and transmitted to the AP, a similar processing sequence occurs in reverse order. Individual layer managers 380 can be deployed in the AP and UT to control how information flows up and down to each MAC sublayer. In general, the layer manager 380 can use any type of feedback 28 from the physical layer 240 to perform various sub-layer functions. The physical layer manager 386 interfaces with the physical layer 240. Any function in the layer administrator (examples include the admission control function 384 and the QOS administrator 382). Their functions can then interact with any of the sub-layer functions described above. The principles described in this article can be deployed with any physical layer specification that supports multiple transport formats. For example, many physical layer formats allow multiple transmission rates. The throughput of any given physical link can be determined by available functions, channel interference, supported modulation formats, and the like. Exemplary systems include OFDM systems and cDMA systems that can use MIMO technology. In their systems, closed-loop technology is used to determine the transmission rate and format. The closed loop can use various messages or signals to indicate channel metrics, supported transmission rates, etc. Those skilled in the art can easily adapt these and other systems to deploy the technology described in this 96870.doc -44-200525375 article. The physical layer feedback can be used in the adjustment layer 3 丨 0. For example, transfer rate information can be used in segmentation and reassembly, stream classification, and multicast mapping. Figure M shows an example of incorporating the physical layer feedback into the adjustment layer function. #Method wins This method is described in terms of the access point +, but it can be applied in a similar manner to the user terminal to apply this method. The program starts from step 1410, where it receives data stream packets to be transmitted to the user terminal. At step 1420 ', the adjustment layer function is executed in response to the physical layer feedback of the respective user terminal. To further illustrate this aspect, the following will describe in detail exemplary multicast mapping and segmentation specific embodiments. At step 1440, the physical layer feedback of one or more user terminals is monitored. The process returns to step 1410 and repeats the process for the additionally received data stream packets in response to the updated entity layer feedback. . In an alternative embodiment, transmission rate information fed back from other entity layers may be used in the admission control decision process. For example, high Q0s data stream = permission is granted, unless the target MAC ID entity layer can support a sufficiently efficient transfer rate. This level can be adjusted based on the system load (including the nominal configuration of the existing data stream, the number of UTs in the P #Ware Master Book, and the like). For example, the possibility that a UT with a relative ^ and a τ akabe link is configured to a high QoS data stream is more than one target M + the MAC ID of a lower quality link. If the system is under a small load of 0 ± 4 ', the threshold requirement can be reduced. Multilayer Broadcasting at the Regulation Layer Figure 15 shows a sample method for multicast broadcasting at the regulation layer. 500%. An example of Multicast Broadcasting at the Regulation Layer, and Bianwan Law 1400 is used to incorporate the physical layer feedback 96870.doc -45-200525375 to the function of the Regulation Layer. As described above, a multicast transmission, MAC layer multicast method provides a common MAC ID corresponding to a user terminal list ′. The common or multicast MAC ID is distinguished from the user terminal MAC ID. Therefore, when a UT is assigned to one or more multicast groups, the UT will monitor whether the CCH is not only directed to its own MAC ID but also

It is also directed to the transmission of one or more multicast MAC IDs associated with this vτ. Therefore, a multicast MAC ID may be associated with one or more higher-level data streams, thereby allowing a single data stream to be transmitted to multiple user terminals. In withered layer multicast, if a single transmission for receiving by all user terminals in a multicast list is not performed, one or more additional transmissions of multicast data can be performed to their user terminals One or more user terminals in the machine. In a specific embodiment, the adjustment layer multicast performs a unicast transmission to be transmitted to each user terminal in the multicast group. In an alternative embodiment, the adjustment layer multicast can be performed using-or multiple MAC frames associated with a subset of the multicast group-or multiple MAC layer multicast transmissions. Unicast transmissions can be directed to user terminals that are not included in one of their subgroups. Any of the above mentioned, and σ can be deployed. In step 5-5, a multicast data stream directed to a list of user terminals is received. In a specific embodiment, a MAC ID is associated with the user terminal list. At step 1 520, Sister Ning found it difficult to determine the efficiency of the unicast transmission for users who are on the list. 欢 欢 疋 Whether it is for multicast transmission (that is, $ use The efficiency of the recipient receiving the early age value (j 4 ^^). If the unicast transmission is more efficient than the multicast transmission, then in step 1530, the transmission on two or more 96870.doc -46- 200525375 channels. The unicast channel may include unicast channels, combined . In decision step 1520, if a multicast MAC ID is used, it is transmitted to the members of the multicast group. Their two or more other multicast channels or the combination of the two are more efficient for multicast transmission. In a single transmission, the multicast data broadcast is generally used for multicast transmission. The format must be suitable for transmission on the weakest physical link of the user terminal physical link group rainbow in the multicast group. In some systems, since the lowest common transmission is still necessary for the mother to use the lowest quality physical link to reach the user terminal 'in fact,' it can actually benefit from higher transmission rates and larger throughput A better user terminal does not affect system throughput. As a result, in other cases, it will not remain applicable. For example, consider the use of material space processing in the system. The members of a multicast group may be scattered around the area of interest 'and two or more members will have very different channel characteristics. Consider the example of a multicast group containing two user terminals. By cooperating with the transmission format of each user terminal, it can be implemented, which is suitable for high-speed transmission of unicast transmission to each user terminal. However, because the environment of the two channels used for each physical channel is not 5 tons at all, it is palatable to use-a single multicast message is delivered to each user. The transmission volume of the transmission format of the machine may be lower than any one. On-demand channels. When the difference between the rotation volume of the multicast channel and the unicast channel is large enough, 'the system will use less resources to transmit two multicast data than to transmit and receive a single message. Resources. FIG. 161 shows an exemplary method for deciding whether to use the multi-layer broadcast of the adjustment layer or the multi-point broadcast 96870.doc -47- 200525375. This method is suitable for deployment in step 1 520. At step 1610, the link parameters of each user terminal in the multicast list are received. In a specific embodiment, a transmission rate parameter may be used. In step 1620, a link parameter of a multicast channel suitable for transmission to a user terminal in the multicast list is received. The link parameters of the multicast channel may differ from the link parameters of any and all individual channels for user terminals in the multicast group. In step 丨 63, comparing the system resource requirements for the transmission on the multicast channel (that is, a single transmission uses Multicast On Demand MAC ID) and the total system resource requirements of the individual unicast transmissions can use the table low system Resource requirements determine the most efficient choice. In an alternative specific embodiment, step 1610 may be modified to include the link parameter MAC layer multicast channel (including a subgroup of the multicast group user terminal). Compare the combination of multicast and unicast with pure MAC layer multicast. Those skilled in the art will be aware of these and other modifications of the invention. Physical layer feedback segmentation Figure 17 illustrates an exemplary method P00 for performing segmentation in response to physical layer feedback. This is another example of method 1400 for incorporating physical layer feedback to the adjustment layer functions. This procedure can be implemented in the split and reorganize function 312 in the adjustment layer 310 in order to respond to the physical layer provided by the layer administrator 380. In step 1710, a data stream packet to be transmitted to a corresponding MAC (R) is received. In step 1720, the transmission rate information corresponding to the MAC ID is retrieved. The packet is divided into fragments in step 1730 'in response to the MAC ID transmission rate. In a · 96870.doc -48- 200525375: a general embodiment, this segmentation operation will generate multiple segments 420, which are used to generate a solid sub-layer pDU 43〇, the female reference is shown in Figure 5 The description is described. Figure 1 shows an exemplary method of segmenting segments in response to the transmission rate. This method is suitable for deploying the steps described in the previous paragraph. Process = Start from decision step 1810. If the transmission rate has changed, go to the decision朿 Step 1820. If the transmission rate is not changed, the program stops and the segmentation size remains unchanged. At decision step 1820, if the transmission rate is changed to increase the round rate, it may be: a gain associated with increasing the fragment size. For example , As shown in Figure *, two = receive additions from each layer when it travels the stack of agreements. Reduce slices =! Reduce the amount of additions required. In addition, a higher transmission rate usually means that the channel is more quality. When the channel will When changing rapidly over time, the possible situation is that the Ping # # 8 车 μ _ is constant. The average value of the transmission channel is maintained relatively-the amount of time of the fragment is about the same as that of the transmission at "noon time". The percentage of the smaller segment size is proportional to the channel's tendency to maintain a relatively fixed increase in efficiency, and if it is not 1, increasing the segment size may allow the # segment size to increase. Another consideration to select a lead with disabilities, and persons more time. Transmission rate change occurred together lead ... physical layer transmission rate change

The non- # 6 in the function must be more fragment size, and the non-preemptive priority in the MUX force moon is used to preferentially take the short delay conditions from PM,, and A to constrain the demand to Figure 2; 1 service delay condition constraints, below Will refer to ㈣ 芏 circle Yu Yiping detailed description. 96870.doc -49- 200525375 Various techniques for selecting fragment sizes can be incorporated into the scope of the present invention. Please refer to FIG. 18 for a new reference. In this exemplary embodiment, in decision step 1820, when a transmission rate change occurs, it will proceed to the step to increase the adjustment sub-layer PDU size. In decision step 1820, if the transmission rate changes but the transmission rate decreases, then proceed to step 1840, in which the pDU size of the adjustment sublayer is reduced according to any of the techniques discussed in the previous paragraph. The method shown in Figure 18 is mainly used to explain a feasible mechanism for dividing using the relationship between the transmission rate of the physical layer and the size of the segment. In an alternative embodiment, a fragment size table may be generated, each fragment size being associated with a transmission rate or a range of transmission rates. In another specific example, a function may be deployed, an operand transfer rate of the function, and a fragment size table may be generated for the output of the function. According to the teaching in this article, those familiar with this technology should understand that there are other feasible solutions. Note that as described in the previous paragraph, segmentation can be combined with multicast mapping techniques (as described above with reference to Figures 14 to 16), and any other adjustment layer functions performed in response to physical layer feedback. Multiplexing In an exemplary high-efficiency wireless LAN subnet (eg, wireless network 120), all communication between the AP 104 and one or more UTs 106 occurs. As mentioned above, the nature of these communications may be unicast or multicast. In unicast communication, user data or control data is transmitted from Ap to a single UT, or from UT to AP. Each UT has a unique MAC ID, so all unicast communication systems between the UT and the AP are associated with the unique MAC ID. In multicast communication, user data or 96870.doc -50- 200525375 control data is transmitted from the AP to multiple ^^. A MAC m pool will be set up as a multicast address. There may be one or more multicast groups defined that are associated with an access point, and each group is assigned a unique multicast MAC ID. Each UT may belong to one or more of its multicast groups (or not to any group) and will receive transmissions associated with each multicast group to which it belongs. For the purpose of the multiplexing discussion, multicast at the regulatory layer is considered unicast. In this example, υτ does not transmit multicast data. An access point receives user data addressed from an external network (ie, network 〇 02) to a UT in its own coverage area, and receives user data from the UT in its own coverage area that is directed to other devices Cover user data for UTs in the area, or υτ) attached via the network. An access point may also generate, from the radio link control (RLC) function 340, the logical link control (LLC) function 330, and other entities, individual or multiple UTs intended for its coverage area. User data addressed to a single UT can be isolated into multiple data streams based on QOS considerations or other considerations (for example, source applications), as described above. As described above, in the end, the access point aggregates all data from all sources that are scheduled for a single MAC ID into a single byte data stream, and then the byte data stream is formatted into several MAC pDUs, each MAC pDUs are transmitted in a single MAC frame. The access point can transmit MAC PDUs (ie, on the forward link) with one or more MAC IDs in a single MAc frame. Likewise, the UT may have user data to be transmitted that can be isolated into several data streams. 96870.doc -51-200525375 The UT may also generate control information associated with RLC 340, LLC 330, or other entities. The UT aggregates user data and control data into a single byte data stream, and then the byte data stream is formatted into several MAC PDUs, and each MAC PDU is transmitted to the AP in a single MAC frame. One or more UTs can transmit a MAC PDU (i.e., on the reverse link) in a single MAC frame. The MUX function 360 is implemented by the MAC ID at the AP. Each UT is initially assigned a MAC ID for unicast transmissions. If the UT belongs to one or more multicast groups, an additional MAC ID may be assigned. The MUX function allows (a) to treat a continuous entity layer burst configuration allocated to a MAC ID as a one-tuple data stream; and (b) to multiplex PDUs from one or more LL or RLC entities into MAC Byte data stream. FIG. 19 illustrates an exemplary method 1900 of transmitting multiple data streams and commands in a single MAC frame. This method is suitable for deployment in access points or user terminals. The program starts with decision step 1910. If one or more packets in one or more data streams destined for a MAC ID are received, proceed to step 1920, in which a MUX associated with the MAC ID is prepared for each of the one or more data streams. PDU. In this exemplary embodiment, the MUX PDU is prepared in accordance with the MAC protocol described above, but alternative MAC protocols may be deployed within the scope of the present invention. The MUX PDU may be placed in a suitable queue (in an exemplary embodiment, a high QoS queue or an optimal working queue). If the MAC ID data stream is not received in step 1910, after the MUX PDU has been prepared in step 1920, it proceeds to decision step 1930. In decision step 1930, if one or more 96870.doc -52- 200525375 commands from RLC 340 or LLC 330 are to be transmitted to the UT associated with the MAC ID, proceed to step 1940 and prepare each command PDU. One MUX PDU. If there is no order for the MAC ID, or after the MUX PDU has been prepared in step 1940, then proceed to decision step 1950. The decision step 1950 illustrates an iterative process sequence for continuously monitoring a data stream destined for a MAC ID. Alternate embodiments may incorporate a loop function throughout the access point or any other part of the user terminal process. In an alternative embodiment, the process 1900 is repeated iteratively, or included in other iterative processing sequences. For illustration purposes only, this processing sequence is described in terms of a single MAC ID. Obviously, multiple MAC IDs can be processed simultaneously in an access point. Those skilled in the art will appreciate these and other modifications of the invention. When there is no command or data stream ready to be processed, in this example, the processing sequence loop goes back to decision step 1 910 to repeat the loop. Please note that in the user terminal, the access point must be requested to initiate a MAC frame configuration, as described above. Any such technology can be deployed. Details are not included in Figure 19. Obviously, if there is no command or data stream waiting to be transmitted, no request is required, so no MAC frame configuration will arrive. When a command or data stream is waiting for transmission, the scheduler will configure a MAC frame at any time, as described above. In this exemplary embodiment, an access point scheduler 376 performs forward link MAC frame configuration in response to the MAC ID queue in the UX-specific MUX function 360, and performs reverse link MAC. The frame is configured in response to a request for an RCH or UT proxy queue, as described above. In any case, the communication device executing method 1 900 96870.doc -53- 200525375 waits for a MAC frame configuration in decision step 1950. When a MAC frame configuration is performed in decision step 1950, one or more MUX PDUs are placed in a single MAC PDU in step 1960. The MAC PDU may include the local MUX PDU 464 remaining from the previous MAC frame, a MUX PDU from one or more data streams, one or more command MUX PDUs, or any combination thereof. If any allocated space is still unused, a local MUX PDU can be inserted into the MAC frame (or any type of padding can be inserted to fill the allocated MAC frame). At step 1970, the MAC PDU is transmitted on the physical link at the location indicated by the configuration. Please note that a MAC PDU may include a MUX PDU from any combination of one or more data streams or command PDUs. As described above, in this exemplary embodiment, on the F-TCH or R-TCH, the MAC PDU is a transmission unit that is suitable for being assigned to a physical layer of a MAC ID. FIG. 20 illustrates an exemplary case. A MAC PDU 460 consists of the following items: a MUX indicator 462, followed by a possible local MUX PDU 464 at the beginning, followed by zero or more complete MUX PDUs 466, and finally a physical layer burst A possible local MUX PDU 468 at the end. Please note that the figure shows the respective parts of two consecutive MAC frames 460A and 460B. The sub-portion of MAC frame 460 A transmitted during frame f is identified by an additional "A". The sub-portion of MAC frame 460B transmitted during frame f + 1 is identified by an additional "B". When multiple MUX PDUs are connected in a MAC PDU in series, a local MUX PDU can be transmitted at the tail end of the MAC PDU. In this case, 96870.doc -54- 200525375 will be transmitted in the next MAC frame. The beginning of the transmitted MAC PDU transmits the remainder of the MUX PDU. This is illustrated in Figure 20 by the local MUX PDU 468A transmitted in the MAC frame 460A. The remainder of the MUXPDU 464B will be transmitted during the next MAC frame 460B. The MAC header consists of MUX indicator 2020 and MAC ID 20 10 which may be associated with MAC PDU. When spatial multiplexing is being used, the MAC ID may be required and there may be more than one MAC PDU transmitted at the same time. Those familiar with this technology should know when MAC ID 2010 should be deployed, and these are shaded to indicate these options. In this exemplary embodiment, a 2-byte MUX indicator 2020 is deployed per MAC PDU in order to identify the location of any MUX PDU transmitted in the MAC frame (as shown in Figure 20 from MUX indicator 2020 to MUX PDU 466A As shown by the arrows). Each MAC PDU uses the MUX indicator 2020. The MUX pointer points to the beginning of the first MUX PDU in the MAC PDU. The MUX indicator, together with the length field contained in each MUX PDU, allows the receiver's MUX layer to extract LL and PLC PDUs from a byte data stream (consisting of a continuous physical layer configured to the MAC ID). Those skilled in the art should understand that various alternative means for deploying indicators fall within the scope of the present invention. For example, from the example described above, the MAC frames can be encapsulated in an alternative order. A local MUXPDU can be placed at the end of the MAC frame configuration, and the indicator points to the beginning of the residual, rather than to the new MUX PDU. Therefore, a new PDU (if any) is placed at the beginning. Several indexing techniques can be deployed (ie, an index value to identify a tuple, a time value, a base value plus a shift, or any number known to those skilled in the art 96870.doc -55- 200525375 more Change plan). In this exemplary embodiment, the MUX indicator 2020 includes a single 16-bit field whose value is 1 plus the end of the MUX indicator starting at the beginning of the first MUX PDU at the beginning of the frame. Offset in bytes. If the value is 0, there is no MUX PDU for the start frame. If the value is 1, the MUX PDU will start immediately after the MUX indicator. If the value is η> 1, the first η-1 bytes in the MAC PDU are the trailing end of a MUX PDU that starts at the previous frame. This information helps the receiver MUX (ie, MUX function 360) recover from previous frame errors that caused loss of synchronization to the MUX PDU boundary. Those familiar with this technology should understand that any number of alternative indexing technologies can be deployed. A MUX header containing a type (logical channel) block and a length block is appended to all LL or RLC PDUs provided to the MUX. This type (logical channel) field identifies the LL or RLC entity to which the PDU belongs. As explained in the previous paragraph, the length field is used in conjunction with the MUX indicator to allow the receiving MUX layer to retrieve LL and PLC from the byte data stream (consisting of a continuous entity layer configured to the MAC ID). PDU. As mentioned above, the MUX function 360 maintains three queues for the data to be transmitted. The high QoS queue 362 may include an LL PDU associated with a negotiated service, and the admission control function 384 has configured a guaranteed transmission rate for the negotiated service. The best working queue 364 may include LL PDUs associated with a transmission rate guarantee. The control message queue 366 may include RLC and LLC PDUs. Alternative embodiments may include more than one QOS system. However, as described in this article, the efficient use of high transmission rate WLANs allows a single QoS queue to 96870.doc -56- 200525375 to achieve excellent QoS performance. In some cases, efficient use of available channel bandwidth through the MAC protocol will provide unnecessary additional queues and associated complexity. At the AP, the backlog in each queue is made available to the scheduler 376 in the common MAC function 370. At the AP, backlogs in their queues at υτ are maintained in the UT proxy server (prOxy) of the MUX function 360. Please note that, based on conciseness and clarity, the queues of their 11 proxy servers (1) 1 ^ 7) are not shown separately in Figure 3. Queues 362, 364, and 366 can be considered to include the forward link queue and the reverse link queue for each MAC ID (ie, the UT proxy server (pr〇xy) queue), regardless of the shared fw or Are there queues for deployment in separate components? Note that the number and type of forward link queues and reverse link queues supported need not be exactly the same. The UT proxy queue need not exactly match the UT queue. For example, the UT may maintain a command queue to give priority to certain time-sensitive commands over others (^ 〇8 PDU priority order. At the AP, unidirectional QoS may be used to indicate the two types of UT traffic. Therefore, the priority determined at the UT can be used to fill the configuration of the UT. As another example, different QoS queues can be maintained at the UT or AP, and they will not be maintained at the AP or UT. Maintain the QOS queue of the other party. The scheduler 376 arbitrates the competition requirements from all MAC IDs, and configures a physical layer to send to one or more selected MAC IDs on the F-TCH or R-TCH. Respond to one item Configuration, the corresponding MUX function 36 encapsulates B and RLCpDU into MAC PDU packet bearers' as described above. In this exemplary embodiment, each MUX function 360 will be in the following non-preemptive priority order 96870. doc -57- 200525375 (completely) servos PDUs from the following queues: control message queues 366, high QoS queues 362, and best working queues 364. Before new PDUs from higher priority queues are servoed, Complete any part from previous MAC PDU first PDU (even if the local PDU is from a lower priority queue). In alternative embodiments, preemptive priority may be deployed at one or more levels, as known to those skilled in the art. At the receiver The MUX function retrieves PDUs from a byte stream composed of consecutive MAC PDUs and sends them to the LL or RLC entity to which they belong. The path selection is based on the type field (logical in the MUX PDU header) Channel) as the basis. In this exemplary embodiment, according to the design of the MUX function, once a MUX PDU has started to be transmitted, this transmission will be completed before another MUX PDU can be started. Therefore, if a MAC message Frame to start transmitting a MUX PDU from the best working queue, it will complete this transmission in a subsequent MAC frame (or multiple frames) before transmitting from the control message queue or high QoS queue Other MUX PDUs. In other words, in normal operation, higher class queues have non-preemptive priority. In alternative embodiments, or in this exemplary embodiment, in some cases, one may want to Preemption Priority. For example, if the data rate of the physical layer has changed, it may be necessary to urgently transmit a control message, which needs to take precedence over the best work or high-QoS MUXPDUs. This is a permitted practice. Receive The party MUX will detect and discard incompletely transmitted MUX PDUs, which will be described in further detail below. Preemptive events (that is, changes in the transmission rate of the physical layer) can also cause changes that need to be made. 96870.doc -58- 200525375 This υτ is used by Fragment size. The fragment size used by υτ can be selected to enable non-preemptive priority in the MUX function to satisfy the minimum delay condition constraint or the service delay condition constraint of the control message queue. These techniques may be combined with the segmentation techniques explained above with reference to Figs. FIG. 21 illustrates an exemplary method for preparing a MAC frame using a MUX indicator. 2100 This method can be deployed in an AP or UT. As taught in this article, those skilled in the art can easily adapt this illustrative example to fit many specific embodiments (AP or UT). The procedure starts at step 2110, where the configuration for a MAC PDU is received. In decision step 2120, if the local MUx PDU from the previous MAC frame still exists, proceed to decision step 213. If no local Mux PDU exists, proceed to step 2150. In decision step 2130, if preemptive priority is desired, the local MUXPDU is not transmitted. The program proceeds to step 215. In this exemplary embodiment, a preemptive priority order may be used in some cases to transmit a time-sensitive command Mυχρ〇υ. Other examples of preemptive precedence have been detailed above. When it is desired to abandon the transfer of the remaining terms of Μχχ pDu, any preemptive condition can be used. The receiver of the MAC frame can directly discard the first part of the MUXPDU. In the following, the exemplary receiver function H is described in detail. In the alternative embodiment, the preemptive priority order may be defined in order to allow the MUx PDUs that have the preemptive priority order to be transmitted at a later time. Alternative embodiments may deploy any number of preemptive priority specifications for use in decision step 2130. If you do not want preemptive priority, proceed to step 2 140. 96870.doc -59- 200525375 In step 2140, first place the local MUX PDU in the MAC PDU. If the configuration is smaller than the local MUX PDU, the desired number of MUX PDUs can be used to fill the configuration, and the remaining items can be stored for transmission in subsequent MAC frame configurations. At step 2150, any new MUX PDUs can be placed in the MAC PDU. The MUX function determines the priority of placing MUX PDUs from any available queue. The exemplary priority mechanism has been described above, however, any priority mechanism can be deployed. In step 2160, the MUX indicator is set to the position of the first new MUXPDU. In this exemplary embodiment, a zero value MUX indicator means that no MUX PDU is included in the configuration. A 1-valued MUX indicator means that the first byte following the MUX header is the start of the next new MUX PDU (that is, there is no local MUX PDU at the beginning of the MAC PDU). Other MUX metric values indicate an appropriate boundary between more than one local MUX PDU and the start of any new MUX PDU. In alternative embodiments, other special MUX indicator values may be defined, or indicator value indicator mechanisms may be deployed. In step 2170, if there is still space in the configured MAC PDU, a partial MUX PDU may be placed in the remaining space. Alternatively, any class-like padding can be inserted into the remaining space. The remaining items of a partially placed MUX PDU can be stored for transmission in subsequent frame configurations. FIG. 22 illustrates an exemplary method 2200 for receiving a MAC frame including a MUX indicator. This method can be deployed in an AP or UT. As taught in this article, those skilled in the art can easily adapt this illustrative example to fit many specific embodiments (AP or UT). 96870.doc -60- 200525375 The program starts from step 22 10, where a MAC PDU is received. At step 2215, a MUX indicator is retrieved from the MAC PDU. In decision step 2220, if the MUX index is greater than 1, proceed to step 2225. In this exemplary embodiment, if the MUX indicator is 0 or 1, there is no local MUX PDU at the beginning of the MAC frame. A value of 0 MUX indicates that there are no MUX PDUs. In either case, proceed to decision step 2230. In decision step 2230, if there is a local MUX PDU stored from the previous MAC frame, then proceed to step 2235 and discard the previous frame stored. In this example, the remaining items of the stored frame have been prioritized. Alternative embodiments may allow the remainder of the stored frame to be transmitted later, in which case the previous local MUX PDU may be stored (details are not shown in the exemplified exemplary method 2200). In decision step 2230, if no local MUX PDU has been stored, or if the stored previous local MUX PDU is to be subsequently processed, the process proceeds to step 2240. At step 2240, a new MUX PDU is retrieved at the beginning of the position indicated by the MUX indicator. Please note that in this exemplary embodiment, a value of 0 MUX means that there is no new MUX PDU in the MAC PDU. Any new MUX PDU can be retrieved, including a new local MUX PDU. As mentioned above, the length field in the MUX PDU header can be used to define the boundaries of the MUX PDU. In decision step 2245, if the MAC PDU includes a local MUX PDU, proceed to step 2250 to store the local MUX PDU. This stored local MUX PDU can be combined with the remaining items from a future MAC PDU (unless it is later decided that the local MUX PDU should be discarded, as described above). At 96870.doc -61-200525375 decision step 2245, if the MAC PDU does not include any new local MUX PDUs, or if the local MUX PDU is already stored in step 2250, proceed to step 2255. At step 2255, any complete MUXPDU can be passed for further processing in the contract stack, including reassembly if appropriate, as described above. As mentioned above, the MUX function allows multiplexing of logical channels (F-TCH and R-TCH) within the traffic channel segment defined on the MAC frame. In this exemplary embodiment, the logical channel multiplexed by the MUX function is identified by a 4-bit message type plastic field in the MUX header. Table 1 details this example. Table 1: Logical channel type field Logical channel MUX type field (hexadecimal) UDCH0 0x0 UDCH1 0x1 UDCH2 0x2 UDCH3 0x3 RBCH 0x4 DCCH 0x5 LCCH 0x6 UBCH 0x7 UMCH 0x8 Type of exemplary MUX PDU. User data channel PDUs (UDCH0 2310, UDCH1 2320, UDCH2 2330, UDCH3 2340) can be used to transmit and receive user data. The PDU may be formed as described above with reference to FIG. 4. Each PDU includes a MUX header with type and length stops. The items following the MUX header are: LL header, 1-byte AL header, up to 4,087 bytes of data, and a 3-byte CRC. For UDCH0 2310, the LL standard 96870.doc -62- 200525375 header is 1 byte. For UDCHl 2320, the LL header is 2 bytes. For UDCH2 2330, the LL header is 3 bytes. For UDCH3 2340, the LL header is 4 bytes. The logical layer functions used to handle their LL PDU types have been detailed above. Various control messages PDUs 2350-2370 are also shown in FIG. Each PDU includes a MUX header with a type of block, a reserved field, and a length field. The item following the MUX header is a variable-length data field. This data field may be between 4 and 255 bytes, and includes the RLC message packet bearer. FIG. 23 illustrates a Radio Link Broadcast Channel (RBCH) PDU 2350, a Dedicated Control Channel PDU (DCCH) PDU 2360, and a Logical Link Control Channel (LLCH) PDU 2370. . The format of the User Broadcast Channel (UBCH) PDU and the User Multicast Channel (UMCH) PDU is exactly the same as the UDCH0 PDU 2310. The UBCH type field is set to 0111. The UMCH type block is set to 1000. Those skilled in the art should understand that their PDUs are for illustrative purposes only. Various additional PDUs and a subset of the PDUs shown can also be supported. In alternative embodiments, each field shown may have an alternate width. Other PDUs also contain additional stops. Exemplary Radio Link Control (RLC) The radio link control 340 has been described earlier, and exemplary embodiments will be further detailed in this paragraph. Table 2 presents a set of exemplary RLC messages. The exemplary messages described are merely examples, and a subset of their messages and additional messages may be deployed in various alternative specific 96870.doc -63- 200525375 embodiments. The size and type of fields in each message are also exemplary. According to the content taught in this article, those familiar with this technology can easily adjust the format of the Syrian alternative message. Table 2: RLC message types

Message Type Message - RLCSystemConfigurationParameters 0x00 RLCReSChallengeACK 0x01 RLCHdwrIDReq 0x02 RLCSystemCapabilities 0x04 RLCCalibrationReqACK 0x05 RLCRLCalibrationMeasurementResult 0x40 RLCRegChallengeRej 0x44 RLCCalibrationReqRej 0x80 RLCRegChallenge 0x81 RLCHdwrIDReqACK 0x82 RLCSystemCapabilitiesACK 0x84 RLCCalibrationReq 0x85 RLCCalibrationMeasurementReq 0x87 RLCUTLinkStatus 0xC5 RLCRLCalibrationMeasurementResultNACK In this example, all RLC messages have a common structure, but can be One of several transmission channels uploads their messages. The RLC PDU structure includes an eight-bit type field for identifying specific RLC messages; a packet bearer consisting of 0 to 25 1 bytes; and a CRC consisting of 3 bytes Field. Table 3 illustrates the use of the bit portion in the type field to indicate a certain type of RLC message. The most significant bit (MSB) of 0 or 1 indicates a forward link message or a reverse link message, respectively. When the second MSB is set, the message is a negative acknowledgement (NACK) or a rejection message. 96870.doc -64- 200525375 Table 3 · Bit position significance of RLC message type field Bit location significance System identification control function 346 is a broadcast RLC function. When the UT uses the MAC-ID from the access pool to initiate access to the system, the RLC function assigns a new MAC-ID to the UT. Then, if the UT joins a multicast group, it can be configured with an additional multicast MAC-ID. When a new MAC-ID is assigned to a UT, the RLC function initializes an instance of each of the following functions: AC 344, RRC 342, and LLC 338, as described above. When a new multicast MAC-ID is assigned, the RLC function initializes a new AC instance and an LLC for the LL multicast mode. The AP will use the broadcast MAC-ID to transmit a system identification parameter message (listed in Table 4) every 16 MAC frames. The system identification parameter message contains the network and AP ID and the protocol version number. In addition, the system identification parameter message contains a list of access MAC-IDs used by the UT-initial access system. Table 4 lists other exemplary parameters. Table 4: System identification parameter message on RBCH Parameter name number of bits --- Purpose RLC message type 8 0x3F Network ID 10 Network ID APID 6 Access point ID Leading concealment code 4 Wals ㈣Guide 1½ Stem pU〇tc〇 ver c〇de) index 96870.doc -65- 200525375 power back & 0wer backoff mechanism (one of 16 possible values) used to return level 4 AP revision level 4 software revision § revision level and system Function RCH return 4 RCH random return factor aromatic neighbor list 120 Adjacent access point and frequency configuration access ro pool 4 access ID pool message length 164 Association control (AC) function provides UT authentication. The AC function manages the registration (ie, attach / detach) functions of the UT. As for multicast MAC-ID, the AC function will manage a UT attach / detach multicast group. The AC function also manages cryptocurrency exchanges for LL control. A Registration Challenge Message is transmitted on the reverse link from the UT, as shown in Table 5. The UT includes a 24-bit random number, which allows the AP to distinguish between multiple UTs with access rights and the same MAC-ID. Table 5: Registration inquiry message parameter name bit number purpose RLC message type 8 0x80 MAC ID 10 temporary MAC ID assigned to UT random ID 24 random inquiry to distinguish access conflict reservation 6 future use of CRC 24 cyclic redundancy check check) Message length 72 9 bytes The registration challenge authentication message is transmitted by the AP.

Acknowledgement Message) (as shown in Table 6) in response to the registration inquiry message. The AP includes the random ID transmitted by the UT. This allows to resolve conflicts between UTs that have picked the same MAC-ID and access time slot. 96870.doc -66- 200525375 Form 6 ·· Registration inquiry authorization message parameter name bit number usage RLC message type 8 0x00 MAC ID 10 Temporary MAC ID assigned to UT Random ID 24 Random inquiry to distinguish access conflicts Reserved 6 Reserved for In the future, CRC 24 will be used to check the repeatability of the message. The length of the message will be 72. 9 bytes will be sent by the AP.

Reject Message (as shown in Table 7) to a UT to reject temporary MAC ID assignment, for example, when two or more UTs randomly select the same temporary MAC ID. Table 7 · Registration inquiry rejection message Parameter name Number of bits Purpose RLC message type 8 0x40 MAC ID 10 Temporary MAC ID assigned to UT Reserved 6 Future use of CRC 24 Cyclic repeatability check message length 48 6 bytes transmitted by AP 1. hardware ID request message

Message) (as shown in Table 8) to obtain the hardware ID from the UT. Table 8: Hardware ID request message parameter name bit number usage RLC message type 8 0x01 MAC ID 10 temporary MAC ID assigned to UT Reserved 6 future use of CRC 24 cyclic repeatability check message length 48 6 bytes transmitted by UT Hardware ID Request approval message

Acknowledgment Mess age) (as shown in Table 9) in response to the hardware ID 96870.doc -67- 200525375 request message and includes the 48-bit hardware ID of the UT. (Specifically, the 48-bit IEEE MAC address that the UT can use). Table 9: Hardware ID request acknowledgement message Daddy name Bit number Purpose RLC message type 8 0x81 MAC ID 10 Temporary MAC ID hardware ID assigned to the UT. 48 Hardware ID number reserved 6 Future use of CRC 24 Cyclic repeatability check Message length 96 12 bytes System Capabilities Message (as shown in Table 10) is transmitted to the newly registered UT to the UT Indicates AP function. Table 10: System Function Message Parameter Name Number of Bits Use RLC Message Type 8 0x02 MAC ID 10 Temporary MAC ID assigned to UT Nant 2 Number of AP antennas Nal 8 Number of supported adjustment layers LISTal 8 * Nal List of adjustment layer indexes supported by AP Tbd Tbd Reserved 4 Future use of CRC 24 Cyclic repeatability check Message length variable Variable number of bytes transmitted by the UT System Capabilities

Acknowledgment Message (as shown in Table 11) in response to the system function message 'to indicate to the AP the UT function. 96870.doc 68-200525375 Table 11: System Function Recognition Message Parameter Name Number of Bits Use RLC Message Type 8 0x82 MAC ID 10 Temporary MAC ID assigned to UT Nant 2 Number of AP antennas Nal 8 Number of supported adjustment layers LISTal 8 * Nal The AP & UT supports the adjustment layer index list reservation. 4 Future use of CRC 24. Cyclic repeatability check. Message length variable number of bytes will initialize a radio resource control RRC instance at each UT. The UT- RRC instance in each role will be initialized at the AP. RRC functions located at the AP and UT can share forward and reverse link channel metrics (if required). The RRC manages the calibration of the transmission and reception chains at the AP and UT. In this example, calibration is helpful for the spatial multiplexing mode. The RRC determines the transmission mode and transmission rate control for transmission to the UT, and provides the decision result to the MAC scheduler. The RRC determines the periodicity and length of the dedicated MIMO preambles required for the burst transmission on the physical layer (PHY) on the R-TCH and on the F-TCH (if required). The RRC manages the power control of transmissions to and from a UT in the space-time transmission diversity (STTD) mode, and provides power control to the PY administrator. The RRC determines the timing adjustment of the R-TCH transmission from the UT. The AP transmits a Calibration Request Message (as shown in Grid 12) to request calibration to the UT. The CalType stop indicates the set of calibration tones and the number of quasi symbols per day that will be used in the calibration routine. & 96870.doc -69- 200525375 Table 12: Calibration Request Message Parameter Name Number of Bits Use RLC Message Type 8 0x84 MAC ID 10 Temporary MAC ID Assigned to UT Nant 2 Number of UT Antennas CalType 4 Select Calibration Procedure Reserved 8 Future Use CRC 24 Cyclic Repeatability Check Message Length 56 6 Bytes Table 13 lists the CalType values. Each CalType corresponds to a set of OFDM audio sets and the number of daily line calibration symbols required for calibration. The Calibration Pilot Symbol uses Walsh sequences to build the orthogonality across the transmitting antennas. Table 13: Calibration type values

CalType value calibration audio calibration leader green amount 0000 soil 7, taxi 21 4 0001 soil 3, taxi 7, soil 11, soil 15, taxi 18, soil 21, taxi 24, soil 26 4 0010 soil 1, taxi 2, ··· ·, Soil 25, taxi 26 4 0011 RSVD 4 0100 soil 7, dirt 21 8 0101 taxi 3, ± 7, taxi 11, taxi 15, taxi 18, taxi 21, lawn 24, taxi 26 8 0110 taxi 1, taxi 2 ···, taxi 25, dirt 26 8 0 111 RSVD 8 1000 ± 7, ± 21 16 1001 dirt 3, taxi 7, taxi 11, dirt 15, taxi 18, dirt 21, taxi 24, ± 26 16 1010 taxi 1, dirt 2, ..., taxi 25, taxi 26 16 1011 RSVD 16 1100 taxi 7, dirt 21 32 1101 dirt 3, ± 7, dirt 11, taxi 15, taxi 18, ± 21, taxi 24, dirt 26 32 1110 dirt 1 , Soil 2, ... soil 25, soil 26 32 1111 RSVD 32 The UT transmits a Calibration Request Reject Message (as shown in Table 14) to reject the calibration request from the AP. .doc -70- 200525375 Li " calibration pilot symbol of the channel between UT and AP.

The AP transmits the calibration measurement result message (R ^ uest Measurement Table 14: Calibration Request Rejection Message Parameter Name Bits Number Use RLC Message Type 8 0x44 MAC ID 10 Temporary MAC ID assigned to the UT Reserved 6 Future use of CRC 24 Cyclic Repeat The length of the sex check message is 48. 6 bytes The calibration measurement request message is sent by the UT.

Request Message) (as shown in Table 15) to the AP. This message includes the AP used to

Result Message) (as shown in Table 16), which is used to provide the UT with the channel measurement result completed by the calibration symbol transmitted by the AP in the standard request message. In this example, each calibration measurement result message carries a channel response value of 4 audio of one M channel, a channel response value of up to 8 audio of a 2 × 4 channel, or a maximum of 16 audio of a U4 channel. Channel response value. It may take ^ till the evening of 13 floods to contain the measurement data of the measured buccal channel * buccal path 96870.doc > 71-200525375, so a serial number is also used to track their information. sequence. If there is not enough data to fill the entire data field ’, the unused portion of the lean shelf will be set to zero. Table 16: Calibration measurement results Message parameter name Number of bits Use RLC message type 8 0x05 MAC ID 10 Temporary MAC ID assigned to the UT SEQ 4 Message sequence number (up to 13 messages) Lean material stall 1536 4 audio channel response Value reserved 2 In the future, the CRC 24 cycle repeatability check message length 1584 198 bytes will be used to transmit the Calibration Measurement Result Acknowledgement Message (as shown in Table 17) to recognize the calibration measurement result message. Fragment. Table 17: Calibration measurement results Approved message parameter name Number of bits Use RLC message type 8 0x04 MAC ID 10 Temporary MAC ID assigned to UT SEQ 4 Approved message sequence number reserved 2 Future use of CRC 24 Cyclic repeatability check message length 48 Similarly, the 6 bytes may not recognize the calibration measurement result approval message. In this case, a Calibration Measurement Result NACK Message (such as a table) may be transmitted on the reverse link. (Shown in Fig. 18), by which the fragment of the calibration measurement result message is NACKed. 96870.doc -72- 200525375 Table 1 8: Calibration measurement result negative approval message parameter name bit number purpose RLC message type 8 0xC5 MAC ID 10 Temporary MAC ID assigned to UT " MODE 1 ACK mode (0 = go- back-N (return N); 1 = selective number; ^ SEQ 16 No. of up to 4 NACKed messages are reserved 5 future use of a CRC 24 cyclic repeatability S check " message length 64 8 bytes calibration amount The test result message may be negatively approved based on go-back-N or selective repetition. The SEQ field is composed of four consecutive 4-bit segments, each of which represents a message sequence number. For In go-back-N mode, the MODE bit is set to 0, and the first segment of the SEQ block indicates the sequence number of the first message in the sequence that must be repeated. In this case, the remaining 12 in the SEQ field The bit is set to 0 and ignored. For the selective repeat mode, the MODE bit is set to 1, and the SEQ field holds the sequence number of up to four messages that must be repeated. If less than four messages must be repeated, Only fragments with non-zero values Meaning. All zero-value segments are ignored. The UT Link Status Message (as shown in Table 19) is transmitted by the AP to request feedback from the UT. In this example, the UT must provide information about the buffer status ( The amount of accumulated data and QOS class) and the feedback of the link quality (MIMO and the forward link transmission rate supported by the control channel). 96870.doc -73-200525375 Table 19: UT chain government status message parameter names Number of bits used RLC message type 8 0x87 " --- MAC ID 10 UT_BUF_STAT 16 ϋϋΗ # Wire link buffer status FL_RATE_STAT 16 Highly supported FL transmission rate (value tbd) QOS —FLAG 2 It is said that RL does not contain high-priority data CCH_SUB_CHAN 2 No better CCH sub-channel reservation 2 Future use · CRC 24 cyclic% repetition check message length 80 10 bytes UT- BUF_STAT indicates the UT radio link buffer size (in octets increments). (^ ???? The value indicates a buffer size greater than or equal to 262,140 bytes. FL_RATE_STAT provides each mode Maximum forward chain Transmission rate (bits per mode 4). For diversity mode, only the battle with the top four most significant bits. The remaining 12 bits are set to zero. Q〇S_FLAG indicates whether the RL buffer contains high priority data. The value QOS_FLAG is defined in Table 20. Table 20: QOS-FLAG value Value Meaning 00 No priority data 01 Priority data 10-11 Reserved At the UT, the RRC establishes the link status information of the UT. At the AP, the UT link status message is forwarded to the RRC used to provide a value to the UT proxy server. The exemplary RRC specific embodiments described in this paragraph can be combined with details detailed throughout the specification. The specific embodiments are deployed together. Those familiar with the technology 96870.doc -74- 200525375 should understand that this exemplary embodiment is for illustrative purposes only, and that many alternative embodiments will be apparent in accordance with the teachings herein. Exemplary specific embodiments of the control channel will be described in the next paragraph, which are suitable for deployment in combination with the specific embodiments detailed in the entire specification. Exemplary Control Channel (CCH) As described above, access to the MAC frame and assignment of resources are controlled by the control channel (CCH). The control channel (CCH) assigns F-TCH and R-TCH based on instructions from the scheduler The resource gives the MAC ID. These resource grants may be a response to a known state of one or more queues at the AP associated with that particular MAC ID, or a response to one or more queues at the UT associated with that MAC ID. The response of the known state is like the reflection of the information in the corresponding UT proxy server. The resource grant may also be a response to an access request received on an Access Request Channel (ARCH), or a response to some other stimulus or information available to the scheduler. Exemplary specific embodiments of the CCH are described in detail below. This exemplary CCH is an example of various control mechanisms that can be deployed in a high-performance WLAN as described above. Alternative embodiments may include additional functions, and a subset of the functions described below. The field names, field widths, parameter values, etc. described below are just examples. Those skilled in the art can easily adapt the illustrated principles to configure many alternative embodiments that fall within the scope of the invention. The exemplary CCH is composed of 4 separate sub-channels, each of which operates at a different data transmission rate, as shown in Table 21. The terminology used in Table 21 is well known in the art (SNR stands for Signal to Noise Ratio (Signal to 96870.doc -75- 200525375

Noise Ratio) and FER stands for Forward Error Rate (also known in the art). CCH uses short OFDM symbols in conjunction with STTD. This means that each logical channel is made up of an even number of short OFDM symbols. Messages transmitted on the Random Access Feedback Channel (RFCH) and Frame Control Channel (FCCH) are formatted as Information Element (IE) and transmitted on one of these CCH subchannels. Table 21: Data transmission rate structure of CCH logical channels

CCH channel efficiency (bps / Hz) Bit rate modulation 1% of total information bits per STTD OFBM symbol FER total SNR CCH—0 0.25 0.25 BPSK 24 -2.0 dB CCH 1 0.5 0.5 BPSK 48 2.0 dB CCH—2 1 0.5 QPSK 96 5.0 dB CCH-3 2 0.5 16 QAM 192 11.0 dB BCCH indicates whether a predetermined CCH subchannel exists or does not exist in the CCH-MASK parameter. Table 22 below provides the various types of each CCH subchannel (where N indicates the subchannel end codes 0 to 3). The format includes multiple fields to indicate the number of IEs, the IE itself, the CRC, zero-filled items (if required), and trailing bits. The AP decides which subchannel to use for each IE. The IE type unique to the user terminal (UT) is transmitted on the CCH subchannel used to maximize the transmission efficiency of the UT. If the AP cannot accurately determine the transmission rate associated with a given UT, then CCH-0 may be used. The broadcast / multicast IE type is transmitted on CCH_0. 96870.doc -76- 200525375 Table 22: CCH sub-channel structure CCH_N field number CCH_N_IE number 8 CCH_N_IE variable CCH_N CRC 16 Zero-filling variable tail 6 CCH is from lowest to highest The transmission rate is transmitted. A CRC is provided for each CCH subchannel. All UTs try to decode every CCH that starts with the lowest transmission rate CCH. Failure to decode correctly means that the higher transmission rate CCH being decoded has errors. Each CCH subchannel can transmit up to 32 IEs. The CCH transmission channel is mapped to two logical channels. The RFCH includes acknowledgement of access attempts received on the RCH. The FCCH includes resource allocation (that is, physical layer frame assignment on F-TCH and R-TCH), physical layer control functions (including physical layer data transmission rate control on F-TCH and R-TCH, and R-TCH dedicated preamble Insertion, R-TCH timing, and R-TCH power control. The FCCH may also include an R-TCHR-TCH to request a buffer and link status updates from a UT. Generally speaking, in this specific embodiment, The information transmitted on the CCH is time-critical and will be used by the recipients in the current MAC frame. Table 23 lists the CCH information element types and their respective type values. The format of the information elements will be further detailed below. In the table below, all displacement values are in units of 800 nanometers. 96870.doc -77- 200525375 Table 23: CCH IE Type Assignment IE Type Information Element 0x0 RegistrationReqACK 0x1 FwdDivModeAssign 0x2 FwdDivModeAssignStat 0x3 FwdSpaModeAssignMode 0x5 RevAssign 0x7 DivModeAssign 0x8 SpaModeAssign 0x9 LinkStatusReq OxA CalRequestAck OxB CalRequestRej Table 24 shows The Registration Request Recognition IE (Registration Request Acknowledgment IE) (RFCH) (labeled RegistrationReqACK in Form 23). The registration request approval is used in response to a registration request received from a UT on the RCH. The format includes an IE type, A slot ID, the access ID (selected by the UT and included in its registration request), the MAC ID assigned to the UT, and a timing advanced value.

Form 24: Registration requirements recognize the number of IE fields. IE TYPE 4 0x0 SLOT-ID 5 Time slot ID used by UT to access RCH ACCESS ID 10 Access ID used by UT MAC ID 10 Temporary MAC ID assigned to UT REV_TIMING ADV 7 R-TCH TX time advanced (in samples) Total 36 Table 25 shows F-TCH Diversity Mode Assignment IE (FCCH) (labeled as FwdDivModeAssign in Table 23) Format. The F-TCH diversity mode assignment is used to indicate the MAC PDUs to be transmitted on the 96870.doc -78- 200525375 F-TCH using the diversity mode. Diversity is another STTD deadline included. The format includes an IE type, a MAC ID, an F_TCH offset (used to indicate the position of the MAC PDU in the MAC frame), the transmission rate used, the number of OFDM symbols in the packet, the type of the leading item (described in detail below), and the packet The number of short OFDM symbols in.

Refer to the ft2ii type to assign the number of IE fields. IE-TYP 4 0x1 MAC-ID 10 MAC ID assigned to UT FWD-OFFSET 12 F-TCH shift FWD-RATE 4 nCH transmission rate FWD-PREAMBLE 2 F-TCH leading item Type FWD_N_LONG 7 Number of long OFDM symbols in the packet FWD_N_SHORT 2 Total number of short OFDM symbols in the packet 41 Table 26 shows the F-TCH diversity mode assignment IE (FCCH) with R-TCH (FwdDivModeAssignStat in Table 23). This IE is used to indicate the MAC PDUs to be transmitted on the F-TCH using diversity mode, and R-TCH space is configured to respond to a status request. The format includes FwdDivModeAssign blocks. In addition, the format includes a configuration shift for the UT to report its buffer status on the R-TCH. The configuration for the link status message on the R-TCH specifies the type of the R-TCH preamble, and the reverse parameters, including the transmission rate, timing adjustment, status message requirements, and long and short types in the link status packet Number of OFDM symbols. 96870.doc -79- 200525375

Table 26: F-TCH diversity mode with R-TCH status assignment IE number of slots role IE TYPE 4 0x2 MACJD 10 MAC ID assigned to UT FWD_OFFSET 12 F-TCH shift FWD_RATE 4 F-TCH transmission Rate FWD—N—LONG 7 Number of long OFDM symbols in the packet FWD—PREAMBLE 2 F-TCH preamble type FWD—N—SHORT 2 Number of short OFDM symbols in the packet REV—OFFSET 12 R-TCH shift REV—PREAMBLE 2 R-TCH leading item type REV-RATE 4 R-TCH transmission rate REV-TIMING 2 R-TCH timing adjustment REV-STATUS-REQ 1 R-TCH status message requires REV-N-LONG 7 Long in the link status packet Number of type OFDM symbols REV_N_SHORT 2 Total number of short OFDM symbols in the link state packet 71 FWD_PREAMBLE and REV_PREAMBLE fields respectively provide the length of the previous leading term used on the reverse link and transmitted on the reverse link Status message. The leading term consists of the number of short OFDM symbols provided in Table 27, and only carries the steered reference for the main characteristic mode (eigenmode) ° Table 27: FWD—PREAMBLE, REVJPREAMBLE Value Meaning 00 None Leading Item 01 Four Leading Items 10 Eight Leading Items 11 Reserved Table 28 shows F-TCH Spatial Multiplex Mode Assignment IE (FCCH) (labeled 96870.doc -80 in Table 23) -200525375

FwdSpaModeAssign). This IE field is similar to FwdDivModeAssign, except that it uses spatial multiplexing instead of diversity.

Table 28: F-TCH space multiplexing mode assignment IE number of slots role IE TYPE 4 0x3 MAC-ID 10 MAC ID assigned to UT FWD_OFFSET 12 F-TCH shift FWD_RATE 16 F-TCH space mode 0 -3 transmission rate FWD_PREAMBLE 2 F-TCH preamble type FWD_N_LONG 7 Number of long OFDM symbols in the packet FWD_N_SHORT 2 Total number of short OFDM symbols in the packet 53 Table 29 shows the R-TCH Format of the stateful F-TCH spatial multiplexing mode assignment IE (FCCH) (labeled as FwdSpaModeAssignStat in Table 23). This IE field is similar to FwdDivModeAssignStat, except that spatial multiplexing is used instead of diversity.

Table 29: F-TCH spatial multiplexing mode assignment with R-TCH status IE number of blocking bits role IE TYPE 4 " 〇 ^ 4-MAC_ID 10 MAC ID assigned to UT FWD_OFFSET 12 F- TCH shift FWD—RATE 16 F-1 (JH space mode 0-3 transmission rate FWD-PREAMBLE 2 F-TCH preamble type FWD-N-LONG 7 Number of long OFDM symbols in the packet FWD-N-SHORT 2 packets Number of short OFDM symbols in the REV_OFFSET 12 R-TCH shift REV_PREAMBLE 2 R-TCH preamble type REV_RATE 4 R-TUH transmission rate REV_TIMING 2 ~ R: tch ^ ~~ REV_STATUS_REQ 1 109¾¾ Requires REV—N—LONG 7 Number of long OFDM symbols in the link state packet REV N-SHORT 2 Total number of short OFDM symbols in the link state packet 83 96870.doc * 81-200525375 Table 30 shows R -TCH Diversity Mode Assignment IE (FCCH) (RevDivModeAssign in Table 23) format. This IE is used to signal an R-TCH configuration for MAC PDUs using diversity mode. This IE includes the MAC ID field as described above. This IE also includes the status as described above The reverse key fields (FwdDivModeAssignStat and FwdSpaModeAssignStat) included in the status request message. This IE further includes a reverse transmission power adjustment field.

Table 30: R-TCH diversity mode assignment IE field number function IE TYPE 4 0x5 MAC-ID 10 MAC ID assigned to UT REV_OFFSET 12 R-TCH shift REV—PREAMBLE 2 R-TCH leading item type REV— RATE 4 R-TCH transmission rate REV_TIMING 2 R-TCH TX timing adjustment REV_STATUS_REQ 1 R-TCH status message requires REV_N_LONG 7 Number of long OFDM symbols in the packet REV_N_SHORT 2 packets Number of short OFDM symbols in the REV-POWER 2 R-TCH TX total power adjustment 46 Table 3 1 shows the R-TCH Spatial Multiplex Mode Assignment IE (FCCH) (labeled in Table 23 The format is RevSpaModeAssign). This IE field is similar to Re vDivMode As si gn, except that it uses spatial multiplexing (instead of diversity) 0 96870.doc -82- 200525375

Table 31: R-TCH spatial multiplexing mode assignment IE field number role IETYPE 4 0x6 MAC_ID 10 MAC ID assigned to UT REV_OFFSET 12 R_tch shift REV_PREAMBLE 2 R-TCH leading item type REV_RATE 16 H_TCH transmission rate REV_TIMING 2 R-TCH TX timing adjustment REV_STATUS_REQ 1 R-TCH status message request REV_N_LONG 7 Number of long OFDM symbols in the packet REV_N_SHORT 2 Short in the packet Number of type OFDM symbols REV-POWER 2 Total number of R-TCHTX power adjustments 58 Table 32 shows the format of TCH Div Mode Assignment IE (FCCH) (labeled DivModeAssign in Table 袼 23). This IE is used to configure forward link and reverse link MAC PDUs. This IE field combination of fields PwdDivModeAssign and RevDivModeAssign.

Table 32: TCH diversity mode assignment IE field number function IE_TYPE 4 0x7 MAC_ID 10 MAC ID assigned to UT FWD_OFFSET 12 fch shift FWD_PREAMBLE 2 F_TCH Leading item type FWD_RATE 4 F-TCH Transmission rate FWD_N_LONG 7 Number of long OFDM symbols in the packet FWD_N_SHORT 2 Number of short OFDM symbols in the packet REV_OFFSET 12 R-TCH shift REV_PREAMBLE 2 H-TCH leading item type REV_ RATE 4 ITCH transmission rate REV_TIMING 2 R / TCHTX timing adjustment REV_STATUS_REQ 1 R-TCH status message request REV_N_LONG 7 Number of long OFDM symbols in the packet 96870.doc • 83-200525375 REV_N Number of short OFDM symbols in a SHORT 2 packet REV-POWER 2 R-TCH TX total power adjustment 73 Table 33 shows TCH Spatial Mul mode assignment ie (TCH Spatial Mul

Mode Assignment IE) (FCCH) (labeled SpaModeAssign in Table 23). This IE field is similar to DivModeAssign except that it uses spatial multiplexing instead of diversity.

Table 33: Number of IE fields assigned in TCH spatial multiplexing mode IE_Type 4 0x8 MAC_ID 10 MAC ID assigned to UT FWD_OFFSET 12 FCH shift FWD_RATE 16 F-TCH transmission rate FWD_PREAMBLE 2 F-TCH preamble entry type FWD_N_LONG 7 Number of long OFDM symbols in the packet FWD_N_SHORT 2 Number of short OFDM symbols in the packet REV_OFFSET 12 R-TCH shift REV_PREAMBLE 2 R-TCH preamble Item type REV_RATE 16 R-TCH transmission rate REV_TIMING 2 R-TCHTX timing adjustment REV_STATUS_REQ 1 R-TCH status message request REV__N_LONG 7 Number of long OFDM symbols in the packet REV_N_SHORT 2 Number of short OFDM symbols in the packet REV-POWER 2 Total number of R-TCHTX power adjustments 97 Table 34 shows the buffer and link status requirements IE (Buffer and Link

Status Request IE) (RFCH or FCCH) (labeled LinkStatusReq in Table 23). The AP uses this IE to request the current status of the buffer and the current status of the physical link connected to the UT from the UT. A reverse link configuration to provide a response is coordinated with this requirement. In addition to the type and MAC ID fields, the reverse link configuration also includes fields of the reverse link configuration of type 96870.doc -84- 200525375 described above.

Table 34: R-TCH link status requirements IE number of bits role IE Type 4 0x9 MAC_ID 10 MAC ID assigned to UT REV_OFFSET 12 R, tch shift REV_PREAMBLE 2 R-TCH leading item type REV -Timing 2 R-TCHTX timing adjustment REV_STATUS-REQ 1 R-TCH status message request REV_N_LONG 7 Number of long OFDM symbols in the link state packet Total number of OFDM symbols 40 Table 35 shows the calibration request approval IE (Calibration Request

Acknowledgment IE) (FCCH) (labeled CalRequestAck in Table 23). This IE is transmitted to recognize the calibration requirements of a UT. Calibration is usually performed immediately after registration, and rarely afterwards. Although the TDD radio channel is symmetrical, the transmission and reception chains at the AP and UT may have unequal gains and phases. Calibration is performed to eliminate this asymmetry. This IE includes a type field, a MAC ID block (including the temporary MAC ID assigned to the UT), the number of antennas in the UT, and approval of the desired calibration type. The 4-bit calibration type field specifies the audio combination used for calibration 'and the number of training symbols transmitted based on the calibration purpose.

Table 35: Calibration requirements approved IE Parameter name Number of bits Use IEType 4 OxA MAC ID 10 Temporary MAC ID assigned to UT Nant 2 Number of UT antennas CalType 4 Calibration procedure required for accreditation Message length 20 96870.doc -85- 200525375 Form 36 shows the format of Calibration Request Reject IE (FCCH) (labeled CalRequestRej in Table 23). This IE rejects calibration requests from a UT. This IE includes a type field, a MAC ID field, and a calibration request type field, like CalRequestAck. In addition, a reason field is provided to explain why the calibration request was rejected.

Table 36: Calibration Request Rejection IE Parameter Name Number of Bits Purpose IEType 4 OxB MAC ID 10 Temporary MAC ID assigned to UT CalType 4 Required Calibration Procedure Reason 4 Reason for Rejecting Calibration Request Message Length 22 Refer to a Cause Value Reason for calibration requirement. Table 37 details the causes and cause values. _Parameter 37: Cause Value Meaning Value Cause 0000 Calibration not required 0001 The required procedure is not supported 0010 Calibration procedure timeout 0011-1111 Reserved Table 38 shows the format of the Request Mess age (ARCH). Upon initial access, the request message is treated as a registration request. The accessing UT will randomly select an access ID from a set of IDs set for initial access and published in the BCCH message. If the request message is continuously received, the AP will use the registration request approval process on the RFCH to recognize the request message and assign a temporary MAC ID to the UT. 96870.doc -86- 200525375 Registered UTs will use the same message on ARCH, but use the MAC ID assigned in the Access ID field to request service. If the request message is received continuously, the AP will transmit an R-TCH link status request IE to obtain the type and size of the desired configuration of the UT. Table 38: ARCH requires the number of message slots to be used as the leading variable. Short or long SLOT-ID 5 UT time slot ID used by UT to access the RCH. It should be understood that any of a variety of different terms or techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips are useful for representing voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof. Those skilled in the art should further understand that the various illustrated logical blocks, modules, circuits, and algorithm steps described in conjunction with the specific embodiments published herein can be implemented as electronic hardware, computer software, or a combination thereof. In order to clearly explain the interchangeability of hardware and software, in the previous article, various components, blocks, modules, circuits, and steps of various diagrams have been extensively explained in terms of functions. Depending on the specific application and design constraints affecting the entire system, the functionality is implemented as hardware or software. Those skilled in the art can implement the described functions in different ways for each particular application, but this implementation decision cannot be regarded as departing from the scope of the present invention. A general-purpose processor, digital signal processor (DSP), Circuit (ASIC), field programmable gate array (FPGA), or other programmable logic device (67070.doc -87- 200525375), discrete gate or transistor logic, discrete hardware components, or any of them Combination to perform the functions described herein, to implement or execute the various illustrated logical blocks, modules, and circuits described in conjunction with the specific embodiments published herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may be implemented as a combination of computer devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a microprocessor $ connected to one or a core of the core, or any other such configuration. In conjunction with the method or algorithm steps described in the specific embodiments disclosed herein, it can be directly embodied by hardware, a software module executed by a processor, or a combination of software and hardware. Software modules can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, scratchpad, hard disk, removable disk, CD-ROM, or this technology In any other form of storage medium known. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In the alternative, the media can be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. The headings listed in this article are for reference and to help find the paragraphs. These headings are not intended to limit the scope of the concepts described in this article. These concepts can be applied throughout the specification. Descriptions of the specific embodiments disclosed are provided elsewhere so that those skilled in the art may utilize or utilize the invention. Those skilled in the art should understand the various modifications of these specific 96870.doc -88- 200525375 embodiments, and other specific embodiments defined herein, the general principles can be applied to

The most extensive Fan Lun with the same principles and novel functions as explained in the text

FIG. 2 illustrates an exemplary embodiment of a wireless communication device, and the wireless communication device can be configured as an access point or a user terminal; FIG. 3 illustrates an exemplary subnet protocol stack; FIG. 4 illustrates a pass protocol Stacks of user data packets traveling at various layers. Figure 5 shows an exemplary MAC frame. Figure 6 shows an exemplary method of transmitting forward link message transmission. Figure 7 shows an exemplary method of receiving forward link message transmission. Figure 8 illustrates an exemplary method of transmitting reverse link message transmission; Figure 9 illustrates an exemplary method of receiving reverse link message transmission; Figure 10 illustrates an exemplary method of UT performing initial access and registration; FIG. 11 shows an exemplary method for the AP to perform initial access and registration; FIG. 12 shows an exemplary method for the AP user data stream; 200; FIG. 13 shows an exemplary method for the UT user data stream. 〇; Figure 14 shows an exemplary method of incorporating physical layer feedback into the adjustment layer function. Figure 15 shows an exemplary method of performing adjustment layer multicast. Figure 16 shows the decision whether to use adjustment layer multicast or MAC. Multipoint 96870.doc -89- 200525375 Broadcast Exemplary method; FIG. 17 illustrates an exemplary method of performing segmentation in response to feedback from the physical layer; FIG. 18 illustrates segmentation in response to a transmission rate; FIG. 19 illustrates transmission of multiple data in a single MAC frame Exemplary method of flow and command; FIG. 20 illustrates a continuous MAC frame including an example of transmitting various local MUX PDUs; FIG. 21 illustrates an exemplary method of preparing a MAC frame using a MUX indicator; FIG. 22 illustrates reception including MUX Exemplary method of MAC frame of the indicator; Fig. 23 illustrates an exemplary MUXPDU format; Fig. 24 illustrates an exemplary system configured for Ethernet regulation; Fig. 25 illustrates an exemplary system configured for IP regulation Exemplary system; FIG. 26 illustrates an exemplary Ethernet protocol stack; and FIG. 27 illustrates an exemplary IP protocol stack. [Description of main component symbols] 100 system 102 network 104 access point (AP) 106A-N user terminal (UT) 1 10, 270 connection 120 wireless LAN area (WLAN) (Figure 1) 120 RF link (Figure 26) 210 transceiver 96870.doc -90- 200525375 220 MAC processor 240 LAN transceiver (Figure 2) 250A-N antenna 255 memory 260 data stream 280 feedback 300 subnet protocol stack (Figure 3) 310A, 310B Adjustment Layer 312 Segmentation and Reassembly (SAR) 314 Data Stream Classification 316 Multicast Map 320A, 320B Data Link Layer 240A, 240B Physical Layer (PHY) 320 Data Link Control Layer (Figure 3) 330 Logical Link (LL ) Layer 332 Accessible Broadcast / Multicast / Unicast 334 Negative Approval 336 Approval 340 Radio Link Control (RLC) Layer 342 Radio Resource Control (RRC) 344 Association Control Function 350 System Configuration Control 360 MUX Function 370 Common MAC function 96870.doc -91- 200525375 372 MAC group frame function 374 Control channel function 376 MAC scheduler 378 Random access control function 380 Layer administrator 382 QoS administrator function 384 Admission control function 3 86 Physical layer administrator 410 User data packet 420A_N Fragment 430 Adjust sub-layer PDU 434, 444, 454 Packet payload (payload) 440 Logical link sub-layer PDU (LL PDU) 442 LL header 450 MUX sub-layer PDU (MPDU) 452 MUX header 462 MUX indicator 464 Local MPDU 466 New PDU 466A MPDU 468 Local MUX PDU 500 MAC frame 510 Broadcast channel (BCH) 520 Control channel (CCH) 96870.doc -92- 200525375 530 Forward traffic channel (F-TCH ) 540 Reverse Traffic Channel (F-TCH) 550 Random Access Channel (RCH) 560 Fragment 2410 IP router 2610, 2710 Upper layers 2615, 2720A IP layer 2620A Ethernet MAC layer 2620B Ethernet MAC 2640 Ethernet Network Tuning Protocol Stack (UT Protocol Stack) 2650 Ethernet Tuning Protocol Stack (AP Protocol Stack) 2740 IP Tuning Protocol Stack (UT Protocol Stack) 2750 IP Tuning Protocol Stack (AP Protocol Stack) 96870.doc 93-

Claims (1)

200525375 10. Scope of patent application: 1. A device, including: a first layer for receiving one or more packets from one or more data streams, and for generating one or more packets from the one or more packets; Or multiple first layer protocol data unit PDUs. 2. The device of claim 1, further comprising a second layer for receiving the one or more first layer PDUs from the first layer and generating from the one or more first layer PDUs One or more second layer pDUs. 3. The device of claim 2, further comprising a third layer for receiving the-or more second layer PDUs, and transmitting the one or more second layer coffees to a remote station. 4. 5. 6. The device of item 2 further includes a layer of administrators for receiving feedback from the second layer, and magically delivering the second layer of feedback to the first layer. For example, the device of claim 3 further includes a layer of administrators for receiving the feedback of the third layer and transmitting the feedback of the third layer to the first layer.求 求人 3 之. Also prepared ’further includes a layer of administrators for receiving the third layer of anti-H’ and «the third layer is fed back to the second layer. For example, & prepare 'for π Finding Item 1 where the layer PDUs are generated in response to the physical layer feedback. & taxi% seeking item 5 & prepare ' wherein the first layer P is generated in response to the physical layer feedback. 9. The device of claim 8, wherein the Shen Xing cA 3-day μ _ # τ 4 through-body feedback includes one or more parameters associated with the transmission. 1〇 · —Agreement stack, including: 96870.doc 200525375-a first layer, including: a first logic, used to check the upper layer or multiple data streams from the header and the packets after responding to these checks . The classification of these packets becomes ~ 11 12. 13. 14. 15. 16. 17. • If the agreement stack of claim 10 is added, the first + the generation P eight phase 々 ^ '括 bracketing is used for multicast broadcasting The second logic of the classified packets of the Shibian Temple. Listening and shooting, such as the agreement stack of item 11 of the request, its c ^, W Hai 苐 a logic to receive real feedback, and multicast mapping of these ... through the body layer body feedback. The packet of knives responds to the agreement stack of the real request item 10, and further% ^ 4 _ 乂 includes the second logic for splitting the distributed packets. If the agreement stack of item 13 is requested, the second logic receives the entity layer, 0 ^., And a packet in response to the feedback from the entity layer. For example, the #question 10 agreement stack, enter a bullfight, s Step I includes the second logic for reorganizing the classified packets. For example, the protocol stack of claim 10 further advances the pv step to include the second logic for the physical layer to transmit the seek / knife packets. A device comprising: a, a continuation layer for receiving one or more data streams from one or more data streams and for generating one or more packets from the one or more packets; PDUs in response to feedback from the physical layer; and a link control layer for receiving one or more regulatory layer PDUs from the regulatory layer and generating them from the one or more regulatory layers Pdu—or Multiple physical layer PDUs; 96870.doc 200525375 a physical layer for receiving the one or more physical layer PDUs, transmitting the one or more physical layer PDUs to a remote station A, and &W; Cut-through body feedback includes one or more parameters associated with the transmission And a layer of administrators for receiving feedback from the physical layer, and 1 for the feedback from the physical layer to the adjustment layer. M 19 · As requested by the device of item 17 20. As claimed by the device of item 17 ·· as requested Device 22 of item π, such as device 2 of item 17, 2 Device 18 of item 2, 2 18, such as device of item 17, wherein the physical layer feedback includes a transmission rate, and the physical layer feedback includes a transmission rate. Round: rate where the entity layer feedback includes a modulation format. Where the entity layer feedback includes a packet size. Where the entity layer performs spatial processing. Where the entity layer performs spatial multiplexing. 24. = equipment of request item 22, Among them, the entity layer performs space-time round robin 25. If the device of item 22 is requested. 26. If the device of item 22 is requested. 2 7 • If the device of item 22 is requested. 28 If the device of item 22 is requested. Beam steering. The physical layer includes orthogonal frequency division multiplexing. The physical layer includes code division multiplexing. Continuing, the physical layer includes two or more, and performs multiple input multiple output processing. 29 · If Please The device of item 17 is classified as a data stream. ^ Body feedback is used to perform the 30. If the device of item 17 is requested, the layer can be adjusted for less than 4 weeks, so that a received packet is divided into a plurality of fragments. The size should be determined by stomach response / cross-body feedback-the device of item 30, where the fragment size is proportional to the transmission rate. 96870.doc 200525375 32. The device of item 17, wherein the adjustment layer performs multicast mapping— Or multiple received packets in response to the entity layer feedback. 33. The device of claim 32, wherein the adjustment layer comprises: a first circuit operable to map a multicast packet to a single layer-adjustment layer PDU for transmission to two or more remote locations End stations; a second circuit operable to map a multicast packet to two or more second regulatory layer PDUs for transmission to the two or more remote stations; a third circuit ' It is operable to calculate a first transmission metric associated with the first-regulation-layer PDU and a second transmission metric associated with the second-regulation-layer PDU. Channel-related physical layer feedback, these channels correspond to multiple remote stations; said -comparator 'for comparing the first transmission metric with the second transmission metric' to produce a metric comparison result; and or The supportable transmission rate for a single channel of more than two remote stations, and the second transmission metric is-the supportable transmission rate from one of the two or more channels. -A selector for responding to the metric comparison result and generating one or more output adjustment layers pDu by selecting the first or second adjustment layer_. 34. The device of claim 33, wherein the first pass metric is one to the two K's of the device of claim 33, wherein the first transmission metric and the second transmission metric are to the two or The capacity used by the single channel of two or more remote stations' and the capacity used by the two or more channels of the two or more remote stations 96870.doc 200525375. 36. The device of claim 34, wherein when the metric comparison result indicates that the capacity used by the first regulation layer PDU is less than the capacity used by the second regulation layer pDU, the first regulation layer pDU is selected; otherwise The second regulatory layer PDUs are selected. 3 7. A wireless communication system comprising a first layer for receiving one or more packets from one or more data streams and for generating one or more packets from the one or more packets Layer 1 protocol data unit PDU. 38. The wireless communication system of claim 37, further comprising a second layer for receiving the one or more first layer pDus from the first layer or the second layer from the first or second layers. PDU to generate one or more second-level chats. 39. The wireless communication system of claim 38, further comprising a third layer for receiving the one or more second layer chats and transmitting the one or more second layer PDUs to a remote station. 40. The wireless communication system as claimed in item 38, further comprising a layer of administrators for receiving feedback from the second layer and passing the second layer feedback to the first layer 0 41. As the wireless communication system for item 39, enter The __step includes-the layer administrator is used to receive the third layer feedback 'and pass the third layer feedback to the first layer 0. The first layer PDU is generated. 42. The wireless communication system as claimed in item 37, wherein the first response entity is Layer feedback. 43 · —a wireless communication system, including ································································ Multiple adjustment layers agree on data unit PDUs in response to the physical layer feedback;-the data link control layer is used to receive the one or more adjustment layers from the tune; The layer has just generated one or more physical layer PDUs; the physical layer feedback includes one or more parameter physical layers associated with the transmission for receiving the-or more physical layers, and the- Or multiple physical layer PDUs are transmitted from the first station to a remote station; and a layer of administrators is used to receive the physical layer feedback and pass the physical layer feedback to the adjustment layer. 44. A method comprising: receiving one or more packets from one or more data streams; and generating one or more first layer pDUs from the one or more packets. 45. The method of # 求 项 44, further comprising generating one or more second layer Pdus from the one or more first layer PDUs. 46. The method of claim 45, further comprising transmitting the one or more layer 2 PDUs to a remote station. 47. The method of claim 44 wherein the first layer pDUs are generated in response to physical layer feedback. 4 8 · — A media access control method, including: receiving one or more packets from one or more data streams; waiting for one or more packets from the edge to generate one or more adjustment layer pDUs to 96870. doc 200525375 in response to physical layer feedback; generating one or more physical layer PDUs from the one or more conditioning layer PDUs; and, 9 transmitting the one or more physical layer PDUs to a remote station. 49. 50. 51. 52. 53. 54. 55. 56. 57. The method of claim 48, wherein the transmission includes space processing according to a transmission rate ' The transmission rate is associated with the physical layer feedback. The method of item 48, further comprising performing data stream classification in response to child-level body feedback in order to generate one or more adjustment layers pDu. For example, the method of item 48 may further include segmenting a received packet in response to physical layer feedback in order to generate one or more adjustment layers pDu. The method of eye-seeking item 51 further includes selecting a segment size for the segmentation in response to physical layer feedback. For example, the method of finding term 52, wherein the fragment size is directly proportional to a transmission rate. The method according to item 48 further includes multicast mapping a packet to two or more channels in response to the entity layer feedback. Shi Ming's method of finding item 54, wherein among the two or more channels-or more channels are unicast channels. As in the method of claim 48, the further steps include multicasting in a first mode: mapping to a single channel 'and multicasting to two or more channels in a second mode. The method of female whistle seeking item 56 further includes selecting the first selection when the system resources required for multicast mapping to one: channel are less than the system resources required for multicast mapping to two or more channels The second mode. ， No 96870.doc 200525375 58. If the method of item 57 is requested, Ganshan, and the two ^ will be linked together in a single channel, the last two or two to calculate the system resource requirements. The transmission rate required for transmission on the channel, come 59.-a method of media access control, including:-receiving-a packet directed to a remote station, and a packet of segments into two or more segments, etc. Slice = size ^ 照 _physical layer parameters associated with the remote station channel 60_ — a method of media access control, including access to a packet addressed to a multicast group, the multicast group, In addition, two or more remote stations are included, and the packet is transmitted to the remote stations in the multicast group on two or more channels. 61-A media access control method, including ..., receiving a packet addressed to a multicast group, the multicast group including two or more remote stations; The second resource configuration of the multicast configuration of the channel multicast transmission to the multicast group, and the multicast transmission of the multicast group to two or more channels to the multicast group; and When the first resource configuration is less than the second resource configuration, the packet is transmitted on a single channel; otherwise, the packet is transmitted on two or more channels. The method of finding item 61 in the month, wherein the first resource configuration is the minimum supportable transmission of the channel that can be received by each remote station in the multicast group. 96870.doc 200525375: x Wait for two or more frequencies, f the minimum transmission rate of each channel. ^ 63. If the method of item 62 is explicitly requested, Dou Zhong will receive the body's #. Y w π tomographic feedback to receive the data. Yan 64. 65. A computer-readable medium that is operable to perform the following steps: receiving one or more packets from-or more data streams; and generating one or more packets from the one or more packets First pdu. A computer-readable medium such as § Month Item 64, which is operable to perform the following steps: From the one or more first layer PDUs to generate one or more second frame PDUs. 9 The computer-readable medium of claim 65 is operable to perform the following steps: transmit the one or more layer 2 PDUs to a remote station. 67. The computer-readable medium of claim 64, wherein the generating step is operable to generate one or more first-level chats in response to entity-level feedback. A computer-readable medium that is operable to perform the following steps: receive one or more packets from one or more data streams; wait for one or more packets to generate one or more conditioning layer PDUs in response to an entity Layer feedback; one or more adjustment layer pDUs, such as δ, to generate one or more physical layer PDUs; and transmitting the one or more physical layer PDUs to a remote station. 69.-A computer-readable medium operable to perform the following steps: receiving-a packet directed to-a remote station; and dividing the received packet into two or more fragments, such pieces 96870. The size of the doc 200525375 segment is based on the physical layer parameters associated with the remote station channel. 70. A computer-readable medium operable to perform the following steps: receiving a packet addressed to a multicast group, the multicast group including two or more remote stations; and The packet is transmitted on two or more channels to the remote stations in the multicast group. 71 · —a computer-readable medium operable to perform the following steps: receiving a packet addressed to a multicast group, the multicast group including two or more remote stations, · Compare the > source configuration of a single channel multicast transmission to the multicast group with the one required for multicast transmission to the multicast group on two or more channels A second resource configuration; and when the first resource configuration is less than the second resource configuration, the packet is transmitted on a single channel; otherwise, the packet is transmitted on two or more channels. 7 2 · A device comprising: one or more receivers for receiving from one or more data streams · η packet-like structure for generating one or more components from the one or more packets. Solid layer-layer coffee 73. The device of claim 72, further comprising means for generating one or more second layers from the one-inch or more one-layer PDUs? 1) 1; components. 74. The device of claim 73, further comprising means for transmitting one μf or more 96870.doc • 10-200525375 75 76 one layer of PDUs to a remote station. The device of claim 74, wherein the first layer pDUs are generated in response to body feedback. • A device comprising a structure for receiving one or more packets from a device; or multiple lean streams From the one or more packets to generate a y Lang layer PDU to generate one or more entities Means for responding to the physical layer feedback or multiple adjustment layer PDUs means for transmitting from the one or more adjustment layer PDUs; and for transmitting the one or more physical layers to a remote station. 77. 78. 79. A device comprising: a means for receiving a packet directed to _Please ★ 山 a / 到 随 &station; and a means for dividing the received packet into two or two Phases of the above snippets Pieces ’size of the temple fragment to be received} Eighty” your neodymium makeup is associated with the physical parameters of the remote station frequency. '' A device comprising: means for receiving-addressed packets to a multicast group, the multicast group M comprising two or more remote stations; and The multiple frequencies must force the components that transmit the packet to the remote stations in the multicast group. A device comprising: · a component for receiving a packet addressed to more than one "" broadcast group, 96870.doc -11- 200525375 the multicast group includes two or more remote stations · A comparison component for comparing a first resource configuration required for a single channel multicast transmission to the multicast group, and a multicast transmission to the multicast for two or more channels A second resource configuration required by the group; and a transmission component for transmitting the packet on a single-channel when the first resource configuration is less than the second resource configuration; otherwise, two or more than two The packet is transmitted on a channel. 80 ·-a wireless communication system comprising: means for receiving one or more packets from one or more data streams; and for generating _ or- 81. The wireless communication system of claim 80. The wireless communication system of claim 80, further comprising a component for generating one or more second-level coffees from the one or more first-level rewards. 82. A wireless communication system as claimed in item 81 The further steps include components that transmit one or more layer 2 PDUs to a remote station. 83. The wireless communication system of claim 80, wherein the layer 1 PDUs are generated in response to physical layer feedback. 8 4. A wireless communication system comprising: means for receiving from one or more data streams J or more packets, each packet to generate a packet for adjustment from the one or more or more of them in response to physical layer feedback Layer PDU components; 96870.doc -12- 200525375 components for generating one or more physical layer PDUs from the one or more conditioning layer PDUs; and for transmitting the one or more physical layer PDUs to Components of a remote station 0 96870.doc -13-