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

Abstract

The present disclosure relates to a method and an apparatus for changing at least one QoS profile configured through stream classification service (SCS) negotiation in a wireless local area network (WLAN) communication system. The method of an access point in a wireless local area network (WLAN) communication system, according to one embodiment of the present disclosure, comprises the steps of: receiving, from a station, a stream classification service (SCS) request frame for configuring an SCS stream; transmitting, to the station, an SCS response frame for configuring the SCS stream; and transmitting, to the station, a first frame for notifying of a change in at least one quality of service (QoS) parameter set configured for 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] A Wireless Local Area Network (WLAN), also known by the alias Wi-Fi, allows 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 the 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 changing a negotiated profile when an access point (AP) cannot support some QoS profiles when generating 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 an access point performing Wi-Fi communication according to one embodiment of the present disclosure comprises: receiving an SCS request frame for setting up a stream classification service (SCS) stream from a station; and transmitting an SCS response frame for setting up the SCS stream to the station; and transmitting a first frame to the station for notifying a change to at least one set of QoS parameters set for the SCS stream.

[0011] 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; and receiving a first frame from the access point to notify a change to at least one set of QoS parameters set for the SCS stream.

[0012] 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 setting up a stream classification service (SCS) stream from a station, and to transmit an SCS response frame for setting up the SCS stream to the station, and to transmit a first frame for notifying the station of a change to at least one set of QoS parameters set for the SCS stream.

[0013] A station performing Wi-Fi communication according to one embodiment of the present disclosure comprises: a transceiver; and at least one processor; wherein the at least one processor is configured to transmit an SCS request frame for setting up a stream classification service (SCS) stream to an access point, and to receive an SCS response frame for setting up the SCS stream from the access point, and to receive a first frame from the access point for notifying a change to at least one set of QoS parameters set for 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, an electronic device can efficiently utilize wireless resources and improve the service user experience by generating multiple quality of service (QoS) profiles for a single SCS stream through stream classification service (SCS) negotiation with an access point, and then allowing the AP to change the negotiated QoS profiles in consideration of the AP environment.

[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] FIG. 3a illustrates the operation of an AP in a Wi-Fi communication system terminating an SCS setting using an Unsolicited SCS Response frame.

[0021] FIG. 3b illustrates the operation of an AP according to one embodiment of the present disclosure updating a QoS profile using an SCS Change Notice frame.

[0022] FIGS. 4a, FIGS. 4b and FIGS. 4c are drawings illustrating an example of an SCS Change Notice frame that notifies of a change, suspension, or resumption of application of some profiles of a set SCS according to one embodiment of the present disclosure.

[0023] FIGS. 5a and 5b are drawings illustrating an example of an SCS Change Notice frame that notifies a change, suspension, or resumption of application of a plurality of QoS profiles included in a plurality of SCS descriptor elements having different SCSIDs, according to one embodiment of the present disclosure.

[0024] FIGS. 6a, FIG. 6b, and FIG. 6c are drawings illustrating an example of an SCS Change Notice frame that transmits change information for a plurality of QoS profiles having the same SCSID and different profile IDs, according to an embodiment of the present disclosure.

[0025] FIGS. 7a, FIGS. 7b and FIG. 7c are drawings illustrating an example of an Unsolicited SCS response frame that transmits change information for a plurality of QoS profiles according to one embodiment of the present disclosure.

[0026] FIG. 8 is a diagram illustrating an example of a QoS Characteristics element that, according to one embodiment of the present disclosure, together informs a set of QoS parameters that can be provided by another link when transmitting change information for a plurality of QoS profiles.

[0027] FIG. 9 is a diagram illustrating an example of an Unsolicited SCS response frame that, according to one embodiment of the present disclosure, together informs a set of QoS parameters that can be provided by another link when transmitting change information for a plurality of QoS profiles.

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

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

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

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

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

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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).

[0037] 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).

[0038] 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.

[0039] 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.

[0040] 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).

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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).

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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).

[0054] 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.

[0055] 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.

[0056] 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.

[0057] 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).

[0058] 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).

[0059] 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).

[0060] 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.

[0061] 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.

[0062] 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).

[0063] 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.

[0064] 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).

[0065] stream classification service (SCS)

[0066] 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.

[0067] 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.

[0068] 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.

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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).

[0075] 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 indicating a Robust AV Streaming frame (e.g., “19”), 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.

[0076] 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, "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, for example, to "0".

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

[0078] 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.

[0079] 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.

[0080] 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).

[0081] The Category field (220) and Robust Action field (225) may be described as described in FIG. 2a for the Category field (200) and Robust Action field (205), and for 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.

[0082] 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.

[0083] 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.

[0084] 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.

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

[0086] 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).

[0087] 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.

[0088] 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).

[0089] 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.

[0090] 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".

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

[0098] 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.

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

[0103] In one embodiment, multiple QoS profiles may be set through the SCS negotiation procedure described above. That is, multiple QoS profiles may be set for a single SCS stream through an SCS negotiation procedure for dynamically applying QoS profiles to an SCS stream.

[0104] In one embodiment, during the SCS negotiation, the STA may request the AP to set up by including information on multiple QoS profiles in the SCS request frame. The information on multiple QoS profiles included in the SCS request frame may be distinguished based on at least one of the SCS Descriptor element including different SCS IDs, different profile IDs, and QoS Characteristics element including different profiled IDs included in the SCS request frame.

[0105] Even if SCS negotiation for dynamic QoS profile operation is completed as described above, support for the granted QoS profile may become difficult depending on changes in the AP environment (e.g., association with SATs or load).

[0106] FIG. 3a illustrates the operation of an AP terminating an SCS setup using an Unsolicited SCS Response frame.

[0107] Referring to Fig. 3a, if it is difficult for the AP to support the previously allowed set of QoS parameters due to the AP environment, the AP can terminate the configuration of the SCS stream by sending an Unsolicited SCS Response frame to the STA. Subsequently, the AP and the STA can perform a new SCS negotiation procedure. That is, the STA can send an SCS request frame for a new SCS addition for SCS negotiation. In this case, the AP can send an SCS Response frame containing information indicating whether the QoS parameter sets included in the SCS request frame are approved (e.g., SUCCESS or REJECTED_WITH_SUGGESTED_CHANGES). In this case, since the configuration of the SCS stream was previously terminated by the AP's Unsolicited SCS Response frame, the STA does not know information regarding the appropriate set of QoS parameters to use for the new SCS negotiation.

[0108] FIG. 3b illustrates the operation of an AP according to one embodiment of the present disclosure updating a QoS profile using an SCS Change Notice frame.

[0109] In one embodiment, if it is difficult to support a pre-allowed set of QoS parameters due to AP environments, the AP may perform a profile-level operation by sending an SCS Change Notice frame to the STA. The profile-level operation may include an operation to notify of a change, suspension, or resumption of application of QoS profiles (and / or sets of QoS parameters) to be applied to a configured SCS stream.

[0110] In one embodiment, the STA may transmit an SCS Request frame for profile update when the QoS profile (and / or, QoS parameter set) is changed, or when the changed QoS profile (and / or, QoS parameter set) is inappropriate. In one embodiment, the AP may transmit an SCS Response frame for the SCS Request frame to the STA.

[0111] FIGS. 4a, FIGS. 4b and FIGS. 4c are drawings illustrating an example of an SCS Change Notice frame that notifies of a change, suspension, or resumption of application of some profiles of a set SCS according to one embodiment of the present disclosure.

[0112] FIG. 4a illustrates an example of an SCS status duple (430) that may be included in an SCS Change Notice frame (400), an Instruction field (415), and an SCS Status List field (417) of the SCS Change Notice frame (400), according to one embodiment of the present disclosure.

[0113] Referring to (a) of FIG. 4a, the SCS Change Notice frame (400) may include at least one of a Category field (410), a Robust Action field (413), a Dialog Token field, an Instruction field (415), an SCS status list field (417), and an SCS Descriptor List field (419). The Category field (410) may include a value (e.g., "19") representing a frame of Robust AV Streaming.

[0114] In one embodiment, the value of the Robust Action field (413), which is the Action Field of the SCS Change Notice frame (400), may be used to indicate that the SCS Change Notice frame (400) is an SCS Change Notice frame that notifies that the parameter set applicable to some of the QoS profiles for the SCS streams set by the AP and STA has been changed, or that the application has been discontinued or resumed. FIG. 4c(a) illustrates a value that may be included in the Robust Action field (413), and to indicate that it is an SCS Change Notice frame (400), the Robust Action field (413) may include a value (e.g., "8") signifying an SCS Change Notice.

[0115] Figure 4a(b) illustrates information elements that may be included in the Instruction field (415). The AP can use the information included in the Instruction field (415) to transmit a request for a subsequent operation to the STA.

[0116] Referring to Fig. 4a (b), the Instruction field (415) may include at least one of the Request Required field (421) and the Delay Period field (423).

[0117] The Request Required field (421) may indicate the transmission of a subsequent Request frame by the STA that received the SCS Change Notice frame (400). In one embodiment, the Request Required field (421) may indicate the transmission of an SCS Request frame by the STA that received the SCS Change Notice frame (400) to delete at least one profile, excluding one of the profiles having the same QoS parameter set indicated in the SCS Descriptor List field (419). In one embodiment, the Request Required field (421) may indicate the transmission of an SCS Request frame by the STA that received the SCS Change Notice frame (400) to request a change in the QoS parameter set for profiles including the profile that has been changed or discontinued from application. In one embodiment, in this case, the QoS parameter set to be changed may include a parameter set to which a more relaxed standard than that of the parameters provided by the AP is applied.

[0118] The above Delay Period field (423) may indicate the delay time until the transmission of a subsequent Request frame by the STA that received the SCS Change Notice frame (400). That is, the STA that received the SCS Change Notice frame (400) may transmit an SCS Request frame after the delay time included in the Delay Period field (423). For example, the information regarding the delay time included in the Delay Period field (423) may be expressed in units of TBTT (target beacon transmission time) or as a multiple of a specific time unit.

[0119] Referring to (a) of FIG. 4a, the SCS Status List field (417) may include multiple SCS Status duples.

[0120] FIG. 4a(c) illustrates an example of the SCS Status duples. Referring to FIG. 4a(c), the SCS Status duple (430) may include at least one of the SCSID field (431) and the Status field (433).

[0121] In one embodiment, the SCSID field (431) may include the SCSID value of an SCS descriptor element that contains information on a QoS profile, which indicates whether to change, stop, or resume the application of profiles in the corresponding Status field (433) among the different SCSIDs, when the SCS request frame received by the AP contains multiple SCS descriptor elements of different SCSIDs.

[0122] In one embodiment, the Status field (433) may indicate whether the QoS profiles set for the SCS stream have been changed, suspended, or resumed. That is, the Status field (433) may include at least one of information (and / or code) notifying a change in the set QoS profiles (e.g., "SCS_CHANGED_INSUFFICIENT_QOS"), information notifying a suspension of SCS application (e.g., "SCS_SUSPENDED_INSUFFICIENT_QOS"), and information notifying the reapplication of the suspended SCS (e.g., "SCS_RESUMED").

[0123] FIG. 4b illustrates an SCS Descriptor element (440) that may be included in the SCS Descriptor List field (419) of the SCS Change Notice frame (400) and a Subelement (450) that may be included in the Optional Subelements field (445) of the SCS Descriptor element (440).

[0124] Referring to (a) of FIG. 4a, the SCS descriptor element (440) may include at least one of the SCSID field (441), the Request Type field (443), and the Optional Subelements field (445).

[0125] The Request Type field (443) may indicate whether to change, suspend, or resume the application of QoS profiles set for the SCS stream. That is, the Request Type field (443) may include at least one of information notifying a change in the set QoS profiles (e.g., "Change"), information notifying a suspension of SCS application (e.g., "Suspend"), or information notifying the reapplication of the suspended SCS (e.g., "Resume"). In one embodiment, the Status field (433) of the SCS Status duple (430) may include information indicating a change (e.g., "SCS_CHANGED_INSUFFICIENT_QOS").

[0126] Referring to FIG. 4b(b), the Subelement (450) may include at least one of a Subelement ID field (451), a Length field, and an Application Time field (453). The Subelement ID field (451) may include a value indicating the type of data that may be included in the Subelement (450), and FIG. 4c(b) illustrates an example of a value that may be included in the Subelement ID field (451). The Subelement ID field (451) may include a value (e.g., "220") indicating that the Application Time should be included in the data field of the Subelement (450).

[0127] The above Application Time field (453) may include time information regarding the time when a change in the profile, suspension of application, or resumption of application is applied as indicated in the SCS Status duple (430) or SCS Descriptor element (440) above.

[0128] FIGS. 5a and 5b are drawings illustrating an example of an SCS Change Notice frame that notifies a change, suspension, or resumption of application of a plurality of QoS profiles included in a plurality of SCS descriptor elements having different SCSIDs, according to one embodiment of the present disclosure.

[0129] Referring to Figures 5a and 5b, the SCS Change Notice frame can notify of changes, suspension or resumption of application for QoS profiles by SCSID, and transmit a set of QoS parameters.

[0130] FIG. 5a illustrates an example of SCS status duples (520 and 530) that may be included in an SCS Change Notice frame (500) and an SCS Status List of the SCS Change Notice frame (500), according to one embodiment of the present disclosure.

[0131] Referring to (a) of FIG. 5a, the SCS Change Notice frame (500) may include at least one of a Category field (510), a Robust Action field (513), a Dialog Token field, an Instruction field (515), an SCS status list field (517), and an SCS Descriptor List field (519). The description of the Category field (510), Robust Action field (513), and Instruction field (515) may be applied to the description of the Category field (410), Robust Action field (413), and Instruction field (415) described in (a) of FIG. 4a.

[0132] FIG. 5a(b) illustrates SCS status duples (520 and 530) included in the SCS Status List (517) of the SCS Change Notice frame (500). The plurality of SCS Status duples (520 and 530) may include information notifying the change, suspension, or resumption of application for each QoS profile when the SCS request frame received by the AP includes multiple QoS profiles included in multiple SCS descriptor elements with different SCSIDs.

[0133] Referring to FIG. 5a(b), SCS status duples (520 and 530) may include at least one of an SCSID field (521, 531) and a Status field (523, 533). The SCSID field (521, 531) may include different SCSIDs (e.g., "X" or "Y").

[0134] The above Status fields (523, 533) may include information indicating a change, suspension, or resumption of application for each SCSID included in the corresponding SCSID fields (521, 531). The description of the above Status fields (523, 533) may be applied to the description of the Status field (433) of (c) in FIG. 4a.

[0135] FIG. 5b shows an example of a plurality of SCS descriptor elements (540, 550) that may be included in the SCS Descriptor List (519).

[0136] Referring to FIG. 5b, the SCS descriptor element may include at least one of the SCSID field, the Request Type field, and the QoS Characteristics element field.

[0137] The SCS descriptor element (540) and SCS descriptor element (550) illustrated in FIG. 5b are SCS Descriptor elements corresponding to requested QoS profiles based on different SCSIDs, and each SCSID field (541, 551) may include the value of the corresponding different SCSID (e.g., "X" or "Y").

[0138] In one embodiment, when the Status field (523) of the SCS Status duple (520) with SCSID "X" indicates a change ("CHANGED"), the QoS Characteristics element (545) included in the SCS descriptor element (540) with SCSID "X" can convey a changed QoS parameter set.

[0139] In one embodiment, when the Status field (533) of the SCS Status duple (530) with SCSID "Y" indicates suspension ("SUSPENDED"), the QoS Characteristics element (555) included in the SCS descriptor element (550) with SCSID "Y" can convey a set of QoS parameters that the AP can provide.

[0140] In one embodiment, when a common QoS parameter set is transmitted to all SCSIDs without distinguishing by SCSID, the common parameter set may be transmitted by including an SCS Descriptor element where SCSID=0 instead of including an SCS Descriptor Element for each SCSID.

[0141] FIGS. 6a, FIG. 6b, and FIG. 6c are drawings illustrating an example of an SCS Change Notice frame that transmits change information for a plurality of QoS profiles having the same SCSID and different profile IDs, according to an embodiment of the present disclosure.

[0142] Referring to FIGS. 6a and FIG. 6b, the SCS Change Notice frame can notify of changes, suspension, or resumption of application for QoS profiles distinguished by profile IDs within the same SCSID, and can transmit a set of QoS parameters.

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

[0144] Referring to FIG. 6a (a), the SCS Change Notice frame (600) may include at least one of a Category field (610), a Robust Action field (613), a Dialog Token field, an Instruction field (615), an SCS status list field (617), and an SCS Descriptor List field (619). The description of the Category field (610), Robust Action field (613), and Instruction field (615) may be applied to the description of the Category field (410), Robust Action field (413), and Instruction field (415) shown in FIG. 4a (a).

[0145] Figure 6a (b) illustrates SCS status duples (620) included in the SCS Status List (617) of the SCS Change Notice frame (600).

[0146] Referring to FIG. 6a(b), SCS status duples (620) may include at least one of an SCSID field (631) and a Status field (633). The SCSID field (631) may include the same SCSID value (e.g., "X") when the SCS request frame received by the AP contains SCS descriptor elements with the same SCSID. In one embodiment, when the SCS request frame received by the AP contains SCS descriptor elements with the same SCSID and transmits change information for QoS profiles distinguished by Profile ID in the SCS Change Notice frame (600), the Status field (633) may include information indicating a change (e.g., "CHANGED").

[0147] Figure 6b (a) shows an example of a plurality of SCS descriptor elements (640, 650) that may be included in the SCS Descriptor List (619).

[0148] Referring to (a) of FIG. 6b, the SCS descriptor element may include at least one of the SCSID field, the Request Type field, the QoS Characteristics element field, and the Optional Subelements field.

[0149] The SCS descriptor element (640) and SCS descriptor element (650) illustrated in FIG. 6b (a) are SCS Descriptor elements corresponding to requested QoS profiles that have the same SCSID and are distinguished by profile ID, and each SCSID field (641, 651) may contain a value of the corresponding same SCSID (e.g., "X").

[0150] The Request Type fields (643, 653) in FIG. 6b may indicate whether to change, suspend, or resume the application of QoS profiles set for an SCS stream. FIG. 6c shows an example of information that may be included in the Request Type fields (643, 653). That is, the Request Type fields (643, 653) may include at least one of information notifying a change in the set QoS profiles (e.g., "Change"), information notifying a suspension of SCS application (e.g., "Suspend"), and information notifying the reapplication of the suspended SCS (e.g., "Resume").

[0151] Fig. 6b(b) illustrates a Subelement (660) that can be included in the Optional Subelements fields (645, 665).

[0152] Referring to FIG. 6b (b), a Subelement (660) may include at least one of a Subelement ID field (661), a Length field (663), and a Profile ID field (665). The Subelement ID field (661) may include a value indicating the type of data that may be included in the Subelement (660). In one embodiment, the Subelement ID field (661) may include a value (e.g., "0") indicating that the data field of the Subelement (660) includes a Profile ID. In one embodiment, the Profile ID field (665) may include a list of profiles to which the change, suspension, or resumption status indicated in the Request Type fields (643, 653) is applied.

[0153] In one embodiment, the Profile ID field (665) may include a list of profiles to which the QoS parameter set indicated in the QoS Characteristics Element fields (644, 654) is to be applied. The length ("L") of the Profile ID field (665) may be equal to the number of QoS parameter sets to be changed that may be included in the Profile ID field (665).

[0154] In one embodiment, the Length field (663) may include a length value (e.g., "L") equal to the number of changeable QoS parameter sets that may be included in the Profile ID field (665).

[0155] FIGS. 7a, FIGS. 7b and FIG. 7c are drawings illustrating an example of an Unsolicited SCS response frame that transmits change information for a plurality of QoS profiles according to one embodiment of the present disclosure.

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

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

[0158] In one embodiment, to indicate that the SCS Response frame (700) 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 (713), which is an Action Field, may include a value (e.g., "7") signifying a D(dynamic)-SCS Response. Alternatively, in one embodiment, the Robust Action field (713) of the SCS Response frame (700) may include a value (e.g., "1") signifying an SCS Response.

[0159] Referring to (a) of FIG. 7a, the SCS Status List field (717) may contain one or more SCS Status duples.

[0160] FIG. 7a(b) illustrates an example of an SCS Status duple that may be included in the SCS Status List field (717). Referring to FIG. 7a(b), the SCS Status duple (720) may include at least one of the SCSID field (721) and the Status field (723).

[0161] In one embodiment, the SCSID field (721) may include the SCSID value of an SCS descriptor element that contains information on a QoS profile, which indicates whether to change, stop, or resume the application of profiles in the corresponding Status field (723) among the different SCSIDs, when the SCS request frame received by the AP contains multiple SCS descriptor elements of different SCSIDs.

[0162] In one embodiment, the SCSID field (721) may include the same SCSID value (e.g., "X") when the SCS request frame received by the AP contains SCS descriptor elements with the same SCSID.

[0163] In one embodiment, the Status field (723) may indicate whether the QoS profiles set for the SCS stream have been changed, suspended, or resumed. That is, the Status field (723) may include at least one of information (and / or code) notifying a change in the set QoS profiles (e.g., "SCS_CHANGED_INSUFFICIENT_QOS"), information notifying a suspension of SCS application (e.g., "SCS_SUSPENDED_INSUFFICIENT_QOS"), and information notifying the re-application of the suspended SCS (e.g., "SCS_RESUMED").

[0164] In one embodiment, when an SCS request frame received by an AP contains SCS descriptor elements with the same SCSID and QoS profiles distinguished by a Profile ID, and when change information for the QoS profiles distinguished by a Profile ID is transmitted in the SCS Response frame (700), the Status field (723) may include information indicating a change (e.g., "SCS_CHANGED_INSUFFICIENT_QOS").

[0165] FIG. 7b illustrates an SCS Descriptor element (730) that may be included in the SCS Descriptor List field (719) of the SCS Response frame (700) and a Subelement (740) that may be included in the Optional Subelements field (737) of the SCS Descriptor element (730).

[0166] Referring to (a) of FIG. 7b, the SCS descriptor element (730) may include at least one of the SCSID field (731), the Request Type field (733), the QoS Characteristics element field (735), and the Optional Subelements field (737).

[0167] In one embodiment, when the SCS request frame received by the AP contains multiple SCS descriptor elements of different SCSIDs, the SCSID field (731) may be configured as each SCSID field (541, 551) described in FIG. 5b. In one embodiment, when the SCS request frame received by the AP contains SCS descriptor elements with the same SCSID and QoS profiles distinguished by Profile ID, the SCSID field (731) may be configured as the SCSID (641, 651) illustrated in FIG. 6b.

[0168] The Request Type field (733) may indicate whether to change, suspend, or resume the application of QoS profiles set for the SCS stream. That is, the Request Type field (733) may include at least one of information notifying a change in the set QoS profiles (e.g., "Change"), information notifying a suspension of SCS application (e.g., "Suspend"), or information notifying the reapplication of the suspended SCS (e.g., "Resume"). In one embodiment, the Status field (723) of the SCS Status duple (720) may include information indicating a change (e.g., "SCS_CHANGED_INSUFFICIENT_QOS").

[0169] Referring to FIG. 7b(b), the Subelement (740) may include at least one of a Subelement ID field (741), a Length field, and an Instruction field (743). The Subelement ID field (741) may include a value indicating the type of data that may be included in the Subelement (740), and FIG. 7c illustrates an example of a value that may be included in the Subelement ID field (741). The Subelement ID field (741) may include a value (e.g., "3") indicating that Instruction information will be included in the data field of the Subelement (740).

[0170] For the above Instruction field (743), the description of the Instruction field (415) shown in (a) and (b) of FIG. 4a may be applied.

[0171] FIG. 8 is a diagram illustrating an example of a QoS Characteristics element that, according to one embodiment of the present disclosure, together informs a set of QoS parameters that can be provided by another link when transmitting change information for a plurality of QoS profiles.

[0172] FIG. 8 illustrates an example of a QoS Characteristics element (800) and a Control Info field (810) included in the QoS Characteristics element (800) according to one embodiment of the present disclosure.

[0173] Referring to FIG. 8, the QoS characteristic element (800) may include a Control Info field (810), and if the Link ID field (830) of the Control Info field (810) includes a Link ID for a link different from the current link, the QoS characteristic element (800) may include a set of QoS parameters that can be provided by the other link. That is, when the AP notifies a change in the SCS set between the multi-link supporting AP and the STA, it may include a set of QoS parameters that can be provided by the other link. In this case, if the STA includes a QoS Char. Element that includes a link ID different from the link that received the frame, it may interpret it as a set of QoS parameters that the AP can provide by the other link.

[0174] The QoS characteristic element (800) shown in Fig. 8 may be included in the SCS Change Notice frame or SCS Response frame.

[0175] FIG. 9 is a diagram illustrating an example of an Unsolicited SCS response frame that, according to one embodiment of the present disclosure, together informs a set of QoS parameters that can be provided by another link when transmitting change information for a plurality of QoS profiles.

[0176] FIG. 9 illustrates an example of an SCS Descriptor element (920) that may be included in an SCS response frame (900) and an SCS Descriptor List field (917) of the response frame (900), according to one embodiment of the present disclosure.

[0177] Referring to FIG. 9(a), the SCS response frame (900) may include at least one of a Category field (910), a Robust Action field (913), a Dialog Token field, an SCS status list field (915), and an SCS Descriptor List field (917). The description of the Category field (910), the Robust Action field (913), and the SCS status list field (915) may be applied to the description of the Category field (710), the Robust Action field (713), and the SCS status list field (717) described in FIG. 7a.

[0178] The above SCS Descriptor List field (917) may include one or more SCS Descriptor elements.

[0179] FIG. 9(b) illustrates an example of an SCS Descriptor element (920) that may be included in an SCS Descriptor List field (917). Referring to FIG. 9(b), the SCS Descriptor element (920) may include a QoS Characteristics element field (930). The description of the QoS Characteristics element field (930) may be the same as the description of the QoS Characteristics element field (800) described in FIG. 8. That is, the QoS characteristic element (930) may include a Control Info field, and if the Link ID field of the Control Info field includes a Link ID for a link different from the current link, the QoS characteristic element may include a set of QoS parameters available from the other link.

[0180] In one embodiment, in this case, a QoS characteristic element including a set of QoS parameters available from the other link may be included in the QoS Characteristics element field (930) included in the SCS Descriptor element (920). In one embodiment, a QoS characteristic element including a set of QoS parameters available from the other link may be included in the QoS Characteristics element field of a separate SCS Descriptor element different from the existing SCS Descriptor element (920) included in the SCS Descriptor List (917) of the SCS response frame (900). That is, in this case, the separate SCS Descriptor element may include a separate SCS Descriptor element different from the SCS Descriptor element (920) which includes a Link ID field indicating a Link ID for the other link.

[0181] 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 through 9 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.

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

[0183] In step 1000, the access point can receive an SCS request frame from the station to set up a stream classification service (SCS) stream.

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

[0185] In step 1020, the access point may transmit a first frame to the station to notify a change to at least one set of QoS parameters set for the SCS stream.

[0186] In one embodiment, the access point may receive an SCS request frame from the station requesting a change to the changed QoS parameter set in response to the first frame.

[0187] In one embodiment, the first frame may include instruction information for the SCS request frame.

[0188] In one embodiment, the instruction information instructs to transmit the SCS request frame requesting a change to the changed QoS parameter set, or the instruction information may include time information regarding the time to transmit the SCS request frame.

[0189] In one embodiment, the first frame may include information indicating at least one of changing, stopping, or resuming the application of at least one set of QoS parameters set for the SCS stream.

[0190] In one embodiment, information indicating at least one of the change, suspension of application, or resumption of application may be included in at least one of the SCS Status List field or the SCS Descriptor List field of the first frame.

[0191] In one embodiment, the first frame may include information regarding the timing of when a change, suspension of application, or resumption of application of at least one set of QoS parameters set for the SCS stream is applied.

[0192] In one embodiment, when a plurality of QoS parameter sets are determined for the set SCS stream, information indicating at least one of changing, stopping, or resuming the application of the plurality of QoS parameter sets for the SCS stream can be distinguished based on at least one of an SCSID or a Profile ID associated with the plurality of QoS parameter sets.

[0193] In one embodiment, the first frame may include an SCS response frame.

[0194] In one embodiment, the first frame may include information about at least one set of QoS parameters that can be provided by a link other than the link currently in use.

[0195] In one embodiment, information about the other link may be included in the Control field of the QoS Characteristics element included in the first SCS Descriptor element included in the first frame. In one embodiment, information about at least one set of QoS parameters available from the other link may be included in the first SCS Descriptor element or the second SCS Descriptor element included in the first frame.

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

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

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

[0199] In step 1120, the station may receive a first frame from the access point to notify of a change to at least one set of QoS parameters set for the SCS stream.

[0200] In one embodiment, the station may send an SCS request frame to the access point requesting a change to the changed QoS parameter set in response to the first frame.

[0201] In one embodiment, the first frame may include instruction information for the SCS request frame.

[0202] In one embodiment, the instruction information instructs to transmit the SCS request frame requesting a change to the changed QoS parameter set, or the instruction information may include time information regarding the time to transmit the SCS request frame.

[0203] In one embodiment, the first frame may include information indicating at least one of changing, stopping, or resuming the application of at least one set of QoS parameters set for the SCS stream.

[0204] In one embodiment, information indicating at least one of the change, suspension of application, or resumption of application may be included in at least one of the SCS Status List field or the SCS Descriptor List field of the first frame.

[0205] In one embodiment, the first frame may include information regarding the timing of when a change, suspension of application, or resumption of application of at least one set of QoS parameters set for the SCS stream is applied.

[0206] In one embodiment, when a plurality of QoS parameter sets are determined for the set SCS stream, information indicating at least one of changing, stopping, or resuming the application of the plurality of QoS parameter sets for the SCS stream can be distinguished based on at least one of an SCSID or a Profile ID associated with the plurality of QoS parameter sets.

[0207] In one embodiment, the first frame may include an SCS response frame.

[0208] In one embodiment, the first frame may include information about at least one set of QoS parameters that can be provided by a link other than the link currently in use.

[0209] In one embodiment, information about the other link may be included in the Control field of the QoS Characteristics element included in the first SCS Descriptor element included in the first frame. In one embodiment, information about at least one set of QoS parameters available from the other link may be included in the first SCS Descriptor element or the second SCS Descriptor element included in the first frame.

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

[0211] In FIG. 12, the access point may include at least one of a processor (1201), a transceiver (1202), and a memory (1203). At least one of the processor (1201), the transceiver (1202), and the memory (1203) of the access point may be operated according to the method(s) described in the embodiments described above in FIG. 1 to 11. 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 (1201), the transceiver (1202), and the memory (1203) may be implemented in the form of at least one chip.

[0212] The transceiver (1202) 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 (1202). At this time, the signal being transmitted and received may include at least one of control information and data. To this end, the transceiver (1202) 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 (1202), and the components of the transceiver (1202) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1202) can receive a signal and output it to a processor (1201), and transmit the signal output from the processor (1201) to another network entity through a network.

[0213] The memory (1203) 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 11. Additionally, the memory (1203) can store control information and / or data included in a signal obtained from the access point. The memory (1203) 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.

[0214] The processor (1201) 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 11. The processor (1201) may include at least one processor.

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

[0216] In FIG. 13, the station may include at least one of a processor (1301), a transceiver (1302), and a memory (1303). At least one of the processor (1301), the transceiver (1302), and the memory (1303) of the station may operate according to the method(s) described in the aforementioned embodiments of FIG. 1 to 11. 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. Furthermore, the processor (1301), the transceiver (1302), and the memory (1303) may be implemented in the form of at least one chip.

[0217] The transceiver (1302) 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 (1302). At this time, the signal being transmitted and received may include at least one of control information and data. To this end, the transceiver (1302) 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 (1302), and the components of the transceiver (1302) are not limited to an RF transmitter and an RF receiver. Additionally, the transceiver (1302) can receive a signal and output it to a processor (1301), and transmit the signal output from the processor (1301) to another network entity through a network.

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

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

[0220] According to one embodiment of the present disclosure, a method of an AP may include the step of transmitting a first frame to notify an AP STA of a change in the status and application parameters of an already set SCS, and the step of receiving a second frame from the STA that includes a request for a parameter change.

[0221] In one embodiment, the first frame may include at least one of a field indicating the transmission of a second frame to the STA and a field indicating a time prohibiting the transmission of the second frame.

[0222] In one embodiment, the SCS Status List field within the first frame may include status change information of the QoS profile distinguished by SCSID.

[0223] In one embodiment, the SCS Descriptor List field in the first frame may include at least one of the status and parameter change information of a QoS profile distinguished by a separate identifier other than the SCSID. In one embodiment, the Optional subelement field in the first frame may include a field that can indicate the time of the status change.

[0224] In one embodiment, the first frame may include a field that provides QoS parameter information that can be provided by another link.

[0225] 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.

[0226] 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 an access point in a wireless local area network (WLAN) communication system, A step of receiving an SCS request frame from a station to set up an SCS (stream classification service) stream; A step of transmitting an SCS response frame to the above station to establish the SCS stream; and A method characterized by including the step of transmitting a first frame to the station to notify a change to at least one set of quality of service (QoS) parameters set for the SCS stream.

2. In Paragraph 1, A method further comprising the step of receiving a second SCS request frame from the station requesting a change in the changed QoS parameter set in response to the first frame.

3. In paragraph 2, the first frame is, A method characterized by including instruction information for the transmission of the second SCS request frame.

4. In paragraph 3, the instruction information instructs the station to transmit the second SCS request frame requesting a change to the changed QoS parameter set, or A method characterized in that the above instruction information includes time information regarding the time of transmitting the second SCS request frame.

5. In paragraph 1, the first frame is, A method characterized by including information indicating one of a change, suspension of application, or resumption of application of at least one set of QoS parameters set for the above SCS stream.

6. In Paragraph 5, Information indicating one of the above changes, suspension of application, or resumption of application, A method characterized by being included in at least one of the SCS Status List field or SCS Descriptor List field of the first frame.

7. In paragraph 1, the first frame is, A method characterized by including information on the timing of when a change, suspension of application, or resumption of application of at least one set of QoS parameters set for the above SCS stream is applied.

8. A method according to claim 1, wherein, when a plurality of QoS parameter sets are determined for the set SCS stream, information indicating one of changing, suspending, or resuming the application of the plurality of QoS parameter sets for the SCS stream is distinguished based on at least one of an SCSID or a Profile ID associated with the plurality of QoS parameter sets.

9. In paragraph 1, the first frame is A method characterized by including an SCS response frame.

10. In paragraph 1, the first frame is, A method characterized by including information on at least one set of QoS parameters that can be provided by a link other than the currently used link.

11. In paragraph 10, information regarding the other link is included in the Control field of the QoS Characteristics element included in the first SCS Descriptor element included in the first frame, and A method characterized in that information regarding at least one set of QoS parameters available from the other link above is included in the first SCS Descriptor element or the second SCS Descriptor element included in the first frame.

12. 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; A step of receiving an SCS response frame for establishing the SCS stream from the access point; and A method characterized by including the step of receiving a first frame from the access point to notify a change to at least one set of quality of service (QoS) parameters set for the SCS stream.

13. In Paragraph 12, A method further comprising the step of transmitting a second SCS request frame to the access point, requesting a change in the changed QoS parameter set in response to the first frame.

14. 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 configure the SCS (stream classification service) stream, and To the above station, transmit an SCS response frame to establish the SCS stream, and An access point characterized by causing the station to transmit a first frame to notify of a change to at least one set of QoS parameters set for the SCS stream.

15. 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 configure the SCS (stream classification service) stream, and From the access point, receive an SCS response frame for establishing the SCS stream, and A station characterized by causing to receive a first frame from the access point to notify a change to at least one set of QoS parameters set for the SCS stream.

Images