Access point device, method performed by same, and computer program product

Abstract

At least one embodiment of the present disclosure provides an access point device, a method performed by the same, and a computer program product. The method executed by an access point (AP) device supporting a mirror stream classification service (MSCS) function comprises the following steps: acquiring MSCS function switching information, wherein the MSCS function switching information is used for indicating to open or close the MSCS function of the AP device; and on the basis of the MSCS function switch information, opening or closing the MSCS function of the AP equipment. According to the method executed by the AP equipment, the opening and closing of the MSCS function of the AP equipment can be flexibly controlled so as to meet diversified scene requirements.

Description

Technical Field

[0001] Embodiments of this disclosure relate to the field of communications, and more specifically, to access point devices and methods thereof, as well as computer program products. Background Technology

[0002] As Wi-Fi networks increasingly support real-time services, ensuring QoS for downlink traffic has become crucial for enhancing the experience of audio and video conferencing, cloud gaming, and other applications. To guarantee the transmission quality of critical streams, Mirrored Stream Classification Service (MSCS) has emerged.

[0003] MSCS mirrors the flow classification rules on the client side to the access point, enabling APs to accurately identify and prioritize downlink traffic using the same strategy. This end-to-network collaborative classification mechanism allows uplink and downlink data flows to use the same identification and scheduling mechanism, thereby improving end-to-end QoS assurance capabilities and providing stable and reliable wireless transmission support for latency-sensitive services such as audio / video, conferencing, and cloud gaming. However, there is still room for improvement in how to efficiently apply MSCS. Summary of the Invention

[0004] At least one embodiment of this disclosure provides a method performed by an access point (AP) device, wherein the AP device supports the Mirror Stream Classification Service (MSCS) function, and the method includes: obtaining MSCS function switch information, the MSCS function switch information being used to indicate whether the MSCS function of the AP device is turned on or off; and turning the MSCS function of the AP device on or off based on the MSCS function switch information.

[0005] For example, in some embodiments, the method further includes: in response to enabling the MSCS function of the AP device, notifying one or more clients that the AP device supports the MSCS function; and accepting an MSCS request initiated by an MSCS client among the one or more clients.

[0006] For example, in some embodiments, the method further includes: in response to disabling the MSCS function of the AP device, notifying one or more clients that the AP device does not support the MSCS function; and stopping the provision of MSCS services to the MSCS clients among the one or more clients.

[0007] For example, in some embodiments, stopping the provision of MSCS services to the MSCS client among the one or more clients includes: rejecting MSCS requests initiated by the MSCS client.

[0008] For example, in some embodiments, stopping the provision of MSCS services to the MSCS clients among the one or more clients includes: stopping the established MSCS rules and notifying the associated MSCS clients corresponding to the established MSCS rules that the established MSCS rules are interrupted.

[0009] For example, in some embodiments, notifying the associated MSCS client of the established MSCS rule that the established MSCS rule is interrupted in one or more MSCS clients includes: notifying the associated MSCS rule that the established MSCS rule is interrupted by sending a response message to the associated MSCS client; and / or disconnecting the AP device from the associated MSCS client.

[0010] For example, in some embodiments, the method further includes: in response to enabling the MSCS function of the AP device, stopping or allowing the provision of MSCS services to a subset of MSCS clients based on acquired rule configuration information, wherein the rule configuration information is used to indicate the rules for filtering out the subset of MSCS clients from the MSCS clients.

[0011] For example, in some embodiments, the rule configuration information is associated with at least one of the number of MSCS clients receiving MSCS services and the transmission rate of the MSCS clients receiving MSCS services.

[0012] For example, in some embodiments, the rule configuration information is a configuration list, which includes configuration entries, and the configuration entries contain the identifiers of the portion of the MSCS clients.

[0013] For example, in some embodiments, the method further includes: receiving a list configuration request, the list configuration request containing information for adding, modifying or deleting items in the configuration list; and adding, modifying or deleting items in the configuration list based on the list configuration request.

[0014] For example, in some embodiments, the configuration list includes a blacklist, and the step of stopping or allowing the provision of MSCS services to certain MSCS clients based on the acquired rule configuration information includes: rejecting MSCS requests initiated by MSCS clients that match the configuration entries in the blacklist; and / or accepting MSCS requests initiated by MSCS clients that do not match the configuration entries in the blacklist.

[0015] For example, in some embodiments, the configuration list includes a blacklist, and the step of stopping or allowing the provision of MSCS services to certain MSCS clients based on the acquired rule configuration information includes: determining whether an associated MSCS client of an established MSCS rule matches the configuration entry in the blacklist; and in response to the associated MSCS client matching the configuration entry in the blacklist, stopping the established MSCS rule and notifying the associated MSCS client that the established MSCS rule is interrupted.

[0016] For example, in some embodiments, the configuration list includes a whitelist, and wherein, based on the acquired rule configuration information, stopping or allowing the provision of MSCS services to certain MSCS clients includes: accepting MSCS requests initiated by MSCS clients that match the configuration entries in the whitelist; and / or rejecting MSCS requests initiated by MSCS clients that do not match the configuration entries in the whitelist.

[0017] For example, in some embodiments, the configuration list includes a whitelist, and the step of stopping or allowing the provision of MSCS services to certain MSCS clients based on the acquired rule configuration information includes: determining whether the associated MSCS client of an established MSCS rule matches the configuration entry in the whitelist; and in response to the associated MSCS client not matching the configuration entry in the whitelist, stopping the established MSCS rule and notifying the associated MSCS client that the established MSCS rule is interrupted.

[0018] At least one embodiment of this disclosure provides an access point (AP) device, including: one or more processors; and a memory; wherein the memory stores computer-readable instructions and is communicatively connected to the one or more processors; the one or more processors are configured to execute the computer-readable instructions stored in the memory to implement the method as described above.

[0019] For example, in some embodiments, the AP device is a router.

[0020] At least one embodiment of this disclosure provides a computer program product having instructions stored thereon that, when executed by a processor, cause the method described above to be performed. Attached Figure Description

[0021] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings of the embodiments of this disclosure will be briefly described below. Clearly, the drawings described below only relate to some embodiments of this disclosure and are not intended to limit the scope of this disclosure.

[0022] Figure 1 An exemplary architecture diagram of a wireless communication system is shown;

[0023] Figure 2A An exemplary interaction diagram between a STA and an AP that implements the MSCS function is shown;

[0024] Figure 2B A schematic diagram of an exemplary architecture for AP to perform MSCS mapping on downlink flows is shown;

[0025] Figure 2C This diagram illustrates an exemplary architecture where the AP does not perform MSCS mapping on the downlink flow;

[0026] Figure 3 A flowchart is shown of a method performed by an access point (AP) device according to at least one embodiment of the present disclosure;

[0027] Figure 4 A flowchart illustrating the MSCS function for activating an AP device according to at least one embodiment of the present disclosure is shown.

[0028] Figure 5 A flowchart illustrating the MSCS function for shutting down an AP device according to at least one embodiment of the present disclosure is shown.

[0029] Figure 6 A flowchart illustrating a blacklist function according to at least one embodiment of the present disclosure is shown;

[0030] Figure 7 A flowchart illustrating a whitelist function according to at least one embodiment of the present disclosure is shown;

[0031] Figure 8 A schematic diagram of an electronic device according to at least one embodiment of the present disclosure is shown. Detailed Implementation

[0032] Reference will now be made in detail to specific embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. Although the present disclosure will be described in conjunction with specific embodiments, it will be understood that it is not intended to limit the present disclosure to the described embodiments. Rather, it is intended to cover variations, modifications, and equivalents included within the spirit and scope of the present disclosure as defined by the appended claims. It should be noted that the method operations described herein can be implemented by any functional block or functional arrangement, and any functional block or functional arrangement can be implemented as a physical entity or a logical entity, or a combination of both.

[0033] To enable those skilled in the art to better understand this disclosure, the disclosure will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0034] Note that the examples described below are merely specific examples and are not intended to limit the embodiments of this disclosure to the specific shapes, hardware, connections, operations, values, conditions, data, sequences, etc., shown and described. Those skilled in the art can utilize the concepts of this disclosure to construct further embodiments not mentioned herein by reading this specification.

[0035] The terminology used in this disclosure is that which is currently widely used in the art in consideration of the functionality of this disclosure; however, these terms may vary depending on the intent, precedent, or new technology of those skilled in the art. Furthermore, specific terms may be chosen by the applicant, and in such cases, their detailed meanings will be described in the detailed description of this disclosure. Therefore, the terminology used in this specification should not be construed as simple names, but rather based on the meaning of the terms and the overall description of this disclosure.

[0036] This disclosure uses flowcharts to illustrate the operations performed by the system according to embodiments of this application. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, various steps can be processed in reverse order or simultaneously as needed. Furthermore, other operations can be added to these processes, or one or more steps can be removed from them.

[0037] In the description of this disclosure, it should be noted that terms such as “first,” “second,” and “third” are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Similarly, words such as “a,” “an,” or “the” do not indicate a quantity limitation but rather indicate the presence of one or more. Words such as “including” or “comprising” mean that the element or object preceding the word encompasses those elements or objects listed following the word and their equivalents, without excluding other elements or objects.

[0038] Discussions using terms such as “receive,” “send,” “determine,” “transfer,” “request,” “evaluate,” “trigger,” “establish,” “re-establish,” “enable,” or similar terms in this document may refer to the operation and / or processing of a computer, computing platform, computing system, or other electronic computing device that involves the manipulation and / or conversion of data represented as physical (e.g., electronic) quantities in computer registers and / or memory into physical quantities in computer registers and / or memory or other information storage media that may store instructions for performing the operation and / or processing. Terms such as “connect” and “link” are not limited to physical or mechanical connections but also include direct or indirect electrical connections.

[0039] The terminology used in this disclosure is that which is currently widely used in the art in consideration of the functionality of this disclosure; however, these terms may vary depending on the intent, precedent, or new technology of those skilled in the art. Furthermore, specific terms may be chosen by the applicant, and in such cases, their detailed meanings will be described in the detailed description of this disclosure. Therefore, the terminology used in this specification should not be construed as simple names, but rather based on the meaning of the terms and the overall description of this disclosure.

[0040] In this disclosure, an AP, interchangeably referred to as a Wireless Access Point (WAP), is a communication device capable of communicating with non-access point (non-AP) devices (e.g., stations (STAs) or clients) in a WLAN and allowing non-APs to connect to a wired network. An AP is typically connected as a standalone device to a router (via a wired network), but it can also be integrated with or used within a router. Similarly, in this disclosure, a non-AP (e.g., a client or station, interchangeably referred to as a STA) is a communication device that does not operate as an AP but can communicate with an AP to obtain various communication services (such as voice, video, packet data, messaging, broadcasting, etc.). An STA can be any device containing a Media Access Control (MAC) and Physical Layer (PHY) interface compliant with the IEEE 802.11 standard to the wireless medium (WM). For example, an STA can be a laptop computer, desktop personal computer (PC), personal digital assistant (PDA), access point, or Wi-Fi phone in a WLAN environment. STAs can be fixed or mobile. In a WLAN environment, the terms "STA," "client device," "wireless client," "client," "user," and "user equipment" are generally used interchangeably.

[0041] In this disclosure, a STA in a WLAN can function as an AP in different scenarios, and vice versa. This is because communication devices in the context of IEEE 802.11 (Wi-Fi) technology may include both STA and AP hardware components. In this way, the communication device can switch between STA mode and AP mode based on the actual WLAN conditions and / or requirements. In the various embodiments described below, STA may refer to a STA in a WLAN that is not implemented as an AP.

[0042] Figure 1 An exemplary architecture diagram of a wireless communication system is shown. Figure 1 As shown, the wireless communication system 100 includes an AP device (e.g., Figure 1 AP device 101) and client (e.g., Figure 1Clients 102 and 103 in the example can be used in, for example, IEEE 802.11 WLAN networks. An AP device is a device that provides services to clients, and clients can communicate with the AP device. It is understood that... Figure 1 The number of AP devices and clients is just an example.

[0043] AP device 101 can establish WLAN communication with clients 102 and 103, enabling the clients to connect to a wired network. This allows clients 102 and 103 to access various communication services from the Internet, including voice, video, packet data, messaging, and broadcasting. The clients in the embodiments of this disclosure have wireless transceiver functionality, can support protocols such as the IEEE 802.11 series, and can communicate with the AP device or another client. After clients 102 and 103 successfully associate with the AP through, for example, an IEEE 802.11 association process, data transmission can begin between clients 102 and 103 and the AP. This allows clients 102 and 103 to send data packets to and receive data packets from the network via the AP.

[0044] A client is any user communication device that allows a user to communicate with an AP, thereby communicating with a WLAN. For example, a client can be a user device capable of connecting to a network, including but not limited to, smartphones, tablets, desktop computers, laptops, notebooks, ultra-portable personal computers, handheld computers, netbooks, personal digital assistants, and other devices capable of connecting to the Internet. It can be an IoT node in the Internet of Things (IoT) or an in-vehicle communication device in the Internet of Vehicles (IoV). An AP device is a device that serves the client and may support the IEEE 802.11 series of protocols. For example, an AP device can be a communication entity such as a communication server, router, switch, or bridge, or it can include various forms of macro base stations, micro base stations, repeaters, etc. Alternatively, an AP device can be a chip and processing system in various forms of devices to implement the methods and functions in the embodiments of this disclosure. In this document, the term "data packet" may refer to "data frame," etc.

[0045] Figure 1 The architecture shown is illustrative only and does not impose any limitation on any embodiments of this disclosure. Multiple access points (APs) in a WLAN network can serve specific associated client sets, and the number of clients in each service set can be greater than the single client shown in the figure, depending on application requirements and overall network constraints.

[0046] exist Figure 1In the architecture shown, Wi-Fi Quality of Service (QoS) management technology can be applied, for example, between clients 102 and 103 and AP device 101. Wi-Fi QoS management technology extends the functionality of Wi-FiCERTIFIED WMM™, simplifying the prioritization and management of latency-sensitive Internet Protocol (IP) traffic in Wi-Fi networks. For example, it can classify IP data flows and map them to one of the QoS access categories defined by WMM® to help ensure that traffic for real-time applications and services is inserted into higher-priority queues, resulting in a better end-user experience. Here, WMM is a subset of IEEE 802.11e developed by the Wi-Fi Alliance, called the WMM (Wi-Fi Multimedia) specification, used to guarantee the prioritization of data packets in WLANs.

[0047] MSCS is a technology in Wi-Fi Quality of Service (QoS) management used to improve downlink QoS consistency. Specifically, MSCS is based on the concept of "mirroring" or "reflection" QoS, where access points (APs) derive QoS rules for downlink IP flows by monitoring the corresponding uplink IP flows sent by clients. For example, this can be achieved by monitoring the "User Priority" (UP) field in the IP header and the IEEE 802.11 MAC header.

[0048] User priority here refers to a priority label used to distinguish different data streams. User priority is typically used to differentiate quality of service (QoS) to ensure that different types of data streams receive different levels of service (e.g., transmission) according to their importance. Specifically, user priority is a field defined based on the IEEE 802.1p standard, which can classify data streams into eight priority levels, from 0 to 7.

[0049] Figure 2A A schematic diagram illustrating an exemplary interaction between a STA and an AP that implements the MSCS function is shown. For example, Figure 2A The STA shown can be Figure 1 One of the clients 102 and 103 in the game. Figure 2A The AP shown can be Figure 1 The AP device 101 in the diagram is included, but is not limited to this.

[0050] See Figure 2A To implement the MSCS function, the exemplary interaction process between the STA and the AP is as follows:

[0051] In step S202, the STA can send an Association Request to the AP, which carries information about its ability to support MSCS.

[0052] In step S204, the AP can return an association response to the STA, confirming that it also supports MSCS capabilities, thus completing the capability negotiation between the two parties.

[0053] In step S206, the AP may send an MSCS request to the STA.

[0054] In step S208, the STA can return the corresponding MSCS response to the AP to confirm the MSCS request.

[0055] In step S210, the STA can send uplink QoS data (also known as uplink traffic or uplink flow) to the AP, which includes the flow classification rules defined on the client side.

[0056] In step S212, the AP receives and parses the uplink traffic, and modifies / maps the UP of the corresponding downlink QoS data (also known as downlink traffic or downlink flow) to be the same as the UP of the uplink traffic, so as to apply it to downlink QoS data scheduling.

[0057] In step S214 and optional step S216, the AP may send downlink traffic to the STA with a modified UP value.

[0058] exist Figure 2A MSCS mapping can be implemented in the middle, and the following is an example. Figure 2B An example is provided for illustration. Figure 2B A schematic diagram of an exemplary architecture for AP to perform MSCS mapping on downlink flows is shown.

[0059] See Figure 2B When both the AP and STA support the MSCS function, in the uplink direction (STA→AP), the uplink UP=6 and is assigned to the AC_VO queue. The AP can modify / map the corresponding downlink UP to be the same as the uplink UP (6), thus ensuring that in the downlink direction (AP→STA), the downlink UP=6 and is assigned to the AC_VO queue. This ensures that both uplink and downlink flows are transmitted with high user priority, reducing latency and improving the wireless user experience for clients using MSCS-enabled clients (hereinafter referred to as MSCS clients).

[0060] The value of UP can be determined based on a User Priority Bitmap and a User Priority Limit. The User Priority Bitmap can be, for example, 8 bits representing which UP values ​​from 0 to 7 are allowed / enabled. For example, if the User Priority Bitmap = 11110000, it means only UP values ​​4, 5, 6, and 7 are allowed. The User Priority Limit specifies the highest allowed UP priority. For example, if the User Priority Limit = 6, it means that among the allowed user priorities, the highest is UP = 6.

[0061] and Figure 2B In contrast, Figure 2C This diagram illustrates an exemplary architecture where the AP does not perform MSCS mapping on the downlink flow.

[0062] See Figure 2C ,and Figure 2B Similarly, in the uplink direction (STA→AP), the uplink UP=6 and is assigned to the AC_VO queue. However, when the AP does not support the MSCS function, the AP cannot modify the corresponding downlink UP to 6 based on the uplink UP=6; it retains the default UP=0 and assigns the downlink to the AC_BE queue. In this case, the downlink cannot be transmitted via high-user priority, resulting in data transmission latency and thus failing to further improve the user's wireless experience.

[0063] The inventors of this disclosure recognized during their research that, as described above, the introduction of the MSCS function improves the user's wireless experience. However, the application of the MSCS function on the STA and AP sides is still in its early stages. Specifically, currently only a few types of STAs on the market support the MSCS function, and even fewer APs support it. Furthermore, if an AP device supports the MSCS function, it typically needs to serve both STAs that support the MSCS function (hereinafter referred to as MSCS clients) and STAs that do not support the MSCS function (hereinafter referred to as non-MSCS clients), especially since currently only a few types of STAs support the MSCS function. In this situation, while the introduction of the MSCS function can effectively reduce the latency of MSCS clients, it will also reduce the performance latency of other non-MSCS clients because the uplink and downlink traffic uplink / down ...

[0064] In view of this, at least one embodiment of the present disclosure provides an access point device and a method thereof, as well as a computer program product, which enables the opening and closing of the MSCS function of the AP device that supports the MSCS function through MSCS function switch information, so as to flexibly control the opening and closing of the MSCS function of the AP device to meet diverse scenario requirements.

[0065] Figure 3 A flowchart illustrating a method performed by an access point (AP) device according to at least one embodiment of the present disclosure is shown. The AP device supports MSCS functionality. Here, "supports" means having the hardware configuration and / or software modules that implement MSCS functionality, capable of performing data processing, control logic, or protocol interactions related to MSCS functionality. For example, in conjunction with... Figure 3 The described client or STA can be Figure 1 One of the clients 102 and 103 in the middle, combined Figure 3 The described AP device can be Figure 1 The AP device 101 in the diagram is included, but is not limited to this.

[0066] See Figure 3 The method 300 includes steps S310 to S320.

[0067] In step S310, the MSCS function switch information is obtained, which is used to indicate whether the MSCS function of the AP device is turned on or off.

[0068] AP devices can obtain MSCS function switch information in various ways, and this disclosure does not limit the source of MSCS function switch information.

[0069] In some embodiments, the AP device can obtain MSCS function switch information from an external source. In one example, a user can manage the AP device using an application (APP) or webpage on their user terminal, input the MSCS function switch information, and transmit this information to the AP device, thus enabling the AP device to obtain the MSCS function switch information. In another example, a user can generate MSCS function switch information by pressing a physical button on the AP device and then transmit this information to the AP device, thereby enabling the AP device to obtain the MSCS function switch information.

[0070] In other embodiments, the AP device can obtain MSCS function switch information from within the AP device itself. In one example, the AP device may have preset rules or logic, based on which it can automatically generate and obtain MSCS function switch information. For example, the preset rules or logic may be associated with a large number of currently served MSCS clients and / or a high data rate. In one instance, when the number of currently served MSCS clients is large and / or the data rate is high, the AP device can predict a degraded user experience for non-MSCS clients. In this case, the AP device can internally determine that the preset rule is met, and generate and obtain the MSCS function switch information. In this way, the AP device can automatically control the activation and deactivation of the MSCS function without user intervention. As another example, the preset rules or logic may be associated with time. In one instance, the AP device can generate and obtain MSCS function switch information within a predetermined time period or point in time.

[0071] In step S320, the MSCS function of the AP device is turned on or off based on the MSCS function switch information.

[0072] As mentioned above, the MSCS function of the exemplary AP device is always enabled, which exacerbates the performance latency of the non-MSCS clients.

[0073] In contrast, in this embodiment, the MSCS function of the AP device can be flexibly enabled or disabled using MSCS function switch information, thereby adapting to diverse scenario requirements. For example, when the demand prioritizes meeting the service needs of MSCS clients, the MSCS function of the AP device can be enabled using the MSCS function switch information. Conversely, when the demand balances the service needs of non-MSCS clients, the MSCS function of the AP device can be disabled using the MSCS function switch information.

[0074] To implement the MSCS function, in some embodiments, the method 300 may further include: in response to enabling the MSCS function of the AP device, notifying one or more clients that the AP device supports the MSCS function; and accepting MSCS requests initiated by MSCS clients among the one or more clients. In this embodiment, after enabling the MSCS function of the AP device, MSCS requests initiated by MSCS clients can be accepted to provide MSCS services to the MSCS clients, thereby effectively reducing the latency of the MSCS clients. The following is in conjunction with... Figure 4 An exemplary description is provided.

[0075] Figure 4 A flowchart illustrating the MSCS function for activating an AP device according to at least one embodiment of the present disclosure is shown. For example, Figure 4 The client shown can be Figure 1 One of the clients 102 and 103 in the game. Figure 4 The AP shown can be Figure 1 The AP device 101 in the diagram is included, but is not limited to this.

[0076] See Figure 4 In step S402, the user can transmit the MSCS function switch information to the AP device through the user terminal's APP or webpage to enable the MSCS function of the AP device.

[0077] In step S404, after enabling the MSCS function, the AP device can notify external parties that it supports the MSCS function. For example, the AP device can send a beacon frame to notify external parties that it supports the MSCS function. Accordingly, clients near the AP device (e.g., including MSCS clients and non-MSCS clients) can receive this notification.

[0078] In step S406, the MSCS client that needs to connect to the AP device can initiate an MSCS request to the AP device.

[0079] In step S408, the AP device can accept the MSCS request initiated by the MSCS client, establish MSCS rules, and reply to the corresponding MSCS client with an MSCS response.

[0080] In step S410, after receiving the MSCS response, the corresponding MSCS client can send uplink traffic to the AP device. The uplink traffic may include information about the UP value.

[0081] In step S412, the AP device can map the UP value of the uplink traffic to the UP value of the downlink traffic and assign the downlink traffic to the corresponding WMM queue.

[0082] To refuse or prevent the execution of the MSCS function, in some embodiments, the method 300 may further include: in response to disabling the MSCS function of the AP device, notifying one or more clients that the AP device does not support the MSCS function; and stopping the provision of MSCS services to MSCS clients among the one or more clients. In this embodiment, after disabling the MSCS function of the AP device, the provision of MSCS services to MSCS clients can be stopped, thereby effectively reducing latency for, for example, non-MSCS clients. The following is in conjunction with... Figure 5 An exemplary description is provided.

[0083] Figure 5 A flowchart illustrating the MSCS function for shutting down an AP device according to at least one embodiment of the present disclosure is shown. For example, Figure 5 The client shown can be Figure 1 One of the clients 102 and 103 in the game. Figure 5 The AP shown can be Figure 1 The AP device 101 in the diagram is included, but is not limited to this.

[0084] See Figure 5 In step S502, the user can transmit MSCS function switch information to the AP device through the user terminal's APP or webpage to disable the MSCS function of the AP device.

[0085] Subsequently, the AP device can stop providing MSCS services to the MSCS client. The various aspects of stopping the provision of MSCS services to the MSCS client will be described below with reference to steps S504 to 512.

[0086] In some embodiments, different implementations can be used to stop providing MSCS services to the MSCS client based on whether the AP device has already established MSCS rules with the MSCS client.

[0087] For example, in one embodiment, stopping the provision of MSCS services to one or more MSCS clients may include: stopping established MSCS rules and notifying the associated MSCS clients corresponding to the established MSCS rules that the established MSCS rules are interrupted. In this embodiment, after disabling the MSCS function of the AP device, for MSCS clients with which the AP device has established MSCS rules, all established MSCS rules are stopped (e.g., deleted or not used), and the corresponding MSCS clients (i.e., associated MSCS clients) are notified.

[0088] For example, return Figure 5 In step S504, after disabling the MSCS function, the AP device can notify external parties that it does not support the MSCS function. For example, the AP device can notify external parties that it does not support the MSCS function without sending a beacon frame. MSCS clients can receive this notification.

[0089] In step S506, the AP device can stop the established MSCS rules.

[0090] In step S508, the AP device may notify the associated MSCS client corresponding to the established MSCS rule that the established MSCS rule has been interrupted.

[0091] Additionally, in step S508, the interruption of an established MSCS rule can be notified in various ways. In some embodiments, notifying one or more associated MSCS clients of the interruption of an established MSCS rule can include: notifying the interruption of the established MSCS rule by sending a response message to the associated MSCS client; and / or directly disconnecting the AP device from the associated MSCS client. In this embodiment, the interruption of the MSCS rule can be flexibly notified in an explicit or implicit manner.

[0092] For example, in one embodiment, stopping the provision of MSCS services to one or more MSCS clients may include rejecting MSCS requests initiated by the MSCS clients. In this embodiment, after disabling the MSCS function of the AP device, for MSCS clients with which the AP device has not established MSCS rules, the provision of MSCS services to the MSCS clients can be stopped by rejecting the MSCS requests initiated by the MSCS clients.

[0093] For example, return Figure 5 In step S510, the MSCS client that needs to connect to the AP device can initiate an MSCS request to the AP device.

[0094] In step S512, the AP device may reject the MSCS request initiated by the MSCS client. Additionally, in step S512, the AP device may choose not to reply to the corresponding MSCS client, or it may reply to the corresponding MSCS client with an MSCS response to notify of the rejection.

[0095] It is worth noting that in step S512, the MSCS client with which the AP device rejects its MSCS request can be an MSCS client with which the AP device has not established an MSCS rule, or it can be an MSCS client with which the AP device has established an MSCS rule (i.e., an associated MSCS client). For example, even if the AP device notifies the associated MSCS client that the established MSCS rule is interrupted, the associated MSCS client may still have a need to continue sending MSCS requests to the AP device to request the AP device to provide it with MSCS services. Therefore, in this embodiment, the AP device can still reject the MSCS request from the associated MSCS client to stop providing it with MSCS services.

[0096] The inventors of this disclosure further recognize that, after enabling the MSCS function, the exemplary AP device responds to all MSCS requests initiated by MSCS clients and establishes corresponding MSCS rules. Therefore, when multiple MSCS clients send high-priority uplink traffic to the AP device, and the AP device sends a large amount of high-priority downlink traffic to the MSCS clients, it significantly reduces the performance and latency of other clients (e.g., low-priority MSCS clients or non-MSCS clients). This is especially problematic when the 2GHz band channels are congested, resulting in a very poor experience for other clients.

[0097] The aforementioned scenarios where MSCS functionality is enabled have caused several issues. For example, if a user's client does not support MSCS (i.e., is a non-MSCS client), in congested channel conditions, other users' MSCS clients may be associated with the access point (AP), leading to a degraded wireless experience for that user. Similarly, even if a user's client supports MSCS (i.e., is an MSCS client), the presence of other MSCS clients with stronger channel contention capabilities (i.e., high-priority MSCS clients) associated with the AP and consuming significant amounts of high-priority bandwidth will also negatively impact the user's wireless experience. Therefore, addressing how to mitigate or avoid negative impacts on the wireless experience of low-priority MSCS clients or non-MSCS clients while enabling MSCS functionality is a pressing issue.

[0098] In view of this, in some embodiments, the AP device can be allowed to accept only some requests from MSCS clients, or reject some requests from MSCS clients, thereby mitigating or avoiding the degradation of the wireless user experience of low-priority MSCS clients or non-MSCS clients caused by the addition of other MSCS clients.

[0099] Therefore, in one embodiment, the method 300 may further include: in response to enabling the MSCS function of the AP device, stopping or allowing the provision of MSCS services to some MSCS clients based on the acquired rule configuration information, wherein the rule configuration information is used to indicate the rules for filtering out some MSCS clients from the MSCS clients.

[0100] In this embodiment, the AP device can filter out a subset of MSCS clients from one or more MSCS clients based on acquired rule configuration information to accept or reject their MSCS requests, instead of the example AP device accepting MSCS requests from all MSCS clients in one or more MSCS clients. This establishes an MSCS client filtering mechanism to mitigate or avoid the degradation of the wireless user experience for low-priority MSCS clients or non-MSCS clients caused by the addition of other MSCS clients. More specifically, this filtering mechanism can allow only some clients to use the MSCS function. In bandwidth-congested environments, it can improve the performance of designated clients, reduce latency, and prevent other clients with stronger channel occupancy capabilities from using the MSCS function to send large amounts of high-priority traffic, thus reducing the original client's wireless user experience.

[0101] It is worth noting that while the above-described filtering mechanism is presented in the context of an AP device equipped with its MSCS function enabled or disabled, this disclosure is not limited thereto. For example, the filtering mechanism can be applied to AP devices that are not equipped with their MSCS function enabled or disabled. For instance, the filtering mechanism can be applied to AP devices where the MSCS function is always enabled, thereby similarly mitigating or avoiding the degradation of the wireless user experience for low-priority MSCS clients or non-MSCS clients due to the addition of other MSCS clients.

[0102] The method for obtaining rule configuration information can be the same as or similar to the method for obtaining MSCS function switch information described above, and will not be repeated here.

[0103] The rule configuration information in the above embodiments can be diverse, as long as it can help mitigate or avoid the degradation of the wireless user experience of low-priority MSCS clients or non-MSCS clients caused by the addition of other MSCS clients.

[0104] For example, in one embodiment, the rule configuration information is associated with at least one of the number of MSCS clients accepting MSCS services and the transmission rate of the MSCS clients accepting MSCS services.

[0105] In this embodiment, rule configuration information can be set by limiting the number of MSCS clients receiving MSCS services and / or the transmission rate of MSCS clients receiving MSCS services. In reality, the number of clients served by an AP device (e.g., MSCS clients and / or non-MSCS clients) and the bandwidth it can support for data transmission are limited. When a large number of clients connect to the AP device, the AP device will prioritize transmitting data with MSCS clients and delay transmitting data with non-MSCS clients, or the AP device will prioritize transmitting data with high-priority MSCS clients and delay transmitting data with low-priority MSCS clients and non-MSCS clients. By limiting the number of MSCS clients and / or the transmission rate of MSCS clients, the degradation of the wireless user experience for low-priority MSCS clients or non-MSCS clients caused by the addition of other MSCS clients can be effectively mitigated or avoided.

[0106] In some examples, the rule configuration information can be the maximum number of MSCS clients accepting MSCS services, such as 10, 20, 50, 100, or other numbers. When the number of MSCS clients currently establishing MSCS rules reaches this maximum, MSCS requests from other MSCS clients can be rejected. Alternatively, MSCS clients can be randomly retained or deactivated to control the number of MSCS clients accepting MSCS services within this maximum. In some examples, the rule configuration information can be the maximum transmission rate for MSCS clients accepting MSCS services, such as 100 Mbps or other transmission rates. When the transmission rate of a particular MSCS client exceeds this maximum transmission rate, MSCS services can be stopped for that MSCS client.

[0107] Regarding the addition or substitution of rule configuration information, in one embodiment, the rule configuration information may be a configuration list, which includes configuration entries, and the configuration entries contain identifiers of some MSCS clients.

[0108] In this embodiment, certain MSCS clients can be identified through configuration entries in the configuration list, i.e., MSCS clients whose requests are to be accepted or rejected. In fact, identifying certain MSCS clients through a configuration list enables fine-grained management. For example, users can record the identifiers of MSCS clients whose requests are to be accepted or rejected in the configuration entries included in the configuration list to achieve fine-grained management of those specific MSCS clients. Furthermore, to determine whether an MSCS client meets the rule configuration information, only the identifier of the MSCS client needs to be matched with the configuration entries in the configuration list. This approach has the characteristics of low computational load and fast response, making it suitable for real-time verification and high-frequency judgment scenarios. In addition, the configuration list is easy to dynamically maintain and flexibly configure. For example, the filtering strategy can be adjusted simply by configuring the content of the configuration entries included in the list, without modifying the AP device's program / hardware.

[0109] In some examples, the identifier includes, but is not limited to, the client's MAC address and the client's source IP address. Additionally, the identifier may be carried in fields within management frames sent by the client to the AP device.

[0110] To maintain and flexibly configure the configuration list, in some embodiments, the method 300 may further include: receiving a list configuration request, the list configuration request containing information for adding, modifying, or deleting items from the configuration list; and performing additions, modifications, or deletions on the configuration list based on the list configuration request. In this embodiment, users can maintain and flexibly configure the configuration list by sending a list configuration request to the AP device, thereby specifying desired filtering strategies. For example, users can send a list configuration request to the AP device via an APP or webpage to manage or configure the configuration list.

[0111] For example, in some embodiments, the AP device may include a request module for receiving a list configuration request sent by an external entity (e.g., a user). Additionally, the AP device may include a response module for processing the list configuration request received by the request module and performing corresponding addition, modification, or deletion operations on the configured list based on the list configuration request.

[0112] The configuration list in the above embodiments may include a blacklist and / or a whitelist, and may be used to stop providing MSCS services to some MSCS clients based on whether the AP device has established MSCS rules with the MSCS client.

[0113] For example, in some embodiments, the configuration list may include a blacklist, and the process of stopping or allowing the provision of MSCS services to certain MSCS clients based on the acquired rule configuration information may include: determining whether an associated MSCS client of an established MSCS rule matches a configuration entry in the blacklist; and, in response to an associated MSCS client matching a configuration entry in the blacklist, stopping the established MSCS rule and notifying the associated MSCS client that the established MSCS rule has been interrupted. In this embodiment, after enabling the MSCS function of the AP device, for MSCS clients with which the AP device has already established MSCS rules, the established MSCS rules of the MSCS clients in the blacklist can be stopped (e.g., deleted or not used), and the corresponding MSCS clients (i.e., associated MSCS clients) can be notified to stop providing MSCS services to the corresponding MSCS clients, thereby effectively mitigating or avoiding the degradation of the wireless user experience of low-priority MSCS clients or non-MSCS clients due to the addition of other MSCS clients. The following is in conjunction with... Figure 6 An exemplary description is provided.

[0114] Figure 6 A flowchart illustrating a blacklist function according to at least one embodiment of the present disclosure is shown. For example, Figure 6 The client shown can be Figure 1 One of the clients 102 and 103 in the game. Figure 6 The AP shown can be Figure 1 The AP device 101 in the diagram is included, but is not limited to this.

[0115] See Figure 6 In step S602, the user can add the AP device to the blacklist through the user terminal's APP or webpage to put the AP device into blacklist mode. For example, step S602 can be an example of the rule configuration information obtained above.

[0116] In step S604, the AP device can traverse the blacklist and stop the established MSCS rules for MSCS clients in the blacklist.

[0117] In step S606, the AP device can notify the associated MSCS clients in the blacklist that the established MSCS rules have been interrupted.

[0118] Similar to step S508, in step S606, the MSCS rule interruption can be flexibly notified either explicitly or implicitly, which will not be elaborated here.

[0119] For example, steps S604 and S606 could be an example of the above-described method of stopping or allowing the provision of MSCS services to some MSCS clients.

[0120] For example, in some embodiments, the configuration list may include a blacklist, and the decision to stop or allow the provision of MSCS services to certain MSCS clients based on the acquired rule configuration information may include: rejecting MSCS requests initiated by MSCS clients that match the configuration entries in the blacklist; and / or accepting MSCS requests initiated by MSCS clients that do not match the configuration entries in the blacklist. In this embodiment, after enabling the MSCS function of the AP device, for MSCS clients with which the AP device has not established MSCS rules, the blacklist can be used to precisely stop or allow the provision of MSCS services to certain MSCS clients, thereby effectively mitigating or avoiding the degradation of the wireless user experience of low-priority MSCS clients or non-MSCS clients due to the addition of other MSCS clients.

[0121] For example, return Figure 6 In step S608, MSCS clients on the blacklist can initiate MSCS requests.

[0122] In step S610, the AP device may reject MSCS requests initiated by MSCS clients on the blacklist. In step S610, the AP device may choose not to reply to the corresponding MSCS client, or it may reply to the corresponding MSCS client with an MSCS response to notify of the rejection.

[0123] It is worth noting that, similar to step S512, in step S610, the MSCS client that the AP device rejects its MSCS request can be an MSCS client in the blacklist with which the AP device has not established an MSCS rule, or it can be an MSCS client in the blacklist with which the AP device has established an MSCS rule (i.e., an associated MSCS client).

[0124] In step S612, MSCS clients not on the blacklist can initiate an MSCS request to the AP device.

[0125] In step S614, the AP device can accept the MSCS request, establish MSCS rules, and reply with an MSCS response to the corresponding MSCS client.

[0126] For example, steps S608 and S610 and / or steps S612 and S614 could be an example of the above-described cessation or permission to provide MSCS services to certain MSCS clients.

[0127] In contrast to a blacklist, in some embodiments, the configuration list may include a whitelist. Based on the acquired rule configuration information, stopping or allowing the provision of MSCS services to certain MSCS clients may include: determining whether an associated MSCS client with an established MSCS rule matches a configuration entry in the whitelist; and, in response to an associated MSCS client not matching a configuration entry in the whitelist, stopping the established MSCS rule and notifying the associated MSCS client that the established MSCS rule is interrupted. In this embodiment, after enabling the MSCS function of the AP device, for MSCS clients with which the AP device has already established MSCS rules, the established MSCS rules for MSCS clients outside the whitelist can be stopped (e.g., deleted or not used), and the corresponding MSCS clients (i.e., associated MSCS clients) can be notified to stop providing MSCS services to the corresponding MSCS clients. This effectively mitigates or avoids the degradation of the wireless user experience for low-priority MSCS clients or non-MSCS clients caused by the addition of other MSCS clients. The following is in conjunction with... Figure 7 An exemplary description is provided.

[0128] Figure 7 A flowchart illustrating a whitelist function according to at least one embodiment of the present disclosure is shown. For example, Figure 7 The client shown can be Figure 1 One of the clients 102 and 103 in the game. Figure 7 The AP shown can be Figure 1 The AP device 101 in the diagram is included, but is not limited to this.

[0129] See Figure 7 In step S702, the user can add the AP device to the whitelist through the user terminal's APP or webpage to enable the AP device to enter whitelist mode. For example, step S702 can be an example of the rule configuration information obtained above.

[0130] In step S704, the AP device can traverse the whitelist and stop the established MSCS rules for MSCS clients that are not in the whitelist.

[0131] In step S706, the AP device can notify the associated MSCS client that is not in the whitelist that the established MSCS rule has been interrupted.

[0132] Similar to step S508, in step S706, the MSCS rule interruption can be flexibly notified either explicitly or implicitly, which will not be elaborated here.

[0133] For example, steps S704 and S706 could be an example of the above-described method of stopping or allowing the provision of MSCS services to some MSCS clients.

[0134] For example, in some embodiments, the configuration list may include a whitelist, and wherein, based on the acquired rule configuration information, stopping or allowing the provision of MSCS services to certain MSCS clients may include: accepting MSCS requests initiated by MSCS clients that match the configuration entries in the whitelist; and / or rejecting MSCS requests initiated by MSCS clients that do not match the configuration entries in the whitelist. In this embodiment, after enabling the MSCS function of the AP device, for MSCS clients with which the AP device has not established MSCS rules, the whitelist can be used to precisely stop or allow the provision of MSCS services to certain MSCS clients, thereby effectively mitigating or avoiding the degradation of the wireless user experience of low-priority MSCS clients or non-MSCS clients caused by the addition of other MSCS clients.

[0135] For example, return Figure 7 In step S708, MSCS clients not on the whitelist can initiate an MSCS request to the AP device.

[0136] In step S710, the AP device may reject the MSCS request. Additionally, in step S710, the AP device may choose not to reply to the corresponding MSCS client, or it may reply to the corresponding MSCS client with an MSCS response to notify of the rejection.

[0137] It is worth noting that, similar to steps S512 and S610, in step S710, the MSCS client that the AP device rejects its MSCS request can be an MSCS client in the whitelist with which the AP device has not established an MSCS rule, or it can be an MSCS client in the whitelist with which the AP device has established an MSCS rule (i.e., an associated MSCS client).

[0138] In step S712, whitelisted MSCS clients can initiate MSCS requests to the AP device.

[0139] In step S714, the AP device can accept the MSCS request, establish MSCS rules, and reply with an MSCS response to the corresponding MSCS client.

[0140] For example, steps S708 and S710 and / or steps S712 and S714 could be an example of the above-mentioned cessation or permission to provide MSCS services to some MSCS clients.

[0141] At least one embodiment of this disclosure also provides a computer program product having instructions stored thereon that, when executed by a processor, cause the execution of a method and additional aspects thereof performed by an access point (AP) device according to at least one embodiment of this disclosure.

[0142] At least one embodiment of this disclosure also provides an electronic device. Figure 8 A schematic diagram of an electronic device according to at least one embodiment of the present disclosure is shown. In some embodiments, the electronic device may be an access point device, such as... Figure 1 The AP device 101 in the diagram is such as a router. Additionally or alternatively, this electronic device can be a client (e.g., Figure 1 (One of clients 102 and 103 in the middle).

[0143] like Figure 8 As shown, the electronic device 800 includes at least one processor 820 and a memory 810. The memory 810 stores computer-readable instructions and is communicatively connected to the processor 820. The processor 820 executes the computer-readable instructions stored in the memory 810 to implement a method and additional aspects thereof performed by an access point (AP) device according to at least one embodiment of the present disclosure.

[0144] For example, the memory 810 and the processor 820 can communicate with each other directly or indirectly. For example, in some examples, such as... Figure 8 As shown, the electronic device 800 may also include a system bus 830, through which the memory 810 and the processor 820 can communicate with each other. For example, the processor 820 can access the memory 810 through the system bus 830. For example, in other examples, components such as the memory 810 and the processor 820 can communicate through a network on-chip (NOC) connection.

[0145] For example, processor 820 can control other components in electronic device 800 to perform desired functions. Processor 820 can be a device with data processing and / or program execution capabilities, such as a central processing unit (CPU), tensor processor (TPU), network processor (NP), or graphics processing unit (GPU), or it can be a digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0146] For example, memory 810 may include any combination of one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, erasable programmable read-only memory (EPROM), portable compact disc read-only memory (CD-ROM), USB memory, flash memory, etc.

[0147] For example, one or more computer-readable instructions can be stored on memory 810, and processor 820 can execute the computer-readable instructions to perform various functions. Various application programs and various data, such as instruction processing code and various data used and / or generated by the application programs, can also be stored in the computer-readable storage medium.

[0148] For example, some computer instructions stored in memory 810, when executed by processor 820, can perform one or more steps of the method and its additional aspects as described above by the access point AP device.

[0149] For example, such as Figure 8 As shown, the electronic device 800 may further include an input interface 840 that allows external devices to communicate with the electronic device 800. For example, the input interface 840 may be used to receive instructions from an external computer device, a user, etc. The electronic device 800 may also include an output interface 850 that enables the electronic device 800 to connect to one or more external devices. For example, the electronic device 800 can communicate via the output interface 850, etc.

[0150] It should be noted that the electronic device 800 according to at least one embodiment of the present disclosure is exemplary and not restrictive. Depending on the actual application needs, the electronic device 800 may also include other conventional components or structures. For example, in order to realize the necessary functions of the electronic device, those skilled in the art may set other conventional components or structures according to the specific application scenario. The embodiments of the present disclosure do not limit this.

[0151] At least one embodiment of this disclosure also provides a computer-readable storage medium. This computer-readable storage medium stores computer-readable instructions that, when executed by a computer (including a processor), can implement a method and additional aspects thereof performed by an access point (AP) device according to at least one embodiment of this disclosure.

[0152] For example, one or more computer-readable instructions may be stored on a computer-readable storage medium. Some of the computer-readable instructions stored on the computer-readable storage medium may be, for example, instructions for implementing one or more steps in the methods described above.

[0153] For example, a computer-readable storage medium may include the storage component of a tablet computer, a hard disk of a personal computer, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), optical disc read-only memory (CD-ROM), flash memory, or any combination of the above computer-readable storage media, or other suitable storage media. For example, a computer-readable storage medium may include the memory 810 in the above-described electronic device 800.

[0154] This disclosure can be a system, method, and / or computer program product at any possible level of integrated technical detail. A computer program product may include computer-readable program instructions for causing a processor to perform various aspects of this disclosure.

[0155] Unless otherwise stated, an element mentioned in the singular is not intended to mean "one and only one," but rather "one or more." Similarly, a plural reference to an element does not mean "more than one," but rather "one or more," unless otherwise stated or contradicting description elsewhere. Terms such as "if," "when," and "although" should be interpreted as "under the condition of," rather than implying an immediate temporal relationship or response. That is, these phrases, such as "when," do not imply an immediate action in response to an action occurring or during an action, but merely imply that an action will occur if the condition is met, but does not require a specific or immediate time constraint for the action to occur. Combinations, such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof," include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Combinations such as “at least one of A, B or C”, “one or more of A, B or C”, “at least one of A, B and C”, “one or more of A, B and C” and “A, B, C or any combination thereof” can be only A, only B, only C, A and B, A and C, B and C or A, B and C, wherein any such combination may contain one or more members of A, B or C.

[0156] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the possible structures, functions, and operations of the methods and apparatus according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, a program segment, or a portion of code containing at least one executable instruction for implementing a specified logical function. It should also be noted that in some alternative embodiments, the functions described in a block may occur in a different order than those described in the accompanying drawings. For example, two blocks shown consecutively may actually be executed in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a dedicated hardware system that performs the specified function or operation, or by a combination of dedicated hardware and computer instructions.

[0157] The various embodiments described in this disclosure are for illustrative purposes and are not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope of the described embodiments. The terminology used herein is chosen to best explain the principles of the embodiments, their practical application, or improvements to techniques found in the market, or to enable those skilled in the art to understand the embodiments disclosed herein.

[0158] Throughout the description and claims of this specification, the word “comprising” and variations thereof, such as “comprising” and “including,” means “including, but not limited to,” and are not intended to exclude, for example, other additives, components, integers, or steps. “Exemplary” means “an example of a preferred or ideal implementation and is not intended to convey its indication.” “Like” is not used in a limiting sense but for interpretative purposes.

[0159] As used in this disclosure, the term "determine" can include a variety of operations. For example, "determine," calculation, operation, processing, derivation, investigation, search (e.g., searching in a table, database, or other data structure), and ascertainment are all considered "determine." Additionally, "determine" also refers to receiving (e.g., receiving information), sending (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory). Furthermore, "determine" can also refer to parsing, selecting, picking, building, and comparing. In other words, several actions can be considered "determine."

[0160] As used in this disclosure, terms such as “connection,” “coupling,” or any variations thereof refer to any direct or indirect connection or combination between two or more units, which may include situations where one or more intermediate units exist between two units that are “connected” or “coupled” to each other. The coupling or connection between units may be physical or logical, or a combination of both. As used in this disclosure, two units may be considered electrically connected by means of one or more wires, cables, and / or printing, and as numerous non-limiting and non-exhaustive examples, may be “connected” or “coupled” to each other by means of electromagnetic energy in the radio frequency region, microwave region, and / or light (visible and invisible) region, etc.

[0161] The present disclosure has been described in detail above, but it will be apparent to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description in this disclosure is illustrative and has no limiting effect on the present disclosure.

[0162] In addition to the exemplary descriptions above, the following points should be noted regarding this disclosure:

[0163] (1) The accompanying drawings of the embodiments of this disclosure only involve the structures involved in the embodiments of this disclosure. Other structures can be referred to the general design.

[0164] (2) Where there is no conflict, the embodiments of this disclosure and the features in the embodiments can be combined with each other to obtain new embodiments.

[0165] The above description is merely an exemplary embodiment of this disclosure and is not intended to limit the scope of protection of this disclosure, which is determined by the appended claims.

Claims

1. A method executed by an access point (AP) device, wherein, The AP device supports the Mirror Stream Classification Service (MSCS) function, and the method includes: Obtain MSCS function switch information, which is used to indicate whether the MSCS function of the AP device is turned on or off; and Based on the MSCS function switch information, the MSCS function of the AP device is turned on or off.

2. The method according to claim 1, further comprising: In response to enabling the MSCS function of the AP device, notify one or more clients that the AP device supports the MSCS function; as well as Accepts MSCS requests initiated by one or more MSCS clients.

3. The method according to claim 1, further comprising: In response to disabling the MSCS function of the AP device, notify one or more clients that the AP device does not support the MSCS function; as well as Stop providing MSCS services to the MSCS clients in one or more of the clients.

4. The method according to claim 3, wherein, The step of stopping the provision of MSCS services to the MSCS clients among the one or more clients includes: The MSCS request initiated by the MSCS client is rejected.

5. The method according to claim 3, wherein, The step of stopping the provision of MSCS services to the MSCS clients among the one or more clients includes: Stop the established MSCS rule and notify the associated MSCS client corresponding to the established MSCS rule that the established MSCS rule has been interrupted.

6. The method according to claim 5, wherein, The step of notifying the associated MSCS client in one or more MSCS clients of the interruption of the established MSCS rule includes: The established MSCS rule is notified of interruption by sending a response message to the associated MSCS client; and / or Disconnect the AP device from the associated MSCS client.

7. The method according to claim 1, further comprising: In response to enabling the MSCS function of the AP device, based on the acquired rule configuration information, the provision of MSCS services to some MSCS clients may be stopped or allowed. The rule configuration information is used to indicate the rules for filtering out certain MSCS clients from the MSCS clients.

8. The method according to claim 7, wherein, The rule configuration information is associated with at least one of the number of MSCS clients receiving MSCS services and the transmission rate of the MSCS clients receiving MSCS services.

9. The method according to claim 7, wherein, The rule configuration information is a configuration list, which includes configuration entries, and the configuration entries contain the identifiers of the selected MSCS clients.

10. The method of claim 9, further comprising: Receive a list configuration request, the list configuration request containing information for adding, modifying or deleting items from the configured list; as well as Based on the list configuration request, the configured list can be added, modified, or deleted.

11. The method according to claim 9, wherein, The configuration list includes a blacklist, and the step of stopping or allowing the provision of MSCS services to certain MSCS clients based on the obtained rule configuration information includes: Reject MSCS requests initiated by MSCS clients that match the configuration entries in the blacklist; and / or Accept MSCS requests initiated by MSCS clients that do not match the configuration entries in the blacklist.

12. The method according to claim 9, wherein, The configuration list includes a blacklist, and the step of stopping or allowing the provision of MSCS services to certain MSCS clients based on the obtained rule configuration information includes: Determine whether the associated MSCS clients of the established MSCS rules match the configuration entries in the blacklist; and In response to the associated MSCS client matching the configuration entry in the blacklist, the established MSCS rule is stopped, and the associated MSCS client is notified that the established MSCS rule is interrupted.

13. The method according to claim 9, wherein, The configuration list includes a whitelist, and the step of stopping or allowing the provision of MSCS services to certain MSCS clients based on the obtained rule configuration information includes: Accept MSCS requests initiated by MSCS clients that match the configuration entries in the whitelist; and / or MSCS requests initiated by MSCS clients that do not match the configuration entries in the whitelist are rejected.

14. The method according to claim 12, wherein, The configuration list includes a whitelist, and the step of stopping or allowing the provision of MSCS services to certain MSCS clients based on the obtained rule configuration information includes: Determine whether the associated MSCS clients of the established MSCS rules match the configuration entries in the whitelist; and In response to the associated MSCS client not matching the configuration entry in the whitelist, the established MSCS rule is stopped, and the associated MSCS client is notified that the established MSCS rule is interrupted.

15. An access point (AP) device, comprising: One or more processors; as well as Memory; wherein, The memory stores computer-readable instructions and is communicatively connected to the one or more processors; The one or more processors are configured to execute the computer-readable instructions stored in the memory to implement the method according to any one of claims 1-14.

16. The AP device according to claim 15, wherein, The access point (AP) device is a router.

17. A computer program product having instructions stored thereon that, when executed by a processor, cause the method according to any one of claims 1-14 to be performed.

Images