access point
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-11
- Publication Date
- 2026-08-11
AI Technical Summary
[0015] According to the present invention, an access point can be provided that can determine whether an access point uses the Co-SR function and can control the activation and deactivation of the Co-SR function.
Smart Images

Figure CN122556128A_ABST
Abstract
Description
Technical Field
[0001] The implementation method relates to an access point. Background Technology
[0002] Wireless LANs (local area networks) are known as communication systems that wirelessly connect access points (APs) to terminal devices. Terminal devices can access the network via an access point within a communicable area through a wireless LAN. In the UHR-SG (ultra-high reliability study group), which studies next-generation wireless LAN systems standardized by IEEE 802.11, the multi-AP functionality involving coordinated operation of multiple access points was investigated.
[0003] As one method of multi-AP functionality, multiple second access points connected to the first access point coordinate to perform data communication between the first access point and the terminal device. As a coordination action among the multiple second access points, for example, consider distributing the data traffic exchanged between the first access point and non-AP_MLD (non-access point multi-link device) to each of the second access points. non-AP_MLD corresponds to a function block in the terminal device that manages wireless connections using multi-AP functionality.
[0004] Furthermore, in the 802.11 standard, to fully utilize the multi-AP function for spatial reuse (SR), the Co-SR (Coordinated-Spatial Reuse) function, which coordinates SR at the second access point, is under investigation. Consequently, as applications of the Co-SR function, Co-Beamforming and Co-OFDMA (Coordinated-Orthogonal Frequency Division Multiple Access) are being researched.
[0005] Existing technical documents
[0006] Non-patent literature
[0007] Non-patent literature 1: IEEE 802.11-23 / 0058r0, “Spatial Reuse in Coordinated M-AP for UHR”, January 2023
[0008] Non-patent document 2: IEEE Std 802.11TM-2020, December 2020 Summary of the Invention
[0009] The problem the invention aims to solve
[0010] However, the use cases for Co-Beamforming, Co-OFDMA, and other extensions of Co-SR functionality are limited depending on the degree of overlap in the Overlapping Basic Service Set (OBSS). In other words, the judgment of which areas benefit more from using Co-SR functionality and which benefit less from not using it depends on the environment. For example, when the OBSS overlap is high, the reduced power control effect caused by using Co-SR functionality makes it preferable not to use it.
[0011] Therefore, the purpose of this invention is to provide an access point that can determine whether an access point uses the Co-SR function and control the opening and closing of the Co-SR function.
[0012] means for solving problems
[0013] The access point in the implementation includes a communication circuit and a processor. The communication circuit is configured to communicate with multiple access points. The processor is configured to determine whether each of the multiple access points uses spatial multiplexing functionality based on information from each of the multiple access points, and to apply spatial multiplexing functionality settings to the multiple access points based on the determination results.
[0014] The effects of the invention
[0015] According to the present invention, an access point can be provided that can determine whether an access point uses the Co-SR function and can control the activation and deactivation of the Co-SR function. Attached Figure Description
[0016] Figure 1 This is a block diagram illustrating an example of the overall structure of the communication system according to the first embodiment.
[0017] Figure 2 This is a block diagram illustrating an example of the hardware structure of the shared access point (Sharing AP) in the communication system of the first embodiment.
[0018] Figure 3 This is a block diagram illustrating an example of the hardware structure of a shared access point (Shared AP) in the communication system of the first embodiment.
[0019] Figure 4This is a block diagram illustrating an example of the hardware structure of the terminal device included in the communication system of the first embodiment.
[0020] Figure 5 This is a block diagram illustrating an example of the functional structure of the shared access point in the communication system of the first embodiment.
[0021] Figure 6 This is a block diagram illustrating an example of the functional structure of the shared access point in the communication system of the first embodiment.
[0022] Figure 7 This is a block diagram illustrating an example of the functional structure of a terminal device included in the communication system of the first embodiment.
[0023] Figure 8 This is a block diagram illustrating an example of the functional structure of an auxiliary STA included in a terminal device of the communication system of the first embodiment.
[0024] Figure 9 This is a flowchart illustrating an example of a control method for enabling and disabling the Co-SR function of a shared access point in the communication system of the first embodiment.
[0025] Figure 10 This is a schematic diagram illustrating an example of an information acquisition method used in determining whether the Co-SR function is enabled or disabled in the communication system of the first embodiment.
[0026] Figure 11 This is a schematic diagram illustrating the first usage conditions of the Co-SR function in the communication system of the first embodiment.
[0027] Figure 12 This is a schematic diagram illustrating the second usage conditions of the Co-SR function in the communication system of the first embodiment.
[0028] Figure 13 This is a schematic diagram illustrating the third usage condition of the Co-SR function in the communication system of the first embodiment.
[0029] Figure 14 This is a schematic diagram illustrating the fourth usage condition of the Co-SR function in the communication system of the first embodiment.
[0030] Figure 15 This is a flowchart illustrating an example of a control method for enabling and disabling the Co-SR function of a shared access point in the communication system of the second embodiment.
[0031] Figure 16 This is a schematic diagram illustrating an example of an information acquisition method used in determining whether the Co-SR function is enabled or disabled in the communication system of the second embodiment.
[0032] Figure 17 This is a schematic diagram illustrating the usage conditions of the Co-SR function in the communication system of the second embodiment.
[0033] Figure 18 This is a block diagram illustrating an example of the structure of a communication system modified from the first embodiment. Detailed Implementation
[0034] Hereinafter, various embodiments will be described with reference to the accompanying drawings. Each embodiment illustrates an apparatus and method for embodying the technical concept of the invention. The drawings are schematic or conceptual. Constituent elements having substantially the same function and structure are given the same reference numerals. Numbers following the characters constituting the reference numerals are referred to by reference numerals containing the same characters and are used to distinguish elements having the same structure from one another. Similarly, hyphens followed by numbers constituting the reference numerals are referred to by reference numerals containing the same numbers and are used to distinguish elements having the same structure from one another.
[0035] Hereinafter, "access point" will be appropriately abbreviated as "AP". In this manual, the access point of the wireless LAN may also be referred to as a "base station". In this manual, the first access point in the multi-AP function is referred to as the "sharing access point", and the second access point in the multi-AP function is referred to as the "shared access point". In this manual, using the Co-SR function corresponds to enabling the Co-SR function (on state). Not using the Co-SR function corresponds to disabling the Co-SR function (off state).
[0036] <1> Implementation Method 1
[0037] In the communication system 1 of the first embodiment, the shared AP is configured to control the activation and deactivation of the Co-SR function based on the information control of the managed shared AP. The details of the communication system 1 of the first embodiment will be described below.
[0038] <1-1> Structure
[0039] First, the structure of the communication system 1 according to the first embodiment will be described. Hereinafter, the communication system 1 will be described with the premise of establishing a multi-AP connection using the multi-AP function.
[0040] <1-1-1> Overall Structure of Communication System 1
[0041] Figure 1 This is a block diagram illustrating an example of the overall structure of the communication system 1 according to the first embodiment. For example... Figure 1As shown, the communication system 1 includes a shared AP10, multiple shared AP20s, and a terminal device 30.
[0042] Shared AP10 is a wireless LAN access point. Shared AP10 connects to network NW. Shared AP10 is configured to communicate wirelessly with a server (not shown) on network NW, and to communicate wirelessly with multiple shared APs 20. Shared AP10 establishes multi-AP connections with the non-AP_MLD of terminal device 30.
[0043] A shared AP20 is a wireless LAN access point. The shared AP20 is configured to communicate wirelessly with both the shared AP10 and the terminal device 30. Multiple shared AP20s are located in separate positions and have distinct communication areas. The communication areas of each shared AP20 may overlap with those of other shared AP20s. Figure 1 Two shared APs, 20-1 and 20-2, are shown connected to the shared AP10.
[0044] Terminal device 30 is a wireless terminal such as a smartphone or PC (Personal Computer). Terminal device 30 has multiple affiliated stations (STAs) (hereinafter also referred to as "A-STAs") and a non-AP_MLD. The multiple affiliated STAs include A-STA1, which is wirelessly connected to the shared AP20-1, and A-STA2, which is wirelessly connected to the shared AP20-2. The wireless connection between the shared AP20 and the affiliated STAs is equivalent to the connection between a pair of access points and STAs in the past. Each A-STA can switch its connection destination to another shared AP20 as terminal device 30 moves. The non-AP_MLD is an MLD (multi-link device) that manages the link status and wireless communication of the multiple A-STAs. The non-AP_MLD can establish multi-AP connections with the shared AP10 via multiple affiliated STAs and multiple shared AP20s, and exchange data, etc.
[0045] In communication system 1, when establishing a multi-AP connection, information about multiple shared APs 20 under the jurisdiction of shared AP10 and multiple auxiliary STAs under the jurisdiction of non-AP_MLD are exchanged between shared AP10 and non-AP_MLD. Thus, communication system 1 can uniformly perform a comprehensive connection between shared AP10 and non-AP_MLD, targeting multiple shared APs 20 and multiple auxiliary STAs.
[0046] The wireless communication used in communication system 1 follows, for example, the IEEE 802.11 standard. The IEEE 802.11 standard features wireless communication capabilities based on the OSI (Open Systems Interconnection) reference model. In the OSI reference model, wireless communication capabilities are divided into seven layers (Layer 1: Physical Layer, Layer 2: Data Link Layer, Layer 3: Network Layer, Layer 4: Transport Layer, Layer 5: Session Layer, Layer 6: Presentation Layer, Layer 7: Application Layer). The Data Link Layer includes the LLC (Logical Link Control) sublayer and the MAC (Media Access Control) sublayer. For example, the 2.4 GHz band, 5 GHz band, 6 GHz band, 45 GHz band, and 60 GHz band can be utilized in the wireless communication of communication system 1. Multiple channels can be allocated to each band. A-STA1 and A-STA2 can be assigned different channels or the same channel. Furthermore, A-STA1 and A-STA2 can use either the same frequency band or different frequency bands.
[0047] <1-1-2> Hardware Structure of Communication System 1
[0048] The hardware structure of the communication system 1 according to the first embodiment will be described below.
[0049] (1: Hardware structure of shared AP10)
[0050] Figure 2 This is a block diagram illustrating an example of the hardware structure of the shared AP10 included in the communication system 1 of the first embodiment. For example... Figure 2 As shown, the shared AP10 includes, for example, a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a wireless communication module 14, and a wired communication module 15.
[0051] CPU 11 is an integrated circuit capable of executing various programs and controlling the overall operation of the shared AP 10. ROM 12 is, for example, a non-volatile semiconductor memory that stores programs and control data used to control the shared AP 10. RAM 13 is, for example, a volatile semiconductor memory and is used as the operating area of CPU 11. Wireless communication module 14 is configured to transmit and receive wireless signals via an antenna. Wireless communication module 14 is used for transmitting and receiving data, etc., with each shared AP 20. Wired communication module 15 is a circuit for transmitting and receiving data, etc., via wired signals. Wired communication module 15 is configured to connect to network NW.
[0052] It should be noted that the shared AP10 can also have other hardware structures. For example, when the shared AP10 is wirelessly connected to the network NW, the wired communication module 15 can be omitted from the shared AP10. When the shared AP10 is wiredly connected to the network NW, the wireless communication module 14 can be omitted from the shared AP10. The antenna can be either built into the shared AP10 or externally connected to the shared AP10.
[0053] (2: Shared AP20 hardware structure)
[0054] Figure 3 This is a block diagram illustrating an example of the hardware structure of the shared AP20 included in the communication system 1 of the first embodiment. For example... Figure 3 As shown, Figure 2 As shown, the common AP20 includes, for example, a CPU21, ROM22, RAM23, and a wireless communication module24.
[0055] CPU 21 is an integrated circuit capable of executing various programs and controlling the overall operation of the shared AP 20. ROM 22 is, for example, a non-volatile semiconductor memory that stores programs and control data used to control the shared AP 20. RAM 23 is, for example, a volatile semiconductor memory that is used as the operating area of CPU 21. The wireless communication module 24 is configured to transmit and receive wireless signals via an antenna. The wireless communication module 24 is used for transmitting and receiving data, etc., with the shared AP 10 and with the terminal device 30.
[0056] It should be noted that the shared AP20 can also have other hardware structures. For example, the antenna can be built into the shared AP20 or externally connected to it. The shared AP20 can also be wired to the shared AP10. In this case, the shared AP20 also has a wired communication module configured to communicate with the shared AP10. It should be noted that the communication system 1 can also have both a shared AP20 wired to the shared AP10 and a shared AP20 wirelessly connected to the shared AP10.
[0057] (3: Hardware structure of terminal device 30)
[0058] Figure 4 This is a block diagram illustrating an example of the hardware structure of the terminal device 30 included in the communication system 1 of the first embodiment. For example... Figure 4 As shown, the terminal device 30 includes, for example, a CPU 31, a ROM 32, a RAM 33, a wireless communication module 34, a display 35, and a storage device 36.
[0059] CPU 31 is an integrated circuit capable of executing various programs and controlling the overall operation of terminal device 30. ROM 32 is, for example, a non-volatile semiconductor memory that stores programs, control data, etc., used to control terminal device 30. RAM 33 is, for example, a volatile semiconductor memory used as the operating area of CPU 31. Wireless communication module 34 is configured to transmit and receive wireless signals via an antenna. Wireless communication module 34 is used for transmitting and receiving data, etc., with the shared AP 20. Display 35 is, for example, an LCD (Liquid Crystal Display) or EL (Electro-Luminescence) display. Display 35 displays, for example, a GUI (Graphical User Interface) corresponding to application software. Storage 36 is a non-volatile storage device, for example, storing system software, etc., of terminal device 30.
[0060] It should be noted that the terminal device 30 can also be other hardware structures. For example, if the terminal device 30 is an IoT (Internet of Things) terminal, the display 35 can be omitted from the terminal device 30. The display 35 can also function as an input interface for the terminal device 30. The antenna can be built into the terminal device 30 or externally connected to the terminal device 30.
[0061] <1-1-3> Functional Structure of Communication System 1
[0062] The functional structure of the communication system 1 in the first embodiment will be described below.
[0063] (1: Functional structure of shared AP10)
[0064] Figure 5 This is a block diagram illustrating an example of the functional structure of the shared AP10 in the communication system 1 of the first embodiment. For example... Figure 5 As shown, the shared AP10 functions as a computer, for example, equipped with an LLC processing unit 110, a data processing unit 120, a management unit 130, a frame processing unit 140, and a transceiver unit 150. The LLC processing unit 110 is a functional block that performs processing corresponding to the LLC sublayer of Layer 2 and Layers 3 to 7. The data processing unit 120, management unit 130, and frame processing unit 140 are functional blocks that perform processing corresponding to the MAC sublayer of Layer 2. The transceiver unit 150 is a functional block that performs processing corresponding to Layer 1.
[0065] LLC processing unit 110, for example, appends DSAP (Destination Service Access Point) headers and SSAP (Destination Service Access Point) headers to data received from network NW to generate LLC packets. Then, LLC processing unit 110 inputs the generated LLC packets to data processing unit 120. Additionally, LLC processing unit 110 extracts data from the LLC packets input from data processing unit 120. Then, LLC processing unit 110 sends the extracted data to network NW.
[0066] The data processing unit 120 appends a MAC header to the LLC packets input from the LLC processing unit 110 to generate a MAC frame. Then, the data processing unit 120 inputs the generated MAC frame to the frame processing unit 140. Additionally, the data processing unit 120 extracts LLC packets from the MAC frames input from the frame processing unit 140. Then, the data processing unit 120 inputs the extracted LLC packets to the LLC processing unit 110. It should be noted that the MAC frame containing data is also called a "data frame".
[0067] The management unit 130 performs tasks such as establishing wireless connections (wireless links), mapping data types to links, setting BlockAck, and controlling Co-SR (Coordinated-Spatial Reuse) functions between itself and the non-AP_MLD of the terminal device 30. For example, the management unit 130 performs multi-AP association processing based on multi-AP association requests from the terminal device 30. For example, when the terminal device 30 uses two A-STA1 and A-STA2, through multi-AP association processing, A-STA1 establishes a wireless link with the shared AP 20-1, and A-STA2 establishes a wireless link with the shared AP 20-2.
[0068] Additionally, the management unit 130 includes multi-AP management information 131, link management information 132, and a determination unit 133. The multi-AP management information 131 includes information related to the access points (i.e., shared AP 10 and shared APs 20-1 and 20-2) and terminal devices 30 used for multi-AP connections. For example, the multi-AP management information 131 is set on each terminal device 30 that establishes a multi-AP connection. The link management information 132 includes information related to the status of the links established in the multi-AP connection. Based on information from the managed shared AP 20, the determination unit 133 determines whether to set the Co-SR function of the managed shared AP 20 to an enabled (enabled) or disabled (disabled) state. Then, the shared AP 10 notifies each shared AP 20 of the determination result. The information of the managed shared AP 20 can be stored in the management unit 130 or retrieved from the managed shared AP 20. Furthermore, the determination unit 133 detects notifications sent from the managed shared AP 20 regarding whether the Co-SR function is used.
[0069] When a MAC frame is input from the data processing unit 120 or the management unit 130, the frame processing unit 140 outputs the input MAC frame to the transceiver unit 150. Alternatively, when a MAC frame is input from the transceiver unit 150, the frame processing unit 140 outputs the input frame to the data processing unit 120 or the management unit 130 according to the frame type. For example, when a data frame is input from the transceiver unit 150, the frame processing unit 140 outputs the input frame to the data processing unit 120. When a management frame or control frame is input from the transceiver unit 150, the frame processing unit 140 outputs the input frame to the management unit 130. The management frame or control frame may contain, for example, management information. This management information may include notification information for any device in the shared AP 20 and terminal device 30, control information related to controlling the operation of any device in the shared AP 20 and terminal device 30, etc.
[0070] The transceiver unit 150 transmits and receives data and management information with each of the multiple shared APs 20 belonging to the shared AP 10. For example, each of the multiple shared APs 20 belonging to the shared AP 10 has one wireless signal processing unit within the transceiver unit 150. Each wireless signal processing unit of the transceiver unit 150 is configured to transmit and receive wireless signals using different frequency bands or channels.
[0071] Each wireless signal processing unit of transceiver unit 150 generates a wireless frame by adding a preamble or the like to the MAC frame input from frame processing unit 140, and converts the generated wireless frame into a wireless signal. Then, each wireless signal processing unit transmits (transmits) the converted wireless signal to the wirelessly connected shared AP 20 via an antenna. Additionally, each wireless signal processing unit of transceiver unit 150 converts a wireless signal received from any of the shared AP 20 via an antenna into a wireless frame. Then, each wireless signal processing unit extracts a MAC frame from the converted wireless frame and outputs the extracted MAC frame to frame processing unit 140. It should be noted that when transceiver unit 150 simultaneously notifies multiple shared AP 20s, it can also use multicast or broadcast. Multicast and broadcast are used, for example, for transmitting beacons.
[0072] It should be noted that the multi-AP management information 131 can include information related to frequency band, channel, application parameters, and access category. Frequency band information, for example, indicates the frequency band used by the A-STA in the radio link. Channel information, for example, indicates the channel used by the A-STA in the radio link. Application parameter information includes, for example, CWmin, CWmax, AIFS (arbitration interframe space), and TXOP (transmission opportunity) Limit. CWmin and CWmax represent the minimum and maximum values of the contention window, respectively. The contention window is a parameter used to calculate the backoff time (transmission waiting time) to avoid collisions. AIFS is a fixed transmission waiting time set for each access category of the service. TXOPLimit represents the upper limit of the channel occupancy period (TXOP). Access category information is represented, for example, by "VO (Voice)," "VI (Video)," "BE (Best Effort)," "BK (Background)," and "LL (Low Latency)." In addition, the multi-AP management information 131 can also store whether the Co-SR function of the shared AP 20 under its jurisdiction is effective or ineffective.
[0073] Link management information 132 can include information indicating whether the wireless link is enabled or disabled. Multi-AP management information 131 and link management information 132 can also be integrated. Frame processing unit 140 can input data, such as data sent to shared AP 20-1, to the wireless signal processing unit associated with shared AP 20-1 based on multi-AP management information 131, and output data, such as data sent to shared AP 20-2, to the wireless signal processing unit associated with shared AP 20-2. Frame processing unit 140 can also determine the destination of MAC frames input from data processing unit 120 based on the TID (traffic identifier) corresponding to the access class. This process of establishing a correspondence between TID and link is also called "TID-link mapping." Wireless signal processing units for transmitting and receiving data, etc., can be set up in transceiver unit 150, and wireless signal processing units for transmitting management information can also be set up.
[0074] (2: Shared functional structure of AP20)
[0075] Figure 6 This is a block diagram illustrating an example of the functional structure of the shared AP20 provided in the communication system 1 of the first embodiment. For example... Figure 6 As shown, the shared AP20 functions, for example, as a computer comprising transceiver units 210-1 and 210-2, a management unit 220, frame processing units 230-1 and 230-2, and a data processing unit 240. Transceiver units 210-1 and 210-2 are functional blocks that perform processing corresponding to Layer 1. Management unit 220 and frame processing units 230-1 and 230-2 are functional blocks that perform processing corresponding to the MAC sublayer of Layer 2.
[0076] Transceiver unit 210-1 transmits and receives data and management information with the shared AP 10 via wireless communication. Transceiver unit 210-2 transmits and receives data and management information with the terminal device 30 via wireless communication. Transceiver units 210-1 and 210-2 are respectively associated with frame processing units 230-1 and 230-2. When notifying the terminal device 30, transceiver unit 210-2 can also use multicast or broadcast. For example, multicast or broadcast can be used to send beacons containing information about multiple AP connections. Transceiver units 210-1 and 210-2 each have a wireless signal processing unit. It should be noted that in the shared AP 20, the wireless signal processing units of transceiver unit 210-1 and transceiver unit 210-2 are preferably configured to use different frequency bands or channels.
[0077] The wireless signal processing unit of transceiver unit 210-1 adds preambles and other parameters to the MAC frames (data frames, management frames, etc.) input from frame processing unit 230-1 to generate wireless frames. Then, the wireless signal processing unit of transceiver unit 210-1 converts the generated wireless frames into wireless signals and transmits (transmits) the converted wireless signals to shared AP10 via the antenna. Additionally, the wireless signal processing unit of transceiver unit 210-1 converts wireless signals received from shared AP10 via the antenna into wireless frames. Then, the wireless signal processing unit of transceiver unit 210-1 extracts MAC frames from the converted wireless frames and outputs the extracted MAC frames to frame processing unit 230-1.
[0078] The wireless signal processing unit of transceiver unit 210-2 adds preambles and other parameters to the MAC frames (data frames, management frames, etc.) input from frame processing unit 230-2 to generate wireless frames. Then, the wireless signal processing unit of transceiver unit 210-2 converts the generated wireless frames into wireless signals and transmits (transmits) the converted wireless signals to terminal device 30 via antenna. Additionally, the wireless signal processing unit of transceiver unit 210-2 converts wireless signals received from terminal device 30 via antenna into wireless frames. The wireless signal processing unit of transceiver unit 210-2 extracts MAC frames from the converted wireless frames and outputs the extracted MAC frames to frame processing unit 230-2.
[0079] The management unit 220 controls the establishment of the wireless connection (wireless link) between the shared AP10 and the non-APMLD of the terminal device 30 in a multi-AP connection. Furthermore, based on notifications from the shared AP10, the management unit 220 performs tasks such as generating and distributing beacons required for the multi-AP connection, managing the status of the wireless link between the A-AP of the shared AP20 and the A-STA of the terminal device 30 in the multi-AP connection, and controlling the Co-SR (Coordinated-Spatial Reuse) function. The management unit 220 also includes link management information 221 and a decision unit 222.
[0080] Link management information 221 stores management information about the status of the wireless link used in a multi-AP connection. Additionally, link management information 221 includes, for example, the identifier of the shared AP 10 to which this station belongs and the identifier of the A-STA of the terminal device 30 that has established a wireless link with this station. Link management information 221 may also store information included in multi-AP management information 131 and link management information 132. Management unit 220 uses link management information 221 to manage the validity and invalidation of the wireless link. Determination unit 222 detects signals from the managed terminal device 30 and performs determination processing described later. In the determination processing, determination unit 222 determines, based on information from the managed terminal device 30, whether to set the Co-SR function to an enabled state (valid) or a disabled state (invalid). Information about the managed terminal device 30 is obtained from the managed terminal device 30. Determination unit 222 may also notify the shared AP 10 of the determination result. The specific usage method of determination unit 222 will be described in the second embodiment.
[0081] When a MAC frame is input from the data processing unit 240, the frame processing unit 230-1 outputs the input frame to the transceiver unit 210-1. When a MAC frame is input from the transceiver unit 210-1, the frame processing unit 230-1 outputs the input MAC frame to the management unit 220 or the data processing unit 240, depending on the frame type. For example, when a data frame is input from the transceiver unit 210-1, the frame processing unit 230-1 outputs the input frame to the data processing unit 240. When a management frame or control frame for the local station is input from the transceiver unit 210-1, the frame processing unit 230-1 outputs the input frame to the management unit 220.
[0082] When a MAC frame is input from the data processing unit 240, the frame processing unit 230-2 outputs the input frame to the transceiver unit 210-2. When a MAC frame is input from the transceiver unit 210-2, the frame processing unit 230-2 outputs the input MAC frame to the management unit 220 or the data processing unit 240, depending on the frame type. For example, when a data frame is input from the transceiver unit 210-2, the frame processing unit 230-2 outputs the input frame to the data processing unit 240. When a management frame or control frame for the local station is input from the transceiver unit 210-2, the frame processing unit 230-2 outputs the input frame to the management unit 220.
[0083] The data processing unit 240 outputs the MAC frame input from the frame processing unit 230-1 to the frame processing unit 230-2. Conversely, the data processing unit 240 outputs the MAC frame input from the frame processing unit 230-2 to the frame processing unit 230-1.
[0084] (3: Functional structure of terminal device 30)
[0085] Figure 7 This is a block diagram illustrating an example of the functional structure of the terminal device 30 included in the communication system 1 of the first embodiment. For example... Figure 7 As shown, the terminal device 30 functions, for example, as a computer comprising an application execution unit 300, an LLC processing unit 310, a data processing unit 320, a management unit 330, a frame processing unit 340, and A-STA1 and A-STA2. The application execution unit 300 is a function block that performs processing corresponding to Layer 7. The LLC processing unit 310 is a function block that performs processing corresponding to the LLC sublayer of Layer 2 and Layers 3 through 6. The data processing unit 320, management unit 330, and frame processing unit 340 are function blocks that perform processing corresponding to the MAC sublayer of Layer 2. A-STA1 and A-STA2 are function blocks that perform processing corresponding to the MAC sublayer of Layer 2 and Layer 1. For example, the group consisting of the LLC processing unit 310, data processing unit 320, management unit 330, and frame processing unit 340 corresponds to non-AP_MLD.
[0086] The application execution unit 300 executes the application based on data input from the LLC processing unit 310. Additionally, the application execution unit 300 outputs data to the LLC processing unit 310. For example, the application execution unit 300 can display application information on the display 35. Furthermore, the application execution unit 300 can perform actions based on operations of the input interface.
[0087] LLC processing unit 310 generates LLC packets by appending DSAP headers, SSAP headers, etc., to the data input from application execution unit 300 (upper level). Then, LLC processing unit 310 outputs the generated LLC packets to data processing unit 320. Additionally, LLC processing unit 310 extracts data from the LLC packets input from data processing unit 320. Then, LLC processing unit 310 outputs the extracted data to application execution unit 300 (upper level).
[0088] The data processing unit 320 appends a MAC header to the LLC packets input from the LLC processing unit 310 to generate a MAC frame. Then, the data processing unit 320 outputs the generated MAC frame to the frame processing unit 340. Additionally, the data processing unit 320 extracts LLC packets from the MAC frames input from the frame processing unit 340. Then, the data processing unit 320 outputs the extracted LLC packets to the LLC processing unit 310.
[0089] The management unit 330 establishes a wireless connection (wireless link) with the shared AP 10, maps data types to links, and sets BlockAck. For example, the management unit 330 can obtain management information from beacons received from the shared AP 20. Furthermore, the management unit 330 manages the status of the wireless link between the A-AP of the shared AP 20 and the A-STA of the terminal device 30 in a multi-AP connection. Additionally, the management unit 330 includes link management information 331.
[0090] Link management information 331 stores management information related to the status of the wireless link used in a multi-AP connection. Additionally, link management information 331 includes, for example, information about the identifier of the shared AP 10 to which this station belongs and the identifier of the shared AP 20 with which this station has established a wireless link. Link management information 331 may also store information contained in multi-AP management information 131 and link management information 132. Management unit 330 uses link management information 331 to manage the validity and invalidation of wireless links.
[0091] When a MAC frame is input from the data processing unit 320, the frame processing unit 340 outputs the input frame to at least one of A-STA1 and A-STA2 according to the service allocation. Alternatively, when a MAC frame is input from either A-STA1 or A-STA2, the frame processing unit 340 outputs the input frame to either the management unit 330 or the data processing unit 320 according to the frame type. For example, when a data frame is input from either A-STA1 or A-STA2, the frame processing unit 340 outputs the input frame to the data processing unit 320. When a data frame is input from the data processing unit 320, the frame processing unit 340 outputs the input frame to either A-STA1 or A-STA2. When a management frame or control frame for the local station is input from either A-STA1 or A-STA2, the frame processing unit 340 outputs the input frame to the management unit 330.
[0092] A-STA1 and A-STA2 each function as a wireless signal processing unit, configured to transmit and receive data and management information with the shared AP20 via wireless communication. A-STA adds a preamble or similar code to the MAC frame input from the frame processing unit 340 to generate a wireless frame. Then, A-STA converts the generated wireless frame into a wireless signal. A-STA then transmits (transmits) the converted wireless signal to the wirelessly connected shared AP20 via an antenna. Additionally, A-STA converts wireless signals received from the wirelessly connected shared AP20 via an antenna into wireless frames. A-STA extracts the MAC frame from the converted wireless frame and outputs the extracted MAC frame to the frame processing unit 340.
[0093] Figure 8 This is a block diagram illustrating an example of the functional structure of the auxiliary STA (A-STA) included in the terminal device 30 of the communication system 1 according to the first embodiment. For example... Figure 8 As shown, A-STA includes a MAC frame generation unit 351, a transceiver unit 352, and a MAC frame processing unit 353.
[0094] The MAC frame generation unit 351 generates a MAC frame by adding a MAC header to the data input from the frame processing unit 340, and outputs it to the transceiver unit 352. The MAC header contains a sequence number (SN) assigned to identify the data. That is, the sequence number (SN) is output from the non-AP_MLD transmit buffer along with the data.
[0095] The transceiver unit 352 performs wireless processing on the MAC frames input from the MAC frame generation unit 351 and transmits them. On the other hand, the transceiver unit 352 extracts MAC frames from the wireless signals received via the antenna and outputs them to the MAC frame processing unit 353.
[0096] The MAC frame processing unit 353 determines whether a MAC frame received from the transceiver unit 352 has been correctly received based on the frame check sequence. Then, the MAC frame processing unit 353 outputs the correctly received data to the non-AP_MLD frame processing unit 340.
[0097] <1-2> Actions
[0098] Next, the operation of the communication system 1 of the first embodiment will be described.
[0099] <1-2-1> Control method for enabling / disabling the Co-SR function
[0100] Figure 9 This is a flowchart illustrating an example of a control method for enabling and disabling the Co-SR function of the shared AP10 in the communication system 1 of the first embodiment.
[0101] For example, shared AP10 executes (starts) periodically based on a predetermined schedule. Figure 9 A series of processes. Figure 9 The series of processes can begin either based on user actions or based on pre-defined triggers.
[0102] First, the shared AP10 obtains information about the shared AP20 under its jurisdiction (step S10). Details about the shared AP20 under its jurisdiction will be described later.
[0103] Next, the shared AP10 determines whether to use the Co-SR function (step S11). Specifically, the determination unit 133 of the shared AP10 performs a determination process. In the determination process, the determination unit 133 uses the information of the managed shared AP20 obtained through the process of step S10 and the pre-set usage conditions of the Co-SR function to determine whether the Co-SR function should be set to an on state or an off state.
[0104] Next, the shared AP10 confirms whether the determination result is different from the current usage status of the Co-SR function (step S12). At this time, the determination unit 133 obtains the current usage status of the Co-SR function from, for example, the link management information 132.
[0105] If, during the processing in step S12, it is confirmed that the determination result is the same as the current usage status of the Co-SR function (step S12: No), the sharing of AP10 ends. Figure 9 A series of processes (end). For example, if the Co-SR function is enabled in the shared AP20 under its jurisdiction, and the determination result of step S11 shows that, with the Co-SR function enabled, the shared AP10 maintains the current setting of the Co-SR function of the shared AP20 under its jurisdiction.
[0106] If, during the processing in step S12, it is confirmed that the determination result is different from the current usage status of the Co-SR function (step S12: Yes), the shared AP10 notifies the shared AP20 of the determination result (step S13).
[0107] After the processing in step S13, the shared AP10 sets the Co-SR function based on the determination result (step S14). Then, the shared AP10 terminates. Figure 9 A series of processes (end). For example, if the Co-SR function is off in the managed shared AP20, and the determination result of step S11 shows that the Co-SR function is turned on, the shared AP10 sets the Co-SR function of the managed shared AP20 to the on state through the process of step S14.
[0108] <1-2-2> Information Collection Methods Used in Determining the Enabling and Disabling of the Co-SR Function
[0109] Figure 10 This is a schematic diagram illustrating an example of an information acquisition method used in determining the activation / deactivation of the Co-SR function in the communication system 1 of the first embodiment. Hereinafter, as... Figure 10The following examples illustrate the connection between shared AP20-1 and terminal devices 30-1, 30-2, and 30-3, and shared AP20-2 and terminal devices 30-4, 30-5, and 30-6. It should be noted that the connection between shared AP20 and terminal device 30 can be either a multi-link or a single-link connection.
[0110] like Figure 10 As shown, in order to collect information used in the Co-SR function settings, the shared AP10 sends a radio frame containing a request to the managing shared AP20. Then, based on the received request, the managing shared AP20 notifies the shared AP10 of the information used in determining whether the Co-SR function is enabled or disabled. The shared AP10 can either store the request in beacon signals transmitted via multicast or broadcast, or it can send the request to each shared AP20.
[0111] The shared AP20 can also store information used in determining whether the Co-SR function is enabled or disabled in elements such as those appended to action frames or beacon frame formats. The shared AP20 can then use such radio frames to notify the shared AP10 of its intention to use the Co-SR function.
[0112] It should be noted that the shared AP20 can also append notification blocks and elements for information to the trigger frame and BlockAck and send them. Additionally, the shared AP20 can also be configured to spontaneously notify the shared AP10 of information. In this case, the sending of the request from the shared AP10 to the shared AP20 related to the notification of this information can be omitted.
[0113] <1-2-3> Conditions for using the Co-SR function
[0114] The following describes an example of the usage conditions of the Co-SR function referenced in the decision-making process. It should be noted that the communication system 1 shown in the accompanying diagram illustrating the usage conditions of the Co-SR function... Figure 10 It is constructed in the same way.
[0115] (1: First condition for use)
[0116] Figure 11 This is a schematic diagram illustrating the first usage conditions of the Co-SR function in the communication system 1 of the first embodiment. The first usage condition of the Co-SR function in the first embodiment is that the number of shared APs 20 that wish to use the Co-SR function is a predetermined number or more. Figure 11 In one example shown, as the first condition for using the Co-SR function, the number of shared AP20s that want to use the Co-SR function is set to be 2 or more.
[0117] In this example, using AP20-1 and 20-2 together means using the Co-SR function. Figure 11 (The "○"). Therefore, shared AP10 instructs shared APs 20-1 and 20-2 to enable the Co-SR function. Then, shared APs 20-1 and 20-2 begin using the Co-SR function. In this way, shared AP10 can determine the use of the Co-SR function based on the number of shared APs 20 that want to use the Co-SR function.
[0118] It should be noted that, in the first condition for using the Co-SR function, each shared AP20 can also notify the shared AP10 of two values indicating whether it wants to use the Co-SR function or not. Additionally, each shared AP20 can also notify the shared AP10 of its intention to use the Co-SR function using a value greater than two. For example, the four stages from 0 to 3 could represent the level of request for the Co-SR function. In this case, the shared AP10, for example, determines the use of the Co-SR function based on the total level of Co-SR function requests from the managed shared AP20s and a predetermined threshold.
[0119] (2: Second usage conditions)
[0120] Figure 12 This is a schematic diagram illustrating the second usage condition of the Co-SR function in the communication system 1 of the first embodiment. The second usage condition of the Co-SR function in the first embodiment is that the distance between the two shared APs 20 (distance between shared APs) is greater than a predetermined distance. Figure 12 In one example shown, as a second condition for using the Co-SR function, the distance between the shared APs is set to exceed Dth. Dth is set to a value that, for example, ensures good power control when the Co-SR function is used on the two shared APs 20.
[0121] In this example, the distance between shared APs 20-1 and 20-2 is greater than Dth. Therefore, shared AP 10 instructs shared APs 20-1 and 20-2 to enable the Co-SR function. Then, shared APs 20-1 and 20-2 respectively begin using the Co-SR function. In this way, shared AP 10 can determine the use of the Co-SR function based on the distance between shared APs. That is, shared AP 10 can determine the use of the Co-SR function based on the location of shared AP 20.
[0122] It should be noted that the shared AP10 can estimate the location of the shared AP20 based on the power level of the signal received from the shared AP20. Additionally, the shared AP10 can pre-store the configuration coordinates of each shared AP20. In this case, the shared AP10 can calculate the distance between the shared APs based on the configuration coordinates of each shared AP20. Each shared AP20 can be equipped with GPS (Global Positioning System) or configured to notify the shared AP10 of its location information obtained from GPS. In this case, the shared AP10 can calculate the distance between the shared APs based on the location information received from each shared AP20.
[0123] Furthermore, the second usage condition for the Co-SR function can also be used when there are three or more shared APs 20. For example, for each shared AP 20, the decision to enable or disable the Co-SR function is performed using the distance between the shared APs and the nearest shared AP 20. The second usage condition for the Co-SR function can also be combined with the first usage condition for the Co-SR function. In this case, the shared AP 10 determines whether to use the Co-SR function for each shared AP 20 based on the number of shared APs 20 for which the Co-SR function is desired and the distance between the shared APs 20.
[0124] (3: Third condition for use)
[0125] Figure 13 This is a schematic diagram illustrating the third usage condition of the Co-SR function in the communication system 1 of the first embodiment. The third usage condition of the Co-SR function in the first embodiment is that the managed shared AP20 uses beamforming. Figure 13 In one example, shared APs 20-1 and 20-2 each use beamforming. Therefore, shared AP 10 instructs shared APs 20-1 and 20-2 to enable the Co-SR function. Then, shared APs 20-1 and 20-2 each begin using the Co-SR function. In this way, shared AP 10 can determine the use of the Co-SR function based on the beamforming settings of the shared APs.
[0126] It should be noted that the shared AP10 can also refer to the detailed beamforming settings in the third usage condition of the Co-SR function. For example, the shared AP10 can determine whether to enable the Co-SR function based on the signal directivity information based on the beamforming settings. Furthermore, in the third usage condition of the Co-SR function, the determination of whether to enable the Co-SR function can also be based on the number of shared AP20s using beamforming. For example, if the number of shared AP20s using beamforming exceeds a predetermined threshold, the Co-SR function will be enabled.
[0127] (4: Fourth condition for use)
[0128] Figure 14 This is a schematic diagram illustrating the fourth usage condition of the Co-SR function in the communication system 1 of the first embodiment. The fourth usage condition of the Co-SR function in the first embodiment is whether the number of terminal devices 30 detected by the shared AP 20 that are not detected by other shared AP 20s is greater than or equal to a predetermined number. Figure 14 In one example shown, as the fourth condition for using the Co-SR function, the number of terminal devices 30 detected by the shared AP 20 that are not detected by other shared AP 20s is set to two or more. Hereinafter, the terminal devices 30 detected by the shared AP 20 will be referred to as "detected terminals".
[0129] In this example, the detection terminals sharing AP20-1 are terminal devices 30-1, 30-2, 30-3, and 30-4. On the other hand, the detection terminals sharing AP20-2 are terminal devices 30-3, 30-4, 30-5, and 30-6. In this case, terminal devices 30-3 and 30-4 are duplicated among the detection terminals of both shared AP20-1 and 20-2. Therefore, the number of terminal devices 30 detected by shared AP20-1 that are not detected by other shared AP20-2 is two (terminal devices 30-1 and 30-2). Similarly, the number of terminal devices 30 detected by shared AP20-1 that are not detected by other shared AP20-2 is two (terminal devices 30-5 and 30-6).
[0130] The shared AP10 can determine the number of undetected terminals in each shared AP20 based on the information about the detected terminals notified by shared APs 20-1 and 20-2. In this example, since there are more than two undetected terminals in each shared AP20, the shared AP10 instructs shared APs 20-1 and 20-2 to enable the Co-SR function. Then, shared APs 20-1 and 20-2 begin using the Co-SR function. In this way, the shared AP10 can determine the use of the Co-SR function based on the number of terminal devices 30 detected by the shared APs 20 that are not detected by other shared APs 20.
[0131] In other words, the shared AP10 compares the number of terminal devices 30 that each shared AP20 can detect. Then, the shared AP10 determines the configuration deviation of the terminal devices 30. If the deviation exceeds a certain threshold, that is, if the number of terminal devices 30 above the threshold cannot detect each other, it determines that the Co-SR function is enabled.
[0132] It should be noted that the shared AP20 can determine whether the terminal device 30 has been detected based on the received power value. For example, the shared AP20 can also treat a signal source that has been successfully demodulated with a preamble at a received power of -62dBm or higher as the detected terminal device 30.
[0133] <1-3> Effects of the first embodiment
[0134] As explained above, in the communication system 1 of the first embodiment, the shared AP 10 can determine whether the Co-SR function is enabled or disabled based on information from the managed shared AP 20, and change the settings of the Co-SR function applied to the shared AP 20. As a result, the communication system 1 of the first embodiment can use the Co-SR function efficiently and improve the effect of power control.
[0135] <2> Implementation Method 2
[0136] In the communication system 1 of the second embodiment, the shared AP 20 is configured to control the activation and deactivation of the Co-SR function based on information from the managed terminal device 30. Hereinafter, details of the communication system 1 of the second embodiment will be described, primarily focusing on aspects that differ from the first embodiment. It should be noted that the structure of the communication system of the second embodiment is the same as that of the first embodiment.
[0137] <2-1> Actions
[0138] The operation of the communication system 1 in the second embodiment will be described below.
[0139] <2-1-1> Control method for enabling / disabling the Co-SR function
[0140] Figure 15 This is a flowchart illustrating an example of a control method for enabling and disabling the Co-SR function of the shared AP20 in the communication system 1 of the second embodiment.
[0141] Shared AP20, for example, is executed regularly based on a predetermined schedule. Figure 15 A series of processes (beginning). Figure 15 The series of processes can begin based on a request from the shared AP10, a user action, or a pre-defined trigger.
[0142] First, the AP20 is used to obtain information about the managed terminal device 30 (step S20). Details about the information about the managed terminal device 30 will be described later.
[0143] Next, the shared AP20 determines whether to use the Co-SR function (step S21). Specifically, the determination unit 222 of the shared AP20 performs a determination process. In the determination process, the determination unit 222 uses the information of the managed terminal device 30 obtained through the process of step S20 and the preset usage conditions of the Co-SR function to determine whether to set the Co-SR function to an on state or an off state.
[0144] Next, AP20 confirms whether the determination result differs from the current usage status of the Co-SR function (step S22). At this time, determination unit 222 obtains the current usage status of the Co-SR function from, for example, link management information 331.
[0145] In step S22, if it is confirmed that the determination result is the same as the current usage status of the Co-SR function (step S22: No), the shared AP20 ends. Figure 15 A series of processes (end). For example, if its own Co-SR function is effective and the determination result of step S21 shows that the Co-SR function is effective, the shared AP20 maintains the current setting of its own Co-SR function.
[0146] In step S22, if it is confirmed that the determination result is different from the current usage status of the Co-SR function (step S22: Yes), the shared AP20 notifies the shared AP10 of the determination result (step S23). The shared AP10, which has been notified of the determination result, updates the usage status of the Co-SR function in the shared AP20, which is the source of the determination result.
[0147] After the processing in step S23, the shared AP20 sets the Co-SR function based on the determination result (step S14). Then, the shared AP20 terminates. Figure 15 A series of processes (end). For example, if its own Co-SR function is off and the determination result of step S21 indicates that the Co-SR function should be on, the shared AP20 sets its own Co-SR function to on through the process of step S24.
[0148] <2-1-2> Information Collection Methods Used in Setting Up the Co-SR Function
[0149] Figure 16 This is a schematic diagram illustrating an example of an information acquisition method used in determining whether the Co-SR function is enabled or disabled in the communication system 1 of the second embodiment.
[0150] like Figure 16As shown, the shared AP 20 sends a radio frame containing a request to the managed terminal device 30 in order to collect information used in setting up the Co-SR function. Then, the managed terminal device 30, based on the received request, notifies the shared AP 20 of the information used in determining whether the Co-SR function is enabled or disabled. The shared AP 20 can store the request in beacon signals transmitted via multicast or broadcast, or it can send the request to each terminal device 30.
[0151] Terminal device 30 may also store the information used in determining whether the Co-SR function is enabled or disabled in elements attached to action frames, beacon frame formats, etc. Terminal device 30 can use such radio frames to notify the shared AP 20 of its intention to use the Co-SR function.
[0152] It should be noted that terminal device 30 may also append blocks or elements for information notification to the trigger frame or BlockAck and send them. Alternatively, terminal device 30 may be configured to spontaneously notify the shared AP 20 of the information. In this case, the transmission of the request from shared AP 20 to terminal device 30 related to the notification of this information can be omitted.
[0153] <2-1-3>Conditions for Using Co-SR Function
[0154] Figure 17 This is a schematic diagram illustrating the usage conditions of the Co-SR function in the communication system of the second embodiment. For example, the usage conditions of the Co-SR function in the second embodiment include whether the number of terminal devices 30 that wish to use the Co-SR function is greater than a predetermined number. Figure 17 In one example shown, as a condition for using the Co-SR function, it is set whether the number of terminal devices 30 that want to use the Co-SR function is 3 or more.
[0155] In this example, terminal devices 30-1, 30-2, and 30-3 connected to the shared AP20-1 respectively indicate the use of the Co-SR function. Figure 17 (The circle "○" is used). Therefore, the shared AP20-1 spontaneously begins to use the Co-SR function. On the other hand, the terminal devices 30-4, 30-5, and 30-6 connected to the shared AP20-2 do not indicate that they intend to use the Co-SR function. In this case, the shared AP20-2 disables the Co-SR function.
[0156] In this way, the shared AP 20 can determine the use of the Co-SR function based on the number of terminal devices 30 that wish to use the Co-SR function, without relying on instructions from the shared AP 10. It should be noted that, in the Co-SR function usage conditions of the second embodiment, each terminal device 30 can also notify the shared AP 20 of a binary value indicating whether it wants to use the Co-SR function or not. Alternatively, each terminal device 30 can also notify the shared AP 20 of its intention to use the Co-SR function using a value greater than binary. For example, the four stages from 0 to 3 represent the level of request for the Co-SR function. In this case, the shared AP 20, for example, determines the use of the Co-SR function based on the total level of Co-SR function requests from the managed terminal devices 30 and a predetermined threshold.
[0157] It should be noted that the shared AP 20 may also obtain information used in determining the use of the Co-SR function only from a specific terminal device 30. In this case, the shared AP 20 determines the use of the Co-SR function based on the information obtained from the specific terminal device 30. For example, the shared AP 20 may designate the terminal device 30 that wants to perform beamforming-based transmission as the terminal device 30 used in determining the use of the Co-SR function. Alternatively, the terminal device 30 may also spontaneously transmit information used in determining the use of the Co-SR function to the shared AP 20.
[0158] As described above, the shared AP20 can determine whether to use the Co-SR function separately from the Co-SR function setting configured by the shared AP10. For example, even if the shared AP10 does not instruct the use of the Co-SR function, the shared AP20 can still use the Co-SR function if the above usage conditions are met. It should be noted that the setting for enabling or disabling the Co-SR function can be based either on the determination result of the shared AP10 or on the determination result of the shared AP20.
[0159] <2-2> Effects of the second implementation method
[0160] In the communication system 1 of the second embodiment, the shared AP 20 can determine whether the Co-SR function is enabled or disabled based on information from the managed terminal devices 30, and change the settings of the Co-SR function applied to itself. As a result, the communication system 1 of the second embodiment can use the Co-SR function efficiently and improve the effect of power control.
[0161] <3> other
[0162] In the above embodiments, the shared AP10 can either set the Co-SR function on / off to the same setting for all managed shared AP20s, or it can set them independently. The above embodiments illustrate a case where each terminal device 30 establishes multiple links with one shared AP20, but it is not limited to this. The control method for enabling / disabling the Co-SR function described in the above embodiments can be executed similarly when the terminal device 30 is connected to multiple APs. Furthermore, the terminal device 30 connected to the shared AP20 can also be a single-link device. Both single-link and multi-link devices can be connected to the shared AP20. The determination unit 133 of the shared AP10 can also determine whether to use the Co-SR function based on information received from the terminal device 30 via the managed shared AP20.
[0163] Figure 18 This is a block diagram illustrating an example of the structure of a communication system modified from the first embodiment. For example... Figure 18 As shown, the communication system 1 may also include multiple shared APs 10 connected via a network NW. In this example, shared AP 10-1 and shared AP 10-2 are connected via the network NW. The multiple shared APs 10 can be connected to each other either by wired or wireless means. Information about the shared APs 20 managed by each shared AP 10 and information related to the determination results of enabling or disabling the Co-SR function can also be exchanged between the determination units 133 of each shared AP 10 and the determination units 133 of other shared APs 10. Therefore, the communication system 1 of the modified embodiment of the first embodiment enables multiple shared APs 10 to cooperate in controlling the enabling or disabling of the Co-SR function of the shared APs 20 managed by each shared AP 10.
[0164] The transformation process from wireless frames to wireless signals described in the above embodiments includes, for example, convolutional coding, interleaving, subcarrier modulation, inverse fast Fourier transform, OFDM modulation, and frequency conversion. The transformation process from wireless signals to wireless frames described in the embodiments includes, for example, frequency conversion, OFDM demodulation, fast Fourier transform, subcarrier demodulation, deinterleaving, and Viterbi decoding. In this specification, BlockAck may also be referred to as a receive acknowledgment frame. A BlockAck request may also be referred to as a receive acknowledgment request frame.
[0165] In the above embodiments, the CPU 11 of the shared AP10, the CPU 21 of the shared AP20, and the CPU 31 of the terminal device 30 can be other circuits. For example, the shared AP10, the shared AP20, and the terminal device 30 can each have an MPU (Micro Processing Unit) instead of a CPU. The processing described in the above embodiments can also be implemented by dedicated hardware. The processing of the shared AP10, the shared AP20, and the terminal device 30 can be a mixture of software-executed processing and hardware-executed processing, or only one of them. The CPU can also be referred to as a "processor". The wireless communication module can also be referred to as a "communication circuit".
[0166] In the above embodiments, the flowchart used to illustrate the actions is merely one example. The order of the actions described in the embodiments can be rearranged to the extent possible, and additional processes can be added. For example, Figure 9 The processing order of steps S13 and S14 shown can also be reversed. Similarly, Figure 15 The processing order of steps S23 and S24 shown can also be reversed. As a wireless communication standard, a wireless communication standard different from the IEEE 802.11 standard can also be used.
[0167] It should be noted that the present invention is not limited to the above-described embodiments, and various modifications can be made during implementation without departing from its essence. Furthermore, the embodiments can be appropriately combined to achieve combined effects. Moreover, the above embodiments include various inventions, and various inventions can be extracted by selecting combinations from the disclosed multiple constituent elements. For example, if the problem can be solved and the effect obtained even if several constituent elements are deleted from all the constituent elements shown in the embodiments, the structure with the deleted constituent elements can be extracted as an invention.
[0168] Explanation of reference numerals in the attached figures
[0169] 1…Communication system; 10…Shared access point; 20…Common access point; 30…Terminal device; 11, 21, 31…CPU; 12, 22, 32…ROM; 13, 23, 33…RAM; 14, 24, 34…Wireless communication module; 15…Wired communication module; 35…Display; 36…Storage; 110, 310…LLC processing unit; 120, 240, 320…Data processing unit; 130, 220, 330…Management unit; 131…Multi-AP management information; 132, 221…Link management information; 133, 222…Decision unit; 140, 230-1, 230-2, 340…Frame processing unit; 300…Application execution unit; 351…MAC frame generation unit; 352…Transmitter / receiver unit; 353…MAC frame processing unit.
Claims
1. An access point, wherein, This access point has the following features: The communication circuit is configured to communicate with multiple access points; and The processor is configured to determine whether each of the plurality of access points uses spatial multiplexing function based on information from each of the plurality of access points, and to apply the spatial multiplexing function setting based on the result of the determination to the plurality of access points.
2. The access point according to claim 1, wherein, The processor is further configured to determine whether to use the spatial multiplexing function based on the number of access points among the plurality of access points that wish to use the spatial multiplexing function.
3. The access point according to claim 1, wherein, The processor is further configured to determine whether to use the spatial multiplexing function based on the distance between two closest access points among the plurality of access points.
4. The access point according to claim 3, wherein, The processor is further configured to determine whether to use the spatial multiplexing function based on the number of beamforming access points among the plurality of access points.
5. The access point according to claim 1, wherein, The plurality of access points includes a first access point and a second access point. The processor is further configured to determine whether to use the spatial multiplexing function based on the number of terminal devices detected by the first access point that were not detected by the second access point.
6. An access point, configured in a communication system for transmitting data between terminal devices governed by the access point and other access points via the access point, wherein, This access point has the following features: The communication circuit is configured to communicate with the other access points and multiple terminal devices respectively; as well as The processor is configured to determine whether to use the spatial multiplexing function based on information from each of the plurality of terminal devices, and to apply the spatial multiplexing function settings based on the result of the determination.
7. The access point according to claim 6, wherein, The processor is further configured to determine whether to use the spatial multiplexing function based on the number of terminal devices among the plurality of terminal devices that wish to use the spatial multiplexing function.
8. The access point according to claim 6, wherein, The processor is further configured to notify the access point of the spatial multiplexing function setting based on the result of the determination when the current spatial multiplexing function setting differs from the spatial multiplexing function setting based on the result of the determination.