CN114079908A - Communication method, device, apparatus and storage medium in communication network - Google Patents

Communication method, device, apparatus and storage medium in communication network Download PDF

Info

Publication number
CN114079908A
CN114079908A CN202010818357.6A CN202010818357A CN114079908A CN 114079908 A CN114079908 A CN 114079908A CN 202010818357 A CN202010818357 A CN 202010818357A CN 114079908 A CN114079908 A CN 114079908A
Authority
CN
China
Prior art keywords
communication
token
communication network
request
service set
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.)
Pending
Application number
CN202010818357.6A
Other languages
Chinese (zh)
Inventor
杨志杰
吴海芹
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.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
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 Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to CN202010818357.6A priority Critical patent/CN114079908A/en
Priority to US17/355,439 priority patent/US11659443B2/en
Priority to EP21183427.0A priority patent/EP3955618A3/en
Publication of CN114079908A publication Critical patent/CN114079908A/en
Priority to US18/303,071 priority patent/US20230262524A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/08Load balancing or load distribution
    • H04W28/09Management thereof
    • H04W28/0958Management thereof based on metrics or performance parameters
    • H04W28/0967Quality of Service [QoS] parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • H04W12/065Continuous authentication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/14Mobility data transfer between corresponding nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60Context-dependent security
    • H04W12/69Identity-dependent
    • H04W12/73Access point logical identity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/08Load balancing or load distribution
    • H04W28/0827Triggering entity
    • H04W28/0838User device
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/08Load balancing or load distribution
    • H04W28/086Load balancing or load distribution among access entities
    • H04W28/0861Load balancing or load distribution among access entities between base stations
    • H04W28/0865Load balancing or load distribution among access entities between base stations of different Radio Access Technologies [RATs], e.g. LTE or WiFi
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/08Load balancing or load distribution
    • H04W28/0875Load balancing or load distribution to or through Device to Device [D2D] links, e.g. direct-mode links
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/08Load balancing or load distribution
    • H04W28/0883Load balancing or load distribution between entities in ad-hoc networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/20Selecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/043Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
    • H04W12/0431Key distribution or pre-distribution; Key agreement
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/08Testing, supervising or monitoring using real traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/08Load balancing or load distribution
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/02Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10Small scale networks; Flat hierarchical networks
    • H04W84/12WLAN [Wireless Local Area Networks]

Abstract

The disclosed embodiments relate to a communication method, device, apparatus and storage medium in a communication network. The method comprises the following steps: receiving, at a first device in a communication network, a first request from at least one second device in the communication network to obtain a token, the token being a credential for communicating with a third device; selecting one device from the first device and the at least one second device as a communication device for providing a communication service to the third device based on the first request; and sending the token to the communication device. The communication device receives the token to communicate with a third device. The other device receives key information associated with communication with the third device from the first device and listens for data associated with communication with the third device. Therefore, the optimal communication equipment can be dynamically selected for the third equipment by adjusting the load balance of the first equipment or the second equipment and timely capturing the moving path of the third equipment, so that the time delay of the terminal equipment is greatly reduced, and the communication safety is ensured.

Description

Communication method, device, apparatus and storage medium in communication network
Technical Field
Embodiments of the present disclosure relate to the field of communications, and more particularly, to a communication method, device, apparatus, and computer-readable storage medium for use in a communication network.
Background
Communication networks, such as Extended Service Set (ESS) networks and Mesh Basic Service Set (MBSS) networks, are made up of a plurality of Access Point (AP) devices (also referred to as nodes). Conventionally, a terminal device in a mobile state may scan to different AP nodes and dynamically select an AP node with a large Received Signal Strength Indication (RSSI) value to roam (roaming) to the selected AP node. If a certain AP node is overloaded or a signal of a packet received from the terminal device is weak, the AP node recommends other candidate AP nodes to the terminal device, so that the terminal device establishes a connection with the other candidate AP nodes, thereby implementing load balance (load balance).
However, no matter roaming or load balancing, the terminal device needs to complete the authentication connection with the new AP node before the terminal device can obtain the internet service through the new AP node. In application scenarios with huge data volume and ultra-low delay, such as Augmented Reality (AR) and Virtual Reality (VR), the problem of momentary jamming due to delay during roaming occurs, and good customer experience cannot be provided. And the renegotiation of the key is involved in the connection process with the new AP node, so that once the key is captured in the negotiation process due to the sniffing attack, the possibility of leakage and interception of user data exists.
Disclosure of Invention
In general, embodiments of the present disclosure provide an improved communication mechanism in a communication network.
In a first aspect of embodiments of the present disclosure, a first device in a communication network is provided. The first device includes: a processor; and a memory coupled with the processor, the memory having instructions stored therein that, when executed by the processor, cause the first device to: receiving a first request from at least one second device in the communication network to obtain a token, the token being a credential for communicating with a third device, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device; selecting one device from the at least one second device and the first device as a communication device in the communication network for providing a communication service for the third device based on the first request; and sending the token to the communication device to communicate with the third device through the communication device.
In a second aspect of embodiments of the present disclosure, a second device in a communication network is provided. The second device includes: a processor; and a memory coupled with the processor, the memory having instructions stored therein that, when executed by the processor, cause the second device to: in response to receiving a probe request from a third device, sending a first request to a first device in the communication network for obtaining a token, the token being a credential for communicating with the third device, the first device and the at least one second device each having the same SSID, BSSID, and AID in communication with the third device; and receiving the token from the first device to communicate with the third device.
In a third aspect of the disclosed embodiments, a second device in a communication network is provided. The second device includes: a processor; and a memory coupled with the processor, the memory having instructions stored therein that, when executed by the processor, cause the second device to: receiving key information associated with communication with a third device from a first device in the communication network, the first device and the at least one second device each having the same SSID, BSSID, and AID in communication with the third device; and listen for data associated with communication with the third device based on the key information.
In a fourth aspect of embodiments of the present disclosure, a third apparatus is provided. The third apparatus includes: a processor; and a memory coupled with the processor, the memory having instructions stored therein that, when executed by the processor, cause the third device to: transmitting a probe request to each of a first device and at least one second device in a communication network, each of the first device and the at least one second device having a same SSID, BSSID, and AID in communication with the third device; receiving a response to the probe request from one of the first device and the at least one second device; and communicating via the one device.
In a fifth aspect of embodiments of the present disclosure, a method for communication is provided. The method comprises the following steps: receiving, at a first device in a communication network, a first request from at least one second device in the communication network to obtain a token, the token being a credential for communicating with a third device, the first device and the at least one second device each having a same SSID, BSSID, and AID in communication with the third device; selecting one device from the at least one second device and the first device as a communication device in the communication network for providing a communication service for the third device based on the first request; and sending the token to the communication device to communicate with the third device through the communication device.
In a sixth aspect of embodiments of the present disclosure, a method for communication is provided. The method comprises the following steps: at a second device in a communication network, in response to receiving a probe request from a third device, sending a first request to a first device in the communication network to obtain a token, the token being a credential for communicating with the third device, the first device and the at least one second device each having a same SSID, BSSID, and AID in communication with the third device; and receiving the token from the first device to communicate with the third device.
In a seventh aspect of embodiments of the present disclosure, a method for communication is provided. The method comprises the following steps: receiving, at a second device in a communication network, key information associated with communication with a third device from a first device in the communication network, the first device and the at least one second device each having the same SSID, BSSID, and AID in communication with the third device; and listen for data associated with communication with the third device based on the key information.
In an eighth aspect of embodiments of the present disclosure, a method for communication is provided. The method comprises the following steps: transmitting, at a third device, a probe request to each of a first device and at least one second device in a communication network, each of the first device and the at least one second device having a same SSID, BSSID, and AID in communication with the third device; receiving a response to the probe request from one of the first device and the at least one second device; and communicating via the one device.
In a ninth aspect of embodiments of the present disclosure, an apparatus for communication is provided. The device includes: means for receiving, at a first device in a communication network, a first request from at least one second device in the communication network to acquire a token for communication by a third device, the first device and the at least one second device each having a same SSID, BSSID, and AID in communication with the third device; means for selecting one device from the at least one second device and the first device as a communication device for providing a communication service for the third device based on the first request; and means for sending the token to the communication device for communication with the third device through the communication device.
In a tenth aspect of embodiments of the present disclosure, an apparatus for communication is provided. The device includes: means for transmitting, at a second device in a communication network, a first request to a first device in the communication network to obtain a token in response to receiving a probe request from a third device, the token being a credential for communicating with the third device, the first device and the at least one second device each having a same SSID, BSSID, and AID in communication with the third device; and means for receiving the token from the first device to communicate with the third device.
In an eleventh aspect of embodiments of the present disclosure, an apparatus for communication is provided. The device includes: means for receiving, at a second device in a communication network, key information related to communication with a third device from a first device in the communication network, the first device and the at least one second device each having the same SSID, BSSID, and AID in communication with the third device; and means for listening for data related to communication of the third device based on the key information.
In a twelfth aspect of embodiments of the present disclosure, an apparatus for communication is provided. The device includes: means for transmitting, at a third device, a probe request to each of a first device and at least one second device in a communication network, each of the first device and the at least one second device having a same SSID, BSSID, and AID in communication with the third device; means for receiving a response to the probe request from one of the first device and the at least one second device; and means for communicating via the one device.
In a thirteenth aspect of embodiments of the present disclosure, a computer-readable storage medium is provided. The computer readable storage medium comprises machine executable instructions which, when executed by a device, cause the device to perform the method according to the fifth aspect of embodiments of the present disclosure described above.
In a fourteenth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. The computer readable storage medium comprises machine executable instructions which, when executed by a device, cause the device to perform the method according to the sixth aspect of an embodiment of the present disclosure as described above.
In a fifteenth aspect of embodiments of the present disclosure, a computer-readable storage medium is provided. The computer readable storage medium comprises machine executable instructions which, when executed by a device, cause the device to perform the method according to the seventh aspect of an embodiment of the present disclosure as described above.
In a sixteenth aspect of embodiments of the present disclosure, a computer-readable storage medium is provided. The computer readable storage medium comprises machine executable instructions which, when executed by a device, cause the device to perform the method according to the eighth aspect of an embodiment of the present disclosure as described above.
According to the scheme of the embodiment of the present disclosure, a new communication mechanism in a communication network is introduced, which enables a plurality of nodes in the communication network to face a terminal device with the same identification information, that is, from the perspective of the terminal device, the plurality of nodes can be regarded as one node. In this case, by adjusting the load balance of the first or second device and capturing the moving path of the third device in time, the optimal communication device can be dynamically selected for the third device, so that the service delay of the terminal device can be greatly reduced. In addition, the reconnection process of the terminal equipment among a plurality of nodes can be greatly reduced, so that the communication safety of the terminal equipment can be ensured.
It should be understood that the statements herein reciting aspects are not intended to limit the critical or essential features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. In the drawings, like or similar reference characters designate like or similar elements, and wherein:
FIG. 1 illustrates a schematic diagram of an example communication system in which embodiments of the present disclosure may be implemented;
FIG. 2 shows a schematic diagram of exemplary interactions between devices in a communication process, according to an embodiment of the disclosure;
fig. 3 shows a flow chart of a communication method implemented at a first device in a communication network according to an embodiment of the present disclosure;
fig. 4 shows a flow chart of a communication method implemented at a second device in a communication network according to an embodiment of the present disclosure;
fig. 5 shows a flow diagram of a communication method implemented at a second device in a communication network according to another embodiment of the present disclosure;
fig. 6 shows a flow chart of a communication method implemented at a third device according to an embodiment of the present disclosure;
FIG. 7 shows a schematic block diagram of an apparatus according to an embodiment of the present disclosure; and
FIG. 8 shows a schematic diagram of a computer-readable storage medium according to an embodiment of the disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been illustrated in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
The terms "include" and variations thereof as used herein are inclusive and open-ended, i.e., "including but not limited to. The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment". Relevant definitions for other terms will be given in the following description.
It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of the embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the listed terms.
The term "circuitry" as used herein refers to one or more of the following:
(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry); and
(b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of analog and/or digital hardware circuitry and software/firmware, and (ii) any portion of a hardware processor in combination with software (including a digital signal processor, software, and memory that work together to cause a device such as an Optical Line Terminal (OLT) or other computing device to perform various functions); and
(c) a hardware circuit and/or processor, such as a microprocessor or a portion of a microprocessor, that requires software (e.g., firmware) for operation, but may lack software when software is not required for operation.
The definition of circuit applies to all usage scenarios of this term in this application, including any claims. As another example, the term "circuitry" as used herein also covers an implementation of merely a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor, or software or firmware accompanying it. For example, the term "circuitry" would also cover a baseband integrated circuit or processor integrated circuit or a similar integrated circuit in an OLT or other computing device, as applicable to the particular claim element.
As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as LTE, LTE-advanced (LTE-a), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), narrowband internet of things (NB-IoT), and so forth. Further, communication between the terminal device and the network devices in the communication network may be performed according to any suitable generation communication protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols and/or first generation (WIFI1), second generation (WIFI2), third generation (WIFI3), fourth generation (WIFI4), fifth generation (WIFI5), sixth generation (WIFI6), future seventh generation (WIFI7) local area network communication protocols and/or any other protocol now known or developed in the future. Embodiments of the present invention are applicable to various communication systems. In view of the rapid development of communication technology, there will of course be future types of communication technology and systems with which the present invention may be combined. It should not be considered as limiting the scope of the disclosure to only the above-described systems.
As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services therefrom. Depending on the terminology and technology applied, a network device may refer to a Base Station (BS) or an Access Point (AP), e.g., a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header (RH), a Remote Radio Header (RRH), a relay, a low power node such as a pico base station or a femto base station, etc.
The term "terminal device" refers to any terminal device capable of wireless communication. By way of example, and not limitation, a terminal device may also be referred to as a communication device, User Equipment (UE), Subscriber Station (SS), portable subscriber station, Mobile Station (MS), or Access Terminal (AT). The end devices may include, but are not limited to, mobile phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable end devices, Personal Digital Assistants (PDAs), portable computers, desktops, image capture end devices such as digital cameras, gaming end devices, music storage and playback devices, in-vehicle wireless end devices, wireless endpoints, mobile stations, notebook embedded devices (LEEs), notebook computer devices (LMEs), USB dongle, smart devices, wireless Customer Premises Equipment (CPE), internet of things (LOT) devices, watches or other wearable devices, Head Mounted Displays (HMDs), vehicles, drones, medical devices and applications (e.g., tele-surgery), industrial devices and applications (e.g., robots and/or other wireless devices in industrial and/or automated processing chain contexts), Consumer electronics devices, devices operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.
As used herein, the term "communication network" may refer to a home network, an enterprise network, or other similar local area network that communicates wirelessly using WiFi, bluetooth, or the like. The communication network may also be any wired or wireless communication network capable of implementing embodiments of the present disclosure. In some embodiments, the communication network may be one of an MBSS and an ESS. In view of the rapid development of communication technology, there will of course be future types of communication technology and networks with which the present invention may be combined. Accordingly, it should not be taken as limiting the scope of the disclosure to only the above-described networks.
In conventional MBSS and ESS networks, each AP node has the same SSID in communication with the end device (i.e., fronthaul), but has a different BSSID. In this case, no matter roaming or load balancing, the terminal device needs to complete authentication connection with the new AP node, and then can obtain internet service through the new AP node. In application scenarios with ultra-large data volume and ultra-low delay, such as AR and VR, the problem of momentary jamming due to delay during roaming occurs, and good customer experience cannot be provided. In addition, re-negotiation of keys may be involved in the connection process. Once subjected to a sniffing attack, causing the key to be captured during the negotiation, there is a potential for leakage and interception of user data.
In the conventional scheme, fast roaming is proposed for the problem of delay in the roaming process, as defined by the 802.11r standard. In this way, the latency can be reduced to 50ms, but the requirement of ultra-low latency for AR/VR cannot still be met. And the AP node and the terminal device are required to support the 802.11r standard to operate normally. For a terminal device which cannot support the 802.11r standard, the operation can be performed only according to the steps of re-association, four-way handshake and application for an IP address. Thus, the latency problem still exists.
In addition, in the conventional scheme, both the 802.1X standard and the Wi-Fi protected access (WPA)3 protocol propose a more secure key agreement mechanism for the problem that a sniffing attack may exist in the key agreement process. These mechanisms require both the AP node and the terminal device to support the 802.1X standard or the WPA3 protocol for proper operation. Most current terminal devices, especially internet of things (IoT) devices, cannot support the 802.1X standard or the WPA3 protocol. Furthermore, the mechanism proposed by the 802.1X standard results in longer latency.
In view of this, embodiments of the present disclosure propose a new communication mechanism in a communication network. In this mechanism, a plurality of AP nodes in a communication network face a terminal device with the same identification information. That is, from the viewpoint of the terminal device, the plurality of AP nodes may be regarded as one node. In this case, since the plurality of AP nodes each have the same identification information in communication with the terminal device, seamless handover can be achieved between the plurality of AP nodes without affecting communication of the terminal device. That is, by cooperation among a plurality of AP nodes, it is possible to make it possible for a terminal device to securely connect to an arbitrary AP node without re-establishing a connection. This can improve the security of communication of the terminal device. In addition, by adjusting the load balance of the first or second device and capturing the moving path of the third device in time, the optimal communication device can be dynamically selected for the third device, thereby greatly reducing the service delay of the terminal device. In addition, most terminal equipment can be well compatible.
Fig. 1 illustrates a schematic diagram of an example communication system 100 in which embodiments of the present disclosure may be implemented. As shown in fig. 1, the system 100 may include a communication network 110, the internet 120, and a device 130 (hereinafter also referred to as a third device 130 for convenience). The third device 130 may be connected to the internet 120 via the communication network 110 for data access. In some embodiments, the third device 130 may be a terminal device. Of course, the embodiments of the present disclosure are not limited thereto, and the third device may be other types of devices.
The communication network 110 may include a first device 111 and second devices 112-1 and 112-2 (which may also be collectively referred to hereinafter as at least one second device 112 for convenience). The first device 111 acts as a root node in the communication network 110 and the second device 112 acts as an extension node in the communication network 110. In some embodiments, the first device 111 and the second device 112 may be routers. Of course, the embodiments of the present disclosure are not limited thereto, and the first device and the second device may be other types of devices. Further, the number of second devices is not limited to the number shown, but may include a greater or lesser number.
The third device 130 may communicate with any AP node in the communication network 110, such as the first device 111 and the second device 112, by way of a wireless link. The nodes in the communication network 110 may communicate with each other via backhaul (backhaul) via wireless links or ethernet links. A first device 111 in the communication network 110 may be connected to the internet 120 through a Wide Area Network (WAN) port. It should be understood that the number of communication networks 110 and third devices 130 is not limited to the example shown in fig. 1, but may include a greater number. Furthermore, their implementation is not limited to the specific examples described above, but may be implemented in any suitable manner.
In an embodiment of the present disclosure, the first device 111 and the second device 112 in the communication network 110 both have the same identification information in the communication (i.e., the forwarding) with the third device 130. Thus, the first device 111 and the second device 112 may be treated as the same node by the third device 130. In some embodiments, the first device 111 and the second device 112 both have the same SSID, BSSID, and AID. In some embodiments, the first device 111 and the second device 112 also both have the same basic service set color (BSS color). In some embodiments, the first device 111 and the second device 112 also both have the same timestamp. For example, the first device 111 and the second device 112 both have the same beacon frame timestamp. Of course, embodiments of the present disclosure are not limited to these specific examples, and any other implementation is possible.
In the embodiment of the present disclosure, after the third device 130 accesses or re-accesses the communication network 110, all AP nodes (e.g., the first device 111 and the second device 112) in the communication network 110 may acquire and update the key information associated with the communication of the third device 130.
In an embodiment of the present disclosure, there is only one token in the communication network 110 that communicates with the third device 130. In some embodiments, only the AP node holding the token can normally communicate with the third device 130, and other AP nodes not holding the token can receive the data sent by the third device 130, but cannot send an acknowledgement message (ACK) and a unicast message (except a null data message (NDP) or a null packet announcement (NDPA) message) to the third device 130.
According to the embodiment of the present disclosure, through cooperation between a plurality of AP nodes such as the first device 111 and the second device 112 in the communication network 110, the third device 130 may be enabled to be securely and seamlessly connected to any AP node, thereby enabling data access to the internet 120. This is explained in more detail below in conjunction with fig. 2-6. Fig. 2 shows a schematic diagram 200 of exemplary interactions between devices during communication, according to an embodiment of the disclosure. For convenience, this is described herein in connection with the example of fig. 1.
Scanning operation of AP node
As shown in fig. 2, for example, when the third device 130 turns on Wi-Fi, the third device 130 may issue a probe request. In some embodiments, the third device 130 may issue probe request frames (probe request frames) to the surroundings. Of course, this is merely an example, and the probe request may take other forms. Accordingly, the second device 112-1 in the communication network 110 may receive 201 the probe request, and the second device 112-2 may also receive 201' the probe request. Further, the first device 111 in the communication network 110 may also receive 201 "the probe request.
In response to receiving the probe request, the second device 112-1 sends 202 a request for obtaining a token (hereinafter also referred to as a first request for convenience) to the first device 111, and the second device 112-1 also sends 202' a request for obtaining a token (hereinafter also referred to as a first request for convenience) to the first device 111. The token is a credential for communicating with the third device 110. For example, each second device 112 that receives a probe request from the third device 130 may simultaneously apply the first device 111 for a token for communication with the third device 130. In some embodiments, the first device 111 may itself generate the token request.
The first device 111, upon receiving the first request from the second devices 112-1 and 112-2, selects 203 one device from the second devices 112-1 and 112-2 and the first device 111 as a communication device for providing a communication service to the third device 130. In some embodiments, the first device 111 may determine whether information for the communication device is stored at the first device 111. If it is determined that information of the communication device is stored, the communication device may be determined from the information. In some embodiments, the first device 111 may locally store a table for recording the issuance, registration, transfer and withdrawal of tokens, such as shown in table 1.
Table 1 example of token related information
Device identification Node information holding token Key information Token expiration time
It should be appreciated that the token related information in table 1 is merely an example, and any other suitable information may also be stored. Moreover, the form of table 1 is merely exemplary, and any other suitable data structure may be employed.
In an example in which the table is stored, the first device 111 may determine whether information of a communication device associated with the third device 130 is stored at the first device 111 based on the table. If information of the communication device associated with the third device 130 is stored in the table, the communication device may be determined from the information.
If the information of the communication device is not stored at the first device 111, for example, if no information associated with the third device 130 is stored in the table, the first device 111 may select the communication device based on a predetermined policy. In some embodiments, the first device 111 may select one device from the second devices 112-1 and 112-2 and the first device 111 as the communication device based on a Received Signal Strength Indication (RSSI) value. For example, the first device 111 may calculate and provide an RSSI value of the third device from the second devices 112-1 and 112-2 and the first device 111 itself, and then determine a device having a larger RSSI value as a communication device for providing a communication service to the third device 130. As another example, the first device 111 may calculate and provide an RSSI value of a third device from the second devices 112-1 and 112-2 and the first device 111, then determine at least one device having an RSSI value higher than a predetermined threshold, and finally randomly select one device from the at least one device as the communication device. Of course, these are merely examples, and any other suitable approach is possible.
In some alternative embodiments, the first device 111 may select one device from the second devices 112-1 and 112-2 and the first device 111 as the communication device based on a load balancing policy. For example, the first device 111 may determine respective loads of the second devices 112-1 and 112-2 and the first device 111 itself, and then determine the second device having a smaller load as a communication device for providing a communication service to the third device 130. As another example, the first device 111 may determine respective loads of the second devices 112-1 and 112-2 and the first device 111 itself, then determine at least one device having a load lower than a predetermined load, and finally randomly select one device from the at least one device as the communication device. Of course, these are merely examples, and any other suitable approach is possible. It should be understood that the above selection may also be performed based on a combination of various policies.
In some embodiments in which information of a communication device associated with the third device 130 is not stored, upon selection of the communication device, the first device 111 may store 204 the information of the selected communication device in association with the third device 130. For example, assuming in this example that the second device 112-1 is determined to be a communication device, the first device 111 may update table 1 as shown below. In this way, token-related information (also referred to as communication information) stored at the first device 111 may be constantly updated, thereby facilitating increased efficiency and reduced latency for subsequent communications.
Table 1 example of token related information
Figure BDA0002633567800000141
The first device 111 may then send 205 a token for communicating with the third device 130 to the second device 112-1, which is a communication device. For example, the first device 111 may indicate the issuance of the token by sending a specific message to the second device 112-1. Of course, it is possible to use other means to indicate the issuance of the token.
The second device 112-1, upon receiving the token, sends 206 a response to the probe request to the third device 130. For example, the second device 112-1 may transmit a probe response frame (probe response frame) to the third device 130. In this way, the third device 130 is enabled to detect the communication network 110.
In some alternative embodiments, the token issuance process may be deferred to an authentication process (authentication process) of the third device 130 for discovery of the third device of the communication network 110 through a Beacon frame (Beacon frame). For example, the third device 130 may receive a beacon frame from the first device 111 or the second device 112 (e.g., periodically broadcast), thereby discovering the communication network 110. The third device 130 may then issue an authentication request, e.g., issue an authentication request frame, to the communication network 110. In response to the authentication request, the communication network 110 may issue a token to the first device 111 or the second device 112. The first device 111 or the second device 112 holding the token may reply to the third device 130 with an acknowledgement (Acknowledge) frame acknowledging receipt of the request and sending a response frame (authentication response frame) to the authentication request.
Access operation of a communication network
Upon receiving the response from the second device 112-1, the third device 130 may complete 207 the association authentication and four-way handshake operation with the second device 112-1 to obtain the Internet Protocol (IP) address from the first device 111.
In some embodiments, the second device 112-1 may send 208 key information associated with the communication of the third device 130 to the first device 111. In some embodiments, the key information may include a Pairwise Transient Key (PTK). In some embodiments, the key information may further include at least one group key of: a Group Temporary Key (GTK) and an Integrity Group Temporary Key (IGTK). Of course, other key forms are possible, and the application is not limited thereto.
In some embodiments, the first device 111, upon receiving the key information, may store 209 the key information in association with the third device 130. For example, table 1 may be updated as shown below. Of course, storage may be performed in other ways.
Table 1 example of token related information
Figure BDA0002633567800000151
In some embodiments, the first device 111 may distribute 210 the key information to the second devices 112-1 and 112-2 and to other devices in the first device 111 other than the communication device (e.g., the second device 112-2 and the first device 111 itself). Thus, the second device 112-2 and the first device 111 may listen for data associated with communication with the third device 130 based on the key information. In other words, the second device 112-2 and the first device 111 wait for communication with the third device 130.
Roaming operations
In embodiments where the second device 112-1 is determined to be a communication device, when the third device 130 moves from location a to location B, the second device 112-1 may determine 211 whether an RSSI value associated with the communication received by the second device 112-1 with the third device 130 is below a predetermined threshold (also referred to below as a fourth threshold for convenience). The second device 112-1 may trigger the roaming mechanism if the RSSI value associated with the communication with the third device 130 is below a fourth threshold. In this case, the second device 112-1 may send 212 a request for roaming of the third device 130 (hereinafter also referred to as a second request for convenience) to the first device 111. In some embodiments, the second request may include the token and cached data associated with the third device 130 at the second device 112-1. The data, i.e., data associated with the third device 130 that is not being processed by the second device 112-1, is buffered.
In response to receiving the roaming request, the first device 111 may select 213 one device from the second devices 112-1 and 112-2 and the first device 111 as a candidate device (hereinafter also referred to as a first candidate device for convenience) for subsequent use in communicating with the third device 130. In this example, assume that the second device 112-2 is the candidate device. In some embodiments, the first device 111 may select one device having an RSSI value higher than a predetermined threshold (hereinafter also referred to as a first threshold for convenience) as the first candidate device. In some embodiments, the first device 111 may select the device with the highest RSSI value as the first candidate device. It should be appreciated that the selection of the first candidate device may be implemented in any suitable manner and is not limited to the above examples.
After determining the first candidate device, the first device 111 may send 214 the token received back from the second device 112-1 and the cached data associated with the third device 130 from the second device 112-1 to the second device 112-2 as the candidate device. In the case where each of the first device 111 and the second device 112 in the communication network 110 are in the same operating channel, the second device 112-2 can communicate directly with the third device 130 after obtaining the token and the cache data.
In some embodiments, the first device 111 may determine 215 whether the communication device (in this case, the second device 112-1) and the first candidate device (in this case, the second device 112-2) are on the same operating channel. If the first device 111 determines that the communication device and the first candidate device are on different operating channels, e.g., a first operating channel and a second operating channel, respectively, the first device 111 notifies 216 the second device 112-1 to cause the third device 130 to switch to the second operating channel on which the first candidate device is located. In some embodiments, first device 111 may transmit a Channel Switch Announcement (CSA) message to second device 112-1, in which indication information of the second working channel and identification information of third device 130 may be included. Of course, messages in other known or future developed forms are possible and are not limited by this application.
The second device 112-1, upon receiving the notification, may request 217 the third device 130 to switch from the first operating channel to the second operating channel. For example, second device 112-1 may send an action frame with CSA IE unicast to third device 130. Of course, this is merely an example, and other suitable manners may be used to request the third device 130 to switch the working channel.
In response to the request, the third device 130 may switch 218 from the first operating channel to the second operating channel. The second device 112-2 may then communicate 219 directly with the third device 130.
In some embodiments, the second device 112-2 may send 220 an indication (hereinafter also referred to as a first indication for convenience) to the first device 111 that the roaming of the third device 130 is complete. In this way, the second device 112-2 may report the event of the completion of the roaming of the third device 130 to the first device 111. Based on the indication, the first device 111 may update 221 information of the communication device associated with the third device 130. For example, the node information holding the token in Table I may be updated from the first device 112-1 to the second device 112-2, as shown below. Thus, the roaming operation of the third device 130 from the second device 112-1 to the second device 112-2 is completed.
Table 1 example of token related information
Figure BDA0002633567800000171
Load balancing operations
In some embodiments, the second device 112-1 may determine 222 whether the load of the second device 112-1 exceeds a predetermined threshold (also referred to below as a fifth threshold for convenience). When the load of the second device 112-1 exceeds the fifth threshold, the second device 112-1 may trigger a load balancing mechanism. In this case, the second device 112-1 may send 223 a load balancing request (hereinafter also referred to as a third request for convenience) to the first device 111. In some embodiments, the third request may include the token and cached data associated with the third device 130 at the second device 112-1. The data, i.e., data associated with the third device 130 that is not being processed by the second device 112-1, is buffered.
In response to receiving the load balancing request, the first device 111 may select 224 one device from the second devices 112-1 and 112-2 and the first device 111 as a candidate device (hereinafter also referred to as a second candidate device for convenience) for subsequent communication with the third device 130. In this example, assume that the second device 112-2 is the candidate device. In some embodiments, the first device 111 may select one device having an RSSI value higher than a predetermined RSSI value (also referred to as a second threshold value for convenience) and having a load lower than a predetermined load (also referred to as a third threshold value for convenience) as the second candidate device. In some alternative embodiments, the first device 111 may select the device with the highest RSSI value as the second candidate device. In some alternative embodiments, the first device 111 may also select the device with the lowest load as the second candidate device. It should be appreciated that the selection of the second candidate device may be implemented in any suitable manner and is not limited to the above examples.
After determining the second candidate device, the first device 111 may send 225 the token received back from the second device 112-1 and the cached data from the second device 112-1 to the second device 112-2 as the candidate device. In the case where each of the first device 111 and the second device 112 in the communication network 110 are in the same operating channel, the second device 112-2 can communicate directly with the third device 130 after obtaining the token and the cache data.
In some embodiments, the first device 111 may determine 226 whether the communication device (in this case, the second device 112-1) and the second candidate device (in this case, the second device 112-2) are on the same operating channel. If the first device 111 determines that the communication device and the second candidate device are in different operating channels, e.g., a first operating channel and a second operating channel, respectively, the first device 111 notifies 227 the second device 112-1 to cause the third device 130 to switch to the second operating channel in which the second candidate device is located. In some embodiments, first device 111 may transmit a CSA message to second device 112-1, in which indication information of the second working channel and identification information of third device 130 may be included. Of course, messages in other known or future developed forms are possible and are not limited by this application.
The second device 112-1, upon receiving the notification, may request 228 the third device 130 to switch from the first operating channel to the second operating channel. For example, second device 112-1 may send an action frame with CSA IE unicast to third device 130. Of course, this is merely an example, and other suitable manners may be used to request the third device 130 to switch the working channel.
In response to the request, the third device 130 may switch 229 from the first operating channel to the second operating channel. In turn, the second device 112-2 may communicate 230 directly with the third device 130.
In some embodiments, the second device 112-2 may send 231 an indication (also referred to below as a second indication for convenience) to the first device 111 that the load balancing of the third device 130 is complete. In this way, the second device 112-2 may report to the first device 111 an event that the load balancing of the third device 130 is complete. Based on the indication, the first device 111 may update 232 information of the communication device associated with the third device 130. For example, the node information holding the token in Table I may be updated from the first device 112-1 to the second device 112-2, as shown below. Thus, the load balancing operation of the third device 130 between the second device 112-1 and the second device 112-2 is completed.
Table 1 example of token related information
Figure BDA0002633567800000191
In some embodiments, in response to first device 111 updating locally stored token related information, first device 111 may update a forwarding table (FBT) to indicate that third device 130 obtained internet service via the new AP node.
Operation of disconnection
In some embodiments, for example, when the third device 130 turns off Wi-Fi, the third device 130 may send 233 a request to disconnect to a second device (e.g., the second device 112-1) for which communication services are being provided at that time. In some embodiments, the third device 130 may send a de-authentication frame (de-authentication frame) to the second device 112-1. In some embodiments, the third device 130 may send a de-association frame (de-association frame) to the second device 112-1.
The second device 112-1 may delete 234 the key information associated with the third device 130 from the second device 112-1 in response to receiving the request to disconnect from the third device 130. Thereby disconnecting the third device 130. In some embodiments, the second device 112-1 may send 235 to the first device 111 a request for disconnection of the third device 130 (also referred to herein as a third request for convenience). In other words, the second device 112-1 may report the request for disconnection of the third device 130 to the first device 111.
In response to receiving the third request, the first device 111 may delete 236 locally stored key information associated with the third device 130. For example, the key information associated with the third device 130 in table 1 is deleted, as shown below.
Table 1 example of token related information
Figure BDA0002633567800000201
In some embodiments, the first device 111 may send 237 an indication to the second device 112-2 to delete key information associated with the third device 130. Based on the indication, the second device 112-2 may delete the key information associated with the third device 130. Thus, the second device 112-2 cancels listening for the communication of the third device 130.
Token expiration operations
In some embodiments, if the communication network 110 no longer detects the signal of the third device 130 within a certain period of time, it determines that the token of the third device 130 is expired, and thus may trigger a token expiration operation. For example, the current communication device (i.e., the AP node holding the token) is the second device 112-1. In some embodiments, the second device 112-1 may determine 239 whether a signal from the third device 130 has not been detected within a certain period of time. If it is determined that a signal from the third device 130 has not been detected within a certain period of time, the second device 112-1 may send 240 an indication (hereinafter also referred to as a third indication for convenience) to the first device 111 that a token associated with the third device 130 is expired.
Based on the third indication, first device 111 may reclaim the token from second device 112-1 and delete 241 communication information associated with third device 130 stored at first device 111. For example, the first device 111 may delete the entry in table 1 associated with the third device 130, as shown below.
Table 1 example of token related information
Figure BDA0002633567800000202
Simulation result
The inventors have performed simulations for different security modes. Table 2 below shows an example of simulation results of the time delay.
Table 2 example of delay simulation results for different security modes
Figure BDA0002633567800000211
It can be seen that the latency can be significantly reduced according to the scheme of the embodiment of the present disclosure compared to the conventional scheme.
Thus far, an example communication procedure in a communication network according to an embodiment of the present disclosure has been described. It should be understood that the process may also include more additional steps or omit some of the steps shown, and is not limited to the example of fig. 2. Accordingly, embodiments of the present disclosure also provide methods implemented at a first device as a root node in a communication network, a second device as an extension node in a communication network, and a third device for communicating via a communication network. As described in detail below in conjunction with fig. 3-6.
Fig. 3 shows a flow diagram of a communication method 300 implemented at a first device in a communication network, in accordance with an embodiment of the present disclosure. The method 300 may be implemented, for example, at the first device 111 of fig. 1 as a root node. For convenience, the following is described in connection with the example of fig. 1.
As shown in fig. 3, at block 310, the first device 111 receives a first request from at least one second device 112 in the communication network 110 to obtain a token, which is a credential for communicating with the third device 130.
In block 320, the first device 111 selects one device from the at least one second device 112 and the first device 111 as a communication device providing a communication service for the third device 130 based on the first request. In some embodiments, the first device 111 may select one device by: determining whether communication device information associated with the third device 130 is stored at the first device 111; determining the communication device from the communication device information if it is determined that the communication device information is stored at the first device 111; and determining one device as the communication device from among the at least one second device 112 and the first device 111 based on a predetermined policy if the communication device information is not stored at the first device 111. In some embodiments, the predetermined policy may be based on at least one of RSSI values and load.
In block 330, the first device 111 sends a token to the communication device to communicate with the third device 130 through the communication device.
In some embodiments, the first device 111 and the at least one second device 112 each have the same SSID, BSSID, and AID in communication with the third device 130. In some embodiments, the first device 111 and the at least one second device 112 may also each have at least one of the following in communication with the third device 130: the same basic service set color; and the same time stamp.
In some embodiments, the first device 111 may store the information of the communication device and the token in association with the third device 130.
In some embodiments, the first device 111 may receive key information from the communication device, the key information being associated with the communication of the third device 130; and transmitting the key information to at least one second device 112 and a second device other than the communication device among the first devices 111. In some embodiments, the first device 111 may update the key information associated with the third device 130 stored at the first device based on the received key information.
In some embodiments, the first device 111 may receive a second request from the communication device for roaming of the third device 130, the second request including buffered data at the communication device related to the third device 130, select one of the at least one second device 112 and the first device 111 as a first candidate device, the first candidate device having an RSSI value above a first threshold; and sending the token and the cached data to the first candidate device.
In some embodiments, the first device 111 may notify the communication device to switch the third device 130 to the second operating channel in response to determining that the communication device and the first candidate device are in the first operating channel and the second operating channel, respectively.
In some embodiments, the first device 111 may receive a first indication from the first candidate device that roaming of the third device 130 is complete; and updating the information of the communication device associated with the third device 130 stored at the first device 111 to the information of the first candidate device based on the first indication.
In some embodiments, the first device 111 may receive a third request from the communication device for load balancing of the third device 130, the third request including cached data at the communication device related to the third device 130; selecting one device from the at least one second device 112 and the first device 111 as a second candidate device based on the third request, the second candidate device having an RSSI value above the second threshold and a load below a third threshold; and sending the token and the cached data to the second candidate device.
In some embodiments, the first device 111 may notify the communication device to switch the third device 130 to the second operating channel in response to determining that the communication device and the second candidate device are in the first operating channel and the second operating channel, respectively.
In some embodiments, the first device 111 may receive a second indication from the second candidate device that load balancing of the third device 130 is complete; and updating the information of the second device associated with the third device 130 stored at the first device 111 to the information of the second candidate device based on the second indication.
In some embodiments, the first device 111 may receive a third request from the communication device to disconnect from the third device 130; deleting key information associated with the third device 130 stored at the first device 111 based on the third request; and transmitting an indication for deleting the key information to a device other than the communication device among the at least one second device 112 and the first device 111.
In some embodiments, the first device 111 may receive a third indication from the communication device that the token of the third device 130 is expired; and deleting the communication information associated with the third device 130 stored at the first device 111 based on the third indication.
In some embodiments, the first device 111 may be a router that is a root node in the communication network 110, the second device 112 may be a router that is an extension node in the communication network 110, and the third device 130 may be a terminal device. In some embodiments, the communication network 110 may be one of an ESS and an MBSS. Of course, communication network 100 is not so limited, but may include any other suitable network known in the art or developed in the future.
Fig. 4 shows a flow diagram of a method 400 implemented at a second device in a communication network, in accordance with an embodiment of the present disclosure. The method 400 may be implemented, for example, at any of the second devices 112-1 and 112-2 of FIG. 1. For convenience of description, the following description will be made taking an embodiment at the second device 112-1 as an example. For convenience, the following is described in connection with the example of fig. 1.
As shown in fig. 4, in response to receiving the probe request from the third device 130, the second device 112-1 sends a first request to the first device 111 in the communication network 110 to obtain a token, which is a credential for communicating with the third device 130, at block 410.
At block 420, the second device 112-1 receives the token from the first device 111 to communicate with the third device 130. In some embodiments, the first device 111 and the at least one second device 112 each have the same SSID, BSSID, and AID in communication with the third device 130. In some embodiments, the first device 111 and the at least one second device 112 may also each have at least one of the following in communication with the third device 130: the same basic service set color; and the same time stamp.
In some embodiments, the second device 112-1 may send a response to the probe request to the third device 130 in response to receiving the token. In some embodiments, second device 112-1 may send key information associated with the communication of third device 130 to first device 111.
In some embodiments, the second device 112-1 may send a second request to the first device 111 for roaming of the third device 130 in response to the third device 130 moving from the first location to the second location and the RSSI value for the third device 130 being below a fourth threshold, the second request including the token and cached data at the second device 112-1 related to the third device 130. In some embodiments, the second device 112-1 may receive a notification from the first device 111 indicating to switch the third device 130 from the first operating channel to the second operating channel; and requesting the third device 130 to switch to the second operating channel in response to the notification.
In some embodiments, the second device 112-1 may send a third request for load balancing of the third device 130 to the first device 111 in response to the load of the second device 112-1 exceeding a fifth threshold, the third request including the token and cached data associated with the third device 130 at the second device 112-1. In some embodiments, the second device 112-1 may receive a notification from the first device 111 indicating to switch the third device 130 from the first operating channel to the second operating channel; and requesting the third device 130 to switch to the second operating channel in response to the notification.
In some embodiments, the second device 112-1 may delete the key information associated with the third device 130 in response to receiving a request to disconnect from the third device 130; and sending a third request to the first device 111 for disconnection of the third device 130.
In some embodiments, the second device 112-1 may send an indication to the first device 111 that the token of the third device 130 is expired.
In some embodiments, the first device 111 may be a router that is a root node in the communication network 110, the second device 112 may be a router that is an extension node in the communication network 110, and the third device 130 may be a terminal device. In some embodiments, the communication network 110 may be one of an ESS and an MBSS. Of course, communication network 100 is not so limited, but may include any other suitable network known in the art or developed in the future.
Fig. 5 shows a flow diagram of a method 500 implemented at a second device in a communication network, according to another embodiment of the present disclosure. The method 500 may be implemented, for example, at any of the second devices 112-1 and 112-2 of FIG. 1. For ease of description, the following description will be made taking the embodiment at the second device 112-2 as an example. For convenience, the following is described in connection with the example of fig. 1.
As shown in fig. 5, at block 510, the second device 112-2 receives key information associated with communication with the third device 130 from the first device 111 in the communication network 110.
At block 520, the second device 112-2 listens for data associated with the communication with the third device 130 based on the key information.
In some embodiments, the first device 111 and the at least one second device 112 each have the same SSID, BSSID, and AID in communication with the third device 130. In some embodiments, the first device 111 and the at least one second device 112 may also each have at least one of the following in communication with the third device 130: the same basic service set color; and the same time stamp.
In some embodiments, the second device 112-2 may also send, in response to receiving the probe request from the third device 130, a first request to the first device 111 to obtain a token, which is a credential for communicating with the third device 130.
In some embodiments, the second device 112-2 may also receive a token associated with the communication with the third device 130 from the first device 111 and cached data related to the third device 130 at the second device 112-2; and performing communication for the third device 130 based on the token and the cache data. In some embodiments, the second device 112-2 may perform communication for the third device 130 by: the communication of the third device 130 is performed in response to the third device 130 switching from the first operating channel to the second operating channel in which the second device is located.
In some embodiments, the second device 112-2 may also send a first indication to the first device 111 that the roaming of the third device 130 is complete. In some embodiments, the second device 112-2 may also send a second indication to the first device 111 that the load balancing of the third device 130 is complete. In some embodiments, the second device 112-2 may also receive an indication from the first device 111 to delete the key information; and deleting the key information based on the indication.
In some embodiments, the first device 111 may be a router that is a root node in the communication network 110, the second device 112 may be a router that is an extension node in the communication network 110, and the third device 130 may be a terminal device. In some embodiments, the communication network 110 may be one of an ESS and an MBSS. Of course, communication network 100 is not so limited, but may include any other suitable network known in the art or developed in the future.
Fig. 6 shows a flow diagram of a method 600 implemented at a third device in accordance with an embodiment of the present disclosure. The method 600 may be implemented, for example, at the third device 130 of fig. 1. For convenience, the following is described in connection with the example of fig. 1.
As shown in fig. 6, at block 610, the third device 130 sends a probe request to each of the first device 111 and the at least one second device 112 in the communication network 110. In an embodiment of the present disclosure, each of the first device 111 and the at least one second device 112 has the same SSID, BSSID, and AID in communication with the third device 130. In some embodiments, the first device 111 and the at least one second device 112 may also each have at least one of the following in communication with the third device 130: the same basic service set color; and the same time stamp.
At block 620, the third device 130 receives a response to the probe request from one of the first device 111 and the at least one second device 112.
At block 630, the third device 130 communicates via the one device.
In some embodiments, the third device 130 may also receive an indication from one device to switch from the first operating channel to the second operating channel via a dedicated message; and performing a handover from the first operating channel to the second operating channel based on the indication.
In some embodiments, the third device 130 may also send a request to disconnect to the one device.
In some embodiments, the first device 111 may be a router that is a root node in the communication network 110, the second device 112 may be a router that is an extension node in the communication network 110, and the third device 130 may be a terminal device. In some embodiments, the communication network 110 may be one of an ESS and an MBSS. Of course, communication network 100 is not so limited, but may include any other suitable network known in the art or developed in the future.
A communication method in a communication network according to an embodiment of the present disclosure has been described so far. Other details can be found in the corresponding description above in connection with fig. 2 and will not be described here. According to the method of the embodiment of the disclosure, the terminal device can be safely and seamlessly connected to any AP node through cooperation among a plurality of AP nodes without reestablishing the connection. Therefore, the communication safety of the terminal equipment can be improved, and the service time delay of the terminal equipment is greatly reduced. In addition, most terminal equipment can be well compatible.
Corresponding to the method, the embodiment of the disclosure also provides a corresponding device. An apparatus capable of performing the method 300 may include corresponding means for performing the steps of the method 300. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module. In some embodiments, the apparatus may be implemented on a root node (such as the first device 111 of fig. 1) in a communication network.
In some embodiments, the apparatus may comprise: means for receiving, at a first device 111 in the communication network 110, a first request from at least one second device 112 in the communication network 110 to obtain a token, the token being a credential for communicating with a third device 130, each of the first device 111 and the at least one second device 112 having the same SSID, BSSID, and AID in communication with the third device 130; means for selecting one device from the at least one second device 112 and the first device 111 as a communication device for providing a communication service to the third device 130 based on the first request; and means for sending the token to a communication device for communication with a third device 130 through the communication device.
An apparatus capable of performing the method 400 may include corresponding means for performing the steps of the method 400. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module. The apparatus may be implemented at an expansion node in a communication network, such as any of the second devices 112-1 and 112-2, here exemplified by the second device 112-1.
In some embodiments, the apparatus may comprise: means for sending, at a second device 112-1 in the communication network 110, in response to receiving a probe request from a third device 130, a first request to a first device 111 in the communication network 110 for obtaining a token, the token being a credential for communicating with the third device 130, each of the first device 111 and the at least one second device 112 having the same SSID, BSSID, and AID in communication with the third device 130; and means for receiving the token from the first device 111 to communicate with the third device 130.
An apparatus capable of performing the method 500 may include corresponding means for performing the steps of the method 500. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module. The apparatus may be implemented at an expansion node in a communication network, such as any of the second devices 112-1 and 112-2, here exemplified by the second device 112-2.
In some embodiments, the apparatus may comprise: means for receiving, at a second device 112-2 in the communication network 110, key information associated with communication with a third device 130 from a first device 111 in the communication network 110, each of the first device 111 and the at least one second device 112 having the same SSID, BSSID, and AID in communication with the third device 130; and means for listening for data associated with communication with the third device 130 based on the key information.
An apparatus capable of performing the method 600 may include corresponding means for performing the steps of the method 600. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module. The apparatus may be implemented at a third device for communicating via a communication network, such as third device 130.
In some embodiments, the apparatus may comprise: means for transmitting, at the third device 130, a probe request to each of the first device 111 and the at least one second device 120 in the communication network 110, each of the first device 111 and the at least one second device 120 having the same SSID, BSSID, and AID in communication with the third device 130; means for receiving a response to the probe request from one of the first device 111 and the at least one second device 112; and means for communicating via the one device.
Fig. 7 is a simplified block diagram of a device 700 suitable for implementing embodiments of the present disclosure. The device 700 may be provided to implement communication devices such as the first device 111, the second device 112-1, the second device 112-2, and the third device 130 shown in fig. 1. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processors 710, and one or more communication modules 740 coupled to the processors 710.
The communication module 740 is used for bidirectional communication. A communication interface may represent any interface necessary to communicate with other network elements.
The processor 710 may be of any type suitable for a local technology network, and may include one or more of the following, as limiting examples: general purpose computers, special purpose computers, microprocessors, Digital Signal Processors (DSPs) and processors based on a multi-core processor architecture. The device 700 may have multiple processors, such as application specific integrated circuit chips, that are time dependent from a clock synchronized with the main processor.
Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, Read Only Memory (ROM)724, Electrically Programmable Read Only Memory (EPROM), flash memory, a hard disk, a Compact Disk (CD), a Digital Video Disk (DVD), and other magnetic storage and/or optical storage devices. Examples of volatile memory include, but are not limited to, Random Access Memory (RAM)722 and other volatile memory that does not persist for the duration of the power down.
The computer programs 730 include computer-executable instructions that are executed by the associated processor 710. The program 730 may be stored in the ROM 720. Processor 710 may perform any suitable actions and processes by loading programs 730 into RAM 720.
Embodiments of the present disclosure may be implemented by way of program 730 such that device 700 may perform any of the processes of the present disclosure as discussed with reference to fig. 2-6. Embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
In some embodiments, the program 730 can be tangibly embodied in a computer-readable medium, which can be included in the device 700 (such as in the memory 720) or other storage device accessible by the device 700. The program 730 may be loaded from a computer-readable medium into the RAM 722 for execution. The computer readable medium may include any type of tangible, non-volatile memory, such as ROM, EPROM, flash memory, a hard disk, a CD, a DVD, etc. Fig. 8 shows an example of a computer readable medium 800 in the form of a CD or DVD. The program 730 is stored on a computer readable medium.
In general, the various example embodiments of this disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Certain aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While aspects of embodiments of the disclosure have been illustrated or described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. Examples of hardware devices that may be used to implement embodiments of the present disclosure include, but are not limited to: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
By way of example, embodiments of the disclosure may be described in the context of machine-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or divided between program modules as described. Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed facility, program modules may be located in both local and remote memory storage media.
Computer program code for implementing the methods of the present disclosure may be written in one or more programming languages. These computer program codes may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the computer or other programmable data processing apparatus, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. The program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server.
In the context of the present disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations described above. Examples of a carrier include a signal, computer readable medium, and the like.
Examples of signals may include electrical, optical, radio, acoustic, or other forms of propagated signals, such as carrier waves, infrared signals, and the like.
A machine-readable medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More detailed examples of a machine-readable storage medium include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical storage device, a magnetic storage device, or any suitable combination thereof.
Additionally, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking or parallel processing may be beneficial. Likewise, while the above discussion contains certain specific implementation details, this should not be construed as limiting the scope of any invention or claims, but rather as describing particular embodiments that may be directed to particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (53)

1. A first device in a communication network, comprising:
a processor; and
a memory coupled with the processor, the memory having instructions stored therein that, when executed by the processor, cause the first device to:
receiving a first request from at least one second device in the communication network to obtain a token, the token being a credential for communicating with a third device, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device;
selecting one device from the at least one second device and the first device as a communication device in the communication network for providing a communication service for the third device based on the first request; and
sending the token to the communication device to communicate with the third device through the communication device.
2. The first device of claim 1, wherein the first device and the at least one second device each further have at least one of the following in communication with the third device: the same basic service set color; and the same time stamp.
3. The first device of claim 1, wherein the first device is caused to select the communication device by:
determining whether information of the communication device is stored at the first device;
determining the communication device from the information of the communication device if it is determined that the information of the communication device is stored at the first device; and
determining the communication device from the at least one second device and the first device based on a predetermined policy if the information of the communication device is not stored at the first device.
4. The first device of claim 3, wherein the predetermined policy is based on at least one of a received signal strength indicator value and a load.
5. The first device of claim 1, wherein the first device is further caused to:
storing information of the communication device and the token in association with the third device.
6. The first device of claim 1, wherein the first device is further caused to:
receiving key information from the communication device, the key information being associated with the communication of the third device; and
and sending the key information to the at least one second device and the devices except the communication device in the first device.
7. The first device of claim 6, wherein the first device is further caused to:
updating key information associated with the third device stored at the first device based on the received key information.
8. The first device of claim 1, wherein the first device is further caused to:
receiving a second request from the communication device for roaming of the third device, the second request including cached data at the communication device related to the third device;
selecting one device from the at least one second device and the first device as a first candidate device having a received signal strength indicator value above a first threshold; and
sending the token and the cached data to the first candidate device.
9. The first device of claim 8, wherein the first device is further caused to:
in response to determining that the communication device and the first candidate device are in a first operating channel and a second operating channel, respectively, notifying the communication device to switch the third device to the second operating channel.
10. The first device of claim 8, wherein the first device is further caused to:
receiving a first indication from the first candidate device that roaming of the third device is complete; and
updating information of a communication device associated with the third device stored at the first device to information of the first candidate device based on the first indication.
11. The first device of claim 1, wherein the first device is further caused to:
receiving a third request from the communication device for load balancing of the third device, the third request including cached data at the communication device related to the third device;
selecting one device from the at least one second device and the first device as a second candidate device based on the third request, the second candidate device having a received signal strength indicator value above a second threshold and a load below a third threshold; and
sending the token and the cached data to the second candidate device.
12. The first device of claim 11, wherein the first device is further caused to:
notifying the communication device to switch the third device to the second working channel in response to determining that the communication device and the second candidate device are in the first working channel and the second working channel, respectively.
13. The first device of claim 11, wherein the first device is further caused to:
receiving a second indication from the second candidate device that load balancing of the third device is complete; and
updating information of a communication device associated with the third device stored at the first device to information of the second candidate device based on the second indication.
14. The first device of claim 1, wherein the first device is further caused to:
receiving a third request from the communication device to disconnect from the third device;
deleting key information associated with the third device stored at the first device based on the third request; and
sending an indication for deleting the key information to the at least one second device and a device other than the communication device among the first devices.
15. The first device of claim 1, wherein the first device is further caused to:
receiving a third indication from the communication device that the token of the third device is expired; and
deleting communication information associated with the third device stored at the first device based on the third indication.
16. The first device of any of claims 1-15, wherein the first device is a router that is a root node in the communication network, the second device is a router that is an extension node in the communication network, and the third device is a terminal device, and
wherein the communication network is one of an Extended Service Set (ESS) network and a mesh basic service set network (MBSS).
17. A second device in a communication network, comprising:
a processor; and
a memory coupled with the processor, the memory having instructions stored therein that, when executed by the processor, cause the second device to:
in response to receiving a probe request from a third device, sending a first request to a first device in the communication network for obtaining a token, the token being a credential for communicating with the third device, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device; and
receiving the token from the first device to communicate with the third device.
18. The second device of claim 17, wherein the first device and the at least one second device each further have at least one of the following in communication with the third device: the same basic service set color; and the same time stamp.
19. The second device of claim 17, wherein the second device is further caused to:
in response to receiving the token, sending a response to the probe request to the third device.
20. The second device of claim 17, wherein the second device is further caused to:
sending, to the first device, key information associated with communication with the third device.
21. The second device of claim 17, wherein the second device is further caused to:
in response to the third device moving from a first location to a second location and a received signal strength indicator value for the third device being below a fourth threshold, sending a second request to the first device for roaming of the third device, the second request including the token and buffered data at the second device related to the third device.
22. The second device of claim 21, wherein the second device is further caused to:
receiving a notification from the first device, the notification indicating to switch the third device from a first operating channel to a second operating channel; and
requesting the third device to switch to the second operating channel in response to the notification.
23. The second device of claim 17, wherein the second device is further caused to:
in response to the load of the second device exceeding a fifth threshold, sending a third request to the first device for load balancing of the third device, the third request including the token and cached data at the second device related to the third device.
24. The second device of claim 23, wherein the second device is further caused to:
receiving a notification from the first device, the notification indicating to switch the third device from a first operating channel to a second operating channel; and
requesting the third device to switch to the second operating channel in response to the notification.
25. The second device of claim 17, wherein the second device is further caused to:
deleting key information associated with communication of the third device in response to receiving a request to disconnect from the third device; and
sending a third request to the first device for disconnection of the third device.
26. The second device of claim 17, wherein the second device is further caused to:
sending an indication to the first device that the token of the third device is expired.
27. The second device of any of claims 17-26, wherein the first device is a router as a root node in the communication network, the second device is a router as an extension node in the communication network, and the third device is a terminal device, and
wherein the communication network is one of an Extended Service Set (ESS) network and a mesh basic service set network (MBSS).
28. A second device in a communication network, comprising:
a processor; and
a memory coupled with the processor, the memory having instructions stored therein that, when executed by the processor, cause the second device to:
receiving key information associated with communication with a third device from a first device in the communication network, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device; and
listen for data associated with communication with the third device based on the key information.
29. The second device of claim 28, wherein the first device and the at least one second device each further have at least one of the following in communication with the third device: the same basic service set color; and the same time stamp.
30. The second device of claim 28, wherein the second device is further caused to:
in response to receiving a probe request from the third device, sending a first request to the first device to obtain a token, the token being a credential for communicating with the third device.
31. The second device of claim 28, wherein the second device is further caused to:
receiving a token associated with the communication of the third device from the first device and cached data related to the third device at the second device; and
performing communication for the third device based on the token and the cached data.
32. The second device of claim 31, wherein the second device is further caused to:
sending a first indication to the first device that roaming of the third device is complete.
33. The second device of claim 31, wherein the second device is caused to perform the communication of the third device by:
and responding to the third equipment switching from the first working channel to the second working channel where the second equipment is positioned, and executing the communication of the third equipment.
34. The second device of claim 31, wherein the second device is further caused to:
sending a second indication to the first device that load balancing of the third device is complete.
35. The second device of claim 28, wherein the second device is further caused to:
receiving an indication from the first device to delete the key information; and
based on the indication, deleting the key information.
36. The second device of any of claims 28-35, wherein the first device is a router as a root node in the communication network, the second device is a router as an extension node in the communication network, and the third device is a terminal device, and
wherein the communication network is one of an Extended Service Set (ESS) network and a mesh basic service set network (MBSS).
37. A third device, comprising:
a processor; and
a memory coupled with the processor, the memory having instructions stored therein that, when executed by the processor, cause the third device to:
transmitting a probe request to each of a first device and at least one second device in a communication network, each of the first device and the at least one second device having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device;
receiving a response to the probe request from one of the first device and the at least one second device; and
communicating via the one device.
38. The third device of claim 37, wherein the first device and the at least one second device each further have at least one of the following in communication with the third device: the same basic service set color; and the same time stamp.
39. The third device of claim 37, the third device further caused to:
receiving, via a dedicated message, an indication from the one device to switch from a first operating channel to a second operating channel; and
performing a handover from the first operating channel to the second operating channel based on the indication.
40. The third device of claim 37, the third device further caused to:
sending a request to disconnect to the one device.
41. The third device of any of claims 37-40, wherein the first device is a router as a root node in the communication network, the second device is a router as an extension node in the communication network, and the third device is a terminal device, and
wherein the communication network is one of an Extended Service Set (ESS) network and a mesh basic service set network (MBSS).
42. A method for communication, comprising:
receiving, at a first device in a communication network, a first request from at least one second device in the communication network to obtain a token, the token being a credential for communicating with a third device, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device;
selecting one device from the at least one second device and the first device as a communication device in the communication network for providing a communication service for the third device based on the first request; and
sending the token to the communication device to communicate with the third device through the communication device.
43. A method for communication, comprising:
at a second device in a communication network, in response to receiving a probe request from a third device, sending a first request to a first device in the communication network to obtain a token, the token being a credential for communicating with the third device, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device; and
receiving the token from the first device to communicate with the third device.
44. A method for communication, comprising:
receiving, at a second device in a communication network, key information associated with communication with a third device from a first device in the communication network, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device; and
listen for data associated with communication with the third device based on the key information.
45. A method for communication, comprising:
transmitting, at a third device, a probe request to each of a first device and at least one second device in a communication network, each of the first device and the at least one second device having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device;
receiving a response to the probe request from one of the first device and the at least one second device; and
communicating via the one device.
46. An apparatus for communication, comprising:
means for receiving, at a first device in a communication network, a first request from at least one second device in the communication network to obtain a token, the token being a credential for communicating with a third device, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device;
means for selecting one device from the at least one second device and the first device as a communication device in the communication network for providing communication services for the third device based on the first request; and
means for sending the token to the communication device to communicate with the third device through the communication device.
47. An apparatus for communication, comprising:
means for transmitting, at a second device in a communication network, a first request to a first device in the communication network to obtain a token in response to receiving a probe request from a third device, the token being a credential for communicating with the third device, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device; and
means for receiving the token from the first device to communicate with the third device.
48. An apparatus for communication, comprising:
means for receiving, at a second device in a communication network, key information associated with communication with a third device from a first device in the communication network, the first device and the at least one second device each having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device; and
means for listening for data associated with communication with the third device based on the key information.
49. An apparatus for communication, comprising:
means for transmitting, at a third device, a probe request to each of a first device and at least one second device in a communication network, each of the first device and the at least one second device having a same Service Set Identification (SSID), Basic Service Set Identification (BSSID), and Association Identifier (AID) in communication with the third device;
means for receiving a response to the probe request from one of the first device and the at least one second device; and
means for communicating via the one device.
50. A computer readable storage medium comprising machine executable instructions which, when executed by a device, cause the device to perform the method of claim 42.
51. A computer readable storage medium comprising machine executable instructions which, when executed by a device, cause the device to perform the method of claim 43.
52. A computer readable storage medium comprising machine executable instructions which, when executed by a device, cause the device to perform the method of claim 44.
53. A computer readable storage medium comprising machine executable instructions which, when executed by a device, cause the device to perform the method of claim 45.
CN202010818357.6A 2020-08-14 2020-08-14 Communication method, device, apparatus and storage medium in communication network Pending CN114079908A (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN202010818357.6A CN114079908A (en) 2020-08-14 2020-08-14 Communication method, device, apparatus and storage medium in communication network
US17/355,439 US11659443B2 (en) 2020-08-14 2021-06-23 Method, device, apparatus and storage medium for communication in communication network
EP21183427.0A EP3955618A3 (en) 2020-08-14 2021-07-02 Method, device, apparatus and storage medium for communication in communication network
US18/303,071 US20230262524A1 (en) 2020-08-14 2023-04-19 Method, device, apparatus and storage medium for communication in communication network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010818357.6A CN114079908A (en) 2020-08-14 2020-08-14 Communication method, device, apparatus and storage medium in communication network

Publications (1)

Publication Number Publication Date
CN114079908A true CN114079908A (en) 2022-02-22

Family

ID=76764903

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010818357.6A Pending CN114079908A (en) 2020-08-14 2020-08-14 Communication method, device, apparatus and storage medium in communication network

Country Status (3)

Country Link
US (2) US11659443B2 (en)
EP (1) EP3955618A3 (en)
CN (1) CN114079908A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023178523A1 (en) * 2022-03-22 2023-09-28 Nokia Shanghai Bell Co., Ltd. Device, method and medium for mesh network

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115884298B (en) * 2023-02-03 2023-05-23 深圳酷源数联科技有限公司 Method, device, equipment and storage medium for realizing CPE cooperative work under 5G network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109905887A (en) * 2017-12-08 2019-06-18 上海诺基亚贝尔股份有限公司 For the communication means of trunking, equipment and computer readable storage medium
WO2019168764A1 (en) * 2018-03-01 2019-09-06 Cisco Technology, Inc. Seamless roaming for clients between access points with wpa-2 encryption
WO2019223679A1 (en) * 2018-05-21 2019-11-28 中兴通讯股份有限公司 Roaming method, access point, and access point collaborative work controller

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2364049B1 (en) * 2010-02-26 2012-06-06 Research In Motion Limited Reducing WLAN power consumption on a mobile device utilizing a cellular radio interface
US9655012B2 (en) * 2012-12-21 2017-05-16 Qualcomm Incorporated Deriving a WLAN security context from a WWAN security context
US9800389B2 (en) * 2013-03-08 2017-10-24 Qualcomm Incorporated Systems and methods for discovering and synchronizing within a neighbor aware network
US9730151B2 (en) * 2015-04-24 2017-08-08 Qualcomm Incorporated Method and apparatus for initiating channel sounding with unassociated access points

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109905887A (en) * 2017-12-08 2019-06-18 上海诺基亚贝尔股份有限公司 For the communication means of trunking, equipment and computer readable storage medium
WO2019168764A1 (en) * 2018-03-01 2019-09-06 Cisco Technology, Inc. Seamless roaming for clients between access points with wpa-2 encryption
WO2019223679A1 (en) * 2018-05-21 2019-11-28 中兴通讯股份有限公司 Roaming method, access point, and access point collaborative work controller

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANATOLIJ ZUBOW: "BIGAP – Seamless Handover in High Performance Enterprise IEEE 802.11 Networks", 《DBLP》, 25 April 2016 (2016-04-25) *
APURV BHARTIA: "ClientMarshal: Regaining Control from Wireless Clients for Better Experience", 《DBLP》, 5 August 2019 (2019-08-05), pages 5 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023178523A1 (en) * 2022-03-22 2023-09-28 Nokia Shanghai Bell Co., Ltd. Device, method and medium for mesh network

Also Published As

Publication number Publication date
EP3955618A3 (en) 2022-05-04
EP3955618A2 (en) 2022-02-16
US20220053376A1 (en) 2022-02-17
US11659443B2 (en) 2023-05-23
US20230262524A1 (en) 2023-08-17

Similar Documents

Publication Publication Date Title
US11184886B2 (en) Method, base station, and user equipment for implementing carrier aggregation
US11576112B2 (en) Discovery and security in LWA communication
US20210360498A1 (en) Communication method, apparatus, and system
TWI589168B (en) Method of handling cell selection and related communication device
US11641638B2 (en) Communications method and apparatus
US20210337461A1 (en) Network access method and apparatus
US10349258B2 (en) Identification of potentially neighboring network nodes in a wireless communication network
JP2018504059A (en) Method, apparatus and system for dual connection handover
CN114521010A (en) MLD privacy and operation enhancements
US20230262524A1 (en) Method, device, apparatus and storage medium for communication in communication network
US20140295826A1 (en) Method and apparatus for controlling traffic next generation mobile communication system
EP3986015A1 (en) Method and device for establishing aggregated connection, and storage medium
EP3437382A1 (en) Rapidly disseminated operational information for wlan management
EP4124107A1 (en) Communication method, access network device, terminal device and core network device
US20160066310A1 (en) Base station device, radio terminal device, network apparatus, and communication method
WO2021226967A1 (en) Handover method and device
WO2017171835A1 (en) Key management for fast transitions
US20170164194A1 (en) Offloading of a wireless node authentication with core network
EP3846535A1 (en) Cell handover method, device and readable storage medium
US20230171687A1 (en) Wireless roaming method and system
CN114631398A (en) Communication method, communication device and communication system
US20230089037A1 (en) Mode switching method, terminal, and network-side device
US11974178B2 (en) Cell handover method, device and readable storage medium
WO2023212944A1 (en) Identification and discovery of device
US11166149B2 (en) Device-to-device communication method, terminal device, and network device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination