Method of transmitting and receiving information and communication device

Abstract

Embodiments of the present application provide a method for sending and receiving information, which can be applied to a WLAN system supporting IEEE 802.11 series protocols, such as 802.11be / Wi-Fi 7, Wi-Fi 8, EHT or the next generation protocol, etc. By modifying the value of the negotiation type field of the TWT element, or by expanding the broadcast TWT parameter set and designing some fields or their values in the expanded broadcast TWT parameter set, or by specifying the number and position of the broadcast TWT parameter set containing the limited TWT service information in a TWT element, or by introducing a new element type and an element identifier for identifying the element type, the limited TWT service information field carried in the broadcast management frame is supported, and the traditional station will not misread the information in the TWT element due to the carrying of the limited TWT service information field in the broadcast management frame.

Description

Technical Field

[0001] This application relates to wireless local area networks, and more specifically, to a method for sending and receiving information, as well as a communication device. Background Technology

[0002] Wireless Local Area Networks (WLANs) have evolved through standards such as IEEE 802.11a / b / g / n / ac / ax, and are currently under discussion in the industry as 802.11be, with its standard versions continuously developing and evolving. Currently, an increasing number of wireless network applications and services are placing stringent requirements on latency characteristics, such as online gaming, virtual reality, and industrial environments. Therefore, the 802.11be standard prioritizes ensuring latency and reducing latency jitter as key technical objectives, proposing to introduce restricted target wakeup time (r-TWT) technology to improve latency guarantee performance. The r-TWT parameter information is carried in the TWT element field of the broadcast management frame. For a broadcast TWT, the TWT parameter information contains multiple broadcast TWT parameter sets. The broadcast TWT suggestion subfield in the request type field of each broadcast TWT parameter set indicates the TWT type specified by that broadcast TWT parameter set. After the 802.11be standard introduced r-TWT, it extended the values ​​of the broadcast TWT suggestion subfield so that the extended value of the broadcast TWT suggestion subfield could indicate that the TWT type specified by the extended value was r-TWT.

[0003] However, since r-TWT was introduced in the 802.11be standard, legacy stations (legacy STAs) cannot understand it. Therefore, if a broadcast TWT parameter set within a TWT element contains r-TWT service information, the length of that broadcast TWT parameter set will change accordingly. However, legacy STAs will always assume the broadcast TWT parameter set is 9 bytes long, leading to misinterpretations of the information within that TWT element and unpredictable consequences. Summary of the Invention

[0004] This application provides a method for sending and receiving information, which can support carrying restricted TWT service information (i.e., r-TWT service information) in broadcast management frames without causing legacy STAs to misread the information in the TWT element carrying the restricted TWT service information.

[0005] The method for sending information provided in the first or second aspect below can be applied to an access point (i.e., AP) of a WLAN. For example, the method can be executed by the AP, or by a chip or chip system deployed on the AP, without limitation. The following explanation uses the execution of the method at an access point as an example.

[0006] Firstly, a method for sending information is provided, the method comprising:

[0007] The access point generates a management frame, and the broadcast management frame contains a first TWT element. The first TWT element contains a first broadcast TWT parameter set. The first broadcast TWT parameter set contains a restricted TWT service information field.

[0008] The first TWT element conforms to one of the following:

[0009] The first TWT element contains a negotiation type field, and the negotiation type field has a value of 3;

[0010] or,

[0011] The first TWT element contains a first broadcast TWT parameter set comprising two 9-byte fields. The first 9-byte field contains a request type field and a broadcast TWT information field. The request type field contains a broadcast TWT suggestion field, the value of which belongs to the set {4,5,6,7}. The broadcast TWT information field contains a restriction TWT service information presence indication field, the value of which belongs to the set {4,5,6,7}. The second 9-byte field contains a first field and a restriction TWT service information field. The first field is the first two bytes of the second 9-byte field. The restriction TWT service information field is located after the first field. The first field contains a second field. The position of the second field in the first field is the same as the position of the broadcast TWT suggestion field in the request type field of the first 9-byte field. The value of the second field belongs to the set {4,5,6,7}.

[0012] or,

[0013] The first broadcast TWT parameter set contained in the first TWT element is the last broadcast TWT parameter set in the broadcast TWT parameter set contained in the first TWT element. The first broadcast TWT parameter set contains a request type field, which contains a broadcast TWT suggestion field. The value of the broadcast TWT suggestion field belongs to the set {4,5,6,7}.

[0014] The access point sends a broadcast management frame.

[0015] In this technical solution, the carrying of restricted TWT service information fields in broadcast management frames is supported by modifying the value of the negotiation type field of the TWT element, expanding the broadcast TWT parameter set and designing some fields or their values ​​in the expanded broadcast TWT parameter set, or specifying the number and position of broadcast TWT parameter sets containing restricted TWT service information in a TWT element. First-type stations (i.e., traditional stations) do not parse the TWT element or the broadcast TWT parameter set containing the restricted TWT service information field based on the information carried in the TWT element. This prevents traditional stations from misinterpreting the information in the TWT element due to the restricted TWT service information field being carried in the broadcast frame.

[0016] Secondly, a method for sending information is provided, the method comprising:

[0017] The access point generates a broadcast management frame;

[0018] The broadcast management frame includes a first TWT element, which includes an element identifier field and a restricted TWT parameter information field. The element identifier field is used to identify the first TWT element as a TWT element that includes a restricted TWT service information field, and the restricted TWT parameter information field includes the restricted TWT service information field.

[0019] The access point sends a broadcast management frame.

[0020] This technical solution introduces a new element type, namely the restricted TWT element (i.e., the r-TWT element), and a new element identifier to identify the restricted TWT element, thereby enabling the carrying of the restricted TWT service information field in broadcast management frames. Traditional sites do not parse the r-TWT element based on its element identifier, thus avoiding misreading of information.

[0021] The method for receiving information provided in any of the third to fifth aspects below can be applied to a WLAN station (i.e., STA). For example, the method can be executed by the STA, or by a chip or chip system deployed on the STA, without limitation. The following description uses the execution of the method by the STA as an example.

[0022] Optionally, the STA that performs this method is a conventional STA, that is, the first type of STA described in this application. The specification contains a detailed description of the first type of STA, which will not be repeated here.

[0023] Thirdly, a method for receiving information is provided, the method comprising:

[0024] The first type of station receives broadcast management frames from the access point;

[0025] The broadcast management frame contains a first TWT element, the first TWT element contains a first broadcast TWT parameter set, and the first broadcast TWT parameter set contains a restricted TWT service information field.

[0026] In addition, the first TWT element also contains a negotiation type field, which takes the value 3;

[0027] The first type of station processes broadcast management frames.

[0028] In conjunction with the third aspect, in some implementations of the third aspect, the first type of site does not parse the first TWT element when the value of the negotiation type field of the first TWT element is 3.

[0029] Fourthly, a method for receiving information is provided, the method comprising:

[0030] The first type of station receives broadcast management frames from the access point.

[0031] The broadcast management frame contains a first TWT element, the first TWT element contains a first broadcast TWT parameter set, and the first broadcast TWT parameter set contains a restricted TWT service information field.

[0032] Furthermore, the first broadcast TWT parameter set includes two 9-byte sets. The first 9-byte set contains a request type field and a broadcast TWT information field. The request type field contains a broadcast TWT suggestion field, the value of which belongs to the set {4,5,6,7}. The broadcast TWT information field contains a restriction TWT service information presence indication field, the value of which is 1. The second 9-byte set contains a first field and the restriction TWT service information field. The first field is the first two bytes of the second 9-byte set. The restriction TWT service information field is located after the first field. The first field contains a second field. The position of the second field in the first field is the same as the position of the broadcast TWT suggestion field in the request type field of the first 9-byte set. The value of the second field belongs to the set {4,5,6,7}.

[0033] The first type of station processes broadcast management frames.

[0034] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second 9 bytes contain a 3-byte restricted TWT service information field and a 3-bit broadcast TWT suggestion field, the 3 bits of which are the 8th to 10th bits of the request type field;

[0035] The second field contains 3 bits, which are the 8th to 10th bits in the first field.

[0036] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the last four bytes of the second nine bytes are reserved bytes.

[0037] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the first type of station processes broadcast management frames, including:

[0038] For the first type of station, if the value of the broadcast TWT suggestion field in the first broadcast TWT parameter set contained in the first TWT element belongs to the set {4,5,6,7}, the first 9 bytes are skipped.

[0039] For the first type of site, if the value of the second field in the second 9 bytes belongs to the set {4,5,6,7}, the second 9 bytes are skipped.

[0040] Fifthly, a method for receiving information is provided, the method comprising:

[0041] The first type of station receives broadcast management frames from the access point.

[0042] The broadcast management frame contains a first TWT element, which contains a first broadcast TWT parameter set. The first broadcast TWT parameter set is the last broadcast TWT parameter set in the first TWT element. The first broadcast TWT parameter set contains a request type field, which contains a broadcast TWT suggestion field. The value of the broadcast TWT suggestion field belongs to the set {4,5,6,7}.

[0043] The first type of station processes broadcast management frames.

[0044] In conjunction with the fifth aspect, in certain implementations of the fifth aspect, the first type of station processes broadcast management frames, including:

[0045] For the first type of site, if the value of the broadcast TWT suggestion field in the first broadcast TWT parameter set belongs to the set {4,5,6,7}, the first broadcast TWT parameter set is skipped. If, based on the length of the first TWT element, it is determined that the number of bytes or bits following the first broadcast TWT parameter set is insufficient to constitute a broadcast TWT parameter set, the parsing of the first TWT element ends.

[0046] Sixthly, a method for receiving information is provided, the method comprising:

[0047] The first type of station receives broadcast management frames from the access point.

[0048] The broadcast management frame includes a first TWT element, which includes an element identifier field and a restricted TWT parameter information field. The element identifier field is used to indicate that the first TWT element is a TWT element that includes a restricted TWT service information field, and the restricted TWT parameter information field includes the restricted TWT service information field.

[0049] The first type of station processes broadcast management frames.

[0050] In conjunction with the sixth aspect, in certain implementations of the sixth aspect, the first type of station processes broadcast management frames, including:

[0051] For the first type of site, the first TWT element is not parsed based on its element identifier.

[0052] The technical effects of the methods in aspects three through six above can be found in the descriptions of the technical effects of the corresponding technical solutions in aspects one or two, and will not be repeated here.

[0053] In a seventh aspect, a communication device is provided, the communication device having the function of implementing the methods of the first aspect or the second aspect, or any possible implementation of these aspects. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-described functions.

[0054] Eighthly, a communication device is provided, the communication device having the function of implementing any one of the third to sixth aspects, or any possible implementation of these aspects. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above-described functions.

[0055] A ninth aspect provides a communication device including a processor and a memory. Optionally, it may also include a transceiver. The memory stores a computer program, the processor invokes and runs the computer program stored in the memory, and controls the transceiver to send and receive signals, causing the communication device to perform methods as described in the first or second aspect, or any possible implementation thereof.

[0056] A tenth aspect provides a communication device including a processor and a memory. Optionally, it may also include a transceiver. The memory stores a computer program, the processor invokes and runs the computer program stored in the memory, and controls the transceiver to send and receive signals, causing the communication device to perform methods as described in any of the third to sixth aspects, or in any possible implementation thereof.

[0057] Eleventhly, a communication device is provided, comprising a processor and a communication interface, the communication interface being configured to receive data and / or information and transmit the received data and / or information to the processor, the processor processing the data and / or information, and the communication interface being further configured to output the processed data and / or information such that a method as described in the first or second aspect, or any possible implementation thereof, is executed.

[0058] In a twelfth aspect, a communication apparatus is provided, comprising a processor and a communication interface, the communication interface being configured to receive data and / or information and transmit the received data and / or information to the processor, the processor processing the data and / or information, and the communication interface being further configured to output the processed data and / or information such that a method as described in any of the third to sixth aspects, or any possible implementation thereof, is executed.

[0059] In a thirteenth aspect, a computer-readable storage medium is provided, wherein computer instructions are stored therein, which, when executed on a computer, cause a method, such as in the first or second aspect, or any possible implementation thereof, to be performed.

[0060] In a fourteenth aspect, a computer-readable storage medium is provided, wherein computer instructions are stored therein, which, when executed on a computer, cause a method, such as any one of the third to sixth aspects, or any possible implementation thereof, to be performed.

[0061] In a fifteenth aspect, a computer program product is provided, the computer program product comprising computer program code that, when the computer program code is run on a computer, causes a method, such as in the first aspect or the second aspect, or any possible implementation thereof, to be executed.

[0062] In a sixteenth aspect, a computer program product is provided, the computer program product comprising computer program code that, when run on a computer, causes a method, such as any one of the third to sixth aspects, or any possible implementation thereof, to be executed.

[0063] In a seventeenth aspect, a chip is provided, the chip including a processor, a memory for storing a computer program disposed independently of the chip, the processor being configured to execute the computer program stored in the memory, causing a device mounted on the chip to perform a method as described in the first aspect or the second aspect, or any possible implementation thereof.

[0064] Eighteenth aspect, a chip is provided, the chip including a processor, a memory for storing a computer program disposed independently of the chip, the processor being configured to execute the computer program stored in the memory, causing a device mounted on the chip to perform a method as described in any of the third to sixth aspects, or any possible implementation thereof.

[0065] Optionally, the processor in the sixteenth or seventeenth aspect may be a processing circuit or a logic circuit.

[0066] Furthermore, the chip may also include a communication interface. The communication interface may be an input / output interface or an interface circuit, etc. Furthermore, the chip may also include the memory.

[0067] Optionally, the processor can be one or more, and the memory can be one or more.

[0068] Nineteenth aspect, a communication system is provided, including the communication apparatus as described in the sixth and / or seventh aspects. Attached Figure Description

[0069] Figure 1 This is a schematic diagram of the r-TWT mechanism.

[0070] Figure 2 This is a schematic diagram of the frame structure of a TWT element.

[0071] Figure 3 An example of a legacy STA misreading information in a broadcast frame.

[0072] Figure 4 This is a schematic diagram of a communication system applicable to embodiments of this application.

[0073] Figure 5 A schematic flowchart illustrating the method for sending information provided in this application.

[0074] Figure 6 The frame structure for the extended broadcast TWT parameter set provided in this application.

[0075] Figure 7 This is a schematic diagram of the frame structure of the TWT element provided in this application.

[0076] Figure 8 This is a schematic diagram of the frame structure of the r-TWT element provided in this application.

[0077] Figure 9 A schematic block diagram of the communication device provided in this application.

[0078] Figure 10A schematic structural diagram of the communication device provided in this application. Detailed Implementation

[0079] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0080] To facilitate understanding of the technical solution of this application, a brief introduction to the relevant technologies involved in this application will be given first.

[0081] Under 802.11be, many real-time applications (RTAs) exist at non-access point (non-AP) extremely high throughput (EHT) STAs. These applications have very strict latency requirements. Therefore, the restricted target wakeup time (r-TWT) mechanism was proposed. r-TWT is a new mechanism derived from the existing broadcast TWT in 802.11ax to ensure low-latency services.

[0082] See Figure 1 , Figure 1 This is a schematic diagram of the r-TWT mechanism. (Example) Figure 1 In the r-TWT mechanism, the AP broadcasts one or more r-TWT service periods (SPs) via beacon frames or probe response frames. When an EHT STA within the basic service set (BSS) receives information from any r-TWT SP broadcast by the AP, if the EHT STA's dot11RestrictedTWTOptionImplemented setting is true, then the EHT STA must terminate its transmission opportunity (TXOP) before the start time of the r-TWT SP. Furthermore, the AP can set a 1-millisecond silence interval in the beacon frame or probe response frame corresponding to the start time of the r-TWT SP. EHT STAs belonging to the same r-TWT SP group (grouped by broadcast TWT ID) are required to ignore this silence interval and compete for the channel after the r-TWT SP begins. Other EHT STAs need to remain silent according to the silence interval, which reduces the number of EHT STAs competing for the channel within the BSS and increases the probability of EHT STAs with low-latency services obtaining the channel.

[0083] The r-TWT parameter information is indicated in the TWT element field.

[0084] See Figure 2 , Figure 2 This is a schematic diagram of the frame structure of a TWT element. Figure 2 For a broadcast TWT element, it includes an element identifier field, a length field, a control field, and a TWT parameter information field. The control field includes an NDPpaging indicator field, a responder PM mode field, a negotiation type field, a TWT information frame disabled field, a wakeupduration unit field, a link identifier bitmap present field, and a reservation field.

[0085] The TWT parameter information field contains one or more broadcast TWT parameter sets. Each broadcast TWT parameter set includes a request type field, a target wakeup time (TWT) field, a nominal minimum TWT wakeup duration field, a TWT wakeup interval mantissa field, and a broadcast TWT info field. The request type field includes a broadcast TWT recommendation field, which indicates the TWT type specified by the broadcast TWT parameter set. When the broadcast TWT recommendation field has a value of 4, it indicates that the broadcast TWT parameter set corresponds to an r-TWT. Alternatively, when the broadcast TWT recommendation field has a value of 4, it indicates that the broadcast TWT parameter set specifies an r-TWT type. This request type was introduced in IEEE 802.11be and is therefore incomprehensible to legacy STAs. In addition, the broadcast TWT information field may include a restricted TWT traffic information present field, a broadcast TWT ID field, and a broadcast TWT persistence field. A 2-bit space is reserved between the restricted TWT traffic information present field and the broadcast TWT ID field. The broadcast TWT ID field identifies the TWT group.

[0086] If a broadcast TWT parameter set corresponds to an r-TWT, then the broadcast TWT information field includes a one-bit r-TWT service information presence indication field. Optionally, the name of the r-TWT service information presence indication field is not limited in this application and can be other names. The function of this field is to indicate whether the broadcast TWT parameter set contains the r-TWT service information field. For example, this field can have two values: one value indicates that the broadcast TWT parameter set contains the r-TWT service information field, and the other value indicates that the broadcast TWT parameter set does not contain the r-TWT service information field. For example, the r-TWT service information presence indication field can contain 1 bit. When the 1 bit is 1, it indicates that the TWT element field contains the r-TWT service information field; when the 1 bit is 0, it indicates that the TWT element field does not contain the r-TWT service information field.

[0087] Alternatively, this application does not limit the name of the r-TWT service information field; other names may also be used. Figure 2 The example shown is merely an illustration.

[0088] The descriptions of the r-TWT service information presence indication field and the r-TWT service information field given here are also applicable to the embodiments described below, and will not be repeated here.

[0089] from Figure 2 It can be seen that if a broadcast TWT information field does not contain an r-TWT service information field, then the length of this broadcast TWT information field is 9 bytes; if a broadcast TWT information field contains an r-TWT service information field, then the length of this broadcast TWT information field is 12 bytes. As mentioned above, since r-TWT and the r-TWT service information field were introduced in 802.11be, legacy STAs always consider the broadcast TWT information field to be 9 bytes. Therefore, when a broadcast frame carries an r-TWT service information field, it may cause legacy STAs to misread it, leading to unpredictable consequences.

[0090] See Figure 3 , Figure 3 An example of a legacy STA misreading information in a broadcast frame.

[0091] like Figure 3 A TWT element in a beacon frame sent by the AP contains N broadcast TWT parameter sets. Assume the i-th broadcast parameter set is the first broadcast TWT parameter set corresponding to r-TWT, meaning the broadcast proposal field in the request type field of the i-th broadcast TWT parameter set has a value of 4. In other words, the 1st to (i-1th)-th broadcast TWT parameter sets do not correspond to r-TWT, meaning the broadcast TWT proposal field in the request type field has a value of 0, 1, 2, or 3.

[0092] The following is based on Figure 3Let's analyze the reason for the legacy STA's misinterpretation. As mentioned earlier, since the i-th broadcast TWT parameter set is the first broadcast TWT parameter set corresponding to r-TWT, the first i-1 broadcast TWT parameter sets can be correctly parsed by the legacy STA. However, when the legacy STA parses the i-th broadcast TWT parameter set, it finds that the broadcast TWT suggestion field in its request type field has a value of 4. The legacy STA cannot understand this request type, so it intends to skip the i-th broadcast TWT parameter set and parse the (i+1)-th broadcast TWT parameter set. However, because the legacy STA believes that the length of the i-th broadcast TWT parameter set is 9 bytes, while in reality, the i-th broadcast TWT parameter set is 12 bytes long due to the inclusion of the r-TWT service information field, the starting position of the (i+1)-th broadcast TWT parameter set as perceived by the legacy STA is 3 bits earlier than its actual starting position, causing a bit misalignment. This bit scrambling problem will cause all broadcast TWT parameter sets from the i-th broadcast TWT parameter set onwards to be misread by the legacy STA, leading to unpredictable consequences.

[0093] Based on this, the embodiments of this application provide a method for transmitting information in a wireless local area network (WLAN) system, aiming to prevent legacy STAs from misreading the broadcast frame when the broadcast frame carries the r-TWT service information field. This method can be implemented by a communication device in the WLAN system or by a chip or processor within that device.

[0094] The technical solution provided in this application can be applied to WLAN scenarios, for example, to IEEE 802.11 system standards, such as 802.11a / b / g, 802.11n, 802.11ac, 802.11ax, or their next generation, such as 802.11be or even later.

[0095] Although the embodiments of this application are primarily illustrated using the deployment of WLAN networks, especially those employing the IEEE 802.11 system standard, those skilled in the art will readily understand that the various aspects of this application can be extended to other networks employing various standards or protocols, such as high-performance radio local area networks (HIPERLANs), wide area networks (WANs), personal area networks (PANs), or other networks now known or to be developed in the future. HIPERLAN is a wireless standard similar to the IEEE 802.11 standard, primarily used in Europe. Therefore, regardless of the coverage area and wireless access protocol used, the various aspects provided in this application can be applied to any suitable wireless network.

[0096] The embodiments of this application can also be applied to wireless local area network systems such as Internet of Things (IoT) networks or vehicle-to-everything (V2X) networks. Of course, the embodiments of this application can also be applied to other possible communication systems, such as Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th generation (5G) systems, and future 6th generation (6G) systems.

[0097] The communication systems described above that are applicable to this application are merely illustrative examples, and the communication systems applicable to this application are not limited to these. They will be uniformly described here and will not be repeated below.

[0098] See Figure 4 , Figure 4 This is a schematic diagram of a communication system applicable to embodiments of this application. For example... Figure 4The method for sending and receiving information provided in this application is applicable to data communication between an AP and one or more STAs (e.g., data communication between AP1 and STA1, STA2). Optionally, the STAs mentioned herein include at least a legacy STA, such as STA1. Additionally, EHT STAs, such as STA2, may also be included.

[0099] Access points are points through which terminal devices (e.g., mobile phones) access wired (or wireless) networks. They are primarily deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters. They can also be deployed outdoors. An access point acts as a bridge between wired and wireless networks, connecting various wireless network clients and then connecting the wireless network to the Ethernet. Specifically, access points can be terminal devices (such as mobile phones) or network devices (such as routers) with Wi-Fi chips. Access points can be devices supporting the 802.11be standard. They can also be devices supporting various 802.11 family of wireless local area networks (WLANs), including 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, and 802.11be next-generation. The access point in this application can be a high-efficiency (HE) AP or an extremely high-throughput (EHT) AP, or it can be an access point that is compatible with a future generation of Wi-Fi standards.

[0100] A site can be a wireless communication chip, wireless sensor, or wireless communication terminal, and can also be referred to as a user. For example, a site can be a mobile phone supporting Wi-Fi communication, a tablet computer supporting Wi-Fi communication, a set-top box supporting Wi-Fi communication, a smart TV supporting Wi-Fi communication, a smart wearable device supporting Wi-Fi communication, an in-vehicle communication device supporting Wi-Fi communication, and a computer supporting Wi-Fi communication, etc. Optionally, the site can support the 802.11be standard. The site can also support various wireless local area networks (WLAN) standards of the 802.11 family, including 802.11a / b / g / n, 802.11ac, 802.11ax, 802.11be, and 802.11be next-generation.

[0101] The technical solution of this application is described below.

[0102] See Figure 5 , Figure 5 A schematic flowchart illustrating the method for sending information provided in this application.

[0103] 510. AP generates broadcast management frames.

[0104] The broadcast management frame contains a first TWT element, the first TWT element contains a first broadcast TWT parameter set, and the first broadcast TWT parameter set contains a restricted TWT service information field.

[0105] Optionally, the first TWT element may contain one or more first broadcast TWT parameter sets. That is, the first TWT element refers to a TWT element that contains a restricted TWT service information field, and the first TWT element containing a broadcast TWT parameter set with a restricted TWT service information field (i.e., the first broadcast TWT parameter set) can be one or more, without limitation. Optionally, the broadcast management frame contains one or more first TWT elements. In addition, the broadcast management frame may also contain one or more other TWT elements. Here, other TWT elements may refer to TWT elements that do not contain an r-TWT service information field, without limitation.

[0106] The frame structure of the first TWT element or the first broadcast TWT parameter set provided in this application will be described in detail below, as in Schemes 1 to 4 below.

[0107] 520. AP sends broadcast management frame.

[0108] The first type of STA receives broadcast management frames from the AP.

[0109] Optionally, the second type of STA receives broadcast management frames from the AP.

[0110] It should be understood that the 802.11n standard is also called high throughput (HT), the 802.11ac standard is called very high throughput (VHT), the 802.11ax standard is called high efficient (HE), and the 802.11be standard is called extremely high throughput (EHT). Standards prior to HT, such as 802.11a / b / g, are collectively referred to as non-high throughput (Non-HT).

[0111] For example, the first type of STA refers to a legacy STA, which may not support the 802.11be standard but supports 802.11 standards prior to 802.11be, such as STAs supporting 802.11a / b / g / n / ac / ax. Due to the introduction of the r-TWT mechanism in 802.11be, under this mechanism, a TWT element may contain a restricted TWT service information field within its broadcast TWT parameter set. The value of the broadcast TWT suggestion field in the request type field of this broadcast TWT parameter set indicates that the TWT type specified by the broadcast TWT parameter set is r-TWT, a request type that legacy STAs cannot understand. In other words, the first type of STA may be a STA that does not understand or cannot recognize the r-TWT type.

[0112] Furthermore, the first type of site can also refer to a site that, functionally, can ignore the broadcast TWT parameter set containing restricted TWT service information, or a site that can ignore the TWT element containing restricted TWT service information. Here, "can ignore" also means that the site does not need to obtain the restricted TWT service information, and therefore can choose not to read or parse the broadcast TWT parameter set or TWT element containing the restricted TWT service information.

[0113] The second type of STA can be an EHT STA, or a STA that supports the 802.11be standard or a later version of the 802.11 standard. If the TWT element contains a request type field in the broadcast TWT parameter set that indicates that the TWT type specified by the broadcast TWT parameter set is r-TWT, the second type of STA can understand that request type.

[0114] 530. Type 1 STA processes broadcast management frames.

[0115] Specifically, based on the frame structure of the broadcast management frame provided in this application, the first type of STA may not parse the first TWT element in the broadcast management frame, or may not parse the first TWT element containing the first broadcast TWT parameter set.

[0116] Alternatively, the first type of STA does not parse the first TWT element, that is, the first type of STA parses other TWT elements in the broadcast management frame besides the first TWT element.

[0117] The second type of STA processes broadcast management frames, including parsing the first broadcast TWT parameter set.

[0118] The first type of STA does not parse the first broadcast TWT parameter set in the first TWT element. That is, when the first type of STA parses one or more TWT elements contained in the broadcast management frame, for the first TWT element, the first type of STA parses other broadcast TWT parameter sets besides the first broadcast TWT parameter set.

[0119] In the technical solution of this application, when the first TWT element contains a restricted TWT service information field, by changing the values ​​of some fields contained in the first TWT element or changing the frame structure of some fields contained in the first TWT element, the first type of STA can skip the first TWT element (or, in other words, not parse the first TWT element), or skip the first broadcast TWT parameter set containing the restricted TWT service information field in the first TWT element (or, in other words, not parse the first broadcast TWT parameter set). This can avoid misreading of the information in the TWT element (i.e., the first TWT element) containing restricted TWT service information.

[0120] Specifically, this application provides the following solutions 1 to 4, which can avoid misinterpretation of the information contained in the first TWT element by the first type of site.

[0121] Option 1

[0122] Modify the negotiation type field of the TWT element.

[0123] In this application, if a TWT element contains at least one broadcast TWT parameter set that includes an r-TWT service information field, then the value of the negotiation type field in the TWT element is set to 3.

[0124] Specifically, in existing protocols, the TWT element carrying the broadcast TWT parameter set in broadcast frames such as beacon frames includes a "negotiation type field," and the value of this negotiation type field is fixed at 2. In this embodiment, it is allowed to set the value of the negotiation type field in the TWT element carrying the broadcast TWT parameter set in broadcast frames such as beacon frames to 3. That is, if one or more broadcast TWT parameter sets contained in a certain TWT element carried in a broadcast frame contain (or carry) the r-TWT service information field, then the AP sets the negotiation type field of that TWT element to 3.

[0125] That is, in the application, the value of the protocol type field of the first TWT element is set to 3.

[0126] It is important to understand that, according to existing protocols, TWT elements with a negotiation type field value of 2 can only be carried in broadcast frames (e.g., beacon frames or probe response frames). In other words, when a TWT element is carried in a broadcast frame, the negotiation type field of that TWT element is set to 2. That is, when the negotiation type field of a TWT element is set to 2, it indicates that the TWT element does not contain the r-TWT service information field. In this application, by allowing the negotiation type field of a TWT element to be set to 3 in broadcast management frames, it is indicated that the TWT element is a TWT element carrying the r-TWT service information field.

[0127] For legacy STAs, the negotiation type field of a TWT element in a broadcast frame can only be 2. If the negotiation type field of a TWT element is 3, the legacy STA will not parse that TWT element. Therefore, during the parsing of a broadcast management frame, if the negotiation type field of the currently processed TWT element is 3, the legacy STA will skip this TWT element and proceed to the next TWT element. Thus, by setting the negotiation type field of the first TWT element to 3, the legacy STA can skip the first TWT element, thereby avoiding misreading.

[0128] The values ​​and descriptions of the negotiated type field of the modified TWT element are shown in Table 1.

[0129] Table 1

[0130]

[0131]

[0132] As shown in Table 1, by modifying the description of the negotiation type field (as shown in the bold italicized part in Table 1), it is possible to support the AP that schedules TWTs to send broadcast management frames that carry TWT elements with a negotiation type field value of 3.

[0133] Option 2

[0134] By expanding the broadcast TWT parameter set, misreading by legacy STAs can be avoided.

[0135] Specifically, if a broadcast TWT parameter set corresponds to an r-TWT, and the value of the restricted TWT traffic info present field (r-TWT traffic info present) in the broadcast TWT information field is 1, it indicates that the broadcast TWT parameter set contains an r-TWT traffic info field. This broadcast TWT parameter set is the first broadcast TWT parameter set in the embodiments of this application. The first broadcast TWT parameter set will adopt the two 9-byte frame structures proposed in this application, as detailed in [link to relevant documentation]. Figure 6 (a)~(c).

[0136] See Figure 6 , Figure 6 A schematic diagram of the frame structure of the extended broadcast TWT parameter set provided in this application.

[0137] like Figure 6 (a) The first broadcast TWT parameter set contains two 9-byte bytes.

[0138] The first 9-byte of the two sets of two 9-byte segments contains a request type field and a broadcast TWT information field. The request type field contains a broadcast TWT suggestion field, the value of which is set to a value from the set {4,5,6,7}. The broadcast TWT information field contains a restriction TWT service information presence indication field, the value of which is set to 1.

[0139] The second 9-byte segment of the two 9-byte segments contains a first field and a restriction TWT service information field. The first field consists of the first two bytes of the second 9-byte segment. The restriction TWT service information field follows the first field. The first field contains a second field, and the position of the second field within the first field is the same as the position of the broadcast TWT suggestion field within the request type field of the first 9-byte segment. The value of the second field is set to a number from the set {4,5,6,7}.

[0140] The first broadcast TWT parameter set uses two 9-byte frame structures. When the legacy STA parses the first 9 bytes, if the broadcast TWT suggestion field in the request type field is a value from the set {4, 5, 6, 7}, the legacy STA does not understand the request type and will skip the first 9 bytes. It should be noted that, assuming the request type field of the i-th broadcast TWT parameter set in a TWT element contains a broadcast TWT suggestion field value from {4, 5, 6, 7}, indicating that the TWT type specified by the i-th broadcast TWT parameter set is r-TWT, and the legacy STA does not understand r-TWT, it intends to skip the i-th broadcast TWT parameter set. Simultaneously, the legacy STA considers each broadcast TWT parameter set to be the existing 9 bytes; therefore, the legacy STA will skip 9 bytes. At this point, the legacy STA considers it to begin parsing the (i+1)-th broadcast TWT parameter set.

[0141] Therefore, in this application, if the value of the broadcast TWT suggestion field contained in the request type field of the first broadcast TWT parameter set is one of the values ​​in {4,5,6,7}, the legacy STA will skip the first 9 bytes of the first broadcast TWT parameter set.

[0142] Meanwhile, when the legacy STA parses the second 9 bytes of the first broadcast TWT parameter set, it sees the second field as a broadcast TWT parameter set whose position in the first field is the same as the position of the broadcast TWT suggestion field in the first 9 bytes in the request type field of the first 9 bytes, and the value of the second field is also set to a value in {4,5,6,7}. Therefore, the legacy STA treats the second 9 bytes as a broadcast TWT parameter set whose specified TWT type cannot be understood, and thus continues to skip the second 9 bytes.

[0143] Thus, even if the second 9 bytes of the first broadcast TWT parameter set carry a restriction TWT service information field, it will not cause bit errors when the legacy STA parses the first broadcast TWT parameter set, thus preventing subsequent bits in the first TWT element from becoming corrupted. The legacy STA will skip this first broadcast TWT parameter set, which contains two 9-byte blocks.

[0144] Optionally, the second 9 bytes can be further designed, such as... Figure 6 (b)

[0145] First, the first 9 bytes can have the same structure as the broadcast TWT parameter set in existing protocols, specifically including a 2-byte request type field, a 1-byte TWT field (i.e., the target wake-up time field), a 1-byte minimum TWT wake-up duration field, and a 2-byte broadcast TWT information field. The request type field contains a broadcast TWT suggestion field, which contains 3 bits, namely bits 8 to 10 of the request type field, such as b7 to b9. Considering that legacy STAs can skip the first 9 bytes and then continue skipping the second 9 bytes, the second field in the second 9 bytes also contains 3 bits, namely bits 8 to 10 of the first field.

[0146] Optionally, such as Figure 6 In (c), the first field in the second 9 bytes can be a "Request Type Extension Field," the second field can be a "Ambiguity Dissolution Field," and the "Request Type Extension Field" is 2 bytes. Following the Request Type Extension Field is a 3-byte r-TWT business information field. Optionally, the last 4 bytes of the second 9 bytes are reserved bytes.

[0147] Optionally, in the above Figure 6 In designs (a) to (c) of 6, the first 9 bytes, in addition to the request type field and the broadcast TWT information field, may also include a TWT field, a minimum TWT wake-up duration field, and a TWT wake-up interval mantissa field, each with a length as shown in Figure 6. Figure 6 As shown in the image.

[0148] In one implementation, the value of the broadcast TWT suggestion field in the first 9 bytes can be set to 4, indicating that the TWT type specified by the broadcast TWT parameter set is r-TWT. However, legacy STAs cannot understand this request type.

[0149] In view of this, this application designs bits 8 to 10 of the 16 bits in the Request Type Extension field contained in the second 9 bytes of the first broadcast TWT parameter set as an ambiguity resolution field, and sets its value to 4. For legacy STAs resolving the first broadcast TWT parameter set, a value of 4 for this ambiguity resolution field will have the same effect as a value of 4 for the broadcast TWT suggestion field in the first 9 bytes.

[0150] In other words, for the legacy STA, after receiving the first broadcast TWT parameter set, the broadcast TWT suggestion field in the first 9-byte request type field has a value of 4. As mentioned above, the legacy STA cannot understand this request type. Therefore, the legacy STA intends to skip the first 9 bytes and process the second 9 bytes. Since the ambiguity disambiguation field in the second 9 bytes is also set to 4, the legacy STA will assume that this is another broadcast TWT parameter set with a broadcast TWT suggestion field value of 4. Because it cannot understand this request type, the legacy STA will continue to skip the second 9 bytes, thus avoiding the problem of the legacy STA's perceived start time of the broadcast TWT parameter set being inconsistent with the actual start time, thereby preventing misreading by the legacy STA.

[0151] It should be noted that in this implementation, when the value of the broadcast TWT suggestion field in a broadcast TWT parameter set is 4, the EHT STA can understand the request type. That is, the EHT STA will know that the TWT type specified by the broadcast TWT parameter set is r-TWT.

[0152] In another implementation, the value of the broadcast TWT suggestion field in the first 9 bytes of the first broadcast TWT parameter set can be set to one of 5 to 7. On the one hand, if the broadcast TWT suggestion field is set to one of 5 to 7, the legacy STA still cannot understand the request type and will skip the first 9 bytes, instead parsing the second 9 bytes. If the ambiguity dissipation field of the request type extension field in the second 9 bytes is set to 4, as mentioned above, the legacy STA continues to skip the second 9 bytes, thus achieving the same effect as the first implementation and avoiding misreading by the legacy STA. On the other hand, for the EHT STA, if the broadcast TWT suggestion field of a broadcast TWT parameter set is set to 4, the EHT STA knows that the TWT type specified by the broadcast TWT parameter set is r-TWT. When the broadcast proposal field of a broadcast TWT parameter set takes the value of one of 5 to 7, the EHT STA will know that the TWT type specified by the broadcast TWT parameter set is r-TWT, and that the broadcast TWT parameter set is an extended broadcast TWT parameter set that is extended to two 9-byte sets, which is the first broadcast TWT parameter set in this application.

[0153] Therefore, the first 9-byte broadcast TWT suggestion field in the first broadcast TWT parameter set can be set to any value from 4 to 7, and the second 9-byte disambiguation field can also be set to any value from 4 to 7. That is, the first 9-byte broadcast TWT suggestion field belongs to the set {4, 5, 6, 7}, and the second 9-byte disambiguation field also belongs to the set {4, 5, 6, 7}. This design also allows legacy STAs to skip the first 9 bytes of the broadcast TWT parameter set, and subsequently skip the second 9 bytes, preventing misreading by legacy STAs.

[0154] It can be seen that in Scheme 2, a TWT element can contain both TWT service information for legacy STAs and r-TWT service information for EHT STAs, without causing misreading by legacy STAs.

[0155] Option 3

[0156] A TWT element can contain at most one broadcast TWT parameter set with an r-TWT service information field, and this broadcast TWT parameter set with the r-TWT service information field can only be the last broadcast TWT parameter set of that TWT element. Figure 7 To illustrate.

[0157] See Figure 7 , Figure 7 This is a schematic diagram of the frame structure of the TWT element provided in this application.

[0158] like Figure 7 The TWT element contains n broadcast TWT parameter sets. The first n-1 broadcast TWT parameter sets are not allowed to contain the r-TWT service information field. Only the last broadcast TWT parameter set (i.e., the nth broadcast TWT parameter set) is allowed to contain the r-TWT service information field. Figure 7 The nth broadcast TWT parameter set in the example is an example of the first broadcast TWT parameter set in this application.

[0159] For legacy STAs, the first n-1 broadcast TWT parameter sets will not cause misreading. For the last broadcast TWT parameter set, if broadcast TWT parameter set n contains a request type field, and the request type field contains a broadcast TWT suggestion field, where the broadcast TWT suggestion field can be set to 4. As described in Scheme 3 above, if the broadcast TWT suggestion field is set to 4, legacy STA will not be able to understand the TWT type specified by broadcast TWT parameter set n, and will therefore skip 9 bytes, i.e., skip broadcast TWT parameter set n. Combined with the length indicated by the length field of the TWT element, after skipping these 9 bytes, if there is not enough length for the subsequent broadcast TWT parameter sets, legacy STA will end the parsing of the TWT element, thus avoiding misreading.

[0160] As can be seen, Scheme 3 does not require modification of the frame structure of the TWT element; it only requires defining the framing rules of the TWT element.

[0161] Option 4

[0162] A new element type, the r-TWT element, is introduced, along with a corresponding element identifier. This means the element identifier of the r-TWT element is incomprehensible to the legacy STA. Therefore, the legacy STA will not parse the r-TWT element, preventing misinterpretation of r-TWT elements containing r-TWT business information fields.

[0163] It should be understood that the r-TWT element mentioned in Scheme 4 refers to a TWT element containing the r-TWT business information field. The r-TWT element is an example of the first TWT element in this application.

[0164] See Figure 8 , Figure 8 This is a schematic diagram of the frame structure of the r-TWT element provided in this application. Figure 8 An r-TWT element includes an element identifier field, a length field, and an r-TWT parameter information field. The r-TWT parameter information field may contain one or more r-TWT parameter sets. This application does not focus on the frame structure of the r-TWT parameter set; those skilled in the art can design the frame structure of the r-TWT parameter set. For example, the r-TWT parameter set may adopt the same frame structure as the broadcast TWT parameter set, without limitation. The r-TWT service information field may be included in the r-TWT parameter set, for example, r-TWT parameter set 1.

[0165] The method for sending information provided in this application has been described in detail above. The communication device provided in this application will be described below.

[0166] See Figure 9 , Figure 9 A schematic block diagram of the communication device provided in this application. Figure 9 The communication device 1000 includes a processing unit 1100, a receiving unit 1200, and a transmitting unit 1300.

[0167] Optionally, the communication device 1000 may correspond to the access point in the embodiments of this application.

[0168] In this implementation, each unit of the communication device 1000 is used to perform the following functions:

[0169] The processing unit 1100 is used to generate broadcast management frames;

[0170] The broadcast management frame includes a first target wake-up time (TWT) element, the first TWT element includes a first broadcast TWT parameter set, and the first broadcast TWT parameter set includes a restriction TWT service information field.

[0171] Wherein, the first TWT element conforms to one of the following:

[0172] The first TWT element contains a negotiation type field, and the value of the negotiation type field is 3;

[0173] or,

[0174] The first TWT element contains a first broadcast TWT parameter set comprising two 9-byte sets. The first 9-byte set comprises a request type field and a broadcast TWT information field. The request type field comprises a broadcast TWT suggestion field, the value of which belongs to the set {4,5,6,7}. The broadcast TWT information field comprises a restriction TWT service information presence indication field, the value of which belongs to the set {4,5,6,7}. The second 9-byte set comprises a first field and the restriction TWT service information field. The first field is the first two bytes of the second 9-byte set. The restriction TWT service information field is located after the first field. The first field contains a second field, the position of which is the same as the position of the broadcast TWT suggestion field in the request type field of the first 9-byte set. The value of the second field belongs to the set {4,5,6,7}.

[0175] or,

[0176] The first broadcast TWT parameter set contained in the first TWT element is the last broadcast TWT parameter set in the broadcast TWT parameter set contained in the first TWT element. The first broadcast TWT parameter set contains a request type field, the request type field contains a broadcast TWT suggestion field, and the value of the broadcast TWT suggestion field belongs to the set {4,5,6,7}.

[0177] The sending unit 1300 is used to send the broadcast management frame.

[0178] Optionally, as an example, if the first broadcast TWT parameter set contained in the first TWT element is the two 9-byte structure, the restriction TWT service information field contained in the second 9 bytes contains 3 bytes.

[0179] The broadcast TWT proposal field contains 3 bits, which are the 8th to 10th bits in the request type field;

[0180] The second field contains 3 bits, which are the 8th to 10th bits in the first field.

[0181] Optionally, as an example, the last 4 bytes of the second 9 bytes are reserved bytes.

[0182] Alternatively, in another embodiment, the communication device 1000 corresponds to the access point in the embodiments of this application.

[0183] The processing unit 1100 is used to generate broadcast management frames;

[0184] The broadcast management frame includes a first TWT element, which includes an element identifier field and a restricted TWT parameter information field. The element identifier field is used to identify the first TWT element as a TWT element that includes a restricted TWT service information field, and the restricted TWT parameter information field includes the restricted TWT service information field.

[0185] The sending unit 1300 is used to send the broadcast management frame.

[0186] Optionally, the communication device 1000 may correspond to a first type of station in the embodiments of this application.

[0187] In this implementation, each unit of the communication device 1000 is used to perform the following functions:

[0188] The receiving unit 1200 is used to receive broadcast management frames from the access point;

[0189] The broadcast management frame includes a first TWT element, the first TWT element includes a first broadcast TWT parameter set, and the first broadcast TWT parameter set includes a restricted TWT service information field.

[0190] In addition, the first TWT element also includes a negotiation type field, the value of which is 3;

[0191] The processing unit 1100 is used to process the broadcast management frame.

[0192] Optionally, as an example, the processing unit 1100 is used for:

[0193] If the value of the negotiation type field of the first TWT element is 3, the first TWT element is not parsed.

[0194] Alternatively, in another embodiment, the receiving unit 1200 is configured to:

[0195] Receive broadcast management frames from the access point.

[0196] The broadcast management frame includes a first TWT element, the first TWT element includes a first broadcast TWT parameter set, and the first broadcast TWT parameter set includes a restricted TWT service information field.

[0197] Furthermore, the first broadcast TWT parameter set includes two 9-byte sets. The first 9-byte set contains a request type field and a broadcast TWT information field. The request type field contains a broadcast TWT suggestion field, the value of which belongs to the set {4,5,6,7}. The broadcast TWT information field contains a restriction TWT service information presence indication field, the value of which is 1. The second 9-byte set contains a first field and the restriction TWT service information field. The first field is the first two bytes of the second 9-byte set. The restriction TWT service information field is located after the first field. The first field contains a second field. The position of the second field in the first field is the same as the position of the broadcast TWT suggestion field in the request type field of the first 9-byte set. The value of the second field belongs to the set {4,5,6,7}.

[0198] The processing unit 1100 is used to process the broadcast management frame.

[0199] Optionally, in one example, the second 9 bytes contain a 3-byte Restricted TWT Service Information field and a 3-bit Broadcast TWT Proposal field, wherein the 3 bits in the Broadcast TWT Proposal field are the 8th to 10th bits in the Request Type field;

[0200] The second field contains 3 bits, which are the 8th to 10th bits in the first field.

[0201] Optionally, in one example, the last four bytes of the second nine bytes are reserved bytes.

[0202] Optionally, in one example, the processing unit 1100 is configured to:

[0203] If the value of the broadcast TWT suggestion field in the first broadcast TWT parameter set contained in the first TWT element belongs to the set {4,5,6,7}, skip the first 9 bytes;

[0204] If the value of the second field in the second 9 bytes belongs to the set {4,5,6,7}, then skip the second 9 bytes.

[0205] Alternatively, in another embodiment, the receiving unit 1200 is configured to:

[0206] Receive broadcast management frames from the access point.

[0207] The broadcast management frame contains a first TWT element, the first TWT element contains a first broadcast TWT parameter set, the first broadcast TWT parameter set is the last broadcast TWT parameter set in the first TWT element, the first broadcast TWT parameter set contains a request type field, the request type field contains a broadcast TWT suggestion field, and the value of the broadcast TWT suggestion field belongs to the set {4,5,6,7}.

[0208] The processing unit 1100 is used to process the broadcast management frame.

[0209] Optionally, as an example, the processing unit 1100 is used for:

[0210] If the value of the broadcast TWT suggestion field in the first broadcast TWT parameter set belongs to the set {4,5,6,7}, skip the first broadcast TWT parameter set. If, based on the length of the first TWT element, it is determined that the number of bytes or bits following the first broadcast TWT parameter set is insufficient to constitute a broadcast TWT parameter set, end the parsing of the first TWT element.

[0211] Alternatively, in another embodiment, the receiving unit 1200 is configured to:

[0212] A broadcast management frame is received from an access point, wherein the broadcast management frame includes a first TWT element, the first TWT element includes an element identifier field and a restricted TWT parameter information field, the element identifier field is used to indicate that the first TWT element is a TWT element that includes a restricted TWT service information field, and the restricted TWT parameter information field includes the restricted TWT service information field;

[0213] The processing unit 1100 is used to process the broadcast management frame.

[0214] Optionally, in one example, the processing unit 1100 is configured to:

[0215] Based on the element identifier of the first TWT element, the one or more restricted TWT elements are not parsed.

[0216] In the above implementation methods, the receiving unit 1200 and the transmitting unit 1300 can also be integrated into a transceiver unit, which has both receiving and transmitting functions. This is not a limitation here.

[0217] In various embodiments of the communication device 1000 corresponding to the access point, the processing unit 1100 is used to perform processing and / or operations implemented internally by the access point, other than the sending and receiving actions. The receiving unit 1200 is used to perform the receiving action of the access point, and the sending unit 1300 is used to perform the sending action of the access point.

[0218] For example, in Figure 5 In this process, the processing unit 1100 is used to execute step 510, and the sending unit 1300 is used to execute the sending action of step 520.

[0219] In various embodiments of the communication device 1000 corresponding to a first type of station, the processing unit 1100 is used to perform processing and / or operations implemented internally by the first type of station, other than the sending and receiving operations. The receiving unit 1200 is used to perform the receiving operation of the first type of station, and the sending unit 1300 is used to perform the sending operation of the first type of station.

[0220] For example, in Figure 5 In the process, the receiving unit 1200 is used to perform the receiving action in step 520, and the processing unit 1100 is used to perform step 530.

[0221] See Figure 10 , Figure 10 A schematic structural diagram of the communication device provided in this application. Figure 10The communication device 10 includes one or more processors 11, one or more memories 12, and one or more communication interfaces 13. The processor 11 is used to control the communication interface 13 to send and receive signals, the memory 12 is used to store computer programs, and the processor 11 is used to call and run the computer programs from the memory 12 so that the communication device 10 performs the processing performed by the access point or the first type of station in the various method embodiments of this application.

[0222] For example, processor 11 may have Figure 9 The processing unit 1100 shown has the following functions, and the communication interface 13 may have... Figure 9 The functions of the receiving unit 1200 and / or the transmitting unit 1300 shown are illustrated. Specifically, the processor 11 can be used to perform processing or operations executed internally by the communication device, and the communication interface 13 is used to perform the transmitting and / or receiving operations of the communication device.

[0223] In one implementation, the communication device 10 can be the access point in the method embodiment. In this implementation, the communication interface 13 can be the transceiver of the access point. The transceiver may include a receiver and / or a transmitter. Optionally, the processor 11 can be the baseband device of the access point, and the communication interface 13 can be a radio frequency device.

[0224] In another implementation, the communication device 10 can be a chip (or chip system) installed in the access point. In this implementation, the communication interface 13 can be an interface circuit or an input / output interface.

[0225] In one implementation, the communication device 10 can be a first type of station in the method embodiments. In this implementation, the communication interface 13 can be a transceiver for the first type of station. The transceiver can include a receiver and / or a transmitter. Optionally, the processor 11 can be a baseband device for the first type of station, and the communication interface 13 can be a radio frequency device.

[0226] In another implementation, the communication device 10 can be a chip (or chip system) installed in a first type of station. In this implementation, the communication interface 13 can be an interface circuit or an input / output interface.

[0227] in, Figure 10 The dashed box following a device (e.g., processor, memory, or communication interface) indicates that there can be more than one such device.

[0228] In addition, this application also provides a computer-readable storage medium storing computer instructions that, when executed on a computer, cause operations and / or processes performed by an access point in the various method embodiments of this application to be executed.

[0229] This application also provides a computer-readable storage medium storing computer instructions that, when executed on a computer, cause operations and / or processes performed by a first-type site in the various method embodiments of this application to be performed.

[0230] In addition, this application also provides a computer program product, which includes computer program code or instructions, such that when the computer program code or instructions are run on a computer, the operations and / or processes performed by the access point in the various method embodiments of this application are executed.

[0231] This application also provides a computer program product, which includes computer program code or instructions that, when run on a computer, cause operations and / or processes performed by a first type of site in the various method embodiments of this application to be executed.

[0232] Furthermore, this application also provides a chip including a processor, a memory for storing a computer program disposed independently of the chip, the processor being used to execute the computer program stored in the memory, causing a communication device on which the chip is installed to perform operations and / or processes performed by an access point in any of the method embodiments.

[0233] Furthermore, the chip may also include a communication interface. The communication interface may be an input / output interface or an interface circuit, etc. Furthermore, the chip may also include the memory.

[0234] This application also provides a chip including a processor, a memory for storing a computer program disposed independently of the chip, the processor for executing the computer program stored in the memory, causing a communication device on which the chip is installed to perform operations and / or processes performed by a first type of station in any of the method embodiments.

[0235] Furthermore, the chip may also include a communication interface. The communication interface may be an input / output interface or an interface circuit, etc. Furthermore, the chip may also include the memory.

[0236] Optionally, the processor can be one or more, and the memory can be one or more.

[0237] Furthermore, this application also provides a communication device (e.g., a chip or chip system) including a processor and a communication interface, the communication interface being used to receive (or input) data and / or information and transmit the received data and / or information to the processor, the processor processing the data and / or information, and the communication interface also being used to output (or output) the data and / or information processed by the processor, so that operations and / or processes performed by an access point in any method embodiment are executed.

[0238] This application also provides a communication device (e.g., a chip or chip system) including a processor and a communication interface, the communication interface being used to receive (or input) data and / or information and transmit the received data and / or information to the processor, the processor processing the data and / or information, and the communication interface being further used to output (or output) the data and / or information processed by the processor, so that operations and / or processes performed by a first type of station in any method embodiment are performed.

[0239] Furthermore, this application also provides a communication device including at least one processor coupled to at least one memory, the at least one processor being configured to execute a computer program or instructions stored in the at least one memory, causing the communication device to perform operations and / or processes performed by an access point in any of the method embodiments.

[0240] This application also provides a communication device including at least one processor coupled to at least one memory, the at least one processor being configured to execute a computer program or instructions stored in the at least one memory, causing the communication device to perform operations and / or processes performed by a first type of station in any of the method embodiments.

[0241] Furthermore, this application also provides a wireless communication system, including an access point and / or a first type of station as described in the method embodiments of this application. Optionally, it may also include a second type of station as described in the method embodiments.

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

[0243] The processor in this application embodiment can be an integrated circuit chip with the ability to process signals. In implementation, each step of the above method embodiment can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application embodiment can be directly implemented by a hardware encoding processor, or by a combination of hardware and software modules in the encoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0244] The memory in this application embodiment can be volatile memory or non-volatile memory, or it can include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0245] The methods provided in the above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, they can be implemented, in whole or in part, in the form of a computer program product. The computer program product may include one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media.

[0246] To facilitate a clear description of the technical solutions in the embodiments of this application, the embodiments of this application use designations such as "first" and "second" to distinguish identical or similar items with essentially the same function and purpose. For example, the designations of a first type of site and a second type of site are merely to distinguish between two types of sites that differ in the applicable standards they describe. Those skilled in the art will understand that designations such as "first" and "second" do not limit the quantity. That is, in practical applications, there can be one or more first type sites, and there can also be one or more second type sites.

[0247] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A existing alone, A and B existing simultaneously, and B existing alone. A, B, and C can all be singular or plural, without limitation.

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

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

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

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

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

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

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

Claims

1. A method for sending information, characterized in that, include: Generate a broadcast management frame, the broadcast management frame containing a first target wake-up time (TWT) element, the first TWT element containing a first broadcast TWT parameter set, the first broadcast TWT parameter set containing a restriction TWT service information field; Wherein, the first TWT element conforms to one of the following: The first TWT element contains a negotiation type field, and the value of the negotiation type field is 3; or, The first TWT element contains a first broadcast TWT parameter set comprising two 9-byte sets. The first 9-byte set comprises a request type field and a broadcast TWT information field. The request type field contains a broadcast TWT suggestion field, the value of which belongs to the set {4, 5, 6, 7}. The broadcast TWT information field contains a restriction TWT service information presence indication field, the value of which is 1. The second 9-byte set comprises a first field and the restriction TWT service information field. The first field consists of the first two bytes of the second 9-byte set. The restriction TWT service information field is located after the first field. The first field contains a second field, the position of which is the same as the position of the broadcast TWT suggestion field in the request type field of the first 9-byte set. The value of the second field belongs to the set {4, 5, 6, 7}. or, The first broadcast TWT parameter set contained in the first TWT element is the last broadcast TWT parameter set in the broadcast TWT parameter set contained in the first TWT element. The first broadcast TWT parameter set contains a request type field, the request type field contains a broadcast TWT suggestion field, and the value of the broadcast TWT suggestion field belongs to the set {4, 5, 6, 7}. Send the broadcast management frame.

2. The method as claimed in claim 1, characterized in that, If the first broadcast TWT parameter set contained in the first TWT element is the two 9-byte structures, and the restricted TWT service information field contained in the second 9-byte structure contains 3 bytes, The broadcast TWT proposal field contains 3 bits, which are the 8th to 10th bits in the request type field; The second field contains 3 bits, which are the 8th to 10th bits in the first field.

3. The method as described in claim 2, characterized in that, The last four bytes of the second nine-byte sequence are reserved bytes.

4. A method for sending information, characterized in that, include: A broadcast management frame is generated, the broadcast management frame includes a first TWT element, the first TWT element includes an element identifier field and a restricted TWT parameter information field, the element identifier field is used to identify the first TWT element as a TWT element that includes a restricted TWT service information field, and the restricted TWT parameter information field includes the restricted TWT service information field; Send the broadcast management frame.

5. A method for receiving information, characterized in that, include: The first type of station receives broadcast management frames from the access point. The broadcast management frame includes a first TWT element, the first TWT element includes a first broadcast TWT parameter set, and the first broadcast TWT parameter set includes a restricted TWT service information field. In addition, the first TWT element also includes a negotiation type field, the value of which is 3; The first type of site processes the broadcast management frame.

6. The method as described in claim 5, characterized in that, The first type of station processes the broadcast management frame, including: The first type of site does not parse the first TWT element when the value of the negotiation type field of the first TWT element is 3.

7. A method for receiving information, characterized in that, include: The first type of station receives broadcast management frames from the access point. The broadcast management frame includes a first TWT element, the first TWT element includes a first broadcast TWT parameter set, and the first broadcast TWT parameter set includes a restricted TWT service information field. Furthermore, the first broadcast TWT parameter set includes two 9-byte sets. The first 9-byte set contains a request type field and a broadcast TWT information field. The request type field contains a broadcast TWT suggestion field, the value of which belongs to the set {4, 5, 6, 7}. The broadcast TWT information field contains a restriction TWT service information presence indication field, the value of which is 1. The second 9-byte set contains a first field and the restriction TWT service information field. The first field is the first two bytes of the second 9-byte set. The restriction TWT service information field is located after the first field. The first field contains a second field. The position of the second field in the first field is the same as the position of the broadcast TWT suggestion field in the request type field of the first 9-byte set. The value of the second field belongs to the set {4, 5, 6, 7}. The first type of site processes the broadcast management frame.

8. The method of claim 7, characterized in that, The second 9 bytes contain a 3-byte restricted TWT service information field and a 3-bit broadcast TWT suggestion field. The 3 bits in the broadcast TWT suggestion field are the 8th to 10th bits in the request type field. The second field contains 3 bits, which are the 8th to 10th bits in the first field.

9. The method of claim 8, characterized in that, The last four bytes of the second nine-byte sequence are reserved bytes.

10. The method according to any one of claims 7-9, characterized in that, The first type of station processes the broadcast management frame, including: If the value of the broadcast TWT suggestion field in the first broadcast TWT parameter set contained in the first TWT element belongs to the set {4, 5, 6, 7}, the first type of site skips the first 9 bytes; If the value of the second field in the second 9 bytes of the first type of site belongs to the set {4, 5, 6, 7}, the second 9 bytes are skipped.

11. A method for receiving information, characterized in that, include: The first type of station receives broadcast management frames from the access point. The broadcast management frame contains a first TWT element, the first TWT element contains a first broadcast TWT parameter set, the first broadcast TWT parameter set is the last broadcast TWT parameter set in the first TWT element, the first broadcast TWT parameter set contains a request type field, the request type field contains a broadcast TWT suggestion field, and the value of the broadcast TWT suggestion field belongs to the set {4, 5, 6, 7}. The first type of site processes the broadcast management frame.

12. The method of claim 11, characterized in that, The first type of station processes the broadcast management frame, including: If the value of the broadcast TWT suggestion field in the first broadcast TWT parameter set belongs to the set {4, 5, 6, 7}, the first type of site skips the first broadcast TWT parameter set. If, based on the length of the first TWT element, it is determined that the number of bytes or bits following the first broadcast TWT parameter set is insufficient to constitute a broadcast TWT parameter set, the parsing of the first TWT element ends.

13. A method for receiving information, characterized in that, include: The first type of station receives broadcast management frames from the access point. The broadcast management frame includes a first TWT element, which includes an element identifier field and a restricted TWT parameter information field. The element identifier field is used to indicate that the first TWT element is a TWT element that includes a restricted TWT service information field, and the restricted TWT parameter information field includes the restricted TWT service information field. The first type of site processes the broadcast management frame.

14. The method of claim 13, characterized in that, The first type of station processes the broadcast management frame, including: The first type of site does not parse the first TWT element based on the element identifier of the first TWT element.

15. A communication device, characterized in that, include: The processing unit is configured to generate a broadcast management frame, the broadcast management frame containing a first TWT element, the first TWT element containing a first broadcast TWT parameter set, and the first broadcast TWT parameter set containing a restricted TWT service information field. Wherein, the first TWT element conforms to one of the following: The first TWT element contains a negotiation type field, and the value of the negotiation type field is 3; or, The first TWT element contains a first broadcast TWT parameter set comprising two 9-byte sets. The first 9-byte set comprises a request type field and a broadcast TWT information field. The request type field contains a broadcast TWT suggestion field, the value of which belongs to the set {4, 5, 6, 7}. The broadcast TWT information field contains a restriction TWT service information presence indication field, the value of which is 1. The second 9-byte set comprises a first field and the restriction TWT service information field. The first field consists of the first two bytes of the second 9-byte set. The restriction TWT service information field is located after the first field. The first field contains a second field, the position of which is the same as the position of the broadcast TWT suggestion field in the request type field of the first 9-byte set. The value of the second field belongs to the set {4, 5, 6, 7}. or, The first broadcast TWT parameter set contained in the first TWT element is the last broadcast TWT parameter set in the broadcast TWT parameter set contained in the first TWT element. The first broadcast TWT parameter set contains a request type field, the request type field contains a broadcast TWT suggestion field, and the value of the broadcast TWT suggestion field belongs to the set {4, 5, 6, 7}. The transmitting unit is used to transmit the broadcast management frame.

16. The communication device as claimed in claim 15, characterized in that, If the first broadcast TWT parameter set contained in the first TWT element is the two 9-byte structures, and the restricted TWT service information field contained in the second 9-byte structure contains 3 bytes, The broadcast TWT proposal field contains 3 bits, which are the 8th to 10th bits in the request type field; The second field contains 3 bits, which are the 8th to 10th bits in the first field.

17. The communication device as claimed in claim 16, characterized in that, The last four bytes of the second nine-byte sequence are reserved bytes.

18. A communication device, characterized in that, include: A processing unit is configured to generate a broadcast management frame, the broadcast management frame containing a first TWT element, the first TWT element containing an element identifier field and a restricted TWT parameter information field, the element identifier field being used to identify the first TWT element as a TWT element containing a restricted TWT service information field, and the restricted TWT parameter information field containing the restricted TWT service information field; The transmitting unit is used to transmit the broadcast management frame.

19. A communication device, characterized in that, include: A receiving unit is configured to receive a broadcast management frame from an access point, the broadcast management frame containing a first TWT element, the first TWT element containing a first broadcast TWT parameter set, and the first broadcast TWT parameter set containing a restricted TWT service information field. In addition, the first TWT element also includes a negotiation type field, the value of which is 3; A processing unit is used to process the broadcast management frame.

20. The communication device as claimed in claim 19, characterized in that, The processing unit is used for: If the value of the negotiation type field of the first TWT element is determined to be 3, the first TWT element is not parsed.

21. A communication device, characterized in that, include: The receiving unit is used to receive broadcast management frames from the access point; The broadcast management frame includes a first TWT element, the first TWT element includes a first broadcast TWT parameter set, and the first broadcast TWT parameter set includes a restricted TWT service information field. Furthermore, the first broadcast TWT parameter set includes two 9-byte sets. The first 9-byte set contains a request type field and a broadcast TWT information field. The request type field contains a broadcast TWT suggestion field, the value of which belongs to the set {4, 5, 6, 7}. The broadcast TWT information field contains a restriction TWT service information presence indication field, the value of which is 1. The second 9-byte set contains a first field and the restriction TWT service information field. The first field is the first two bytes of the second 9-byte set. The restriction TWT service information field is located after the first field. The first field contains a second field. The position of the second field in the first field is the same as the position of the broadcast TWT suggestion field in the request type field of the first 9-byte set. The value of the second field belongs to the set {4, 5, 6, 7}. A processing unit is used to process the broadcast management frame.

22. The communication device as claimed in claim 21, characterized in that, The second 9 bytes contain a 3-byte restricted TWT service information field and a 3-bit broadcast TWT suggestion field. The 3 bits in the broadcast TWT suggestion field are the 8th to 10th bits in the request type field. The second field contains 3 bits, which are the 8th to 10th bits in the first field.

23. The communication device as claimed in claim 22, characterized in that, The last four bytes of the second nine-byte sequence are reserved bytes.

24. The communication device as claimed in any one of claims 21 to 23, characterized in that, The processing unit is used for: If it is determined that the value of the broadcast TWT suggestion field in the first broadcast TWT parameter set contained in the first TWT element belongs to the set {4, 5, 6, 7}, the first 9 bytes are skipped; If it is determined that the value of the second field in the second 9 bytes belongs to the set {4, 5, 6, 7}, then the second 9 bytes are skipped.

25. A communication device, characterized in that, include: The receiving unit is used to receive broadcast management frames from the access point. The broadcast management frame contains a first TWT element, the first TWT element contains a first broadcast TWT parameter set, the first broadcast TWT parameter set is the last broadcast TWT parameter set in the first TWT element, the first broadcast TWT parameter set contains a request type field, the request type field contains a broadcast TWT suggestion field, and the value of the broadcast TWT suggestion field belongs to the set {4, 5, 6, 7}. A processing unit is used to process the broadcast management frame.

26. The communication device as claimed in claim 25, characterized in that, The processing unit is used for: If the value of the broadcast TWT suggestion field in the first broadcast TWT parameter set belongs to the set {4, 5, 6, 7}, skip the first broadcast TWT parameter set. If, based on the length of the first TWT element, it is determined that the number of bytes or bits following the first broadcast TWT parameter set is insufficient to constitute a broadcast TWT parameter set, end the parsing of the first TWT element.

27. A communication device, characterized in that, include: The receiving unit is used to receive broadcast management frames from the access point. The first TWT element includes an element identifier field and a restricted TWT parameter information field. The element identifier field is used to indicate that the first TWT element is a TWT element that includes a restricted TWT service information field. The restricted TWT parameter information field includes the restricted TWT service information field. A processing unit is used to process the broadcast management frame.

28. The communication device as claimed in claim 27, characterized in that, The processing unit is used for: Based on the element identifier of the first TWT element, the first TWT element is not parsed.

29. A communication device, characterized in that, The device includes at least one processor coupled to at least one memory, the at least one processor being configured to execute a computer program or instructions stored in the at least one memory to cause the communication device to perform the method as described in any one of claims 1-4, or to perform the method as described in any one of claims 5-14.

30. A chip, characterized in that, The device includes a processor and a communication interface, the communication interface being used to receive data and / or information and transmit the received data and / or information to the processor, the processor processing the data and / or information to perform the method as described in any one of claims 1-4, or to perform the method as described in any one of claims 5-14.

31. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on a computer, cause the method as described in any one of claims 1-4, or the method as described in any one of claims 5-14, to be implemented.

32. A computer program product, characterized in that, The computer program product includes computer program code that, when run on a computer, causes the method as described in any one of claims 1-4, or the method as described in any one of claims 5-14, to be implemented.

Images