Base station, communication method, and integrated circuit

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 technology]

[0002] The Institute of Electrical and Electronics Engineers (IEEE) is currently studying the IEEE 802.11be (hereinafter referred to as "11be") standard for next-generation wireless local area networks (LANs), which will be the successor to the IEEE 802.11ax (hereinafter referred to as "11ax"). For example, IEEE 802.ax is also known as High Efficiency (HE), and IEEE 802.be is also known as Extreme High Throughput (EHT). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] IEEE 802.11-19 / 0804r0, Multi-AP Transmission Procedure [Non-patent document 2] IEEE 802.11-19 / 1788r1, Coordinated OFDMA Operation [Non-patent document 3] IEEE 802.11-19 / 1102r0, A unified transmission procedure for multi-AP coordination [Non-patent document 4] IEEE 802.11-20 / 0033r1, spatially coordinated reuse operation [Non-Patent Document 5] IEEE 802.11-20 / 0576r1, Coordinated Spatial Reuse Protocol Summary of the Invention

[0004] However, the control method of cooperative communication in wireless communication such as wireless LAN has not been fully studied.

[0005] Non-limiting examples of the present disclosure contribute to providing a base station, a communication device, and a communication method that can improve communication efficiency in cooperative communication.

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

[0007] These comprehensive or specific aspects may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a recording medium, or may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a recording medium.

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

[0009] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings. Such advantages and / or benefits may be provided by some of the embodiments and features described in the specification and drawings, but not necessarily all of them may be provided to obtain one or more identical features. [Brief explanation of the drawings]

[0010] [Figure 1] An example of a Multi-AP (MAP) Trigger frame format [Figure 2] A diagram showing an example of MAP configuration [Figure 3]A diagram showing an example of notification information for each MAP type [Figure 4] FIG. 1 is a block diagram showing a configuration example of a part of an AP according to a first embodiment; [Figure 5] FIG. 1 is a block diagram showing an example of the configuration of an AP according to a first embodiment; [Figure 6] FIG. 1 is a block diagram showing an example of the configuration of an STA according to a first embodiment; [Figure 7] FIG. 1 shows an example of a MAP Trigger frame format according to the first embodiment. [Figure 8] Figure showing an example of a Frame Control field definition [Figure 9] A diagram showing an example of a MAP type definition [Figure 10] A diagram showing an example of a MAP type definition [Figure 11] FIG. 10 is a diagram showing an example of a MAP Trigger frame format according to the second embodiment. [Figure 12] A diagram showing an example of a definition of the Trigger Type subfield [Figure 13] FIG. 10 is a diagram showing an example of a MAP Trigger frame format according to the third embodiment. [Figure 14] A diagram showing an example of a definition of the Trigger Type subfield [Figure 15] FIG. 10 shows an example of a MAP Trigger frame format according to the fourth embodiment. [Figure 16] FIG. 13 shows an example of a MAP Trigger frame format according to the fifth embodiment. [Figure 17] FIG. 10 is a diagram showing a comparative example of the fourth and fifth embodiments. [Figure 18] FIG. 20 shows an example of a MAP Trigger frame format according to the sixth embodiment. [Figure 19] FIG. 20 shows an example of a MAP Trigger frame format according to the sixth embodiment. [Figure 20] A diagram showing an example of the definition of Total MAP Type and MAP Type Index [Figure 21]FIG. 20 shows an example of a MAP Trigger frame format according to the seventh embodiment. [Figure 22] FIG. 20 shows an example of a MAP Trigger frame format according to the eighth embodiment. [Figure 23] A diagram showing an example of MAP type indication when the MAP type differs for each Station (STA) [Figure 24] FIG. 10 is a diagram showing a comparative example of the sixth, seventh, and eighth embodiments. [Figure 25] FIG. 20 shows an example of a MAP Trigger frame format according to the ninth embodiment. DETAILED DESCRIPTION OF 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 "cooperative communication") has been considered, in which multiple access points (APs: Access Point, also called "base stations") cooperate to send and receive data between each terminal (STAs: Station, also called "non-AP STAs") (for example, Non-Patent Documents 1 to 5).

[0013] Multiple types of cooperative communication (e.g., communication types, hereinafter referred to as "MAP types") are being considered for 11be. For example, the following MAP types are listed: 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] JT includes, for example, a method of transmitting the same signal from multiple cooperating APs and a method of transmitting different transmission streams from multiple cooperating APs. The method of 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, the method of transmitting the same signal from multiple cooperating APs is defined as "JT," and the method of transmitting different transmission streams from multiple cooperating APs is defined as "D-MIMO."

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

[0017] 1 is a diagram illustrating an example of a MAP Trigger frame format based on the Trigger frame format in 11ax. As illustrated in FIG. 1, for example, “Per AP Info” which is information (or a field) for each AP may be defined.

[0018] FIG. 2 is a diagram showing an example of the configuration of APs and STAs (an example of the configuration of MAPs) that perform cooperative communication.

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

[0020] 2 shows an example in which the Sharing AP and the Shared AP are different APs, but the present invention is not limited to this. For example, one of the Shared APs may also function as the Sharing AP. For example, a MAP Trigger frame may be transmitted from the Sharing AP to the Shared AP. By transmitting the MAP Trigger frame, the Sharing AP may instruct the Shared AP to control (e.g., start) cooperative communication. The MAP Trigger frame may include, for example, information for each Shared AP (e.g., Per AP Info).

[0021] In one embodiment of the present disclosure, a method for controlling a plurality of MAP types in a MAP Trigger frame in an integrated and efficient manner (for example, setting the MAP Trigger frame format) will be described.

[0022] [Wireless communication system configuration] The wireless communication system according to this embodiment may include a plurality of APs 100 and STAs 200. The AP 100 may have the functions of both a Sharing AP and a Shared AP, or may have the functions of only one of them, for example.

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

[0024] Furthermore, the AP 100 that is a Sharing AP may determine (or change) the format of the MAP Trigger frame based on the MAP type, for example, and transmit the MAP Trigger frame in the determined format to another AP 100 that is a Shared AP.

[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 that are 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 interpreted as "based on" the MAP type, for example. The term "independent" from the MAP type may be interpreted as other terms such as "not based on" or "independent" from the MAP type, for example.

[0026] Examples of parameters that do not depend on the MAP type include the following parameters: BW (bandwidth), MAP type (information indicating the type of cooperative communication), Shared AP ID (identification information of the Shared AP), uplink (UL) / downlink (DL) Flag (information indicating either UL or DL), Resource Allocation

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

[0028] In FIG. 3, the parameters marked with a "●" 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 FIG. 3, transmission parameters such as a Modulation and Coding Scheme (MCS), a Sequence Number, and a Spatial Stream Index may be notified.

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

[0032] Also, for example, in the MAP type "C-OFDMA" shown in FIG. 3, the above-described parameters depending on the MAP type do not need to be notified.

[0033] The above-mentioned parameters independent of the MAP type and parameters dependent on the MAP type are merely examples, and other parameters may be used.

[0034] 4 is a block diagram illustrating a configuration example of a portion of an AP 100 according to an embodiment of the present disclosure. In the AP 100 illustrated in FIG. 4, a control unit 101 (e.g., a control circuit) determines the format of a control signal (e.g., a MAP Trigger frame) based on the type of cooperative communication (e.g., a MAP type). A wireless transceiver 105 (e.g., a transmission circuit) transmits the control signal to another base station (e.g., a Shared AP) in the format described above.

[0035] (Embodiment 1) [AP100 configuration example] Fig. 5 is a block diagram showing an example configuration of AP 100. AP 100 shown in Fig. 5 may include, for example, a control unit 101, a STA-directed control signal generation unit 102, an AP-directed control signal generation unit 103, 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 a MAP Trigger frame. For example, when the AP 100 is a Sharing AP, the control unit 101 may control the generation of a control signal (for example, a MAP Trigger frame) for another AP 100 (for example, a Shared AP). For example, the control unit 101 may determine the MAP Trigger frame format based on the MAP type. Furthermore, when the AP 100 is a Shared AP, the control unit 101 may identify the format of the MAP Trigger frame transmitted from another AP 100 (for example, a Sharing AP) based on information about the MAP type.

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

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

[0039] The STA-directed control signal generating unit 102 may generate a control signal (eg, a trigger frame) for the STA 200 and output the generated control signal to the transmission signal generating unit 104, for example.

[0040] The AP-directed control signal generating unit 103 may generate, for example, a control signal (for example, a MAP Trigger frame) for the AP 100. For example, the AP-directed control signal generating unit 103 may generate the control signal based on control information input from the control unit 101 and information input from the received signal demodulating and decoding unit 106.

[0041] The control signal for the AP 100 may include, for example, time and frequency resource information (for example, RU allocation information for uplink cooperative communication, TXOP, LENGTH, etc.) as well as at least one of parameters related to cooperative communication (for example, the above-mentioned MAP type, parameters independent of the MAP type, or parameters dependent on the MAP type). The AP-directed control signal generating unit 103 outputs the generated control signal to, for example, the transmission signal generating unit 104.

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

[0043] The radio transmission / reception unit 105 performs radio transmission processing such as D / A conversion and up-conversion to a carrier frequency on the transmission signal input from the transmission signal generation unit 104, and transmits the signal after radio transmission processing via an antenna.

[0044] For example, when the AP 100 receives an uplink signal transmitted from the STA 200 or a control signal transmitted from another AP 100, the AP 100 may operate as follows.

[0045] A radio signal received via an antenna is input to the radio transmission / reception unit 105. The radio transmission / reception unit 105 performs radio reception processing, such as down-conversion of the carrier frequency, on the received radio signal, and outputs the signal after radio reception processing to the received signal demodulation / decoding unit 106.

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

[0047] [STA200 configuration example] Fig. 6 is a block diagram showing an example configuration of STA 200 according to this embodiment. STA 200 shown in Fig. 6 may include, for example, a radio transmission / reception unit 201, a received signal demodulation / decoding unit 202, and a transmission signal generation unit 203.

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

[0049] The received signal demodulation and decoding unit 202 may, for example, perform processing such as autocorrelation processing on the signal input from the radio transmission / reception unit 201 to extract the received radio frame. The received signal demodulation and decoding unit 202 may, for example, demodulate and decode a control signal (e.g., a trigger frame) included in the extracted radio frame to obtain uplink transmission control parameters. The received signal demodulation and decoding unit 202 may, for example, output the obtained uplink transmission control parameters to the transmission signal generation unit 203.

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

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

[0052] In this embodiment, for example, a case will be described in which the MAP type of a plurality of (for example, all) Shared APs is the same.

[0053] When the MAP type of multiple Shared APs is common, the AP 100 (Sharing AP) may notify the other APs 100 of the MAP type in a "MAP Type" field located in a common information (e.g., Common Info) field containing information common to multiple Shared APs in the MAP Trigger frame. In other words, the MAP type (information indicating the type of cooperative communication) may be included in a field in Common Info for notifying the MAP type. Note that "configuration" may be replaced with other terms such as "mapping" or "configuration."

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

[0055] FIG. 7 is a diagram showing an example of a MAP Trigger frame format according to this embodiment.

[0056] For example, the fact that the frame type is "MAP Trigger" may be notified to the Shared AP by the "Frame Control" field (e.g., Type and Subtype subfields). Fig. 8 is a diagram showing an example of the definition of Type and Subtype subfields in the Frame Control field. Fig. 8 shows an excerpt of the Control type in 11ax as an example. In the example shown in Fig. 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 Fig. 8, and the Subtype value of MAP Trigger may be defined in another value (e.g., another reserved value).

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

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

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

[0060] 9 and 10 are diagrams showing examples of MAP type definitions. For example, the MAP type definition example shown in FIG. 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 FIG. 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 together and assigned an index. For example, MAP type definition example 2 can reduce the MAP type table size compared to definition example 1.

[0061] 7, for example, notification information (or individual information) individual to the Shared AP may be set in the Per AP Info field. The individual information for each Shared AP may be, for example, information common to STA 200 associated (or connected) to the Shared AP. The individual information for each Shared AP may include, for example, individual information independent of the MAP type (or individual information common to a plurality of MAP types) and individual information dependent on the MAP type (or individual information MAP Type Dependent Info that differs depending on the MAP type).

[0062] The individual information independent of the MAP type may include, for example, a Shared AP ID, a Resource Allocation, and an UL / DL Flag.

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

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

[0065] Also, 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 the 11ax HE-SIG-B, or a method similar to the method extended for 11be.

[0066] Also, for example, in the RU Allocation subfield of 11ax, RUs with a size of less than 20 MHz are defined, but this definition is not limiting, and for example, a size of 20 MHz or more may be defined in the Resource Allocation.

[0067] As described above, in this embodiment, the AP 100 (Sharing AP) notifies other APs 100 (Shared APs) of the MAP type by using the MAP type field arranged in the Common Info field in the MAP Trigger frame, and notifies the other APs 100 of MAP type-dependent common information (for example, MAP Type Dependent Common Info) and MAP type-dependent information (MAP Type Dependent Info) according to the 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 setting this MAP Trigger frame, the AP 100 can notify other APs 100 of control signals corresponding to each of a plurality of MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, it is possible to improve communication efficiency in cooperative communication.

[0069] (Embodiment 2) The configurations of the AP and STA according to this embodiment may be the same as those in the first embodiment.

[0070] In this embodiment, for example, as in the first embodiment, a case will be described in which the MAP type of a plurality of (for example, all) Shared APs is the same.

[0071] When the MAP type of multiple Shared APs is common, the AP 100 (Sharing AP) may notify the other APs 100 (Shared APs) of the MAP type of the MAP Trigger in, for example, a Trigger Type field (similar to the UL Trigger of 11ax, for example). In other words, the MAP type (information indicating the type of cooperative communication) may be included in a field for notifying the Trigger type in Common Info.

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

[0073] Fig. 11 is a diagram showing an example of a MAP Trigger frame format according to this embodiment, and Fig. 12 is a diagram showing an example of a definition of the Trigger Type subfield.

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

[0075] In FIG. 11, common information (for example, BW) that does not depend on the MAP type in the Common Info field may be the same as in the first embodiment, for example.

[0076] In addition, in FIG. 11, the trigger type dependent common information (for example, trigger type dependent common info) in the common info field may be the same as the map type dependent common information (map type dependent common info) in the first embodiment.

[0077] In addition, in FIG. 11, individual information that does not depend on the MAP type in the Per AP Info field (for example, Shared AP ID, Resource Allocation, and UL / DL Flag) may be the same as in the first embodiment, for example.

[0078] Also, in FIG. 11, the trigger type dependent information (for example, Trigger Type Dependent Info) in the Per AP Info field may be the same as the MAP type dependent information (for example, MAP Type Dependent Info) in the first embodiment.

[0079] As described above, in this embodiment, the AP 100 notifies other APs 100 of the MAP type of the MAP Trigger by using the Trigger Type field in the MAP Trigger frame. Furthermore, the AP 100 notifies other APs 100 of, for example, Trigger Type Dependent Common Info and Trigger Type Dependent Info according to the MAP type notified in the Trigger Type field. In other words, in the MAP Trigger frame, the formats of the Trigger Type Dependent Common Information and Trigger Type Dependent Information are changed based on the MAP type, as in the first embodiment.

[0080] By setting this MAP Trigger frame, the AP 100 can notify other APs 100 of control signals corresponding to each of a plurality of MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, it is possible to improve communication efficiency in cooperative communication.

[0081] (Embodiment 3) The configurations of the AP and STA according to this embodiment may be the same as those in the first embodiment.

[0082] In this embodiment, for example, as in the first embodiment, a case will be described in which the MAP type of a plurality of (for example, all) Shared APs is the same.

[0083] When the MAP type of multiple Shared APs is common, the AP 100 (Sharing AP) may notify the other APs 100 (Shared APs) of the MAP Trigger, for example, in a Trigger Type field (similar to the UL Trigger of 11ax). Also, the AP 100 may notify the MAP type, for example, in a Trigger Type Dependent Common Info field. In other words, in the Common Info, information that triggers MAP coordination (cooperative communication) is included in a field for notifying the trigger type, and the MAP type (information indicating the type of cooperative communication) is included in a field that depends on the Trigger type.

[0084] In addition, AP100 may determine (or change) the format of the MAP type dependent common information (e.g., MAP Type Dependent Common Info) in the Common Info field and the format of 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] Fig. 13 is a diagram showing an example of a MAP Trigger frame format according to this embodiment, and Fig. 14 is a diagram showing an example of a definition of the Trigger Type subfield.

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

[0087] Also, for example, a MAP Type field may be placed in Trigger Type Dependent Common Info in the Common Info field. The Shared AP may identify (or recognize or determine) the MAP type in the MAP Type field in the Common Info field of a MAP Trigger frame whose Trigger Type is MAP.

[0088] In FIG. 13, common information (for example, BW) that does not depend on the MAP type in the Common Info field may be the same as in the first embodiment, for example.

[0089] In addition, in FIG. 13, MAP type dependent common information (for example, MAP Type Dependent Common Info) in the Common Info field may be the same as the MAP type dependent common information (MAP Type Dependent Common Info) in the first embodiment.

[0090] In addition, in FIG. 13, individual information that does not depend on the MAP type in the Per AP Info field (for example, Shared AP ID, Resource Allocation, and UL / DL Flag) may be the same as in the first embodiment, for example.

[0091] Also, in FIG. 13, the MAP type dependent information (for example, Trigger Type Dependent Info) in the Per AP Info field may be the same as the MAP type dependent information (for example, MAP Type Dependent Info) in the first embodiment.

[0092] As described above, in the present embodiment, the AP 100 notifies other APs 100 that the MAP is triggered by the Trigger Type field in the MAP Trigger frame, and notifies other APs 100 of the MAP type in the MAP Type field in the Trigger Type Dependent Common Info. Furthermore, the AP 100 notifies other APs 100 of, for example, Trigger Type Dependent Common Info and Trigger Type Dependent Info according to the notified MAP type. In other words, in the MAP Trigger frame, the formats of the Trigger Type Dependent Common Information and Trigger Type Dependent Information are changed based on the MAP type.

[0093] By setting this MAP Trigger frame, the AP 100 can notify other APs 100 of control signals corresponding to each of a plurality of MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, it is possible to improve communication efficiency in cooperative communication.

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

[0095] Also, for example, in terms of signaling of the MAP Trigger frame formats of the first, second and third embodiments, there is a difference in that notification of the 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 Third embodiment: Trigger Type in Common Info and MAP Type in Trigger Type Dependent Common Info

[0096] Therefore, for example, the format to be applied among the MAP Trigger frame formats of the first, second and third embodiments may be determined in consideration of a definition area used for a purpose other than the MAP setting.

[0097] For example, if there are more unused areas (e.g., reserved areas) in the definition area of ​​the Frame Control subtype (e.g., FIG. 8) than in the definition area of ​​the Trigger Type subfield (e.g., FIG. 12 or FIG. 14), the MAP Trigger frame format of embodiment 1 may be applied. On the other hand, if there are more unused areas (e.g., reserved areas) in the definition area of ​​the Trigger Type subfield (e.g., FIG. 12 or FIG. 14) than in the definition area of ​​the Frame Control subtype (e.g., FIG. 8), the MAP Trigger frame format of embodiment 2 or 3 may be applied.

[0098] (Fourth embodiment) The configurations of the AP and STA according to this embodiment may be the same as those in the first embodiment.

[0099] In this embodiment, for example, a case where the MAP types of multiple shared APs are different will be described.

[0100] When the MAP types of the shared APs are different, the AP 100 (sharing AP) may notify the other APs 100 (shared APs) of the MAP types of each of the multiple shared APs in a MAP Type field arranged in the Common Info field. In other words, the MAP types of each of the multiple shared APs (information indicating the type of cooperative communication) may be included in Common Info (for example, a MAP Type field).

[0101] In addition, 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 multiple Shared APs, for example.

[0102] FIG. 15 is a diagram showing an example of a MAP Trigger frame format according to this embodiment.

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

[0104] The fact that the frame shown in FIG. 15 is a MAP Trigger may be notified to the Shared AP by Frame Control as in the first embodiment, or by Trigger Type as in the second or third embodiment.

[0105] In addition, in FIG. 15, common information (for example, BW) that does not depend on the MAP type in the Common Info field may be the same as in the first embodiment, for example.

[0106] In addition, in FIG. 15, MAP type dependent common information (for example, MAP Type Dependent Common Info) in the Common Info field may be the same as the MAP type dependent common information (MAP Type Dependent Common Info) in the first embodiment.

[0107] For example, if at least one of the MAP types of the 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 any of the MAP types of the multiple Shared APs notified by the MAP Trigger frame is a type other than "C-SR" (e.g., C-OFDMA, JT, CBF, or D-MIMO), the MAP type-dependent common information field may not include notification information.

[0108] In addition, in FIG. 15, individual information that does not depend on the MAP type in the Per AP Info field (for example, Shared AP ID, Resource Allocation, and UL / DL Flag) may be the same as in the first embodiment, for example.

[0109] Also, in FIG. 15, the MAP type dependent information (for example, MAP Type Dependent Info) in the Per AP Info field may be the same as the MAP type dependent information (for example, MAP Type Dependent Info) in the first embodiment.

[0110] As described above, in this embodiment, the AP 100 notifies other APs 100 of the MAP type for each of multiple Shared APs by using a MAP Type field arranged in the Common Info field in the MAP Trigger frame. Also, the AP 100 notifies other APs 100 of, for example, MAP Type Dependent Common Info and MAP Type Dependent Info according to the MAP type. In other words, in the MAP Trigger frame, the formats of the MAP type dependent common information and MAP type dependent information are changed based on the MAP types of the multiple Shared APs.

[0111] By setting this MAP Trigger frame, even if the MAP types are different among multiple Shared APs, the AP 100 can notify other APs 100 of control signals corresponding to each of the multiple MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, it is possible to improve communication efficiency in cooperative communication.

[0112] (Embodiment 5) The configurations of the AP and STA according to this embodiment may be the same as those in the first embodiment.

[0113] In this embodiment, for example, a case where the MAP types of multiple shared APs are different will be described as in the fourth embodiment.

[0114] When the MAP types of the shared APs are different, the AP 100 (sharing AP) may notify the other APs 100 (shared APs) of the MAP types of the multiple shared APs, for example, in the Per AP Info field. In other words, the MAP types of the multiple shared APs (information indicating the type of cooperative communication) may be included in the Per AP Info (for example, individual information).

[0115] Furthermore, the AP 100 may determine (or change) the format of MAP type dependent information (for example, MAP Type Dependent Info) based on the MAP type notified for each of a plurality of Shared APs, for example.

[0116] FIG. 16 is a diagram showing an example of a MAP Trigger frame format according to this embodiment.

[0117] For example, as shown in FIG. 16, the MAP type of each of a plurality of shared APs may be set (in other words, indicated) in a MAP Type field in the Per AP Info field.

[0118] The fact that the frame shown in FIG. 16 is a MAP Trigger may be notified to the Shared AP by Frame Control as in the first embodiment, or by Trigger Type as in the second or third embodiment.

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

[0120] 16, for example, individual information for each shared AP (in other words, notification information common to STAs 200 associated with the shared AP) may be set in the Per AP Info field. The individual information for each shared AP may include, for example, individual information independent of the MAP type and individual information dependent on the MAP type.

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

[0122] Furthermore, individual information that depends on the MAP type (for example, MAP Type Dependent Info) may include, for example, the following information: 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 Parameters (e.g., MCS, Sequence Number, etc.) For CBF: STA ID to Suppress, STA Resource Allocation Info to Suppress For C-OFDMA: No information

[0123] Here, the Per AP Info field length may be, for example, a fixed length or a variable length. In other words, the size of Per AP Info (individual information) may be common among 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 (e.g., made uniform) based on the format of the MAP type with the largest size (e.g., the largest size) among the Per AP Info field lengths corresponding to each MAP type. 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 a Reserved field.

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

[0126] Also, for example, if the Per AP Info field length is variable, the length of the MAP Type Dependent Info may be set based on the MAP type. The Shared AP may specify 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 according to the MAP type set for each Shared AP is notified, thereby reducing the amount of signaling compared to when the Per AP Info field is fixed length.

[0128] As described above, in this embodiment, the AP 100 notifies other APs 100 of the MAP type for each of multiple Shared APs by using a MAP Type field arranged in the Per AP Info field in the MAP Trigger frame. Also, the AP 100 notifies other APs 100 of, for example, MAP type dependent information (MAP Type Dependent Info) according 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 Shared APs.

[0129] By setting this MAP Trigger frame, even if the MAP types are different among multiple Shared APs, the AP 100 can notify other APs 100 of control signals corresponding to each of the multiple MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, it is possible to improve communication efficiency in cooperative communication.

[0130] (Comparison of Embodiments 4 and 5) Fig. 17 is a diagram showing a comparison example of the processing complexity and signaling amount related to the MAP Trigger frame format of each of Embodiments 4 and 5. Note that Fig. 17 shows the case where the Per AP Info field length is variable for Embodiment 4, and shows the cases where the Per AP Info field length is fixed and variable for Embodiment 5.

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

[0132] For example, when emphasis is placed on reducing the complexity of processing, the format in which the Per AP Info field length is fixed according to the fifth embodiment may be applied (or selected). Also, when emphasis is placed on reducing the amount of signaling, the format in which the Per AP Info field length is variable according to the fifth embodiment may be applied (or selected). Also, when emphasis is placed on balancing the reduction in complexity of processing and the reduction in the amount of signaling, the format in the fourth embodiment may be applied (or selected).

[0133] (Embodiment 6) The configurations of the AP and STA according to this embodiment may be the same as those in the first embodiment.

[0134] In this embodiment, for example, a case will be described in which the MAP types are different among the multiple STAs 200. Note that this embodiment assumes, as an example, a case in which a Sharing AP determines resource allocation for each STA associated (or connected) to a Shared AP.

[0135] When the MAP types of the STAs 200 are different, the AP 100 (Sharing AP) may notify the Shared AP of the MAP type in, for example, a "Per STA Info" field (also called terminal-specific information), which is information specific to each STA 200 arranged in the Per AP Info field. In other words, the MAP type (information indicating the type of cooperative communication) for each STA 200 may be included in Per STA Info (for example, terminal-specific information).

[0136] In addition, the AP 100 may determine (or change) the format of MAP type dependent information (eg, MAP Type Dependent Info) in the Per STA Info field based on the MAP type for each of the multiple STAs 200, for example.

[0137] FIG. 18 is a diagram showing an example of a MAP Trigger frame format according to the present embodiment.

[0138] For example, as shown in FIG. 18, the Common Info field may include information ("# of STAs") regarding the number of STAs 200 associated with each of multiple Shared APs (e.g., AP#1, AP#2, ...). For example, the number of Per STA Info fields to be placed in each Per AP Info field may be determined based on the information regarding the number of STAs 200. For example, as shown in FIG. 18, the Common Info field may specify the number of STAs for each Shared AP. Alternatively, the Common Info field may specify the number of STAs common to multiple Shared APs (e.g., the maximum number of STAs), and any Shared AP that does not meet the specified number of STAs may be filled with padding. FIG. 18 illustrates a case where information regarding the number of STAs is included in Common Info, but the information may also be placed in Per AP Info.

[0139] Furthermore, the MAP type is not limited to being set in the Per STA Info field in the Per AP Info field as shown in Fig. 18, and may be used in conjunction with, for example, the method of embodiment 1. For example, the presence of a mixture of multiple MAP types may be notified to the Shared AP by information on the total MAP type (e.g., "Total MAP Type") in Common Info. Also, for example, in Per STA Info, information on 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.

[0140] Fig. 19 is a diagram showing a method for specifying the above-mentioned MAP type, which is used in combination with the method of embodiment 1. Fig. 20 is a diagram showing an example of the definition of the Total MAP Type in the Common Info field, and an example of the definition of the MAP Type Index in the Per STA Info field.

[0141] As shown in Fig. 20, the presence of a plurality of MAP types may be notified by a plurality of MAP Type Elements (e.g., MAP Type Elements 1, 2, ...) depending on the Total MAP Type. For example, any one of a plurality of MAP types (0 to 4 in the example of Fig. 20) may be set in each MAP Type Element.

[0142] Also, as shown in FIG. 20, for example, a MAP Type Element corresponding to the MAP type of each STA 200 may be notified by the MAP Type Index.

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

[0144] For example, in Fig. 20, when MAP Type Index = 1, it corresponds to MAP Type Element 2, so the 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 Fig. 20 and may be other relationships.

[0145] 18 and 19, Per STA Info in the Per AP Info field may be set with, for example, individual information that is individual to the STA 200. The individual information for each STA 200 may include, for example, individual information that is independent of the MAP type (in other words, information that is common to a plurality of MAP types) and individual information that is dependent on the MAP type (in other words, information that differs depending on the MAP type).

[0146] The individual information independent of the MAP type may include, for example, the ID of the STA (STA ID), the MAP Type, the Resource Allocation, and the UL / DL Flag.

[0147] Furthermore, individual information that depends on the MAP type (for example, MAP Type Dependent Info) may include, for example, the following information, as in the fifth embodiment. 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 Parameters (e.g., MCS, Sequence Number, etc.) For CBF: STA ID to Suppress, STA Resource Allocation Info to Suppress For C-OFDMA: No information

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

[0149] Also, the field length of Per STA Info may be fixed or variable, as in the Per AP Info field of embodiment 5, as shown in Figures 18 and 19. In other words, the size of Per STA Info (terminal individual information) may be common among MAP types, or may differ for each MAP type. The processing complexity and signaling volume when the field length of Per STA Info is fixed or variable are the same as those of Per AP Info of embodiment 5.

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

[0151] As described above, in this embodiment, the AP 100 notifies other APs 100 of the MAP type for each of the multiple STAs 200 by using a MAP Type field arranged in the Per STA Info field in the MAP Trigger frame. Also, the AP 100 notifies other APs 100 of, for example, MAP type dependent information (MAP Type Dependent Info) according 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 STAs 200.

[0152] By setting this MAP Trigger frame, the AP 100 can notify other APs 100 of control signals corresponding to each of the multiple MAP types, even if the MAP types are different among the multiple STAs 200. Therefore, according to this embodiment, it is possible to improve communication efficiency in cooperative communication.

[0153] In this embodiment, as an example, a case has been described in which a Sharing AP determines resource allocation for each STA that associates (or connects) to a Shared AP, but this is not limited to this, and for example, a Shared AP may determine resource allocation for each STA that associates to the Shared AP.

[0154] (Embodiment 7) The configurations of the AP and STA according to this embodiment may be the same as those in the first embodiment.

[0155] In this embodiment, for example, a case will be described in which the MAP types of a plurality of shared APs are different, and the MAP types of the STAs 200 subordinate to each shared AP are the same.

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

[0157] Furthermore, the AP 100 may determine (or change) the format of MAP type dependent information (for example, MAP Type Dependent Info) in Per STA Info based on the MAP type notified for each of multiple Shared APs, for example.

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

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

[0160] As for the method of specifying the number of STAs, the number of STAs may be specified for each Shared AP, as in embodiment 6, or a number of STAs common to multiple Shared APs (for example, the maximum number of STAs) may be specified, and Shared APs with less than the specified number of STAs may be filled with padding. Also, as in embodiment 6, Fig. 21 shows the case where information on the number of STAs 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 that multiple MAP types are mixed using information regarding the total MAP type (Total MAP Type) in Common Info, and in Per AP Info, information regarding the identification of 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 FIG. 21, the MAP type notified by each Per AP Info field may be common among the STAs 200 under the Shared AP corresponding to the Per AP Info.

[0163] 21, Per STA Info in the Per AP Info field may be set with, for example, individual information specific to the STA 200. The individual information for each STA 200 may include, for example, individual information independent of the MAP type (in other words, information common to a plurality of MAP types) and individual information dependent on the MAP type (in other words, information that differs depending on the MAP type).

[0164] The individual information independent of the MAP type may include, for example, the ID (STA ID), Resource Allocation, and UL / DL Flag of the STA 200. The individual information dependent on the MAP type may be the same as in the sixth embodiment.

[0165] Also, the field length of Per STA Info may be fixed or variable, as in the Per AP Info field of the fifth embodiment, as shown in Fig. 21. In other words, the size of Per STA Info (terminal individual information) may be common to all MAP types, or may differ for each MAP type. The complexity of processing and the amount of signaling required when the field length of Per STA Info is fixed or variable is the same as that of Per AP Info of the fifth embodiment.

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

[0167] In this manner, in this embodiment, the AP 100 notifies other APs 100 of the MAP type common to the multiple STAs 200 under each Shared AP by using the MAP Type field arranged in the Per AP Info field in the MAP Trigger frame. This reduces the amount of signaling related to the notification of the MAP type.

[0168] Furthermore, the AP 100 notifies, for example, MAP type dependent information (MAP Type Dependent Info) according to the MAP type to other APs 100. In other words, in the MAP Trigger frame, the format of the MAP type dependent information is changed based on the MAP type of the Shared AP.

[0169] By setting this MAP Trigger frame, even if the MAP types are different among multiple Shared APs, the AP 100 can notify other APs 100 of control signals corresponding to each of the multiple MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, it is possible to improve communication efficiency in cooperative communication.

[0170] (Embodiment 8) The configurations of the AP and STA according to this embodiment may be the same as those in the first embodiment.

[0171] In this embodiment, for example, a case where the MAP types of the plurality of STAs 200 are different will be described.

[0172] When the MAP types of the STAs 200 are different, the AP 100 (Sharing AP) may notify the other APs 100 (Shared APs) of the MAP type for each STA 200 in, for example, a Per STA Info (for example, terminal individual information) field.

[0173] Furthermore, the AP 100 may determine (or change) the format of MAP type dependent information (for example, MAP Type Dependent Info) in Per STA Info based on the MAP type notified for each of the multiple STAs 200, for example.

[0174] FIG. 22 is a diagram showing an example of a MAP Trigger frame format according to this embodiment.

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

[0176] 22, Per STA Info may be set with, for example, individual information for each STA 200. The individual information for each STA 200 may include, for example, individual information that is independent of the MAP type (in other words, information common to a plurality of MAP types) and individual information that is dependent on the MAP type (in other words, information that differs depending on the MAP type).

[0177] The individual information independent of the MAP type may include, for example, the ID (STA ID) of the STA 200, the MAP Type, the Resource Allocation, and the UL / DL Flag.

[0178] Furthermore, individual information that differs depending on the MAP type (for example, MAP Type Dependent Info) may include, for example, the following information, as in the fifth embodiment. 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 Parameters (e.g., MCS, Sequence Number, etc.) For CBF: STA ID to Suppress, STA Resource Allocation Info to Suppress For C-OFDMA: No information

[0179] Fig. 23 is a diagram showing an example of specifying a MAP type when the MAP type differs for each STA 200. In Fig. 23, the method of the sixth embodiment and the method of the eighth embodiment are compared as an example.

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

[0181] For example, the method of the sixth embodiment is a method in which the MAP type is indicated for each STA 200 under the Shared AP by the Per STA Info for each Per AP Info. Therefore, in the method of the sixth embodiment, for example, the MAP types of the STAs under each Shared AP are indicated. In the example shown in Fig. 23, the MAP types of STA1 and STA2 under the Shared AP with AP ID 1 are indicated in the Per AP Info corresponding to AP ID 1, and the MAP types of STA2 and STA3 under the Shared AP with AP ID 2 are indicated in the Per AP Info corresponding to AP ID 2.

[0182] On the other hand, for example, the method of the eighth embodiment is a method of indicating a MAP type for each STA 200 by Per STA Info. Therefore, in the eighth embodiment, for example, a MAP type for each STA 200 is indicated regardless of the Shared AP with which the STA 200 is associated. In the example shown in Fig. 23, the MAP type for each of STA1, 2, and 3 is indicated in Per STA Info.

[0183] For example, focusing on STA2 (STA ID 2) in Fig. 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, according to the method of embodiment 8, it is possible to reduce signaling related to the MAP type compared to the method of embodiment 6.

[0184] Also, the field length of Per STA Info may be fixed or variable, as in the Per AP Info field of the fifth embodiment, as shown in Fig. 22. In other words, the size of Per STA Info (terminal individual information) may be common to all MAP types, or may differ for each MAP type. The complexity of processing and the amount of signaling required when the field length of Per STA Info is fixed or variable is the same as that of Per AP Info of the fifth embodiment.

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

[0186] Furthermore, when the STA 200 is specified by the STA ID in the MAP Trigger frame, a unique STA ID may be assigned to each of the STAs 200 under the control of multiple Shared APs. For example, when AID or AID12 is used to assign a unique STA ID, the following method may be used. A method of centrally managing an ID space (e.g., a specified range) so that it is shared across the entire system and unique AIDs are assigned. In this method, for example, the Sharing AP may manage the AIDs and assign them to the STAs 200 directly or via the Shared AP. A method for negotiating the use of an exclusive region of the AID space in each Shared AP.

[0187] As described above, in this embodiment, the AP 100 notifies other APs 100 of the MAP type for each of the plurality of STAs 200 in a MAP Type field arranged in a Per STA Info field in a MAP Trigger frame. Also, the AP 100 notifies other APs 100 of, for example, MAP type dependent information (MAP Type Dependent Info) according 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 plurality of STAs 200.

[0188] By setting this MAP Trigger frame, even if the MAP types differ among the multiple STAs 200, the AP 100 can notify other APs 100 of control signals corresponding to each of the multiple MAP types, thereby improving signaling efficiency. Also, for example, duplication of STA information such as MAP type can be suppressed, thereby reducing signaling. Therefore, according to this embodiment, communication efficiency in cooperative communication can be improved.

[0189] (Comparison of Embodiments 6, 7 and 8) FIG. 24 is a diagram showing a comparative example of the processing complexity and signaling amount related to the MAP Trigger frame format of each of the sixth, seventh, and eighth embodiments.

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

[0191] Also, for example, in the seventh embodiment, Per STA Info is arranged in the Per AP Info field, and a common MAP type is indicated to STA 200 in a region different from Per STA Info in the Per AP Info field.

[0192] Also, for example, the eighth embodiment is a method in which Per AP Info is not arranged, and the MAP type is indicated in Per STA Info.

[0193] As shown in Fig. 24, the processing complexity decreases, for example, in the order of Embodiments 7, 6, and 8. Also, as shown in Fig. 24, the amount of signaling decreases, for example, in the order of Embodiments 8, 7, and 6.

[0194] For example, when emphasis is placed on reducing the complexity of processing, the seventh embodiment may be applied (or selected). Also, for example, when emphasis is placed on reducing the amount of signaling, the eighth embodiment may be applied (or selected).

[0195] (Embodiment 9) The configurations of the AP and STA according to this embodiment may be the same as those in the first embodiment.

[0196] In this embodiment, for example, a method of switching between the methods (or MAP Trigger frame formats) of the fourth embodiment to the eighth embodiment will be described.

[0197] For example, the format type applied to the MAP Trigger frame (for example, any of the frame formats according to the fourth to eighth embodiments) may be indicated in the Common Info field.

[0198] Fig. 25 is a diagram showing an example of a MAP Trigger frame format according to the present embodiment, in which the frame format according to the fourth embodiment is applied.

[0199] 25, the Common Info field may include, for example, information indicating the format type of the MAP Trigger frame (for example, MAP Format Type). The AP 100 may determine the format of the MAP Format Type field and subsequent fields in the MAP Trigger frame based on, for example, the format type indicated in the MAP Format Type.

[0200] The format type specified by MAP Format Type may be, for example, one of the following formats: A format that indicates the MAP type of each Shared AP in the MAP type field of Common Info (for example, embodiment 4). A format that indicates the MAP type in the Per AP Info field (for example, embodiment 5). Format for indicating MAP type in Per STA Info field in Per AP Info (e.g., embodiment 6) A format in which Per STA Info is placed within Per AP Info, and a MAP type common to all STAs is indicated in an area different from the Per STA Info within Per AP Info (for example, embodiment 7). A format in which Per AP Info is not placed and the MAP type is indicated in the Per STA Info field (e.g., embodiment 8)

[0201] The selection criteria for the format type include, for example, the following methods.

[0202] For example, a format with a smaller total number of bits or a format that is easier to process may be selected. For example, if there are multiple formats that can notify the MAP type configuration to be set in the Shared AP (e.g., a MAP type common to the Shared APs, a MAP type for each Shared AP, or a MAP type for each STA 200), a format with a smaller total number of 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 depending on, for example, the MAP type setting status for each Shared AP and the STA 200 subordinate to each Shared AP.

[0203] For example, if the MAP type differs for each Shared AP and is the same within each AP (for example, between subordinate STAs 200), AP 100 (e.g., a Sharing AP) may select the format of embodiment 5, and if the MAP type differs for each Shared AP and each subordinate STA 200 of the Shared AP, AP 100 may select the format of embodiment 6.

[0204] In this way, the AP 100 may select (or switch) one of a plurality of formats of the MAP Trigger frame based on, for example, a selection criterion, and transmit a MAP Trigger frame including information indicating the type of the selected format (for example, MAP Format Type). By switching formats, the AP 100 can select a format that is easier to process or a format that requires less signaling, for example, depending on the MAP type settings of each Shared AP and the STAs 200 subordinate to each Shared AP.

[0205] In this embodiment, as an example, a method for switching the MAP Trigger frame format described in embodiments 4 to 8 has been described, but the candidate formats to be switched are not limited to this and may be, for example, at least some of the formats described in embodiments 1 to 8.

[0206] Furthermore, in the present embodiment, as an example, a case has been described in which the MAP Trigger frame format is specified by the MAP Format Type. However, this is not limited to this, and for example, the MAP Trigger frame format (format type) may be implicitly notified to the Shared AP based on other parameters.

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

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

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

[0210] Furthermore, in the above-described embodiment, examples of definitions of the Frame Control field (e.g., FIG. 8), MAP type (e.g., FIG. 9 and FIG. 10), Trigger Type subfield (e.g., FIG. 12 and FIG. 14), and Total MAP Type and MAP Type Index (e.g., FIG. 20) are shown, but the examples are not limited to these definition examples and may be defined to other values.

[0211] In the above embodiment, the type of MAP is described using the term "MAP type," but this is not limiting and other terms may be used. For example, the term "Multi-AP coordination schemes" used in the 11be specifications currently being formulated may be used.

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

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

[0214] The present disclosure can be realized by software, hardware, or software linked to hardware. Each functional block used in the description of the above embodiments may be partially or entirely realized as an LSI, which is an integrated circuit, and each process described in the above embodiments may be partially or entirely controlled by a single LSI or a combination of LSIs. The LSI may be composed of individual chips, or may be composed of a single chip that includes some or all of the functional blocks. The LSI may have data input and output. Depending on the degree of integration, the LSI may be called an IC, system LSI, super LSI, or ultra LSI.

[0215] The integrated circuit method is not limited to LSI, but may be realized by a dedicated circuit, a general-purpose processor, or a dedicated processor. Also, a field programmable gate array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that can reconfigure the connections and settings of circuit cells within the LSI, may be used. The present disclosure may be realized as digital processing or analog processing.

[0216] Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology or other derivative technologies, it is natural that such technology can be used to integrate functional blocks. The application of biotechnology, etc. is also a possibility.

[0217] The present disclosure may be implemented in any type of apparatus, device, or system (collectively referred to as a communications apparatus) that has a communications function. The communications apparatus may include a wireless transceiver and processing / control circuitry. The wireless transceiver may include a receiver and a transmitter, or both functions. The wireless transceiver (transmitter and receiver) may include a radio frequency (RF) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or the like. Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks), cameras (e.g., digital still / video cameras), digital players (e.g., digital audio / video players), wearable devices (e.g., wearable cameras, smartwatches, tracking devices), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles or mobile transportation (e.g., cars, airplanes, ships), and combinations of the above devices.

[0218] Communications equipment is not limited to portable or mobile equipment, but also includes non-portable or fixed equipment, devices, and systems of any kind, such as smart home devices (such as appliances, lighting equipment, smart meters or metering devices, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0219] Communications include data communications via cellular systems, wireless LAN systems, communications satellite systems, etc., as well as data communications via combinations of these.

[0220] A communications apparatus also includes devices such as controllers and sensors connected or coupled to a communications device that performs the communications functions described in this disclosure, such as controllers and sensors that generate control and data signals used by the communications device to perform the communications functions of the communications apparatus.

[0221] The communication apparatus also includes infrastructure facilities, such as base stations, access points, and any other apparatus, device, or system that communicates with or controls the various apparatuses listed above, but are not limited to these.

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

[0223] In one embodiment of the present disclosure, the control signal includes common information including information common to a plurality of base stations and individual information 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 a field for notifying the type in the common information.

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

[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 a trigger type, and the information indicating the type is included in a field that depends on the trigger type.

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

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

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

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

[0231] In one embodiment of the present disclosure, the control circuit performs resource allocation for the terminal connected to the other base station.

[0232] In one embodiment of the present disclosure, the control signal includes common information including information common to multiple base stations and terminal-specific information that is individual to multiple terminals, information indicating the type of each of the multiple 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 an embodiment of the present disclosure, the size of the terminal individual information is common among the types or different for each type.

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

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

[0236] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2020-156398, filed on September 17, 2020, are incorporated herein by reference in their entirety. [Industrial Applicability]

[0237] One embodiment of the present disclosure is useful in wireless communication systems. [Explanation of symbols]

[0238] 100 AP 101 Control section 102 STA control signal generation unit 103 AP control signal generation unit 104,203 Transmission signal generator 105,201 Radio transmitter / receiver 106,202 Received signal demodulation and decoding unit 200 STA

Claims

1. a receiving circuit that receives a control signal including a parameter that does not depend on the type of cooperative communication and a parameter that depends on the type from another base station; a control circuit that performs the cooperative communication based on the control signal; Equipped with a format of the control signal is determined based on the type; The field length of the type-dependent parameter is variable depending on the type. Base station.

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

3. The identification information of the other base station is included in the type-independent parameters. The base station of claim 2.

4. The control signal includes terminal-specific information specific to a terminal connected to the base station itself, The information indicating the type is included in the terminal individual information. The base station of claim 1 .

5. the control signal includes terminal individual information that is individual to a plurality of terminals; the information indicating the type of each of the plurality of terminals is included in the terminal individual information, The format of the terminal individual information is determined based on the type. The base station of claim 1 .

6. The size of the terminal individual information is common among the types or different for each type. The base station of claim 5.

7. the format of the control signal is any one format selected from the plurality of formats based on a selection criterion; the receiving circuit receives the control signal including information indicating the type of the selected format. The base station of claim 1 .

8. The base station is receiving a control signal from another base station, the control signal including a parameter independent of a type of cooperative communication and a parameter dependent on the type of cooperative communication; performing the cooperative communication based on the control signal; a format of the control signal is determined based on the type; The field length of the type-dependent parameter is variable depending on the type. Communication method.

9. receiving a control signal from another base station, the control signal including a parameter independent of a type of cooperative communication and a parameter dependent on the type of cooperative communication; performing the cooperative communication based on the control signal; An integrated circuit for controlling a format of the control signal is determined based on the type; The field length of the type-dependent parameter is variable depending on the type. Integrated circuit.

Images