Resource sharing methods and related apparatus

Abstract

The present application belongs to the technical field of wireless communications. Provided are resource sharing methods and a related apparatus. A resource sharing method is applied to a first station side, and comprises: receiving a second frame sent by at least one second station; and, on the basis of the second frame, sending a third frame to a target station among the at least one second station, the third frame being used for indicating a first transmission resource to the target station, and the first transmission resource being a transmission resource shared by a first station with the target station.

Description

Resource sharing methods and related devices Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a resource sharing method and related apparatus. Background Technology

[0002] In WiFi networks based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11bn standard for WiFi-8 and its subsequent evolutions, how to enable multiple nearby access points (APs) to share time-frequency domain resources, thereby avoiding interference between them and improving overall system performance and resource utilization, is a question worth discussing. Summary of the Invention

[0003] This application provides a resource sharing method and related apparatus to achieve flexible sharing and efficient utilization of transmission resources.

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

[0005] This application provides a resource sharing method applied to a first site, comprising: receiving a second frame sent by at least one second site; and, based on the second frame, sending a third frame to a target site among the at least one second site, wherein the third frame is used to indicate a first transmission resource to the target site, the first transmission resource being a transmission resource shared by the first site to the target site.

[0006] A second aspect of this application provides a resource sharing method applied to a second site, comprising: sending a second frame to a first site, the second frame including but not limited to at least one of the following: first indication information, second indication information, third indication information, and / or fourth indication information, wherein the first indication information is used to indicate service status information, the second indication information is used to indicate whether bandwidth expansion operation is supported, the third indication information is used to indicate supported multi-AP cooperative transmission mode information, and the fourth indication information is used to indicate identification information of non-AP sites participating in the multi-AP cooperative transmission; and receiving a third frame sent by the first site, the third frame being used to indicate a first transmission resource shared by the first site.

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

[0008] A fourth aspect of this application also provides a computer-readable storage medium, the computer-readable storage medium including instructions that, when executed, cause the method described in any of the preceding claims to be implemented. Attached Figure Description

[0009] Figure 1 is a flowchart of a possible existing technology resource sharing process;

[0010] Figure 2 is a flowchart of a possible resource sharing method provided in this application;

[0011] Figure 2a is a schematic diagram of a possible frame structure provided in this application;

[0012] Figure 2b is a schematic diagram of another possible frame structure provided in this application;

[0013] Figure 2c is a schematic diagram of a possible frame structure provided in this application;

[0014] Figure 2d is a schematic diagram of another possible frame structure provided in this application;

[0015] Figure 2e is a schematic diagram of another possible frame structure provided in this application;

[0016] Figure 2f is a schematic diagram of another possible frame structure provided in this application;

[0017] Figure 2g is a schematic diagram of another possible frame structure provided in this application;

[0018] Figure 2h is a schematic diagram of another possible frame structure provided in this application;

[0019] Figure 2i is a schematic diagram of another possible frame structure provided in this application;

[0020] Figure 3 is a flowchart of another possible resource sharing method provided in this application;

[0021] Figure 3a is a schematic diagram of another possible frame structure provided in this application.

[0022] Figure 3b is a schematic diagram of another possible frame structure provided in this application.

[0023] Figure 3c is an interaction diagram of another possible resource sharing method provided in this application;

[0024] Figure 4 is a flowchart of another possible resource sharing method provided in this application;

[0025] Figure 4a is a schematic diagram of another possible frame structure provided in this application;

[0026] Figure 5 is a storage diagram of a possible wireless communication device provided in this application. Detailed Implementation

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

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

[0029] It should be understood that the term "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should be noted that the naming of the parameters in this document is for ease of description; other names may be used in practice, and this application does not impose any restrictions on their specific use.

[0030] The messages described in this article include frames, instructions, commands, etc., and the names of device or functional entities, process names, frames, fields, etc. are not unique and are only used to assist in the description of functions, methods, behaviors, information, etc.

[0031] This application applies to the field of multi-AP cooperative multiple access and transmission opportunity sharing in Wi-Fi networks based on the IEEE 802.11bn standard, specifically Wi-Fi 8 and its subsequent evolutions. The target application scenarios include multiple adjacent APs sharing transmission opportunities (TXOP) to jointly utilize a single transmission resource (time and / or frequency, etc.), thereby avoiding interference and improving overall system performance. The core technology involves APs instructing each other on rules and resources for sharing transmission opportunities to ensure that the shared time is used according to service needs, rather than inefficiently and arbitrarily. Please refer to Figure 1, which shows an interaction diagram of a possible TXOP sharing method in the prior art, including the following steps:

[0032] After AP1 obtains a transmission opportunity (TXOP), it sends an Initial Control Frame (ICF) to its nearby APs, including AP2 and AP3.

[0033] AP 2 and AP 3 reply with response frames to AP 1 indicating whether they participate in Co-TDMA (i.e. whether they need AP 1 to share a portion of its acquired TXOPs with them);

[0034] Then AP1 communicates with its associated STA(s);

[0035] After completing communication with its associated STA(s), AP 1 sends a MU-RTS TXS Trigger frame to AP 3 as instructed by the Response frame(s), declaring that a portion of the TXOP will be shared with AP 3 for use;

[0036] After AP 3 responds to a CTS frame to AP 1, it immediately begins communicating with its associated STA(s) using the shared TXOP time.

[0037] After AP 3 finishes communicating with its associated STA(s), if there is still time remaining after the sharing, it will return the remaining TXOP time to AP 1, and AP 1 will continue to use the remaining TXOP time.

[0038] However, through analysis of a series of existing solutions, the applicant discovered the following problems, including but not limited to:

[0039] Question 1: Currently, Co-TDMA does not support bandwidth extension operations. When an AP that has acquired a TXOP shares a portion of its TXOP with other APs, the AP being shared with can use channel (frequency) resources within the operating bandwidth range of the AP initiating the sharing by default. It is not currently supported for the AP being shared to extend its use of channel (frequency) resources outside the operating bandwidth range of the AP initiating the sharing through certain rules.

[0040] Question 2: Current Co-TDMA does not support adjusting the TXOP usage order based on service priority. The existing 802.11bn draft specifies that the AP initiating the sharing must first use the TXOP for transmission, and then share a portion of the remaining TXOP with the AP being shared with. Existing proposals and patents limit the sharing to a specific operation where the AP being shared with can use the TXOP first, followed by the AP initiating the sharing. Currently, it does not support the AP initiating the sharing deciding the TXOP usage order based on service priority information from polled APs.

[0041] Question 3: Current Co-TDMA does not support multi-AP cooperative transmission within the shared time. Limited by the 802.11bn draft, where the AP initiating the TXOP sharing is only allowed to transmit one or more PPDUs by another AP within the shared time, and by existing patents allowing each STA to perform its own transmission according to its allocated time after sharing with multiple STAs, the following two types of multi-AP cooperative transmission operations cannot be achieved: the AP initiating the TXOP sharing cannot perform Co-BF and / or Co-SR transmissions together with the AP being shared with; the AP initiating the TXOP sharing does not support allowing two other APs to perform Co-BF and / or Co-SR transmissions together.

[0042] Question 4: Current Co-TDMA does not support the AP that initiated the sharing continuing to transmit autonomously within the shared time. Existing technology supports the first site requesting the second site to share the time in reverse within the time shared with the second site, allowing the first site to transmit; however, this design is limited to the first site requesting the second site, and the second site then sharing, and does not support autonomous transmission without a request.

[0043] Question 5: Current Co-TDMA TXOP return does not support returning only a portion of the TXOP usage rights. Existing technology includes TXOP return operations, but by default, the device sharing the TXOP returns all remaining time (and / or frequency) resources to the device that initiated the TXOP (i.e., the AP).

[0044] In view of this, this application proposes several resource sharing methods to address the aforementioned issues. Specifically, these are categorized into the following scenarios: A) sharing resources with one site; B) sharing resources with multiple sites. Furthermore, regarding issue 5, this application proposes a new return mechanism for shared resources, which will be described in detail below. For ease of description, this application uses a shared transmission resource as a TXOP as an example. In practical applications, the transmission resource can also be a time-domain resource or a frequency-domain resource, etc., without limitation.

[0045] For scenario A, where resources are shared with a website, please refer to Figure 2, which is a flowchart of a possible resource sharing method, including but not limited to at least one of the following steps:

[0046] 201. The first station sends a first frame to at least one second station;

[0047] A first station sends a first frame to at least one second station within its transmission range. This first frame is used to request station information, which is used to determine the target station. Specifically, the first frame carries at least one of the following: first request information and second request information. The first request information is used to request service status information, which in this application includes, but is not limited to, at least one of the following: service type, service volume, service priority information, service expiration time information, or service latency requirement information. The second request information is used to request whether the capability to perform bandwidth expansion operations is supported.

[0048] It should be noted that the first frame includes at least one first field, each of which corresponds to one of the second stations. The receiver address RA of the first frame can be a broadcast MAC address. The first frame includes a first receiver indication and / or a second receiver indication. The first receiver indication is used to indicate the identification information of the AP in the second station, and the second receiver indication is used to indicate the identification information of the non-AP station in the second station. For example, the explanation uses a BSRP Trigger frame as the first frame. It is understood that the first frame can also be other frames, such as control frames, data frames, etc., and this application does not limit the specific frame type. Please refer to Figure 2a, which is a schematic diagram of the frame structure of a possible Buffer Status Report Poll (BSRP) trigger frame. The common information field can be either the EHT variant common Info field on the left or the UHR variant common Info field on the right of Figure 2a. The trigger type field is used to indicate what type of trigger frame the trigger frame is. For example, when the trigger type field is set to 4, it means that the trigger frame is a BSRP trigger frame.

[0049] In addition, the first request information carried in the first frame can be implemented in the following two ways:

[0050] Option 1a: No special instruction is required. When the Trigger Type field is set to 4, it indicates that the Trigger frame is a BSRP Trigger frame. If the GI And HE / UHR-LTF Type subfield of the Common Info field is set to a value other than 3, the receiver is required by default to provide service status information in the format of a TB PPDU, i.e., to provide service type, service volume, and / or service priority information, etc. When the GI And HE / UHR-LTF Type subfield of the Common Info field of the unicast Trigger frame is set to 3, the receiver is required by default to provide service status information in the form of a Multi-STA BlockAck frame contained in a non-HT (duplicate) PPDU, i.e., to provide service type, service volume, and / or service priority information, etc.

[0051] Option 2a: Explicit instructions are required. For example, define any (EHT / UHR) Reserved field in the EHT variant Common Info field and / or UHR variant Common Info field of Figure 2a as "Traffic Info Requested". When Traffic Info Requested is set to 1, it means that the receiver needs to provide feedback on the service status information. It should be noted that when providing feedback on the service status information, the receiver also needs to provide the due date information (or delay requirement information) for each service. When Traffic Info Requested is set to 0, it means that the receiver does not need to provide feedback on the service status information.

[0052] Similarly, the second request information carried in the first frame is used to request whether the capability for bandwidth expansion operation is supported. The implementation of this second request information requires explicit indication, which can be achieved by the first frame including a bandwidth expansion field. This bandwidth expansion field indicates the second request information, and each value of the bandwidth expansion field corresponds to different information requested or indicated by the second request information. Optionally, the bandwidth expansion field can have a first value and a second value. When the bandwidth expansion field is the first value, the information requested or indicated by the second request information includes: the receiver providing feedback on whether the capability for bandwidth expansion operation is supported and / or the available bandwidth range, and / or, the shared user within the first transmission resource is allowed to perform bandwidth expansion operation; or, when the bandwidth expansion field is the second value, the information requested or indicated by the second request information includes: the receiver not providing feedback on whether the capability for bandwidth expansion operation is supported, and / or, the shared user within the first transmission resource is not allowed to perform bandwidth expansion operation. For ease of understanding, exemplarily, the implementation in this application can be as follows: Any (EHT / UHR) Reserved field in the EHT variant Common Info field and / or UHR variant Common Info field of Figure 2a can be defined as a Bandwidth Expansion field. When the Bandwidth Expansion is set to 1, there are two possible operations: Operation 1: The receiver needs to provide feedback on whether it supports the bandwidth expansion operation, and / or, if supported, the bandwidth range that can be expanded; Operation 2: The first site indicates that the recipient can perform a bandwidth expansion operation during the current TXOP sharing period. When the Bandwidth Expansion is set to 0, there are two possible operations: Operation 1: The receiver does not need to provide feedback on whether it supports the bandwidth expansion operation; Operation 2: The first site indicates that the recipient cannot perform a bandwidth expansion operation during the current TXOP sharing period.

[0053] Optionally, in this embodiment, the first site and at least one second site can both be access points (APs).

[0054] 202. The first station receives a second frame sent by at least one second station;

[0055] It should be noted that in step 202, the first station receives a second frame sent by at least one second station. This second frame can be used by at least one second station in response to the first frame received in step 201, or it can be actively sent by at least one second station, such as periodic sending or condition-triggered sending. The specifics are not limited here. That is, step 201 is an optional step.

[0056] After receiving the first frame sent by the first station, the second station sends a response second frame to the first station. That is, the first station receives at least one second frame sent by the second station. The second frame includes at least first indication information and / or second indication information, wherein the first indication information is used to indicate service status information, and the second indication information is used to indicate whether the bandwidth expansion operation is supported. In this embodiment, the second frame can be a QoS Null frame, a QoS Data frame, or a Multi-STA BlockAck frame, or other frames, which are not specifically limited here. For example, corresponding to the implementation of the first request information carried by the first frame in step 201, Option 1a: when the GI And HE / UHR-LTF Type subfield is set to a value not equal to 3, the second frame is a QoS Null frame or a QoS Data frame; when the GI And HE / UHR-LTF Type subfield is set to a value equal to 3, the second frame is a Multi-STA BlockAck frame.

[0057] When the second frame is a QoS Null frame or a QoS Data frame, the first indication information, i.e., the service status information corresponding to the second site, will be indicated through the QoS Control field or BSR Control field. It should be noted that, as described in Option 2a above, since the first request information included in the first frame can also request the receiver to provide feedback on the expiration time information or latency requirement information for each service, the first indication information may include the expiration time information or latency requirement information for each service. Furthermore, there are various ways in which the second frame carries the first indication information, including but not limited to the QoS Control field, HT Control field, A-Control field, or per AID TID info field carried in the second frame. These will be explained in detail below:

[0058] Option 1b: Use the QoS Control field to carry the service expiration time information or service delay requirement information from the first indication information;

[0059] At least one second station, such as AP 2 and / or AP 3, sends a second frame including a QoS Control field, using Applicable frame(sub)types: QoS Null frames sent by HC. For example, Bits 8 to 15 of the QoS Control field can be defined as the AP PS Buffer State subfield as shown in Figure 2b. Specifically, the reserved bit B0 of the AP PS Buffer State subfield is defined as Buffer Time Indicated. When Buffer Time Indicated is set to 1, it means that the current AP PS Buffer State subfield indicates the service expiration time information or service delay requirement information cached / to be transmitted by the second station.

[0060] The Buffered State Indicated subfield indicates whether the buffered state of the AP is specified. When this subfield is set to 1, it indicates that the buffered state of the AP is explicitly specified.

[0061] The Highest Priority Buffered AC subfield indicates the highest priority access class for remaining buffered traffic in the AP, excluding the MSDU or A-MSDU of the current frame.

[0062] Optionally, when the reserved bit B0 is defined as Buffer Time Indicated (=1), Bits 4 to 7 can also be redefined as the Buffered Time field, which is used to indicate the latency requirement or expiration time corresponding to the cached service AC. The starting point of the time is the sending / receiving of the second frame.

[0063] When the value of the Buffered State Indicated subfield is 0, both the Highest Priority Buffered AC subfield and the Buffered Time subfield are reserved.

[0064] Option 2b: The ability to carry service expiration time information or service delay requirement information from the first indication information and / or bandwidth expansion operation information from the second indication information using the HT Control field or A-Control field;

[0065] For example, the format of the HT Control field can be shown in Figure 2c. When B0 B1 = 11, it indicates that the HT Control field is an HE variant HT Control field. B2 to B31 are used to represent the A-Control field. The format of the A-Control field (which is included in the HE variant HT Control field) can be shown in Figure 2d, including the Control List subfield and the Padding subfield. The Control List contains one or more Control fields. The format of each Control field is shown in Figure 2e, carrying the Control ID and Control Information. The Control ID occupies 4 bits. When the value of the Control ID is set to 3, the Control Information is used to indicate the Buffer Status Report (BSR), which is 26 bits in total. The values ​​of the Control ID, 10 to 14, are reserved values.

[0066] In this application, the A-Control field can also be used to carry first indication information. In Figure 2e, when the Control ID value is set to any value between 10 and 14 (e.g., 14), the Control Information subfield of the A-Control field can be used to indicate the Buffered Time Status, occupying a total of 18 bits, as shown in Figure 2f. The Buffered Time High field represents the traffic latency requirement or expiration time cached by the AP and identified by the ACI High subfield for the Access Class (AC), and its unit can be a Scaling Factor byte. The Buffered Time All field represents the traffic latency requirement or expiration time cached by the AP and identified by the ACI Bitmap subfield for all Access Classes (ACs), and its unit can also be a Scaling Factor byte.

[0067] Alternatively, in this application, the second indication information can also be carried through the A-Control field. In Figure 2e, when the Control ID value is set to any value from 10 to 14 (for example, set to 13, different from the value 14 corresponding to Buffered Time Status), the Control Information subfield of the A-Control field can be used to indicate the Bandwidth Expansion. Its frame structure can be shown in Figure 2g, including Bandwidth Expansion Control and / or Expansion Range, which can be exemplarily designed as 4 bits. That is, it can be understood that when the first and second indication information are carried through the A-Control field, since the A-Control field is only 30 bits long in total, of which 4 bits (Control ID) + 18 bits (Buffered Time Status) are used to carry the first indication information as mentioned above, totaling 22 bits, then 8 bits are left to carry the second indication information. Among them, the Control ID corresponding to the second indication information occupies 4 bits, so the remaining 4 bits indicate the second indication information.

[0068] In Figure 2g, when the Bandwidth Expansion Control indicator is a first value such as 0, it means that the current device does not support (or does not enable) bandwidth expansion operation; when the Bandwidth Expansion Control indicator is a second value such as 1, it means that the current device supports (or enables) bandwidth expansion operation. In this case, an Expansion Range field may exist to indicate the range of bandwidth expansion that the device can perform, including but not limited to the following indication methods: different bits correspond to different bandwidth expansion ranges. For example, in the three bits B1 to B3, B1 indicates support for bandwidth expansion from 20MHz to 40MHz, B2 indicates support for bandwidth expansion from 80MHz to 160MHz, and B3 indicates support for bandwidth expansion from 160MHz to 320MHz; or, different values ​​indicated by N bits correspond to different bandwidth expansion ranges. For example, the three bits B1 to B3 can indicate 8 values, each corresponding to a bandwidth expansion value (e.g., 20MHz). For example, when Expansion... A Range indicator of 111 (i.e., equal to the 8th value) represents support for a bandwidth extension operation of 8 * 20 MHz = 160 MHz. Therefore, the specific indication method for the bandwidth extension range is not limited in this application.

[0069] When using a Multi-STA BlockAck frame to carry service expiration time information or service delay requirement information from the first indication information;

[0070] When the second frame is a Multi-STA BlockAck frame, the Multi-STA BlockAck frame includes one or more Per AID TID Info fields, which carry first indication information and / or second indication information. For example, please refer to Figure 2h, which shows the structure of an existing Multi-STA BlockAck frame. The first indication information can be placed in the Block Ack Bitmap field, and its specific format and meaning are similar to the design of Option 1b and Option 2b described above, and will not be repeated here.

[0071] In some implementations, for a unicast Multi-STA BlockAck frame, the Receive Address (RA) of the Multi-STA BlockAck frame indicates the unicast receiver (such as the first site). The first indication information and / or the second indication information can be indicated in the AID11 field of the AID TID Info subfield, as shown in Figure 2i, which is the frame structure of the AID TID Info subfield. When the first indication information and / or the second indication information are carried in the AID11 field, their specific format and meaning are consistent with the design described above in other fields, and will not be repeated here.

[0072] 203. The first site determines the sharing mode of the first TXOP based on the second frame, and determines the target site in at least one second site;

[0073] After receiving a second frame sent by at least one second station, the first station determines the sharing mode of the first TXOP based on the second frame. The sharing mode includes, but is not limited to: immediately enabling TXOP sharing, enabling TXOP sharing after the first station completes its transmission, and whether bandwidth expansion operations are allowed during the TXOP sharing period. In practice, other sharing modes can also be set, but this application does not limit them.

[0074] The first site further determines a target site among at least one second site based on the second frame to share the first TXOP. Specifically, the method for determining the target site includes: determining the resource demand level of each second site based on the second frame sent by each second site; when the maximum resource demand level among the resource demand levels of each second site is greater than the resource demand level of the first site, the site corresponding to the maximum resource demand level is determined as the target site. For example, by comparing the service type, cache size, priority, and expiration time information (or latency requirement information) of the first site with those of at least one second site, devices with high priority, low latency requirements (or service about to expire), and large cache are selected as the target sites to be shared. In practical applications, weights can be set for each dimension, and the total weight of each site can be calculated to obtain the resource demand level of each site, thereby determining the target site.

[0075] It should be noted that there are multiple ways to determine the target site in this application. For example, it can be randomly selected from at least one second site, or the second site closest to the first site, or the second site with the largest amount of cached data, or the second site with low-latency services to be transmitted can be used as the target site. Therefore, this application does not limit the method of determining the target site.

[0076] In addition, if the first site has the greatest resource demand, or if, after comprehensive evaluation, the device with the above-mentioned business characteristics is the first site itself, then the first site will start using the current TXOP to communicate with its associated STAs after receiving the SIFS time of the second frame.

[0077] 204. The first station sends the third frame to the target station;

[0078] After receiving the SIFS time of the second frame, the first station sends a third frame to the target station. The third frame also includes a sixth indication information and / or a seventh indication information. The sixth indication information is used to indicate the service type and / or service priority that are allowed to be transmitted within the first TXOP. The seventh indication information is used to indicate whether bandwidth expansion operation is allowed within the first TXOP. The eighth indication information is used to indicate the sharing mode of the first TXOP. The sharing mode of the first TXOP includes, but is not limited to, at least one of the following modes: sharing the first TXOP after sending the third frame, sharing the first TXOP after the first station has completed the transmission, whether the first station participates in the transmission within the first TXOP, and / or, a multi-AP cooperative transmission mode that is allowed within the first TXOP.

[0079] For example, this third frame is described as an MU-RTS TXS Trigger frame. In actual scenarios, the third frame can be any other frame. As shown in Figure 2a, the MU-RTS TXS Trigger frame includes a Common Info field and a User Info List field, where the User Info List field contains one or more User Info fields. The receiver address (i.e., the RA field) of this MU-RTS TXS Trigger frame is set to the MAC address of the target site; or, the receiver address (i.e., the RA field) is set to the broadcast MAC address, and the AID12 field of the User Info field of the MU-RTS TXS Trigger frame indicates the identification information of the target site, such as the APID of the target site.

[0080] Additionally, N reserved bits (e.g., 3 or 4 bits) in the Common Info field and / or Special User Info field and / or User Info field of the MU-RTS TXS Trigger frame can be defined as the Traffic Constraint field, used to indicate the sixth indication information, i.e., the service type / TID and other service-related information allowed to be transmitted within the first TXOP. Specifically, this includes the following two methods: Method 1: The Traffic Constraint field indicates the service category (e.g., access type AC: AC_VO, AC_VI, AC_BE, AC_BK) or service identifier (Traffic Identifier, TID), such as TID = 0~7, etc., that can only be transmitted within the shared first TXOP time. This can also be understood as services other than those indicated by the Traffic Constraint field not being allowed to be transmitted within the shared TXOP time. Method 2: The Traffic Constraint field indicates that only service categories higher than or equal to the indicated service category can be transmitted within the shared first TXOP time. When the field is indicated as AC_VI, AC_VI and AC_VO can be transmitted within the shared TXOP time. For example, when the Traffic Constraint field is indicated as TID=2, services corresponding to TID=0,1,2 can be transmitted within the shared TXOP time.

[0081] Optionally, N reserved bits (e.g., 1 or 4 bits) in the Common Info field and / or Special User Info field and / or User Info field of the MU-RTS TXS Trigger frame can be defined as the Bandwidth Expansion field to indicate the seventh indication information, namely whether bandwidth expansion operation is allowed during the shared TXOP time, and / or the range of allowed bandwidth expansion operation.

[0082] 205. The target station sends the fourth frame to the first station;

[0083] Optionally, the target station sends a fourth frame to the first station to indicate acceptance of the first TXOP shared by the first station. In this embodiment, the fourth frame can be a CTS frame, meaning that if the target station accepts the allocation and indication from the first station, it can reply via the CTS frame; otherwise, if it does not accept, the target station does not send the CTS frame. The specific format of the CTS frame can be found in existing standards and will not be elaborated here.

[0084] 206. The target station communicates with its associated station within the first TXOP duration based on the third frame.

[0085] During the first shared TXOP duration, the target site communicates with its associated STA(s) according to the instructions of the third frame, including the following operations: the type of service communicated between the target site and its associated STA(s) is restricted by the instructions of the third frame; the target site may perform bandwidth expansion operations according to the instructions of the third frame, or may not perform them according to the instructions of the third frame; if the third frame does not indicate bandwidth expansion operations, the target site may decide whether to perform bandwidth expansion operations within the first shared TXOP duration and the scope of bandwidth expansion.

[0086] Specifically, if the third frame indicates a bandwidth expansion operation via the Bandwidth Expansion field, the target site needs to perform a TXOP expansion operation within the first shared TXOP time as instructed by the third frame. The extent of the bandwidth expansion is indicated by the Bandwidth Expansion field. The bandwidth expansion operation includes the following two methods:

[0087] Method 1: Before transmitting within the shared bandwidth (if not explicitly indicated, the default is the working bandwidth of the first site), the target site will perform CCA detection on a channel outside the shared bandwidth to check if the channel is idle. If the idle time exceeds the first preset time, such as the PIFS time or DIFS time or other times greater than or equal to PIFS, the target site will use the shared bandwidth and the channel bandwidth detected by CCA for transmission.

[0088] Method 2: Before transmitting within the shared bandwidth (if not explicitly specified, the default is the working bandwidth of the first site), the target site will perform a backoff on a channel outside the shared bandwidth. If the channel remains idle or the idle time exceeds the second preset time during the backoff execution, the target site will use the shared bandwidth and the idle channel bandwidth detected by the backoff for transmission.

[0089] It is important to note that after the target station completes the transmission with its associated STA(s), if there is still time remaining in the first shared TXOP, it can send a fifth frame to the first station to indicate that the remaining time of the shared TXOP is returned to the first station, so that the first station can continue to use the remaining time until the acquired TXOP expires.

[0090] In this embodiment, after acquiring the first TXOP, the first station sends a first frame to at least one surrounding second station. The first frame indicates the allowed operating modes and / or service priority information for subsequent first TXOP sharing, whether bandwidth expansion operations are allowed, etc. At least one second station replies with a second frame to the first station according to the requirements of the first frame. Based on the content of the second frame, the first station determines the first TXOP sharing strategy (including the transmission order, transmission mode, and parameters, etc.) and sends a third frame to the target station for TXOP sharing. After accepting the shared first TXOP, the target station uses the shared first TXOP according to the instructions in the third frame. After completing the transmission within the shared first TXOP time, the remaining time of the shared first TXOP is used by other stations, such as the first station or other second stations, according to the instructions in the fifth frame.

[0091] By instructing the bandwidth expansion operation when an AP shares a TXOP, the AP receiving the TXOP can use more transmission bandwidth within a given transmission time, improving the transmission rate and thus reducing the latency of data transmission in the case of large data volumes. In addition, by collecting information such as the service priorities of surrounding APs, after obtaining a TXOP, the AP preparing to share the TXOP can flexibly adjust the order of TXOP usage based on the service priorities, thus achieving priority guarantee of low-latency service transmission across BSSs.

[0092] For scenario B, where resources are shared across multiple sites, please refer to Figure 3, which is a flowchart of another possible resource sharing method, including but not limited to at least one of the following steps:

[0093] 301. The first station sends a first frame to at least one second station;

[0094] In this embodiment, step 301 is similar to step 201 in the embodiment shown in Figure 2. The main difference is that in addition to the first request information and / or second request information included in the first frame of step 201, the first frame in this embodiment may also include third request information, fourth request information and / or fifth request information. The third request information is used to request the receiver to provide feedback on the supported multi-AP cooperative transmission mode information. The fourth request information is used to request the receiver to provide feedback on the identification information of the non-AP sites participating in the multi-AP cooperative transmission. The fifth request information is used to request the receiver to provide feedback on whether it participates in the first multi-AP cooperative transmission mode.

[0095] For example, when the first frame is a BSRP Trigger frame, the first frame carries a third request message requesting the receiver to provide feedback on the supported multi-AP cooperative transmission mode information. The multi-AP cooperative transmission mode includes, but is not limited to, at least one of the following cooperative modes: Coordinated Beamforming (Co-BF), Coordinated Spatial Reuse (Co-SR), Coordinated Restricted Target Wake Time (Co-RTWT), Coordinated Orthogonal Frequency-Division Multiple Access (Co-OFDMA), etc. The specific indication method for the third request message is as follows: for example, any (EHT / UHR) Reserved field in the EHT variant Common Info field and / or UHR variant Common Info field of Figure 2a is defined as "Multi-AP Mode Requested". When the Multi-AP Mode Requested is set to a third value such as 1, it means that the receiver needs to provide feedback on the supported multi-AP cooperative transmission information; when the Multi-AP Mode... When Requested is set to the fourth value, such as 0, it means that the receiver does not need to provide feedback on the supported multi-AP cooperative transmission information.

[0096] For example, when the first frame is a BSRP Trigger frame, the first frame carries a fourth request information to request the receiver to provide the identification information of the non-AP sites participating in the multi-AP cooperative transmission, that is, to request the acquisition of at least one second site and the STA(s) associated with the first site. The specific indication method of the fourth request information is as follows: the receiver address (i.e., RA field) of the first frame (such as a BSRP Trigger frame) is set to the broadcast MAC address, and then the User Info List of the BSRP Trigger frame contains multiple User Info fields, some of which have AID12 field indicating the APID of the AP (e.g., the second AP), and others have AID12 field indicating the high / low 12 bits of the Association ID (AID) of the non-AP STA.

[0097] In this embodiment, the first multi-AP cooperative transmission mode includes, but is not limited to, any of the following modes: Co-BF, Co-SR, Co-RTWT, or Co-TDMA. For example, the first multi-AP cooperative transmission mode is Co-TDMA.

[0098] 302. At least one second station sends a second frame to the first station;

[0099] In this embodiment, step 302 is similar to step 202 in the embodiment shown in FIG2. The main difference is that, corresponding to the first frame in step 301, the second frame in this embodiment may include, in addition to the first indication information and / or the second indication information in the embodiment shown in FIG2, a third indication information, a fourth indication information, and / or a fifth indication information. The third indication information is used to indicate the supported multi-AP cooperative transmission mode information, the fourth indication information is used to indicate the identification information of the non-AP site participating in the multi-AP cooperative transmission, and the fifth indication information is used to indicate whether it participates in the first multi-AP cooperative transmission mode.

[0100] Optionally, the third indication information is carried in the A-Control field or the per AID TID info field in the second frame. Specifically, the A-Control field includes at least one Control subfield. When the Control ID value in the Control subfield is the eighth value, the Control Information field in the Control subfield is used to indicate the third indication information. For example, when the Control ID value is set to any one of 10 to 14 (e.g., set to 12), the Control Information subfield of the A-Control field is used to indicate the Multi-AP Mode in this application, as shown in Figure 3a. In Figure 3a, the values ​​of each field are 0 or 1 as an example. In actual applications, other values ​​can also be used. In other words, Co-BF set to 1 indicates that the sender of the second frame carrying the Multi-AP Mode field supports the Co-BF multi-AP cooperative transmission mode, and vice versa; Co-SR set to 1 indicates that the sender of the second frame carrying the Multi-AP Mode field supports the Co-SR multi-AP cooperative transmission mode, and vice versa; Co-OFDMA set to 1 indicates that the sender of the second frame carrying the Multi-AP Mode field supports the Co-OFDMA multi-AP cooperative transmission mode, and vice versa; Co-RTWT set to 1 indicates that the sender of the second frame carrying the Multi-AP Mode field supports the Co-RTWT multi-AP cooperative transmission mode, and vice versa.

[0101] Optionally, when the second frame is a Multi-STA BlockAck frame, the second frame includes one or more Per AID TID Info fields. The third indication information shown in Figure 3a can be carried in the AID TID Info or Block Ack Bitmap field indication. The specific implementation method is shown in the relevant design of step 202 in Figure 2, which will not be elaborated here.

[0102] Optionally, for the fifth request message, at least one second station can reply with a fifth indication message after receiving the first frame. Specifically, if it wants to participate in the first multi-AP cooperative transmission mode, the fifth indication message indicates participation; if it does not want to participate in the first multi-AP cooperative transmission mode, the fifth indication message indicates non-participation. Optionally, it may not reply with the first frame. In this case, if the first station does not receive the second frame sent by the second station within a preset time period, it is assumed that the second station does not participate in the first multi-AP cooperative transmission mode.

[0103] It should be noted that if the second station does not participate in the first multi-AP cooperative transmission mode, or does not participate in the sharing of the first station's first TXOP, the second station can immediately enter the power-saving mode after replying to the second frame, or switch from the current first channel to the non-primary channel access (NPCA) primary channel. Power-saving modes include sleep mode. Optionally, it can also skip sending the second frame and directly enter power-saving mode, or switch from the current first channel to the NPCA primary channel.

[0104] 303. The first site determines the sharing mode of the first TXOP based on the second frame, and determines the target site in at least one second site;

[0105] In this embodiment, step 303 is similar to step 203 in the embodiment shown in Figure 2, and will not be described again here.

[0106] 304. The first station sends the third frame to the target station;

[0107] In this embodiment, step 304 is similar to step 204 shown in Figure 2. The main difference is that the third frame in step 304, in addition to carrying the sixth and / or seventh indication information contained in the third frame in step 204, also includes eighth indication information. The eighth indication information is used to indicate the sharing mode of the first transmission resource. The sharing mode of the first transmission resource includes, but is not limited to, at least one of the following modes: sharing the first transmission resource after sending the third frame, sharing the first transmission resource after the first station has completed the transmission, whether the first station participates in the transmission within the first transmission resource, and / or, the multi-AP cooperative transmission mode allowed within the first transmission resource.

[0108] For example, this third frame is described as the MU-RTS TXS Trigger frame. In actual scenarios, the third frame can also be other frames. As shown in Figure 2a, the MU-RTS TXS Trigger frame includes a Common Info field and a User Info List field, where the User Info List field contains one or more User Info fields. In this application, the L reserved bits in the Common Info field and / or Special User Info field and / or User Info field of the MU-RTS TXS Trigger frame can be defined as the Sharing AP Priority Transmission field. The value of L can be 1 or other values, used to indicate whether the TXOP holder (i.e., the first site) that initiated the TXOP sharing during the sharing time also uses the shared first TXOP for priority transmission. For example, setting the Sharing AP Priority Transmission field to 0 means that the first site will not use its shared first TXOP for priority transmission. Setting the field to 1 indicates that the first station will use its shared TXOP for priority transmission. The specific priority transmission method is as follows: Condition a. When the target station is an AP, within the first TXOP, the inter-frame interval for frame interaction between the target station and its associated STA is a preset time length. For example, when the target AP interacts with its associated STA(s) for frames, the inter-frame interval needs to be set to PIFS or DIFS, which is longer than PIFS; Action b. If the buffered service or the service to be transmitted by the first station meets the first condition, it will immediately perform a transmission operation when the channel is idle for SIFS or PIFS time. Within the first TXOP, the target site seizes transmission opportunities. For example, if the target site has low-latency services to transmit, it will immediately transmit during the SIFS or PIFS time when the channel is detected to be idle. It should be noted that if the inter-frame interval in condition a is set to PIFS, then the transmission operation will be performed immediately during the SIFS time when the channel is detected to be idle in action b; if the inter-frame interval in condition a is set to DIFS, then the transmission operation will be performed immediately during the SIFS or PIFS time when the channel is detected to be idle in action b. Action c. The target site detects the channel through CCA within the first TXOP time. If the detection is idle, it can transmit according to condition a. If the detection is busy, it waits and continues to perform CCA detection.

[0109] In this embodiment, z reserved bits or existing bits (e.g., 28 bits, which can be implemented by defining a new Special User Info field or by using two User Info fields; the specific method will not be elaborated here) in the Common Info field and / or Special User Info field and / or User Info field of the MU-RTS TXS Trigger frame can also be defined as a Multi-AP Transmission field, used to indicate the multi-AP cooperative transmission mode and objects allowed during the shared TXOP time. The specific implementation method is as follows: As shown in Figure 3b, a possible frame structure diagram is shown, where the AID12 field and Peer AID12 field (or AID11 and Peer AID11 fields, 11 bits of AID, which is not limited here) are used to indicate the APID of the two APs participating in the multi-AP cooperative transmission; Co-BF, Co-SR, Co-OFDMA, and Co-RTWT are used to indicate the multi-AP cooperative transmission mode to be used by the AP indicated by the AID12 field and Peer AID12 field. An example of field settings is as follows:

[0110] Example 1: AID12 is set to AP 1, such as the APID of the first site; Peer AID12 is set to AP 2, such as the APID of the target site; Co-BF is set to 1; Co-SR, Co-OFDMA and Co-RTWT are all set to 0; This means that during the TXOP time shared by AP 1, AP 1 and AP 2 will perform Co-BF cooperative beamforming transmission operations together.

[0111] Example 2: AID12 is set to the APID of AP 2; Peer AID12 is set to the APID of AP 3; Co-SR is set to 1; Co-BF, Co-OFDMA and Co-RTWT are all set to 0; This means that during the TXOP time shared by the first site, AP 2 and AP 3 will perform Co-SR cooperative spatial multiplexing transmission operations together.

[0112] Furthermore, this third frame can indicate only one AP (e.g., AP 3) via its RA address or AID12, without needing to indicate another AP participating in the multi-AP cooperative transmission via Peer AID12. This allows AP 1 to be associated with another AP through a default cooperative set. In other words, if AP 3 establishes a multi-AP cooperative set with AP 2 through the multi-AP cooperative transmission set establishment process, then AP 1 only needs to indicate AP 3's APID via AID12 as shown in Figure 3b in the third frame it sends. This enables AP 1 to share a portion of its acquired TXOP time with both AP 3 and AP 2 for use, without needing to specifically indicate AP 2's APID or MAC address.

[0113] In this embodiment, the example of the third frame instructing the first station and the target station to perform multi-AP cooperative transmission within the first TXOP shared by the first station is shown in Figure 3c. The sharing station AP 1 and the shared station AP 2 use the TXOP time shared by AP 1 to perform multi-AP cooperative transmission in Co-SR and / or Co-BF modes. Based on Figure 3c, AID12 shown in Figure 3b is set to the APID of AP 1, Peer AID12 is set to the APID of AP 2, and Co-BF and / or Co-SR are set to 1, with the remaining fields set to 0. Then, after AP 2 replies with the fourth frame SIFS time, AP 1 or AP 2 will send a multi-AP trigger frame to trigger AP 1 and AP 2 to jointly perform Co-BF and / or Co-SR transmission modes.

[0114] Optionally, in this embodiment, the third frame can also be sent from the first station to at least one of the aforementioned second stations. That is, the third frame can be sent only to the target station, or it can be sent to all at least one of the second stations. When the recipient address of the third frame is one of the at least one second station, the third frame can also include ninth indication information. The ninth indication information is used to indicate the target station. That is, the function of the third frame includes: re-indicating or confirming the information in the first frame and / or the second frame, and selecting the target station as the object for TXOP sharing after the first station completes its own BSS transmission.

[0115] From the perspective of at least one second station, if the second frame sent by second station A to first station indicates participation in the first multi-AP cooperative transmission mode or the first TXOP sharing, second station A can maintain a receiving state, such as an active state, to receive the third frame sent by first station. When the ninth indication information in the third frame does not include the identification information of second station A or second station A does not receive the third frame, that is, it indicates or defaults that second station A will not participate in (or be scheduled) the first multi-AP cooperative transmission mode or AP 1 TXOP Sharing initiated by first station, second station A can switch to power-saving mode, or switch from the current first channel to the NPCA main channel.

[0116] Optionally, the third frame may also include tenth indication information, which indicates the start time of the first TXOP sharing or the start time of the first multi-AP cooperative mode. If the second frame sent by the second station A to the first station indicates participation in the first multi-AP cooperative transmission mode or the first TXOP sharing, the second station A may maintain a receiving state, such as an active state, to receive the third frame sent by the first station. When the ninth indication information in the third frame includes the identification information of the second station A or when the second station A receives the third frame, it indicates or defaults to the second station A participating in the first multi-AP cooperative transmission mode or AP 1 TXOP Sharing initiated by the first station. The second station A may switch to power-saving mode or switch from the current first channel to the NPCA main channel before the time indicated by the tenth indication information is reached. When the time indicated by the tenth indication information is reached, the second station A switches back to the active state or the wake-up state, or switches back from the NPCA main channel to the first channel.

[0117] 305. The target station sends the fourth frame to the first station;

[0118] In this embodiment, step 305 is similar to step 205 in the embodiment shown in Figure 2, and will not be described again here.

[0119] 306. The first station and / or the target station communicate with their respective associated stations within the first TXOP duration based on the third frame.

[0120] In this embodiment, step 306 is similar to step 206 in the embodiment shown in Figure 2. The difference is that the first site, i.e. the first TXOP sharing site, can also use the first TXOP to communicate with its associated sites, thus realizing resource sharing for use by multiple sites.

[0121] Furthermore, based on the embodiment shown in Figure 2a, this embodiment enables two APs to perform multi-AP collaborative transmission during the shared TXOP time by indicating the allowed working modes. This shared time also forms the basis for multi-AP collaboration and provides the AP that initiates the TXOP sharing with more flexible transmission opportunities, enabling timely transmission of low-latency services.

[0122] It should be noted that the fields defined in the various embodiments of this application, such as the Bandwidth Expansion field, Traffic Info Requested field, and Multi-AP Transmission field, are named in an exemplary manner to facilitate understanding and distinction. In actual applications, they can also be named in other ways, and this application does not limit them in any specific way.

[0123] Furthermore, during resource sharing, there may be situations where the recipient does not fully utilize the shared resources and needs to return the remaining resources. Therefore, this application embodiment also provides a new return mechanism, which can be combined with existing resource sharing methods or with the resource sharing methods shown in Figures 2 and 3 above. The following description will use an existing resource sharing method as an example. It should be noted that other resource sharing scenarios that adopt a return mechanism similar to this application can be considered within the scope of protection of this application. Please refer to Figure 4, which is a flowchart of another possible resource sharing method, including but not limited to at least one of the following steps:

[0124] 401. The first site sends a resource sharing frame to the target site;

[0125] 402. The first station receives the response frame sent by the target station;

[0126] 403. The target site communicates with its associated site during the first TXOP duration;

[0127] The first site, acting as a resource sharer, sends a resource sharing frame to the target site, indicating that it will share the first TXOP with the target site. In response to this resource sharing frame, the target site sends a response frame to the first site, indicating whether it accepts the shared first TXOP. Optionally, if the target site refuses to accept the shared first TXOP, it may default not to sending this response frame.

[0128] It should be noted that steps 401 and 402 are used for the first site to share the first TXOP with the target site. The specific sharing method can be the resource sharing method shown in the embodiment of Figure 2 or Figure 3 in this application, or other resource sharing methods in the prior art. This application does not limit the specific method.

[0129] After receiving the first TXOP, the target site communicates with its associated site STA(s) within the duration of the first TXOP.

[0130] 404. The target station sends the fifth frame to the first station;

[0131] After the target station completes the transmission with its associated STA(s) within the first TXOP shared by the first station, if there is still time remaining in the shared first TXOP, it can send a fifth frame to the first station. The fifth frame indicates the return rules for the remaining time of the shared first TXOP. The rules indicate the service type and / or service priority that are allowed to be transmitted within the remaining time of the returned first TXOP. The indication of the service type or service priority that is allowed to be transmitted is not limited to any of the following: direct indication, or indication of the lowest category of service type or lowest service priority that is allowed to be transmitted.

[0132] Specifically, in this embodiment, the fifth frame can be defined as a TXOP Return frame or other named frames. Its frame structure diagram is exemplarily shown in Figure 4a. In this case, TXOP Return Mode set to 0 represents a fully returned frame, meaning the device sending the TXOP Return frame will not transmit during the remaining time of the current TXOP; in this case, the Returned Traffic Category field is reserved. TXOP Return Mode set to 1 represents a partially returned frame, meaning the device sending the TXOP Return frame may continue transmitting during the remaining time of the current TXOP. In this case, the Returned Traffic Category field indicates the service type / TID and other service-related information allowed to be transmitted within the return time. Specifically, it can include the following two indication methods:

[0133] Direct Instructions: Returned Traffic Category indicates the type of service that the TXOP holder and / or TXOP Responder can only transmit during the returned TXOP period. Examples include Access Category (AC): Voice (AC-VO), Video (AC-VI), Best-Effort (AC-BE), Background (AC-BK), or Traffic Identifier (TID), such as TID = 0-7. Services other than those indicated by the Returned Traffic Category are not allowed to be transmitted during the shared TXOP period.

[0134] The Returned Traffic Category indicates the lowest allowed service category or priority for transmission: During the returned TXOP period, the TXOP holder and / or TXOP Responder can only transmit services of a category higher than or equal to the indicated category. For example, if the Returned Traffic Category is AC_VI, AC_VI and AC_VO can be transmitted during the returned TXOP period; if the Returned Traffic Category is TID=2, services corresponding to TID=0,1,2 can be transmitted during the returned TXOP period.

[0135] 405. The first station sends the sixth frame to the target station.

[0136] After receiving the fifth frame, if the first station has a service with a higher priority than the service indicated by the fifth frame, it sends a sixth frame to the second station. The sixth frame is used to indicate that there is a service that meets the return rules, such as the first station having a high-priority service that needs to start transmission immediately.

[0137] Optionally, the first site may not need to send the sixth frame. After the target site completes sending the fifth frame, the first site and the target site will share the returned TXOP time by default until the shared TXOP duration expires.

[0138] Specifically, after the first station receives the fifth frame, if the TXOP Return Mode of the fifth frame is set to 1, and if the first station itself has a service with a higher priority than the service indicated by the fifth frame, then the first station can perform the following two actions:

[0139] Behavior 1: The first station does not send the sixth frame. After the target station has sent the fifth frame SIFS time, the first station and the target station share (e.g., using a contention method) the returned first TXOP time until the shared first TXOP duration expires.

[0140] Action 2: The first site sends a sixth frame to the target site, where the seventh frame indicates that the first site has high-priority service and needs to immediately begin transmitting high-priority service (here, high-priority service refers to service with a priority higher than or equal to that indicated by the Returned Traffic Category in the fifth frame); the usage rules of the remaining resources of the first TXOP can be exemplarily as follows: First site usage rule: Immediately transmit service of any type and priority after sending the sixth frame within SIFS time; Target site usage rule: After receiving the sixth frame, do not transmit any type and priority service, and wait for further signaling instructions from the first site. Optionally, the usage rules of the remaining resources of the first TXOP can also be set to other rules based on specific scenario needs, which are not limited in this application.

[0141] After the first station receives the remaining resources of the first TXOP returned, it will transmit high-priority services within those remaining resources.

[0142] Optionally, if the first station has remaining time after completing the high-priority service transmission, it can send a seventh frame to the target station. This seventh frame indicates that the first station has completed the high-priority service transmission and the target station can continue to use the remaining time. The target station, following the instructions of the seventh frame, continues to use the remaining time, for example, to continue transmitting its own low-priority services. These low-priority services refer to those with a priority lower than the service indicated by the Returned Traffic Category in the fifth frame. Based on the remaining time, the target station continues transmitting until all its cached services are completed or the shared (or returned) TXOP time expires, whichever expires first. It should be noted that if the first station's behavior after receiving the fifth frame is as described in Action 1, i.e., it does not send the sixth frame but shares the returned remaining resources with the target station, then the first station does not need to send the seventh frame.

[0143] Optionally, if there is remaining time after the first station has completed transmitting the high-priority service, the remaining time can be shared with other stations, including the target station. The resource sharing method can be as shown in Figure 2 or Figure 3, or other resource sharing methods of existing technology. The specific method is not limited here.

[0144] In this embodiment, considering that the AP initiating the TXOP sharing and the AP receiving the TXOP have different service priorities, the AP receiving the TXOP should be allowed to instruct the AP initiating the TXOP sharing to return some high-priority service transmission rights. That is: 1) If the AP initiating the TXOP sharing has a service with a higher priority (e.g., low latency) than the AP receiving the TXOP, the AP initiating the TXOP sharing can use the returned remaining TXOP to transmit that high-priority (e.g., low latency) service; 2) If the AP initiating the TXOP sharing does not have a service with a higher priority than the AP receiving the TXOP, the AP receiving the TXOP will still use the remaining TXOP to transmit its own service. In other words, if there is remaining time after the AP receiving the TXOP has used it, the rule for using this time is that whichever service has a higher priority (i.e., the sharer and the recipient) uses it. In this embodiment, after the target site completes transmission within the first shared TXOP time, the remaining time of the first shared TXOP is continued to be used by the first site and / or the target site and / or the third site according to the indication information in the fifth frame, improving resource utilization efficiency. At the same time, prioritizing TXOP returns allows high-priority services to utilize more transmission opportunities, thereby ensuring the transmission of low-latency services.

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

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

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

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

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

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

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

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

[0153] 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.

[0154] Those skilled in the art will clearly 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.

[0155] 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.

[0156] 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.

[0157] 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.

[0158] 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.

[0159] 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 resource sharing method, applied to a first site, characterized in that, include: Receive a second frame sent by at least one second station; Based on the second frame, a third frame is sent to the target station among the at least one second station. The third frame is used to indicate a first transmission resource to the target station, which is a transmission resource shared by the first station to the target station.

2. The method according to claim 1, characterized in that, Before receiving the second frame sent by at least one second station, the method further includes: A first frame is sent to the at least one second station, the first frame being used to request station information, the station information being used to determine the target station, and a second frame being used to respond to the first frame.

3. The method according to claim 2, characterized in that, The first frame includes at least one first field, and each first field corresponds to each of the second stations.

4. The method according to claim 2 or 3, characterized in that, The receiver address RA of the first frame is the broadcast MAC address. The first frame includes a first receiver indication and / or a second receiver indication. The first receiver indication is used to indicate the identification information of the access point (AP) in the second site, and the second receiver indication is used to indicate the identification information of the non-access point (non-AP) site in the second site.

5. The method according to claim 4, characterized in that, The first frame is a BSRP Trigger frame. The first frame includes a User Info List field, which includes at least one User Info subfield. Some or all of the User Info subfields in the User Info List field include the first receiver indication, and / or some or all of the User Info subfields in the User Info List field include the second receiver indication.

6. The method according to any one of claims 2 to 5, characterized in that, The first frame includes at least one of the following: a first request, a second request, a third request, a fourth request, and / or a fifth request, wherein... The first request information is used to request service status information; the second request information is used to request whether the capability of bandwidth expansion operation is supported; the third request information is used to request the receiver to provide feedback on the supported multi-AP cooperative transmission mode information; the fourth request information is used to request the receiver to provide feedback on the identification information of non-AP sites participating in the multi-AP cooperative transmission; and the fifth request information is used to request the receiver to provide feedback on whether it participates in the first multi-AP cooperative transmission mode.

7. The method according to claim 6, characterized in that, The indication method for the first request information includes: direct indication or indirect indication.

8. The method according to claim 6 or 7, characterized in that, The business status information includes, but is not limited to, at least one of the following: business type, business volume, business priority, business expiration time, or business delay requirement.

9. The method according to any one of claims 6 to 8, characterized in that, The first frame includes a bandwidth expansion field, which is used to indicate the second request information. Each value of the bandwidth expansion field corresponds to different information requested or indicated by the second request information.

10. The method according to claim 9, characterized in that, The bandwidth extension field can take two values: a first value and a second value. When the value of the bandwidth expansion field is the first value, the information requested or indicated by the second request information includes: whether the receiver can provide feedback on whether it supports bandwidth expansion operation and / or the bandwidth range that can be expanded, and / or whether the sharer allows bandwidth expansion operation within the first transmission resource. or, When the value of the bandwidth expansion field is the second value, the information requested or indicated by the second request information includes: the receiver does not provide feedback on whether it supports bandwidth expansion operations, and / or, the sharer within the first transmission resource is not allowed to perform bandwidth expansion operations.

11. The method according to any one of claims 6 to 10, characterized in that, The first frame includes a Multi-AP Mode Requested field, which indicates whether the receiver has responded with the third request information.

12. The method according to any one of claims 6 to 11, characterized in that, The first frame includes a non-AP site request field for participating in multi-AP collaboration, which is used to indicate whether the receiver should respond to the fourth request information.

13. The method according to any one of claims 6 to 12, characterized in that, The second frame includes, but is not limited to, at least one of the following: first indication information, second indication information, third indication information, fourth indication information, and / or fifth indication information, wherein, The first indication information is used to indicate the service status information, the second indication information is used to indicate whether the bandwidth expansion operation is supported, the third indication information is used to indicate the supported multi-AP cooperative transmission mode information, the fourth indication information is used to indicate the identification information of the non-AP site participating in the multi-AP cooperative transmission, and the fifth indication information is used to indicate whether to participate in the first multi-AP cooperative transmission mode.

14. The method according to claim 13, characterized in that, The second frame is either a QoS Null frame or a Multi-STA BlockAck frame.

15. The method according to claim 13 or 14, characterized in that, The first indication information is carried in the QoS Control field, HT Control field, A-Control field, or per AID TID info field in the second frame.

16. The method according to claim 15, characterized in that, The QoS Control field in the second frame includes a Buffer State subfield, which is used to indicate the service expiration time information or service delay requirement information in the first indication information.

17. The method according to claim 16, characterized in that, The Buffer State subfield includes a Buffer Time Indicated bit. When the value of the Buffer Time Indicated bit is the third value, the Buffer State subfield indicates the expiration time information of the cached service / pending transmission service, or the latency requirement information of the cached service / pending transmission service; or, The Buffer State subfield also includes a cache time field. When the value of the Buffer Time Indicated bit is the fourth value, the cache time field is used to indicate the latency requirement information or expiration time information corresponding to a specific cache service.

18. The method according to claim 15, characterized in that, The HT Control field in the second frame includes a first subfield and a second subfield. When the first subfield is a specific value, the second subfield is an A-Control subfield. The A-Control subfield includes at least one Control field. When the Control ID value in the Control field is the fifth value, the Control Information field in the Control field is used to indicate the cache status report in the first indication information.

19. The method according to claim 15, characterized in that, The A-Control field in the second frame includes at least one Control subfield. When the Control ID value in the Control subfield is the sixth value, the Control Information field in the Control subfield is used to indicate the cache time status information in the first indication information.

20. The method according to claim 13 or 14, characterized in that, The second indication information is carried in the HT Control field or the A-Control field in the second frame.

21. The method according to claim 19, characterized in that, The A-Control field in the second frame includes at least one Control subfield. When the Control ID value in the Control subfield is the seventh value, the Control Information field in the Control subfield includes the bandwidth extension control and / or bandwidth extension range in the second indication information.

22. The method according to claim 20, characterized in that, When the value of the bandwidth extension control is the eighth value, the Control Information field of the Control subfield contains a field used to indicate the bandwidth extension range.

23. The method according to claim 21, characterized in that, The indication method of the bandwidth extension range field includes, but is not limited to, any of the following: different bandwidth extension ranges are indicated by different bits, or different bandwidth extension ranges are indicated by different values ​​indicated by N bits.

24. The method according to claim 13 or 14, characterized in that, The third indication information is carried in the A-Control field or the per AID TID info field in the second frame.

25. The method according to claim 24, characterized in that, The A-Control field includes at least one Control subfield. When the Control ID value in the Control subfield is the ninth value, the Control Information field in the Control subfield is used to indicate the third indication information.

26. The method according to claim 14, characterized in that, When the second frame is a Multi-STA BlockAck frame, the Multi-STA BlockAck frame includes at least one Per AID TID Info field, the Per AID TID Info field carrying the first indication information and / or the second indication information and / or the third indication information.

27. The method according to any one of claims 1 to 26, characterized in that, Sending the third frame to the target station among the at least one second station based on the second frame includes: Based on the second frame, the target station is determined among the at least one second station; The third frame is sent to the target site or the at least one second site.

28. The method according to claim 27, characterized in that, Determining the target station among the at least one second station based on the second frame includes: Based on the second frames sent by each of the second stations, the resource demand level of each of the second stations is determined; When the maximum resource demand among the resource demand levels of each of the second sites is greater than the resource demand level of the first site, the site corresponding to the maximum resource demand level is determined as the target site.

29. The method according to claim 27 or 28, characterized in that, The third frame also includes at least one of the following information: sixth indication information, seventh indication information, eighth indication information, and tenth indication information. The sixth indication information is used to indicate the service type and / or service priority that are allowed to be transmitted within the first transmission resource; the seventh indication information is used to indicate whether bandwidth expansion operation is allowed within the first transmission resource; the eighth indication information is used to indicate the sharing mode of the first transmission resource; and the tenth indication information is used to indicate the sharing start time of the first transmission resource or the start time of the first multi-AP cooperation mode.

30. The method according to claim 29, characterized in that, The sharing mode of the first transmission resource includes, but is not limited to, at least one of the following modes: sharing the first transmission resource after sending the third frame, sharing the first transmission resource after the first station has completed transmission, whether the first station participates in transmission within the first transmission resource, and / or, multi-AP cooperative transmission mode allowed within the first transmission resource.

31. The method according to any one of claims 27 to 30, characterized in that, The third frame is a MU-RTS TXS Trigger frame.

32. The method according to claim 30, characterized in that, The third frame includes a Common Info field and a User Info List field, wherein the User Info List field includes at least one User Info subfield.

33. The method according to claim 32, characterized in that, The RA in the third frame is the target site; or, the RA in the third frame is the broadcast MAC address, and the AID12 field of the User Info subfield indicates the identification information of the target site.

34. The method according to claim 33, characterized in that, At least one of the following fields in the third frame is defined as the Traffic Constraint field: the Common Info field, the Special User Info field, and / or N reserved bits in the User Info subfield, the Traffic Constraint field being used to indicate the sixth indication information.

35. The method according to claim 33 or 34, characterized in that, At least one of the following fields of the third frame is defined as a bandwidth extension field: the Common Info field, the Special User Info field, and / or, M reserved bits in the User Info subfield, wherein the bandwidth extension field is used to indicate the seventh indication information.

36. The method according to any one of claims 33 to 35, characterized in that, At least one of the following fields in the third frame is defined as the sharer priority transmission field: the Common Info field, the Special User Info field, and / or, L reserved bits in the User Info subfield. The sharer priority transmission field is used to indicate whether the first site in the eighth indication information performs priority transmission within the first transmission resource.

37. The method according to claim 36, characterized in that, The priority transmission method includes the following: when the target site is an AP, within the first transmission resource, the inter-frame interval for frame interaction between the target site and the associated STA is a preset time length. If the cached service or the service to be transmitted by the first site meets the first condition, the transmission opportunity is preempted when the channel is idle or within the preset time length.

38. The method according to any one of claims 33 to 35, characterized in that, The third frame has at least one of the following fields defined as a multi-AP transmission field: the Common Info field, the Special User Info field, and / or the Z reserved bits in the User Info subfield, wherein the multi-AP transmission field is used to indicate the multi-AP cooperative transmission mode and / or cooperative transmission object allowed within the first transmission resource in the eighth indication information.

39. The method according to claim 38, characterized in that, The indication method for the multi-AP cooperative transmission modes allowed within the first transmission resource includes: using multiple bits to correspond to multiple multi-AP cooperative transmission modes, and the values ​​of the multiple bits are used to indicate whether the corresponding multi-AP cooperative transmission mode is supported.

40. The method according to claim 38 or 39, characterized in that, The indication method for the cooperative transmission object includes: indicating it by carrying the AP ID and Peer ID in the third frame, or indicating one of the cooperative transmission objects by carrying the RA or AP ID in the third frame.

41. The method according to any one of claims 27 to 40, characterized in that, When the recipient of the third frame is the at least one second station, the third frame also includes ninth indication information, which is used to indicate the target station.

42. The method according to any one of claims 29 to 41, characterized in that, Before sending the third frame to the target station in the second station, the method further includes: Based on the second frame, the sharing mode of the first transmission resource is determined.

43. The method according to any one of claims 1 to 42, characterized in that, After sending a third frame to the target station among the at least one second station, the method further includes: The fourth frame sent by the target device is received, the fourth frame being used to indicate acceptance of the first transmission resource.

44. The method according to claim 43, characterized in that, The fourth frame is a CTS frame.

45. The method according to any one of claims 1 to 44, characterized in that, The method further includes: The fifth frame sent by the target device is received, the fifth frame being used to indicate the remaining resources to be returned to the first transmission resource and / or the return rules of the remaining resources.

46. ​​The method according to claim 45, characterized in that, The return rules include the service types and / or service priorities that are allowed to be transmitted within the remaining resources.

47. The method according to claim 46, characterized in that, The fifth frame includes a transmission resource return field, which includes a return mode subfield and / or a return service type subfield.

48. The method according to claim 47, characterized in that, The return mode subfield is used to indicate whether the target device should continue transmission within the remaining resources.

49. The method according to claim 48, characterized in that, When the return mode subfield is used to indicate whether the target device should continue transmitting within the remaining resources, the return service type subfield is used to indicate the service type or service priority that is allowed to be transmitted.

50. The method according to claim 49, characterized in that, The indication method for the permitted service type or service priority includes, but is not limited to, any of the following: direct indication, or indication of the lowest category of service type or lowest service priority that is permitted to be transmitted.

51. The method according to any one of claims 45 to 50, characterized in that, The method further includes: A sixth frame is sent to the target site, the sixth frame being used to indicate that there is a service to be transmitted that conforms to the return rule.

52. The method according to any one of claims 45 to 51, characterized in that, After the first station completes the transmission within the remaining resources, the method further includes: A seventh frame is sent to the target site or the at least one second site, the seventh frame being used to instruct the receiver to continue using the remaining resources.

53. A resource sharing method, applied to a second site, characterized in that, include: A second frame is sent to the first station, the second frame including but not limited to at least one of the following: first indication information, second indication information, third indication information, fourth indication information, and / or fifth indication information. Wherein, the first indication information is used to indicate service status information, the second indication information is used to indicate whether bandwidth expansion operation is supported, the third indication information is used to indicate the supported multi-AP cooperative transmission mode information, the fourth indication information is used to indicate the identification information of non-AP sites participating in the multi-AP cooperative transmission, and the fifth indication information is used to indicate whether to participate in the first multi-AP cooperative mode.

54. The method according to claim 53, characterized in that, After sending the second frame to the first station, the method further includes: Receive a third frame sent by the first site, the third frame being used to indicate the first transmission resource shared by the first site.

55. The method according to claim 53 or 54, characterized in that, Before sending the second frame to the first station, the method further includes: The system receives a first frame sent by the first station, the first frame including at least one of the following: first request information, second request information, third request information, fourth request information, and / or fifth request information, wherein... The first request information is used to request the service status information; the second request information is used to request whether the bandwidth expansion operation is supported; the third request information is used to request the receiver to provide feedback on the supported multi-AP cooperative transmission mode information; the fourth request information is used to request the receiver to provide feedback on the identification information of the non-AP sites participating in the multi-AP cooperative transmission; and the fifth request information is used to request the receiver to provide feedback on whether it participates in the first multi-AP cooperative mode.

56. The method according to claim 53, characterized in that, Sending the second frame to the first station includes: The second frame is periodically sent to the first station; or, When the first condition is met, the second frame is sent to the first station.

57. The method according to claim 54 or 55, characterized in that, The third frame includes, but is not limited to, at least one of the following: sixth indication information, seventh indication information, eighth indication information, ninth indication information, and / or tenth indication information; The sixth indication information is used to indicate the service type and / or service priority allowed to be transmitted within the first transmission resource; the seventh indication information is used to indicate whether bandwidth expansion operation is allowed within the first transmission resource; the eighth indication information is used to indicate the sharing mode of the first transmission resource; the ninth indication information is used to indicate the sharing site of the first transmission resource; and the tenth indication information is used to indicate the sharing start time of the first transmission resource or the start time of the first multi-AP cooperation mode.

58. The method according to claim 57, characterized in that, When the third frame does not include the seventh indication information, the method further includes: Determine whether a bandwidth expansion operation is performed on the first transmission resource, and / or, the range of bandwidth expansion when a bandwidth expansion operation is performed.

59. The method according to claim 57 or 58, characterized in that, The method further includes: On channels outside the bandwidth corresponding to the first transmission resource, perform channel idle detection or backoff operation; If the idle time of the first channel exceeds a preset value, then transmission will be performed on the bandwidth corresponding to the first transmission resource and the bandwidth corresponding to the first channel. or, If the second channel is idle during the backoff operation, transmission will be performed on the bandwidth corresponding to the first transmission resource and the bandwidth corresponding to the second channel.

60. The method according to any one of claims 53 to 59, characterized in that, The method further includes: A fourth frame is sent to the first station, the fourth frame being used to indicate acceptance of the first transmission resource.

61. The method according to any one of claims 53 to 60, characterized in that, The method further includes: A fifth frame is sent to the first station, the fifth frame being used to indicate the remaining resources to be returned to the first transmission resource and / or the rules for returning the remaining resources.

62. The method according to claim 61, characterized in that, The method further includes: The system receives a sixth frame sent by the first station, the sixth frame being used to indicate that there is a service to be transmitted that conforms to the return rule.

63. The method according to claim 61 or 62, characterized in that, After the first station completes the transmission within the remaining resources, the method further includes: The receiver receives a seventh frame sent by the first station, the seventh frame being used to instruct the receiver to continue using the remaining resources.

64. The method according to claim 53, characterized in that, When the fifth indication information is used to indicate non-participation in the first multi-AP collaboration mode, the method further includes: Switch to energy-saving mode, or switch from the current first channel to a non-primary channel to access the NPCA primary channel.

65. The method according to claim 57, characterized in that, When the ninth indication information in the third frame does not include the identification information of the second station, the method further includes: Switch to power saving mode, or switch from the current first channel to the NPCA main channel.

66. The method according to claim 65, characterized in that, When the third frame indicates that the first transmission resource is shared with the second station, the method further includes: Before the time indicated by the tenth instruction information, switch to energy-saving mode, or switch from the current first channel to the NPCA main channel.

67. The method according to claim 66, characterized in that, The method further includes: When the time indicated by the tenth instruction message is reached, switch to active mode or wake-up state, or switch back from the NPCA main channel to the first channel.

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

69. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed, cause the method according to any one of claims 1 to 67 to be implemented.

Images