Base stations, communication methods, and integrated circuits

Abstract

To improve communication efficiency in cooperative communication.SOLUTION: A base station includes a receiving circuit that receives a control signal including parameters that are independent of the type of cooperative communication and parameters that are dependent on the type from another base station, and a control circuit that performs cooperative communication based on the control signal. The format of the control signal is determined based on the type, and the field length of the type-dependent parameters is variable depending on the type.SELECTED DRAWING: Figure 5

Description

Technical Field

[0001] The present disclosure relates to a base station, a communication device, and a communication method.

Background Art

[0002] In the Institute of Electrical and Electronics Engineers (IEEE), the standard IEEE 802.11be (hereinafter also referred to as "11be") for the next-generation wireless local area network (LAN), which is a successor standard to the standard IEEE 802.11ax (hereinafter also referred to as "11ax"), is being studied. For example, IEEE 802.ax is also called High Efficiency (HE), and IEEE 802.be is also called Extream High Throughput (EHT).

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Non-Patent Document 5

[0004] However, methods for controlling cooperative communication in wireless communication such as Wi-Fi have not been sufficiently studied.

[0005] Non-limiting embodiments of this disclosure contribute to the provision of base stations, communication devices, and communication methods that can improve communication efficiency in cooperative communication.

[0006] A base station according to one embodiment of the present disclosure comprises a control circuit that determines the format of a control signal based on the type of cooperative communication, and a transmission circuit that transmits the control signal to another base station according to the format.

[0007] These comprehensive or specific embodiments may be implemented as systems, devices, methods, integrated circuits, computer programs, or recording media, or as any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0008] According to one embodiment of the present disclosure, communication efficiency in cooperative communication can be improved.

[0009] Further advantages and effects of one embodiment of this disclosure will be made apparent from the specification and drawings. Such advantages and / or effects are provided by several embodiments and features described in the specification and drawings, but not all of them are necessarily provided in order to obtain one or more identical features. [Brief explanation of the drawing]

[0010] [Figure 1] Diagram showing an example of the Multi-AP (MAP) Trigger frame format. [Figure 2] Diagram showing an example of MAP configuration [Figure 3]Figure showing an example of notification information for each MAP type [Figure 4] Block diagram showing a partial configuration example of the AP according to Embodiment 1 [Figure 5] Block diagram showing a configuration example of the AP according to Embodiment 1 [Figure 6] Block diagram showing a configuration example of the STA according to Embodiment 1 [Figure 7] Figure showing an example of the MAP Trigger frame format according to Embodiment 1 [Figure 8] Figure showing a definition example of the Frame Control field [Figure 9] Figure showing a definition example of the MAP type [Figure 10] Figure showing a definition example of the MAP type [Figure 11] Figure showing an example of the MAP Trigger frame format according to Embodiment 2 [Figure 12] Figure showing a definition example of the Trigger Type subfield [Figure 13] Figure showing an example of the MAP Trigger frame format according to Embodiment 3 [Figure 14] Figure showing a definition example of the Trigger Type subfield [Figure 15] Figure showing an example of the MAP Trigger frame format according to Embodiment 4 [Figure 16] Figure showing an example of the MAP Trigger frame format according to Embodiment 5 [Figure 17] Figure showing a comparison example between Embodiment 4 and Embodiment 5 [Figure 18] Figure showing an example of the MAP Trigger frame format according to Embodiment 6 [Figure 19] Figure showing an example of the MAP Trigger frame format according to Embodiment 6 [Figure 20] Figure showing a definition example of Total MAP Type and MAP Type Index [Figure 21]Figure showing an example of the MAP Trigger frame format according to Embodiment 7 [Figure 22] Figure showing an example of the MAP Trigger frame format according to Embodiment 8 [Figure 23] Figure showing an example of indicating the MAP type when the MAP type is different for each Station (STA) [Figure 24] Figure showing a comparative example of Embodiments 6, 7, and 8 [Figure 25] Figure showing an example of the MAP Trigger frame format according to Embodiment 9 **Embodiments for Carrying out the Invention**

[0011] Hereinafter, each embodiment of the present disclosure will be described in detail with reference to the drawings.

[0012] In 11be, for example, the application of Multi-AP (hereinafter referred to as "MAP") coordination (hereinafter referred to as "coordinated communication") in which a plurality of access points (AP: Access Point, also referred to as "base station") cooperate to transmit and receive data to and from each terminal (STA: Station, also referred to as "non-AP STA") has been considered (for example, Non-Patent Documents 1 to 5).

[0013] A plurality of types (for example, communication types, hereinafter referred to as "MAP types") are considered for coordinated communication in 11be. For example, the following MAP types can be mentioned. · Coordinated Spatial Reuse (hereinafter referred to as "C-SR") · Coordinated Orthogonal Frequency Division Multiple Access (hereinafter referred to as "C-OFDMA") · Joint Transmissions (hereinafter referred to as "JT") · Coordinated Beamforming (hereinafter referred to as "CBF")

[0014] Furthermore, JT includes methods for transmitting the same signal from multiple cooperating APs, and methods for transmitting different transmission streams from multiple cooperating APs. The method for transmitting different transmission streams from multiple cooperating APs is called, for example, Distributed Multi-User - Multiple Input Multiple Output (D-MIMO).

[0015] For example, "JT" may be defined as a method of transmitting the same signal from multiple cooperating APs, and may be defined as a different method from "D-MIMO". In the following, as an example, "JT" will be defined as a method of transmitting the same signal from multiple cooperating APs, and "D-MIMO" will be defined as a method of transmitting different transmission streams from multiple cooperating APs.

[0016] Furthermore, as a control method for cooperative communication, for example, the MAP Trigger frame (sometimes called a MAP Announcement frame) format is being considered. For example, the control procedures for each MAP type or the information (notification information) notified from the AP to the STA are being examined for the MAP Trigger frame format.

[0017] Figure 1 shows an example of a MAP Trigger frame format based on the Trigger frame format in 11ax. As shown in Figure 1, for example, "Per AP Info," which is information (or a field) for each AP, may be defined.

[0018] Figure 2 shows an example configuration of APs and STAs (an example configuration of MAPs) that perform cooperative communication.

[0019] In Figure 2, "Sharing AP" may be, for example, an AP that acquires a channel usage (or transmission) period (e.g., TXOP: transmission opportunity) and initiates (or controls) cooperative communication. "Shared AP" may be an AP that is instructed to perform cooperative communication by the Sharing AP.

[0020] Note that while Figure 2 shows an example where the Sharing AP and Shared AP are different APs, the configuration is not limited to this; for example, one of the Shared APs may also function as the Sharing AP. For example, the MAP Trigger frame may be sent from the Sharing AP to the Shared AP. By sending the MAP Trigger frame, the Sharing AP may instruct the Shared AP to perform control related to cooperative communication (e.g., initiate). The MAP Trigger frame may include information specific to each Shared AP (e.g., Per AP Info).

[0021] One embodiment of this disclosure describes a method for integrating and efficiently controlling multiple MAP types in a MAP Trigger frame (e.g., setting the MAP Trigger frame format).

[0022] [Configuration of the wireless communication system] The wireless communication system according to this embodiment may include a plurality of AP100s and STA200s. An AP100 may have both Sharing AP and Shared AP functions, or one of them.

[0023] For example, AP100, which is a Sharing AP, may notify other AP100s, which are Shared APs, of the MAP type (e.g., C-SR, C-OFDMA, JT, CBF, or D-MIMO) in the MAP Trigger frame. Note that "notification" may be read as "transmission" or "instruction".

[0024] Furthermore, AP100, which is a Sharing AP, may, for example, determine (or change) the format of the MAP Trigger frame based on the MAP type, and send the MAP Trigger frame to other AP100s, which are Shared APs, in the determined format.

[0025] Here, the parameters (or notification information) notified from the Sharing AP to the Shared AP in the MAP Trigger frame may include parameters that are independent of the MAP type (or parameters common to multiple MAP types) and parameters that are dependent on the MAP type (or parameters that differ among multiple MAP types). Note that the term "dependent on the MAP type" may be rephrased as, for example, "based on the MAP type." The term "independent of the MAP type" may be rephrased as, for example, "not based on the MAP type" or "independent."

[0026] Examples of parameters that are independent of the MAP type include the following: • BW (bandwidth) • MAP type (information indicating the type of cooperative communication) • Shared AP ID (Identification information for the Shared AP) • Uplink (UL) / Downlink (DL) Flag (Information indicating either UL or DL) • Resource Allocation (Resource allocation information)

[0027] Figure 3 shows an example of parameters that depend on the MAP type.

[0028] In Figure 3, the parameters corresponding to "●" indicate the parameters notified by the MAP Trigger frame for the corresponding MAP type.

[0029] For example, in the MAP type "C-SR" shown in Figure 3, the transmission power of the Sharing AP and Shared AP (e.g., Sharing AP Tx Power and Shared AP Maximum Tx Power) and the acceptable interference level (e.g., Sharing AP Acceptable Maximum Interference Level and Shared AP Interference Level) may be notified.

[0030] Furthermore, for example, in the MAP types "JT" and "D-MIMO" shown in Figure 3, transmission parameters such as the Modulation and Coding Scheme (MCS), Sequence Number, and Spatial Stream Index may be notified.

[0031] Furthermore, for example, in the MAP type "CBF" shown in Figure 3, the ID of the STA that suppresses interference by beamforming (e.g., STA ID to Suppress) and resource allocation information (STA Resource Allocation Info to Suppress) may be notified.

[0032] Furthermore, for example, in the MAP type "C-OFDMA" shown in Figure 3, the parameters that depend on the MAP type mentioned above do not need to be notified.

[0033] Note that the parameters described above, both those independent of the MAP type and those dependent on the MAP type, are merely examples, and other parameters may also be used.

[0034] Figure 4 is a block diagram showing a partial configuration example of AP100 according to one embodiment of the present disclosure. In AP100 shown in Figure 4, the control unit 101 (corresponding to, for example, a control circuit) determines the format of the control signal (e.g., MAP Trigger frame) based on the type of cooperative communication (e.g., MAP type). The wireless transceiver unit 105 (corresponding to, for example, a transmission circuit) transmits the control signal to another base station (e.g., a Shared AP) in the above format.

[0035] (Embodiment 1) [Example configuration of AP100] Figure 5 is a block diagram showing an example configuration of AP100. The AP100 shown in Figure 5 may include, for example, a control unit 101, a control signal generation unit 102 for STA, a control signal generation unit 103 for AP, a transmission signal generation unit 104, a wireless transmission / reception unit 105, and a received signal demodulation / decoding unit 106.

[0036] The control unit 101 may, for example, control the setting of MAP Trigger frames. For example, if AP100 is a Sharing AP, the control unit 101 may control the generation of control signals (e.g., MAP Trigger frames) to other AP100s (e.g., Shared APs). For example, the control unit 101 may determine the MAP Trigger frame format based on the MAP type. Also, if AP100 is a Shared AP, the control unit 101 may, for example, identify the format of a MAP Trigger frame transmitted from another AP100 (e.g., a Sharing AP) based on information about the MAP type.

[0037] An example of the MAP Trigger frame format will be discussed later.

[0038] Furthermore, the control unit 101 may set control information for, for example, the STA200 or other AP100. For example, the control unit 101 may set resource allocation information and scheduling information such as MCS for each STA200. Also, the control unit 101 may determine parameters related to transmission control (for example, the parameters related to cooperative communication described above) based on information input from the received signal demodulation / decoding unit 106 (for example, control information notified from the Sharing AP to the Shared AP). The control unit 101 may output control information including the determined transmission control parameters to the STA control signal generation unit 102 and the AP control signal generation unit 103.

[0039] The STA control signal generation unit 102 may, for example, generate a control signal for the STA200 (e.g., a trigger frame) and output the generated control signal to the transmission signal generation unit 104.

[0040] The AP control signal generation unit 103 may, for example, generate a control signal for AP100 (for example, a MAP Trigger frame). For example, the AP control signal generation unit 103 may generate a control signal based on control information input from the control unit 101 and information input from the received signal demodulation / decoding unit 106.

[0041] The control signal for AP100 may include, for example, time and frequency resource information (e.g., RU allocation information for uplink cooperative communication, TXOP, LENGTH, etc.) as well as at least one parameter related to cooperative communication (e.g., the MAP type, a parameter independent of the MAP type, or a parameter dependent on the MAP type, as described above). The AP control signal generation unit 103 outputs the generated control signal to the transmission signal generation unit 104, for example.

[0042] The transmission signal generation unit 104 may, for example, perform transmission processing on control signals, data, and ACK / Block-ACK input from the STA control signal generation unit 102 or the AP control signal generation unit 103, and generate a wireless frame (transmission signal). The transmission signal generation unit 104 outputs the generated transmission signal to the wireless transceiver unit 105.

[0043] The wireless transceiver unit 105 performs wireless transmission processing on the transmission signal input from the transmission signal generation unit 104, such as D / A conversion and upconversion to the carrier frequency, and transmits the processed signal via the antenna.

[0044] When AP100 receives, for example, an uplink signal transmitted from STA200, or a control signal transmitted from another AP100, it may operate as follows:

[0045] The wireless signal received via the antenna is input to the wireless transceiver 105. The wireless transceiver 105 performs wireless reception processing on the received wireless signal, such as down-converting the carrier frequency, and outputs the processed signal to the received signal demodulation / decoding unit 106.

[0046] The received signal demodulation / decoding unit 106 may, for example, perform processing such as autocorrelation on the signal input from the wireless transceiver unit 105 to extract the received wireless frame. The received signal demodulation / decoding unit 106 may also decode and demodulate, for example, the uplink signal from the STA200 (e.g., response signal, feedback information) or the control signal from another AP100 (e.g., MAP Trigger frame) included in the extracted wireless frame. The received signal demodulation / decoding unit 106 may, for example, output the demodulated control signal to the control unit 101, the STA control signal generation unit 102, and the AP control signal generation unit 103.

[0047] [STA200 Configuration Example] Figure 6 is a block diagram showing an example configuration of the STA200 according to this embodiment. The STA200 shown in Figure 6 may include, for example, a wireless transmitting / receiving unit 201, a received signal demodulation / decoding unit 202, and a transmitted signal generation unit 203.

[0048] The wireless transceiver unit 201, for example, receives a signal transmitted from AP100 via the antenna, performs wireless reception processing such as down-conversion and A / D conversion on the received signal, and outputs the processed signal to the received signal demodulation / decoding unit 202. The wireless transceiver unit 201 may also perform wireless transmission processing such as D / A conversion and up-conversion to the carrier frequency on a signal input from the transmission signal generation unit 203, and transmit the processed signal via the antenna.

[0049] The received signal demodulation / decoding unit 202 may, for example, perform autocorrelation processing on the signal input from the wireless transceiver unit 201 to extract the received wireless frame. The received signal demodulation / decoding unit 202 may, for example, demodulate and decode the control signals (e.g., trigger frames) contained within the extracted wireless frame to obtain uplink transmission control parameters. The received signal demodulation / decoding unit 202 may, for example, output the acquired uplink transmission control parameters to the transmission signal generation unit 203.

[0050] The transmission signal generation unit 203 may, for example, perform transmission signal processing on the uplink signal (e.g., response signal) based on uplink transmission control parameters input from the reception signal demodulation / decoding unit 202, and generate a wireless frame (transmission signal). The transmission signal generation unit 203 may, for example, output the generated transmission signal to the wireless transceiver unit 201.

[0051] [Example of MAP Trigger frame format settings] Next, an example of setting the MAP Trigger frame format according to this embodiment will be described.

[0052] This embodiment describes, for example, the case where multiple (for example, all) Shared APs share the same MAP type.

[0053] If multiple Shared APs share the same MAP type, AP100 (Sharing AP) may notify other AP100s of the MAP type in the "MAP Type" field, which is located within the Common Information field (e.g., Common Info) of the MAP Trigger frame, which contains information common to multiple Shared APs. In other words, the MAP type (information indicating the type of cooperative communication) may be included in the field for notifying the MAP type in Common Info. Note that "placement" may be replaced with other terms such as "mapping" or "configuration".

[0054] Furthermore, AP100 may determine (or change) the format of the MAP type-dependent common information in the Common Info field (e.g., MAP Type Dependent Common Info) and the MAP type-dependent information in the Per AP Info field (e.g., MAP Type Dependent Info) based on the MAP type to be notified to multiple Shared APs.

[0055] Figure 7 shows an example of the MAP Trigger frame format according to this embodiment.

[0056] For example, the frame type being "MAP Trigger" may be notified to the Shared AP by the "Frame Control" field (e.g., Type and Subtype subfields). Figure 8 shows an example of the definition of the Type and Subtype subfields in the Frame Control field. As an example, Figure 8 shows an excerpt of the Control type in 11ax. In the example shown in Figure 8, the Subtype of MAP Trigger is defined in the Subtype value "0001", which is a Reserved value in 11ax. Note that the definition in the Frame Control field is not limited to the example shown in Figure 8, and the Subtype value of MAP Trigger may be defined in other values ​​(e.g., other Reserved values).

[0057] In Figure 7, the Common Info field may contain, for example, notification information (or common information) that is common to multiple Shared APs. This common information for multiple Shared APs may include, for example, common information that is independent of the MAP type (or information common to multiple MAP types), and common information that is dependent on the MAP type (or information that differs depending on the MAP type; MAP Type Dependent Common Info).

[0058] Common information that is independent of the MAP type may include, for example, information about the MAP type and bandwidth (BW).

[0059] Furthermore, common information that depends on the MAP type may include, for example, information such as Sharing AP Tx Power and Sharing AP Acceptable Maximum Interference Level.

[0060] Figures 9 and 10 show examples of MAP type definitions. For example, the MAP type definition example shown in Figure 9 (hereinafter referred to as "Definition Example 1") is an example in which an index is assigned to each MAP type. Also, for example, the MAP type definition example shown in Figure 10 (hereinafter referred to as "Definition Example 2") is an example in which MAP types that use similar parameters, such as JT and D-MIMO, are grouped into one and an index is assigned to it. For example, MAP type definition Example 2 can reduce the table size of the MAP types compared to definition Example 1.

[0061] In Figure 7, the Per AP Info field may contain, for example, individual notification information (or individual information) for each Shared AP. The individual information for each Shared AP may be, for example, information common to all STA200s associated with (or connected to) the Shared AP. The individual information for each Shared AP may include, for example, individual information that is independent of the MAP type (or individual information common to multiple MAP types), and individual information that is dependent on the MAP type (or individual information that differs depending on the MAP type, MAP Type Dependent Info).

[0062] Individual information that is independent of the MAP type may include, for example, the Shared AP ID, Resource Allocation, and UL / DL Flag.

[0063] Furthermore, the individual information that depends on the MAP type may include, for example, the following: • For C-SR: Shared AP Maximum Tx Power, Shared AP Interference Level • For JT or D-MIMO: Transmission Parameter (e.g., MCS, Sequence Number,…) • For CBF: STA ID to Suppress, STA Resource Allocation Info to Suppress • In the case of C-OFDMA: No information available.

[0064] Note that BW in Figure 7 may be the same as, or different from, the definition of "UL BW subfield" in the Common Info field of the 11ax Trigger frame format. Also, Resource Allocation in Figure 7 may be the same as, or different from, the definition of "RU Allocation subfield" in the User Info field of the 11ax Trigger frame format.

[0065] Alternatively, for example, AP100 may determine the size and location of the RU based on the RU Allocation subfield and the Spatial Configuration subfield of the User Specific field defined in the Common field of HE-SIG-B of 11ax, or a method similar to the one extended for 11be.

[0066] Furthermore, for example, the RU Allocation subfield of 11ax defines RUs with a size of less than 20 MHz, but resource allocation is not limited to this definition, and for example, sizes of 20 MHz or larger may be defined.

[0067] Thus, in this embodiment, AP100 (Sharing AP) notifies other AP100 (Shared AP) of its MAP type in the MAP Trigger frame using the MAP type field placed in the Common Info field, and notifies them of MAP type-dependent common information (e.g., MAP Type Dependent Common Info) and MAP type-dependent information (MAP Type Dependent Info) corresponding to that MAP type. In other words, in the MAP Trigger frame, the contents of the MAP type-dependent common information and MAP type-dependent information are changed based on the MAP type.

[0068] By configuring this MAP Trigger frame, AP100 can notify other AP100s of control signals corresponding to each of the multiple MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in cooperative communication can be improved.

[0069] (Embodiment 2) The configuration of AP and STA in this embodiment may be the same as in Embodiment 1.

[0070] In this embodiment, for example, a case where multiple (for example, all) Shared APs share the same MAP type will be described, similar to Embodiment 1.

[0071] If multiple Shared APs share the same MAP type, AP100 (Sharing AP) may notify other AP100s (Shared APs) of the MAP type of the MAP Trigger, for example, in the Trigger Type field (similar to the UL trigger for 11ax). In other words, the MAP type (information indicating the type of cooperative communication) may be included in the field for notifying the Trigger type in Common Info.

[0072] Furthermore, AP100 may determine (or change) the format of the MAP type-dependent common information in the Common Info field (e.g., MAP Type Dependent Common Info) and the MAP type-dependent information in the Per AP Info field (e.g., MAP Type Dependent Info) based on the MAP type to be notified to multiple Shared APs.

[0073] Figure 11 shows an example of the MAP Trigger frame format according to this embodiment. Figure 12 shows an example of the definition of the Trigger Type subfield.

[0074] For example, as shown in Figure 12, multiple MAP types may be defined with values ​​8 to 12 for each of the Trigger Type subfields of 11ax (e.g., Table 9-31b). Based on this definition of MAP types, the Shared AP may identify (or recognize, determine) the MAP type in the Trigger Type field within the Common Info field shown in Figure 11.

[0075] In Figure 11, the common information in the Common Info field that does not depend on the MAP type (e.g., BW) may be the same as in Embodiment 1, for example.

[0076] Furthermore, in Figure 11, the Trigger Type Dependent Common Info in the Common Info field may be the same as, for example, the MAP Type Dependent Common Info in Embodiment 1.

[0077] Furthermore, in Figure 11, the individual information in the Per AP Info field that is independent of the MAP type (e.g., Shared AP ID, Resource Allocation, UL / DL Flag) may be the same as in Embodiment 1, for example.

[0078] Furthermore, in Figure 11, the Trigger type dependency information (e.g., Trigger Type Dependent Info) in the Per AP Info field may be the same as, for example, the MAP type dependency information (e.g., MAP Type Dependent Info) in Embodiment 1.

[0079] Thus, in this embodiment, AP100 notifies other AP100s of the MAP type of the MAP Trigger using the Trigger Type field in the MAP Trigger frame. AP100 also notifies other AP100s of Trigger Type Dependent Common Info and Trigger Type Dependent Info, for example, according to the MAP type notified in the Trigger Type field. In other words, in the MAP Trigger frame, the format of the Trigger Type Dependent Common Info and Trigger Type Dependent Info is changed based on the MAP type, as in Embodiment 1.

[0080] By configuring this MAP Trigger frame, AP100 can notify other AP100s of control signals corresponding to each of the multiple MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in cooperative communication can be improved.

[0081] (Embodiment 3) The configuration of AP and STA in this embodiment may be the same as in Embodiment 1.

[0082] In this embodiment, for example, a case where multiple (for example, all) Shared APs share the same MAP type will be described, similar to Embodiment 1.

[0083] If multiple Shared APs share the same MAP type, AP100 (Sharing AP) may notify other AP100s (Shared APs) of the MAP Trigger, for example, in the Trigger Type field (similar to the UL Trigger for 11ax). AP100 may also notify the MAP type, for example, in the Trigger Type Dependent Common Info field. In other words, in Common Info, the information that triggers MAP coordination is included in the field for notifying the trigger type, and the MAP type (information indicating the type of coordination) is included in the field that depends on the Trigger type.

[0084] Furthermore, AP100 may determine (or change) the format of the MAP type-dependent common information (e.g., MAP Type Dependent Common Info) within the Trigger type-dependent common information (e.g., Trigger Type Dependent Common Info) in the Common Info field, and the Trigger type-dependent information (e.g., Trigger Type Dependent Info) in the Per AP Info field, based on the MAP type to be notified to multiple Shared APs.

[0085] Figure 13 shows an example of the MAP Trigger frame format according to this embodiment. Figure 14 shows an example of the definition of the Trigger Type subfield.

[0086] For example, as shown in Figure 14, the Trigger Type subfield of 11ax (e.g., Table 9-31b) may be defined with a value of 8 as MAP (Multi-AP). With this MAP definition, the Shared AP may recognize that the Trigger Type in the Common Info shown in Figure 13 is MAP.

[0087] Furthermore, for example, a MAP Type field may be placed in the Common Info field, which contains trigger type-dependent common information (e.g., Trigger Type Dependent Common Info). A Shared AP may identify (or recognize, determine) the MAP type in the MAP Type field within the Common Info field of a MAP Trigger frame whose Trigger Type is MAP.

[0088] In Figure 13, the common information in the Common Info field that does not depend on the MAP type (e.g., BW) may be the same as in Embodiment 1, for example.

[0089] Furthermore, in Figure 13, the MAP type dependent common information (e.g., MAP Type Dependent Common Info) in the Common Info field may be the same as, for example, the MAP type dependent common information (MAP Type Dependent Common Info) in Embodiment 1.

[0090] Furthermore, in Figure 13, the individual information in the Per AP Info field that is independent of the MAP type (e.g., Shared AP ID, Resource Allocation, UL / DL Flag) may be the same as in Embodiment 1, for example.

[0091] Furthermore, in Figure 13, the MAP type dependency information (e.g., Trigger Type Dependent Info) in the Per AP Info field may be the same as, for example, the MAP type dependency information (e.g., MAP Type Dependent Info) in Embodiment 1.

[0092] Thus, in this embodiment, AP100 notifies other AP100s in the MAP Trigger frame that a MAP is triggered by the Trigger Type field, and notifies other AP100s of the MAP type in the MAP Type field within the Trigger Type Dependent Common Info. AP100 also notifies other AP100s, for example, Trigger Type Dependent Common Info and Trigger Type Dependent Info corresponding to the notified MAP type. In other words, in the MAP Trigger frame, the format of the Trigger Type Dependent Common Info and Trigger Type Dependent Info is changed based on the MAP type.

[0093] By configuring this MAP Trigger frame, AP100 can notify other AP100s of control signals corresponding to each of the multiple MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in cooperative communication can be improved.

[0094] (Comparison of Embodiments 1, 2, and 3) For example, the complexity of the processing related to the MAP Trigger frame format in each of embodiments 1, 2, and 3 is equivalent.

[0095] Furthermore, for example, in terms of signaling for the MAP Trigger frame formats of each embodiment 1, 2, and 3, the difference lies in the fact that notification of being a MAP Trigger and notification of the MAP type are performed in the following fields. • Embodiment 1: MAP Type in Frame Control and Common Info • Embodiment 2: Trigger Type in Common Info • Embodiment 3: Trigger Type in Common Info and MAP Type in Trigger Type Dependent Common Info

[0096] Therefore, for example, among the MAP Trigger frame formats of Embodiments 1, 2, and 3, the format to be applied may be determined based on the definition area used in other applications different from MAP settings.

[0097] For example, if there is a large amount of unused space (e.g., Reserved space) in the definition area of ​​the Frame Control subtype (e.g., Figure 8) compared with the definition area of ​​the Trigger Type subield (e.g., Figure 12 or Figure 14), the MAP Trigger frame format of Embodiment 1 may be applied. On the other hand, if there is a large amount of unused space (e.g., Reserved space) in the definition area of ​​the Trigger Type subfield (e.g., Figure 12 or Figure 14) compared with the definition area of ​​the Frame Control subtype (e.g., Figure 8), the MAP Trigger frame format of Embodiment 2 or 3 may be applied.

[0098] (Embodiment 4) The configuration of AP and STA in this embodiment may be the same as in Embodiment 1.

[0099] This embodiment describes, for example, a case where the MAP types differ among multiple Shared APs.

[0100] If the MAP types differ between shared APs, AP100 (Sharing AP) may notify other AP100s (Shared APs) of the MAP types for each of the multiple shared APs, for example, in the MAP Type field located within the Common Info field. In other words, the MAP types for each of the multiple shared APs (information indicating the type of cooperative communication) may be included in Common Info (for example, the MAP Type field).

[0101] Furthermore, AP100 may determine (or change) the format of MAP type-dependent common information (e.g., MAP Type Dependent Common Info) and MAP type-dependent information (e.g., MAP Type Dependent Info) based on the MAP type notified for each of the multiple Shared APs.

[0102] Figure 15 shows an example of the MAP Trigger frame format according to this embodiment.

[0103] For example, as shown in Figure 15, the MAP Type field in the Common Info field may be set (in other words, indicated) for each of the multiple Shared APs (e.g., AP#1, AP#2, ...).

[0104] The fact that the frame shown in Figure 15 is a MAP Trigger may be notified to the Shared AP by Frame Control, as in Embodiment 1, or by Trigger Type, as in Embodiment 2 or 3.

[0105] Furthermore, in Figure 15, the common information in the Common Info field that does not depend on the MAP type (e.g., BW) may be the same as in Embodiment 1, for example.

[0106] Furthermore, in Figure 15, the MAP type dependent common information (e.g., MAP Type Dependent Common Info) in the Common Info field may be the same as, for example, the MAP type dependent common information (MAP Type Dependent Common Info) in Embodiment 1.

[0107] For example, if at least one of the MAP types of multiple Shared APs notified by the MAP Trigger frame is "C-SR", the MAP type-dependent common information field may include Sharing AP Tx Power and Sharing AP Acceptable Maximum Interference Level. On the other hand, if, for example, all of the MAP types of multiple Shared APs notified by the MAP Trigger frame are of a type other than "C-SR" (e.g., C-OFDMA, JT, CBF, or D-MIMO), the MAP type-dependent common information field does not need to include notification information.

[0108] Furthermore, in Figure 15, the individual information in the Per AP Info field that is independent of the MAP type (e.g., Shared AP ID, Resource Allocation, UL / DL Flag) may be the same as in Embodiment 1, for example.

[0109] Furthermore, in Figure 15, the MAP type dependency information (e.g., MAP Type Dependent Info) in the Per AP Info field may be the same as, for example, the MAP type dependency information (e.g., MAP Type Dependent Info) in Embodiment 1.

[0110] Thus, in this embodiment, AP100 notifies other AP100s of the MAP type for each of the multiple Shared APs using the MAP Type field placed within the Common Info field in the MAP Trigger frame. AP100 also notifies other AP100s, for example, MAP Type Dependent Common Info and MAP Type Dependent Info, depending on the MAP type. In other words, the format of the MAP Type Dependent Common Info and MAP Type Dependent Info in the MAP Trigger frame is changed based on the MAP types of the multiple Shared APs.

[0111] By configuring this MAP Trigger frame, AP100 can notify other AP100s of control signals corresponding to each of the multiple MAP types, even when the MAP types differ among multiple Shared APs, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in cooperative communication can be improved.

[0112] (Embodiment 5) The configuration of AP and STA in this embodiment may be the same as in Embodiment 1.

[0113] In this embodiment, for example, a case where the MAP types differ between multiple Shared APs will be described, similar to Embodiment 4.

[0114] If the MAP types differ between shared APs, AP100 (Sharing AP) may notify other AP100s (Shared APs) of the MAP types for each of the multiple shared APs, for example, in the Per AP Info field. In other words, the MAP types for each of the multiple shared APs (information indicating the type of cooperative communication) may be included in Per AP Info (for example, individual information).

[0115] Furthermore, AP100 may determine (or change) the format of MAP type dependent information (e.g., MAP Type Dependent Info) based on the MAP type to be notified for each of the multiple Shared APs.

[0116] Figure 16 shows an example of the MAP Trigger frame format according to this embodiment.

[0117] For example, as shown in Figure 16, the MAP Type field within the Per AP Info field may be set (in other words, indicated) for each of the multiple Shared APs.

[0118] The fact that the frame shown in Figure 16 is a MAP Trigger may be notified to the Shared AP by Frame Control, as in Embodiment 1, or by Trigger Type, as in Embodiment 2 or 3.

[0119] In Figure 16, the Common Info field may contain, for example, common information that is common to multiple Shared APs and is independent of the MAP type. Common information independent of the MAP type may include, for example, information about bandwidth (BW).

[0120] Furthermore, in Figure 16, the Per AP Info field may contain, for example, individual information for each Shared AP (in other words, notification information common to STA200s associated with the Shared AP). This individual information for each Shared AP may include, for example, individual information that is independent of the MAP type, and individual information that is dependent on the MAP type.

[0121] Individual information that is independent of the MAP type may include, for example, the Shared AP ID (AP ID), MAP Type, Resource Allocation, and UL / DL Flag.

[0122] Furthermore, individual information that depends on the MAP type (for example, MAP Type Dependent Info) may include the following information, for example: • For C-SR: Shared AP Tx Power, Sharing AP Acceptable Maximum Interference Level, Shared AP Maximum Tx Power, Shared AP Interference Level • For JT or D-MIMO: Transmission Parameter (e.g., MCS, Sequence Number,…) • For CBF: STA ID to Suppress, STA Resource Allocation Info to Suppress • In the case of C-OFDMA: No information available.

[0123] Here, the Per AP Info field length may be fixed or variable. In other words, the size of Per AP Info (individual information) may be common across MAP types or may differ for each MAP type.

[0124] For example, if the Per AP Info field length is fixed, the MAP Type Dependent Info may be set to a fixed length regardless of the MAP type. For example, the Per AP Info field length may be set based on the format of the largest MAP type (e.g., the largest size) among the Per AP Info field lengths corresponding to each MAP type (e.g., they may be aligned). For example, if the size of the MAP Type Dependent Info corresponding to a certain MAP type is shorter than the fixed length of the Per AP Info field, the remaining area may be set in the Reserved field.

[0125] If the Per AP Info field length is fixed, each Shared AP can determine the location of MAP type-dependent information corresponding to that Shared AP, regardless of the MAP type of other Shared APs, thus simplifying processing of Per AP Info (e.g., reading operations).

[0126] Furthermore, for example, if the Per AP Info field length is variable, the MAP Type Dependent Info may have its length set based on the MAP type. A Shared AP may, for example, determine the Per AP Info field length for each Shared AP based on the MAP type of the Per AP Info corresponding to each Shared AP.

[0127] When the Per AP Info field length is variable, MAP type-dependent information of a size corresponding to the MAP type set for each Shared AP is notified, thus reducing the amount of signaling compared to when the Per AP Info field has a fixed length.

[0128] Thus, in this embodiment, AP100 notifies other AP100s of the MAP type for each of the multiple Shared APs using the MAP Type field placed within the Per AP Info field in the MAP Trigger frame. AP100 also notifies other AP100s of MAP type dependent information (MAP Type Dependent Info) corresponding to the MAP type. In other words, the format of the MAP type dependent information in the MAP Trigger frame is changed based on the MAP types of the multiple Shared APs.

[0129] By configuring this MAP Trigger frame, AP100 can notify other AP100s of control signals corresponding to each of the multiple MAP types, even when the MAP types differ among multiple Shared APs, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in cooperative communication can be improved.

[0130] (Comparison of Embodiments 4 and 5) Figure 17 shows the complexity of the processing related to the MAP Trigger frame format and a comparative example of the signaling amount for each of Embodiments 4 and 5. In Figure 17, Embodiment 4 is shown for the case where the Per AP Info field length is variable, and Embodiment 5 is shown for both the fixed-length and variable-length Per AP Info field lengths.

[0131] As shown in Figure 17, compared to Embodiment 4, when the Per AP Info field length in Embodiment 5 is fixed, the complexity of processing can be reduced and the amount of signaling can be increased. Also, as shown in Figure 17, compared to Embodiment 4, when the Per AP Info field length in Embodiment 5 is variable, the complexity of processing can be increased and the amount of signaling can be reduced.

[0132] For example, if reducing processing complexity is a priority, the fixed-length Per AP Info field format of Embodiment 5 may be applied (or selected). Also, for example, if reducing the amount of signaling is a priority, the variable-length Per AP Info field format of Embodiment 5 may be applied (or selected). Furthermore, for example, if a balance between reducing processing complexity and reducing the amount of signaling is a priority, the format of Embodiment 4 may be applied (or selected).

[0133] (Embodiment 6) The configuration of AP and STA in this embodiment may be the same as in Embodiment 1.

[0134] This embodiment describes, for example, a case where the MAP types differ among multiple STA200s. This embodiment assumes, as an example, that a Sharing AP determines resource allocation for each STA associated with (or connected to) a Shared AP.

[0135] If the MAP types differ between STA200s, AP100 (Sharing AP) may notify the Shared AP of the MAP type in a separate "Per STA Info" field (or terminal-specific information) for each STA200, for example, placed within the Per AP Info field. In other words, the MAP type for each STA200 (information indicating the type of cooperative communication) may be included in Per STA Info (e.g., terminal-specific information).

[0136] Furthermore, AP100 may determine (or change) the format of the MAP type-dependent information (e.g., MAP Type Dependent Info) in the Per STA Info field based on the MAP type of each of the multiple STA200s.

[0137] Figure 18 shows an example of the MAP Trigger frame format according to this embodiment.

[0138] For example, as shown in Figure 18, the Common Info field may contain information about the number of STA200s associated with each of the multiple Shared APs (e.g., AP#1, AP#2, ...) ("# of STAs"). For example, the number of Per STA Info fields to be placed within each Per AP Info field may be determined based on this information about the number of STA200s. For example, as shown in Figure 18, the number of STAs for each Shared AP may be specified in the Common Info field. Alternatively, the Common Info field may specify a common number of STAs for multiple Shared APs (e.g., the maximum number of STAs), and Shared APs with fewer than the specified number of STAs may be padded. Figure 18 shows an example where information about the number of STAs is included in Common Info, but it may also be placed within Per AP Info.

[0139] Furthermore, the MAP type is not limited to being set in the Per STA Info field within the Per AP Info field, as shown in Figure 18; for example, it may be used in combination with the method of Embodiment 1. For example, in Common Info, information about the overall MAP type (e.g., "Total MAP Type") may be used to notify Shared APs that multiple MAP types are mixed. Also, for example, in Per STA Info, information regarding the identification of the MAP type for each Shared AP (MAP Type Index) may be notified to Shared APs based on the overall MAP type (Total MAP Type) notified in Common Info.

[0140] Figure 19 shows a method for specifying the MAP type described above in combination with the method of Embodiment 1. Figure 20 shows an example of the definition of Total MAP Type in the Common Info field and an example of the definition of MAP Type Index in the Per STA Info field.

[0141] As shown in Figure 20, the Total MAP Type may indicate, for example, that multiple MAP types are mixed, and this can be communicated through multiple MAP Type Elements (e.g., MAP Type Element 1, 2, ...). Each MAP Type Element may be set to one of the multiple MAP types (for example, any of 0 to 4 in the example in Figure 20).

[0142] Furthermore, as shown in Figure 20, the MAP Type Index may, for example, notify the MAP Type Element corresponding to the MAP type of each STA200.

[0143] Shared AP may, for example, identify the MAP type corresponding to each STA200 based on the MAP Type Index, according to the following formula. MAP Type Index variant = MAP Type Element (MAP Type Index value + 1)

[0144] For example, in Figure 20, when MAP Type Index = 1, it corresponds to MAP Type Element 2, so Shared AP may identify the MAP type corresponding to the MAP Type Element value of MAP Type Element 2 in Total MAP Type. Note that the relationship between Total MAP Type and MAP Type Index is not limited to the relationship shown in Figure 20; other relationships are also possible.

[0145] Furthermore, in Figures 18 and 19, the Per STA Info field within the Per AP Info field may contain, for example, individual information specific to each STA200. This individual information for each STA200 may include, for example, individual information that is independent of the MAP type (in other words, information common to multiple MAP types) and individual information that is dependent on the MAP type (in other words, information that differs depending on the MAP type).

[0146] Individual information that is not dependent on the MAP type may include, for example, the STA ID, MAP Type, Resource Allocation, and UL / DL Flag.

[0147] Furthermore, the individual information that depends on the MAP type (for example, MAP type dependent information (MAP Type Dependent Info)) may include the following information, for example, as in Embodiment 5. • For C-SR: Shared AP Tx Power, Sharing AP Acceptable Maximum Interference Level, Shared AP Maximum Tx Power, Shared AP Interference Level • For JT or D-MIMO: Transmission Parameter (e.g., MCS, Sequence Number,…) • For CBF: STA ID to Suppress, STA Resource Allocation Info to Suppress • In the case of C-OFDMA: No information available.

[0148] Regarding the STA ID, for example, the Medium Access Control (MAC) address (48 bits) may be used as an instruction for an STA200 that is not associated with a Shared AP. Alternatively, an STA identifier called a "Short ID" with fewer bits than the MAC address may be defined for the STA ID. This reduces the overhead of the STA ID. The Short ID may be defined, for example, included in the Association ID (AID) specified in 11ax, or it may be assigned to the Reserved AID12.

[0149] Furthermore, the field length of Per STA Info may be fixed or variable, as shown in Figures 18 and 19, for example, similar to the Per AP Info field in Embodiment 5. In other words, the size of Per STA Info (individual terminal information) may be common across MAP types or may differ for each MAP type. The complexity of processing and the amount of signaling in the cases where the field length of Per STA Info is fixed or variable are the same as for Per AP Info in Embodiment 5.

[0150] Furthermore, if the Shared AP can identify the field corresponding to each Shared AP in the MAP Trigger frame, for example, when the Shared AP's order is notified to the Shared AP in advance, the Shared AP ID (e.g., AP ID) in the Per AP Info field shown in Figures 18 and 19 may be omitted.

[0151] Thus, in this embodiment, AP100 notifies other AP100s of the MAP type for each of the multiple STA200s using the MAP Type field located within the Per STA Info field in the MAP Trigger frame. AP100 also notifies other AP100s of MAP type dependent information (MAP Type Dependent Info) corresponding to the MAP type. In other words, in the MAP Trigger frame, the format of the MAP type dependent information is changed based on the MAP types of the multiple STA200s.

[0152] By configuring this MAP Trigger frame, AP100 can notify other AP100s of control signals corresponding to each of the multiple MAP types, even when the MAP types differ among multiple STA200s, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in cooperative communication can be improved.

[0153] In this embodiment, we have described, as an example, the case in which a Sharing AP determines resource allocation for each STA associated with (or connected to) a Shared AP. However, the embodiment is not limited to this, and for example, a Shared AP may determine resource allocation for each STA associated with that Shared AP.

[0154] (Embodiment 7) The configuration of AP and STA in this embodiment may be the same as in Embodiment 1.

[0155] In this embodiment, for example, a case is described in which the MAP types differ among multiple Shared APs, but the MAP types of the STA200s under each Shared AP are common.

[0156] AP100 (Sharing AP) may, for example, place Per STA Info for each STA200 within the Per AP Info field, and notify other AP100s (Shared APs) of a MAP type common to all STA200s in a field different from the Per STA Info within the Per AP Info field. In other words, the MAP type (information indicating the type of cooperative communication) for each of the multiple Shared APs may be included in Per AP Info (for example, individual information).

[0157] Furthermore, AP100 may determine (or change) the format of the MAP type dependency information (e.g., MAP Type Dependent Info) within Per STA Info based on the MAP type notified for each of the multiple Shared APs.

[0158] Figure 21 shows an example of the MAP Trigger frame format according to this embodiment.

[0159] For example, as shown in Figure 21, similar to Embodiment 6, Common Info may include information ("# of STAs") regarding the number of STA200s associated with each of the multiple Shared APs (e.g., AP#1, AP#2, ...). For example, the number of Per STA Info fields placed within each Per AP Info field may be determined based on this information regarding the number of STA200s.

[0160] Regarding the method for specifying the number of STAs, as in Embodiment 6, the number of STAs may be specified for each Shared AP, or a common number of STAs (e.g., maximum number of STAs) may be specified for multiple Shared APs, and Shared APs that do not meet the specified number of STAs may be filled with padding. Also, in Figure 21, as in Embodiment 6, information regarding the number of STAs is shown when it is included in Common Info, but it may also be placed in Per AP Info.

[0161] Furthermore, the MAP type is not limited to being set in the Per AP Info field. For example, as in Embodiment 6, the Shared AP may be notified in Common Info that multiple MAP types are mixed by information about the total MAP type (Total MAP Type), and in Per AP Info, information about identifying the MAP type for each Shared AP (MAP Type Index) may be notified to the Shared AP from the total MAP type (Total MAP Type) notified in Common Info.

[0162] In Figure 21, the MAP Type notified by each Per AP Info field may be the same among the STA200s under the Shared AP corresponding to that Per AP Info.

[0163] Furthermore, in Figure 21, the Per STA Info field within the Per AP Info field may contain, for example, individual information specific to STA200. This individual information for each STA200 may include, for example, individual information that is independent of the MAP type (in other words, information common to multiple MAP types) and individual information that is dependent on the MAP type (in other words, information that differs depending on the MAP type).

[0164] Individual information that is not dependent on the MAP type may include, for example, the STA200 ID (STA ID), Resource Allocation, and UL / DL Flag. Individual information that is dependent on the MAP type may be, for example, the same as in Embodiment 6.

[0165] Furthermore, the field length of Per STA Info may be fixed or variable, as shown in Figure 21, for example, similar to the Per AP Info field in Embodiment 5. In other words, the size of Per STA Info (individual terminal information) may be common across MAP types or may differ for each MAP type. The complexity of processing and the amount of signaling in the cases where the field length of Per STA Info is fixed or variable are the same as for Per AP Info in Embodiment 5.

[0166] Furthermore, if the Shared AP can identify the field corresponding to each Shared AP in the MAP Trigger frame, for example, when the Shared AP is notified in advance of the order of the Shared APs, then, similar to Embodiment 6, the Shared AP ID (e.g., AP ID) in the Per AP Info field shown in Figure 21 may be omitted.

[0167] Thus, in this embodiment, AP100 notifies other AP100s of a common MAP type to multiple STA200s under each Shared AP by using the MAP Type field located within the Per AP Info field in the MAP Trigger frame. This reduces the amount of signaling related to MAP type notification.

[0168] Furthermore, AP100 notifies other AP100s of MAP Type Dependent Info, for example, depending on the MAP type. In other words, the format of the MAP Type Dependent Info in the MAP Trigger frame is changed based on the MAP type of the Shared AP.

[0169] By configuring this MAP Trigger frame, AP100 can notify other AP100s of control signals corresponding to each of the multiple MAP types, even when the MAP types differ among multiple Shared APs, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in cooperative communication can be improved.

[0170] (Embodiment 8) The configuration of AP and STA in this embodiment may be the same as in Embodiment 1.

[0171] This embodiment describes, for example, the case where the MAP types differ among multiple STA200 units.

[0172] If the MAP types differ between STA200s, AP100 (Sharing AP) may notify other AP100s (Shared APs) of the MAP type for each STA200, for example, in the Per STA Info (e.g., terminal-specific information) field.

[0173] Furthermore, AP100 may determine (or change) the format of MAP type-dependent information (e.g., MAP Type Dependent Info) within Per STA Info based on the MAP type notified for each of the multiple STA200s.

[0174] Figure 22 shows an example of the MAP Trigger frame format according to this embodiment.

[0175] As shown in Figure 22, in a MAP Trigger frame, the Per STA Info field may be placed in the same hierarchy as the Common Info field. In other words, in Figure 22, the Per AP Info field may be placed in place of the Per AP Info field in the format shown in Figure 1.

[0176] Furthermore, in Figure 22, Per STA Info may contain, for example, individual information specific to STA200. This individual information for each STA200 may include, for example, individual information that is independent of the MAP type (in other words, information common to multiple MAP types) and individual information that is dependent on the MAP type (in other words, information that differs depending on the MAP type).

[0177] Individual information that is not dependent on the MAP type may include, for example, the STA200 ID (STA ID), MAP Type, Resource Allocation, and UL / DL Flag.

[0178] Furthermore, the individual information that differs depending on the MAP type (for example, MAP type dependent information (MAP Type Dependent Info)) may include the following information, for example, as in Embodiment 5. • For C-SR: Shared AP Tx Power, Sharing AP Acceptable Maximum Interference Level, Shared AP Maximum Tx Power, Shared AP Interference Level • For JT or D-MIMO: Transmission Parameter (e.g., MCS, Sequence Number,…) • For CBF: STA ID to Suppress, STA Resource Allocation Info to Suppress • In the case of C-OFDMA: No information available.

[0179] Figure 23 shows examples of MAP type instructions when the MAP type differs for each STA200. In Figure 23, the method of Embodiment 6 and the method of Embodiment 8 are compared as examples.

[0180] Furthermore, Figure 23 shows, as an example, a case where the STA200s under the Shared AP with AP ID 1 are STA1 and STA2, and the STA200s under the Shared AP with AP ID 2 are STA2 and STA3. As shown in Figure 23, STA2 performs cooperative communication with the Shared APs of AP ID 1 and AP ID 2, respectively.

[0181] For example, the method of Embodiment 6 is a method in which the MAP type is specified for each STA200 under the Shared AP by Per STA Info for each Per AP Info. Therefore, in the method of Embodiment 6, for example, the MAP type of the STAs under each Shared AP is specified. In the example shown in Figure 23, the MAP types of STA1 and STA2 under the Shared AP of AP ID 1 are specified in the Per AP Info corresponding to AP ID 1, and the MAP types of STA2 and STA3 under the Shared AP of AP ID 2 are specified in the Per AP Info corresponding to AP ID 2.

[0182] On the other hand, for example, the method of this embodiment 8 is a method of specifying the MAP type for each STA200 by Per STA Info. Therefore, in embodiment 8, for example, the MAP type for each STA200 is specified regardless of the Shared AP to which the STA200 is associated. In the example shown in Figure 23, the MAP types for STA1, STA2, and STA3 are specified in Per STA Info.

[0183] For example, focusing on STA2 (STA ID 2) in Figure 23, in the method of Embodiment 6, the MAP type is specified in two Per AP Info fields corresponding to AP ID 1 and AP ID 2, respectively, whereas in the method of Embodiment 8, the MAP type is specified in one Per STA Info field corresponding to STA ID 2. Therefore, the method of Embodiment 8 can reduce signaling related to the MAP type compared to the method of Embodiment 6.

[0184] Furthermore, the field length of Per STA Info may be fixed or variable, as shown in Figure 22, for example, similar to the Per AP Info field in Embodiment 5. In other words, the size of Per STA Info (individual terminal information) may be common across MAP types or may differ for each MAP type. The complexity of processing and the amount of signaling in the cases where the field length of Per STA Info is fixed or variable are the same as for Per AP Info in Embodiment 5.

[0185] For example, if STA200 is specified in the MAP Trigger frame, each Shared AP can identify the Shared AP with which that STA200 has an association (maintains a connection relationship). Therefore, the Shared AP ID (AP ID) does not need to be notified to the Shared AP in the MAP Trigger frame.

[0186] Furthermore, when specifying STA200 by STA ID in a MAP Trigger frame, a unique STA ID may be assigned to each of the multiple STA200s under the Shared AP. For example, if AID or AID12 is used to assign a unique STA ID, the following methods can be used. A method for centrally managing and sharing an ID space (e.g., a specified range) across the entire system to assign unique AIDs. In this method, for example, a Sharing AP may manage the AIDs and assign them to the STA200 directly or via the Shared AP. A method for negotiating the use of an exclusive area of ​​the AID space for each Shared AP.

[0187] Thus, in this embodiment, AP100 notifies other AP100s of the MAP type for each of the multiple STA200s in the MAP Type field located within the Per STA Info field in the MAP Trigger frame. AP100 also notifies other AP100s of MAP type dependent information (MAP Type Dependent Info) corresponding to the MAP type. In other words, in the MAP Trigger frame, the format of the MAP type dependent information is changed based on the MAP type for each of the multiple STA200s.

[0188] By configuring this MAP Trigger frame, AP100 can notify other AP100s of control signals corresponding to each of the multiple MAP types, even when the MAP types differ among multiple STA200s, thereby improving signaling efficiency. Furthermore, duplication of STA information, such as MAP type, can be suppressed, reducing signaling effort. Therefore, according to this embodiment, communication efficiency in cooperative communication can be improved.

[0189] (Comparison of Embodiments 6, 7, and 8) Figure 24 shows a comparison of the complexity of processing related to the MAP Trigger frame format and the amount of signaling for each of Embodiments 6, 7, and 8.

[0190] For example, Embodiment 6 is a method in which Per STA Info is placed within Per AP Info field, and the MAP type is indicated in Per STA Info.

[0191] Furthermore, for example, Embodiment 7 is a method in which Per STA Info is placed within Per AP Info field, and a common MAP type is indicated for STA200 in a region different from Per STA Info within Per AP Info field.

[0192] Furthermore, for example, Embodiment 8 is a method in which Per AP Info is not provided, and the MAP type is indicated in Per STA Info.

[0193] As shown in Figure 24, the complexity of the process decreases in the order of Embodiments 7, 6, and 8. Also, as shown in Figure 24, the signaling amount decreases in the order of Embodiments 8, 7, and 6.

[0194] For example, if reducing the complexity of the process is a priority, Embodiment 7 may be applied (or selected). Also, for example, if reducing the amount of signaling is a priority, Embodiment 8 may be applied (or selected).

[0195] (Embodiment 9) The configuration of AP and STA in this embodiment may be the same as in Embodiment 1.

[0196] In this embodiment, for example, a method for switching between the methods (or MAP Trigger frame formats) of Embodiment 4 and Embodiment 8 will be described.

[0197] For example, the format type applied in the MAP Trigger frame (e.g., any of the frame formats from Embodiments 4 to 8) may be indicated in the Common Info field.

[0198] Figure 25 shows an example of the MAP Trigger frame format according to this embodiment. In Figure 25, as an example, an example in which the frame format according to Embodiment 4 is applied is shown.

[0199] As shown in Figure 25, the Common Info field may include information indicating the format type of the MAP Trigger frame (e.g., MAP Format Type). AP100 may determine the format of the MAP Format Type field and subsequent fields in the MAP Trigger frame based on the format type indicated in MAP Format Type.

[0200] Furthermore, the format type specified by MAP Format Type can be any of the following formats, for example. • A format for indicating the MAP type of each Shared AP in the MAP type field of Common Info (e.g., Embodiment 4). • A format for indicating the MAP type in the Per AP Info field (e.g., Embodiment 5). • A format for indicating the MAP type in the Per STA Info field within Per AP Info (e.g., Embodiment 6) • A format in which Per STA Info is placed within Per AP Info, and a common MAP type for STA is indicated in a different area from Per STA Info within Per AP Info (for example, Embodiment 7). • A format in which Per AP Info is not provided, and the MAP type is indicated in the Per STA Info field (e.g., Embodiment 8)

[0201] Furthermore, the following methods can be used as criteria for selecting a format type.

[0202] For example, a format with fewer total bits or a format that is easier to process may be selected. For example, if there are multiple formats that can notify the configuration of the MAP type to be set on the Shared AP (e.g., a MAP type common to the Shared AP, a MAP type for each Shared AP, or a MAP type for each STA200), a format with fewer total bits (in other words, the amount of signaling) or a format that is easier to process (in other words, a format with less processing complexity) may be selected. Note that the criteria for selecting the format type are not limited to these, and other criteria may be used, for example, depending on the MAP type settings for each Shared AP and each STA200 under each Shared AP.

[0203] For example, if AP100 (e.g., Sharing AP) has different MAP types for each Shared AP, but the MAP types are the same within each AP (e.g., between subordinate STA200s), then the format of Embodiment 5 may be selected. If the MAP types differ for each Shared AP and each subordinate STA200, then the format of Embodiment 6 may be selected.

[0204] Thus, AP100 may, for example, select (or switch) one of several formats for the MAP Trigger frame based on selection criteria, and send a MAP Trigger frame that includes information indicating the type of the selected format (e.g., MAP Format Type). By switching formats, AP100 can select a format that is easier to process or a format with less signaling, for example, depending on the MAP type settings of each Shared AP and the STA200 under each Shared AP.

[0205] In this embodiment, a method for switching between the MAP Trigger frame formats described in Embodiments 4 to 8 was explained as an example. However, the candidates for the format to be switched are not limited to these, and for example, at least some of the formats from Embodiments 1 to 8 may also be used.

[0206] Furthermore, while this embodiment describes a case where the MAP Trigger frame format is specified by the MAP Format Type as an example, it is not limited to this, and the MAP Trigger frame format (format type) may be implicitly notified to the Shared AP based on other parameters, for example.

[0207] The embodiments of this disclosure have been described above.

[0208] (Other embodiments) In the embodiments described above, the same method (in other words, setting the frame format) may be applied to both DL and UL.

[0209] Furthermore, while an example of notification information regarding MAP in the MAP Trigger frame was described in the above-described embodiment, the information to be notified is not limited to the information shown in the above-described embodiment. For example, other information may be added, or at least a part of the defined information may be deleted.

[0210] Furthermore, in the embodiments described above, examples of definitions for the Frame Control field (e.g., Figure 8), MAP type (e.g., Figures 9 and 10), Trigger Type subfield (e.g., Figures 12 and 14), and Total MAP Type and MAP Type Index (e.g., Figure 20) are shown. However, the definitions are not limited to these examples, and other values ​​may be used.

[0211] Furthermore, although the type of MAP was described using the term "MAP type" in the above embodiment, it is not limited to this term, and other terms may be used. For example, the term "Multi-AP coordination schemes," which is used in the specifications currently being developed for 11be, may also be used.

[0212] Furthermore, in the above embodiment, the AP that instructs cooperative communication and the AP that is instructed to perform cooperative communication were described using the terms "Sharing AP" and "Shared AP," respectively, but the invention is not limited to these terms, and other terms may be used.

[0213] Furthermore, although the above embodiment was described based on the 11be format as an example, the format to which one embodiment of this disclosure is applied is not limited to the 11be format. One embodiment of this disclosure can also be applied, for example, to IEEE 802.11bd (NGV (Next Generation V2X)), which is the next-generation standard to the automotive standard IEEE 802.11p.

[0214] This disclosure can be implemented in software, hardware, or software in conjunction with hardware. Each functional block used in the description of the above embodiments may be implemented in part or in whole as an integrated circuit (LSI), and each process described in the above embodiments may be controlled in part or in whole by a single LSI or a combination of LSIs. An LSI may consist of individual chips, or it may consist of a single chip that includes some or all of the functional blocks. An LSI may have data inputs and outputs. Depending on the degree of integration, LSIs may be referred to as ICs, system LSIs, super LSIs, or ultra LSIs.

[0215] The method of integration is not limited to LSIs; it may also be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, FPGAs (Field Programmable Gate Arrays) that can be programmed after LSI manufacturing, or reconfigurable processors that allow for the reconfiguration of the connections and settings of circuit cells within the LSI, may also be used. This disclosure may be implemented as digital or analog processing.

[0216] Furthermore, if advancements in semiconductor technology or other derived technologies lead to the emergence of integrated circuit technologies that replace LSIs, then naturally, it would be possible to use those technologies to integrate functional blocks. The application of biotechnology, for example, is a possibility.

[0217] This disclosure is applicable to all types of devices, systems, and equipment having communication capabilities (collectively referred to as communication equipment). Communication equipment may include a radio transceiver and a processing / control circuit. A radio transceiver may include a receiver and a transmitter, or both as functions. A radio transceiver (transmitter, receiver) may include an RF (Radio Frequency) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or similar. Non-exclusive examples of communication devices include telephones (mobile phones, smartphones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still / video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth / telemedicine devices, vehicles or mobile transport with communication capabilities (cars, airplanes, ships, etc.), and combinations of the above-mentioned devices.

[0218] Communication devices are not limited to portable or movable devices, but also include all kinds of non-portable or fixed devices, devices, and systems, such as smart home devices (appliances, lighting equipment, smart meters or measuring instruments, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0219] Communication includes data communication via cellular systems, wireless LAN systems, and communication satellite systems, as well as data communication using combinations of these.

[0220] Furthermore, the communication device also includes devices such as controllers and sensors that are connected to or linked to a communication device that performs the communication functions described in this disclosure. For example, this includes controllers and sensors that generate control signals and data signals used by the communication device that performs the communication functions of the communication device.

[0221] Furthermore, communication equipment includes infrastructure facilities such as base stations, access points, and any other devices, devices, and systems that communicate with or control the aforementioned non-limited types of equipment.

[0222] A base station according to one embodiment of the present disclosure comprises a control circuit that determines the format of a control signal based on the type of cooperative communication, and a transmission circuit that transmits the control signal to another base station according to the format.

[0223] In one embodiment of the present disclosure, the control signal includes common information that is common to a plurality of base stations and individual information that is specific to the plurality of base stations, and the control circuit determines the format of at least one of the common information and the individual information based on the type.

[0224] In one embodiment of the present disclosure, the information indicating the type is included in the common information in the field for notifying the type.

[0225] In one embodiment of the present disclosure, the information indicating the type is included in the common information in a field for notifying the trigger type.

[0226] In one embodiment of the present disclosure, in the common information, the information that triggers the cooperative communication is included in a field for notifying the trigger type, and the information indicating the type is included in a field that depends on the trigger type.

[0227] In one embodiment of the present disclosure, the information indicating the type for each of the plurality of base stations is included in the common information.

[0228] In one embodiment of the present disclosure, the information indicating the type for each of the plurality of base stations is included in the individual information.

[0229] In one embodiment of the present disclosure, the size of the individual information is common to all types or differs for each type.

[0230] In one embodiment of the present disclosure, the individual information includes individual terminal information specific to a terminal connected to a base station corresponding to the individual information, and the information indicating the type is included in the individual terminal information.

[0231] In one embodiment of the present disclosure, the control circuit allocates resources to the terminal connected to the other base station.

[0232] In one embodiment of the present disclosure, the control signal includes common information that is common to a plurality of base stations and terminal-specific information that is individual to a plurality of terminals, wherein the information indicating the type of each of the plurality of terminals is included in the terminal-specific information, and the control circuit determines the format of the terminal-specific information based on the type.

[0233] In one embodiment of the present disclosure, the size of the individual terminal information is common to all types, or differs for each type.

[0234] In one embodiment of the present disclosure, the control circuit selects one of a plurality of formats based on selection criteria, and the transmission circuit transmits the control signal including information indicating the type of the selected format.

[0235] In a communication method according to one embodiment of the present disclosure, a base station determines the format of a control signal based on the type of cooperative communication and transmits the control signal to other base stations in the said format.

[0236] All disclosures in the specification, drawings, and abstract contained in the Japanese application 2020-156398, filed on 17 September 2020, are incorporated herein by reference. [Industrial applicability]

[0237] One embodiment of this disclosure is useful for wireless communication systems. [Explanation of Symbols]

[0238] 100 AP 101 Control Unit 102 Control signal generation unit for STA Control signal generation unit for 103 AP 104,203 Transmit signal generation unit 105,201 Wireless Transceiver Unit 106,202 Received signal demodulation / decoding section 200 STA

Claims

1. A receiving circuit that receives a control signal from another base station, which includes parameters independent of the type of cooperative communication and parameters dependent on the type of cooperative communication. A control circuit that performs the cooperative communication based on the aforementioned control signal, It is equipped with, The format of the control signal is determined based on the type. The field length of the parameter, which depends on the type, is variable according to the type. Base station.

2. The information indicating the type is included in the parameter that is independent of the type. The base station according to claim 1.

3. The identification information of the other base stations is included in the parameters that are independent of the type. The base station according to claim 2.

4. The control signal includes individual terminal information for each terminal connected to the base station itself. The information indicating the type is included in the terminal individual information. The base station according to claim 1.

5. The aforementioned control signal includes individual terminal information for each of the multiple terminals. The information indicating the type for each of the aforementioned multiple terminals is included in the individual terminal information. The format of the individual terminal information is determined based on the type. The base station according to claim 1.

6. The size of the individual terminal information is common across all types, or differs for each type. The base station according to claim 5.

7. The format of the control signal is one of several formats selected based on selection criteria. The receiving circuit receives the control signal which includes information indicating the type of the selected format. The base station according to claim 1.

8. The base station is, A control signal including parameters independent of the type of cooperative communication and parameters dependent on the type is received from another base station. Based on the aforementioned control signal, the aforementioned cooperative communication is performed. The format of the control signal is determined based on the type. The field length of the parameter, which depends on the type, is variable according to the type. Communication method.

9. A process that receives a control signal from another base station, which includes parameters independent of the type of cooperative communication and parameters dependent on the type of cooperative communication. A process that performs the aforementioned coordinated communication based on the aforementioned control signal, A control, integrated circuit, The format of the control signal is determined based on the type. The field length of the parameter, which depends on the type, is variable according to the type. Integrated circuit.

Images