CN115209352A

CN115209352A - Wireless communication method and device

Info

Publication number: CN115209352A
Application number: CN202110385389.6A
Authority: CN
Inventors: 冉鑫怡; 田莹莹; 鞠宏浩; 周培; 黄磊; 卢刘明; 罗朝明
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-04-09
Filing date: 2021-04-09
Publication date: 2022-10-18
Also published as: WO2022213425A1

Abstract

The application provides a wireless communication method and equipment, wherein the data authentication delay in the eBCS acquisition process is reduced and the problem of data loss caused by eBCS authentication delay is solved by modifying an enhanced broadcast request ANQP element structure and an enhanced broadcast response ANQP element structure or modifying an eBCS request element structure and an eBCS response element structure.

Description

Wireless communication method and device

Technical Field

The present embodiments relate to the field of communications, and in particular, to a wireless communication method and apparatus.

Background

In the standard 802.11bc, a Station (STA) rapidly discovers (i.e., rapidly acquires) eBCS by requesting (Request) and responding (Response) an Access Network Query Protocol (ANQP), or by requesting (Request) and responding (Response) an Enhanced Broadcast Service (eBCS). However, the enhanced broadcast response ANQP element structure in the current ANQP response does not have the authentication information of the eBCS, and similarly, the eBCS response element structure in the current eBCS response does not have the authentication information of the eBCS. Therefore, the STA cannot obtain the authentication information of the eBCS through the ANQP request and ANQP response, the eBCS request and the eBCS response, but must wait for receiving the eBCS information (Info) frame before obtaining the authentication information of the eBCS.

However, the eBCS information frame Transmission period is large, and the Transmission interval is a Target Beacon Transmission Time (TBTTs). At this time, for an eBCS authenticated by Public Key Frame Authentication (PKFA), waiting for Authentication information provided by an eBCS information Frame increases the Authentication delay of a PKFA MAC Protocol Data Unit (MPDU), and cannot meet the requirement of the PKFA on delay-sensitive Data Authentication; for Hash Chain Frame Authentication (HCFA) Without immediate Authentication, waiting for Authentication information provided by an eBCS information Frame increases the Authentication delay of an HCFA MPDU, and cannot meet the requirement that the HCFA Without immediate Authentication is used for continuous content distribution (real-time streaming transmission or regular file transmission); for an HCFA (HCFA With Instant Authentication) performing immediate Authentication, a large time delay is introduced during waiting for an eBCS information frame, which may cause the STA to discard the HCFA MPDU that has been received, resulting in data waste. In a word, the prior art has the problems of large data authentication delay in the eBCS acquisition process and data loss caused by eBCS authentication delay.

Disclosure of Invention

The embodiment of the application provides a wireless communication method and equipment, so that the data authentication delay in the eBCS acquisition process can be reduced, and the problem of data loss caused by the eBCS authentication delay is solved.

In a first aspect, a wireless communication method is provided, including: the method comprises the steps that a station sends a first request to an access point, wherein the first request is used for requesting to acquire eBCS; the station receives a first response, the first response comprising: authentication information of eBCS.

In a second aspect, a wireless communication method is provided, including: the sending end sends an ANQP request to the receiving end, wherein the ANQP request comprises the following steps: and requesting the termination time, wherein the request termination time is the time when the sender requests the eBCS to be terminated.

In a third aspect, a wireless communication method is provided, including: the method comprises the steps that an access point receives a first request, wherein the first request is used for requesting to acquire eBCS; the access point sends a first response to the station, the first response comprising: authentication information of eBCS.

In a fourth aspect, a wireless communication method is provided, including: the receiving end receives an ANQP request sent by the sending end, wherein the ANQP request comprises the following steps: and requesting the termination time, wherein the request termination time is the time when the sender requests the termination of the eBCS.

In a fifth aspect, a station is provided for performing the method of the first aspect or its implementations.

In particular, the station comprises functional modules for performing the method of the first aspect or its implementations described above.

In a sixth aspect, a transmitting end is provided, configured to perform the method in the second aspect or its implementation manners.

Specifically, the transmitting end includes a functional module for executing the method in the second aspect or each implementation manner thereof.

In a seventh aspect, an access point is provided for performing the method of the third aspect or its implementation manners.

In particular, the access point comprises functional means for performing the method of the third aspect or its implementations described above.

In an eighth aspect, a receiving end is provided, configured to perform the method in the fourth aspect or each implementation manner thereof.

Specifically, the receiving end includes a functional module for executing the method in the fourth aspect or its implementation manner.

In a ninth aspect, a communication device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method in the first aspect to the fourth aspect or each implementation manner thereof.

In a tenth aspect, there is provided an apparatus for implementing the method of any one of the first to fifth aspects or implementations thereof.

Specifically, the apparatus includes: a processor configured to call and run the computer program from the memory, so that the device on which the apparatus is installed performs the method according to any one of the first to fourth aspects or the implementation manners thereof.

In an eleventh aspect, a computer-readable storage medium is provided for storing a computer program, which causes a computer to execute the method of any one of the first to fourth aspects or implementations thereof.

In a twelfth aspect, a computer program product is provided, which comprises computer program instructions to make a computer execute the method of any one of the first to fourth aspects or implementations thereof.

In a thirteenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the first to fourth aspects or implementations thereof.

In summary, in the present application, the structure of the enhanced broadcast response ANQP element may be modified, or the structure of the enhanced broadcast request ANQP element and the structure of the enhanced broadcast response ANQP element may be modified, or the structure of the eBCS response element may be modified, or the structure of the eBCS request element and the structure of the eBCS response element may be modified, so as to reduce the data authentication delay in the eBCS acquisition process and alleviate the data loss problem caused by the eBCS authentication delay. The application enables the eBCS to support the termination notification process only by registering through modifying the structure of the ANQP element of the enhanced broadcast request.

Drawings

FIG. 1 provides a schematic flow diagram of eBCS DL;

FIG. 2 is a diagram of an enhanced broadcast response ANQP element structure in an ANQP response;

FIG. 3 is a schematic diagram of an eBCS response element structure in an eBCS response;

FIG. 4 is a schematic diagram of the structure of an eBCS information frame;

FIG. 5 is a sequence diagram of eBCS fast discovery with PKFA authentication;

fig. 6 is a sequence diagram of a service fast discovery in HCFA authentication;

FIG. 7 is a flow diagram of a termination notification process negotiation flow;

FIG. 8 is a block diagram of an eBCS termination notification frame;

FIG. 9 is a diagram of the eBCS request element structure;

FIG. 10 is a diagram of the structure of eBCS response elements;

FIG. 11 is a diagram illustrating an enhanced broadcast request ANQP element structure;

FIG. 12 is a diagram of an enhanced broadcast service ANQP element structure;

FIG. 13 is a sequence diagram illustrating negotiation of an eBCS termination notification procedure requiring registration and association;

fig. 14 is an interaction flow diagram of a wireless communication method according to an embodiment of the present application;

fig. 15 is a schematic diagram illustrating an enhanced broadcast request ANQP element structure according to an embodiment of the present application;

fig. 16 is a diagram illustrating another structure of an enhanced broadcast request ANQP element according to an embodiment of the present application;

fig. 17 is a diagram illustrating a structure of an ANQP element for a further enhanced broadcast request according to an embodiment of the present application;

fig. 18 is a schematic structural diagram of an enhanced broadcast response ANQP element according to an embodiment of the present application;

fig. 19 is a schematic diagram illustrating another structure of an enhanced broadcast response ANQP element according to an embodiment of the present application;

fig. 20 is a schematic structural diagram of an eBCS request element according to an embodiment of the present application;

fig. 21 is a schematic structural diagram of an eBCS response element according to an embodiment of the present application;

fig. 22 is a schematic structural diagram of another eBCS response element provided in this application embodiment;

fig. 23 is a timing diagram of fast acquiring eabcs in PKFA mode according to an embodiment of the present application;

fig. 24 is a timing chart of fast acquiring eBCS in the HCFA mode according to the embodiment of the present application;

fig. 25 is an interaction flow diagram of another wireless communication method provided in an embodiment of the present application;

fig. 26 is a schematic diagram illustrating an enhanced broadcast request ANQP element structure according to an embodiment of the present application;

fig. 27 is a diagram illustrating another structure of an enhanced broadcast request ANQP element according to an embodiment of the present application;

fig. 28 is a diagram illustrating another structure of an enhanced broadcast request ANQP element according to an embodiment of the present application;

fig. 29 is a negotiation timing chart of an eBCS termination notification procedure requiring only registration according to an embodiment of the present application;

fig. 30 shows a schematic block diagram of a STA3000 according to an embodiment of the present application;

FIG. 31 shows a schematic block diagram of a transmit end 3100 in accordance with an embodiment of the present application;

fig. 32 shows a schematic block diagram of an AP3200 according to an embodiment of the application;

fig. 33 shows a schematic block diagram of a receiving end 3300 according to an embodiment of the present application;

fig. 34 is a schematic structural diagram of a communication device 3400 provided in an embodiment of the present application;

fig. 35 is a schematic configuration diagram of an apparatus according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art without making any creative effort with respect to the embodiments in the present application belong to the protection scope of the present application.

Before the technical scheme of the application is introduced, the related knowledge of the application is explained as follows:

ieee802.11bc provides an Enhanced Broadcast Service DownLink (eBCS DL) for enabling an Access Point (AP) to Broadcast data to STAs.

It should be understood that the AP is also referred to as an eBCS AP and the STA is also referred to as an eBCS non-AP STA in the present application, which is not limited by the present application.

In the eBCS DL flow, the AP periodically broadcasts an eBCS information frame to discover the eBCS DL service and provide Authentication (Authentication) information of the eBCS (i.e., eBCS data). The scheme mainly improves the eBCS in the eBCS DL process to quickly acquire service and perfects the negotiation process of the termination notification process.

Fig. 1 provides a schematic flow diagram of eBCS DL. As shown in fig. 1, the specific process includes:

(1) In the scanning phase, the AP transmits a Beacon (Beacon) frame or a Probe Response (Probe Response) frame, which carries a field about the Next ebscs information frame (Next ebscs Info frame) to inform the STA of the broadcast time of the Next ebscs information frame.

(2) After receiving the eBCS information frame at the designated time, the STA acquires the transmission time and the authentication information of the eBCS data (data) frame. Therefore, the STA receives the eBCS data frame broadcasted by the AP at a designated time, thereby acquiring the eBCS.

It should be understood that the eBCS data frame in the present application is also referred to as an eBCS or an eBCS data, and the present application is not limited thereto.

(3) Besides the above-mentioned STA passively acquiring the eBCS, the eBCS DL flow also supports the STA sending an ANQP request or an eBCS request to actively request one or more eBCS services, so as to achieve the purpose of rapidly discovering the eBCS. For eBCS which needs to be registered but does not need to be associated, the STA completes eBCS service rapid discovery through the ANQP request and the ANQP response frame, so that the sending time of the eBCS is obtained; for the eBCS service needing to be associated, the STA completes the rapid discovery of the eBCS service through the eBCS request and the eBCS response frame, so that the sending time of the eBCS data is obtained. Fig. 2 is a schematic diagram of an Enhanced Broadcast Response ANQP element structure (Enhanced Broadcast Response ANQP-element) in an ANQP Response, and fig. 3 is a schematic diagram of an eBCS Response element structure (eBCS Response element) in an eBCS Response, as shown in fig. 2 and fig. 3, both the Enhanced Broadcast Response ANQP element structure and the eBCS Response element structure do not include authentication information of eBCS data.

(4) Therefore, after acquiring the eBCS data frame, the STA must wait for the eBCS information frame to acquire the authentication information of the eBCS data frame.

Further, after the STA receives the eBCS data frame, for different eBCS data authentication methods, a data authentication process in different methods is adopted, which is specifically divided into the following 3 types:

a) If the authentication is the PKFA authentication, the STA needs to wait for receiving the eBCS information frame. The Certificate (Certificate) of the AP is then cached from the eBCS info frame to authenticate the eBCS data, which in this case is also referred to as PKFA MPDU. PKFA is mainly suitable for occasional small data transmissions or time-sensitive data transmissions.

b) If the STA is an HCFA that does not perform immediate authentication, the STA needs to wait for receiving an eBCS Info frame, extract eBCS Info Interval (eBCS Info Interval), HCFA Base Key (HCFA Base Key), and HCFA Key Change Interval (HCFA Key Change Interval) information from the eBCS Info frame, and extract information such as HCFA Base Key published in subsequent eBCS data to authenticate the eBCS data, which is also referred to as HCFA MPDU.

c) In order to perform the HCFA for immediate authentication, the STA needs to wait for receiving the eBCS information frame, and extract the Number Of immediate Authenticators (Number Of Instant Authenticators), the Hash Distance Of the immediate Authenticators (Instant Authenticator Hash Distance), and the immediate Authenticator (Instant Authenticator) information from the eBCS information frame to authenticate the eBCS data, which is also referred to as an HCFA MPDU in this case. It should be noted that, for the eBCS data authenticated by the HCFA, before receiving the eBCS information frame, the STA discards the received eBCS data because the STA does not obtain the authentication information of the eBCS data.

Fig. 4 is a schematic structural diagram of an eBCS information frame, and as shown in fig. 4, the eBCS information frame includes important information about the eBCS, which is mainly divided into time dimension information and authentication dimension information. The time dimension information includes an eBCS information frame Interval (eBCS Info Interval) and a Next data frame transmission time (Next Schedule) corresponding to the eBCS identified by each Content (Content) identifier (Identity, ID). The authentication dimension information includes authentication Certificate (Certificate), HCFA Base Key (HCFA Base Key), HCFA Key Change Interval (HCFA Key Change Interval) information, and the like.

Under the existing 802.11bc standard, the eBCS rapid discovery process aiming at different authentication modes is as follows:

eBCS fast discovery process adopting PKFA authentication mode

Fig. 5 is a sequence diagram of an eBCS rapid discovery with PKFA authentication, as shown in fig. 5, when an STA joins an existing communication network at the time point shown in fig. 5. Because the transmission period of the eBCS information frame is very long and the transmission interval is TBTTs, it is assumed that the STA at this time misses the first eBCS information frame in the figure, and it cannot acquire the information about PKFA authentication in the eBCS information frame. Aiming at eBCS which needs to be registered but does not need to be associated, STA completes eBCS service rapid discovery through ANQP request/ANQP response frame, thereby obtaining the sending time of PKFA MPDU; aiming at eBCS needing to be associated, the STA completes eBCS service rapid discovery through the eBCS request and the eBCS response frame after completing the association, thereby obtaining PKFA MPDU sending time. The specific process is as follows:

(1) The STA receives the beacon frame or the probe response frame, and informs the STA of the broadcast time of the Next ebsc information frame (Next ebsc Info frame) through a field in the frame about the Next ebsc information frame.

(2) The STA completes eBCS quick discovery through the ANQP request and ANQP response frame, the eBCS request and the eBCS response frame, and therefore PKFA MPDU sending time is obtained. However, authentication information of the PKFA MPDU does not exist in the ANQP response or the eBCS response, and thus, even if the STA can receive the PKFA MPDU, it cannot authenticate the PKFA MPDU. Assuming the credentials of the second eBCS information frame are within a limited period, the STA buffers the PKFA MPDU and waits for the arrival of the second eBCS information frame.

(3) And when the STA receives the second eBCS Info frame, the sending time and the authentication information of the PKFA MPDU are obtained, the authentication information is cached, and the PKFA MPDU is verified by utilizing the cached authentication information. And obtaining eBCS after the verification is successful.

Fig. 6 is a timing chart of fast discovery of services by HCFA authentication, when the STA joins the existing communication network at the time point shown in fig. 6, because the transmission period of the eBCS information frame is large and the transmission interval is TBTTs, it cannot acquire information about HCFA authentication in the eBCS information frame, assuming that the STA at this time misses the first eBCS information frame. For eBCS which needs to be registered but does not need to be associated, the STA completes the rapid discovery of the eBCS through the ANQP request and the ANQP response frame, so that the sending time of the HCFA MPDU is obtained; for eBCS needing to be associated, the STA completes eBCS fast discovery through an eBCS request and an eBCS response frame after completing the association, and therefore HCFA MPDU sending time is obtained. The specific process is as follows:

(2) The STA completes eBCS quick discovery through an ANQP request and an ANQP response or an eBCS request and eBCS response mode, so that the sending time of the HCFA MPDU is obtained. However, no HCFA authentication information exists in the ANQP response or the eBCS response, and thus even if the STA can receive the HCFA MPDU, it cannot authenticate the HCFA MPDU. Therefore, before receiving no eBCS information frame, the STA discards the HCFA MPDU and waits for the arrival of a second eBCS information frame.

(3) And when the STA receives the second eBCS information frame, acquiring the time information and the authentication information of the HCFA MPDU. And according to the Next data frame transmission time (Next Schedule) indicated in the eBCS information frame, the STA waits for the arrival of the HCFA MPDU at the corresponding time point.

(4) When the STA receives the HCFA MPDU, the key verifying the HCFA MPDU is not disclosed, so the STA buffers the HCFA MPDU and waits for the key corresponding to the HCFA MPDU to be disclosed. The HCFA algorithm is a key delay disclosure algorithm, and the assumed key disclosure time is delayed with respect to the time of HCFA MPDU reception as shown in fig. 6. After the public key is acquired at the assumed time point, the STA authenticates the HCFA MPDU buffered before according to the time scale. The latest time point of key delay disclosure is when the third eBCS information frame is received, since the key information is contained in the field of this eBCS information frame. And obtaining eBCS after the verification is successful.

Negotiation technical scheme for terminating notification process

Referring to the termination notification procedure described in 802.11bc, when the sender is about to terminate an eBCS, the specific negotiation flow is shown in fig. 7:

it should be understood that the transmitting end is a device for broadcasting data, the transmitting end may be an STA, and correspondingly, the receiving end may be an AP. Or, the sending end may be an AP, and correspondingly, the receiving end may be an STA, which is not limited in this application.

Fig. 7 is a flow chart illustrating negotiation of the termination notification procedure, as shown in fig. 7,

(1) When an eBCS is about to terminate within a Time interval less than or equal to an eBCS Termination notification Time (eBCS Termination notification Time) specified by the protocol, the sender sends an eBCS Termination notification (eBCS Termination notification) frame to inform the receiver of the expected Termination Time of the eBCS. In addition, the eBCS Termination notification frame indicates, in addition To the eBCS Termination Time (Time To Termination) corresponding To the Content (Content) ID specific To the eBCS, the following extended information that needs To be extended by the eBCS if necessary, including a service Address (Destination Address) and a service extension Request Method (Request Method), and fig. 8 is a schematic structural diagram of the eBCS Termination notification frame, as shown in fig. 8.

(2) If the eBCS expected termination time indicated in the eBCS termination notification frame is acceptable to the receiver, the eBCS will terminate exactly according to the expected termination time, wherein the acceptable termination time for the receiver is not specified in the 802.11bc standard. If the expected eBCS termination time indicated in the eBCS termination notification frame is earlier than the time that the receiving end actually expects to terminate, the receiving end requests the eBCS to be extended according to the eBCS extension information indicated by the received eBCS termination notification frame. The eBCS extension Request mode (Request Method) can adopt two modes of eBCS Request or ANQP Request.

(3) For the eBCS that needs to be registered and associated, the receiving end sends an eBCS request carrying a request Termination Time (Requested Time to Termination), so that after the request eBCS is successfully extended, the sending end carries the Termination Time (Time to Termination) in the eBCS response to reply a new eBCS Termination Time to the receiving end, as shown in fig. 9 and 10.

(4) For the eBCS that only needs to register and does not need to be associated, the receiving end sends an ANQP request including an enhanced broadcast request ANQP element structure, and after the request eBCS is successfully extended, the sending end carries the termination time in the enhanced broadcast service ANQP element structure included in the ANQP response, so as to reply the new eBCS termination time to the receiving end, as shown in fig. 11 and 12. However, in fig. 11, the ANQP element structure of the enhanced broadcast request has no relevant field of the termination time, so that the request and negotiation cannot be performed for the new eBCS termination time, and the purpose of the eBCS extension cannot be achieved.

For the negotiation of the eBCS termination notification procedure that requires registration and association, a specific negotiation timing diagram is shown in fig. 13:

s1301: the sender determines that the eBCS is to be terminated.

Optionally, the terminating eBCS includes: media Access Control (MAC) broadcasts terminate and the application layer may still create a data source situation.

S1302: the transmitting end generates a termination notification frame.

S1303: the transmitting end transmits a termination notification frame to the receiving end.

S1304: the receiving end acquires eBCS Termination Time (Time To Termination), service Address (Destination Address) and service extension Request mode (Request Method) corresponding To the content identification from the Termination notification frame.

S1305: if the receiver determines that the expected eBCS termination time indicated in the eBCS termination notification frame is acceptable to the receiver, the eBCS is terminated strictly according to the expected termination time.

S1306: if the expected expiration time of the eBCS indicated in the eBCS expiration notification frame is earlier than the time that the receiving end actually expects expiration, the receiving end generates an eBCS Request (Request frame).

S1307: the receiving end sends the eBCS request to the sending end.

The eBCS request includes: the content ID (eBCS) and the Request termination time (Request time to termination) of the eBCS. Optionally, the eBCS request includes: an eBCS Request Information Set (eBCS Request Information Set) including a Request termination time.

S1308: after receiving the eBCS Request, the sender analyzes the Request termination time (Request time to termination) from the eBCS Request, so that the sender acquires the newly requested eBCS termination time.

S1309: the sender generates an eBCS Response (eBCS Response frame).

S1310: and the transmitting end transmits the eBCS response to the receiving end.

The eBCS response includes a content ID (content ID), a Time to Termination (Time to Termination), a Service Process duration (duration), and an SP Interval (interval) corresponding to the eBCS. Optionally, the eBCS Response includes an eBCS Response information set (eBCS Response information set) including a Time to Termination (Time to Termination).

S1311: after receiving the eBCS response, the receiving end analyzes the Termination Time (Time to Termination) from the eBCS response to acquire the negotiated eBCS Termination Time.

The application mainly solves the following two technical problems:

1. as described above, in the standard 802.11bc, the STA quickly discovers eBCS through ANQP request and ANQP response, or through eBCS request and eBCS response. However, the enhanced broadcast response ANQP element structure in the current ANQP response does not have the authentication information of the eBCS, and similarly, the eBCS response element structure in the current eBCS response does not have the authentication information of the eBCS. Therefore, the STA cannot obtain the authentication information of the eBCS through the ANQP request/ANQP response, the eBCS request, and the eBCS response, but must wait to receive the eBCS information (Info) frame before obtaining the authentication information of the eBCS, which results in a problem of large data authentication delay and data loss caused by the eBCS authentication delay in the eBCS obtaining process.

2. For the eBCS which only needs to be registered, after the sending end sends an eBCS termination notification frame to the receiving end, if the eBCS expected termination time indicated in the eBCS termination notification frame is earlier than the time actually expected to be terminated by the receiving end, the receiving end requests the extension of the eBCS by adopting an ANQP request mode according to the eBCS extended information indicated by the received eBCS termination notification frame. But there is no end of service time field in the current enhanced broadcast request ANQP element structure. Therefore, this element structure cannot support the eBCS termination notification procedure that only needs to be registered.

In view of the above technical problem 1, the present application mainly adopts the following ways to solve the technical problem: modifying an enhanced broadcast response (ANQP) element structure, or modifying an enhanced broadcast request (ANQP) element structure and modifying an enhanced broadcast response (ANQP) element structure, or modifying an eBCS response element structure, or modifying an eBCS request element structure and an eBCS response element structure.

In view of the above 2 nd technical problem, the present application mainly adopts the following method to solve the technical problem: the enhanced broadcast request ANQP element structure is modified.

The technical scheme of the application is explained in detail as follows:

fig. 14 is an interaction flowchart of a wireless communication method according to an embodiment of the present application, and as shown in fig. 14, the method includes the following steps:

s1410: the STA sends a first request to the AP, wherein the first request is used for requesting to acquire the eBCS.

S1420: the AP sends a first response to the STA, wherein the first response comprises: authentication information of the eBCS.

The first alternative is as follows: the eBCS is an eBCS which needs to be registered and does not need to be associated, correspondingly, the first request is an ANQP request, and the first response is an ANQP response.

The second option is: the eBCS is the eBCS needing to be associated, correspondingly, the first request is an eBCS request, and the first response is an eBCS response.

The ANQP request in option one is exemplarily illustrated as follows:

fig. 15 is a schematic diagram of an Enhanced Broadcast Request ANQP element structure provided in an embodiment of the present application, and as shown in fig. 15, an Enhanced Broadcast service Request Control (Enhanced Broadcast Services Request Control) field is added to an Enhanced Broadcast service Request tuple (Enhanced Broadcast Services Request tuple) of the Enhanced Broadcast Request ANQP element structure, and Request Authentication information (Request Authentication Info) is added under the Enhanced Broadcast service Request Control field, where the Request Authentication information is used to indicate whether to Request to acquire Authentication information of eBCS. Optionally, when the value of the request authentication information is 1, the STA is instructed to request the eBCS to acquire quickly, and request to acquire the authentication information of the eBCS; and when the value of the request authentication information is 0, indicating the STA not to request the authentication information of the eBCS.

Alternatively, as shown in fig. 15, a request Termination Time indication (Requested Time To Termination Present) may be included in the enhanced broadcast service request control field, which is used for the Termination notification procedure of the STA.

Alternatively, as shown in fig. 15, the enhanced broadcast service request tuple may include a request Termination Time (Requested Time to Termination).

Optionally, as shown in fig. 15, the enhanced broadcast service Request control field may include a Request Target AP information indication (Request Target AP Info Present) for an AP-to-AP Request procedure of the STA, which is not described in detail in this embodiment.

Optionally, as shown in fig. 15, the enhanced broadcast Service request tuple may include a Target AP (Target AP) Basic Service Set Identifier (BSSID).

Example 2, fig. 16 is a schematic diagram of another enhanced broadcast request ANQP element structure provided in an embodiment of the present application, and as shown in fig. 16, an enhanced broadcast service request control field is not added in the enhanced broadcast request ANQP element structure. But adds the request authentication information in a reserved field of a Broadcast Action (Broadcast Action) field.

Example 3, in the enhanced broadcast request ANQP element structure, no field is added, as shown in fig. 11. And the default AP will carry the authentication information of eBCS in the ANQP response.

Example 4, fig. 17 is a schematic diagram of a structure of another enhanced broadcast request ANQP element provided in an embodiment of the present application, and as shown in fig. 17, an enhanced broadcast service request tuple in the structure of the enhanced broadcast request ANQP element includes request authentication information.

It should be noted that the above examples 1 to 4 are only a few examples of modifying the structure of the enhancement broadcast request ANQP element, but are not limited thereto. And the length of each field in the structure regarding the enhanced broadcast request ANQP element is not limited to the field lengths shown in fig. 15 to 17 and fig. 11.

An example is made for the ANQP response in option one:

fig. 18 is a schematic diagram of an Enhanced Broadcast service Response ANQP element structure provided in an embodiment of the Present application, and as shown in fig. 18, an Enhanced Broadcast service Response Control field (Enhanced Broadcast service Response Control) field is added in an Enhanced Broadcast service Response tuple (Enhanced Broadcast service Response tuple) of the Enhanced Broadcast Response ANQP element structure, and a Response Authentication information indication (Response Authentication information Present) is added under the Enhanced Broadcast service Response Control field. Optionally, when the response authentication information indication value is 1, the STA is indicated to successfully request the eBCS to quickly acquire, and the authentication information of the eBCS is added to the enhanced broadcast service response tuple; when the response authentication information indicates that the value is 0, indicating that the STA cannot obtain the authentication information of the eBCS, that is, the authentication information of the eBCS is not added in the structure of the enhanced broadcast response ANQP element.

Optionally, the authentication information of the eBCS includes: an Authentication Algorithm (Authentication Algorithm) field to indicate an Authentication Algorithm employed for the eBCS.

Optionally, the authentication algorithm is any one of the following, but is not limited thereto: the method does not perform Frame Authentication, and forces Higher-level Source Authentication (No Frame Authentication With management high Layer Source Authentication, HLSA), PKFA, HCFA without immediate Authentication, and HCFA With immediate Authentication.

Optionally, the authentication algorithm of eBCS is shown in table 1:

TABLE 1eBCS authentication algorithm

Value taking	Authentication algorithm
		0	HLSA
1	PKFA
		2	HCFA without immediate authentication
3	HCFA performing immediate authentication
		4-255	Reserved value

Optionally, if the corresponding value of the authentication algorithm is 0, the eabcs authentication mode of the request is indicated as HLSA, and the relevant authentication information field does not exist. If the corresponding value of the authentication algorithm is 1, indicating that the eBCS authentication mode of the request is PKFA, the authentication information further comprises: allowable Time Difference (Allowable Time Difference), authentication Certificate Length (Certificate Length), and authentication Certificate (Certificate). If the corresponding value of the authentication algorithm is 2, indicating that the requested eBCS authentication mode is an HCFA which does not perform immediate authentication, the authentication information further comprises: allowed Time Difference (Allowable Time Difference), eBCS information frame Interval (eBCS Info Interval), HCFA Key Change Interval (HCFA Key Change Interval), and HCFA Base Key (HCFA Base Key). If the corresponding value of the authentication algorithm is 3, indicating that the requested eBCS authentication mode is the HCFA performing immediate authentication, the authentication information further includes: an Allowable Time Difference (Allowable Time Difference), a Number Of immediate Authenticators (Number Of Instant Authenticators), an immediate Authenticator List (Instant Authenticator List), and the immediate Authenticator List includes: the Hash Distance of the immediate Authenticator (Instant Authenticator Hash Distance) and the immediate Authenticator field.

It should be noted that, for the explanation of each item of information included in the authentication information, reference may be made to the contents in standard 802.11bc, which is not described in this application.

Optionally, the enhanced broadcast response ANQP element structure may further include: the Response Target AP information indication (Response Target AP Info Present) and/or the Response Target AP information (Response Target AP Info) are used for the cross-AP Response procedure of the STA, and are not described in detail in this solution.

Fig. 19 is a schematic diagram of another Enhanced Broadcast service Response ANQP element structure according to an embodiment of the present disclosure, and as shown in fig. 19, an Enhanced Broadcast service Response Control field (Enhanced Broadcast service Response Control) field is not added in an Enhanced Broadcast service Response tuple (Enhanced Broadcast service Response packets) of the Enhanced Broadcast service Response ANQP element structure. Instead, the authentication information of the eBCS is directly added to the enhanced broadcast service response tuple, and for the authentication information, reference may be made to the explanation of example 1 above, which is not described herein again.

It should be noted that the above examples 1 to 2 are only a few examples of modifying the structure of the enhancement broadcast response ANQP element, but are not limited thereto. And the length of each field in the structure regarding the enhanced broadcast response ANQP element is not limited to the field lengths shown in fig. 18 and 19.

An example explanation is made for the eBCS request in option two:

example 1, fig. 20 is a schematic diagram of an eBCS Request element structure provided in an embodiment of the present application, as shown in fig. 20, an eBCS Request Information Set (eBCS Request Information Set) in the eBCS Request element structure includes an eBCS Request Information Control (eBCS Request Info Control) field, and Request authentication Information is added under the eBCS Request Information Control, where the Request authentication Information is used to indicate whether to Request to acquire authentication Information of an eBCS. Optionally, when the value of the request authentication information is 1, the STA is instructed to request the eBCS to acquire quickly, and request to acquire the authentication information of the eBCS; and when the value of the request authentication information is 0, indicating the STA not to request to acquire the authentication information of the eBCS.

Example 2, in the eBCS request element structure, no field is added, as shown in fig. 9. And the default AP will carry the authentication information of the eBCS in the eBCS response.

It should be noted that the above examples 1 to 2 are only a few examples of modifying the structure of the eBCS request element, but are not limited thereto. And the length of each field in the structure regarding the eBCS request element is not limited to the field lengths shown in fig. 20 and 9.

An example explanation is made for the eBCS response in option two:

example 1, fig. 21 is a schematic diagram of an eBCS response element structure provided in an embodiment of the present application, and as shown in fig. 21, the eBCS response element structure includes: an eBCS Response Information Set (eBCS Response Information Set), the eBCS Response Information Set comprising: an eBCS Response information Control (eBCS Response Info Control) field to which a Response Authentication information indication (Response Authentication Info present) is added. Optionally, when the increase response authentication information indication value is 1, the STA is indicated to successfully request the eBCS to quickly acquire, and the authentication information of the eBCS is added to the eBCS response information set; and when the increased response authentication information indication value is 0, indicating the STA to request the eBCS to rapidly acquire failure, and not increasing the authentication information of the eBCS in an eBCS response element structure.

Fig. 22 is a schematic diagram of another structure of an eBCS Response element provided in the embodiment of the present application, and as shown in fig. 22, a Response Authentication information indication (Response Authentication information present) is not added to an eBCS Response information control field in the structure of the eBCS Response element, and an eBCS Response element structure of a default AP directly carries Authentication information of an eBCS.

It should be noted that, for different authentication algorithms, reference may be specifically made to the foregoing for corresponding to different authentication information, which is not described in detail herein. For the explanation of each item of information included in the authentication information, reference may be made to the contents of standard 802.11bc, which is not described in this application.

It should be noted that the above examples 1 to 2 are only a few examples of modifying the structure of the eBCS response element, but are not limited thereto. And the length of each field in the structure of the eBCS response element is not limited to the field lengths shown in fig. 21 and 22.

In summary, in the present application, the structure of the enhanced broadcast response ANQP element may be modified, or the structure of the enhanced broadcast request ANQP element and the structure of the enhanced broadcast response ANQP element may be modified, or the structure of the eBCS response element may be modified, or the structure of the eBCS request element and the structure of the eBCS response element may be modified, so as to reduce the data authentication delay in the eBCS acquisition process and alleviate the data loss problem caused by the eBCS authentication delay.

The eBCS fast acquisition process adopting the PKFA authentication mode will be described as follows:

in 802.11bc, eBCS DL supports both associated and non-associated eBCS. Consider that the STA quickly discovers eBCS using ANQP requests and ANQP responses, or eBCS requests and eBCS responses. Aiming at the PKFA authentication mode, the authentication information of the eBCS is added in the ANQP response or the eBCS response, and the eBCS of the PKFA authentication can be quickly acquired. Fig. 23 is a timing diagram of fast acquiring eabcs in the PKFA mode according to the embodiment of the present application, and the specific flow is as follows:

(1) In the scanning phase, the STA joins the existing communication network by receiving a beacon frame or a probe response frame at a point of time in fig. 23. Since 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.

(2) And the STA requests to quickly acquire the required service content by adopting an ANQP (internet request for protocol) request or an eBCS (embedded binary system control) request mode according to the condition whether the association is required or not. Aiming at eBCS which needs to be registered but does not need to be associated, STA completes eBCS fast acquisition through ANQP request and AN response, thereby obtaining PKFA MPDU sending time and authentication information; for eBCS needing to be associated, the STA completes the rapid acquisition of eBCS service through an eBCS request and an eBCS response after the association, thereby obtaining PKFA MPDU sending time and authentication information.

(3) And when the STA receives the ANQP response or the eBCS response, the sending time and the authentication information of the PKFA MPDU are obtained, and the authentication information is cached.

(4) And finally, the STA receives the PKFA MPDU at the appointed time and authenticates the integrity of the PKFA MPDU by using the cached authentication information.

In summary, the sequence diagram of the eBCS fast acquisition for PKFA authentication is shown in fig. 23. As can be seen from comparing fig. 5 and fig. 23, in the PKFA authentication mode, if the fast service acquisition mode provided by the present application is adopted, on one hand, the time for the STA to acquire the eBCS is saved, and on the other hand, the utilization rate of the PKFA MPDU is also improved.

The fast eBCS acquisition process using HCFA authentication will be described as follows:

as described above, in the eBCS DL of 802.11bc, in the HCFA authentication scheme, the STA must wait for the eBCS information frame to acquire information of HCFA authentication (i.e., authentication information of the eBCS). According to the method and the device, the HCFA authentication information is newly added in the ANQP response or the eBCS response, and the eBCS of the HCFA authentication is rapidly acquired. Fig. 24 is a timing diagram for rapidly acquiring eBCS in the HCFA mode according to the embodiment of the present application, and the specific flow is as follows:

(1) In the scanning phase, the STA joins the existing communication network by receiving a beacon frame or a probe response frame at a point of time as shown in fig. 24. Since the transmission period of the eBCS information frame is very long and the transmission interval is TBTTs, it is assumed that the STA misses the first eBCS information frame at this time.

(2) And the STA requests to quickly acquire the required service content by adopting an ANQP (internet request for protocol) request or an eBCS (embedded binary system control) request mode according to the condition whether the association is required or not. Aiming at eBCS which needs to be registered but does not need to be associated, STA completes eBCS fast acquisition through ANQP request and ANQP response, thereby obtaining HCFA MPDU sending time and authentication information; for eBCS needing to be associated, the STA completes the rapid acquisition of eBCS service through an eBCS request and an eBCS response after the association, thereby obtaining HCFA MPDU sending time and authentication information.

(3) For the eBCS of the HCFA which does not perform immediate authentication, the ANQP response or the eBCS response is newly added with the information of three fields of an eBCS information frame Interval (eBCS Info Interval), an HCFA Key Change Interval (HCFA Key Change Interval) and an HCFA Base Key (HCFA Base Key). For an eBCS for HCFA authentication for immediate authentication, three fields Of the Number Of immediate Authenticators (Number Of Instant Authenticators), the Hash Distance Of the immediate Authenticators (Instant Authenticator Hash Distance) and the immediate Authenticators (Instant Authenticator) are newly added to the ANQP response or the eBCS response. And after receiving the ANQP response or the eBCS response, the STA acquires the sending time and the authentication information of the HCFA MPDU, caches the authentication information and waits for receiving the HCFA MPDU.

(4) And the STA receives the HCFA MPDU, caches the HCFA MPDU and waits for the public key corresponding to each HCFA MPDU because the HCFA authentication information is acquired. The HCFA is a delayed public mode using a secret key, assuming that the time for disclosing the HCFA MPDU secret key of the DL eBCS1 is as shown in fig. 24, after the STA acquires the public secret key at an assumed time point, the STA de-authenticates the HCFA MPDU that is cached before according to a time scale. The latest time point of key delay disclosure is when the second eBCS information frame in the figure is received, and the HCFA MPDU key information is contained in the field of this eBCS information frame.

In summary, the sequence diagram of eBCS fast acquisition for HCFA authentication is shown in fig. 24. As can be seen from comparing fig. 6 and fig. 24, in the HCFA authentication mode, if the fast service discovery method provided by the present application is adopted, on one hand, the time for the STA to acquire the eBCS service is saved, and on the other hand, the utilization rate of the HCFA MPDU is also improved.

Fig. 25 is an interaction flowchart of another wireless communication method according to an embodiment of the present application, and as shown in fig. 25, the method includes the following steps:

s2510: the sending end sends an ANQP request to the receiving end, wherein the ANQP request comprises the following steps: and requesting the termination time, wherein the request termination time is the time when the sender requests the termination of the eBCS.

Optionally, the eBCS is an eBCS that needs registration and does not need association, and the ANQP request is used to request extension of the eBCS.

Optionally, the sending end may be an AP and the receiving end is an STA, or the sending end may be an STA and the receiving end is an AP.

An exemplary illustration is made for the ANQP request:

fig. 26 is a schematic diagram of an Enhanced Broadcast Request ANQP element structure provided in an embodiment of the present application, and as shown in fig. 26, an Enhanced Broadcast service Request Control (Enhanced Broadcast service Request Control) field and a Request Termination Time (Requested Time to Termination) are added to an Enhanced Broadcast service Request tuple (Enhanced Broadcast service Request tuple) of the Enhanced Broadcast Request ANQP element structure, where the Enhanced Broadcast service Request Control field is used by a receiving end to negotiate an eBCS Termination Time with a sending end. A request Termination Time indication (Requested Time to Termination Present) is added under the enhanced broadcast service request control field. Optionally, when the request termination time indication value is 1, indicating that the request termination time exists; when the request termination time indication value is 0, it indicates that the request termination time does not exist.

Optionally, the remaining part of the enhanced broadcast service request control field is a reserved field.

Optionally, the enhanced broadcast service request control field further includes: request Authentication information (Request Authentication Info) for eBCS fast acquisition by the STA.

Optionally, the enhanced broadcast service request control field further includes: the Request Target AP information indication (Request Target AP Info Present) is used for an AP-crossing Request process of the STA, and is not described in detail in this embodiment.

Alternatively, as shown in fig. 26, the enhanced broadcast service request tuple may include a Target AP basic service set identification (Target AP BSSID).

Example 2, fig. 27 is a schematic diagram of another enhanced broadcast request ANQP element structure provided in the embodiment of the present application, and as shown in fig. 27, in the enhanced broadcast request ANQP element structure, an enhanced broadcast service request control field and a request termination time indication are not additionally added, and the request termination time is carried in the enhanced broadcast request ANQP element structure by default.

Example 3, fig. 28 is a schematic diagram of another enhanced broadcast request ANQP element structure provided in an embodiment of the present application, and as shown in fig. 28, in the enhanced broadcast request ANQP element structure, a request termination time indication is added by using other reserved fields of the enhanced broadcast request ANQP element structure, such as a reserved field under a broadcast action field, instead of additionally adding an enhanced broadcast service request control field.

It should be noted that the above examples 1 to 3 are only a few examples of modifying the structure of the enhancement broadcast request ANQP element, but are not limited thereto. And the length of each field in the structure regarding the enhanced broadcast request ANQP element is not limited to the field lengths shown in fig. 26 and 28.

In conclusion, the application enables the eBCS which only needs to be registered to support the termination notification process by modifying the structure of the ANQP element of the enhanced broadcast request.

Negotiation scheme embodiments for termination notification procedure

The present application implements negotiation of an eBCS termination notification process that only needs to be registered, specifically, a specific negotiation timing chart is shown in fig. 29:

s2901: the sender determines that the eBCS is to be terminated.

Optionally, the terminating eBCS includes: the MAC broadcast terminates and the application layer may still create a data source situation.

S2902: the transmitting end generates a termination notification frame.

S2903: the transmitting end transmits a termination notification frame to the receiving end.

S2904: the receiving end acquires eBCS Termination Time (Time To Termination), service Address (Destination Address) and service extension Request mode (Request Method) corresponding To the content identification from the Termination notification frame.

S2905: if the receiver determines that the expected eBCS termination time indicated in the eBCS termination notification frame is acceptable to the receiver, the eBCS is terminated strictly according to the expected termination time.

S2906: if the eBCS expected termination time indicated in the eBCS termination notification frame is earlier than the time that the receiver actually expects termination, the receiver generates a Generic Advertisement Service (GAS) initial Request frame (interactive Request frame).

The GAS initial Request frame carries a Query Request (Query Request) field, the field includes an ANQP Request, the ANQP Request includes an enhanced broadcast Request ANQP element structure, and the element structure may include: content identification, broadcast action field, and request termination time.

S2907: the receiving end sends the GAS initial request frame to the transmitting end.

S2908: after receiving the GAS initial request frame, the transmitting end generates a GAS initial Response frame (GAS initial Response frame).

The GAS initial Response frame carries a Query Response (Query Response) field, and the field includes an ANQP Response, the ANQP Response includes an enhanced broadcast service ANQP element structure, and the element structure may include: content identification, expiration time, request mode, service address, etc.

S2909: and the transmitting end transmits the GAS initial response frame to the receiving end.

S2910: and after receiving the GAS initial response frame, the receiving end analyzes the termination time from the GAS initial response frame to acquire the negotiated eBCS termination time.

Fig. 30 shows a schematic block diagram of a STA3000 according to an embodiment of the present application. As shown in fig. 30, the STA3000 includes: a communication unit 3010 configured to: and sending a first request to the AP, wherein the first request is used for requesting to acquire the eBCS. Receiving a first response, the first response comprising: authentication information of the eBCS.

Optionally, the eBCS is an eBCS that needs registration and does not need association, and accordingly, the first request is an ANQP request, and the first response is an ANQP response.

Optionally, the ANQP request includes: the enhanced broadcast request ANQP element structure, and the enhanced broadcast request ANQP element structure includes: an enhanced broadcast service request tuple, the enhanced broadcast service request tuple comprising: authentication information is requested. The request authentication information is used for indicating whether to request to acquire the authentication information of the eBCS.

Optionally, the enhanced broadcast service request tuple includes: an enhanced broadcast service request control field, and the enhanced broadcast service request control field includes: authentication information is requested.

Optionally, the enhanced broadcast service request tuple includes: and broadcasting the action field, wherein the reserved field of the action field carries the request authentication information.

Optionally, the ANQP response further includes: in response to the authentication information indication. Wherein the response authentication information indicates authentication information indicating whether eBCS is included in the ANQP response.

Optionally, the enhanced broadcast service response control field includes: in response to the authentication information indication.

Optionally, the eBCS is an eBCS that needs to be associated, and correspondingly, the first request is an eBCS request, and the first response is an eBCS response.

Optionally, the eBCS request includes: an eBCS request element structure, and the eBCS request element structure includes: the eBCS request information set comprises the following steps: authentication information is requested. The request authentication information is used for indicating whether to request to acquire the authentication information of the eBCS.

Optionally, the eBCS request information set includes: the eBCS request information control field, and the eBCS request information control field includes: authentication information is requested.

Optionally, the eBCS response further includes: in response to the authentication information indication. Wherein the response authentication information indicates authentication information indicating whether the eBCS is included in the eBCS response.

Optionally, the eBCS response includes: an eBCS response information set, wherein the eBCS response information set comprises: in response to the authentication information indication.

Optionally, the eBCS response information set includes: an eBCS response information control field, the eBCS response information control field comprising: in response to the authentication information indication.

Optionally, the authentication information of the eBCS includes: an authentication algorithm field to indicate an authentication algorithm employed for the eBCS.

Optionally, the authentication algorithm is any one of the following: HLSA, PKFA, HCFA without immediate authentication, HCFA with immediate authentication.

Optionally, if the authentication algorithm is PKFA, the authentication information of the eBCS further includes: allowed time difference, authentication certificate length, authentication certificate.

Optionally, if the authentication algorithm is an HCFA that does not perform immediate authentication, the authentication information of the eBCS further includes: allowed time difference, eBCS information frame interval, HCFA key change interval, HCFA base key.

Optionally, if the authentication algorithm is an HCFA performing immediate authentication, the authentication information of the eBCS further includes: allowed time difference, number of immediate authenticators, list of immediate authenticators. Wherein the immediate authenticator list comprises: the hash distance of the immediate authenticator and the immediate authenticator field.

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

It should be understood that the STA3000 according to the embodiment of the present application may correspond to an STA in the method embodiment, and the above and other operations and/or functions of each unit in the STA3000 are respectively for implementing corresponding processes of the STA in the method embodiment, and are not described herein again for brevity.

Fig. 31 shows a schematic block diagram of a transmitting end 3100 according to an embodiment of the application. As shown in fig. 31, the transmit end 3100 includes: a communication unit 3110, configured to send an ANQP request to a receiving end, where the ANQP request includes: and requesting the termination time, wherein the request termination time is the time when the sender requests the termination of the eBCS.

Optionally, the ANQP request includes: the enhanced broadcast request ANQP element structure, and the enhanced broadcast request ANQP element structure includes: an enhanced broadcast service request tuple, the enhanced broadcast service request tuple comprising: a termination time is requested.

Optionally, the ANQP request includes: the action field is broadcast, and the reserved field of the action field carries the request termination time indication. Wherein the request termination time indication indicates whether the ANQP request includes a request termination time.

Optionally, the enhanced broadcast service request tuple includes: an enhanced broadcast service request control field, and the enhanced broadcast service request control field includes: an indication of the termination time is requested. Wherein the request termination time indication indicates whether the ANQP request includes a request termination time.

It should be understood that transmitting end 3100 according to an embodiment of the present application may correspond to a transmitting end in the method embodiment, and the above and other operations and/or functions of each unit in transmitting end 3100 are respectively for implementing a corresponding flow of the transmitting end in the method embodiment, and are not described herein again for brevity.

Fig. 32 shows a schematic block diagram of an AP3200 according to an embodiment of the application. As shown in fig. 32, the AP3200 includes: the communication unit 3210 is configured to receive a first request, where the first request is used to request to acquire an eBCS. Sending a first response to the station, the first response comprising: authentication information of eBCS.

Optionally, the ANQP response includes: an enhanced broadcast service response control field, the enhanced broadcast service response control field comprising: in response to the authentication information indication.

Optionally, the eBCS request includes: the eBCS request element structure, and the eBCS request element structure includes: the eBCS request information set comprises the following steps: authentication information is requested. The request authentication information is used for indicating whether to request to acquire the authentication information of the eBCS.

Optionally, the authentication algorithm is any one of: HLSA, PKFA, HCFA that does not perform immediate authentication, HCFA that performs immediate authentication.

It should be understood that the AP3200 according to the embodiment of the present application may correspond to an AP in a method embodiment, and the above and other operations and/or functions of each unit in the AP3200 are respectively for implementing a corresponding flow of the AP in the method embodiment, and are not described herein again for brevity.

Fig. 33 shows a schematic block diagram of a receiving end 3300 according to an embodiment of the present application. As shown in fig. 33, the receiving end 3300 includes: a communication unit 3310, configured to receive an ANQP request sent by a sending end, where the ANQP request includes: and requesting the termination time, wherein the request termination time is the time when the sender requests the termination of the eBCS.

Optionally, the ANQP request includes: the enhanced broadcast request ANQP element structure, and the enhanced broadcast request ANQP element structure comprises: an enhanced broadcast service request tuple, the enhanced broadcast service request tuple comprising: a termination time is requested.

It should be understood that the receiving end 3300 according to the embodiment of the present application may correspond to a receiving end in the method embodiment, and the above and other operations and/or functions of each unit in the receiving end 3300 are respectively for implementing a corresponding flow of the receiving end in the method embodiment, and are not described herein again for brevity.

Fig. 34 is a schematic structural diagram of a communication device 3400 provided in an embodiment of the present application. The communication device 3400 shown in fig. 34 includes a processor 3410, and the processor 3410 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.

Alternatively, as shown in fig. 34, the communication device 3400 may further include a memory 3420. The processor 3410 may call and run a computer program from the memory 3420 to implement the method in the embodiments of the present application.

The memory 3420 may be a separate device from the processor 3410 or may be integrated in the processor 3410.

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, may send information or data to the other devices or receive information or data sent by the other devices.

The transceiver 3430 may include a transmitter and a receiver, among others. The transceiver 3430 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 3400 may specifically be an STA according to the embodiment of the present application, and the communication device 3400 may implement a corresponding process implemented by the STA in each method according to the embodiment of the present application, which is not described herein again for brevity.

Optionally, the communication device 3400 may specifically be an AP according to the embodiment of the present application, and the communication device 3400 may implement a corresponding process implemented by the AP in each method according to the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the communication device 3400 may specifically be a transmitting end in this embodiment, and the communication device 3400 may implement a corresponding flow implemented by the transmitting end in each method in this embodiment, which is not described herein again for brevity.

Optionally, the communication device 3400 may specifically be a receiving end in the embodiment of the present application, and the communication device 3400 may implement a corresponding process implemented by the receiving end in each method in the embodiment of the present application, which is not described herein again for brevity.

Fig. 35 is a schematic configuration diagram of an apparatus according to an embodiment of the present application. The apparatus 3500 shown in fig. 35 comprises a processor 3510, and the processor 3510 can call up and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 35, the apparatus 3500 may further comprise a memory 3520. The processor 3510 can call and run a computer program from the memory 3520 to implement the method in the embodiment of the present application.

The memory 3520 may be a separate device from the processor 3510, or may be integrated into the processor 3510.

Optionally, the apparatus 3500 may further comprise an input interface 3530. 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 the other devices or chips.

Optionally, the apparatus 3500 may further comprise an output interface 3540. The processor 3510 may control the output interface 3540 to communicate with other devices or chips, and may output information or data to the other devices or chips.

Optionally, the apparatus may be applied to the network device in the embodiment of the present application, and the apparatus may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the apparatus may be applied to the terminal device in the embodiment of the present application, and the apparatus may implement the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.

Optionally, the device mentioned in this embodiment of the present application may also be a chip. For example, it may be a system-on-chip, a system-on-chip or a system-on-chip, etc.

It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or 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), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the STA, the AP, the sending end, or the receiving end in this embodiment, and the computer program enables the computer to execute a corresponding process implemented by the STA, the AP, the sending end, or the receiving end in each method in this embodiment.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to the STA, the AP, the sending end, or the receiving end in this embodiment, and the computer program instructions enable the computer to execute corresponding processes implemented by the STA, the AP, the sending end, or the receiving end in each method in this embodiment.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to the STA, the AP, the sending end, or the receiving end in this embodiment, and when the computer program runs on a computer, the computer executes a corresponding process implemented by the STA, the AP, the sending end, or the receiving end in each method in this embodiment, which is not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. With regard to such understanding, the technical solutions of the present application may be essentially implemented or contributed to by the prior art, or may be implemented in a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, comprising:

a site sends a first request to an access point, wherein the first request is used for requesting to acquire an enhanced broadcast service eBCS;

the station receives a first response comprising: authentication information of the eBCS.

2. The method of claim 1, wherein the eBCS is an eBCS that requires registration and does not require association, and wherein the first request is an Access Network Query Protocol (ANQP) request and the first response is an ANQP response.

3. The method of claim 2,

the ANQP request includes: an enhanced broadcast request (ANQP) element structure, and the enhanced broadcast request (ANQP) element structure comprises: an enhanced broadcast service request tuple, the enhanced broadcast service request tuple comprising: requesting authentication information;

wherein the request authentication information is used for indicating whether to request to acquire the authentication information of the eBCS.

4. The method of claim 3, wherein the enhanced broadcast service request tuple comprises: an enhanced broadcast service request control field, and the enhanced broadcast service request control field includes: the request authentication information.

5. The method of claim 3, wherein the enhanced broadcast service request tuple comprises: and broadcasting an action field, wherein a reserved field of the broadcast action field carries the request authentication information.

6. The method of any of claims 2-5 wherein the ANQP response further comprises: responding to the authentication information indication;

wherein the response authentication information indicates authentication information indicating whether the eBCS is included in the ANQP response.

7. The method of claim 6, wherein the ANQP response comprises: an enhanced broadcast service response control field, the enhanced broadcast service response control field comprising: the response authentication information indicates.

8. The method of claim 1, wherein the eBCS is an eBCS that needs to be associated, and accordingly, the first request is an eBCS request and the first response is an eBCS response.

9. The method of claim 8,

the eBCS request includes: an eBCS request element structure, and the eBCS request element structure comprises: an eBCS request information set, wherein the eBCS request information set comprises: requesting authentication information;

10. The method of claim 9, wherein the eBCS request information set comprises: an eBCS request information control field, and the eBCS request information control field includes: the request authentication information.

11. The method of any one of claims 8-10, wherein the eBCS response further comprises: responding to the authentication information indication;

wherein the response authentication information indicates whether authentication information of the eBCS is included in the eBCS response.

12. The method of claim 11, wherein the eBCS response comprises: an eBCS response information set, wherein the eBCS response information set comprises: the response authentication information indicates.

13. The method of claim 12, wherein the eBCS response information set comprises: an eBCS response information control field, the eBCS response information control field comprising: the response authentication information indicates.

14. The method according to any of claims 1-13, wherein the eBCS authentication information comprises: an authentication algorithm field to indicate an authentication algorithm employed for the eBCS.

15. The method of claim 14, wherein the authentication algorithm is any one of: and the method does not perform frame authentication, and forces higher-level source authentication HLSA, public key frame identity authentication PKFA, hash chain frame identity authentication HCFA which does not perform immediate authentication and HCFA which performs immediate authentication.

16. The method of claim 15, wherein if the authentication algorithm is PKFA, the authentication information of the eBCS further comprises: allowed time difference, authentication certificate length, authentication certificate.

17. The method of claim 15, wherein if the authentication algorithm is an HCFA that does not perform immediate authentication, the authentication information of the eBCS further comprises: allowed time difference, eBCS information frame interval, HCFA key change interval, HCFA base key.

18. The method of claim 15, wherein if the authentication algorithm is an HCFA performing immediate authentication, the authentication information of the eBCS further comprises: an allowed time difference, a number of immediate authenticators, an immediate authenticator list;

wherein the immediate authenticator list comprises: the hash distance of the immediate authenticator and the immediate authenticator field.

19. A method of wireless communication, comprising:

the method comprises the steps that a sending end sends an ANQP request to a receiving end, wherein the ANQP request comprises the following steps: requesting a termination time, wherein the request termination time is the time when the sender requests to terminate the eBCS.

20. The method of claim 19, wherein the ANQP request comprises: an enhanced broadcast request (ANQP) element structure, and the enhanced broadcast request (ANQP) element structure comprises: an enhanced broadcast service request tuple, the enhanced broadcast service request tuple comprising: the request termination time.

21. The method of claim 19 or 20, wherein the ANQP request comprises: a broadcast action field, and a reserved field of the broadcast action field carries a request termination time indication;

wherein the request termination time indication indicates whether the ANQP request includes the request termination time.

22. The method of claim 20, wherein the enhanced broadcast service request tuple comprises: an enhanced broadcast service request control field, and the enhanced broadcast service request control field includes: a request expiration time indication;

23. The method of any of claims 19-22 wherein the eBCS is an eBCS that requires registration and no association, and wherein the ANQP request is used to request extension of the eBCS.

24. A method of wireless communication, comprising:

the method comprises the steps that an access point receives a first request, wherein the first request is used for requesting to acquire eBCS;

the access point sends a first response to the station, the first response comprising: authentication information of the eBCS.

25. The method of claim 24 wherein the eBCS is an eBCS that requires registration and no association, and wherein the first request is an ANQP request and the first response is an ANQP response.

26. The method of claim 25,

27. The method of claim 26, wherein the enhanced broadcast service request tuple comprises: an enhanced broadcast service request control field, and the enhanced broadcast service request control field includes: the request authentication information.

28. The method of claim 26, wherein the enhanced broadcast service request tuple comprises: and broadcasting an action field, wherein a reserved field of the broadcast action field carries the request authentication information.

29. The method of any of claims 25-28 wherein the ANQP response further comprises: responding to the authentication information indication;

30. The method of claim 29 wherein the ANQP response comprises: an enhanced broadcast service response control field, the enhanced broadcast service response control field comprising: the response authentication information indicates.

31. The method of claim 24 wherein the eBCS is an eBCS that needs to be associated, and accordingly, the first request is an eBCS request and the first response is an eBCS response.

32. The method of claim 31,

33. The method of claim 32 wherein the eBCS request information set comprises: an eBCS request information control field, and the eBCS request information control field includes: the request authentication information.

34. The method of any one of claims 31-33, wherein the eBCS response further comprises: responding to the authentication information indication;

35. The method of claim 34, wherein the eBCS response comprises: an eBCS response information set, wherein the eBCS response information set comprises: the response authentication information indicates.

36. The method of claim 35 wherein the eBCS response information set comprises: an eBCS response information control field, the eBCS response information control field comprising: the response authentication information indicates.

37. The method according to any of claims 24-36, wherein the eBCS authentication information comprises: an authentication algorithm field to indicate an authentication algorithm employed for the eBCS.

38. The method of claim 37, wherein the authentication algorithm is any one of: HLSA, PKFA, HCFA that does not perform immediate authentication, HCFA that performs immediate authentication.

39. The method of claim 38, wherein if the authentication algorithm is PKFA, the authentication information of the eBCS further comprises: allowed time difference, authentication certificate length, authentication certificate.

40. The method of claim 38, wherein if the authentication algorithm is an HCFA that does not perform immediate authentication, the authentication information of the eBCS further comprises: allowed time difference, eBCS information frame interval, HCFA key change interval, HCFA base key.

41. The method of claim 38, wherein if the authentication algorithm is an HCFA performing immediate authentication, the authentication information of the eBCS further comprises: an allowed time difference, a number of immediate authenticators, an immediate authenticator list;

42. A method of wireless communication, comprising:

the receiving end receives an ANQP request sent by a sending end, wherein the ANQP request comprises the following steps: requesting a termination time, wherein the request termination time is the time when the sender requests to terminate the eBCS.

43. The method of claim 42 wherein the ANQP request comprises: an enhanced broadcast request (ANQP) element structure, and the enhanced broadcast request (ANQP) element structure comprises: an enhanced broadcast service request tuple, the enhanced broadcast service request tuple comprising: the request termination time.

44. The method of claim 42 or 43 wherein the ANQP request comprises: a broadcast action field, and a reserved field of the broadcast action field carries a request termination time indication;

45. The method of claim 43, wherein the enhanced broadcast service request tuple comprises: an enhanced broadcast service request control field, and the enhanced broadcast service request control field includes: a request expiration time indication;

46. The method of any of claims 42-45 wherein the eBCS is an eBCS that requires registration and no association, and wherein the ANQP request is used to request extension of the eBCS.

47. A station, comprising: a communication unit to:

sending a first request to an access point, wherein the first request is used for requesting to acquire eBCS;

receiving a first response, the first response comprising: authentication information of the eBCS.

48. A transmitting end, comprising:

a communication unit, configured to send an ANQP request to a receiving end, where the ANQP request includes: requesting a termination time, wherein the request termination time is the time when the sender requests to terminate the eBCS.

49. An access point, comprising: a communication unit to:

receiving a first request, wherein the first request is used for requesting to acquire eBCS;

sending a first response to a station, the first response comprising: authentication information of the eBCS.

50. A receiving end, comprising:

a communication unit, configured to receive an ANQP request sent by a sending end, where the ANQP request includes: requesting a termination time, wherein the request termination time is the time when the sender requests to terminate the eBCS.

51. A station, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 18.

52. A transmitting end, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 19 to 23.

53. An access point, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 24 to 41.

54. A receiving end, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 42 to 46.

55. A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 46.

56. A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 46.

57. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 46.

58. A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1 to 46.