Access point and control method for coordinated communication

Abstract

An AP device includes: a transmission / reception unit that receives information relating to coordinated communication; and a control circuit that determines whether to operate as a coordinated AP.

Description

Technical Field

[0001] The present disclosure relates to an access point and a control method for coordinated communication. Background Art

[0002] As the successor standard of 802.11ax (hereinafter referred to as "11ax"), the IEEE (the Institute of Electrical and Electronics Engineers) 802.11 standard, the technical specifications of 802.11be (hereinafter referred to as "11be") are being planned and formulated. 11ax is also called "High Efficiency (HE)" and 11be is also called "Extreme High Throughput (EHT)". In addition, the required specifications for the successor standard of 11be (sometimes called "UHR (Ultra High Reliability)", hereinafter referred to as "beyond 11be") are also being discussed.

[0003] Prior art literature

[0004] Non-patent literature

[0005] Non-patent document 1: IEEE 802.11-18 / 1982r0, Consideration on multi-APCoordination for EHT

[0006] Non-patent document 2: IEEE 802.11-19 / 0103r1, AP Coordination in EHT

[0007] Non-patent document 3: IEEE Std 802.11-2020, December 2020 Summary of the invention

[0008] However, there has been insufficient research on control methods for multi-AP (Access Point) coordination (hereinafter referred to as "coordinated communication"), such as methods for selecting coordinated communication, methods for starting coordinated communication actions, or actions when direct transmission and reception between APs is not possible.

[0009] Non-limiting embodiments of the present disclosure facilitate providing access points and control methods for coordinating communications.

[0010] An access point according to an embodiment of the present disclosure includes: a transceiver for receiving information related to coordinated communication; and a control circuit for determining whether to operate as an access point for controlling coordinated communication.

[0011] It should be noted that these general or specific aspects may be implemented by a system, an apparatus, a method, an integrated circuit, a computer program or a recording medium, or may be implemented by any combination of systems, apparatuses, methods, integrated circuits, computer programs and recording media.

[0012] According to the present invention, an access point and a control method for coordinated communication can be provided.

[0013] More advantages and effects of an embodiment of the present disclosure will be explained through the description and drawings. These advantages and / or effects are provided by several embodiments, and the features described in the description and drawings, but not necessarily all of them need to be provided in order to obtain one or more of the same features. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 It is a diagram showing the format of an element.

[0015] Figure 2 This is a diagram showing a table of element IDs (Identifiers).

[0016] Figure 3 This is a diagram showing the structure of a STA (Station).

[0017] Figure 4 It is a diagram showing the structure of AP.

[0018] Figure 5 It is a diagram showing the overall steps.

[0019] Figure 6 This is a diagram showing an example of an action sequence for determining whether to act as a coordinator AP (Coordinator AP).

[0020] Figure 7 This is a diagram showing a combination of the availability information of the coordinator AP and coordinated AP (Coordinated AP), and the coordinator selection result.

[0021] Figure 8 This diagram shows an example format of a coordination bitmap sent through multiple AP elements.

[0022] Fig. 8A This is a diagram showing an example format of an element including capability information of a beyond 11be terminal.

[0023] Figure 8B This is a diagram showing an example format of a multi-AP capability information (Capabilities Information) field.

[0024] Fig. 9 This is a diagram showing an example of a multi-AP setup request (Setup Request) specified by a multi-AP element.

[0025] Fig.10 This is a diagram showing another example of an operation sequence for determining whether to operate as a coordinator AP.

[0026] Fig. 10A This is a diagram showing an example of a format for transmitting the operation status of multiple APs.

[0027] Fig.11 This is a diagram showing still another example of an action sequence for determining whether to act as a coordinator AP.

[0028] Fig.12 is a diagram showing an example of an AP notification format specified by a multi-AP element.

[0029] Fig.13 This is a diagram showing an example of an operation sequence in which AP1 and AP2 are activated in order and a coordinator AP is selected after AP2 is activated.

[0030] Fig.14 This is a diagram showing a flowchart of an operation example using backhaul communication.

[0031] Fig.15 is a diagram representing another overall step.

[0032] Fig.16 This is a diagram showing an example of the configuration of AP and STA.

[0033] Fig.17 This is a diagram showing an example of a coordination start request specified by a multi-AP element.

[0034] Fig.18 This is a diagram showing another configuration example of AP and STA.

[0035] Fig.19 This is a diagram showing still another configuration example of AP and STA.

[0036] Fig. 20 Is a diagram representing a coordination bitmap.

[0037] Fig.21 This is a diagram showing a coordination bitmap in which bits indicating "permission of coordinator AP", "permission of coordinated AP", and "permission of each coordination method" are provided.

[0038] Fig. 22 This is a diagram showing a coordination bitmap in which bits indicating the availability of each coordination method are provided for each "availability of coordinator AP" and "availability of coordinated AP".

[0039] Fig.23 This is a diagram showing a coordination bitmap in which bits indicating "permission of coordinator AP" and "permission of coordinated AP" are provided for each coordination method. DETAILED DESCRIPTION

[0040] <About multi-AP coordination>

[0041] In 11be and beyond 11be, applications of coordinated communication in which an access point (also referred to as a base station (AP STA) and hereinafter referred to as an AP) coordinates to send and receive data with each terminal (also referred to as a non-AP STA and hereinafter referred to as a STA) are studied.

[0042] As a structure for coordinated communication, a method is being studied for an AP that controls coordinated communication (also called "coordinator AP, primary AP, controller AP, or master AP. hereinafter referred to as "coordinator AP") to control an AP that is controlled to coordinate communication (also called "coordinated AP, secondary AP, agent AP, or slave AP. hereinafter referred to as "coordinated AP") (refer to non-patent document 1).

[0043] On the other hand, as a method of coordinated communication, C-OFDMA (Coordinated Orthogonal Frequency Division Multiple Access), C-TDMA (Coordinated Time Division Multiple Access), C-SR (Coordinated Spatial Reuse), CBF (Coordinated Beamforming), JT (Joint Transmissions), dynamic AP selection (dynamic AP selection), etc. have been proposed (refer to non-patent document 2).

[0044] In addition, in IEEE802.11, elements are included as information to be transmitted and received. Figure 1 The format of the element is shown in Figure 2 A table of element IDs is shown in FIG. 1 (see non-patent document 3).

[0045] <Implementation method 1>

[0046] In one aspect of the present invention, when at least two APs are deployed, it is determined whether each AP is to operate as a coordinator AP to perform multi-AP coordinated communication.

[0047] [STA structure]

[0048] Figure 3 STA includes a transmission packet generation unit 301, a control signal generation unit 302, a wireless transceiver unit 303, a reception packet decoding unit 304, and a reception quality measurement unit 305. The control circuit 306 may also be composed of at least one of the transmission packet generation unit 301, the control signal generation unit 302, the reception packet decoding unit 304, and the reception quality measurement unit 305. The packet is sometimes referred to as a physical layer (PHY: physical layer) protocol data unit (PPDU: PHY protocol data unit). In addition, the packet and / or PPDU may also be a signal for encoding and modulating a medium access control (MAC: medium access control) frame (MPDU: MAC protocol data unit).

[0049] The transmission packet generation unit 301 generates a transmission packet based on the input data and the control signal generated by the control signal generation unit 302, and outputs it to the wireless transmission and reception unit 303. The input data may be referred to as a media access control service data unit (MSDU: MAC service data unit) or higher layer data.

[0050] The control signal generating section 302 generates a control signal based on input data, control information output from the reception packet decoding section 304 , reception quality measured by the reception quality measuring section 305 , and an internal state, and outputs the control signal to the transmission packet generating section 301 .

[0051] The wireless transmission and reception unit 303 converts the transmission packet generated by the transmission packet generation unit 301 into a wireless signal and outputs it to the antenna. In addition, the wireless transmission and reception unit 303 receives a wireless signal from the antenna and outputs the received signal to the reception packet decoding unit 304 and the reception quality measurement unit 305.

[0052] The reception packet decoding section 304 outputs output data obtained by decoding the reception signal received from the wireless transmission / reception section 303 , and outputs control information to the reception quality measurement section 305 and the control signal generation section 302 .

[0053] The reception quality measurement unit 305 measures the reception quality based on the reception signal received from the wireless transmission / reception unit 303 , the control information received from the reception packet decoding unit 304 , and the internal state.

[0054] [AP Structure]

[0055] Figure 4 4 is a diagram showing the structure of an AP. The AP includes a transmission packet generation unit 401, a control signal generation unit 402, a wireless transceiver unit 403, a reception packet decoding unit 404, a reception quality measurement unit 405, and a coordination control unit 406. Figure 3 The STA configuration shown in the figure has the configuration of the coordination control unit 406 added. The control circuit 407 may be constituted by at least one of the transmission packet generation unit 401, the control signal generation unit 402, the reception packet decoding unit 404, the reception quality measurement unit 405 and the coordination control unit 406.

[0056] The sending packet generating unit 401, the control signal generating unit 402, the wireless transceiver unit 403, the receiving packet decoding unit 404, and the receiving quality measuring unit 405 may also have the same functions as the sending packet generating unit 301, the control signal generating unit 302, the wireless transceiver unit 303, the receiving packet decoding unit 304, and the receiving quality measuring unit 305.

[0057] The coordination control unit 406 generates coordination control information for performing coordinated communication based on input data, control information output by the reception packet decoding unit 404 , reception quality measured by the reception quality measurement unit 405 , and internal states, and outputs the information to the control signal generation unit 402 .

[0058] <Example 1>

[0059] Hereinafter, as an example, a case will be described in which, when AP1 is set in a state of periodically transmitting a beacon, AP2 is newly set, started, or / and restarted. Figure 5 The overall steps are shown in FIG. Figure 5 As shown, after the multi-AP setting S501, each AP performs multi-AP measurement S502 and multi-AP transmission S503.

[0060] In multi-AP setting S501 , the AP negotiates with surrounding APs to decide whether the AP is to act as a coordinator AP or a coordinated AP.

[0061] In multi-AP measurement S502, AP and STA measure the amount of interference and send the measurement results to each other. It should be noted that the coordinator AP can also specify the measurement object. The measurement can be performed periodically or, for example, when the path loss changes. In the case where the coordination method to be operated is, for example, C-TDMA or C-OFDMA, since there is no need to perform control based on the amount of interference, multi-AP measurement may not be performed. Therefore, since there is no need to perform interference measurement of STA, the power consumption of STA can be reduced. In addition, since there is no need to send the interference measurement result, the throughput can be prevented from decreasing.

[0062] In multi-AP transmission S503, the sharing AP (i.e., the AP that obtains TXOP (Transmission Opportunity)) can also specify the transmission and reception of coordinated communication. Coordinated communication can also be performed only when the coordinator AP becomes a sharing AP. When the coordinated AP becomes a sharing AP, coordinated communication can also be performed by the designation (e.g., triggering) of the coordinator AP.

[0063] An example is shown in which the AP obtains TXOP for coordinated communication in multi-AP transmission S503, but the service interval for coordinated communication can also be set in multi-AP setting S501, and in multi-AP transmission S503, coordinated communication is performed based on the set service interval (for example, AP1 and AP2 transmit in a dedicated service interval). It should be noted that the setting of the service interval can also be, for example, the setting of TWT (Target Wake Time) containing setting information for coordinated communication.

[0064] In addition, each AP (coordinator AP and coordinated AP) may perform transmission and reception with each STA associated with it individually, in addition to coordinating communication.

[0065] Figure 6 FIG. 4 shows an example of an action sequence in which AP2 decides whether to act as a coordinator AP through negotiation with AP1 in multi-AP setting S501.

[0066] The AP1 broadcasts or notifies the capability information related to the coordinated communication. For example, the availability information (hereinafter referred to as "coordination bitmap") of the coordinator AP and the coordinated AP may be included in the beacon.

[0067] like Fig. 20 As shown, the coordination bitmap can also be composed of "a bit indicating whether the coordinator AP is allowed" and "a bit indicating whether the coordinated AP is allowed". The order of the bits can also be reversed. For example, bit 1 can represent "yes" and bit 0 can represent "no", or bit 1 can represent "no" and bit 0 can represent "yes".

[0068] In S601, AP2 may also search for surrounding APs when starting up (also called "exploring" or "scanning").

[0069] In S602, AP2 may also receive beacons periodically sent by AP1, and obtain capability information related to coordinated communication (e.g., coordination bitmap) contained in the received beacon. AP2 may also send a probe request (Probe Request), receive a probe response (Probe Response) sent by AP1 in response to the probe request, and obtain capability information related to coordinated communication from the probe response.

[0070] In S603, AP2 determines the coordinator AP based on information (internal information) equivalent to the received capability information related to coordinated communication of AP1 and the capability information related to coordinated communication of AP2 itself. For example, the possibility of coordinated communication and the coordinator AP may be selected based on internal information equivalent to the received coordination bitmap of AP1 and the coordination bitmap of AP2.

[0071] In S604, when it is determined that coordinated communication is possible, AP2 may send a multi-AP setting request to AP1 as a coordinated communication start request (coordination start request). The selection result of the coordinator AP may be included in the multi-AP setting request.

[0072] In S605, AP1 may also send a multi-AP setup response (Setup Response) to AP2 as a response to the coordination start request (coordination start response). The coordinator AP selection result may also be included in the multi-AP setup response. AP1 may also send an Ack (acknowledge) instead of a multi-AP setup response.

[0073] Figure 7 , which is based on the internal information of the coordination bitmap of AP1 and the coordination bitmap of AP2, shows an example of the combination of the coordinator AP permission information and the coordinated AP permission information for each AP, and the selection result of the coordinator AP. Figure 7 The combination shown in the figure can be used to coordinate communication and the selection of the coordinator AP. Figure 7 In the case where both the coordinator AP and the coordinated AP in the coordination bitmap are "not possible", coordinated communication is obviously not possible, so it is not recorded.

[0074] Figure 7 in 1 (both AP1 and AP2 are "yes", both the coordinator AP and the coordinated AP are "yes"), the AP with more coordinated APs or associated STAs can also be used as the coordinator AP. In this case, the AP can also include at least one of the coordinated AP number and the associated STA number in the multi-AP setting request to be sent. 2 (both AP1 and AP2 are only coordinator APs that are "available"), it can also be determined that coordination is not possible. Alternatively, if both AP1 and AP2 are possible, a coordination method that does not require one to be a coordinator AP and the other to be a coordinated AP (for example, C-TDMA or dynamic AP selection) is selected, and both AP1 and AP2 can be coordinator APs, or neither the coordinator AP nor the coordinated AP can be selected. 3 (AP1 and AP2 are both "available" APs that are only coordinated), it can also be determined that coordination is not possible. Alternatively, if both AP1 and AP2 are capable of action, a coordination method that does not require one to be a coordinator AP and the other to be a coordinated AP is selected, and both AP1 and AP2 can be coordinated APs, or neither the coordinator AP nor the coordinated AP can be selected.

[0075] When the AP sending the coordination bitmap is a coordinated AP logged in to another coordinator AP, the availability of the coordinator AP in the coordination bitmap may be set to available, or the item "coordinated AP logged in to another coordinator AP" may be added to the coordination bitmap.

[0076] Thus, in multi-AP setting S501, the AP selects a coordinator AP based on information equivalent to the coordination bitmap notified by other APs and its own coordination bitmap, and can perform multi-AP measurement S502 and multi-AP transmission S503 under the control of the coordinator AP.

[0077] The coordination bitmap may also include information on the coordination modes in which each AP can operate (e.g., C-TDMA, C-OFDMA, C-SR, CBF, JT, dynamic AP selection, etc.). The coordination bitmap may be as follows: Fig.21 The coordination bitmap shown in FIG. 1 is a bit indicating whether each coordination mode is available for each AP, or a bit indicating whether each coordination mode is available for each AP may be a bitmap as shown in FIG. Fig. 22 The coordination bitmap shown in FIG. 1 is a bit indicating whether each coordination method is feasible or not for each "coordinator AP" and "coordinated AP". It can also be as follows Fig.23 The coordination bitmap shown in the figure is a bitmap that indicates "whether the coordinator AP is available" and "whether the coordinated AP is available" for each coordination mode. Fig.21 , Fig. 22 and Fig.23In the coordination method, the order can be different orders or a specified order. It can be only a part of the coordination methods, or it can include coordination methods other than those exemplified. In this case, the coordination method used in the coordinated communication can be limited to the coordination method that can be operated by all APs based on the information of the coordination method contained in the coordination bitmap. In this case, for example, the coordination method that can be operated can also be notified in the multi-AP setting request. In this way, the coordination method corresponding to the function of the AP to be coordinated can be selected. In addition, when using Fig. 22 and Fig.23 In the case of the coordination bitmap shown, Figure 7 Zhongwei 1 (both AP1 and AP2 are “yes”, both the coordinator AP and the coordinated AP are “yes”), an AP that can operate in more coordination modes can also be set as the coordinator AP.

[0078] AP2 may also construct a BSS (Basic Service Set) (also called "the start of a BSS") after multi-AP setting S501. By constructing a BSS after multi-AP setting S501, it is possible to specify a primary CH corresponding to the coordination method. For example, when operating in C-SR, CBF, or JT, AP2 can easily allocate the same transmission frequency band required for coordinated communication by specifying the same primary CH as AP1. For example, when operating in C-OFDMA, AP2 can easily allocate different transmission frequency bands required for coordinated communication by specifying a primary CH different from AP1.

[0079] Alternatively, each AP has a coordinated AP list, and the coordinator AP adds the APs that are coordinated APs in the multi-AP setting S501 to the coordinated AP list. In addition, becoming a coordinator AP and becoming a coordinated AP (included in the coordinated AP list) may be referred to as "joining a coordination group (or coordination set)".

[0080] It can also be that as a response to the multi-AP request sent by AP2, when AP1 successfully sends a multi-AP setup response, that is, when AP2 receives a multi-AP setup response, or when AP1 receives an Ack for a multi-AP setup response, it is considered that the multi-AP Setup negotiation is successful.

[0081] Alternatively, AP2 may include "coordinator AP candidates or other multi-AP related parameter candidates" in a multi-AP setting request and AP1 may send a multi-AP setting response including "whether to agree to the candidate", or may send a response including "agree / request change / reject (candidate)".

[0082] When a multi-AP setting response indicating "agreement" is successfully sent, it is determined that the multi-AP setting negotiation is successful and the coordinator AP / coordinated AP is determined.

[0083] When a multi-AP setting response indicating "required change" is successfully sent, AP2 may also send a multi-AP setting response including whether to agree to the change of the coordinator AP / coordinated AP.

[0084] When a multi-AP setting response indicating "reject" is successfully sent, it is determined that the multi-AP setting negotiation fails without determining the coordinator AP / coordinated AP.

[0085] When the multi-AP setting negotiation is successful, the coordinator AP may also add the AP of the negotiation object (ie, the coordinated AP) to the coordinated AP list.

[0086] The coordinator AP can assign the coordination group ID (or coordination set ID) as an identifier for identifying the coordination group (or coordination set) to the coordination group (or coordination set). It should be noted that the coordination group ID can also be assigned when changing the multi-AP setting request / response or after negotiation by changing the request / response. The coordination group ID can also be set to an ID that is uniquely identified in the group of the coordinator AP's ID and the coordination group ID, that is, an ID unique to each coordinator AP's ID. AP can also join multiple coordination groups. In addition, the coordinator AP can also manage the group of coordination group IDs and coordinated AP lists for one coordination group. The coordination group ID can be notified to the coordinated AP, or it can be notified to other APs through beacons, etc. A list of the IDs of the APs contained in the coordinator AP and the coordinated AP list (such as BSS ID, Mac address, BSS color, etc.) can also be used as a coordination AP list, and notified to other APs and STAs through beacons, etc.

[0087] For an already established coordination group (e.g., a coordination group formed by AP1 and AP2), an AP (e.g., AP3) that has not joined the coordination group can also join the coordination group (e.g., a coordination group formed by AP1 and AP2) by sending a multi-AP setting request to the AP (e.g., AP1) that constitutes the coordination group and conducting negotiation. For example, when AP3 identifies the coordination group that AP1 joins the coordination group ID contained in the beacon through the coordination group ID contained in the beacon of AP1, a multi-AP setting request including the coordination group ID contained in the beacon can also be sent to AP1. AP3 can also join the coordination group by receiving a multi-AP setting response from AP1.

[0088] Although the example of using a multi-AP setup request as a coordination start request and a multi-AP setup response as a coordination start response is shown, AP2 may also send a frame that does not require a response, such as an Announcement or an Advertisement, instead of a multi-AP setup request. In this case, AP1 may also send back an Ack frame instead of a multi-AP setup response.

[0089] The above shows an example of an operation in which AP2 sends a coordination start request (e.g., a multi-AP setup request) to AP1, but AP2 may also send a coordination start request (e.g., a multi-AP setup request) by broadcast. For example, when a coordination group includes multiple APs, by sending by broadcast, coordination start requests can be sent to multiple APs included in the coordination group at the same time.

[0090] [Format example]

[0091] You can also use Figure 1 The element format shown in FIG. 1 is used to notify control information related to multiple APs (such as a coordination bitmap). For example, Figure 2 The element ID table shown has element ID = 255 and element ID extension (Extension) = 111 as a multi-AP element. The value of the element ID extension is set to 111 as an example, but it can also be other values ​​indicating that the element is a multi-AP element. The multi-AP element can be included in the information of the management frame (for example, beacon, probe response, association request (Association Request), re-association request (Re Association Request), association response (Association Response), or re-association response (Re Association Response) frame), or multi-AP setting request frame, multi-AP setting response frame, and can also be included in other action frames (Action frame) newly defined in the 11be standard or subsequent standards. In addition, control information related to multiple APs can also be notified in a format other than the element format. The multi-AP element can also be set to other names (for example, a multi-AP information element (Information element)).

[0092] Figure 8 An example of sending a coordination bitmap in a format using multiple AP elements is shown in FIG. Figure 8In the example of the multi-AP element shown, the type (Type) value used to send the coordination bitmap is set to 0 (type = 0). It should be noted that the multi-AP setting request or multi-AP setting response can also use other type values ​​of multi-AP elements. The content can also be changed according to the transmission method of the coordination bitmap (including the case of the beacon, the case of the multi-AP setting request, etc.). Figure 8 As shown, the element containing the field indicating whether or not it can act as a coordinator AP (for example, a coordination bitmap) can also be called a multi-AP status variant (Status variant), a multi-AP advertisement variant (Advertisement variant), a multi-AP operation variant (Operation variant), a multi-AP configuration variant (Configuration variant), a multi-AP setup information variant (SetupInformation variant), etc.

[0093] Figure 8 The coordination bitmap field can also be set to Fig. 20 The coordination bitmap shown.

[0094] The numAP field may also be set to the number of coordinated APs in the coordination group that includes the corresponding AP.

[0095] The numSTA field can be set to the number of STAs associated with the corresponding AP, or the number of STAs associated with the AP in the coordination group. Figure 7 of 1, it can be added to the coordination bitmap only when both the coordinator AP and the coordinated AP are "available". numAP or numSTA can also be sent only when the received AP is in use.

[0096] Alternatively, use Figure 8 The multi-AP element includes information related to whether it can act as a coordinator AP (coordination bitmap information) in an element (for example, called a "UHR" capability element (Capabilities element)) that contains capability information of beyond 11be terminals (including APs. For example, AP1 and AP2).

[0097] Fig. 8A An example of the format is shown in . The element ID field is set to a value (255) indicating that the element includes an element ID extension field.

[0098] The Length field contains information related to the length of the element.

[0099] The Element ID extension field contains a value (for example, 200) indicating that the element is a UHR capability element.

[0100] The UHR MAC capability information field includes information indicating whether the terminal supports optional functions of the MAC layer of beyond 11be, and includes a plurality of fields (not shown) corresponding to each optional function.

[0101] The UHR PHY capability information field includes information on whether the terminal supports optional functions of the PHY layer of beyond be, and includes a plurality of fields (not shown) corresponding to each optional function.

[0102] The multi-AP capability information field contains information indicating whether the terminal (including AP) supports optional functions related to multi-AP coordination. The multi-AP capability information field is set as an optional field. When the AP sends a UHR capability element, the multi-AP capability information field can be included in the UHR capability element. In the case where the STA sends a UHR capability element, the multi-AP capability information field may not be included in the UHR capability element.

[0103] Figure 8B An example of the format of the multi-AP capability information field is shown in FIG.

[0104] The coordinator AP mode supported (mode supported) subfield indicates whether the AP can act as a coordinator AP.

[0105] The coordinated AP mode support subfield indicates whether the AP can act as a coordinated AP.

[0106] The combination of the coordinator AP mode support and coordinated AP mode support subfields may also be referred to as a “coordination bitmap”.

[0107] The maximum number of coordinated APs subfield contains information related to the maximum number of coordinated APs that can be added when the AP acts as a coordinator AP. It should be noted that when the value of the maximum number of coordinated APs subfield is 0, it can also be specified to indicate that the coordinator AP action is not supported and the coordinator AP mode support subfield is omitted.

[0108] The Supported coordination types subfield contains information related to the coordination modes (C-TDMA, C-OFDMA, C-SR, CBF, JT, dynamic AP selection, etc.) supported by the AP.

[0109] Multi-AP setup request and multi-AP setup response can also be defined as a management frame. Or, for example, you can define a multi-AP action frame with a category set to multi-AP as an action frame, and define a multi-AP setup request frame or a multi-AP setup response frame as a subtype.

[0110] Multi-AP setup request and multi-AP setup response are defined by other types of values ​​of multi-AP elements, and the content may also be changed according to the purpose (including the case of beacon, included in the case of setup request, etc.). In addition, Figure 8 , Fig. 8A The frame of the coordination bitmap may also include part of the information of the coordination bitmap. In addition, each bit of the coordination bitmap may also be included in different frames. For example, Figure 8 (Multi-AP element) contains the permission information of the coordinator AP and omits the permission information of the coordinated AP. Alternatively, Fig. 8A (UHR Capability Element) includes the availability information of the coordinated AP and omits the availability information of the coordinator AP.

[0111] The multi-AP setting request frame may also be defined as a frame in which the type value of the multi-AP element is set to 1 (type=1). Fig. 9 An example of a multi-AP setting request in which the type value of the multi-AP element is specified as 1 is shown.

[0112] exist Fig. 9 In the coordinator AP ID, the coordinator AP ID indicates the ID of the AP that becomes the coordinator AP. For example, when AP1 acts as the coordinated AP with AP3 as the coordinator AP, when AP1 is selected as the AP to be the target of this multi-AP setting action (determination using the coordination bitmap), the coordinator AP ID may also be set to the ID of AP3. Information indicating whether it is a coordinator (1 bit) may also be used instead of the coordinator AP ID.

[0113] The coordination type (Coordinate Type) may also indicate the coordination mode (C-TDMA, C-OFDMA, C-SR, CBF, JT, dynamic AP selection, etc.).

[0114] The information may be set as control information in each coordination method, or may include control information of multiple coordination methods that can be operated. The information contained in the information may be, for example, a time slot or a transmission start timing and a transmission interval in the case of C-TDMA, a maximum interference power or a path loss detection threshold (maximum or minimum value) in the case of C-SR, CBF or JT, or a switching detection power threshold and the number of front / rear protection times in the case of dynamic AP selection.

[0115] The multi-AP setting request may include the ID of the multi-AP coordination group, and the coordinator AP ID may also be set to the ID of the multi-AP coordination group. The multi-AP setting request may also include a coordinated AP list.

[0116] Shown is an example of a multi-AP element specified in the multi-AP setup request, but the field following the coordinator AP ID may also be included as a field other than the element in the multi-AP setup frame (Setup frame).

[0117] Multi-AP setting response can be set to Fig. 9 The format shown in FIG. 1 may also be set to include either "candidate for approval" or "candidate for approval / request for change / rejection". For example, the format may be made selectable, and in the case where AP1 becomes the coordinator AP, the format may be set to Fig. 9 The format shown is set to include any one of "candidate for approval" and "candidate for approval / change request / rejection" when AP1 becomes the coordinated AP.

[0118] The coordination type included in the multi-AP setting response may also be set to a coordination mode in which both AP1 and AP2 can operate.

[0119] <Example 2>

[0120] In Example 1, the following embodiment is shown, that is, in the multi-AP setting S501, the capability information related to the multi-AP is included in the beacon or the detection response (for example, the coordination bitmap), and in Example 2, the following embodiment is shown, that is, in the multi-AP setting S501, the capability information related to the multi-AP is included in the multi-AP setting request (for example, the coordination bitmap).

[0121] Fig.10 FIG. 4 shows another example of an action sequence for deciding whether to act as a coordinator AP through negotiation between AP1 and AP2 in multi-AP setting S501.

[0122] In S1001, AP2 may also search for surrounding APs when starting up.

[0123] In S1002, AP2 receives beacons periodically sent by AP1. AP2 may also send a probe request and receive a probe response sent by AP1 in response to the probe request.

[0124] In S1003, AP2 may also send a multi-AP setting request to AP1. At this time, AP2 may also include a coordination bitmap in the multi-AP setting request to be sent. In this case, the multi-AP setting request frame may include a multi-AP element (as an example, Figure 8 frame format shown).

[0125] In S1004, AP1 that has received the multi-AP setting request selects a coordinator AP. Similar to the first embodiment, the coordinator AP may be selected based on internal information corresponding to the received coordination bitmap of AP2 and the coordination bitmap of AP1.

[0126] In S1005, AP1 may also send a multi-AP setup response to AP2. AP1 that receives a multi-AP setup request may also send a multi-AP setup response to AP2 only when the coordinated communication action is ready. In this case, the multi-AP setup response frame may also include a multi-AP element (as an example, Fig. 9 frame format shown).

[0127] The beacon or probe response sent by AP1 may also include a coordination communication action permission flag indicating whether the coordination communication action can be performed. In this case, AP2 can prevent sending invalid multi-AP setting requests by sending multi-AP setting requests only when the coordination communication action permission flag of AP1 is "yes".

[0128] in addition, Fig.10 In the present invention, AP1 may include information indicating the operation status of multiple APs in a beacon or a probe response and send the information.

[0129] Fig. 10A An example of the information format representing the operation status of multiple APs (multi-AP operation element) is shown in FIG.

[0130] The group ID field contains the ID of the multi-AP group (called "multi-AP group", "coordination group", etc.). When AP1 does not perform multi-AP settings with other APs, or when the multi-AP action is completed, the value of the group ID field can also be set to a specific value (0 or 255, etc.) that is not used as an ID, and the situation that the multi-AP action has not started is notified to other APs. In addition, a field indicating whether the multi-AP is in action (not shown) can also be included in the multi-AP operation element.

[0131] The coordinator field contains information indicating whether AP1 is acting as a coordinator AP. It should be noted that when the group ID field and / or other fields indicate that multiple APs are not in action, the coordinator field can also indicate whether AP1 can act as a coordinator AP. In other words, the meaning of the coordinator field can also be changed by whether multiple APs are in action.

[0132] The coordinated AP list field contains a list of IDs (BSSID, BSS color, MAC address, hash value of MAC address, etc.) of APs participating in the multi-AP coordinated group indicated by the group ID field.

[0133] The Connectivity bitmap field may also include information indicating whether each AP shown in the coordinated AP list field can communicate directly with the coordinator AP through a wireless medium. It should be noted that the coordinated APs that cannot communicate directly with the coordinator AP through a wireless medium expect to communicate with the coordinator AP through a wired backhaul (Ethernet connection) or the like to coordinate multiple APs. Therefore, each AP shown in the coordinated AP list field may also include information indicating whether to communicate with the coordinator AP through a wired medium (e.g., a wired backhaul bitmap field) instead of the connectivity bitmap field.

[0134] When AP1 does not act as a coordinator AP (including when it is not set), the coordinated AP list field and the connection bitmap field may be omitted.

[0135] According to the second embodiment, the amount of information transmitted by the periodically transmitted beacon can be reduced compared to the first embodiment.

[0136] <Example 3>

[0137] In Example 1 and Example 2, an embodiment of selecting a coordinator AP using a coordination bitmap in a multi-AP setting S501 is shown, and in Example 3, the following embodiment is shown, namely, in a multi-AP setting S501, the AP notifies the surrounding APs whether it can act as a coordinator AP (hereinafter referred to as "coordinator AP feasibility information"), and selects a coordinator AP.

[0138] Fig.11 2 shows still another example of an action sequence for deciding whether to act as a coordinator AP through negotiation between AP1 and AP2 in multi-AP setting S501.

[0139] In S1101, AP2 may also search for surrounding APs when starting up.

[0140] In S1102, AP2 receives the beacon sent periodically by AP1. AP1 may also include the coordinator AP availability information (capability information) in the beacon to be sent. AP2 may also send a probe request and receive a probe response sent by AP1 in response to the probe request. In this case, the probe response may also include the coordinator AP availability information (capability information).

[0141] In S1103, AP2 that receives the beacon or probe response sent by AP1 can determine whether coordinated communication is possible based on the coordinator AP availability information contained in the beacon or probe response. For example, it can also be determined that coordinated communication is possible in the case that "AP1 can act as a coordinator AP and AP2 cannot act as a coordinator AP" or "AP1 cannot act as a coordinator AP and AP2 can act as a coordinator AP".

[0142] In S1104, AP2 may also send a multi-AP setting request to AP1. For example, AP2 may also send a multi-AP setting request when it is determined that coordinated communication is possible. The multi-AP setting request may be used Fig. 9 The format shown can also be used Fig. 9 The format obtained by removing the coordinator AP ID information may be a format including information indicating whether to act as a coordinator AP instead of the coordinator AP ID information.

[0143] In S1105, AP1 may also send a multi-AP setup response to AP2. The format of the multi-AP setup response may also be set to the same format as the multi-AP setup request. It should be noted that the coordination type contained in the multi-AP setup response may also be set to a coordination mode in which both AP1 and AP2 can act. The multi-AP setup response may also be used to notify that the preparation for coordinated communication as a coordinator AP or a coordinated AP has been completed. It may also be determined that the preparation for coordinated communication as a coordinator AP or a coordinated AP has been completed by sending or receiving a multi-AP setup response.

[0144] <Modification>

[0145] In Embodiment 1, Embodiment 2, and Embodiment 3, embodiments of determining a coordinator AP in multi-AP setting S501 are shown. For example, after determining a coordinator AP in multi-AP setting S501, an AP (hereinafter referred to as "AP for inter-AP communication connection destination") for notifying control information of coordinated communication may be determined. The variation may be combined with any one of Embodiment 1, Embodiment 2, and Embodiment 3.

[0146] For example, in the first embodiment, in the case where AP1 is a coordinator AP or AP1 is a coordinated AP that joins a coordination group, and AP2 is to become a coordinated AP and AP2 can transmit and receive with multiple APs, AP1 can also notify AP2 which AP should be notified most appropriately when AP2 transmits to AP1. For example, AP2 notifies AP1 of the transceiveable AP information (information of multiple APs that AP2 can transmit and receive), and the intermediate APs also perform the same action, so that when AP1 receives the transceiveable AP information, AP1 can also specify the inter-AP communication connection destination AP (the AP to be transmitted when the final destination AP is AP1) when AP2 transmits to AP1 based on at least one of the number of forwardings from AP2 and the reception quality during forwarding. In this case, it is also possible to notify AP2 of the transceiveable AP information notified to AP1 through a multi-AP setting request, and notify AP1 of the inter-AP communication connection destination AP notified to AP2 through a multi-AP setting response.

[0147] When the coordinator AP is other than AP1, AP1 may also forward the multi-AP setting request and the multi-AP setting response notified between the coordinator AP and AP2.

[0148] In Example 1, in the case where AP2 is a coordinator AP or a coordinated AP joining a coordination group, and AP1 is to become a coordinated AP and AP1 is able to transmit and receive with multiple APs, AP1 can also notify AP2 of the transceiver AP information through a multi-AP setting response, and notify AP2 of the inter-AP communication connection destination AP notified to AP1 by defining a multi-AP action frame with a category specified as the coordinating AP.

[0149] It should be explained that the following action example is shown, namely, an action example in which AP information that can be sent and received is notified through a multi-AP setting request or a multi-AP setting response, and an AP that is a destination AP for communication connection between APs is notified through a multi-AP setting response or a multi-AP action frame with the category set to the coordinated AP. However, both the AP information that can be sent and received and the AP that is a destination AP for communication connection between APs can be notified through a multi-AP action frame with the category set to the coordinated AP specified, or can be notified through other frames.

[0150] It can send and receive AP information or AP-to-AP communication. It can also be used to notify the destination AP. Fig.12 The AP notification format is shown.

[0151] Fig.12 In the AP notification format shown, the AP ID field may be set to the ID of the AP that can transmit and receive AP information when AP information can be transmitted and received. The AP ID may be set to the ID of the AP that can be connected to the AP in the inter-AP communication.

[0152] The RSSI (Received Signal Strength Indication) field can also be set to the reception quality of each transceiver AP (e.g., the received power or path loss of the beacon sent by each AP). It can also be used to select the best AP using the coordinator AP. RSSI can be omitted in the response to specify the destination of the communication connection between APs.

[0153] Fig.12 An example of setting the type value to 3 (type = 3) in a multi-AP element is shown in FIG. It can also be set to a format in which, for example, an AP ID and RSSI are added to a multi-AP setting request or a multi-AP setting response. In addition, when notifying the destination AP of the inter-AP communication connection, it can be set to a format that includes only one AP ID.

[0154] <Example 4>

[0155] The AP coordinator AP availability information of the AP in Example 3 may be specified by a higher layer.

[0156] Fig.13 FIG. 4 shows an example of an action sequence in which, in multi-AP setting S501, AP1 and AP2 are started in order and a coordinator AP is selected after AP2 is started.

[0157] In S1301, in AP1, when starting up, the SME (station management entity) as a higher layer sends a MLME-START.request primitive including multi-AP parameters (including coordinator AP availability information) to the MLME (MAC sublayer management entity) as a lower layer.

[0158] In S1302, the MLME of AP1 that receives the MLME-START.request can also confirm whether to receive beacons sent by surrounding APs. In this action example, beacons sent by surrounding APs are not received, so periodic beacon sending (including coordinator AP availability information) can also be started. AP1 can send beacons periodically or irregularly.

[0159] In S1303, while starting to send the beacon, the MLME-START.confirm primitive may also be sent back to the SME of AP1.

[0160] In S1304, in AP2, similarly to AP1, the MLME of AP2 receives the MLME-START.request primitive from the SME at the time of startup.

[0161] In S1305, the MLME of AP2 may also confirm whether to receive beacons sent by surrounding APs. In this action example, the beacon sent by AP1 is received. AP2 may also send a probe request and receive a probe response sent by AP1 in response to the probe request.

[0162] In S1306, the MLME of AP2 determines whether coordinated communication is possible based on the coordinator AP availability information contained in the MLME-START.request primitive and the coordinator AP availability information contained in the beacon or probe response sent by AP1. For example, the MLME of AP2 may also determine that coordinated communication is possible when "AP1 can act as a coordinator AP and AP2 cannot act as a coordinator AP" or "AP1 cannot act as a coordinator AP and AP2 can act as a coordinator AP". AP2 may also send a multi-AP setup request to AP1 when it is determined that coordinated communication is possible.

[0163] In S1307, AP1 may also send a multi-AP setting response to AP2 when receiving the multi-AP setting request.

[0164] In S1308, the MLME of AP2 that receives the multi-AP setup response may also send a MLME-START.confirm primitive back to the SME. It should be noted that the MLME-START.confirm primitive may also include information indicating the start of the coordinated communication action.

[0165] It should be noted that the high layer is set to SME, but it can also be a high layer other than SME, such as the hostapd program, firmware, access point management program, IEEE1905 standard entity, terminal specified in the Wi-Fi standard, etc.

[0166] When AP1 is a coordinated AP under the control of other coordinator APs, it can also be notified of being a coordinated AP under the control of other coordinator APs through beacons or probe responses. In this case, AP1 can also notify AP2 of the ID of the coordinator AP through beacons, probe responses or multi-AP setup responses.

[0167] The coordinator AP may also notify the update of the coordinated AP list when there are other coordinated APs. For example, when AP1 is the coordinator AP, the coordinated AP list may also be notified through a multi-AP setting response frame. When AP2 is the coordinator AP, the coordinated AP list may also be notified through a multi-AP setting request frame. Furthermore, the coordinated AP list may also include the ID of the coordinated AP.

[0168] In Example 4, an example is shown in which the high layer notifies the coordinator AP availability information of the AP in Example 3. In the action examples of Example 1, Example 2 or the modified example, the coordination bitmap can also be notified by the high layer in the same manner. The information notified by the high layer can also be set as the availability information of the coordinator AP and the availability information of the coordinated AP, and the coordination bitmap can be created in the MLME based on this information. In addition, the information notified from the high layer can also include the coordination mode that can be operated, and the coordination mode that can be notified can also be limited to, for example, the mode related to the path for sending data (such as JT or dynamic AP selection, etc.).

[0169] <Example 5>

[0170] Fig.14 An example of a flowchart of an operation example using backhaul communication in multi-AP setting S501 is shown in FIG.

[0171] When backhaul communication is used, a multi-AP structure can be used even when beacons sent by other APs cannot be received. Therefore, it is necessary to determine whether to be a coordinator AP or a coordinated AP even when beacons cannot be received.

[0172] In S1401, the AP type is determined. The AP type (coordinator AP or coordinated AP) can be determined by the SME. For example, when the AP acts as a controller AP of Wi-Fi Easy Mesh, it can be set as a coordinator AP, and when the AP acts as a proxy AP of Wi-Fi Easy Mesh, it can also be set as a coordinated AP.

[0173] When the AP is determined to be a coordinated AP in AP type determination S1401 (when S1402 is No), it is also possible to use the coordinator AP search in S1403 to find a coordinator AP that can be backhauled connected, and start the action as a coordinated AP in S1404 and perform the coordination group joining procedure. In this case, the coordination group joining procedure can also be performed in the coordinator AP through backhaul communication. "Backhaul connection" can be a situation where IP (Internet Protocol) communication can be performed, or it can be a situation where two or more APs on the same network segment (subnet) can perform IP communication. "Coordination group joining procedure" may also include at least one of an ID login procedure, a capability exchange procedure, and an authentication procedure.

[0174] When the AP is determined as a coordinator AP in AP type determination S1401 (when S1402 is Yes), it is also possible to use the coordinated AP to search and find a coordinated AP that can be connected to backhaul in S1405, and start operating as a coordinator AP and generate a coordination group in S1406. In this case, the coordinated AP can also be subjected to the coordination group participation procedure through backhaul communication.

[0175] The determination results of the coordinator AP and coordinated APs obtained in AP type determination S1401 and coordination group information (ID of the coordination group or a list of coordinated APs, etc.) may be included in, for example, MLME-START.request notified from the SME to the MLME.

[0176] The inter-AP communication shown in Embodiment 1, Embodiment 2, Embodiment 3, Variation, and Embodiment 4 may also be performed through backhaul communication. For example, the coordinator AP may receive a coordination group joining request from the coordinated AP through backhaul communication after the coordinator AP starts to act, and the coordinator AP may also determine whether to join and notify the coordinated AP of the result through backhaul communication.

[0177] A backhaul transceiver for performing backhaul communication may be provided, and input data input to the coordination control unit 406 and output data (not shown) output from the coordination control unit 406 may include information transmitted and received by the backhaul communication.

[0178] The coordinator AP may also notify other coordinated APs of the updated list of the coordinator AP through backhaul communication, and the coordinated APs that receive the notification may also notify the MLME of the updated list from the SME. For example, the information may also be included in the newly specified MLME-MULTIAP-RECONFIGURATION.request and notified.

[0179] The above shows an example of an operation of setting up multiple APs using backhaul communication, but multiple APs can also be set up using inter-AP communication at the same time.

[0180] For example, in Fig.14 In the coordinator AP retrieval and coordinated AP retrieval shown, beacons can be received from other APs, or detection requests can be sent to other APs, and the multi-AP setting actions shown in Examples 1 to 4 can be performed in the presence of other APs. Multi-AP setting can also be performed on the AP that sent the received beacon through backhaul communication, and the AP for multi-AP setting through backhaul communication can be limited to the AP that receives the beacon.

[0181] (Implementation Method 2)

[0182] In one aspect of the present invention, the operation of coordinated communication (including interference measurement) is started based on the status of the AP and the STA.

[0183] The configurations of STA and AP may be the same as those shown in Implementation 1.

[0184] <Example 6>

[0185] Fig.15 Shown in Figure 5 Different overall steps. An example is shown when AP2 is newly set up in a state where AP1 is set up and beacons are sent regularly. Fig.15 As shown, each AP performs multi-AP measurement S1503 and multi-AP transmission S1504 after multi-AP setting S1501 and coordination start determination S1502.

[0186] Fig.15 In the embodiment, the actions of multi-AP setting S1501, multi-AP measurement S1503, and multi-AP transmission S1504 may be the same as those in implementation mode 1. The coordination start determination S1502 may also be determined to start coordinated communication when a transmission wait occurs due to interference from other APs or STAs. Multi-AP measurement S1503 and multi-AP transmission S1504 may also be started after the coordination start determination S1502. It should be noted that, regarding the determination of whether a transmission wait has occurred, when the transmission data stored in the transmission buffer increases (the transmission queue length increases), or when the data transmission delay increases, it may be determined that a transmission wait has occurred.

[0187] When determining to start coordinated communication, the coordinated AP may notify the coordinator AP of a coordination start request.

[0188] When determining to start coordinated communication, the STA may notify the associated AP of a coordination start request, and when the associated AP is the coordinated AP, the STA may send a coordination start request to the coordinator AP.

[0189] The coordination start request may also include its own ID, the ID of the detected AP (such as BSS ID or BSS color), and the unordered list / definition list (UL / DL: Unordered List / Definition List) information of the interference group. The objects of multi-AP measurement may also be limited based on the information included in the received coordination start request.

[0190] Thus, by starting coordinated communication when transmission waiting occurs, interference measurement is performed only when coordinated communication is required, thereby reducing STA power consumption. In addition, by transmitting and forwarding interference data only when coordinated communication is required, frequency utilization efficiency can be improved.

[0191] Fig.16 This is a diagram showing an example of the configuration of AP and STA. Fig.16 This shows a configuration example in which STA1-1 and STA1-2 are associated with AP1 as the coordinator AP, and STA2-1 is associated with AP2 as the coordinated AP. Fig.16 The configuration discloses the action in the case where STA2-1 is unable to transmit due to the influence of interference caused by the signal transmitted by AP1 and thus enters the transmission waiting state.

[0192] STA2-1 detects the occurrence of transmission waiting and notifies AP2, the associated AP, of a coordination start request. The coordination start request may also include information on the source of the interference signal (AP1 in this example). AP2, the coordinated AP, forwards STA2-1's coordination start request to AP1, the coordinator AP.

[0193] AP1 that has received the forwarded coordination start request measures interference and instructs AP2 to measure interference.

[0194] AP1 and AP2 can instruct their respective associated STAs (for example, STA1-1 and STA1-2, and STA2-1) to measure interference. It should be noted that the objects of interference measurement can also be limited to a part of STAs. For example, when the coordination method to be acted is C-SR, the STAs for measuring interference can also be limited to STAs with smaller path loss (for example, STA1-1) and STA2-1 that has notified the coordination start request. AP1 can also specify the action of coordinated communication based on the results of the above interference measurement. For example, AP1 can also specify C-SR to simultaneously send from AP1 to STA1-1 and from STA2-1 to AP2.

[0195] It should be noted that the notification of the coordination start request may be limited to the case where there is an influence of interference caused by the signals sent by the coordinating AP (coordinator AP and coordinated AP) and the STA associated with the coordinating AP. In this case, the coordinating AP list (including the BSS ID or BSS color of the coordinating AP) may also be notified to the STA in advance. In this way, it is possible to prevent the notification of the coordination start request due to the influence of interference caused by the signals sent by the AP and STA other than the coordinated communication object.

[0196] In addition, the multi-AP setting S1501 may be performed when a request to start coordinated communication is generated. In this way, the multi-AP setting S1501 targeting the APs that perform coordinated communication can be performed. Furthermore, the construction of unnecessary coordinated groups can be prevented.

[0197] [Format example]

[0198] The coordination start request shown in Example 6 can also be defined as a type of management frame. The coordination start request can also be defined by, for example, a multi-AP action frame in which the category is set to the coordination start request in the action frame. For example, in the multi-AP element, the type value can also be specified by 4 (type=4). Fig.17 An example of a coordination start request specified in a multi-AP element is shown in FIG.

[0199] Fig.17 In the AP / STA ID field, the AP or STA affected by the interference may be set to AID (Association ID) in the case of STA or to an unused AID (eg, 4094) in the case of AP.

[0200] The BSS ID field may also be set to the BSS ID or BSS color of the interference source.

[0201] The DL / UL field is the DL / UL information of the interference group, and can be set to "0: DL, 1: UL, 2: DL and UL" for example. It should be noted that when DL / UL is UL or DL ​​and UL, Fig.17 The transmission source STA ID is added to the format shown.

[0202] (Implementation 3)

[0203] In one aspect of the present invention, when APs are located in a position where direct transmission and reception between APs is not possible, STAs forward information (coordination control information, etc.) for communication between APs, thereby enabling transmission and reception between APs. The configurations of STAs and APs may be the same as those shown in Embodiment 1.

[0204] <Example 7>

[0205] Fig.18 Another configuration example of AP and STA is shown in FIG. Fig.18 This indicates that, in a state where AP1 and STA1 associated with AP1 are configured, AP2 is newly configured at a location where it cannot directly transmit or receive data with AP1 but can directly transmit or receive data with STA1. Fig.18 In the illustrated configuration, an example is described in which STA1 transfers information transmitted between AP1 and AP2 to perform the multi-AP coordination operation shown in Embodiments 1 and 2.

[0206] When STA1 receives the beacon of the newly started AP2, it may also notify AP1 that AP2 has been configured (hereinafter referred to as "coordination candidate AP notification"). It should be noted that the presence or absence of notification may also be determined by the capability information related to multiple APs contained in the beacon of AP2 (for example, the coordination action permission flag). In addition, notification may be made when a transmission wait occurs in STA1, such as when there is an influence of interference caused by AP2 or a STA associated with AP2, or when AP2 is not included in the coordination AP list.

[0207] Alternatively, AP1 that has received the coordination candidate AP notification sends a coordination start request (for example, the multi-AP setup request shown in Implementation Example 1) to AP2 to STA1, and STA1 forwards the received coordination start request to AP2. It should be noted that since STA1 is communicating with AP2, STA1 can also be associated with AP2. When STA1 is associated with AP2, information indicating the purpose of coordinating control data transfer between APs (for example, a flag indicating transfer or the ID of AP1, etc.) may be included, and a coordination start request may be included in the signal sent when associating.

[0208] Hereinafter, the communication between AP1 and AP2 in the cooperative communication shown in Embodiment 1 and Embodiment 2 may be communication via STA1.

[0209] In this way, even between APs that cannot directly transmit and receive, coordinated actions can be performed by communicating through STAs.

[0210] (Implementation 4)

[0211] When the coordination method applied to the multi-AP coordinated communication shown in Implementation Example 1, Implementation Example 2, and Implementation Example 3 is dynamic AP selection, it can also be set to the following actions.

[0212] Fig.19 Still another configuration example of AP and STA is shown in FIG. Fig.19 2 shows an operation example in which AP1 and AP2 that can be operated by dynamic AP selection as a coordination method are added to the same coordination group, and STA1 moves toward AP2 after associating with AP1.

[0213] For AP1 and AP2, through the multi-AP setting S501 shown in Implementation Mode 1, Implementation Mode 2, and Implementation Mode 3, dynamic AP selection is selected as the coordination method.

[0214] STA1 may also associate with AP2 as a candidate for switching to dynamic AP selection. For example, when AP2 is included in the coordinated AP list and / or the received power of the signal (e.g., beacon) sent by AP2 exceeds a certain threshold, STA1 may also associate. In addition, when AP1 notifies STA1 of the list of APs capable of dynamic AP selection in advance and the list of APs received by STA1 includes AP2, STA1 may also associate.

[0215] In this way, by determining the AP to be the cooperative communication target in the multi-AP setting, dynamic AP selection can be performed. In addition, by associating the STA with a high possibility of dynamic AP selection with the switching candidate destination AP, unnecessary association can be prevented.

[0216] It should be noted that the association request notified by STA1 to AP2 may include information indicating the status of the candidate mobile destination selected by the dynamic AP, and may also include the ID of the AP (e.g., AP1) to which STA1 is currently associated and the ID of STA1 (e.g., the AID assigned by AP1). Thus, the candidate switching destination AP can determine the switching source AP.

[0217] In addition, the association response notified by AP2 to STA1 may also include information on whether dynamic AP selection is possible and / or rank information. The rank information may be set to rank 1, for example, when the sent packet information can be shared between AP1 and AP2, and to rank 2 when it cannot be shared. STA1 may also change the parameters of dynamic AP selection according to the rank (for example, the threshold value of the difference between the received power of AP1 and the received power of AP2 for determining the start of the switching action, or the number of forward and backward protections for the switching). For example, rank 1 may also be a value that makes it easy to implement the switching. Thus, switching may also be performed according to the functions of the switching destination AP and the switching source AP.

[0218] Alternatively, STA1 may notify AP1 (switching source AP) and AP2 (switching destination AP) of a request to switch the transmission and reception destination.

[0219] In addition, AP1 may issue a switching request. In this case, the switching request may be made based on the result of the multi-AP measurement S1503 (measurement of interference from AP2 to STA1).

[0220] Alternatively, a BSS (virtual BSS) including AP1 and AP2 may be provided. In this case, STA1 may associate with the virtual BSS instead of associating with the AP2.

[0221] The above embodiment is described with reference to the accompanying drawings, but the present disclosure is not limited to this example. It should be clear that as long as one is skilled in the art, various variations or modifications can be thought of within the scope of the claims. It should be understood that these variations or modifications also belong to the technical scope of the present disclosure. In addition, the various constituent elements in the embodiment can be arbitrarily combined within the scope of the present disclosure.

[0222] In the above-mentioned embodiments, the expression "part" used in each component can also be replaced by " Circuitry", " Components (assembly)", " Device, Unit" or " "module" and other expressions.

[0223] The present disclosure can be implemented by software, hardware or software in cooperation with hardware. Each functional block used in the description of the above-mentioned embodiments is partially or entirely implemented as an LSI (Large Scale Integration) as an integrated circuit, and each process described in the above-mentioned embodiments may also be partially or entirely controlled by an LSI or a combination of LSIs. LSI may be composed of individual chips, or may be composed of one chip in a manner that includes part or all of the functional blocks. LSI may also include input and output of data. LSI may also be referred to as "IC (Integrated Circuit)", "System LSI", "Super LSI", "Ultra LSI" depending on the degree of integration.

[0224] The method of integrated circuitization is not limited to LSI, and can also be implemented by a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (Field Programmable Gate Array) that can be programmed after LSI manufacturing, or a reconfigurable processor (Reconfigurable Processor) that can reconfigure the connection or setting of the circuit block inside the LSI can also be used. The present disclosure can also be implemented as digital processing or analog processing.

[0225] Furthermore, if integrated circuit technology that replaces LSI emerges as semiconductor technology advances or other technologies are derived, it is of course possible to use this technology to achieve integration of functional blocks. There is also the possibility of applying biotechnology, etc.

[0226] The present disclosure can be implemented in all kinds of devices, equipment, and systems (collectively referred to as "communication devices") with communication functions. The communication device may also include a wireless transceiver and a processing / control circuit. The wireless transceiver may also include a receiving unit and a transmitting unit, or perform the functions of these parts. 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 a device similar to these. Non-limiting examples of communication devices include: phones (mobile phones, smart phones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebook computers, etc.), cameras (digital cameras, digital video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smart watches, tracking devices, etc.), game consoles, e-book readers, telehealth / telemedicine (telehealth / medical prescription) equipment, vehicles or transportation vehicles with communication functions (cars, airplanes, ships, etc.), and combinations of the above-mentioned various devices.

[0227] Communication devices are not limited to portable or mobile devices, but also include all kinds of devices, equipment, and systems that cannot be carried or fixed. For example, they 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.

[0228] The communication includes data communication performed by a cellular system, a wireless LAN (Local Area Network) system, a communication satellite system, etc., and also includes data communication performed by a combination of these systems.

[0229] In addition, the communication device also includes devices such as controllers or sensors connected or linked to the communication device that performs the communication function described in the present invention. For example, it includes a controller or sensor that generates a control signal or data signal used by the communication device that performs the communication function of the communication device.

[0230] In addition, the communication device includes infrastructure equipment that communicates with the above-mentioned non-limiting various devices or controls the above-mentioned various devices, such as base stations, access points, and all other devices, equipment, and systems.

[0231] In recent years, in IoT (Internet of Things) technology, CPS (Cyber ​​Physical Systems) has attracted attention as a new concept that creates new added value through information cooperation between physical space and cyber space. The above-mentioned embodiment can also adopt this CPS concept.

[0232] That is, as a basic configuration of CPS, for example, an edge server configured in a physical space can be connected to a cloud server configured in a network space via a network, and the processors installed on both servers can perform distributed processing. Here, each processed data generated in the edge server or the cloud server is preferably generated on a standardized platform. By using such a standardized platform, the efficiency of building a system including various sensor groups or IoT application software can be improved.

[0233] (1) An access point according to an embodiment of the present disclosure includes: a transceiver for receiving information related to coordinated communication; and a control circuit for determining whether to operate as an access point for controlling coordinated communication.

[0234] (2) In an access point according to an embodiment of the present disclosure, in the access point of (1), the information related to coordinated communication received by the transceiver is information received from another access point, the transceiver sends the information related to coordinated communication to the other access point, and the control circuit determines whether to act as an access point for controlling coordinated communication through negotiation with the other access point.

[0235] (3) In an access point according to an embodiment of the present disclosure, in the access point of (2), the information related to coordinated communication received from the other access point or the information related to coordinated communication sent to the other access point is a coordination bitmap.

[0236] (4) In an access point according to an embodiment of the present disclosure, in the access point of (1), the transceiver sends a message to other access points as to whether the access point can operate as an access point for controlling coordinated communication.

[0237] (5) In an access point according to an embodiment of the present disclosure, in the access point of (1), the control circuit is designated by a higher layer whether to operate as an access point for controlling coordinated communication.

[0238] (6) In an access point according to an embodiment of the present disclosure, in the access point of (1), the information related to coordinated communication received by the transceiver is information including a coordination method received from another access point, and the control circuit determines the coordination method of the coordinated communication based on an operable coordination method.

[0239] (7) In an access point according to an embodiment of the present disclosure, in the access point of (1), the control circuit determines to start coordinated communication based on a result of interference measurement performed by another access point or terminal.

[0240] (8) In an access point according to an embodiment of the present disclosure, in the access point of (1), the transceiver receives information related to coordinated communication sent by another access point from the terminal.

[0241] (9) In an access point of one embodiment of the present disclosure, in the access point of (1), a switching source access point for dynamic AP selection is determined by receiving the following association from a terminal, wherein the association includes information indicating that the access point is a candidate for a mobile destination for dynamic AP selection or includes an ID of an access point to which the terminal is currently associated and an ID of the terminal.

[0242] (10) In a coordinated communication control method according to an embodiment of the present disclosure, an access point receives information related to coordinated communication and determines whether to act as an access point for controlling coordinated communication.

[0243] The disclosed contents of the specification, drawings, and abstract contained in the Japanese patent application No. 2022-162392 filed on October 7, 2022 are incorporated herein by reference in their entirety.

[0244] Industrial Applicability

[0245] The present disclosure is useful for coordinating communications.

[0246] Description of Reference Numerals

[0247] 301, 401: Sending packet generation unit

[0248] 302, 402: Control signal generating unit

[0249] 303, 403: Wireless transceiver unit

[0250] 304, 404: Received packet decoding unit

[0251] 305, 405: Reception quality measurement unit

[0252] 306, 407: Control circuit

[0253] 406: Coordination and Control Department

Claims

1. An access point, characterized in that: include: The transceiver department receives and coordinates communications related information; as well as The control circuit determines whether to act as an access point for control coordination communication.

2. The access point according to claim 1, wherein: The information related to coordinated communication received by the transceiver is information received from other access points, The transceiver sends information related to coordinated communication to the other access points. The control circuit determines whether to act as an access point for controlling coordinated communication through negotiation with the other access points.

3. The access point according to claim 2, wherein: The information related to coordinated communication received from the other access point or the information related to coordinated communication sent to the other access point is a coordination bitmap.

4. The access point according to claim 1, wherein: The transceiver transmits information indicating whether the access point can operate as an access point for controlling coordinated communication to another access point.

5. The access point according to claim 1, wherein: The control circuit is designated by a higher layer whether to act as an access point for controlling coordinated communication.

6. The access point of claim 1, wherein: The information related to coordinated communication received by the transceiver unit is information including a coordination method and received from another access point. The control circuit determines a coordination method for cooperative communication based on operable coordination methods.

7. The access point of claim 1, wherein: The control circuit determines to start coordinated communication based on a result of interference measurement performed by another access point or terminal.

8. The access point of claim 1, wherein: The transceiver receives information related to coordinated communication sent by other access points from the terminal.

9. The access point of claim 1, wherein: The control circuit determines the switching source access point of the dynamic AP selection by receiving the following association from the terminal, the association including information indicating that the access point is a moving destination candidate of the dynamic AP selection or including the ID of the access point currently associated with the terminal and the ID of the terminal.

10. A method for controlling coordinated communication, characterized in that: The access point receives information related to coordinated communications and decides whether to act as an access point controlling the coordinated communications.

Images