Key generation for seamless roaming

By pre-generating and distributing PTKs in the seamless mobile domain, the problem of key generation delay in seamless roaming is solved, enabling a faster roaming process.

CN123077148APending Publication Date: 2026-11-10CISCO TECHNOLOGY INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580024494.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-03-25
Filing Date
2025-03-25
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing technologies require frequent random number exchanges when generating key levels during seamless roaming, leading to increased roaming transition time and latency.

Method used

Paired temporary keys (PTKs) are pre-generated in the seamless mobile domain and distributed to target access points (APs) via push or pull models to avoid random number exchange during roaming.

Benefits of technology

It reduces roaming time, improves the efficiency of seamless roaming, and avoids additional key negotiation delays.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123077148A_ABST
    Figure CN123077148A_ABST
Patent Text Reader

Abstract

A Seamless Mobility Domain (SMD) is described, in which a PTK (Pre-Computed Key) for a wireless device is pre-computed or pre-generated before a client roams from a serving AP in the SMD to a target AP. The pre-computed PTK can be distributed (i.e., pushed) to one or more target APs before the wireless device roams, or the PTK can be stored in a key repository and retrieved by the target AP from the key repository once the wireless device roams to the target AP. In another embodiment, a PMK and / or PTK key is generated using an SMD identifier, such as an SMD MAC address or a special ID used for the SMD.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications This application claims the benefit of co-pending U.S. Provisional Patent Application Serial No. 63 / 569,653, filed March 25, 2024. The entire contents of the aforementioned patent application are incorporated herein by reference. Technical Field

[0002] The embodiments presented in this disclosure generally relate to roaming in a seamless mobile domain (SMD) using a pre-generated key. Background Technology

[0003] The Ultra-High Reliability Study Group (UHR SG) and IEEE 802.11bn (Wi-Fi 8) have discussed roaming enhancements to support more reliable and seamless roaming. To achieve seamless roaming, it is desirable to reduce roaming transition times and minimize latency increases due to roaming-related operations.

[0004] Using Fast Transform (FT), a key hierarchy is generated, where a pairwise master key (PMK) is generated for each access point (AP) in the mobile domain. Specifically, a root key (called PMK R0) is created for each station (STA) or client associated with the mobile domain. Then, a PMK (i.e., PMK R1) for each AP is generated from the root key PMK R0. When an STA roams between APs in the mobile domain, both the STA and the AP must generate a new pairwise temporary key (PTK). This is performed using random number exchange between the STA and the new AP, thus increasing roaming time. Attached Figure Description

[0005] To enable a detailed understanding of the features described above in this disclosure, a more specific description of the disclosure, which has been briefly summarized above, can be obtained by referring to the embodiments, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only typical embodiments and should not be considered limiting; other equally effective embodiments are also contemplated.

[0006] Figure 1 The pre-generation of PTK in a seamless mobile domain is illustrated according to one embodiment.

[0007] Figure 2 This is a flowchart of pre-generating PTK in a seamless mobile domain according to one embodiment.

[0008] Figure 3 This is a workflow for pre-generating a generic PTK in a seamless mobile domain, according to one embodiment.

[0009] Figure 4 This is a workflow for pre-generating PTK for each AP in a seamless mobile domain, according to one embodiment.

[0010] Figure 5 This is a workflow for generating PMK and PTK for each AP in a seamless mobile domain, according to one embodiment.

[0011] Figure 6 This is a workflow for pre-generating PTK for each AP in a seamless mobile domain, according to one embodiment.

[0012] Figure 7 An example computing device configured to perform various aspects of this disclosure is depicted according to one embodiment.

[0013] For ease of understanding, the same reference numerals are used where possible to refer to common elements in the figures. It is conceivable that elements disclosed in one embodiment may be advantageously used in other embodiments without being specifically enumerated. Detailed Implementation

[0014] Overview One embodiment of this disclosure is a network device including one or more memories and one or more processors communicatively coupled to the one or more memories, wherein the one or more processors are configured to perform operations individually or jointly. The operations include: generating a pairwise temporary key (PTK) after the wireless device associates with a first access point (AP) in a seamless mobile domain (SMD) for exchanging encrypted content between the wireless device and a second AP in the SMD; and making the PTK available to the second AP before the wireless device communicates with the second AP.

[0015] One embodiment of this disclosure is a method comprising: associating a wireless device with a first access point (AP) in an SMD; generating a PTK for exchanging encrypted content between the wireless device and a second AP in the SMD; and making the PTK available to the second AP prior to communication between the wireless device and the second AP.

[0016] One embodiment of this disclosure is a network device including one or more memories and one or more processors communicatively coupled to the one or more memories, wherein the one or more processors are configured to perform operations individually or jointly. The operations include: generating a PMK for the wireless device after the wireless device is associated with an AP in an SMD, or when the wireless device is associated with an AP in the SMD, and generating a PTK based on the PMK for exchanging encrypted content between the wireless device and the AP. Furthermore, at least one of the PMK or the PTK is generated using an identifier of the SMD, wherein the identifier of the SMD can be one of an SMD MAC address or an SMD ID.

[0017] Example Implementation The embodiments described herein depict a Seamless Mobility Domain (SMD) in which a PTK is pre-computed or pre-generated for the client / STA / non-AP MLD (or more generally, wireless devices) prior to a client roaming from a serving AP in the SMD to a target AP. The pre-computed PTK may be distributed (i.e., pushed) to one or more target APs before the client roams, or the PTK may be stored in a key repository and retrieved by the target AP from the key repository once the client initiates roaming to the target AP. In one embodiment, the pre-computed PTK may be the same PTK shared by each AP in the SMD (…). Figure 3 In other embodiments, the system uses the root PTK to pre-compute a separate PTK for the AP in the SMD. Figure 4 ), or pre-compute a separate PTK by using the PTK generated at the serving AP ( Figure 6 By pre-compiling the PTK, the four-way handshake typically used to generate the PTK during client roaming can be avoided, thereby reducing roaming time. In each of these embodiments, the PTK can be pre-computed without requiring a separate random number exchange between the wireless device and the target AP for PTK generation.

[0018] The embodiments described herein also include generating the PMK and / or PTK using an SMD identifier (ID). This advantageously binds the PMK and PTK to the SMD. The SMD ID can be an SMD MAC address (which may be different from the MAC address of the AP in the SMD), a special ID used for the SMD (which may be shorter than the MAC address), or the same as the MAC address of one of the APs in the SMD. The SMD ID can be used as input to a hash function for generating the PMK or PTK. Furthermore, it can be advantageous to generate the PMK or PTK using the SMD ID, whether the PTK is pre-computed before roaming or during roaming.

[0019] Figure 1A pre-generated PTK in a seamless mobility domain is illustrated according to one embodiment. In this example, SMD 100 includes both a serving AP 110A (to which STA 105 is currently associated) and a target AP 110B to which STA 105 may roam in the future. Although two APs are shown, SMD 100 can include any number of APs. For example, APs in a deployment (e.g., multi-story building, campus, warehouse, etc.) can be part of the same SMD 100. In one embodiment, SMD 100 enables STAs to switch between APs without losing connectivity. SMD 100 allows STAs to associate with one AP in SMD 100 at a time and then seamlessly roam to any other AP in SMD 100. SMD 100 may enable services such as key sharing, which will be discussed in more detail below, that facilitate seamless STA roaming (i.e., without needing to re-associate with target AP 105B).

[0020] Figure 1 Arrow 115 in the diagram indicates that STA 105 was initially associated with the serving AP 110A. When STA 105 first associates with an AP in SMD 100 (or more generally, the mobile domain), the station is authorized using, for example, Simultaneous Peer Authentication (SAE) or Extensible Authentication Protocol (EAP) as defined in IEEE 802.1x, or a pre-shared key (PSK). Once authenticated, SMD generates a PMK, from which a PTK can be generated. The PMK and PTK can be used generically within SMD (e.g., each AP uses the same PMK and PTK, such as...). Figure 3 As shown), each AP uses the same PMK but each AP uses a different PTK (e.g., Figure 4 As shown), each AP receives different PMK and PTK (e.g. Figure 5 (as shown), or use the PTK of the serving AP 110A to generate a different PTK for each AP (such as...). Figure 6 (As shown).

[0021] exist Figure 3 , Figure 4 and Figure 6 In the illustrated embodiment, the PTK is pre-generated (i.e., before STA 105 decides to roam to the target AP 110B), while Figure 5 In this context, PTK is generated after (or at) STA 105 decides to roam to target AP 110B.

[0022] Figure 1 The pre-generated PTK 120 is shown as can be generated by the serving AP 110A or the WLAN controller (WLC) 125, as indicated by the dashed lines. Furthermore, although... Figure 1Not shown, instead of pushing the pre-generated PTK 120 to the target AP 110B (referred to as the push model), the serving AP 110A or WLC 125 can store the pre-generated PTK 120 in a key repository accessible by APs in the SMD, and the target AP 110B can pull the PTK 120 from the key repository after learning that STA 105 is roaming to the target AP 110B (referred to as the pull model). In either case, the pre-generated PTK 120 has already been generated, so STA 105 and the target AP 110B do not need to exchange random numbers to generate their respective PTKs during roaming, thereby reducing roaming latency.

[0023] Figure 2 This is a flowchart of a method 200 for pre-generating a PTK in an SMD according to one embodiment. In block 205, the STA (also known as a client, non-AP MLD, or wireless device) is associated with a first AP in the SMD.

[0024] In box 210, the SMD generates a PTK for exchanging encrypted content with the STA and the second AP in the SMD. That is, the PTK is generated (or computed) before the STA roams to the second AP. For example, the STA may still be associated with the first AP (e.g., the serving AP). Therefore, in box 210, since the PTK is generated for use by the second AP (e.g., the target AP) before the STA roams to the second AP, this PTK is referred to as a pre-generated or pre-computed PTK.

[0025] The pre-generated PTK can be generated by the first AP, or it can be generated by the controller in the SMD (such as...). Figure 1 The PTK is generated from the PMK (WLC125). Because the PTK is generated from the PMK, the PMK can be transferred to any executor responsible for pre-compiling the PTK.

[0026] While method 200 describes pre-compiling a PTK, the SMD can generate multiple PTKs for multiple target APs. For example, in some embodiments, the SMD pre-compiles individual PTKs for a set of potential roaming target APs in the SMD. For example, the SMD can generate a PTK for each AP in the SMD, or it can generate a PTK for a subset of APs (e.g., only the neighboring APs of the first AP currently serving the STA).

[0027] Following box 210, method 200 either transfers the PTK to the second AP in box 215 or stores the PTK in a key repository in box 220. That is, box 215 is an example of a push model, where pre-computed PTK(one or more) is pushed to the second AP(one or more); and box 220 is an example of a pull model, where pre-computed PTK(one or more) is stored in a key repository. When the STA begins roaming to the second AP, the second AP can query the key repository to retrieve (i.e., pull) the pre-computed PTK.

[0028] In block 225, the STA roams from the first AP to the second AP. The embodiments described herein are not limited to any particular seamless roaming process. In one embodiment, the STA may notify the first AP that it wishes to roam to the second AP, and the first AP may transfer the roaming context to the second AP to perform seamless roaming. This roaming context may include a protocol or capability, an association context, and a roaming MAC address (the MAC address used as the sender address (TA) when roaming). In another embodiment, the STA may notify the second AP that it wishes to roam to the second AP while the first AP is still the STA's serving AP (referred to as "roaming by destination"). The second AP can then obtain the roaming context from the first AP.

[0029] In one embodiment, the context of the transfer includes PTK and / or PMK, which the second AP can use to securely communicate with the wireless device. That is, the first AP can transfer this information to the second AP (or the second AP can obtain this information from the first AP).

[0030] In block 230, the second AP uses the PTK to exchange encrypted content with the STA. The encrypted content may include encrypted data or encrypted management frames. In one embodiment, the second AP does not need to calculate its PTK for secure communication with the STA, because the PTK has been pre-calculated in block 210. STA 105 can roam without re-association and without renegotiating the PTK (e.g., using a four-way handshake and random number exchange).

[0031] Figure 3This is a workflow 300 for pre-generating a generic PTK in SMD 100 according to one embodiment. Workflow 300 illustrates two different ways of performing initial authentication between STA 105 and SMD 100. Arrow 305 shows PSK / SAE authorization performed between STA 105 and the serving (or first) AP 110A, while arrow 315 shows 802.1X / EAP authorization performed between STA 105 and the serving AP 110A. If PSK / SAE authorization is used, it is performed before STA 105 transmits the (re)association request and the serving AP 110A transmits the response, as shown by arrow 310. However, if 802.1X / EAP authorization is performed, it is performed after the (re)association request / response shown by arrow 310.

[0032] In either case, after authentication, both STA 105 and the service AP 110A generate the PMK-SMD. That is, the PMK-SMD is generated independently on both STA 105 and the service AP 110A. Alternatively, the PMK-SMD may be generated at the WLC.

[0033] In one embodiment, STA 105 and the serving AP 110A receive (or generate) a master PMK (MPMK) and then use the MPMK to generate a PMK-SMD. For example, the MPMK can be generated from an MSK (for IEEE 802.1X authentication), a PSK (for password-based authentication), or a PMK (for SAE-based authentication) as defined in the 802.11 standard.

[0034] In one embodiment, STA 105 and the serving AP 110A use a key derivation function (KDF) from IEEE 802.11 to generate PMK-SMD: Output key = KDF- Hash - Length (Key, Label, Context) KDF can be modified to generate PMK-SMD as follows: PMK-SMD = KDF- Hash - Length (MPMK, “ST-PMK”, SSIDlength || SSID || SMDMAC address || AP MLD MAC address || SPA) KDF-Hash-Length is the KDF used for negotiating the AKM (Authentication and Key Management) cryptographic suite. "Hash" indicates the hash algorithm (e.g., SHA-256). "Length" indicates the length of the hash algorithm's digest (e.g., 192 bits, 256 bits, etc.). In the aforementioned equation, the inputs to the KDF hash are MPMK, the string "ST PMK", the Service Set Identifier (SSID) length, the SSID, the MAC address of the SMD, the MAC address of the serving AP 110A, and the SPA (e.g., the MAC address of STA 105). These inputs are concatenated when fed into the hash function.

[0035] "ST-PMK" provides a unique label for PMK-SMD generation, where ST stands for "Seamless BSS Transformation". Alternatively, this label can be any other suitable unique string used for this KDF, and can be agreed upon in the standard.

[0036] The context string includes the SMD MAC address to bind PMK-SMD to the SMD. This string also includes the AP MLD MAC address of the AP MLD that generated PMK-SMD. Additionally, it includes the SPA, which is the MAC address of the STA 105.

[0037] Alternatively, a shortened SMD ID (SMD identifier) ​​can be included in the PMK-SMD generation, as follows: PMK-SMD = KDF- Hash - Length (MPMK, “ST-PMK”, SSIDlength || SSID || SMDID || AP MLD MAC address || SPA) In another embodiment, PMK-SMD is not bound to any SMD ID and uses the same algorithm defined in the 802.11 standard. Therefore, generating PMK using an SMD ID is not required.

[0038] In another embodiment, PMK-SMD may not be bound to an SSID, for example, when the SMD is defined to include APs belonging to more than one Extended Service Set (ESS) / SSID.

[0039] In one embodiment, during the initial association between the STA and SMD 100, the PTK-SMD is generated as part of a four-way handshake performed after a (re)association request / response exchange between the STA 105 and the service AP 110A.

[0040] Arrow 320 illustrates STA 105 and the serving AP 110A performing a four-way handshake to generate PTK-SMD. In one embodiment, PTK-SMD is generated from PMK-SMD, as shown below: PTK-SMD = KDF- Hash - Length (PMK-SMD, “ST-PTK”, SNonce || ANonce || SMD MAC address || AP MLD MAC address || SPA) The “ST-PTK” label can be set to any other appropriate label used for PTK generation.

[0041] Alternatively, a shortened SMDID (which can be shorter than the MAC address) can be included in the PTK-SMD generation, as shown below: PTK-SMD = KDF- Hash - Length (PMK-SMD, “ST-PTK”, SNonce || ANonce || SMDID || AP MLD MAC address || SPA) In another embodiment, PTK-SMD includes only the SMD MAC address and excludes the MLD MAC address of the service AP110A that generated PTK-SMD. This binds PTK-SMD solely to the SMD.

[0042] PTK-SMD = KDF- Hash - Length (PMK-SMD, “ST-PTK”, SNonce || ANonce || SMDMAC address || SPA) In one embodiment, PTK-SMD uses the Robust Secure Network Association (RSNA) key update procedure for key updates. This key update can be performed after roaming has occurred.

[0043] Arrow 325 illustrates the distribution of PMK-SMD and PTK-SMD to one or more target APs 110B. Arrow 325 represents a push model where PMK-SMD and PTK-SMD are pushed to target APs 110B and installed there. In this example, this occurs during the initial association of STA 105 with SMD 100, but it can be performed when STA 105 roams to another AP within SMD 100.

[0044] Arrow 330 illustrates the pull model, where PMK-SMD and PTK-SMD are transmitted and stored in the key repository 360. Then, when one of the target APs 110 requests them, the key repository 360 can provide PMK-SMD and PTK-SMD. For example, when STA 105 initiates a roaming to another target AP 110B, as shown by arrow 335, and if PMK-SMD and PTK-SMD are not already installed at the target AP 110B, these keys can be obtained from the key repository 360 (as shown by arrow 340) and installed. However, using the push model, when the roaming request shown by arrow 335 is received, PMK-SMD and PTK-SMD are already installed at the target AP 110B.

[0045] Although Figure 3 The example shown illustrates that the serving AP 110A makes the PTK available to one or more target APs (e.g., distributing PMK-SMD and PTK-SMD to target AP 110B or key repository 360), but in another embodiment, the WLC can distribute these keys.

[0046] Figure 3 The advantage of the push and pull models shown is that the target AP 110B does not need to negotiate with STA 105 to generate the PTK, because the PTK can be pre-computed on both STA 105 and the target AP 110B. In the pull model, the only latency is the time it takes for the target AP 110B to retrieve the pre-computed PMK-SMD and PTK-SMD from the key repository 360.

[0047] Figure 3 Key level 350 is also shown. As shown, PTK-SMD is generated from PMK-SMD. Each AP in SMD communicates with STA 105 using the same PMK-SMD and PTK-SMD. When a new STA 105 is associated with SMD 100, new PMK-SMD and PTK-SMD are generated and distributed as discussed above. That is, each STA associated with SMD has a different PMK-SMD and PTK-SMD, and each AP in SMD 100 uses the PMK-SMD and PTK-SMD to exchange encrypted content with the corresponding STA.

[0048] Figure 4 This is a workflow 400 for pre-generating a PTK for each AP in an SMD 100 according to one embodiment. (Compared to...) Figure 3 Same, Figure 4 The workflow 400 uses the same PMK-SMD. However, compared to... Figure 3 The workflow 400 generates different PTKs for the AP in SMD 100.

[0049] Arrow 405 indicates PSK / SAE authorization being performed between STA 105 and the serving (or first) AP 110A, while arrow 415 indicates 802.1X / EAP authorization being performed between STA 105 and the serving AP 110A. If PSK / SAE authorization is used, it is performed before STA 105 transmits the (re)association request and the serving AP 110A transmits the response, as shown by arrow 410. However, if 802.1X / EAP authorization is performed, it is performed after the (re)association request / response, as shown by arrow 410.

[0050] In either case, after authentication, both STA 105 and the serving AP 110A generate the PMK-SMD. That is, the PMK-SMD is generated independently on both STA 105 and the serving AP 110A. Alternatively, the PMK-SMD can be generated at the WLC. The above can be used... Figure 3 Any techniques and equations discussed herein are used to generate PMK-SMD.

[0051] Arrow 420 illustrates that STA 105 and the serving AP 110A perform a four-way handshake to generate a root PTK (i.e., PTK-SMD-R0) at both STA 105 and the serving AP 110A. The serving AP 110A (or WLC) can use the root PTK-SMD-R0 to generate individual PTKs (i.e., PTK-R1 keys) for one or more target APs 110B. That is, workflow 400 has two levels of PTK-SMD keys: PTK-SMD-R0 and PTK-R1 keys. In one embodiment, the PTK-R0 key holder is the AP that generated the PTK-SMD-R0 (in this example, the serving AP 110A, but it could also be the WLC). The PTK-R1 key holder is the AP that holds the PTK-R1 (e.g., the serving AP 110A).

[0052] A single PTK-SMD-R0 is generated by the PTK-R0 key holder as follows. The PTK-SMD-R0 can have the same validity / expiration period as the PMK-SMD.

[0053] PTK-SMD-R0 = KDF- Hash - Length (PMK-SMD, “ST-PTK-R0”, SNonce || ANonce || SMD MAC address || PTK-R0-KH MAC address || SPA) The PTK-R0-KH MAC address is the MAC address of the AP that generated PTK-SMD-R0.

[0054] In another embodiment, PTK-SMD-R0 includes only the SMD MAC address and excludes the MLD MAC address of the AP that generated PTK-SMD-R0 (e.g., serving AP 110A). This binds PTK-SMD-R0 solely to the SMD: PTK-SMD-R0 = KDF- Hash - Length (PMK-SMD, “ST-PTK-R0”, SNonce || ANonce || SMD MAC address || SPA) A set of PTK-R1 keys can be derived from PTK-SMD-R0 by the R0 key holder, one for each AP of SMD 100, as follows: PTK-R1 = KDF- Hash - Length (PTK-SMD-R0, “ST-PTK-R1”, SMD MAC address || PTK-R1-KH MAC address || SPA) or PTK-R1 = KDF- Hash - Length (PTK-SMD-R0, “ST-PTK-R1”, PTK-R1-KH MAC address || SPA) The PTK-R1-KH MAC address is the MLD MAC address of the AP (the holder of the PTK-R1) that generated the PTK-R1.

[0055] PTK-R1 keys can have a short validity period and are updated using the RSNA key update process.

[0056] Each PTK-R1 key does not need to be explicitly bound to an SMD MAC address. Furthermore, generating a different PTK-R1 key for each AP of the SMD 100 does not require a new set of random number exchanges between the STA 105 and the corresponding target AP 110B. Once the PTK-R1 keys are generated, they can be installed on the corresponding target AP 110B, which is the PTK-R1 key holder. Additionally, PTK-R1 keys can be updated using existing RSNA key update procedures.

[0057] Arrow 425 illustrates the distribution of the PMK-SMD and PTK-R1 keys to one or more target APs 110B. That is, each target AP 110B receives the same PMK-SMD but a different PTK-R1 key. Arrow 325 represents a push model where the PMK-SMD and PTK-R1 keys are pushed to the target AP 110B and installed there. In this example, this is done during the initial association of STA 105 with SMD 100, but it can be performed when STA 105 roams to another AP within SMD 100.

[0058] Arrow 430 illustrates the pull model, where the PMK-SMD and PTK-R1 keys are transmitted and stored in the key repository 360. Then, when one of the target APs 110 requests them, the key repository 360 can provide the PMK-SMD and PTK-R1 keys. For example, when STA 105 initiates a roaming request to another target AP 110B, as shown by arrow 435, and if the PMK-SMD and its corresponding PTK-R1 keys are not already installed at the target AP 110B, these keys are retrieved from the key repository 360 and installed, as shown by arrow 440. However, using the push model, when the roaming request shown by arrow 435 is received, the PMK-SMD and PTK-R1 keys are already installed at the target AP 110B.

[0059] Although Figure 4 The illustration shows that the serving AP 110A distributes PMK-SMD and PTK-R1 keys to the target AP 110B or key repository 360, but in another embodiment, the WLC can distribute these keys.

[0060] Furthermore, as shown, STA 105 still locally generates PTK-R1 for use when communicating with the target AP 110B, but STA 105 can generate PTK-R1 without any exchange with the target AP 110B, meaning roaming does not require additional exchanges as in the FT case. STA 105 can generate PTK-R1 from the locally generated root PTK-SMD-R0, which is derived from PMK-SMD. Advantageously, roaming can be performed using two frame exchanges (e.g., roaming request and roaming response). Furthermore, STA 105 can generate its PTK-R1 after determining to roam to the target AP 110B, or it can pre-compute its PTK-R1 before STA 105 decides to roam.

[0061] Figure 4 Key level 450 is also shown. As shown, root PTK-SMD-R0 is generated from PMK-SMD. Each AP in SMD uses a different PTK-R1 (i.e., PTK-R1...).A PTK-R1 B (etc.) communicates with STA 105. When a new STA 105 is associated with SMD 100, a new PMK-SMD, root PTK-SMD-R0, and PTK-R1 are generated and distributed as discussed above. That is, each AP uses a different PTK-R1 to exchange encrypted content with the corresponding STA.

[0062] Figure 5 This is a workflow 500 for generating PMK and PTK for each AP in an SMD 100 according to one embodiment. Figure 3 and Figure 4 Unlike in Workflow 500, the AP's PTK is not pre-computed, but the PMK is pre-computed and distributed to other APs before STA 105 roams.

[0063] Arrow 505 indicates PSK / SAE authorization being performed between STA 105 and the serving (or first) AP 110A, while arrow 515 indicates 802.1X / EAP authorization being performed between STA 105 and the serving AP 110A. If PSK / SAE authorization is used, it is performed before STA 105 transmits the (re)association request and the serving AP 110A transmits the response, as shown by arrow 510. However, if 802.1X / EAP authorization is performed, it is performed after the (re)association request / response, as shown by arrow 510.

[0064] In either case, after authentication, both STA 105 and Service AP 110A generate root PMK-SMD-R0 and PMK-R1. These can be used with... Figure 3 and Figure 4 The same technique described in the document is used to generate the root PMK-SMD-R0.

[0065] In addition, the serving AP 110A generates one or more PMK-R1 keys for one or more target APs 110B in SMD 100. That is, with Figure 3 and Figure 4 Each AP in SMD 100 uses the same master PMK (i.e., PMK-SMD), but different master PMKs are generated for each AP based on each STA / client. Different PMK-R1 keys can be derived from the root PMK-SMD-R0 as follows: PMK-R1 = KDF- Hash - Length (PMK-SMD-R0, “ST-PMK-R1”, PMK-R1-KH MAC address || SPA) The PMK-R1-KH MAC Address is the MLD MAC address of the AP that generated PMK-R1 (the holder of PMK-R1, which in this example is the serving AP 110A).

[0066] Arrow 520 illustrates STA 105 and serving AP 110A performing a four-way handshake to generate PTK-R1. Generating PTK-R1 for the first serving AP 110A where the initial (re)association occurs can include random values ​​from both sides (authenticator and requester), as shown below: PTK-R1 = KDF- for the first AP MLD Hash - Length (PMK-R1, “ST-PTK-R1”, SNonce|| ANonce || PTK-R1-KH MAC address|| SPA) The PTK-R1-KH MAC address is the MLD MAC address of the AP (the holder of the PTK-R1) that generated the PTK-R1. STA 105 and the serving AP 110A can then exchange encrypted content using the PMK-R1 and PTK-R1.

[0067] Arrow 525 shows that the serving AP 110A distributes PMK-R1 to the target AP 110B. For clarity, Figure 5 The key repository is not shown, but when using a pull model instead of a push model, the PMK-R1 can be stored in the key repository instead.

[0068] Arrow 530 illustrates STA 105 instructing serving AP 110A to initiate roaming preparation. In response, as shown by arrow 535, serving AP 110A can notify target AP 110B that STA 105 may roam to them. For example, serving AP 110A can provide target AP 110B with information about STA 105 (e.g., STA 105's SPA), enabling AP 110B to generate a PTK-R1 for communicating with STA 105.

[0069] Target AP 110B locally generates PTK-R1 using its own PMK-R1 (and information received from serving AP 110A) to communicate with STA 105. In one embodiment, target AP 110B derives PTK-R1 without explicit random number exchange with STA 105. PTK-R1 can be derived as follows: PTK-R1 = KDF- for target AP Hash - Length(PMK-R1, “ST-PTK-R1”, PTK-R1-KHMAC Address || SPA) Note that the generation of subsequent PTK-R1 keys for the target AP can be completed without the need for random number exchange between STA 105 and the target AP 110B. Subsequent PTK-R1 keys can be generated independently by STA 105 and the target AP 110B. This ensures that a different PTK is used for each target AP 110B without the need for negotiation to generate a new PTK for the target AP 110B.

[0070] Arrow 540 indicates that the serving AP 110A notifies STA 105 that roaming preparation is complete. This notifies STA 105 that the target AP 110B now has a PTK-R1 capable of secure communication with STA 105.

[0071] Arrow 545 shows STA 105 informing serving AP 110A which target AP 110B it wants to roam to. In response, serving AP 110A can transfer the roaming context to the selected target AP 110B, as shown by arrow 550. Arrow 555 shows serving AP 110A instructing STA 105 that the context transfer is complete. At this time (or before), STA 105 locally generates a PTK-R1 key.

[0072] The PMK-R1 and PTK-R1 keys have now been generated and installed on both the STA 105 and the target AP 110B, enabling secure uplink (UL) and downlink (DL) switching as shown by arrow 560.

[0073] Figure 5 The key level 590 is also shown, where different PMK and PTK keys are generated for each AP MLD of the SMD. That is, AP MLD A has different PMK and PTK keys for communicating with the STA than AP MLD B, and so on. This means that different PMK-R1 and PTK-R1 keys are generated for each AP MLD of the SMD. PMK-SMD-R0 is generated at the SMD level.

[0074] Figure 6 This is a workflow 600 for pre-generating PTK for each AP in SMD 100 according to one embodiment. In this example, such as Figure 3 and Figure 4 In the same way, a single PMK is generated, but a different PTK is generated for each AP.

[0075] Arrow 605 indicates PSK / SAE authorization being performed between STA 105 and the serving (or first) AP 110A, while arrow 615 indicates 802.1X / EAP authorization being performed between STA 105 and the serving AP 110A. If PSK / SAE authorization is used, it is performed before STA 105 transmits the (re)association request and the serving AP 110A transmits the response, as shown by arrow 610. However, if 802.1X / EAP authorization is performed, it is performed after the (re)association request / response, as shown by arrow 610.

[0076] In either case, after authentication, both STA 105 and Service AP 110A generate a root PMK-SMD. This can be used with... Figure 3 and Figure 4 The same technique described in the document for generating PMK-SMD is used to generate PMK-SMD.

[0077] Arrow 620 illustrates that STA 105 and the serving AP 110A perform a four-way handshake to generate a PTK at both STA 105 and the serving AP 110A. This initial PTK generated when STA 105 first associates with SMD 100 is called the PTK. current And it can be generated as follows: PTK current = KDF- Hash - Length (PMK, “ST-PTK-Current”, SNonce || ANonce ||AP MLD MAC address || SPA) Note that PTK is used in this example. current Not bound to SMD MAC address.

[0078] Arrow 625 indicates that STA 105 instructs the serving AP 110A to initiate roaming preparation. In response, the serving AP retrieves information from the PTK. current Generate a PTK for one or more target APs. For example, the serving AP (or WLC) uses a PTK. current Generate a PTK (called PTK) for each target AP. target ), use the following equation: PTK target (For target AP ML) = KDF- Hash - Length (PTK current “ST-PTK-Target”, Target AP MLD MAC address (SPA) It is worth noting that this PTK targetThe calculation does not require another random number exchange.

[0079] One or more PTKs for one or more target APs are generated by the currently serving AP 110A and distributed / installed on the target AP 110B as part of the roaming process, as indicated by arrow 635. Instead of pushing the PTK to the target AP 110B as described above, the PTK can be stored in a key repository (not shown) and then pulled from the key repository when the target AP 110B is notified that STA105 is roaming to it.

[0080] Arrow 640 shows STA 105 informing serving AP 110A which target AP 110B it wants to roam to. In response, serving AP 110A can transfer the roaming context to the selected target AP 110B, as shown by arrow 645. Arrow 650 shows serving AP 110A instructing STA 105 that the context transfer is complete. At this point (or before), STA 105 can locally generate a PTK (i.e., a PTK for the selected target AP 110B). target ).

[0081] PTK target The keys have now been generated and installed on both the STA 105 and the target AP 110B, enabling secure uplink (UL) and downlink (DL) switching as shown by arrow 655.

[0082] Figure 6 Key level 660 is also shown. A PTK is generated using PMK for the AP initially associated with STA 105 in SMD 100. current The first AP can then use PTK. current Pre-calculate different PTKs for the target AP in SMD target Key. That is, AP MLD A has a different PTK than AP MLD B. target And so on. In this way, the PTK of the target AP is derived from the PTK of the initial AP instead of the PMK.

[0083] exist Figures 3 to 6 In any of the embodiments shown, after roaming has been performed and any buffered DL data has been delivered / retrieved (or timed out) from the serving AP 110A, an RSNA key update operation can be initiated to refresh the PTK at the new target AP 110B (exchanging SNonce and ANonce between the STA and the AP). The PTK key update can be initiated by the new target AP 110B or by STA 105 using any suitable PTK key update mechanism.

[0084] Furthermore, in any of the key generation algorithms described above, the Label string can be changed to any other suitable string used for key generation.

[0085] Note that none of the above embodiments require additional negotiation between STA 105 and AP for key regeneration as part of the roaming execution phase, thereby avoiding any key negotiation delays in seamless roaming and providing faster roaming execution.

[0086] Figure 7 An example computing device configured to perform various aspects of this disclosure is depicted according to one embodiment. Although depicted as a physical device, in the embodiment, computing device 700 may be implemented using one or more virtual devices and / or across multiple devices (e.g., in a cloud environment). In one embodiment, computing device 700 corresponds to a network device (e.g., a computing system), such as AP 110 or STA 105.

[0087] As shown, computing device 700 includes CPU 705 (one or more processors), memory 710 (or multiple memories), storage device 715, network interface 725, and one or more input / output (I / O) interfaces 720. In the illustrated embodiment, CPU 705 retrieves and executes programming instructions stored in memory 710, and stores and retrieves application data residing in storage device 715. CPU 705 typically represents a single CPU and / or GPU, multiple CPUs and / or GPUs, a single CPU and / or GPU with multiple processing cores, etc. Memory 710 is typically included to represent random access memory. Storage device 715 can be any combination of disk drives, flash-based storage devices, etc., and may include fixed and / or removable storage devices such as fixed disk drives, removable memory cards, caches, optical storage devices, network-attached storage devices (NAS), or storage area networks (SANs).

[0088] In some embodiments, I / O devices 735 (such as a keyboard, monitor, etc.) are connected via one or more I / O interfaces 720. Furthermore, computing device 700 can be communicatively coupled to one or more other devices and components (e.g., via a network that may include the Internet, one or more local area networks, etc.) via network interface 725. As shown, CPU 705, memory 710, storage device 715, one or more network interfaces 725, and one or more I / O interfaces 720 are communicatively coupled via one or more buses 730.

[0089] Memory 710 may include for use as described above in Figures 1 to 6The software program or application that generates PMK and PTK discussed herein. Although shown as residing in memory 710, in embodiments, the operations discussed above (and others not shown) can be implemented using hardware, software, or a combination of hardware and software.

[0090] Various embodiments have been referenced in this disclosure. However, the scope of this disclosure is not limited to the embodiments specifically described. Rather, any combination of features and elements described, whether or not relating to different embodiments, is contemplated for implementing and practicing the embodiments contemplated. Furthermore, when elements of an embodiment are described in the form of "at least one of A and B" or "at least one of A or B," it should be understood that embodiments including only element A, only element B, and embodiments including both elements A and B are all considered. Moreover, while some embodiments disclosed herein may achieve advantages relative to other possible solutions or prior art, whether a given embodiment achieves a particular advantage does not limit the scope of this disclosure. Therefore, aspects, features, embodiments, and advantages disclosed herein are merely illustrative and should not be considered elements or limitations of the appended claims unless expressly recited in one or more claims. Similarly, references to "the invention" should not be construed as a generalization of any inventive subject matter disclosed herein and should not be considered elements or limitations of the appended claims unless expressly recited in one or more claims.

[0091] As those skilled in the art will understand, the embodiments disclosed herein can be implemented as a system, method, or computer program product. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, which may be collectively referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can take the form of a computer program product embodied in one or more computer-readable media having computer-readable program code embodied thereon.

[0092] Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, RF, or any suitable combination thereof.

[0093] Computer program code for performing the operations of embodiments of this disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet through an Internet service provider). As an example, a computer-readable medium carrying instructions that, when executed by one or more processors, cause any of the methods described herein to be performed.

[0094] This document describes aspects of the present disclosure with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments set forth in this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0095] These computer program instructions may also be stored in a computer-readable medium that can direct a computer, other programmable data processing apparatus or other device to operate in a particular manner, such that the instructions stored in the computer-readable medium produce an article of writing which implements the functions / actions specified in one or more blocks of a flowchart and / or block diagram.

[0096] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus or other equipment to cause a series of operational steps to be performed on the computer, other programmable apparatus or other equipment, thereby producing a computer-implemented process, such that the instructions, which execute on the computer, other programmable data processing apparatus or other equipment, provide a process for implementing the function / action specified in one or more blocks of a flowchart and / or block diagram.

[0097] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments. In this regard, each block in a flowchart or block diagram may represent a module, segment, or code portion comprising one or more executable instructions for implementing a specified logical function(s). It should also be noted that in some alternative implementations, the functions described in the blocks may not occur in the order shown in the drawings. For example, depending on the functions involved, two blocks shown consecutively may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and computer instructions that performs the specified functions or actions.

[0098] In view of the foregoing, the scope of this disclosure is defined by the appended claims.

Claims

1. A network device, comprising: One or more memory units; as well as One or more processors communicatively coupled to the one or more memories, wherein the one or more processors are configured to perform operations individually or jointly, the operations including after the wireless device is associated with a first AP in a Seamless Mobile Domain (SMD): Generate a pairwise temporary key (PTK) for exchanging encrypted content between the wireless device and the second AP in the SMD; as well as Before the wireless device communicates with the second AP, the PTK is made available to the second AP.

2. The network device according to claim 1, wherein the encrypted content includes at least one of encrypted data and encrypted management frames.

3. The network device according to claim 1 or 2, wherein the wireless device uses the same PTK when exchanging encrypted content with at least one other AP among the first AP, the second AP, and the SMD.

4. The network device according to claim 3, further comprising: Before generating the PTK, a pairwise master key (PMK) corresponding to the wireless device is generated, wherein the first AP and the second AP use the same PMK to generate the PTK for the wireless device; as well as Make the PMK and PTK available to multiple APs in the SMD.

5. The network device of claim 4, further comprising, after making the PTK available to the second AP: At the first AP, a roaming request to roam to the second AP is received from the wireless device; and The context associated with the wireless device is transferred from the first AP to the second AP, wherein the context includes the PTK and PMK to be used by the second AP for the wireless device.

6. The network device according to claim 4 or 5, wherein the operation further comprises: Generate root PTK; Generate different PTKs for multiple APs in the SMD, including the first AP and the second AP, wherein the PTK is one of the different PTKs; as well as Before the wireless device communicates with the plurality of APs, at least one of the following is performed: The different PTKs are stored in a keystore accessible by the multiple APs; or The different PTKs are transmitted to the multiple APs.

7. The network device according to any of the preceding claims, wherein the operation further comprises: Generate a first PTK to be used by the first AP to communicate with the wireless device; Based on the first PTK, different PTKs are generated for multiple APs in the SMD that include the second AP; Before the wireless device communicates with the plurality of APs, at least one of the following is performed: The different PTKs are stored in a keystore accessible by the multiple APs; or The different PTKs are transmitted to the multiple APs.

8. The network device according to claim 7, wherein, The different PTKs used for the plurality of APs including the second AP in the SMD are generated at the first AP, without the need for separate random number exchange between the wireless device and the second AP or the plurality of APs in the SMD.

9. The network device according to any of the preceding claims, wherein the PTK is generated using the identifier of the SMD, wherein the identifier of the SMD can be one of an SMD MAC address or an SMD ID.

10. The network device of claim 9, wherein the identifier of the SMD is the SMD MAC address, wherein the SMD MAC address is one of the following: different from the MAC address of each AP in the SMD, or the same as the MAC address of one of the APs in the SMD.

11. The network device of claim 9, wherein the identifier of the SMD is the SMD ID, and the SMD ID is shorter than the MAC address.

12. A method comprising: Associate the wireless device with the first access point (AP) in the Seamless Mobile Domain (SMD). Generate a pairwise temporary key (PTK) for exchanging encrypted content between the wireless device and the second AP in the SMD; as well as Before the wireless device communicates with the second AP, the PTK is made available to the second AP.

13. The method of claim 12, wherein the PTK is generated at the first AP without requiring a separate random number exchange between the wireless device and the second AP.

14. The method of claim 12 or 13, wherein the wireless device uses the same PTK when exchanging encrypted content with at least one other AP among the first AP, the second AP, and the SMD. The method further includes: Before generating the PTK, a PMK corresponding to the wireless device is generated, wherein the first AP and the second AP use the same PMK to generate the PTK for communicating with the wireless device; as well as Make the PMK and PTK available to multiple APs in the SMD.

15. The method of claim 14, further comprising, after making the PTK available to the second AP: At the first AP, a roaming request to roam to the second AP is received from the wireless device; and The context associated with the wireless device is transferred from the first AP to the second AP, wherein the context includes the PTK and PMK to be used by the second AP for the wireless device.

16. The method according to claim 14 or 15, further comprising: Generate root PTK; Generate different PTKs for multiple APs in the SMD, including the first AP and the second AP, wherein the PTK is one of the different PTKs; as well as Before the wireless device communicates with the plurality of APs, at least one of the following is performed: The different PTKs are stored in a keystore accessible by the multiple APs; or The different PTKs are transmitted to the multiple APs.

17. A network device, comprising: One or more memory units; as well as One or more processors communicatively coupled to the one or more memories, wherein the one or more processors are configured to perform operations individually or jointly, the operations including after a wireless device is associated with an access point (AP) in a Seamless Mobility Domain (SMD), or when a wireless device is associated with an access point (AP) in a Seamless Mobility Domain (SMD): Generate a pairwise master key (PMK) for the wireless device; and Based on the PMK, a pairwise temporary key (PTK) is generated for exchanging encrypted content between the wireless device and the AP. The PMK or PTK is generated using the identifier of the SMD, wherein the identifier of the SMD can be either an SMD MAC address or an SMD ID.

18. The network device according to claim 17, further comprising: Generate root PMK; Use the root PMK to generate different PMKs for multiple APs in the SMD; as well as Before the wireless device communicates with the plurality of APs, at least one of the following is performed: The different PMKs are stored in a keystore accessible by the multiple APs; or Transmit the different PMKs to the multiple APs; and The different PMKs are configured to be used by the plurality of APs to generate different PTKs for encrypted communication with the wireless device.

19. The network device of claim 17 or 18, wherein the identifier of the SMD is the SMD MAC address, wherein the SMD MAC address is one of the following: different from the MAC address of each AP in the SMD, or the same as the MAC address of one of the APs in the SMD.

20. The network device according to any one of claims 17 to 19, wherein the identifier of the SMD is the SMDID, and the SMDID is shorter than the MAC address.

21. A method comprising, after a wireless device is associated with an access point (AP) in a Seamless Mobility Domain (SMD), or when a wireless device is associated with an access point (AP) in a Seamless Mobility Domain (SMD): Generate a pairwise master key (PMK) for the wireless device; and Based on the PMK, a pairwise temporary key (PTK) is generated for exchanging encrypted content between the wireless device and the AP. The PMK or PTK is generated using the identifier of the SMD, wherein the identifier of the SMD can be either an SMD MAC address or an SMD ID.

22. A computer-readable medium carrying instructions that, when executed by one or more processors, cause the method of any one of claims 12 to 16 and / or 20 to be performed.