Identifier allocation method, identifier acquisition method, and related apparatus

Abstract

The present application relates to the technical filed of wireless communications, and provides an identifier acquisition method, an identifier allocation method, and a related apparatus. The identifier acquisition method is applied to an AMP STA device, and comprises: receiving a first broadcast message broadcasted by a first reader; when an AMP STA is in an unassigned ID state, sending an identification feedback message to the first reader; and receiving an identifier allocation message sent by the first reader and carrying an ID, and switching to a low energy consumption state, or receiving an ACK message sent by the first reader and switching to the low energy consumption state, so as to receive the identifier allocation message. The present application aims to design a wireless communication / transmission mechanism matching the characteristics of AMP devices, thereby achieving the authentication, association, identification and / or counting between readers and AMP IoT devices.

Description

Identification allocation method, identification acquisition method and related devices Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to an identifier allocation method, identifier acquisition and related apparatus. Background Technology

[0002] The Internet of Things (IoT) is a network of device components that collect data, share data with other devices, and communicate via the internet. This vast network of devices not only generates, collects, and communicates data, but also supports intelligent decision-making based on data. Features such as remote access, automation, and intelligence have led to the widespread deployment of IoT devices in applications such as smart homes, smart manufacturing, smart agriculture, and warehousing and logistics. In these applications, maintaining a continuous power supply and managing a large number of devices presents significant challenges, making ultra-low-power, ultra-long-life IoT devices a hot research area. Ambient energy IoT requires self-powered units that can obtain sufficient power from environmental conditions such as light, vibration, and heat to eliminate reliance on power cords and high-capacity batteries. Typically, IoT devices receive or generate data and then wirelessly transmit it to other devices to perform any given task. This makes the standardization of ultra-low-power IoT devices involve both wireless communication and wireless charging.

[0003] Currently, the IEEE 802.11 working group has established the Ambient Power (AMP) Study Group to address the communication challenges of ambient energy harvesting devices in 802.11 networks. AMP devices do not require a power source or large-capacity battery; instead, they harvest energy from the environment to charge and support their communication. Energy sources can include light, heat, vibration, and radio waves. However, due to their environmental energy harvesting characteristics, AMP devices, unlike traditional devices, cannot remain online for extended periods. This can lead to AMP stations (STAs) being unrecognizable in certain scenarios and hindering the transmission of large amounts of data.

[0004] To better ensure the completion of transmission and support the implementation of AMP STA wireless communication, it is necessary to design a wireless communication / transmission mechanism that matches the characteristics of AMP devices.

[0005] Summary of the Invention

[0006] This application provides an identifier allocation method, an identifier acquisition method, and related apparatus to design a wireless communication / transmission mechanism that matches the characteristics of AMP devices, and to realize authentication, association, identification, and / or counting between the reader and the AMP IoT device.

[0007] To achieve the above objectives, this application adopts the following technical solution:

[0008] The first aspect provides an identifier acquisition method for an AMP STA device, characterized in that it includes: receiving a first broadcast message broadcast by a first reader; when the AMP STA is in an IDless state, sending an identification feedback message to the first reader; receiving an identifier allocation message carrying an ID sent by the first reader, and switching to a low-power state.

[0009] Possibly, the first broadcast message includes overall AMP identification parameters.

[0010] Possibly, the overall AMP identification parameters include, but are not limited to, one or more of the following: identification available window, used to indicate the time period for device identification; identification interval, used to indicate the interval at which the AMP identification process is repeated periodically; type information, used to indicate the type of device requesting or allowed access; status information, used to indicate the status of the device requesting or allowed access; bandwidth information, used to indicate the bandwidth requested or allocated; maximum number of identification slots, used to indicate the maximum number of times the identification message can be resent if the identification feedback message is not received; and ID allocation mode, used to indicate the method of ID allocation.

[0011] Possibly, the overall AMP identification parameters may be indicated at least by fields or elements in the first broadcast message, including broadcast TWT elements or elements related to AMP identification.

[0012] Possibly, when the overall AMP identification parameters indicate that the AMP identification process is periodic identification, after receiving the first broadcast message broadcast by the first reader, the method further includes: receiving an identification message broadcast by the first reader, the identification message including the time window of the current identification slot.

[0013] Possibly, when the overall AMP identification parameters indicate that the AMP identification process is non-periodic, the first broadcast message is the first identification message transmitted within the identification available window. The first broadcast message includes the time parameters of the current identification slot and the overall AMP identification parameters. Subsequent identification messages transmitted within the identification available window include the time parameters of subsequent identification slots.

[0014] Possibly, the no-ID state includes an unassigned ID state, or an ID state where an ID exists but no first reader assigns an ID.

[0015] Possibly, the identification message may also include the identification information of the first reader, and the method may further include: based on the identification information of the first reader, searching in the locally or cloud-stored IDs for an ID corresponding to the identification information of the first reader; if no ID is found, the AMP STA is in the state of having an ID but no first reader assigning an ID.

[0016] Possibly, when in the state of having an ID but no first reader assigning an ID, the identification feedback message may also include an ID modification indication and a current ID, wherein the ID modification indication is used to indicate whether modification of the current ID is allowed; or, after receiving the identifier assignment message carrying an ID sent by the first reader, the method may further include: correspondingly storing the ID assigned by the first reader and the identifier information of the first reader, wherein the identifier information of the first reader is included in the identifier assignment message.

[0017] Possibly, the identification feedback message may also include device information, so that the first reader can group according to the device information, which includes, but is not limited to, one or more of the following: location information, data type, charging-related capabilities and / or PHY capability information.

[0018] Possibly, the identifier assignment message may also include a corresponding group identifier.

[0019] Possibly, the low-energy state includes at least one of the following states: no longer receiving and / or sending messages during the identification availability window, or receiving only identification assignment messages within the identification availability window.

[0020] Possibly, when the ID allocation mode is the per-ID allocation mode, the low-power state means that messages are no longer received and / or sent within the identification availability window.

[0021] Possibly, when the ID allocation mode is a unified allocation mode, after sending an identification feedback message in response, the method further includes: receiving an ACK message sent by the first reader to enable the AMP STA device to switch to the low-power state, wherein the low-power state is to only receive identification allocation messages within the identification availability window.

[0022] Possibly, the identifier allocation message may also include identifier information of the first reader, which includes, but is not limited to, at least one of the following: the identifier of the first reader, the MAC address of the first reader, and the basic service set identifier (BSSID) of the first reader.

[0023] Possibly, after receiving the identifier allocation message carrying the ID sent by the first reader, the method further includes: correspondingly storing the ID allocated by the first reader and the identifier information of the first reader.

[0024] Possibly, the ID assignment message may also include the ID's expiration period, indicating that the ID is a non-lifelong ID.

[0025] Possibly, the method may also include: re-acquiring the ID when the validity period of the ID expires.

[0026] Possibly, the method may also include: re-acquiring the ID if no message is received from the first reader within a preset time.

[0027] Possibly, the method further includes: receiving an ID allocation list broadcast by the first reader, the ID allocation list including allocated IDs and corresponding AMP STA addresses; querying the ID allocation list to determine whether the corresponding ID has been revoked or reassigned.

[0028] A second aspect of this application provides an identifier allocation method for a first reader, comprising: broadcasting a first broadcast message; receiving identification feedback messages sent by each environmental power AMP station STA, and sending an identifier allocation message carrying an identifier ID to each AMP STA.

[0029] Possibly, the first broadcast message includes overall AMP identification parameters.

[0030] Possibly, the overall AMP identification parameters include, but are not limited to, one or more of the following: identification available window, used to indicate the time period for device identification; identification interval, used to indicate the interval at which the AMP identification process is repeated periodically; type information, used to indicate the type of device requesting or allowed access; status information, used to indicate the status of the device requesting or allowed access; bandwidth information, used to indicate the bandwidth requested or allocated; maximum number of identification slots, used to indicate the maximum number of times the identification message can be resent if the identification feedback message is not received; and ID allocation mode, used to indicate the method of ID allocation.

[0031] Possibly, the overall AMP identification parameters may be indicated at least by fields or elements in the first broadcast message, including broadcast TWT elements or elements related to AMP identification.

[0032] Possibly, when the overall AMP identification parameters indicate that the AMP identification process is periodic identification, after the first broadcast message is sent, the method further includes: periodically broadcasting identification messages, the identification messages including the time window of the current identification slot.

[0033] Possibly, when the overall AMP identification parameters indicate that the AMP identification process is non-periodic, before the first broadcast message is sent, the method further includes: competing for an identification availability window for transmitting the first broadcast message, wherein, within the identification availability window, the first identification message transmitted includes the time parameter of the current identification slot and the overall AMP identification parameters, and the first identification message is the first broadcast message; subsequent identification messages transmitted only include the time parameter of the subsequent identification slot.

[0034] Possibly, the identification feedback message may also include device messages for each AMP, which include, but are not limited to, one or more of the following: location information, data type, charging-related capabilities, and physical PHY layer capability information.

[0035] Possibly, after receiving the identification feedback message sent by each AMP STA, the method further includes: grouping according to the device messages of each AMP STA and assigning an ID to each AMP STA, wherein the identification assignment message also includes the group identifier corresponding to each AMP STA.

[0036] Possibly, the method further includes: terminating the identification availability window when no identification feedback message is received from any AMP STA within the identification availability window, and the identification broadcast count is repeatedly sent up to the maximum identification slot number; broadcasting a de-restriction message, the de-restriction message being used to indicate the removal of access restrictions on device types that are not requested or allowed to access during the duration of the identification availability window.

[0037] Possibly, after the first broadcast message is sent, the method further includes: determining the remaining identification window based on the identification message, the identifier allocation message, and the identification available window; terminating the identification available window when the duration of the remaining identification available window does not meet a preset condition; and broadcasting a de-restriction message, which indicates the removal of access restrictions on device types that are not requested or allowed to access during the duration of the identification available window.

[0038] Possibly, the ID allocation mode includes a sequential allocation mode and a unified allocation mode. The sequential allocation mode is used to indicate that ID allocation is performed after each slot is identified; the unified allocation mode is used to indicate that ID allocation is performed uniformly after all slots are identified.

[0039] Possibly, when the ID allocation mode is a unified allocation mode, after receiving the identification feedback message sent by the AMP STA, the method further includes: sending an ACK message to the AMP STA that has sent the identification feedback message, and storing the identification feedback message.

[0040] Possibly, when the ID allocation mode is the per-ID allocation mode, the identifier allocation message is also used to instruct the AMP STA with the assigned ID not to provide identification feedback within the identification availability window.

[0041] Possibly, when the ID allocation mode is a unified allocation mode, sending the identifier allocation message carrying the identifier ID to each AMP STA includes: allocating the corresponding ID to each AMP STA via unicast / broadcast / unicast.

[0042] Possibly, the identifier allocation message may also include the identifier information of the first reader, which includes, but is not limited to, at least one of the following: the identifier of the first reader, the MAC address of the first reader, and the basic service set identifier (BSSID) of the first reader.

[0043] Possibly, receiving the identification feedback message sent by the AMP STA includes: receiving a first identification feedback message sent by the AMP STA, the first identification feedback message including first ID information and an ID modification indication, the first ID information being the ID that the first AMP STA has been assigned, and the ID modification indication being used to indicate whether to accept ID modification.

[0044] Possibly, the method may also include: performing an ID update when the conditions for an ID update are met.

[0045] Possibly, the conditions for ID updates include, but are not limited to, one or more of the following conditions: the number of allocated IDs exceeds a first preset value, the number of active IDs within a preset time period is less than a second preset value, and the reader is in an idle state.

[0046] Possibly, the ID includes a lifelong ID and a non-lifelong ID; when the ID is a non-lifelong ID, the identifier allocation message also includes the validity period of the ID.

[0047] Possibly, the ID update includes: when the number of times the AMP STA with the assigned ID is triggered or polled exceeds a preset value, and no response is received from the AMP STA with the assigned ID, the assigned ID is reclaimed and reallocated; when the assigned ID is a non-lifelong ID and its validity period has expired, the assigned ID is reclaimed and reallocated.

[0048] Possibly, the method may further include: broadcasting an ID allocation list, the ID allocation list including allocated IDs and corresponding AMP STA addresses.

[0049] A third aspect of this application also provides an identifier allocation method for a reading device, comprising: broadcasting an identification message; receiving identification feedback messages sent by each AMP STA; sending an identification reporting message to a control device based on the identification feedback messages of each AMP STA, wherein the control device is a device that has established an authentication association with the reading device; receiving an ID message allocated by the control device to each AMP STA, and forwarding it to each AMP STA.

[0050] Possibly, before broadcasting the identification message, the method further includes: sending an identification request message to the control device to request an identification available window for AMP STA identification; receiving a first broadcast message from the control device, the first broadcast message including overall AMP identification parameters; or, receiving an identification indication message sent by the control device to indicate AMP STA identification; and receiving the first broadcast message sent by the control device.

[0051] Possibly, the identification message may also include a time parameter for identifying the slot.

[0052] Possibly, before broadcasting the identification message, the method further includes: competing for an identification availability window, the identification availability window being used to transmit the identification message, the identification message including overall AMP identification parameters and identification slot time parameters.

[0053] Possibly, the time parameters for identifying slots include, but are not limited to, one or more of the following: identification start point, used to indicate the start time of the identification phase; identification duration, used to indicate the overall duration of the identification phase; identification slot number, used to indicate the number of times the identification message is repeatedly sent; identification slot duration; identification slot repetition interval; maximum identification slot number, used to indicate the maximum number of times the identification message can be repeatedly sent if the identification feedback message is not received.

[0054] Possibly, the identification reporting message includes a feedback indication to indicate whether feedback has been received from each AMP STA during the identification duration.

[0055] Possibly, the method further includes: receiving a trigger indication message sent by the controller, polling or triggering the AMP STAs with assigned IDs; and when the number of polling or triggering reaches a preset number, reclaiming the assigned IDs of the unresponsive AMP STAs.

[0056] A fourth aspect of this application also provides an identifier allocation method for a controller, comprising: receiving an identification reporting message sent by a reader, the identification reporting message including information of each AMP STA, the reader having established an authentication association with the controller; and sending an identifier allocation message to the reader, the identifier allocation message carrying the ID of each AMP STA, so that the reader forwards the message to each AMP STA.

[0057] Possibly, before receiving information about each AMP STA sent by the reader, the method further includes: receiving an identification request message sent by the reader to request an identification available window for AMP STA identification; in response to the identification request message, broadcasting a first broadcast message, the first broadcast message including overall AMP identification parameters; or, sending an identification indication message to the reader to indicate AMP STA identification; and broadcasting the first broadcast message.

[0058] Possibly, the information of each AMP STA includes the device information of each AMP STA; assigning an ID to each AMP STA includes: grouping according to the device information of each AMP STA; and assigning a corresponding ID to each AMP STA according to the grouping information, wherein the ID includes a group identifier.

[0059] Possibly, the method may also include: performing an ID update when the conditions for an ID update are met.

[0060] Possibly, the conditions for ID updates include, but are not limited to, one or more of the following conditions: the number of allocated IDs exceeds a first preset value, the number of active IDs within a preset time period is less than a second preset value, and the reader is in an idle state.

[0061] Possibly, the ID update includes sending a trigger indication message to the reader, instructing the reader to trigger the AMP STA with the assigned ID to reclaim the assigned ID.

[0062] A fifth aspect of this application also provides an identifier acquisition method for an AMP STA, comprising: receiving an identification message broadcast by a reader; when the AMP STA is in an IDless state, sending an identification feedback message to the reader; receiving an ACK message sent by the reader and switching to a low-power state to receive an identifier allocation message carrying an ID sent by the first reader.

[0063] Optionally, the identification message may include overall AMP identification parameters and identification slot time parameters; or, before the identification message is broadcast by the receiving reader, the method may further include: receiving a first broadcast message sent by the controller, the first broadcast message including the overall AMP identification parameters.

[0064] Optionally, the low-power state means receiving only the identifier allocation message within the identification availability window, and the overall AMP identification parameters include information from the identification availability window.

[0065] A sixth aspect of this application also provides a wireless communication device, including: a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the method as described in any of the preceding embodiments. Attached Figure Description

[0066] Figure 1a is a flowchart of a possible identifier allocation method based on successive ID allocation provided in an embodiment of this application;

[0067] Figure 1b is a flowchart of another possible identifier allocation method based on unified ID allocation provided in the embodiments of this application. Figure 1-1a is a timing diagram of a possible AMP STA identification based on a reader provided in the embodiments of this application.

[0068] Figure 1-1b is a timing diagram of another possible reader-based AMP STA identification provided in the embodiments of this application;

[0069] Figure 1-2a is a flowchart of a possible reader-based AMP STA identification and ID allocation process provided in an embodiment of this application;

[0070] Figure 1-2b is a flowchart of another possible reader-based AMP STA identification and ID allocation process provided in the embodiments of this application;

[0071] Figure 1-2c is a timing diagram of a possible ID successive allocation provided by an embodiment of this application;

[0072] Figures 1-2d are timing diagrams of a possible unified ID allocation provided by an embodiment of this application;

[0073] Figures 1-3a are message interaction diagrams for a possible ID sequential allocation provided in an embodiment of this application;

[0074] Figure 1-3b is a message interaction diagram of a possible unified ID allocation provided in an embodiment of this application;

[0075] Figure 2a is a flowchart of another possible identifier allocation method provided in an embodiment of this application;

[0076] Figure 2b is a flowchart of a possible AMP STA identification and ID allocation process based on a controller and a reader, provided in an embodiment of this application.

[0077] Figure 2c is a schematic diagram of the frame structure of the second frame provided in an embodiment of this application;

[0078] Figure 2d is a sequence diagram of a possible identification process based on a controller and a reader provided in an embodiment of this application.

[0079] Figure 3 is a storage diagram of a wireless communication device provided in an embodiment of this application. Detailed Implementation

[0080] For ease of understanding, the relevant technologies involved in the embodiments of this application will be described below.

[0081] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0082] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0083] The messages described in this article include frames, instructions, and commands. The names of device or functional entities, processes, frames, and fields are not unique and are only used to aid in the description of functions, methods, behaviors, and information. Additionally, the dashed lines in the diagrams indicate that the corresponding steps are optional and not mandatory.

[0084] The IEEE 802.11 wireless communication standard defines the authentication and association process for non-AP STAs to access BSSs. Before authentication and association, the STA discovers the AP or BSS based on a standard-defined scan (SCAN), including the following methods:

[0085] 1) If the wireless station STA is set to Ad-hoc (no AP) mode:

[0086] STA first checks if an independent basic service set (IBSS) (with the same service set identifier (SSID) as STA) already exists. If it does, it joins. If not, it creates its own IBSS and waits for other stations to join.

[0087] 2) If the wireless station STA is set to Infrastructure (with AP) mode:

[0088] --Active scanning method, characterized by its ability to quickly locate targets.

[0089] Non-AP STAs sequentially send Probe request messages on each channel. After receiving the Probe request, the AP replies with a Probe Response. The non-AP STA obtains the base station (BSS) information from the Probe Response.

[0090] --Passive scanning method (characteristics: longer detection time, but STA saves power)

[0091] Non-AP STAs discover networks by listening to beacon frames periodically sent by APs. The beacon frames contain basic information about the base station BSS to which the AP belongs, as well as the AP's basic capability level, including: Basic Service Set Identifier (BSSID) (the AP's MAC address), SSID, supported rates, supported authentication methods, encryption algorithms, beacon frame transmission intervals, and the channel used.

[0092] This application does not limit the discovery of AP or BSS. After SCAN, STA actively initiates channel contention, completes the authentication process by exchanging with AP to send an authentication request frame and an authentication response frame, and completes the association process by sending an association request frame and receiving an association response frame from AP after authentication.

[0093] The IEEE 802.11 working group recently established the 802.11BP working group to conduct research on wireless communication using IoT devices that harvest energy from the environment. During this phase, use cases, device types, performance requirements, technical feasibility, and economic feasibility of this technology have been extensively discussed. Simultaneously, standardization research is underway, aiming to produce a standard document describing the necessary modifications at the MAC and PHY layers of the device to implement this technology within the IEEE 802.11 standard framework. Against this research background, this application aims to design a technical solution capable of identifying, counting, and assigning IDs to AMP STAs by a reader or controller. To support the implementation of AMP STA wireless communication, a periodic identification method meeting its ultra-low power consumption and minimalist design requirements is designed, along with the necessary frame structure. It should be noted that this application may be applicable to IEEE 802.11BP, IEEE 802.11BH, IEEE 802.11BA, and other related wireless communication standards.

[0094] However, unlike traditional legacy STAs in the IEEE 802.11 standard, AMP STAs draw power from the environment and can only activate their transmitters and / or receivers to send or receive wireless frames after accumulating a certain amount of energy. During the authentication and association process, they need to send authentication requests, receive authentication feedback, send association requests, and receive association feedback, which may lead to energy depletion and inability to complete the transmission and reception process. Furthermore, due to its own power consumption limitations, AMP STAs may not be able to perform functions such as AP or BSS discovery, channel listening, and channel contention. That is, they cannot actively initiate authentication or association requests; the AP or non-AP STA needs to indicate this via wireless frames after winning a channel access opportunity, sharing the acquired channel access time with the AMP STA and silencing other STAs within the BSS to prevent transmission conflicts and trigger the AMP STA's wireless frame transmission. Therefore, AMP IoT devices cannot support existing authentication and association processes and cannot obtain the corresponding ID for subsequent reader triggering.

[0095] Furthermore, if a large number of AMP STAs communicate simultaneously with the AP or non-AP STAs, without a reasonable packet scheduling and access restriction mechanism, it will lead to numerous transmission collisions, wasting wireless transmission resources and preventing normal data exchange. Therefore, before communicating with a large number of AMP STAs, the AP or reader should implement certain packet scheduling and access restrictions to reduce the possibility of transmission collisions caused by a large number of AMP STAs accessing the channel simultaneously. Since the AP or reader cannot obtain information about the AMP STAs within its transmission range in advance, such as their location, number, and identifiers, within the AP or reader's transmission range, AMP STAs in that area are completely blind to the AP unless they have joined the BSS or are identified. Moreover, AMP STAs have a certain degree of mobility; that is, the number of AMP STAs within the transmission range is not fixed, and AMP STAs can leave or enter the AP or reader's transmission range at any time. In this situation, the AP lacks AMP STA information for packet scheduling and access restrictions. The AP or reader should periodically identify and count AMP STAs, complete ID allocation, and group them appropriately to allocate wireless transmission resources to AMP STAs based on time division, frequency division, or space division. However, during the AP's identification and counting process, collisions will inevitably occur due to a large number of responses from AMP STAs, making it difficult to identify all valid AMP STAs within the range at once.

[0096] In view of this, this application designs an identification and ID allocation process method for AMP STA that conforms to its device capabilities and characteristics, which can be divided into two scenarios: A) The main entities in the identification and allocation process include the reader and the AMP STA; B) The main entities in the identification and allocation process are the controller, the reader, and the AMP STA. It should be noted that the controller in the embodiments of this application is a functional entity that manages the process during identification, such as an AP or a server. It can be the same device as the reader or two separate devices. The reader can be a non-AP STA or an AP. The AP can be an AP, soft AP, or AMP AP as defined by the relevant IEEE 802.11 standards. The AMP STA can be a common AMP IoT device or functional entity such as an AMP non-AP STA, an AMP tag, an AMP sticker, or an AMP sensor. The specifics are not limited here.

[0097] The following will describe the two scenarios separately:

[0098] Scenario A: The main entities involved in the ID allocation process include the reader and the AMP STA. The reader can be an AP or a non-AP STA. To better describe the scheme for Scenario A, it is divided into two cases based on the different ID allocation modes: a) sequential allocation mode, where IDs are assigned to AMP STAs one by one; b) unified allocation mode, where information from multiple AMP STAs is collected and IDs are assigned to multiple AMP STAs uniformly. Details are as follows:

[0099] Please refer to Figure 1a, which is a flowchart of a possible identifier allocation method based on a successive allocation pattern provided in this application, including the following steps:

[0100] 101a. The first reader broadcasts and sends a first broadcast message;

[0101] The reader-based identification and ID allocation process involves both the reader and the AMP STA. The overall identification process includes identification and ID allocation. The reader determines the duration of the identification process, i.e., the identification protection window, to initiate the identification process. This identification process can be periodic, meaning the first reader can periodically repeat the identification process, or it can determine the identification interval for periodic identification. Alternatively, it can be non-periodic.

[0102] 1. When the first reader's decision-making and identification process is periodic, after the first reader broadcasts and sends the first broadcast message, it also includes periodically broadcasting and sending identification messages. The first broadcast message includes overall AMP identification parameters, and the identification message includes time parameters for identifying the slot. In this embodiment, the overall AMP identification parameters include, but are not limited to, one or more of the following information:

[0103] The Identify protection window indicates the time period for device identification. It can be indicated by the Availability Window element or by referring to the clock accuracy of the AMP STA using the duration field.

[0104] The identification interval (optional) is used to indicate the interval at which the AMP identification process is repeated periodically.

[0105] The type information indicates the type of device requesting or permitted access.

[0106] The status information is used to indicate the status of the device requesting or allowing access. The device status indicates relevant power-saving states such as awake or doze. By indicating the status of the device that allows access, the status indicates whether the AMP STA in power-saving mode needs to respond to the identification frame. That is, this field can characterize whether the identification frame has the ability to wake up.

[0107] Bandwidth information bw is used to indicate the requested or allocated bandwidth; maximum identification slot number (max slot number (optional)) is used to indicate the maximum number of times the identification message can be resent if the identification feedback message is not received, i.e., the maximum number of optional identification slots when no feedback is received from any AMP STA.

[0108] The ID assignment mode indicates the method of ID assignment. This ID assignment mode can be represented by a 1-bit value, such as 0 and 1, as shown in Table 1 below:

[0109] It should be noted that the overall AMP identification parameters can be directly indicated in the message through fields or elements. Elements include the Target Wake Times (TWT) element or elements related to AMP identification.

[0110] As shown in Figure 1-1a, before the start of the periodic identification process, the reader can carry TWT elements in a broadcast frame (i.e., the first broadcast message) to indicate the overall AMP identification parameters to the legacy STAs and AMP STAs within the BSS. These parameters include time parameters, the objects participating in the broadcast TWT, and the number of times the identification slot is repeated during the identification process. The type information in the overall AMP identification parameters indicates that the requested or allowed access device type is AMP STA, while legacy STAs are not allowed to access the channel in their indicated identify protection window. After the first reader broadcasts the first broadcast message, it periodically sends identification messages. These identification messages include the time window for the current identification slot. Within this time window, the periodic AMP identification process is performed, with the interval between each AMP identification process being the Identify interval.

[0111] 2. When the first reader's identification process is non-periodic, before broadcasting the first broadcast message, it competes for the identification availability window used to transmit the first broadcast message. The first broadcast message is the first identification message transmitted within the identification availability window. The first broadcast message includes the time parameter of the current identification slot and the overall AMP identification parameters. Subsequent identification messages sent within the identification availability window include the time parameters of the subsequent identification slots. That is, when identification is performed in a non-periodic repetitive manner, after each competition for the identification availability window, the first identification message broadcast by the first reader indicates not only the time parameter of the identification slot but also the parameters of the overall AMP identification process. Subsequent identification messages only need to indicate the information of the identification slot, as shown in Figure 1-1b. Similarly, legacy STAs are not allowed to access the channel in their indicated identify protection window. Subsequent identification messages only include the time parameter of the subsequent identification slot. In this embodiment, the time parameter of the identification slot may include one or more of the following information:

[0112] Identify start indicates the start time of the identification phase, i.e., the start time of the first identification slot;

[0113] Identification duration, used to indicate the overall duration of the identification phase, is indicated in a certain time unit to indicate the overall duration of the identification phase;

[0114] Identify slot number, which indicates the number of times the identification message is repeatedly sent, i.e., the number of slots identified in this identification process;

[0115] Identify slot duration; Identify slot repetition interval.

[0116] The maximum number of identification slots (Max slot number) indicates the maximum number of times the identification message can be resent if the identification feedback message is not received; that is, the maximum number of selectable identification slots.

[0117] It should be noted that in Figures 1-1a and 1-1b, the first broadcast message or identification message can be a control frame such as POLL, PS-POLL, Trigger, or a management frame such as beacon, S1G beacon, Authentication, probe, or a WUR class1 frame such as WUR beacon, WUR discovery. No specific limitation is made here.

[0118] In summary, the first reader decides for itself whether the recognition process is periodic or non-periodic. It can indicate the relevant parameters of the recognition process through the first broadcast message before the periodic recognition process, or it can indicate not only the time parameters of the current recognition slot, but also the overall AMP recognition parameters through the first recognition message broadcast after each competition for an available window.

[0119] 102a. Each AMP STA sends an identification message feedback to the first reader;

[0120] In step 101a, when the first reader periodically performs the identification process, each AMP STA receives a first broadcast message including the overall AMP identification parameters and then performs periodic identification; when the first reader broadcasts identification messages through competition for the identification available window, that is, when the identification process is performed non-periodically, the first identification message received by each AMP STA within the window includes the overall AMP identification parameters and the time parameters of the current identification slot, and subsequent identification messages only include the time parameters of the subsequent identification slot.

[0121] After receiving the first broadcast message from the first reader, the AMP STA in the IDless state sends an identification feedback message to the first reader. In this embodiment, the IDless state includes an unassigned ID state, or an ID state with an ID but without an ID assigned by the first reader. Specifically, when the AMP STA is in the unassigned ID state, it responds to the identification message and receives and stores the identification information of the first reader and the ID assigned by the first reader. When the AMP STA is in the ID state, after receiving the identification message from the first reader, it searches for an ID corresponding to the identification information of the first reader in the locally or cloud-stored IDs based on the identification information of the first reader also carried in the identification message. If no ID is found, the AMP STA is considered to be in the ID state with an ID but without an ID assigned by the first reader, and responds to the identification message.

[0122] When the AMP STA is in a state where it has an ID but no first reader has assigned an ID, the identification feedback message also includes an ID modification indication and the current ID. The ID modification indication is used to indicate whether modifying the current ID is allowed. It should be noted that the identification information of the first reader includes, but is not limited to, one or more of the following: the identifier of the first reader, the MAC address of the first reader, and the Basic Service Set Identifier (BSSID) of the first reader.

[0123] This can be understood as follows: after an AMP STA is initially assigned an ID, it needs to store identifiers such as the MAC address of the reader that assigned that ID. Upon receiving an identification message from the first reader, the AMP STA uses the identifiers such as the MAC address of the first reader carried in the identification message to determine whether the identification message comes from a new reader. If the identification message comes from a new reader, the AMP STA sends a feedback message, carrying the following fields in the feedback message:

[0124] ID info: Indicates the ID that the current AMP STA has been assigned;

[0125] ID request: Indicates whether the current AMP STA accepts a new reader modifying its existing ID, as shown in the following example:

[0126] During the slot identification period, the AMP STA searches its local or cloud storage for the reader identifier information indicated in the identification message to determine if it has been assigned an ID by the current reader. If not, it sends an identification feedback message to the reader using methods such as Time Division Multiple Access (TDMA) or Frequency Division Multiple Access (FDMA) (e.g., based on the AC_BK channel access level). Optionally, this feedback message carries the AMP STA's own capability information, location information, and other device information. Upon receiving feedback from the AMP STA, the AP counts the IDs and assigns them IDs for subsequent grouping and access restrictions. By determining whether the identification message originates from a new reader and providing feedback on existing IDs and whether the modification of the new reader's ID is accepted, the AMP STA does not need to store every ID and reader identifier, saving storage space.

[0127] 103a. The first reader sends an identifier allocation message to each AMP STA;

[0128] 104a and AMP STA switch to low power consumption mode.

[0129] After the first reader has collected a certain number of AMP STAs, it sends an identifier allocation message to each AMP STA to perform ID allocation. For the ID allocation step, the first reader allocates IDs based on the information reported by the AMP STAs that successfully responded during the identification process, using the following two ID allocation methods:

[0130] The identification feedback message of 1AMP STA does not carry device information, but only serves as an indication that AMP STA "exists and requests ID allocation" in this transmission area. Therefore, the identification process is simply a counting process, and IDs can be allocated in the order of arrival.

[0131] ② The identification feedback message from the AMP STA carries device information, such as location, PHY layer capabilities (including data rate, MCS, BW, antenna array, etc.), data type, charging-related capabilities, etc. The first reader can then group and assign IDs based on the device information. For example, AMP STAs that can collect similar data or AMP STAs in the same area can be grouped together, and their group IDs can be indicated in the following way:

[0132] 1. The different bits of its ID can indicate not only the AMP STA itself, but also its group identifier; that is, the ID includes both the AMP STA itself and the group identifier.

[0133] 2. The ID field indicates the ID assigned to the AMP STA, and the group ID field indicates its group identifier. That is, the AMP STA's own identifier and the group identifier are different fields, which are carried in the ID assignment message.

[0134] The above details the IDs assigned by the first reader and the indication method. Regarding how to assign IDs to each AMP STA, IDs can be assigned immediately after each identification step, or they can be assigned uniformly after multiple identifications. That is, ID allocation methods include sequential allocation and uniform allocation. Please refer to Figure 1-2a, which provides a possible flowchart of reader-based AMP STA identification and ID allocation. The overall process includes two steps: identification and ID allocation. In the identification step, the reader broadcasts an authentication frame, indicating the duration information of each identification slot for the AMP STA. The ID allocation step, as shown in Figure 1-2a, is completed immediately after each identification.

[0135] In this embodiment, the identification protection window can be a transmission opportunity (TXOP), a service period (SP) containing multiple TXOPs, or a time period defined by the reader. Please refer to Figure 1-2b, which illustrates a timing example of sequential allocation using TXOP or SP as the identification window. In Figure 1-2b, after each identification slot within a TXOP or SP (including identification slot 1 to identification slot n), an ID is assigned to the AMP STA. AMP STAs with assigned IDs will not participate in the next identification slot. Furthermore, if the reader does not receive any feedback from any AMP STA in a certain identification slot, it can directly send the next identification message. Throughout the identify protection window, the reader independently decides the number of times the identification slot is repeated. Since the reader's feedback to AMP STAs is unpredictable, the reader needs to reserve time for the final ID allocation based on the identify protection window. That is, after each identification frame is sent, the remaining identify protection window is assessed. If it is insufficient to support a complete identification slot and ID allocation, the reader can prematurely end the current identify protection window and broadcast the removal of access restrictions on other non-AMP non-AP STAs. It should be noted that the remaining available identification window can be determined based on the identification message, the identifier allocation message, and the available identification window.

[0136] To reduce the energy consumption of AMP STAs in the identification and allocation process, please refer to Figure 1-3a, which provides a possible message interaction diagram for sequential ID allocation. In Figure 1-3a, after each identification step, time is reserved for ID allocation. ID allocation is performed on the AMP STA that successfully sent the identification feedback message. The STA with the allocated ID switches to a low-energy state and does not need to provide feedback on the identification frame again in the next identification slot. The advantage of this method is that ID allocation is performed immediately after each AMP STA is identified. The AMP STA that successfully receives the ID allocation message can immediately switch from the awake state to the doze / sleep state, without needing to keep TX and / or RX enabled for the entire protection period, thus further saving energy. The reader does not need to wait for the AMP STA's ACK after sending the ID allocation message. If the AMP STA does not successfully receive the allocated ID, it will naturally participate in the next identification slot.

[0137] In this application, the low-power state can be any of the following states: the transmitter and / or receiver of the device are turned off; switching to the sleep or doze state defined by the IEEE 802.11 series of standards; the primary communication radio (PCR) is turned off; no more receiving and / or transmitting radio frames is taken; or switching to the low data rate radio (LDR) state is taken. Compared to the conventional wireless transmission state, the LDR state can be characterized by lower transmission rates, lower data throughput, simpler coding and modulation schemes, and other PHY parameters. For example, in the embodiments of this application, when the ID allocation mode is the per-ID allocation mode, the low-power state means that messages are no longer received and / or transmitted within the available identification window.

[0138] After an AMP STA is assigned an ID, the reader can use that ID for group triggering, polling, or access restriction during subsequent data transmission, thereby preventing congestion caused by a large number of devices accessing the channel simultaneously. Once all IDs have been assigned, the reader can update the AMP STA IDs. That is, the reader should trigger or poll AMP STAs when no IDs can be assigned. If the reader does not receive a response from an AMP STA with a particular ID after triggering or polling it n times, the reader can reclaim that ID and reassign it to other AMP STAs. Optionally, besides the case where no IDs can be assigned, the reader can also initiate ID updates independently under the following conditions, including but not limited to the following:

[0139] Condition 1: The reader is in an idle state, that is, the reader has no wireless transmission task for a period of time;

[0140] Condition 2: The AMP STA is inactive, meaning that the reader has no data transfer task with the AMP STA for a period of time;

[0141] Correspondingly, for AMP STA, it can determine whether an ID has been revoked or is invalid through, but not limited to, the following methods:

[0142] Method 1: For IDs that are not lifelong, the reader indicates the ID's validity period in the ID allocation message during ID allocation. After the ID expires, the AMP STA must re-evaluate the identification message and obtain a new ID; or,

[0143] Method 2: For non-lifelong IDs, after ID allocation, the AMP STA performs a decision-making process. If no trigger, wake-up, or polling frame is received from the reader after a certain period of time, the AMP STA considers that the reader has left the current transmission area, determines that the ID is invalid, and re-participates in the identification and ID allocation process to obtain a new ID.

[0144] Method 3: After ID allocation, the reader will broadcast the currently allocated IDs and their corresponding AMP STA address list. When the AMP STA queries the list, it will determine whether its own ID has been revoked and reallocated.

[0145] Furthermore, considering scenarios where multiple readers initiate identification in practical applications—for example, a new reader entering the current transmission range or an AMP STA moving to a new transmission area—it's understandable that when different readers initiate AMP identification and ID allocation, the allocated ID is unique to the current reader and AMP STA. That is, after receiving the allocated ID, the AMP STA stores the current ID along with its source reader identification information, such as the reader's MAC address. When a reader sends an identification message, the AMP STA uses the reader identification information carried in the identification frame to determine whether it has already obtained the ID allocated by that reader and decides whether to respond to the identification message sent by that reader. If it has already obtained the ID, it does not need to respond to the identification message sent by that reader.

[0146] If the ID assigned by the reader is not obtained, the AMP STA responds to the identification message and can store the ID assigned by the reader and the reader's identification information accordingly. That is, the ID of the AMP STA can be different for different readers, so that ID conflicts will not occur between different readers. All readers are triggered and scheduled through their own assigned IDs.

[0147] Alternatively, the AMP STA can respond to the identification message, carrying an ID modification indication and the current ID. The ID modification indication specifies whether modifying the current ID is allowed. If allowed, the reader assigns a new ID to the AMP STA, and the AMP STA updates the ID. If not allowed, the reader does not need to assign an ID to the AMP STA. This way, the AMP STA does not need to store every ID and reader identification information, saving both the AMP STA's storage space and the reader's ID allocation resources.

[0148] In summary, for environmental IoT application scenarios, to avoid channel contention and transmission conflicts caused by the simultaneous access of a large number of devices, this application designs a method and system for identification and ID allocation between a controller or reader and an AMP STA with extremely low power consumption and extremely low complexity. This includes device identification, device counting, device ID allocation and / or device grouping, and ID updating. The reader periodically or non-periodically sends broadcast messages to allocate periodic identification available windows to the AMP STA, and performs preliminary time-division, frequency-division, space-division, or a combination of these transmission resources through broadcast messages. Based on the identification feedback messages from the AMP STA, the reader identifies and counts the AMP STA, optionally obtains the AMP STA's device information, and completes the allocation of identifiers and / or indication of grouping information through ID allocation frames. Specifically, by allocating protection windows, transmission opportunities, or service periods through a controller or reader, this application supports STAs without scanning or channel contention capabilities to participate in authentication, identification, and ID allocation. Unlike the IEEE 802.11 legacy authentication association process, it eliminates the need for complex request and feedback procedures; the AMP STA only needs to participate in a single frame interaction to acquire device information and obtain its ID. This enables the reader to periodically identify, count, and allocate IDs for AMP STAs within the transmission range, facilitating subsequent transmission scheduling and access restrictions. For AMP STAs with mobility within the transmission range, this application also supports non-periodic or periodic identification and ID updates.

[0149] Please refer to Figure 1b, which is a flowchart of a possible identifier allocation method based on a unified allocation mode provided in this application, including the following steps:

[0150] 101b. The first reader broadcasts and sends a first broadcast message;

[0151] 102b. Each AMP STA sends an identification message feedback to the first reader;

[0152] It should be noted that steps 101b to 102b are similar to steps 101a to 102a in Figure 1a, and will not be described in detail here.

[0153] 103b. The first reader sends an ACK message to each AMP STA;

[0154] 104b. Each AMP STA switches to low-power mode;

[0155] In this process, a unified allocation mode is adopted. After each AMP STA sends an identification message feedback to the first reader, the first reader sends an ACK message to each AMP STA so that the AMP STA no longer feeds back the identification message and switches to a low-power state. At this time, the low-power state means that only the identifier allocation message is received within the identification available window.

[0156] Figure 1-2c shows a possible flowchart of AMP STA identification and ID allocation based on a reader. Within the identification available window shown in Figure 1-2c, after all identification steps are completed, ID allocation is performed uniformly via broadcast, multicast, or unicast. Referring to Figure 1-2d, which uses TXOP or SP as examples of identification windows, a timing example of unified allocation is shown. In Figure 1-2d, the reader can perform unified ID allocation to AMP STAs after multiple identification slots. To avoid AMP STAs repeatedly participating in feedback in each identification slot, the AMP STA waits for an ACK message from the first reader after successfully sending a feedback message. Furthermore, within the entire identify protection window, the reader independently decides the number of times an identification slot is repeated and reserves time for the final ID allocation. Optionally, if multiple identification messages are sent without receiving feedback from the AMP STA, no further ID allocation time needs to be reserved; the current identify protection window is ended early, and the access restrictions on other non-AMP non-AP STAs are lifted via broadcast.

[0157] To reduce the energy consumption of AMP STA in the identification and allocation process, please refer to Figure 1-3b, which provides a message interaction diagram for one possible unified ID allocation. When the ID allocation method is unified allocation, the reader decides the number of times the authentication step is repeated, which can be done in the following two ways:

[0158] 1. Regardless of whether a response is received from the AMP STA within the identify protection window, repeat the identification steps multiple times. After collecting all successfully received AMP STA information, assign IDs uniformly.

[0159] 2. Alternatively, within the identify protection window, a maximum number of authentication repetitions (n) can be set after no response has been received from the AMP STA. If no feedback is received from the AMP STA after n repetitions, the identify protection window can be terminated early.

[0160] In the method shown in Figure 1-3b, the AP needs to send an ACK to the AMP STA that successfully sent authentication feedback within each authentication slot. This allows the AMP STA to confirm that it has been successfully counted in the current authentication slot. Upon receiving the ACK, the AMP STA switches to a low-power state and no longer participates in the next authentication slot, without needing to provide feedback for the next identification message. The advantage of this method is that it eliminates the need for ID allocation after each identification step. Only one unified ID allocation period is required within the identification protection window. Within the same identification protection window, the authentication steps can be repeated more times, allowing for more efficient identification of more AMP STAs within each authentication and ID allocation identification protection window.

[0161] In this application, the low-power state can be any of the following states: the transmitter and / or receiver of the device are turned off; switching to the sleep or doze state defined by the IEEE 802.11 series of standards; the primary communication radio (PCR) is turned off; no longer receiving and / or transmitting radio frames; switching to the low data rate radio (LDR) state, where, compared to the conventional wireless transmission state, the LDR state may use lower transmission rates, lower data throughput, simpler coding and modulation schemes, and other PHY parameters for transmission. For example, in the embodiments of this application, when the ID allocation mode is the unified allocation mode, the low-power state is to only receive identifier allocation messages in the available identification window.

[0162] 105b. The first reader sends an identifier allocation message to each AMP STA.

[0163] It should be noted that step 105b is similar to step 104a in Figure 1a, and the details will not be repeated here.

[0164] After describing the two scenarios in scenario A above, we will now describe the controller identification and allocation process in scenario B.

[0165] Scenario B: The main components in the identification allocation process include the reader, controller, and AMP STA. Please refer to Figure 2a, a flowchart of a possible identification allocation method provided in this application, including the following steps:

[0166] 201. The reader broadcasts an identification message;

[0167] 202. Each AMP STA sends an identification feedback message to the reader;

[0168] 203. Each AMP STA receives the ACK message sent by the reader;

[0169] 204. Each AMP STA switches to low-power mode;

[0170] 205. The controller receives the identification reporting message sent by the reader;

[0171] 206. The controller sends an identifier assignment message to the reader;

[0172] 207. The reader forwards the ID of each AMP STA to each AMP STA.

[0173] Unlike Scenario A, Scenario B introduces a controller, which is a functional entity that manages the process. In practical applications, the controller is often an AP (Application Processor), and the reader is a STA (Stationary Asynchronous Unit) that has completed the authentication association process with the controller. For AMP STA identification, authentication is similarly performed either non-periodicly or periodically. It should be noted that the ID allocation modes in Scenario A include unified allocation and successive allocation modes, while in Scenario B, the reader collects information from each AMP STA after passing through multiple slots and reports it to the controller. The controller then uniformly allocates IDs to each AMP STA. Therefore, the ID allocation mode in Scenario B is the unified allocation mode, which is similar to the steps in the unified allocation mode in Scenario A. After receiving the identification feedback message from each AMP STA, the reader sends an ACK message to each AMP STA and counts the results. Specific details will not be elaborated here.

[0174] In addition, in this scenario, AMP recognition can be initiated in the following ways:

[0175] I. Periodic Authentication Method: As shown in Figure 2b, this application provides a flowchart of AMP STA identification and ID allocation based on a controller and a reader. The reader initiates an identification request to the controller, and the controller sends feedback to it. The request and feedback carry parameters related to the AMP STA identification process, such as the identify protection window, identify interval, and maximum number of identification attempts (upper limit of the number of identification slots) specified by the controller. The reader only completes the collection and reporting of AMP STA information during the identification process. The controller performs ID allocation and subsequent grouping and grouping restrictions, similar to the reader's ID allocation and subsequent grouping and grouping restrictions in scenario A, which will not be elaborated here. After receiving the instruction information from the controller, the reader further broadcasts, multicasts, or unicasts notifications to the AMP STA.

[0176] Alternatively, the controller can directly instruct the reader to begin identifying the AMP STA and specify relevant parameters for the identification process, such as the identify protection window, identify interval, and maximum number of identification attempts (the upper limit of the number of identification slots). Specifically, as shown in Figure 2c, which is a possible timing diagram of ID allocation for reader-initiated identification provided by an embodiment of this application, the reader sends an identification request message to the controller. Before receiving the identification reporting message sent by the reader, the controller also receives the identification request message sent by the reader to request an available identification window for identifying and allocating IDs for the AMP STA. Based on this identification request message, the controller broadcasts a first broadcast message to instruct the identification process. The first broadcast message includes overall AMP identification parameters and, optionally, may also indicate relevant parameters for the AMP identification process. These parameters are the same as those defined in scenario A and will not be repeated here. After receiving the first broadcast message, at a set interval (e.g., SIFS), the reader sends a second broadcast message indicating the relevant parameters for identifying the slot and receives feedback from the AMP STA. The subsequent identification and ID allocation steps are omitted in the diagram. Similarly, non-AMP non-AP STAs are not allowed to access the channel during the Identify protection window. The identification request message is optional, as the controller can also directly initiate the identification process. This process can be periodic, similar to scenario A. In the first broadcast message, relevant parameters can be indicated by broadcasting TWT elements or by direct indication. The first broadcast message is a trigger frame, and the second broadcast message can be a control frame such as POLL, PS-POLL, or Trigger; a management frame such as beacon, S1G beacon, Authentication, or probe; or a WUR class 1 frame such as WUR beacon or WUR discovery. Specific details are not limited here.

[0177] It should be noted that when the controller is involved, the controller can also instruct the allocation of identification slots through the first broadcast message, including: instructing the time period for the reader to perform the identification phase; instructing the time period for each identification slot; and instructing the number of identification slots. Optionally, it can also indicate the maximum number of identification slots that can be repeated if no AMP STA response is received.

[0178] In the first broadcast message sent by the controller, in addition to the parameters related to the overall AMP recognition process, the message can also carry the time parameter for recognizing the slot. The content of the parameter is similar to the time parameter for recognizing the slot in scenario A, and will not be described in detail here. The time parameter for recognizing the slot can be indicated in the first broadcast message through fields or elements.

[0179] II. Non-periodic authentication method: The reader automatically competes for the TXOP or SP and begins to identify the AMP STA, independently deciding on relevant parameters for the identification process, such as specifying the identify protection window and the maximum number of identification attempts (the upper limit of the number of identification slots). The steps are similar to those in scenario A and will not be repeated here.

[0180] In summary, for the AMP recognition process in this scenario, when the controller is involved, the reader can initiate the recognition process on its own, or it can initiate the recognition process by requesting the controller or receiving instructions from the controller.

[0181] It should be noted that, as shown in Figure 2d, which is a possible overall timing example of an identification process based on a controller and a reader, within the entire identify protection window, depending on the different authentication initiation methods, there may be an authentication indication time phase. After multiple authentication slots, in the reporting phase, the reader reports the received AMP STA information to the controller. In the ID allocation phase, the controller allocates IDs and groups and sends them to the reader, which then notifies the AMP STA. For ID allocation, similar to scenario A, the controller performs ID allocation, grouping, and other operations based on the information it receives from the AMP STA.

[0182] As shown in Figure 2a, when the controller participates in the identification process, it completes ID allocation. The reader collects certain AMP STA information during the identification step and reports it to the controller. That is, the controller's ID allocation includes receiving AMP STA information and performing ID allocation. Specifically, the reader sends an identification reporting message, i.e., an AMP STA info report frame, to the controller. After receiving this reporting message, the controller sends an ID allocation message back to the reader. The reader then forwards the ID allocation message to the AMP STA via broadcast, multicast, or unicast. The information fields contained in the ID allocation message are similar to those in scenario A, and will not be elaborated further here.

[0183] The AMP STA info report frame sent by the reader may include the following fields:

[0184] Info flag: Indicates whether feedback was received from AMP STA in this identification phase, as shown in the table below:

[0185] After the info flag indicates that feedback has been received from the AMP STA, an AMP STA info field exists:

[0186] AMP STA info: Indicates the information carried by the AMP STA in the identification feedback frame received by the reader, which can be indicated by a list, bitmap, etc.

[0187] In summary, similar to the reader in Scenario A, when the controller initiates AMP identification, it can indicate the relevant parameters for the identification phase, reporting phase, and ID allocation phase via a first broadcast message. All processes are completed within the identify protection window. Optionally, if the identify protection window closes before reporting and ID allocation are completed, or if the controller prematurely terminates the available window or the identify protection window is insufficient to complete reporting and ID allocation, the reader and controller can compete again to initiate transmission, completing reporting and ID allocation. The reader then broadcasts the ID allocation result to the AMP STA. The only difference in the ID allocation method is that the controller instructs the reader to allocate the result, and the reader then notifies the AMP STA; further details are omitted.

[0188] When no available ID is assigned to a new AMP STA, the controller similarly instructs the reader to initiate polling or triggering of the AMP STA. For AMP STAs that fail to respond multiple times, their IDs are reclaimed and reassigned. Optionally, even if the ID pool is not full, the controller can also decide to update the IDs independently. It should be noted that with the controller involved, even with multiple readers, the ID of each AMP STA is no longer associated with a single reader; instead, it is allocated centrally by the controller, preventing ID conflicts across multiple readers. During the data transmission phase after identification, the controller designates a specific reader to poll or trigger the AMP STA; that is, when the controller is unique, the AMP STA ID is also unique.

[0189] The figures above illustrate in detail the identifier allocation method and identifier acquisition method provided in the embodiments of this application. Please refer to Figure 3, which is a storage diagram of the wireless communication device in the embodiments of this application. The storage medium 20 of the wireless communication device in the embodiments of this application stores instruction / program data 21. When the instruction / program data 21 is executed, it implements the method provided by any embodiment of the communication method of this application and any non-conflicting combination thereof. The instruction / program data 21 can be formed into a program file and stored in the storage medium 20 in the form of a software product, so that a computer device (which may be a personal computer, server, or network device, etc.) or processor can execute all or part of the steps of the methods of various embodiments of this application. The aforementioned storage medium 20 includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, or terminal devices such as computers, servers, mobile phones, and tablets.

[0190] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0191] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0192] The above are merely embodiments of this application and do not limit the scope of this patent application. Any equivalent structural or procedural changes made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of this application.

[0193] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0194] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0195] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0196] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0197] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0198] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0199] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0200] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0201] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0202] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0203] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for obtaining an identifier, used in an AMP STA device, characterized in that, include: Receive the first broadcast message sent by the first reader; When the AMP STA is in an unidentified ID state, an identification feedback message is sent to the first reader; Receive the identifier allocation message carrying the ID sent by the first reader and switch to low-power mode. or, Receive the ACK message sent by the first reader and switch to a low-power state to receive the identifier allocation message.

2. The method according to claim 1, characterized in that, The first broadcast message includes overall AMP identification parameters.

3. The method according to claim 2, characterized in that, The overall AMP identification parameters include, but are not limited to, one or more of the following information: The available window indicates the time period for device identification; The recognition interval is used to indicate the interval at which the AMP recognition process is repeated periodically. Type information, used to indicate the type of device requesting or permitted access; Status information, used to indicate the status of the device requesting or allowing access; Bandwidth information, used to indicate the requested or allocated bandwidth; The maximum number of identification slots indicates the maximum number of times the identification message can be retransmitted if the identification feedback message is not received. ID allocation mode is used to indicate the method of ID allocation.

4. The method according to claim 3, characterized in that, The overall AMP identification parameters are indicated at least by fields or elements in the first broadcast message, including broadcast TWT elements or elements related to AMP identification.

5. The method according to claim 3, characterized in that, When the overall AMP identification parameters indicate that the AMP identification process is periodic identification, after receiving the first broadcast message broadcast by the first reader, the method further includes: Receive the identification message broadcast by the first reader, the identification message including the time window of the current identification slot.

6. The method according to claim 3, characterized in that, When the overall AMP recognition parameters indicate that the AMP recognition process is aperiodic, the first broadcast message is the first recognition message transmitted within the available recognition window. The first broadcast message includes the time parameter of the current recognition slot and the overall AMP recognition parameters. The subsequent identification messages transmitted within the available identification window include the time parameters of the subsequent identification slot.

7. The method according to claim 1, characterized in that, The state without an ID includes either an unassigned ID state or an ID state where an ID exists but no first reader assigns an ID.

8. The method according to claim 7, characterized in that, The identification message also includes the identification information of the first reader, and the method further includes: Based on the identification information of the first reader, search the locally or cloud-stored IDs for an ID that corresponds to the identification information of the first reader. If it does not exist, then the AMP STA is in the state of having an ID but no first reader assigning an ID.

9. The method according to claim 8, characterized in that, When in the state where there is an ID but no first reader assigns an ID. The identification feedback message also includes an ID modification indication and a current ID, wherein the ID modification indication is used to indicate whether modification of the current ID is allowed; or, After receiving the identifier allocation message carrying the ID sent by the first reader, the method further includes: The corresponding storage includes the ID assigned to the first reader and the identification information of the first reader, with the identification information of the first reader being contained in the identification assignment message.

10. The method according to claim 1, characterized in that, The identification feedback message also includes device information, so that the first reader can group according to the device information. The device information includes, but is not limited to, one or more of the following: location information, data type, charging-related capabilities and / or PHY capability information.

11. The method according to claim 10, characterized in that, The identifier allocation message also includes the corresponding group identifier.

12. The method according to claim 1, characterized in that, The low-energy state includes at least one of the following states: no longer receiving and / or sending messages in the identification available window, or only receiving identification allocation messages in the identification available window.

13. The method according to claim 12, characterized in that, When the ID allocation mode is the sequential allocation mode, receiving the identifier allocation message carrying the ID sent by the first reader and switching to the low-power state includes: Receive the identifier allocation message carrying the ID sent by the first reader and switch to no longer receive and / or send messages during the identification availability window.

14. The method according to claim 12, characterized in that, When the ID allocation mode is a unified allocation mode, receiving the ACK message sent by the first reader and switching to a low-power state includes: Receive the ACK message sent by the first reader and switch to receiving only the identifier allocation message within the identification availability window.

15. The method according to claim 1, characterized in that, The identifier allocation message also includes the identifier information of the first reader, which includes, but is not limited to, at least one of the following: the identifier of the first reader, the MACADDRESS address of the first reader, and the Basic Service Set Identifier (BSSID) of the first reader.

16. The method according to claim 15, characterized in that, After the first reader receives the identifier allocation message carrying the ID sent by the first reader, the method further includes: The corresponding storage includes the ID assigned by the first reader and the identification information of the first reader.

17. The method according to claim 1, characterized in that, The ID assignment message also includes the validity period of the ID, used to indicate that the ID is a non-lifelong ID.

18. The method according to claim 17, characterized in that, The method further includes: When the validity period of the ID expires, a new ID will be obtained.

19. The method according to claim 17, characterized in that, The method further includes: If no message is received from the first reader within a preset time, the ID is retrieved again.

20. The method according to claim 1, characterized in that, The method further includes: Receive the ID allocation list broadcast by the first reader, the ID allocation list including the allocated IDs and the corresponding AMP STA addresses; Query the ID allocation list to determine whether the corresponding ID has been revoked or reassigned.

21. An identifier allocation method for a first reader, characterized in that, include: The first broadcast message was sent. Receive identification feedback messages from each environmental power supply AMP station STA, and send an identification assignment message carrying an identification ID to each AMP STA.

22. The method according to claim 21, characterized in that, The first broadcast message includes overall AMP identification parameters.

23. The method according to claim 22, characterized in that, The overall AMP identification parameters include, but are not limited to, one or more of the following information: The available window indicates the time period for device identification; The recognition interval is used to indicate the interval at which the AMP recognition process is repeated periodically. Type information, used to indicate the type of device requesting or permitted access; Status information, used to indicate the status of the device requesting or allowing access; Bandwidth information, used to indicate the requested or allocated bandwidth; The maximum number of identification slots indicates the maximum number of times the identification message can be retransmitted if the identification feedback message is not received. ID allocation mode is used to indicate the method of ID allocation.

24. The method according to claim 23, characterized in that, The overall AMP identification parameters are indicated at least by fields or elements in the first broadcast message, including broadcast TWT elements or elements related to AMP identification.

25. The method according to claim 23, characterized in that, When the overall AMP identification parameters indicate that the AMP identification process is periodic, the method further includes, after the first broadcast message is sent: Identification messages are periodically broadcast, and these identification messages include the time window for the current identification slot.

26. The method according to claim 23, characterized in that, When the overall AMP identification parameters indicate that the AMP identification process is aperiodic, the method further includes, before the first broadcast message is sent: A competition identification available window is used to transmit the first broadcast message, wherein the first identification message transmitted within the identification available window includes the time parameter of the current identification slot and the overall AMP identification parameter, and the first identification message is the first broadcast message; The transmitted subsequent identification messages only include the time parameters of the subsequent identification slot.

27. The method according to claim 23, characterized in that, The identification feedback message also includes device messages for each AMP, which include, but are not limited to, one or more of the following: location information, data type, charging-related capabilities, and physical PHY layer capability information.

28. The method according to claim 27, characterized in that, After receiving the identification feedback messages sent by each AMP STA, the method further includes: The devices of each AMP STA are grouped according to their device messages, and an ID is assigned to each AMP STA. The identification and assignment message also includes the group identifier corresponding to each AMP STA.

29. The method according to claim 23, characterized in that, The method further includes: If no identification feedback message is received from any AMP STA within the identification available window, and the identification broadcast count is repeatedly sent to the maximum identification slot number, then the identification available window is terminated. Broadcast a de-restriction message, which indicates the removal of access restrictions on device types that were not requested or allowed to access during the duration of the identified available window.

30. The method according to claim 23, characterized in that, After the broadcast sends the first broadcast message, the method further includes: The remaining available identification windows are determined based on the identification message, the identifier allocation message, and the identification available windows. When the remaining time available for identification does not meet the preset condition, the available window for identification is terminated; Broadcast a de-restriction message, which indicates the removal of access restrictions on device types that were not requested or allowed to access during the duration of the identified available window.

31. The method according to claim 23, characterized in that, The ID allocation modes include individual allocation mode and unified allocation mode. The sequential allocation mode is used to indicate that ID allocation is performed after each slot is identified. The unified allocation mode is used to indicate that IDs are allocated uniformly after all identification slots have been completed.

32. The method according to claim 31, characterized in that, When the ID allocation mode is a unified allocation mode, after receiving the identification feedback message sent by the AMP STA, the method further includes: Send an ACK message to the AMP STA that has sent the identification feedback message, and store the identification feedback message.

33. The method according to claim 31, characterized in that, When the ID allocation mode is the individual allocation mode, the identifier allocation message is also used to instruct the AMP STA with the assigned ID not to provide identification feedback within the identification availability window.

34. The method according to claim 31, characterized in that, When the ID allocation mode is a unified allocation mode, sending the identifier allocation message carrying the identifier ID to each AMP STA includes: Each AMP STA is assigned a corresponding ID via unicast / broadcast / unicast.

35. The method according to claim 21, characterized in that, The identifier allocation message also includes identifier information of the first reader, which includes, but is not limited to, at least one of the following: The identifier of the first reader, the MACADDRESS address of the first reader, The Basic Service Set Identifier (BSSID) of the first reader.

36. The method according to claim 21, characterized in that, The identification feedback message received from the AMP STA includes: The system receives a first identification feedback message sent by the AMP STA. The first identification feedback message includes first ID information and an ID modification indication. The first ID information is the ID that the first AMP STA has been assigned, and the ID modification indication is used to indicate whether to accept ID modification.

37. The method according to claim 21, characterized in that, The method further includes: When the conditions for ID update are met, perform ID update.

38. The method according to claim 37, characterized in that, The conditions for ID updates include, but are not limited to, one or more of the following conditions: the number of allocated IDs exceeds a first preset value, the number of active IDs within a preset time period is less than a second preset value, and the reader is in an idle state.

39. The method according to claim 21, characterized in that, The ID includes lifelong IDs and non-lifelong IDs; When the ID is not a lifelong ID, the identifier allocation message also includes the validity period of the ID.

40. The method according to claim 39, characterized in that, The ID update includes: If the number of times an AMP STA with an assigned ID is triggered or polled exceeds a preset value, and no response is received from the AMP STA with the assigned ID, the assigned ID is reclaimed and reallocated. When an assigned ID is a non-lifelong ID and its validity period has expired, the assigned ID is reclaimed and redistributed.

41. The method according to claim 21, characterized in that, The method further includes: Broadcast ID allocation list, which includes allocated IDs and their corresponding AMP STA addresses.

42. An identifier allocation method for a reader, characterized in that, include: Broadcast the identification message; Receive identification feedback messages sent by each AMP STA; Send ACK messages to each AMP STA; Based on the identification feedback messages of each AMP STA, an identification reporting message is sent to the control device, wherein the control device is a device that has established an authentication association with the reading device; The control device receives the ID message assigned to each AMP STA and forwards it to each AMP STA.

43. The method according to claim 42, characterized in that, Before broadcasting the identification message, the method further includes: Send an identification request message to the control device to request an available identification window for AMP STA identification; Receive a first broadcast message fed back by the control device, the first broadcast message including overall AMP identification parameters; or, Receive the identification instruction message sent by the control device, which is used to instruct AMP STA identification to be performed; Receive the first broadcast message sent by the control device.

44. The method according to claim 43, characterized in that, The identification message also includes the time parameter for identifying the slot.

45. The method according to claim 43, characterized in that, Before broadcasting the identification message, the method further includes: A competition is set up to identify available windows, which are used to transmit the identification message, which includes overall AMP identification parameters and identification slot time parameters.

46. ​​The method according to claim 44 or 45, characterized in that, The time parameters for identifying the slot include, but are not limited to, one or more of the following: Identify the starting point, which indicates the start time of the identification phase; Identification duration, used to indicate the overall duration of the identification phase; The slot number is used to indicate the number of times the identification message is repeatedly sent; Identify the duration of the slot; Identify slot repetition intervals; The maximum number of identification slots indicates the maximum number of times the identification message can be resent if the identification feedback message is not received.

47. The method according to claim 46, characterized in that, The identification and reporting message includes a feedback indication, which indicates whether feedback has been received from each AMP STA during the identification duration.

48. The method according to claim 42, characterized in that, The method further includes: Receive the trigger indication message sent by the controller, and poll or trigger the AMP STA with the assigned ID; When the number of polls or triggers reaches a preset number, the assigned IDs of unresponsive AMP STAs are reclaimed.

49. An identifier allocation method for a controller, characterized in that, include: The reader receives an identification reporting message sent by the controller. The identification reporting message includes information about each AMP STA. The reader and the controller have established an authentication association. A identifier allocation message is sent to the reader, the identifier allocation message carrying the ID of each AMP STA, so that the reader forwards it to each AMP STA.

50. The method according to claim 49, characterized in that, Before receiving information from each AMP STA sent by the reader, the method further includes: Receive the identification request message sent by the reader, which is used to request the identification available window for AMP STA identification; In response to the identification request message, a first broadcast message is broadcast, the first broadcast message including the overall AMP identification parameters; or, Send an identification instruction message to the reader to instruct it to perform AMP STA identification; Broadcast the first broadcast message.

51. The method according to claim 50, characterized in that, The information for each AMP STA includes the device information for each AMP STA; Assigning IDs to each AMP STA includes: Grouping based on the device information of each AMP STA; Each AMP STA is assigned a corresponding ID based on the grouping information, and the ID includes a group identifier.

52. The method according to claim 50, characterized in that, The method further includes: When the conditions for ID update are met, perform ID update.

53. The method according to claim 52, characterized in that, The conditions for ID updates include, but are not limited to, one or more of the following conditions: the number of allocated IDs exceeds a first preset value, the number of active IDs within a preset time period is less than a second preset value, and the reader is in an idle state.

54. The method according to claim 53, characterized in that, The ID update includes: A trigger instruction message is sent to the reader to instruct the reader to trigger the AMP STA with the assigned ID in order to reclaim the assigned ID.

55. An identifier acquisition method for an AMP STA device, characterized in that, include: Receive the identification message broadcast by the reader; When the AMP STA is in an IDless state, an identification feedback message is sent to the reader; The system receives the ACK message sent by the reader and switches to a low-power state to receive the identifier allocation message carrying the ID sent by the first reader.

56. The method according to claim 55, characterized in that, The identification message includes overall AMP identification parameters and time parameters for identifying the slot; or... Before the identification message broadcast by the receiving reader, the method further includes: The receiver sends a first broadcast message, which includes the overall AMP identification parameters.

57. The method according to claim 56, characterized in that, The low-power state means receiving only the identifier allocation message within the identification available window, and the overall AMP identification parameters include information about the identification available window.

58. A wireless communication device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to perform the method as described in any one of claims 1 to 57.

Images