[go: up one dir, main page]

WO2025131259A1 - Procédés d'itinérance pour dispositifs à liaisons multiples - Google Patents

Procédés d'itinérance pour dispositifs à liaisons multiples Download PDF

Info

Publication number
WO2025131259A1
WO2025131259A1 PCT/EP2023/086782 EP2023086782W WO2025131259A1 WO 2025131259 A1 WO2025131259 A1 WO 2025131259A1 EP 2023086782 W EP2023086782 W EP 2023086782W WO 2025131259 A1 WO2025131259 A1 WO 2025131259A1
Authority
WO
WIPO (PCT)
Prior art keywords
sta
information
communication links
communication
communication link
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
PCT/EP2023/086782
Other languages
English (en)
Inventor
Rocco Di Taranto
Abhishek AMBEDE
Sebastian Max
Leif Wilhelmsson
Charlie PETTERSSON
Guido Roland Hiertz
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.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/EP2023/086782 priority Critical patent/WO2025131259A1/fr
Publication of WO2025131259A1 publication Critical patent/WO2025131259A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0027—Control or signalling for completing the hand-off for data sessions of end-to-end connection for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H04W36/008355—Determination of target cell based on user equipment [UE] properties, e.g. UE service capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present disclosure relates to wireless communications, and in particular, to roaming methods for multi-link devices (MLDs).
  • MLDs multi-link devices
  • Wi-Fi also known as Wireless Local Area Network (WLAN)
  • WLAN Wireless Local Area Network
  • PHY physical
  • MAC medium access layer
  • STAs may include Access Point (AP) STAs, which may be referred to as APs, and non-AP STAs, which may be referred to as STAs.
  • AP Access Point
  • STAs non-AP STAs
  • MLO multi-link operation
  • Wi-Fi devices such as APs and STAs.
  • MLO allows APs and STAs to be configured as an MLD, i.e., to have more than one radio, and therefore more than one active link to another MLD that can transmit or receive concurrently.
  • an MLD may use one radio in the 5 GHz band and one in the 6 GHz band simultaneously, which may provide higher throughput, lower channel access delay as well as higher reliability due to redundancy, when compared to a single-link device.
  • IEEE 802.1 Ibe defines four different modes of multi-link operation:
  • EMLSR Enhanced Multi-Link Single Radio
  • EMLMR Enhanced Multi-Link Multiple Radio
  • STR allows simultaneous and asynchronous operations on the links.
  • NSTR allows simultaneous operations of the links but requires their synchronization to avoid self-interference, and EMLSR/EMLMR only allow non-simultaneous operation.
  • An 802.11 MLD may choose to deliver data belonging to a certain traffic flow on one or more links.
  • the device can make use of the TID-to- link mapping element, where TID refers to traffic identifier. This element allows for quick rearranging of what TIDs are mapped to a certain link and may be used dynamically.
  • Wi-Fi Alliance One or more standard amendments and Wi-Fi Alliance (WFA) programs provide further mechanisms to speed up the connection setup and the transition between APs, as described below. However, a seamless, zero-loss handover procedure is not guaranteed.
  • WFA Wi-Fi Alliance
  • a client such as a STA
  • STA Whenever a client, such as a STA, discovers a new network and wants to establish a connection, it must perform a full connection establishment procedure with the AP to access the network.
  • This action consists of several steps such as layer 2 (L2) authentication and association, Extensible authentication protocol (EAP) authentication, Extensible Authentication Protocol over LAB (EAPOL), and Dynamic Host Configuration Protocol (DHCP).
  • EAP Extensible authentication protocol
  • EAPOL Extensible Authentication Protocol over LAB
  • DHCP Dynamic Host Configuration Protocol
  • This activity generates frames in both directions over the wireless link between the STA and the AP.
  • the WFA program Optimized Connectivity introduces Fast Initial Link Setup (FILS) improvement based on the Internet Engineering Task Force (IETF)’s EAP re-authentication protocol (ERP). With FILS, the initial connection setup can be completed by transmitting only four frames on the wireless link.
  • ERP Authentication / Authorization / Accounting
  • the IEEE 802.1 Ir amendment introduced the Fast BSS Transition (FT) mechanism and defines a means for a STA to set up security and Quality of Service (QoS) parameters prior to reassociation to a new AP.
  • FT Fast BSS Transition
  • QoS Quality of Service
  • This mechanism allows timeconsuming operations to be removed from the time-critical reassociation process.
  • the overhead incurred during the FT initial mobility domain association in a robust security network (RSN) can be reduced using FILS authentication.
  • Fast BSS transition seeks to reduce the length of time that connectivity is lost between a STA and the DS (distribution system) during a BSS transition.
  • the FT protocols are part of the reassociation service and only apply to STA transitions between APs within the same mobility domain within the same Extended Service Set (ESS).
  • ESS Extended Service Set
  • the FT protocols may require information to be exchanged during the initial association (or a later reassociation) between a STA (known as the FT Originator (FTO)) and AP.
  • the initial exchange is referred to as the FT initial mobility domain association.
  • Subsequent reassociations to APs within the same mobility domain may make use of the FT protocols.
  • the message exchanges are performed using one of two methods:
  • the FTO communicates directly with the target AP using IEEE 802.11 authentication with the FT authentication algorithm.
  • the FTO communicates with the target AP via the current AP.
  • the communication between the FTO and the target AP is carried in FT Action frames between the FTO and the current AP.
  • the AP may convert between the two encapsulations.
  • the 802.1 Ik amendment provides tools for the STAs to search quickly for nearby APs that are available as roaming targets by creating an optimized list of channels. When the signal strength of the current AP weakens, the STA immediately scans for target APs listed as nearby APs.
  • BSS Basic Service Set
  • Section 9.6.13.9 (BSS Transition Management Request frame format) in the standard describes the Disassociation Imminent bit field which indicates whether the STA will be disassociated from the current AP.
  • the value 1 in the Disassociation Imminent bit in the Request Mode field indicates that the STA is to be disconnected from the current AP, while the value 0 indicates that the disassociation is not imminent.
  • the Disassociation Timer indicates the time after which the AP issues a Disassociation frame to this STA. It contains the number of beacon transmission times (TBTTs) until the AP sends a Disassociation frame to this STA.
  • Wi-Fi Certified Voice Enterprise program by the Wi-Fi Alliance provides voice quality and bandwidth management tools for the enterprise and defines the requirements for achieving enterprise-grade voice quality, improved mobility, device power savings, and security over Wi-Fi.
  • the Voice Enterprise program is designed to help large enterprise networks deliver voice quality in applications such as online collaboration tools and meeting applications and enable consistent Wi-Fi calling while traversing large campuses across multiple APs. Key features include:
  • Traffic prioritization network administrators can prioritize voice traffic over other multimedia traffic to provide QoS specific to voice application.
  • WMM-Admission Control provides bandwidth management tools to optimize voice delivery and balance traffic load (see more details below). • Seamless transitions based on fast BSS transitions, as discussed above.
  • the Voice Enterprise program includes features from several amendments, for example, 1 Ik, 1 Iv, 1 Ir.
  • WMM-Admission Control certification is a prerequisite for WFA Voice Enterprise.
  • an AP admits only traffic streams that can be supported by the AP.
  • an AP with WMM-AC enabled will admit voice calls only when the network can accommodate the call.
  • Admission Control is used for voice and video priority streams, and is effective only when both the AP and STA client support WMM-AC. It attempts to provide reliability of applications in progress by preventing oversubscription of bandwidth.
  • WMM- Admission Control accomplished this by enhancing the prioritization of traffic using the four Wi-Fi access categories (i.e., voice, video, best effort data and background data) and by using bandwidth management to take into account network load and channel conditions.
  • WMM-Admission Control uses IEEE 802.11 management frames for the signaling between the AP and the client device.
  • the AP evaluates the request frame from the client device against the network load and channel conditions. If the AP can accommodate the request, it accepts the request and grants the client the medium time for the traffic stream. If the request is rejected, the client device is not allowed to initiate the requested traffic stream, and may decide to either delay the traffic stream, associate with a different AP, or establish a best-effort traffic stream outside the operation of WMM-Admission Control.
  • Voice-Enterprise certified devices must meet the following thresholds: 1) Packet loss of less than 1%, 2) No more than three consecutive lost packets, 3) Latency of less than 50 milliseconds, 4) Maximum jitter of less than 50 milliseconds.
  • Optimized Connectivity Program by the Wi-Fi Alliance improves mobility and allows users to experience more consistent connections while roaming with and across networks by reducing airtime overhead and enabling faster authentication to the select AP.
  • This program provides metrics to assist client devices in quickly making decisions about the AP that will deliver the best possible connection based on bidirectional link quality estimation and network topology information.
  • EasyMesh is another program by the Wi-Fi Alliance based on which networks employ multiple access points that work together to form a unified network that provides smart, efficient Wi-Fi throughout the home and outdoor spaces. EasyMesh program, among other things, guides devices to roam to the best connection and avoid interference.
  • the Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.
  • 4G Fourth Generation
  • 5G Fifth Generation
  • NR New Radio
  • Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs.
  • the 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.
  • mobility in connected mode is controlled by the network and assisted by the device.
  • the device transmits measurement reports, for which triggering conditions are configured by the network. Triggering conditions could be for instance if the link to the serving cell is getting degraded and/or the link to another neighboring cell operating in the same frequency band is getting better than the link to the serving cell.
  • the network decides when to hand over the device from the serving cell to the neighbor cell, balancing between too early (e.g., unnecessary) handovers and too late (potentially failing) handovers.
  • conditional handover is provided to improve the mobility robustness while avoiding unnecessary handovers.
  • the main principle in conditional handover is that the device receives a handover command in advance, together with an associated condition to be monitored. When the condition is fulfilled, the device applies the previously received handover command, instead of first sending a measurement report (that could fail to be transmitted) and then waiting to receive the command (which may fail to be received).
  • the serving network node can prepare more than one target “candidate” cell, as it is not certain how the device will move and if the device will access a specific target cell.
  • DAPS dual-active protocol stacks
  • NR Release 16 describes the use of spatial diversity through multiple transmission reception points (multi-TRP) transmission strategies, which may include increasing the reliability and robustness of a transmitted data packet, from multiple transmit/reception point (multi-TRP) perspective, to transmit multiple copies of the same data payload so that the WD can combine them.
  • multi-TRP multiple transmission reception points
  • FIG. 1 shows an example non-AP STA in communication with a first AP (e.g., an AP STA) before a handover procedure is performed.
  • the STA of this example is a non-AP MLD operating on one link in the 5 GHz band (channel width 80 MHz) and another link in the 2.4 GHz band (channel width 20 MHz).
  • FIG. 2 shows an example handover procedure at the example STA (e.g., non- AP STA) operating on one link in the 5 GHz band (channel width 80 MHz) and another link in the 2.4 GHz band (channel width 20 MHz). That is, after some time, the non-AP STA performs a handover from the first AP to the second AP with the 5 GHz link (while still being connected to the first AP on the 2.4 GHz link for a period of time). Because the non-AP MLD is simultaneously connected to the two APs, a zero-loss handover may be expected, i.e., a link to the first AP would not be disconnected before another link to the second AP is completely set up and running.
  • the example STA e.g., non- AP STA
  • Some embodiments advantageously provide methods, systems, and apparatuses for performing roaming associated with MLDs.
  • a non-AP STA can request in advance whether sufficient resources are available at a target AP, and if not, the non-AP STA may decide not to roam (or the target AP may refuse the request).
  • such mechanism may be used by the non-AP STA over operating communication links of the second AP to determine, e.g., which links not to use with the target AP.
  • a seamless, zero-loss handover procedure is not guaranteed by any conventional state-of-the-art methods.
  • even such a generalized mechanism described here does not provide the second AP with the option to actively reserve some resources to accommodate the incoming STA’s required service.
  • One or more embodiments provide the non-AP STA (e.g., roaming MLD STA) with tools to make an informed decision on which link(s) to disconnect first from the first AP and on which link(s) to use first when connecting to the second AP (target AP).
  • a decision can be made, accounting not only for link qualities with first and second APs, but also considering whether the link(s) to be used at the second AP have enough resources, possibly reserved, for the required service.
  • the second AP may learn on the service required by the non-AP STA and consequently free up resources to serve the non-AP STA according to the requested service.
  • One or more embodiments provide a non-AP STA with tools for effective and smooth handover.
  • the embodiments also help the second AP reserve proper resources to the non-AP STA, which in turn results in better usage of the resources at the second AP.
  • the first AP may ask the second AP about how “good” its channels are.
  • the first AP may ask the second AP about those channels that meet certain STA requirement.
  • STA according to the information received from API, decides how to perform handover.
  • a method in a first access point (AP) station is described.
  • the first AP STA is configured to communicate with a second AP STA.
  • the first AP STA is configured to communicate with a non-AP STA using a first plurality of communication links
  • the second AP STA is configured to communicate with the non-AP STA using a second plurality of communication links.
  • the first AP STA, the second AP STA, and the non-AP STA are multi-link devices (MLDs).
  • the method includes determining first information associated with at least non-AP STA capabilities and a non-AP STA location based on a first indication received from the non-AP STA and transmitting, to the second AP STA, the first information.
  • the method further includes receiving, from the second AP STA, second information associated with at least one communication link of the second plurality of communication links.
  • the second information being usable by the non-AP STA to select none, one or more communication links from the second plurality of communication links to communicate with the second AP STA during a handover procedure.
  • the method includes transmitting, to the non-AP STA, the second information.
  • the method further includes transmitting, to the second AP STA, a first request requesting third information associated with a status of the at least one communication link of the second plurality of communication links. At least a subset of the third information is comprised in the second information.
  • the method further includes transmitting, to the second AP STA, a second request requesting fourth information comprising one or more parameters associated with each communication link of the second plurality of communication links.
  • the one or more parameters include data rate, delay information, and communication link reliability, and at least a subset of the fourth information is comprised in the second information.
  • the first information is further associated with a non- STA requirement
  • the method further includes transmitting, to the second AP STA, a third request requesting fifth information associated with the at least one communication link of the second plurality of communication links that meet a non- STA requirement. At least a subset of the fifth information is comprised in the second information.
  • the method further includes receiving, from the second AP STA, the fifth information, determining, based on the fifth information, a second indication indicating one or more communication links of the second plurality of communication links that meet the non-STA requirement, and transmitting, to the non-AP STA, the second indication.
  • the second indication is usable by the non-AP STA to select the none, one or more communication links.
  • the fifth information includes a list of channels and/or combinations of channels that meet the non-STA requirement.
  • the first information is further associated with at least one resource required by non-STA, and the at least one resource of the at least one communication link of the second plurality of communication links is reserved for the non-AP STA by the second AP STA.
  • the second information associated with at least one communication link of the second plurality of communication links is further usable by the non-AP STA for determining an order to be followed by the non-AP STA to disconnect from the at least one communication link of the first plurality of communication links.
  • the order is further based on one or more of: (A) relative ranking of the at least one communication link of the first plurality of communication links based on communication performance; (B) a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links; and (C) information associated with neighboring AP STAs.
  • A relative ranking of the at least one communication link of the first plurality of communication links based on communication performance
  • B a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links
  • C information associated with neighboring AP STAs.
  • a first access point (AP) station STA
  • the first AP STA is configured to communicate with a second AP STA.
  • the first AP STA is configured to communicate with a non-AP STA using a first plurality of communication links
  • the second AP STA is configured to communicate with the non-AP STA using a second plurality of communication links.
  • the first AP STA, the second AP STA, and the non-AP STA are multi-link devices (MLDs).
  • the first AP STA is configured to determine first information associated with at least non-AP STA capabilities and a non-AP STA location based on a first indication received from the non-AP STA and transmit, to the second AP STA, the first information.
  • the first AP STA is further configured to receive, from the second AP STA, second information associated with at least one communication link of the second plurality of communication links.
  • the second information is usable by the non-AP STA to select none, one or more communication links from the second plurality of communication links to communicate with the second AP STA during a handover procedure.
  • the first AP STA is configured to transmit, to the non-AP STA, the second information.
  • the first AP STA is further configured to transmit, to the second AP STA, a first request requesting third information associated with a status of the at least one communication link of the second plurality of communication links. At least a subset of the third information is comprised in the second information.
  • the first AP STA is further configured to transmit, to the second AP STA, a second request requesting fourth information comprising one or more parameters associated with each communication link of the second plurality of communication links.
  • the one or more parameters include data rate, delay information, and communication link reliability, and at least a subset of the fourth information is comprised in the second information.
  • the first information is further associated with a non- STA requirement
  • the first AP STA is further configured to transmit, to the second AP STA, a third request requesting fifth information associated with the at least one communication link of the second plurality of communication links that meet a non- STA requirement. At least a subset of the fifth information is comprised in the second information.
  • the first AP STA is further configured to receive, from the second AP STA, the fifth information, determine, based on the fifth information, a second indication indicating one or more communication links of the second plurality of communication links that meet the non-STA requirement, and transmit, to the non-AP STA, the second indication.
  • the second indication being usable by the non-AP STA to select the none, one or more communication links.
  • the fifth information includes a list of channels and/or combinations of channels that meet the non-STA requirement.
  • the first information is further associated with at least one resource required by non-STA, and the at least one resource of the at least one communication link of the second plurality of communication links is reserved for the non-AP STA by the second AP STA.
  • the second information associated with at least one communication link of the second plurality of communication links is further usable by the non-AP STA for determining an order to be followed by the non-AP STA to disconnect from the at least one communication link of the first plurality of communication links.
  • the order is further based on one or more of: (A) relative ranking of the at least one communication link of the first plurality of communication links based on communication performance; (B) a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links; and (C) information associated with neighboring AP STAs.
  • A relative ranking of the at least one communication link of the first plurality of communication links based on communication performance
  • B a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links
  • C information associated with neighboring AP STAs.
  • a method in a second access point (AP) station is described.
  • the second AP STA is configured to communicate with a first AP STA.
  • the first AP STA is configured to communicate with a non-AP STA using a first plurality of communication links
  • the second AP STA is configured to communicate with the non-AP STA using a second plurality of communication links.
  • the first AP STA, the second AP STA, and the non-AP STA are multi-link devices, MLDs.
  • the method includes receiving, from the first AP STA, first information associated with at least non-AP STA capabilities and a non-AP STA location and determining second information associated with at least one communication link of the second plurality of communication links based on the first information.
  • the second information is usable by the non-AP STA to select none, one or more communication links from the second plurality of communication links to communicate with the second AP STA during a handover procedure.
  • the method includes transmitting the second information to the first AP STA.
  • the method further includes receiving, from the first AP STA, a first request requesting third information associated with a status of the at least one communication link of the second plurality of communication links. At least a subset of the third information is comprised in the second information.
  • the method further includes receiving, from the first AP STA, a second request requesting fourth information comprising one or more parameters associated with each communication link of the second plurality of communication links.
  • the one or more parameters include data rate, delay information, and communication link reliability, and at least a subset of the fourth information is comprised in the second information.
  • the first information is further associated with a non- STA requirement
  • the method further includes receiving, from the first AP STA, a third request requesting fifth information associated with the at least one communication link of the second plurality of communication links that meet a non- STA requirement.
  • Aat least a subset of the fifth information is comprised in the second information.
  • the method further includes transmitting, to the first AP STA, the fifth information.
  • the fifth information is usable by the first AP STA to determine a second indication indicating one or more communication links of the second plurality of communication links that meet the non-STA requirement.
  • the second indication is usable by the non-AP STA to select the none, one or more communication links.
  • the fifth information includes a list of channels and/or combinations of channels that meet the non-STA requirement.
  • the first information is further associated with at least one resource required by non-STA, and the at least one resource of the at least one communication link of the second plurality of communication links is reserved for the non-AP STA by the second AP STA.
  • the second information associated with at least one communication link of the second plurality of communication links is further usable by the non-AP STA for determining an order to be followed by the non-AP STA to disconnect from the at least one communication link of the first plurality of communication links.
  • the order is further based on one or more of (A) relative ranking of the at least one communication link of the first plurality of communication links based on communication performance; (B) a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links; and (C) information associated with neighboring AP STAs.
  • A relative ranking of the at least one communication link of the first plurality of communication links based on communication performance
  • B a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links
  • C information associated with neighboring AP STAs.
  • a second access point (AP) station STA is described.
  • the second AP STA is configured to communicate with a first AP STA.
  • the first AP STA is configured to communicate with a non-AP STA using a first plurality of communication links, and the second AP STA being configured to communicate with the non-AP STA using a second plurality of communication links.
  • the first AP STA, the second AP STA, and the non-AP STA are multi-link devices, MLDs.
  • the second AP STA is configured to receive, from the first AP STA, first information associated with at least non-AP STA capabilities and a non-AP STA location and determine second information associated with at least one communication link of the second plurality of communication links based on the first information.
  • the second information is usable by the non-AP STA to select none, one or more communication links from the second plurality of communication links to communicate with the second AP STA during a handover procedure.
  • the second AP STA is also configured to transmit the second information to the first AP STA.
  • the second AP STA is further configured to receive from the first AP STA, a first request requesting third information associated with a status of the at least one communication link of the second plurality of communication links. At least a subset of the third information is comprised in the second information.
  • the second AP STA is further configured to receive, from the first AP STA, a second request requesting fourth information comprising one or more parameters associated with each communication link of the second plurality of communication links.
  • the one or more parameters including data rate, delay information, and communication link reliability, and at least a subset of the fourth information is comprised in the second information.
  • the first information is further associated with a non- STA requirement
  • the second AP STA is further configured to receive, from the first AP STA, a third request requesting fifth information associated with the at least one communication link of the second plurality of communication links that meet a non-STA requirement. At least a subset of the fifth information being comprised in the second information.
  • the second AP STA is further configured to transmit, to the first AP STA, the fifth information, the fifth information being usable by the first AP STA to determine a second indication indicating one or more communication links of the second plurality of communication links that meet the non- STA requirement.
  • the second indication is usable by the non-AP STA to select the none, one or more communication links.
  • the fifth information includes a list of channels and/or combinations of channels that meet the non-STA requirement.
  • the first information is further associated with at least one resource required by non-STA, and the at least one resource of the at least one communication link of the second plurality of communication links is reserved for the non-AP STA by the second AP STA.
  • the second information associated with at least one communication link of the second plurality of communication links is further usable by the non-AP STA for determining an order to be followed by the non-AP STA to disconnect from the at least one communication link of the first plurality of communication links.
  • the order is further based on one or more of: (A) relative ranking of the at least one communication link of the first plurality of communication links based on communication performance; (B) a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links; and (C) information associated with neighboring AP STAs.
  • A relative ranking of the at least one communication link of the first plurality of communication links based on communication performance
  • B a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links
  • C information associated with neighboring AP STAs.
  • a system comprising a first access point (AP) station (STA), a second AP STA, and a non-AP STA is described.
  • the first AP STA is configured to communicate with a second AP STA.
  • the first AP STA is configured to communicate with a non-AP STA using a first plurality of communication links, and the second AP STA being configured to communicate with the non-AP STA using a second plurality of communication links.
  • the first AP STA, the second AP STA, and the non-AP STA are multi-link devices (MLDs).
  • MLDs multi-link devices
  • the first AP STA is configured to transmit, to the second AP STA, first information associated with at least non-AP STA capabilities and a non-AP STA location based on a first indication received from the non-AP STA and receive, from the second AP STA, second information associated with at least one communication link of the second plurality of communication links.
  • the second information is usable by the non-AP STA to select none, one or more communication links from the second plurality of communication links to communicate with the second AP STA during a handover procedure.
  • the first AP STA is further configured to transmit, to the non-AP STA, the second information.
  • the second AP STA is configured to receive, from the first AP STA, the first information, determine the second information based on the first information, and transmit the second information to the first AP STA.
  • the non-AP STA is configured to receive the second information and select the none, one or more communication links from the second plurality of communication links to communicate with the second AP STA during a handover procedure.
  • FIG. 1 shows an example non-AP STA in communication with a first AP (e.g., an AP STA) before a handover procedure is performed;
  • a first AP e.g., an AP STA
  • FIG. 2 shows an example steps of a handover procedure
  • FIG. 3 is a schematic diagram of an example network architecture illustrating a communication system according to the principles in the present disclosure
  • FIG. 4 is a block diagram of an AP communicating with a non-AP STA over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 5 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG. 6 is a block diagram of a host computer communicating via an access point with a non-AP STA over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 7 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for executing a client application at a non-AP STA according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for receiving user data at a non-AP STA according to some embodiments of the present disclosure
  • FIG. 9 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for receiving user data from the non-AP STA at a host computer according to some embodiments of the present disclosure
  • FIG. 10 is a flowchart illustrating example methods implemented in a communication system including a host computer, an access point and a non-AP STA for receiving user data at a host computer according to some embodiments of the present disclosure
  • FIG. 11 is a flowchart of an example process in a first AP STA according to some embodiments of the present disclosure
  • FIG. 12 is a flowchart of an example process in a second AP STA according to some embodiments of the present disclosure.
  • FIG. 13 is an example communication system configured to performed one or more steps according to some embodiments of the present disclosure.
  • relational terms such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term, “in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • Coupled may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • the term “access point” or “AP” is used interchangeably and may comprise, or be, a network node.
  • the AP may include any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), relay node, integrated access and backhaul (IAB), donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in
  • the non-limiting term “device” is used to describe a wireless device (WD) and/or user equipment (UE) that may be used to implement some embodiments of the present disclosure.
  • the device may be and/or comprise an access point (AP) station (STA).
  • the device may be and/or comprise a non-access point station (non-AP STA).
  • AP STA is referred to as AP
  • non-AP STA is referred to as STA.
  • the device may be any type of device capable of communicating with a network node, such as an AP, over radio signals.
  • the device may be any radio communication device, target device, a portable device, device-to- device (D2D) device, machine type device or device capable of machine to machine communication (M2M), low-cost and/or low-complexity device, a sensor equipped with a device, a computer, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, Reduced Capability (RedCap) device, etc.
  • D2D device-to- device
  • M2M machine to machine communication
  • M2M machine to machine communication
  • low-cost and/or low-complexity device a sensor equipped with a device, a computer, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a
  • a device may be considered a network node and may include physical components, such as processors, allocated processing elements, or other computing hardware, computer memory, communication interfaces, and other supporting computing hardware.
  • the network node may use dedicated physical components, or the node may be allocated use of the physical components of another device, such as a computing device or resources of a datacenter, in which case the network node is said to be virtualized.
  • a network node may be associated with multiple physical components that may be located either in one location, or may be distributed across multiple locations.
  • the principles herein may be explained in the context of one of a Downlink (DL) and an Uplink (UL) communication, it should be understood that the basic principles disclosed may also be applicable to the other of the one of the DL and the UL communication.
  • the principles may be considered applicable to, e.g., a first STA and, e.g., a second STA.
  • the first STA may be the transmitter, and the second STA may be the receiver.
  • the transmitter may be the second STA, and the receiver may be the first STA .
  • the first STA may be an AP or non-AP STA
  • the second STA may be an AP or a non-AP STA.
  • IEEE 802.11 denotes a set of Wireless Local Area Network (WLAN) air interface standards developed by the IEEE 802.11 committee for short- range communications (e.g., tens of meters to a few hundred meters).
  • WLAN Wireless Local Area Network
  • Some embodiments may also be supported by standard documents disclosed in 3GPP technical specifications. That is, some embodiments of the description can be supported by the above documents (e.g., standard documents). In addition, all the terms disclosed in the present document may be described by the above standard documents.
  • wireless systems such as, for example, IEEE 802.11, 3GPP, Long Term Evolution (LTE), 5th Generation (5G) and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system.
  • Other wireless systems including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by one or more of a first STA, second STA, transmitting STA, receiving STA, AP, non-AP STA, wireless device, network node, etc. may be distributed over a plurality of STAs, APs, non-AP STAs, wireless devices, network nodes, etc.
  • the functions of the devices described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • transmission signal quality condition may refer to transmit (TX) signal quality requirements, such as in terms of EVM of the transmitted signal.
  • TX transmit
  • a maximum TX power may be limited by the transmit signal quality requirements.
  • FIG. 3 a schematic diagram of the communication system 10, according to one embodiment, constructed in accordance with the principles of the present disclosure.
  • the communication system 10 in FIG. 3 is a non-limiting example and other embodiments of the present disclosure may be implemented by one or more other systems and/or networks.
  • system 10 may comprise a wireless local area network (WLAN).
  • WLAN wireless local area network
  • the devices in the system 10 may communicate over one or more spectrums, such as, for example, an unlicensed spectrum, which may include frequency bands typically used by Wi-Fi technology.
  • One or more of the devices may be further configured to communicate over other frequency bands, such as shared licensed frequency bands, etc.
  • the system 10 may include one or more service areas 12a, 12b, etc. (collectively referred to herein as “service area 12”), which may be defined by corresponding access points (APs) 14a, 14b, etc. (collectively referred to herein as “AP STA 14” or “STA 14”), which may be configured as MLDs.
  • a service area 12 may also correspond to and/or be associated with a coverage area, a cell, and/or a basic service set (BSS).
  • BSS basic service set
  • the AP STAs 14 may or may not be connectable to another network, such as a core network over a wired or wireless connection.
  • the system 10 includes a plurality of non-AP devices, such as, for example, non-AP STAs 16a, 16b, 16c (collectively referred to as “non-AP STAs 16” or “STA 16”), which may be configured as MLDs.
  • Each of the non-AP STAs 16 may be located in one or more service areas 12 and may be configured to wirelessly connect to one or more AP STA 14.
  • the communication system may include many more non-AP STAs 16 and AP STAs 14.
  • Each AP STA 14 may connect to/serve/configure/schedule/etc. one or more non-AP STAs 16.
  • system 10 may include additional nodes and/or devices not shown in FIG. 3.
  • system 10 may include many more connections and/or interfaces than those shown in FIG. 3.
  • a non-AP STA 16 can be in communication and/or configured to separately communicate with more than one AP STA 14 and/or more than one type of AP STA 14.
  • an AP STA 14 may be in communication and/or configured to separately communicate with other AP STAs 14, as described herein, which may be via wired and/or wireless communication channels.
  • a non-AP STA 16 is configured to include a non-AP STA Management Unit 17, which is configured to perform one or more non-AP STA 16 functions described herein.
  • An AP STA 14 is configured to include an AP STA Management Unit 18, which is configured to perform one or more AP STA 14 functions described herein.
  • Example implementations, in accordance with an embodiment, of the AP STA 14 and non-AP STA 16 discussed in the preceding paragraphs will now be described with reference to FIG. 4.
  • An AP STA 14 or a non-AP STA 16 may be generally referred to as a STA 19.
  • a first STA 19a may be an AP STA 14, and a second STA 19b may be a non-AP STA 16.
  • System 10 may include one or more additional STAs 19n (which include AP STAs 14 and/or non-AP STAs 16), which may be in communication with STA 19a and/or STA 19b.
  • Any STA 19 may be configured as an MLD.
  • the AP STA 14 includes hardware 20 including a communication interface 22, processing circuitry 24, a processor 26, and memory 28.
  • the communication interface 22 may be configured to communicate with any of the nodes/devices in the system 10 according to some embodiments of the present disclosure, such as with one or more other AP STAs 14 and/or one or more non-AP STAs 16.
  • communication interface 22 may be configured to communicate with one or more AP STA 14 via communication link 37 (e.g., a wired/wireless communication link), according to some embodiments of the present disclosure.
  • the communication interface 22 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface. In some embodiments, the communication interface 22 may also include a wired interface.
  • RF radio frequency
  • the processing circuitry 24 may include one or more processors 26 and memory, e.g., memory 28.
  • the processing circuitry 24 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 26 may be configured to access (e.g., write to and/or read from) the memory 28, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the memory 28 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the AP STA 14 may further include software 30 stored internally in, for example, memory 28, or stored in external memory (e.g., database) accessible by the AP STA 14 via an external connection.
  • the software 30 may be executable by the processing circuitry 24.
  • the processing circuitry 24 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., AP STA 14.
  • the memory 28 is configured to store data, programmatic software code and/or other information described herein.
  • the software 30 may include instructions stored in memory 28 that, when executed by the processor 26 and/or AP STA Management Unit 18 causes the processing circuitry 24 and/or configures the AP STA 14 to perform the processes described herein with respect to the AP STA 14.
  • the non-AP STA 16 includes hardware 32, which may include a communication interface 34, processing circuitry 36, a processor 38, and memory 40.
  • the communication interface 34 may be configured to communicate with one or more AP STA 14 and/or other STA 19n, such as via communication link 35 (e.g., wired/wireless communication link), and/or with other elements in the system 10, according to some embodiments of the present disclosure.
  • the communication interface 34 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers, and/or may be considered a radio interface.
  • the communication interface 34 may also include a wired interface.
  • AP STA 14 may be configured to communicate with another AP STA 14, non-AP STA 16, and/or STA 19n via communication link 35 and/or via a wired connection (not shown).
  • the processing circuitry 36 may include one or more processors 38 and memory, such as, the memory 40. Furthermore, in addition to a traditional processor and memory, the processing circuitry 36 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors 38 and memory such as, the memory 40.
  • the processing circuitry 36 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 38 may be configured to access (e.g., write to and/or read from) the memory 40, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the memory 40 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the non-AP STA 16 may further include software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database) accessible by the non-AP STA 16 via an external connection.
  • the software 42 may be executable by the processing circuitry 36.
  • the processing circuitry 36 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by the non-AP STA 16.
  • the memory 40 is configured to store data, programmatic software code and/or other information described herein.
  • the software may include instructions stored in memory 40 that, when executed by the processor 38 and/or non-AP STA Management Unit 17, causes the processing circuitry 36 and/or configures the non-AP STA 16 to perform the processes described herein with respect to the non-AP STA 16.
  • connection between the STAs 19 i.e., AP STA 14, the non-AP STA 16, and STA 19n
  • AP STA 14 the connection between the STAs 19
  • STA 19n the connection between the STAs 19
  • intermediary devices and/or connections may exist between these devices, although not explicitly shown.
  • FIG. 4 shows non-AP STA Management Unit 17 and AP STA Management Unit 18, as being within a processor, it is contemplated that this element may be implemented such that a portion of the element is stored in a corresponding memory within the processing circuitry. In other words, the element may be implemented in hardware or in a combination of hardware and software within the processing circuitry.
  • FIG. 5 is a schematic diagram of a communication system 10, according to another embodiment of the present disclosure.
  • the access point STA 14 and non-AP STAs 16 may be similar to those of the example of FIG. 3, described herein.
  • one or more AP STAs 14 and/or non-AP STAs 16 may form and/or be part of a service set network 44 (e.g., a basic service set, or any other network, set, and/or grouping of AP STAs 14 and non- AP STAs 16).
  • a service set network 44 e.g., a basic service set, or any other network, set, and/or grouping of AP STAs 14 and non- AP STAs 16.
  • the communication system 10 and/or service set network 44 may itself be connected to a host computer 46, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 46 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • the connections 48, 50 between the communication system 10 and/or the service set network 44 and the host computer 46 may extend directly from the service set network 44 to the host computer 46 or may extend via an optional intermediate network 52.
  • the intermediate network 52 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 52 if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 52 may comprise two or more sub-networks (not shown).
  • the communication system of FIG. 5 as a whole enables connectivity between one of the connected non-AP STAs 16 and the host computer 46.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 46 and the connected non AP-STAs 16 are configured to communicate data and/or signaling via the OTT connection, using the service set network 44, any intermediate network 52 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • an AP STA 14 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 46 to be forwarded (e.g., handed over) to a connected non-AP STA 16.
  • the AP STA 14 need not be aware of the future routing of an outgoing uplink communication originating from the non-AP STA 16 towards the host computer 46.
  • the AP STA 14 and the non-AP STA 16 may have similar features and components as the AP STA 14 and non-AP STA 16 depicted in FIG. 4.
  • the host computer 46 comprises hardware (HW) 53 including a communication interface 54 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 46 further comprises processing circuitry 56, which may have storage and/or processing capabilities.
  • the processing circuitry 56 may include a processor 58 and memory 60.
  • the processing circuitry 56 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 58 may be configured to access (e.g., write to and/or read from) memory 60, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 60 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 56 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 46.
  • Processor 58 corresponds to one or more processors 58 for performing host computer 46 functions described herein.
  • the host computer 46 includes memory 60 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 62 and/or the host application 64 may include instructions that, when executed by the processor 58 and/or processing circuitry 56, causes the processor 58 and/or processing circuitry 56 to perform the processes described herein with respect to host computer 46.
  • the instructions may be software associated with the host computer 46.
  • the software 62 of host computer 46 may be executable by the processing circuitry 56.
  • the software 62 includes a host application 64.
  • the host application 64 may be operable to provide a service to a remote user, such as a non-AP STA 16 connecting via an OTT connection 66 terminating at the non-AP STA 16 and the host computer 46.
  • the host application 64 may provide user data which is transmitted using the OTT connection 66.
  • the “user data” may be data and information described herein as implementing the described functionality.
  • the host computer 46 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 56 of the host computer 46 may enable the host computer 46 to observe, monitor, control, transmit to and/or receive from the AP STA 14 and/or the non-AP STA 16.
  • the processing circuitry 56 of the host computer 46 may include a host management unit 68 configured to enable the service provider to observe/monitor/control/transmit to/receive from/configure/etc. the AP STA 14 and/or the non-AP STA 16.
  • the communication interface 22 of AP STA 14 may be configured to facilitate a connection 66 to the host computer 46.
  • the connection 66 may be direct or it may pass through a service set network 44 of the communication system 10 and/or through one or more intermediate networks 52 outside the communication system 10.
  • the communication interface 34 of non-AP STA 16 may be configured to facilitate a connection 66 to the host computer 46.
  • the connection 66 may be direct or it may pass through a service set network 44 of the communication system 10 and/or through one or more intermediate networks 52 outside the communication system 10.
  • the software 42 of non-AP STA 16 may include a client application 70.
  • the client application 70 may be operable to provide a service to a human or non-human user via the non-AP STA 16, with the support of the host computer 46.
  • an executing host application 64 may communicate with the executing client application 70 via the OTT connection 66 terminating at the non-AP STA 16 and the host computer 46.
  • the client application 70 may receive request data from the host application 64 and provide user data in response to the request data.
  • the OTT connection 66 may transfer both the request data and the user data.
  • the client application 70 may interact with the user to generate the user data that it provides.
  • the inner workings of the AP STA 14, non-AP STA 16, and host computer 46 may be as shown in FIG. 5 and independently, the surrounding network topology may be that of FIG. 6.
  • the OTT connection 66 has been drawn abstractly to illustrate the communication between the host computer 46 and the non-AP STA 16 via the AP STA 14, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the non-AP STA 16 or from the service provider operating the host computer 46, or both. While the OTT connection 66 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the communication link 35 between the non-AP STA 16 and the AP STA 14 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the non-AP STA 16 using the OTT connection 66, in which the communication link 35 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 66 may be implemented in the software 62 of the host computer 46 or in the software 42 of the non-AP STA 16, or both.
  • sensors may be deployed in or in association with communication devices through which the OTT connection 66 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 62, 42 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 66 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the AP STA 14, and it may be unknown or imperceptible to the AP STA 14. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary wireless device signaling facilitating the host computer’s 46 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 62, 42 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 66 while it monitors propagation times, errors, etc.
  • the host computer 46 includes processing circuitry 56 configured to provide user data and a communication interface 54 that is configured to forward the user data to a wireless network and/or cellular network for transmission to the non-AP STA 16.
  • the wireless network and/or cellular network also includes the AP STA 14 with a communication interface 22.
  • the AP STA 14 is configured to, and/or the AP STA 14 processing circuitry 24 is configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the non-AP STA 16, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the non-AP STA 16.
  • the host computer 46 includes processing circuitry 56 and a communication interface 54 that is configured to receive user data originating from a transmission from a non-AP STA 16 to an AP STA 14.
  • the non-AP STA 16 is configured to, and/or comprises a communication interface 34 and/or processing circuitry 36 configured to perform the functions and/or methods described herein for preparing/initiating/maintaining/supporting/ending a transmission to the AP STA 14, and/or preparing/terminating/maintaining/supporting/ending in receipt of a transmission from the AP STA 14.
  • FIG. 7 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 3 and 4, in accordance with one embodiment.
  • the communication system may include a host computer 46, an AP STA 14 and a non-AP STA 16, which may be those described with reference to FIG. 6.
  • the host computer 46 provides user data (Block SI 00).
  • the host computer 46 provides the user data by executing a host application, such as, for example, the host application 64 (Block SI 02).
  • the host computer 46 initiates a transmission carrying the user data to the non-AP STA 16 (Block SI 04).
  • the AP STA 14 transmits to the non-AP STA 16 the user data which was carried in the transmission that the host computer 46 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06).
  • the non-AP STA 16 executes a client application, such as, for example, the client application 70, associated with the host application 64 executed by the host computer 46 (Block SI 08).
  • FIG. 8 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 6, in accordance with one embodiment.
  • the communication system may include a host computer 46, an AP STA 14 and a non-AP STA 16, which may be those described with reference to FIGS. 3 and 4.
  • the host computer 46 provides user data (Block SI 10).
  • the host computer 46 provides the user data by executing a host application, such as, for example, the host application 64.
  • the host computer 46 initiates a transmission carrying the user data to the non-AP STA 16 (Block SI 12).
  • the transmission may pass via the AP STA 14, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the non-AP STA 16 receives the user data carried in the transmission (Block SI 14).
  • FIG. 9 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 6, in accordance with one embodiment.
  • the communication system may include a host computer 46, an AP STA 14 and a non-AP STA 16, which may be those described with reference to FIGS. 3 and 4.
  • the non-AP STA 16 receives input data provided by the host computer 46 (Block SI 16).
  • the non-AP STA 16 executes the client application 70, which provides the user data in reaction to the received input data provided by the host computer 46 (Block SI 18).
  • the non-AP STA 16 provides user data (Block S120).
  • the non-AP STA 16 provides the user data by executing a client application, such as, for example, client application 70 (Block S122).
  • client application 70 may further consider user input received from the user.
  • the non-AP STA 16 may initiate, in an optional third substep, transmission of the user data to the host computer 46 (Block S124).
  • the host computer 46 receives the user data transmitted from the non-AP STA 16, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
  • FIG. 10 is a flowchart illustrating an exemplary method implemented in a communication system, in accordance with one embodiment.
  • the communication system may include a host computer 46, an AP STA 14 and a non-AP STA 16, which may be those described with reference to FIGS. 3 and 4.
  • the AP STA 14 receives user data from the non-AP STA 16 (Block S128).
  • the AP STA 14 initiates transmission of the received user data to the host computer 46 (Block S130).
  • the host computer 46 receives the user data carried in the transmission initiated by the AP STA 14 (Block S132).
  • FIG. 10 is a flowchart illustrating an exemplary method implemented in a communication system, in accordance with one embodiment.
  • the communication system may include a host computer 46, an AP STA 14 and a non-AP STA 16, which may be those described with reference to FIGS. 3 and 4.
  • the AP STA 14 receives user data from the non-AP STA 16 (Block S128).
  • FIG. 11 is a flowchart of an example process in a first AP STA 14a.
  • One or more Blocks and/or functions and/or methods performed by the first AP STA 14a may be performed by one or more elements of the first AP STA 14a such as by AP STA Management Unit 18 in processing circuitry 24, memory 28, processor 26, communication interface 22, etc. according to the example process/method.
  • the first AP STA 14a is configured to determine (Block S134) first information associated with at least non-AP STA 16 capabilities and a non-AP STA location based on a first indication received from the non-AP STA 16 and transmit (Block S136), to the second AP STA, the first information.
  • the first AP STA 14a is further configured to receive (Block S138), from the second AP STA, second information associated with at least one communication link 35 of the second plurality of communication links 35.
  • the second information is usable by the non-AP STA 16 to select none, one or more communication links 35 from the second plurality of communication links 35 to communicate with the second AP STA during a handover procedure.
  • the first AP STA 14a is configured to transmit (Block S140), to the non-AP STA 16, the second information.
  • the first AP STA 14a is further configured to transmit, to the second AP STA, a first request requesting third information associated with a status of the at least one communication link 35 of the second plurality of communication links 35. At least a subset of the third information is comprised in the second information.
  • the first AP STA 14a is further configured to transmit, to the second AP STA, a second request requesting fourth information comprising one or more parameters associated with each communication link 35 of the second plurality of communication links 35.
  • the one or more parameters include data rate, delay information, and communication link reliability, and at least a subset of the fourth information is comprised in the second information.
  • the first information is further associated with a non- STA requirement
  • the first AP STA 14a is further configured to transmit, to the second AP STA, a third request requesting fifth information associated with the at least one communication link 35 of the second plurality of communication links 35 that meet a non-STA requirement. At least a subset of the fifth information is comprised in the second information.
  • the first AP STA 14a is further configured to receive, from the second AP STA, the fifth information, determine, based on the fifth information, a second indication indicating one or more communication links 35 of the second plurality of communication links 35 that meet the non-STA requirement, and transmit, to the non-AP STA 16, the second indication. The second indication being usable by the non-AP STA 16 to select the none, one or more communication links 35.
  • the fifth information includes a list of channels and/or combinations of channels that meet the non-STA requirement.
  • the first information is further associated with at least one resource required by non-STA, and the at least one resource of the at least one communication link 35 of the second plurality of communication links 35 is reserved for the non-AP STA 16 by the second AP STA.
  • the second information associated with at least one communication link 35 of the second plurality of communication links 35 is further usable by the non-AP STA 16 for determining an order to be followed by the non-AP STA 16 to disconnect from the at least one communication link 35 of the first plurality of communication links 35.
  • the order is further based on one or more of (A) relative ranking of the at least one communication link 35 of the first plurality of communication links 35 based on communication performance; (B) a mapping between a traffic identifier (TID) and a corresponding communication link 35 of the first plurality of communication links 35; and (C) information associated with neighboring AP STAs 14.
  • A relative ranking of the at least one communication link 35 of the first plurality of communication links 35 based on communication performance
  • B a mapping between a traffic identifier (TID) and a corresponding communication link 35 of the first plurality of communication links 35
  • C information associated with neighboring AP STAs 14.
  • FIG. 12 is a flowchart of an example process in a second AP STA 14b.
  • One or more Blocks and/or functions and/or methods performed by the second AP STA 14b may be performed by one or more elements of the second AP STA 14b such as by AP STA Management Unit 18 in processing circuitry 24, memory 28, processor 26, communication interface 22, etc. according to the example process/method.
  • the first AP STA 14a is configured to receive (Block S142), from the first AP STA 14a, first information associated with at least non-AP STA 16 capabilities and a non-AP STA location and determine (Block SI 44) second information associated with at least one communication link 35 of the second plurality of communication links 35 based on the first information.
  • the second information is usable by the non-AP STA 16 to select none, one or more communication links 35 from the second plurality of communication links 35 to communicate with the second AP STA during a handover procedure.
  • the second AP STA is also configured to transmit (Block S146) the second information to the first AP STA 14a.
  • the second AP STA is further configured to receive from the first AP STA 14a, a first request requesting third information associated with a status of the at least one communication link 35 of the second plurality of communication links 35. At least a subset of the third information is comprised in the second information.
  • the second AP STA is further configured to receive, from the first AP STA 14a, a second request requesting fourth information comprising one or more parameters associated with each communication link 35 of the second plurality of communication links 35.
  • the one or more parameters including data rate, delay information, and communication link reliability, and at least a subset of the fourth information is comprised in the second information.
  • the first information is further associated with a non- STA requirement
  • the second AP STA is further configured to receive, from the first AP STA 14a, a third request requesting fifth information associated with the at least one communication link 35 of the second plurality of communication links 35 that meet a non-STA requirement. At least a subset of the fifth information being comprised in the second information.
  • the second AP STA is further configured to transmit, to the first AP STA 14a, the fifth information, the fifth information being usable by the first AP STA 14a to determine a second indication indicating one or more communication links 35 of the second plurality of communication links 35 that meet the non-STA requirement.
  • the second indication is usable by the non-AP STA 16 to select the none, one or more communication links 35.
  • the fifth information includes a list of channels and/or combinations of channels that meet the non-STA requirement.
  • the first information is further associated with at least one resource required by non-STA, and the at least one resource of the at least one communication link 35 of the second plurality of communication links 35 is reserved for the non-AP STA 16 by the second AP STA.
  • the second information associated with at least one communication link 35 of the second plurality of communication links 35 is further usable by the non-AP STA 16 for determining an order to be followed by the non-AP STA 16 to disconnect from the at least one communication link 35 of the first plurality of communication links 35.
  • the order is further based on one or more of: (A) relative ranking of the at least one communication link of the first plurality of communication links 35 based on communication performance; (B) a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links 35; and (C) information associated with neighboring AP STAs 14.
  • A relative ranking of the at least one communication link of the first plurality of communication links 35 based on communication performance
  • B a mapping between a traffic identifier (TID) and a corresponding communication link of the first plurality of communication links 35
  • C information associated with neighboring AP STAs 14.
  • communication link 35 may comprise one or more communication links 35 such as communication links 35a, 35b, 35c, etc.
  • FIG. 13 shows an example communication system 10 which includes a first AP STA 14a supporting operation on two or more communication links 35a, 35b, a second AP STA 14b supporting operation on two or more other communication links 35 (not shown), and a non-AP STA 16. Any one of the first AP STA 14a, the second AP STA 14b, and the non-AP STA 16 may be an MLD.
  • a method for handover may include establishing communication with an AP STA 14 using one or more communication links 35 and/or terminating communication with another AP STA 14 by disconnecting from one or more communication links 35.
  • the method may include one or more of the following: a) The first AP STA 14a providing the second AP STA 14b information on STA capabilities and position (which may be provided by the non-AP STA 16 to the first AP STA 14a in an indication frame); b) The first AP STA 14a requesting the second AP STA 14b status information about the second AP STA Mb’s communication links 35 which may be operating links; c) The non-AP STA 16 monitoring connection quality toward the first AP STA 14a on the two or more communication links 35; d) The non-AP STA 16 assessing when at least one of the communication links 35 currently connected to the first AP STA 14a is underperforming and may/should be switched to the second AP STA 14b; e) The
  • the first AP STA 14a sends a request to AP 2 on which communication links 35, if any, would meet the requirement of the non-AP STA 16;
  • the second AP STA 14b further reserves some resources to the coming STA to provide the required service in some communication links 35 (e.g., APs setup semi-persistent agreements to facilitate handover, or the second AP STA 14b reserves resources (link, rTWT) before handover);
  • some communication links 35 e.g., APs setup semi-persistent agreements to facilitate handover, or the second AP STA 14b reserves resources (link, rTWT) before handover
  • the one or more conditions may include one or more of: (A) Relative ranking of the existing communication links 35 based on ongoing communication performance (e.g., in terms of SNR, SINR, number of successful transmissions, rate, etc.); (B) TID-to-link mapping; and (C) Information gathered about neighboring AP MLDs, (e.g., using neighbor reports or via the DS if exchanged);
  • the STA capabilities are learned during an association process, while the location information is (estimated and) shared with dedicated frames.
  • the non-AP STA 16 is connected with the first AP STA 14a using two communication links 35a, 35b.
  • the first AP STA 14a and second AP STA 14b may connect via a wire (e.g., Ethernet cable) and/or over the air.
  • the communication link 37 between the first AP STA 14a and the second AP STA 14b may be used as follows:
  • the first AP STA 14a requests the second AP STA 14b to explicitly provide information about different operating communication links 35 such as how good the operating communication links 35 are, e.g., in terms of data rate, delay, reliability. Then the non-AP STA 16 (via the first AP STA 14a) obtains a detailed list of link quality indicators of each operating communication link 35 of the second AP STA 14b. This may help the non-AP STA 16 select one or more communication links 35 to be used at the same time. Further, the second AP STA 14b may provide statistics on currently operating communication links 35 and/or not operating communication links 35.
  • the first AP STA 14a may notify or indicate the non-AP STA 16 of the operating communication link information received from the second AP STA 14b.
  • the second AP STA 14b can choose any channel, in any band, and provide information about such channel. There may be no need to determine in advance what are the operating channels of the second AP STA 14b, before the handover occurs.
  • the second AP STA 14b may already operate one or more channels (e.g., two channels), but the second AP STA 14b may also have MLD capability to operate on a third channel, currently not used. That is, the second AP STA 14b may, when requested, provide information about the third channel as well.
  • the first AP STA 14a may send a request to the second AP STA 14b requesting information about which communication link 35, if any, would meet the non-AP STA 16 requirements, e.g., on data rate , relay, reliability.
  • Non-AP STA 16 (via the first AP STA 14a) obtains a positive/negative indication of capability for each operating communication link 35 of the second AP STA 14b, such as a capability to provide the required service.
  • the first AP STA 14a may further ask the second AP STA 14b to obtain a communication link 35 with sufficient quality to serve the non-AP STA 16, or the second AP STA 14b may obtain a communication link 35 with sufficient quality to serve the non-AP STA 16 even without an explicit request by the AP STA 14a.
  • the second AP STA 14b may assess what level of service it can provide to the non-AP STA 16 (e.g., what rate) such as after obtaining information about non-AP STA capabilities (e.g., MIMO support, number of antennas, etc..) and non-AP STA positioning information (and therefore path loss). Such information may be provided by the first AP STA 14a to the second AP STA 14b over communication link 37.
  • what level of service it can provide to the non-AP STA 16 e.g., what rate
  • non-AP STA capabilities e.g., MIMO support, number of antennas, etc..
  • non-AP STA positioning information and therefore path loss
  • the second AP STA 14b may be made aware (by the first AP STA 14a) of the STA requirements and therefore may proactively reserve some resources in its BSS to favor the handover procedure. For example, the second AP STA 14b may move (all, or most, or some of) its non-AP STAs 16 to one of its operating channels, to create less traffic in the operating channel indicated as suitable for the STA handover. Alternatively, the second AP STA 14b, given the non-AP STA 16 traffic requirements (e.g., in terms of TID or traffic class), may decide to reserve some communication links 35 to carry only traffic related to such TID, or traffic class.
  • the non-AP STA 16 traffic requirements e.g., in terms of TID or traffic class
  • such communication links 35 may be indicated as suitable, via the first AP STA 14a, to the roaming non-AP STA 16.
  • the second AP STA 14b may leave some (time/frequency/spatial) resources semi-persistently, or ad-hoc, for exclusive roaming STA usage.
  • the second AP STA 14b may convey to the first AP STA 14a that it is not capable of operating in certain bands and/or channels.
  • the first AP STA 14a may inform the second AP STA 14b on already planned or possible future STAs handovers.
  • different roaming choices may occur at the roaming non-AP STA 16 (e.g., if lower band is busy/interfered at the second AP STA 14b, then the non-AP STA 16 may wait to be close to MLD AP B and then use higher band link).
  • the non-AP STA 16 may prefer an earlier handover using long range lower band instead. Further examples of operations are provided in the next subsection.
  • communication links 35 to disconnect first may be selected (the non-AP STA 16).
  • the non-AP STA 16 may base the decision to move to another AP STA 14 on aspects such as the throughput in the current BSS and the Radio Signal Strength Indication (RSSI) from other AP STAs 14.
  • RSSI Radio Signal Strength Indication
  • a non-AP STA 16 may be assumed to be connected via two communication links 35, one in the 2.4 GHz and the other in the 6 GHz band.
  • the non-AP STA 16 experiences poor service (by AP STA 14a) on the 2.4 GHz band, and at the same time a signal having signal quality above a threshold is available from the second AP STA 14b in the 2.4 GHz channel.
  • the non-AP STA 16 would disconnect first the 2.4 GHz link as a good service may be expected by the second AP STA 14b, given that signal quality is good. However, this may be acceptable if the second AP STA 14b can provide good service in its 2.4 GHz link.
  • AP STA 14b may provide a good service to non-AP STA 16 if sufficient resources are available, e.g., if channel can be accessed timely (this information is not entailed in the channel quality indicator). Otherwise, this may be a poor handover decision.
  • the non-AP STA 16 may also inquire the second AP STA 14b about each link quality before the handover occurs, e.g., to learn that the 2.4 GHz band link is congested and therefore decide to disconnect the 6 GHz link first.
  • this conventional handover procedure is that it results in delays longer than a predetermined threshold and packet losses. Further, deteriorated performance may be expected when the procedure needs to be repeated across all active communication links 35. This may be very problematic especially when considering for example non-STR devices, that need to coordinate their operations across communication links 35.
  • the first AP STA 14a may request the second AP STA 14b information about status of its operating communication links 35. With this information relayed by the first AP STA 14a, the non-AP STA 16 may decide to use the 6 GHz link for handover while minimizing packet losses and having low delay (lower than a predetermined threshold). In another example, in case the second AP STA 14b has indicated that no communication link 35 alone can provide satisfactory service to the non-AP STA 16, the non-AP STA 16 may realize that instead that using both communication links 35 at the same time for handover is the best procedure, e.g., because the second AP STA 14b has provided detailed information about the capability of each communication link 35.
  • the second AP STA 14b may be aware of the service required by the non-AP STA 16. Depending on its capabilities and on the channel conditions, the second AP STA 14b may indicate that a communication link 35 (e.g., the 6 GHz link) is acceptable for STA usage and/or indicate that another communication link 35 (e.g., the 2.4 GHz link) is acceptable for STA usage. For example, this may be the case where the second AP STA 14b manages to reserve some resources for the incoming non-AP STA 16. In turn, the non-AP STA 16 can choose the communication link 35 that better suits its needs.
  • a communication link 35 e.g., the 6 GHz link
  • another communication link 35 e.g., the 2.4 GHz link
  • the second AP STA 14b may proactively reserve the resources on one communication link 35, or on multiple communication links 35 to be used at the same time.
  • the second AP STA 14b may share info about its communication links 35 directly with the non-AP STA 16 without going through the first AP STA 14a.
  • signaling from the first AP STA 14a to the non-AP STA 16 may be transmitted even if all handover decisions (when, using which link, etc.) are performed by the non-AP STA 16 itself.
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD- ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

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

Abstract

Est décrit un procédé dans une première station (STA) de point d'accès (AP). La première STA AP est configurée pour communiquer avec une seconde STA AP. La première STA AP est configurée pour communiquer avec une STA non AP à l'aide d'une première pluralité de liaisons de communication, et la seconde STA AP est configurée pour communiquer avec la STA non AP à l'aide d'une seconde pluralité de liaisons de communication. La première STA AP, la seconde STA AP et la STA non AP sont des dispositifs à liaisons multiples (MLD). Le procédé consiste à déterminer des premières informations associées au moins à des capacités de STA non AP et à une STA non AP. Le procédé consiste en outre à recevoir, en provenance de la seconde STA AP, et à transmettre, à la STA non AP, des secondes informations utilisables par la STA non AP pour sélectionner aucune, une ou plusieurs liaisons de communication de la seconde pluralité de liaisons de communication pour communiquer avec la seconde STA AP pendant une procédure de transfert intercellulaire.
PCT/EP2023/086782 2023-12-20 2023-12-20 Procédés d'itinérance pour dispositifs à liaisons multiples Pending WO2025131259A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2023/086782 WO2025131259A1 (fr) 2023-12-20 2023-12-20 Procédés d'itinérance pour dispositifs à liaisons multiples

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2023/086782 WO2025131259A1 (fr) 2023-12-20 2023-12-20 Procédés d'itinérance pour dispositifs à liaisons multiples

Publications (1)

Publication Number Publication Date
WO2025131259A1 true WO2025131259A1 (fr) 2025-06-26

Family

ID=89507576

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/086782 Pending WO2025131259A1 (fr) 2023-12-20 2023-12-20 Procédés d'itinérance pour dispositifs à liaisons multiples

Country Status (1)

Country Link
WO (1) WO2025131259A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180220340A1 (en) * 2016-12-20 2018-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Handover Procedures in Multi-Carrier Networks
US20220322162A1 (en) * 2020-08-03 2022-10-06 Chengdu Xgimi Technology Co., Ltd Roaming method in a multi-link scenario, multi-link device, and storage medium
EP4117383A1 (fr) * 2020-03-04 2023-01-11 LG Electronics Inc. Procédé d'exécution d'une communication à liaisons multiples dans un système de communication sans fil

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180220340A1 (en) * 2016-12-20 2018-08-02 Telefonaktiebolaget Lm Ericsson (Publ) Handover Procedures in Multi-Carrier Networks
EP4117383A1 (fr) * 2020-03-04 2023-01-11 LG Electronics Inc. Procédé d'exécution d'une communication à liaisons multiples dans un système de communication sans fil
US20220322162A1 (en) * 2020-08-03 2022-10-06 Chengdu Xgimi Technology Co., Ltd Roaming method in a multi-link scenario, multi-link device, and storage medium

Similar Documents

Publication Publication Date Title
US11950315B2 (en) User equipment, radio network node and methods performed therein for handling communication
US9661515B2 (en) Cloud-based management platform for heterogeneous wireless devices
US9119154B2 (en) Opportunistic carrier aggregation for dynamic flow switching between radio access technologies
US7706326B2 (en) Wireless communication methods and components that implement handoff in wireless local area networks
CN102932927B (zh) 无线通信方法、基站和终端
JP2022514288A (ja) アンライセンススペクトルで動作する方法およびデバイス
US10555356B2 (en) Methods of operating network nodes in a communication network, and network nodes implementing the same
US9820324B2 (en) Network control of terminals with respect to multiple radio access networks
US12052585B2 (en) Client steering method in multiple access point network and device therefor
WO2014176503A1 (fr) Plateforme de gestion en nuage pour des dispositifs sans fil heterogenes
RU2657869C2 (ru) Межсетевое взаимодействие между сетями, работающими в соответствии с разными технологиями радиодоступа
CN103391632A (zh) 网络接入方法及装置
EP4569912A1 (fr) Rapport d'informations d'état de canal (csi) pour mobilité intercellulaire de couche 1 et de couche 2
JP2013085242A (ja) アップリンク及びダウンリンクに対し、それぞれ異なる基地局に端末を接続させる方法、およびその基地局
EP4059266B1 (fr) Resélection de cellule basée sur le groupe ue
CN106993322A (zh) 电子设备和通信方法
WO2016180213A1 (fr) Procédé de traitement d'informations de groupe de point d'accès (ap) et nœud b évolué (enb)
US11936589B2 (en) Systems and methods for customizing wireless communication beacons and transmitting wireless communication beacons
US9497696B2 (en) Techniques for region-based scanning of different frequency bands for use in a wireless LAN
WO2025131259A1 (fr) Procédés d'itinérance pour dispositifs à liaisons multiples
US20180139675A1 (en) Network nodes and methods thereof
US12457489B2 (en) Handling incompatible wireless devices
WO2024260954A1 (fr) Coordination de point d'accès pour économie d'énergie
CN117014857A (zh) 漫游方法、设备及通信系统
WO2023007020A1 (fr) Technique de sélection de cellules

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23836762

Country of ref document: EP

Kind code of ref document: A1