Method for managing WI-FI quality of service in network

Abstract

Embodiments herein disclose systems and methods for managing a Wireless Fidelity (Wi-Fi) Quality of Service (QoS) in a network (300). The method includes detecting, by a mobile device (100), a real-time application traffic in the mobile device (100), when the mobile device (100) is connected with an access point (AP) (200) from a plurality of APs. Further, the method includes determining, by the mobile device (100), a connected AP capability for a Mirrored Stream Classification Service (MSCS) using extended capability information exchanged during a Wi-Fi association process. Further, the method includes generating, by the mobile device (100), an MSCS request comprising at least one MSCS parameter when the connected AP (200) supports the MSCS. Further, the method includes sending, by the mobile device (100), the MSCS request to the connected AP for prioritization the real-time application traffic.

Description

METHOD FOR MANAGING WI-FI QUALITY OF SERVICE IN NETWORK

[0001] Embodiments disclosed herein relate to wireless communication networks, and more particularly to systems and methods for application independent Wireless Fidelity (Wi-Fi) Quality of Service (QoS) management using Mirrored Stream Classification Service (MSCS) in a mobile device (or user Equipment (UE)) for enhancing latency.

[0002] Wi-Fi Quality of Service (QoS) is a set of protocols and techniques to prioritize specific data services within a network to improve latency, jitter, and reliability, which improves user experience (as depicted in FIG. 2). This was introduced in IEEE 802.11e standard.

[0003] One of the QoS features is Enhanced Distributed Channel Access (EDCA). The EDCA categorizes traffic into Access Categories (ACs) to obtain different priority classifications. Each AC has its own message queue and specific contention parameters for accessing the wireless medium. The EDCA ensures critical data, like voice and video, can get prioritized access in Wi-Fi networks over other types of traffic (as depicted in the example in FIG. 1). For instance, voice might be given the highest priority, while background data traffic might be given the lowest.

[0004] The FIG. 2 on the left shows the Wi-Fi QoS WMM AC priority queues in the Wi-Fi access point (AP) which will send the application traffic to any one of the 4 queues depending on the priority / WMM AC value.

[0005] VO = voice (highest priority, for latency-sensitive applications)

[0006] VI = video

[0007] BE = best effort (default)

[0008] BK = background (lowest priority)

[0009] The WMM AC value of AC_VI refers to the Video Access Category in the Wi-Fi Multimedia (WMM) standard. The WMM is a Quality of Service (QoS) enhancement for Wi-Fi networks that prioritizes different types of traffic based on their sensitivity to latency and jitter. The AC_VI is one of the four Access Categories (ACs) defined by the WMM, and it is assigned to traffic that requires low latency and minimal delay, such as video streaming and real-time applications.

[0010] It has a higher priority compared to other categories like AC_BK (Background), AC_BE (Best Effort), and AC_BK (Background). Packets with the AC_VI priority are given preferential treatment in terms of bandwidth allocation and scheduling, ensuring they are transmitted and received with minimal delay.

[0011] Mirrored Stream Classification Service (MSCS) (as depicted in FIG. 3) enables the app in a client device (or mobile device) (100) to request the AP (200) to apply specific QoS treatment of downlink IP flows using QoS mirroring. In MSCS, the gaming application (app) in the client device (100) sends the AP (200) an MSCS request to prompt the AP (200) to initiate mirroring and assign priorities to specified downlink traffic flows by manually. In an example, the user of the client device (100) had to manually enter "mscs add" and "mscs remove" commands in the terminal to send an MSCS request to the AP (200) and the AP (200) would enable MSCS for all the traffic coming from the client device (100). The AP (200) aligns the priorities with what the client device (100) initially assigned to the corresponding uplink traffic flows and performs QoS treatment for certain uplink Internet Protocol (IP) flows that result in reduced latency and a better end-user experience with real-time applications. The MSCS descriptor specifies the set of classification parameters (e.g., source IP, port or the like), not the actual values of those parameters, which results in the AP (200) identifying and tracking multiple streams. The client devices (100) use a dedicated frame exchange to trigger the MSCS process. The MSCS functionality works only for client devices that support MSCS.

[0012] The mobile device (100) includes an application layer 402, a framework layer (404), and a Kernel layer (406). Currently all applications in the mobile devices (100) are sending and receiving packets with Best Effort WMM AC (as depicted in FIG. 4). This does not differentiate packets coming from real-time applications from that of non-real-time applications. In a shared environment, gaming application (app) experiences high latency and results in screen lag and poor QoE for app users. The app traffic competes with other network traffic for bandwidth.

[0013] With the introduction of MSCS, although it can reduce latency in RT applications and improve the QoE for app users, many application developers are yet to implement this. In other words, the app traffic competes with other network traffic for bandwidth. In shared environment, RT apps like gaming / calling / live streaming apps experiences high latency and results in screen lag, dropped connections, reduced responsiveness, and poor QoE for app users. Currently implemented systems are unable to prioritize traffic coming from specific applications in mobile devices (100) on the AP side (200).

[0014] In an example, every application in the mobile device (100) used to get same traffic priority on the AP side (200), by having WMM AC value of best effort in the packets. The main problem is that RT app traffic would interfere with the background download traffic leading to inefficient network management and users complaining about poor quality of experience when using gaming / calling / live streaming applications on their devices.

[0015] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0016] Accordingly, the embodiments disclosed herein relate to a method for managing a Wireless Fidelity (Wi-Fi) Quality of Service (QoS) in a network. The method includes detecting, by a mobile device, a real-time application traffic in the mobile device, when the mobile device is connected with an access point (AP) from a plurality of APs. Further, the method includes determining, by the mobile device, a connected AP capability for a Mirrored Stream Classification Service (MSCS) using extended capability information exchanged during a Wi-Fi association process. Further, the method includes generating, by the mobile device, an MSCS request comprising at least one MSCS parameter when the connected AP supports the MSCS. Further, the method includes sending, by the mobile device, the MSCS request to the connected AP for prioritization the real-time application traffic.

[0017] In an embodiment, further, the method includes receiving, by the mobile device, at least one of: a success message and a failure message corresponding to the MSCS request from the connected AP. Further, the method includes managing, by the mobile device, a downlink QoS by ensuring that the MSCS is applied for at least one received packet from the connected AP based on the MSCS request when the mobile device receives the success message corresponding to the MSCS request from the connected AP.

[0018] In an embodiment, managing, by the mobile device, the downlink QoS includes performing, by the mobile device, an uplink QoS priority mapping using at least one of: a Differentiated Services Code Point-to-Enhanced Distributed Channel Access (DSCP-to-EDCA) mapping, DSCP-to-UP mapping with video (VI) or video (VO) priority, and managing, by the mobile device, the downlink QoS based on the uplink QoS priority mapping.

[0019] In an embodiment, further, the method includes detecting, by the mobile device, that a real-time application running in the mobile device is stopped. Further, the method includes automatically reverting, by the mobile device, at least one of: a default Best Effort (BE) classification and a Background (BG) traffic classification when the real-time application running in the mobile device is stopped. further, the method includes sending, by the mobile device, an MSCS remove request to the connected AP upon stopping the real-time application.

[0020] In an embodiment, the detection of the real-time application traffic is performed by an Application-Agnostic Mirrored Stream Classification Service (AMSCS) embedded in an operating system of the mobile device.

[0021] In an embodiment, the AMSCS determines the at least one MSCS parameter using a traffic classification (TCLAS), wherein the at least one MSCS parameter comprises at least one of: a stream timeout, a user priority bitmap, a user priority limit, and a frame classifier.

[0022] In an embodiment, the AMSCS dynamically adjusts the at least one MSCS parameter based on at least one of: a real-time network condition and an application priority level.

[0023] In an embodiment, the frame classifier in the MSCS request is populated using at least one of: a DSCP bit, an 802.1p priority value and a port-based classification.

[0024] In an embodiment, the mobile device maintains a list of MSCS-capable APs and selectively sends the MSCS request to the MSCS-capable APs from the plurality of APs.

[0025] In an embodiment, the mobile device continuously monitors a status of the real-time application and dynamically updates or removes the MSCS request based on at least one of: a foreground state of the real-time application and a background state of the real-time application.

[0026] In an embodiment, the extended capability information comprises at least one capability bit in an extended capabilities information element included in a Wi-Fi association response frame, wherein the extended capability information includes an indication of support for the MSCS in accordance with an IEEE 802.11 standard, and wherein the extended capability information is received from the AP during an association response message of the Wi-Fi association process.

[0027] Accordingly, the embodiments disclosed herein relate to a method for managing a Wi-Fi QoS in a network. The method includes receiving, by an access point (AP), a MSCS request from a mobile device for prioritization a real-time application traffic, when the mobile device is connected with the access point (AP) from a plurality of APs and determines a connected AP capability for a Mirrored Stream Classification Service (MSCS) using extended capability information exchanged during a Wi-Fi association process. Further, the method includes sending, by the AP, at least one of: a success message and a failure message corresponding to the MSCS request to the mobile device. Further, the method includes managing, by the AP, a downlink QoS by ensuring that the MSCS is applied for at least one packet to the mobile device based on the MSCS request when the mobile device receives the success message corresponding to the MSCS request from the AP.

[0028] In an embodiment, managing the downlink QoS includes performing an uplink QoS priority mapping at the mobile device using at least one of: a Differentiated Services Code Point-to-Enhanced Distributed Channel Access (DSCP-to-EDCA) mapping, DSCP-to-UP mapping with video (VI) or video (VO) priority and managing the downlink QoS based on the uplink QoS priority mapping.

[0029] Accordingly, the embodiments disclosed herein relate to a mobile device including a Wi-Fi QoS managing controller coupled with a processor and a memory. The Wi-Fi QoS managing controller is configured to detect a real-time application traffic in the mobile device, when the mobile device is connected with an access point (AP) from a plurality of APs. Further, the Wi-Fi QoS managing controller is configured to determine a connected AP capability for a MSCS using extended capability information exchanged during a Wi-Fi association process. Further, the Wi-Fi QoS managing controller is configured to generate an MSCS request comprising at least one MSCS parameter when the connected AP supports the MSCS. Further, the Wi-Fi QoS managing controller is configured to send the MSCS request to the connected AP for prioritization the real-time application traffic.

[0030] Accordingly, the embodiments disclosed herein relate to an access point (AP) including a Wi-Fi QoS managing controller coupled with a processor and a memory. The Wi-Fi QoS managing controller is configured to receive a MSCS request from a mobile device for prioritization a real-time application traffic, when the mobile device is connected with the AP from a plurality of APs and determines a connected AP capability for a MSCS using extended capability information exchanged during a Wi-Fi association process. Further, the Wi-Fi QoS managing controller is configured to send at least one of: a success message and a failure message corresponding to the MSCS request to the mobile device. Further, the Wi-Fi QoS managing controller is configured to manage a downlink QoS by ensuring that the MSCS is applied for at least one packet to the mobile device based on the MSCS request when the mobile device receives the success message corresponding to the MSCS request from the AP.

[0031] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0032] The principal object of embodiments herein is to disclose systems and methods for application independent Wi-Fi QoS management using MSCS in a UE (or mobile device) for enhancing latency.

[0033] Another object of embodiments herein is to provide a proposed application agnostic method automatically detecting and upgrading a download and upload WMM intelligently in the mobile device.

[0034] Another object of embodiments herein is to disclose App-agnostic Mirrored Stream Classification Service (AMSCS service), wherein a station (STA) (or mobile device) automatically detects the priority traffic and triggers a corresponding MSCS request (with VO or VI), and automatically informing the AP to fall back to the previous mechanism (BE or BG) (on the application being closed or the priority has changed), further, the application need not be modified and the system ensures for all the real time gaming or video calling or AR / VT traffic, the MSCS is properly handled from the mobile device to the AP.

[0035] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0036] FIG. 1 depicts an example priority for users, according to existing arts;

[0037] FIG. 2 depicts a Wi-Fi QoS, according to existing arts;

[0038] FIG. 3 depicts an example MSCS, according to existing arts;

[0039] FIG. 4 depicts an example AMSCS service for a UE (or mobile device), according to existing arts;

[0040] FIG. 5 depicts an example AMSCS service for the UE, according to embodiments as disclosed herein;

[0041] FIG. 6 depicts an example process of identifying MSCS supported AP(s), according to embodiments as disclosed herein;

[0042] FIG. 7 depicts an example process of sending an AMSCS request, according to embodiments as disclosed herein;

[0043] FIG. 8 depicts an example process of the AMSCS modifying downlink packets, according to embodiments as disclosed herein;

[0044] FIG. 9 depicts an example process of disabling the AMSCS, when the app stops running, according to embodiments as disclosed herein;

[0045] FIG. 10 shows various hardware components of a mobile device, according to the embodiments as disclosed herein;

[0046] FIG. 11 shows various hardware components of an AP, according to the embodiments as disclosed herein;

[0047] FIG. 12 is a flow chart illustrating a method, implemented by the mobile device, for managing the Wi-Fi QoS in a network, according to the embodiments as disclosed herein; and

[0048] FIG. 13 is a flow chart illustrating a method, implemented by the AP, for managing the Wi-Fi QoS in a network, according to the embodiments as disclosed herein.

[0049] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0050] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.,", "i.e.," are merely used herein to mean "serving as an example, instance, or illustration. Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.," , "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0051] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0052] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0053] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0054] The terms "UE", "mobile device", "client device", "station", and "STA" are used interchangeably in the patent disclosure.

[0055] The embodiments herein achieve systems and methods for application independent Wi-Fi QoS management using MSCS in the UE for enhancing latency. Accordingly, the embodiments disclosed herein relate to a method for managing a Wireless Fidelity (Wi-Fi) Quality of Service (QoS) in a network. The method includes detecting, by a mobile device, a real-time application traffic in the mobile device, when the mobile device is connected with an access point (AP) from a plurality of APs. Further, the method includes determining, by the mobile device, a connected AP capability for a Mirrored Stream Classification Service (MSCS) using extended capability information exchanged during a Wi-Fi association process. Further, the method includes generating, by the mobile device, an MSCS request comprising at least one MSCS parameter when the connected AP supports the MSCS. Further, the method includes sending, by the mobile device, the MSCS request to the connected AP for prioritization the real-time application traffic.

[0056] Embodiments herein disclose App-agnostic Mirrored Stream Classification Service (AMSCS service), wherein the mobile device automatically detects the priority traffic and triggers a corresponding MSCS request (with VO or VI), and automatically informing the AP to fall back to the previous mechanism (BE or BG) (on the application being closed or the priority has changed), further, the application need not be modified and the system ensures for all the real time gaming or video calling or AR / VT traffic, the MSCS is properly handled from the mobile device to the AP.

[0057] The system and method can be used for application independent Wi-Fi QoS management using MSCS in the UE (i.e., mobile device or the like) for enhancing latency. The proposed method can be used to reduce latency for real-time application network traffic on a client side of the mobile device, so as to enhance responsiveness between applications and their servers without user intervention, whenever any real-time app runs in foreground. The proposed method identifies MSCS supported devices and effectively utilizes them, so as to minimize unnecessary robust action frame requests without requiring any modifications to the application itself.

[0058] The proposed method ensures proper Wi-Fi Quality of Service (QoS) management for both uplink and downlink packets. Additionally, the proposed method automatically disables AMSCS when the application stops running in the foreground, promoting efficient resource utilization.

[0059] In an example, first, the user of the mobile device determines whether the connected AP supports mirrored stream classification service, which will mirror the access categories of the upstream packets that were set using QBOX. When the mobile device detects that there is a real-time application running on the foreground and the AP supports MSCS, a request is sent to the AP to enable MSCS for this particular application traffic. If the upstream packets (packets from a client to AP) have WMM AC value of AC_VI (video; second-highest priority), then the AP will mirror that value for downstream packets and will be given higher priority of AC_VI, so that it can reach the mobile device earlier than other packets. This reduces latency in gaming or calling applications. Once the real-time app is no longer running in the foreground, a request is sent to the AP to remove MSCS rules for this particular application traffic.

[0060] In an example, consider, a user of the mobile device playing a multiplayer game like PUBG on the device using Wi-Fi. The proposed method will request the AP to give a higher priority to the game's packets by mirroring the upstream packets' access category so that it reaches the device faster and improves the latency and the quality of experience for the user.

[0061] Referring now to the drawings, and more particularly to FIGS. 5 through 13, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0062] FIG. 5 depicts an example AMSCS service for a UE (mobile device) (100). The mobile device (100) includes an application layer 402, a framework layer (404), and a Kernel layer (406). FIG. 5 shows the system architecture and flow of the proposed AMSCS system. The framework layer detects if any RT app is running in the foreground. If true, and the AP supports MSCS, the DSCP value of the packets related to the app is changed to 0x80 to set a higher priority to the application traffic. An MSCS request is sent to the AP (200) to enable MSCS, via the enableMscs API in the framework layer. Since the DSCP values have been changed, the WMM AC values also changes to AC_VI.

[0063] Initially, the MSCS identifies supported AP(s) (200) (as depicted in FIG. 6). MSCS requests need not be sent for all the APs, and MSCS requests can be send only to the supported AP(s). While connecting the Wi-Fi (i.e., an AP), during the initial 4-way handshake establishment, embodiments herein verify the AP extended capabilities. If the extended capabilities has "MSCS" element, embodiments herein add the specific SSID to the allowed list. During the active priority app, before sending the MSCS request, embodiments herein verify if the connected AP (200) is MSCS capable. This reduces the Robust Action frame request, when the AP (200) doesn't support MSCS.

[0064] Embodiments herein send an AMSCS request (as depicted in FIG. 7). Once the real-time app is detected by the AMSCS service, it validates the capability list of supported AP (200). If the AP (200) supports MSCS, then AMSCS service automatically determines the MSCS parameters including the stream timeout, user priority bitmap, user priority limit and corresponding frame classifier using TCLAS. Once the request is built by the AMSCS service, the mobile device (100) sends it to the AP (200). The AP (200) responds with status code (0 as success or other failure codes).

[0065] Embodiments herein disclose the AMSCS modifying downlink packets (as depicted in FIG. 8). Consider that the DSCP to EDCA mapping for the uplink is appropriately set. Hence, embodiments herein use the DSCP bit in the TCLAS to fill the frame classifier in MSCS request. If the DSCP to EDCA mapping for the uplink is not appropriately set, or the appropriate DSCP value is unable to be modified (due to any uncertainty), embodiments herein use the IP and PORT fields of the TCLAS to fill the frame classifier in MSCS requests. Embodiments herein ensure DSCP-to-UP mapping with VI or VO priority and with AMSCS, embodiments herein can guarantee the downlink packets also to be mapped with VI or VO priority. Thereby, embodiments herein can manage the appropriate Wi-Fi QoS management for both uplink and downlink packets.

[0066] Embodiments herein disclose disabling the AMSCS, when the application stops running (as depicted in FIG. 9). When the device detects that the RT app stops running in the foreground, then the AMSCS service will send a remove request to the AP (200). The AP (200) sends a response with a status code (0 as success or other failure codes). This can be done automatically within the device.

[0067] FIG. 10 shows various hardware components of the mobile device (100), according to the embodiments as disclosed herein. The mobile device (100) can also be the UE and station (STA). The mobile device (100) can be, for example, but not limited to, a laptop, a desktop computer, a notebook, a Device-to-Device (D2D) device, a vehicle to everything (V2X) device, a smartphone, a foldable phone, a smart TV, a tablet, an immersive device, an internet of things (IoT) device, an Extended Reality (XR) device, a Virtual Reality (VR) device, a Mixed Reality (MR) device, an Augmented Reality (AR) device, an Head-Mounted Display (HMD) device or the like.

[0068] The mobile device (100) includes a processor (110), a communicator (120), a memory (130), and a Wi-Fi QoS managing controller (140). The processor (110) is coupled with the communicator (120), the memory (130), and the Wi-Fi QoS managing controller (140).

[0069] The Wi-Fi QoS managing controller (140) maintains a list of MSCS-capable APs (200) and selectively sends the MSCS request to the MSCS-capable APs (200) from the plurality of APs. The Wi-Fi QoS managing controller (140) continuously monitors a status of the real-time application and dynamically updates or removes the MSCS request based on at least one of: a foreground state of the real-time application and a background state of the real-time application.

[0070] The Wi-Fi QoS managing controller (140) detects the real-time application traffic in the mobile device (100), while the mobile device (100) is connected with the AP (200) from the plurality of APs. In an embodiment, the detection of the real-time application traffic is performed by the AMSCS embedded in an operating system of the mobile device (100). The AMSCS determines the at least one MSCS parameter using a traffic classification (TCLAS). The AMSCS dynamically adjusts the at least one MSCS parameter based on at least one of: a real-time network condition and an application priority level. The at least one MSCS parameter can be, for example, but not limited to at least one of: a stream timeout, a user priority bitmap, a user priority limit, and a frame classifier. The frame classifier in the MSCS request is populated using at least one of: a DSCP bit, an 802.1p priority value and a port-based classification.

[0071] Further, the Wi-Fi QoS managing controller (140) determines the connected AP capability for the MSCS using extended capability information exchanged during the Wi-Fi association process. In an embodiment, the extended capability information comprises at least one capability bit in an extended capabilities information element included in a Wi-Fi association response frame, wherein the extended capability information includes an indication of support for the MSCS in accordance with an IEEE 802.11 standard, and wherein the extended capability information is received from the AP (200) during an association response message of the Wi-Fi association process.

[0072] Further, the Wi-Fi QoS managing controller (140) generates an MSCS request including at least one MSCS parameter when the connected AP (200) supports the MSCS. Further, the Wi-Fi QoS managing controller (140) sends the MSCS request to the connected AP (200) for prioritization the real-time application traffic.

[0073] Further, the Wi-Fi QoS managing controller (140) receives at least one of: the success message and the failure message corresponding to the MSCS request from the connected AP (200). Further, the Wi-Fi QoS managing controller (140) manages a downlink QoS by ensuring that the MSCS is applied for at least one received packet from the connected AP (200) based on the MSCS request when the mobile device (100) receives the success message corresponding to the MSCS request from the connected AP (200).

[0074] In an embodiment, the Wi-Fi QoS managing controller (140) performs the uplink QoS priority mapping using at least one of: the DSCP-to-EDCA mapping, the DSCP-to-UP mapping with video (VI) or video (VO) priority. Further, the Wi-Fi QoS managing controller (140) manages the downlink QoS based on the uplink QoS priority mapping.

[0075] In an embodiment, the Wi-Fi QoS managing controller (140) detects that the real-time application running in the mobile device (100) is stopped. The Wi-Fi QoS managing controller (140) automatically reverts at least one of: the default BE classification and a Background (BG) traffic classification when the real-time application running in the mobile device (100) is stopped. Further, the Wi-Fi QoS managing controller (140) sends an MSCS remove request to the connected AP upon stopping the real-time application.

[0076] The Wi-Fi QoS managing controller (140) is implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0077] The processor (110) may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The processor (110) may include multiple cores and is configured to execute the instructions stored in the memory (130).

[0078] Further, the processor (110) is configured to execute instructions stored in the memory (130) and to perform various processes. The communicator(120) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (130) also stores instructions to be executed by the processor (110). The memory (130) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (130) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (130) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0079] Although FIG. 10 shows various hardware components of the mobile device (100) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the mobile device (100) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention. One or more components can be combined together to perform the same or substantially similar function in the mobile device (100).

[0080] FIG. 11 shows various hardware components of the AP (200), according to the embodiments as disclosed herein. The AP (200) includes a processor (210), a communicator (220), a memory (230), and a Wi-Fi QoS managing controller (240). The processor (210) is coupled with the communicator (220), the memory (230), and the Wi-Fi QoS managing controller (240).

[0081] The Wi-Fi QoS managing controller (240) receives the MSCS request from the mobile device (100) for prioritization the real-time application traffic, when the mobile device (100) is connected with the AP (200) from the plurality of APs and determines the connected AP capability for the MSCS using extended capability information exchanged during the Wi-Fi association process. Further, the Wi-Fi QoS managing controller (240) sends the at least one of: the success message and the failure message corresponding to the MSCS request to the mobile device (100). Further, the Wi-Fi QoS managing controller (240) manages the downlink QoS by ensuring that the MSCS is applied for at least one packet to the mobile device (100) based on the MSCS request when the mobile device (100) receives the success message corresponding to the MSCS request from the AP (200).

[0082] In an embodiment, the Wi-Fi QoS managing controller (240) performs the uplink QoS priority mapping at the mobile device (100) using at least one of: the DSCP-to-EDCA mapping, the DSCP-to-UP mapping with video (VI) or video (VO) priority. Further, the Wi-Fi QoS managing controller (240) manages the downlink QoS based on the uplink QoS priority mapping.

[0083] The Wi-Fi QoS managing controller (240) is implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0084] The processor (210) may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The processor (210) may include multiple cores and is configured to execute the instructions stored in the memory (230).

[0085] Further, the processor (210) is configured to execute instructions stored in the memory (230) and to perform various processes. The communicator(220) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (230) may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory (230) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0086] Although FIG. 11 shows various hardware components of the AP (200) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the AP (200) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention. One or more components can be combined together to perform the same or substantially similar function in the AP (200).

[0087] FIG. 12 is a flow chart (S1200) illustrating a method, implemented by the mobile device (100), for managing the Wi-Fi QoS in the network (300), according to the embodiments as disclosed herein. The operations (S1202-S1208) are handled by the Wi-Fi QoS managing controller (140).

[0088] At S1202, the method includes detecting the real-time application traffic in the mobile device (100), whilethe mobile device (100) is connected with the AP (200) from the plurality of APs. At S1204, the method includes determining whether the connected AP supports the MSCS based on extended capability information received during the Wi-Fi association process from the connected AP.

[0089] At S1206, the method includes generating the MSCS request comprising the at least one MSCS parameter associated with prioritization of the real-time application traffic when(or if) the connected AP (200) supports the MSCS. At S1208, the method includes transmitting the MSCS request to the connected AP.

[0090] FIG. 13 is a flow chart (S1300) illustrating a method, implemented by the AP (200), for managing the Wi-Fi QoS in the network (300), according to the embodiments as disclosed herein. The operations (S1302-S1306) are handled by the Wi-Fi QoS managing controller (240).

[0091] At S1302, the method includes receiving the MSCS request from the mobile device (100) connected with the access point (AP) associated wiht prioritization of the real-time application traffic. At S1304, the method includes transmitting a MSCS response corresponding to the MSCS request, the MSCS response including at least one of: the success message and the failure message corresponding to the MSCS request to the mobile device (100). At S1306, the method includes transmitting at least one downlink packet based on the at least one MSCS parameter to the mobile device (100) based on transmitting the success message corresponding to the MSCS request from the AP (200) to the the mobile device (100).

[0092] Further, upon transmitting the success message, the Wi-Fi QoS managing controller (140) transmit at least one downlink packet based on the at least one MSCS parameter to the mobile device. In particular, once the MSCS request is successfully accepted, the Wi-Fi QoS managing controller identifies(orutilizes) the MSCS parameter (for example, a frame classifier, a user priority bitmap, a user priority limit, or a stream timeout) included in the MSCS request to identify a corresponding downlink traffic flow and to apply an appropriate user priority for the downlink transmission. The Wi-Fi QoS managing controller maps the downlink packet to an Enhanced Distributed Channel Access (EDCA) access category based on the user priority indicated in the MSCS parameter, thereby ensuring that the downlink packet is transmitted with the same priority level as the uplink packet for which the mobile device initiated the MSCS request.

[0093] after the mobile device receives a success message corresponding to the MSCS request from the AP, the mobile device begins to receive at least one downlink packet that is transmitted by the AP based on the MSCS parameter included in the MSCS request. The MSCS parameter, which may include a frame classifier, a user priority bitmap, a user priority limit, or a stream timeout, enables the AP to identify a corresponding downlink traffic flow and to apply a user priority to the downlink transmission.

[0094] The proposed method prioritizes real-time application network traffic on the AP side (200), so as to ensure faster connectivity and improve the overall user experience. The proposed method can be used to identify MSCS supported APs (200) and effectively utilize them, so as to reduce unnecessary robust action frame requests. The proposed method leverages existing systems like QBOX to ensure proper Wi-Fi QoS management for both uplink and downlink packets. The proposed method incorporates automatic disabling of AMSCS when the app stops running in the foreground, showcasing efficient resource management. The proposed method enhances connectivity speeds and QoS management.

[0095] The proposed method proposes an application-agnostic technique to prioritize real-time application network traffic on the AP side (200). By implementing the proposed method in a framework layer, the method sends a request to the AP (200) to mirror the priority of the upstream traffic onto the downstream traffic, resulting in faster connectivity between applications and their servers by around 20-30% (for example). The proposed method can be used to identify MSCS supported APs and utilize them effectively.

[0096] The various actions, acts, blocks, steps, or the like in the flow chart (S1200 and S1300) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0097] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0098] The embodiments disclosed herein describe systems and methods for application independent Wi-Fi QoS management using MSCS in the UE for enhancing latency. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile deviceor any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0099] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments, those skilled in the art will recognize that the embodiments herein can be practised with modification within the scope of the embodiments as described herein.

Claims

1.A method for managing a Wireless Fidelity (Wi-Fi) Quality of Service (QoS) in a network (300), comprising:detecting, by a mobile device (100), real-time application traffic in the mobile device (100), while the mobile device (100) is connected with an access point (AP) (200) from a plurality of APs;determining, by the mobile device (100), whether the connected AP supports a Mirrored Stream Classification Service (MSCS) based on extended capability information received during a Wi-Fi association process from the connected AP;generating, by the mobile device (100), an MSCS request comprising at least one MSCS parameter associated with prioritization of the real-time application traffic when the connected AP (200) supports the MSCS; andtransmitting, by the mobile device (100), the MSCS request to the connected AP (200).2.The method as claimed in claim 1, wherein the method comprisesreceiving, by the mobile device (100), MSCS response corresponding to the MSCS request, the MSCS response including at least one of a success message and a failure message corresponding to the MSCS request from the connected AP (200); andreceiving, by the mobile device (100), at least one downlink packet transmitted based on the at least one MSCS parameter to the mobile device (100) by the connected AP (200), based on receiving the success message corresponding to the MSCS request from the connected AP (200).3.The method as claimed in claim 2, wherein managing, by the mobile device (100), the downlink QoS comprises:performing, by the mobile device (100), an uplink QoS priority mapping using at least one of: a Differentiated Services Code Point-to-Enhanced Distributed Channel Access (DSCP-to-EDCA) mapping, DSCP-to-UP mapping with video (VI) or video (VO) priority; andmanaging, by the mobile device (100), the downlink QoS based on the uplink QoS priority mapping.4.The method as claimed in claim 1, wherein the method comprises:detecting, by the mobile device (100), that a real-time application running in the mobile device (100) is stopped;reverting, by the mobile device (100), at least one of: a default Best Effort (BE) classification and a Background (BG) traffic classification when the real-time application running in the mobile device (100) is stopped; andtransmitting, by the mobile device (100), an MSCS remove request to the connected AP (200) upon stopping the real-time application.5.The method as claimed in claim 1, wherein the detection of the real-time application traffic is performed by an Application-Agnostic Mirrored Stream Classification Service (AMSCS) embedded in an operating system of the mobile device (100), wherein the AMSCS determines the at least one MSCS parameter using a traffic classification (TCLAS), wherein the at least one MSCS parameter comprises at least one of: a stream timeout, a user priority bitmap, a user priority limit, and a frame classifier.6.The method as claimed in claim 5, wherein the AMSCS dynamically adjusts the at least one MSCS parameter based on at least one of: a real-time network condition and an application priority level.7.The method as claimed in claim 5, wherein the frame classifier in the MSCS request is populated using at least one of: a DSCP bit, an 802.1p priority value and a port-based classification.8.The method as claimed in claim 1, wherein the mobile device (100) maintains a list of MSCS-capable APs and selectively transmits the MSCS request to the MSCS-capable APs (200) from the plurality of APs.9.The method as claimed in claim 1, wherein the mobile device (100) continuously monitors a status of the real-time application and dynamically updates or removes the MSCS request based on at least one of: a foreground state of the real-time application and a background state of the real-time application.10.The method as claimed in claim 1, wherein the extended capability information comprises at least one capability bit in an extended capabilities information element included in a Wi-Fi association response frame, wherein the extended capability information includes an indication of support for the MSCS in accordance with an IEEE 802.11 standard, and wherein the extended capability information is received from the AP (200) during an association response message of the Wi-Fi association process.11.A method for managing a Wireless Fidelity (Wi-Fi) Quality of Service (QoS) in a network, comprising:receiving, by an access point (AP) (200), a mirrored stream classification service (MSCS) request from a mobile device (100) connected with the access point (AP) including at least one MSCS parameter associated with prioritization of a real-time application traffic;transmitting, by the AP (200), a MSCS response corresponding to the MSCS request, the MSCS response including at least one of a success message and a failure message corresponding to the MSCS request to the mobile device (100); andtransmit, by the AP (200), at least one downlink packet based on the at least one MSCS parameter to the mobile device (100) based on transmitting the success message corresponding to the MSCS request from the AP (200) to the the mobile device (100).12.The method as claimed in claim 11, wherein managing the downlink QoS comprises:performing an uplink QoS priority mapping at the mobile device (100) using at least one of: a Differentiated Services Code Point-to-Enhanced Distributed Channel Access (DSCP-to-EDCA) mapping, DSCP-to-UP mapping with video (VI) or video (VO) priority; andmanaging the downlink QoS based on the uplink QoS priority mapping.13.A mobile device (100), comprising:a processor (110);a memory (130); anda Wi-Fi QoS managing controller (140), coupled with the processor (110) and the memory (130), configured to:detect real-time application traffic in the mobile device (100), while the mobile device (100) is connected with an access point (AP) (200) from a plurality of APs;determine whether the connected AP supports a Mirrored Stream Classification Service (MSCS) based on extended capability information received during a Wi-Fi association process from the connected AP;generate an MSCS request comprising at least one MSCS parameter associated with prioritization of the real-time application traffic when the connected AP (200) supports the MSCS; andtransmit the MSCS request to the connected AP.14.The mobile device (100) of claim 13, wherein the Wi-Fi QoS managing controller (140) is configured to:receive a MSCS response corresponding to the MSCS request, the MSCS response including at least one of a success message and a failure message corresponding to the MSCS request from the connected AP (200); andreceive at least one downlink packet transmitted based on the at least one MSCS parameter to the mobile device (100) by the connected AP (200), based on receiving the success message corresponding to the MSCS request from the connected AP (200).15.An access point (AP) (200), comprising:a processor (210);a memory (230); anda Wi-Fi QoS managing controller (240), coupled with the processor (210) and the memory (230), configured to:receive a mirrored stream classification service (MSCS) request from a mobile device (100) connected with the access point (AP) including at least one MSCS parameter associated with prioritization of a real-time application traffic;transmit a MSCS response corresponding to the MSCS request, the MSCS response including at least one of a success message and a failure message corresponding to the MSCS request to the mobile device (100); andtransmit at least one downlink packet with a MSCS-based priority corresponding to the prioritization of the real-time application to the mobile device (100) based on transmitting the success message corresponding to the MSCS request from the AP (200) to the the mobile device (100).

Images