Base station, communication device, and communication method

Abstract

A base station includes: control circuitry that determines the format of control signals based on the type of coordinated communication; and transmission circuitry that transmits control signals to other base stations according to the format.

Description

Technical Field

[0001] This disclosure relates to base stations, communication devices, and communication methods. Background Technology

[0002] The Institute of Electrical and Electronics Engineers (IEEE) is working on the IEEE 802.11be (hereinafter referred to as "11be") standard, a successor to the IEEE 802.11ax (hereinafter also referred to as "11ax") standard, for next-generation wireless local area networks (LANs). For example, IEEE 802.ax is also known as "High Efficiency" (HE), and IEEE 802.be is also known as "Extreme High Throughput" (EHT).

[0003] Existing technical documents

[0004] Non-patent literature

[0005] Non-patent document 1: IEEE 802.11-19 / 0804r0, Multi-AP Transmission Procedure

[0006] Non-patent literature 2: IEEE 802.11-19 / 1788r1, Coordinated OFDMA Operation

[0007] Non-patent document 3: IEEE 802.11-19 / 1102r0, A unified transmission procedure for multi-AP coordination

[0008] Non-patent document 4: IEEE 802.11-20 / 0033r1, coordinated spatial reuse operation

[0009] Non-patent document 5: IEEE 802.11-20 / 0576r1, Coordinated Spatial Reuse Protocol Summary of the Invention

[0010] However, control methods for coordinated communication in wireless communications such as wireless LANs have not been fully studied.

[0011] The non-limiting embodiments disclosed herein help to provide base stations, communication devices, and communication methods that can improve communication efficiency in coordinated communications.

[0012] One embodiment of the base station disclosed herein includes: a control circuit that determines the format of a control signal based on the type of coordinated communication; and a transmission circuit that transmits the control signal to other base stations according to the format.

[0013] It should be noted that these general or specific methods can be implemented by systems, devices, methods, integrated circuits, computer programs, or recording media, or by any combination of systems, devices, methods, integrated circuits, computer programs, and recording media.

[0014] According to one embodiment of this disclosure, communication efficiency in coordinated communications can be improved.

[0015] Further advantages and effects of one embodiment of this disclosure will be clearly presented by the specification and accompanying drawings. These advantages and / or effects are provided by various embodiments and the features described in the specification and drawings, but not all of them need to be provided to obtain one or more of the same features. Attached Figure Description

[0016] Figure 1 This is a diagram illustrating an example of a multi-AP (MAP) trigger frame format.

[0017] Figure 2 This is a diagram illustrating a structural example of a MAP.

[0018] Figure 3 This is a diagram representing an example of notification information for each MAP type.

[0019] Figure 4 This is a block diagram illustrating a structural example of a portion of the AP in Implementation 1.

[0020] Figure 5 This is a block diagram illustrating a structural example of the AP in Implementation Method 1.

[0021] Figure 6 This is a block diagram illustrating a structural example of the STA in Implementation Method 1.

[0022] Figure 7 This is a diagram illustrating an example of the MAP trigger frame format of Implementation 1.

[0023] Figure 8 This is a diagram illustrating an example definition of the Frame Control field.

[0024] Figure 9 This is a diagram representing a definition example of the MAP type.

[0025] Figure 10 This is a diagram representing a definition example of the MAP type.

[0026] Figure 11 This is a diagram illustrating an example of the MAP trigger frame format in Implementation Method 2.

[0027] Figure 12 This is a diagram representing a definition example of a trigger type subfield.

[0028] Figure 13 This is a diagram illustrating an example of the MAP trigger frame format in Implementation 3.

[0029] Figure 14 This is a diagram representing an example of the definition of a trigger type subfield.

[0030] Figure 15 This is a diagram illustrating an example of the MAP trigger frame format in Implementation 4.

[0031] Figure 16 This is a diagram illustrating an example of the MAP trigger frame format in Implementation 5.

[0032] Figure 17 This is a diagram showing a comparison between Embodiment 4 and Embodiment 5.

[0033] Figure 18 This is a diagram illustrating an example of the MAP trigger frame format in Implementation 6.

[0034] Figure 19 This is a diagram illustrating an example of the MAP trigger frame format in Implementation 6.

[0035] Figure 20 This is a diagram illustrating the definition of the Total MAP Type and the Type Index.

[0036] Figure 21 This is a diagram illustrating an example of the MAP trigger frame format in Implementation 7.

[0037] Figure 22 This is a diagram illustrating an example of the MAP trigger frame format in Implementation 8.

[0038] Figure 23 This is a diagram illustrating an example of how MAP types differ depending on the terminal (STA: Station).

[0039] Figure 24 This is a diagram showing a comparative example between Embodiment 6, Embodiment 7 and Embodiment 8.

[0040] Figure 25 This is a diagram illustrating an example of the MAP trigger frame format of Implementation 9. Detailed Implementation

[0041] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0042] In 11be, for example, the application of multi-AP (hereinafter referred to as "MAP") coordination (hereinafter referred to as "coordinated communication") for sending and receiving data between multiple access points (APs, or also referred to as "base stations") and various terminals (STAs, or also referred to as "non-AP STAs") was studied (e.g., Non-Patent Documents 1 to 5).

[0043] For coordinated communication in 11be, several categories are examined (e.g., communication types, hereinafter referred to as "MAP types"). For example, the following MAP types can be listed.

[0044] • Coordinated Spatial Reuse (hereinafter referred to as "C-SR")

[0045] • Coordinated Orthogonal Frequency Division Multiple Access (hereinafter referred to as "C-OFDMA")

[0046] • Joint Transmissions (hereinafter referred to as "JT")

[0047] • Coordinated Beamforming (hereinafter referred to as "CBF")

[0048] Furthermore, JT includes, for example, methods for sending the same signal from multiple coordinated APs, and methods for sending different transmission streams from multiple coordinated APs. The method for sending different transmission streams from multiple coordinated APs is, for example, referred to as "Distributed Multi-User-Multiple Input Multiple Output (D-MIMO)".

[0049] For example, "JT" can also be defined as a method of sending the same signal from multiple coordinated APs, and is defined differently from "D-MIMO". Below, as an example, the method of sending the same signal from multiple coordinated APs is defined as "JT", while the method of sending different transmission streams from multiple coordinated APs is defined as "D-MIMO".

[0050] In addition, as a control method for coordinated communication, the format of MAP trigger frames (or, sometimes also called "MAP announcement frames") has been studied. For example, regarding the MAP trigger frame format, the control process for each MAP type or the information (notification information) notified by the AP to the STA has been studied.

[0051] Figure 1 This is a diagram illustrating an example of the MAP trigger frame format based on the trigger frame format in 11ax. For example... Figure 1 As shown, for example, you can define information (or, a field) for each AP, namely "Per AP Info".

[0052] Figure 2 This is a diagram illustrating the structure of an AP and STA (a structure example of a MAP) that coordinates communication.

[0053] exist Figure 2 In this context, a "Sharing AP" can be, for example, an AP that acquires channel usage (or, transmission) during a period (e.g., TXOP: transmission opportunity) and initiates (or controls) coordinated communication. Conversely, a "Shared AP" can be an AP that has been instructed by the Sharing AP to coordinate communication.

[0054] In addition, although Figure 2 The example shown illustrates a scenario where the sharing AP and the shared AP are different APs, but it is not limited to this. For example, it could also be a structure where one shared AP also acts as the sharing AP. For instance, a MAP trigger frame can be sent from the sharing AP to the shared AP. By sending the MAP trigger frame, the sharing AP can instruct the shared AP on controls related to coordinated communication (e.g., initiation). The MAP trigger frame may contain information about each shared AP (e.g., Per APInfo).

[0055] In one embodiment of this disclosure, a method is described as follows (e.g., setting the MAP trigger frame format): a method for uniformly and efficiently controlling multiple MAP types in a MAP trigger frame.

[0056] [Structure of a wireless communication system]

[0057] The wireless communication system of this embodiment may include multiple AP100 and STA200. AP100 may have the functions of both sharing AP and being shared AP, or only one of them.

[0058] For example, AP100, acting as a shared AP, can notify other AP100s acting as the shared APs of the MAP type (e.g., C-SR, C-OFDMA, JT, CBF, or D-MIMO) in a MAP trigger frame. Furthermore, "notification" can be replaced with "send" or "instruction".

[0059] Additionally, AP100, as a shared AP, can, 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 that are being shared, according to the determined format.

[0060] Here, the parameters (or notification information) notified by the shared AP to the shared AP in the MAP trigger frame can 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 across multiple MAP types). Furthermore, the term "dependent on MAP type" can be replaced, for example, with "based on" MAP type. The term "independent of MAP type" can also be replaced, for example, with other terms such as "not based on" or "independent of" MAP type.

[0061] The following parameters can be listed as examples of parameters that do not depend on the MAP type.

[0062] •BW (bandwidth)

[0063] • MAP type (information indicating the category of coordinated communication),

[0064] • Shared AP ID (Identifier) ​​(Identification information of the shared AP)

[0065] • Uplink (UL) / Downlink (DL) flags (representing information about either UL or DL),

[0066] • Resource Allocation

[0067] Figure 3 This represents an example of a parameter that depends on the MAP type.

[0068] exist Figure 3In the diagram, the parameter corresponding to "●" indicates the parameter that is notified by the MAP trigger frame in the relevant MAP type.

[0069] For example, in Figure 3 The MAP type “C-SR” shown can inform the share AP and the shared AP of their transmit power (e.g., Sharing AP Tx Power and Shared AP Maximum Tx Power) and the allowed interference level (e.g., Sharing AP Acceptable Maximum Interference Level and Shared AP Interference Level).

[0070] Additionally, for example in Figure 3 The MAP types “JT” and “D-MIMO” shown can provide transmission parameters such as modulation and coding scheme (MCS), sequence number, and spatial stream index.

[0071] Additionally, for example in Figure 3 The MAP type "CBF" shown can notify the ID of the STA that uses beamforming to suppress interference (e.g., STA ID to Suppress) and resource allocation information (STA Resource Allocation Info to Suppress).

[0072] Additionally, for example in Figure 3 The MAP type "C-OFDMA" shown can be used without notifying the parameters that depend on the MAP type.

[0073] Furthermore, the parameters that do not depend on the MAP type and those that do depend on the MAP type mentioned above are examples; other parameters may also be used.

[0074] Figure 4 This is a block diagram illustrating a structural example of AP100, an embodiment of the present disclosure. Figure 4 In the AP100 shown, the control unit 101 (e.g., equivalent to a control circuit) determines the format of the control signal (e.g., MAP trigger frame) based on the type of coordinated communication (e.g., MAP type). The wireless transceiver unit 105 (e.g., equivalent to a transmission circuit) transmits the control signal to other base stations (e.g., shared APs) according to the above format.

[0075] (Implementation Method 1)

[0076] [Structure example of AP100]

[0077] Figure 5 This is a block diagram representing a structural example of AP100. Figure 5 The AP100 shown may include, for example, a control unit 101, a control signal generation unit 102 for a STA, a control signal generation unit 103 for an AP, a transmission signal generation unit 104, a wireless transceiver unit 105, and a receive signal demodulation / decoding unit 106.

[0078] Control unit 101 can, for example, control the setting of MAP trigger frames. For example, when AP 100 is a shared AP, control unit 101 can control the generation of control signals (e.g., MAP trigger frames) for other APs 100 (e.g., the shared AP). For example, control unit 101 can determine the MAP trigger frame format based on the MAP type. In addition, for example, when AP 100 is a shared AP, control unit 101 can determine the format of the MAP trigger frame based on information related to the MAP type in the MAP trigger frames sent from other APs 100 (e.g., the shared AP).

[0079] Furthermore, examples of the MAP trigger frame format will be described later.

[0080] Furthermore, the control unit 101 can, for example, set control information for STA 200 or other AP 100. For example, the control unit 101 can set resource allocation information for each STA 200, and scheduling information such as MCS. Additionally, the control unit 101 can, for example, determine transmission control-related parameters (e.g., parameters related to the aforementioned coordinated communication) based on information input from the received signal demodulation / decoding unit 106 (e.g., control information notified to the shared AP by the sharing AP). The control unit 101 can, for example, output control information containing the determined transmission control parameters to the control signal generation unit 102 for STAs and the control signal generation unit 103 for APs.

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

[0082] The control signal generation unit 103 for the AP can generate control signals for the AP 100 (e.g., MAP trigger frames). For example, the control signal generation unit 103 for the AP can generate control signals based on control information input from the control unit 101 and information input from the received signal demodulation / decoding unit 106.

[0083] The control signals used for AP100 may include, for example, time and frequency resource information (e.g., RU allocation information, TXOP, length, etc. for uplink coordination communication), at least one of the parameters related to coordination communication (e.g., the MAP type mentioned above, parameters that do not depend on the MAP type, or parameters that depend on the MAP type). The control signal generation unit 103 for AP outputs the generated control signals to the transmission signal generation unit 104, for example.

[0084] The transmission signal generation unit 104 can, for example, process control signals or data input from the control signal generation unit 102 for STA or the control signal generation unit 103 for AP, and generate a radio frame (transmission signal). The transmission signal generation unit 104 outputs the generated transmission signal to the radio transceiver unit 105.

[0085] 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 (Digital / Analog) conversion and up-conversion to the carrier frequency, and transmits the processed signal via an antenna.

[0086] For example, when AP100 receives an uplink signal from STA200 or a control signal from another AP100, it can operate as follows.

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

[0088] The received signal demodulation / decoding unit 106 can, for example, perform autocorrelation processing on the signal input from the wireless transceiver unit 105 and extract the received wireless frames. Furthermore, the received signal demodulation / decoding unit 106 can, for example, decode and demodulate uplink signals (e.g., response signals, feedback information) from the STA 200 or control signals (e.g., MAP trigger frames) from other APs 100 contained in the extracted wireless frames. The received signal demodulation / decoding unit 106 can, for example, output the demodulated control signals to the control unit 101, the control signal generation unit 102 for the STA, and the control signal generation unit 103 for the AP.

[0089] [Structure example of STA200]

[0090] Figure 6 This is a block diagram illustrating a structural example of the STA200 in this embodiment. Figure 6 The STA200 shown may include, for example, a wireless transceiver unit 201, a received signal demodulation / decoding unit 202, and a transmitted signal generation unit 203.

[0091] The wireless transceiver unit 201 receives signals transmitted from the AP100 via an antenna, performs wireless reception processing on the received signals such as down-conversion and A / D (Analog / Digital) conversion, and outputs the processed signal to the received signal demodulation / decoding unit 202. Alternatively, the wireless transceiver unit 201 can perform wireless transmission processing on signals input from the transmission signal generation unit 203, such as D / A conversion and up-conversion to a carrier frequency, and transmit the processed signal via an antenna.

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

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

[0094] [Example of MAP trigger frame format settings]

[0095] Next, an example of setting the MAP trigger frame format in this embodiment will be described.

[0096] In this embodiment, for example, the case where the MAP type is common to multiple (e.g., all) shared APs will be described.

[0097] When multiple shared APs share a common MAP type, AP100 (the shared AP) can, for example, notify other AP100s of the MAP type in the "MAP Type" field configured within the common information (e.g., Common Info) field of the MAP trigger frame, which contains information common to all shared APs. In other words, the MAP type (information indicating the category of coordinated communication) can be included in the field within the common information used to notify the MAP type. Furthermore, "configuration" can be replaced with other terms such as "mapping" or "setting."

[0098] Additionally, AP100 may, for example, determine (or change) the format of MAP type-dependent common information (e.g., MAP Type Dependent Common Info) in the common information field and MAP type-dependent information (e.g., MAP Type Dependent Info) in the dedicated information field (e.g., Per AP Info) for multiple shared APs based on the MAP type notified to multiple shared APs.

[0099] Figure 7 This is a diagram illustrating an example of the MAP trigger frame format in this embodiment.

[0100] For example, the fact that a frame is classified as "MAP Trigger" can be communicated to the shared AP using "Frame Control" fields (e.g., Type and Subtype subfields). Figure 8 This is a diagram illustrating an example of the definition of type and subtype subfields within a frame control field. As an example, Figure 8 Extract and represent the Control types in 11ax. In Figure 8 In the example shown, the subtype triggered by MAP is defined as the reserved value in 11ax, i.e., the subtype value "0001". Furthermore, the definitions in the frame control field are not limited to... Figure 8 The example shown can also define the subtype value triggered by MAP as other values ​​(e.g., other reserved values).

[0101] exist Figure 7Within this framework, you can set notification information (or general information) common to multiple shared APs in the general information field. This general information for multiple shared APs can include, for example, general information independent of the MAP type (or information common to multiple MAP types) and general information dependent on the MAP type (or information that differs based on the MAP type: MAP Type Dependent Common Info).

[0102] In general information that does not depend on the MAP type, information related to MAP type and bandwidth (BW) can be included.

[0103] Additionally, general information that depends on the MAP type may include information such as the shared AP transmit power and the maximum permissible interference level of the shared AP.

[0104] Figure 9 and Figure 10 This is a diagram representing an example of the definition of a MAP type. For example, Figure 9 The MAP type definition example shown (hereinafter referred to as "Definition Example 1") is an example of appending indexes to each MAP type. Additionally, for example... Figure 10 The example definition of the MAP type shown (hereinafter referred to as "Definition Example 2") is an example of grouping MAP types that use the same parameters, such as JT and D-MIMO, into a group and attaching an index. For example, compared with Definition Example 1, Definition Example 2 can reduce the table size of the MAP type.

[0105] exist Figure 7 Within the Per AP Info field, you can set notification information (or dedicated information) specific to the shared AP. The dedicated information for each shared AP can be, for example, information common to the STA200 associated with (or connected to) the shared AP. The dedicated information for each shared AP can include, for example, dedicated information independent of the MAP type (or dedicated information common to multiple MAP types) and dedicated information dependent on the MAP type (or dedicated information MAP Type Dependent Info that differs depending on the MAP type).

[0106] In proprietary information that does not depend on the MAP type, for example, the shared AP ID, resource allocation, and UL / DL markings may be included.

[0107] Additionally, the specific information that depends on the MAP type may include, for example, the following information.

[0108] • In the case of C-SR: Maximum transmit power of the shared AP, interference level of the shared AP

[0109] • In the case of JT or D-MIMO: transmit parameters (e.g., MCS, sequence number, ...).

[0110] • In the case of CBF: Suppressed STA ID, suppressed STA resource allocation information

[0111] • In the case of C-OFDMA: No information

[0112] also, Figure 7 The BW field in the code can be the same as, or different from, the "UL BW subfield" defined in the Common Info field of the 11ax trigger frame format. Figure 7 The resource allocation in the 11ax trigger frame format can be the same as or different from the definition of the "RU Allocation subfield" in the User Infofield.

[0113] Alternatively, for example, AP100 can 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 (High Efficiency-Signal-B) of 11ax, or the same method extended for use with 11be.

[0114] Additionally, although an RU with a size less than 20MHz is defined in the RU allocation subfield of 11ax, it is not limited to this definition. A size greater than 20MHz can also be defined in the resource allocation, for example.

[0115] Thus, in this embodiment, AP100 (the sharing AP) uses the MAP type field configured in the general information field within the MAP trigger frame to notify other AP100s (the shared APs) of the MAP type, and also notifies them of the corresponding MAP type dependency general information (e.g., MAP Type Dependent Common Info) and MAP type dependency information (MAP Type Dependent Info). In other words, the content of the MAP type dependency general information and the MAP type dependency information changes based on the MAP type within the MAP trigger frame.

[0116] By setting this MAP trigger frame, AP100 can notify other AP100s of control signals corresponding to multiple MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in coordinated communication can be improved.

[0117] (Implementation Method 2)

[0118] The structures of AP and STA in this embodiment can be the same as those in embodiment 1.

[0119] In this embodiment, for example, similar to embodiment 1, the case where the MAP type is common to multiple (e.g., all) shared APs will be described.

[0120] When multiple shared APs share the same MAP type, AP100 (the shared AP) can, for example, notify other AP100s (the shared APs) of the MAP trigger type in the Trigger Type field (e.g., the same as the UL trigger in 11ax). In other words, the MAP type (information indicating the category of coordinated communication) can be included in the field for notifying the trigger type in the general information.

[0121] Additionally, AP100 can, for example, determine (or change) the format of MAP type dependent common information (e.g., MAP Type Dependent Common Info) in the Common Information field and MAP type dependent information (e.g., MAP Type Dependent Info) in the PerAP Info field based on the MAP type notified to multiple shared APs.

[0122] Figure 11 This diagram illustrates an example of the MAP trigger frame format in this embodiment. Additionally, Figure 12 This is a diagram representing an example of the definition of a trigger type subfield.

[0123] For example, such as Figure 12 As shown, for the trigger type subfield of 11ax (e.g., Table 9-31b), multiple MAP types can be defined as values ​​8 through 12 respectively. Through this MAP type definition, shared APs can... Figure 11 In the trigger type field shown in the general information field, determine (or identify, decide) the MAP type.

[0124] In addition, Figure 11 In this context, the general information field, which is independent of the MAP type (e.g., BW), can be the same as in Implementation 1.

[0125] In addition, Figure 11 In the common information field, the trigger type-dependent common information (e.g., Trigger TypeDependent Common Info) can be the same as the MAP type-dependent common information (MAP TypeDependent Common Info) in Implementation 1.

[0126] In addition, Figure 11 In this context, the proprietary information in the Per AP Info field that is independent of the MAP type (e.g., shared AP ID, resource allocation, UL / DL flag) can be the same as in Implementation 1.

[0127] In addition, Figure 11 In this context, the trigger type dependency information (e.g., Trigger TypeDependent Info) in the Per AP Info field can be the same as the MAP type dependency information (e.g., MAP Type DependentInfo) in Implementation 1.

[0128] Thus, in this embodiment, AP100 notifies other AP100s of the MAP type triggered by using the trigger type field in the MAP trigger frame. Additionally, AP100, for example, notifies other AP100s of the trigger type dependency common information and trigger type dependency information corresponding to the MAP type notified by the trigger type field. In other words, the format of the trigger type dependency common information and trigger type dependency information in the MAP trigger frame changes based on the MAP type, similar to embodiment 1.

[0129] By setting this MAP trigger frame, AP100 can notify other AP100s of control signals corresponding to multiple MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in coordinated communication can be improved.

[0130] (Implementation Method 3)

[0131] The structures of AP and STA in this embodiment can be the same as those in embodiment 1.

[0132] In this embodiment, for example, similar to embodiment 1, the case where the MAP type is common to multiple (e.g., all) shared APs will be described.

[0133] When multiple shared APs share a common MAP type, AP100 (the shared AP) can, for example, notify other AP100s (the shared APs) of the MAP trigger in the trigger type field (e.g., the same as the UL trigger for 11ax). Alternatively, AP100 can, for example, notify the MAP type in the trigger type-dependent common information field (e.g., Trigger Type Dependent Common Info). In other words, in the common information, information about triggering MAP coordination (coordination communication) is included in the field used to notify the trigger type, and the MAP type (information indicating the category of coordination communication) is included in the field dependent on the trigger type.

[0134] Additionally, AP100 can determine (or change) the format of the trigger type dependent common information (e.g., Trigger Type Dependent Common Info) in the common information field, the MAP type dependent common information (e.g., MAP Type Dependent Common Info) in the common information field, and the trigger type dependent information (e.g., Trigger Type Dependent Info) in the Per AP Info field, based on the MAP type of notifications from multiple shared APs.

[0135] Figure 13 This diagram illustrates an example of the MAP trigger frame format in this embodiment. Additionally, Figure 14 This is a diagram representing an example of the definition of a trigger type subfield.

[0136] For example, such as Figure 14 As shown, for the trigger type subfield of 11ax (e.g., Table 9-31b), MAP (Multiple APs) can be defined as a value of 8. Through this MAP definition, the shared APs can be identified. Figure 13 The trigger type shown in the general information is MAP.

[0137] Additionally, for example, the MAP type field can be configured in the trigger type-dependent common information (e.g., Trigger TypeDependent Common Info) within the common information field. The shared AP can, for example, determine (or identify, decide) the MAP type in the MAP type field within the common information field of the MAP trigger frame whose trigger type is MAP.

[0138] In addition, Figure 13 In this context, the general information field, which is independent of the MAP type (e.g., BW), can be the same as in Implementation 1.

[0139] In addition, Figure 13In the general information field, the MAP type-dependent general information (e.g., MAP TypeDependent Common Info) can be the same as the MAP type-dependent general information (MAP TypeDependent Common Info) in Implementation 1.

[0140] In addition, Figure 13 In this context, the proprietary information in the Per AP Info field that is independent of the MAP type (e.g., shared AP ID, resource allocation, UL / DL flag) can be the same as in Implementation 1.

[0141] In addition, Figure 13 In this context, the MAP type dependency information (e.g., Trigger TypeDependent Info) in the Per AP Info field may be the same as the MAP type dependency information (e.g., MAP Type DependentInfo) in Implementation 1.

[0142] Thus, in this embodiment, AP100 notifies other AP100s of the MAP triggering status using the trigger type field in the MAP trigger frame, and notifies other AP100s of the MAP type in the MAP type field within the trigger type dependent common information (Trigger Type Dependent Common Info). Additionally, AP100, for example, notifies other AP100s of the trigger type dependent common information (Trigger Type Dependent Common Info) and trigger type dependent information (Trigger Type Dependent Info) corresponding to the notified MAP type. In other words, the format of the trigger type dependent common information and trigger type dependent information changes based on the MAP type in the MAP trigger frame.

[0143] By setting this MAP trigger frame, AP100 can notify other AP100s of control signals corresponding to multiple MAP types, thereby improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in coordinated communication can be improved.

[0144] (Comparison between Implementation Method 1, Implementation Method 2, and Implementation Method 3)

[0145] For example, the complexity of the processing related to the respective MAP trigger frame formats of Embodiment 1, Embodiment 2 and Embodiment 3 is the same.

[0146] Furthermore, from the perspective of the signaling of the MAP trigger frame format in each of Embodiments 1, 2, and 3, the difference lies in that the notification of MAP triggering and the notification of MAP type are performed in the following fields.

[0147] • Implementation Method 1: MAP Type within Frame Control and General Information

[0148] • Implementation Method 2: Trigger Types within General Information

[0149] • Implementation Method 3: Trigger types within the general information and the MAP type that the trigger type depends on within the general information (Trigger TypeDependent Common Info).

[0150] Therefore, in the MAP trigger frame formats of embodiments 1, 2 and 3, for example, the applied format can also be determined according to the definition area used for other purposes that are different from the MAP settings.

[0151] For example, in the definition area of ​​the trigger type subfield (e.g., Figure 12 or Figure 14 Compared to this, the Frame Control subtype (e.g., Figure 8 When there are many unused areas (e.g., reserved areas) in the defined area of ​​a frame, the MAP trigger frame format of Implementation 1 can also be applied. On the other hand, for example, when combined with frame control subtypes (e.g., Figure 8 Compared to the definition area of ​​the trigger type subfield (e.g., ...), the definition area of ​​the trigger type subfield is... Figure 12 or Figure 14 If there are many unused areas (e.g., reserved areas) in the MAP trigger frame format of embodiment 2 or embodiment 3, the MAP trigger frame format can also be applied.

[0152] (Implementation Method 4)

[0153] The structures of AP and STA in this embodiment can be the same as those in embodiment 1.

[0154] In this embodiment, for example, the case where multiple shared APs have different MAP types will be described.

[0155] When the MAP types of the shared APs differ, AP100 (the sharing AP) can, for example, notify other AP100 (the shared APs) of the MAP types of each shared AP in the MAP Type field configured within the general information field. In other words, the MAP types of each shared AP (information indicating the category of coordinated communication) can be included in the general information (e.g., the MAP Type field).

[0156] Additionally, AP100 may, for example, 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 to each of the multiple shared APs.

[0157] Figure 15 This is a diagram illustrating an example of the MAP trigger frame format in this embodiment.

[0158] For example, such as Figure 15 As shown, the MAP type of multiple shared APs (e.g., AP#1, AP#2, ...) can be set (in other words, indicated) in the MAP Type field within the general information field.

[0159] also, Figure 15 The frame shown is a MAP-triggered case. This situation can be notified to the shared AP by frame control, as in Embodiment 1, or by trigger type, as in Embodiment 2 or Embodiment 3.

[0160] In addition, Figure 15 In this context, the general information field, which is independent of the MAP type (e.g., BW), can be the same as in Implementation 1.

[0161] In addition, Figure 15 In the general information field, the MAP type-dependent general information (e.g., MAP TypeDependent Common Info) can be the same as the MAP type-dependent general information (MAP TypeDependent Common Info) in Implementation 1.

[0162] 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 dependency general information field may include the shared AP transmit power and the maximum permissible interference level of the shared AP. On the other hand, if the MAP types of multiple shared APs notified by the MAP trigger frame are all different from "C-SR" (e.g., one of C-OFDMA, JT, CBF, or D-MIMO), the MAP type dependency general information field may not include notification information.

[0163] In addition, Figure 15 In this context, the proprietary information in the Per AP Info field that is independent of the MAP type (e.g., shared AP ID, resource allocation, UL / DL flag) can be the same as in Implementation 1.

[0164] In addition, Figure 15 In this context, the MAP type dependency information (e.g., MAP TypeDependent Info) in the Per AP Info field may be the same as the MAP type dependency information (e.g., MAP Type DependentInfo) in Implementation 1.

[0165] Thus, in this embodiment, AP100, in the MAP trigger frame, uses the MAP type field configured in the general information field to notify other AP100s of the MAP types of each of the multiple shared APs. Additionally, AP100, for example, notifies other AP100s of the MAP type dependency general information (MAP Type Dependent Common Info) and MAP type dependency information (MAP Type Dependent Info) corresponding to the MAP types. In other words, in the MAP trigger frame, the format of the MAP type dependency general information and the MAP type dependency information changes based on the MAP types of the multiple shared APs.

[0166] By setting this MAP trigger frame, even when multiple shared APs have different MAP types, AP100 can still notify other AP100s of control signals corresponding to each of the multiple MAP types, thus improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in coordinated communication can be improved.

[0167] (Implementation Method 5)

[0168] The structures of AP and STA in this embodiment can be the same as those in embodiment 1.

[0169] In this embodiment, for example, similar to embodiment 4, the case where the MAP types of multiple shared APs are different will be described.

[0170] When the MAP types of the shared APs differ, AP100 (the sharing AP) can, for example, inform the other AP100 (the shared AP) of the MAP types of each of the shared APs in the Per APInfo field. In other words, the MAP types of each of the shared APs (information indicating the category of coordinated communication) can be included in the Per AP Info (e.g., dedicated information).

[0171] Additionally, AP100 may, for example, determine (or change) the format of MAP type dependency information (e.g., MAP Type Dependent Info) based on the MAP type notified to each of the multiple shared APs.

[0172] Figure 16 This is a diagram illustrating an example of the MAP trigger frame format in this embodiment.

[0173] For example, such as Figure 16 As shown, the MAP type of multiple shared APs can be set (in other words, indicated) in the MAP Type field within the Per AP Info field.

[0174] also, Figure 16 The frame shown is a MAP-triggered case. This situation can be notified to the shared AP by frame control, as in Embodiment 1, or by trigger type, as in Embodiment 2 or Embodiment 3.

[0175] exist Figure 16 Within this, the general information field can contain general information common to multiple shared APs and independent of the MAP type. This general information, independent of the MAP type, can include, for example, information related to bandwidth (BW).

[0176] In addition, Figure 16 In the Per AP Info field, you can set the specific information for each shared AP (in other words, the notification information common to the STA200 associated with the shared AP). The specific information for each shared AP can include, for example, specific information that does not depend on the MAP type and specific information that depends on the MAP type.

[0177] In proprietary information that does not depend on the MAP type, for example, the shared AP ID (AP ID), MAP type, resource allocation, and UL / DL mark may be included.

[0178] Additionally, the following information may be included in the special information that depends on the MAP type (e.g., MAP type dependency information (MAP TypeDependent Info)).

[0179] • In the case of C-SR: Shared AP transmit power, maximum allowable interference level of the shared AP, maximum transmit power of the shared AP, and interference level of the shared AP.

[0180] • In the case of JT or D-MIMO: transmit parameters (e.g., MCS, sequence number, ...).

[0181] • In the case of CBF: Suppressed STA ID, suppressed STA resource allocation information

[0182] • In the case of C-OFDMA: No information

[0183] Here, the length of the Per AP Info field can be either fixed or variable. In other words, the size of the Per AP Info (specific information) can be common across MAP types or can vary depending on the MAP type.

[0184] For example, when the Per AP Info field length is fixed, the MAP Type Dependent Info can be set to a constant length regardless of the MAP type. Alternatively, the Per AP Info field length can be set based on the format of the MAP type corresponding to the larger size (e.g., the largest size) of the Per AP Info field lengths for each MAP type (e.g., to make the Per AP Info field lengths consistent). 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 can be set as a reserved field.

[0185] When the Per AP Info field has a fixed length, each shared AP can determine the configuration location of the MAP type dependency information corresponding to that shared AP without relying on the MAP types of other shared APs. Therefore, the processing of Per AP Info (e.g., reading processing) can be simplified.

[0186] Additionally, for example, when the Per AP Info field length is variable, the length of the MAP Type Dependent Info can be set based on the MAP type. For instance, the length of the Per AP Info field for each shared AP can be determined based on the MAP type corresponding to the Per AP Info for each shared AP.

[0187] When the Per AP Info field has a variable length, it notifies the MAP type dependency information corresponding to the size of the MAP type set for each shared AP. Therefore, it can reduce the signaling volume compared to the case where the Per AP Info field has a fixed length.

[0188] Thus, in this embodiment, AP100, in the MAP trigger frame, uses the MAP type field configured in the Per AP Info field to notify other AP100s of the MAP types of each of the multiple shared APs. Additionally, AP100, for example, notifies other AP100s of MAP type dependency information corresponding to the MAP types. In other words, the format of the MAP type dependency information in the MAP trigger frame changes based on the MAP types of the multiple shared APs.

[0189] By setting this MAP trigger frame, even when multiple shared APs have different MAP types, AP100 can still notify other AP100s of control signals corresponding to each of the multiple MAP types, thus improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in coordinated communication can be improved.

[0190] (Comparison between Embodiment 4 and Embodiment 5)

[0191] Figure 17 This is a diagram showing a comparison of the processing complexity and signaling volume related to the respective MAP trigger frame formats of Embodiments 4 and 5. Furthermore, in Figure 17 In Embodiment 4, the case where the length of the Per AP Info field is variable is shown. In Embodiment 5, the cases where the length of the Per AP Info field is fixed and variable are shown.

[0192] like Figure 17 As shown, in Implementation 5 where the Per AP Info field length is fixed, the processing complexity decreases compared to Implementation 4, but the signaling volume increases. Additionally, as... Figure 17As shown, in Implementation 5, when the length of the Per APInfo field is variable, the processing complexity increases and the signaling volume decreases compared to Implementation 4.

[0193] For example, when reducing processing complexity is a priority, the format of PerAP Info field length in Implementation 5, which has a fixed length, can be applied (or selected). Alternatively, when reducing signaling volume is a priority, the format of PerAP Info field length in Implementation 5, which has a variable length, can be applied (or selected). Furthermore, when balancing the reduction of processing complexity with the reduction of signaling volume is a priority, the format of Implementation 4 can be applied (or selected).

[0194] (Implementation Method 6)

[0195] The structures of AP and STA in this embodiment can be the same as those in embodiment 1.

[0196] In this embodiment, for example, the case where multiple STA200s have different MAP types will be described. Furthermore, as an example, this embodiment envisions a situation where the shared AP determines the resource allocation for each STA associated with (or connected to) the shared AP.

[0197] When the MAP types differ among STA200s, AP100 (the shared AP) can, for example, inform the shared AP of the MAP type in the "Per STA Info" field (or, "Terminal-Specific Information"), which is configured within the Per AP Info field and is specific to each STA200. In other words, the MAP type (information indicating the category of coordinated communication) of each STA200 can be included in the Per STA Info (e.g., Terminal-Specific Information).

[0198] Additionally, AP100 can, for example, determine (or change) the format of MAP type dependency information (e.g., MAP Type Dependent Info) in the Per STA Info field based on the MAP type of each of the multiple STA200s.

[0199] Figure 18 This is a diagram illustrating an example of the MAP trigger frame format in this embodiment.

[0200] For example, such as Figure 18As shown, the General Information field can contain information (“#of STAs”) about the number of STA200s associated with multiple shared APs (e.g., AP#1, AP#2, ...). For example, the number of Per STA Info fields configured in each Per AP Info field can be determined based on information about the number of STA200s. For example, as... Figure 18 As shown, the number of STAs for each shared AP can be specified in the General Information field. Alternatively, a common number of STAs for multiple shared APs (e.g., maximum number of STAs) can be specified in the General Information field, and padding can be used to compensate for shared APs that do not meet the specified number of STAs. Although in Figure 18 The example shows a case where information related to the number of STAs is included in the general information, but it can also be configured within Per AP Info.

[0201] In addition, MAP types are not limited to such Figure 18 The settings shown in the Per STA Info field within the Per AP Info field can also be used, for example, with the method in Implementation 1. For example, information related to the overall MAP type in the general information (e.g., "total MAP type") can be used to notify the shared AP that there are multiple MAP types mixed together. Alternatively, for example, information (MAP type index) can be provided to the shared AP in the Per STA Info field, which is information about determining the MAP type for each shared AP from the overall MAP type (total MAP type) notified in the general information.

[0202] Figure 19 This is a diagram illustrating the method used in conjunction with the method of Implementation 1 for specifying the aforementioned MAP type. Additionally, Figure 20 This is a diagram illustrating an example of the definition of the general MAP type within the general information field, and an example of the definition of the MAP type index within the Per STA Info field.

[0203] like Figure 20 As shown, the presence of multiple MAP types can be indicated using a total MAP type, for example, within multiple MAP type elements (e.g., MAP type element 1, MAP type element 2, ...). Within each MAP type element, one of the multiple MAP types can be specified (in...). Figure 20 In the example, one of 0 to 4).

[0204] In addition, such as Figure 20As shown, MAP type indexes can be used, for example, to notify the MAP type elements corresponding to the MAP type of each STA200.

[0205] The shared AP can, for example, be based on the MAP type index, and the MAP type corresponding to each STA200 can be determined according to the following formula.

[0206] MAP type index variant = MAP type element(MAP type index value) + 1

[0207] For example, in Figure 20 In the context of the total MAP types, the case where MAP type index = 1 corresponds to MAP type element 2. Therefore, the shared AP can, for example, determine the MAP type corresponding to the MAP type element value of MAP type element 2 in the total MAP types. Furthermore, the relationship between the total MAP types and MAP type indices is not limited to... Figure 20 The relationship shown can also be other relationships.

[0208] In addition, Figure 18 and Figure 19 Within the Per AP Info field, in the Per STA Info section, you can set specific information for each STA200, for example. This specific information for each STA200 can include, for example, specific information that is independent of the MAP type (in other words, information common to multiple MAP types) and specific information that is dependent on the MAP type (in other words, information that differs depending on the MAP type).

[0209] Specialized information that does not depend on the MAP type may include, for example, the STA ID, MAP type, resource allocation, and UL / DL markings.

[0210] Additionally, the following information may be included in the special information that depends on the MAP type (e.g., MAP type dependency information (MAP TypeDependent Info)), similar to that in Implementation 5.

[0211] • In the case of C-SR: Shared AP transmit power, maximum allowable interference level of the shared AP, maximum transmit power of the shared AP, and interference level of the shared AP.

[0212] • In the case of JT or D-MIMO: transmit parameters (e.g., MCS, sequence number, ...).

[0213] • In the case of CBF: Suppressed STA ID, suppressed STA resource allocation information

[0214] • In the case of C-OFDMA: No information

[0215] Furthermore, regarding the STA ID, for example, a Medium Access Control (MAC) address (48 bits) can be used as an indicator for STA200s not associated with the shared AP. Alternatively, a "Short ID," a STA identifier with fewer bits than the MAC address, can be defined. This reduces the overhead of the STA ID. The Short ID can be defined, for example, within the Association ID specified in 11ax, or it can be assigned to a reserved AID12.

[0216] Additionally, for example, such as Figure 18 and Figure 19 As shown, the field length of Per STA Info is the same as that of Per APInfo in Implementation 5; it can be either a fixed length or a variable length. In other words, the size of Per STA Info (terminal-specific information) can be common across MAP types or can vary depending on the MAP type. The processing complexity and signaling volume are the same for Per APInfo in Implementation 5 when the field length of Per STA Info is both fixed and variable.

[0217] Alternatively, if, for example, the order of the shared APs has been pre-notified to the shared APs, and the shared APs can identify the fields corresponding to each shared AP within the MAP trigger frame, then the fields can be omitted. Figure 18 and Figure 19 The ID of the shared AP (e.g., AP ID) is shown in the PerAP Info field.

[0218] Thus, in this embodiment, AP100, in the MAP trigger frame, uses the MAP type field configured in the Per STA Info field to notify other AP100s of the MAP types of each of the multiple STA200s. Additionally, AP100, for example, notifies other AP100s of MAP type dependency information corresponding to the MAP types. In other words, in the MAP trigger frame, the format of the MAP type dependency information changes based on the MAP types of the multiple STA200s.

[0219] By setting this MAP trigger frame, even when multiple STA200s have different MAP types, AP100 can still notify other AP100s of control signals corresponding to each of the multiple MAP types, thus improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in coordinated communication can be improved.

[0220] Furthermore, although this embodiment illustrates, as an example, the resource allocation for each STA associated with (or connected to) the shared AP is determined by the sharing AP, it is not limited to this. For example, the resource allocation for each STA associated with the shared AP can also be determined by the shared AP.

[0221] (Implementation Method 7)

[0222] The structures of AP and STA in this embodiment can be the same as those in embodiment 1.

[0223] In this embodiment, for example, the following situation is described: the MAP types of multiple shared APs are different, but the MAP types of the STA200s under each shared AP are common.

[0224] For example, AP100 (the shared AP) can configure the Per STA Info for each STA200 in the Per AP Info field, and inform the other AP100 (the shared APs) of the common MAP type of STA200 in a field different from the Per STA Info field within the Per AP Info field. In other words, the MAP type (information indicating the category of coordinated communication) of multiple shared APs can be included in the Per AP Info (e.g., dedicated information).

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

[0226] Figure 21 This represents an example of the MAP trigger frame format in this embodiment.

[0227] For example, such as Figure 21As shown, similarly to implementation 6, the general information may include information (“#of STAs”) about the number of STAs associated with each of the multiple shared APs (e.g., AP#1, AP#2, ...). For example, the number of Per STA Info fields configured in each Per AP Info field may be determined based on the information about the number of STAs.

[0228] Furthermore, regarding the method for specifying the number of STAs, similar to implementation 6, the number of STAs for each shared AP can be specified, or a common number of STAs for multiple shared APs (e.g., a maximum number of STAs) can be specified, and padding can be used to compensate for shared APs that do not meet the specified number of STAs. Additionally, in Figure 21 Similar to implementation 6, although the case where information related to the number of STAs is included in general information is shown, it can also be configured in Per AP Info.

[0229] In addition, the MAP type is not limited to the case where it is set in the Per AP Info field. For example, similar to Implementation 6, the information related to the overall MAP type in the general information (total MAP type) can be used to notify the shared AP that there are multiple MAP types. In the Per AP Info, the following information (MAP type index) is notified to the shared AP, which is the information about determining the MAP type for each shared AP from the overall MAP type (total MAP type) notified in the general information.

[0230] exist Figure 21 In this context, the MAP type notified by each Per AP Info field can be used across STA200s under the shared AP corresponding to that Per AP Info.

[0231] In addition, Figure 21 Within the Per AP Info field, in the Per STA Info section, you can set specific information for each STA200, for example. This specific information for each STA200 can include, for example, specific information that is independent of the MAP type (in other words, information common to multiple MAP types) and specific information that is dependent on the MAP type (in other words, information that differs depending on the MAP type).

[0232] The proprietary information that does not depend on the MAP type may include, for example, the STA200's ID (STA ID), resource allocation, and UL / DL markings. Alternatively, the proprietary information that depends on the MAP type may be the same as in Implementation 6.

[0233] In addition, such as Figure 21 As shown, the field length of Per STA Info can be either fixed or variable, similar to the Per AP Info field in Implementation 5. In other words, the size of Per STA Info (terminal-specific information) can be common across MAP types or vary depending on the MAP type. The processing complexity and signaling volume of Per STA Info with fixed and variable field lengths are the same as those of Per APInfo in Implementation 5.

[0234] Alternatively, if, for example, the order of the shared APs has been pre-notified to the shared APs, and the shared APs can identify the field corresponding to each shared AP within the MAP trigger frame, then, similar to embodiment 6, the field can be omitted. Figure 21 The ID of the shared AP (e.g., AP ID) shown in the Per AP Info field.

[0235] Thus, in this embodiment, AP100, in the MAP trigger frame, uses the MAP type field configured in the Per AP Info field to notify other AP100s of the MAP type common to multiple STA200s under each shared AP. This reduces the signaling volume related to MAP type notification.

[0236] Additionally, AP100 may, for example, notify other AP100s of MAP type dependency information corresponding to the MAP type. In other words, the format of the MAP type dependency information in the MAP trigger frame changes based on the MAP type of the shared AP.

[0237] By setting this MAP trigger frame, even when multiple shared APs have different MAP types, AP100 can still notify other AP100s of control signals corresponding to each of the multiple MAP types, thus improving signaling efficiency. Therefore, according to this embodiment, communication efficiency in coordinated communication can be improved.

[0238] (Implementation Method 8)

[0239] The structures of AP and STA in this embodiment can be the same as those in embodiment 1.

[0240] In this embodiment, for example, the case where multiple STA200s have different MAP types will be described.

[0241] In cases where the MAP types differ between STA200s, AP100 (the sharing AP) can, for example, notify the other AP100 (the sharing AP) of the MAP type of each STA200 in the Per STA Info (e.g., terminal-specific information) field.

[0242] Additionally, AP100 may, for example, determine (or change) the format of MAP type dependency information (e.g., MAP Type Dependent Info) within Per STA Info based on the MAP type notified to each of the multiple STA200s.

[0243] Figure 22 This is a diagram illustrating an example of the MAP trigger frame format in this embodiment.

[0244] like Figure 22 As shown, in the MAP trigger frame, the Per STA Info field can be configured at the same level as the general information field. In other words, it can be configured in... Figure 22 The Per AP Info field is used to replace Figure 1 The Per APInfo field is shown in the format shown.

[0245] In addition, Figure 22 In the Per STA Info, for example, specific information specific to STA200 can be set. The specific information for each STA200 can include, for example, specific information that is independent of MAP type (in other words, information common to multiple MAP types) and specific information that is dependent on MAP type (in other words, information that differs depending on the MAP type).

[0246] Specific information that does not depend on the MAP type may include, for example, the STA200 ID (STA ID), MAP type, resource allocation, and UL / DL markings.

[0247] Additionally, the specific information that varies depending on the MAP type (e.g., MAP type dependency information, MAP TypeDependent Info) may include, for example, the following information, similar to that in Implementation 5.

[0248] • In the case of C-SR: Shared AP transmit power, maximum allowable interference level of the shared AP, maximum transmit power of the shared AP, and interference level of the shared AP.

[0249] • In the case of JT or D-MIMO: transmit parameters (e.g., MCS, sequence number, ...).

[0250] • In the case of CBF: Suppressed STA ID, suppressed STA resource allocation information

[0251] • In the case of C-OFDMA: No information

[0252] Figure 23 This is a diagram illustrating an example of MAP type specifications, where the MAP type differs according to STA200. In Figure 23 As an example, the method of embodiment 6 is compared with the method of embodiment 8.

[0253] In addition, Figure 23 As an example, the following situation is shown: AP ID1's shared AP has STA200s STA1 and STA2, while AP ID2's shared AP has STA2 and STA3. Figure 23 As shown, STA2 coordinates communication with AP ID1 and AP ID2, which are shared APs.

[0254] For example, the method in Implementation 6 is as follows: using the Per STA Info of each Per AP Info, the MAP type is indicated for each STA 200 under the shared AP. Thus, in the method of Implementation 6, for example, the MAP type of each STA under the shared AP is indicated. Figure 23 In the example shown, the Per AP Info corresponding to AP ID1 indicates the MAP type of STA1 and STA2 under the shared AP of AP ID1, and the Per AP Info corresponding to AP ID2 indicates the MAP type of STA2 and STA3 under the shared AP of AP ID2.

[0255] On the other hand, for example, the method of this embodiment 8 is a method of indicating the MAP type for each STA 200 using Per STA Info. Therefore, in embodiment 8, for example, the MAP type of each STA 200 is not indicated based on the shared AP associated with the STA 200. Figure 23 In the example shown, the MAP type of STA1, STA2, and STA3 is indicated in Per STA Info.

[0256] For example, if we focus on Figure 23Regarding STA2 (STA ID2), in Implementation 6, the MAP type is specified in two Per AP Info fields corresponding to AP ID1 and APID2 respectively, while in Implementation 8, the MAP type is specified in one Per STA Info field corresponding to STA ID2. Therefore, according to Implementation 8, compared to Implementation 6, the signaling related to the MAP type can be reduced.

[0257] In addition, such as Figure 22 As shown, the field length of Per STA Info can be either fixed or variable, similar to the Per AP Info field in Implementation 5. In other words, the size of Per STA Info (terminal-specific information) can be common across MAP types or vary depending on the MAP type. The processing complexity and signaling volume are the same for Per AP Info when the field length of Per STA Info is fixed or variable, respectively.

[0258] Furthermore, if STA200 is specified in the MAP trigger frame, each shared AP can determine the shared AP associated with (maintaining connection relationship) that STA200 is associated with. Therefore, it is not necessary to notify the shared AP of the shared AP ID (AP ID) in the MAP trigger frame.

[0259] Additionally, when using STA ID to specify STA200 in the MAP trigger frame, a unique STA ID can be assigned to each STA200 under multiple shared APs. For example, the following methods can be used to assign a unique STA ID when using AID or AID12.

[0260] • A method of unified management by using a shared ID space (e.g., a specified range) across the entire system and attaching unique AIDs. In this method, for example, AIDs can be managed by a shared AP, and AIDs can be attached to the STA200 directly or via the shared AP.

[0261] • A method of negotiating the use of a unique area of ​​AID space for each shared AP.

[0262] Thus, in this embodiment, AP100 notifies other AP100s of the MAP type field configured in the Per STA Info field of the MAP trigger frame, specifying the MAP type of each of the multiple STA200s. Additionally, AP100, for example, notifies other AP100s of MAP type dependency information corresponding to the MAP type. In other words, the format of the MAP type dependency information in the MAP trigger frame changes based on the respective MAP types of the multiple STA200s.

[0263] By setting this MAP trigger frame, even when multiple STAs 200 have different MAP types, AP 100 can still notify other APs 100 of control signals corresponding to each of the multiple MAP types, thus improving signaling efficiency. Furthermore, it can suppress the duplication of STA information such as MAP types, thereby reducing signaling. Therefore, according to this embodiment, communication efficiency in coordinated communication can be improved.

[0264] (Comparison between Embodiment 6, Embodiment 7 and Embodiment 8)

[0265] Figure 24 This is a diagram showing a comparison of the processing complexity and signaling volume related to the respective MAP trigger frame formats of Embodiments 6, 7, and 8.

[0266] For example, implementation 6 is a method in which Per STA Info is configured in the Per AP Info field and the MAP type is indicated in Per STA Info.

[0267] Alternatively, implementation 7 is a method in which Per STA Info is configured in the Per AP Info field, and the MAP type common to STA200 is indicated in a different area of ​​the Per AP Info field than Per STA Info.

[0268] Alternatively, implementation method 8 is as follows: Per AP Info is not configured, but the MAP type is indicated in Per STA Info.

[0269] like Figure 24 As shown, the processing complexity decreases, for example, in the order of Embodiment 7, Embodiment 6, and Embodiment 8. Furthermore, as... Figure 24 As shown, the signaling volume is less in the order of implementation method 8, implementation method 7, and implementation method 6.

[0270] For example, when reducing processing complexity is a priority, implementation method 7 can be applied (or selected). Alternatively, when reducing signaling volume is a priority, implementation method 8 can be applied (or selected).

[0271] (Implementation Method 9)

[0272] The structures of AP and STA in this embodiment can be the same as those in embodiment 1.

[0273] In this embodiment, for example, a method for switching between the methods of Embodiments 4 to 8 (or, MAP trigger frame format) will be described.

[0274] For example, the format category applied to the MAP trigger frame can be indicated in the general information field (e.g., a frame format of embodiments 4 to 8).

[0275] Figure 25 This diagram illustrates an example of the MAP trigger frame format in this embodiment. Figure 25 Here, as an example, we show an example of applying the frame format of implementation method 4.

[0276] like Figure 25 As shown, the general information field may contain information indicating the format category of the MAP trigger frame (e.g., MAP Format Type). AP100 may, for example, determine the format following the MAP Format Type field in the MAP trigger frame based on the format category indicated by the MAP Format Type.

[0277] Additionally, the format category specified by the MAP format type can be one of the following formats, for example.

[0278] • The format indicates the MAP type of each shared AP in the MAP type field of the general information (e.g., implementation 4).

[0279] • Indicate the MAP type format in the Per AP Info field (e.g., implementation 5).

[0280] • The format of indicating the MAP type is in the Per STA Info field within the Per AP Info (e.g., implementation 6).

[0281] • Configure Per STA Info within Per AP Info, and indicate the MAP type common to STA in a different area within Per AP Info than Per STA Info (e.g., implementation 7).

[0282] • Do not configure Per AP Info, but indicate the MAP type in the Per STA Info field (e.g., implementation 8).

[0283] In addition, the following methods can be listed as criteria for selecting format categories.

[0284] For example, a format with fewer total bits or a format that is easier to process can be selected. For example, when there are multiple formats that can indicate the MAP type configured for the shared AP (e.g., a common MAP type for 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, signaling volume) or a format that is easier to process (in other words, a format with less processing complexity) can be selected. Furthermore, the selection criteria for the format category are not limited to these criteria; for example, other criteria corresponding to the MAP type configuration for each shared AP and each STA200 under each shared AP can also be used.

[0285] For example, if the MAP type of AP100 (e.g., a shared AP) is different according to the shared AP, and the MAP type is the same within each AP (e.g., among its subordinate STA200), then the format of Implementation 5 can be selected; if the MAP type is different according to the shared AP and the STA200 subordinate to the shared AP, then the format of Implementation 6 can be selected.

[0286] In this way, AP100 can, for example, select (or switch) one of several formats of MAP trigger frames based on a selection criterion, and send a MAP trigger frame containing information indicating the category of the selected format (e.g., MAP format type). By switching formats, AP100 can, for example, select a format that is easier to process or has less signaling, depending on the MAP type settings of each shared AP and each STA200 under the shared AP.

[0287] Furthermore, although this embodiment describes a method for switching the MAP trigger frame format described in Embodiments 4 to 8 as an example, the candidate formats for switching are not limited to this, and may be at least some of the formats in Embodiments 1 to 8.

[0288] Furthermore, although this embodiment illustrates the case of specifying the MAP trigger frame format based on the MAP format type as an example, it is not limited to this. For example, the MAP trigger frame format (format type) can also be implicitly notified to the shared AP based on other parameters.

[0289] The above describes the various embodiments of this disclosure.

[0290] (Other implementation methods)

[0291] In the above implementation, the same method can also be applied to both DL and UL (in other words, the setting of the frame format).

[0292] Furthermore, although an example of MAP-related notification information in a MAP trigger frame has been described in the above embodiments, the notified information is not limited to the information shown in the above embodiments. For example, other information may be added, or at least a portion of the defined information may be deleted.

[0293] Furthermore, in the above embodiments, although an example definition of the frame control field is shown (for example, Figure 8 ), MAP type definition example (for example, Figure 9 and Figure 10 ), Example of defining a trigger type subfield (e.g., Figure 12 and Figure 14 ), and examples of the definition of the total MAP type and MAP type index (e.g., Figure 20 However, it is not limited to these definitions and can be defined as other values.

[0294] Furthermore, while the term "MAP type" is used to describe the category of MAP in the above embodiments, it is not limited to this and other terms may be used. For example, the term "Multi-AP coordination schemes" used in the specifications for the planning and development of 11be may also be used.

[0295] Furthermore, in the above embodiments, although the terms "shared AP" and "shared AP" are used to describe the AP that instructs the coordinated communication and the AP that is instructed to coordinate the communication, they are not limited to these terms and other terms may also be used.

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

[0297] This disclosure can be implemented in software, hardware, or software in cooperation with hardware. The functional blocks used in the above embodiments are implemented partially or wholly as LSIs (Large Scale Integration), and the processes described in the above embodiments can also be controlled partially or wholly by a single LSI or a combination of LSIs. An LSI can be composed of individual chips, or it can be composed of a single chip containing some or all of the functional blocks. An LSI can also include data input and output. Depending on the degree of integration, an LSI can also be referred to as an "IC (Integrated Circuit)," "System LSI," "Super LSI," or "Ultra LSI."

[0298] The method of integrating LSIs is not limited to LSIs; it can also be implemented using dedicated circuits, general-purpose processors, or special-purpose processors. Alternatively, LSIs can be used to fabricate programmable FPGAs (Field Programmable Gate Arrays), or reconfigurable processors that allow for reconfiguration of the connections or settings of the circuit blocks within the LSI. This disclosure can also be implemented for digital or analog processing.

[0299] Furthermore, if advancements in semiconductor technology or the emergence of other derivative technologies lead to integrated circuit technologies that can replace LSIs, these technologies could also be used to integrate functional blocks. There are also possibilities for applications such as biotechnology.

[0300] This disclosure can be implemented in all categories of devices, apparatuses, and systems with communication capabilities (collectively referred to as "communication devices"). A communication device may also include a wireless transceiver and processing / control circuitry. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these units. The wireless transceiver (transmitting unit, receiving unit) may also include an RF (Radio Frequency) module and one or more antennas. The RF module may also include an amplifier, an RF modulator / demodulator, or similar devices. Non-limiting examples of communication devices include: telephones (mobile phones, smartphones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, laptops, etc.), cameras (digital cameras, digital camcorders, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, e-book readers, remote health / telemedicine (remote healthcare / medical prescription) devices, vehicles or transportation vehicles with communication capabilities (cars, airplanes, ships, etc.), and combinations of the various devices described above.

[0301] Communication devices are not limited to portable or mobile devices, but also include all categories of devices, equipment, and systems that cannot be carried or fixed. Examples include smart home devices (home appliances, lighting equipment, smart meters or meters, control panels, etc.), vending machines, and all other "things" that can exist on the IoT (Internet of Things) network.

[0302] In addition to data communication via cellular systems, wireless LAN (Local Area Network) systems, and communication satellite systems, communication also includes data communication via a combination of these systems.

[0303] In addition, the communication device also includes devices such as controllers or sensors that are connected or linked to a communication device performing the communication functions described in this disclosure. For example, it includes a controller or sensor that generates control signals or data signals used by the communication device to perform the communication functions of the communication device.

[0304] In addition, the communication device includes infrastructure equipment that communicates with or controls the various devices described above (not limited to these), such as base stations, access points, and all other devices, equipment, and systems.

[0305] One embodiment of the base station disclosed herein includes: a control circuit that determines the format of a control signal based on the type of coordinated communication; and a transmission circuit that transmits the control signal to other base stations according to the format.

[0306] In one embodiment of this disclosure, the control signal includes general information containing information common to multiple base stations and dedicated information specific to each of the multiple base stations. The control circuit determines the format of at least one of the general information and the dedicated information based on the category.

[0307] In one embodiment of this disclosure, information representing the category is included in a field in the general information used to notify the category.

[0308] In one embodiment of this disclosure, information representing the category is included in a field for notification triggering type in the general information.

[0309] In one embodiment of this disclosure, in the general information, the information that triggers the coordination communication is included in a field for notifying the trigger type, and the information indicating the category is included in a field that depends on the trigger type.

[0310] In one embodiment of this disclosure, information representing the respective categories of the plurality of base stations is included in the general information.

[0311] In one embodiment of this disclosure, information representing the respective categories of the plurality of base stations is included in the dedicated information.

[0312] In one embodiment of this disclosure, the size of the proprietary information is either common across the categories or differs depending on the category.

[0313] In one embodiment of this disclosure, the dedicated information includes terminal-specific information specific to a terminal connected to a base station corresponding to the dedicated information, indicating that information of the category is included in the terminal-specific information.

[0314] In one embodiment of this disclosure, the control circuit performs resource allocation for the terminal connected to the other base stations.

[0315] In one embodiment of this disclosure, the control signal includes general information containing information common to multiple base stations and terminal-specific information specific to multiple terminals, indicating that information of each of the multiple terminals is contained in the terminal-specific information, and the control circuit determines the format of the terminal-specific information based on the category.

[0316] In one embodiment of this disclosure, the size of the terminal-specific information is either common across the categories or varies depending on the category.

[0317] In one embodiment of this disclosure, the control circuit selects one of the plurality of formats based on a selection criterion, and the transmitting circuit transmits the control signal, the control signal containing information indicating the category of the selected format.

[0318] In a communication method according to one embodiment of this disclosure, a base station determines the format of a control signal based on the type of coordinated communication; and sends the control signal to other base stations according to the format.

[0319] The entire contents of the specification, drawings and abstract of the specification contained in Japanese Patent Application No. 2020-156398, filed on September 17, 2020, are incorporated herein by reference.

[0320] Industrial applicability

[0321] One embodiment of this disclosure is useful for wireless communication systems.

[0322] Explanation of reference numerals in the attached figures

[0323] 100AP

[0324] 101 Control Department

[0325] 102 is a control signal generation unit for STA.

[0326] 103 is used for the control signal generation unit of the AP.

[0327] 104, 203 Transmitting signal generation unit

[0328] 105, 201 Wireless Transceiver Unit

[0329] 106, 202 Receive Signal Demodulation / Decoding Unit

[0330] 200STA

Claims

1. A base station, comprising: The control circuit, based on the MAP category of the coordinated communication, determines the format of control signals including parameters independent of the MAP category and parameters dependent on the MAP category that correspond to the shared AP performing the coordinated communication; as well as The transmitting circuit sends the control signal to the shared AP according to the stated format. The field length of the parameters that depend on the MAP category is variable according to the MAP category. The parameters, which are independent of the MAP category, contain the identification information of the shared AP.

2. The base station as described in claim 1, wherein, Information indicating the category is contained in parameters that are independent of the category.

3. The base station as described in claim 1, wherein, The control signal includes terminal-specific information specific to the terminal connected to the shared AP. Information indicating the category is included in the terminal-specific information.

4. The base station as described in claim 3, wherein, The control circuit performs resource allocation for the terminal connected to the shared AP.

5. The base station as described in claim 1, wherein, The control signals include terminal-specific information specific to each of the multiple terminals. The information representing the category for each of the multiple terminals is included in the terminal-specific information. The control circuit determines the format of the terminal-specific information based on the category.

6. The base station as described in claim 5, wherein, The size of the terminal-specific information may be common across the categories, or may differ depending on the category.

7. The base station as described in claim 1, wherein, The control circuit selects one of the multiple formats based on a selection criterion. The transmitting circuit sends the control signal, which contains information indicating the category of the selected format.

8. A communication method, Based on the MAP category of the coordinated communication, the base station determines the format of control signals, including parameters independent of the MAP category and parameters dependent on the MAP category, corresponding to the shared AP performing the coordinated communication; and The base station sends the control signal to the shared AP according to the specified format. The field length of the parameters that depend on the MAP category is variable according to the MAP category. The parameters, which are independent of the MAP category, contain the identification information of the shared AP.

Images