Communication method and communication apparatus
The proposed communication method for ambient power-enabled Wi-Fi devices reduces overhead and complexity by establishing a pairing relationship with a temporary identification, enabling efficient data exchange without repeated initial access procedures.
Patent Information
- Application Number
- PCT/CN2025/094031
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing communication methods for ambient power-enabled Wi-Fi devices involve high overhead and complexity due to the need for frequent initial access procedures such as authentication and association before each communication session.
A communication method that establishes a pairing relationship between an ambient power access point (AMP AP) and a non-AP AMP station (STA) using a temporary identification (PID), allowing subsequent communications without initial access, and supports both secure and open pairing relationships through various AMP frames.
Reduces overhead and communication complexity by eliminating the need for repeated initial access procedures, facilitating efficient data exchange.
Smart Images

Figure CN2025094031_12112026_PF_FP_ABST
Abstract
Description
COMMUNICATION METHOD AND COMMUNICATION APPARATUSTECHNICAL FIELD
[0001] The present disclosure relates generally to the field of communication technologies, and more particularly to communication methods and apparatuses.BACKGROUND
[0002] Ambient power (AMP) or 802.11 bp is a task group (TG) within the Institute of Electrical and Electronics Engineer (IEEE) 802.11 working group that is studying support of AMP communication in IEEE 802.11 network. A goal is to address needs of an ambient power-enabled Wi-Fi device (like a non-access point (AP) AMP station (STA) ) . The TG is exploring power harvesting technologies that may significantly increase the battery lifespan of the non-AP AMP STAs, such as radio frequency (RF) power harvesting (or backscattering) , power harvesting using light, motion etc.
[0003] In the IEEE 802.11-24 / 871, a transaction based communication for AMP is proposed in which AMP devices do not perform the typical 802.11 procedure to join a network (authentication, association, 4-way handshake etc. ) , and the AMP devices may not need to maintain association. Instead it is proposed that prior to each communication session, two communicating AMP devices may perform procedure that is required for the communication session, such as initial access for an identification or capability exchanges, and if security is enabled, security key generation procedure, etc. There may be room for further improvement in overhead and communication complexity.
[0004] This background information is provided to reveal information believed by the applicant to be of possible relevance to the present disclosure. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art against the present disclosure.SUMMARY
[0005] Implementations of the present disclosure provide a communication method and a communication apparatus, which may facilitate decreasing overhead and communication complexity.
[0006] In a first aspect, a communication method is described. The method may be applied at an ambient power (AMP) access point (AP) . The communication method includes: generating a first AMP frame indicating a pairing relationship between the AMP AP and a non-AP AMP station (STA) , wherein the first AMP frame includes a first field indicating a temporary identification assigned by the AMP AP to the non-AP AMP STA, and a second field indicating an identification of the AMP AP; and transmitting the first AMP frame to the non-AP AMP STA.
[0007] The temporary identification assigned by the AMP AP to the non-AP AMP STA may be called a paired identification (PID) (e.g., a 16-bits identification) for subsequent communication. The identification of the AMP AP may refer to a permanent identification of the AMP AP, such as a MAC address or other identifications. For ease of description, the identification of the AMP AP may be called an AP address or a paired AP address, and the AMP AP having the pairing relationship with the non-AP AMP STA may be called a paired AMP AP or a paired AP. After the pairing relationship establishment, according to the PID and paired AP address in the first AMP frame, the non-AP AMP AP may perform subsequent communication (e.g., data exchange) with the AMP AP. The subsequent communication may also be called paired communication.
[0008] In this way, the AMP AP and the non-AP AMP STA may not perform initial access before each paired communication (such as data exchange) , which may facilitate decreasing overhead and communication complexity.
[0009] In some embodiments, the method further includes: receiving, from the non-AP AMP STA, a second AMP frame for requesting establishment of the pairing relationship.
[0010] The second AMP frame may refer to an AMP pairing request frame or an AMP authentication request frame. The second AMP frame may also carry capabilities of the non-AP AMP STA. Upon receiving the second AMP frame, the AMP AP may decide to accept the request, which may facilitate decreasing complexity of the establishment of the pairing relationship, and provide a flexible option.
[0011] In some embodiments, the method further includes: transmitting, to the non-AP AMP STA, a second AMP frame for requesting establishment of the pairing relationship; and receiving, from the non-AP AMP STA, a third AMP frame indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.
[0012] The third AMP frame may refer to an AMP pairing response frame or an AMP authentication response frame. The establishment of the pairing relationship may also be initiated by the non-AP AMP STA, which may also provide a flexible option.
[0013] In some embodiments, the third AMP frame includes at least one of: a third field indicating an identification of the non-AP AMP STA, a fourth field indicating a presence of the third field, or a fifth field indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.
[0014] For example, upon receiving the third AMP frame, the AMP AP may obtain the identification of the non-AP AMP STA that accepts the request, and the AMP AP may assign the PID for the non-AP AMP STA.
[0015] In some embodiments, the second AMP frame includes at least one of: a sixth field indicating an identification of the non-AP AMP STA, or a seventh field indicating a presence of the sixth field.
[0016] For example, the second AMP frame may be an AMP pairing request frame. In a case where the non-AP AMP STA initiates the establishment of the pairing relationship. The AMP AP may obtain an identification (e.g., a 16-bits random number (RN16) , an electronic product code (EPC) , or a MAC address) of the non-AP AMP STA. And the AMP AP may decide whether to accept the request.
[0017] In some embodiments, after transmitting the first AMP frame to the non-AP AMP STA, the method further includes: transmitting or receiving a fourth AMP frame including the temporary identification for communication, where the fourth AMP frame is an unprotected AMP frame.
[0018] For example, the pairing relationship may be an open pairing relationship. The temporary identification may refer to the PID. After the establishment of the open pairing relationship, the AMP AP and the non-AP AMP STA may perform open paired communication such as data exchange. And the fourth AMP frame may be an AMP request frame or an AMP request frame used in the open paired communication.
[0019] In some embodiments, the fourth AMP frame includes a cyclic redundancy check (CRC) field, and the CRC field is determined based on the identification of the AMP AP.
[0020] For example, the fourth AMP frame may be an AMP request frame transmitted by the non-AP AMP STA. The AMP request frame may include a CRC field and a Transmitter ID field indicating an identification of the AMP AP.In a case where the Transmitter ID field in the AMP request frame is omitted. The non-AP AMP STA may utilize the CRC field to indicate the identification of the AMP AP indirectly. For example, upon receiving the AMP request frame, the non-AP AMP STA may check whether the AMP AP is a paired AMP AP through the CRC field in the AMP request frame.
[0021] In some embodiments, the second AMP frame is used for requesting an authentication of the non-AP AMP STA, and the third AMP frame indicates that the non-AP AMP STA accepts the requesting.
[0022] For example, the second AMP frame may be an AMP authentication request frame, which may be utilized to initiate establishment of a secure pairing relationship. And the third AMP frame may be an AMP authentication response frame.
[0023] In some embodiments, the method further includes: performing the authentication of the non-AP AMP STA, where the transmitting the first AMP frame to the non-AP AMP STA, includes: transmitting the first AMP frame to the non-AP AMP STA in a case where the authentication succeeds.
[0024] In order to establish a secure pairing relationship, the AMP AP may perform the authentication of the non-AP AMP STA. The establishment of the secure pairing relationship may also be regarded as establishment of secure communication.
[0025] In some embodiments, the second AMP frame includes at least one of: an eighth field indicating the identification of the AMP AP, or a ninth field indicating a presence of the eighth field.
[0026] For example, the second AMP frame may be an AMP authentication request frame. In a case where the AMP AP initiates the establishment of the secure pairing relationship. Upon receiving the second AMP frame, the non-AP AMP STA may obtain the identification (such as a MAC address) of the AMP AP. The non-AP AMP STA may decide whether to accept the request or not, based on the AMP AP’ conditions or its own conditions, for example, according to its current power level.
[0027] In some embodiments, after transmitting the first AMP frame to the non-AP AMP STA, the method further includes: transmitting or receiving a fifth AMP frame including the temporary identification for communication, where the fifth AMP frame is a protected AMP frame.
[0028] For example, the pairing relationship may be a secure pairing relationship. The temporary identification may refer to the PID. After the establishment of the secure pairing relationship, the AMP AP and the non-AP AMP STA may perform secure paired communication such as data exchange. And the fifth AMP frame may be an AMP request frame or an AMP request frame used in the secure paired communication.
[0029] In some embodiments, the fifth AMP frame is protected by additional authentication data (AAD) including the identification of the AMP AP.
[0030] The AAD may commonly be used in a counter mode with cipher block chaining message authentication code protocol (CCMP) encapsulation and decapsulation procedure. The CCMP is an encryption and integrity protection protocol used for ensuring confidentiality, integrity, and authenticity of frames. Similar to its application in the CCMP, the AAD may also be used in the protected AMP frame. For example, the AAD used to secure a fifth AMP frame transmitted by the AMP AP may include the identification of the AMP AP. Upon receiving the fifth AMP frame, the non-AP AMP STA may check whether the identification included in the AAD that is used to secure the AMP frame corresponds to a paired AMP AP.
[0031] In some embodiments, the fifth AMP frame includes a message integrity check (MIC) , and the MIC is determined based on the identification of the AMP AP.
[0032] It is understood that in secure paired communication, frame exchange may also require authentication to ensure security, e.g., based on a security key. For example, in secure paired communication, the protected AMP frame may be used for data exchange. The MIC may be determined based on a paired AP address and a PID for authentication.
[0033] In some embodiments, the method further includes: transmitting or receiving a sixth AMP frame indicating termination of the pairing relationship.
[0034] Both of the AMP AP and the non-AP AMP STA may transmit the sixth frame to terminate the pairing relationship. For example, the non-AMP AMP STA may not have enough energy to keep paired communication, and then the non-AP AMP STA may transmit the sixth AMP frame to terminate the pairing relationship.
[0035] In some embodiments, the sixth AMP frame includes a tenth field indicating a reason for the termination of the pairing relationship.
[0036] In a second aspect, a communication method is described. The method may be applied at a non-AP AMP STA. The communication method includes: receiving, from an AMP AP, a first AMP frame indicating a pairing relationship between the AMP AP and the non-AP AMP STA, where the first AMP frame includes a first field indicating a temporary identification assigned by the AMP AP to the non-AP AMP STA, and a second field indicating an identification of the AMP AP.
[0037] In some embodiments, the method further includes: transmitting, to the AMP AP, a second AMP frame for requesting establishment of the pairing relationship.
[0038] In some embodiments, the method further includes: receiving, from the AMP AP, a second AMP frame for requesting establishment of the pairing relationship; and transmitting, to the AMP AP, a third AMP frame indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.
[0039] In some embodiments, the third AMP frame includes at least one of: a third field indicating an identification of the non-AP AMP STA, a fourth field indicating a presence of the third field, or a fifth field indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.
[0040] In some embodiments, the second AMP frame includes at least one of: a sixth field indicating an identification of the non-AP AMP STA, or a seventh field indicating a presence of the sixth field.
[0041] In some embodiments, after receiving the first AMP frame from the AMP AP, the method further includes: receiving or transmitting a fourth AMP frame including the temporary identification for communication, where the fourth AMP frame is an unprotected AMP frame.
[0042] In some embodiments, the fourth AMP frame includes a cyclic redundancy check (CRC) field, and the CRC field is determined based on the identification of the AMP AP.
[0043] In some embodiments, the second AMP frame is used for requesting an authentication of the non-AP AMP STA, and the third AMP frame indicates that the non-AP AMP STA accepts the requesting.
[0044] In some embodiments, the receiving the first AMP frame from the AMP AP, includes: receiving the first AMP frame from the AMP AP in a case where the authentication succeeds.
[0045] In some embodiments, the second AMP frame includes at least one of: an eighth field indicating the identification of the AMP AP, or a ninth field indicating a presence of the eighth field.
[0046] In some embodiments, after receiving the first AMP frame from the AMP AP, the method further includes: receiving or transmitting a fifth AMP frame including the temporary identification for communication, where the fifth AMP frame is a protected AMP frame.
[0047] In some embodiments, the fifth AMP frame is protected by additional authentication data (AAD) including the identification of the AMP AP.
[0048] In some embodiments, the fifth AMP frame includes a message integrity check (MIC) , and the MIC is determined based on the identification of the AMP AP.
[0049] In some embodiments, the method further includes: receiving or transmitting a sixth AMP frame indicating a termination of the pairing relationship.
[0050] In some embodiments, the sixth AMP frame includes a tenth field indicating a reason for the termination of the pairing relationship.
[0051] In a third aspect, an apparatus is described. The apparatus has a function of implementing the first aspect or the second aspect. For example, the apparatus includes a corresponding module, unit, or means for performing operations in the first aspect or the second aspect. The module, unit, or means may be specifically implemented by using software, may be implemented by using hardware, or may be implemented by using software in combination with hardware.
[0052] In a fourth aspect, an apparatus is described, which includes: one or more processors; and a memory storing instructions which, when executed by the one or more processors, cause the apparatus to perform any implementation of the first aspect or the second aspect.
[0053] In a fifth aspect, a computer-readable storage medium is described, which has instructions stored thereon which, when executed by one or more processors, cause the one or more processors to perform the method in any possible implementation of the first aspect or the second aspect.
[0054] In a sixth aspect, a computer program product is described, which stores instructions which, when executed, cause an apparatus to perform the method in any possible implementation of the first aspect or the second aspect.
[0055] This disclosure encompasses various embodiments, including not only method embodiments, but also other embodiments such as apparatus embodiments and embodiments related to non-transitory computer readable storage media. Embodiments may incorporate, individually or in combinations, the features disclosed herein.BRIEF DESCRIPTION OF THE DRAWINGS
[0056] For a better understanding of the various described embodiments, reference should be made to the Detailed Description below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
[0057] FIG. 1 illustrates a schematic diagram of an example communication system according to one or more implementations of the present disclosure;
[0058] FIG. 2 illustrates a schematic diagram of another example communication system according to one or more implementations of the present disclosure;
[0059] FIG. 3 illustrates a transaction based communication between an ambient power (AMP) access point (AP) and a non-AP AMP station (STA) ;
[0060] FIG. 4 illustrates a transaction based communication between AMP APs and non-AP AMP STAs;
[0061] FIG. 5 illustrates a flowchart of a communication method according to some embodiments of the present disclosure;
[0062] FIG. 6 illustrates a schematic diagram of a possible communication process according to some embodiments of the present disclosure;
[0063] FIG. 7 illustrates a general format of an example AMP frame according to some embodiments of the present disclosure;
[0064] FIG. 8 illustrates a general format of an example frame body of an AMP pairing frame according to some embodiments of the present disclosure;
[0065] FIG. 9 illustrates another communication method according to some embodiments of the present disclosure;
[0066] FIG. 10 illustrates a general format of a frame body of an example AMP pairing request frame according to some embodiments of the present disclosure;
[0067] FIG. 11 illustrates a general format of a frame body of an example AMP pairing response frame according to some embodiments of the present disclosure;
[0068] FIG. 12 illustrates a general format of a frame body of an example AMP pairing confirm frame according to some embodiments of the present disclosure;
[0069] FIG. 13 illustrates a general format of an example unprotected AMP frame according to some embodiments of the present disclosure;
[0070] FIG. 14 illustrates a block diagram of an example verification using a CRC field, according to some embodiments of the present disclosure;
[0071] FIG. 15 illustrates a general format of a frame body of an example AMP unpair frame according to some embodiments of the present disclosure;
[0072] FIG. 16 illustrates yet another communication method according to some embodiments of the present disclosure;
[0073] FIG. 17 illustrates a general format of a frame body of an example AMP authentication request frame according to some embodiments of the present disclosure;
[0074] FIG. 18 illustrates a general format of a frame body of an example AMP authentication response frame according to some embodiments of the present disclosure;
[0075] FIG. 19 illustrates a general format of a frame body of an example AMP authentication confirm frame according to some embodiments of the present disclosure;
[0076] FIG. 20 illustrates a block diagram of an example of generating a pairwise master key (PMK) and a pairwise transient key (PTK) , according to some embodiments of the present disclosure;
[0077] FIG. 21 illustrates a general format of an example protected AMP frame according to some embodiments of the present disclosure;
[0078] FIG. 22 illustrates a general format of an example AAD according to some embodiments of the present disclosure;
[0079] FIG. 23 illustrates a general format of an example Nonce according to some embodiments of the present disclosure;
[0080] FIG. 24 illustrates a general format of a frame body of an example AMP deauthentication frame according to some embodiments of the present disclosure;
[0081] FIG. 25 illustrates a schematic diagram of pairing states transition of a non-AP AMP STA according to some embodiments;
[0082] FIG. 26 illustrates a schematic diagram of a communication apparatus in accordance with some embodiments; and
[0083] FIG. 27 illustrates a schematic diagram of a communication apparatus in accordance with some embodiments.DETAILED DESCRIPTION
[0084] Numerous details are described herein to provide a thorough understanding of the example embodiments illustrated in the accompanying drawings. However, some embodiments may be practiced without many of the specific details, and the scope of the claims is only limited by those features and aspects specifically recited in the claims. Furthermore, well-known processes, components, and materials have not necessarily been described in exhaustive detail so as to avoid obscuring pertinent aspects of the embodiments described herein.
[0085] The technical solutions according to the embodiments of the present disclosure may be applied to wireless local area network (WLAN) systems, such as Wi-Fi systems. The technical solutions according to the embodiments of the present disclosure may be applied to a series of Institute of Electrical and Electronics Engineers (IEEE) protocols, such as IEEE 802.11 protocols (e.g., the 802.11 a / b / g protocol, the 802.11 n protocol, the 802.11ac protocol, the 802.11 ax protocol, the 802.11 be / Wi-Fi 7 / EHT (extremely high throughput) protocol, the IEEE 802.11 bn / UHR (ultra high reliability) / Wi-Fi 8 protocol, the IEEE 802.11 bf / sensing protocol) , IEEE 802.15 / UWB (ultra-wideband) protocol, or IEEE Integrated mmWave / IMMW protocol. The technical solutions according to the embodiments of the present disclosure may be applied to a spark link / near link protocol, or a future protocol, and the protocols are not limited thereto.
[0086] A Wi-Fi system may include one or more basic service sets (BSSs) , and a BSS may include an access point (AP) and one or more stations (STAs) . For example, the AP is a provider of Wi-Fi network, which allows access of a STA, and provides data access for the STA. The STA may be a device that accesses the Wi-Fi network. The STA may also be referred to as a user unit, access terminal, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, user device, or user equipment (UE) . An electronic device that supports a Wi-Fi function may be used as the STA. The electronic device used as the STA may be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) , handheld device with wireless local area network (WLAN) communication function, wearable device, computing device, or other processing device connected to a wireless modem.
[0087] The technical solutions according to the embodiments of the present disclosure may also be applied to the wireless personal area network (WPAN) based on the millimeter wave (MMW) and ultra-wideband (UWB) technologies, e.g., the IEEE 802.15.4z protocol, 802.15.4ab protocol, etc. The technical solutions according to the embodiments of the present disclosure may also be applied to communication systems such as Internet of Things (IoT) systems, vehicle to everything (V2X, X may represent anything) systems, device to device (D2D) systems, narrowband Internet of Things (NB-IoT) systems, long term evolution (LTE) systems, the fifth generation (5G) communication system, or other communication systems in future. For example, the V2X system may include vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication, vehicle to network (V2N) communication, etc.
[0088] In order to facilitate the understanding of the solutions of the present disclosure, some terms mentioned herein are first introduced.
[0089] 1. Ambient Power (AMP)
[0090] AMP is a task group (802.11 bp) within the IEEE 802.11 working group that is studying the support of ambient power communication in IEEE 802.11 network. The goal is to address the need of ambient power-enabled Wi-Fi IoT devices (e.g., AMP IoT STAs) . The TG is exploring power harvesting technologies that can significantly increase the battery lifespan of the AMP IoT STAs, such as radio frequency (RF) power harvesting (or backscattering) , power harvesting using light, motion, etc.
[0091] 2. AMP channel access
[0092] AMP channel access is an AMP-based communication or energy access that may enable access to and management of communication channels by combining energy sources (e.g., radio frequencies, light, heat, etc. ) that exist in an environment. The core idea of the AMP channel access is to utilize existing energy sources in the environment to support an operation of a communication device without additional batteries or power supplies.
[0093] 3. AMP AP STA
[0094] An AMP AP STA is an AP that can transmit and receive AMP physical protocol data unit (PPDU) , and can communicate with AMP non-AP STAs. An AMP AP STA may be abbreviated as an AMP AP or AP.
[0095] 4. AMP non-AP STA
[0096] An AMP non-AP STA is a non-AP STA that can transmit and receive AMP PPDU, and can communicate with an AMP AP or another AMP non-AP STA. Based on its capabilities the AMP non-AP STA may be classified as: an AMP enabled non-AP STA, an active Tx non-AP AMP STA and a backscatter non-AP AMP STA. The AMP enabled non-AP STA has capability to support legacy 802.11 protocols (e.g., 802.11 b / g / n) and support its own energy source, e.g., battery. The active Tx non-AP AMP STA may not support legacy 802.11 protocols and may support low power transceiver operations and also possess some sort of small energy source, e.g., large capacitor, or ambient power source etc. The active Tx non-AP AMP STA may be capable of active transmitting without any backscattering excitation signal. The backscatter non-AP AMP STA may refer to a non-AP AMP STA that backscatters its uplink (UL) data, on an excitation waveform provided by an AMP AP or an AMP energizer.
[0097] 5. AMP Reader
[0098] An AMP reader is an AMP AP STA or AMP non-AP STA that is able to receive and decode a backscattered signal from a backscatter non-AP AMP STA or an uplink signal from an active Tx non-AP AMP STA, and that is able to transmit a downlink control signal and a carrier signal to the backscatter non-AP AMP STA or a downlink control signal to the active Tx non-AP AMP STA. An AMP reader may be an AMP AP, an AMP relay, an AMP energizer, a smartphone with AMP capabilities, etc. An AMP reader may be abbreviated as a reader.
[0099] 6. AMP Energizer
[0100] An AMP energizer is an AMP non-AP STA that provides energy using wireless power transfer (WPT) for another AMP non-AP STA or provides excitation signal to allow another AMP non-AP STA to charge and / or backscatter its signal.
[0101] FIG. 1 illustrates a schematic diagram of an example communication system according to one or more implementations of the present disclosure.
[0102] As shown in FIG. 1, the communication system 100 includes an AMP AP 101, non-AP AMP STA 102, non-AP AMP STA 103 and non-AP AMP STA 104. For example, the AMP AP 101 acts as an AMP reader that interacts with the three non-AP AMP STAs that are in tag form. Although FIG. 1 illustrates a possible deployment of the communication system, it is not meant to be restrictive, and a number of devices in the communication system 100 is not limited thereto.
[0103] In a possible implementation, all the non-AP AMP STAs 102, 103 and 104 are active Tx non-AP AMP STA and may communicate with the AMP reader (i.e., the AMP AP 101) without requiring any excitation signal. In this case, the communication system 100 further includes an AMP energizer 105 employed to transmit wireless power transfer (WPT) to the non-AP AMP STAs 102, 103 and 104 to provide power for active transmissions.
[0104] In another possible implementation, the non-AP AMP STAs 102, 103 and 104 are backscatter non-AP AMP STAs, in which case they require excitation signal from the AMP AP 101 to backscatter their signal. Because the non-AP AMP STAs 102, 103 and 104 may not be able to transmit or receive the legacy 802.11 frames (also known as protocol version (PV) 0 frames) , they may not be able to or required to associate with the AMP AP 101.
[0105] It is noted that in the communication system 100, dashed lines represent communication over the mainstream 802.11 link (e.g., high throughput (HT) , very high throughput (VHT) , high efficiency (HE) , extremely high throughput (EHT) , etc. ) , while dotted lines represent communication over the AMP link, including the transmission of the WPT waveform.
[0106] FIG. 1 illustrates an example of a communication system with one AP, and in other possible scenarios, there may also be multiple AMP APs in a communication system. FIG. 2 illustrates a schematic diagram of another example communication system according to one or more implementations of the present disclosure.
[0107] As shown in FIG. 2, the communication system 200 includes AMP APs 201, 202 and 203, non-AP AMP STAs 204, 205 and 206, an AMP energizer 207, clouds 208 and 209, a terminal 210, a server 211, and a switch device 212. Although FIG. 2 illustrates a possible deployment of the communication system 200, it is not meant to be restrictive, and a number of devices in the communication system 200 is not limited thereto.
[0108] The AMP AP 203 may be a mobile AMP AP, and the three AMP APs 201, 202 and 203 act as AMP readers that interact with three tag form non-AP AMP STAs: non-AP AMP STAs 204, 205 and 206. A description of same parts may be referred to the communication system 100, and will not be repeated here.
[0109] The three AMP APs 201, 202 and 203 may be participants in a multi-AP coordination framework and may have means of communicating with each other to coordinate transmissions. The three AMP APs 201, 202 and 203 may interact with a large number of non-AP AMP STAs, though in the communication system 200, three non-AP AMP STAs 204, 205 and 206 are illustrated.
[0110] Due to a large number of non-AP AMP STAs, a management / control of the non-AP AMP STAs may be done at a central server (e.g., the server 211) instead of an AMP AP. For example, the terminal 210 may be a computer that is used for connecting the server 211 and the AMP APs 201, 202 and 203 via the cloud 208. The switch device 212 may be used for managing a flow of data and forwarding the data. Although not shown in FIG. 2, the AMP AP 203 may also be connected to other servers via the cloud 208. It is also possible that in some deployments, one of the AMP APs 201, 202 and 203 acts as a server. In a large deployment scenario such as the communication system 200, a non-AP AMP STA may be accessible to multiple AMP APs.
[0111] It is noted that in the communication system 200, dashed lines represent communication over the 802.11 link (e.g., HT, VHT, HE, extremely EHT, etc. ) , dotted lines represent communication over the AMP link, including the transmission of the WPT waveform, and solid lines represent communication over the wide area network (WAN) link, such as over ethernet or fiber network.
[0112] Next, a transaction based communication between an AMP AP and a non-AP AMP STA, for example in the communication system 100 shown in FIG. 1, is illustrated in FIG. 3. For example, the AMP AP in FIG. 3 may be the AMP AP 101 in FIG. 1, and the non-AP AMP STA may be any one of the non-AP AMP STAs 102, 103, and 104 in FIG. 1. The transaction based communication refers to communication between devices without any pre-negotiation procedure (such as authentication or association commonly performed in 802.11 networks) . As shown in FIG. 3, the communication method 300 includes steps 301 to 310.
[0113] In step 301, an AMP AP transmits an AMP poll frame to a non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP poll frame.
[0114] Because the AMP AP may have no knowledge regarding the non-AP AMP STA, the AMP AP may start a transaction by transmitting an AMP poll frame to initiate a random access session. For example, the AMP poll frame may be used for requesting an identification of the non-AP AMP STA.
[0115] In step 302, the non-AP AMP STA transmits an AMP response frame for responding to the AMP poll frame to the AMP AP. Accordingly, the AMP AP receives the AMP response frame.
[0116] For example, the AMP response frame may carry an identification (such as a 16-bits random number (RN16) or a MAC address) of the non-AP AMP STA as a response to the AMP poll frame.
[0117] In step 303, the AMP AP transmits an AMP request frame to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP request frame.
[0118] The AMP request frame may be used for requesting capability information of the non-AP AMP STA. For example, the AMP request frame may be used for requesting information about whether the non-AP AMP STA is capable of supporting security.
[0119] In step 304, the non-AP AMP STA transmits an AMP response frame for responding to the AMP request frame to the AMP AP. Accordingly, the AMP AP receives the AMP response frame.
[0120] The AMP response frame in the step 304 may include a capability report of the non-AP AMP STA. For example, the capability report indicates that the non-AP AMP STA is capable of supporting security.
[0121] It is noted that the steps 303 and 304 may be omitted in a case where the non-AP AMP STA’s capability is already included in the non-AP AMP STA’s response during the random access session (such as the steps 301 and 302) . For example, the AMP response frame in the step 302 may carry the capability report.
[0122] In step 305, the non-AP AMP STA may support security, and the AMP AP transmits an AMP authentication request frame to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP authentication request frame.
[0123] There may be various methods for performing authentication between the AMP AP and the non-AP AMP STA. For example, the AMP authentication request frame may be used for initiating the authentication, which may carry a type (e.g., using a password, a token, or a key) of the authentication, and other relevant information about the authentication.
[0124] In step 306, the non-AP AMP STA transmits an AMP authentication response frame for responding to the AMP authentication request frame to the AMP AP. Accordingly, the AMP AP receives the AMP authentication response frame.
[0125] For example, the non-AP AMP STA may obtain the type of the authentication and agree to the request. The non-AP AMP STA my further generate an authentication response according to the AMP authentication request frame, and transmit the authentication response through the AMP authentication response frame.
[0126] In step 307, the AMP AP transmits an AMP authentication confirm frame to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP authentication confirm frame.
[0127] Upon receiving the AMP authentication response frame, the AMP AP may authenticate the authentication response. If the authentication succeeds, the AMP AP transmits the AMP authentication confirm frame and the non-AP AMP STA receives the authentication confirm, which means that a secured relationship between the AMP AP and the non-AP AMP STA may be established. Next, the AMP AP and the non-AP AMP STA may perform secure communication.
[0128] In step 308, the AMP AP and the non-AP AMP STA perform data exchange.
[0129] In this case, the AMP AP and the non-AP AMP STA may perform data exchange via secure communication or encrypted communication.
[0130] It is noted that the steps 303 to 307 are optional. In another possible implementation, after the step 302, the AMP AP and the non-AP AMP STA may also perform data exchange in the step 308 via insecure communication or plain communication.
[0131] It is also noted that the steps 303 to 307 show an example of establishment of a secured relationship between the AMP AP and the non-AP AMP STA. There may be other ways of the establishment of the secured relationship.
[0132] Step 309 may be regarded as a combined step of steps 301 to 307. As shown in steps 309 and 310, at a later point in time, this entire procedure may be repeated to perform another data exchange.
[0133] While the transaction based communication may be suitable in a case where the data exchange is expected to be performed infrequently, it can be seen that this mode may not be suitable in use cases that require frequent data exchange due to the large overhead caused by the frame exchanges (ablock 1 in FIG. 3) prior to the actual data exchange.
[0134] For a multi-AP scenario, the above problem also exists. A transaction based communication between AMP APs and non-AP AMP STAs in a large deployment, for example in the communication system 200 shown in FIG. 2, is illustrated in FIG. 4. For example, AMP AP 1 and AMP AP 2 in FIG. 4 may be any two of the AMP APs 201, 202 and 203 in FIG. 2, and the non-AP AMP STA may be any one of the non-AP AMP STAs 204, 205, and 206 in FIG. 2.
[0135] For ease of understanding, there are two AMP APs and a non-AP AMP STA illustrated in a communication method 400, which is only illustrative and is not intended to be limiting. In practical application scenarios, there may be multiple AMP APs and multiple non-AP AMP STAs. As shown in FIG. 4, the communication method 400 includes steps 401 to 411.
[0136] As mentioned in FIG. 2, in a large deployment, the management of non-AP AMP STAs may be centrally performed, e.g., in a network connected server. The server may be one of the two AMP APs. As shown in FIG. 4, the AMP AP 1 may be the server.
[0137] The communication method 400 is similar to the communication method 300, and the same parts will not be repeated here. For example, steps 401 to 403 may refer to description of the steps 301 to 303, and steps 406 to 409 may refer to description of the steps 305 to 308.
[0138] In step 404, the AMP AP 2 may receive a capability report of the non-AP AMP STA from the AMP response frame.
[0139] In step 405, the AMP AP 2 may transmit the capability report to the AMP AP 1.
[0140] In a case where the non-AP AMP STA is capable of supporting security, the non-AP AMP STA and the AMP AP 1 may perform authentication (steps 406 to 408, which are similar to the steps 305 to 307 in FIG. 3) . Because the AMP AP 1 acts as a server, although not shown in FIG. 4, the AMP AP 1 may synchronize information related to the authentication to the AMP AP 2. After the authentication succeeds, the non-AP AMP STA may perform data exchange with the AMP AP 2 via secure communication or encrypted communication (step 409, which is similar to the step 308 in FIG. 3) .
[0141] It is noted that the steps 403 to 408 are optional. In another possible implementation, after the step 402, the AMP AP 2 and the non-AP AMP STA may also perform data exchange in step 409 via insecure communication, open communication or plain communication.
[0142] It is also noted that the steps 403 to 408 show an example of establishment of a secured relationship between the AMP AP 1 and the non-AP AMP STA. There may be other ways of the establishment of the secured relationship.
[0143] Likewise, step 410 may be regarded as a combined step of steps 401 to 408. As shown in steps 410 and 411, at a later point in time, this entire procedure may be repeated to perform another data exchange.
[0144] It can also be seen that the transaction based communication may not be suitable in use cases that require frequent data exchanges due to the large overhead caused by the frame exchanges (ablock 2 in FIG. 4) prior to the actual data exchange.
[0145] As shown in FIGS. 3 and 4, in the transaction based communication, the AMP AP and the non-AP AMP STA require a frames interaction process for IDs or capabilities, before each data exchange. And the frames interaction process (such as the block 1 in FIG. 3 or the block 2 in FIG. 4) is also known as initial access, which may lead to large overhead and increase communication complexity.
[0146] In light of this, some embodiments of the present disclosure provide a communication method, in which a pairing relationship between an AMP AP and a non-AP AMP STA may be established. Once the pairing relationship is established, the AMP AP may assign a temporary identification (which may be called a pairing identification (PID) ) to the non-AP AMP STA. In this case, the AMP AP and the non-AP AMP STA may perform data exchange based on the PID and an identification (such as a MAC address) of the AMP AP. In this way, before each data exchange, the initial access may be omitted, which may decrease overhead and communication complexity.
[0147] A communication method according to some embodiments of the present disclosure will be described in conjunction with FIGS. 5 to 25. The communication method may be applied to various communication systems, such as the communication system 100 shown in FIG. 1, the communication system 200 shown in FIG. 2, or other communication systems. A wireless communication connection may exist between two communication devices in the communication system. One of the communication devices may correspond to an AMP AP (e.g., an AMP AP shown in FIG. 1 or FIG. 2) , or it may be part of the AMP AP, such as a module, chip, or circuit within the AMP AP. The other communication device may correspond to a non-AP AMP STA (e.g., a non-AP AMP STA shown in FIG. 1 or FIG. 2) , or it may be part of the non-AP AMP STA, such as a module, chip, or circuit within the non-AP AMP STA.
[0148] Hereinafter, without loss of generality, an interaction process between the AMP AP and the non-AP AMP STA will be used as an example to describe the communication method according to some embodiments of the present disclosure.
[0149] FIG. 5 illustrates a flowchart of a communication method according to some embodiments of the present disclosure. As shown in FIG. 5, the communication method 500 includes steps 501 and 502.
[0150] In step 501, an AMP AP generates a first AMP frame indicating a pairing relationship between the AMP AP and a non-AP AMP STA. The first AMP frame includes a first field indicating a temporary identification assigned by the AMP AP to the non-AP AMP STA, and a second field indicating an identification of the AMP AP.
[0151] The pairing relationship may be defined as a bonding relationship between an AMP AP and a non-AP AMP STA. An AMP AP may be paired with multiple non-AP AMP STAs, and a non-AP AMP STA may also be paired with multiple AMP APs.
[0152] The temporary identification assigned by the AMP AP to the non-AP AMP STA may be called a paired identification (PID) (e.g., a 16-bits identification) for subsequent communication. The PID is only illustrative and is not intended to be limiting, and the temporary identification may alternatively be referred to using other designations. The identification of the AMP AP may refer to a permanent identification of the AMP AP, such as a MAC address or other identifications, which is only illustrative and is not intended to be limiting. For ease of description, the identification of the AMP AP may be called an AP address or a paired AP address, and the AMP AP having the pairing relationship with the non-AP AMP STA may be called a paired AMP AP or a paired AP.
[0153] It is noted that the term “pairing” used in embodiments of the disclosure is only illustrative and is not intended to be limiting. In a practical application scenario, other terms may also be used, e.g., light association, AMP connection, etc.
[0154] In step 502, the AMP AP transmits the first AMP frame to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the first AMP frame.
[0155] After the pairing relationship establishment, according to the PID and paired AP address in the first AMP frame, the non-AP AMP AP may perform subsequent communication (e.g., data exchange) with the AMP AP. The subsequent communication may also be called paired communication.
[0156] In this way, the AMP AP and the non-AP AMP STA may not perform the initial access (such as block 1 in FIG. 3 or a block 2 in FIG. 4) before each paired communication (such as data exchange) , which may facilitate decreasing overhead and communication complexity.
[0157] The establishment of the pairing relationship may be initiated by the AMP AP. In some embodiments, the method 500 further includes step 503 and 504.
[0158] In step 503, the AMP AP transmits a second AMP frame for requesting establishment of a pairing relationship to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the second AMP frame.
[0159] The establishment of the pairing relationship may be initiated by the AMP AP through the second AMP frame. For example, the second AMP frame includes at least one of: a sixth field indicating an identification of the non-AP AMP STA, or a seventh field indicating a presence of the sixth field.
[0160] For example, the second AMP frame may also include at least one of: an eighth field indicating the identification of the AMP AP, or a ninth field indicating a presence of the eighth field.
[0161] Upon receiving the second AMP frame, the non-AP AMP STA may obtain the identification (such as a MAC address) of the AMP AP. The non-AP AMP STA may decide whether to accept the request or not, based on the AMP AP’ conditions or its own conditions, for example, according to its current power level.
[0162] In step 504, the non-AP AMP STA transmits, to the AMP AP, a third AMP frame indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship. Accordingly, the AMP AP receives the third AMP frame.
[0163] For example, the third AMP frame includes at least one of: a third field indicating an identification of the non-AP AMP STA, a fourth field indicating a presence of the third field, or a fifth field indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.
[0164] For example, upon receiving the third AMP frame, the AMP AP may obtain the identification of the non-AP AMP STA that accepts the request, and the AMP AP may assign a PID for the non-AP AMP STA.
[0165] As mentioned earlier, after the establishment of the pairing relationship, the AMP AP and the non-AP AMP STA may perform paired communication (e.g., data exchange) . And either the AMP AP or the non-AP AMP STA may choose to terminate the pairing relationship.
[0166] In some embodiments, the method 500 further includes step 505. In step 505, the AMP AP may transmit or receive a sixth AMP frame indicating termination of the pairing relationship.
[0167] For example, the sixth AMP frame includes a tenth field indicating a reason for the termination of the pairing relationship. For example, the non-AMP AMP STA may not have enough energy to keep paired communication, and then the non-AP AMP STA may transmit the sixth AMP frame to terminate the pairing relationship.
[0168] In a possible implementation, the pairing relationship may be an open pairing relationship, and accordingly, the paired communication may be open paired communication. In another possible implementation, the pairing relationship may be a secure pairing relationship, and accordingly, the paired communication may be secure paired communication.
[0169] For example, whether the pairing relationship is open or secure may depend on capabilities of the non-AP AMP STA. In a case where the non-AP AMP STA is not capable of supporting security, the pairing relationship may be the open pairing relationship. In this case, the first AMP frame may be an AMP pairing confirm frame. In a case where the non-AP AMP STA is capable of supporting security, the pairing relationship may be the secure pairing relationship. In this case, the first AMP frame may be an AMP authentication confirm frame.
[0170] It is understood that, before the communication in the method 500, because the AMP AP may have no knowledge regarding the non-AP AMP STA, the AMP AP may initiate a random access, such as the steps 301 and 302 in FIG. 3 (the steps 303 and 304 may also be needed, for example, in a case where the AMP AP still lacks knowledge of whether the-non-AP AMP STA is capable of supporting security or not after the steps 301 and 302) , which may refer to related description in FIG. 3 and will not be repeated here. The AMP AP may obtain an identification (such as a RN16 or a MAC address) of the non-AP AMP STA, and the AMP AP may also obtain whether the non-AP AMP STA is capable of supporting security or not. In a possible implementation, whether the non-AP AMP STA is capable of supporting security may be explicitly indicated by the non-AP AMP STA, e.g., in its capability report. In another possible implementation, whether the non-AP AMP STA is capable of supporting security may be implicitly known based on a type of the non-AP AMP STA (e.g., a backscatter non-AP AMP STA may not be capable of supporting security, while an active Tx non-AP AMP STA may be capable of supporting security) .
[0171] In order to facilitate paired communication, the non-AMP AP STA may be required to meet following conditions. The non-AP AMP STA may possess a unique permanent identification (e.g., an electronic product code (EPC) , a tag identifier (TID) , a MAC address, or a public key used for identification, etc. ) . The non-AP AMP STA may possess sufficient energy to sustain long term memory. In a possible implementation, the non-AP AMP STA may possess energy source (alarge capacitor, an energy harvester, or a small battery, etc. ) . In another possible implementation, the non-AP AMP STA may be provided with wireless power (e.g., via an AMP energizer) . It is noted that a backscatter non-AP AMP STA that is able to sustain the long term memory is also eligible for the paired communication.
[0172] FIG. 6 illustrates a schematic diagram of a possible communication process according to some embodiments of the present disclosure. As shown in FIG. 6, the AMP AP and the non-AP AMP STA may be required to store pairing information in order to facilitate paired communication. For example, the AMP AP may save pairing information A, including: an identification (e.g., a MAC address, an EPC, a TID) of the non-AP AMP STA and a PID (e.g., a 16-bits identification) of the non-AP AMP STA. After the establishment of the pairing relationship, the non-AP AMP STA may save pairing information B, including: a paired AP address (e.g., the MAC address of the AMP AP) and the PID of the non-AP AMP STA. The pairing information A and the pairing information B may further include a security related context (e.g., a secure key (such as a pairwise master key (PMK) or a pairwise transient key (PTK) ) and a packet number (PN) etc. ) , in a case where the pairing relationship is a secure pairing relationship.
[0173] As shown in FIG. 6, after the establishment of the pairing relationship, the AMP AP and the non-AP AMP STA may engage in paired communication, e.g., direct unicast communication, using the PID and the paired AP address.
[0174] Next, taking establishment of an open pairing relationship and open paired communication as examples, a communication method will be described in conjunction with FIGS. 7 to 15.
[0175] In the establishment of the open pairing relationship, an AMP AP and a non-AP AMP STA may communicate via AMP pairing frames. For example, the first AMP frame may be an AMP pairing confirm frame, the second AMP frame may be an AMP pairing request frame, the third AMP frame may be an AMP pairing response frame, and the sixth AMP frame may be an AMP unpair frame, all of which belong to the AMP pairing frames.
[0176] It is understood that the AMP pairing frames may belong to AMP frames. FIG. 7 illustrates a general format of an example AMP frame according to some embodiments of the present disclosure.
[0177] The AMP frame includes: a MAC header field with a variable length of 8, 16, 24, 32, 40, 48, 56 or 64 bits, a Frame Body field with a variable length, and a frame check sequence (FCS) field with a length of 16 bits.
[0178] The MAC Header field may be responsible for controlling and managing transmission of the AMP frame, including an identification, addressing, type indication, etc. The Frame Body field may carry actual data or management instructions according to a type of the AMP frame. The FCS field may be used either to carry a CRC for detecting whether an error occurs during transmission of the AMP frame, or to carry an MIC for secure communication.
[0179] FIG. 8 illustrates a general format of an example frame body of an AMP pairing frame according to some embodiments of the present disclosure.
[0180] As shown in FIG. 8, the frame body of the AMP pairing frame include: a Sub-Type field with a length of 2 bits, a Sub-Type Control field with a length of 6 bits, and a Type Dependent Payload field with a variable length.
[0181] The Sub-Type field may indicate a type of the AMP pairing frame. The AMP pairing frame may fulfill different functions with different values of the Sub-Type field. For example, various values of the Sub-Type field of the AMP pairing frame are shown in Table 1. Table 1
[0182] It is noticed that Table 1 shows possible correspondences between the value of the Sub-Type field and the type of the AMP pairing frame, but there may be other correspondences therebetween. For example, a Sub-Type field with a value of 0 may indicate that the AMP pairing frame is an AMP pairing request frame.
[0183] The Sub-Type Control field may carry additional control information related to the AMP pairing frame. The Type Dependent Payload field may carry data according to a type of the AMP pairing frame.
[0184] FIG. 9 illustrates another communication method according to some embodiments of the present disclosure. As shown in FIG. 9, the communication method 900 includes steps 901 to 909. Steps 901 to 904 may describe establishment of an open pairing relationship, steps 905 to 908 may describe open paired communication based on the open pairing relationship, and step 909 may describe termination of the open pairing relationship.
[0185] In step 901, an AMP AP transmits an AMP pairing request frame to a non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP pairing request frame.
[0186] The AMP pairing request frame may refer to the second AMP frame mentioned above. FIG. 10 illustrates a general format of a frame body of an example AMP pairing request frame according to some embodiments of the present disclosure. Because the AMP pairing request frame belongs to the AMP pairing frame shown in FIG. 8, the same parts will not be repeated here.
[0187] Referring to Table 1, a value of a Sub-Type field of the AMP pairing request frame may be 0. For example, as shown in FIG. 10, the Sub-Type Control field may carry an ID Present field with a length of 1 bit and a Reserved field with a length of 5 bits. The Type Dependent Payload field may further include an ID field with a length of 0 bit or a variable length.
[0188] As shown in FIG. 10, the ID field may include an ID field indicating an identification (e.g., a RN16, an EPC or a MAC address) of the non-AP AMP STA, with a variable length, and an ID length field indicating a length of the identification with a length of 8 bits. The ID field with the length of 0 bit or the variable length may refer to the sixth field mentioned above. The ID Present field, which may refer to the seventh field, may indicate whether the ID field with the length of 0 bit or the variable length exists or not. The Reserved field may be used for further expansion, data alignment or protocol security.
[0189] In a case where the length of the identification is non-ambiguous (e.g., if the 802.11 bp specifies it to be a 48-bit MAC address) , the ID Length field may be omitted. It is noted that although not shown in FIG. 10, in a case where the AMP pairing request frame is transmitted by a non-AP AMP STA, the AMP pairing request frame may also carry capabilities of the non-AP AMP STA.
[0190] Upon receiving the AMP pairing request frame in the step 901, the non-AP AMP STA may decide to accept the request.
[0191] In step 902, the non-AP AMP STA transmits an AMP pairing response frame to the AMP AP. Accordingly, the AMP AP receives the AMP pairing response frame.
[0192] The AMP pairing response frame may refer to the third AMP frame mentioned above. FIG. 11 illustrates a general format of a frame body of an example AMP pairing response frame according to some embodiments of the present disclosure. A structure of the frame body of the AMP pairing response frame is similar to a structure of the frame body of the AMP pairing request frame shown in FIG. 10, and the same parts will not be repeated here.
[0193] Referring to Table 1 again, a value of a Sub-Type field of the AMP pairing response frame may be 1. A Type Dependent Payload field may include a Status field with a length of 8 bits. The Status field may indicate whether the non-AP AMP STA agrees to establishment of an open pairing relationship. For example, in a case where the non-AP AMP STA agrees to the establishment of the open pairing relationship, the Status field may be set as “OK” , else the Status field may be set as a value other than “OK” . It is noted that although not shown in FIG. 11, in a case where the AMP pairing response frame is transmitted by the non-AP AMP STA, the AMP pairing response frame may also carry capabilities of the non-AP AMP STA.
[0194] As shown in FIG. 11, an ID field with a length of 0 or a variable length may refer to the third field mentioned above, an ID Present field may refer to the fourth field mentioned above, and the Status field may refer to the fifth field mentioned above.
[0195] In the step 902, the non-AP AMP STA may decide to accept the request and transmit the AMP pairing response frame to the AMP AP, with the Status field set as “OK” .
[0196] As shown in option 1 of FIG. 9, the steps 901 and 902 illustrate a scenario where the AMP AP initiates a pairing relationship. As shown in option 2 of FIG. 9, the pairing relationship may also be initiated by the non-AP AMP STA.
[0197] In some embodiments, the AMP AP receives, from the non-AP AMP STA, a second AMP frame for requesting establishment of the pairing relationship. The second AMP frame may also refer to an AMP pairing request frame.
[0198] As shown in step 903, the non-AP AMP STA transmits an AMP pairing request frame to the AMP AP. Accordingly, the AMP AP receives the AMP pairing request frame.
[0199] The AMP pairing request frame may refer to related description in FIG. 10 and will not be repeated here. The AMP pairing request frame may also carry capabilities of the non-AP AMP STA. Upon receiving the AMP pairing request frame, the AMP AP may decide to accept the request. The step 903 describes another way that the establishment of the pairing relationship is initiated by the non-AP AMP STA, which may facilitate decreasing complexity of the establishment of the pairing relationship, and provide a flexible option.
[0200] In step 904, the AMP AP transmits an AMP pairing confirm frame to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP pairing confirm frame.
[0201] The AMP pairing confirm frame may refer to the first AMP frame mentioned above, which may indicate a pairing relationship between the AMP AP and the non-AP AMP STA. FIG. 12 illustrates a general format of a frame body of an example AMP pairing confirm frame according to some embodiments of the present disclosure. The frame body of the AMP pairing confirm frame is similar to the frame body of the AMP pairing response frame shown in FIG. 11, and the same parts will not be repeated here.
[0202] Referring to Table 1 again, a value of a Sub-Type field of the AMP pairing confirm frame may be 2. As shown in FIG. 12, a Type Dependent Payload field may include a PID field (which may refer to the first field mentioned above) with a length of 16 bits and a Paired AP Address field (which may refer to the second field mentioned above) with a length of 0 or 64 bits. The PID field may indicate a PID assigned by the AMP AP to the non-AP AMP STA. The Paired AP Address field may indicate a paired AP address.
[0203] The Sub-Type Control field may carry a Paired AP Address Present field with a length of 1 bit indicating whether the Paired AP Address field exists or not, and a Reserved field with a length of 5 bits.
[0204] The steps 901 to 904 may illustrate establishment of an open pairing relationship. After the establishment of the open pairing relationship, the AMP AP and the non-AP AMP STA may perform open paired communication such as data exchange.
[0205] In some embodiments, after the AMP AP transmits the first AMP frame to the non-AP AMP STA, the AMP AP may transmit or receive a fourth AMP frame including the temporary identification for communication. The fourth AMP frame is an unprotected AMP frame.
[0206] In the open paired communication, all AMP frames (such as AMP request frames and AMP response frames in steps 905 to 908) may refer to the fourth AMP frames.
[0207] For example, the AMP AP may transmit the fourth AMP frame to the non-AP AMP STA, and the non-AP AMP STA may receive the fourth AMP frame. For another example, the non-AP AMP STA may transmit the fourth AMP frame to the AMP AP, and the AMP AP may receive the fourth AMP frame. The temporary identification may refer to a PID.
[0208] FIG. 13 illustrates a general format of an example unprotected AMP frame according to some embodiments of the present disclosure. As shown in FIG. 13, the unprotected AMP frame includes: a MAC header field with a length of 8, 16, 24, 32, 40 or 48 bits, a Frame Body field with a variable length, and a cyclic redundancy check (CRC) field with a length of 16 bits. The unprotected AMP frame shown in FIG. 13 also belongs to an AMP frame shown in FIG. 7. It is noted that the CRC field may include a CRC algorithm for generating a check code, which is used for detecting errors. The FCS field shown in FIG. 7 may include data typically generated by the CRC algorithm and also used for error detection.
[0209] As shown in FIG. 13, the MAC Header field may include: a Frame Control field with a length of 8 bits, a Transmitter ID field with a length of 0 or 16 bits, a Receiver ID field with a length of 0 or 16 bits and a Length field with a length of 0 or 8 bits.
[0210] The Transmitter ID field may include an ID of a transmitter of the unprotected AMP frame. The Receiver ID field may include an identification of a receiver of the unprotected AMP frame. The Length field may indicate a length of the Frame Body field.
[0211] The Frame Control field may include: a Frame Type field with a length of 4 bits, a Protected field with a length of 1 bit, a Transmitter ID Present field with a length of 1 bit, a Receiver ID Present field with a length of 1 bit and a Length Present field with a length of 1 bit.
[0212] The Frame Type field may indicate a type of the AMP frame. For example, various values of the Frame Type field of the AMP frame are shown in Table 2. Table 2
[0213] It is noted that Table 2 illustrates possible correspondences between the value of the Frame Type field and the type of the AMP frame, but there may be other correspondences therebetween. For example, a Frame Type field with a value of 12 may indicate that the AMP frame may be an AMP trigger frame. It is also noted that the AMP trigger frame may refer to an AMP request frame mentioned earlier.
[0214] The Protected field may indicate whether the AMP frame is protected or unprotected. For example, the Protected field may be set as 0, indicating that the AMP frame is an unprotected AMP frame. The Transmitter ID Present field may indicate whether the Transmitter ID field exists or not. The Receiver ID Present field may indicate whether the Receiver ID field exists or not. The Length Present field may indicate whether the Length field exist or not.
[0215] The Frame Body field may include a Type Dependent Control field with a length of 0, 8 or 16 bits and a Type Dependent Payload field with a variable length. The Type Dependent Control field may be used for carrying control information according to a type of the AMP frame, such as a function indication, a version number, a command code, etc. The Type Dependent Payload field may be used for carrying actual data content according to the type of the AMP frame, such as an energy parameter, status data, etc.
[0216] In step 905, the AMP AP transmits an AMP request frame to the non-AP AMP STA, and the non-AP AMP STA may receive the AMP request frame.
[0217] The AMP request frame may be used for requesting data from the non-AP AMP STA. For example, the AMP AP may request an energy state of the non-AP AMP STA. The AMP request frame may be the fourth AMP frame mentioned above, which belongs to the unprotected AMP frame as shown in FIG. 13. For example, the AMP AP and the non-AP AMP STA may engage in unicast unprotected communication using the non-AP AMP STA’s PID, in which case a Receiver ID field in the AMP request frame may be set as the PID of the non-AP AMP STA.
[0218] In a possible implementation, a Transmitter ID field in the AMP request frame may also be set as an identification of the AMP AP. After receiving the AMP request frame, the non-AP AMP STA may check whether the AMP AP is a paired AMP AP through the Transmitter ID field.
[0219] In some embodiments, the fourth AMP frame includes a cyclic redundancy check (CRC) field, and the CRC field is determined based on the identification of the AMP AP.
[0220] For example, the Transmitter ID field in the AMP request frame (which may be the fourth AMP frame) may be omitted. In this case, upon receiving the AMP request frame, the non-AP AMP STA may check whether the AMP AP is a paired AMP AP through a CRC field in the AMP request frame.
[0221] FIG. 14 illustrates a block diagram of an example verification using a CRC field, according to some embodiments of the present disclosure.
[0222] The CRC field may include a CRC value generated through a Calculation field and a CRC algorithm (such as CRC-16) . As shown in FIG. 14, the Calculation field may include content of an AMP frame: a MAC header in the MAC Header field as shown in FIG. 13, a frame body in the Frame Body field as shown in FIG. 13, and a paired AP address of the AMP AP, even though the paired AP address is not carried in any fields of the AMP frame.
[0223] As shown in FIG. 14, the Calculation field may be serial data input that is input to a CRC-16 module. The CRC-16 module may use the serial data input to generate serial data output via the CRC-16 algorithm. The serial data output may be set as the CRC value in the CRC field carried in the AMP request frame transmitted by the AMP AP. Upon receiving the AMP request frame, the non-AP AMP STA may also calculate a CRC value via the same CRC algorithm using a paired AP address it has saved. The non-AP AMP STA may check whether the two CRC values are the same, to check whether the AMP AP is a paired AMP AP.
[0224] In step 906, the non-AP AMP STA transmits an AMP response frame to the AMP AP, and the AMP AP may receive the AMP response frame.
[0225] The AMP response frame may be used for responding to the AMP request frame. For example, the AMP response frame may carry energy state information of the non-AP AMP STA. As mentioned earlier, the AMP response frame may also be the fourth AMP frame, which belongs to the unprotected AMP frame as shown in FIG. 13. In this case, the AMP AP and the non-AP AMP STA may engage in unicast unprotected communication using the PID of the non-AP AMP STA. For example, a Transmitter ID field in the AMP response frame may be set as the PID of the non-AP AMP STA.
[0226] In a possible implementation, a Receiver ID field in the AMP response frame may be set as an identification of the AMP AP. In another possible implementation, the Receiver ID field in the AMP response frame may be omitted. In this case, the AMP AP may check whether the AP address is correct through a CRC field in the AMP response frame, which may refer to related description of FIG. 14 and will not be repeated here.
[0227] After a period of time, the AMP AP and the non-AP AMP STA may perform open paired communication again (such as next data exchange) .
[0228] In step 907, the AMP AP transmits an AMP request frame to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP request frame.
[0229] In step 908, the non-AP AMP STA transmits an AMP response frame to the AMP AP. Accordingly, the AMP AP receives the AMP response frame.
[0230] The steps 907 and 908 may be regarded as subsequent open paired communication, which may refer to description of the steps 905 and 906 and not be repeated here. Because of a pairing relationship between the AMP AP and the non-AP AMP STA, the AMP AP and the non-AP AMP STA may not perform initial access between the step 906 and the step 907.
[0231] The open pairing relationship may be terminated. As shown in step 909, the AMP AP transmits an AMP unpair frame to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP unpair frame.
[0232] It is noted that the step 909 is only illustrative and is not intended to be limiting. For example, the non-AP AMP STA may also transmit the AMP unpair frame to the AMP AP to terminate the open pairing relationship. In other words, at any time, either the AMP AP or the non-AP AMP STA may terminate the open pairing relationship by transmitting an AMP unpair frame.
[0233] The AMP unpair frame may refer to the sixth AMP frame mentioned above, which may also belong to an AMP pairing frame as shown in Table 1. FIG. 15 illustrates a general format of a frame body of an example AMP unpair frame according to some embodiments of the present disclosure. The frame body of the AMP unpair frame is similar to a frame body of the AMP pairing confirm frame shown in FIG. 12, and the same parts will not be repeated here.
[0234] Referring to Table 1 again, and as shown in FIG. 15, a value of a Sub-Type field of the AMP unpair frame may be 3. The Sub-Type Control field may be reserved. The Type Dependent Payload field may include a Reason field indicating a reason for the termination of the pairing relationship, and the Reason field may be the tenth field mentioned above.
[0235] Next, taking establishment of a secure pairing relationship and secure paired communication as examples, a communication method will be described in conjunction with FIGS. 16 to 24.
[0236] As mentioned earlier, through a random access, an AMP AP may know whether a non-AP AMP STA is capable of supporting security or not. For example, the non-AP AMP STA is capable of supporting security, and the AMP AP may initiate the establishment of the secure pairing relationship.
[0237] In some embodiments, the second AMP frame is used for requesting authentication of the non-AP AMP STA, and the third AMP frame indicates that the non-AP AMP STA accepts the request.
[0238] For example, the first AMP frame may be an AMP authentication confirm frame, the second AMP frame may be an AMP authentication request frame, the third AMP frame may be an AMP authentication response frame, and the sixth AMP frame may be an AMP deauthentication frame, all of which belong to AMP authentication frames.
[0239] In the establishment of the secure pairing relationship and secure paired communication, authentication may facilitate improving communication security and provide a flexible option.
[0240] It is noted that a general format of a frame body of the AMP authentication frame may refer to a frame body of the AMP pairing frame as shown in FIG. 8, and the same parts will not be repeated here.
[0241] The difference is that a Sub-Type field indicating a type of the AMP authentication frame may be different and the Frame Type field in the MAC Header (as shown in FIG. 13 or FIG. 21) may be set to indicate the AMP authentication. An AMP authentication frame may fulfill different functions with different values of the Sub-Type field. For example, various values of the Sub-Type field of the AMP authentication frame are shown in Table 3. Table 3
[0242] It is noticed that Table 3 illustrates possible correspondences between the value of the Sub-Type field and the type of the AMP authentication frame, but there may be other correspondences therebetween. For example, a larger Sub-Type field (e.g., using 4 bits) with a value of 9 may indicate that the AMP authentication frame is an AMP authentication request frame.
[0243] FIG. 16 illustrates yet another communication method according to some embodiments of the present disclosure. The communication method 1600 includes steps 1601 to 1609. Steps 1601 to 1604 may describe establishment of a secure pairing relationship, steps 1605 to 1608 may describe secure paired communication based on the secure pairing relationship, and step 1609 may describe termination of the secure pairing relationship.
[0244] It is noted that the establishment of the secure pairing relationship may also be regarded as authentication, such as steps 305 to 307 in the method 300 or other possible methods. For example, once the authentication succeeds, the secure pairing relationship may be established.
[0245] In step 1601, an AMP AP transmits an AMP authentication request frame to a non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP authentication request frame.
[0246] The AMP authentication request frame may also refer to the second AMP frame mentioned above. FIG. 17 illustrates a general format of a frame body of an example AMP authentication request frame according to some embodiments of the present disclosure.
[0247] As shown in FIG. 17, the frame body of the AMP authentication request frame include: a Sub-Type field with a length of 2 bits, a Sub-Type Control field with a length of 6 bits, and a Type Dependent Payload field with a variable length. Referring to Table 3 again, for the AMP authentication request frame, the Sub-Type field may be set as 0.
[0248] The Type Dependent Payload field may include: an Authentication Algorithm field with a length of 2 bits, an Authentication Transaction Sequence Number field with a length of 2 bits, an Algo Dependent Content field with a variable length, a Nonce field with a length of 2 or 256 bits and a Paired AP Address field with a length of 0 or 64 bits.
[0249] The Authentication Algorithm field may specify an algorithm used for authentication and PMK generation as listed in Table 4. Table 4
[0250] It is noticed that Table 4 illustrates possible correspondences between the value of the Authentication Algorithm field and the type of the algorithm, but there may be other correspondences therebetween. For example, an Authentication Algorithm field with a value of 2 may indicate that the algorithm is AMP-PSK.
[0251] For example, AMP-PSK may be used as an authentication algorithm for pairwise master key (PMK) generation, and the Authentication Algorithm field may be set as 1. The Authentication Transaction Sequence Number field may be reserved and used for identifying serial numbers of steps in authentication. The Algo Dependent Content field may carry parameters required for the PMK generation using PSK. The PMK may be used for generating a subsequent encryption key (e.g., a pairwise transient key (PTK) ) , and the PTK may be a key that is actually used for protecting communication link, such as by encrypting data or verifying a message integrity code (MIC) . The MIC may be used for ensuring integrity and authenticity of AMP frame transmission.
[0252] The Algo Dependent Content field may include a NumRepetition field with a length of 4 bits, a PMK-Length field with a length of 4 bits and a Hash Control field with a variable length.
[0253] The NumRepetition field indicates a number of repetitions required in the authentication. For example, in password-based key derivation function (PBKDF) algorithm, a number of repetitions for PBKDF hashing may be 2NumRepetition. The PMK-Length field may specify a length of the PMK. The Hash Control field may include a Hash Function Type field with a length of 4 bits, a Hash-String-Length field with a length of 4 bits and a Hash-string field with a variable length. The Hash Function Type field may indicate a type of hash function, as shown in Table 5. Table 5
[0254] It is noticed that Table 5 illustrates possible correspondences between the value of the Hash Function Type field and the type of the hash function, but there may be other correspondences therebetween. For example, a Hash Function Type field with a value of 9 may indicate that the hash function is SHA-256.
[0255] The Hash-String field may carry a hash-string that is a fixed-length string generated by applying a hash function to an input, typically a text or binary sequence. The Hash-String-Length field may indicate a length of the hash-string. For example, the Hash-String-Length field may be used in the PBKDF, and the length of the hash-string may be 2Hash-String-Length.
[0256] The Nonce field may carry an AP-generated Nonce (Anonce) , or the Nonce field may include a STA-generated Nonce (Snonce) . The Anonce may refer to a random number generated by the AMP AP for security. Similarly, a STA-generated Nonce (Snonce) may refer to a random number generated by the non-AP AMP STA for security. The Anonce and the Snonce are used for PTK generation. The Paired AP Address field (which may refer to the eighth field) may carry an identification (e.g., a permanent identification like a MAC Address) of the AMP AP.
[0257] The Sub-Type Control field may include: a Nonce Present field with a length of 1 bit, a MIC Present field with a length of 1 bit, a NumRepitition Present field with a length of 1 bit, a PMK-Length Present field with a length of 1 bit, a Paired AP Address Present field (which may refer to the ninth field) with a length of 1 bit, and a Reserved field with a length of 1 bit. The description of these fields may refer to related description described above, and will not be repeated here.
[0258] There may be various methods of performing authentication between the AMP AP and the non-AP AMP STA. For example, in the step 1601, the AMP authentication request frame may carry AMP AP’s materials required to generate security key, such as a PMK and a PTK. The AMP AP’s materials may include: a number used once (Nonce) , the NumRepetition and an identification (such as a MAC address) of the AMP AP in the Paired AP Address field.
[0259] In step 1602, the non-AP AMP STA transmits an AMP authentication response frame for responding to the AMP authentication request frame to the AMP AP. Accordingly, the AMP AP receives the AMP authentication response frame.
[0260] FIG. 18 illustrates a general format of a frame body of an example AMP authentication response frame according to some embodiments of the present disclosure.
[0261] The frame body of the AMP authentication response frame as shown in FIG. 18 is similar to the frame body of the AMP authentication request frame as shown in FIG. 17, and the same parts will not be repeated here. Referring to Table 3 again, the AMP authentication response frame may correspond to a Sub-Type field with a value of 1.
[0262] As shown in FIG. 18, a Type Dependent Payload field may include an ID field with a length of 0 or a variable length, a Status Code field with a length of 4 bits, and a MIC field with a length of 0 or 16 bits. The ID field may include an ID field with a variable length and an ID Length field with a length of 8 bits. The ID field may carry an identification (ID) of the non-AP AMP STA, such as a RN16 or an EPC, and the ID Length field may indicate a length of the ID. The Status Code field may carry a status related to an authentication algorithm. The MIC field may carry a MIC generated by the non-AP AMP STA. And a Sub-Type Control field may include an ID Present field with a length of 1 bit.
[0263] For example, upon receiving the AMP authentication request frame, the non-AP AMP STA accepts the authentication request. The non-AP AMP STA may generate a first PMK and a first PTK based on the AMP AP’s materials carried in the AMP authentication request frame. The non-AP AMP STA may respond with an AMP authentication response frame carrying the non-AP AMP STA’s materials required to generate a security key. For example, the non-AP AMP STA’s materials may include: a Nonce and an identification (such as a MAC address) of the non-AP AMP STA. The AMP authentication response frame may carry an identification of the non-AP AMP STA. The AMP authentication response frame may also carry a MIC generated using the first PTK.
[0264] In some embodiments, the AMP AP may perform the authentication of the non-AP AMP STA, and the AMP AP may transmit the first AMP frame to the non-AP AMP STA in a case where the authentication succeeds.
[0265] As shown in step 1603, the AMP AP performs the authentication of the non-AP AMP STA.
[0266] Upon receiving the AMP authentication response frame, the AMP AP may authenticate the response. For example, the AMP AP also generates a second PMK and a second PTK based on the non-AP AMP STA’s materials carried in the AMP authentication response frame. The AMP AP may use the second PTK to validate the MIC carried in the AMP authentication response frame. For example, the AMP AP may generate another MIC using the second PTK and check whether these two MICs are consistent.
[0267] In step 1604, the AMP AP transmits an AMP authentication confirm frame to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP authentication confirm frame.
[0268] For example, if the MIC is valid, the AMP AP transmits the AMP authentication confirm frame (the first AMP frame) to the non-AP AMP STA and the non-AP AMP STA receives the AMP authentication confirm frame, it means that a secured relationship between the AMP AP and the non-AP AMP STA may be established, and a secure paired relationship is also established.
[0269] FIG. 19 illustrates a general format of a frame body of an example AMP authentication confirm frame according to some embodiments of the present disclosure.
[0270] The frame body of the AMP authentication confirm frame as shown in FIG. 19 is similar to the frame body of the AMP authentication response frame as shown in FIG. 18, and the same parts will not be repeated here. Referring to Table 3 again, the AMP authentication confirm frame may correspond to a Sub-Type field with a value of 2.
[0271] As shown in FIG. 19, a Type Dependent Payload field may include a PID field with a length of 16 bits, and a Paired AP Address field with a length of 0 or 64. The PID field may include a PID assigned by the AMP AP to the non-AP AMP STA. The Paired AP Address field may carry an ID of the AMP AP, such as a paired AP address. A Sub-Type Control field may include a Paired ID Present field with a length of 1 bit.
[0272] FIG. 20 illustrates a block diagram of an example of generating a PMK and a PTK, according to some embodiments of the present disclosure. It is noted that a process of generating the PMK and the PTK in FIG. 20 may be performed by a non-AP AMP STA or an AMP AP. For ease of understanding, an example of the AMP AP generating the PMK and the PTK will be illustrated.
[0273] As shown in FIG. 20, the AMP AP may generate a PMK using a pre-shared key (PSK) as described in the IEEE 802.11 specification. For example, in a case where SHA-256 is specified as a hash function to be used for PBKDF, and a length of the PMK is 256. The PMK may be given by: PMK = 2NumRepetitiontimes (SHA-256 (PSK, hash- string || transmitter’s ID || receiver’s ID) ) . (1)
[0274] Some parameters in Eq. (1) are described earlier and will not be repeated here. As shown in Eq. (1) , the PMK may be generated by performing SHA-256 hash operations for 2NumRepetition times. The transmitter’ ID and the receiver’s ID may be permanent IDs (e.g., MAC address or other forms of an ID) of an initiating and responding devices respectively. For example, the transmitter’ ID may refer to a paired AP address and the receiver’s ID may refer to a PID. The transmitter’ ID may also be called ID1 and the receiver’s ID may also be called ID2. The “||” may denote byte-level concatenation, and the PMK may be generated.
[0275] The PTK is used for temporary, single-connection encryption, and is further derived from the PMK. For example, the PTK may be given by: PTK = SHA-256 (PMK, “AMP Pairwise Key expansion” , Min (ID1, ID2) || Max (ID1, ID2) || Min (Anonce, Snonce) || Max (Anonce, Snonce) ) . (2)
[0276] Some parameters in Eq. (2) are described earlier and will not be repeated here. As shown in Eq. (2) , "AMP Pairwise Key expansion" may be used as a fixed string for security. The Min and Max refer to arranging elements based on their quantitative relationship to ensure consistency in generation by the AMP AP and the non-AP AMP STA.
[0277] The PTK may be partitioned as a key confirmation key (KCK) and a temporal key (TK) . The KCK may be used for protecting integrity and authentication, for example, the KCK may be used for generating a MIC, for example used in the AMP authentication frames. The TK may be used for protecting (either authenticate or encrypt) other unicast AMP frames. A length of the KCK or the TK may be 128 bits or 256 bits.
[0278] For example, the KCK may be computed as first KCK_bits bits (e.g., bit 0 to bit (KCK_bits –1) ) of the PTK and may be given by: KCK= ExtractBits (PTK, 0, KCK_bits) . (3)
[0279] As shown in Eq. (3) , the ExtractBits may be a truncation function that indicates "extracting a segment of KCK_bits length from the PTK starting at bit 0" . In other words, the KCK may refer to a string consisting of bits from bit 0 to bit (KCK_bits –1) of the PTK, and a length of the string is KCK_bits. The TK may be given by: TK=ExtractBits (PTK, KCK_bits, TK_bits) . (4)
[0280] As shown in Eq. (4) , the ExtractBits may be a truncation function that indicates "extracting a segment of TK_bits length from the PTK starting at bit TK_bits" . In other words, the TK may refer to a string consisting of bits from bit KCK_bits to bit (KCK_bits + TK_bits) of the PTK, and a length of the string is TK_bits.
[0281] It is noted that FIG. 20 is only illustrative and is not intended to be limiting. In practical application scenarios, there may be other ways of generating the PMK and PTK. As mentioned earlier, after the establishment of the secure pairing relationship, an AMP AP and a non-AP AMP STA may save the PMK and PTK for subsequent secure paired communication. The PMK may also be used for generating subsequent PTKs and MICs.
[0282] Alternatively, the AMP AP may transmit the AMP authentication confirm frame (without the PID and paired AP address) to confirm the establishment of the security keys, and the AMP AP may subsequently transmit an AMP pairing confirm frame confirming the establishment of the secure pairing relationship and carrying the PID assigned to the non-AP AMP STA. The AMP pairing confirm frame may also carry the paired AP address that identifies the pairing AMP AP.
[0283] After the establishment of the secure pairing relationship, the AMP AP and the non-AP AMP STA may perform secure paired communication.
[0284] In some embodiments, after the AMP AP transmits the first AMP frame to the non-AP AMP STA, the AMP AP may transmit or receive a fifth AMP frame including the temporary identification for communication. The fifth AMP frame is a protected AMP frame.
[0285] In the secure paired communication, all AMP frames (such as AMP request frames and AMP response frames in steps 1605 to 1608) may refer to the fifth AMP frames.
[0286] For example, the AMP AP may transmit the fifth AMP frame to the non-AP AMP STA, and the non-AP AMP STA may receive the fifth AMP frame. For another example, the non-AP AMP STA may transmit the fifth AMP frame to the AMP AP, and the AMP AP may receive the fifth AMP frame. The temporary identification may refer to a PID.
[0287] FIG. 21 illustrates a general format of an example protected AMP frame according to some embodiments of the present disclosure. The protected AMP frame shown in FIG. 21 is similar to the unprotected AMP frame shown in FIG. 13, and the same parts will not be repeated here.
[0288] The protected AMP frame includes: a MAC header field with a length of 24, 32, 40, 48, 56 or 64 bits, a Frame Body field with a variable length, and a MIC field carrying a MIC with a length of 16 bits. As mentioned earlier, a MIC may be used for secure communication.
[0289] As shown in FIG. 21, in a Frame Control field of the MAC Header field, a Protected field may be set as 1. A Protection Control field may include an Encrypted field with a length of 1 bit, a Key ID field with a length of 3 bits and a PN field with a length of 12 bits.
[0290] The Encrypted field may indicate whether the protected AMP frame is encrypted or not. For example, in a case where the Encrypted field is set as 1, the protected AMP frame may be encrypted and needs to be decrypted with a secure key. The Key ID field may indicate an index of the secure key that is used for encryption or decryption of the protected AMP frame. A receiver of the protected AMP frame may select a correct secure key for decryption based on the index. The PN field may carry a PN which may indicate a sequence number of the protected AMP frame.
[0291] In some embodiments, the fifth AMP frame includes a MIC, and the MIC is determined based on the identification of the AMP AP.
[0292] It is noted that in the establishment of the secure pairing relationship, a MIC for authentication may be in a MIC field carried in an AMP authentication response frame (as shown in FIG. 18) . However, in secure paired communication, a MIC for authentication may be in a MIC field carried in a protected AMP frame (as shown in FIG. 21) .
[0293] It is understood that in secure paired communication, frame exchange may also require authentication to ensure security, e.g., based on a security key. For example, in secure paired communication, the protected AMP frame may be used for data exchange. The MIC may be determined based on a paired AP address and a PID for authentication, which may refer to related description in FIG. 20 and will not be repeated here.
[0294] In step 1605, the AMP AP transmits an AMP request frame to the non-AP AMP STA, and the non-AP AMP STA may receive the AMP request frame. The AMP request frame may indicate that a value of PN1 is 0.
[0295] The AMP request frame may be used for requesting data from the non-AP AMP STA. For example, the AMP AP may request an energy state of the non-AP AMP STA. As mentioned earlier, the AMP request frame may be the fifth AMP frame, which belongs to a protected AMP frame as shown in FIG. 21. For example, the AMP AP and the non-AP AMP STA may engage in unicast protected communication using the non-AP AMP STA’s PID. For example, as shown in FIG. 21, a Receiver ID field in the AMP request frame may be set as a PID of the non-AP AMP STA. A Transmitter ID field in the AMP request frame may also be set as an identification (such as a paired AP address) of the AMP AP. After receiving the AMP request frame, the non-AP AMP STA may check whether the AMP AP is a paired AMP AP through the paired AP address.
[0296] The PN1 may be used to number the protected AMP frames transmitted by the AMP AP. For example, a first protected AMP frame is assigned a number of 0. A value of PN1 may be carried in a PN field in a protected AMP frame (as shown in FIG. 21) transmitted by the AMP AP.
[0297] In some embodiments, the fifth AMP frame is protected by an additional authentication data (AAD) including the identification of the AMP AP.
[0298] The AAD may commonly be used in a counter mode with cipher block chaining message authentication code protocol (CCMP) encapsulation and decapsulation procedure. The CCMP is an encryption and integrity protection protocol used for ensuring confidentiality, integrity, and authenticity of frames. Similar to their application in the CCMP, the AAD and Nonce may also be used in the protected AMP frame. The AAD may refer to authentication data derived from key fields (e.g., a Frame Control field as shown in FIG. 21) in the protected AMP frame. The Nonce, as a random input, may be used for ensuring uniqueness of the protected AMP frame and may be used for preventing replay attacks.
[0299] It is understood that the AAD and Nonce are not directly transmitted; however, their constituent elements exist within the protected AMP frame, allowing a receiver of the protected AMP frame to reconstruct the AAD and Nonce for frame protection.
[0300] FIG. 22 illustrates a general format of an example AAD according to some embodiments of the present disclosure. The AAD may include a Frame Control field with a length of 1 octet, a Transmitter ID field with a length of 0 or 2 octets, a Receiver ID field with a length of 0 or 2 octets, a Length field with a length of 0 or 1 octet, a Paired AP Address field with a length of 0 or 6 octets, and a Protection Control field with a length of 1 octet. The octet is a unit of digital information composed of 8 bits.
[0301] The Paired AP Address field may indicate a Paired AP address. The Frame Control field, Transmitter ID field, Receiver ID field, and Protection Control field and the Length field may refer to related description in FIG. 21, which will not be repeated here.
[0302] It is noted that lengths of certain fields in the AAD may be greater than that of the corresponding fields in the protected AMP frame. This is because the AAD is not a direct copy of the fields from the protected AMP frame, but may be constructed in a normalized manner, which may include field alignment, length padding, and format standardization.
[0303] As shown in FIG. 22, the AAD may also indicate the identification (the Paired AP address) of the AMP AP even though the identification is not carried in the AMP frame. For example, a Transmitter ID field in the AMP request frame (which may refer to the protected AMP frame as shown in FIG. 21) may be omitted. In this case, upon receiving the AMP request frame, the non-AP AMP STA may check whether the AMP AP is a paired AMP AP through the AAD.
[0304] FIG. 23 illustrates a general format of an example Nonce according to some embodiments of the present disclosure. The Nonce may include: a Source ID field with a length of 6 octets and a PN field with a length of 2 octets. The Source ID field may indicate an identification of a transmitter of a protected AMP frame corresponding to the Nonce. The PN field may include a PN field with a length of 12 bits and a Reserved field with a length of 4 bits. The PN field with the length of 12 bits may indicate a sequence number of the protected AMP frame corresponding to the Nonce.
[0305] It is noted that the PN field in the Nonce and the PN field in the protected AMP frame shown in FIG. 21 may not indicate two independent entities (two PNs) , but rather different manifestations of the same PN at different stages. For example, the PN indicated by the Nonce may also be used for MIC generation.
[0306] In step 1606, the non-AP AMP STA may transmit an AMP response frame to the AMP AP, and the AMP AP may receive the AMP response frame. The AMP response frame may indicate that a value of PN2 is 0.
[0307] Similar to PN1, the PN2 may be used to number the protected AMP frames transmitted by the non-AP AMP STA. For example, a first protected AMP frame is also assigned a number of 0. A value of PN2 may also be carried in a PN field in a protected AMP frame (as shown in FIG. 21) transmitted by the non-AP AMP STA.
[0308] The AMP response frame may be used for responding to the AMP request frame. For example, the AMP response frame may carry energy state information of the non-AP AMP STA. The AMP response frame may also be the fifth AMP frame, which belongs to the protected AMP frame as shown in FIG. 21. For example, a Transmitter ID field in the AMP response frame may be set as a PID of the non-AP AMP STA.
[0309] In a possible implementation, a Receiver ID field in the AMP response frame may also be set as an identification of the AMP AP. In another possible implementation, the Receiver ID field in the AMP response frame may be omitted. In this case, the AMP AP may check whether the paired AP address is the same as its own address through the AAD (as shown in FIG. 22) .
[0310] Steps 1607 and 1608 may be similar to the steps 1605 and 1606, and the same parts will not be repeated here. In the secure paired communication shown in the steps 1605 to 1608, the AMP AP and the non-AP AMP STA may also perform authentication for security. For example, as mentioned earlier, the AMP AP and the non-AP AMP STA may save the PMK and PTK. The AMP AP and the non-AP AMP STA may generate the MIC based on the PTK. Upon receiving a protected AMP frame, a receiver may authenticate whether a MIC in the protected AMP frame matches a MIC generated by itself.
[0311] As shown in the steps 1607 and 1608, PN1 and PN2 may increase compared with that in the steps 1605 and 1606, which means that the authentication may also be related to the PN. For example, a length of the PN field (as shown in FIG. 21) may determine lifespan of the PTK used in authentication, e.g., a 12-bit PN may restrict the PTK reuse to 4096 times for the AMP AP or the non-AP AMP STA. PN1 for a transmission direction (from the AMP AP to the non-AP AMP STA) is maintained by the AMP AP. PN2 for another transmission direction (from the non-AP AMP STA to the AMP AP) is maintained by the non-AP AMP STA.
[0312] For example, with interaction of protected AMP frames, PN1 and PN2 will increase. In a case where PN1 and PN2 both remain below a maximum value N (e.g., 4096) , the AMP AP and non-AMP AP STA may continue to use an original MIC for authentication. However, for example, in a case where the PN1 reaches N, a new PTK may be generated using a new PMK, and a new MIC for next authentication may also be generated. The PN1 may be set to 0 and start counting again.
[0313] In this case, the AMP AP may communicate with the non-AP AMP STA for authentication information (e.g., the new PMK or PN reset indication) . For example, the authentication information may be carried in the AMP request frame in the step 1607, or may be carried in other frames, which is not limited thereto. In this way, the AMP AP and the non-AP AMP STA may continue to perform secure paired communication.
[0314] After secure paired communication, the secure pairing relationship may be terminated. As shown in step 909, the AMP AP transmits an AMP deauthentication frame to the non-AP AMP STA. Accordingly, the non-AP AMP STA receives the AMP deauthentication frame.
[0315] It is noted that the step 1609 is only illustrative and is not intended to be limiting. For example, the non-AP AMP STA may also transmit the AMP deauthentication frame to the AMP AP to terminate the secure pairing relationship. In other words, at any time, either the AMP AP or the non-AP AMP STA may terminate the secure pairing relationship by transmitting an AMP deauthentication frame.
[0316] The AMP deauthentication frame may refer to the sixth AMP frame mentioned above. FIG. 24 illustrates a general format of a frame body of an example AMP deauthentication frame according to some embodiments of the present disclosure. A structure of the frame body of the AMP deauthentication frame is similar to a structure of the frame body of the AMP authentication confirm frame shown in FIG. 19, and the same parts will not be repeated here. Referring to Table 3 again, the AMP deauthentication frame may correspond to a Sub-Type field with a value of 3.
[0317] As shown in FIG. 24, a Type Dependent Payload field may include a Reason field with a length of 8 bits. The Reason field may indicate a reason for termination of the secure pairing relationship. The Reason field may be the tenth field mentioned above.
[0318] FIG. 25 illustrates a schematic diagram of pairing states transition of a non-AP AMP STA according to some embodiments. A non-AP AMP STA may track its pairing state. An AMP AP may also track a non-AP AMP STA’s pairing state. Before a pairing relationship is established (e.g., a pairing request is not accepted or authentication fails) , the non-AP AMP STA stays in an Init state (e.g., process 251 in FIG. 25) . In a case where an open pairing relationship is established (e.g., the non-AP AMP STA receives an AMP pairing confirm frame) , the non-AP AMP STA may transition from the Init state to the Open Paired state (e.g., process 252 in FIG. 25) . Once the open pairing relationship is terminated (e.g., the non-AP AMP STA receives an AMP unpair frame) , the non-AP AMP STA may transition from the Open Paired state to the Init state (e.g., process 253 in FIG. 25) . In a case where a secure pairing relationship is established (e.g., the non-AP AMP STA receives an AMP authentication confirm frame) , the non-AP AMP STA may transition from the Init state to the Secure Paired state (e.g., process 254 in FIG. 25) . Once the secure pairing relationship is terminated (e.g., the non-AP AMP STA receives an AMP deauthentication frame) , the non-AP AMP STA may transition from the Secure Paired state to the Init state (e.g., process 255 in FIG. 25) .
[0319] The communication methods provided in the embodiments of the present disclosure are described in detail above with reference to FIGS. 1 to 25. Next, the communication apparatus in the embodiments of the present disclosure will be described in detail below with reference to FIGS. 26 and 27.
[0320] FIGS. 26 and 27 are structural diagrams of example communication apparatuses in accordance with some embodiments of the present disclosure. These communication apparatuses may be used to realize the functions of the AMP AP or the non-AP AMP STA in the method embodiments, and therefore may also achieve the beneficial effects of the method embodiments.
[0321] As shown in FIG. 26, the communication apparatus 2600 includes a transceiver unit 2610 and a processing unit 2620. The communication apparatus 2600 is used to implement the functions of the AMP AP or non-AP AMP STA in the method embodiments.
[0322] In a case where the communication apparatus 2600 is used to implement the functions of the AMP AP in the method embodiments, the processing unit 2620 is configured to: generate a first AMP frame indicating a pairing relationship between the AMP AP and the non-AP AMP STA, where the first AMP frame includes a first field indicating a temporary identification assigned by the AMP AP to the non-AP AMP STA, and a second field indicating an identification of the AMP AP. And the transceiver unit 2610 is configured to: transmit the first AMP frame to the non-AP AMP STA.
[0323] In some embodiments, the transceiver unit 2610 is configured to receive, from the non-AP AMP STA, a second AMP frame for requesting establishment of the pairing relationship.
[0324] In some embodiments, the transceiver unit 2610 is configured to transmit, to the non-AP AMP STA, a second AMP frame for requesting establishment of the pairing relationship; and receive, from the non-AP AMP STA, a third AMP frame indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.
[0325] In some embodiments, the third AMP frame includes at least one of: a third field indicating an identification of the non-AP AMP STA, a fourth field indicating a presence of the third field, or a fifth field indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.
[0326] In some embodiments, the second AMP frame includes at least one of: a sixth field indicating an identification of the non-AP AMP STA, or a seventh field indicating a presence of the sixth field.
[0327] In some embodiments, after transmitting the first AMP frame to the non-AP AMP STA, the transceiver unit 2610 is also configured to transmit or receive a fourth AMP frame including the temporary identification for communication, where the fourth AMP frame is an unprotected AMP frame.
[0328] In some embodiments, the fourth AMP frame includes a cyclic redundancy check (CRC) field, and the CRC field is determined based on the identification of the AMP AP.
[0329] In some embodiments, the second AMP frame is used for requesting an authentication of the non-AP AMP STA, and the third AMP frame indicates that the non-AP AMP STA accepts the requesting.
[0330] In some embodiments, the processing unit 2620 is configured to perform the authentication of the non-AP AMP STA, and the transceiver unit 2610 is configured to transmit the first AMP frame to the non-AP AMP STA in a case where the authentication succeeds.
[0331] In some embodiments, the second AMP frame includes at least one of: an eighth field indicating the identification of the AMP AP, or a ninth field indicating a presence of the eighth field.
[0332] In some embodiments, after transmitting the first AMP frame to the non-AP AMP STA, the transceiver unit 2610 is also configured to transmit or receive a fifth AMP frame including the temporary identification for communication, where the fifth AMP frame is a protected AMP frame.
[0333] In some embodiments, the fifth AMP frame is protected by additional authentication data (AAD) including the identification of the AMP AP.
[0334] In some embodiments, the fifth AMP frame includes a message integrity check (MIC) , and the MIC is determined based on the identification of the AMP AP.
[0335] In some embodiments, the transceiver unit 2610 is configured to transmit or receive a sixth AMP frame indicating termination of the pairing relationship.
[0336] In some embodiments, the sixth AMP frame includes a tenth field indicating a reason for the termination of the pairing relationship.
[0337] In a case where the communication apparatus 2600 is used to implement the functions of the non-AP AMP STA in the method embodiment, the transceiver unit 2610 is configured to receive, from an AMP AP, a first AMP frame indicating a pairing relationship between the AMP AP and the non-AP AMP STA, where the first AMP frame includes a first field indicating a temporary identification assigned by the AMP AP to the non-AP AMP STA, and a second field indicating an identification of the AMP AP.
[0338] In some embodiments, the transceiver unit 2610 is configured to transmit, to the AMP AP, a second AMP frame for requesting establishment of the pairing relationship.
[0339] In some embodiments, the transceiver unit 2610 is configured to receive, from the AMP AP, a second AMP frame for requesting establishment of the pairing relationship; and transmit, to the AMP AP, a third AMP frame indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.
[0340] In some embodiments, the third AMP frame includes at least one of: a third field indicating an identification of the non-AP AMP STA, a fourth field indicating a presence of the third field, or a fifth field indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.
[0341] In some embodiments, the second AMP frame includes at least one of: a sixth field indicating an identification of the non-AP AMP STA, or a seventh field indicating a presence of the sixth field.
[0342] In some embodiments, after receiving the first AMP frame from the AMP AP, the transceiver unit 2610 is also configured to receive or transmit a fourth AMP frame including the temporary identification for communication, where the fourth AMP frame is an unprotected AMP frame.
[0343] In some embodiments, the fourth AMP frame includes a cyclic redundancy check (CRC) field, and the CRC field is determined based on the identification of the AMP AP.
[0344] In some embodiments, the second AMP frame is used for requesting an authentication of the non-AP AMP STA, and the third AMP frame indicates that the non-AP AMP STA accepts the requesting.
[0345] In some embodiments, the transceiver unit 2610 is configured to receive the first AMP frame from the AMP AP in a case where the authentication succeeds.
[0346] In some embodiments, the second AMP frame includes at least one of: an eighth field indicating the identification of the AMP AP, or a ninth field indicating a presence of the eighth field.
[0347] In some embodiments, after receiving the first AMP frame from the AMP AP, the transceiver unit 2610 is also configured to receive or transmit a fifth AMP frame including the temporary identification for communication, where the fifth AMP frame is a protected AMP frame.
[0348] In some embodiments, the fifth AMP frame is protected by additional authentication data (AAD) including the identification of the AMP AP.
[0349] In some embodiments, the fifth AMP frame includes a message integrity check (MIC) , and the MIC is determined based on the identification of the AMP AP.
[0350] In some embodiments, the transceiver unit 2610 is configured to receive or transmit a sixth AMP frame indicating a termination of the pairing relationship.
[0351] In some embodiments, the sixth AMP frame includes a tenth field indicating a reason for the termination of the pairing relationship.
[0352] As shown in FIG. 27, the communication apparatus 2700 includes a processor 2710 and an interface circuit 2720. The processor 2710 and the interface circuit 2720 are coupled to each other. It will be understood that the interface circuit 2720 may be a transceiver or an input / output interface. For example, the communication apparatus 2700 may further include a memory 2730 for storing instructions executed by the processor 2710, or storing input data required by the processor 2710 for executing the instructions, or storing data generated after the processor 2710 executing the instructions. In some examples, the interface circuit 2720 may be understood as part of the processor 2710, and thus the communication apparatus 2700 includes the processor 2710.
[0353] In a case where the communication apparatus 2700 is used to implement the method embodiments, the processor 2710 is configured to implement the functions of the processing unit 2620, and the interface circuit 2720 is configured to implement the functions of the transceiver unit 2610.
[0354] It will be understood that, the processor in the embodiments of the present disclosure may be a central processing unit, or may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other programmable logic device, a transistor logic device, a hardware component or any combination thereof. The general-purpose processor may be a microprocessor, or any conventional processor.
[0355] Some embodiments of the present disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) . The computer-readable storage medium has instructions stored thereon which, when executed by one or more processors, cause the one or more processors to perform the communication method corresponding to the AMP AP or non-AP AMP STA in any of the above embodiments.
[0356] Some embodiments of the present disclosure provide a computer program product carried on a non-transitory computer-readable storage medium. The computer program product stores a computer program (namely, codes or instructions) which, when executed, cause an apparatus to perform the communication method corresponding to the AMP AP or non-AP AMP STA in any of the above embodiments.
[0357] In the present disclosure, the terms "a" , "an" and "one" are defined to mean"at least one" , that is, these terms do not exclude a plural number of items, unless stated otherwise.
[0358] In the present disclosure, terms such as "substantially" , "generally" and "about" , which modify a value, condition or characteristic of a feature of an exemplary embodiment, should be understood to mean that the value, condition or characteristic is defined within tolerances that are acceptable for the proper operation of this exemplary embodiment for its intended application.
[0359] In the present disclosure, unless stated otherwise, the terms "connected" and "coupled" , and derivatives and variants thereof, refer herein to any structural or functional connection or coupling, either direct or indirect, between two or more elements. For example, the connection or coupling between the elements can be acoustical, mechanical, optical, electrical, thermal, logical, or any combinations thereof.
[0360] In the present disclosure, expressions such as "match" , "matching" and "matched" , including variants and derivatives thereof, are intended to refer herein to a condition in which two or more elements are either the same or within some predetermined tolerance of each other. That is, these terms are meant to encompass not only "exactly" or "identically" matching the two elements but also "substantially" , "approximately or" subjectively "matching the two or more elements, as well as providing a higher or best match among a plurality of matching possibilities.
[0361] In the present disclosure, the expression "based on" is intended to mean "based at least partly on" , that is, this expression can mean "based solely on or" based partially on ", and so should not be interpreted in a limited manner. More particularly, the expression "based on" could also be understood as meaning "depending on" , "representative of" , "indicative of" , "associated with" or similar expressions.
[0362] In the present disclosure, the terms "system" and "network" may be used interchangeably in embodiments of this application. "At least one" means one or more, and "a plurality of" means two or more. The term "and / or" describes an association relationship of associated objects, and indicates that three relationships may exist. For example, A and / or B may indicate the following three cases: only A exists, both A and B exist, and only B exists, where A and B may be singular or plural. The character " / " usually indicates an "or" relationship between associated objects. "At least one of the following items (pieces) " or a similar expression thereof indicates any combination of these items, including a single item (piece) or any combination of a plurality of items (pieces) . For example, "at least one of A, B, or C" includes A, B, C, A and B, A and C, B and C, or A, B, and C, and "at least one of A, B, and C" may also be understood as including A, B, C, A and B, A and C, B and C, or A, B, and C. In addition, unless otherwise specified, ordinal numbers such as "first" and "second" in embodiments of this application are used to distinguish between a plurality of objects, and are not used to limit a sequence A time sequence, priorities, or importance of the plurality of objects.
[0363] A person skilled in the art should understand that embodiments of this application may be provided as a method, an apparatus (or system) , computer-readable storage medium, or a computer program product. Therefore, this application may use a form of a hardware-only embodiment, a software-only embodiment, or an embodiment with a combination of software and hardware. Moreover, this application may use a form of a computer program product that is implemented on one or more computer-usable storage media (including but not limited to a disk memory, an optical memory, and the like) that include computer-usable program code.
[0364] This application is described with reference to the flowcharts and / or block diagrams of the method, the device (system) , and the computer program product according to this application. It should be understood that computer program instructions may be used to implement each process and / or each block in the flowcharts and / or the block diagrams and a combination of a process and / or a block in the flowcharts and / or the block diagrams. The computer program instructions may be provided for a general-purpose computer, a dedicated computer, an embedded processor, or a processor of another programmable data processing device to generate a machine, so that the instructions executed by the computer or the processor of the another programmable data processing device generate an apparatus for implementing a specific function in one or more procedures in the flowcharts and / or in one or more blocks in the block diagrams.
[0365] The computer program instructions may alternatively be stored in a computer-readable memory that can indicate a computer or another programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate an artifact that includes an instruction apparatus. The instruction apparatus implements a specific function in one or more procedures in the flowcharts and / or in one or more blocks in the block diagrams.
[0366] The computer program instructions may alternatively be loaded onto a computer or another programmable data processing device, so that a series of operations and steps are performed on the computer or the another programmable device, so that computer-implemented processing is generated. Therefore, the instructions executed on the computer or the another programmable device provide steps for implementing a specific function in one or more procedures in the flowcharts and / or in one or more blocks in the block diagrams.
[0367] It is clearly that a person skilled in the art can make various modifications and variations to this application without departing from the scope of this application. This application is intended to cover these modifications and variations of this application provided that they fall within the scope of protection defined by the following claims and their equivalent technologies.
Claims
1.A communication method performed at an ambient power (AMP) access point (AP) , the method comprising:generating a first AMP frame indicating a pairing relationship between the AMP AP and a non-AP AMP station (STA) , wherein the first AMP frame comprises a first field indicating a temporary identification assigned by the AMP AP to the non-AP AMP STA, and a second field indicating an identification of the AMP AP; andtransmitting the first AMP frame to the non-AP AMP STA.2.The method of claim 1, further comprising:receiving, from the non-AP AMP STA, a second AMP frame for requesting establishment of the pairing relationship.3.The method of claim 1, further comprising:transmitting, to the non-AP AMP STA, a second AMP frame for requesting establishment of the pairing relationship; andreceiving, from the non-AP AMP STA, a third AMP frame indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.4.The method of claim 3, wherein the third AMP frame comprises at least one of:a third field indicating an identification of the non-AP AMP STA, a fourth field indicating a presence of the third field, or a fifth field indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.5.The method of any of claims 2 to 4, wherein the second AMP frame comprises at least one of:a sixth field indicating an identification of the non-AP AMP STA, or a seventh field indicating a presence of the sixth field.6.The method of any of claims 1 to 5, after transmitting the first AMP frame to the non-AP AMP STA, further comprising:transmitting or receiving a fourth AMP frame comprising the temporary identification for communication, wherein the fourth AMP frame is an unprotected AMP frame.7.The method of claim 6, wherein the fourth AMP frame comprises a cyclic redundancy check (CRC) field, and the CRC field is determined based on the identification of the AMP AP.8.The method of claim 3, wherein the second AMP frame is used for requesting an authentication of the non-AP AMP STA, and the third AMP frame indicates that the non-AP AMP STA accepts the requesting.9.The method of claim 8, further comprising:performing the authentication of the non-AP AMP STA, whereinthe transmitting the first AMP frame to the non-AP AMP STA, comprises:transmitting the first AMP frame to the non-AP AMP STA in a case where the authentication succeeds.10.The method of claim 8 or 9, wherein the second AMP frame comprises at least one of:an eighth field indicating the identification of the AMP AP, or a ninth field indicating a presence of the eighth field.11.The method of any of claims 8 to 10, after transmitting the first AMP frame to the non-AP AMP STA, further comprising:transmitting or receiving a fifth AMP frame comprising the temporary identification for communication, wherein the fifth AMP frame is a protected AMP frame.12.The method of claim 11, wherein the fifth AMP frame comprises a message integrity check (MIC) , and the MIC is determined based on the identification of the AMP AP.13.The method of any of claims 1 to 12, further comprising:transmitting or receiving a sixth AMP frame indicating termination of the pairing relationship.14.A communication method performed at a non-AP AMP STA, the method comprising:receiving, from an AMP AP, a first AMP frame indicating a pairing relationship between the AMP AP and the non-AP AMP STA, wherein the first AMP frame comprises a first field indicating a temporary identification assigned by the AMP AP to the non-AP AMP STA, and a second field indicating an identification of the AMP AP.15.The method of claim 14, further comprising:transmitting, to the AMP AP, a second AMP frame for requesting establishment of the pairing relationship.16.The method of claim 14, further comprising:receiving, from the AMP AP, a second AMP frame for requesting establishment of the pairing relationship; andtransmitting, to the AMP AP, a third AMP frame indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.17.The method of claim 16, wherein the third AMP frame comprises at least one of:a third field indicating an identification of the non-AP AMP STA, a fourth field indicating a presence of the third field, or a fifth field indicating that the non-AP AMP STA agrees to the establishment of the pairing relationship.18.The method of any of claims 15 to 17, wherein the second AMP frame comprises at least one of:a sixth field indicating an identification of the non-AP AMP STA, or a seventh field indicating a presence of the sixth field.19.The method of any of claims 14 to 18, after receiving the first AMP frame from the AMP AP, further comprising:receiving or transmitting a fourth AMP frame comprising the temporary identification for communication, wherein the fourth AMP frame is an unprotected AMP frame.20.The method of claim 19, wherein the fourth AMP frame comprises a cyclic redundancy check (CRC) field, and the CRC field is determined based on the identification of the AMP AP.21.The method of claim 16, wherein the second AMP frame is used for requesting an authentication of the non-AP AMP STA, and the third AMP frame indicates that the non-AP AMP STA accepts the requesting.22.The method of claim 21, wherein the receiving the first AMP frame from the AMP AP, comprises:receiving the first AMP frame from the AMP AP in a case where the authentication succeeds.23.The method of claim 21 or 22, wherein the second AMP frame comprises at least one of:an eighth field indicating the identification of the AMP AP, or a ninth field indicating a presence of the eighth field.24.The method of any of claims 21 to 23, after receiving the first AMP frame from the AMP AP, further comprising:receiving or transmitting a fifth AMP frame comprising the temporary identification for communication, wherein the fifth AMP frame is a protected AMP frame.25.The method of claim 24, wherein the fifth AMP frame comprises a message integrity check (MIC) , and the MIC is determined based on the identification of the AMP AP.26.The method of any of claims 14 to 25, further comprising:receiving or transmitting a sixth AMP frame indicating a termination of the pairing relationship.27.A communication apparatus, configured to perform the method of any one of claims 1 to 13, or any one of claims 14 to 26.28.An apparatus, comprising:one or more processors; anda memory storing instructions which, when executed by the one or more processors, cause the apparatus to perform the method of any one of claims 1 to 13, or any one of claims 14 to 26.29.A computer-readable storage medium having instructions stored thereon which, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1 to 13, or any one of claims 14 to 26.30.A computer program product for storing instructions which, when executed, cause an apparatus to perform the method of any one of claims 1 to 13, or any one of claims 14 to 26.
