Method and apparatus for managing quality of service in wi-fi communication

Abstract

The present disclosure relates to a method and an apparatus for configuring a multi-quality of service (QoS) profile through stream classification service (SCS) negotiation in a wireless local area network (WLAN) communication system. The method performed by a station in a wireless local area network (WLAN) communication system, according to one embodiment of the present disclosure, comprises the steps of: transmitting, to an access point, a stream classification service (SCS) request frame for configuring an SCS stream; and receiving, from the access point, an SCS response frame for configuring the SCS stream, wherein the SCS request frame includes information about a plurality of quality of service (QoS) profiles that can be dynamically applied to the SCS stream.

Description

Method and device for managing quality of service in Wi-Fi communication

[0001] The present disclosure relates to a method for managing quality of service in Wi-Fi communication between electronic devices.

[0002] Recently, due to the development of wireless technology, wired networks used by many people are being replaced by wireless networks. In other words, as wireless technology can solve the mobility limitations of wired networks, many technologies utilizing wireless networks are being actively researched.

[0003] Wireless Local Area Networks (WLANs), also known by the alias Wi-Fi, allow users to access the internet via mobile devices or laptops within a certain distance from an Access Point (AP). The Wi-Fi Alliance defines Wi-Fi as a wireless local area network (WLAN) product based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. Wi-Fi communication primarily uses the 2.4 GHz and 5 GHz wireless bands. In particular, with the popularization of mobile devices, wireless LANs, which possess potential as open wireless networks, are expanding rapidly, and Wi-Fi is being used to provide high-speed data services throughout cities, including in schools, airports, hotels, and offices.

[0004] The Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT with big data processing technologies through connections with cloud servers, is also emerging. Implementing IoT requires technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology. Recently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are being researched for connecting objects.

[0005] In an IoT environment, intelligent IT (Internet Technology) services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT (Information Technology) with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0006] Meanwhile, in Wi-Fi communication, Quality of Service (QoS) management is essential for ensuring the quality of service for various traffic types, such as voice, video, and data, by efficiently allocating network resources. Wi-Fi networks provide a mechanism to manage traffic according to priority to satisfy the conditions required by each application, such as latency, jitter, and packet loss. The IEEE 802.11 standard has introduced various QoS management functions for this purpose and is designed to guarantee high transmission quality, particularly for real-time services such as high-resolution video streaming, VoIP, and online gaming. These QoS management functions can contribute to maximizing the user experience by maintaining stable data transmission even in situations of network congestion.

[0007] The present disclosure proposes a method and apparatus for performing operations to manage service quality during Wi-Fi communication.

[0008] The present disclosure proposes a method and apparatus for setting multiple quality of service (QoS) profiles through stream classification service (SCS) negotiation during Wi-Fi communication.

[0009] The technical problems to be solved by the present disclosure are not limited to those mentioned above, and other unmentioned technical problems may be considered by those skilled in the art from the various embodiments of the present disclosure described below.

[0010] A method of a station performing Wi-Fi communication according to one embodiment of the present disclosure comprises: transmitting an SCS request frame to an access point to set up a stream classification service (SCS) stream; and receiving an SCS response frame from the access point to set up the SCS stream, wherein the SCS request frame includes information on a plurality of quality of service (QoS) profiles that can be dynamically applied to the SCS stream.

[0011] A method of an access point performing Wi-Fi communication according to one embodiment of the present disclosure comprises: receiving an SCS request frame for establishing an SCS stream from a station; and transmitting an SCS response frame for establishing the SCS stream to the station; wherein the SCS request frame includes information on a plurality of QoS profiles that can be dynamically applied to the SCS stream.

[0012] According to one embodiment of the present disclosure, a station performing Wi-Fi communication comprises: a transceiver; and at least one processor; wherein the at least one processor is configured to transmit an SCS request frame for establishing a stream classification service (SCS) stream to an access point and to receive an SCS response frame for establishing the SCS stream from the access point, and wherein the SCS request frame includes information on a plurality of quality of service (QoS) profiles that can be dynamically applied to the SCS stream.

[0013] According to one embodiment of the present disclosure, an access point performing Wi-Fi communication comprises: a transceiver; and at least one processor; wherein the at least one processor is configured to receive an SCS request frame for establishing an SCS stream from a station and to transmit an SCS response frame for establishing the SCS stream to the station, and wherein the SCS request frame includes information on a plurality of QoS profiles that can be dynamically applied to the SCS stream.

[0014] The various embodiments of the present disclosure described above are merely some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by those skilled in the art based on the detailed description to be described below.

[0015] According to one embodiment of the present disclosure, as the electronic device generates multiple quality of service (QoS) profiles for a single SCS stream through stream classification service (SCS) negotiation with an access point, it is possible to dynamically change and use QoS profiles for a single SCS stream, thereby enabling efficient use of wireless resources and improving the service user experience.

[0016] The effects obtainable from the various embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by those skilled in the art based on the following detailed description.

[0017] FIG. 1a is a diagram illustrating the form of a short-range communication connection of an electronic device.

[0018] FIG. 1b is a diagram illustrating the operation of an access point and a station for establishing a Wi-Fi connection.

[0019] FIGS. 2A, FIGS. 2B, and FIGS. 2C are drawings for explaining the SCS request frame action field format, SCS response frame action field format, and SCS descriptor element format in a Wi-Fi communication system.

[0020] FIGS. 3a and 3b are drawings illustrating an example of an SCS request frame that transmits information about a plurality of quality of service (QoS) profiles using a plurality of SCS descriptor elements with different SCSIDs, according to an embodiment of the present disclosure.

[0021] FIGS. 4a and 4b are drawings illustrating an example of an SCS request frame that transmits information about a plurality of QoS profiles using a plurality of SCS descriptor elements having the same SCSID and different profile IDs, according to an embodiment of the present disclosure.

[0022] FIGS. 5a, 5b, and 5c are drawings illustrating an example of an SCS request frame that transmits information about a plurality of QoS profiles using a plurality of QoS characteristic elements having the same SCSID and different profile IDs, according to an embodiment of the present disclosure.

[0023] FIGS. 6a and 6b are drawings illustrating an example of an SCS response frame indicating acceptance of a plurality of QoS profiles included in a plurality of SCS descriptor elements with different SCSIDs, according to an embodiment of the present disclosure.

[0024] FIG. 7 is a diagram illustrating an example of an SCS response frame indicating whether to fully accept a plurality of QoS profiles that have the same SCSID and are indicated by different profile IDs, according to one embodiment of the present disclosure.

[0025] FIGS. 8a and 8b are drawings illustrating an example of an SCS response frame indicating partial acceptance of a plurality of QoS profiles with the same SCSID and different profile IDs, according to an embodiment of the present disclosure.

[0026] FIGS. 9a and 9b are drawings illustrating an example of an SCS descriptor element that displays priority information of a plurality of QoS profiles separated into a plurality of different SCS descriptor elements, according to an embodiment of the present disclosure.

[0027] FIG. 10 is a drawing illustrating an example of an SCS descriptor element that displays time information of a plurality of QoS profiles separated into a plurality of different SCS descriptor elements, according to one embodiment of the present disclosure.

[0028] FIG. 11 is a drawing illustrating an example of a QoS characteristics element that displays priority information of a plurality of QoS profiles distinguished by a plurality of different QoS characteristics elements, according to one embodiment of the present disclosure.

[0029] FIG. 12 is a diagram illustrating an example of a QoS characteristics element that displays time information of a plurality of QoS profiles, which are distinguished into a plurality of different QoS characteristics elements, according to one embodiment of the present disclosure.

[0030] FIGS. 13a and FIG. 13b are drawings illustrating an example of a QoS characteristics element that displays priority information and time information of a plurality of QoS profiles distinguished by a plurality of different QoS characteristics elements, according to an embodiment of the present disclosure.

[0031] FIG. 14 is a flowchart illustrating the operation of a station according to one embodiment of the present disclosure.

[0032] FIG. 15 is a flowchart illustrating the operation of an access point according to one embodiment of the present disclosure.

[0033] FIG. 16 is a drawing showing an example of a configuration of a station according to one embodiment of the present disclosure.

[0034] FIG. 17 is a drawing showing an example of a configuration of an access point according to one embodiment of the present disclosure.

[0035] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0036] In describing the embodiments, technical details that are well known in the technical field to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0037] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference number.

[0038] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. The embodiments of the present disclosure are provided merely to make the present disclosure complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, like reference numerals refer to like components.

[0039] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing means of instruction to perform the function described in the flow diagram block(s).

[0040] Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that execute a computer or other programmable data processing equipment by performing a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer may also provide steps for executing the functions described in the flowchart block(s).

[0041] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For instance, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order depending on the corresponding function.

[0042] In this embodiment, the term "part" used refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Accordingly, according to some embodiments, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Furthermore, according to some embodiments, the 'parts' may include one or more processors.

[0043] In the present disclosure, each of the phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B, or C” may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish a corresponding component from another corresponding component and do not limit the components in any other aspect (e.g., importance or order).

[0044] The terms 'station', 'terminal', or 'device' as used herein may be referred to as a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit, subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile, or other terms. Various embodiments of a terminal may include a cellular telephone, a smartphone with wireless communication capabilities, a personal digital assistant (PDA) with wireless communication capabilities, a wireless modem, a portable computer with wireless communication capabilities, a photographic device such as a digital camera with wireless communication capabilities, a gaming device with wireless communication capabilities, a music storage and playback appliance with wireless communication capabilities, an internet appliance capable of wireless internet access and browsing, as well as portable units or terminals integrating combinations of such capabilities. Additionally, the terminal may include, but is not limited to, M2M (Machine to Machine) terminals and MTC (Machine Type Communication) terminals / devices. In this specification, the terminal may be referred to as an electronic device or simply a device.

[0045] Exemplary embodiments are described below in relation to Wireless Local Area Network (WLAN) systems solely for the sake of simplicity. It should be understood that the exemplary embodiments are equally applicable to systems using signals of one or more wired standards or protocols (e.g., Ethernet and / or HomePlug / PLC standards), as well as other wireless networks (e.g., cellular networks, pico networks, femto networks, satellite networks). As used herein, the terms “WLAN” and “Wi-Fi®” may include communications controlled by the IEEE 802.11 family of standards, BLUETOOTH®, HiperLAN (a set of wireless standards comparable to IEEE 802.11 standards, mainly used in Europe), and other technologies having a relatively short wireless range. Accordingly, the terms “WLAN” and “Wi-Fi” may be used interchangeably herein. Additionally, although the following describes an infrastructure WLAN system comprising one or more access points (APs) and multiple wireless stations (STAs), exemplary embodiments are equally applicable to other WLAN systems, such as multiple WLANs, peer-to-peer (or independent basic service set) systems, Wi-Fi Direct systems and / or hotspots.

[0046] Additionally, while this specification describes the exchange of data frames between wireless devices, exemplary embodiments may be applied to the exchange of any data unit, packet, and / or frame between wireless devices. Accordingly, the term “frame” may include any frame, packet, or data unit such as, for example, protocol data units (PDUs), MAC (media access control) protocol data units (MPDUs), and PLCP (physical layer convergence procedure) protocol data units (PPDUs). The term “A-MPDU” may mean aggregated MPDUs.

[0047] In the following description, many specific details, such as examples of specific components, circuits, and processes, are presented to provide a thorough understanding of the present disclosure. As used herein, the term “connected” means being directly connected or being connected through one or more intervening components or circuits. The term “connected access point” means an access point to which a given station is currently associated and / or connected (e.g., there exists a communication channel or link established between the access point and the given station). Additionally, in the following description and for illustrative purposes, specific nomenclature is presented to provide a thorough understanding of exemplary embodiments. However, it will be apparent to those skilled in the art that these specific details may not be necessary to carry out the exemplary embodiments. In other cases, to avoid obscuring the present disclosure, well-known circuits and devices are illustrated in block diagram form.

[0048] Specific terms used in the following description are provided to aid in understanding the present disclosure, and the use of such specific terms may be modified in other forms without departing from the technical spirit of the present disclosure.

[0049] The operating principles of the present disclosure will be described in detail below with reference to the attached drawings. In describing the present disclosure below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Furthermore, the terms described below are defined in consideration of their functions in the present disclosure, and these may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0050] FIG. 1a is a drawing for illustrating a short-range communication connection type of an electronic device that can be applied to the present disclosure.

[0051] According to various embodiments, with reference to FIG. 1a, an electronic device (100) may be connected to an access point (AP) (140) based on a plurality of communication methods based on Wi-Fi. According to various embodiments, the electronic device (100) may include a processor (120) and a communication module (130).

[0052] According to various embodiments, the communication module (130) can receive a communication signal from the outside or transmit a communication signal to the outside based on a Wi-Fi communication method (e.g., IEEE 802.11be). For example, the communication module (130) can operate based on at least one of the Wi-Fi communication methods IEEE 802.11ac, 802.11ax, 802.11be, or 802.11bn, and in particular, IEEE 802.11be or 802.11bn supports a wider bandwidth, higher data throughput, and shorter latency compared to IEEE 802.11ax, thereby improving performance.

[0053] According to various embodiments, the communication module (130) may include a transceiver (131) for transmitting and receiving data with an external device and a communication processor (133) (e.g., a communication processor (not shown), or a short-range wireless communication module (e.g., a Wi-Fi chipset)). According to various embodiments, the communication module (130) may further include memory.

[0054] According to various embodiments, the transceiver (131) can convert a baseband transmission signal into a wireless signal or convert a received wireless signal into a baseband reception signal.

[0055] According to various embodiments, the communication module (130) may further include, in addition to the transceiver (131) and the communication processor (133), components for orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), e.g., a modulator, a digital-analog converter, a frequency converter, an A / D converter, an amplifier, and / or a demodulator.

[0056] Although not illustrated, according to various embodiments, the electronic device (100) may be electrically connected to a communication module of an access point (140) and may include at least one antenna module that supports a communication protocol and / or frequency band supported by the communication module of the access point (140).

[0057] According to various embodiments, the communication processor (133) can control the transceiver (131) to form a communication connection with the access point (140). For example, the communication connection may include a Wi-Fi network. For example, the communication processor (133) can control the transceiver (131) to form a wireless connection with the access point (140) using a wireless local area network (WLAN) standard in the 2.4 GHz, 5 GHz, or 6 GHz band, such as IEEE 802.11ac, 802.11ax, 802.11be, or 802.11bn. Alternatively, the communication processor (133) can control the transceiver (131) to form a wireless connection with the access point (140) using a WLAN standard in the 60 GHz band, such as IEEE 802.11ad or 802.11ay.

[0058] According to various embodiments, a method of communicating between an electronic device (100) and an access point (140) using a wireless local area network (WLAN) standard may be referred to as a communication method based on STA mode.

[0059] According to various embodiments, the processor (120) may include an application processor. The processor (120) may perform a specified operation of the electronic device (100) or control other hardware (e.g., a communication module (130)) to perform a specified operation.

[0060] According to various embodiments, the access point (140) may support the operation of transmitting data to an external network and / or the operation of the multiple electronic devices (e.g., electronic device (100)) receiving data from an external network based on the connection between the multiple electronic devices (e.g., electronic device (100)) and an external network (e.g., Internet, external LAN, or cellular network).

[0061] According to various embodiments, the access point (140) may be a wireless router. The access point (140) may be a dedicated wireless router or a general-purpose device that supports a mobile hotspot function, and there are no limitations on its implementation. For example, the access point (140) may include the same components (e.g., a processor and / or a communication module) as the electronic device (100).

[0062] According to various embodiments, the access point (140) may transmit and receive data with an external device, such as a server (e.g., server (108) of FIG. 1) or an electronic device (100). For example, the access point (140) may transmit at least some of the data received from the server to the electronic device (100). According to various embodiments, the access point (140) and the electronic device (100) may transmit and receive UL (uplink) / DL (downlink) data during an operation period. For example, the access point (140) may transmit traffic to the electronic device (100) only during an operation period set based on schedule information received from the electronic device (100).

[0063] FIG. 1b is a diagram illustrating the operation of an access point and a station for establishing a Wi-Fi connection according to one embodiment of the present disclosure.

[0064] As illustrated in FIG. 1a, the access point (140) can communicate with the station (150) based on Wi-Fi. The station (150) can be implemented as the electronic device (100) of FIG. 1a. The station (150) may be a terminal (or a terminal with a Wi-Fi interface) that supports Wi-Fi communication according to the IEEE 802.11 standard.

[0065] The station (150) may transmit (or broadcast) a probe request message to the access point (140) (S161). According to one embodiment, the probe request message may be a message for the station (150) to search for nearby access points (140). According to one embodiment, the probe request message may include information regarding at least one communication capability supported by the station (150). According to one embodiment, the station (150) may receive a beacon message from the access point (140) and transmit a probe request message to the access point (140) based on the information contained in the beacon message. The access point (140) may transmit a probe response message in response to the probe request message (S162).

[0066] Upon receiving the probe response message, the station (150) may send an authentication request message to the access point (140) (S163). The access point (140) may send an authentication response message to the station (150) in response to the authentication request message (S164), and the authentication procedure between the access point (140) and the station (150) may be completed. According to one embodiment, the authentication procedure of S163 and S164 may be a process of selecting and authenticating the channel with the strongest reception strength among the messages received during the channel discovery process. According to one embodiment, through the authentication procedure of S163 and S164, the station (150) and the access point (140) may negotiate the encryption method of the authentication procedure.

[0067] When the authentication process is completed, the station (150) may send an association request message to the access point (140) to perform an association setup for the access point (140) (S165). According to one embodiment, the association request message may include information regarding at least one capability to be used for data communication between the station (150) and the access point (140) (e.g., according to the IEEE 802.11 standard). The access point (140) may generate an association ID (AID) for the station (150) and send an association response message to the station (150) (S166).

[0068] stream classification service (SCS)

[0069] SCS refers to a service that can be provided between an Access Point (AP) and a non-AP STA that supports SCS, which distinguishes multiple traffic streams and assigns data transmission priorities tailored to the characteristics of each stream. By classifying traffic flows and allocating them according to priority, SCS can maximize transmission efficiency based on user requirements.

[0070] SCS can classify traffic into four main classes (voice, video, best effort, and background) to guarantee the QoS required by specific traffic. For example, voice and video streams are assigned high priority to minimize latency and jitter, and by prioritizing the transmission of critical packets, stable service can be enabled even during network congestion. On the other hand, general data traffic and background traffic are assigned relatively low priority to enable efficient use of network resources.

[0071] Through SCS, the AP can classify individually addressed MSDUs based on parameters provided by non-AP STAs. This allows the AP to select user priority (UP), drop eligibility, and an enhanced distributed channel access (EDCA) transmission queue for the classified MSDUs.

[0072] Additionally, the AP can use the SCSID to identify the SCS stream in the SCS response frame. Upon receiving an SCS request frame from a non-AP STA, the AP transmits an SCS response frame containing a status value for the SCS request, and can set the value SUCCESS in the SCS status field if the SCS request is accepted. Conversely, if the request is rejected, it can set a value such as REQUEST_DECLINED in the SCS status field.

[0073] If the AP rejects the request to change the SCSID, the previously approved classification settings may continue to operate. If the AP approves the requested SCS, the AP can then process MSDUs from the distribution system (DS) or wireless medium (WM) that match the TCLAS element and optional TCLAS Processing element classifier.

[0074] FIGS. 2A, FIGS. 2B, and FIGS. 2C are drawings for explaining the SCS request frame action field format, SCS response frame action field format, and SCS descriptor element format in a Wi-Fi communication system.

[0075] Figure 2a illustrates the action field format of an SCS request frame transmitted by an STA to an AP in a Wi-Fi communication system.

[0076] An SCS request frame may refer to a frame used by an STA to request the creation, modification, or removal of stream classifications from an AP using the SCS procedure.

[0077] Referring to FIG. 2a, the SCS request frame action field format may include at least one of a Category field (200), a Robust Action field (205), a Dialog Token field, and an SCS descriptor list field (210).

[0078] The Category field (200) is a field indicating the category of the Action frame and can be set to one of the non-reserved values ​​shown in the code column of the table for Category values ​​presented in the IEEE 802.11 standard. An Action frame of a specific category may be referred to as the “Category Name” Action Frame. For example, if the Category field (200) contains a value (e.g., 19) indicating a Robust AV Streaming frame, it may be called the Robust AV Streaming Action Frame. An Action frame of a specific category is further identified by a subfield of the Action Details field and may be referred to as the “Subfield Name” Frame. For example, in the case of an SCS request frame such as in FIG. 2a, the Category field (200) may indicate Robust AV Streaming and the Robust Action subfield (Robust Action field (205)) may be set to a value indicating an SCS Request.

[0079] The Robust Action field (205) corresponds to an action details field that further identifies an action frame of the Robust AV Streaming category, and several action frame formats are defined to support Robust AV streaming. The value of the Robust Action field (205) associated with each frame format within the Robust AV Streaming category can be predefined, for example, as 0 (SCS Request), 1 (SCS Response), etc. In the case of the SCS request frame shown in FIG. 2a, the value of the Robust Action field (210) can be set to, for example, 0.

[0080] The SCS descriptor list field (210) may contain one or more SCS descriptor elements, and the SCS descriptor element may contain information about the stream classified using the SCS procedure. A detailed description of the SCS descriptor element format will be provided later in FIG. 2c.

[0081] Figure 2b illustrates the action field format of an SCS response frame transmitted from an AP to a STA in a Wi-Fi communication system.

[0082] The above SCS response frame may refer to a frame that the AP transmits to the STA as a response to the SCS request frame described in Figure 2a using the SCS procedure.

[0083] Referring to FIG. 2b, the SCS response frame action field format may include at least one of a Category field (220), a Robust Action field (225), a Dialog Token field, a Count field, an SCS Status List field (230), and an SCS descriptor list field (235).

[0084] The Category field (220) and Robust Action field (225) may be subject to the description of the Category field (200) and Robust Action field (205) described in FIG. 2a, and in the case of an SCS response frame such as FIG. 2b, the Category field (220) may indicate the Robust AV Streaming category and the Robust Action subfield (Robust Action field (225)) may be set to a value (e.g., 1) representing the SCS Response.

[0085] The SCS Status List field (230) may include one or more SCS status duples, and the SCS status duple may include an SCSID field and a Status field. The SCSID field may be set to the SCSID field value included in the SCS descriptor element received in the SCS Request frame. The Status field may indicate the status of the requested SCSID.

[0086] The SCS descriptor list field (235) may be optionally included when the SCS response frame is transmitted from an STA associated with one MLD (multi-link device) to an STA associated with another MLD.

[0087] FIG. 2c is a diagram illustrating an SCS descriptor element format that may be included in the SCS request frame or the SCS response frame in a Wi-Fi communication system.

[0088] An SCS descriptor element can contain information about a stream classified using an SCS procedure.

[0089] Referring to FIG. 2c, the SCS descriptor element may include at least one of the following fields: Element ID field, Length field, SCSID field (240), Request Type field (245), Intra-Access Category Priority Element field (247), TCLAS (traffic classification) elements field (250), TCLAS processing element field (255), QoS characteristics element field (260), and Optional Subelements field (265).

[0090] The SCSID field (240) can be set to a non-zero value that identifies an SCS stream specified by the AP (or AP STA). This value can identify an SCS stream specified in this SCS Descriptor element.

[0091] The Request Type field (245) can be set to a number that identifies the type of SCS request when the SCS request frame contains an SCS descriptor element. A non-AP STA that supports SCS can be used to request the creation, modification, or deletion of a setting for an SCS stream identified by the SCSID by sending an SCS request frame that includes an "Add," "Remove," or "Change" setting in the Request Type field (245).

[0092] The Intra-Access Category Priority Element field (247) can provide a non-AP STA with information about the relative priority of a stream within its access category to the AP. The Intra-Access Category Priority Element field (247) may include a user priority subfield, an Alternate Queue subfield, and a Drop Eligibility subfield. The user priority subfield may indicate the user priority of the MSDU or A-MSDU of the corresponding stream associated with the Intra-Access Category Priority Element.

[0093] The TCLAS elements field (250) may include one or more TCLAS elements necessary to identify PDUs or incoming MSDUs included in the traffic stream. The TCLAS element may include at least one of a user priority field and a frame classifier field. The user priority field may include a value representing priority information based on the access category values ​​of the MSDUs (e.g., AC-VO (access category-voice), AC-VI (access category-video), etc.). The frame classifier field may include at least one of a Classifier Type field, a Classifier Mask, and a Classifier Parameters field for classification. One or more TCLAS elements may be included when the Request Type field (245) of the SCS request frame is "Add" or "Change", and TCLAS elements may not be included when the Request Type field (245) is "Remove".

[0094] The TCLAS processing element field (255) exists when there is one or more TCLAS elements in the TCLAS elements field (250) and may include a TCLAS Processing element that defines how multiple TCLAS elements will be processed. If a TCLAS Processing element exists in the SCS descriptor element, the Processing subfield must have a value of 0 or 1, and the AP may reject an SCS request frame that does not meet this condition.

[0095] The QoS characteristics element field (260) may include zero or one QoS characteristics element to describe the characteristics of the traffic flow belonging to the SCS stream and QoS expectations. If the Request Type field (245) of the SCS request frame is "Add" or "Change", there may be zero or one QoS characteristics element, and if the Request Type field (245) is "Remove", there may be no QoS characteristics element.

[0096] The Optional Subelements (265) field may include zero or one or more subelements and may include at least one of the Subelement ID field, Length field, and Data field to indicate additional information to be included in the SCS request frame or the SCS response frame.

[0097] Meanwhile, when the QoS requirements of an application change dynamically in Wi-Fi communication, it is necessary to notify the AP of the dynamic changes in QoS requirements so that the AP can better meet the QoS requirements of various LL (low latency) applications. Based on dynamic QoS updates, the AP can perform UL (uplink) and DL (downlink) scheduling more efficiently, thereby avoiding over-allocation or under-allocation of resources for STAs.

[0098] The QoS Characteristics of the above SCS request frame are defined to allow the STA to provide QoS requirements for its traffic flow. Accordingly, it is necessary to define a mechanism that allows a non-AP STA to dynamically change QoS expectations or QoS flows with the connected AP. Failing to dynamically change QoS requirements can interfere with latency-sensitive applications on the client. As previously illustrated in Fig. 2c, the SCS and QoS-related fields included in the SCS descriptor elements transmitted and received during the SCS negotiation process are primarily designed for static / semi-static flows where QoS Characteristics remain the same or change infrequently.

[0099] The existing SCS change mechanism can be used to update QoS requirements by transmitting the QoS characteristics of the traffic flow as updated QoS Characteristics in an SCS change ("change") request. However, in the case of dynamic QoS updates, the SCS change request must undergo a re-authentication process at the AP, so it may fail like a new SCS request or take time to complete, which can have a negative impact on the quality of the traffic flow.

[0100] STA may request the highest possible resource allocation in the initial SCS request (SCS + QoS characteristics) to reduce the possibility of future rejection, but this leads to over-allocation of resources, and in the worst case, there is a possibility that the SCS will fail due to a lack of available resources.

[0101] Furthermore, since the SCS Change approach does not provide a means for the AP to clearly recognize the scope of the application's QoS requirements, the AP may find it difficult to efficiently plan resources throughout the flow and meet dynamic QoS changes.

[0102] The QoS characteristics element field (260) of the SCS descriptor element described above in FIG. 2c may contain up to one QoS characteristics element. Accordingly, in order to include multiple QoS-related information (e.g., QoS profiles) having a single SCSID, multiple SCS descriptor elements must be included, which may entail overhead. Additionally, if an AP is classified as the same TCLAS elements in multiple SCS descriptor elements with different SCSIDs, a conflict may occur in the operation of the AP.

[0103] Furthermore, since the importance and utilization weight of multiple QoS-related information (e.g., QoS profiles) cannot be indicated, an AP receiving an SCS request frame may perform resource planning or provisioning based on the worst-case scenario among the multiple QoS-related information (e.g., QoS profiles). In this case, when the AP cannot accommodate some QoS-related information, it cannot determine how important that information is within the SCS stream.

[0104] The following is a description of each specific embodiment. The present invention may include a plurality of embodiments, each of which is distinguished for convenience to explain the implementation according to the present disclosure and may be implemented independently; however, as long as they are not mutually exclusive, all or part of the plurality of embodiments may be selectively combined and implemented. Such combinations include various variations and modifications of the present invention and may be made in various ways depending on technical needs or application environments. Even if the plurality of embodiments use different approaches to achieve the purpose of the invention, they may be used simultaneously or complementarily as long as the embodiments of the present invention are not technically mutually exclusive. Such combinations may be varied depending on technical requirements or specific application cases, and the present invention may encompass various embodiments including such variations and combinations. Although the name of a Wi-Fi communication system is used to describe the embodiments of the present disclosure, this is merely an example and can be understood as a message that includes information or performs the same role as described below.

[0105] In the present disclosure, the term QoS profile may include at least one of QoS-related setting information to be applied to a specific SCS stream, configuration information of the stream, and information regarding identification conditions of the stream. In one embodiment, the QoS profile may include a set of QoS parameters to be applied to a specific SCS stream. The set of QoS parameters may be represented using information elements within a QoS characteristics element field (260) included in an SCS descriptor element shown in FIG. 2c.

[0106] In one embodiment, the QoS profile may include priority-related settings to be applied to the corresponding SCS stream. The priority-related settings may be indicated using information elements within the Intra-Access Category Priority element field (247) included in the SCS descriptor element shown in FIG. 2c.

[0107] In one embodiment, the QoS profile may include information related to conditions for identifying a packet as belonging to a specific stream. The conditions for identification may be indicated using at least one of the information elements among the TCLAS (traffic classification) elements field (250) and the TCLAS processing element field (255) included in the SCS descriptor element shown in FIG. 2c.

[0108] Hereinafter, FIGS. 3a, 3b, 4a, 4b, 5a, 5b, and 5c describe the configuration of a request frame for an STA to request an AP to set a plurality of QoS profiles according to an embodiment of the present disclosure.

[0109] FIGS. 3a and 3b are drawings illustrating an example of an SCS request frame that transmits information about a plurality of quality of service (QoS) profiles using a plurality of SCS descriptor elements with different SCSIDs, according to an embodiment of the present disclosure.

[0110] FIG. 3a illustrates an example of an SCS request frame and an SCS Descriptor element included in the SCS request frame according to one embodiment of the present disclosure.

[0111] Referring to (a) of FIG. 3a, the SCS request frame (300) may include at least one of a Category field (310), a Robust Action field (315), a Dialog Token field, and an SCS descriptor list field (317). The Category field (310) may include a value (e.g., 19) representing a frame of Robust AV Streaming.

[0112] In one embodiment, to indicate that the SCS request frame (300) is an SCS request frame containing multiple QoS profiles and is an SCS request frame for operating a dynamic QoS profile, the value of the Robust Action field (315), which is the Action Field of the SCS request frame (300), may be used. FIG. 3b illustrates a value that may be included in the Robust Action field (315), and to indicate that the SCS request frame (300) is an SCS request frame containing multiple QoS profiles and is an SCS request frame for operating a dynamic QoS profile, the Robust Action field (315) may include a value (e.g., 6) signifying a D(dynamic)-SCS Request.

[0113] Referring to (a) of FIG. 3a, the SCS descriptor list field (317) may include multiple SCS descriptor elements (320, 325) having different SCSIDs. In one embodiment, each SCS descriptor element may include up to one QoS Characteristics element.

[0114] FIG. 3a(b) illustrates an example of each of the above SCS descriptor elements (320, 325). Referring to FIG. 3a(b), the SCS descriptor element (330) may include at least one of an SCSID field (331), a Request Type (333), and a QoS characteristics element field (335).

[0115] The above SCSID field (331) may include SCSID values ​​of each SCS descriptor element (320, 325), and in order to distinguish multiple QoS profiles, the SCSID field (331) of each SCS descriptor element (320, 325) may include different SCSID values.

[0116] The above Request Type (333) may request the creation or modification of an SCS stream by including a value (0 or 2) indicating "Add" or "Change".

[0117] The above QoS characteristics element field (335) may include up to one QoS Characteristics element and may include information elements describing the characteristics of the traffic flow belonging to the SCS stream corresponding to each SCSID and QoS expectations.

[0118] In one embodiment, as described in FIG. 3a, when information about multiple quality of service (QoS) profiles is transmitted using multiple SCS descriptor elements with different SCSIDs in an SCS request frame, if the value of the Robust Action field (315) includes a value (e.g., 6) indicating a D(dynamic)-SCS Request, the access point can recognize that it is an SCS request frame for operating a dynamic QoS profile. In this case, the AP can recognize that it is a setting for operating a dynamic QoS profile for a specific stream, even if the TCLAS elements fields included in multiple SCS descriptor elements with different SCSIDs within the received SCS request frame indicate the same TCLAS elements.

[0119] FIGS. 4a and 4b are drawings illustrating an example of an SCS request frame that transmits information about a plurality of QoS profiles using a plurality of SCS descriptor elements having the same SCSID and different profile IDs, according to an embodiment of the present disclosure.

[0120] FIG. 4a illustrates an example of an SCS request frame (400), an SCS Descriptor element (430) that may be included in the SCS request frame (400), and a Subelement (440) that may be included in the SCS Descriptor element, according to one embodiment of the present disclosure.

[0121] Referring to (a) of FIG. 4a, the SCS request frame (400) may include at least one of a Category field (410), a Robust Action field (415), a Dialog Token field, and an SCS descriptor list field (417). The Category field (410) may include a value (e.g., 19) representing a frame of Robust AV Streaming.

[0122] In one embodiment, to indicate that the SCS request frame (400) is an SCS request frame containing multiple QoS profiles and is an SCS request frame for operating a dynamic QoS profile, the Robust Action field (415) may include a value (e.g., 6) signifying a D(dynamic)-SCS Request, as described in FIG. 3b. Alternatively, in one embodiment, the Robust Action field (415), which is the Action Field of the SCS request frame (400), may include a value (e.g., 0) signifying an SCS Request.

[0123] Referring to FIG. 4a (a), the SCS descriptor list field (417) may include multiple SCS descriptor elements (420, 425) having the same SCSID. In one embodiment, each SCS descriptor element may include up to one QoS Characteristics element.

[0124] FIG. 4a(b) illustrates an SCS descriptor element (430) which is an example of each of the above SCS descriptor elements (420, 425). Referring to FIG. 4a(b), the SCS descriptor element (430) may include at least one of an SCSID field (431), a Request Type field (433), a QoS characteristics element field (435), and an Optional Subelements field (437).

[0125] The above SCSID field (431) may include SCSID values ​​of each SCS descriptor element (420, 425), and in one embodiment, the SCSID field (431) of each SCS descriptor element (420, 425) may include the same SCSID value (e.g., X).

[0126] The above Request Type field (433) may request the creation or modification of settings for an SCS stream by including a value (0 or 2) indicating "Add" or "Change".

[0127] The above QoS characteristics element field (435) may include up to one QoS Characteristics element and may include information elements (e.g., at least one parameter) describing the characteristics of the traffic flow belonging to the SCS stream corresponding to each SCSID and the QoS expectations.

[0128] The Optional Subelements field (437) may contain zero or one or more subelements. In one embodiment, when transmitting information about multiple quality of service (QoS) profiles using multiple SCS descriptor elements (420, 425) with the same SCSID in an SCS request frame (400), the QoS profiles can be distinguished by including different profile IDs in each Optional Subelements field (437) included in the multiple SCS descriptor elements (420, 425) with the same SCSID.

[0129] Figure 4a (c) illustrates an example in which a Subelement (440) included in the Optional Subelements field (437) includes a field for indicating different profile IDs to distinguish multiple QoS profiles.

[0130] Referring to FIG. 4a(c), the Subelement (440) may include a Subelement ID field (441), a Length field, and a Profile ID field (443). The Subelement ID field (441) may include a value indicating the type of data that may be included in the Subelement (440). FIG. 4b illustrates an example of a value that may be included in the Subelement ID field (441). In one embodiment, the Subelement ID field (441) may include a value (e.g., 0) indicating that the data field of the Subelement (440) includes a Profile ID.

[0131] The above Profile ID field (443) can be used to distinguish information about multiple QoS profiles by including different values ​​for each SCS descriptor element containing information about multiple QoS profiles.

[0132] FIGS. 5a, 5b, and 5c are drawings illustrating an example of an SCS request frame that transmits information about a plurality of QoS profiles using a plurality of QoS characteristic elements with different profile IDs included in a single SCS Descriptor element, according to an embodiment of the present disclosure.

[0133] FIG. 5a illustrates an example of an SCS request frame (500), an SCS Descriptor element (530) that may be included in the SCS request frame (500), and a Subelement (540) that may be included in the SCS Descriptor element (530), according to one embodiment of the present disclosure.

[0134] Referring to (a) of FIG. 5a, the SCS request frame (500) may include at least one of a Category field (510), a Robust Action field (515), a Dialog Token field, and an SCS descriptor list field (517).

[0135] In one embodiment, the Category field (510) may include a value (e.g., 19) representing a frame of Robust AV Streaming.

[0136] In one embodiment, to indicate that the SCS request frame (500) is an SCS request frame containing multiple QoS profiles and is an SCS request frame for operating a dynamic QoS profile, the Robust Action field (515) may include a value (e.g., 6) signifying a D(dynamic)-SCS Request as described in FIG. 3b. Alternatively, in one embodiment, the Robust Action field (515), which is the Action Field of the SCS request frame (500), may include a value (e.g., 0) signifying an SCS Request.

[0137] Referring to (a) of FIG. 5a, the SCS descriptor list field (517) may contain a single SCS Descriptor element having any SCSID. In one embodiment, each SCS descriptor element may contain zero or one or more QoS Characteristics elements.

[0138] FIG. 5a(b) illustrates an SCS descriptor element (530) which is an example of an SCS descriptor element included in the SCS descriptor list field (517). Referring to FIG. 5a(b), the SCS descriptor element (530) may include at least one of an SCSID field (531), a Request Type field (533), a QoS characteristics element field (535), and an Optional Subelements field (537).

[0139] The above SCSID field (531) may include SCSID values ​​of SCS descriptor elements included in the above SCS descriptor list field (517).

[0140] The above Request Type field (533) may request the creation or modification of a setting for an SCS stream by including a value (e.g., 0 or 2) indicating "Add" or "Change".

[0141] The above QoS characteristics element field (535) may include zero or one or more QoS Characteristics elements and may include information elements (e.g., at least one parameter) describing the characteristics of the traffic flow belonging to the SCS stream corresponding to the SCSID and QoS expectations. If the above QoS characteristics element field (535) includes multiple QoS Characteristics elements (e.g., QoS profiles), the multiple QoS characteristic elements may include different profile IDs within the above QoS characteristics element field (535) to distinguish the QoS profiles. A detailed description of the above QoS characteristics element field (535) is provided later in FIG. 5b.

[0142] The Optional Subelements field (537) may include zero or one or more subelements. In one embodiment, when transmitting information about a plurality of quality of service (QoS) profiles in an SCS request frame (500), the Optional Subelements field (537) included in at least one SCS Descriptor element (530) may include information about a plurality of QoS profiles (e.g., a plurality of QoS characteristic elements).

[0143] Figure 5a (c) illustrates an example in which a Subelement (540) included in the Optional Subelements field (537) includes a field for including multiple QoS profiles.

[0144] Referring to FIG. 5a(c), a Subelement (540) may include a Subelement ID field (541), a Length field, and a Multiple QoS Characteristic elements field (543). The Subelement ID field (541) may include a value indicating the type of data that may be included in the Subelement (540). FIG. 5c illustrates an example of a value that may be included in the Subelement ID field (541). In one embodiment, the Subelement ID field (541) may include a value (e.g., 4) indicating that the data field of the Subelement (540) will include Multiple QoS Characteristic elements.

[0145] The above Multiple QoS Characteristic elements field (543) may include information about multiple QoS profiles (e.g., multiple QoS characteristic elements). In this case, the above QoS characteristics element field (535) may not include QoS Characteristics elements. That is, information about multiple QoS profiles may be included in the above QoS characteristics element field (535) or the above Multiple QoS Characteristic elements field (543).

[0146] FIG. 5b illustrates an example of a QoS Characteristics element (550) that may be included in the QoS characteristics element field (535) or the Multiple QoS Characteristic elements field (543) according to one embodiment of the present disclosure, and a Control Info field (553) that may be included in the QoS Characteristics element (550).

[0147] Referring to FIG. 5b(a), when the QoS characteristics element field (535) contains a plurality of QoS Characteristics elements, each QoS Characteristics element (550) may include a Profile ID field (555) to distinguish the plurality of QoS Characteristics elements. The Profile ID field (555) may represent a Profile ID value for distinguishing the plurality of QoS Characteristics elements.

[0148] FIG. 5b(b) illustrates the information elements of the Control Info field (553) included in each QoS Characteristics element (550), and the Control Info field (553) may include a Profile ID Presence field (560). The Profile ID Presence field (560) may include a value indicating the presence of the Profile ID field (555).

[0149] Hereinafter, FIGS. 6a, 6b, 7, 8a, and 8b describe the configuration of a response frame for indicating whether to accept the setting of a plurality of QoS profiles requested within a request frame, according to one embodiment of the present disclosure, where AP is STA.

[0150] FIGS. 6a and 6b are drawings illustrating an example of an SCS response frame indicating acceptance of a plurality of QoS profiles included in a plurality of SCS descriptor elements with different SCSIDs, according to an embodiment of the present disclosure.

[0151] FIG. 6a illustrates an example of an SCS status duple (630) that may be included in an SCS response frame (600) and an SCS Status List field (617) of the SCS response frame (600), according to one embodiment of the present disclosure.

[0152] Referring to (a) of FIG. 6a, the SCS response frame (600) may include at least one of a Category field (610), a Robust Action field (615), a Dialog Token field, an SCS status list field (617), and an SCS Descriptor List (619). The Category field (610) may include a value (e.g., 19) representing a frame of Robust AV Streaming.

[0153] In one embodiment, the value of the Robust Action field (615), which is the Action Field of the SCS response frame (600), may be used to indicate that the SCS response frame (600) is a response frame to an SCS request frame containing multiple QoS profiles and / or an SCS response frame for operating a dynamic QoS profile. FIG. 6b illustrates a value that may be included in the Robust Action field (615), and to indicate that the SCS response frame (600) is a response frame to an SCS request frame containing multiple QoS profiles and / or an SCS response frame for operating a dynamic QoS profile, the Robust Action field (615) may include a value (e.g., 7) representing a D(dynamic)-SCS Response.

[0154] Referring to (a) of FIG. 6a, the SCS Status List field (617) may include multiple SCS Status duples (620, 625) having different SCSIDs. The multiple SCS Status duples (620, 625) may include acceptance statuses for multiple QoS profiles included in multiple SCS descriptor elements that have different SCSIDs included in the SCS request frame received by the AP.

[0155] FIG. 6a(b) illustrates an example of the SCS Status duples (620, 625). Referring to FIG. 6a(b), the SCS Status duple (630) may include at least one of the SCSID field (631) and the Status field (633).

[0156] In one embodiment, the SCSID field (631) may include the SCSID value of an SCS descriptor element that contains information of a QoS profile to indicate acceptance in the corresponding Status field (633) among the different SCSIDs of a plurality of SCS descriptor elements included in an SCS request frame received by the AP.

[0157] In one embodiment, the Status field (633) may indicate the status of the requested SCSID. That is, the Status field (633) may include a value indicating whether the QoS profile included in the SCS descriptor element corresponding to the SCSID value included in the SCSID field (631) among the plurality of SCS descriptor elements included in the SCS request frame received by the AP is accepted.

[0158] In one embodiment, the Status field (633) may include at least one of the values ​​representing “SUCCESS,” “REJECTED,” or “REJECTED_SUGGESTED_CHANGED.”

[0159] In one embodiment, when the Status field (633) contains a value representing at least one "rejection and offer parameter (REJECTED_SUGGESTED_CHANGED)", at least one SCS descriptor element included in the SCS Descriptor List field (619) may include a set of QoS parameters that can be provided to the QoS Characteristics element field.

[0160] FIG. 7 is a diagram illustrating an example of an SCS response frame indicating whether to fully accept a plurality of QoS profiles that have the same SCSID and are indicated by different profile IDs, according to one embodiment of the present disclosure.

[0161] FIG. 7 illustrates an example of an SCS status duple (730) that may be included in an SCS response frame (700) and an SCS Status (717) of the SCS response frame (700), according to one embodiment of the present disclosure.

[0162] Referring to FIG. 7(a), the SCS response frame (700) may include at least one of a Category field (710), a Robust Action field (715), a Dialog Token field, an SCS status list field (717), and an SCS Descriptor List (719). The Category field (710) may include a value (e.g., 19) representing a frame of Robust AV Streaming.

[0163] In one embodiment, to indicate that the SCS response frame (700) is a response frame to an SCS request frame containing a plurality of QoS profiles and / or an SCS response frame for operating a dynamic QoS profile, the Robust Action field (715), which is the Action Field of the SCS response frame (700), may include a value (e.g., 7) representing a D(dynamic)-SCS Response as described in FIG. 6b. Alternatively, in one embodiment, the Robust Action field (715) may include a value (e.g., 1) representing an SCS Response.

[0164] FIG. 7(b) illustrates an example of an SCS Status duple (730) included in an SCS Status field (717). Referring to FIG. 7(b), the SCS Status duple (730) may include at least one of an SCSID field (731) and a Status field (733).

[0165] In one embodiment, the SCSID field (731) may include the same SCSID value of a plurality of SCS descriptor elements included in an SCS request frame received by the AP.

[0166] In one embodiment, the Status field (733) may indicate the status of the requested SCSID. That is, the Status field (733) may include a value indicating whether the QoS profile included in the SCS descriptor element corresponding to the SCSID value included in the SCSID field (731) is fully accepted.

[0167] In one embodiment, the Status field (733) may include at least one of the values ​​representing “SUCCESS,” “REJECTED,” or “REJECTED_SUGGESTED_CHANGED.”

[0168] In one embodiment, when the Status field (733) contains a value representing a rejection and proposal parameter (REJECTED_WITH_SUGGESTED_CHANGED), at least one SCS descriptor element included in the SCS Descriptor List field (719) may include a set of QoS parameters that can be provided to the QoS Characteristics element field.

[0169] In one embodiment, the SCS response frame illustrated in FIG. 7 can be transmitted as a response frame to the SCS request frame illustrated in FIG. 4a and FIG. 5a.

[0170] FIGS. 8a and 8b are drawings illustrating an example of an SCS response frame indicating partial acceptance of a plurality of QoS profiles with the same SCSID and different profile IDs, according to an embodiment of the present disclosure.

[0171] FIG. 8a illustrates an example of an SCS status duple (830) that may be included in an SCS response frame (800) and an SCS Status (817) field of the SCS response frame (800), according to one embodiment of the present disclosure.

[0172] Referring to (a) of FIG. 8a, the SCS response frame (800) may include at least one of a Category field (810), a Robust Action field (815), a Dialog Token field, an SCS status list field (817), and an SCS Descriptor List (819). The Category field (810) may include a value (e.g., 19) representing a frame of Robust AV Streaming.

[0173] In one embodiment, to indicate that the SCS response frame (800) is a response frame to an SCS request frame containing multiple QoS profiles and / or an SCS response frame for operating a dynamic QoS profile, the Robust Action field (815), which is the Action Field of the SCS response frame (800), may include a value (e.g., 7) representing a D(dynamic)-SCS Response as described in FIG. 6b. Alternatively, in one embodiment, the Robust Action field (815) may include a value (e.g., 1) representing an SCS Response.

[0174] FIG. 8a(b) illustrates an example of an SCS Status duple (830) included in an SCS Status field (817). Referring to FIG. 8(b), the SCS Status duple (830) may include at least one of an SCSID field (831) and a Status field (833).

[0175] In one embodiment, the SCSID field (831) may include the same SCSID value of a plurality of SCS descriptor elements included in an SCS request frame received by the AP.

[0176] In one embodiment, the Status field (833) may indicate the status of the requested SCSID. That is, the Status field (833) may include a value indicating whether the QoS profile included in the SCS descriptor element corresponding to the SCSID value included in the SCSID field (831) is partially accepted.

[0177] In one embodiment, the Status field (833) may include at least one of the values ​​representing “partial acceptance (e.g., PARTIALLY_SUCCESS”), “partial rejection (e.g., PARTIALLY_REJECTED”), or “partial rejection and offer parameter (e.g., PARTIALLY_REJECTED_WITH_SUGGESTED_CHANGED”).

[0178] In one embodiment, the SCS Descriptor List field (819) may include at least one Profile ID value for a partially accepted or partially rejected QoS profile. In one embodiment, the SCS Descriptor List field (819) may include a set of QoS parameters available for each rejected profile, or a list of rejected profiles with one set of QoS parameters that are commonly applied, when the Status field (833) includes a value indicating “partially rejected (PARTIALLY_REJECTED)" or “partially rejected and proposed parameters (PARTIALLY_REJECTED_WITH_SUGGESTED_CHANGED).”

[0179] FIG. 8b illustrates an example of an SCS Descriptor element (840) that may be included in the SCS Descriptor List field (819) and a Subelement (850) that may be included in the Optional Subelements field (845) of the SCS Descriptor element (840), according to one embodiment of the present disclosure.

[0180] Referring to (a) of FIG. 8b, the SCS Descriptor element (840) may include at least one of a QoS characteristics element field (843) and an Optional Subelements field (845).

[0181] In one embodiment, when the Status field (833) contains a value indicating “PARTIALLY_REJECTED_WITH_SUGGESTED_CHANGED”, the QoS characteristics element field (843) may contain a set of QoS parameters that can be provided for each rejected profile, or a list of rejected profiles with a single set of QoS parameters that is applied commonly.

[0182] FIG. 8b(b) illustrates an example of at least one Subelement (850) that may be included in the Optional subelements field (845). Referring to FIG. 8b(b), the Subelement (850) may include at least one of a Subelement ID field (851), a Length field (853), and a Profile ID field (855).

[0183] The above Subelement ID field (851) may include a value indicating the type of data that can be included in the above Subelement (850), and as described in FIG. 4b, the above Subelement ID field (851) may include a value (e.g., 0) indicating that the data field of the above Subelement (850) includes a Profile ID.

[0184] The above Profile ID field (855) may include a list of at least one Profile ID value for some accepted or some rejected QoS profiles.

[0185] The Length field (853) may have a value equal to the number of at least one Profile ID value included in the Profile ID field (855).

[0186] In one embodiment, the SCS response frame illustrated in FIG. 8 can be transmitted as a response frame to the SCS request frame illustrated in FIG. 4a and FIG. 5a.

[0187] Hereinafter, FIGS. 9a, 9b, 10, 11, and 12 describe a configuration in which a requesting STA (STA) transmits a request frame to an AP (requested STA) for requesting the setting of a plurality of QoS profiles, including priority information and time information for each profile, according to one embodiment of the present disclosure.

[0188] The above priority information may indicate priority by profile. The above priority information may include priority information indicating an essential profile (or mandatory profile). For example, the priority information indicating an essential profile may include a predefined specific value (e.g., 0). Among the above priority information, priority information containing a value other than the specific value indicating an essential profile may indicate an optional profile.

[0189] In one embodiment, the AP (requested STA) may be required to accept the essential profile when determining whether to accept the profiles included in the SCS request frame in which the priority information is displayed. That is, if some of the essential profiles cannot be accepted, the entire SCS request may be rejected.

[0190] The above time information may represent application time information per profile. The above time information may include, for example, at least one of periodic application information of the corresponding profile or relative application time ratio information per profile.

[0191] FIGS. 9a and 9b are drawings illustrating an example of an SCS descriptor element that displays priority information of a plurality of QoS profiles separated into a plurality of different SCS descriptor elements, according to an embodiment of the present disclosure.

[0192] FIG. 9a illustrates an example of an SCS Descriptor element (900) and a Subelement (920) that may be included in the Optional Subelements (910) of the SCS Descriptor element (900), according to one embodiment of the present disclosure.

[0193] The above SCS Descriptor element (900) illustrates an example of the plurality of SCS descriptor elements when the SCS request frame transmitted by the STA (requesting STA) to the AP (requested STA), as described in FIG. 3a, includes information about the plurality of QoS profiles using the plurality of SCS descriptor elements with different SCSIDs. Alternatively, the above SCS Descriptor element (900) illustrates an example of the plurality of SCS descriptor elements when the SCS request frame transmitted by the STA (requesting STA) to the AP (requested STA), as described in FIG. 4a, includes information about the plurality of QoS profiles using the plurality of SCS descriptor elements with the same SCSID and different profile IDs.

[0194] Accordingly, the descriptions for the SCSID field, Request Type field, and QoS Characteristics element field of the above SCS Descriptor element (900) may be applied to the descriptions of fields with the same names described in the description of FIG. 3a (b) or FIG. 4a (b).

[0195] Referring to (a) of FIG. 9a, the SCS Descriptor element (900) may include an Optional Subelements field (910), and the Optional Subelements field (910) may include priority information for QoS profiles included in a plurality of SCS descriptor elements. The priority information may include a value representing a priority per profile.

[0196] Referring to FIG. 9a(b), the Subelement (920) may include at least one of a Subelement ID field (925) and a Priority field (927). Additionally, if the SCS Descriptor element (900) is one of a plurality of SCS descriptor elements having the same SCSID and different profile IDs, the Subelement (920) may further include at least one of a Subelement ID field (921) and a Profile ID field (923). The description of the Subelement ID field (921) and the Profile ID field (923) described in FIG. 4a(c) may be applied to the Subelement ID field (441) and the Profile ID field (443).

[0197] The above Subelement ID field (925) may include a value indicating the type of data that may be included in the above Subelement (920). FIG. 9b illustrates an example of a value that may be included in the above Subelement ID field (925). In one embodiment, the above Subelement ID field (925) may include a value (e.g., 1) indicating that the data field of the above Subelement (920) includes a Priority value.

[0198] The above Priority field (927) may include priority information for the QoS profile included in the above SCS Descriptor element (900).

[0199] FIG. 10 is a drawing illustrating an example of an SCS descriptor element that displays time information of a plurality of QoS profiles separated into a plurality of different SCS descriptor elements, according to one embodiment of the present disclosure.

[0200] FIG. 10 illustrates an example of an SCS Descriptor element (1000) and a Subelement (1020) that may be included in the Optional Subelements (1010) of the SCS Descriptor element (1000), according to one embodiment of the present disclosure.

[0201] The description of the SCS Descriptor element (1000) shown in Fig. 10 (a) can be applied to the description of the SCS Descriptor element (900) shown in Fig. 9a (a).

[0202] Referring to FIG. 10 (a), the SCS Descriptor element (1000) may include an Optional Subelements field (1010), and the Optional Subelements field (1010) may include time information for QoS profiles included in a plurality of SCS descriptor elements.

[0203] Referring to FIG. 10(b), the Subelement (1020) may include at least one of a Subelement ID field (1025), a Type field (1027), and a Time Data field (1029). Additionally, if the SCS Descriptor element (1000) is one of a plurality of SCS descriptor elements having the same SCSID and different profile IDs, the Subelement (1020) may further include at least one of a Subelement ID field (1021) and a Profile ID field (1023). The description of the Subelement ID field (1021) and the Profile ID field (1023) described in FIG. 4a(c) may be applied to the Subelement ID field (441) and the Profile ID field (443).

[0204] The above Subelement ID field (1025) may include a value indicating the type of data that can be included in the above Subelement (1020). FIG. 9b, described above, illustrates an example of a value that can be included in the above Subelement ID field (1025). In one embodiment, the above Subelement ID field (1025) may include a value (e.g., 2) indicating that time information (Time info) will be included in the data field of the above Subelement (1020).

[0205] The Type field (1027) may include type information indicating the type of time information included in the Time Data field (1029). In one embodiment, the type of time information may include at least one of application cycle information and relative ratio information of application time per profile. The type information may include a value indicating the application cycle information (e.g., 0) or a value indicating the relative ratio information of application time per profile (e.g., 1).

[0206] The Time Data field (1029) may include time information. In one embodiment, if the Type field (1027) includes a value (e.g., 0) representing the application period information, the Time Data field (1029) may include at least one of the Start Time field (1040), the Duration field (1043), and the Interval field (1045).

[0207] The Start Time field (1040) may include information regarding the start time of application of the profile. The Duration field (1043) may include information regarding the application time of the profile. The Interval field (1045) may include information regarding the interval time between the application cycles of the profile.

[0208] In one embodiment, if the Type field (1027) includes a value (e.g., 1) representing relative ratio information of the application time per profile, the Time Data field (1029) may include a Ratio field (1030).

[0209] The above Ratio field (1030) may include information (e.g., 0.3) representing the ratio of the time a corresponding profile is applied among the multiple QoS profiles requested in the SCS request frame.

[0210] FIG. 11 is a drawing illustrating an example of a QoS characteristics element that displays priority information of a plurality of QoS profiles distinguished by a plurality of different QoS characteristics elements, according to one embodiment of the present disclosure.

[0211] FIG. 11 illustrates an example of an SCS Descriptor element (1100), a QoS Characteristics element (1120) that may be included in the QoS characteristics element field (1110) of the SCS Descriptor element (1100), and a Control Info field (1130) that may be included in the QoS Characteristics element (1120), according to one embodiment of the present disclosure.

[0212] The above SCS Descriptor element (1100) includes an example of an SCS Descriptor element in which, as described in FIG. 5a, the SCS request frame transmitted by the STA (requesting STA) to the AP (requested STA) includes information about multiple QoS profiles using multiple QoS characteristic elements with different profile IDs included in the SCS Descriptor element with the same SCSID.

[0213] Accordingly, the descriptions for the SCSID field, Request Type field, and QoS Characteristics element field of the above SCS Descriptor element (1100) may be applied to the descriptions for the fields with the same names as described in (b) of FIG. 5a.

[0214] The QoS Characteristics element field (1110) of the above SCS Descriptor element (1100) may include zero or one or more QoS Characteristics elements.

[0215] Figure 11 (b) illustrates an example of the plurality of QoS characteristic elements.

[0216] Referring to FIG. 11(b), the QoS characteristic element (1120) may include at least one of a Control Info field (1130), a Profile ID field (1133), and a Priority field (1135). The QoS characteristic element (1120) may include priority information for the included QoS profile.

[0217] The above Control Info field (1130) may include at least one field indicating whether at least one of the Profile ID field (1133) and the Priority field (1135) exists.

[0218] The Priority field (1135) may indicate priority information of the corresponding QoS profile. The Profile ID field (1133) may include the Profile ID of the corresponding QoS profile.

[0219] Referring to Fig. 11 (c), the Control Info field (1130) may include at least one of a Profile ID Presence field (1150) indicating whether a Profile ID field (1133) exists and a Priority Presence field (1155) indicating whether a Priority field (1135) exists.

[0220] FIG. 12 is a diagram illustrating an example of a QoS characteristics element that displays time information of a plurality of QoS profiles, which are distinguished into a plurality of different QoS characteristics elements, according to one embodiment of the present disclosure.

[0221] FIG. 12 illustrates an example of a QoS Characteristics element (1200), a Control Info field (1210) that may be included in the QoS Characteristics element (1200), and a Time Info field (1215) that may be included in the Control Info field (1210), according to one embodiment of the present disclosure.

[0222] Figure 12 (a) illustrates an example of the above QoS characteristic element.

[0223] Referring to FIG. 12(a), the QoS characteristic element (1200) may include at least one of a Control Info field (1210), a Profile ID field (1213), and a Time Info field (1215). The QoS characteristic element (1200) may include time information for the included QoS profile.

[0224] The above Control Info field (1210) may include at least one field indicating whether at least one of the Profile ID field (1213) and the Time Info field (1215) exists.

[0225] The Time Info field (1215) above may include time information of the corresponding QoS profile. The Profile ID field (1213) above may include the Profile ID of the corresponding QoS profile.

[0226] Referring to FIG. 12(b), the Control Info field (1210) may include at least one of a Profile ID Presence field (1220) indicating whether a Profile ID field (1213) exists, and a Time Info Presence field (1225) indicating whether a Time Info field (1215) exists.

[0227] Referring to Fig. 12 (c), the Time Info field (1215) may include at least one of a Type field (1230) and a Time Data field (1235).

[0228] The Type field (1230) may include type information indicating the type of time information included in the Time Data field (1235). In one embodiment, the type of time information may include application cycle information and relative ratio information of application time per profile. The type information may include a value indicating the application cycle information (e.g., 0) or a value indicating the relative ratio information of application time per profile (e.g., 1).

[0229] The Time Data field (1235) may include time information. In one embodiment, if the Type field (1230) includes a value (e.g., 0) representing the application period information, the Time Data field (1235) may include at least one of the Start Time field (1250), the Duration field (1253), and the Interval field (1255).

[0230] The Start Time field (1250) may include information regarding the start time of application of the profile. The Duration field (1253) may include information regarding the application time of the profile. The Interval field (1255) may include information regarding the interval time between application cycles of the profile.

[0231] In one embodiment, if the Type field (1230) includes a value (e.g., 1) representing relative ratio information of the application time per profile, the Time Data field (1235) may include a Ratio field (1240).

[0232] The above Ratio field (1240) may include information (e.g., 0.3) representing the ratio of the time a corresponding profile is applied among the multiple QoS profiles requested in the SCS request frame.

[0233] FIGS. 13a and FIG. 13b are drawings illustrating an example of a QoS characteristics element that displays priority information and time information of a plurality of QoS profiles distinguished by a plurality of different QoS characteristics elements, according to an embodiment of the present disclosure.

[0234] FIGS. 13a and FIG. 13b illustrate an example of a QoS characteristics element that includes priority information of multiple QoS profiles distinguished by multiple different QoS characteristics elements described in FIG. 11 and time information described in FIG. 12.

[0235] FIG. 13a illustrates an example of a QoS characteristics element (1300) that includes priority information and time information of multiple QoS profiles, which are distinguished into multiple different QoS characteristics elements.

[0236] Referring to FIG. 13a, the QoS characteristics element (1300) may include at least one of a Control Info field (1310), a Profile ID field (1313), a Priority field (1315), and a Time Info field (1317). The descriptions for the Profile ID field (1313), the Priority field (1315), and the Time Info field (1317) may be applied to the descriptions of fields with the same names in FIG. 11 and FIG. 12.

[0237] The above Control Info field (1310) can indicate whether there are priority information and time information related fields of multiple QoS profiles in the QoS characteristics element.

[0238] Figures 13b (a) and (b) illustrate an example of the configuration of the Control Info field (1310).

[0239] FIG. 13b(a) illustrates the configuration of a Control Info field (1320) that may be included as an example of the Control Info field (1310). Referring to FIG. 13a(a), the Control Info field (1320) may include at least one of a Profile ID Presence field (1330) indicating whether the Profile ID field (1313) exists in the QoS characteristics element, a Priority Presence field (1333) indicating whether the Priority field (1315) exists in the QoS characteristics element, and a Time Info Presence field (1335) indicating whether the Time Info field (1317) exists in the QoS characteristics element.

[0240] FIG. 13b(b) illustrates the configuration of a Control Info field (1340) that may be included as an example of a Control Info field (1310). Referring to FIG. 13b(b), the Control Info field (1340) may include a D-SCS Info Presence field (e.g., 1 bit) (1350) indicating whether the Profile ID field (1313), Priority field (1315), and Time Info field (1317) exist in the QoS characteristics element.

[0241] The size (e.g., byte / bit size) and / or position of each of the fields included in the frame formats or element formats illustrated in FIGS. 2a to 13b are merely examples for convenience of explanation, and the size and / or position of each of the fields may be implemented with various values ​​according to design specifications.

[0242] FIG. 14 is a flowchart illustrating the operation of a station according to one embodiment of the present disclosure.

[0243] In step 1400, the station can send an SCS request frame to the access point to set up a stream classification service (SCS) stream.

[0244] In step 1410, the station may receive an SCS response frame from the access point to establish the SCS stream.

[0245] In one embodiment, the SCS request frame may include information on a plurality of QoS (quality of service) profiles that can be dynamically applied to the SCS stream.

[0246] In one embodiment, the plurality of QoS profiles included in the SCS request frame can be distinguished by different SCSIDs (stream classification service identifiers).

[0247] In one embodiment, the plurality of QoS profiles included in the SCS request frame may be included in SCS descriptor elements including the different SCSIDs.

[0248] In one embodiment, the plurality of QoS profiles included in the SCS request frame can be distinguished by different Profile IDs (identifiers).

[0249] In one embodiment, the plurality of QoS profiles included in the SCS request frame may be included in SCS descriptor elements distinguished by the different Profile IDs or QoS Characteristics elements distinguished by the different Profile IDs.

[0250] In one embodiment, the SCS response frame may include information indicating whether to accept at least one of the plurality of QoS profiles.

[0251] In one embodiment, the SCS response frame may include information indicating whether to accept the QoS profile corresponding to each SCSID when the plurality of QoS profiles included in the SCS request frame are distinguished by different SCSIDs.

[0252] In one embodiment, the SCS response frame may include information indicating whether to accept all of the plurality of QoS profiles when the plurality of QoS profiles included in the SCS request frame are distinguished by different Profile IDs.

[0253] In one embodiment, the plurality of QoS profiles included in the SCS request frame are distinguished by different Profile IDs, and the SCS response frame includes information indicating whether to accept a portion of the plurality of QoS profiles; in this case, the SCS response frame may include at least one Profile ID corresponding to at least one QoS profile for which acceptance is indicated.

[0254] In one embodiment, information indicating whether to accept a portion of the plurality of QoS profiles may include at least one of information indicating partial acceptance, partial rejection, and proposed changes upon partial rejection.

[0255] In one embodiment, if the SCS response frame includes information indicating a proposed change when partially rejecting some of the plurality of QoS profiles, the information regarding the proposed change when partially rejecting some of the plurality of QoS profiles may be included in the SCS Descriptor element of the SCS response frame.

[0256] In one embodiment, the SCS request frame may include at least one of priority information or time information for the plurality of QoS profiles.

[0257] In one embodiment, the priority information may include priority information indicating that the corresponding QoS profile is an essential profile or mandatory profile.

[0258] In one embodiment, if the corresponding QoS profile corresponding to the essential profile is not accepted, the SCS request frame may be rejected.

[0259] In one embodiment, the time information may include at least one of periodic application information of the corresponding QoS profile or relative application time ratio information of the corresponding QoS profile among the plurality of QoS profiles.

[0260] In one embodiment, at least one of the priority information or time information for the plurality of QoS profiles may be included in at least one of the SCS Descriptor element or QoS Characteristics element of the SCS request frame.

[0261] FIG. 15 is a flowchart illustrating the operation of an access point according to one embodiment of the present disclosure.

[0262] At step 1500, the access point can receive an SCS request frame from the station to establish an SCS stream.

[0263] In step 1510, the access point can send an SCS response frame to the station to establish the SCS stream.

[0264] In one embodiment, the SCS request frame may include information on a plurality of QoS profiles that can be dynamically applied to the SCS stream.

[0265] In one embodiment, the plurality of QoS profiles included in the SCS request frame can be distinguished by different SCSIDs (stream classification service identifiers).

[0266] In one embodiment, the plurality of QoS profiles included in the SCS request frame may be included in SCS descriptor elements including the different SCSIDs.

[0267] In one embodiment, the plurality of QoS profiles included in the SCS request frame can be distinguished by different Profile IDs (identifiers).

[0268] In one embodiment, the plurality of QoS profiles included in the SCS request frame may be included in SCS descriptor elements distinguished by the different Profile IDs or QoS Characteristics elements distinguished by the different Profile IDs.

[0269] In one embodiment, the SCS response frame may include information indicating whether to accept at least one of the plurality of QoS profiles.

[0270] In one embodiment, the SCS response frame may include information indicating whether to accept the QoS profile corresponding to each SCSID when the plurality of QoS profiles included in the SCS request frame are distinguished by different SCSIDs.

[0271] In one embodiment, the SCS response frame may include information indicating whether to accept all of the plurality of QoS profiles when the plurality of QoS profiles included in the SCS request frame are distinguished by different Profile IDs.

[0272] In one embodiment, the plurality of QoS profiles included in the SCS request frame are distinguished by different Profile IDs, and the SCS response frame includes information indicating whether to accept a portion of the plurality of QoS profiles; in this case, the SCS response frame may include at least one Profile ID corresponding to at least one QoS profile for which acceptance is indicated.

[0273] In one embodiment, information indicating whether to accept a portion of the plurality of QoS profiles may include at least one of information indicating partial acceptance, partial rejection, and proposed changes upon partial rejection.

[0274] In one embodiment, if the SCS response frame includes information indicating a proposed change when partially rejecting some of the plurality of QoS profiles, the information regarding the proposed change when partially rejecting some of the plurality of QoS profiles may be included in the SCS Descriptor element of the SCS response frame.

[0275] In one embodiment, the SCS request frame may include at least one of priority information or time information for the plurality of QoS profiles.

[0276] In one embodiment, the priority information may include priority information indicating that the corresponding QoS profile is an essential profile or mandatory profile.

[0277] In one embodiment, if the corresponding QoS profile corresponding to the essential profile is not accepted, the SCS request frame may be rejected.

[0278] In one embodiment, the time information may include at least one of periodic application information of the corresponding QoS profile or relative application time ratio information of the corresponding QoS profile among the plurality of QoS profiles.

[0279] In one embodiment, at least one of the priority information or time information for the plurality of QoS profiles may be included in at least one of the SCS Descriptor element or QoS Characteristics element of the SCS request frame.

[0280] FIG. 16 is a drawing showing an example of a configuration of a station according to one embodiment of the present disclosure.

[0281] In FIG. 16, the station may include at least one of a processor (1601), a transceiver (1602), and a memory (1603). At least one of the processor (1601), the transceiver (1602), and the memory (1603) of the station may operate according to the method(s) described in the embodiments described above in FIG. 1 to 15. However, the components of the station are not limited to the examples described above. For example, the station may include more components or fewer components than the components described above. In addition, the processor (1601), the transceiver (1602), and the memory (1603) may be implemented in the form of at least one chip.

[0282] The transceiver (1602) is a collective term for a receiver and a transmitter, and can transmit and receive signals with a station or other network entity through the transceiver (1602). At this time, the signal being transmitted and received may include at least one of control information and data. To this end, the transceiver (1602) may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that low-noise amplifies the received signal and down-converts the frequency. This is merely one embodiment of the transceiver (1602), and the components of the transceiver (1602) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1602) can receive a signal and output it to a processor (1601), and transmit the signal output from the processor (1601) to another network entity through a network.

[0283] The memory (1603) can store programs and data necessary for the operation of a station according to at least one of the embodiments of FIGS. 1 to 15. Additionally, the memory (03) can store control information and / or data included in signals obtained from the station. The memory (1603) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD.

[0284] The processor (1601) can control a series of processes so that the station can operate according to at least one of the embodiments of FIGS. 1 to 15. The processor (1601) may include at least one processor.

[0285] FIG. 17 is a drawing showing an example of a configuration of an access point according to one embodiment of the present disclosure.

[0286] In FIG. 17, the access point may include at least one of a processor (1701), a transceiver (1702), and a memory (1703). At least one of the processor (1701), the transceiver (1702), and the memory (1703) of the access point may be operated according to the method(s) described in the embodiments described above in FIG. 1 to 15. However, the components of the access point are not limited to the examples described above. For example, the access point may include more components or fewer components than the components described above. In addition, the processor (1701), the transceiver (1702), and the memory (1703) may be implemented in the form of at least one chip.

[0287] The transceiver (1702) is a collective term for a receiver and a transmitter, and can transmit and receive signals with a station or other network entity through the transceiver (1702). At this time, the signal being transmitted and received may include at least one of control information and data. To this end, the transceiver (1702) may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that low-noise amplifies the received signal and down-converts the frequency. This is merely one embodiment of the transceiver (1702), and the components of the transceiver (1702) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1702) can receive a signal and output it to a processor (1701), and transmit the signal output from the processor (1701) to another network entity through a network.

[0288] The memory (1703) can store programs and data necessary for the operation of an access point according to at least one of the embodiments of FIGS. 1 to 15. Additionally, the memory (1703) can store control information and / or data included in a signal obtained from the access point. The memory (1703) may be composed of a storage medium or a combination of storage media such as ROM, RAM, a hard disk, a CD-ROM, and a DVD.

[0289] The processor (1701) can control a series of processes so that the access point can operate according to at least one of the embodiments of FIGS. 1 to 15. The processor (1701) may include at least one processor.

[0290] A method for exchanging a first frame (Dynamic SCS Request) and a second frame (Dynamic SCS Response) between an STA and an AP according to one embodiment of the present disclosure may include the step of the STA providing information about one or more QoS profiles constituting an SCS stream, including one or more sets of QoS parameters, through the first frame, and the step of the AP providing information about whether to accept the said SCS stream and each QoS profile through the second frame.

[0291] In one embodiment, the first frame may include one or more QoS profiles distinguished by different SCSIDs. In one embodiment, the first frame may include one or more QoS profiles distinguished by different identifiers having the same SCSID.

[0292] In one embodiment, the second frame may include information indicating acceptance for the entire SCS stream. In one embodiment, the second frame may include information indicating acceptance for each QoS profile.

[0293] In one embodiment, the first frame may include priority or importance among the QoS profiles. In one embodiment, the first frame may include time-related information related to the QoS profile. The application time-related information may include at least one of the utilization time information of the QoS profile or time information regarding the weight of the corresponding QoS profile among a plurality of QoS profiles.

[0294] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0295] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. In a method performed by a station in a wireless local area network (WLAN) communication system, A step of transmitting an SCS request frame to an access point to establish an SCS (stream classification service) stream; and The method includes the step of receiving an SCS response frame for establishing the SCS stream from the access point. A method characterized in that the above SCS request frame includes information on a plurality of QoS (quality of service) profiles that can be dynamically applied to the above SCS stream.

2. In paragraph 1, the plurality of QoS profiles included in the SCS request frame are, A method characterized by being distinguished by different SCSIDs (stream classification service identifiers) or different Profile IDs (identifiers).

3. In the case of Paragraph 1, where the plurality of QoS profiles included in the SCS request frame are distinguished by different SCSIDs, A method characterized by being included in SCS descriptor elements containing the above different SCSIDs.

4. In the case of Paragraph 1, where the plurality of QoS profiles included in the SCS request frame are distinguished by different Profile IDs (identifiers), A method characterized by being included in SCS descriptor elements distinguished by the above different Profile IDs or QoS Characteristics elements distinguished by the above different Profile IDs.

5. In paragraph 1, the above SCS response frame is, A method characterized by including information indicating acceptance of at least one of the plurality of QoS profiles.

6. In paragraph 1, the above SCS response frame is, When the plurality of QoS profiles included in the above SCS request frame are distinguished by different SCSIDs, the frame includes information indicating whether to accept the QoS profile corresponding to each SCSID, and A method characterized by including information indicating acceptance of all of the plurality of QoS profiles when the plurality of QoS profiles included in the above SCS request frame are distinguished by different Profile IDs.

7. In the case of paragraph 1, where the plurality of QoS profiles included in the SCS request frame are distinguished by different Profile IDs, and the SCS response frame includes information indicating whether to accept some of the plurality of QoS profiles, The above SCS response frame includes at least one Profile ID corresponding to at least one QoS profile for which acceptance is indicated, and information indicating acceptance for a portion of the plurality of QoS profiles is A method characterized by including at least one of information indicating partial approval, partial rejection, and proposed changes upon partial rejection.

8. In paragraph 7, where the SCS response frame includes information indicating proposed changes upon partial rejection for some of the plurality of QoS profiles, A method characterized in that information regarding proposed changes when some of the above multiple QoS profiles are rejected is included in the SCS Descriptor element of the above SCS response frame.

9. In paragraph 1, the above SCS request frame is, A method characterized by including at least one of priority information or time information for the plurality of QoS profiles.

10. In paragraph 9, the above priority information includes priority information indicating that the relevant QoS profile is an essential profile or mandatory profile, and A method characterized by rejecting the SCS request frame when the corresponding QoS profile corresponding to the above-mentioned essential profile is not accepted.

11. A method according to claim 9, wherein the time information comprises at least one of periodic application information of the corresponding QoS profile or relative application time ratio information of the corresponding QoS profile among the plurality of QoS profiles.

12. A method according to claim 9, characterized in that at least one of the priority information or time information for the plurality of QoS profiles is included in at least one of the SCS Descriptor element or QoS Characteristics element of the SCS request frame.

13. In a method performed by an access point in a wireless local area network (WLAN) communication system, A step of receiving an SCS request frame from a station to establish an SCS stream; and The method includes the step of transmitting an SCS response frame to the above station to establish the SCS stream; A method characterized in that the above SCS request frame includes information on a plurality of QoS profiles that can be dynamically applied to the above SCS stream.

14. In a station of a wireless local area network (WLAN) communication system, Transmitter / receiver; One or more processors including processing circuitry; and It includes memory for storing instructions, and when the instructions are executed individually or collectively by one or more processors, the station: Send an SCS request frame to the access point to establish an SCS (stream classification service) stream, and Causing to receive an SCS response frame for establishing the SCS stream from the above access point, and A station characterized in that the above SCS request frame includes information on a plurality of QoS (quality of service) profiles that can be dynamically applied to the above SCS stream.

15. In an access point in a wireless local area network (WLAN) communication system, Transmitter / receiver; One or more processors including processing circuitry; and It includes memory for storing instructions, and when the instructions are executed individually or collectively by the one or more processors, the access point: Receive an SCS request frame from the station to establish an SCS stream, and Causing the above station to transmit an SCS response frame to establish the SCS stream, and An access point characterized in that the above SCS request frame includes information on a plurality of QoS profiles that can be dynamically applied to the above SCS stream.

Images