EP3292714B1 - Gestion de dispositif sans fil définie par logiciel - Google Patents

Gestion de dispositif sans fil définie par logiciel Download PDF

Info

Publication number
EP3292714B1
EP3292714B1 EP15727485.3A EP15727485A EP3292714B1 EP 3292714 B1 EP3292714 B1 EP 3292714B1 EP 15727485 A EP15727485 A EP 15727485A EP 3292714 B1 EP3292714 B1 EP 3292714B1
Authority
EP
European Patent Office
Prior art keywords
network
client device
association
access point
determining
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP15727485.3A
Other languages
German (de)
English (en)
Other versions
EP3292714A2 (fr
Inventor
Sachin Ganu
Jin Xie
Partha Narasimhan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hewlett Packard Enterprise Development LP
Original Assignee
Hewlett Packard Enterprise Development LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hewlett Packard Enterprise Development LP filed Critical Hewlett Packard Enterprise Development LP
Publication of EP3292714A2 publication Critical patent/EP3292714A2/fr
Application granted granted Critical
Publication of EP3292714B1 publication Critical patent/EP3292714B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0866—Checking the configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00837—Determination of triggering parameters for hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00837—Determination of triggering parameters for hand-off
    • H04W36/008375—Determination of triggering parameters for hand-off based on historical data

Definitions

  • the present disclosure relates to network management in a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the present disclosure relates to a mechanism for software-defined wireless device management in a WLAN.
  • Wireless digital networks such as networks operating under the current Electrical and Electronics Engineers (IEEE) 802.11 standards, are spreading in their popularity and availability.
  • IEEE Electrical and Electronics Engineers
  • a network device is capable of finding the best radio of all access points (APs) in the WLAN for each client to connect with.
  • the network device can identify one or more clients with incompatible behaviors, and match the one or more clients to another radio of the same or different access point in the WLAN that the clients are compatible with.
  • the conventional network device can homogenize client behaviors without requiring any client-side installation of software applications.
  • the approach described above has certain limitations. For example, there are a number of behaviors that the network device expects from the client devices. The client devices may not perform the expected behavior due to various reasons, e.g., lack of interoperability, power save mode configuration, device-specific configurations, etc. Therefore, a more flexible approach is needed for matching client devices to the best radios of the APs in the WLAN.
  • FIG. 1 shows exemplary computing environment according to examples of the present disclosure.
  • FIG. 1 includes a network controller 120 and a plurality of access points, e.g., AP1 130 and AP2 135, in a wireless local area network (WLAN) 100.
  • WLAN 100 may be also connected to Internet 150 or another external network via a router 140.
  • network controller 120 is communicatively coupled with one or more access points (APs), such as AP1 130 and AP2 135, to provide wireless network services by transmitting network packets. Any number of network controllers and/or access points may be utilized.
  • an "access point” (AP) generally refers to a receiving point for any known or convenient wireless access technology which may later become known.
  • the term AP is not intended to be limited to IEEE 802.11-based APs.
  • APs generally function as an electronic device that is adapted to allow wireless devices to connect to a wired network via various communications standards.
  • Network may operate on a private network including one or more local area networks.
  • the local area networks may be adapted to allow wireless access, thereby operating as a wireless local area network (WLAN).
  • WLAN wireless local area network
  • one or more networks may share the same extended service set (ESS) although each network corresponds to a unique basic service set (BSS) identifier.
  • ESS extended service set
  • BSS basic service set
  • network depicted in FIG. 1 may include multiple network devices, such as network controllers, access points, routers, network servers, etc.
  • Each network controller device e.g., a network controller or an access point
  • the network controller device may be responsible for managing one or more additional network devices, such as access points or network servers, within the sub-network.
  • client devices 160- 164 are associated with AP1 130
  • client devices, such as client device 168, are associated with AP2 135.
  • client devices may be connected to the access points via wired or wireless connections in any suitable configuration.
  • a wireless station such as client device 160, client device 164, or client device 168, is associated with a respective access point, e.g., access point AP1 130, access point AP2 135, etc.
  • Access points may have varying capabilities.
  • AP1 130 may support IEEE 802.1 lac standards
  • AP2 135 may support IEEE 802.1 In standards.
  • client devices may have varying capabilities as well.
  • client device 160 may be compatible with IEEE 802.1 In standard
  • client device 168 may be compatible with both IEEE 802.1 lac and IEEE 802.1 In standards.
  • network controller 120 may maintain a data store for storing client device capability information about one or more client devices. Additionally, or alternatively, network controller 120 may maintain a data store (e.g., the same data store used to store the capability information about one or more client devices) for storing network device capability information about one or more network devices (e.g., one or more access points). Network controller 120 may utilize the client device capability information and network device capability information to determine that a particular access point (e.g., AP 1 130) has sufficient capabilities to provide network service to a client device (e.g., client device 168). Such a determination by network controller 120 can be communicated (e.g., using a set of instructions) to access points, including AP1 130 and AP2 135, in WLAN 100.
  • a particular access point e.g., AP 1 130
  • client device e.g., client device 168
  • Such a determination by network controller 120 can be communicated (e.g., using a set of instructions) to access points, including AP1 130
  • an access point may de-authenticate a client device (e.g., client device 168), such that the client device (e.g., client device 168) is no longer provided network service by the access point.
  • the client device may proceed with establishing an association with another access point (e.g., AP1 130).
  • another access point e.g., AP 1 130
  • another access point may include different capabilities that are better suited to providing network service to client device than a the capabilities of a previously associated access point.
  • the client device may be provided better network service (e.g., less dropped packets, lower latency connection, greater bandwidth, etc.) by a particular access point depending on the capabilities of the access point.
  • FIG. 2 illustrates an application programmable interface (API) that is provided by the network controller and/or the APs of FIG. 1 in a WLAN.
  • API application programmable interface
  • Such an API may be utilized by an external entity (e.g., a laptop operated by network administrator) in order to modify configuration of the network in real-time.
  • the external entity may include any type of hardware device and/or software application capable of transmitting information an application programming interface.
  • FIG. 2 includes API 200 which includes one or more interface parameters including, but not limited to a user role 210, session information 220, a device type 230, an XML configuration 240, etc.
  • FIG. 2 also includes an exemplary mapping of one or more interface parameters to a network service category (COS 290) for a client device and/or a set of client devices.
  • a "network service category” (alternatively referred to herein as a “class of service category” or “COS”) may specific a set of network control actions that are available for a client device and/or a set of client devices.
  • execution of a "network control action” may alter at least one configuration of the network (e.g., by modifying an association between a client device and an access point).
  • execution of a "network control action" may include, but is not limited to, modifying association information indicating an association between a client device and an access point, inhibiting an association modification, selecting a particular mechanism for modifying the association information, selecting a particular time for modifying the association information, or enforcing a threshold number of association modifications for the client device during a specified time period.
  • one or more interface parameters may be used to determine a network service category for a particular client device (or group of client devices).
  • the mapping can be configured either by a network administrator and/or be trained or modified using dynamic machine learning technologies.
  • a network device e.g., the network controller 120 of FIG. 1 or an access point of FIG. 1
  • may receive indication e.g., using API 200
  • a particular network application executing on a client device is encountering problems (e.g., network traffic corresponding to the application running on the client device indicates dropped packets over a threshold number).
  • the network device may modify a network service category associated with the client device (e.g., the mapping). Therefore, the network device may adjust network service provided to a client device dynamically, in real-time.
  • the interface parameters of API 200 include, but are not limited to, a type of traffic, a user role, an operating system, session information, a device type, a manufacturer of device, a Network Interface Card (NIC) of a device, an application type, etc.
  • a combination of interface parameters may be used to control various network configurations (e.g., an association between a client device and an access point).
  • one or more interface parameters may be used to determine whether to move a particular client device (or a particular set of client devices) from one radio of one access point to another radio of a different access point in the WLAN.
  • API 200 may specify user role 210 as an interface parameter.
  • a user of the client device may be associated with a special user role (e.g., VIP).
  • a network device can be configured to provide a different class of service (e.g., according to a network service category) for the client devices that are authenticated by users belonging to the special user role.
  • the different class of service may be associated with a number of network control actions that, for example, may ensure that the a client device is matched to a best radio among all APs in the WLAN, and/or ensure that the client device is not deauthenticated from an AP (e.g., ever or for a period of time), and/or ensure a minimum quality of service for the client devices, etc.
  • Session information 220 may specify what type of traffic is being transmitted on a particular client device or a particular set of client devices. For example, if the system determines that a client device is currently making a voice call, the system may perform various actions based on the determination that the voice call is active. For example, the system may be configured to avoid de-authenticating a client device when a voice call is active. As another example, the system may determine to move a client to a different radio and/or access point upon detecting poor voice call quality.
  • the system may disassociated a first client device (e.g., a client device that is not on an active call) from a first AP and associate the first client device to a second AP, so that an incoming client device (e.g., a client device that is on an active call) can be associated with the first AP.
  • modifying the association of the first client device may be performed due to the first AP having capabilities that make it being better suited than the second AP to provide higher voice call quality.
  • the network system may detect that a particular client device is roaming from a first AP to a second AP.
  • a number of client devices e.g., 10 devices
  • the network system can detect that the client devices that are currently associated with the second AP are running applications (e.g., Internet browsers) that use Hypertext Transfer Protocol (HTTP) for data transmissions.
  • the network system can proactively move a subset of client devices that are currently associated with the second AP to a different AP prior to the particular client device sends an association request to the second AP.
  • Such actions may ensure that the second AP has the capacity to provide network service to the incoming client device on an active voice call.
  • a user when a client device is executing a unified communication (UC) application for a video/audio call, a user can set the session information interface parameter based on a known port number and/or Media Access Control (MAC) identifier.
  • MAC Media Access Control
  • the user e.g., a network administrator
  • the set of client devices running such client-side application can be associated with a network service category that corresponds to a high quality of network service.
  • session information indicates that a particular type of application, e.g., Lync® application, has become active on a client device
  • the client device will be provided with "platinum" level class of service until the session expires.
  • ip access-list session lync-acl any any svc-sips permit queue high cm-cos platinum any any any permit
  • a device type, device behaviors, or an operating system can also be included as an interface parameter of the application programming interface.
  • the system can detect (e.g., using network traffic, predefined identification data, and/or a device fingerprint) that a client device is an Apple® device installed with iOS® operating system. Based on the device type and/or operating system, the system may allow a client device to move from one AP to another AP in the WLAN. Alternatively, based on the device type and/or operating system, the system may inhibit the client device from moving from one AP to another AP. As a further example, the system may limit the number of moves for a particular client device installed with a particular operating system.
  • the system may allow the external entity to provide a user-defined rule for mapping a set of configuration parameters to a particular network service category.
  • a user-defined rule may be provided using an interface parameter (e.g., XML Configuration interface parameter of FIG. 2 ) of the application programming interface (e.g., API 200 of FIG. 2 ).
  • the rule may be defined using a markup language (e.g., extensible markup language (XML)).
  • XML configuration can be configured by a user dynamically without requiring any code change in the system's existing logic used for moving client devices.
  • many client devices may subscribe to the same multicast stream. These client devices may be initially associated with different APs in the WLAN. It is generally undesirable for multiple client devices subscribing to one multicast stream (sharing a multicast address) to be connected to different APs because traffic intended for the multicast stream would have to be sent to each AP that was associated with each client device subscribed to the multicast stream. If on the other hand, all client devices subscribing to the same multicast stream are connected to the same AP, then the system need only transmit one copy of the multicast packet to one AP (e.g., the AP shared by the client devices subscribed to the multicast stream). This would greatly improve the efficiency of the network system by avoid flooding extra multicast packets in the network system.
  • the network system may not be aware that there are multiple client devices subscribing to the same multicast stream that are connected to different APs in the WLAN.
  • An external entity e.g., a computing device operated by a network administrator, a network monitoring device
  • the external entity can use the XML configuration interface parameter of FIG. 2 to group the client devices based on their multicast stream subscription. Receipt of the XML configuration interface parameter may trigger the network system to move all client devices subscribing to the same multicast stream to the same radio and/or AP in the WLAN.
  • a client device is known to be incompatible with network devices of the network system, for instance, based on its operating system (OS) and/or Network Interface Card (NIC), then the network system can alter its default behavior based XML defined rule such as the one described below. Specifically, the sample rule defined below limits the number of steers to one move per 5 minutes for iOS based client devices.
  • Such a rule may be communicated between network devices using the application programming interface (e.g., using the XML Configuration interface parameter of the application programming interface).
  • API 200 may further provide an interface to enable an external entity to specify one or more network control actions to be performed on a particular client device or a set of client devices. Additionally, or alternatively, the external entity can provide input on how to map one or more interface parameters applicable to a particular client device (or a set of client devices) to a predefined (or dynamically learned) network service category.
  • a network service category may specify a set of available network control actions. Execution of a network control action may alter a configuration of the network.
  • a network control action includes, but is not limited to, modifying association information indicating an association between a client device and an access point, inhibiting an association modification, selecting a particular mechanism for modifying the association information, selecting a particular time for modifying the association information, or enforcing a threshold number of association modifications for the client device during a specified time period, etc.
  • the API can enable an external entity to configure (e.g., provide a rule) as to whether or not to move a client device (or a set of client devices) using a combination of the interface parameters.
  • a "move,” or “moving" a client device is intended to refer to disassociating the client device from an access point and associating the client device to a different access point.
  • the external entity using the application programming interface, may stimulate the system to move a client device if the client device is on an active voice call.
  • the external entity, using the application programming interface specify that the network system shall not move a client device on an active voice call, such that the client device will not experience any disrupted network services.
  • the set of rules associated with providing network services to a client device can be either statically defined or dynamically detected.
  • a rule of the set of rules provides a mapping between one or more interface parameters and a network service category.
  • a rule may map one or more interface parameters to a set of network control actions.
  • a rule may specify that the network system move a client to a different radio and/or access point upon detecting poor voice call quality.
  • the network device may (e.g., utilizing the application programming interface) cause the particular client device to move to a different radio and/or access point. If, however, the network device detects that the quality of the voice call is above a quality threshold value for the particular client device, then the network system will not move the particular client device to a different radio/AP.
  • Some client devices will stop trying to connect to the network if the client device has been de-authenticated (e.g.,disassociated from an access point) by the network system for more than a threshold number of times.
  • the API may enable an external entity to configure a rule that specifies a maximum number of moves allowed by the network system. For example, a maximum of three moves may be allowed by the WLAN infrastructure. Accordingly, after three unsuccessful attempts to move a particular client device to associate with a different access point, the network system , in accordance with the rule, will not activate any move mechanisms in order to avoid causing the client device to permanently disconnecting with the WLAN.
  • the particular client device may reverse the move. For example, the client device may continuously assess the received signal strength on various frequency bands and detect that the received signal strength on the first wireless frequency band is stronger than that on the second frequency band. Thus, the particular client device may disassociate with the WLAN on the second wireless frequency band, and re-associate with the WLAN on the first wireless frequency band.
  • the network system may set a limit on the maximum number of moves attempted for such client devices. If the client particular client device continues to move back to the first wireless frequency band after a maximum threshold number of moves, the network system will not attempt to move the particular client device to a different AP or radio in the WLAN.
  • the network system can learn a rule associated with client device behaviors dynamically, and store the rule that may be applicable in the future. For example, when the network system detects that a particular client device identified by a particular MAC address exhibits the above described "reversal" behavior, the network system can store the MAC address of the particular client device on a list. When the particular client device associates with the network system in the future, the network system will apply a static rule that limit the number of move attempts to, e.g., three times.
  • the stored rule can be evolving over a period of time based on observed client behaviors. For example, when the same client device joins the WLAN for the third time, the network system may adjust the maximum allowed number of moves to two instead of three because of the persistent "reversal" behaviors observed from the same client device in the past.
  • the API can enable an external entity to specify a particular move mechanism for a particular client device.
  • a "move mechanism” includes, but is not limited to, a sticky move mechanism, a band steering mechanism, a load balancing mechanism, etc.
  • execution of a network control action facilitates execution of one or more move mechanisms.
  • the external entity can specify precise control of move mechanisms through an interface parameters (e.g., an XML configuration interface parameter of FIG. 2 ).
  • the external entity can provide an interface parameter that specifies a first threshold level of signal noise ratio (SNR) associated with a signal transmitted from a current AP.
  • the external entity can provide an interface parameter that specifies a second threshold level of SNR acceptable at a target AP.
  • SNR signal noise ratio
  • the network system will search for a target AP, whose signal's SNR exceeds the second threshold level, and steer the client device to associate with the target AP.
  • the external entity can provide an interface parameter that specifies a first threshold level associated with a signal strength on a first wireless frequency band (e.g., 2.4GHz band), and/or a second threshold level associated with a signal strength on a second wireless frequency band (e.g., 5GHz band).
  • a first threshold level associated with a signal strength on a first wireless frequency band
  • a second threshold level associated with a signal strength on a second wireless frequency band
  • the network system may steer the client device to disassociate with the network on the first wireless frequency band, and re-associate with the network on the second wireless frequency band.
  • the external entity can provide an interface parameter that specifies a threshold number of client devices associated with a particular radio of an access point.
  • the network system will initiate a move of a client device to a different radio and/or access point to balance the load on the particular radio of the AP.
  • the external entity can provide an interface parameter that specifies a minimum threshold of SNR associated with a target radio of a target AP.
  • a minimum threshold of SNR associated with a target radio of a target AP specifies a minimum threshold of SNR associated with a target radio of a target AP.
  • the API can enable an external entity to select a particular time period for moving a particular client device.
  • the network system may delay the second move attempt by a predefined period of time, e.g., after 30 minutes. If the second move attempt has been undone by the client device, the network system further delays the third move attempt by an additional predefined period of time, e.g., after 60 minutes. The delay can be subsequently increased exponentially until it exceeds a threshold period of time after which the network system will not attempt to move the client device. Also, the network system may adjust the time period to match the preference and/or configurations of the particular client device.
  • the API can enable an external entity to select a particular subset of client devices meeting certain criteria to be moved by the network system.
  • the external entity can select the particular subset of client devices based on a combination of triggers and assign a class of service (e.g., silver class of service, or level 2 class of service) to the particular subset of client devices.
  • a class of service e.g., silver class of service, or level 2 class of service
  • the API can enable an external entity to select a particular protocol for moving the client devices.
  • the network system may de-authenticate the client devices to allow them to associate with a different AP in the WLAN.
  • the network system may transmit a basic service set (BSS) transition message to a respective client device.
  • BSS transition message allows an AP to request a client device that is currently associated with the AP to associate with a different AP as identified by the basic service set identifier (BSSID) in the message.
  • the client device upon receiving the BSS transition request, can either accept or deny the request in a response message to the AP.
  • the network system can fingerprint client devices to identify the subset of client devices that support IEEE 802.11v standards and selectively use BSS transition mechanism rather than de-authentication mechanism to move the identified subset of client devices.
  • the API can support any kind of customized and selective moves of a particular client device (or a set of client devices).
  • a network device may include a rule engine that supports determining a number of network control actions (e.g., a plurality of move mechanisms) that are supported by the network system.
  • Move mechanisms include, but are not limited to, sticky client move (ST 250), band steer move (BS 260), load balancing move (LB 270), de-authentication move (DA 280), etc.
  • ST 250 sticky client move
  • BS 260 band steer move
  • LB 270 load balancing move
  • DA 280 de-authentication move
  • a client device may be moved by the network system because it is a "sticky" client device.
  • a "sticky" client device generally refers to a client device that does not disassociate with an access point even though the corresponding signal strength of a received radio frequency (RF) signal is weak.
  • RF radio frequency
  • a client device may be moved by the network system to be associated with the same or different AP on a different radio frequency band. Furthermore, a client device may be moved by the network system to from a first AP to a second AP in the WLAN to balance traffic load between the first AP and the second AP. Also, a client device may simply be de-authenticated by its currently associated AP, such that the client device is forced to associate with another AP in the neighborhood.
  • the API provides an interface to enable an external entity to the WLAN to specify dynamically one or more triggers, as well as how to map a particular client device (or set of client devices) to a particular class of service (i.e., COS 290) based on the triggers. Rule engine can then determine a course of actions to be taken on the particular client device (or set of client devices) based on the class of service.
  • COS level 1 may allow the use of all four different move mechanisms, such as sticky client move (ST 250), band steer move (BS 260), load balancing move (LB 270), de-authentication move (DA 280), etc.
  • COS level 2 may only allow three of the supported move mechanisms, such as sticky client move (ST 250), load balancing move (LB 270), de-authentication move (DA 280), etc.
  • COS level 3 merely allows two of the supported move mechanisms, such as sticky client move (ST 250), band steer move (BS 260), etc. Therefore, the API provides the ability for the network system to dynamically control network configuration.
  • the network system when the network system fails to move a subset of client devices in the WLAN, the network system will need to disable the client matching feature of the WLAN infrastructure.
  • the network system can use different move mechanism for different client devices, and thus allow flexible use of the different move mechanisms to ensure that the client matching feature of the WLAN infrastructure works for a majority of client devices in the WLAN.
  • FIG. 3 illustrates an exemplary process for software-defined wireless device management in a WLAN according to examples of the present disclosure.
  • a network device e.g., a network controller or an access point
  • the network device determines a number of times the client device has been caused to change an association with an access point during the first period of time (operation 320).
  • the network device determines whether the number exceeds a threshold value for the first period of time (operation 340). Responsive at least to determining that the number does not exceed the threshold value, the network device causes the client device to switch the association with the second access point to an association with the third access point (operation 360).
  • the network device refrains from causing the client device to switch the association with the second access point to the association with the third access point.
  • the threshold value for the first period of time is based on device type.
  • the threshold value for the first period of time can further be based on one or more of: user role, traffic type, application type, session information, client roaming activity, device fingerprint, device signature, etc.
  • the network device responsive to determining that a service provided by the second access point does not meet one or more minimum criteria, for example, when the quality of connection is poor, causes the client device to switch the association with the second access point to the association with the third access point.
  • FIG. 4 illustrates another exemplary process for software-defined wireless device management in a WLAN according to examples of the present disclosure.
  • a network device determines for a first client device of a plurality of client devices a corresponding first configuration which indicates when any access point with which the client device is associated may be modified (operation 400). Based on the first configuration, the network device further determines that an association of the first client device with a first access point should not be modified (operation 420). Also, the network device determines for a second client device of the plurality of client devices a corresponding second configuration which indicates when any access point with which the second client device is associated may be modified (operation 440). Here, the second configuration is different than the first configuration. Based on the second configuration, the network device determines that an association of the second client device with the first access point should be modified to an association with a second access point (operation 460).
  • the first configuration indicates that an association of the first client device can never be caused to be modified by a network device.
  • the client device can choose to modify its own association with the access point, but the network device will not intervene with the selection of APs for that client device.
  • the first configuration indicates a maximum number of times that the association of the first client device with a current access point can be modified within a particular period of time.
  • the second configuration indicates a maximum number of times that the association of the first client device with a current access point can be modified within a particular period of time.
  • the network device automatically determines the first configuration and/or the second configuration based on one or more attributes associated with the first client device and/or the second client device, respectively.
  • the attributes associated with the first client device may include a device type.
  • the attributes associated with the first client device may also include one or more of: user role, traffic type, application type, session information, client roaming activity, device fingerprint, device signature, etc.
  • the network device determines that the association of the second device with the first access point should be modified to the association with the second access point based on determining that the client device is a member of a same multicast group as client devices associated with the second access point.
  • the network device determines that the association of the second client device with the first access point should be modified to the association with the second access point based on determining that the client device is on a voice call with poor quality and determining that the first configuration permits at least one more modification during the voice call.
  • the network device determines that the association of the first client device with the first access point should not be modified to the association with the second access point based on determining that the first client device is on a voice call and determining that the second configuration prohibits modification during the voice call. In some examples, if it is determined that the second client device is on an active voice call, the second access point causes at least a third device to switch association with the second access point to association to a third access point.
  • FIG. 5 illustrates yet another exemplary process for software-defined wireless device management in a WLAN according to examples of the present disclosure.
  • a network device determines one or more attributes corresponding to a client device associated with a first access point (operation 500). Based on the one or more attributes, the network device determines that the association of the client device with the first access point should be switched to an association with a second access point (operation 520). Further, based on the one or more attributes, the network device selects a mechanism, of a plurality of mechanisms, for causing the client device to switch an association with the first access point to an association with the second access point (operation 540). Subsequently, the network device uses the selected mechanism to cause the client device to switch from the association with the first access point to the association with the second access point (operation 560).
  • the selected mechanism involves the first access point transmitting de-authentication message or a dis-association message corresponding to the client device.
  • receiving the set of instructions at an access point facilitates transmission of a de-authentication message or a disassociation message.
  • the selected mechanism involves the first access point transmitting instructions to the client device to associate with the second access point.
  • the first access point may transmit a BSS transition request compliant with IEEE 802.11v standard to the client device to request the client device to associate with the second access point.
  • the selected mechanism involves configuring the first access point to reject one or more requests from the client device and configuring the second access point to accept the one or more requests from the client device.
  • the selected mechanism involves selecting a particular time during which the client device can be caused to switch association with the first access point to association with the second access point.
  • FIG. 6 is a block diagram illustrating a system for software-defined wireless device management in a WLAN according to examples of the present disclosure.
  • Network device 600 includes at least one or more radio antennas 610 capable of either transmitting or receiving radio signals or both, a network interface 620 capable of communicating to a wired or wireless network, a processor 630 capable of processing computing instructions, and a memory 640 capable of storing instructions and data. Moreover, network device 600 further includes a receiving mechanism 650, a transmitting mechanism 660, and a detecting mechanism 670, all of which are in communication with processor 630 and/or memory 640 in network device 600. Network device 600 may be used as a client system, or a server system, or may serve both as a client and a server in a distributed or a cloud computing environment.
  • Radio antenna 610 may be any combination of known or conventional electrical components for receipt of signaling, including but not limited to, transistors, capacitors, resistors, multiplexers, wiring, registers, diodes or any other electrical components known or later become known.
  • Network interface 620 can be any communication interface, which includes but is not limited to, a modem, token ring interface, Ethernet interface, wireless IEEE 802.11 interface, cellular wireless interface, satellite transmission interface, or any other interface for coupling network devices.
  • Processor 630 can include one or more microprocessors and/or network processors.
  • Memory 640 can include storage components, such as, Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), etc.
  • DRAM Dynamic Random Access Memory
  • SRAM Static Random Access Memory
  • Receiving mechanism 650 generally receives one or more network messages via network interface 620 or radio antenna 610 from a wireless client.
  • the received network messages may include, but are not limited to, requests and/or responses, beacon frames, management frames, control path frames, and so on.
  • Receiving mechanism 650 may additionally, or alternatively, receive one or more interface parameters using an application programming interface, wherein the one or more interface parameters relate to a client device in a network, wherein the one or more interface parameters are received from an external entity.
  • receiving mechanism 650 may receive a user-defined rule using the application programming interface, wherein the user-defined rule related to providing network services to the client device. Receiving mechanism 650 may add the user-defined rule to the set of rules. Alternatively, the receiving mechanism 650 may communicate the user-defined rule to determining mechanism 670 such that determining mechanism 650 may add the user-defined rule to the set of rules. In at least one example, the determining mechanism 650 may add the user-defined rule to the set of rules prior to determining the network service category.
  • receiving mechanism 650 may receive a pre-determined rule.
  • the pre-determined rule may be associated with providing network services to the client device.
  • the receiving mechanism 650 may add the pre- determined rule to a set of rules, wherein the pre-determined rule is added before the network service category is determined.
  • Transmitting mechanism 660 generally transmits messages, which include, but are not limited to, requests and/or responses, beacon frames, management frames, control path frames, and so on. Additionally, or alternatively, transmitting mechanism 660 may transit a set of instructions. In some examples, transmitting a set of instructions causes an access point to transmit a de-authentication message or a disassociation message to the client device.
  • Determining mechanism 670 generally determines whether and how to cause a client device switch to connect with a different radio and/or access point. Specifically, in some examples, determining mechanism 670 determines a number of times the client device has been caused to switch association with an access point during a period of time. Further, determining mechanism 670 can determine whether the number exceeds a threshold value for first period of time.
  • determining mechanism 670 obtains a set of rules related to providing network services to a client device. Additionally, or alternatively, determining mechanism 670 determines a network service category for the client device using the set of rules and the one or more interface parameters, wherein the network service category specifies a set of available network control actions, and wherein execution of a network control action alters a configuration of the network. Additionally, or alternatively, determining mechanism 670 determines a network control action of a set of available network control actions using one or more interface parameters. Additionally, or alternatively, determining mechanism 670 determines a set of instructions that correspond to a network control action (or a set of network control actions).
  • a network service category is associated with a quality threshold value
  • determining the network control action includes determining that the client device is being provided a quality of network service that is below the quality threshold value associated with the network service category.
  • a rule may provide a mapping between an interface parameter (or a set of interface parameters) and a network service category.
  • a rule (or a pre-determined rule) may be defined using a markup language (e.g., XML).
  • determining mechanism 670 determines a network control action of the set of available network control actions using one or more interface parameters.
  • a the network control action includes modifying association information indicating an association between a client device and an access point, inhibiting an association modification, selecting a particular mechanism for modifying the association information, selecting a particular time for modifying the association information, or enforcing a threshold number of association modifications for the client device during a specified time period.
  • determining mechanism 670 determines a network control action.
  • determining a network control action includes determining a threshold value corresponding to a maximum number of times an association for the client device can be modified within a period of time and determining a number of association changes for the client device occurring within the period of time, wherein execution of the determined network control action inhibits a change to the association when the number of association changes occurring within the period of time exceeds the threshold value.
  • the network control action allows a change to the association when the number of association changes occurring within the period of time is less than a threshold number.
  • the threshold number may be the same or a different number than the threshold value corresponding to a maximum number of times the association for the client device can be modified within a period of time.
  • determining mechanism 670 determines a network control action. In some examples, determining a network control action includes determining a multicast group for the client device from the configuration information. In some examples, determining a network control action includes determining an additional multicast group associated with an additional client device on the network and determining that the multicast group for the client device is the same as the additional multicast group of the additional client device, wherein executing the network control action modifies the association information associated with the client device, and wherein modifying the association information for the client device causes the client device and the additional client device to be associated with a same access point.
  • determining mechanism 670 determines a network control action. In some examples, determining a network control action includes determining, using the one or more interface parameters, that the client device is being provided a quality of network service below a quality threshold value associated with the network service category.
  • execution of the determined network control action allows a change to the association when the number of association changes occurring within the period of time is less than the threshold value.
  • the threshold value is determined using the one or more interface parameters, roaming activity information of the client device, a fingerprint of the client device, or a signature of the client device.
  • determining mechanism 670 maintains a data store for storing information related to one or more client devices and one or more access points and stores the one or more interface parameters in the information data store.
  • determining mechanism 670 determines that the association of the first client device with the first access point should not be modified to the association with the second access point based on determining that the first client device is on a voice call and determining that the second configuration prohibits modification during the voice call.
  • determining mechanism 670 determines for a first client device of a plurality of client devices a corresponding first configuration, which indicates when any access point with which the client device is associated may be modified. Based on the first configuration, determining mechanism 670 determines that an association of the first client device with a first access point should not be modified. Furthermore, determining mechanism 670 determines for a second client device of the plurality of client devices a corresponding second configuration, which indicates when any access point with which the second client device is associated may be modified. Note that, the second configuration is different than the first configuration. Based on the second configuration, determining mechanism 670 can determine that an association of the second client device with the first access point should be modified to an association with a second access point.
  • the first configuration indicates that an association of the first client device can never be caused to be modified by a network device. In some examples, the first configuration indicates a maximum number of times that the association of the first client device with a current access point can be modified within a particular period of time. In some examples, the second configuration indicates a maximum number of times that the association of the first client device with a current access point can be modified within a particular period of time. Additionally, or alternatively transmitting mechanism 660 may transmit a set of instructions, using the one or more processors. Transmitting the set of instructions may facilitate execution of one or more network control actions by one or more network devices.
  • determining mechanism 670 automatically determines the first configuration and/or the second configuration based on one or more attributes associated with the first client device and/or the second client device, respectively.
  • the attributes associated with the first client device may include, but are not limited to, a device type, a user role, a traffic type, an application type, session information, a client roaming activity, a device fingerprint, a device signature, etc.
  • determining mechanism 670 determines that the association of the second device with the first access point should be modified to the association with the second access point based on determining that the client device is a member of a same multicast group as client devices associated with the second access point.
  • determining mechanism 670 determines that the association of the second client device with the first access point should be modified to the association with the second access point based on determining that the client device is on a voice call with poor quality and determining that the first configuration permits at least one more modification during the voice call.
  • determining mechanism 670 can determine one or more attributes corresponding to a client device associated with a first access point. Based on the one or more attributes, determining mechanism 670 determines that the association of the client device with the first access point should be switched to an association with a second access point.
  • Switching mechanism 680 generally causes a client device to switch to a different radio and/or access point. Specifically, switching mechanism 680 can cause a client device to switch association with a first access point to an association with a second access point during a first period of time. Responsive at least to determining mechanism 670 determines that the number does not exceed the threshold value, switching mechanism 680 causes the client device to switch the association with the second access point to an association with the third access point. Responsive at least to determining mechanism 670 determines that the number exceeds the threshold value, switching mechanism 680 refrains from causing the client device to switch the association with the second access point to the association with the third access point.
  • the threshold value for the first period of time is based on one or more attributes of a device type, a user role, a traffic type, an application type, session information, a client roaming activity, a device fingerprint, a device signature, etc.
  • switching mechanism 680 can select one of a plurality of mechanisms for causing the client device to switch an association with the first access point to an association with the second access point. Further, switching mechanism 680 uses the selected mechanism to cause the client device to switch from the association with the first access point to the association with the second access point.
  • the selected mechanism may involve the first access point transmitting de-authentication message or a dis-association message corresponding to the client device.
  • the selected mechanism may involve the first access point transmitting instructions to the client device to associate with the second access point.
  • the selected mechanism may involve configuring the first access point to reject one or more requests from the client device and configuring the second access point to accept the one or more requests from the client device.
  • the selected mechanism involves selecting a particular time during which the client device can be caused to switch association with the first access point to association with the second access point.
  • switching mechanism 680 causes the client device to switch the association with the second access point to the association with the third access point.
  • switching mechanism 680 responsive to determining mechanism 670 determines that the second client device is on an active voice call, switching mechanism 680 causes at least a third device to switch association with the second access point to association to a third access point.
  • the present disclosure may be realized in hardware, software, or a combination of hardware and software.
  • the present disclosure may be realized in a centralized fashion in one computer system or in a distributed fashion where different elements are spread across several interconnected computer systems coupled to a network.
  • a typical combination of hardware and software may be an access point with a computer program that, when being loaded and executed, controls the device such that it carries out the methods described herein.
  • the present disclosure also may be embedded in non-transitory fashion in a computer-readable storage medium (e.g., a programmable circuit; a semiconductor memory such as a volatile memory such as random access memory "RAM,” or nonvolatile memory such as read-only memory, power-backed RAM, flash memory, phase-change memory or the like; a hard disk drive; an optical disc drive; or any connector for receiving a portable memory device such as a Universal Serial Bus "USB" flash drive), which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods.
  • a computer-readable storage medium e.g., a programmable circuit; a semiconductor memory such as a volatile memory such as random access memory "RAM,” or nonvolatile memory such as read-only memory, power-backed RAM, flash memory, phase-change memory or the like; a hard disk drive; an optical disc drive; or any connector for receiving a portable memory device such as a Universal Serial Bus "USB” flash drive
  • Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
  • network device generally includes a device that is adapted to transmit and/or receive signaling and to process information within such signaling such as a station (e.g., any data processing equipment such as a computer, cellular phone, personal digital assistant, tablet devices, etc.), an access point, data transfer devices (such as network switches, routers, controllers, etc.) or the like.
  • a station e.g., any data processing equipment such as a computer, cellular phone, personal digital assistant, tablet devices, etc.
  • data transfer devices such as network switches, routers, controllers, etc.
  • interconnect or used descriptively as “interconnected” is generally defined as a communication pathway established over an information-carrying medium.
  • the "interconnect” may be a wired interconnect, wherein the medium is a physical medium (e.g., electrical wire, optical fiber, cable, bus traces, etc.), a wireless interconnect (e.g., air in combination with wireless signaling technology) or a combination of these technologies.
  • information is generally defined as data, address, control, management (e.g., statistics) or any combination thereof.
  • information may be transmitted as a message, namely a collection of bits in a predetermined format.
  • One type of message namely a wireless message, includes a header and payload data having a predetermined number of bits of information.
  • the wireless message may be placed in a format as one or more packets, frames or cells.
  • wireless local area network generally refers to a communications network that links two or more devices using some wireless distribution method (for example, spread-spectrum or orthogonal frequency-division multiplexing radio), and usually providing a connection through an access point to the Internet; and thus, providing users with the mobility to move around within a local coverage area and still stay connected to the network.
  • some wireless distribution method for example, spread-spectrum or orthogonal frequency-division multiplexing radio
  • nism generally refers to a component of a system or device to serve one or more functions, including but not limited to, software components, electronic components, electrical components, mechanical components, electro-mechanical components, etc.
  • example generally refers an example that serves to illustrate by way of example but not limitation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (14)

  1. Dispositif de gestion de réseau (600), le dispositif de gestion de réseau comprenant :
    un récepteur sans fil (650) pour recevoir, à l'aide d'un ou plusieurs processeurs (630), un paramètre d'interface, le paramètre d'interface étant reçu d'une entité externe à l'aide d'une interface de programmation d'application, et le paramètre d'interface étant associé à un dispositif client dans le réseau ;
    un moteur de règles (670) configuré pour effectuer des opérations comprenant :
    l'obtention d'un ensemble de règles à partir d'une base de données, l'ensemble de règles étant associé au réseau, et l'ensemble de règles facilitant la fourniture de services réseau au dispositif client sur le réseau ;
    la détermination d'une catégorie de service réseau pour le dispositif client à l'aide du paramètre d'interface et de l'ensemble de règles, la catégorie de service réseau spécifiant un ensemble d'actions de gestion de réseau disponibles, et une action de gestion de réseau affectant une configuration du réseau ;
    la détermination de l'action de gestion de réseau à l'aide du paramètre d'interface, la détermination de l'action de gestion de réseau comporte :
    la détermination d'une valeur de seuil correspondant à un nombre maximum de fois où une association entre le dispositif client et un point d'accès peut être modifiée durant un laps de temps ; et
    la détermination d'un certain nombre de changements d'association pour le dispositif client se produisant durant le laps de temps, l'exécution de l'action de gestion de réseau déterminée inhibant un changement de l'association lorsque le nombre de changements d'association se produisant durant le laps de temps dépasse la valeur de seuil ;
    dans lequel la valeur de seuil est déterminée à l'aide d'une empreinte digitale du dispositif client, l'empreinte digitale identifiant un type de dispositif et/ou un système d'exploitation du dispositif client ; et
    la détermination d'un ensemble d'instructions correspondant à l'action de gestion de réseau ; et
    un émetteur (660) pour transmettre l'ensemble d'instructions, la transmission de l'ensemble d'instructions facilitant l'exécution de l'action de gestion de réseau par un dispositif de réseau.
  2. Dispositif de gestion de réseau selon la revendication 1, dans lequel l'ensemble d'actions de gestion de réseau disponibles comporte la modification d'informations d'association indiquant une association entre le dispositif client et un point d'accès, l'inhibition d'une modification d'association, la sélection d'un mécanisme particulier pour modifier les informations d'association ou la sélection d'un moment précis pour modifier les informations d'association, ou le fait d'imposer un nombre seuil de modifications d'association pour le dispositif client pendant un laps de temps spécifié.
  3. Dispositif de gestion de réseau selon la revendication 1, dans lequel les paramètres d'interface comportent un type de trafic, un rôle d'utilisateur, un système d'exploitation, des informations de session, un type de dispositif, un fabricant, une carte d'interface réseau (NIC) ou un type d'application.
  4. Dispositif de gestion de réseau selon l'une quelconque des revendications 1 à 3, dans lequel l'exécution de l'action de gestion de réseau déterminée permet un changement de l'association lorsque le nombre de changements d'association se produisant durant le laps de temps est inférieur à un nombre seuil.
  5. Dispositif de gestion de réseau selon l'une quelconque des revendications 1 à 4, dans lequel l'empreinte digitale identifie si le dispositif client prend en charge les normes IEEE 802.11v.
  6. Dispositif de gestion de réseau selon l'une quelconque des revendications 1 à 4, dans lequel la valeur de seuil est déterminée à l'aide d'un paramètre d'interface, des informations d'activité d'itinérance du dispositif client ou d'une signature du dispositif client.
  7. Dispositif de gestion de réseau selon l'une quelconque des revendications 1 à 6, dans lequel le moteur de règles est configuré pour effectuer d'autres opérations comportant :
    le maintien d'une mémoire de données pour stocker des informations associées à un dispositif client et à un point d'accès ; et
    le stockage du paramètre d'interface dans la mémoire de données d'informations.
  8. Procédé mis en œuvre par ordinateur comprenant :
    la réception, à l'aide d'un ou plusieurs processeurs (630), d'un paramètre d'interface, le paramètre d'interface étant reçu d'une entité externe à l'aide d'une interface de programmation d'application, et le paramètre d'interface étant associé à un dispositif client (160, 164, 186) dans un réseau (100) ;
    l'obtention d'un ensemble de règles associées au réseau, l'ensemble de règles facilitant la fourniture de services réseau au dispositif client sur le réseau, et l'ensemble de règles étant stocké dans une base de données ;
    la détermination d'une catégorie de service réseau pour le dispositif client à l'aide du paramètre d'interface et de l'ensemble de règles, la catégorie de service réseau spécifiant un ensemble d'actions de gestion de réseau disponibles, et une action de gestion de réseau affectant une configuration du réseau ;
    la détermination d'une action de gestion de réseau à l'aide du paramètre d'interface, la détermination de l'action de gestion de réseau comporte :
    la détermination d'une valeur de seuil correspondant à un nombre maximum de fois où une association entre le dispositif client et un point d'accès peut être modifiée durant un laps de temps ; et
    la détermination d'un certain nombre de changements d'association pour le dispositif client se produisant durant le laps de temps, l'exécution de l'action de gestion de réseau déterminée inhibant un changement de l'association lorsque le nombre de changements d'association se produisant durant le laps de temps dépasse la valeur de seuil ;
    dans lequel la valeur de seuil est déterminée à l'aide d'une empreinte digitale du dispositif client, l'empreinte digitale identifiant un type de dispositif et/ou un système d'exploitation du dispositif client ; et
    la détermination d'un ensemble d'instructions correspondant à l'action de gestion de réseau ; et
    la transmission de l'ensemble d'instructions, la transmission de l'ensemble d'instructions facilitant l'exécution de l'action de gestion de réseau par un dispositif de réseau.
  9. Procédé mis en œuvre par ordinateur selon la revendication 8, dans lequel l'ensemble d'actions de gestion de réseau disponibles comporte la modification d'informations d'association indiquant une association entre un dispositif client et un point d'accès, l'inhibition d'une modification d'association, la sélection d'un mécanisme particulier pour modifier les informations d'association, la sélection d'un moment précis pour modifier les informations d'association, ou le fait d'imposer un nombre seuil de modifications d'association pour le dispositif client pendant un laps de temps spécifiée.
  10. Procédé mis en œuvre par ordinateur selon la revendication 8 ou 9, dans lequel les paramètres d'interface comportent un type de trafic, un rôle d'utilisateur, un système d'exploitation, des informations de session, un type de dispositif, un fabricant, une carte d'interface réseau (NIC) ou un type d'application.
  11. Procédé mis en œuvre par ordinateur selon l'une quelconque des revendications 8 à 10, dans lequel l'exécution de l'action de gestion de réseau déterminée permet un changement de l'association lorsque le nombre de changements d'association se produisant durant le laps de temps est inférieur à une valeur seuil.
  12. Procédé mis en œuvre par ordinateur selon l'une quelconque des revendications 8 à 11, dans lequel l'empreinte digitale identifie si le dispositif client prend en charge les normes IEEE 802.11v.
  13. Procédé mis en œuvre par ordinateur selon l'une quelconque des revendications 8 à 11, dans lequel une valeur de seuil est déterminée à l'aide d'un paramètre d'interface, des informations d'activité d'itinérance du dispositif client ou d'une signature du dispositif client.
  14. Procédé selon l'une quelconque des revendications 8 à 13, comprenant en outre :
    le maintien d'une mémoire de données pour stocker des informations associées à un dispositif client et à un point d'accès ; et
    le stockage du paramètre d'interface dans la mémoire de données d'informations.
EP15727485.3A 2014-04-29 2015-04-28 Gestion de dispositif sans fil définie par logiciel Active EP3292714B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/264,525 US10080166B2 (en) 2014-04-29 2014-04-29 Software defined wireless device management
PCT/US2015/028033 WO2015168148A2 (fr) 2014-04-29 2015-04-28 Gestion de dispositif sans fil définie par logiciel

Publications (2)

Publication Number Publication Date
EP3292714A2 EP3292714A2 (fr) 2018-03-14
EP3292714B1 true EP3292714B1 (fr) 2021-10-13

Family

ID=53298583

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15727485.3A Active EP3292714B1 (fr) 2014-04-29 2015-04-28 Gestion de dispositif sans fil définie par logiciel

Country Status (3)

Country Link
US (1) US10080166B2 (fr)
EP (1) EP3292714B1 (fr)
WO (1) WO2015168148A2 (fr)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105634923B (zh) * 2015-12-29 2018-11-02 北京邮电大学 基于sdn控制器的以太网广播优化处理方法
US10250315B2 (en) * 2015-12-30 2019-04-02 Futurewei Technologies, Inc. System and method for inter-basic service set communications
CN106302505B (zh) * 2016-08-30 2019-04-30 广东美的制冷设备有限公司 一种路由器入侵侦测警示方法及系统
EP3327971A1 (fr) * 2016-11-29 2018-05-30 Thomson Licensing Procédé et appareil permettant de gérer des interfaces de direction dans des dispositifs de communication
US10939349B2 (en) * 2018-11-16 2021-03-02 Arris Enterprises Llc Method and apparatus to configure access points in a home network controller protocol
JP7568656B2 (ja) 2019-05-24 2024-10-16 マーベル アジア ピーティーイー、リミテッド 複数の通信リンクを用いたｗｌａｎにおける省電力且つグループアドレス指定されたフレーム
CN112770364B (zh) * 2019-11-05 2022-02-01 中国科学院声学研究所 一种无线局域网的终端信道切换方法及系统
US20230091127A1 (en) * 2021-09-13 2023-03-23 Juniper Networks, Inc. Wireless network control based on roaming quality assessments

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110261786A1 (en) * 2008-04-22 2011-10-27 Chandra Bontu Restricting handover of a mobile station
WO2012034588A1 (fr) * 2010-09-14 2012-03-22 Nokia Siemens Networks Oy Détection de la dégradation de cellules
CN102647771A (zh) * 2012-04-10 2012-08-22 华为技术有限公司 无线局域网络的发现与选择方法、设备及系统与终端
WO2013159648A1 (fr) * 2012-04-28 2013-10-31 华为技术有限公司 Procédé et dispositif pour la création d'une association entre une station et un point d'accès

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0589552B1 (fr) * 1992-09-08 2002-10-23 Sun Microsystems, Inc. Méthode et appareil pour le maintien de la connection des noeuds dans un réseau local sans fil
FI20030967A (fi) * 2003-06-27 2004-12-28 Nokia Corp Yhteysasetusten valinta
US20060007930A1 (en) * 2004-07-09 2006-01-12 Dorenbosch Jheroen P Downlink multicast method in wireless internet protocol system
EP1810473B1 (fr) * 2004-11-09 2008-03-12 Telefonaktiebolaget Lm Ericsson Appareil et procede de prevention d'utilisations frauduleuses lors de l'acces a travers des reseaux locaux sans fil
US7653037B2 (en) * 2005-09-28 2010-01-26 Qualcomm Incorporated System and method for distributing wireless network access parameters
US7848241B2 (en) * 2006-01-31 2010-12-07 Motorola Mobility, Inc. Method and apparatus for handoff control in mobile communications systems
JP4723458B2 (ja) * 2006-11-07 2011-07-13 富士通株式会社 中継装置、無線通信システム及びマルチキャスト中継方法
CN102387563B (zh) * 2010-08-26 2015-05-27 华为技术有限公司 机器类型通讯设备的业务控制方法和相关装置及系统
US8943229B2 (en) * 2010-12-30 2015-01-27 Google Inc. Peripheral device detection with short-range communication
US20120224522A1 (en) * 2011-03-04 2012-09-06 Electronics And Telecommunications Research Institute Method and apparatus for managing multicast service
EP2702803B1 (fr) * 2011-04-27 2017-03-22 Fujitsu Limited Amélioration pour la préparation de transferts intercellulaires multiples
WO2012150880A1 (fr) * 2011-05-02 2012-11-08 Telefonaktiebolaget L M Ericsson (Publ) Procédé dans un nœud de réseau radio pour contrôler une décision de transfert d'un équipement utilisateur
US9007980B2 (en) * 2011-06-07 2015-04-14 Verizon Patent And Licensing Inc. Multicast-unicast handoff services
US20130237233A1 (en) * 2012-03-08 2013-09-12 Qualcomm Incorporated Method and apparatus for offloading devices in femtocell coverage
US9736703B2 (en) * 2012-04-06 2017-08-15 Plume Design, Inc. Interference management and network performance optimization in dense WiFi networks

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110261786A1 (en) * 2008-04-22 2011-10-27 Chandra Bontu Restricting handover of a mobile station
WO2012034588A1 (fr) * 2010-09-14 2012-03-22 Nokia Siemens Networks Oy Détection de la dégradation de cellules
CN102647771A (zh) * 2012-04-10 2012-08-22 华为技术有限公司 无线局域网络的发现与选择方法、设备及系统与终端
EP2824870A1 (fr) * 2012-04-10 2015-01-14 Huawei Technologies Co., Ltd. Procédé, dispositif et système de découverte et de sélection de réseau local sans fil, et terminal associé
WO2013159648A1 (fr) * 2012-04-28 2013-10-31 华为技术有限公司 Procédé et dispositif pour la création d'une association entre une station et un point d'accès
EP2844025A1 (fr) * 2012-04-28 2015-03-04 Huawei Technologies Co., Ltd. Procédé et dispositif pour la création d'une association entre une station et un point d'accès

Also Published As

Publication number Publication date
EP3292714A2 (fr) 2018-03-14
US10080166B2 (en) 2018-09-18
US20150312131A1 (en) 2015-10-29
WO2015168148A3 (fr) 2015-12-30
WO2015168148A2 (fr) 2015-11-05

Similar Documents

Publication Publication Date Title
EP3292714B1 (fr) Gestion de dispositif sans fil définie par logiciel
US9544840B2 (en) Distributed method for client optimization
US10764349B2 (en) Self-organizing network communication
US10172031B2 (en) Wireless assistance method, apparatus and system
CA3064945C (fr) Voie de donnees de machine virtuelle a fonctionnalite de serveur dhcp
US20170111301A1 (en) Client side queue sharding
US9565627B2 (en) Distributed radio management
US9713051B2 (en) Session aware access point load balancing
KR20140131555A (ko) 셀룰러 전화의 셀룰러 통신으로부터 와이파이 통신으로의 무결절성 천이
US20170171809A1 (en) Wireless access point power save mode
WO2018089615A1 (fr) Nœud de réseau d'accès radio (ran), dispositif mobile et procédés de configuration d'un mode de diffusion groupée dans un réseau défini par logiciel (sdn)
US9788249B2 (en) Wireless communication apparatus, wireless communication method, and computer-readable recording medium
US10091730B2 (en) Adaptive management of wireless clients based on clients radio behaviors and capabilities
CN116055311A (zh) 一种通信方法及装置
US10154439B2 (en) Dynamic channel bandwidth selection based on information for packets transmitted at different channel bandwidths
US20130083689A1 (en) Ownership requests for access points
US10512091B2 (en) Data communications over a distributed multi-core wireless communication network
US10516998B2 (en) Wireless network authentication control
US11218912B2 (en) Method and apparatus for controlling traffic of network device in wireless communication network
US9736719B2 (en) Adaptive resource allocation in congested wireless local area network deployment
US10595301B2 (en) Managing signaling resources using hidden public land mobile network signals
US20240224009A1 (en) Method and apparatus for configuring offloading policy for vplmn edge service in mobile communication system
US11197263B1 (en) Decentralized dynamic frequency selection (DFS) master service
KR20240144937A (ko) 네트워크 슬라이싱을 사용하는 미디어 애플리케이션들의 정책 관리를 위한 방법 및 장치
TW202320518A (zh) 用於致能基於無線傳輸／接收單元（ｗｔｒｕ）之邊緣計算縮放之方法及設備

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAJ Public notification under rule 129 epc

Free format text: ORIGINAL CODE: 0009425

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170817

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

PUAG Search results despatched under rule 164(2) epc together with communication from examining division

Free format text: ORIGINAL CODE: 0009017

17Q First examination report despatched

Effective date: 20190404

B565 Issuance of search results under rule 164(2) epc

Effective date: 20190404

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 48/14 20090101AFI20190401BHEP

Ipc: H04W 36/24 20090101ALI20190401BHEP

Ipc: H04W 48/20 20090101ALI20190401BHEP

Ipc: H04W 48/18 20090101ALI20190401BHEP

Ipc: H04W 36/30 20090101ALI20190401BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602015074086

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0048140000

Ipc: H04W0036000000

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 48/14 20090101ALI20210312BHEP

Ipc: H04W 36/00 20090101AFI20210312BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20210512

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015074086

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1439072

Country of ref document: AT

Kind code of ref document: T

Effective date: 20211115

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20211013

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1439072

Country of ref document: AT

Kind code of ref document: T

Effective date: 20211013

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220113

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220213

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220214

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220113

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20220114

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015074086

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20220714

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20220430

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602015074086

Country of ref document: DE

Representative=s name: FLEUCHAUS & GALLO PARTNERSCHAFT MBB - PATENT- , DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 602015074086

Country of ref document: DE

Representative=s name: FLEUCHAUS & GALLO PARTNERSCHAFT MBB PATENTANWA, DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220428

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220430

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220430

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220430

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220428

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 602015074086

Country of ref document: DE

Owner name: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP, SPR, US

Free format text: FORMER OWNER: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP, HOUSTON, TX, US

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230427

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20150428

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20240423

Year of fee payment: 10

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211013