Wireless communication method and device

Abstract

The present application provides a wireless communication method and device for reducing delay in data authentication in an eBCS acquisition process and mitigating a problem of data loss due to delay in eBCS authentication by modifying an extended broadcast request ANQP element structure and an extended broadcast response ANQP element structure, or modifying an eBCS request element structure and an eBCS response element structure. The present application further provides a unified eBCS request element and a unified eBCS response element for requesting and acquiring an eBCS, which are valid for both associated and unassociated eBCS.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority to a Chinese patent application filed by Oppo Guangdong Mobile Communications Co., Ltd. on April 9, 2021, with the China Patent Office, bearing application number 2021103853896, for the invention "Wireless communication method and apparatus," and also claims priority to a PCT application filed by Oppo Guangdong Mobile Communications Co., Ltd. on April 21, 2021, bearing application number PCT / CN2021 / 088708, for the invention "Wireless communication method and apparatus," the entire contents of which are incorporated herein by reference.

[0002] TECHNICAL FIELD The present embodiments relate to the field of communications, and more particularly to wireless communication methods and devices. [Background technology]

[0003] In the 802.11bc standard, a station (STA) quickly discovers (i.e., quickly acquires) eBCS using an Access Network Query Protocol (ANQP) request and response, or an Enhanced Broadcast Service (eBCS) request and response. However, the current ANQP response does not include eBCS authentication information in its extended broadcast response ANQP element structure, and similarly, the current eBCS response does not include eBCS authentication information in its eBCS response element structure. Therefore, the STA cannot acquire eBCS authentication information using the ANQP request and response, or the eBCS request and response, and must wait until it receives an eBCS information (Info) frame to acquire eBCS authentication information.

[0004] However, the transmission period of the eBCS information frame is long, and the transmission interval is the target beacon transmission time (TBTTs). In this case, in the case of eBCS using Public Key Frame Authentication (PKFA), waiting for authentication information provided by the eBCS information frame increases the authentication delay of the PKFA MAC Protocol Data Unit (MPDU), which fails to meet the demand of PKFA for delay-sensitive data authentication. In the case of Hash Chain Frame Authentication (HCFA) without Instant Authentication, waiting for authentication information provided by the eBCS information frame increases the authentication delay of the HCFA MPDU, which fails to meet the purpose of continuous content delivery (real-time streaming or periodic file transmission) of HCFA without instant authentication. In the case of HCFA with Instant Authentication, which performs instant authentication, the long delay incurred when waiting for the eBCS information frame causes STAs to discard the received HCFA MPDU, resulting in data waste. In short, in the conventional technology, there is a large delay in data authentication in the eBCS acquisition process, and there is a problem of data loss due to the delay in eBCS authentication. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present application provide a wireless communication method and device, which can reduce the data authentication delay in the eBCS acquisition process and solve the problem of data loss caused by the eBCS authentication delay. [Means for solving the problem]

[0006] In a first aspect, a wireless communication method is provided, the method including: a station sending a first request to an access point, the first request being used to request acquisition of an eBCS; and the station receiving a first response, the first response including authentication information for the eBCS.

[0007] In a second aspect, a wireless communication method is provided, the method including: a transmitting terminal sending an ANQP request to a receiving terminal, the ANQP request including a request end time, the request end time being a time at which the transmitting terminal requests termination of eBCS.

[0008] In a third aspect, there is provided a wireless communication method, the method including: an access point receiving a first request, the first request being used to request acquisition of an eBCS; and the access point sending a first response to a station, the first response including authentication information for the eBCS.

[0009] In a fourth aspect, there is provided a wireless communication method, the method including: a receiving terminal receiving an ANQP request sent from a transmitting terminal, the ANQP request including a request end time, the request end time being a time at which the transmitting terminal requests termination of eBCS.

[0010] In a fifth aspect, there is provided a wireless communication method, the method comprising: a station transmitting, to an access point, a request frame carrying an eBCS request element; and the station receiving, to an access point, a response frame carrying an eBCS response element, wherein the eBCS request element is a unified request element for an eBCS that requires registration but does not require association and an eBCS that requires association, and the eBCS response element is a unified response element for an eBCS that requires registration but does not require association and an eBCS that requires association.

[0011] In a sixth aspect, there is provided a wireless communication method, the method comprising: an access point receiving a request frame transmitted from a station, the request frame carrying an eBCS request element; and the access point transmitting a response frame to the station, the response frame carrying an eBCS response element, the eBCS request element being a unified request element for eBCS that requires registration but does not require association and eBCS that requires association; and the eBCS response element being a unified response element for eBCS that requires registration but does not require association and eBCS that requires association.

[0012] In a seventh aspect, there is provided a station for carrying out the method of the first aspect above or each realisation thereof.

[0013] In particular, the station comprises a functional module configured to carry out the method of the first aspect above or each realization thereof.

[0014] In an eighth aspect, there is provided a sending terminal for carrying out the method of the second aspect above or each realization thereof.

[0015] Specifically, the sending terminal comprises a functional module configured to perform the method of the second aspect above or each realization thereof.

[0016] In a ninth aspect, there is provided an access point for performing the method in the third aspect above or each realization thereof.

[0017] Specifically, the access point comprises a functional module configured to perform the method of the above third aspect or each implementation thereof.

[0018] In a tenth aspect, there is provided a receiving terminal for performing the method in the above fourth aspect or each realization thereof.

[0019] Specifically, the receiving terminal comprises a functional module configured to execute the method of the above fourth aspect or each realization thereof.

[0020] In an eleventh aspect, there is provided a station for carrying out the method of the fifth aspect above or each realisation thereof.

[0021] Specifically, the station comprises a functional module configured to perform the method of the above fifth aspect or each realization thereof.

[0022] In a twelfth aspect, there is provided an access point for performing the method in the sixth aspect or each realization thereof.

[0023] Specifically, the access point comprises a functional module configured to perform the method of the above sixth aspect or each implementation thereof.

[0024] In a thirteenth aspect, there is provided a communications device including a processor and a memory, wherein the memory is configured to store a computer program, and the processor is configured to execute the method of any one of the first to sixth aspects or their respective implementations by calling and executing the computer program stored in the memory.

[0025] In a fourteenth aspect, there is provided an apparatus for realizing the method in any one of the first to sixth aspects or each realization mode thereof.

[0026] Specifically, the device includes a processor, and the processor is configured to call up and execute a computer program from memory, thereby causing an appliance in which the device is installed to execute a method according to any one of the first to sixth aspects or their respective implementation forms.

[0027] In a fifteenth aspect, there is provided a computer-readable storage medium storing a computer program, the computer program causing a computer to execute the method of any one of the above first to sixth aspects or their respective realization modes.

[0028] In a sixteenth aspect, there is provided a computer program product including computer program instructions, the computer program instructions causing a computer to perform the method of any one of the above first to sixth aspects or each realization thereof.

[0029] In a seventeenth aspect, a computer program is provided, which, when executed by a computer, causes the computer to execute the method of any one of the above-described first to sixth aspects or their respective realization modes.

[0030] As described above, the present application modifies the extended broadcast response ANQP element structure, or modifies the extended broadcast request ANQP element structure and the extended broadcast response ANQP element structure, or modifies the eBCS response element structure, or modifies the eBCS request element structure and the eBCS response element structure, thereby reducing data authentication delay in the eBCS acquisition process and mitigating the problem of data loss due to eBCS authentication delay. The present application modifies the extended broadcast request ANQP element structure to support a termination notification process for an eBCS that only requires registration. The present application further provides a unified eBCS request element and a unified eBCS response element for requesting and acquiring an eBCS, where the unified eBCS request element is valid for both an associated eBCS and an unassociated eBCS, and the unified eBCS response element is valid for both an associated eBCS and an unassociated eBCS. [Brief explanation of the drawings]

[0031] [Figure 1] This is a flowchart of eBCS DL. [Figure 2] 1 is a schematic diagram of an extended broadcast response ANQP element structure in an ANQP response. [Figure 3] FIG. 1 is a schematic diagram of an eBCS response element structure in an eBCS response. [Figure 4]FIG. 10 is an exemplary structural diagram of an eBCS information frame. [Figure 5] 10 is a timing chart of the rapid discovery of eBCS that employs the PKFA authentication method. [Figure 6] 1 is a timing chart showing a rapid service discovery process using the HCFA authentication method. [Figure 7] 10 is a flowchart of a termination notification process negotiation. [Figure 8] FIG. 10 is an exemplary structural diagram of an eBCS termination notification frame. [Figure 9] FIG. 1 is a schematic diagram of the eBCS request element structure. [Figure 10] FIG. 1 is a schematic diagram of the eBCS response element structure. [Figure 11] FIG. 1 is a schematic diagram of an extended broadcast request ANQP element structure. [Figure 12] 1 is a schematic diagram of an enhanced broadcast service ANQP element structure. [Figure 13] 10 is a negotiation timing chart for the eBCS termination notification process, which requires registration and association. [Figure 14] 2 is an interaction flowchart of a wireless communication method according to an embodiment of the present application; [Figure 15] FIG. 1 is a schematic diagram of an extended broadcast request ANQP element structure according to an embodiment of the present invention. [Figure 16] FIG. 10 is a schematic diagram of another extended broadcast request ANQP element structure according to an embodiment of the present application; [Figure 17] FIG. 10 is a schematic diagram of yet another extended broadcast request ANQP element structure according to an embodiment of the present application; [Figure 18] 1 is a schematic diagram of an extended broadcast response ANQP element structure according to an embodiment of the present invention; [Figure 19] 10 is a schematic diagram of another extended broadcast response ANQP element structure according to an embodiment of the present application; [Figure 20] FIG. 1 is a schematic diagram of an eBCS request element structure according to an embodiment of the present invention. [Figure 21] FIG. 1 is a schematic diagram of an eBCS response element structure according to an embodiment of the present invention. [Figure 22] FIG. 10 is a schematic diagram of another eBCS response element structure according to an embodiment of the present invention. [Figure 23] 10 is a timing chart showing quick acquisition of eBCS using the PKFA method according to an embodiment of the present invention. [Figure 24] 10 is a timing chart showing quick acquisition of eBCS using the HCFA method according to an embodiment of the present invention. [Figure 25] 4 is an interaction flowchart of another wireless communication method according to an embodiment of the present application; [Figure 26] FIG. 1 is a schematic diagram of an extended broadcast request ANQP element structure according to an embodiment of the present invention. [Figure 27] FIG. 10 is a schematic diagram of another extended broadcast request ANQP element structure according to an embodiment of the present application; [Figure 28] FIG. 10 is a schematic diagram of another extended broadcast request ANQP element structure according to an embodiment of the present application; [Figure 29] 10 is a negotiation timing chart of an eBCS end notification process that requires only registration according to an embodiment of the present invention. [Figure 30] FIG. 1 is an exemplary block diagram of STA3000 according to an embodiment of the present invention. [Figure 31] FIG. 31 is an exemplary block diagram of a transmitting terminal 3100 according to an embodiment of the present invention. [Figure 32] FIG. 1 is an exemplary block diagram of an AP3200 according to an embodiment of the present invention. [Figure 33] FIG. 33 is an exemplary block diagram of a receiving terminal 3300 according to an embodiment of the present invention. [Figure 34] 34 is an exemplary structural diagram of a communication device 3400 according to an embodiment of the present application. [Figure 35] 1 is an exemplary structural diagram of an apparatus according to an embodiment of the present invention; [Figure 36] 4 is an interaction flowchart of another wireless communication method according to an embodiment of the present application; [Figure 37] FIG. 1 is a schematic diagram of unified eBCS requirement elements. [Figure 38] FIG. 1 is a schematic diagram of the unified eBCS response elements. [Figure 39] FIG. 39 is an exemplary block diagram of a station 3900 according to an embodiment of the present invention. [Figure 40] FIG. 4 is an exemplary block diagram of an access point 4000 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0032] The following describes the technical solutions of the embodiments of the present application with reference to the drawings of the embodiments of the present application, but obviously, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments, and all other embodiments that can be obtained by those skilled in the art without any creative efforts are included in the protection scope of the present application.

[0033] Before describing the technical solution of the present application, the following will explain the knowledge related to the present application.

[0034] IEEE 802.11bc provides an Enhanced Broadcast Service DownLink (eBCS DL) that enables an Access Point (AP) to broadcast data to STAs.

[0035] It should be understood that the AP in this application may also be referred to as an eBCS AP, and the STA may also be referred to as an eBCS non-AP STA, but the application is not limited thereto.

[0036] In the eBCS DL process, the AP periodically broadcasts eBCS information frames to realize eBCS DL service discovery and provide authentication information for eBCS (i.e., eBCS data). This technical solution mainly improves the eBCS quick acquisition service in the eBCS DL process and complements the negotiation process in the termination notification process.

[0037] Figure 1 shows the eBCS DL flow chart. As shown in Figure 1, the specific process is as follows:

[0038] (1) During the scanning phase, the AP transmits a beacon frame or a probe response frame, which carries a field related to the next eBCS info frame to notify the STA of the broadcast time of the next eBCS info frame.

[0039] (2) After receiving the eBCS information frame at the specified time, the STA acquires the transmission time and authentication information of the eBCS data frame. Therefore, the STA acquires the eBCS by receiving the eBCS data frame broadcast from the AP at the specified time.

[0040] It should be understood that the eBCS data frame in this application may also be referred to as eBCS or eBCS data, and this application is not limited thereto.

[0041] (3) In addition to the STA passively acquiring the eBCS, the eBCS DL process also supports the STA to actively request one or more eBCS services by sending an ANQP request or an eBCS request, thereby achieving the goal of quickly discovering the eBCS. For eBCS services that require registration but not association, the STA obtains the eBCS transmission time by completing eBCS service quick discovery via an ANQP request and an ANQP response frame. For eBCS services that require association, the STA obtains the eBCS data transmission time by completing eBCS service quick discovery via an eBCS request and an eBCS response frame. Figure 2 is a schematic diagram of an Enhanced Broadcast Response ANQP-element in an ANQP response, and Figure 3 is a schematic diagram of an eBCS Response element in an eBCS response. As shown in Figures 2 and 3, neither the Enhanced Broadcast Response ANQP element structure nor the eBCS Response element structure includes authentication information for the eBCS data.

[0042] (4) Therefore, after obtaining the eBCS data frame, the STA needs to wait for the eBCS information frame to obtain the authentication information of the eBCS data frame.

[0043] Furthermore, after the STA receives the eBCS data frame, it adopts different data authentication processes for different eBCS data authentication methods, which can be specifically divided into the following three types:

[0044] a) In the case of PKFA authentication, the STA needs to wait for the reception of an eBCS information frame. Then, it caches the AP's certificate from the eBCS information frame to authenticate the eBCS data, which is also called a PKFA MPDU. PKFA is suitable for occasional small data transfers or time-sensitive data transfers.

[0045] b) In the case of HCFA that does not perform immediate authentication, the STA must wait to receive an eBCS information frame, extract the eBCS information interval (eBCS Info Interval), HCFA base key, and HCFA key change interval information from the eBCS information frame, and then extract information such as the HCFA base key published in the subsequent eBCS data to authenticate the eBCS data; in this case, the eBCS data is also called an HCFA MPDU.

[0046] c) In the case of HCFA with instant authentication, the STA must wait to receive an eBCS information frame, extract the number of instant authenticators, instant authenticator hash distance, and instant authenticator information from the eBCS information frame, and authenticate the eBCS data. In this case, the eBCS data is also called an HCFA MPDU. Note that for HCFA-authenticated eBCS data, the STA discards the received eBCS data because the STA has not obtained the authentication information for the eBCS data before receiving the eBCS information frame.

[0047] 4 is an exemplary structural diagram of an eBCS information frame. As shown in FIG. 4, the eBCS information frame includes important information related to the eBCS, which is mainly divided into time dimension information and authentication dimension information. Here, the time dimension information includes the eBCS information frame interval (eBCS Info Interval) and the time (Next Schedule) of the next data frame transmission corresponding to the eBCS identified by each content (ID). The authentication dimension information includes information such as an authentication certificate, an HCFA base key, and an HCFA key change interval.

[0048] In the existing 802.11bc standard, the eBCS rapid discovery process for different authentication methods is as follows:

[0049] 1. eBCS rapid discovery process using PKFA certification method FIG. 5 is a timing chart for rapid discovery of eBCS employing the PKFA authentication method. As shown in FIG. 5, a STA joins an existing communication network at the time shown in FIG. 5. Because the transmission period of eBCS information frames is long and the transmission interval is TBTTs, if the STA misses the first eBCS information frame in the figure, it will not be able to obtain information about PKFA authentication in the eBCS information frame. For eBCSs that require registration but do not require association, the STA completes eBCS service rapid discovery using ANQP request / ANQP response frames, thereby obtaining the transmission time of the PKFA MPDU. For eBCSs that require association, the STA completes eBCS service rapid discovery using eBCS request and eBCS response frames after completing association, thereby obtaining the transmission time of the PKFA MPDU. The specific process is as follows:

[0050] (1) The STA receives a beacon frame or a probe response frame, and notifies the STA of the broadcast time of the next eBCS information frame by a field related to the next eBCS information frame in the frame.

[0051] (2) The STA completes eBCS rapid discovery using the ANQP request and ANQP response frames, and the eBCS request and eBCS response frames, thereby obtaining the PKFA MPDU transmission time. However, since the ANQP response or eBCS response does not contain authentication information for the PKFA MPDU, even if the STA can receive the PKFA MPDU, it cannot authenticate the PKFA MPDU. If the authentication of the second eBCS information frame is within a finite period, the STA caches the PKFA MPDU and waits for the arrival of the second eBCS information frame.

[0052] (3) When the STA receives the second eBCS Info frame, it acquires the transmission time and authentication information of the PKFA MPDU, caches the authentication information, and verifies the PKFA MPDU using the cached authentication information. If the verification is successful, the eBCS is acquired.

[0053] Figure 6 is a timing chart for rapid discovery of a service that employs the HCFA authentication method. When a STA joins an existing communication network at the time shown in Figure 6, the transmission period of the eBCS information frame is large, with a transmission interval of TBTTs. If the STA misses the first eBCS information frame, it will not be able to obtain information about HCFA authentication in the eBCS information frame. For eBCSs that require registration but do not require association, the STA completes eBCS rapid discovery using ANQP request and ANQP response frames, thereby obtaining the transmission time of the HCFA MPDU. For eBCSs that require association, the STA completes eBCS rapid discovery using eBCS request and eBCS response frames after completing association, thereby obtaining the HCFA MPDU transmission time. The specific process is as follows:

[0054] (1) The STA receives a beacon frame or a probe response frame, and notifies the STA of the broadcast time of the next eBCS information frame by a field related to the next eBCS information frame in the frame.

[0055] (2) The STA completes eBCS rapid discovery using the ANQP request and ANQP response or the eBCS request and eBCS response method, thereby obtaining the transmission time of the HCFA MPDU. However, since the ANQP response or eBCS response does not contain HCFA authentication information, even if the STA can receive the HCFA MPDU, it cannot authenticate the HCFA MPDU. Therefore, before receiving the eBCS information frame, the STA discards the HCFA MPDU and waits for the arrival of the second eBCS information frame.

[0056] (3) When the STA receives the second eBCS information frame, it acquires the time information and authentication information of the HCFA MPDU and waits for the arrival of the HCFA MPDU at the corresponding time according to the time of the next data frame transmission (Next Schedule) indicated in the eBCS information frame.

[0057] (4) When a STA receives an HCFA MPDU, the key for verifying the HCFA MPDU has not been released, so the STA caches the HCFA MPDU and waits for the release of the key corresponding to the HCFA MPDU. The HCFA algorithm is a delayed key release algorithm, and the expected time delay for key release relative to the reception of an HCFA MPDU is shown in Figure 6. After obtaining the public key at the expected time, the STA also authenticates the previously cached HCFA MPDU according to the timescale. Here, the latest time for delayed key release is when the third eBCS information frame is received, because the key information is included in the field of this eBCS information frame at this time. If the verification is successful, the eBCS is acquired.

[0058] Technical solutions for negotiating the termination notification process Referring to the termination notification process described in 802.11bc, when a transmitting terminal attempts to terminate a certain eBCS, the specific negotiation process is as shown in FIG.

[0059] It should be understood that the transmitting terminal is a device that broadcasts data, and the transmitting terminal may be a STA, and the receiving terminal may be an AP correspondingly, or the transmitting terminal may be an AP, and the receiving terminal may be an STA correspondingly, and the present application is not limited thereto.

[0060] FIG. 7 is a flowchart of the termination notification process negotiation. As shown in FIG. 7, (1) If an eBCS is about to terminate within a time interval less than or equal to the eBCS Termination Notice Time specified in the protocol, the transmitting terminal transmits an eBCS Termination Notice frame to notify the receiving terminal of the expected termination time of this eBCS. In addition to indicating the eBCS termination time corresponding to this eBCS-specific content ID, the eBCS Termination Notice frame also indicates extension information, including a service address (Destination Address) and a service extension request method, if subsequent eBCS extension is required. Figure 8 shows an exemplary structure of an eBCS Termination Notice frame.

[0061] (2) If the expected eBCS end time indicated in the eBCS end notification frame is acceptable to the receiving terminal, the eBCS ends strictly according to the expected end time. The acceptable end time for the receiving terminal is not specified in the 802.11bc standard. If the expected eBCS end time indicated in the eBCS end notification frame is earlier than the actual expected end time of the receiving terminal, the receiving terminal requests an eBCS extension based on the eBCS extension information indicated in the received eBCS end notification frame. The eBCS extension request method can be either an eBCS request or an ANQP request.

[0062] (3) For eBCS that require registration and association, the receiving terminal sends an eBCS request carrying the Requested Time to Termination, and after successfully requesting an eBCS extension, the sending terminal replies to the receiving terminal with the new eBCS termination time, carrying the termination time in an eBCS response, as shown in Figures 9 and 10.

[0063] (4) For eBCS that requires only registration and not association, the receiving terminal sends an ANQP request including an extended broadcast service request ANQP element structure. After successfully requesting an eBCS extension, the sending terminal returns a new eBCS end time to the receiving terminal by carrying the end time in the extended broadcast service ANQP element structure included in the ANQP response, as shown in Figures 11 and 12. However, in Figure 11, the extended broadcast service request ANQP element structure does not have a field related to the end time, so a new eBCS end time cannot be requested or negotiated, and the purpose of eBCS extension cannot be achieved.

[0064] A specific negotiation timing chart for the eBCS termination notification process, which requires registration and association, is shown in FIG.

[0065] In step S1301, the transmitting terminal decides to terminate the eBCS.

[0066] Optionally, the terminating eBCS includes when a Media Access Control (MAC) broadcast ends and the application layer may continue to generate data sources.

[0067] In step S1302, the transmitting terminal generates an end notification frame.

[0068] In step S1303, the transmitting terminal transmits an end notification frame to the receiving terminal.

[0069] In step S1304, the receiving terminal acquires the eBCS termination time (Time To Termination), service address (Destination Address), and service extension request method (Request Method) corresponding to the content identifier from the termination notification frame.

[0070] In step S1305, if the receiving terminal determines that the expected eBCS end time indicated in the eBCS end notification frame is acceptable to the receiving terminal, the eBCS ends strictly according to the expected end time.

[0071] In step S1306, if the expected eBCS end time indicated in the eBCS end notification frame is earlier than the actual expected end time of the receiving terminal, the receiving terminal generates an eBCS request (Request frame).

[0072] In step S1307, the receiving terminal transmits an eBCS request to the transmitting terminal.

[0073] The eBCS request includes a content ID corresponding to the eBCS and a request time to termination. Optionally, the eBCS request includes an eBCS request information set, which includes the request termination time.

[0074] In step S1308, after receiving the eBCS request, the transmitting terminal analyzes the request time to termination from the eBCS request so that the transmitting terminal obtains the most recently requested eBCS termination time.

[0075] In step S1309, the transmitting terminal generates an eBCS response (eBCS Response frame).

[0076] In step S1310, the transmitting terminal transmits an eBCS response to the receiving terminal.

[0077] The eBCS response includes a content ID corresponding to the eBCS, a time to termination, a service process duration, and an SP interval. Optionally, the eBCS response includes an eBCS response information set, which includes a time to termination.

[0078] In step S1311, after receiving the eBCS response, the receiving terminal analyzes the termination time (Time to Termination) from the eBCS response to obtain the eBCS termination time after negotiation.

[0079] The present application mainly solves the following two technical problems.

[0080] 1. As mentioned above, in the 802.11bc standard, a STA can quickly discover eBCS through an ANQP request and an ANQP response, or through an eBCS request and an eBCS response. However, the extended broadcast response ANQP element structure in the current ANQP response does not include eBCS authentication information, and similarly, the eBCS response element structure in the current eBCS response does not include eBCS authentication information. Therefore, the STA cannot obtain eBCS authentication information through the ANQP request / ANQP response or eBCS request and eBCS response methods, and must wait to receive an eBCS information (Info) frame to obtain eBCS authentication information. This results in a large data authentication delay in the eBCS acquisition process, which can lead to data loss issues.

[0081] 2. For eBCS that requires registration only, after a transmitting terminal transmits an eBCS termination notification frame to a receiving terminal, if the expected eBCS termination time indicated in the eBCS termination notification frame is earlier than the actual expected termination time of the receiving terminal, the receiving terminal will request an eBCS extension using the ANQP request method based on the eBCS extension information indicated in the received eBCS termination notification frame. However, the current extended broadcast request ANQP element structure does not have a service termination time field. Therefore, this element structure cannot support the eBCS termination notification process that requires registration only.

[0082] With regard to the first technical problem described above, the present application solves the technical problem mainly by changing the extended broadcast response ANQP element structure, or by changing the extended broadcast request ANQP element structure and the extended broadcast response ANQP element structure, or by changing the eBCS response element structure, or by changing the eBCS request element structure and the eBCS response element structure.

[0083] Regarding the second technical problem, the present application solves the technical problem mainly by modifying the extended broadcast request ANQP element structure.

[0084] The technical solution of the present application is described in detail below.

[0085] FIG. 14 is an interaction flowchart of a wireless communication method according to an embodiment of the present application. As shown in FIG. 14, the method includes the following processes:

[0086] In step S1410, the STA sends a first request to the AP, where the first request is used to request acquisition of the eBCS.

[0087] In step S1420, the AP sends a first response to the STA, where the first response includes authentication information of the eBCS.

[0088] Alternative 1: The eBCS is a registration-only, non-association eBCS, and correspondingly, the first request is an ANQP request and the first response is an ANQP response.

[0089] Alternative 2: The eBCS is an eBCS with which association is required, and correspondingly, the first request is an eBCS request and the first response is an eBCS response.

[0090] An example of an ANQP request in Alternative Method 1 will be described.

[0091] 15 is a schematic diagram of an enhanced broadcast request ANQP element structure according to an embodiment of the present application. As shown in FIG. 15, an Enhanced Broadcast Services Request Control field is added to the Enhanced Broadcast Services Request Tuples of the enhanced broadcast request ANQP element structure, and Request Authentication Info is added below the Enhanced Broadcast Services Request Control field, where the Request Authentication Info is used to indicate whether to request acquisition of eBCS authentication information. Optionally, a value of the Request Authentication Info indicates that the STA is requested to quickly acquire eBCS and to acquire eBCS authentication information, and a value of the Request Authentication Info indicates that the STA is not requested to acquire eBCS authentication information.

[0092] Optionally, as shown in FIG. 15, the added enhanced broadcast service request control field may include a requested termination time indication (Requested Time To Termination Present) for the termination notification process of the STA.

[0093] Optionally, as shown in FIG. 15, the extended broadcast service request tuple may include a Requested Time to Termination.

[0094] Optionally, as shown in FIG. 15, the added enhanced broadcast service request control field may include a request target AP information indication (Request Target AP Info Present) for the STA's cross-AP request process, which will not be described in detail in this technical proposal.

[0095] Optionally, as shown in FIG. 15, the extended broadcast service request tuple may include a Target AP Basic Service Set Identifier (BSSID).

[0096] Example 2: Figure 16 is a schematic diagram of another extended broadcast request ANQP element structure according to an embodiment of the present application. As shown in Figure 16, the extended broadcast request ANQP element structure does not include an extended broadcast service request control field. Instead, request authentication information is added to a reserved field in the Broadcast Action field.

[0097] Example 3: No fields are added to the extended broadcast request ANQP element structure, as shown in Figure 11. Meanwhile, the default AP carries the authentication information of the eBCS in the ANQP response.

[0098] Example 4: FIG. 17 is a schematic diagram of yet another extended broadcast request ANQP element structure according to an embodiment of the present application. As shown in FIG. 17, the extended broadcast service request tuple in the extended broadcast request ANQP element structure includes request authentication information.

[0099] Note that the above examples 1 to 4 are merely examples of modifying the extended broadcast request ANQP element structure, and are not limited to these. Furthermore, the length of each field in the extended broadcast request ANQP element structure is not limited to the field lengths shown in Figures 15 to 17 and 11.

[0100] An example of an ANQP response in Alternative Method 1 will be described.

[0101] 18 is a schematic diagram of an enhanced broadcast response ANQP element structure according to an embodiment of the present application. As shown in Fig. 18, an Enhanced Broadcast Services Response Control field is added to the Enhanced Broadcast Services Response Tuples of the enhanced broadcast response ANQP element structure, and a Response Authentication Info Present field is added below the Enhanced Broadcast Services Response Control field. Optionally, a value of 1 in the Response Authentication Info Present field indicates that the STA has successfully requested eBCS quick acquisition and will add eBCS authentication information to the enhanced broadcast service response tuple. A value of 0 in the Response Authentication Info Present field indicates that the STA cannot acquire eBCS authentication information, i.e., will not add eBCS authentication information to the enhanced broadcast response ANQP element structure.

[0102] Optionally, the authentication information of the eBCS includes an Authentication Algorithm field, which is used to indicate the authentication algorithm adopted for the eBCS.

[0103] Optionally, the authentication algorithm is one of No Frame Authentication With Mandatory Higher Layer Source Authentication (HLSA), PKFA, HCFA without immediate authentication, and HCFA with immediate authentication.

[0104] Optionally, the authentication algorithm of eBCS is as shown in Table 1. [Table 1] Optionally, if the value corresponding to the authentication algorithm is 0, indicating that the requested eBCS authentication method is HLSA, no associated authentication information field is present. If the value corresponding to the authentication algorithm is 1, indicating that the requested eBCS authentication method is PKFA, the authentication information further includes an Allowable Time Difference, an authentication certificate length, and an authentication certificate. If the value corresponding to the authentication algorithm is 2, indicating that the requested eBCS authentication method is HCFA without immediate authentication, the authentication information further includes an Allowable Time Difference, an eBCS Info Interval, an HCFA Key Change Interval, and an HCFA Base Key. If the value corresponding to the authentication algorithm is 3, indicating that the requested eBCS authentication method is HCFA, which performs instant authentication, the authentication information further includes an Allowable Time Difference, a Number Of Instant Authenticators, and an Instant Authenticator List, and the Instant Authenticator List includes an Instant Authenticator Hash Distance and an Instant Authenticator field.

[0105] The interpretation of each item of information included in the authentication information can be referred to in the 802.11bc standard, and will not be described in this application.

[0106] Optionally, the extended broadcast response ANQP element structure may further include a response target AP information indication (Response Target AP Info Present) and / or a response target AP information (Response Target AP Info) for the STA's cross-AP response process, which will not be described in detail in this technical solution.

[0107] Example 2: Figure 19 is a schematic diagram of another enhanced broadcast response ANQP element structure according to an embodiment of the present application. As shown in Figure 19, the Enhanced Broadcast Services Response Control field is not added to the Enhanced Broadcast Services Response Tuples of the enhanced broadcast response ANQP element structure. Instead, eBCS authentication information is directly added to the enhanced broadcast services response tuple. For the interpretation of the authentication information, please refer to the explanation in Example 1 above, and the explanation will not be repeated here.

[0108] Note that the above examples 1 and 2 are merely examples of modifying the extended broadcast response ANQP element structure, and are not limited to these. Furthermore, the length of each field in the extended broadcast response ANQP element structure is not limited to the field lengths shown in Figures 18 and 19.

[0109] An example of an eBCS request in Alternative Method 2 will be described.

[0110] 20 is a schematic diagram of an eBCS request element structure according to an embodiment of the present application. As shown in FIG. 20, an eBCS Request Information Set in the eBCS request element structure includes an eBCS Request Info Control field, and adds Request Authentication Information under the eBCS Request Info Control, where the Request Authentication Information is used to indicate whether to request acquisition of eBCS authentication information. Optionally, a value of the Request Authentication Information is 1, indicating to the STA that quick eBCS acquisition is requested and that acquisition of eBCS authentication information is requested, and a value of the Request Authentication Information is 0, indicating to the STA that acquisition of eBCS authentication information is not requested.

[0111] Example 2: No fields are added to the eBCS request element structure, as shown in Figure 9. Meanwhile, the default AP carries the eBCS authentication information in the eBCS response.

[0112] Note that the above examples 1 and 2 are merely examples of changing the eBCS request element structure, and the present invention is not limited to these. Furthermore, the length of each field in the eBCS request element structure is not limited to the field lengths shown in Figures 20 and 9.

[0113] An example of an eBCS response in Alternative Method 2 will be described.

[0114] 21 is a schematic diagram of an eBCS response element structure according to an embodiment of the present application. As shown in Fig. 21, the eBCS response element structure includes an eBCS Response Information Set, which includes an eBCS Response Info Control field, and a Response Authentication Info present is added to the eBCS Response Info Control field. Optionally, a value of the added Response Authentication Info Indicator is 1, which indicates that the STA has successfully requested eBCS fast acquisition and will add eBCS authentication information to the eBCS response information set; a value of the added Response Authentication Info Indicator is 0, which indicates that the STA has failed to request eBCS fast acquisition and will not add eBCS authentication information to the eBCS response element structure.

[0115] Example 2: Figure 22 is a schematic diagram of another eBCS response element structure according to an embodiment of the present application. As shown in Figure 22, no response authentication information indication (Response Authentication Info present) is added to the eBCS response information control field in the eBCS response element structure, and eBCS authentication information is directly carried in the eBCS response element structure of the default AP.

[0116] Note that different authentication algorithms correspond to different authentication information, and the above description can be referred to for specific details, and the description will not be repeated in this application. The interpretation of each item of information included in the authentication information can be referred to the content described in the 802.11bc standard, and the description will not be repeated in this application.

[0117] Note that the above examples 1 and 2 are merely examples of changing the eBCS response element structure, and the present invention is not limited to these. Furthermore, the length of each field in the eBCS response element structure is not limited to the field lengths shown in Figures 21 and 22.

[0118] As described above, the present application modifies the extended broadcast response ANQP element structure, or modifies the extended broadcast request ANQP element structure and the extended broadcast response ANQP element structure, or modifies the eBCS response element structure, or modifies the eBCS request element structure and the eBCS response element structure, thereby reducing the data authentication delay in the eBCS acquisition process and mitigating the problem of data loss due to eBCS authentication delay.

[0119] The following describes the eBCS rapid acquisition process that uses the PKFA certification method.

[0120] In IEEE 802.11bc, the eBCS DL supports associated and unassociated eBCSs. Considering that a STA can quickly discover an eBCS using an ANQP request and an ANQP response, or an eBCS request and an eBCS response, in the case of the PKFA authentication method, the present application adds eBCS authentication information to the ANQP response or the eBCS response to realize the quick acquisition of an eBCS through PKFA authentication. Figure 23 is a timing chart showing the quick acquisition of an eBCS through the PKFA method according to an embodiment of the present application, and the specific process is as follows:

[0121] (1) In the scanning phase, at the time shown in Fig. 23, a STA joins an existing communication network by receiving a beacon frame or a probe response frame. Because the transmission period of the eBCS information frame is large and the transmission interval is TBTTs, it is assumed that the STA at this time misses the first eBCS information frame.

[0122] (2) Depending on whether association is required, the STA requests to quickly acquire the required service content by adopting an ANQP request or an eBCS request method. Here, for an eBCS that requires registration but does not require association, the STA obtains the PKFA MPDU transmission time and authentication information by completing eBCS service quick discovery via an ANQP request and an AN response. For an eBCS that requires association, the STA obtains the PKFA MPDU transmission time and authentication information by completing eBCS service quick acquisition via an eBCS request and an eBCS response after association.

[0123] (3) After receiving the ANQP response or eBCS response, the STA acquires the transmission time and authentication information of the PKFA MPDU and caches the authentication information.

[0124] (4) Finally, the STA receives the PKFA MPDU at the specified time and authenticates the PKFA MPDU integrity using the cached authentication information.

[0125] As described above, the timing diagram for quick eBCS acquisition in PKFA authentication is shown in Figure 23. Comparing Figure 5 with Figure 23, it can be seen that in the PKFA authentication method, if the quick service acquisition method provided by the present application is adopted, on the one hand, the time it takes for a STA to acquire eBCS is shortened, and on the other hand, the utilization rate of the PKFA MPDU is also improved.

[0126] The following explains the process for expedited eBCS acquisition using the HCFA certification method.

[0127] As described above, in the HCFA authentication method for 802.11bc eBCS DL, the STA needs to wait for the eBCS information frame to contain HCFA authentication information (i.e., eBCS authentication information). This application realizes eBCS rapid acquisition of HCFA authentication by adding HCFA authentication information to the ANQP response or eBCS response. Figure 24 is a timing chart showing rapid eBCS acquisition using the HCFA method according to an embodiment of this application, and the specific process is as follows:

[0128] (1) In the scanning stage, at the time shown in Fig. 24, a STA joins an existing communication network by receiving a beacon frame or a probe response frame. Since the transmission period of the eBCS information frame is large and the transmission interval is TBTTs, it is assumed that the STA misses the first eBCS information frame at this time.

[0129] (2) The STA requests to quickly acquire the required service content by adopting the ANQP request or eBCS request method according to whether association is required. Here, for an eBCS that requires registration but does not require association, the STA obtains the PKFA MPDU transmission time and authentication information by completing eBCS service quick discovery via an ANQP request and an ANQP response. For an eBCS that requires association, the STA obtains the PKFA MPDU transmission time and authentication information by completing eBCS service quick acquisition via an eBCS request and an eBCS response after association.

[0130] (3) For HCFA eBCS that does not perform instant authentication, three new fields of information are added to the ANQP response or eBCS response: eBCS Info Interval, HCFA Key Change Interval, and HCFA Base Key. For HCFA authentication eBCS that performs instant authentication, three new fields of information are added to the ANQP response or eBCS response: Number Of Instant Authenticators, Instant Authenticator Hash Distance, and Instant Authenticator. After receiving the ANQP response or eBCS response, the STA obtains the transmission time and authentication information of the HCFA MPDU, caches the authentication information, and waits to receive the HCFA MPDU.

[0131] (4) The STA receives the HCFA MPDU and, since it has already obtained the HCFA authentication information, caches the HCFA MPDU and waits for the key release corresponding to each HCFA MPDU. HCFA employs a delayed key release method. Assuming that the HCFA MPDU key release time for DL ​​eBCS1 is as shown in Figure 24, the STA obtains the public key at the expected time and then authenticates the previously cached HCFA MPDU according to the timescale. Here, the latest time for delayed key release is when the second eBCS information frame shown in the figure is received, and at this time, the HCFA MPDU key information is included in the field of this eBCS information frame.

[0132] As described above, the timing diagram for eBCS quick acquisition for HCFA authentication is shown in Figure 24. Comparing Figure 6 with Figure 24, it can be seen that in the HCFA authentication method, if the quick service discovery method provided by the present application is adopted, on the one hand, it shortens the time it takes for a STA to acquire eBCS service, and on the other hand, it also improves the utilization rate of HCFA MPDU.

[0133] FIG. 25 is an interaction flowchart of another wireless communication method according to an embodiment of the present application. As shown in FIG. 25, the method includes the following processes:

[0134] In step S2510, the transmitting terminal transmits an ANQP request to the receiving terminal, where the ANQP request includes a request end time, which is the time at which the transmitting terminal requests the termination of eBCS.

[0135] Optionally, the eBCS is a registration-only, non-association eBCS, and the ANQP request is used to request an extension of the eBCS.

[0136] Optionally, the transmitting terminal may be an AP and the receiving terminal may be a STA, or the transmitting terminal may be a STA and the receiving terminal may be an AP.

[0137] An example of the ANQP request will be described below.

[0138] Example 1: Figure 26 is a schematic diagram of an enhanced broadcast request ANQP element structure according to an embodiment of the present application. As shown in Figure 26, an Enhanced Broadcast Services Request Control field and a Requested Time to Termination field are added to the Enhanced Broadcast Services Request Tuples of the enhanced broadcast request ANQP element structure for negotiating the eBCS termination time between the receiving terminal and the transmitting terminal. A Requested Time to Termination Present field is added below the added Enhanced Broadcast Services Request Control field. Optionally, a value of 1 in the Requested Time to Termination Present field indicates that a requested termination time is present, and a value of 0 in the Requested Time to Termination Present field indicates that a requested termination time is not present.

[0139] Optionally, the remainder of the extended broadcast service request control field is a reserved field.

[0140] Optionally, the enhanced broadcast service request control field further includes Request Authentication Info for fast eBCS acquisition of the STA.

[0141] Optionally, the enhanced broadcast service request control field further includes a request target AP information indication (Request Target AP Info Present) for the cross-AP request process of the STA, which is not described in detail in this technical solution.

[0142] Optionally, as shown in FIG. 26, the extended broadcast service request tuple may include a target AP base service set identifier (Target AP BSSID).

[0143] Example 2: Figure 27 is a schematic diagram of another extended broadcast request ANQP element structure according to an embodiment of the present application. As shown in Figure 27, the extended broadcast request ANQP element structure does not additionally add an extended broadcast service request control field and a request end time indication, and the extended broadcast request ANQP element structure carries the request end time by default.

[0144] Example 3: Figure 28 is a schematic diagram of another extended broadcast request ANQP element structure according to an embodiment of the present application. As shown in Figure 28, an extended broadcast service request control field is not additionally added to the extended broadcast request ANQP element structure, but a request end time indication is added using other reserved fields in the extended broadcast request ANQP element structure, for example, the reserved field below the broadcast action field.

[0145] Note that the above examples 1 to 3 are merely examples of modifying the extended broadcast request ANQP element structure, and are not limited to these. Furthermore, the length of each field in the extended broadcast request ANQP element structure is not limited to the field lengths shown in Figures 26 and 28.

[0146] As described above, the present application can support the termination notification process for eBCS that only require registration by modifying the Extended Broadcast Request ANQP element structure.

[0147] Example of negotiation method for termination notification process This application realizes negotiation of the eBCS termination notification process, which only requires registration. A specific negotiation timing chart is shown in FIG. 29.

[0148] In step S2901, the transmitting terminal decides to terminate the eBCS.

[0149] Optionally, the terminating eBCS includes when the MAC broadcast ends and the application layer may continue to generate data sources.

[0150] In step S2902, the transmitting terminal generates an end notification frame.

[0151] In step S2903, the transmitting terminal transmits an end notification frame to the receiving terminal.

[0152] In step S2904, the receiving terminal acquires the eBCS termination time (Time To Termination), service address (Destination Address), and service extension request method (Request Method) corresponding to the content identifier from the termination notification frame.

[0153] In step S2905, if the receiving terminal determines that the expected eBCS end time indicated in the eBCS end notification frame is acceptable to the receiving terminal, the eBCS is ended strictly according to the expected end time.

[0154] In step S2906, if the eBCS expected end time indicated in the eBCS end notification frame is earlier than the actual expected end time of the receiving terminal, the receiving terminal generates a Generic Advertisement Service (GAS) initial request frame.

[0155] The GAS initial request frame carries a Query Request field, which includes an ANQP request, which includes an extended broadcast request ANQP element structure, which may include a content identifier, a broadcast action field, and a request end time.

[0156] In step S2907, the receiving terminal transmits a GAS initial request frame to the transmitting terminal.

[0157] In step S2908, after receiving the GAS initial request frame, the transmitting terminal generates a GAS initial response frame.

[0158] The GAS initial response frame carries a Query Response field, which includes an ANQP response, which includes an extended broadcast service ANQP element structure, which may include a content identifier, an end time, a request method, a service address, etc.

[0159] In step S2909, the transmitting terminal transmits a GAS initial response frame to the receiving terminal.

[0160] In step S2910, after receiving the GAS initial response frame, the receiving terminal analyzes the end time from the GAS initial response frame to obtain the eBCS end time after negotiation.

[0161] 30 is an exemplary block diagram of a STA 3000 according to an embodiment of the present application. As shown in FIG. 30, the STA 3000 includes a communication unit 3010 configured to: send a first request to an AP, where the first request is used to request acquisition of an eBCS; and receive a first response, where the first response includes authentication information for the eBCS.

[0162] Optionally, the eBCS is a registration-only, non-association eBCS, and correspondingly, the first request is an ANQP request and the first response is an ANQP response.

[0163] Optionally, the ANQP request includes an extended broadcast request ANQP element structure, the extended broadcast request ANQP element structure includes an extended broadcast service request tuple, and the extended broadcast service request tuple includes request authentication information, where the request authentication information is used to indicate whether to request obtaining authentication information for the eBCS.

[0164] Optionally, the extended broadcast service request tuple includes an extended broadcast service request control field, and the extended broadcast service request control field includes request authentication information.

[0165] Optionally, the extended broadcast service request tuple includes a broadcast action field, a reserved field of the broadcast action field carrying request authentication information.

[0166] Optionally, the ANQP response further includes a response authentication information indication, where the response authentication information indication is used to indicate whether the ANQP response includes authentication information of the eBCS.

[0167] Optionally, the extended broadcast service response control field, the extended broadcast service response control field includes a response authentication information indication.

[0168] Optionally, the eBCS is an eBCS with which association is required, and correspondingly, the first request is an eBCS request and the first response is an eBCS response.

[0169] Optionally, the eBCS request includes an eBCS request element structure, the eBCS request element structure includes an eBCS request information set, and the eBCS request information set includes request authentication information, where the request authentication information is used to indicate whether to request obtaining authentication information for the eBCS.

[0170] Optionally, the eBCS request information set includes an eBCS request information control field, and the eBCS request information control field includes request authentication information.

[0171] Optionally, the eBCS response further includes a response authentication information indication, where the response authentication information indication is used to indicate whether the eBCS response includes authentication information for the eBCS.

[0172] Optionally, the eBCS response includes an eBCS response information set, the eBCS response information set including a response authentication information indication.

[0173] Optionally, the eBCS response information set includes an eBCS response information control field, and the eBCS response information control field includes a response authentication information indication.

[0174] Optionally, the authentication information of the eBCS includes an authentication algorithm field, which is used to indicate the authentication algorithm adopted for the eBCS.

[0175] Optionally, the authentication algorithm is one of HLSA, PKFA, HCFA without immediate authentication, and HCFA with immediate authentication.

[0176] Optionally, if the authentication algorithm is PKFA, the authentication information of the eBCS further includes: an allowed time difference, a length of the authentication certificate, and an authentication certificate.

[0177] Optionally, if the authentication algorithm is HCFA without immediate authentication, the authentication information of the eBCS further includes an allowed time difference, an eBCS information frame interval, an HCFA key change interval, and an HCFA base key.

[0178] Optionally, if the authentication algorithm is HCFA with immediate authentication, the authentication information of the eBCS further includes an allowed time difference, a number of immediate authenticators, and an immediate authenticator list, where the immediate authenticator list includes a hash distance and an immediate authenticator field of the immediate authenticator.

[0179] Optionally, in some embodiments, the above communication unit may be a communication interface or transceiver, or may be an input / output interface of a communication chip or a system-on-chip.

[0180] It should be understood that the STA3000 according to the present embodiment can correspond to the STA in the method embodiment, and the above operations and other operations and / or functions of each unit in the STA3000 are for realizing the corresponding processes of the STA in the method embodiment, respectively, and will not be repeated here for the sake of brevity.

[0181] 31 is an exemplary block diagram of a transmitting terminal 3100 according to an embodiment of the present application. As shown in FIG. 31, the transmitting terminal 3100 includes a communication unit 3110, which is configured to send an ANQP request to a receiving terminal, where the ANQP request includes a request end time, and the request end time is a time when the transmitting terminal requests the termination of eBCS.

[0182] Optionally, the ANQP request includes an extended broadcast request ANQP element structure, the extended broadcast request ANQP element structure includes an extended broadcast service request tuple, and the extended broadcast service request tuple includes a request end time.

[0183] Optionally, the ANQP request includes a broadcast action field, and a reserved field in the broadcast action field carries a request end time indication, where the request end time indication is used to indicate whether the ANQP request includes a request end time.

[0184] Optionally, the extended broadcast service request tuple includes an extended broadcast service request control field, and the extended broadcast service request control field includes a request end time indication, where the request end time indication is used to indicate whether the request end time is included in the ANQP request.

[0185] Optionally, the eBCS is a registration-only, non-association eBCS, and the ANQP request is used to request an extension of the eBCS.

[0186] Optionally, in some embodiments, the above communication unit may be a communication interface or transceiver, or may be an input / output interface of a communication chip or a system-on-chip.

[0187] It should be understood that the transmitting terminal 3100 according to the present embodiment may correspond to the transmitting terminal in the method embodiment, and the above operations and other operations and / or functions of each unit in the transmitting terminal 3100 are for respectively realizing the corresponding processes of the transmitting terminal in the method embodiment, and will not be repeated here for the sake of brevity.

[0188] 32 is an exemplary block diagram of an AP 3200 according to an embodiment of the present application. As shown in FIG. 32, the AP 3200 includes a communication unit 3210 configured to receive a first request, where the first request is used to request acquisition of an eBCS, and send a first response to a station, where the first response includes authentication information of the eBCS.

[0189] Optionally, the eBCS is a registration-only, non-association eBCS, and correspondingly, the first request is an ANQP request and the first response is an ANQP response.

[0190] Optionally, the ANQP request includes an extended broadcast request ANQP element structure, the extended broadcast request ANQP element structure includes an extended broadcast service request tuple, and the extended broadcast service request tuple includes request authentication information, where the request authentication information is used to indicate whether to request obtaining authentication information for the eBCS.

[0191] Optionally, the extended broadcast service request tuple includes an extended broadcast service request control field, and the extended broadcast service request control field includes request authentication information.

[0192] Optionally, the extended broadcast service request tuple includes a broadcast action field, a reserved field of the broadcast action field carrying request authentication information.

[0193] Optionally, the ANQP response further includes a response authentication information indication, where the response authentication information indication is used to indicate whether the ANQP response includes authentication information of the eBCS.

[0194] Optionally, the ANQP response includes an extended broadcast service response control field, and the extended broadcast service response control field includes a response authentication information indication.

[0195] Optionally, the eBCS is an eBCS with which association is required, and correspondingly, the first request is an eBCS request and the first response is an eBCS response.

[0196] Optionally, the eBCS request includes an eBCS request element structure, the eBCS request element structure includes an eBCS request information set, and the eBCS request information set includes request authentication information, where the request authentication information is used to indicate whether to request obtaining authentication information for the eBCS.

[0197] Optionally, the eBCS request information set includes an eBCS request information control field, and the eBCS request information control field includes request authentication information.

[0198] Optionally, the eBCS response further includes a response authentication information indication, where the response authentication information indication is used to indicate whether the eBCS response includes authentication information for the eBCS.

[0199] Optionally, the eBCS response includes an eBCS response information set, the eBCS response information set including a response authentication information indication.

[0200] Optionally, the eBCS response information set includes an eBCS response information control field, and the eBCS response information control field includes a response authentication information indication.

[0201] Optionally, the authentication information of the eBCS includes an authentication algorithm field, which is used to indicate the authentication algorithm adopted for the eBCS.

[0202] Optionally, the authentication algorithm is one of HLSA, PKFA, HCFA without immediate authentication, and HCFA with immediate authentication.

[0203] Optionally, if the authentication algorithm is PKFA, the authentication information of the eBCS further includes: an allowed time difference, a length of the authentication certificate, and an authentication certificate.

[0204] Optionally, if the authentication algorithm is HCFA without immediate authentication, the authentication information of the eBCS further includes an allowed time difference, an eBCS information frame interval, an HCFA key change interval, and an HCFA base key.

[0205] Optionally, if the authentication algorithm is HCFA with immediate authentication, the authentication information of the eBCS further includes an allowed time difference, a number of immediate authenticators, and an immediate authenticator list, where the immediate authenticator list includes a hash distance and an immediate authenticator field of the immediate authenticator.

[0206] Optionally, in some embodiments, the above communication unit may be a communication interface or transceiver, or may be an input / output interface of a communication chip or a system-on-chip.

[0207] It should be understood that the AP3200 according to the present embodiment may correspond to the AP in the method embodiment, and the above operations and other operations and / or functions of each unit in the AP3200 are for realizing the corresponding processes of the AP in the method embodiment, respectively, and will not be repeated here for the sake of brevity.

[0208] 33 is an exemplary block diagram of a receiving terminal 3300 according to an embodiment of the present application. As shown in FIG. 33, the receiving terminal 3300 includes a communication unit 3310, which is configured to receive an ANQP request sent from a transmitting terminal, the ANQP request including a request end time, which is a time when the transmitting terminal requests the termination of eBCS.

[0209] Optionally, the ANQP request includes an extended broadcast request ANQP element structure, the extended broadcast request ANQP element structure includes an extended broadcast service request tuple, and the extended broadcast service request tuple includes a request end time.

[0210] Optionally, the ANQP request includes a broadcast action field, and a reserved field in the broadcast action field carries a request end time indication, where the request end time indication is used to indicate whether the ANQP request includes a request end time.

[0211] Optionally, the extended broadcast service request tuple includes an extended broadcast service request control field, and the extended broadcast service request control field includes a request end time indication, where the request end time indication is used to indicate whether the request end time is included in the ANQP request.

[0212] Optionally, the eBCS is a registration-only, non-association eBCS, and the ANQP request is used to request an extension of the eBCS.

[0213] Optionally, in some embodiments, the above communication unit may be a communication interface or transceiver, or may be an input / output interface of a communication chip or a system-on-chip.

[0214] It should be understood that the receiving terminal 3300 according to the present embodiment may correspond to the receiving terminal in the method embodiment, and the above operations and other operations and / or functions of each unit in the receiving terminal 3300 are for respectively realizing the corresponding processes of the receiving terminal in the method embodiment, and will not be repeated here for the sake of brevity.

[0215] 34 is an exemplary structural diagram of a communication device 3400 according to an embodiment of the present application. The communication device 3400 shown in FIG. 34 includes a processor 3410, which can implement the method according to the embodiment of the present application by calling and executing a computer program from a memory.

[0216] Optionally, as shown in Figure 34, the communication device 3400 may further include a memory 3420. Here, the processor 3410 can implement the method in the embodiment of the present application by calling and executing a computer program from the memory 3420.

[0217] Here, the memory 3420 may be a separate device independent of the processor 3410 or may be integrated into the processor 3410.

[0218] Optionally, as shown in FIG. 34, the communication device 3400 may further include a transceiver 3430, and the processor 3410 may control the transceiver 3430 to communicate with other devices, specifically to transmit information or data to other devices or receive information or data transmitted by other devices.

[0219] Here, the transceiver 3430 may include a transmitter and a receiver, and may further include one or more antennas.

[0220] Optionally, the communication device 3400 may specifically be an STA in the present embodiment, and the communication device 3400 may perform the corresponding processes realized by the STA in each method of the present embodiment, which will not be repeated here for the sake of brevity.

[0221] Optionally, the communication device 3400 may specifically be an AP in the embodiments of the present application, and the communication device 3400 may perform the corresponding processes realized by the AP in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

[0222] Optionally, the communication device 3400 may specifically be a transmitting terminal in the embodiments of the present application, and the communication device 3400 may perform corresponding processes realized by the transmitting terminal in each method of the embodiments of the present application, which will not be described again here for the sake of brevity.

[0223] Optionally, the communication device 3400 may specifically be a receiving terminal in the embodiments of the present application, and the communication device 3400 may perform corresponding processes realized by the receiving terminal in each method of the embodiments of the present application, which will not be described again here for the sake of brevity.

[0224] Fig. 35 is an exemplary structural diagram of an apparatus according to an embodiment of the present invention. The apparatus 3500 shown in Fig. 35 includes a processor 3510, which can implement the method according to the embodiment of the present invention by calling and executing a computer program from a memory.

[0225] Optionally, as shown in Figure 35, the device 3500 may further include a memory 3520. Here, the processor 3510 can implement the method in the present embodiment by calling and executing a computer program from the memory 3520.

[0226] Here, the memory 3520 may be a separate device independent of the processor 3510 or may be integrated into the processor 3510.

[0227] Optionally, the device 3500 may further include an input interface 3530. Here, the processor 3510 can control the input interface 3530 to communicate with other devices or chips, and in particular can obtain information or data transmitted by other devices or chips.

[0228] Optionally, the device 3500 may further include an output interface 3540. Here, the processor 3510 can control the output interface 3540 to communicate with other devices or chips, and in particular can output information or data to other devices or chips.

[0229] Optionally, the device can be applied to a network device in the embodiments of the present application, and the chip can perform corresponding processes implemented by the network device in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

[0230] Optionally, the device can be applied to a terminal device in the embodiments of the present application, and the device can perform corresponding processes implemented by the terminal device in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

[0231] Optionally, the device referred to in the embodiments of the present application may be a chip, such as a system level chip, a system chip, a chip system, or a system on a chip.

[0232] It should be understood that the processor in the present embodiment may be an integrated circuit chip with signal processing functions. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit in the form of hardware in the processor or by instructions in the form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. Each method, step, and logic block disclosed in the present embodiment can be realized or executed. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the method disclosed in the present embodiment may be directly executed by a hardware decoding processor, or may be executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in conventional storage media such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is placed in a memory, and a processor reads the information in the memory and completes the steps of the above method in combination with the hardware.

[0233] It is understood that the memory of the present embodiments may be volatile or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. By way of illustrative, but non-limiting example, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0234] It should be understood that the above-mentioned memories are exemplary and not limiting. For example, the memory in the present embodiment may be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). Thus, the memory in the present embodiment is intended to include, but is not limited to, these and any other suitable types of memory.

[0235] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon.

[0236] Optionally, the computer-readable storage medium may be applied to a STA, AP, transmitting terminal or receiving terminal in the embodiments of the present application, and the computer program causes a computer to perform corresponding processes implemented by the STA, AP, transmitting terminal or receiving terminal in each method of the embodiments of the present application, which will not be described repeatedly here for the sake of brevity.

[0237] Embodiments of the present application further provide a computer program product including computer program instructions.

[0238] Optionally, the computer program product may be applied to a STA, AP, transmitting terminal or receiving terminal in the embodiments of the present application, and the computer program causes a computer to perform corresponding processes implemented by the STA, AP, transmitting terminal or receiving terminal in each method of the embodiments of the present application, which will not be described repeatedly here for the sake of brevity.

[0239] Embodiments of the present invention further provide computer program instructions.

[0240] Optionally, the computer program may be applied to a STA, AP, transmitting terminal or receiving terminal in the embodiments of the present application, and the computer program causes a computer to perform corresponding processes implemented by the STA, AP, transmitting terminal or receiving terminal in each method of the embodiments of the present application, which will not be described repeatedly here for the sake of brevity.

[0241] The present application further provides a unified eBCS Request element and a unified eBCS Response element for requesting and obtaining an eBCS, where the unified eBCS Request element is valid for both associated and unassociated eBCSs, and the unified eBCS Response element is valid for both associated and unassociated eBCSs.

[0242] It should be understood that an eBCS request element may also be referred to as an eBCS request element structure, and an eBCS response element may also be referred to as an eBCS response element structure, without this application being so limited.

[0243] The following describes in detail such a unified eBCS request method.

[0244] FIG. 36 is an interaction flowchart of another wireless communication method according to an embodiment of the present application. As shown in FIG. 36, the method includes the following processes:

[0245] In step S3601, the STA transmits a request frame carrying an eBCS request element to the AP.

[0246] In step S3602, the AP sends a response frame carrying an eBCS response element to the STA, where the eBCS request element is a unified request element for eBCS that requires registration but does not require association and eBCS that requires association, and the eBCS response element is a unified response element for eBCS that requires registration but does not require association and eBCS that requires association.

[0247] It should be understood that the fact that an eBCS request element is a unified request element for an eBCS that requires registration but does not require association and an eBCS that requires association means that the eBCS request element applies to both an eBCS that requires registration but does not require association and an eBCS that requires association. Similarly, the fact that an eBCS response element is a unified response element for both an eBCS that requires registration but does not require association and an eBCS that requires association means that the eBCS response element applies to both an eBCS that requires registration but does not require association and an eBCS that requires association.

[0248] For convenience, hereinafter, the eBCS request element is referred to as a unified eBCS request element, and the eBCS response element is referred to as a unified eBCS response element. Here, the unified eBCS request element can also be directly referred to as an eBCS request element, and the unified eBCS response element can also be directly referred to as an eBCS response element.

[0249] Optionally, for eBCS that requires registration but not association, the unified eBCS request element is carried in a GAS initial request frame, i.e., the request frame carrying the above eBCS request element is a GAS initial request frame. For example, Table 2 shows, but is not limited to, an example in which the unified eBCS request element is carried in a GAS initial request frame. [Table 2] Optionally, for an eBCS that requires registration but not association, the eBCS response element is carried in a GAS initial response frame, i.e., the response frame carrying the eBCS response element is a GAS initial response frame. For example, Table 3 shows, but is not limited to, an example in which the unified eBCS response element is carried in a GAS initial response frame. [Table 3] Optionally, for eBCS that require association, the unified eBCS request element is carried in an eBCS request frame, i.e., the request frame carrying said eBCS request element is an eBCS request frame.

[0250] It should be understood that the eBCS request frame may also be described as an eBCS request, and the present application does not limit the same thereto.

[0251] Optionally, in case of eBCS requiring association, the unified eBCS response element is carried in an eBCS response frame.

[0252] It should be understood that the eBCS Response Frame may also be referred to as an eBCS response, and the present application does not limit the same thereto.

[0253] For example, Figure 37 is a schematic diagram of a unified eBCS request element. As shown in Figure 37, the unified eBCS request element may include an extended broadcast service request tuple, which includes an extended broadcast service request control field, a broadcast action, and a content ID.

[0254] It should be understood that this application does not limit in which field of the unified eBCS request element the enhanced broadcast service request control field is carried.

[0255] Optionally, the enhanced broadcast service request control field includes a requested end time indication, where the requested end time indication is used to indicate whether the eBCS request element includes a requested end time, and the requested end time is the time at which the station requests the eBCS to end.

[0256] For example, a requested end time indication value of 1 indicates that the eBCS request element includes a requested end time, and a requested end time indication value of 0 indicates that the eBCS request element does not include a requested end time.

[0257] It should be understood that this application does not limit in which field of the unified eBCS Request element the request end time indication is carried.

[0258] Optionally, if the request end time indication is used to indicate that the eBCS request element includes a request end time, the request end time may be carried in the extended broadcast service request tuple, as shown in, but not limited to, FIG.

[0259] Optionally, the extended broadcast service request control field includes a broadcast equipment MAC address indication, where the broadcast equipment MAC address indication is used to indicate whether the eBCS request element includes a broadcast equipment MAC address, and the broadcast equipment MAC address is the MAC address of an access point.

[0260] For example, a value of 1 in the broadcast device MAC address indication indicates that the eBCS request element includes a broadcast device MAC address, and a value of 0 in the broadcast device MAC address indication indicates that the eBCS request element does not include a broadcast device MAC address.

[0261] It should be understood that this application does not limit in which field of the unified eBCS request element the broadcast device MAC address indication is carried.

[0262] Optionally, if the broadcast equipment MAC address indication is used to indicate that the broadcast equipment MAC address is included in the eBCS request element, the broadcast equipment MAC address is carried in the extended broadcast service request tuple, as shown, but not limited to, in FIG.

[0263] Optionally, the enhanced broadcast service request control field includes request authentication information, where the request authentication information is used to indicate whether to request obtaining authentication information for the eBCS.

[0264] For example, if the value of the requested authentication information is 1, it indicates that the STA requests the acquisition of eBCS authentication information, i.e., supports the STA to quickly acquire eBCS; if the value of the requested authentication information is 0, it indicates that the STA does not request the acquisition of eBCS authentication information, i.e., does not support the STA to quickly acquire eBCS.

[0265] It should be understood that this application does not limit in which field of the unified eBCS request element the request authentication information is carried.

[0266] Optionally, the extended broadcast service request control field includes a request target AP information indication, where the request target AP information indication is used for the cross-AP request process of the station.

[0267] For example, a value of 1 in the Request Target AP Information Indication indicates that the eBCS request element includes a target AP BSSID, and a value of 0 in the Request Target AP Information Indication indicates that the eBCS request element does not include a target AP BSSID.

[0268] It should be understood that this application does not limit in which field of the unified eBCS request element the requested target AP information indication is carried.

[0269] Optionally, if the Request Target AP Information indication is used to indicate that the target AP BSSID is included in the eBCS Request element, the target AP BSSID may be carried in the Enhanced Broadcast Service Request Tuple, as shown in, but not limited to, FIG. 37.

[0270] For example, FIG. 38 is a schematic diagram of a unified eBCS response element. As shown in FIG. 38, the unified eBCS response element may include an extended broadcast service response tuple, which includes an extended broadcast service response control field, a content ID, and a broadcast service transmission.

[0271] It should be understood that this application does not limit in which field of the unified eBCS response element the enhanced broadcast service response control field is carried.

[0272] Optionally, the enhanced broadcast service response control field includes a response authentication information indication, where the response authentication information indication is used to indicate whether the eBCS response element includes authentication information for the eBCS.

[0273] For example, if the value of the response authentication information indication is 1, it indicates that the eBCS response element contains eBCS authentication information, and if the value of the response authentication information indication is 0, it indicates that the eBCS response element does not contain eBCS authentication information.

[0274] It should be understood that this application does not limit in which field of the unified eBCS response element the response authentication information indication is carried.

[0275] Optionally, if the response authentication information indication is used to indicate that the eBCS response element contains eBCS authentication information, the eBCS authentication information may be carried in the Enhanced Broadcast Service Response control field, as shown in, but not limited to, FIG. 38.

[0276] Optionally, the enhanced broadcast service response control field includes an eBCS request status indicating whether the eBCS request was successful or not.

[0277] For example, a value of 1 in the eBCS request status indicates that the eBCS request was successful, and a value of 0 in the eBCS request status indicates that the eBCS request was unsuccessful.

[0278] It should be understood that this application does not limit in which field of the unified eBCS response element the eBCS request status indication is carried.

[0279] Optionally, the enhanced broadcast service response control field includes an end time indication, where the end time indication is used to indicate whether an end time is included in the eBCS response element.

[0280] For example, an end time indication value of 1 indicates that the eBCS response element includes an end time, and an end time indication value of 0 indicates that the eBCS response element does not include an end time.

[0281] It should be understood that this application does not limit in which field of the unified eBCS response element the end time indication is carried.

[0282] Optionally, if an end time indication is used to indicate that an end time is included in the eBCS response element, the end time may be carried in, but is not limited to, the extended broadcast service response control field, as shown in FIG. 38.

[0283] Optionally, the extended broadcast service response control field includes an extended broadcast service SP period indication, where the extended broadcast service SP period indication is used to indicate whether an extended broadcast service SP period is included in the eBCS response element.

[0284] For example, if the value of the extended broadcast service SP period indication is 1, it indicates that the eBCS response element includes an extended broadcast service SP period, and if the value of the extended broadcast service SP period indication is 0, it indicates that the eBCS response element does not include an extended broadcast service SP period.

[0285] It should be understood that the present application does not limit in which field of the unified eBCS response element the enhanced broadcast service SP period indication is carried.

[0286] Optionally, if an extended broadcast service SP period indication is used to indicate that an extended broadcast service SP period is included in the eBCS response element, the extended broadcast service SP period may be carried in the extended broadcast service response control field, as shown in, but not limited to, FIG. 38.

[0287] Optionally, the extended broadcast service response control field includes an extended broadcast service interval time indication, where the extended broadcast service interval time indication is used to indicate whether the eBCS response element includes an extended broadcast service interval time.

[0288] For example, if the value of the extended broadcast service interval time indication is 1, it indicates that the eBCS response element includes an extended broadcast service interval time, and if the value of the extended broadcast service interval time indication is 0, it indicates that the eBCS response element does not include an extended broadcast service interval time.

[0289] It should be understood that the present application does not limit in which field of the unified eBCS response element the extended broadcast service interval time indication is carried.

[0290] Optionally, if the extended broadcast service interval time indication is used to indicate that the eBCS response element includes an extended broadcast service interval time, the extended broadcast service interval time may be carried in the extended broadcast service response control field, as shown in, but not limited to, FIG. 38.

[0291] Optionally, the enhanced broadcast service response control field includes a response target AP information indication, where the response target AP information indication is used to indicate whether the eBCS response element includes response target information.

[0292] For example, if the value of the response target AP information indication is 1, it indicates that the eBCS response element contains response target AP information, and if the value of the response target AP information indication is 0, it indicates that the eBCS response element does not contain response target AP information.

[0293] It should be understood that the present application does not limit in which field of the unified eBCS response element the response target AP information indication is carried.

[0294] Optionally, when the response target AP information indication is used to indicate that the eBCS response element contains the response target AP information, the response target AP information may be carried in an enhanced broadcast service response control field, as shown in FIG. 38, but is not limited to this.

[0295] Optionally, the response target AP information includes an extended broadcast service SP period, an extended broadcast service interval time, a time of the next data frame transmission, and authentication information, where the extended broadcast service SP period is used to indicate the duration of the eBCS, the extended broadcast service interval time is used to indicate the time interval of the eBCS, and the time of the next data frame transmission is used to indicate the allocation time of the next eBCS.

[0296] Optionally, the authentication information of the eBCS includes an Authentication Algorithm field, which is used to indicate the authentication algorithm adopted for the eBCS.

[0297] Optionally, the authentication algorithm is one of, but not limited to, No Frame Authentication With Mandatory Higher Layer Source Authentication (HLSA), PKFA, HCFA without immediate authentication, or HCFA with immediate authentication.

[0298] Optionally, the authentication algorithm of eBCS is as shown in Table 1.

[0299] Optionally, if the value corresponding to the authentication algorithm is 0, indicating that the requested eBCS authentication method is HLSA, no associated authentication information field is present. If the value corresponding to the authentication algorithm is 1, indicating that the requested eBCS authentication method is PKFA, the authentication information further includes an Allowable Time Difference, an authentication certificate length, and an authentication certificate. If the value corresponding to the authentication algorithm is 2, indicating that the requested eBCS authentication method is HCFA without immediate authentication, the authentication information further includes an Allowable Time Difference, an eBCS Info Interval, an HCFA Key Change Interval, and an HCFA Base Key. If the value corresponding to the authentication algorithm is 3, indicating that the requested eBCS authentication method is HCFA, which performs instant authentication, the authentication information further includes an Allowable Time Difference, a Number Of Instant Authenticators, and an Instant Authenticator List, and the Instant Authenticator List includes an Instant Authenticator Hash Distance and an Instant Authenticator field.

[0300] The interpretation of each item of information included in the authentication information can be referred to in the 802.11bc standard, and will not be described in this application.

[0301] The present application further provides a unified eBCS Request element and a unified eBCS Response element for requesting and obtaining an eBCS, where the unified eBCS Request element is valid for both associated and unassociated eBCSs, and the unified eBCS Response element is valid for both associated and unassociated eBCSs.

[0302] As described above, the present application provides a unified eBCS request method. However, currently, in the prior art, there are a request method for only eBCS that requires association (hereinafter referred to as the first eBCS request method) and a request method for only eBCS that requires only registration and not association (hereinafter referred to as the second eBCS request method). Therefore, before making an eBCS request, the STA and AP must first decide which eBCS request method to adopt.

[0303] Optionally, the STA and the AP may adopt the same method to determine which eBCS request method to adopt, or the STA may decide which eBCS request method to adopt and instruct the AP which eBCS request method to adopt, or further, the AP may decide which eBCS request method to adopt and instruct the STA which eBCS request method to adopt.

[0304] Optionally, each eBCS request method corresponds to a unique index.

[0305] For convenience, the present application may apply a unified eBCS request method or target eBCS request method for eBCSs that require registration but not association, and eBCSs that require association.

[0306] Optionally, the unified eBCS request method is substituted for the first eBCS request method or the second eBCS request method, i.e., the first eBCS request method in the prior art is substituted for the unified eBCS request method, or the second eBCS request method in the prior art is substituted for the unified eBCS request method, and for example, as shown in Table 4, the index corresponding to the first eBCS request method corresponds to the unified eBCS request method in the present application. [Table 4] Optionally, as shown in Table 5, the unified eBCS request method has a different index from both the indexes of the first eBCS request method and the second eBCS request method. [Table 5] As described above, the present application provides a unified eBCS request method. However, currently, in the prior art, there are request methods for eBCS only that require association, and request methods for eBCS only that require registration but not association. Therefore, the technical solution provided in the present application allows for flexible determination or indication of the specific eBCS request method to be adopted.

[0307] 39 is an exemplary block diagram of a station 3900 according to an embodiment of the present disclosure. The station 3900 includes a communication unit 3910 configured to transmit a request frame carrying an eBCS request element to an access point and to receive a response frame carrying an eBCS response element. Here, the eBCS request element is a unified request element for an eBCS that requires registration but does not require association and an eBCS that requires association, and the eBCS response element is a unified response element for an eBCS that requires registration but does not require association and an eBCS that requires association.

[0308] Optionally, in case of eBCS where registration and no association is required, the request frame is a GAS initial request frame.

[0309] Optionally, in case of eBCS where registration and no association is required, the response frame is a GAS initial response frame.

[0310] Optionally, in the case of eBCS requiring association, the request frame is an eBCS request frame.

[0311] Optionally, in case of eBCS requiring association, the response frame is an eBCS response frame.

[0312] Optionally, the eBCS request element includes a requested end time indication, where the requested end time indication is used to indicate whether the eBCS request element includes a requested end time, which is the time at which the station requests the eBCS to end.

[0313] Optionally, the eBCS request element includes an extended broadcast service request control field, which carries a request end time indication.

[0314] Optionally, the eBCS request element includes a request end time.

[0315] Optionally, the eBCS request element includes an extended broadcast service request tuple, and the extended broadcast service request tuple includes a request end time.

[0316] Optionally, the eBCS request element includes request authentication information, where the request authentication information is used to indicate whether to request obtaining authentication information for the eBCS.

[0317] Optionally, the eBCS request element includes an extended broadcast service request control field, which carries request authentication information.

[0318] Optionally, the eBCS request element includes an extended broadcast service request tuple, which includes an extended broadcast service request control field.

[0319] Optionally, the eBCS response element includes a response authentication information indication, where the response authentication information indication is used to indicate whether the eBCS response element includes authentication information for the eBCS.

[0320] Optionally, the eBCS response element includes an extended broadcast service response control field, which includes a response authentication information indication.

[0321] Optionally, the eBCS response element includes an extended broadcast service response tuple, which includes an extended broadcast service response control field.

[0322] Optionally, the eBCS response element includes authentication information for the eBCS.

[0323] Optionally, the eBCS response element includes an extended broadcast service response tuple, which includes authentication information for the eBCS.

[0324] Optionally, the authentication information of the eBCS includes an authentication algorithm field, which is used to indicate the authentication algorithm adopted for the eBCS.

[0325] Optionally, the authentication algorithm is one of HLSA, PKFA, HCFA without immediate authentication, and HCFA with immediate authentication.

[0326] Optionally, if the authentication algorithm is PKFA, the authentication information of the eBCS further includes: an allowed time difference, a length of the authentication certificate, and an authentication certificate.

[0327] Optionally, if the authentication algorithm is HCFA without immediate authentication, the authentication information of the eBCS further includes an allowed time difference, an eBCS information frame interval, an HCFA key change interval, and an HCFA base key.

[0328] Optionally, if the authentication algorithm is HCFA with immediate authentication, the authentication information of the eBCS further includes an allowed time difference, a number of immediate authenticators, and an immediate authenticator list, where the immediate authenticator list includes a hash distance and an immediate authenticator field of the immediate authenticator.

[0329] Optionally, the station 3900 comprises a processing unit 3920, wherein the processing unit 3920 is configured to determine to adopt a target eBCS request manner to request an eBCS, where the target eBCS request manner is a unified eBCS request manner for an eBCS that requires registration but does not require association and an eBCS that requires association.

[0330] Optionally, the target eBCS request method corresponds to a unique index.

[0331] Optionally, the target eBCS request method is replaced by a first eBCS request method or a second eBCS request method, where the first eBCS request method is a request method for only an eBCS that requires association, and the second eBCS request method is a request method for an eBCS that requires only registration and not association.

[0332] Optionally, the target eBCS request method has an index different from both the indexes of the first eBCS request method and the second eBCS request method, where the first eBCS request method is a request method for only eBCSs that require association, and the second eBCS request method is a request method for eBCSs that require only registration and not association.

[0333] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or a system-on-chip. The processing unit may be one or more processors.

[0334] It should be understood that the station 3900 according to the present embodiment may correspond to the station in the method embodiment, and the above operations and other operations and / or functions of each unit in the station 3900 are for realizing the corresponding processes of the station in the method embodiment, respectively, and will not be repeated here for the sake of brevity.

[0335] 40 is an exemplary block diagram of an access point 4000 according to an embodiment of the present application. The access point 4000 includes a communication unit 4010 configured to receive a request frame transmitted from a station, the request frame carrying an eBCS request element, and to transmit a response frame carrying an eBCS response element to the station. Here, the eBCS request element is a unified request element for an eBCS that requires registration but does not require association, and an eBCS that requires association. The eBCS response element is a unified response element for an eBCS that requires registration but does not require association, and an eBCS that requires association.

[0336] Optionally, in case of eBCS where registration and no association is required, the request frame is a GAS initial request frame.

[0337] Optionally, in case of eBCS where registration and no association is required, the response frame is a GAS initial response frame.

[0338] Optionally, in the case of eBCS requiring association, the request frame is an eBCS request frame.

[0339] Optionally, in case of eBCS requiring association, the response frame is an eBCS response frame.

[0340] Optionally, the eBCS request element includes a requested end time indication, where the requested end time indication is used to indicate whether the eBCS request element includes a requested end time, which is the time at which the station requests the eBCS to end.

[0341] Optionally, the eBCS request element includes an extended broadcast service request control field, which carries a request end time indication.

[0342] Optionally, the eBCS request element includes a request end time.

[0343] Optionally, the eBCS request element includes an extended broadcast service request tuple, and the extended broadcast service request tuple includes a request end time.

[0344] Optionally, the eBCS request element includes request authentication information, where the request authentication information is used to indicate whether to request obtaining authentication information for the eBCS.

[0345] Optionally, the eBCS request element includes an extended broadcast service request control field, which carries request authentication information.

[0346] Optionally, the eBCS request element includes an extended broadcast service request tuple, which includes an extended broadcast service request control field.

[0347] Optionally, the eBCS response element includes a response authentication information indication, where the response authentication information indication is used to indicate whether the eBCS response element includes authentication information for the eBCS.

[0348] Optionally, the eBCS response element includes an extended broadcast service response control field, which includes a response authentication information indication.

[0349] Optionally, the eBCS response element includes an extended broadcast service response tuple, which includes an extended broadcast service response control field.

[0350] Optionally, the eBCS response element includes authentication information for the eBCS.

[0351] Optionally, the eBCS response element includes an extended broadcast service response tuple, which includes authentication information for the eBCS.

[0352] Optionally, the authentication information of the eBCS includes an authentication algorithm field, which is used to indicate the authentication algorithm adopted for the eBCS.

[0353] Optionally, the authentication algorithm is one of HLSA, PKFA, HCFA without immediate authentication, and HCFA with immediate authentication.

[0354] Optionally, if the authentication algorithm is PKFA, the authentication information of the eBCS further includes: an allowed time difference, a length of the authentication certificate, and an authentication certificate.

[0355] Optionally, if the authentication algorithm is HCFA without immediate authentication, the authentication information of the eBCS further includes an allowed time difference, an eBCS information frame interval, an HCFA key change interval, and an HCFA base key.

[0356] Optionally, if the authentication algorithm is HCFA with immediate authentication, the authentication information of the eBCS further includes an allowed time difference, a number of immediate authenticators, and an immediate authenticator list, where the immediate authenticator list includes a hash distance and an immediate authenticator field of the immediate authenticator.

[0357] Optionally, the access point 4000 comprises a processing unit 4020, wherein the processing unit 4020 is configured to determine to adopt a targeted eBCS request manner to request eBCS, where the targeted eBCS request manner is a unified eBCS request manner for an eBCS that requires registration but does not require association and an eBCS that requires association.

[0358] Optionally, the target eBCS request method corresponds to a unique index.

[0359] Optionally, the target eBCS request method is replaced by a first eBCS request method or a second eBCS request method, where the first eBCS request method is a request method for only an eBCS that requires association, and the second eBCS request method is a request method for an eBCS that requires only registration and not association.

[0360] Optionally, the target eBCS request method has an index different from both the indexes of the first eBCS request method and the second eBCS request method, where the first eBCS request method is a request method for only eBCSs that require association, and the second eBCS request method is a request method for eBCSs that require only registration and not association.

[0361] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or a system-on-chip. The processing unit may be one or more processors.

[0362] It should be understood that the access point 4000 according to the present embodiment may correspond to the access point in the method embodiment, and the above operations and other operations and / or functions of each unit in the access point 4000 are for realizing the corresponding processes of the access point in the method embodiment, respectively, and will not be repeated here for the sake of brevity.

[0363] Those skilled in the art can understand that each exemplary unit and algorithm step described with reference to the embodiments disclosed herein may be realized by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraints of the technical solution. Professional engineers can use different methods to realize the described functions according to each specific application, but such realization should not be considered beyond the scope of the present application.

[0364] Those skilled in the art can clearly understand that for convenience and brevity of description, the specific operating processes of the above systems, devices and units can refer to the corresponding processes in the above method embodiments, and will not be repeated here.

[0365] It should be understood that in some embodiments provided herein, the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative, and the division of the units is merely a division of logical functions. In actual implementation, other division methods may be adopted, for example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. It should be noted that the shown or discussed mutual couplings or direct couplings or communication connections may be realized using some communication interfaces, and indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0366] The units described as separate parts may or may not be physically separated, and the parts shown as units may or may not be physical units, and may be located in one place or distributed across multiple network units. Depending on actual needs, some or all of the units therein may be selected to achieve the objective of the technical solution in this embodiment.

[0367] Furthermore, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0368] When the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, an essential part of the technical solution of the present application, i.e., a part that contributes to the prior art, or all or part of the solution of the technology, can be embodied in the form of a software product, and the computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes various media capable of storing program code, such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0369] The above content is merely a specific embodiment of the present application, and the protection scope of the present application is not limited thereto. Any modifications or replacements that can be easily thought of by those skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. 1. A wireless communication method, comprising: a transmitting terminal transmitting an ANQP request to a receiving terminal, the ANQP request including a request end time, the request end time being a time at which the transmitting terminal requests termination of eBCS; The wireless communication method, wherein the ANQP request includes an extended broadcast request ANQP element structure, the extended broadcast request ANQP element structure includes an extended broadcast service request tuple, and the extended broadcast service request tuple includes the request end time.

2. The ANQP request includes a broadcast action field, and a reserved field of the broadcast action field carries a request end time indication; The request end time indication is used to indicate whether the request end time is included in the ANQP request. The wireless communication method according to claim 1 .

3. the extended broadcast service request tuple includes an extended broadcast service request control field, the extended broadcast service request control field including a request end time indication; The request end time indication is used to indicate whether the request end time is included in the ANQP request. The wireless communication method according to claim 1 .

4. The eBCS is a registration-only, non-association eBCS, and the ANQP request is used to request an extension of the eBCS. The wireless communication method according to any one of claims 1 to 3.

5. 1. A wireless communication method, comprising: receiving, by a receiving terminal, an ANQP request transmitted from a transmitting terminal, the ANQP request including a request end time, the request end time being a time at which the transmitting terminal requests termination of eBCS; The wireless communication method, wherein the ANQP request includes an extended broadcast request ANQP element structure, the extended broadcast request ANQP element structure includes an extended broadcast service request tuple, and the extended broadcast service request tuple includes the request end time.

6. The ANQP request includes a broadcast action field, and a reserved field of the broadcast action field carries a request end time indication; The request end time indication is used to indicate whether the request end time is included in the ANQP request. The wireless communication method according to claim 5.

7. the extended broadcast service request tuple includes an extended broadcast service request control field, the extended broadcast service request control field including a request end time indication; The request end time indication is used to indicate whether the request end time is included in the ANQP request. The wireless communication method according to claim 5.

8. The eBCS is a registration-only, non-association eBCS, and the ANQP request is used to request an extension of the eBCS. The wireless communication method according to any one of claims 5 to 7.

9. A transmitting terminal comprising: a memory for storing a computer program; and a processor for executing the method according to any one of claims 1 to 4 by calling and executing the computer program stored in the memory.

10. A receiving terminal comprising: a memory for storing a computer program; and a processor for executing the method according to any one of claims 5 to 8 by calling and executing the computer program stored in said memory.

11. A computer-readable storage medium storing a computer program for causing a computer to carry out the method according to any one of claims 1 to 8.

Images