Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
  • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
• • 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
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/15—Setup of multiple wireless link connections
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/08—Access point devices
  • H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points

Definitions

• NSTR NON-SIMULTANEOUS TRANSMIT-RECEIVE
• AP MULTI-LINK DEVICE
• This disclosure relates generally to wireless communications, and more specifically to wireless communications associated with multi-link devices (MLDs).
• MLDs multi-link devices
• a wireless local area network may be formed by one or more access points (APs) that provide a shared wireless communication medium for use by a number of client devices also referred to as stations (STAs).
• the basic building block of a WLAN conforming to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is a Basic Service Set (BSS), which is managed by an AP.
• BSS Basic Service Set
• Each BSS is identified by a Basic Service Set Identifier (BSSID) that is advertised by the AP.
• An AP periodically broadcasts beacon frames to enable any STAs within wireless range of the AP to establish or maintain a communication link with the WLAN.
• An AP multi-link device may include a plurality of APs that can independently operate on a plurality of respective communication links.
• Each AP can establish a BSS on a respective communication link, and wireless communication devices associated with the AP MLD can transmit data to or receive data from the AP MLD on one or more of the communication links associated with the AP MLD.
• Each of the communication links may be of various bandwidths by bonding a number of 20 MHz-wide channels together to form 40 MHz-wide channels, 80 MHz-wide channels, 160 MHz-wide channels, or 320 MHz-wide channels.
• STAs may have limited filtering capabilities that can allow the reception of data on one link to interfere with the transmission of data on another link, it may be desirable for STAs to operate as a softAP MLD.
• the method includes operating as a non-simultaneous transmitreceive (NSTR) soft access point (AP) multi -link device (MLD) including a first AP associated with a primary link and including a second AP associated with a non-primary link.
• NSTR non-simultaneous transmitreceive
• AP soft access point
• MLD multi -link device
• the method includes determining that the non-primary link is unavailable.
• the method includes transmitting, on only the primary link, a frame carrying an indication of the unavailability of the non-primary link.
• the frame may be one of a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or an action frame.
• the method may also include disabling the non- primary link or placing the non-primary link into a power save state based on the unavailability of the non-primary link.
• disabling the non-primary link includes removing the non-primary link from a multi-link context associated with the NSTR softAP MLD.
• the method may also include determining that the non- primary link is available after removing the non-primary link from the multi-link context, and adding the non-primary link to the multi-link context based on the availability of the non-primary link.
• disabling the non-primary link includes re-mapping traffic identifiers (TIDs) from the non-primary link to the primary link.
• TIDs traffic identifiers
• the wireless communication device may include at least one modem, at least one processor communicatively coupled with the at least one modem, and at least one memory communicatively coupled with the at least one processor and storing processor-readable code.
• execution of the processor-readable code by the at least one processor in conjunction with the at least one modem may be configured to operate the wireless communication device as an NSTR softAP MLD including a first AP associated with a primary link and including a second AP associated with a non-primary link. Execution of the processor-readable code may be configured to determine that the non-primary link is unavailable.
• execution of the processor-readable code may also be configured to receive an RTS frame from a STA MLD on the primary link, to transmit a CTS frame to the STA MLD on the primary and non-primary links based on receiving the RTS frame, and to receive one or more UL PPDUs from the STA MLD on the primary and non-primary links.
• execution of the processor-readable code may also be configured to switch the primary link from a first channel to a second channel concurrently with switching the non-primary link from the second channel to the first channel.
• the first channel is in one of a 5 GHz frequency band or a 6 GHz frequency band
• the second channel is in the other of the 5 GHz frequency band or the 6 GHz frequency band.
• Figure 1 IB shows an example TBTT Information Header of the RNR Element of Figure 11 A according to some implementations.
• Figure 12B shows an example Multi-Link Control field of the ML Element of Figure 12A according to some implementations.
• Figure 12D shows an example Per-STA Profile subelement of the ML Element of Figure 12A according to some implementations.
• Figure 12F shows an example STA Info field of the Per-STA Profile subelement of Figure 12D according to some implementations.
• Figure 38 shows a block diagram of another example wireless communication device according to some implementations.
• the multi-link context also allows the AP MLD and one or more associated devices to establish a common block acknowledgement (BA) policy or session on multiple communication links of the AP MLD, and to use a single authentication mechanism for multiple communication links of the AP MLD.
• the associated devices can use the multi-link context to dynamically switch communications between the different communication links of the AP MLD without disassociating or re-associating with the AP MLD.
• the AP MLD can use the multi-link context to dynamically change or re-map affiliations between traffic identifier (TID) values and each of the different communication links.
• TID traffic identifier
• non-legacy devices operating on the primary link may be able to decode or parse the complete profiles of both the primary and non-primary links, while legacy devices operating on the primary link may be able to decode or parse only the complete profile of the primary link.
• legacy devices operating on the primary link may not be able to discover or associate with the NSTR softAP MLD on the non-primary link.
• legacy devices operating on the non-primary link may not be able to discover or associate with the NSTR softAP MLD on the non-primary link.
• various aspects of the subject matter disclosed herein may limit communications between the NSTR softAP MLD and legacy devices to the primary link.
• legacy devices may refer to wireless communication devices configured to operate in accordance with the IEEE 802.1 lax or earlier amendments to the 802.11 family of wireless communication standards
• non-legacy devices may refer to wireless communication devices configured to operate in accordance with the IEEE 802.1 Ibe or later amendments to the 802.11 family of wireless communication standards.
• Each of the STAs 104 also may be referred to as a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, among other possibilities.
• the STAs 104 may represent various devices such as mobile phones, personal digital assistant (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (for example, TVs, computer monitors, navigation systems, among others), music or other audio or stereo devices, remote control devices (“remotes”), printers, kitchen or other household appliances, key fobs (for example, for passive keyless entry and start (PKES) systems), among other possibilities.
• PDAs personal digital assistant
• netbooks notebook computers
• tablet computers laptops
• display devices for example, TVs, computer monitors, navigation systems, among others
• music or other audio or stereo devices for example, remote control devices (“remotes”), printers, kitchen or other household appliances
• each of the STAs 104 is configured to perform passive or active scanning operations (“scans”) on frequency channels in one or more frequency bands (for example, the 2.4 GHz, 5.0 GHz, 6.0 GHz, or 60 GHz bands).
• scans passive or active scanning operations
• a STA 104 listens for beacons, which are transmitted by respective APs 102 at a periodic time interval referred to as the target beacon transmission time (TBTT) (measured in time units (TUs) where one TU may be equal to 1024 microseconds (ps)).
• TBTT target beacon transmission time
• TUs time units
• ps microseconds
• a STA 104 may have the opportunity to select one of many BSSs within range of the STA or to select among multiple APs 102 that together form an extended service set (ESS) including multiple connected BSSs.
• An extended network station associated with the WLAN 100 may be connected to a wired or wireless distribution system that may allow multiple APs 102 to be connected in such an ESS.
• a STA 104 can be covered by more than one AP 102 and can associate with different APs 102 at different times for different transmissions.
• a STA 104 also may be configured to periodically scan its surroundings to find a more suitable AP 102 with which to associate. For example, a STA 104 that is moving relative to its associated AP 102 may perform a “roaming” scan to find another AP 102 having more desirable network characteristics such as a greater received signal strength indicator (RS SI) or a reduced traffic load.
• RS SI received signal strength indicator
• FIG. 2A shows an example protocol data unit (PDU) 200 usable for communications between an AP and a number of STAs.
• the PDU 200 can be configured as a PPDU.
• the PDU 200 includes a PHY preamble 202 and a PHY payload 204.
• the PHY preamble 202 may include a legacy portion that itself includes a legacy short training field (L-STF) 206, a legacy long training field (L-LTF) 208, and a legacy signaling field (L-SIG) 210.
• the PHY preamble 202 may also include a non-legacy portion (not shown).
• the L-STF 206 generally enables a receiving device to perform automatic gain control (AGC) and coarse timing and frequency estimation.
• the L-LTF 208 generally enables a receiving device to perform fine timing and frequency estimation and also to estimate the wireless channel.
• the L- SIG 210 generally enables a receiving device to determine a duration of the PDU and use the determined duration to avoid transmitting on top of the PDU.
• the L-STF 206, the L-LTF 208, and the L-SIG 210 may be modulated according to a binary phase shift keying (BPSK) modulation scheme.
• BPSK binary phase shift keying
• FIG. 2B shows an example L-SIG field 220 in the PDU of Figure 2A.
• the L-SIG 220 includes a data rate field 222, a reserved bit 224, a length field 226, a parity bit 228, and a tail field 220.
• the data rate field 222 indicates a data rate (note that the data rate indicated in the data rate field 222 may not be the actual data rate of the data carried in the payload 204).
• the length field 226 indicates a length of the packet in units of, for example, bytes.
• the parity bit 228 is used to detect bit errors.
• the tail field 220 includes tail bits that are used by the receiving device to terminate operation of a decoder (for example, a Viterbi decoder). The receiving device utilizes the data rate and the length indicated in the data rate field 222 and the length field 226 to determine a duration of the packet in units of, for example, microseconds (ps).
• ps microseconds
• FIG. 3 A shows another example PDU 300 usable for wireless communication between an AP and one or more STAs.
• the PDU 300 may be used for SU, OFDMA or MU-MIMO transmissions.
• the PDU 300 may be formatted as a High Efficiency (HE) WLAN PPDU in accordance with the IEEE 802.1 lax amendment to the IEEE 802.11 wireless communication protocol standard.
• the PDU 300 includes a PHY preamble including a legacy portion 302 and a non-legacy portion 304.
• the PDU 300 may further include a PHY payload 306 after the preamble, for example, in the form of a PSDU including a data field 324.
• the legacy portion 302 of the preamble includes an L-STF 308, an L-LTF 310, and an L-SIG 312.
• the non-legacy portion 304 includes a repetition of L-SIG (RL-SIG) 314, a first HE signal field (HE-SIG-A) 316, an HE short training field (HE- STF) 320, and one or more HE long training fields (or symbols) (HE-LTFs) 322.
• the second portion 304 further includes a second HE signal field (HE-SIG-B) 318 encoded separately from HE-SIG-A 316.
• the information in RL-SIG 314 and HE- SIG-A 316 may be duplicated and transmitted in each of the component 20 MHz channels in instances involving the use of a bonded channel.
• the content in HE-SIG-B 318 may be unique to each 20 MHz channel and target specific STAs 104.
• RL-SIG 314 may indicate to HE-compatible STAs 104 that the PDU 300 is an HE PPDU.
• An AP 102 may use HE-SIG-A 316 to identify and inform multiple STAs 104 that the AP has scheduled UL or DL resources for them.
• HE- SIG-A 316 may include a resource allocation subfield that indicates resource allocations for the identified STAs 104.
• HE-SIG-A 316 may be decoded by each HE-compatible STA 104 served by the AP 102.
• HE-SIG-A 316 further includes information usable by each identified STA 104 to decode an associated HE-SIG-B 318.
• non-legacy devices may be aware of the new type of TBTT Information field disclosed herein, and may thus obtain the complete profiles of both the primary and non-primary links from the first frame. Conversely, legacy devices may not understand the new type of TBTT Information field disclosed herein, and may thus ignore the TBTT Information field in the Neighbor AP Information field associated with the non-primary link. In this way, aspects of the subject matter disclosed herein may preclude at least some legacy devices from discovering the non-primary link based on information received on the primary link.
• Figure 7B shows a sequence diagram depicting another example multi-link communication 710 according to some implementations.
• the multi-link communication 710 may be performed between the NSTR softAP MLD and the one or more associated STAs described with reference to Figure 7A (only one associated STA shown for simplicity).
• the NSTR softAP MLD may include a first AP associated with the primary link, and may include a second AP associated with the nonprimary link.
• the first and second APs may be softAPs implemented by the STA operating as the NSTR softAP MLD.
• the STA receives the instruction. At a later time, such as when the STA has queued UL data to transmit, the STA may transmit an RTS frame on the primary link to the NSTR softAP MLD.
• the NSTR softAP MLD receives the RTS frame, determines that the non-primary link is available, and transmits a CTS frame to the STA on both the primary and non-primary links.
• the STA receives the CTS frame on both the primary and non-primary links, and determines that the non-primary link is available based on receiving the CTS frame on both the primary and non-primary links.
• the STA transmits one or more UL PPDUs on one or both of the primary and non-primary links to the NSTR softAP MLD. In some instances, the transmission of the CTS frame to the STA on both the primary and non-primary links may allow the STA to link the nonprimary link and the primary link together.
• the NSTR softAP MLD may use any suitable rules or mechanisms to concurrently switch the channels of the primary and non-primary links.
• the NSTR softAP MLD may use the Channel Switch Announcement (CSA) element or the extended Channel Switch Announcement (eCSA) element carried in the body of management frames (such as beacon frames, probe response frames, association response frames, or reassociation response frames) transmitted on the primary link when performing channel switch operations.
• CSA Channel Switch Announcement
• eCSA extended Channel Switch Announcement
• Figure 8B shows a sequence diagram depicting another example multi -link communication 810 according to some other implementations.
• the multi -link communication 810 may be performed between the NSTR softAP MLD and the one or more associated STAs described with reference to Figures 7A and 7B (only one associated STA shown for simplicity).
• the NSTR softAP MLD may include a first AP associated with the primary link, and may include a second AP associated with the non-primary link.
• the first and second APs may be softAPs implemented by the STA operating as the NSTR softAP MLD.
• the NSTR softAP MLD may advertise the profiles of both the primary and non-primary links on only the primary link.
• the MLD parameters field of the TBTT Information field carried in the Neighbor AP Information field may include a PBCC field carrying a value indicating whether or not any of the BSS parameters of the non-primary link have been updated.
• a value indicating whether or not any of the BSS parameters of the non-primary link have been updated may be carried in another suitable field, element, or header of the third frame.
• the primary link may be configured as a complete BSS
• the non-primary link may be configured as a pseudo-BSS that shares at least some capabilities and operation parameters with the primary link.
• the non-primary link may have the same SSID, TSF value, and beacon interval as the primary link, and may inherit these values from the primary link.
• the non-primary link may also inherit the TBTT offset, short-SSID, BSS parameters, and PSD limits of the primary link.
• the first frame may be a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.
• the second frame may be a probe request frame, an association request frame, or a reassociation request frame.
• the third frame may be a probe response frame, an association response frame, or a reassociation response frame.
• FIG. 9A shows a timing diagram depicting an example multi-link communication 900 according to some implementations.
• the multi-link communication 900 may be performed between the NSTR softAP MLD described with reference to Figures 7A, 7B, 8A, or 8B and two associated wireless stations STA1 and STA2.
• the STAs may be any suitable wireless communication devices including, for example, the STAs 104 and 604 described above with reference to Figures 1 and 6B, respectively.
• the NSTR softAP MLD may include a first AP associated with the primary link, and may include a second AP associated with the nonprimary link. In some instances, the first and second APs may be softAPs implemented by the STA operating as the NSTR softAP MLD.
• STA1 is a legacy device configured to operate in accordance with the IEEE 802.1 lax or earlier amendments to the 802.11 family of wireless communication standards
• STA2 is a non-legacy device configured to operate in accordance with the IEEE 802.1 Ibe or later amendments to the 802.11 family of wireless communication standards.
• the NSTR softAP MLD Prior to time to, the NSTR softAP MLD contends for channel access to the primary link using a suitable channel access mechanism (such as an EDCA mechanism), and obtains a transmission opportunity (TXOP) on the primary link. After obtaining the TXOP on the primary link, the NSTR softAP MLD may also gain channel access to the non-primary link. In some instances, gaining channel access to the nonprimary link may be based on obtaining channel access or a TXOP on the primary link. In some implementations, the NSTR softAP MLD may limit transmissions on the nonprimary link to individually-addressed frames.
• a suitable channel access mechanism such as an EDCA mechanism
• the NSTR softAP MLD transmits, on only the primary link, a first beacon frame 901 that includes the complete profile of the primary link and indicates the complete profile of the non-primary link.
• the primary link may be configured as a complete BSS
• the non-primary link may be configured as a pseudo-BSS that inherits one or more capabilities and operation parameters from the primary link.
• the non-primary link may inherit the SSID, the TSF value, and the beacon interval from the primary link.
• the beacon frame 901 contains a frame body that includes a plurality of fields and elements followed by an ML Element. The plurality of fields and elements may carry the complete profile of the primary link.
• the ML Element may carry a Per- STA Profile subelement that indicates the complete profile of the non-primary link.
• the ML Element may include a Common Info field carrying a BPCC field that indicates updates to one or more BSS parameters associated with the primary link.
• one or more bits of a Multi-Link Control field or the Common Info field carried in the ML Element may indicate whether or not the first beacon frame 901 is transmitted from the first AP of the NSTR softAP MLD.
• the one or more bits of the Multi-Link Control field or the Common Info field may be set to a first value to indicate that the first beacon frame 901 is transmitted from the first AP of the NSTR softAP MLD, or may be set to a second value to indicate that the first beacon frame 901 is transmitted from an AP associated with a simultaneous transmit-receive (STR) device (such as an AP MLD).
• STR simultaneous transmit-receive
• STA1 and STA2 receive the first beacon frame 901 on the primary link, and may parse the first beacon frame 901 to obtain the complete profiles of the primary and non-primary links.
• each of STA1 and STA2 can parse or decode the complete profile of the primary link carried in the fields and elements contained in the body of the first beacon frame 901.
• STA2 may also be able to parse or decode the complete profile of the non-primary link indicated in the ML Element of the first beacon frame 901.
• STA1 may not be able to parse or decode one or more portions of the ML Element carried in the first beacon frame 901, and thus may not be able to obtain the capabilities, operation parameters, and other discovery information associated with the non-primary link from the first beacon frame 901. STA1 may also be unable to parse or decode one or more portions of the RNR Element carried in the first beacon frame 901. Thus, while STA2 may be able to discover and associate with the NSTR softAP MLD on both the primary and non-primary links using information obtained from the first beacon frame 901, STA1 can discover and associate with the NSTR softAP MLD on only the primary link using information obtained from the first beacon frame 901. In this way, communications between the NSTR softAP MLD and STA1 (and other legacy devices associated with the NSTR softAP MLD) may be limited to the primary link.
• the NSTR softAP MLD transmits a first DL PPDU 911 on the primary link to STA1 and transmits a second DL PPDU 912 on the non-primary link to STA2, concurrently.
• the NSTR softAP MLD may use a first group of antenna resources to transmit the DL PPDU 911 on the primary link to a first group of STAs (such as STA1), and may use a second group of antenna resources to transmit the DL PPDU 912 on the non-primary link to a second group of STAs (such as STA2).
• the NSTR softAP MLD transmits a second beacon frame 902 on only the primary link.
• the second beacon frame 902 may be similar to the first beacon frame 901, for example, by carrying the complete profile of the primary link and indicating the complete profile of the non-primary link.
• the second beacon frame 902 may include less information than the first beacon frame 901.
• the second beacon frame 902 may carry or indicate a partial profile of one or both of the primary and nonprimary links.
• the second beacon frame 902 may carry the complete or partial profile of the primary link, and may not include the capabilities or operation parameters of the non-primary link.
• the second beacon frame 902 may be similar to the first frame described with reference to Figure 8B, for example, by carrying or indicating only the BSSID and MLD common parameters of the non-primary link.
• the non-primary link may not be available for communications between the NSTR softAP MLD and its associated STAs.
• STA2 (and other wireless communication devices associated with the NSTR softAP MLD) may not be permitted to transmit UL data on the non-primary link during the deaf state 914.
• UL transmissions that the NSTR softAP MLD may not be able to receive or properly decode due to cross-link interference resulting from the transmission of DL PPDU 921 on the primary link may be prevented or delayed until after the DL transmission ends.
• the deaf state 914 may be of any suitable duration of time.
• the duration of the deaf state 914 may be temporally aligned with the transmit duration of DL PPDU 921 on the primary link.
• the duration of the deaf state 914 may include a guard time, followed by the transmit duration of DL PPDU 921, followed by another guard time. Other durations of time may be suitable for the deaf state 914.
• the guard time may be selected to prevent (or to reduce by more than an amount) the effects of cross-link interference on DL communications transmitted on the non-primary link.
• the duration of the guard time may be configured to ensure that the first and last symbols of the DL PPDU 921 do not interfere with UL transmissions on the nonprimary link.
• recovering the non-primary link from the deaf state 914 may include re-mapping the TIDs from the primary link to the non-primary link.
• the NSTR softAP MLD may transmit a Notification frame on the primary link to indicate that some TIDs affiliated with the primary link have been re-mapped to the non-primary link.
• the NSTR softAP MLD contends for channel access to the primary link between times t7 and ts using a suitable channel access mechanism to obtain another TXOP on the primary link. After obtaining the TXOP on the primary link, the NSTR softAP MLD may gain channel access to and obtain a TXOP on the non-primary link. [0140] At time ts, the NSTR softAP MLD transmits a third beacon frame 903 on only the primary link.
• the third beacon frame 903 may be similar to the first beacon frame 901, for example, by carrying the complete profile of the primary link and indicating the complete profile of the non-primary link.
• the third beacon frame 903 may be similar to the second beacon frame 902, for example, by carrying less information than the first beacon frame 901.
• the non-primary link When in the deaf state 931, the non-primary link may not be available for communications between the NSTR softAP MLD and its associated STAs.
• the NSTR softAP MLD may not transmit DL data on the non-primary link during the deaf state 932. In this way, DL transmissions on the non-primary link that are susceptible to cross-link interference resulting from the transmission of UL PPDU 931 on the primary link may be prevented or delayed until after expiration of the deaf state 932.
• STA2 and other wireless communication devices associated with the NSTR softAP MLD may not be permitted to transmit UL data on the non-primary link during the deaf state 932.
• Figure 9B shows a timing diagram depicting an example multi-link communication 940 according to some other implementations.
• the multi-link communication 940 may be performed between the NSTR softAP MLD and the wireless stations STA1 and STA2 described with reference to Figure 9A.
• the multi-link communication 940 may be performed between the NSTR softAP MLD described with reference to Figures 7A, 7B, 8A, or 8B and associated wireless stations STA1 and STA2.
• the STAs may be any suitable wireless communication devices including, for example, the STAs 104 and 604 described above with reference to Figures 1 and 6B, respectively.
• the NSTR softAP MLD may include a first AP associated with the primary link, and may include a second AP associated with the non-primary link.
• the first and second APs may be softAPs implemented by the STA operating as the NSTR softAP MLD.
• STA1 is a legacy device configured to operate in accordance with the IEEE 802.1 lax or earlier amendments to the 802.11 family of wireless communication standards
• STA2 is a non-legacy device configured to operate in accordance with the IEEE 802.1 Ibe or later amendments to the 802.11 family of wireless communication standards.
• the NSTR softAP MLD Prior to time to, the NSTR softAP MLD contends for channel access to the primary link using a suitable channel access mechanism (such as an EDCA mechanism), and obtains a TXOP on the primary link. After obtaining the TXOP on the primary link, the NSTR softAP MLD may also gain channel access to the non-primary link. In some instances, gaining channel access to the non-primary link may be based on obtaining channel access or a TXOP on the primary link. In some implementations, the NSTR softAP MLD may limit transmissions on the non-primary link to individually-addressed frames.
• a suitable channel access mechanism such as an EDCA mechanism
• the NSTR softAP MLD transmits a first beacon frame 941 on only the primary link.
• the first beacon frame 941 may include the complete profile of the primary link and may indicate the complete profile of the non-primary link.
• the primary link may be configured as a complete BSS
• the non-primary link may be configured as a pseudo-BSS that inherits one or more capabilities and operation parameters from the primary link.
• the non- primary link may have the same SSID, TSF value, and beacon interval as the primary link, and may inherit the SSID, TSF value, and beacon interval from the primary link.
• the first beacon frame 941 may be similar to the first beacon frame 901 of Figure 9A. That is, the first beacon frame 941 may contain a frame body including a plurality of fields and elements followed by an ML Element. The plurality of fields and elements may carry the complete profile of the primary link.
• the ML Element may carry a Per-STA Profile subelement indicating the complete profile of the non-primary link.
• the ML Element may include a Common Info field carrying a BPCC field that indicates updates to one or more BSS parameters of the primary link.
• One or more bits of the Multi-Link Control field or the Common Info field carried in the ML Element may indicate whether or not the first beacon frame 941 is transmitted from the first AP of the NSTR softAP MLD.
• the first beacon frame 941 may also include an RNR Element carrying a Neighbor AP Information field associated with the non-primary link.
• the Neighbor AP Information field may carry a TBTT Information field consisting of a BSSID and one or more MLD parameters of the non- primary link.
• the MLD parameters field of the TBTT Information field carried in the Neighbor AP Information field associated with the non-primary link may include a BPCC field carrying a value that indicates updates to one or more BSS parameters of the non-primary link.
• a value indicating updates to the one or more BSS parameters of the non-primary link may be carried in another suitable field, element, or header of the first beacon frame 941.
• STA1 and STA2 receive the first beacon frame 941 on the primary link, and may parse the beacon frame 941 to obtain the complete profiles of the primary and non- primary links.
• each of STA1 and STA2 can parse or decode the complete profile of the primary link carried in the fields and elements contained in the body of the first beacon frame 941.
• STA2 may also be able to parse or decode the complete profile of the non-primary link indicated in the ML Element of the first beacon frame 941.
• the NSTR softAP MLD transmits a first trigger frame 951 on the primary link concurrently with transmitting a second trigger frame 952 on the nonprimary link.
• the first trigger frame 951 may solicit UL transmissions from a first group of STAs (including STA1) on the primary link
• the second trigger frame 952 may solicit UL transmissions from a second group of STAs (including STA2) on the non-primary link.
• the NSTR softAP MLD may establish coordinated TWT sessions on the primary and non-primary links.
• the TWT session on the primary link may include one or more service periods (SPs) during which the NSTR softAP MLD can schedule transmissions to and from STA1 or the first group of STAs on the primary link
• the TWT session on the non-primary link may include one or more SPs during which the NSTR softAP MLD can schedule transmissions to and from STA2 or the second group of STAs on the non- primary link.
• the NSTR softAP MLD may synchronize the TWT SPs of the respective TWT sessions established on the primary and non-primary links with each other.
• coordinating the respective TWT sessions or TWT SPs on the primary and non-primary links with each other may allow the NSTR softAP MLD to schedule the UL transmission of TB PPDU 961 from STA1 on the primary link concurrently with the UL transmission of TB PPDU 962 from STA2 on the non-primary link.
• transmission of the TB PPDU 961 from STA1 on the primary link may be temporally aligned with the transmission of the TB PPDU 962 from STA2 on the non-primary link.
• the NSTR softAP MLD contends for channel access to the primary link between times t3 and t4 using a suitable channel access mechanism (such as an EDC A mechanism), and obtains a TXOP on the primary link. After obtaining the TXOP on the primary link, the NSTR softAP MLD may gain channel access to and obtain a TXOP on the non-primary link. In some other instances, the NSTR softAP MLD may retain the TXOPs obtained on the primary and non-primary links between times to and ti, and may not have to contend for channel access between times t3 and t4.
• a suitable channel access mechanism such as an EDC A mechanism
• the NSTR softAP MLD transmits a second beacon frame 942 on only the primary link.
• the second beacon frame 942 may be similar to the first beacon frame 941, for example, by carrying the complete profile of the primary link and indicating the complete profile of the non-primary link.
• the second beacon frame 942 may include less information than the first beacon frame 941.
• the second beacon frame 942 may carry or indicate a partial profile of one or both of the primary and non- primary links.
• the second beacon frame 942 may carry the complete or partial profile of the primary link, and may not include the capabilities or operation parameters associated with the non-primary link.
• the second beacon frame 942 may be similar to the first frame described with reference to Figure 8B, for example, by carrying or indicating only the BSSID and MLD common parameters of the non-primary link.
• the transmission of UL PPDU 971 and TB PPDU 963 on the primary and non-primary links from STA1 and STA2, respectively, may prevent the NSTR softAP MLD from transmitting DL data on the primary and non-primary links between times t6 and t7, which may obviate the need to place the non-primary link into a deaf state between times te and t7.
• the NSTR softAP MLD may establish an independent TWT session on the non-primary link to schedule the transmission of the TB PPDU 963 to the NSTR softAP MLD.
• the independent TWT session on the non-primary link may include one or more SPs during which the NSTR softAP MLD can schedule UL transmissions from STA2 or DL transmissions to STA2 (and other associated devices) on the non-primary link.
• the NSTR softAP MLD does not receive any UL communications between times ts and t9, and thus the concurrent transmission of DL PPDUs 981 and 982 on the primary and non-primary links, respectively, may not see any cross-link interference resulting from UL transmissions between times ts and t9.
• the NSTR softAP MLD may use a first group of antenna resources to transmit the DL PPDU 981 on the primary link to the first group of STAs (including STA1), and may use a second group of antenna resources to transmit the DL PPDU 982 on the non-primary link to the second group of STAs (including STA2).
• the NSTR softAP MLD transmits a third beacon frame 943 on only the primary link.
• the third beacon frame 943 may be similar to the first beacon frame 941, for example, by carrying the complete profile of the primary link and indicating the complete profile of the non-primary link.
• the third beacon frame 943 may be similar to the second beacon frame 942, for example, by carrying less information than the first beacon frame 941.
• the duration of the guard time may be configured to ensure that DL transmissions on the non-primary link do not interfere with the first or last symbols of the UL PPDU 991.
• the NSTR softAP MLD recovers the non-primary link from the deaf state 992.
• FIG 10A shows an example management frame 1000A usable for wireless communications that supports NSTR softAP MLDs according to some implementations.
• the management frame 1000 A may be a beacon frame, a probe response frame, an association response frame, a re-association response frame, or some other suitable management frame.
• the management frame 1000A may be an example implementation of the first or second frames of Figure 7A, the first or second frames of Figure 7B, the frame of Figure 8 A, the third frame of Figure 8B, the beacon frames of Figure 9A, or the beacon frames of Figure 9B.
• some information elements of the frame 1000A may also be referred to as a “field,” a “subfield,” an “element,” or a “subelement,” which may be considered interchangeable terms for purposes of discussion herein.
• the frame 1000A is shown to include a plurality of elements and fields 1010, a Reduced Neighbor Report (RNR) Element 1020, capabilities and operating parameters 1030, and a basic Multi-Link (ML) Element 1040.
• the elements and fields 1010 may carry the complete profile of the primary link.
• the RNR element 1020 may include one or more AP entries 1022. Each of the AP entries 1022 may be associated with a respective AP of an AP MLD, and may carry or indicate one or more parameters of the respective AP. In some implementations, the one or more parameters may include the BSSID and MLD parameters of the respective AP.
• the frame 1000B is shown to include a plurality of elements and fields 1010, an RNR Element 1020, capabilities and operating parameters 1030, and a basic ML Element 1050.
• the elements and fields 1010 may carry the complete profile of the primary link.
• the RNR element 1020 may include one or more AP entries 1022. Each of the AP entries 1022 may be associated with a respective AP of an AP MLD, and may carry or indicate one or more parameters of the respective AP. In some implementations, the one or more parameters may include the BSSID and MLD parameters of the respective AP.
• a respective AP entry 1022 may not include one or more of a TBTT offset, a short-SSID, BSS parameters, or a PSD limit of a corresponding non-primary link.
• the capabilities and operating parameters 1030 may include any number of capabilities and operating parameters associated with the primary link.
• the ML Element 1050 may include common information 1042.
• the common information 1042 may include MLD parameters and other information common to the primary link and one or more non-primary links associated with an AP MLD.
• FIG 11 A shows an example RNR Element 1100 usable for multi-link communications according to some implementations.
• the RNR element 1100 may be an example implementation of the RNR Element 1020 of the example management frames 1000 A and 1000B described with reference to Figures 10A and 10B, respectively.
• the RNR Element 1100 may be included in a frame such as (but not limited to) a beacon frame, a probe response frame, an association response frame, or a re-association response frame transmitted from an AP MLD.
• some information elements of the RNR element 1100 may be referred to as a “field,” a “subfield,” an “element,” or a “subelement,” which may be considered interchangeable terms for purposes of discussion herein.
• the RNR Element 1100 may be used to indicate channel information, parameters, and other information related to one or more APs that are affiliated with the AP MLD. As shown, the RNR Element 1100 includes an Element ID field 1102, a Length field 1104, and one or more Neighbor AP Information fields 1106.
• the Element ID field 1102 carries a value identifying the RNR Element 1100.
• the Length field 1104 carries a value indicating the length of the RNR Element 1100.
• Each Neighbor AP Information field 1106 carries information indicating timing references, the operating class, the channel number, and other parameters of a corresponding AP of the AP MLD.
• Figure 1 IB shows an example TBTT Information Header 1120 according to some implementations.
• the TBTT Information Header 1120 may be an example implementation of the TBTT Information Header 1111 of Figure 11 A.
• the TBTT Information Header 1120 includes a TBTT Information Field Type subfield 1121, a Filtered Neighbor AP subfield 1122, a reserved subfield 1123, a TBTT Information Count subfield 1124, and a TBTT Information Length subfield 1125.
• the TBTT Information Field Type subfield 1121 carries a value indicating the type or format of the TBTT Information field.
• the NSTR Link Pair field 1254 carries information identifying the pair of communication links associated with the AP corresponding to the Per-STA Profile subelement 1230.
• the NSTR Bitmap field 1255 carries an NSTR bitmap of the AP corresponding to the Per-STA Profile subelement 1230.
• the process 1600 begins in block 1602 with operating as an NSTR softAP MLD associated with a primary link and a non-primary link.
• the process 1600 continues with determining that the non-primary link is unavailable.
• the process 1600 continues with transmitting, on only the primary link, a frame carrying an indication of the unavailability of the non- primary link.
• the frame may be one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.
• the frame may be an action frame such as a Notification frame.
• the process 2100 may be performed after determining the unavailability of the non-primary link in block 1604 of Figure 16. For example, at block 2102, the process 2100 begins with disabling the non-primary link or placing the non-primary link into a power save state based on the unavailability of the non-primary link.
• the NSTR softAP MLD may also place the softAP (or other transmit chains, receive chains, signal processing circuitry, and so on) associated with the non-primary link into a sleep state, a doze state, or a power-off state while remaining fully operational on the primary link. In this way, the NSTR softAP MLD may reduce power consumption associated with operating on the non-primary link, and may also reduce cross-link interference resulting from UL transmissions on the non-primary link.
• FIG 23 shows a flowchart illustrating an example process 2300 for wireless communications that supports multi-link communications with an NSTR softAP MLD according to some implementations.
• the process 2300 may be performed by a wireless communication device such as the wireless communication device 500 described above with reference to Figure 5.
• the process 2300 may be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to Figures 1 and 6B, respectively.
• the process 2300 may be performed by an AP MLD such as the NSTR softAP MLD described with reference to Figure 7B.
• the process 2800 continues with receiving a third frame on only the primary link from the NSTR softAP MLD, the third frame indicating the complete profile of the non-primary link.
• the first frame may be one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.
• the second frame may be one of a probe request frame, an association request frame, or a reassociation request frame.
• the third frame may be one of a probe response frame, an association response frame, or a reassociation response frame.
• FIG. 29 shows a flowchart illustrating an example process 2900 for wireless communications that supports multi-link communications with an NSTR softAP MLD according to some implementations.
• the process 2900 may be performed by a wireless communication device such as the wireless communication device 500 described above with reference to Figure 5.
• the process 2900 may be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to Figures 1 and 6B, respectively.
• the process 2900 may be performed by an AP MLD such as the NSTR softAP MLD described with reference to Figure 7A.
• the frame may be any suitable frame including (but not limited to) a management frame, a control frame, or a data frame.
• Figure 31 shows a flowchart illustrating an example process 3100 for wireless communications that supports multi-link communications with an NSTR softAP MLD according to some implementations.
• the process 3100 may be performed by a wireless communication device such as the wireless communication device 500 described above with reference to Figure 5.
• the process 3100 may be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to Figures 1 and 6B, respectively.
• the process 3100 may be performed by an AP MLD such as the NSTR softAP MLD described with reference to Figure 9A.
• the process 3100 may be performed after recovering the non-primary link in block 3010 of Figure 30.
• the process 3100 begins with obtaining channel access on the non-primary link based on the channel access to the primary link.
• the process 3100 continues with transmitting a second frame on the non-primary link to a second associated STA concurrently with the transmission of a third frame on the primary link to the first associated STA.
• the NSTR softAP MLD may synchronize transmission of the second frame on the non-primary link with the transmission of the third frame on the primary link.
• the process 3200 begins with obtaining channel access on the non-primary link during at least a portion of the channel access obtained on the primary link.
• the process 3200 continues with transmitting a second frame on the non-primary link to one or more second associated STAs during the transmission of the first frame on the primary link.
• the process 3300 begins in block 3302 with operating as an NSTR softAP MLD associated with a primary link and a non-primary link.
• the process 3300 continues with obtaining channel access to the primary link and the non-primary link.
• the process 3300 continues with establishing a coordinated target wait time (TWT) session on the primary link and the non-primary link.
• TWT target wait time
• the process 3300 continues with transmitting a first trigger frame on the primary link, the first trigger frame soliciting uplink (UL) transmissions from a first group of STAs on the primary link.
• the process 3300 continues with transmitting a second trigger frame on the non-primary link concurrently with the transmission of the first trigger frame on the primary link, the second trigger frame soliciting UL transmissions from a second group of STAs on the non-primary link.
• the coordinated TWT sessions may include one or more respective service periods (SPs) during which corresponding STAs or corresponding groups of STAs can be scheduled or triggered for UL transmissions on the respective primary and non-primary links.
• SPs service periods
• the process 3400 may be performed after transmitting the trigger frames in blocks 3308 and 3310 of Figure 33.
• the process 3400 may begin in block 3402 with receiving one or more first UL PPDUs on the primary link from the first group of STAs based on the first trigger frame.
• the process 3400 continues receiving one or more second UL PPDUs on the nonprimary link from the second group of STAs based on the second trigger frame.
• transmissions of the first and second UL PPDUs from the first and second respective groups of STAs may be synchronized with one other.
• FIG 35 shows a flowchart illustrating an example process 3500 for wireless communications with an NSTR softAP MLD according to some implementations.
• the process 3500 may be performed by a wireless communication device such as the wireless communication device 500 described above with reference to Figure 5.
• the process 3500 may be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to Figures 1 and 6B, respectively.
• the process 3500 may be performed by an AP MLD such as the NSTR softAP MLD described with reference to Figure 9B.
• the process 3500 may be performed in conjunction with the process 3300 of Figure 33.
• the process 3500 may begin in block 3502 with synchronizing one or more TWT service periods on the non-primary link with one or more respective TWT service periods on the primary link.
• transmission of the one or more first UL PPDUs by the first group of STAs on the primary link can temporally aligned with the transmission of the one or more second UL PPDUs by the second group of STAs on the non-primary link.
• FIG 36 shows a flowchart illustrating an example process 3600 for wireless communications that supports multi-link communications with an NSTR softAP MLD according to some implementations.
• the process 3600 may be performed by a wireless communication device such as the wireless communication device 500 described above with reference to Figure 5.
• the process 3600 may be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to Figures 1 and 6B, respectively.
• the process 3600 may be performed by an AP MLD such as the NSTR softAP MLD described with reference to Figure 9B.
• FIG 37 shows a block diagram of an example wireless communication device 3700 according to some implementations.
• the wireless communication device 3700 is configured to perform the communications 700 of Figure 7A, the communications 710 of Figure 7B, or the communications 810 of Figure 8A.
• the wireless communication device 3700 can be an example implementation of the wireless communication device 500 described above with reference to Figure 5.
• the wireless communication device 3700 can be a chip, SoC, chipset, package or device that includes at least one processor and at least one modem (for example, a Wi-Fi (IEEE 802.11) modem or a cellular modem).
• the wireless communication device 3700 can be a device for use in a STA, such as one of the STAs 104 and 604 described with reference to Figures 1 and 6B, respectively.
• the wireless communication device 3700 can be a STA that includes such a chip, SoC, chipset, package or device as well as at least one antenna (such as the antennas 625 of Figure 6B).
• the wireless communication device 3700 may be an example of one or more of the NSTR softAP MLDs described herein.
• portions of one or more of the components 3721, 3722, 3723, 3724, 3725, and 3726 can be implemented as non-transitory instructions (or “code”) executable by a processor (such as the processor 506 of Figure 5) to perform the functions or operations of the respective component.
• the reception component 3710 is configured to receive RX signals over one or more wireless channels or links from other wireless communication devices.
• the communication manager 3720 is configured to control or manage communications with the other wireless communication devices.
• the channel access component 3721 contends for and obtains channel access to a primary link and/or a non-primary link associated with the wireless communication device 3700.
• the frame generation component 3722 generates frames for transmitting discovery information, profile information, operation parameters, updates to the operation parameters, link availability, link timing references, and other suitable information pertaining to an MLD operating on the primary link and the non-primary link.
• the link profile component 3723 generates a complete profile or a partial profile for one or more of the primary link and the non-primary link.
• the link availability component 3724 indicates whether or not the primary link and/or the non-primary link are available.
• the parameters update component 3725 determines changes to one or more parameters of the primary link and the non-primary link, and transmits indications of the parameter updates.
• the timing and synchronization component 3726 generates timing references for the non-primary link relative to the primary link.
• the transmission component 3730 is configured to transmit TX signals, over the wireless channel, to one or more other wireless communication devices.
• the transmission component 3730 may transmit frames that include or indicate discovery information, profile information, operation parameters, updates to the operation parameters, link availability, link timing references, and other suitable information pertaining to the primary link and the non-primary link associated with the wireless communication device 3700.
• FIG 38 shows a block diagram of another example wireless communication device 3800 according to some implementations.
• the wireless communication device 3800 is configured to perform the communications 810 of Figure 8B.
• the wireless communication device 3800 can be an example implementation of the wireless communication device 500 described above with reference to Figure 5.
• the wireless communication device 3800 can be a chip, SoC, chipset, package or device that includes at least one processor and at least one modem (for example, a Wi-Fi (IEEE 802.11) modem or a cellular modem).
• the wireless communication device 3800 can be a device for use in a STA, such as one of the STAs 104 and 604 described with reference to Figures 1 and 6B, respectively.
• the wireless communication device 3800 can be a STA that includes such a chip, SoC, chipset, package or device as well as at least one antenna (such as the antennas 625 of Figure 6B).
• the wireless communication device 3800 may be an example of one or more of the STA MLDs described herein.
• the wireless communication device 3800 includes a reception component 3810, a communication manager 3820, and a transmission component 3830.
• the communication manager 3820 further includes a channel access component 3821, a frame generation component 3822, and a profile request component 3823. Portions of one or more of the components may be implemented at least in part in hardware or firmware. In some implementations, at least some of the components 3821, 3822, and 3823 are implemented at least in part as software stored in a memory (such as the memory 508). For example, portions of one or more of the components 3821, 3822, and 3823 can be implemented as non-transitory instructions (or “code”) executable by a processor (such as the processor 506) to perform the functions or operations of the respective component.
• the reception component 3810 is configured to receive RX signals over one or more wireless channels or links from other wireless communication devices.
• the communication manager 3820 is configured to control or manage communications with the other wireless communication devices.
• the channel access component 3821 contends for and obtains channel access to a primary link and/or a non-primary link associated with an AP MLD such as a NSTR softAP MLD.
• the frame generation component 3822 generates frames for carrying capabilities and operation parameters of the wireless communication device 3800.
• the profile request component 3823 generates a request for the AP MLD to provide the complete profile or the partial profile of one or more of the primary link and the non-primary link.
• the transmission component 3830 is configured to transmit TX signals, over the wireless channel, to one or more other wireless communication devices.
• the transmission component 3830 may transmit frames that include or indicate capabilities, operation parameters, profile requests, and other suitable information pertaining to the primary link and the non-primary link associated with the AP MLD.
• a method for wireless communication by a wireless station including: operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) including a first AP associated with a primary link and including a second AP associated with a non-primary link; and transmitting a frame on only the primary link, the frame including a complete profile of the primary link and indicating a complete profile of the non-primary link, the respective complete profiles of the primary link and the non-primary link each including at least a beacon interval, capability information, a service set identifier (SSID), supported rates, a timing synchronization function (TSF) value, and one or more additional fields or elements associated with discovery of the respective link.
• NSTR non-simultaneous transmit-receive
• AP soft access point
• MLD multi-link device
• TMF timing synchronization function
• the frame body further includes a Reduced Neighbor Report (RNR) Element including a Neighbor AP Information field associated with the non-primary link, the Neighbor AP Information field including a target beacon transmission time (TBTT) Information field consisting of a basic service set identification (BSSID) and one or more MLD parameters of the non-primary link.
• RNR Reduced Neighbor Report
• TBTT target beacon transmission time
• BSSID basic service set identification
• the BSS parameters include at least one of a Channel Switch Announcement (CSA) element, an extended Channel Switch Announcement (eCSA) element, an Enhanced Distributed Channel Access (EDC A) parameter, a Quiet period element, a Direct Sequence Spread Spectrum (DSSS) parameter set, a high-throughput (HT) operation element, a very high-throughput (VHT) operation element, a high-efficiency (HE) operation element, an extremely high-throughput (EHT) operation element, a Wide Bandwidth Channel Switch element, an Operating Mode Notification element, a Broadcast Target Wait Time (TWT) element, a BSS Color Change Announcement element, a Multi-User (MU) EDCA parameter set, a Spatial Reuse parameter set, or an uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameter set.
• CSA Channel Switch Announcement
• eCSA extended Channel Switch Announcement
• EDC A Enhanced Distributed Channel Access
• Quiet period element
• the frame includes one of a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or an action frame.
• a wireless communication device including: at least one modem; at least one processor communicatively coupled with the at least one modem; and at least one memory communicatively coupled with the at least one processor and storing processor-readable code that, when executed by the at least one processor in conjunction with the at least one modem, is configured to: operate as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with a primary link and a non-primary link; obtain channel access on the primary link; transmit a first frame on the primary link to a first associated STA; enter the non-primary link into a deaf state for a duration of the frame transmission on the primary link; and recover the non-primary link from the deaf state after an end of the frame transmission on the primary link.
• NSTR non-simultaneous transmit-receive
• AP soft access point
• MLD multi-link device

Landscapes

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

Applications Claiming Priority (3)

Publications (1)

Family

ID=82702966

Family Applications (2)

Family Applications After (1)

Country Status (5)

Families Citing this family (5)

Family Cites Families (5)

• 2022
  • 2022-06-24 WO PCT/US2022/034881 patent/WO2023027799A1/en not_active Ceased
  • 2022-06-24 JP JP2024510487A patent/JP2024532219A/ja active Pending
  • 2022-06-24 JP JP2024510488A patent/JP2024532220A/ja active Pending
  • 2022-06-24 EP EP22747834.4A patent/EP4393210A1/en active Pending
  • 2022-06-24 EP EP22751190.4A patent/EP4393212A1/en active Pending
  • 2022-06-24 KR KR1020247005511A patent/KR20240043146A/ko active Pending
  • 2022-06-24 KR KR1020247005510A patent/KR20240043145A/ko active Pending
  • 2022-06-24 WO PCT/US2022/034927 patent/WO2023027800A1/en not_active Ceased
  • 2022-07-05 TW TW111125078A patent/TW202310663A/zh unknown
  • 2022-07-05 TW TW111125077A patent/TW202310662A/zh unknown

Also Published As

Similar Documents

Legal Events