Message transmission method, sending device and receiving device
By carrying integrity protection information in MPDU format messages and using temporary keys for verification, the problem of insufficient integrity protection of message headers in the prior art is solved, and the security and reliability of data transmission are achieved.
Patent Information
- Application Number
- PCT/CN2024/115957
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-09-08
- Filing Date
- 2024-08-30
- Publication Date
- 2025-03-13
AI Technical Summary
The prior art has failed to effectively protect the integrity of the packet header in the Media Access Control Protocol Data Unit (MPDU) format, resulting in the susceptibility of important information to be tampered with by attackers.
By carrying integrity protection information in the message, the integrity of the message header is checked using paired temporary keys (CPTKs) or group temporary keys (CGTKs) to ensure the integrity of the message header.
Effectively prevent important information in the message header from being tampered with by the attacker and ensure the security and reliability of data transmission.
Smart Images

Figure CN2024115957_13032025_PF_FP_ABST
Abstract
Description
Message transmission method, sending device and receiving device
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 8, 2023, with application number 202311167963.6 and application name “A message transmission method, device and related equipment”, the entire contents of which are incorporated by reference into this application. Technical Field
[0003] The present application relates to the field of wireless communication technology, and in particular to a message transmission method, a sending device, and a receiving device. Background Art
[0004] With the development of wireless communication technology, more and more wireless communication devices support multi-link communication. Devices that support multi-link communication can be called multi-link devices (MLDs). Each multi-link device has multiple radio frequency modules, and two multi-link devices can communicate through multiple communication links.
[0005] Data that needs to be protected can be transmitted between two multi-link devices via messages in the medium access control protocol data unit (MAC protocol data unit) format. The medium access control protocol data unit can be called a MAC protocol data unit (MPDU).
[0006] Since the message header of the MPDU format message carries important information, the industry has not yet provided a corresponding solution on how to protect the integrity of the message header of the MPDU format message.
[0007] Summary of the Invention
[0008] The present application provides a message transmission method, a sending device, and a receiving device for protecting the integrity of a message header of a message in an MPDU format.
[0009] In a first aspect, the present application provides a message transmission method, performed by a sending device, the method comprising: generating a first message and sending the first message to a receiving device. The first message is a data frame message or a management frame message, the first message comprising a first message header in a media access control protocol data unit (MPDU) format and first integrity protection information; the first integrity protection information is used to perform an integrity check on the first message header.
[0010] In the message transmission method provided in an embodiment of the present application, a data frame message or a management frame message sent by a sending device to a receiving device carries first integrity protection information. The first integrity protection information is used to protect the integrity of the message header of the data frame message or the management frame message, thereby preventing important information carried in the message header from being tampered with by an attacker.
[0011] In an optional implementation, the first message is a unicast data frame message or a unicast management frame message, and the first integrity protection information is generated according to a control pairwise transient key CPTK of the unicast control frame message.
[0012] In the above implementation, reusing the CPTK of the unicast control frame message as the secret key of the unicast data frame message or the unicast management frame message can reduce the derivation and maintenance of the secret key and reduce the processing complexity when the sending device generates the first integrity protection information.
[0013] In another optional implementation, the first message is a multicast data frame message or a multicast management frame message, and the first integrity protection information is generated according to a control group temporary key CGTK of the multicast control frame message.
[0014] In the above implementation, reusing the CGTK of the unicast control frame message as the secret key of the multicast data frame message or the multicast management frame message can reduce the derivation and maintenance of the secret key and reduce the processing complexity when the sending device generates the first integrity protection information.
[0015] In an optional implementation, the first message further includes a first information indicator bit, wherein the first information indicator bit is used to indicate that the first message carries first integrity protection information, so that the receiving device verifies the first message header based on the first integrity protection information.
[0016] In an optional implementation, the first information indicator bit is a reserved bit in a Cipher Block Chaining Message Authentication Code Protocol frame header CCMP Header field of the first message.
[0017] In an optional implementation, the first integrity protection information includes a packet sequence number PN; if the first message is a retransmitted message, the PN in the first integrity protection information is configured according to a rule of increasing packet sequence numbers, so that the receiving device can determine whether the first message is a message replayed by an attacker based on the PN, thereby preventing replay attacks.
[0018] In an optional implementation, the sending device may further generate and send a second message, wherein the second message is a control frame message and includes second integrity protection information and a second information indicator bit, wherein the second information indicator bit is used to indicate that the second message carries the second integrity protection information.
[0019] In the above implementation, the second integrity protection information is added to the control frame message, and the second information indicator bit is set. Regardless of the type of control frame message, integrity protection can be performed to prevent important information carried in the control frame message from being tampered with by attackers.
[0020] In an optional implementation manner, the second information indicator bit is a designated field in a message header of the second message; or, the second information indicator bit is a reserved bit in a block acknowledgement request control BAR control field of the second message.
[0021] In second aspect, the present application provides a message transmission method, which is executed by a receiving device, and the method may include: receiving a first message sent by a sending device; the first message is a data frame message or a management frame message, and the first message includes a first message header in a media access control protocol data unit MPDU format and first integrity protection information; based on the first integrity protection information, performing an integrity check on the first message header.
[0022] In an optional implementation, the method may further include:
[0023] Receive a second message; the second message is a control frame message, the second message includes second integrity protection information and a second information indicator bit; the second information indicator bit is used to indicate that the second message carries the second integrity protection information; based on the second integrity protection information, perform an integrity check on the second message.
[0024] In a third aspect, the present application provides a message transmission method, which is performed by a sending device and may include:
[0025] Generate a second message; the second message is a control frame message, the second message includes second integrity protection information and a second information indicator bit; the second information indicator bit is used to indicate that the second message carries the second integrity protection information;
[0026] Send the second message.
[0027] In an optional implementation manner, the second information indicator bit is a designated field in a message header of the second message; or, the second information indicator bit is a reserved bit in a block acknowledgement request control BAR control field of the second message.
[0028] In a fourth aspect, the present application provides a message transmission method, which is performed by a receiving device. The method may include:
[0029] Receive a second message; the second message is a control frame message, the second message includes second integrity protection information and a second information indicator bit; the second information indicator bit is used to indicate that the second message carries the second integrity protection information;
[0030] Perform an integrity check on the second message based on the second integrity protection information.
[0031] In a fifth aspect, an embodiment of the present application provides a sending device, comprising a module for executing any one of the methods provided in the first aspect, or a module for executing any one of the methods provided in the third aspect.
[0032] In a sixth aspect, an embodiment of the present application provides a receiving device, comprising a module for executing any one of the methods provided in the second aspect, or a module for executing any one of the methods provided in the fourth aspect.
[0033] In the seventh aspect, an embodiment of the present application provides a sending device, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the computer program is executed by the processor, the processor implements any one of the methods provided in the first aspect or the third aspect.
[0034] In an eighth aspect, an embodiment of the present application provides a receiving device, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the computer program is executed by the processor, the processor implements any one of the methods provided in the second aspect or the fourth aspect.
[0035] In the ninth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute any one of the methods provided in the first, second, third or fourth aspects above.
[0036] In a tenth aspect, an embodiment of the present application provides a computer program product comprising computer-executable instructions, which are used to enable a computer to execute any one of the methods provided in the first, second, third or fourth aspects above.
[0037] The technical effects that can be achieved in any of the second to tenth aspects mentioned above can refer to the description of the beneficial effects in the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] FIG1 is a network architecture diagram of a wireless communication system provided in an embodiment of the present application;
[0039] FIG2 is a diagram illustrating an interaction between a sending device and a receiving device during a message transmission process provided by an embodiment of the present application;
[0040] FIG3 is a schematic diagram of a message format of a data frame message or a management frame message;
[0041] FIG4 is a schematic diagram of a message format of a data frame message or a management frame message provided in an embodiment of the present application;
[0042] FIG5 is a schematic diagram of a message format of a frame control field provided in an embodiment of the present application;
[0043] FIG6 is a schematic diagram of a CCMP frame header message format provided in an embodiment of the present application;
[0044] FIG7 is a flowchart of a first message generation process provided in an embodiment of the present application;
[0045] FIG8 is a flowchart of a receiving device processing a first message provided by an embodiment of the present application;
[0046] FIG9 is a schematic diagram of a correspondence between a key and a message type provided in an embodiment of the present application;
[0047] FIG10 is a schematic diagram of another correspondence between a key and a message type provided in an embodiment of the present application;
[0048] FIG11 is a diagram illustrating another interaction between a sending device and a receiving device during a message transmission process provided by an embodiment of the present application;
[0049] FIG12 is a schematic diagram of a message format of a control frame message provided in an embodiment of the present application;
[0050] FIG13 is a structural block diagram of a sending device provided in an embodiment of the present application;
[0051] FIG14 is a structural block diagram of a receiving device provided in an embodiment of the present application;
[0052] FIG15 is a schematic structural diagram of a sending device provided in an embodiment of the present application;
[0053] FIG16 is a schematic structural diagram of a receiving device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0054] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. The terms used in the implementation methods of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application.
[0055] Before introducing the specific solutions provided by the embodiments of the present application, some of the terms in the present application are explained to facilitate understanding by those skilled in the art, and the terms in the present application are not limited.
[0056] (1) Data frame: A message used to transmit data can be called a data frame message. Data frame messages can include unicast data frame messages and multicast data frame messages. The destination address of a unicast data frame message is a single target, that is, the receiving device of a unicast data frame message is uniquely determined. Multicast means that a sending device sends the same message to multiple receiving devices. The destination address of a multicast data frame message is a multicast address, which points to multiple receiving devices belonging to a group.
[0057] (2) Management frame: A message used to transmit management information between an access point device and a station device. Management frame messages can include unicast management frame messages and multicast management frame messages.
[0058] (3) Control frame message: A message used to transmit control signaling and assist data transmission can be called a control frame message. For example, a message used to transmit wake-up signaling can be called a control frame message. Control frame messages can include unicast control frame messages and multicast control frame messages.
[0059] In the embodiments of the present application, "multiple" refers to two or more. In view of this, in the embodiments of the present application, "multiple" can also be understood as "at least two". "At least one" can be understood as one or more, for example, one, two or more. For example, including at least one means including one, two or more, and does not limit which ones are included. For example, including at least one of A, B and C, then the included ones may be A, B, C, A and B, A and C, B and C, or A, B and C. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / ", unless otherwise specified, generally indicates that the previous and subsequent associated objects are in an "or" relationship.
[0060] Unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of the present application are used to distinguish multiple objects and are not used to limit the order, timing, priority or importance of multiple objects.
[0061] The message transmission method provided in the embodiments of the present application can be applied to a wireless communication network, for example, a wireless local area network. FIG1 shows a network architecture diagram of a wireless communication network. As shown in FIG1 , the wireless communication network may include an access point multi-link device (AP MLD) 100 and a non-access point multi-link device (non-AP MLD) 200. FIG1 shows only one AP MLD and one non-AP MLD. In other embodiments, the wireless communication network may include multiple AP MLDs and multiple non-AP MLDs.
[0062] The non-AP MLD200 can be a station (STA) multi-link device, such as a base station. A base station can be understood as a device deployed in a wireless access network to provide wireless communication functions for terminals. For example, it can be a base station (gNodeB or gNB) that meets the 5G standard. A gNB can include various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, and vehicle-mounted devices. A gNB can also be a transmission and reception point (TRP) or a transmission measurement function (TMF). A gNB can include a central unit (CU) and a distributed unit (DU) integrated into the gNB.
[0063] The AP MLD 100 may be a user terminal device, such as a wireless modem, or a mobile station (MS) connected to a wireless modem, a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA), a tablet computer, a wireless modem, a handset, a laptop computer, a machine type communication (MTC) terminal, etc.
[0064] Each AP MLD may include multiple radio modules. For example, AP MLD 100 may include radio modules AP0 and AP1. Each non-AP MLD may include multiple radio modules. For example, non-AP MLD 200 may include radio modules STA0 and STA1. The communication link formed between radio modules AP0 and STA0 can be called link0, and the communication link formed between radio modules AP1 and STA1 can be called link1. That is, the communication links between AP MLD 100 and non-AP MLD 200 include at least link0 and link1. In other words, multi-link devices in a wireless communication network can communicate via multiple communication links. Each communication link corresponding to each multi-link device has a MAC address in the lower MAC (LMAC) sublayer of the MLD. The MAC address corresponding to each communication link can be called a link address. In addition, each multi-link device also has a MAC address in the upper MAC (UMAC) sublayer of the MLD. The MAC address corresponding to the multi-link device can be called an MLD MAC address.
[0065] Multi-link devices can transmit data that needs to be protected through messages in the MPDU format. In order to ensure the integrity of the message header in the MPDU format, an embodiment of the present application provides a message transmission method. Figure 2 shows a flow chart of the interaction between a sending device and a receiving device during the message transmission process. Among them, the sending device and the receiving device are both multi-link devices. For example, the sending device can be the AP MLD100 shown in Figure 1, and the receiving device can be the non-AP MLD200 shown in Figure 1; or, the sending device can be the non-AP MLD200 shown in Figure 1, and the receiving device can be the AP MLD100 shown in Figure 1. As shown in Figure 2, the message transmission process may include the following steps:
[0066] S201: The sending device generates message A.
[0067] Message A can be a unicast data frame or a unicast management frame. For example, when a transmitting device needs to send data to a receiving device, it can generate a unicast data frame; when a transmitting device needs to send management information to a receiving device, it can generate a unicast management frame. Message A can also be a retransmitted unicast data frame or a unicast management frame, both of which can use the MPDU format.
[0068] The message format of a unicast data frame message or a unicast management frame message in the related art is shown in FIG3 , and may include a MAC frame header, a frame body, and a frame check sequence (FCS). The frame body is used to carry the data or management information to be transmitted, and the FCS is used to verify the data or management information. The MAC frame header may be referred to as a message header in the MPDU format. The MAC frame header may include the following fields: frame control, duration, address 1, address 2, address 3, sequence control, QoS control, and HT control. The address 1 field is used to indicate the receiver address (RA), that is, the link address corresponding to the receiving device. The address 2 field is used to indicate the transmitter address (TA), that is, the link address corresponding to the transmitting device. In the case of a non-aggregate MAC service data unit (MSDU), the address 3 field is used to indicate the address of the MLD associated with the receiving end, that is, the MLD MAC address of the receiving device; or, in the case of an aggregated MSDU, the address 3 field is used to indicate the link address associated with the receiving end, such as the link address corresponding to the AP0 of the receiving device. For unicast management frame messages, the address 3 field can be used for frame filtering. For example, according to address 3, it can be known whether the frame belongs to the basic service set (BSS). If not, the receiving device can discard the frame. Sequence control, QoS control and HT control are all control fields. The QoS control field may include a traffic identifier (TID) subfield and an MSDU present (A-MSDU present) subfield. The sequence control field may include two subfields: a fragment number and a sequence number.
[0069] In some embodiments, the message format of a unicast data frame message or a unicast management frame message carrying integrity protection information, that is, the message format of message A, is shown in FIG4 , and may include the following fields: a MAC frame header (MAC header), a cipher-block chaining message authentication code protocol (CBC-MAC) protocol (CCMP) frame header (header), integrity protection information, a protocol data unit (PDU), a message integrity code (MIC) and a frame check sequence (FCS). Among them, the PDU is used to carry data or management information to be transmitted, and the FCS is used to verify the data or management information. The MAC frame header and the CCMP frame header can be called MPDU format message headers, that is, the MPDU format message header can include a MAC frame header and a CCMP frame header. Among them, the structure of the MAC frame header can refer to the structure of the MAC frame header in FIG3 .
[0070] The Frame Control field in the MAC frame header, as shown in Figure 5, may include the following subfields: Protocol Version, Type, Subtype, To DS, From DS, More Fragments, Retry, Power Management, More Data, Protected Frame, and HT Control Presence (+HTC). The Protocol Version subfield occupies two bits and indicates the network transmission protocol version applicable to the frame. For example, the protocol version may be IEEE 802.1X. The Type subfield occupies two bits, and the Subtype subfield occupies four bits. The Type and Subtype subfields indicate the type of the frame, for example, whether it is a unicast data frame, a multicast data frame, or a unicast management frame. The To DS subfield and From DS subfield each occupy one bit and indicate whether the current device is a transmitter or a receiver. The presence of More Fragments, Retry, Power Management, More Data, Protected Frame, and HT Control subfields each occupies one bit. More Fragments indicates whether there are additional fragments associated with the frame, and More Data indicates whether there is additional data associated with the frame. Retry indicates whether the frame is a retransmitted message.
[0071] In some embodiments, as shown in Figure 6, the CCMP frame header may include a packet number (PN) and a key information (Key ID) field. The PN is 6 bytes long, corresponding to PN0-PN5 from low byte to high byte. The Key Information field occupies one byte, the ExtIV bit in this byte is always set to 1, and bits 6-7 in this byte are the Key ID subfield, which can carry a key identifier to indicate the key to be used. The remaining bits are reserved.
[0072] The third byte of the CCMP frame header field is a reserved byte. In some embodiments, message A may also include an information indicator bit a, which is used to indicate that message A carries integrity protection information a. The information indicator bit a can be a reserved byte in the CCMP frame header field of message A or a reserved bit in the reserved bit. For example, when the reserved bit is in the position 1, it indicates that integrity protection information a exists; when the reserved bit is in the position 0, it indicates that integrity protection information a does not exist. In other embodiments, the information indicator bit a can be carried in the MAC frame header. For example, the subtype subfield in the MAC frame header shown in Figure 4 can be set to a new value to indicate that message A is a message in an enhanced protected MPDU frame format, that is, message A contains integrity protection information a to protect the MPDU message header.
[0073] The integrity protection information field is used to carry integrity protection information a. Key ID+PN+MIC can be called integrity protection information a, which is used to perform integrity check on the message header in MPDU format. The message header in MPDU format can be simply referred to as MPDU message header. Exemplarily, the integrity protection information a can be used for additional authentication data (AAD) in the MPDU message header. In the frame control field of the MPDU message header, except for the lower 3 bits of the Subtype subfield, the Retry subfield, the Power management subfield, the More Data subfield, the Protected frame subfield and the +HTC subfield, all other subfields belong to AAD. The Duration field is not protected, and the Sequence Number subfield in the Sequence Control field is not protected. That is to say, the Protocol version subfield, Type subfield, To DS subfield, From DS subfield, More fragments subfield in the frame control field, as well as the Address1 field, Address2 field, Address3 field, Fragment Number subfield in the Sequence Control field, and TID subfield in the QoS control field (the above fields or subfields belong to the MAC frame header) all belong to AAD and are protected.
[0074] In some embodiments, the MAC layer of a multi-link device can be divided into a UMAC sublayer and an LMAC sublayer. Integrity protection of the MPDU format message header can be deployed in the LMAC sublayer of the MAC layer. As shown in Figure 7, the sending device performs the following steps:
[0075] S701: Create an MPDU header for message A.
[0076] S702: Perform integrity protection on the MPDU header.
[0077] For the sending device, after creating the MPDU header for message A, the LMAC layer of the sending device performs integrity protection on the MPDU header. Key ID indicates the key identifier used, and PN is the packet sequence number assigned to the MPDU. PN can be used by the receiving end to detect replay attacks. The MIC is determined based on the protected information, Key, and PN. The protected information may include some or all of the following fields: Protocol version subfield, Type subfield, To DS subfield, From DS subfield, More fragments subfield, Retry subfield, Power Management subfield, More Data subfield, protected frame subfield, +HTC subfield, Address1 field, Address2 field, Address3 field, Sequence Control field, QoS control field, and CCMP frame header field. The MIC is obtained by performing calculations based on the protected information, Key, and PN. Key ID + PN + MIC can be called integrity protection information a.
[0078] In related art, the PN of a retransmitted message is typically the same as that of the initially transmitted message, and does not follow the rule of increasing packet sequence numbers. In the embodiments of the present application, to prevent replay attacks, even if message A is a retransmitted message, the PN in the integrity protection information a is configured according to the rule of increasing packet sequence numbers. That is, the PN also needs to be increased, maintaining a strictly increasing PN.
[0079] In some embodiments, a set of pairwise transient keys (PTKs) can be set separately. The pairwise transient keys can be called XPTKs. XPTKs are used to protect the message headers of the MPDU format of unicast data frame messages or unicast management frame messages. The LMAC layer of the sending device can use the identifier of the XPTK as the Key ID. In an optional embodiment, multiple XPTKs are stored in the sending device. Each communication link between the sending device and the receiving device corresponds to an XPTK, and the identifier of the XPTK corresponding to each communication link can be different. The sending device can determine the identifier of the corresponding XPTK based on the communication link corresponding to message A, and use the determined identifier of the XPTK as the Key ID.
[0080] In other embodiments, considering that the unicast control frame message has a control pairwise transient key (CPTK), the CPTK of the unicast control frame message can be reused, that is, the CPTK is used to protect both the unicast control frame message and the unicast data frame message and the unicast management frame message. The LMAC layer of the sending device can use the identifier of the CPTK as the Key ID. In an optional embodiment, multiple CPTKs are stored in the sending device. Each communication link between the sending device and the receiving device corresponds to a CPTK, and the identifier of the CPTK corresponding to each communication link is different. The sending device can determine the corresponding CPTK identifier based on the communication link corresponding to message A, and use the determined CPTK identifier as the Key ID.
[0081] Reusing the CPTK of the unicast control frame message as the secret key for the unicast data frame message and the unicast management frame message can reduce the derivation and maintenance of the secret key and reduce the processing complexity of the LMAC layer.
[0082] S703: Create a cyclic redundancy check.
[0083] The sending device may calculate a cyclic redundancy check (CRC) to obtain an FCS.
[0084] S704, MPDU aggregation process.
[0085] The sending device may aggregate multiple messages A.
[0086] S202: The sending device sends message A to the receiving device.
[0087] The sending device may send the MPDU obtained by aggregating multiple messages A to the receiving device.
[0088] S203: The receiving device performs an integrity check on the message header a based on the integrity protection information a.
[0089] In some embodiments, after receiving the MPDUs aggregated from multiple messages A, the receiving device may process the aggregated MPDUs as shown in FIG8 , including the following steps:
[0090] S801, MPDU de-aggregation process.
[0091] The receiving device performs de-aggregation processing on the received aggregated MPDU to obtain one or the first message A.
[0092] S802: Perform CRC check on message A.
[0093] The receiving device's LMAC layer uses the FCS to perform a CRC check on message A. If the check passes, it then performs an integrity check on the MPDU header of message A. If the check fails, message A is discarded.
[0094] S803: Perform integrity check on the MPDU header of message A.
[0095] The LMAC layer of the receiving device can obtain the key based on the key ID carried in integrity protection information a and calculate the MIC based on the protected information, the key, and the PN. Specifically, the MIC is calculated by calculating the Protocol version subfield, Type subfield, To DS subfield, From DS subfield, More fragments subfield, Retry subfield, Power management subfield, More Data subfield, Protected frame subfield, +HTC subfield, Address1 field, Address2 field, Address3 field, Sequence Control field, and QoS control field in the frame control field, part or all of the information in the CCMP frame header field, as well as the key and PN. If the calculated MIC is consistent with the MIC in integrity protection information a, verification succeeds and replay attack detection continues on message A. If the calculated MIC is inconsistent with the MIC in integrity protection information a, verification fails and message A is discarded.
[0096] S804: Perform replay attack detection on message A.
[0097] In some embodiments, the receiving device can maintain a replay counter for received unicast messages. The replay counter stores the PN value of the most recently received unicast message. The receiving end compares the PN of message A with the current value in the replay counter. If the PN of message A is less than the current value in the replay counter, it indicates a possible replay attack and message A can be discarded.
[0098] S805: Perform address 1 filtering and block scoreboard status update operations on message A.
[0099] If all of the above verification processes pass, the receiving device can continue filtering message A's address 1 (address1 filtering) and updating the block scoreboard status (block ack scoreboarding). Address 1 is the address of the receiving end. If the receiving end determines that it is not the intended recipient based on Address 1 carried in message A, it can discard message A. If the receiving end determines that it is the intended recipient, it can update the block scoreboard status.
[0100] In some embodiments, the sending device may also send a multicast data frame message or a multicast management frame message to the receiving device. Exemplarily, the sending device may execute step S204.
[0101] S204: The sending device generates message B.
[0102] Message B can be a multicast data frame or a multicast management frame. For example, when a sending device needs to send data to a receiving device via multicast, it can generate a multicast data frame; when a sending device needs to send management information to a receiving device via multicast, it can generate a multicast management frame. Message B can also be a retransmitted multicast data frame or multicast management frame, which can use the MPDU format.
[0103] In some embodiments, the format of a multicast data frame message or a multicast management frame message may refer to the message formats shown in Figures 3 and 5. For example, when a receiving device does not need to reorder multicast frame messages, protection of the MPDU message header of the multicast data frame message or the multicast management frame message may not be considered. In this case, the format of the multicast data frame message or the multicast management frame message may refer to the message format shown in Figure 3. If protection of the MPDU message header of the multicast data frame message or the multicast management frame message is required, integrity protection information b may be carried in the multicast data frame message or the multicast management frame message. In this case, the format of the multicast data frame message or the multicast management frame message may refer to the message format shown in Figure 5.
[0104] In some embodiments, a separate group temporal key (GTK) may be set. This group temporal key may be referred to as XGTK. XGTK is used to protect the MPDU-formatted header of a multicast data frame or multicast management frame. The LMAC layer of the sending device may use the XGTK as the key to determine the MIC based on the protected information, the key, and the PN. The protected information may include some or all of the following fields: the Protocol version subfield, the Type subfield, the To DS subfield, the From DS subfield, the More fragments subfield, the Retry subfield, the Power Management subfield, the More Data subfield, the protected frame subfield, the +HTC subfield, the Address1 field, the Address2 field, the Address3 field, the Sequence Control field, and the QoS control field in the frame control field of the multicast data frame or multicast management frame, and the CCMP frame header field. An operation is performed based on the protected information, the key, and the PN to obtain the MIC. The LMAC layer of the sending device may use the XGTK identifier as the key ID. The key ID + PN + MIC may be referred to as integrity protection information b.
[0105] In an optional embodiment, the sending device stores multiple XGTKs. Each communication link between the sending device and the receiving device corresponds to an XGTK, and the XGTK identifier corresponding to each communication link is different. The sending device can determine the corresponding XGTK identifier based on the communication link corresponding to message B and use the determined XGTK identifier as the Key ID.
[0106] In this embodiment, the correspondence between the keys and the messages is shown in Figure 9: CPTK is used to protect the unicast control frame message (individually addressed control frame), CGTK is used to protect the multicast control frame message (group addressed control frame), XPTK is used to protect the MPDU message header of the unicast data frame message (individually addressed data frame) and the unicast management frame message (individually addressed mamagement frame), and XGTK is used to protect the MPDU message header of the multicast data frame message (group addressed data frame) and the multicast management frame message (group addressed mamagement frame).
[0107] In other embodiments, the control group transient key (CGTK) of the unicast control frame message can be reused, that is, the CGTK is used to protect both multicast control frame messages and multicast data frame messages and multicast management frame messages. The LMAC layer of the sending device can use the CGTK as the key to determine the MIC based on the protected information, the key and the PN, where the protected information can include part or all of the following fields: the Protocol version subfield, the Type subfield, the To DS subfield, the From DS subfield, the More fragments subfield, the Retry subfield, the Power Management subfield, the More Data subfield, the protected frame subfield, the +HTC subfield, the Address1 field, the Address2 field, the Address3 field, the Sequence Control field and the QoS control field in the frame control field of the multicast data frame message or the multicast management frame message, and the CCMP frame header field. The MIC is obtained by performing an operation based on the protected information, the key and the PN. The LMAC layer of the sending device can use the CGTK identifier as the key ID. The key ID + PN + MIC can be called integrity protection information b. The LMAC layer of the sending device may use the identifier of the CGTK as the Key ID, that is, the integrity protection information b is generated according to the CGTK of the multicast control frame message.
[0108] In an optional embodiment, the sending device stores multiple CGTKs. Each communication link between the sending device and the receiving device corresponds to a CGTK, and the identifier of the CGTK corresponding to each communication link can be different. The sending device can determine the identifier of the corresponding CGTK based on the communication link corresponding to message B and use the determined CGTK identifier as the Key ID.
[0109] Reusing the CGTK of the multicast control frame as the secret key for the multicast data frame and multicast management frame can reduce the derivation and maintenance of secret keys and reduce the processing complexity of the LMAC layer.
[0110] In this embodiment, the correspondence between keys and messages is shown in Figure 10: The CPTK is used to protect not only unicast control frames but also the MPDU headers of unicast data frames and unicast management frames. The CGTK is used to protect not only multicast control frames but also the MPDU headers of multicast data frames and multicast management frames.
[0111] In some embodiments, the MAC frame header of a multicast data frame or multicast management frame may also include an aggregated control (A-Control) field, which is 26 bits long. To enable older receiving devices to correctly receive multicast data frames or multicast management frames, the integrity protection information b ("Key ID + PN + MIC") may also be carried in the A-Control field and carried using a newly defined control identifier. If the A-Control field is not long enough, one or more QoS Null frames may be aggregated, and the "Key ID + PN + MIC" may be carried by sequentially concatenating multiple A-Control fields.
[0112] In related art, the PN of a retransmitted message is typically the same as that of the initially transmitted message, and does not follow the rule of increasing packet sequence numbers. In the embodiments of the present application, to prevent replay attacks, even if message B is a retransmitted message, the PN in the integrity protection information b is configured according to the rule of increasing packet sequence numbers. That is, the PN also needs to be increased, maintaining a strictly increasing PN.
[0113] In some embodiments, message B may further include an information indicator bit b, which is used to indicate that message B carries integrity protection information b. The information indicator bit b may be carried in a MAC frame header, or the information indicator bit b may be a reserved byte in a CCMP frame header field of message B or a reserved bit in a reserved bit.
[0114] S205: The sending device sends message B to the receiving device.
[0115] S206: The receiving device performs an integrity check on the message header b based on the integrity protection information b.
[0116] In some embodiments, after receiving message B, the receiving device may deaggregate message B and extract the FCS and integrity protection information b from message B. The LMAC layer of the receiving device may perform a CRC check on message B using the FCS. If the check fails, message B may be discarded. If the check passes, the LMAC layer of the receiving device may obtain the key based on the key ID carried in the integrity protection information b and calculate the MIC based on the protected information, the key, and the PN. Specifically, the MIC is calculated by calculating the Protocol version subfield, Type subfield, To DS subfield, From DS subfield, More fragments subfield, Retry subfield, Power Management subfield, More Data subfield, Protected frame subfield, +HTC subfield, Address1 field, Address2 field, Address3 field, Fragment Number subfield and QoS control field in the Sequence Control field in a multicast data frame or multicast management frame, partial or all information in the CCMP frame header field, and the key and PN. If the calculated MIC is inconsistent with the MIC in the integrity protection information b, the verification fails and message B is discarded. If the calculated MIC is consistent with the MIC in the integrity protection information b, the verification passes, and the LMAC layer of the receiving device continues to perform replay attack detection on message B. In some embodiments, the receiving device can maintain a replay counter for the received multicast message, and the replay counter stores the PN value of the most recently received multicast message. The receiving end compares the PN of message B with the current value in the replay counter. If the PN of message B is less than the current value in the replay counter, it indicates that it may be subject to a replay attack and message B can be discarded. If the above verification process is passed, the receiving device can process message B normally.
[0117] In the above embodiment, the message headers of the data frame message and the management frame message are protected to prevent an attacker from tampering with the sequence number (SN) in the message header to move the scoreboard window WinStart_R of the receiving end and the window WinStart_B of the receive reordering buffer, thereby causing a reception error. In addition, if a wake-up request is carried in the message header, the receiving end can also be prevented from being mistakenly awakened by the attacker, thereby consuming the energy of the receiving device.
[0118] In some embodiments, before sending a data frame message or a management frame message, a control frame message, such as a Trigger control frame message and a block ack request (BAR) control frame message, may be sent between the sending device and the receiving device. The control frame message may be a unicast control frame message or a multicast control frame message. The integrity protection information "Key ID+PN+MIC" of the control frame message may be carried in a User Info field that begins with a special association identifier (AID). However, some control frames that need to be protected do not have a User Info field, such as a BAR control frame message. Based on this, an embodiment of the present application provides a message transmission method. Figure 11 shows a flow chart of the interaction between a sending device and a receiving device in the message transmission method. As shown in Figure 11, the message transmission method may include the following steps:
[0119] S1101: The sending device generates message C.
[0120] Message C is a control frame message, which can be a unicast control frame message or a multicast control frame message. For example, message C can be a BAR control frame message.
[0121] In some embodiments, the message format of message C is shown in Figure 12 and may include a frame control field, a duration field, a received address (RA) field, a transmit address (TA), a BAR control field, a BAR information field, an integrity protection information (Key ID+PN+MIC) field, and a frame check sequence (FCS) field. If message C is a unicast control frame message, the Key ID may be an identifier of the CPTK; if message C is a multicast control frame message, the Key ID may be an identifier of the CGTK. In an optional embodiment, a sending device stores multiple CPTKs and multiple CGTKs. Each communication link between the sending device and the receiving device corresponds to a CPTK and a CGTK. The identifier of the CPTK corresponding to each communication link may be different, and the identifier of the CGTK corresponding to each communication link may also be different. If message C is a unicast control frame message, the sending device can determine the corresponding CPTK identifier based on the communication link corresponding to message C, and use the determined CPTK identifier as the Key ID; if message C is a multicast control frame message, the sending device can determine the corresponding CGTK identifier based on the communication link corresponding to message C, and use the determined CGTK identifier as the Key ID.
[0122] In message C, the fields preceding the BAR information field are referred to as the message header of message C. The frame control field in the message header may occupy 2 octets, and the structure of the frame control field may refer to the structure shown in FIG4 . The frame control field includes a protected frame subfield. The duration field may occupy 2 bytes, the RA field and the TA field may each occupy 6 bytes, the BAR control field may occupy 2 bytes, and the FCS field may occupy 4 bytes. The length of the BAR information field may vary, depending on the length of the control information to be carried.
[0123] In addition to the integrity protection information c, the message C may also include an information indication bit c, and the information indication bit c is used to indicate whether the message C carries the integrity protection information c.
[0124] In one embodiment, the information indication bit c may be a designated field in the message header of the message C, for example, the Protected Frame subfield in the frame control field may be multiplexed; when the Protected Frame subfield is set to 1, it indicates that the integrity protection information c exists; when the Protected Frame subfield is set to 0, it indicates that the integrity protection information c does not exist.
[0125] In another embodiment, the information indicator bit c can be a reserved bit in the BAR control field of message C; when the reserved bit is in position 1, it indicates that the integrity protection information c exists; when the reserved bit is in position 0, it indicates that the integrity protection information c does not exist.
[0126] S1102: The sending device sends message C to the receiving device.
[0127] S1103: The receiving device performs an integrity check on the message C based on the integrity protection information c.
[0128] In some embodiments, after the receiving device receives message C, the processing process of message C can be performed with reference to the processing process of messages A and B, which will not be repeated here.
[0129] Based on the same technical concept as the above embodiments, the present application also provides a sending device. The sending device can be used to implement the functions of any of the methods provided in the above embodiments, thereby achieving the beneficial effects of the above method embodiments.
[0130] As shown in Figure 13, the sending device 1300 may include a message generating module 1301 and a message sending module 1302. The sending device 1300 may be used to implement the functions of the method executed by the sending device in the above embodiment, thereby achieving the beneficial effects of the above embodiment of the message transmission method.
[0131] In some embodiments, the message generation module 1301 can be configured to generate a first message; the first message is a data frame message or a management frame message. The first message includes a first message header in a Media Access Control Protocol Data Unit (MPDU) format and first integrity protection information, where the first integrity protection information is used to perform an integrity check on the first message header. The message sending module 1302 can be configured to send the first message to a receiving device.
[0132] In some implementations, the first message is a unicast data frame message or a unicast management frame message, and the first integrity protection information is generated based on a control pairwise transient key CPTK of the unicast control frame message.
[0133] In other implementations, the first message is a multicast data frame message or a multicast management frame message, and the first integrity protection information is generated based on a control group temporary key CGTK of the multicast control frame message.
[0134] In some implementations, the first message further includes a first information indicator bit; the first information indicator bit is used to indicate that the first message carries first integrity protection information.
[0135] In some implementations, the first information indicator bit is a reserved bit in a Cipher Block Chaining Message Authentication Code Protocol frame header CCMP Header field of the first message.
[0136] In some implementations, the first integrity protection information includes a packet sequence number PN; if the first message is a retransmitted message, the PN in the first integrity protection information is configured according to an increasing rule of the packet sequence number.
[0137] In other embodiments, the message generation module 1301 may be configured to generate a second message; the second message is a control frame message, and the second message includes second integrity protection information and a second information indicator bit; the second information indicator bit is used to indicate that the second message carries the second integrity protection information. The message sending module 1302 may be configured to send the second message.
[0138] In some implementations, the second information indicator bit is a designated field in a message header of the second message; or, the second information indicator bit is a reserved bit in a block acknowledgement request control BAR control field of the second message.
[0139] Based on the same technical concept as the above embodiments, the present application also provides a receiving device. The receiving device can be used to implement the functions of any of the methods provided in the above embodiments, thereby achieving the beneficial effects of the above method embodiments.
[0140] 14, receiving device 1400 may include a message receiving module 1401 and a message processing module 1402. Receiving device 1400 may be used to implement the functions of the method performed by the receiving device in the above embodiment, thereby achieving the beneficial effects of the above embodiment of the message transmission method.
[0141] In some embodiments, the message receiving module 1401 can be used to receive a first message sent by a sending device; the first message is a data frame message or a management frame message, and the first message includes a first message header in a media access control protocol data unit MPDU format and first integrity protection information; the message processing module 1402 can be used to perform integrity verification on the first message header based on the first integrity protection information.
[0142] In other embodiments, the message receiving module 1401 can be used to receive a second message; the second message is a control frame message, and the second message includes second integrity protection information and a second information indicator bit; the second information indicator bit is used to indicate that the second message carries the second integrity protection information; the message processing module 1402 can be used to perform integrity verification on the second message based on the second integrity protection information.
[0143] Based on the same technical concept as the above embodiments, the present application also provides a sending device in an embodiment, which can be AP MLD100 or non-AP MLD200 shown in Figure 1. This sending device can be used to implement the functions of the method performed by the sending device in the above embodiments, thereby achieving the beneficial effects of the above method embodiments.
[0144] In some embodiments, the structure of the sending device 1500 can be as shown in Figure 15, including a processor 1501 and a memory 1502 connected to the processor 1501. The processor 1501 and the memory 1502 can be interconnected via a bus, and the processor 1501 can serve as the main processor of the sending device 1500, that is, the control core of the sending device 1500. The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The specific connection medium between the above-mentioned processor 1501 and the memory 1502 is not limited in the embodiments of the present application.
[0145] Memory 1502 may include the aforementioned memory. Memory 1502 may be volatile memory, such as random access memory; memory may also be non-volatile memory, such as read-only memory (ROM), flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); or memory 1502 may be any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 1502 may be a combination of the aforementioned memories. Memory 1502 may be used to store software programs and modules.
[0146] The processor 1501 may include one or more processors. The processor 1501 executes various functional applications and data processing of the sending device 1500 by running software programs and modules stored in the memory 1502, such as the message transmission method provided in the embodiment of the present application.
[0147] In some embodiments, the transmitting device 1500 may further include a communication module, such as the radio frequency module shown in FIG. 1 , and the communication module may be used to communicate with other network elements in the network.
[0148] It is understood that the structures illustrated in the embodiments of the present application do not constitute specific limitations on network devices. In other embodiments of the present application, the network device may include more or fewer components than shown, or combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0149] Based on the same technical concept as the above embodiments, the present invention also provides a receiving device in an embodiment, which may be AP MLD100 or non-AP MLD200 shown in Figure 1. This receiving device can be used to implement the functions of the method performed by the receiving device in the above embodiments, thereby achieving the beneficial effects of the above method embodiments.
[0150] In some embodiments, the structure of the receiving device 1600 can be as shown in Figure 16, including a processor 1601 and a memory 1602 connected to the processor 1601. The processor 1601 and the memory 1602 can be interconnected via a bus, and the processor 1601 can serve as the main processor of the receiving device 1600, that is, the control core of the receiving device 1600. The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The specific connection medium between the above-mentioned processor 1601 and the memory 1602 is not limited in the embodiments of the present application.
[0151] Memory 1602 may include the aforementioned memory. Memory 1602 may be volatile memory, such as random access memory; memory may also be non-volatile memory, such as read-only memory (ROM), flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); or memory 1602 may be any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 1602 may be a combination of the aforementioned memories. Memory 1602 may be used to store software programs and modules.
[0152] The processor 1601 may include one or more processors. The processor 1601 executes various functional applications and data processing of the receiving device 1600 by running software programs and modules stored in the memory 1602, such as the message transmission method provided in the embodiment of the present application.
[0153] In some embodiments, the receiving device 1600 may further include a communication module, such as the radio frequency module shown in FIG. 1 , and the communication module may be used to communicate with other network elements in the network.
[0154] It is understood that the structures illustrated in the embodiments of the present application do not constitute specific limitations on network devices. In other embodiments of the present application, the network device may include more or fewer components than shown, or combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0155] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing a computer program or instructions. The computer program or instructions can constitute a computer program product. The embodiments of the present application also provide a computer program product comprising computer-executable instructions. In one embodiment, the computer-executable instructions are used to cause a computer to perform the functions of the above-described method embodiments.
[0156] Computer-executable instructions can be stored in a computer-readable storage medium. The present application also provides a computer-readable storage medium having executable instructions stored therein. In one embodiment, the computer-executable instructions are used to cause a computer to perform the functions of the above method embodiment.
[0157] The computer-readable storage medium provided in the embodiments of the present application may be a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of computer-readable storage medium known in the art.
[0158] Computer-executable instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium such as a floppy disk, hard disk, or magnetic tape; an optical medium such as a digital video disc (DVD); or a semiconductor medium such as a solid-state drive.
[0159] In the various embodiments of the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, including a series of steps or units. The method, system, product or device is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0160] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations thereof may be made without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are intended to be illustrative only of the solutions defined by the appended claims and are to be construed as covering any and all modifications, variations, combinations or equivalents within the scope of the present application.
[0161] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.
Claims
1. A message transmission method, characterized in that: Applied to a sending device, the method comprises: Generate a first message; the first message is a data frame message or a management frame message, the first message includes a first message header in a media access control protocol data unit MPDU format and first integrity protection information; the first integrity protection information is used to perform integrity check on the first message header; Send the first message to a receiving device.
2. The method according to claim 1, characterized in that: The first message is a unicast data frame message or a unicast management frame message, and the first integrity protection information is generated according to a control pairwise transient key CPTK of a unicast control frame message.
3. The method according to claim 1, characterized in that The first message is a multicast data frame message or a multicast management frame message, and the first integrity protection information is generated according to a control group temporary key CGTK of the multicast control frame message.
4. The method according to any one of claims 1 to 3, characterized in that: The first message also includes a first information indicator bit; the first information indicator bit is used to indicate that the first message carries the first integrity protection information.
5. The method according to claim 4, characterized in that The first information indicator bit is a reserved bit in a Cipher Block Chaining Message Authentication Code Protocol frame header CCMP Header field of the first message.
6. The method according to any one of claims 1 to 5, characterized in that: The first integrity protection information includes a packet sequence number PN; if the first message is a retransmitted message, the PN in the first integrity protection information is configured according to a rule of increasing packet sequence numbers.
7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: Generate a second message; the second message is a control frame message, the second message includes second integrity protection information and a second information indicator bit; the second information indicator bit is used to indicate that the second message carries the second integrity protection information; the second integrity protection information is used to perform integrity check on the second message; Send the second message.
8. The method according to claim 7, characterized in that The second information indicator bit is a designated field in a message header of the second message; or, the second information indicator bit is a reserved bit in a block acknowledgement request control BAR control field of the second message.
9. A message transmission method, characterized in that: Applied to a receiving device, the method comprises: Receive a first message sent by a sending device; the first message is a data frame message or a management frame message, and the first message includes a first message header in a media access control protocol data unit MPDU format and first integrity protection information; Based on the first integrity protection information, an integrity check is performed on the first message header.
10. The method according to claim 9, characterized in that The method further comprises: receiving a second message; the second message is a control frame message, the second message includes second integrity protection information and a second information indicator bit; the second information indicator bit is used to indicate that the second message carries the second integrity protection information; Based on the second integrity protection information, perform an integrity check on the second message.
11. A message transmission method, characterized in that: Applied to a sending device, the method comprises: Generate a second message; the second message is a control frame message, the second message includes second integrity protection information and a second information indicator bit; the second information indicator bit is used to indicate that the second message carries the second integrity protection information; the second integrity protection information is used to perform integrity check on the second message; Send the second message to the receiving device.
12. The method according to claim 11, characterized in that The second information indicator bit is a designated field in a message header of the second message; or, the second information indicator bit is a reserved bit in a block acknowledgement request control BAR control field of the second message.
13. A message transmission method, characterized in that: Applied to a receiving device, the method comprises: receiving a second message; the second message is a control frame message, the second message includes second integrity protection information and a second information indicator bit; the second information indicator bit is used to indicate that the second message carries the second integrity protection information; Based on the second integrity protection information, perform an integrity check on the second message.
14. A sending device, characterized in that: It comprises a processor and a memory, wherein a computer program is stored in the memory; the processor is used to read and execute the computer program stored in the memory, so that the method according to any one of claims 1 to 8, or the method according to any one of claims 11 to 12 is executed.
15. A receiving device, characterized in that: It comprises a processor and a memory, wherein a computer program is stored in the memory; the processor is used to read and execute the computer program stored in the memory, so that the method according to any one of claims 9 to 10, or the method according to claim 13, is executed.
16. A computer-readable storage medium, characterized in that: Computer executable instructions are stored, and the computer executable instructions are used to enable a computer to execute the method according to any one of claims 1 to 13.
Citation Information
Patent Citations
Control frame processing and generating method, station, access point and storage medium
CN112867005A
Protected control frames
US20140269773A1
Systems and methods for broadcast WLAN messages with message authentication
US20140351932A1
Protected High-Throughput Control Subfield
US20220132306A1