Station equipment, access point equipment

Abstract

Traditional SCS operations had a problem where, if the same TID was set for multiple different SCS streams, it was impossible to distinguish between traffic from SCS streams belonging to the same application. [Solution] By bundling multiple SCS streams belonging to the same application using the Application ID, the AP can schedule traffic belonging to multiple SCS streams in a way that satisfies the application's requirements, even if the same TID is assigned. This is expected to enable low-latency communication.

Description

Technical Field

[0001] The present invention relates to a station device and an access point device.

Background Art

[0002] To achieve further high-speedization of IEEE 802.11, which is a wireless LAN (Local Area Network) standard, IEEE 802.11be is being standardized by the IEEE (The Institute of Electrical and Electronics Engineers Inc.), and wireless LAN devices compliant with the specification draft have appeared on the market. Currently, as a successor standard to IEEE 802.11be, the standardization activity of IEEE 802.11bn has been started. The main theme in the IEEE 802.11bn standardization is the realization of Ultra-High Reliability (UHR). In a wireless LAN, frame transmission and reception can be performed using an unlicensed band that enables wireless communication without the need for permission (license) from a country or region. For personal use such as in a home, a wireless LAN access point function is included in a line terminal device for connecting to a WAN (Wide Area Network) line such as the Internet, or a wireless LAN access point device (also referred to as an access point device) is connected to the line terminal device, etc., and Internet access from within a residence has been wirelessized. That is, a wireless LAN station device such as a smartphone or a Personal Computer (also referred to as a station device) (UHR) is to be realized.

[0003] A wireless LAN access point (Honda) can connect to a wireless LAN access point device and access the internet. Initially, when wireless LANs were first introduced to homes, there was often only one wireless LAN access point device in the house. However, nowadays, it is common to install multiple wireless LAN access point devices to expand the coverage of the wireless LAN area within the home.

[0004] The IEEE 802.11 series specifications define wireless communication devices in wireless LAN systems as ST It is referred to as A(STAtion) and connects to multiple other STAs to provide network services. A STA that connects to an AP STA and provides network services will be referred to as an AP STA (Access Point STA), and an STA that connects to an AP STA and provides network services will be referred to as a Non-AP STA. In the following, AP STA will also be referred to as an access point (AP), base station equipment, or access point equipment, and Non-AP STA will also be referred to as a terminal, user terminal, terminal equipment, user terminal equipment, or station equipment.

[0005] Regarding wireless LANs, the 6GHz band (5.925-7.125GHz) is available for use as an unlicensed band in the United States, and in Europe and Japan, the lower frequencies of the 6GHz band (5.925-6.425GHz) are permitted for use, with consideration being given to the upper frequencies (6.425-7.125GHz). Similar considerations are underway in other countries around the world. Due to these trends, it is becoming likely that wireless LANs will be able to use the 6GHz band in addition to the 2.4GHz and 5GHz bands. To accommodate the expansion of target frequencies, the Wi-Fi Alliance has developed Wi-Fi 6E, an enhanced version of Wi-Fi 6. They have formulated a registered trademark and plan to use the 6GHz band.

[0006] The 6GHz band is a frequency band of approximately 5.925 to 7.125GHz, and in terms of bandwidth, a total of about 1.2GHz becomes available as new bandwidth. In other words, this increases the number of channels by 14 when converted to 80MHz wide channels, or by 7 when converted to 160MHz wide channels. As a result of being able to use abundant frequency resources, the maximum channel bandwidth that can be used by a single wireless LAN communication system (equivalent to BSS described later) has expanded from 160MHz in IEEE 802.11ax to 320MHz in IEEE 802.11be, which is double the previous amount.

[0007] While the 2.4GHz band offers relatively wide coverage (communication range), communication equipment Interference between frequency bands becomes more significant, and the usable bandwidth is relatively narrow. While the 5GHz and 6GHz bands offer wider communication bandwidth, their coverage is limited. Therefore, to implement various services and applications using wireless LAN, it is desirable to bundle or switch between frequency bands (2.4GHz, 5GHz, 6GHz, etc., or channels or subchannels within each frequency band) depending on the use case. However, devices using conventional wireless LAN communication standards could not bundle different frequency bands (2.4GHz, 5GHz, 6GHz, etc.) used for communication. Furthermore, switching between frequency bands required disconnecting the current frequency band and reconnecting to a different frequency band.

[0008] Therefore, IEEE 802.11be allows communication devices to use multiple frequency bands and multiple links ( Multi-Link Operation (MLO), which enables multi-link connections, will be standardized. One example is the simultaneous operation of three link connections: 2.4GHz, 5GHz, and 6GHz. Of course, the combinations of frequency bands, channels, subchannels, and the number of simultaneous connections are not limited to these combinations and can vary. From a frequency band perspective, in the future, millimeter waves (45GHz band, 60GHz band, etc.) may also be used as one of the links that make up Multi-Link. According to MLO, communication equipment can maintain multiple link connections with different radio resources used and communication settings. In other words, by using MLO, communication equipment can simultaneously maintain link connections in different frequency bands. Not only can frames be transmitted and received using multiple links simultaneously, but it is also possible to switch the link connection used to transmit and receive frames (change the frequency band) without performing a reconnection operation.

[0009] Next-generation communication standards such as 6G and TGbn and beyond cite advanced XR (AR / VR) applications targeting immersive experiences as a use case. Advanced XR applications require low-latency communication over end-to-end (E2E), including reduced motion-to-photon latency and synchronization of video and audio. IEEE 802.11 addresses the control of low-latency traffic. To this end, Stream Classification Service (SCS) and Restricted Target Wake Time (R-TWT) have been implemented. SCS is a mechanism for classifying and prioritizing streams, and can efficiently handle real-time traffic such as audio and video. Specifically, when classifying MSDU, i.e., data, it uses User Priority (UP). By mapping the data to a Traffic Identifier (TID), the data can be accessed appropriately. Assign to Category (AC). In addition, SCS Drop Eligibility must meet the requirements. By dropping unnecessary traffic, efficient resource management becomes possible.

[0010] IEEE 802.11be's SCS now allows control of traffic flow (hereinafter referred to as streams or SCS streams) according to the QoS characteristics of traffic using the newly introduced QoS Characteristics Element. The QoS Characteristics Element allows for parametric specification of requirements such as bandwidth, delay bound, and jitter. Furthermore, SCS can be combined with R-TWT and MLO. For example, R-TWT controls other wireless devices from using channels during specific service periods (SPs) by reserving low-latency traffic and real-time traffic classified as high priority by SCS. This minimizes latency and promotes stable real-time communication. On the other hand, MLO optimizes resource utilization by distributing traffic classified by SCS across multiple wireless links. In addition, MLO can handle traffic on other links even if a specific link becomes overloaded, in order to maintain uninterrupted real-time streaming.

[0011] In SCS operations, each SCS stream is managed with a unique SCSID. Furthermore, traffic classified within an SCS stream is managed by TID. SCS stream setup involves the AP receiving an SCS Request from a Non-AP STA. An SCS connection is established by sending an SCS Response frame to the SCS stream. The QoS set for an SCS stream is determined based on the QoS Characteristic Element included in the SCS Request frame. For example, in an XR (AR / VR) application that handles various types of traffic such as video and audio, video, audio, and other data are set up as separate SCS streams. That is, the AP schedules to meet the individually required QoS for video, audio, and other data.

[0012] In the standardization of IEEE 802.11bn, discussions regarding QoS enhancement were held. This is being done (Non-Patent Document 1, Non-Patent Document 2). When multiple different SCS streams are set up between an AP and a Non-AP STA, and the same TID is set for those SCS streams, the AP cannot distinguish between these multiple different SCS streams (Non-Patent Document 1). This is because AP scheduling in SCS operations is handled on a TID basis that classifies traffic, rather than on information to identify the stream that manages the SCS stream (hereinafter also referred to as SCSID).

[0013] For example, if an XR (AR / VR) application requires audio-video synchronization, the application platform (AP) needs to schedule traffic so that the audio-video delay is below a certain value. However, with conventional technology, even if traffic classified into multiple different SCS streams is defined as low-latency traffic, it may be assigned the same TID (Time Identification Number). As a result, the AP cannot distinguish between multiple different SCS streams, making it difficult to schedule traffic to meet the application's requirements. [Prior art documents] [Non-patent literature]

[0014] [Non-Patent Document 1] IEEE 802.11-22 / 0041-00-00be, Jan.2022 [Non-Patent Document 2] IEEE 802.11-24 / 0660-00-00bn, Sept.2024 [Overview of the project] [Problems that the invention aims to solve]

[0015] In SCS operations, a challenge arises when the same TID is set for multiple different SCS streams, making it impossible to distinguish between the traffic between those SCS streams. [Means for solving the problem]

[0016] The station device and access point device according to the present invention, which solve the above-mentioned problems, are as follows.

[0017] (1) That is, a wireless communication device according to one aspect of the present invention is a station device comprising a control unit and a transmitting unit, wherein the control unit includes an SCS Descriptor element in an SCS Request frame, the transmitting unit transmits the SCS Request frame, the SCS Descriptor element includes one or more Optional subelements, and the Optional subelements include an Application Descriptor element.

[0018] (2) Furthermore, a wireless communication device according to one aspect of the present invention is an access point device comprising a transmitting unit and a receiving unit, wherein the receiving unit receives an SCS Request frame, the SCS Request frame includes an SCS Descriptor element, and the SCS Descriptor element is 1 or more Including the upper Optional subelements, and the Application Descriptor in the Optional subelements element is included, and when the transmission unit receives the SCS Request frame, the transmission unit transmits an SCS Response frame, which is characterized in that

Advantages of the Invention

[0019] According to the station device and access point device of the present invention, by associating a plurality of different SCS streams with information for identifying an application, the AP can collectively schedule SCS streams belonging to the same application, and it becomes possible to satisfy the requirement conditions of the application. As a result, the realization of low-latency communication can be expected.

Brief Description of the Drawings

[0020] [Figure 1] It is a diagram showing an example of a frame configuration according to an aspect of the present invention. [Figure 2] It is a diagram showing an example of a frame configuration according to an aspect of the present invention. [Figure 3] It is a diagram showing an example of the architecture of a wireless communication device according to an aspect of the present invention. [Figure 4] It is a schematic diagram showing an example of the division of a wireless medium according to an aspect of the present invention. [Figure 5] It is a diagram showing an example of a configuration of a communication system according to an aspect of the present invention. [Figure 6] It is a block diagram showing an example of a configuration of a wireless communication device according to an aspect of the present invention. [Figure 7] ]>It is a block diagram showing an example of a configuration of a wireless communication device according to an aspect of the present invention. [Figure 8] It is a block diagram showing an example of a configuration of a wireless communication device according to an aspect of the present invention. [Figure 9] It is a diagram showing an example of a frame configuration according to an aspect of the present invention. [Figure 10] This figure shows an example of a frame sequence configuration according to one aspect of the present invention. [Figure 11] This figure shows an example of a frame sequence configuration according to one aspect of the present invention. [Figure 12] This figure shows an example of a frame sequence configuration according to one aspect of the present invention. [Figure 13] This figure shows an example of a frame configuration according to one aspect of the present invention. [Figure 14] This figure shows an example of a frame configuration according to one aspect of the present invention. [Figure 15] This figure shows an example of a frame sequence configuration according to one aspect of the present invention. [Figure 16] This figure shows an example of a frame configuration according to one aspect of the present invention. [Figure 17] This figure shows an example of a frame configuration according to one aspect of the present invention. [Figure 18] This figure shows an example of a frame configuration according to one aspect of the present invention. [Figure 19] This figure shows an example of a frame configuration according to one aspect of the present invention. [Figure 20] This figure shows an example of a frame configuration according to one aspect of the present invention. [Figure 21] This figure shows an example of a frame configuration according to one aspect of the present invention. [Figure 22] This figure shows an example of a frame configuration according to one aspect of the present invention. [Modes for carrying out the invention]

[0021] The wireless communication system in this embodiment includes one access point device (AP, AP STA, also referred to as base station device) and multiple terminal devices (Non-AP STA, also referred to as station devices). Furthermore, the wireless communication system and network composed of the access point device and the terminal devices connected to the access point device are referred to as BSS (Basic Service Set). This is referred to as the "scope of management." In the following, when STA or wireless communication device is mentioned without limitation, it refers to an access point device, a station device, or both.

[0022] The access point devices and station devices within the BSS shall communicate based on CSMA / CA (Carrier sense multiple access with collision avoidance). This embodiment targets an infrastructure mode in which an access point device communicates with multiple station devices; however, the method of this embodiment can also be implemented in an ad-hoc mode in which station devices communicate directly with each other. In ad-hoc mode, station devices take the place of access point devices and form the BSS. The BSS in ad-hoc mode is referred to as IBSS (Independent Basic Service Set). It is also referred to as [another term]. In the following, a station device that forms an IBSS in ad-hoc mode can also be considered an access point device. The method of this embodiment can also be implemented in Wi-Fi Direct®, where station devices communicate directly with each other. In Wi-Fi Direct, station devices act as access point devices and form a Group. In the following, a station device that is the Group owner forming a Group in Wi-Fi Direct can also be considered an access point device.

[0023] Figure 3 shows the architecture diagram of a wireless communication device. The MAC layer corresponds to the upper layer of the PHY layer. The MAC layer may also be called the upper layer, and the PHY layer the lower layer. The PHY layer contains a management entity called PLME (Physical Layer Management Entity), and the management functions of the PHY layer are activated via PLME. Similarly, the MAC layer contains a management entity called MLME (Medium Access Control sublayer Management Entity), and the management functions of the MAC layer are activated via MLME.

[0024] SME (Station Management Entity) is a layer-independent entity, PH It has the role of setting parameter values ​​specific to layers such as PHY and MAC, such as collecting state specific to layers such as Y and MAC. There is an interface called MLME SAP (Service Access Point) between SME and MLME, and the MAC layer and SME interact by exchanging MLME SAP Primitives via MLME SAP. There is an interface called PLME SAP between SME and PLME, and the PHY layer and SME interact by exchanging PLME SAP Primitives via PLME SAP. The MAC layer and communication layers above the MAC layer interact by exchanging M layer Service Primitives (also called MAC SAP Primitives) via MAC SAP. The MAC layer and the PHY layer interact by exchanging PHY Service Primitives (also called MAC SAP Primitives) via PHY SAP. They interact through interaction. MLME SAP Primitive, PLME SAP Primitive, MAC Service Primitive, PHY Service Primitive, etc., are collectively referred to as Primitive.

[0025] In the IEEE 802.11 system, each wireless communication device has a common frame format. It is possible to transmit frames of multiple frame types. Frames consist of a physical (PHY) layer, a medium access control (MAC) layer, and a logical link layer. These are defined in the Logical Link Control (LLC) layer.

[0026] A frame in the PHY layer is called a Physical Protocol Data Unit (PPDU: PHY protocol data unit, physical layer frame, wireless frame, frame). A PPDU consists of a physical layer header (PHY header) which contains header information for signal processing in the physical layer, and a frame for the physical layer. The data unit being processed is the Physical Service Data Unit (PSDU: PHY service data PSDU consists of a retransmission unit in the wireless section and MAC layer frame, etc. It consists of MAC protocol data units (MPDUs) and aggregated MPDUs (A-MPDUs) which are composed of multiple MAC protocol data units. It is possible to do so.

[0027] The PHY header contains a short training field (STF) used for signal detection and synchronization, and channel information for data demodulation. The STF includes reference signals such as the Long Training Field (LTF) used in data demodulation, and control signals such as Signal (SIG) that contain control information for data demodulation. Furthermore, depending on the applicable standard, the STF can be non-High throughput-STF (non-HT STF or L-STF), High throughput-STF (HT-STF), or Very High-throughput STF (VHT-STF), High-efficiency STF (HE-STF), and They are classified into categories such as Extremely High Throughput-STF (EHT-STF), and LTF and SIG as well. Similarly, L-LTF, HT-LTF, VHT-LTF, HE-LTF, L-SIG, HT- They are classified into SIG, VHT-SIG, HE-SIG, and EHT-SIG. VHT-SIG is further classified into VHT-SIG-A1, VHT-SIG-A2, and VHT-SIG-B. Similarly, HE-SIG is classified into HE-SIG-A1~A4 and HE-SIG-B. In addition, a Universal SIGNAL (U-SIG) field containing additional control information may be included to accommodate technical updates within the same standard.

[0028] Furthermore, the PHY header may include information to identify the BSS that originated from the frame (hereinafter also referred to as BSS identification information). This information may include, for example, the BSS's SSID (Service Set Identifier) ​​or the MAC address of the BSS's access point device. Alternatively, the information to identify the BSS may be a value unique to the BSS other than the SSID or MAC address (e.g., BSS Color).

[0029] PPDU is modulated according to the corresponding standard. For example, IEEE 802.11b uses spread spectrum (DSSS), IEEE 802.11a and others use different modulation schemes. If it is a successor standard (such as IEEE802.11g / n / ac / ax / be / bn), the signal will be modulated using orthogonal frequency division multiplexing (OFDM).

[0030] A wireless communication device has either the function to transmit PPDUs, the function to receive them, or both. Figure 1 shows an example of a PPDU configuration transmitted by a wireless communication device. PPDUs compliant with the IEEE 802.11a / b / g standard include L-STF, L-LTF, L-SIG, and Data. The configuration includes frames (MAC frames, MAC frames, payload, data section, data, information bits, etc.). HT PPDU (High throughput PPDU), compliant with the IEEE 802.11n standard, includes L-STF, L-LTF, L-SIG, HT-SIG, HT-STF, HT-LTF, and Data frames. VHT PPDU (Very high throughput PPDU), compliant with the IEEE 802.11ac standard, includes L-STF, L-LTF, L-SIG, VHT-SIG-A, VHT-STF, VHT-LTF, VHT-SIG-B, and some or all of the MAC frames. HE PPDU (High efficiency PPDU), which conforms to the IEEE 802.11ax standard, is a structure that includes L-STF, L-LTF, L-SIG, RL-SIG (a temporal repetition of L-SIG), HE-SIG-A, HE-STF, HE-LTF, HE-SIG-B, and some or all of the Data frame. It is standardized in IEEE 802.11be. An EHT PPDU (Extremely High Throughput PPDU) consists of some or all of the following: L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, EHT-SIG, EHT-STF, EHT-LTF, and Data frames.

[0031] Figure 2 shows an example of an MPDU configuration. An MPDU (also called a MAC frame) contains a MAC header, which includes header information for signal processing at the MAC layer, a MAC service data unit (MSDU) or frame body, which is a data unit processed at the MAC layer, and a frame that is error-free. The MAC header consists of a Frame Check Sequence (FCS) that checks whether or not a frame is valid. The MAC header includes the Frame Control field, Duration / ID field, Address1 field, Address2 field, Address3 field, Sequence Control field, Address4 field, QoS Control field, HT Control field, Frame Body field, and FCS field. The Frame Control field indicates the frame type (such as management frame, control frame, data frame, or extension frame). The Duration / ID field (which can also be simply called the Duration field) contains a value corresponding to the length of the transmission opportunity. Address1 field, Address2 field, Address3 field The frame's sending address (TA: Transmitter Address) and receiving address (RA: Receiver Address) can be determined from information such as the Address4 field.

[0032] In Figure 1, L-STF, L-LTF, and L-SIG are commonly used in the IEEE 802.11 standard. This configuration allows for the following: (Hereafter, L-STF, L-LTF, and L-SIG will be collectively referred to as L-headers). For example, a wireless communication device compliant with the IEEE 802.11a / b / g standard can properly receive the L-header within a PPDU compliant with the IEEE 802.11n / ac standard. A wireless communication device compliant with the IEEE 802.11a / b / g standard can receive a PPDU compliant with the IEEE 802.11n / ac standard as if it were a PPDU compliant with the IEEE 802.11a / b / g standard.

[0033] However, wireless communication devices compliant with the IEEE 802.11a / b / g standards cannot demodulate the PPDU compliant with the IEEE 802.11n / ac standards that follows the L-header. Therefore, they cannot demodulate information regarding the Duration field, which is used to set the Transmitter Address (TA), Receiver Address (RA), and Network Allocation Vector (NAV) contained in the MAC header.

[0034] A wireless communication device compliant with the IEEE 802.11a / b / g standard should properly configure NAV (or As a method for performing reception operations for a predetermined period, IEEE 802.11 specifies that the L-SIG should be configured for Duration This specifies how to insert information. Information regarding the transmission speed within the L-SIG (RATE field, L-RATE field, L-RATE, L_DATARATE, L_DATARATE field) and information regarding the transmission period (LENGTH field, L-LENGTH field, L-LENGTH) are used in wireless communication compliant with the IEEE 802.11a / b / g standard. The device is used to properly configure NAV.

[0035] Next, we will explain how a wireless communication device can identify the BSS from a frame it receives. In order for a wireless communication device to identify the BSS from a frame it receives, the wireless communication device transmitting the PPDU must include information for identifying the BSS (BSS Color, BSS Identifier) ​​in the PPDU. It is preferable to insert information (values ​​specific to BSS). Information indicating BSS Color is HE -It can be included in SIG-A.

[0036] A wireless communication device can transmit an L-SIG multiple times (L-SIG Repetition). For example, a receiving wireless communication device can improve the demodulation accuracy of the L-SIG by receiving the multiple transmitted L-SIGs using MRC (Maximum Ratio Combining). When the signaling device successfully receives the L-SIG via MRC, it can interpret that the PPDU containing the L-SIG is a PPDU that conforms to the IEEE 802.11ax standard.

[0037] Even while receiving a PPDU, the wireless communication device also receives parts of other PPDUs (for example, the preamble, L-STF, L-LTF, and PHY header as defined by IEEE 802.11). The device can perform a receiving operation (also called a dual receiving operation) for PPDUs, etc. If the wireless communication device detects a part of a PPDU other than the PPDU in question during the PPDU receiving operation, it can update some or all of the destination address, source address, and information regarding the PPDU or DATA period.

[0038] MAC layer frame types include management frames (also called wireless management frames) which manage the connection status between wireless communication devices, and control frames (also called control frames) which manage the communication status between wireless communication devices. Control frames are broadly classified into three types: frames (also called wireless control frames), and data frames containing the actual transmitted data. Each of these is further classified into several subframe types. Control frames include Acknowledge (Ack) frames, Request to Send (RTS) frames, and Clear to Send (CTS) frames. This includes things like beacon frames, probe request frames, probe response frames, and authentication frames. This includes connection frames, association request frames, association response frames, deauthentication frames, etc. Data frames include data frames, polling (QoS CF-poll) frames, etc. Each wireless communication device reads the contents of the Frame Control field in the MAC header to determine the frame type and subframe of the received frame. You can understand the frame type.

[0039] MMPDU (MAC Management Protocol Data Unit) is a data unit exchanged between MAC entities, and includes Mesh Control fields and Management MIC (Message It may include an Integrity Code element (MME: Management MIC Element). Even without it, the MAC header, MMPDU (stored in the frame body in Figure 2), and inspection unit are linked together to form a MAC frame, which is called a management frame.

[0040] Note that Ack may include Block Ack. Block Ack can send reception completion notifications to multiple MPDUs.

[0041] The beacon frame contains the beacon transmission interval and the SSID. This includes fields to be recorded, information elements, etc. The access point device periodically sends beacon frames within the BSS. It is possible to notify the access point devices, and by receiving beacon frames, the station device can ascertain the presence and capability information of access point devices in the vicinity of the station device. When the station device ascertains access point devices based on beacon frames notified by the access point devices, this is called passive scanning. On the other hand, when the station device searches for access point devices by notifying the BSS of a probe request frame, this is called active scanning. The access point device can transmit a probe response frame in response to the probe request frame, and the contents of the probe response frame are equivalent to those of the beacon frame.

[0042] After recognizing the access point device, the station device performs a connection process to that access point device. The connection process is classified into an authentication procedure and an association procedure. The station device then contacts the access point device it wishes to connect to. In response, the access point sends an authentication frame (authentication request). Upon receiving the authentication frame, the access point sends an authentication frame (authentication response) to the station device, which includes a status code indicating whether or not authentication to the station device was granted. The station device can determine whether or not its wireless communication device has been authorized for authentication by the access point by reading the status code contained in the authentication frame. The access point and station devices can exchange authentication frames multiple times.

[0043] Following the authentication procedure, the station device sends a connection request frame to the access point device to initiate the connection procedure. Upon receiving the connection request frame, the access point device determines whether to allow the station device to connect and sends a connection response frame to notify the access point of this decision. The connection response frame contains a status code indicating whether the connection process was successful or not, as well as an Association Identifier (AID) to identify the station device. By assigning a different AID to each station device for which a connection has been permitted, the access point device can identify and manage multiple station devices.

[0044] For example, the station device according to this embodiment performs connection processing with the access point device. When a connection is established, a connection request frame is sent. Upon receiving the connection request frame, the access point device determines whether to allow the connection with the station device and sends a connection response frame to notify the user of this decision. The connection request frame and connection response frame contain fields indicating the capability information of the transmitting wireless communication device. The follow-up request frame and the connection response frame include a UHR Capabilities element, which may include fields such as UHR MAC Capabilities Information and UHR PHY Capabilities Information.

[0045] After the connection process is completed, the access point device and the station device perform actual frame transmission and reception (also called frame exchange). In IEEE 802.11 systems, distributed control The following mechanisms are defined: Distributed Coordination Function (DCF), Point Coordination Function (PCF), and extended mechanisms such as Enhanced Distributed Channel Access (EDCA) and Hybrid Coordination Function (HCF). The following explanation will use the example of an access point device transmitting frames to a station device using DCF.

[0046] In DCF, access point devices and station devices perform carrier sense (CS) to check the usage status of radio channels around their own radio communication device before transmitting a frame. For example, if a radio communication device (transmitting station) that plans to transmit a frame is access... This explanation assumes an access point device, but the same applies when the transmitting station is a station device. When an access point device receives a signal higher than a predetermined Clear Channel Assessment Level (CCA level) on a radio channel, it delays the transmission of the frame on that radio channel. Hereinafter, the state in which a signal above the CCA level is detected on the radio channel will be referred to as the Busy state, and the state in which no signal above the CCA level is detected will be referred to as the Idle state. This type of CS, performed by each wireless communication device based on the power of the signal actually received (received power level), is called physical carrier sense (physical CS). The CCA level is also called the carrier sense level (CS level) or CCA threshold (CCA threshold: CCAT). If the demodulation device detects a signal above the CCA level, it will begin demodulating at least the signal from the PHY layer.

[0047] Access point devices perform carrier sensing over an inter-frame space (IFS) depending on the type of frame they transmit to determine whether the wireless channel is busy or idle. The duration of carrier sensing by the access point device varies depending on the frame type and subframe type of the frame the access point device will transmit. In IEEE 802.11 systems, multiple IFSs with different durations are defined, with the highest priority given to the most important. Short IFS (SIFS) is the short frame interval used for a given transmission frame, priority. The frame interval (PCF IFS: PIFS) used for transmission frames with a relatively high priority. Distributed control frame interval (DCF IFS: DIFS) used for low-speed transmission frames, etc. There is.

[0048] After the access point device waits for the DIFS period, it waits for an additional period of random backoff time to prevent frame collisions. In IEEE 802.11 systems, The back-off time is set within the Contention window (CW). In CSMA / CA, it is assumed that a transmission frame sent by one transmitting station is received by a receiving radio communication device (the receiving station) without interference from other transmitting stations. Therefore, if transmitting stations transmit frames at the same time, the frames will collide, and the receiving station will not be able to receive them correctly. To avoid this, each transmitting station waits for a randomly set amount of time before starting to transmit, thus preventing frame collisions. The access point device (corresponding to the transmitting station in this explanation) uses carrier sense to determine which radio channel is available. If the system determines that the channel is in a dollar state, it starts counting down the backoff counter. Only when the backoff counter reaches zero does it gain the opportunity to transmit and send a frame to the station device (corresponding to the receiving station in this explanation). If the access point device determines that the radio channel is busy via carrier sense while the backoff counter is counting down, it stops counting down the backoff counter. When the radio channel becomes idle, the access point device waits for the same period as the IFS (DIFS) mentioned earlier, and then resumes counting down the remaining backoff counter.

[0049] The receiving station device receives a frame, reads the PHY header of the frame, and demodulates the received frame. The station device can then read the MAC header of the demodulated signal to determine whether the frame is intended for its own radio communication device. The station device can also determine the destination of the frame based on the information contained in the PHY header (for example, in the case of a frame corresponding to VHT PPDU, the group identifier (GID) listed in VHT-SIG-A).

[0050] The station device determines that the received frame is intended for its own radio communication device, and if it has successfully demodulated the frame, it sends an Ack frame to the access point device (the transmitting station) to indicate that the frame was received correctly. The Ack frame is one of the highest priority frames, transmitted without a random backoff time after the SIFS waiting period. When the access point device receives the Ack frame from the station device, one frame exchange is considered successful and completes. If the station device fails to receive the frame correctly, it does not send an Ack. Therefore, if the access point device does not receive an Ack frame from the receiving station within a certain period (SIFS + Ack frame length, etc.) after transmitting the frame, it can consider that one frame exchange has failed. Thus, the completion of one frame exchange in an IEEE 802.11 system is Except in special cases such as the transmission of notification signals like beacon frames or when fragmentation is used to divide the transmitted data, the determination will always be based on whether or not an Ack frame has been received.

[0051] If a station device determines that a received frame is not intended for its own wireless communication device, it sets a Network Allocation Vector (NAV) based on the response corresponding to the length of the acquired transmission opportunity, as described in the MAC header or PHY header. The station device does not attempt communication for the period set in the NAV. In other words, the station device performs the same action as if the radio channel were busy based on the physical CS, for the period set in the NAV, and therefore communication control by NAV is also called virtual carrier sense (virtual CS). The NAV can be set based on the information described in the MAC header or PHY header, and in the case of a frame corresponding to HE PPDU... Alternatively, the value specified in the TXOP field included in HE-SIG-A may be used. Furthermore, NAV can also be configured by Request to Send (RTS) frames and Clear to Send (CTS) frames, which are introduced to resolve the Hidden Terminal problem. The value specified in the Duration field included in the MAC header is used.

[0052] In contrast to DCF, where each wireless communication device performs carrier sensing and autonomously acquires transmission opportunities, PCF involves a control station called a point coordinator (PC). It controls the transmission opportunities of each wireless communication device within the BSS. Generally, the access point device acts as a PC and acquires the transmission rights of the station devices within the BSS.

[0053] The communication period under PCF includes a contention-free period (CFP) and a contention-free period. (CP: Contention period) is included. During the CP, the DCF described above is used. Once communication is established, the PC controls the transmission opportunity during the CFP (Communication Frequency). The access point device, which is the PC, broadcasts a beacon frame containing information such as the CFP duration (CFP Max duration) into the BSS prior to PCF communication. PIFS (Pilot-Input-Frequency System) is used to transmit the beacon frame broadcast at the start of PCF transmission, and it is transmitted without waiting for a random backoff time. The station device that receives this beacon frame sets the CFP duration specified in the beacon frame to the NAV (Network Address Vote). Thereafter, until the NAV has elapsed or a signal (e.g., a data frame containing CF-end) indicating the end of the CFP is received within the BSS, the station device can only acquire a transmission opportunity if it receives a signal (e.g., a data frame containing CF-poll) from the PC signaling the acquisition of a transmission opportunity. During the CFP period, packet collisions do not occur within the same BSS, so each station device does not take the random backoff time used in DCF.

[0054] A wireless medium can be divided into multiple resource units (RUs). Figure 4 is a schematic diagram showing an example of the partitioning state of a wireless medium. For example, in resource partitioning example 1, the wireless communication device can partition the frequency resource (subcarrier), which is the wireless medium, into 9 RUs. Similarly, in resource partitioning example 2, the wireless communication device can partition the subcarrier, which is the wireless medium, into 5 RUs. Of course, the resource partitioning examples shown in Figure 4 are just examples, and for example, multiple RUs can each be composed of a different number of subcarriers. In addition, the wireless medium partitioned as RUs can include not only frequency resources but also spatial resources. A wireless communication device (e.g., an access point device) can transmit frames to multiple wireless communication devices (e.g., multiple station devices) simultaneously by placing frames destined for different station devices in each RU. Information An access point device can include information indicating the partitioning state of the wireless medium (Resource allocation) as common control information in the PHY header of the frames it transmits. Furthermore, an access point device can include information indicating the RU to which frames destined for each station device are placed (resource unit assignment information) as unique control information in the PHY header of the frames it transmits.

[0055] Furthermore, multiple wireless communication devices (e.g., multiple station devices) can simultaneously transmit frames by placing and transmitting frames on their respective assigned RUs. After receiving a frame containing trigger information (Trigger frame: TF) transmitted from an access point device, the multiple station devices wait for a predetermined period of time before transmitting the frame. Communication can be conducted. Each station device can determine the RU assigned to its radio communication device based on the information contained in the TF. In addition, each station device can acquire RUs through random access based on the TF. [1. First Embodiment]

[0056] The application used in this embodiment is an application that uses one or more Non-AP STAs. A Non-AP STA can notify its associated APs of an identifier (hereinafter also referred to as information for identifying the application) for managing multiple different SCS streams used by the application as a single group. In other words, the information for identifying the application can bundle two or more different SCS streams used by the application.

[0057] Furthermore, the application used in this embodiment may also set QoS parameters requested by the application, in addition to information for identifying the application (hereinafter also referred to as Application ID). The QoS parameters requested by the application are the time required to transmit traffic belonging to multiple different SCS streams, and the time required for transmission. This can include the set tolerance for delay time, as well as the allowable jitter between multiple different SCS streams and the MSDU Delivery Ratio. These different SCS streams are not limited to specific applications, such as audio stream-video stream or data stream-audio stream. Furthermore, in applications such as XR (AR / VR), the allowable delay time and jitter set for the delay between the stream processing tracking data and the stream transmitting audio and video accordingly (Motion-to-Photon delay), and the delay between the audio stream and video stream (Audio-video delay), can be taken into consideration. ru.

[0058] Furthermore, the QoS parameters required by an application are not limited to specific definitions, uses, or scopes. For example, they could include the delay between the stream processing tracking data and the corresponding stream transmitting audio / video, the acceptable jitter between the audio and video streams, and the MSDU Delivery Ratio. Hereafter, the QoS parameters required by an application will also include Time Difference Bound. It is referred to as such, but the name is not limited to it. Time Difference Bound is, in principle, A This may be newly defined based on the requirements of the application layer or information that sets the class of streams belonging to multiple different SCS streams that make up the application (hereinafter also referred to as QoS Characteristics Element). However, the names and target of these settings are not limited. As will be discussed later, Non-AP STA and AP can set fields in frames (SCS Request / Response frames, trigger frames, TWT Request / Response frames, etc.) that contain QoS parameters requested by the application.

[0059] The wireless communication system in this embodiment will be explained using Figure 5. The wireless communication system 2-5 (also referred to as BSS2-5) includes an access point device 1-1. Furthermore, station devices 2-1, 2-2, 2-3, and 2-4 are collectively referred to as station device 2A ( ) as station devices connected to (associated with) the access point device 1-1. It is also referred to as terminal device 2A. Access point device 1-1 and station device 2A are wirelessly connected and are in a state where they can send and receive frames from each other. Hereafter, BSS will also be referred to as the communication area (coverage).

[0060] The wireless communication system 3-5 (also referred to as BSS3-5) includes an access point device 1-2 and station devices 3-1, 3-2, 3-3, and 3-4. Furthermore, station devices 3-1, 3-2, 3-3, and 3-4 are collectively referred to as station device 2B (terminal device 2B) as devices connected (associated) with access point device 1-2. It is also referred to as [another name]. Access point device 1-2 and station device 2B are wirelessly connected and are in a state where they can send and receive wireless frames to and from each other.

[0061] In this embodiment, the BSS may be a wireless communication device (also referred to as UHR AP, UHR AP MLD, Non-AP UHR STA, or Non-AP UHR MLD) that conforms to the IEEE 802.11bn standard or the next-generation standard of IEEE 802.11bn. In this embodiment, at least wireless communication devices 1-1 to 1-2 (access point devices 1-1 to 1-2), wireless communication devices 2-1 to 2-4 (station devices 2-1 to 2-4), and wireless communication devices 3-1 to 3-4 (station devices 3-1 to 3-4) are included. The numbers are for convenience only.

[0062] Furthermore, in Figure 5, access point device 1-1 is located within the coverage of access point device 1-2's wireless communication system 3-5. Similarly, access point device 1-2 is located within the coverage of access point device 1-1's wireless communication system 2-5. Therefore, it is assumed that access point devices 1-1 and 1-2 can transmit and receive wireless frames from each other.

[0063] Wireless communication equipment is a multi-link device (MLD: Multi-Link) capable of multi-link communication. It may also be an MLD-compatible access point device. Access point devices (access point multilink devices or AP MLDs) and station devices compatible with MLDs will be referred to as MLD station devices (non-access point multilink devices or Non-AP MLDs). MLD access point devices and MLD station devices will also be collectively referred to as MLD wireless communication devices. Furthermore, APs belonging to AP MLDs will be referred to as Affiliated APs or sub-access point devices, and station devices belonging to Non-AP MLDs will be referred to as Non-AP STAs or sub-station devices. In other words, the APs and station devices according to this embodiment... The station device is a multilink device, the AP is an access point multilink device, and the station device is a non-AP multilink device.

[0064] Figure 6 will be used to explain the MLD access point device 20000-1 and the MLD station device 30000-1. An MLD wireless communication device consists of multiple sub-wireless communication devices corresponding to the frequency band (or channel, or subchannel) of each link (also called a physical layer link) that constitutes a multilink. Figure 6 shows an example where the MLD access point device 20000-1 consists of three sub-wireless communication devices, in this case three sub-access point devices (20000-2, 200000-3, 20000-4), but the number of sub-access point devices can be any number of one or more. Similarly, Figure 6 shows an example where the MLD station device 30000-1 consists of three sub-wireless communication devices, in this case three substation devices (30000-2, 300000-3, 30000-4), but the number of substation devices can be any number of one or more. Furthermore, a sub-wireless communication device (such as a sub-access point device or sub-station device) may consist of only a portion of the circuits within the wireless communication device, and may be referred to as a sub-wireless communication unit (sub-access point unit or sub-station unit).

[0065] In Figure 6, multiple sub-wireless communication devices are shown as logically separate blocks (rectangular boxes) for illustrative purposes, but physically they may be configured as a single wireless communication device. Alternatively, they may be configured as separate sub-wireless communication devices, in which case each sub-access point device transmits and receives the necessary information via connections 9-1 and 9-2, and each substation device transmits and receives the necessary information via connections 9-3 and 9-4. In this embodiment, the MLD wireless communication device is assumed to consist of a single physical wireless communication device (10000-1), and its configuration will be explained using Figures 7 and 8, which will be described later.

[0066] Figure 7 shows an example of the device configuration of wireless communication devices 1-1, 1-2, 2A, and 2B (hereinafter collectively referred to as wireless communication device 10000-1). Wireless communication device 10000-1 includes an upper layer section (upper layer processing step) 10001-1, an autonomous distributed control section (autonomous distributed control step) 10002-1, a transmitting section (transmitting step) 10003-1, a receiving section (receiving step) 10004-1, and an antenna section 10005-1. For example, wireless communication devices 1-1 and 1-2 are AP-MLDs, and AP-MLD1-1, AP-MLD1-2, terminal devices 2A and 2B may be Non-AP MLD1 and Non-AP MLD2. Furthermore, the STAs connected to the Non-AP MLD1 are Non-AP STAs, and are also referred to as Non-AP STA2-1, Non-AP STA2-2, Non-AP STA2-3, and Non-AP STA2-4, respectively. The STAs in question are Non-AP STAs, and are also referred to as Non-AP STA3-1, Non-AP STA3-2, Non-AP STA3-3, and Non-AP STA3-4, respectively.

[0067] The upper layer 10001-1 has the functionality of the MAC layer and the DS (Distribution System) It is connected to other networks and other BSSs via this, and can transmit information to the autonomous distributed control unit 10002-1, for example, information destined for other wireless communication devices, or control information contained in management frames or control frames. In addition, the upper layer unit 10001-1 is stream Information for setting the class, information for identifying the stream, application requirements, information for identifying the application, or some or all of the QoS parameters requested by the application may be transmitted to the lower layer. The upper layer 10001-1 may also have MLME functionality, and the upper layer can be configured to transmit the generated frame over one or more links configured for MLD. The upper layer 10001-1 can be configured to include a MAC layer frame generation unit (MAC frame generation step) 10001a-1 and an upper layer control unit (upper layer control step) 10001b-1. The upper layer control unit (upper layer control step) is also simply referred to as the control unit (control step). The MAC layer frame generation unit 10001a-1 generates a MAC frame by adjusting the information bits to a size that fits within the frame body and adding a MAC header and FCS. The information bits include data for constituting a data frame, as well as management data for constituting a management frame and control data for constituting a control frame. The upper layer control unit 10001b-1 performs control related to communication with the DS and communication related to communication with the physical layer, in addition to control within the upper layer unit 10001-1.

[0068] Figure 8 shows an example of the device configuration of the autonomous distributed control unit 10002-1. The autonomous distributed control unit 10002-1 includes a CCA unit (CCA step) 10002a-1, a backoff unit (backoff step) 10002b-1, and a transmission decision unit (transmission decision step) 10002c-1. The CCA unit 10002a-1 can determine the state of a radio resource (including whether it is busy or idle) using either or both of the information regarding the received signal power received via the radio resource and the information regarding the received signal (including the decoded information), which are notified by the receiving unit 10004-1. The CCA unit 10002a-1 can notify the backoff unit 10002b-1 and the transmission decision unit 10002c-1 of the state determination information of the radio resource.

[0069] The backoff unit 10002b-1 can perform a backoff procedure using the status determination information of the radio resource. The backoff unit 10002b-1 has a countdown function for a random backoff time set within CW. For example, it can execute the countdown of the backoff counter when the status determination information of the radio resource indicates idle, and stop the countdown of the backoff counter when the status determination information of the radio resource indicates busy. The backoff unit 10002b-1 can notify the transmission determination unit 10002c-1 of the value of the backoff counter.

[0070] The transmission decision unit 10002c-1 makes a transmission decision using either the status determination information of the wireless resource, the value of the backoff counter, or both. For example, when the status determination information of the wireless resource indicates idle and the value of the backoff counter is 0, it can notify the transmission unit 10003-1 of the transmission decision information. Also, when the status determination information of the wireless resource indicates idle, it can notify the transmission unit 10003-1 of the transmission decision information.

[0071] The transmission unit 10003-1 includes a physical layer frame generation unit (physical layer frame generation step) 10003a-1 and a wireless transmission unit (wireless transmission step) 10003b-1. The physical layer frame generation unit 10003a-1 has the function of generating a physical layer frame (PPDU) based on transmission decision information notified from the transmission decision unit 10002c-1. The physical layer frame generation unit 10003a-1 applies error correction coding, modulation, pre-recording filter multiplication, etc., to the transmission frame sent from the upper layer. The physical layer frame generation unit 10003a-1 outputs the generated physical layer frame to the wireless transmission unit 10003b-1.

[0072] The physical layer frame generation unit 10003a-1 applies error correction coding to the information bits input from the MAC layer, but what is the unit (coded block length) of error correction coding applied? It is not limited to this. For example, the physical layer frame generation unit 10003a-1 can divide the information bit sequence input from the MAC layer into information bit sequences of a predetermined length, apply error correction coding to each, and create multiple coded blocks. When constructing coded blocks, dummy bits can also be inserted into the information bit sequence input from the MAC layer.

[0073] The frame generated by the physical layer frame generation unit 10003a-1 includes control information. This control information includes information indicating which RU (where RU includes both frequency resources and spatial resources) the data destined for each wireless communication device is located in. The frame generated by the physical layer frame generation unit 10003a-1 also includes a trigger frame that instructs the destination terminal wireless communication device to transmit the frame. This trigger frame includes information indicating the RU that the wireless communication device will use when transmitting the frame after being instructed to do so.

[0074] The wireless transmission unit 10003b-1 converts the physical layer frame generated by the physical layer frame generation unit 10003a-1 into a radio frequency (RF) signal, and transmits it as a radio frequency signal. The unit generates a signal. The processing performed by the wireless transmitter 10003b-1 includes digital-to-analog conversion, filtering, and frequency conversion from the baseband to the RF band.

[0075] The receiving unit 10004-1 includes a wireless receiving unit (wireless receiving step) 10004a-1 and a signal demodulation unit (signal demodulation step) 10004b-1. The receiving unit 10004-1 generates information regarding the received signal power from the RF band signal received by the antenna unit 10005-1. The receiving unit 10004-1 can notify the CCA unit 10002a-1 of the information regarding the received signal power and the information regarding the received signal.

[0076] The wireless receiver unit 10004a-1 has the function of converting the RF band signal received by the antenna unit 10005-1 into a baseband signal and generating a physical layer signal (e.g., a physical layer frame). The processing performed by the wireless receiver unit 10004a-1 includes frequency conversion from the RF band to the baseband band, filtering, and analog-to-digital conversion.

[0077] The signal demodulation unit 10004b-1 has the function of demodulating the physical layer signal generated by the wireless receiver unit 10004a-1. The processing performed by the signal demodulation unit 10004b-1 includes channel equalization, demapping, error correction decoding, etc. The signal demodulation unit 10004b-1 can extract from the physical layer signal, for example, information contained in the physical layer header, information contained in the MAC header, and other information contained in the MAC frame. The signal demodulation unit 10004b-1 can output the extracted information to the upper layer unit 10001-1. The signal demodulation unit 10004b-1 can extract any or all of the information contained in the physical layer header, the MAC header, and other information contained in the MAC frame.

[0078] The antenna unit 10005-1 has the function of transmitting the radio frequency signal generated by the radio transmission unit 10003b-1 into the radio space toward another radio device 10000-1. The antenna unit 10005-1 also has the function of receiving the radio frequency signal transmitted from the other radio device 10000-1.

[0079] The wireless communication device 10000-1 can cause surrounding wireless communication devices to set NAV for a period of time by including information indicating the period during which the wireless medium will be used based on the transmission opportunity acquired by the wireless communication device in the PHY header or MAC header of the frame to be transmitted. For example, the wireless communication device 10000-1 may include information in the Duration field of the MAC header of the frame to be transmitted, or the Length field of the L-SIG included in the PHY header, or the HE PPDU field. In the case of HE-SIG-A, information indicating the relevant period can be included in the TXOP field, or in the case of EHT PPDU, in the TXOP field of U-SIG. The NAV period set in the wireless communication devices surrounding the wireless communication device shall be called the transmission opportunity (or TXOP period, also simply called TXOP) acquired by wireless communication device 10000-1. The wireless communication device 10000-1 that acquired this transmission opportunity shall be called the TXOP holder. This is called a control frame (or ruler). The frame type of the frame that the wireless communication device 10000-1 transmits to notify of a transmission opportunity acquired is not limited to any particular type, but is a control frame (e.g., CTS frame, RTS frame, MU-RTS (multi-user request to send) frame, MU-RTS trigger frame, BSRP (Buffer Status Report Poll) trigger frame). It can be a CTS-to-self frame, or a data frame sent in a format such as Non-HT PPDU, HT PPDU, VHT PPDU, EHT PPDU, or UHR PPDU.

[0080] A wireless communication device 10000-1, which is a TXOP holder, can transmit frames to wireless communication devices other than itself during the transmission opportunity. If wireless communication device 1-1 is a TXOP holder, wireless communication device 1-1 can transmit frames to wireless communication device 2A during the transmission opportunity. Also, wireless communication device 1-1 can instruct wireless communication device 2A to transmit frames addressed to wireless communication device 1-1 during the transmission opportunity. Wireless communication device 1-1 can transmit a trigger frame to wireless communication device 2A during the transmission opportunity that includes information instructing wireless communication device 2A to transmit frames addressed to wireless communication device 1-1. For example, wireless communication device 1-1 transmits to all communication bands (operation bandwidth, operation channel, etc.) where frame transmission and reception may occur. You may acquire an opportunity to transmit, or you may acquire an opportunity to transmit to a specific communication band and channel, such as the communication bandwidth (transmit / receive bandwidth, transmit / receive channel) used to actually send and receive frames.

[0081] The wireless communication devices to which wireless communication device 1-1 issues frame transmission and reception instructions within the period of the transmission opportunity it has acquired are not necessarily limited to wireless communication devices connected to itself. For example, a wireless communication device may send management frames such as Reassociation frames, RTS / MU-RTS / BSRP / CTS frames to wireless communication devices in its vicinity. To transmit control frames and data frames, such as M, it is possible to instruct wireless communication devices not connected to the wireless communication device itself to send and receive frames using trigger frames or similar methods.

[0082] Furthermore, we will also explain the transmission opportunities in EDCA, which is a different channel access method (data transmission method) from DCF. The IEEE 802.11e standard is related to EDCA, and This document defines transmission opportunities from the perspective of ensuring Quality of Service (QoS) for various services such as video transmission and VoIP. Services are broadly classified into four access categories: VO (Voice), VI (Video), BE (Best Effort), and BK (Background). Generally, the order of priority from highest to lowest is VO, VI, BE, and BK. Each access category includes settings for the minimum CW value (CWmin), the maximum CW value (CWmax), the length of the AIFS (Arbitration IFS), a type of IFS, and the TXOP Limit, which is the upper limit of transmission opportunities. There are parameters (EDCA Parameters) that are set in the access category, and their values ​​are set to create a difference in priority between access categories. For example, for VO, which has the highest priority for voice transmission, setting CWmin, CWmax, and AIFS to relatively small values ​​compared to other access categories allows for data transmission to be prioritized over other access categories. For example, for VI, which transmits a relatively large amount of data for video transmission, setting a large TXOP Limit allows for a longer transmission opportunity than other access categories. In this way, the values ​​of the EDCA Parameters for each access category are adjusted to guarantee QoS according to the various services.

[0083] The signal demodulation unit 10004b-1 of the station device processes the received signal to the physical layer. Decoding and error detection can be performed. Here, the decoding process includes decoding the error correction code applied to the received signal. Here, error detection includes error detection using an error detection code pre-assigned to the received signal (e.g., cyclic redundancy check (CRC) code) or error detection using an error correction code that inherently has an error detection function (e.g., low-density parity check (LDPC) code). Decoding in the physical layer can be applied to each encoded block.

[0084] The upper layer unit 10001-1 receives the decoding result of the physical layer in the signal demodulation unit 10004b-1 and decodes the MAC layer signal. Then, error detection is performed in the MAC layer (hereinafter also referred to as the MAC layer) to determine whether the MAC layer signal transmitted by the station device that transmitted the received frame was correctly decoded.

[0085] Furthermore, the number of sub-access point devices included in one MLD access point device (also referred to as APs belonging to AP MLD or Affiliated APs), and the number of MLD station devices The number of substation devices (also referred to as Non-AP STAs belonging to Non-AP MLDs) included in a device may vary depending on the grade, class, and capabilities of each MLD wireless communication device. High-grade, high-class, and high-capacity MLD wireless communication devices may have a different number of sub-radio communication devices (sub-access point devices, substation devices) compared to other MLD wireless communication devices. In other words, for each MLD wireless communication device located within a single wireless communication system, the number of sub-radio communication devices (sub-access point devices, substation devices) that make up each MLD wireless communication device may vary depending on the grade, class, and capabilities, and these numbers do not have to be the same.

[0086] In Figure 6, substation device 30000-2 is connected (associated) with subaccess point device 20000-2, establishing link 1. Substation device 30 000-3 is connected to (Associated with) sub-access point device 20000-3, Link 2 is established. Substation device 30000-4 connects (associates) to subaccess point device 20000-4 and establishes link 3. In this embodiment, multi The number of links that make up a link is set to three, but it is not limited to this and can be any number except zero. In this embodiment, the frequency used by each link can be arbitrarily set from among the 2.4GHz band, 5GHz band, 6GHz band, 60GHz band, and other frequency bands, channels, and subchannels supported by the wireless communication system, and may change depending on the laws and regulations of each country.

[0087] Although wireless communication systems 2-5 and 3-5 form different BSSs, this does not necessarily mean that they have different ESSs (Extended Service Sets). An ESS represents a service set that forms a LAN (Local Area Network). Therefore, wireless communication devices belonging to the same ESS can be considered to belong to the same network from a higher layer perspective. Furthermore, BSSs are combined via a DS (Distribution System) to form an ESS. This forms the wireless communication system 2-5 and wireless communication system 3-5 may each be further equipped with multiple wireless communication devices.

[0088] SCS is a function that enables the classification of received MSDUs using Layer 2 / Layer 3 signaling. After being assigned to an access category, individually addressed MSDUs (hereinafter also referred to as individually addressed MSDUs) can be given Drop eligibility. This is possible when Intra-access category prioritization is enabled. In addition, SCS can assign MSDUs that match the classification to the primary or alternate transmit queue. SCS uses SCS to connect Non-AP STAs and APs. The stream is established, and MSDUs are allocated according to QoS. From here on, APs and Non-AP STAs are used. The embodiments will be explained using this method, but it can also be applied to communication between APs, as long as it supports Application ID and SCS.

[0089] The AP or Non-AP STA according to this embodiment conforms to the IEEE 802.11bn standard or the aforementioned standard as described above. The wireless communication device may be compliant with the following standards, and may be an AP MLD consisting of one or more APs or a Non-AP MLD consisting of one or more Non-AP STAs. An AP can configure multiple different SCS streams with one or more Non-AP STAs. A Non-AP STA or AP can use the SCSID that manages the SCS stream to create, modify, or delete SCS streams. An AP can classify each traffic based on the QoS parameters provided by the Non-AP STA for the SCS stream established with the Non-AP STA. Based on this classification, UP (User Priority) is mapped to all MSDUs associated with each traffic, and The TID is set based on the UP. Additionally, Drop Eligibility and EDCA transmission queue settings can be configured for all MSDUs associated with each traffic. This allows the AP to perform scheduling and transmission control based on the priority of each traffic.

[0090] Figure 9 shows an example of the UHR MAC Capabilities Information field. APs and Non-AP STAs set a field to indicate whether or not they support information for identifying the application. Specifically, APs and Non-AP STAs may include an Application ID Support subfield in the UHR MAC Capabilities Information field if Dot11ApplicationIDImplemented is true. Also, if the Application ID Support subfield is included in the UHR MAC Capabilities Information field, the Application ID may be set in that subfield.

[0091] When performing SCS operations using Application ID, the AP and Non-AP STA set the Application ID Support subfield of the UHR MAC Capabilities Information field to 1. One or more Non-AP STAs send an SCS Request frame to the connected AP. I believe it. Non-AP STA uses information to define the stream class (QoS Characteristics Element) and information to identify the application (Application ID) to identify the stream. Information can be associated with it for differentiation. For example, one or more Non-AP STAs can include an Application ID subfield in the QoS Characteristics Element (see Figure 13, middle) of the SCS Descriptor Element (see Figure 13, bottom) within the SCS Descriptor List field of the SCS Request frame, setting a common Application ID for two or more different SCSIDs. It is possible. Furthermore, if one or more Non-AP STAs include the Application ID subfield, they may also include the Time Difference Bound subfield, and two or more different subfields. Time Difference Bound can be set for the SCSID. Bound will be discussed later.

[0092] Figure 10 shows an example of SCS operation using Application ID. Non-AP STA#1 and Non-AP STA#2 are connected to the AP and are running different applications. Non-AP STA#1's application consists of multiple types of traffic, while Non-AP STA#2's application consists of a single type of traffic. Non-AP STA#1 sends SCS Request frames (100-1 to 100-3) to the AP to set up SCS streams for each type of traffic that makes up its application. In this process, Non-AP STA#1 assigns Application ID#X to the application and sends SCS Request frame 100-1, which has SCSID#M set, and SCS Request frame 100-2, which has SCSID#N set, associating Application ID#X with these two frames. Meanwhile, Non-AP STA#2 sends SCS Request frame 100-3, which has SCSID#O set, to the AP.

[0093] AP receives SCS Request frames from one or more Non-AP STAs that it associates with. Upon receiving the SCS Request frame, it sends an SCS Response frame as a response to that SCS Request frame. This is possible. In the example in Figure 10, the AP sends an SCS Response frame (100-4) to the received SCS Request frame, and the Non-AP STA#1, Non-AP STA#2, and SCS stream This allows for the setup of an SCS stream in Non-AP STA#1 where the SCSID and Application ID are associated, enabling scheduling based on that Application ID. The SCS Descriptor element in the SCS Descriptor List field of an SCS Request frame received from one or more Non-AP STAs contains multiple different SCSIDs, and two or more of these SCSIDs share a common Application ID. The SCSID corresponding to this Application ID is different from the SCSIDs corresponding to other Application IDs.

[0094] In the example in Figure 10, if the Non-AP STA#1 XR (AR / VR) application consists of SCSID#M and SCSID#N, i.e., video traffic and audio traffic, the AP manages both streams with Application ID#X. In this case, a Time Difference Bound may be associated with Application ID#X. The Time Difference Bound associated with the Application ID is associated with the SCS Request frame (in the example in Figure 10, 100-1, 100-2). If included in (the corresponding), AP will schedule to satisfy the Time Difference Bound. Perform the action.

[0095] Figures 11 and 15 show an example of scheduling using Application ID. Figure 11 shows an example of scheduling using Application ID based on R-TWT operations. In the example in Figure 11, Non-AP STA#1 and Non-AP STA#2 are connected to the AP and, in order to set up R-TWT membership, TWT Request frames (101-2, 10 1-3) is sent to the AP. The AP sends TWT Response frames (101-4, 101-5) in response to the TWT Request frames received from Non-AP STA#1 and Non-AP STA#2. This sets up R-TWT membership, allowing for priority transmission and reception of low-latency traffic within the designated R-TWT SP (101-7). Furthermore, the R-TWT schedule, i.e., the interval (Interval) and SP length of the R-TWT SPs, can be broadcast in the beacon (101-1) frame. Non-AP STA#1 and Non-AP STA#2 can terminate TXOP before the start time of R-TWT SP101-7 based on the R-TWT schedule, and can also be woken if they are in Doze mode. Within R-TWT SP101-7, after data transmission by the AP, the same Application ID#X is set to satisfy the Time Difference Bound (101-6) for SCSIDs. Schedule data for #N. Non-AP STA and AP can set a field in the frame (SCS Request / Response frame, Trigger frame, TWT Request / Response frame, etc.) that includes the Application ID, or the Application ID and Time Difference Bound. can.

[0096] On the other hand, Figure 15 shows an Application based on the CTS (CTS-to-Self) frame (101-8). An example of scheduling using IDs is shown. In the example in Figure 15, Non-AP STA#1 and Non-AP STA#2 are connected to APs. The AP sends CTS frames 101-8, TXOP(101-9) can be obtained. In Figure 15, within TXOP101-9, after data transmission of SCSID#M, the AP performs a Time Difference Bound(10 To satisfy 1-6), schedule the data for SCSID#N that has the same Application ID#X set.

[0097] As mentioned above, Time Difference Bound is, in principle, an application / app. Based on the requirements of the application layer and information (QoS Characteristics Element) that defines the class of streams belonging to multiple different SCS streams that make up the application. It may also be a newly defined term. That is, Time Difference Bound101 -6 may indicate a time interval or period in which multiple different SCS streams assigned the same Application ID are sent together within a certain period, or a time interval or period in which multiple SCS streams within a certain range are sent together. For example, Time Difference Bound refers to one SCS stream among multiple different SCS streams assigned the same Application ID. The Time Difference Bound may be defined based on the time between the start and end times of transmission of one traffic stream and the time between the start and completion of transmission of the other SCS stream's traffic. This may be defined as a period, time, or condition to prevent the transmission of traffic for SCS streams other than multiple different SCS streams to which an Application ID has been assigned, or as a period, time, or condition to prevent the transmission of traffic for SCS streams to which no Application ID has been assigned.

[0098] As shown in the example in Figure 12, if Non-AP STA and AP do not support Application ID, the AP may not be able to schedule traffic belonging to an application consisting of SCSID#M and SCSID#N in a way that satisfies Time Difference Bound 101-6. This is because, after SCSID#M sends data, SCSID#O, which is traffic from another application, is scheduled, causing data from SCSID#N, which constitutes the same application as SCSID#M, to exceed Time Difference Bound 101-6. This is because it is transmitted or received.

[0099] AP receives SCS Request from multiple Non-AP STAs associated with that AP. Considering the QoS Characteristics Element or Time Difference Bound included in the frame, you can either set the Application ID in the SCS Response frame, or include the Application ID's Recommendation value or Recommendation value list in the SCS Response frame and send it. Non-AP STA may include the Application ID in the SCS Request frame and send it based on the Recommendation value or Recommendation value list included in the SCS Response frame.

[0100] As another example, consider SCS operations when an application consists of two or more Non-AP STAs. Before setting up the SCS stream with the associated AP, the two or more Non-AP STAs may negotiate a common Application ID with other Non-AP STAs belonging to that AP by exchanging Application IDs or QoS Characteristics Elements. For one or more Non-AP STAs associated with the AP, each QoS Characteristics Element is set in a beacon frame, management frame, or action frame. You may include it in the groupcast or broadcast.

[0101] AP schedules based on the Application ID and Time Difference Bound received from one or more Non-AP STAs it associates with. Send a frame to one or more Non-AP STAs. If the AP receives one or more frames (SCS Request frames) containing a Time Difference Bound from one or more associated Non-AP STAs, the AP will send a frame to one or more Non-AP STAs to satisfy the Time Difference Bound. The transmission of these UL frames can be requested by a trigger frame. The AP can send the trigger frame by setting the AID of a non-AP STA, whose SCSID corresponds to the Application ID, in the AID12 subfield of the User Info field of the trigger frame.

[0102] The Application ID set by Non-AP STA and AP consists of one or more Traffic Identifiers (TIDs), one or more Access Categories (ACs), or one or more Associates. It can be defined as something that indicates a tion Identifier (AID).

[0103] The QoS Characteristics Element has an Application ID subfield. If present, the Application ID subfield contains the Application ID value. The Application ID may be a value (unsigned integer) that manages two or more different SCSIDs as a group. The Application ID subfield can be set in the QoS Characteristics Element of the SCS Descriptor field in the SCS Descriptor List field of the SCS Request / Response frame, and the Application ID can be included in this subfield. If the Application ID Support subfield of the UHR MAC Capabilities Information field is set to 1, the QoS Characteristics Element field of the SCS Descriptor Element included in the SCS Descriptor List field must contain the Application ID subfield; otherwise, it should be set to 0.

[0104] As shown in the example in Figure 13, if the QoS Characteristics Element (middle of Figure 13) has an Application ID subfield and a Time Difference Bound associated with the Application ID is set, then a Time Difference Bound subfield may be set in the QoS Characteristics Element and the value of the Time Difference Bound may be included in that field. If the Application ID subfield does not exist, then it is not necessary to set a Time Difference Bound subfield in the QoS Characteristics Element. For example, voice traffic (example) In an application consisting of (e.g., SCSID#1) and video traffic (e.g., SCSID#2), for downlinks, the AP schedules to send the video traffic within a specified Time Difference Bound after receiving the audio traffic. In this case, Time Difference Bound is two or more different S managed by the Application ID. This value indicates the delay time between traffic belonging to the CSID.

[0105] Furthermore, as shown in the example in Figure 13, the Control Info of the QoS Characteristics element The presence or absence of the Application ID subfield and Time Difference Bound subfield is determined using the Presence Bitmap Of Additional Parameters subfield in the field (top of Figure 13). This can be notified. The Presence Bitmap Of Additional Parameters subfield of the Control Info field of the QoS Characteristics element can contain, for example, the Maximum MSDU Size field, the Application ID subfield, or the Time Difference Bound subfield. If the i-th field corresponding to the CODE exists in the QoS Characteristics element, then The bitmap contains a bitmap where the i-th entry is set to 1. For example, Non-AP STA, which supports Application ID, has a Control Info for the QoS Characteristics element. Set the bit corresponding to the Application ID in the Application ID subfield of the Presence Bitmap Of Additional Parameters subfield of the field to 1. Also, in Figure 13 above As shown in the section, the Lin in the Control Info field of the QoS Characteristics element The kID subfield contains the link identifier corresponding to the link on which the Direct link transmission is performed. This field contains (also called Link ID). If the value of `Gold` is anything other than 2 (Direct link), it is reserved. The subfields specify the direction of the data (Uplink, Downlink, Direct link, R). Specify the (eserved) in the Direction subfield encoding. This contains the TID value of the data frame. The TID subfield is User Priority It is set to the same value as Bufield, and values ​​8-15 are reserved.

[0106] The Application ID may be set as a value that groups two or more SCSIDs of Non-AP STAs that fall within a certain threshold or range, based on, for example, transmission power, location information, etc. This threshold may include, for example, a value set from the distance between each Non-AP STA and the deployed AP. Furthermore, Non-AP STAs and APs are defined in the SCS Descriptor List field of the SCS Request frame or SCS Response frame. The Descriptor element includes a QoS Characteristics Element, and Directions If the field is 2 (Direct link), the reserved LinkID sub-field The `Gold`, or LinkID subfield and Reserved subfield may be used as an Application ID subfield, and the Application ID value may be included in the said subfield. Non-AP STAs and APs may use the Optional Sub-elements subfield in the SCS Descriptor element of the SCS Descriptor List field of the SCS Request frame or SCS Response frame. The Optional Sub-elements subfield may also include an Application Descriptor element, including the Application ID. This is possible. Note that the name and target of the Application Descriptor element are not limited.

[0107] Non-AP STAs and APs that support Application ID and SCS should set Dot11SCSImplemented and Dot11ApplicationIDImplemented to true, Dot11SCSActivated and Dot11ApplicationIDActivated to true, and further set the Application ID field and SCS field of the Extended Capabilities elements to be sent to 1. If Dot11SCSActivated and Dot11ApplicationIDActivated are true, then Dot11SCSImplemented and Dot11ApplicationIDImplemented are assumed to be true.

[0108] The QoS Characteristics element is information used as a reference for AP scheduling. Yes. AP has a Direction subfield within the QoS Characteristics element. The AP sends frames indicating that it is DL at intervals that fall within the requested minimum and maximum service intervals. The AP MLD sends UL frames from Non-AP STAs, indicating that the Direction subfield is UL, at intervals that fall within the requested minimum and maximum service intervals. If the QoS Characteristics element includes Application ID, Time Difference Bound, or both, the AP MLD schedules the transmission of UL / DL frames to satisfy the requirements of those applications.

[0109] Non-AP STA is when the Request Type field in the SCS Request frame is Add or Ch If set to `ange`, it can send SCS Request frames with SCS Descriptor element(s) containing the Application ID in the QoS Characteristics element. Non-AP STAs will send SCS Request frames with SCS Descriptor element(s) containing the Application ID in the QoS Characteristics element to APs that have not received a UHR Capabilities element where the Application ID Support and SCS Traffic Description Support fields are 1. It is preferable not to send it.

[0110] Non-AP STA updates the Application ID, or Application ID and Time Difference Bound, when requesting the creation, modification, or deletion of an SCS stream. It can be (or deleted). When an AP receives an SCS Request frame from a Non-AP STA that is associated with it, the AP shall respond with a corresponding SCS Response frame. At this time, the AP can update the Application ID based on the changed SCSID. When the AP processes an SCS Request frame from a Non-AP STA, the SCS Response The SCS Status field of the frame's SCS Status duple shall be set to the value SUCCESS. If the AP rejects the SCS request for the requested SCSID, the corresponding SCS Status field of the SCS Status duple in the SCS Response frame shall be set to REQUEST_DECLINED, REQUESTED_TCLAS_NOT_SUPPORTED_BY_AP, or REQUESTED_TIME_DIFFERENCE_BOUND_NOT_SUPPORTED_BY_AP (meaning the QoS parameters requested by the application). The values ​​INSUFFICIENT_TCLAS_PROCESSING_RESOURCES or INSUFFICIENT_TIME_DIFFERENCE_BOUND_PROCESSING_RESOURCES (not limited to these names, if they represent the QoS parameters requested by the application) may be set.

[0111] As another example, the Non-AP STA and AP according to this embodiment combine R-TWT with an Application ID, or an SCS operation using an Application ID and Time Difference Bound. They can be implemented together. A Non-AP STA where Dot11RestrictedTWTOptionImplemented is true and the Restricted TWT Support subfield of the UHR Capabilities element to be sent is set to 1 is referred to as an R-TWT scheduled STA. Furthermore, an AP where Dot11RestrictedTWTOptionImplemented is true and the Restricted TWT Support subfield of the UHR Capabilities element to be sent is set to 1 is referred to as an R-TWT scheduling AP. The features include Enhanced Medium Access Protection and resource reservation. Resource Reservation Mechanisms can be used.

[0112] The R-TWT scheduling AP establishes an SCS stream defined by a QoS characteristic element including Application ID and Time Difference Bound with the R-TWT scheduled STA. At this time, the TID and Direction fields are established with the R-TWT scheduled STA. If the R-TWT TID and Direction match those of the defined R-TWT schedule, the R-TWT scheduling AP will schedule a DL QoS Data frame corresponding to the R-TWT TID at the R-TWT SP, or receive a UL QoS Data frame. As will be explained later, the R-TWT TID belongs to the SCSID managed by the Application ID. D drink.

[0113] The R-TWT scheduled STA may set the Restricted TWT Support subfield of the UHR Capabilities element it transmits to 1 and the Broadcast TWT Support subfield of the HE Capabilities element it transmits to 1. Otherwise, the Non-AP STA sets the Restricted TWT Support subfield of the UHR Capabilities element it transmits to 0. The R-TWT scheduled STA has one or more Restricted TWT Parameter Sets between it and the R-TWT scheduling AP. This is a Non-AP STA that exchanges broadcast TWT elements including fields. An R-TWT scheduled STA establishes one or more R-TWT memberships with its associated APs. R-TWT membership may be configured by referencing the Application ID included in the SCS Request / Response frame instead of the Broadcast TWT ID (TWT ID). An R-TWT scheduling AP can announce one or more R-TWT schedules.

[0114] The R-TWT scheduled STA can notify the R-TWT scheduling AP in an SCS Request frame of the QoS characteristic element of the traffic intended to be sent and received between the R-TWT SP. The R-TWT scheduling AP receives the QoS characteristic element from the R-TWT scheduled STA, and its TID and Direction fields are R-TWT membership The R-TWT TID matches the Application ID and its specified Direction. In this case, the R-TWT scheduling AP can use the parameters of those QoS Characteristics elements as guidance when setting up R-TWT membership. The R-TWT scheduling AP and R-TWT scheduled STA configure the Restricted TWT Traffic Info field to identify TIDs for carrying low-latency traffic on DL and UL. The TIDs indicated as low-latency traffic on DL and UL in the Restricted TWT Traffic Info field are those included in the set of TIDs mapped on DL and UL, respectively, to the link where R-TWT membership is configured.

[0115] The TID specified in the Restricted TWT Traffic Info field of the TWT element in a TWT response indicating Accept TWT is called the R-TWT DL TID or R-TWT UL TID, and collectively referred to as the R-TWT TID. A TTLM (TID-to-Link Mapping) update will update any R-TWT membership. The R-TWT TID of the link will no longer be mapped to a link with R-TWT membership configured. If this occurs, the corresponding R-TWT membership is considered terminated. If the R-TWT scheduling AP and R-TWT scheduled STA support Application ID, the R-TWT TID will be replaced by Alternatively, you may substitute a TID belonging to the SCSID managed by the Application ID.

[0116] If an R-TWT scheduling AP or R-TWT scheduled STA initiates or joins a frame exchange during an R-TWT SP, it will first deliver the QoS Data frame of the R-TWT TID during the R-TWT SP. This is guaranteed. In Trigger-enabled R-TWT SP, the transmission of the Trigger frame is scheduled. When scheduling, the R-TWT scheduling AP first directs the R-TWT scheduled STA to deliver the R-TWT UL TID QoS Data frame (if any) first. You can also rig it. In a trigger-enabled R-TWT SP, the triggered R-TWT scheduled STA is , MPDU is aggregated. However, R-TWT Scheduled STA is R-TWT UL TID's TID QoS Data The frame (if any) may be included first. An R-TWT scheduling AP may include the lower 12 bits of the AID of a non-AP STA that is not this R-TWT scheduled STA in the trigger frame sent by a trigger-enabled R-TWT SP.

[0117] When an R-TWT scheduling AP or R-TWT scheduled STA initiates or joins a frame exchange during an R-TWT SP, it can be ensured that the QoS Data frame belonging to the SCS stream with the configured Application ID is delivered first during the R-TWT SP. In a trigger-enabled R-TWT SP, when scheduling the transmission of a trigger frame, the R-TWT scheduling AP can ensure that the R-TWT scheduled STA delivers the QoS Data frame (if any) with the R-TWT UL TID first. To enable this, the R-TWT scheduled STA is triggered first. In Trigger-enabled R-TWT SP, A triggered R-TWT scheduled STA aggregates the MPDU. However, the R-TWT scheduled STA should first include the QoS Data frame (if any) of the R-TWT UL TID. An R-TWT scheduling AP may include the lower 12 bits of the AID of a Non-AP STA that is not an R-TWT member in the trigger frame sent by a trigger-enabled R-TWT SP, but it is desirable that this member be set to the same Application ID.

[0118] When transmitting UL dataframes, you may use either a Basic Trigger frame or a MU-RTS TXS Trigger frame. (Dot11UHRTXST for Non-AP STA) If FOptionImplemented is set to true, Direct Link Frame transmission may also use MU-RTS TXS Trigger frames. This is possible if both Non-AP STAs support TXS Mode 2 and the corresponding UHR Capabilities field is set to TXS Mode 2. This is the case when the Support subfield is set to 1. If the Non-AP STA is a TWT scheduled STA or a TWT requesting STA, and there are Negotiated TWT SPs, then the AP is Service Verify that the Period (SP) is consistent with the Negotiated TWT Wake. The STA is an R-TWT scheduled STA, as specified in the Direction subfield within the QoS Characteristics element. If there are Negotiated R-TWT SPs in the same direction (UL or DL) for a given TID, the AP uses these R-TWT SPs to provide traffic corresponding to the direction and TID specified in the QoS Characteristics element, or to TIDs belonging to SCSIDs managed by Application ID.

[0119] If no TID is specified for Negotiated R-TWT SPs, the AP can use these R-TWT SPs to provide traffic corresponding to the TID specified in the QoS Characteristics element. If the R-TWT SPs are Trigger-Enabled, the AP verifies that a Trigger frame is scheduled for the R-TWT SPs. The AP verifies if the frame's Life Time exceeds the value specified in the MSDU Lifetime field, or , QoS parameters specified in Time Difference Bound associated with Application ID If the conditions cannot be met, the DL data frame can be discarded. In the QoS Characteristics element provided by Non-AP STA, the receiving AP can access a specific channel. Use QoS operations (e.g., EDCA). Periodic Traffic For traffic, Non-AP MLD sets the Minimum Service Interval field and Maximum Service Interval field to the same value, and Service start time (service start time) If the exact period indicated in the field cannot be expressed in microseconds (integer), Non-AP MLD can first use the updated service start time to automatically send a QoS Characteristics element or Time Difference Bound with the SCS Request Type set to "Change".

[0120] The SCS operations according to this embodiment can also be applied to Mirrored SCS (MSCS). MSCS procedures can include setting up the MCS, updating parameters, terminating the MCS, classifying MSDUs addressed to Non-AP STAs, and setting up UP for those MSDUs. These are performed at the MLD level and apply to all Non-AP STAs associated with the MLD. An MLD implementing the MSCS procedure can demonstrate its capabilities by setting Dot11MSCSActivated to true for each Non-AP STA associated with that MLD and by setting the Mirrored SCS field to 1 for each Extended Capabilities element sent by each Non-AP STA associated with that MLD.

[0121] A Basic Multi-Link element (BMLE) can be included in Beacon frames, Probe Response frames, Authentication frames, FT Action frames, (Re)Association Request frames, or (Re)Association Response frames. When a Non-AP STA constituting an MLD receives a frame containing a Multi-Link element, it determines the presence or absence of a subfield in the Common Info field based on a subfield in the Presence Bitmap field. Each MLD can maintain an SCSID at the MLD level for each non-AP MLD. In other words, an SCS Request frame sent to an AP belonging to an AP MLD Therefore, the SCSID used by a non-AP STA belonging to a non-AP MLD is unique among all non-AP STAs belonging to that non-AP MLD. Figure 14 shows an example of a BMLE. AP MLDs and Non-AP MLDs that support Application ID and SCS have the presence or absence of the Application ID subfield and Time Difference Bound subfield in the Presence Bitmap of the BMLE at the top of Figure 14, and the same in the Common Info field of the BMLE at the bottom of Figure 14. It is desirable to set the Application ID and Time Difference Bound in the subfields. .

[0122] All non-AP STAs belonging to MLD send Extended Capabilities Element S The CS field must be set to the same value. The SCSID is used when a non-AP MLD requests the creation, modification, or deletion of an SCS stream. This SCSID is used by the AP MLD to identify the SCS stream in the SCS response. MLDs that support SCS and Application ID set Dot11SCSImplemented and Dot11ApplicationIDImplemented to true. MLDs that show Dot11SCSActivated and Dot11ApplicationIDImplemented as true support and transmit Extended stream classification. Set the SCS field and Application ID field of the Capabilities Element to 1. If Dot11SCSActivated and Dot11ApplicationIDImplemented are true, then Dot11SCSImplemented and Dot11ApplicationIDImplemented will also be true. Note that the above-mentioned conditions for SCSID and Extended Capabilities Element apply equally regardless of whether it is Non-MLD or MLD.

[0123] If a non-AP STA belonging to a non-AP MLD sends an SCS Request frame to an AP MLD AP that contains a QoS Characteristics Element whose Direction subfield is set to UL or DL, or does not contain a QoS Characteristics Element, the frame will be M This is interpreted as a request to create or modify an SCS stream applied at the LD level. The QoS Characteristics Element serves as a reference for AP scheduling. If the Direction subfield of the QoS Characteristics Element indicates DL, the AP MLD will schedule the transmission of DL frames to meet the requested Delay Bound and minimum data rate. If the Direction subfield indicates UL, the AP MLD facilitates the transmission of UL frames from Non-AP STA within the requested minimum and maximum service intervals, and the AP can meet the requested minimum data rate. The AP operates on the link specified in the LinkID subfield within the Control Info field of the QoS Characteristics Element. It is desirable to facilitate the transmission of direct link frames from one Non-AP STA to another within the requested minimum and maximum service intervals.

[0124] For periodic traffic, if the Non-AP MLD sets the Minimum Service Interval and Maximum Service Interval fields to the same value and those fields cannot accurately represent the period of traffic (e.g., a 1 / 60 second period cannot be represented as an integer multiple of a microsecond), the non-AP MLD may intermittently send QoS Characteristics Element with updated service start times using SCS Request frames. For example, using the same SCSID and setting the SCS Request Type to Change. If the requested SCS is accepted by the AP MLD and the SCS Descriptor Element does not contain a QoS Characteristics Element, Alternatively, the Direction subfield of the QoS Characteristics Element indicates DL. In addition, the AP MLD may process subsequent individually addressed MSDUs from the DS or WM that match the TCLAS Elements field and the optional TCLAS Processing Element field specified in the SCS Descriptor Element.

[0125] If an SCS Request frame contains an SCS Descriptor element that includes a QoS Characteristics element and is received by an AP associated with an AP MLD, the AP shall send an SCS Response frame containing an SCS Descriptor element whose SCS Status field is set to REJECTED_WITH_SUGGESTED_CHANGES. The AP shall include an SCS Descriptor element containing the proposed Application ID and QoS Characteristics parameters in the SCS Response frame. The AP MLD shall include in the SCS Response frame The SCS Request frame shall include an SCS Descriptor element containing a QoS Characteristics element within the corresponding SCS Descriptor element.

[0126] Non-AP MLDs can be used to request AP MLDs to classify Individually Addressed MSDUs based on parameters provided by the Non-AP MLD, or to request AP MLDs to describe the traffic characteristics of the Non-AP MLD. Non-AP STAs with Dot11SCSImplemented and Dot11ApplicationIDImplemented as true support sending SCS Request frames and include Application IDs. If it contains an SCS Descriptor element with a QoS Characteristics element, send The Application ID Support subfield and SCS Traffic Description Support subfield values ​​of the UHR Capabilities element shall be set to 1. APs that show activated and Dot11ApplicationIDImplemented as true and support sending SCS Response frames that have an SCS Descriptor element and a QoS Characteristics element containing an Application ID will send UHR The Application ID Support subfield and SCS Traffic Description Support subfield values ​​of the Capabilities element shall be set to 1.

[0127] A Non-AP STA is associated with a Non-AP MLD and sends an SCS Request to an AP belonging to the AP MLD. Frames that do not contain a QoS Characteristics Element whose Direction subfield is set to UL or DL ​​are interpreted as requests to create or modify an SCS stream at the MLD level. If an SCS Descriptor element contains a QoS Characteristics element and its Direction subfield indicates DL, the TCLAS Elements frame is interpreted as a request to create or modify an SCS stream at the MLD level. The field shall be contained within the SCS Descriptor element, and the TCLAS Processing Element field may be included. If the TCLAS Element field and TCLAS Processing Element field are present, the Non-AP STA describes the traffic classification that the AP applies to the corresponding stream. If the Direction subfield within the QoS Characteristics subelement contained in the SCS Descriptor element within the SCS Request frame indicates UL, the Intra-Access Category Priority Element, TCLAS Element field, and TCLAS Processing Element field shall not be included. REQUEST_DECLINED, REQUESTED_TCLAS_NOT_SUPPORTED_BY_AP, REJECTED The values ​​of _WITH_SUGGESTED_CHANGES, REQUESTED_TIME_DIFFERENCE_BOUND_NOT_SUPPORTED_BY_AP, INSUFFICIENT_TIME_DIFFERENCE_BOUND_PROCESSING_RESOURCES, or INSUFFICIENT_TCLAS_PROCESSING_RESOURCES are used by AP to determine the SCS stream for the requested SCSID. If you refuse to create or modify a frame, this will be set in the corresponding SCS status tuple in the SCS Status field within the SCS Response frame.

[0128] As a variation of this embodiment, the present invention can also be implemented in applications such as XR (AR / VR) via a server. For example, consider the case of transmitting video traffic, audio traffic, or other traffic from a Non-AP STA at site A to a Non-AP STA at site B. Both the Non-AP STA and AP at both sites support SCS and Application ID, respectively. In order to transmit traffic from the Non-AP STA at site A to the Non-AP STA at site B, the QoS parameters (SCSID, Application ID, and Time Difference Bound) used between the Non-AP STA and AP at site A are transmitted between the Non-AP STA and AP at site B. It is desirable to apply this. Here, Non-AP STA or AP may set the Time Difference Bound to something other than the Differential Services Code Point (DSCP). For example, site AP at site A encapsulates the SCS Request / Response frames exchanged between the Non-AP STA and AP at site A and sends them to AP at site B, thereby directly setting the same QoS parameters between the Non-AP STA and AP at site B as at site A.

[0129] Figure 16 shows an example of a QoS Map Element. The Non-AP STA at site A is shown in Figure 16. As shown in the example, the User Priority subfield corresponds to the Application ID subfield of the DSCP Value subfield of the DSCP Exception List field in the QoS Map Element. By replacing it, the DSCP value can be associated with the Application ID, and the range of DSCP corresponding to the User Priority set from the DSCP Low Value subfield and DSCP High Value subfield of the QoS Map Element's DSCP Range Description field can be used. It is also possible to associate it with a range of DSCPs corresponding to the Application ID (the name of Application ID# DSCP Range is not limited to this).

[0130] In embodiments of the present invention, the embodiments described below can be implemented separately from the embodiments described above. Optional subelement fields of SCS Descriptor elements included in the SCS Descriptor List field of SCS Request frames and SCS Response frames. You may set a new sub-element in the `Rudo` and define an Element corresponding to the new sub-element. The format of the SCS Request frame is shown in Figure 17(a), and the format of the SCS Response frame is shown in Figure 17(b). The SCS Request frame may include a Category field, a Robust Action field, a Dialog Token field, and an SCS Descriptor List field. The SCS Response frame may include a Category field, a Robust Action field, a Dialog Token field, and an SCS Descriptor List field. The SCS Status List field may contain n, Count, SCS Status List, and SCS Descriptor List fields. If the Status subfield of an SCS Status duple within the SCS Status List field indicates REJECTED_WITH_SUGGESTED_CHANGES, then an SCS Descriptor element exists with an SCSID field that matches the corresponding SCSID subfield. Otherwise, no SCS Descriptor element exists. The SCS Status List field may contain 1 or more The above includes the SCS Status duple. The format of the SCS Status duple is shown in Figure 17(c). As is stated, the SCSID field in Figure 17(c) is set to the value of the SCSID field received in the SCS Descriptor element within the SCS Request frame. The Status field indicates the status of the requested SCSID. This is similar to the Status Code field and is requested in the SCS Response. Used to indicate the success or failure of an operation. Format of the Status Code field. In this case, if the operation is successful, the Status Code will be set to SUCCESS (0). If the operation fails, the Status Code indicates the cause of the failure.

[0131] The SCS Descriptor List field is optionally present when an SCS Response frame is sent from one UHR STA belonging to one MLD to another UHR STA belonging to a different MLD. If the SCS Descriptor List field is present, it contains zero or more SCS Descriptor elements. Each SCS Descriptor element contains a QoS Characteristics element that describes the traffic characteristics and QoS Expectations of the traffic flow belonging to the SCS stream identified by the SCSID field value within the SCS Descriptor element.

[0132] The SCS Descriptor element defines information about the stream being classified. The format of the SCS Descriptor element is shown at the bottom of Figure 13. An Element is identified by the Element ID field, and the Length field indicates the number of octets within the Element excluding the Element ID and Length fields. The SCSID field is set to a non-zero value selected by the non-AP STA that identifies the SCS stream specified in the SCS Descriptor element. The Request Type field is set to a number that identifies the type of SCS request. That is, the type of Request Type is 0 (Add), 1 (Remove), 2 (Change), and 3-255 are reserved, according to the value of the Request Type field. That is acceptable.

[0133] This section describes the fields included in the SCS Descriptor element. The Intra-Access Category Priority Element field exists when the Request Type field is Add or Change. The TCLAS Elements field is received as part of the SCS stream. You may include zero or more TCLAS elements to specify how MSDUs are classified. If the Request Type field is Add or Change, one or more TCLAS elements exist; if the Request Type field is Remove, no TCLAS elements exist. The TCLAS Processing Element field exists if the TCLAS Elements field contains two or more TCLAS elements, and contains a TCLAS Processing element that defines how multiple TCLAS elements are processed.

[0134] The QoS Characteristics Element field of the SCS Descriptor element is shown at the bottom of Figure 18. Hereafter, unless otherwise specified, the QoS Characteristics element will be the one shown in Figure 18. It shall include the code. The QoS Characteristics Element field contains the QoS Characteristics element. The QoS Characteristics element is a code for a specific non-AP UHR STA. The text includes a set of parameters that define the characteristics of the traffic flow and QoS expectations that UHR APs and non-AP UHR STAs use to support the forwarding of QoS traffic. This element is used for SCS procedures and R-TWT configuration. It may be used in the procedure. As defined in the QoS Characteristics element, SCS It contains a QoS Characteristics element of 0 or 1 to describe the traffic characteristics and QoS Expectations of the traffic flow belonging to the reem. The Request Type field is For Add or Change, there are 0 or 1 QoS Definitions element. If the Request Type field is Remove, the QoS Characteristics element exists. do not.

[0135] The Optional Subelements field of an SCS Descriptor element contains zero or more subelements (hereinafter also referred to as Subelements). Each subelement has a 1-octet Element-specific Subelement ID field and a 1-octet Length field. It is defined to have an h field and a variable-length sub-element-specific Data field. Each sub-element is assigned a unique Subelement ID within the Element or sub-element it contains. The Length field is the Data field. Specify the number of octets. The value of the Optional Subelement ID field of a defined subelement is shown in Figure 19(a). The SCS Descriptor element is included in the SCS Request frame.

[0136] When the value of the Optional Subelements field of an SCS Descriptor element is 0, the Optional Subelements field is included with the Application Descriptor subelement. However, the value corresponding to the Application Descriptor subelement is not limited to this; other Reserved values ​​or pre-specified values ​​may be used. For UHR STA, the Application Descriptor subelement is included to indicate the Application ID associated with the SCSID of the SCS stream. For example, it is possible to associate the SCSIDs of two or more SCS streams. The Application Descriptor subelement has the same format as the Application Descriptor element. Hereafter, the Application Descriptor subelement will also be referred to as the Application Descriptor element. The name of the Application Descriptor element is not limited to anything specific.

[0137] The Application Descriptor element contains the Application ID. The format of the element is shown in Figure 19(b). The Application Descriptor element includes the Element ID field, Length field, and Element ID Extension field, and Application ID field. The Application ID field is notified by the UHR STA. Identify the Application ID associated with the SCSID being accessed. When the UHR STA receives an Application Descriptor element, it uses the Application Descriptor element to identify the Application ID and its associated SCSID.

[0138] With respect to SCS operations (also referred to as SCS procedures), EHT STAs are subject to additional SCS rules and constraints defined in the EHT SCS procedures. UHR STAs are subject to additional SCS rules and constraints defined in the UHR SCS procedures. SCS procedures are used by non-AP MLDs to request AP MLDs to classify individually addressed incoming MSDUs based on provided parameters, or to communicate traffic characteristics to AP MLDs, but are not limited to MLDs. In other words, UHR STAs establish SCS streams with UHR APs as defined in the SCS procedures and EHT SCS procedures, but the additional rules and constraints described below apply.

[0139] Regarding UHR STA, non-AP UHR STA includes an SCS Descriptor element in the SCS Request frame, the SCS Descriptor element includes one or more Optional subelements, and the Optional subelements include an Application Descriptor element, before sending the SCS Request frame. The UHR AP receives an SCS Request frame, which contains an SCS Descriptor element, and the SCS Descriptor element contains one or more Optional subelements. It includes an Application Descriptor element in Optional subelements. When the UHR AP receives an SCS Request frame, it sends an SCS Response frame. It is possible.

[0140] A non-AP UHR STA with Dot11SCSActivated set to true will set the value of the SCS Traffic Description Support subfield of the UHR Capabilities element it sends to 1 if it supports sending SCS Request frames that include a QoS Characteristics element in the SCS Descriptor element. Similarly, dot11SCSActi If a UHR AP with vated set to true supports sending SCS Response frames that include a QoS Characteristics element in the SCS Descriptor element, then it will send itself. The value of the SCS Traffic Description Support subfield of the UHR Capabilities element. Set to 1. Through the MLD synchronization service, all UHR STAs belonging to the MLD will send the SCS Traffic Description Support subfile of the UHR Capabilities element to be transmitted. Standardize the values ​​of the world.

[0141] Non-AP UHR STAs with Dot11SCSActivated set to true can send SCS Request frames with an SCS Descriptor element containing a QoS Characteristics element if the Request Type field is set to Add or Change. The QoS characteristic element is used to determine the traffic characteristics of the requested SCS stream. Describe the type. However, the value of the SCS Traffic Description Support field is set to 1. For UHR APs that have not received the UHR Capabilities element, do not send an SCS Request frame containing the QoS Characteristics element in the SCS Descriptor element.

[0142] When Dot11SCSActivated is set to true, the SCS Request frame contains an Application Descriptor element in the Optional subelements within the SCS Descriptor element. Non-AP UHR STAs that support sending UHR MAC Capabilities must set the value of the Application ID Support subfield in the UHR MAC Capabilities Information field they send to 1. Similarly, UHR APs that support sending SCS Response frames with dot11SCSActivated set to true and containing an Application Descriptor element in Optional subelements within the SCS Descriptor element must set the value of the Application ID Support subfield in the UHR MAC Capabilities field they send to 1. Do not set the value of the Application ID Support subfield in the Information field to 1. Through the MLD synchronization service, all UHR STAs belonging to the MLD will send the Application ID Support subfield of the UHR MAC Capabilities Information field. Do not standardize the value of "do".

[0143] A non-AP UHR STA with Dot11SCSActivated set to true can send an SCS Request frame with an SCS Descriptor element containing an Application Descriptor element in the Optional subelements field, if the Request Type field is set to Add or Change. The Application Descriptor element is requested. This describes the Application ID associated with the SCS stream. However, for UHR APs that have not received a UHR Capabilities element with the Application ID Support field set to 1, an SCS Request frame containing the Application Descriptor element in the SCS Descriptor element will not be sent. Note that the Optional subelements of the SCS Request frame... If a field contains both an SCS Descriptor element that includes an Application Descriptor element and an SCS Descriptor element that does not include an Application Descriptor element, the UHR AP may send an SCS Response frame to set up an SCS stream for the SCSID specified by the Application Descriptor element.

[0144] The MLD manages the SCSID for each non-AP MLD at the MLD level. In other words, within the SCS Request frame sent to the AP belonging to the AP MLD, the non-AP ST belonging to the non-AP MLD is managed. The SCSID used by A may be unique across all UHR STAs belonging to that non-AP MLD. Similarly, the MLD manages the Application ID for each non-AP MLD at the MLD level. In other words, within the SCS Request frame sent to an AP belonging to an AP MLD, the non-AP MLD belongs The Application ID used by the non-AP STA is the same for all UHR STAs belonging to that non-AP MLD. It may be unique in this context. All UHR STAs belonging to the MLD may set the SCS field of the Extended Capabilities element they send to the same value. The SCSID is used by non-AP MLDs to request the creation, modification, or deletion of SCS streams. The SCSID is also used by AP MLDs to identify SCS streams within SCS Response frames. The Application ID is used by AP MLDs to identify one or more associated SCS streams within SCS Response frames.

[0145] If an SCS Descriptor element contains a QoS Characteristics element and its Direction subfield indicates DL, then the TCLAS Elements field may be included in the SCS Descriptor element, and the TCLAS Processing Element field may also be included in the SCS Descriptor element. The TCLAS Elements field and the TCLAS Processing Element field (if present) are used to request that a non-AP STA apply to the corresponding stream from the AP. Describe the graphical classification. If the SCS Descriptor element included in the SCS Request frame contains a QoS Characteristics subelement, and the Direction subfield of the QoS Characteristics element indicates a direct link or UL, do not include the Intra-Access Category Priority Element, TCLAS Element, and TCLAS Processing Element fields. If the UHR AP rejects the SCS request for the requested SCSID, the SCS Status field of the corresponding SCS Status duple in the SCS Response frame may be set to one of the following values: REQUEST_DECLINED, REQUESTED_TCLAS_NOT_SUPPORTED_BY_AP, REJECTED_WITH_SUGGESTED_CHANGES, or INSUFFICIENT_TCLAS_PROCESSING_RESOURCES. The requested SCSID may also be an Application ID.

[0146] If an SCS Request frame containing an SCS Descriptor element and a QoS Characteristics element is rejected by the UHR AP and its Status field is set to REJECTED_WITH_SUGGESTED_CHANGES, the UHR AP will send an SCS Response frame containing an SCS Descriptor element indicating the proposed QoS Characteristics parameters for this SCS stream and a QoS Characteristics element. The UHR AP will reject the value of the Status field only if the SCS Descriptor element of the corresponding SCS Request frame contains a QoS Characteristics element. The SCS Response frame set to ED_WITH_SUGGESTED_CHANGES includes an SCS Descriptor element and a QoS Characteristic element.

[0147] An SCS Request frame containing an SCS Descriptor element and an Application Descriptor element in its Optional subelements is rejected by the UHR AP, and its Status field is... If the value of is set to REJECTED_WITH_SUGGESTED_CHANGES, the UHR AP sends an SCS Response frame containing an SCS Descriptor element indicating the proposed Application ID for these SCS streams, and an Application Descriptor element in Optional subelements. The UHR AP then includes the Application Descriptor element in Optional subelements in the SCS Descriptor element of the corresponding SCS Request frame. If present, an SCS Response frame with the Status field set to REJECTED_WITH_SUGGESTED_CHANGES may include an SCS Descriptor element and an Application Descriptor element within its Optional subelements. The value of the Status field is not limited to any specific value. For example, if an SCS Request frame containing an SCS Descriptor element and an Application Descriptor element in its Optional subelements is rejected by the UHR AP, the Status field of that SCS Response frame may be set to REJECTED_WITH_SUGGESTED_CHANGES. This could also be REJECTED_APPLICATION_ID_WITH_SUGGESTED_CHANGES or REQUEST_APPLICATION_ID_DECLINED. Furthermore, if the Optional subelements field of the SCS Request frame contains both an SCS Descriptor element with an Application Descriptor element and an SCS Descriptor element without an Application Descriptor element, the UHR AP may send an SCS Response frame rejecting the SCS stream for the SCSID specified by the Application Descriptor element.

[0148] The SCS Descriptor element included in the SCS Response frame does not need to include the Intra-Access Category Priority element, the TCLAS Elements field, or the TCLAS Processing Element field. The value of the Request Type field of the corresponding SCS Descriptor element may be pre-specified. The following fields of the QoS Characteristics element included in the element are the requested S The corresponding values ​​in the CS stream (Minimum Service Interval, Maximum Service Interval, Service Start Time, Medium Time) and the Application ID contained in the Application Descriptor element may differ. (Dot11UHRTXSTFOptionImple) Non-AP UHR STAs with mented set to true will have their UHR STA and associated The Direction field will only be 2 (Direct) if both of the connected UHR APs have set the TXS Mode 2 Support subfield of the UHR Capabilities element they are sending to 1. You can send SCS requests that include the QoS characteristic element set in the Link.

[0149] The QoS Characteristics element serves as the basis for scheduling the UHR AP. If the Direction subfield of the QoS Characteristics element indicates DL, the UHR AP MLD will determine the requested Delay Bound and Minimum Data Rate for DL ​​Data frames. The transmission of DL frames may be scheduled to satisfy the following conditions. The UHR AP MLD indicates that the Direction subfield of the QoS Characteristics element is UL. In this case, the UHR AP may process the transmission of UL frames from the UHR STA within the requested Minimum Service Interval and Maximum Service Interval range, and the UHR AP may operate to satisfy the requested Minimum Data Rate. The UHR AP operates on the link specified in the LinkID subfield within the Control Info field of the QoS Characteristics element. The transmission of Direct Link frames from one UHR STA to another may be processed to occur within the requested Minimum Service Interval and Maximum Service Interval. UL Data frames may be transmitted using Basic Trigger frames, or alternatively, MU-RTS TXS Trigger frames if both UHR STAs have Dot11UHRTXSTFOptionImplemented set to true. Direct Link frames may also be transmitted using MU-RTS TXS Trigger frames if both UHR STAs have the TXS Mode 2 Support field set to 1 in the UHR Capabilities element they transmit.

[0150] The Application Descriptor element within Optional subelements serves as the basis for scheduling the UHR AP. The UHR AP MLD is the Direction of the QoS Characteristics element. If the subfield indicates DL, the DL frame will be configured so that the Delay Bound and Minimum Data Rate of the SCS stream requested for the Application ID are satisfied for the DL Data frame. You may schedule the transmission of the request. The UHR AP MLD requests the Application ID if the Direction subfield of the QoS Characteristics element indicates UL. The UHR STA may transmit UL frames within the Minimum Service Interval and Maximum Service Interval range of the configured SCS stream, and the UHR AP may be controlled to meet the requested Minimum Data Rate. The UHR AP transmits Application ID on the link specified in the LinkID subfield within the Control Info field of the QoS Characteristics element. Within the Minimum Service Interval and Maximum Service Interval range of the SCS stream requested, a Direct Link frame may be sent from one UHR STA to another. The UL Data frame may be sent using a Basic Trigger frame, or alternatively, a MU-RTS TXS Trigger frame may be used if both UHR STAs have dot11UHRTXSTFOptionImplemented set to true. Link frame transmission uses MU-RTS TXS Trigger frames if the TXS Mode 2 Support field is set to 1 in the UHR Capabilities element transmitted by both UHR STAs. It may be used. However, the QoS of the SCS stream requested for the Application ID is not limited to this. This is not fixed, and notification may be given using a different field.

[0151] The UHR MAC Capabilities Information field may include an Application ID Support subfield, as shown in Figure 9. The value of the Application ID Support subfield indicates whether or not the sending and receiving of SCS Descriptor elements containing an Application Descriptor element is supported. UHR APs that support sending SCS Response frames containing an Application Descriptor element should set this field to 1. Non-AP UHR STAs that support sending SCS Request frames containing an Application Descriptor element should set this field to 1. Otherwise, set it to 0.

[0152] In an embodiment of the present invention, a new Classifier Type may be set in the Frame Classifier field of the TCLAS element, and a Classifier Mask and Classifier Parameters corresponding to the new Classifier Type may be defined. Below, an example using 11 as the new Classifier Type will be described, but it is not limited to this, and other Classifier Types may also be used. The TCLAS element includes a set of parameters necessary for identifying a PDU or received MSDU (from the upper layer in all UHR STAs, and from the DS in UHR APs) belonging to a specific TS (Traffic Stream). The format of the TCLAS element is shown in Figure 20(a). The TCLAS element is also used by the FMS (Flexible multicast service), DMS (Directed multicast service), and TFS (Traffic filtering service) services when traffic does not belong to the TS. The TCLAS element is provided in the ADDTS Request and ADDTS Response frames as needed, however This applies only to downlinks or bidirectional links. The TCLAS element is included when a PTP TSPEC is sent to a peer UHR STA via a UHR AP or PCP (Personal Basic Service Set (PBSS) control point). If the UP field contains a value of 7 or less, that value specifies the UP of the associated MSDU. If the UP field contains a value between 8 and 11, that value specifies the access category of the associated MPDU. A value of 255 in the UP field may be pre-specified to indicate that the MSDU's UP and the MPDU's access category are not compared as part of the traffic filter.

[0153] The TCLAS element's Frame Classifier field contains the Classifier Type and Classifier Mask. It consists of the Classifier Type and Classifier Parameters subfields (see Figure 20(b)). The Classifier Type subfield specifies the type of classification parameter within this TCLAS element. If the Classifier Type is 5 or less (except 3) or 11, the Classifier Mask subfield specifies a bitmap, where bits with a value of 1 are the Classifier of the corresponding MSDU. Identify a subset of Parameters. If the values ​​of these identified Classifier Parameters match the corresponding parameters in the MSDU, the MSDU is associated with the TSPEC Element. It is classified as a TS. The bitmap is arranged in the order of LSB (Least Significant Bit) to MSB (Most Significant Bit), and each bit points to the Classifier Parameters at the relative position defined for each Classifier Type. If the number of bits in the bitmap is greater than the number of subsequent Classifier Parameters, the remaining MSB may be reserved or pre-specified.

[0154] When the value of the Classifier Type subfield of the Frame Classifier field of a TCLAS element is 11, the Classifier Parameters subfield includes Application Filter Parameters (see Figure 20(c)). Note that the name of Application Filter Parameters is specific. It is not limited to this use. The Frame Classifier when Classifier Type is 11 The field format is shown in Figure 21. When the value of the Classifier Type subfield is 11, the Classifier Parameters subfield contains the Source Address field, Destination Address field, Application ID List field, and Type field. The Application ID List field is variable in length and contains zero or more Application ID fields, each Application ID field having a length of one octet. It has. Note that Application Filter Parameters are not limited to the above configuration, and may include cases where the Application ID List field is included in different Classifier types, or where new Classifier parameters are defined that include the Application ID List field in any of the Classifier types. For example, the Application ID List field includes IEEE Std 802.1Q for the VLAN Tag TCI (VLAN tag) and subfields that can be included within the VLAN tag. The target may be any tag, and is not limited to a specific tag or any subfield contained within a tag; it may identify other information. The target field is not limited to a specific layer; it may be a field in the physical layer, a field in the MAC layer, a field in the IP layer, or a field used in layers higher than the IP layer.

[0155] In Application Filter Parameters, the corresponding bit positions of the Classifier Mask are bit 0 for the Source Address field and bit 1 for the Destination Address field. Accordingly, the number of Application ID fields included in the Application ID List field is N. Then, if N>=1, the bit position of the Classifier Mask is dynamically adjusted from α to (α+N-1). Here, α represents the starting bit position of the Application ID List field, and if N>=1, The result is 2. Therefore, if N>=1, the bit positions of the Classifier Mask range from 2 to (2+N-1). If N=0, the Application ID List field does not exist, so α is not defined, and the Source Address field is bit 0, and the Destination Address field is bit 1. The Type field is placed in bit 2. The Type field is located at (α+N) in the Classifier Mask, regardless of the value of N. When it exceeds one octet, i.e., N>=6 In this case, the number of bits in the Classifier Mask will be 9 bits or more, so it will be extended to the next octet. This causes the bit position of the Type field to shift from (α+N) to (α+N+1). This is due to a change in bit arrangement that is applied when crossing an octet boundary.

[0156] For example, when N=0 or 1, the bitmap of the Classifier Mask fits within one octet, and the bit positions of each field are mapped as follows: When N=0, the bitmap of the Classifier Mask has bit 0 for the Source Address field and bit 0 for the Destination Address field. The value is placed in bit 1, and the Type field is placed in bit 2. If N=1, Source Address The field is placed in bit 0, the Destination Address field in bit 1, the Application ID (first one) in bit 2, and the Type field in bit 3. Up to N=5, the Classifier Mask has a maximum of 8 bits and fits within one octet.

[0157] When N=6, the number of bits in the Classifier Mask becomes 9 bits, which exceeds one octet, so it is expanded to the next octet. At this time, the bitmap of the Classifier Mask becomes 2 octaves. It is divided into octets, with the first octet containing the Source Address field and the Destination Address field. The fields, Application ID (1st) to Application ID (6th), are placed, The bit in the `type` field is placed at the first bit position of the second octet (bit 8). As a result, the bit position of the `Type` field is shifted from (α+6) to (α+7). This is due to the change in bit arrangement that is applied when crossing octet boundaries.

[0158] As an embodiment of the present invention, the SCS of the SCS Request frame or SCS Response frame You can also set a new SCS Descriptor element in the Descriptor List field. In UHR SCS, UHR STA can include an Application ID Descriptor element in the SCS Descriptor List field of an SCS Request frame or SCS Response frame. Yes. Note that the name of the Application ID Descriptor element is not limited to anything in particular. No. The Application ID Descriptor element, like the SCS Descriptor element, defines information about streams classified using the procedures defined in the UHR SCS. However, there are additional rules and restrictions for the SCS Descriptor element, as follows. An example of the format of the Application ID Descriptor element is shown in Figure 22. The Application ID field of the Application ID Descriptor element is set to a non-zero value selected by the non-AP STA that identifies the traffic specified in this SCS Descriptor element. Request The Type field is set to an identifying value for the Application ID request type. The QoS Characteristics Element field may include a QoS Characteristics element to describe the traffic characteristics and QoS expectations of the traffic flow belonging to this Application ID, as defined by the QoS Characteristics element. Request Type If the field is Add or Change, a QoS Shapes element exists. If the Request Type field is Remove, include the QoS Characteristics element. It is not necessary. However, UHR STA must not include an Application ID Descriptor subelement in the Optional subelements within the Application ID Descriptor element. In the IDs table, the Element ID value for the Application ID Descriptor element is set to 255, but the Element ID Extension value is not limited to anything. The same applies to the presence or absence of Extensible and Fragmentable. [2. Common to all embodiments]

[0159] The wireless communication device according to the present invention operates in a frequency band (frequency spectrum) known as the unlicensed band, which does not require permission for use from a country or region. While communication can be conducted using this method, the usable frequency bands are not limited to this. The wireless communication device according to the present invention can also be effective in frequency bands known as white bands (for example, frequency bands allocated for television broadcasting but not used in some regions) that are not actually used for purposes such as preventing interference between frequencies, even though permission for use for specific services has been granted by a country or region, or in shared spectrum (shared frequency bands) that are expected to be shared by multiple operators. The program that operates in the wireless communication device according to the present invention is a program that controls the CPU and other components (a program that makes the computer function) in order to realize the functions of the above-described embodiments related to the present invention. The information handled by these devices is temporarily stored in RAM during processing, and then stored in various ROMs or HDDs, and read, modified, and written by the CPU as needed. The recording medium for storing the program may be any of the following: semiconductor media (e.g., ROM, non-volatile memory card, solid-state drive, etc.), optical recording medium (e.g., DVD, MO, MD, CD, BD, etc.), magnetic recording medium (e.g., magnetic tape, flexible disk, etc.). Furthermore, in addition to realizing the functions of the above-described embodiments by executing the loaded program, the functions of the present invention may also be realized by processing in cooperation with the operating system or other application programs based on the instructions of the program. Furthermore, when distributing the program to the market, it can be stored on a portable recording medium and distributed, or transferred to a server computer connected via a network such as the Internet. In this case, the storage device of the server computer is also included in the present invention. In addition, some or all of the wireless communication device in the above-described embodiment may be realized as an LSI, which is typically an integrated circuit. Each functional block of the wireless communication device may be individually chipped, or some or all of them may be integrated into a chip. When these are implemented, an integrated circuit control unit is added to control them. It goes without saying that the present invention also includes cases where programs and configuration information are downloaded from a server computer in order to implement at least some of the functions of the above-described embodiments. Furthermore, the method of implementing integrated circuits is not limited to LSIs; it may also be implemented using dedicated circuits or general-purpose processors. Additionally, if advancements in semiconductor technology lead to the emergence of integrated circuit technologies that can replace LSIs, it is possible to use integrated circuits based on those technologies. It should be noted that the present invention is not limited to the embodiments described above. The wireless communication device of the present invention is not limited to application to mobile station devices, but can also be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances. While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and designs that do not depart from the spirit of this invention are also included in the claims. [Industrial applicability]

[0160] The present invention is suitable for use in wireless communication devices and wireless communication methods. [Explanation of Symbols]

[0161] 1-1, 1-2 Access Point Devices 2-1, 2-2, 2-3, 2-4, 3-1, 3-2, 3-3, 3-4 Station equipment 2-5, 3-5 Wireless communication system 10000-1 Wireless communication device 10001-1 Upper layer section 10001a-1 MAC layer frame generation unit 10001b-1 Upper Layer Control Unit 10002-1 Autonomous Distributed Control Unit 10002a-1 CCA Department 10002b-1 Back-off section 10002c-1 Transmission determination unit 10003-1 Transmission Unit 10003a-1 Physical Layer Frame Generation Unit 10003b-1 Wireless Transmission Unit 10004-1 Reception Unit 10004a-1 Wireless Reception Unit 10004b-1 Signal Demodulation Unit 10005-1 Antenna Unit 100-1~100-3 SCS Request Frame 100―4 SCS Response Frame 101-1 Beacon 101-2~101-3 TWT Request Frame 101-4~101-5 TWT Response Frame 101-6 Time Difference Bound 101-7 TWT SP(R-TWT SP) 101-8 CTS(CTS-to-Self) Frame 101-0 TXOP 20000-1 MLD Access Point Device 20000-2, 20000-3, 20000-4 Sub-Access Point Devices 30000-1 MLD Station Device 30000-2, 30000-3, 30000-4 Sub-Station Devices

Claims

1. Station device, It comprises a control unit and a transmission unit. The control unit includes an SCS Descriptor element in the SCS Request frame. The transmitting unit transmits the SCS Request frame, The aforementioned SCS Descriptor element includes one or more optional subelements. The aforementioned Optional subelements include an Application Descriptor element. A station device characterized by the following features.

2. An access point device, It comprises a transmitting unit and a receiving unit, The receiving unit receives an SCS Request frame, The aforementioned SCS Request frame includes an SCS Descriptor element, The aforementioned SCS Descriptor element includes one or more optional subelements. The aforementioned Optional subelements include an Application Descriptor element, When the transmitting unit receives the SCS Request frame, The transmitting unit transmits an SCS Response frame. An access point device characterized by the following features.

Images