Sharing access point, shared access point, and terminal device
The wireless communication system addresses the challenge of multi-AP communication by synchronizing the R-TWT service period across multiple access points, enhancing low-latency traffic efficiency and reducing delays and jitter in the multi-AP environment.
Patent Information
- Application Number
- PCT/JP2023/020522
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-06-01
- Publication Date
- 2024-12-05
AI Technical Summary
In multi-AP communication, efficiently transmitting low-latency traffic is hindered due to the need for individual setup of the R-TWT function for multiple access points and lack of cooperative communication among them.
A wireless communication system with a sharing access point that establishes a multi-AP connection, sets a shared service period for low-latency traffic across multiple links, and notifies each access point to prioritize traffic exchange during this period, enabling efficient low-latency traffic transmission.
This configuration provides a wireless communication environment where low-latency traffic can be efficiently transmitted by synchronizing the service period across multiple access points, reducing delays and jitter, and allowing seamless handovers without reconfiguring the R-TWT agreement.
Smart Images

Figure JP2023020522_05122024_PF_FP_ABST
Abstract
Description
Sharing access point, shared access point, and terminal device
[0001] The embodiments relate to a sharing access point, a shared access point, and a terminal device.
[0002] A wireless local area network (LAN) is known as a communication system that wirelessly connects an access point (AP) and a terminal device. The terminal device can access the network via an access point within a communication area via the wireless LAN. IEEE 802.11be mentions multi-link transmission, in which multiple links (transmission paths) are established between the terminal device and the access point. In multi-link transmission, multiple links can operate independently. Furthermore, multi-AP communication, in which multiple links are established between a terminal device and multiple access points, is being considered for the next generation standard.
[0003] Furthermore, the R-TWT (restricted target wake time) function is known as a method for transmitting and receiving low-latency traffic between an access point and a terminal device. An access point using the R-TWT function sets a service period at a period corresponding to the required latency of the low-latency traffic and notifies the terminal device of the set service period using a management frame or action frame such as a beacon. The access point then prioritizes the transmission and reception of low-latency traffic during the periodically set service period. This can reduce the delay and jitter of the low-latency traffic. When the R-TWT function is used in multilink communication, the contents set up using one link between the access point and the terminal device can be reflected in the other links that make up the multilink.
[0004] IEEE802.11be D3.0, “35.3.24 TWT operation”, p585-p586, January 2023
[0005] However, in multi-AP communication, the R-TWT function must be individually configured for each of the access points connected to the terminal device. Also, in multi-AP communication, if the access points cannot coordinate their communications, efficient low-latency traffic transmission may be hindered.
[0006] The present invention has been made in light of the above circumstances, and its purpose is to provide a wireless communication environment that enables efficient transmission of low-latency traffic in multi-AP communication.
[0007] A shared access point according to an embodiment includes a first management unit. The shared access point is included in a communication system including: a shared access point including a second management unit and a first wireless signal processing unit; another shared access point including a third management unit and a second wireless signal processing unit; and a terminal device including a fourth management unit and third and fourth wireless signal processing units. The first management unit is configured to establish a first wireless link between the first and third wireless signal processing units and a second wireless link between the second and fourth wireless signal processing units, and to collectively establish a service period during which traffic frame exchange can be preferentially performed for the first wireless link and the second wireless link by transmitting and receiving frames via the first wireless link with the third management unit, and to notify each of the second management unit and the third management unit of a start time of the service period.
[0008] According to the embodiment, it is possible to provide a wireless communication environment that allows efficient transmission of low-latency traffic.
[0009] FIG. 1 is a block diagram showing an example of the configuration of a communication system according to an embodiment. FIG. 2 is a block diagram showing an example of the hardware configuration of a shared access point included in the communication system according to an embodiment. FIG. 3 is a block diagram showing an example of the hardware configuration of a shared access point included in the communication system according to an embodiment. FIG. 4 is a block diagram showing an example of the hardware configuration of a terminal device included in the communication system according to an embodiment. FIG. 5 is a block diagram showing an example of the functional configuration of a shared access point included in the communication system according to an embodiment. FIG. 6 is a table showing an example of multi-AP management information included in a management unit of a shared access point included in a communication system according to an embodiment. FIG. 7 is a table showing an example of information associated with one affiliated STA among link management information included in a management unit of a shared access point included in a communication system according to an embodiment. FIG. 8 is a block diagram showing an example of the functional configuration of a shared access point included in a communication system according to an embodiment. FIG. 9 is a block diagram showing an example of the functional configuration of a terminal device included in a communication system according to an embodiment. FIG. 10 is a flowchart showing an example of the operation of a shared access point included in a communication system according to an embodiment. FIG. 11 is a sequence diagram showing an example of processing from multi-link setup to the start of R-TWT communication in a communication system according to an embodiment. FIG. 12 is a time chart showing an example of R-TWT communication in a communication system according to an embodiment.
[0010] Hereinafter, embodiments will be described with reference to the drawings. The embodiments illustrate devices and methods for embodying the technical ideas of the invention. The drawings are schematic or conceptual. In the following description, components having the same function and configuration are assigned common reference symbols. Furthermore, when multiple components having the same function and configuration are to be distinguished from one another, a hyphen and a number are added to the end of the reference symbol.
[0011] <1> Configuration First, the configuration of a communication system 1 according to the embodiment will be described.
[0012] <1-1> Configuration of communication system 1 Fig. 1 is a block diagram showing an example of the configuration of a communication system 1 according to an embodiment. As shown in Fig. 1, the communication system 1 includes a sharing access point (sharing AP) 10, multiple shared access points (shared APs) 20, and a terminal device 30.
[0013] The sharing AP 10 is a type of wireless LAN access point (AP). The sharing AP is connected to the network NW by wire or wirelessly. The sharing AP 10 is configured to communicate by wire or wirelessly with a server (not shown) on the network NW. The sharing AP is also connected by wire or wirelessly to each of the multiple shared APs 20. The sharing AP 10 is configured to communicate by wire or wirelessly with each of the multiple shared APs 20.
[0014] Each shared AP 20 is a type of wireless LAN access point (AP). The multiple shared APs 20 have the same configuration. Each shared AP 20 is configured to communicate wirelessly or via wire with the sharing AP 10 and to communicate wirelessly with the terminal device 30. The multiple shared APs 20 are installed at locations separated from each other and have different communication areas. Note that the communication area of each shared AP 20 may partially overlap with the communication areas of other shared APs 20.
[0015] The terminal device 30 is a wireless terminal such as a smartphone or a PC (Personal Computer). The terminal device 30 is wirelessly connected to each shared AP 20. The terminal device 30 is configured to communicate wirelessly with each shared AP 20. The terminal device 30 supports multi-link communication using multiple channels (links). Note that it is sufficient for the terminal device 30 to be located so as to be included in the communication area of at least one shared AP 20.
[0016] The wireless communication used in the communication system 1 complies with, for example, the IEEE 802.11 standard. The IEEE 802.11 standard has wireless communication functions based on the OSI (Open Systems Interconnection) reference model. In the OSI reference model, wireless communication functions 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, and Layer 7: Application Layer). The data link layer includes a Logical Link Control (LLC) sublayer and a Media Access Control (MAC) sublayer. Frequency bands used in the wireless communication of the communication system 1 include, for example, the 2.4 GHz band, the 5 GHz band, the 6 GHz band, the 45 GHz band, and the 60 GHz band. Multiple channels can be assigned to each frequency band.
[0017] (Communication Method of Communication System 1) In the communication system 1, the sharing AP 10, the shared AP 20, and the terminal device 30 each support multi-link transmission as a communication method. Furthermore, the sharing AP 10 can establish a multi-link with the terminal device 30 using multiple shared APs 20 and indirectly communicate with the terminal device 30 with which the multi-link has been established. In this specification, a wireless connection method in which the terminal device 30 communicates with the sharing AP 10 via multiple shared APs 20 is referred to as a "multi-AP connection method."
[0018] In the multi-AP connection method, a plurality of shared APs 20 belong to a sharing AP 10. Fig. 1 illustrates an example in which three shared APs 20-1, 20-2, and 20-3 belong to the sharing AP 10. The configuration and operation of the communication system 1 will be described below using as an example a case in which three shared APs 20-1, 20-2, and 20-3 belong to the sharing AP 10.
[0019] In this example, a link (transmission path) via shared AP 20-1, a link (transmission path) via shared AP 20-2, and a link (transmission path) via shared AP 20-3 are respectively established between the sharing AP 10 and the terminal device 30. In this case, each of the shared APs 20-1, 20-2, and 20-3 is a candidate destination for data exchange between the sharing AP 10 and the terminal device 30. Then, the terminal device 30 executes data exchange with the sharing AP 10 via one of the candidate shared APs 20-1, 20-2, and 20-3.
[0020] The terminal device 30 includes a non-AP MLD and multiple affiliated STAs (A-STAs). The non-AP MLD is a multi-link device (MLD) that manages the link status and wireless communication of each of the multiple A-STAs. The non-AP MLD may also perform processing to establish a multi-link between the sharing AP 10 and the terminal device 30 in a multi-AP connection method. Each A-STA corresponds to a functional block of a wireless link established with the shared AP 20. In this example, the terminal device 30 includes a non-AP MLD #1 as the non-AP MLD and multiple A-STAs A-STA #1, A-STA #2, and A-STA #3. Different channels or the same channel are assigned to A-STA #1 to #3. The same frequency band or different frequency bands may be used for A-STA #1 to #3.
[0021] The shared AP 20 includes an AP MLD and multiple affiliated APs (A-APs). The AP MLD manages the link status and wireless communication of each of the multiple A-APs. The AP MLD may also perform processing for establishing a multi-link between the sharing AP 10 and the terminal device 30 in a multi-AP connection method. Each A-AP corresponds to a functional block of a wireless link established with the terminal device 30. In this example, the shared AP 20-1 includes AP MLD #1 as the AP MLD and multiple A-APs include A-AP #1, A-AP #2, and A-AP #3. In this example, the shared AP 20-2 includes AP MLD #2 as the AP MLD and multiple A-APs include A-AP #4, A-AP #5, and A-AP #6. In this example, the shared AP 20-3 includes an AP MLD #3 as an AP MLD, and includes A-AP #7, A-AP #8, and A-AP #9 as multiple A-APs.
[0022] Each A-STA may establish a link with one or more A-APs, for example, for each shared AP 20 belonging to the sharing AP 10. Each A-STA is then set to a state in which it can communicate with one of the multiple A-APs with which it has established a link (i.e., a valid link). In this example, A-STAs #1 to #3 each establish a link with A-APs #1 to #9. A-STA #1 has its link with A-AP #1 set to valid, and its links with the other A-APs set to invalid. A-STA #2 has its link with A-AP #5 set to valid, and its links with the other A-APs set to invalid. A-STA #3 has its link with A-AP #9 set to valid, and its links with the other A-APs set to invalid.
[0023] Note that multiple links may be set to be active for one shared AP 20. Depending on the location of the terminal device 30, all links for each shared AP 20 may be set to be inactive. Furthermore, different identifiers are assigned to the above-described non-AP MLD #1, A-STAs #1 to #3, AP MLDs #1 to #3, and A-APs #1 to #9. Link IDs or MAC addresses may be used as such identifiers. In the following description, the non-AP MLD #1, A-STAs #1 to #3, AP MLDs #1 to #3, and A-APs #1 to #9 are each treated as an identifier.
[0024] (R-TWT Function) In the communication system 1, the sharing AP 10, the shared AP 20, and the terminal device 30 each support the R-TWT (restricted target wake time) function. The R-TWT function is a function that assigns a service period to the terminal device 30 during which traffic requiring low latency can be preferentially exchanged. Hereinafter, the service period set by the R-TWT function is referred to as the "R-TWT service period (R-TWT SP)," and traffic requiring low latency is referred to as "low latency traffic."
[0025] The sharing AP 10 sets a fixed period (TWT period) when setting up the R-TWT function. The TWT period is preferably set to match the transmission period of low-latency traffic. One period (TWT interval) of the TWT period includes an R-TWT SP. The R-TWT SP is determined, for example, by a TWT start time and a TWT duration. The TWT duration indicates the length of the R-TWT SP starting from the TWT start time. The terminal device 30 can recognize a time based on the TWT start time and the TWT period as the rTWT start time of the next R-TWT service period SP. The TWT interval also corresponds to the interval between the TWT start times of adjacent R-TWT service periods SP.
[0026] In the R-TWT SP, the sharing AP 10 uses the shared AP 20 with an active link to give priority to the terminal device 30 for frame exchange opportunities. The frame exchange opportunities correspond to opportunities for transmitting traffic (data) through frame exchange. The terminal device 30 transmits low-latency traffic, for example, based on receiving a trigger frame in the R-TWT SP. In this way, the R-TWT function can improve the latency of low-latency traffic by giving priority to transmitting the low-latency traffic of the terminal device 30 in the R-TWT SP.
[0027] In addition, when setting up the R-TWT function, a transmission suppression period may be set to overlap with the R-TWT SP. The transmission suppression period corresponds to a period during which traffic transmission by other terminal devices that are not given priority frame exchange opportunities is suppressed. The initial setting of the R-TWT function can be determined in various ways. For example, the initial setting of the R-TWT function may use traffic attributes, such as the traffic occurrence interval and data volume, notified by an application that generates low-latency traffic. In this case, the sharing AP 10 notifies a server on the network NW of the traffic type to obtain the corresponding traffic attributes. The sharing AP 10 then determines the initial setting of the R-TWT function based on the obtained traffic attributes.
[0028] <1-2> Hardware Configuration of Communication System 1 The hardware configuration of the communication system 1 according to the embodiment will be described below.
[0029] <1-2-1> Hardware Configuration of Sharing AP 10 Fig. 2 is a block diagram showing an example of the hardware configuration of the sharing AP 10 included in the communication system 1 according to the embodiment. Fig. 2 illustrates a case where the sharing AP 10 is wirelessly connected to each shared AP 20, and the sharing AP 10 is wiredly connected to the network NW. As shown in Fig. 2, the sharing AP 10 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.
[0030] The CPU 11 is an integrated circuit capable of executing various programs and controls the overall operation of the sharing AP 10. The ROM 12 is, for example, a non-volatile semiconductor memory that stores programs and control data for controlling the sharing AP 10. The RAM 13 is, for example, a volatile semiconductor memory that is used as a work area for the CPU 11. The wireless communication module 14 is configured to be able to send and receive wireless signals via an antenna. The wireless communication module 14 is used to send and receive data, etc., to and from each shared AP 20. The wired communication module 15 is a circuit used to send and receive data, etc., via wired signals. The wired communication module 15 is configured to be connectable to a network NW.
[0031] The sharing AP 10 may have other hardware configurations. For example, when the sharing AP 10 is wirelessly connected to each of the network NW and the shared AP 20, the wired communication module 15 may be omitted from the sharing AP 10. When the sharing AP 10 is wiredly connected to each of the network NW and the shared AP 20, the wireless communication module 14 may be omitted from the sharing AP 10. The antenna may be built into the sharing AP 10 or may be externally connected.
[0032] <1-2-2> Hardware configuration of the shared AP 20 Fig. 3 is a block diagram showing an example of the hardware configuration of the shared AP 20 included in the communication system 1 according to the embodiment. Fig. 3 illustrates a case where the sharing AP 10 and the shared AP 20 are wirelessly connected. As shown in Fig. 2, the shared AP 20 includes, for example, a CPU 21, a ROM 22, a RAM 23, and a wireless communication module 24.
[0033] The CPU 21 is an integrated circuit capable of executing various programs and controls the overall operation of the shared AP 20. The ROM 22 is, for example, a non-volatile semiconductor memory and stores programs and control data for controlling the shared AP 20. The RAM 23 is, for example, a volatile semiconductor memory and is used as a work area for the CPU 21. The wireless communication module 24 is configured to be able to send and receive wireless signals via an antenna. The wireless communication module 24 is used to send and receive data, etc., to and from the sharing AP 10 and to and from the terminal device 30.
[0034] The shared AP 20 may have other hardware configurations. For example, when the shared AP 20 is connected to the sharing AP 10 via a wired connection, a wired communication module 15 similar to that of the sharing AP 10 may be added to the shared AP 20. The antenna may be built into the shared AP 20 or may be externally connected.
[0035] 4 is a block diagram showing an example of the hardware configuration of the terminal device 30 included in the communication system 1 according to the embodiment. As shown in FIG. 4, 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 36.
[0036] The CPU 31 is an integrated circuit capable of executing various programs and controls the overall operation of the terminal device 30. The ROM 32 is, for example, a non-volatile semiconductor memory and stores programs and control data for controlling the terminal device 30. The RAM 33 is, for example, a volatile semiconductor memory and is used as a work area for the CPU 31. The wireless communication module 34 is configured to be able to send and receive wireless signals via an antenna. The wireless communication module 34 is used to send and receive data to and from the shared AP 20. The display 35 is, for example, a liquid crystal display (LCD) or an electro-luminescence (EL) display. The display 35 displays, for example, a graphical user interface (GUI) corresponding to application software. The storage 36 is a non-volatile storage device and stores, for example, system software for the terminal device 30.
[0037] The terminal device 30 may have other hardware configurations. For example, if the terminal device 30 is an IoT (Internet of Things) terminal or the like, the display 35 may be omitted from the terminal device 30. The display 35 may function as an input interface for the terminal device 30. The antenna may be built into the terminal device 30 or may be externally connected.
[0038] <1-3> Functional Configuration of Communication System 1 The functional configuration of the communication system 1 according to the embodiment will be described below.
[0039] <1-3-1> Functional Configuration of Sharing AP 10 FIG. 5 is a block diagram showing an example of the functional configuration of the sharing AP 10 included in the communication system 1 according to the embodiment. The sharing AP 10 functions as a computer including, for example, 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 executes processing corresponding to the LLC sublayer of layer 2 and layers 3 to 7. The data processing unit 120, the management unit 130, and the frame processing unit 140 are functional blocks that execute processing corresponding to the MAC sublayer of layer 2. When the sharing AP 10 communicates wirelessly with each shared AP 20, the transceiver unit 150 is a functional block that executes processing corresponding to layer 1. When the sharing AP 10 communicates wired with each shared AP 20, the transceiver unit 150 is a functional block that executes processing corresponding to the MAC sublayer of layer 2.
[0040] The LLC processing unit 110 generates LLC packets by, for example, adding a DSAP (Destination Service Access Point) header or an SSAP (Destination Service Access Point) header to data received from the network NW. The LLC processing unit 110 then inputs the generated LLC packets to the data processing unit 120. The LLC processing unit 110 also extracts data from the LLC packets input from the data processing unit 120. The LLC processing unit 110 then transmits the extracted data to the network NW.
[0041] Data processing unit 120 generates a MAC frame by adding a MAC header to the LLC packet input from LLC processing unit 110. Data processing unit 120 then inputs the generated MAC frame to frame processing unit 140. Data processing unit 120 also extracts LLC packets from the MAC frame input from frame processing unit 140. Data processing unit 120 then inputs the extracted LLC packets to LLC processing unit 110. A MAC frame containing data is also called a "data frame."
[0042] The management unit 130 controls the establishment of a wireless connection (wireless link) between the sharing AP 10 and the non-AP MLD of the terminal device 30 in the multi-AP connection method. For example, the management unit 130 executes a multi-AP association process in response to a multi-AP association request from the terminal device 30. For example, if the terminal device 30 uses three A-STAs #1 to #3, through the multi-AP association process, each of the A-STAs #1 to #3 establishes a wireless link with A-APs #1 to #3 of the shared AP 20-1, A-APs #4 to #6 of the shared AP 20-2, and A-APs #7 to #9 of the shared AP 20-3. During actual data exchange, the management unit 130 sets one of the established wireless links as enabled as the wireless link for data exchange, and sets the other wireless links as disabled.
[0043] The management unit 130 also includes multi-AP management information 131 and link management information 132. The multi-AP management information 131 includes information regarding the access points used in the multi-AP connection (i.e., the sharing AP 10 and the shared APs 20-1, 20-2, and 20-3) and the terminal device 30. For example, the multi-AP management information 131 is provided for each terminal device 30 that establishes a multi-AP connection. The link management information 132 includes information regarding the status of links established in the multi-AP connection and the R-TWT function. The multi-AP management information 131 and the link management information 132 will be described in detail below.
[0044] 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. Furthermore, 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 depending on 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 a 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 the control frame includes, for example, management information. The management information may include notification information for either the shared AP 20 or the terminal device 30, control information related to control of the operation of either the shared AP 20 or the terminal device 30, and the like.
[0045] The transmitting / receiving unit 150 transmits and receives data, management information, etc. to and from each of the multiple shared APs 20 belonging to the sharing AP 10. In this example, each of the shared APs 20-1, 20-2, and 20-3 is connected to the transmitting / receiving unit 150 by wire or wirelessly.
[0046] When the sharing AP 10 wirelessly communicates with each of the multiple shared APs 20, the transceiver 150 includes one or more wireless signal processors. Each wireless signal processor of the transceiver 150 is configured to transmit and receive wireless signals using a different frequency band or channel. Each wireless signal processor of the transceiver 150 generates a wireless frame by adding a preamble or the like to the MAC frame input from the frame processor 140 and converts the generated wireless frame into a wireless signal. Each wireless signal processor then transmits (radiates) the converted wireless signal to each shared AP 20 via an antenna. Each wireless signal processor of the transceiver 150 also converts a wireless signal received from one of the shared APs 20 via the antenna into a wireless frame. Each wireless signal processor extracts a MAC frame from the converted wireless frame and outputs the extracted MAC frame to the frame processor 140.
[0047] For example, the transceiver 150 is provided with one wireless signal processing unit for each of the multiple shared APs 20 belonging to the sharing AP 10. The frame processing unit 140 outputs data, etc. to be transmitted to the shared AP 20-1 to the wireless signal processing unit associated with the shared AP 20-1, outputs data, etc. to be transmitted to the shared AP 20-2 to the wireless signal processing unit associated with the shared AP 20-2, and outputs data, etc. to be transmitted to the shared AP 20-3 to the wireless signal processing unit associated with the shared AP 20-3. The transceiver 150 may be provided with a wireless signal processing unit assigned to transmitting and receiving data, etc., and with a wireless signal processing unit assigned to transmitting management information.
[0048] When the sharing AP 10 communicates with each of the multiple shared APs 20 via a wired network, the transmitting / receiving unit 150 is connected to each of the multiple shared APs 20 belonging to the sharing AP 10 via a wired network. The transmitting / receiving unit 150 then transmits and receives data, management information, and the like to and from each of the shared APs 20-1 to 20-3 via the wired network. In this case, the transmitting / receiving unit 150 is configured by a network interface for the wired network.
[0049] After the multi-AP connection is established, the frame processing unit 140 assigns the destination of the MAC frame input from the data processing unit 120 to one of the multiple shared APs 20-1, 20-2, and 20-3 belonging to the sharing AP 10. For example, the frame processing unit 140 outputs the MAC frame to a wireless signal processing unit associated with the shared AP 20 to which a valid link is assigned, among the shared APs 20-1, 20-2, and 20-3 belonging to the sharing AP 10. The frame processing unit 140 may determine the wireless signal processing unit to which the MAC frame is to be output based on a traffic identifier (TID) associated with an access category. Furthermore, the frame processing unit 140 can transmit information used to control the R-TWT function to each of the multiple shared APs 20-1, 20-2, and 20-3 belonging to the sharing AP 10 during R-TWT agreement setup, which will be described later.
[0050] 6 is a table illustrating an example of multi-AP management information 131 included in the management unit 130 of the sharing AP 10 included in the communication system 1 according to the embodiment. As illustrated in FIG. 6, the multi-AP management information 131 includes information related to, for example, a shared AP identifier, a TWT agreement capability (TWT AC), an STA identifier, and a link identifier.
[0051] The shared AP identifier information included in the multi-AP management information 131 includes information about the identifier of the AP MLD assigned to the multi-AP connection and the identifier of the A-AP. In this example, A-APs #1 to #3 are associated with AP MLD #1 and assigned to the multi-AP connection. A-APs #4 to #6 are associated with AP MLD #2 and assigned to the multi-AP connection. A-APs #7 to #9 are associated with AP MLD #3 and assigned to the multi-AP connection.
[0052] The TWT agreement capability information included in the multi-AP management information 131 is recorded for each link assigned to the multi-AP connection and includes, for example, information used as a criterion for whether or not an R-TWT SP can be scheduled. The sharing AP 10 can obtain the TWT agreement capability for each link by requesting it from each shared AP 20. The TWT agreement capability may simply be information indicating whether or not an R-TWT SP can be scheduled.
[0053] The link identifier information included in the multi-AP management information 131 includes information about the identifiers of the links established in the multi-AP connection. The sharing AP 10, for example, uses the link identifiers to manage whether the links used in the multi-AP connection are enabled or disabled. In this example, links #1 to #9 are assigned to A-APs #1 to #9, respectively.
[0054] The multi-AP management information may include information on frequency bands, channels, operational parameters, access categories, etc. The frequency band information indicates the frequency bands used by the A-AP and A-STA for wireless links. The channel information indicates the channels used by the A-AP and A-STA for wireless links. The operational parameter information includes, for example, CWmin, CWmax, AIFS (arbitration interframe space), and TXOP (transmission opportunity) Limit. CWmin and CWmax indicate the minimum and maximum values of the contention window, respectively. The contention window is a parameter used to calculate backoff, which is a transmission waiting time for collision avoidance. AIFS is a fixed transmission waiting time set for each access category of traffic. TXOPLimit indicates the upper limit of the channel occupation period TXOP. The access category information is indicated by, for example, "VO (Voice)", "VI (Video)", "BE (Best Effort)", "BK (Background)", and "LL (Low Latency)".
[0055] 7 is a table showing an example of information associated with one A-STA among the link management information 132 included in the management unit 130 of the sharing AP 10 provided in the communication system 1 according to the embodiment. This table is provided for each A-STA used in a multi-AP connection. As shown in FIG. 7, the link management information 132 includes, for each link identifier, information on, for example, the link status, R-TWT function, and TWT agreement group (TWT_AG) link identifier.
[0056] The link status information included in the link management information 132 indicates whether the wireless link is enabled or disabled. In other words, an enabled link status indicates that data exchange is possible using the wirelessly connected A-AP and A-STA. An disabled link status indicates that data exchange is not possible using the wirelessly connected A-AP and A-STA. In this example, the link status is set such that link #1 is enabled and the other links are disabled. In this case, it is assumed that the terminal device 30 is located at least within the communication area of the shared AP 20-1.
[0057] The information on the R-TWT function included in the link management information 132 indicates whether the R-TWT function is enabled or disabled. In this example, the R-TWT function is enabled in links #1, #5, and #9, and the R-TWT function is disabled in other links. In a multi-AP connection, there may be links, such as links #5 and #9, in which the link status is disabled but the R-TWT function is enabled.
[0058] The R-TWT_AG link identifier information included in the link management information 132 is an identifier assigned to a link assigned to a multi-AP TWT agreement group. A multi-AP TWT agreement group is set by an R-TWT agreement setup (described later) and is composed of links for which the R-TWT function is enabled. In this example, R-TWT links #1, #2, and #3 are assigned to links #1, #5, and #9, respectively.
[0059] In addition, when the terminal device 30 moves from the communication area of the shared AP 20-1 to the communication area of the shared AP 20-2 or 20-3, the link #1 may become invalid and the link #5 or the link #9 may become valid. In this case, since the R-TWT function of the link #5 and the link #9 is enabled, the terminal device 30 can quickly start communication based on the R-TWT procedure (i.e., communication using the R-TWT function) even after moving. In other words, in the communication system 1, the sharing AP 10 and the terminal device 30 can perform communication based on the R-TWT procedure by detecting that both the link state and the R-TWT function are enabled.
[0060] The multi-AP management information 131 and the link management information 132 may be integrated. These pieces of information may also be managed using tables in other formats. The management unit 130 may perform allocation (mapping) of traffic transmitted and received between the sharing AP 10 and the terminal device 30 in cooperation with the AP MLDs of the multiple shared APs 20 belonging to the sharing AP 10 and the non-AP MLD of the terminal device 30. For example, the management unit 130 instructs the frame processing unit 140 on the destination of the traffic based on the traffic allocation. Then, the frame processing unit 140 causes the transceiver unit 150 to transmit the traffic to the shared AP 20 based on the instruction from the management unit 130. Specifically, the traffic allocated to the link associated with the shared AP 20-1 is transmitted from the transceiver unit 150 of the sharing AP 10 to the shared AP 20-1 based on the instruction from the management unit 130. The management unit 130 may allocate traffic based on the TID associated with the access category.
[0061] <1-3-2> Functional Configuration of the Shared AP 20 FIG. 8 is a block diagram showing an example of the functional configuration of the shared AP 20 included in the communication system 1 according to the embodiment. As shown in FIG. 8, the shared AP 20 functions as a computer including, for example, a transceiver 210, a management unit 220, a frame processing unit 230, and wireless signal processing units 240-1, 240-2, and 240-3. The management unit 220 and the frame processing unit 230 are functional blocks that perform processing corresponding to the MAC sublayer of the second layer. The wireless signal processing units 240-1 to 240-3 are functional blocks that perform processing corresponding to the MAC sublayer of the second layer and the first layer. When the sharing AP 10 communicates wirelessly with each shared AP 20, the transceiver 210 is a functional block that performs processing corresponding to the first layer. When the sharing AP 10 communicates wired with each shared AP 20, the transceiver 210 is a functional block that performs processing corresponding to the MAC sublayer of the second layer.
[0062] The transceiver 210 transmits and receives data, management information, and the like to and from the sharing AP 10. When the shared AP 20 communicates wirelessly with the sharing AP 10, the transceiver 210 includes a radio signal processing unit. The radio signal processing unit of the transceiver 210 generates a radio frame by adding a preamble and the like to the MAC frame input from the frame processing unit 230. The radio signal processing unit of the transceiver 210 converts the generated radio frame into a radio signal. The radio signal processing unit transmits (radiates) the converted radio signal to the sharing AP 10 via an antenna. The radio signal processing unit of the transceiver 210 also converts the radio signal received from the sharing AP 10 via the antenna into a radio frame. The radio signal processing unit extracts a MAC frame from the converted radio frame and outputs the extracted MAC frame to the frame processing unit 230.
[0063] When the shared AP 20 communicates with the sharing AP 10 via a wired network, the transmitting / receiving unit 210 is connected to the sharing AP 10 via a wired network. The transmitting / receiving unit 210 transmits and receives data, management information, and the like to and from the sharing AP 10 via the wired network. In this case, the transmitting / receiving unit 210 is configured by a network interface for the wired network.
[0064] The management unit 220 controls the establishment of a wireless connection (wireless link) between the sharing AP 10 and the non-AP MLD of the terminal device 30 in the multi-AP connection method. The management unit 220 also manages the state of the wireless link between the A-AP of the shared AP 20 and the A-STA of the terminal device 30 in the multi-AP connection. During actual data exchange, the management unit 220 sets each wireless link to enabled or disabled as a wireless link for data exchange based on an instruction from the management unit 130 of the sharing AP 10. The management unit 220 also includes link management information 221 and a beacon generation unit 222.
[0065] The link management information 221 stores management information related to the status of wireless links used in a multi-AP connection. The link management information 221 also includes, for example, information about the sharing AP 10 to which the local station belongs and information about the A-STA of the terminal device 30 that has established a wireless link with the local station. The link management information 221 may store information included in the multi-AP management information 131 and the link management information 132. The management unit 220 uses the link management information 221 to manage whether wireless links are enabled or disabled.
[0066] The beacon generation unit 222 generates a beacon frame including information about the multi-AP connection and a beacon frame including control parameters for the R-TWT function based on the management information received from the sharing AP. The beacon generation unit 222 notifies the terminal device 30 of the generated beacon frame via the frame processing unit 230 and at least one of the wireless signal processing units 240-1, 240-2, and 240-3. The beacon frame includes, for example, information about the sharing AP 10, information about the shared AP 20 of the own station, and information about the shared AP 20 of the other station included in the multi-AP connection. The beacon frame may include the multi-AP management information 131 and the link management information 132 transferred from the sharing AP 10. The beacon frame may be transmitted by broadcast or multicast.
[0067] Furthermore, management unit 220 allocates traffic to the wireless link established by its own shared AP 20 in accordance with instructions regarding traffic allocation from sharing AP 10. Then, management unit 220 notifies frame processing unit 230 of the output destination of traffic to be transmitted to terminal device 30 based on the traffic allocation. As a result, management unit 220 notifies frame processing unit 230 of information indicating to which of wireless signal processing units 240-1 to 240-3 the traffic to be transmitted to terminal device 30 should be output.
[0068] When a MAC frame is input from the transceiver 210, the frame processing unit 230 outputs the input MAC frame to the management unit 220 or at least one of the radio signal processing units 240-1 to 240-3 depending on the frame type and traffic allocation. Furthermore, when a MAC frame is input from one of the radio signal processing units 240-1 to 240-3, the frame processing unit 230 outputs the input frame to the management unit 220 or the transceiver 210 depending on the frame type. For example, when a data frame is input from one of the radio signal processing units 240-1 to 240-3, the frame processing unit 230 outputs the input frame to the transceiver 210. When a data frame is input from the transceiver 210, the frame processing unit 230 outputs the input frame to at least one of the radio signal processing units 240-1 to 240-3. When a management frame or control frame intended for the own station is input from the transmitting / receiving unit 210, the frame processing unit 230 outputs the input frame to the management unit 220. When a management frame or control frame intended for the terminal device 30 is input from the transmitting / receiving unit 210, the frame processing unit 230 outputs the input frame to at least one of the radio signal processing units 240-1 to 240-3.
[0069] Each of the radio signal processing units 240-1, 240-2, and 240-3 is configured to be able to transmit and receive data, management information, and the like to and from the terminal device 30 via wireless communication. Each radio signal processing unit 240 uses the same frequency band and channel as the wirelessly connected A-STA. Each radio signal processing unit 240 generates a radio frame by adding a preamble, etc. to the MAC frame input from the frame processing unit 230. Each radio signal processing unit 240 then converts the generated radio frame into a radio signal. Each radio signal processing unit 240 then transmits (radiates) the converted radio signal to the terminal device 30 via an antenna. Each radio signal processing unit 240 also converts a radio signal received from the terminal device 30 via the antenna into a radio frame. Each radio signal processing unit 240 extracts a MAC frame from the converted radio frame and outputs the extracted MAC frame to the frame processing unit 230.
[0070] When the sharing AP 10 and the shared AP 20 communicate wirelessly, the transceiver 210 may be integrated with each wireless signal processor 240. In this case, wireless communication between the sharing AP 10 and the shared AP 20 is performed via any one of the wireless signal processors 240-1 to 240-3 or another wireless signal processor 240 not shown.
[0071] In the example shown in FIG. 8, in the case of shared AP 20-1, the transceiver 210, management unit 220, and frame processing unit 230 correspond to AP MLD#1. In the case of shared AP 20-2, the transceiver 210, management unit 220, and frame processing unit 230 correspond to AP MLD#2. In the case of shared AP 20-3, the transceiver 210, management unit 220, and frame processing unit 230 correspond to AP MLD#3. In addition, in the case of shared AP 20-1, the radio signal processing units 240-1, 240-2, and 240-3 correspond to A-AP#1, A-AP#2, and A-AP#3, respectively. In the case of shared AP 20-2, the radio signal processing units 240-1, 240-2, and 240-3 correspond to A-AP#4, A-AP#5, and A-AP#6, respectively. In the case of the shared AP 20-3, the wireless signal processing units 240-1, 240-2, and 240-3 correspond to A-AP#7, A-AP#8, and A-AP#9, respectively.
[0072] <1-3-3> Functional Configuration of the Terminal Device 30 FIG. 9 is a block diagram showing an example of the functional configuration of the terminal device 30 included in the communication system 1 according to the embodiment. The terminal device 30 functions as a computer including 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 radio signal processing units 350-1, 350-2, and 350-3. The application execution unit 300 is a functional block that executes processing corresponding to layer 7. The LLC processing unit 310 is a functional block that executes processing corresponding to the LLC sublayer of layer 2 and layers 3 to 6. The data processing unit 320, the management unit 330, and the frame processing unit 340 are functional blocks that execute processing corresponding to the MAC sublayer of layer 2. The radio signal processing units 350-1 to 350-3 are functional blocks that execute processing corresponding to the MAC sublayer of layer 2 and layer 1.
[0073] The application execution unit 300 executes an application based on data input from the LLC processing unit 310. The application execution unit 300 also inputs data to the LLC processing unit 310. For example, the application execution unit 300 can display application information on the display 35. The application execution unit 300 can also operate based on operations on an input interface.
[0074] The LLC processing unit 310 generates LLC packets by adding DSAP headers, SSAP headers, etc. to the data input from the application execution unit 300. The LLC processing unit 310 then inputs the generated LLC packets to the data processing unit 320. The LLC processing unit 310 also extracts data from the LLC packets input from the data processing unit 320. The LLC processing unit 310 then inputs the extracted data to the application execution unit 300.
[0075] The data processing unit 320 adds a MAC header to the LLC packet input from the LLC processing unit 310 to generate a MAC frame. The data processing unit 320 then inputs the generated MAC frame to the frame processing unit 340. The data processing unit 320 also extracts an LLC packet from the MAC frame input from the frame processing unit 340. The data processing unit 320 then inputs the extracted LLC packet to the LLC processing unit 310. The management unit 330 controls the establishment of a wireless connection (wireless link) between the sharing AP 10 and the non-AP MLD of the terminal device 30 in the multi-AP connection method. The management unit 330 can acquire management information from, for example, a beacon received from the shared AP 20. The management unit 330 also 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 the multi-AP connection method. During actual data exchange, the management unit 330 sets each wireless link as enabled or disabled as a wireless link for data exchange based on an instruction from the management unit 130 of the sharing AP 10. The management unit 330 also includes link management information 331.
[0076] The link management information 331 stores management information related to the status of wireless links used in a multi-AP connection. The link management information 331 also includes, for example, information about the sharing AP 10 to which the local station belongs and information about the A-AP of the shared AP 20 that has established a wireless link with the local station. The link management information 331 may store information included in the multi-AP management information 131 and the link management information 132. The management unit 330 uses the link management information 331 to manage whether wireless links are enabled or disabled.
[0077] When a MAC frame is input from data processing unit 320, frame processing unit 340 outputs the input frame to at least one of radio signal processing units 240-1 to 240-3 in accordance with traffic allocation. Furthermore, when a MAC frame is input from any of radio signal processing units 350-1 to 350-3, frame processing unit 230 outputs the input frame to management unit 330 or data processing unit 320 in accordance with the frame type. For example, when a data frame is input from any of radio signal processing units 350-1 to 350-3, frame processing unit 340 outputs the input frame to data processing unit 320. When a data frame is input from data processing unit 320, frame processing unit 340 outputs the input frame to at least one of radio signal processing units 350-1 to 350-3. When a management frame or control frame intended for the own station is input from any of radio signal processing units 350 - 1 to 350 - 3 , frame processing unit 340 outputs the input frame to management unit 330 .
[0078] Each of the wireless signal processing units 350-1, 350-2, and 350-3 is configured to be able to transmit and receive data, management information, and the like to and from the shared AP 20 via wireless communication. Each wireless signal processing unit 350 uses the same frequency band and channel as the wirelessly connected A-AP. Each wireless signal processing unit 350 generates a wireless frame by adding a preamble, etc. to the MAC frame input from the frame processing unit 340. Each wireless signal processing unit 350 then converts the generated wireless frame into a wireless signal. Each wireless signal processing unit 350 then transmits (radiates) the converted wireless signal to the shared AP 20 via an antenna. Each wireless signal processing unit 350 also converts the wireless signal received from the shared AP 20 via the antenna into a wireless frame. Each wireless signal processing unit 350 extracts a MAC frame from the converted wireless frame and outputs the extracted MAC frame to the frame processing unit 340.
[0079] 9, application execution unit 300, LLC processing unit 310, data processing unit 320, management unit 330, and frame processing unit 340 correspond to non-AP MLD #1. Also, radio signal processing units 350-1, 350-2, and 350-3 correspond to A-STA #1, A-STA #2, and A-STA #3, respectively.
[0080] <2> Operation Next, the operation of the communication system 1 according to the embodiment will be described.
[0081] 10 is a flowchart showing an example of a communication method of the sharing AP 10 included in the communication system according to the embodiment. An example of a series of processes from establishing a multi-AP connection to setting up the R-TWT function will be described below with reference to FIG. 10. The operation of the sharing AP 10 described below is executed by, for example, the management unit 130.
[0082] The sharing AP 10 starts the series of processes shown in FIG. 10 in response to a request from the terminal device 30 received via one of the shared APs 20, for example.
[0083] First, the sharing AP 10 sets up a multi-AP connection with the terminal device 30 (S10). In the process of S10, for example, management frames and the like are exchanged between the management unit 130 of the sharing AP 10 and the non-AP MLD of the terminal device 30, and between the management unit 130 of the sharing AP 10 and the AP MLD of each shared AP 20. In this example, N links #1 to #N are established in the multi-AP connection between the sharing AP 10 and the terminal device 30. When the setup of the multi-link using multiple shared APs 20, i.e., the multi-AP connection, is complete, the sharing AP 10 proceeds to the process of S11. Note that in the setup of the multi-link, the first link established with the terminal device 30 may be used to perform authentication and association processes for the other links constituting the multi-link, or authentication and association processes may be performed using multiple links.
[0084] In the process of S11, the sharing AP 10 selects K links from among the N links #1 to #N and designates them as a multi-AP TWT agreement group. "N" is an integer equal to or greater than 2 and corresponds to the number of links used in the multi-AP connection. That is, in the process of S11, K links from among the multiple wireless links established in the multi-AP connection are designated as a multi-AP TWT agreement group. Also, in the process of S11, the sharing AP 10 performs numbering (1...K) of the target links. "K" is an integer equal to or greater than 2 and corresponds to the number of links for which the R-TWT function is enabled. As a result, R-TWT links #1 to #K are assigned in the multi-AP connection.
[0085] Next, the sharing AP 10 sets up a TWT agreement for the multi-AP TWT agreement group (S12). In the process of S12, a TWT agreement is set up for all links included in the multi-AP TWT agreement group at once. Specifically, in the TWT agreement, a request including identifiers of all of the target links and a response are exchanged. In the process of S12, the links for which the R-TWT function is enabled are determined based on the TWT agreement capability information notified from each shared AP 20. The TWT agreement is set up, for example, via a specific A-AP of the shared AP 20. This specific A-AP corresponds to, for example, the link for which the non-AP MLD has requested TWT agreement setup. Then, the result of the TWT agreement setup is notified to the non-AP MLD of the terminal device 30. The process of S12 may be called "multi-AP TWT agreement."
[0086] Next, the sharing AP 10 sets the start timing of the R-TWT SP (S13). That is, the sharing AP 10 determines the TWT start time. In the process of S13, the TWT period, TWT duration, transmission suppression period, etc. may also be set. The sharing AP 10 may set the TWT start time, TWT duration, and TWT period to match the generation period of low-latency traffic. The sharing AP 10 may acquire the generation period of low-latency traffic using any method. For example, the sharing AP 10 may acquire information on the data generation period set in the application that generates low-latency traffic from the terminal device 30 and use it to set up the R-TWT function. The set start timing of the R-TWT SP is notified to the AP MLD of the shared AP 20 and the non-AP MLD of the terminal device 30.
[0087] Next, the process of "k=1" is executed (S14). "k" is a variable for executing the process described later. The number "1" substituted for k in the process of S14 corresponds to the first number assigned to the identifier of the R-TWT link (i.e., the R-TWT agreement group link identifier).
[0088] Next, the sharing AP 10 checks whether the R-TWT link #k is enabled (S15). In the process of S15, for example, the link management information 132 is referenced to check the link status of the R-TWT link #k.
[0089] In the process of S15, if it is confirmed that the R-TWT link #k is enabled (S15: YES), the sharing AP 10 proceeds to the process of S16.
[0090] In the process of S15, if it is confirmed that the R-TWT link #k is not enabled, that is, disabled (S15: NO), the sharing AP 10 proceeds to the process of S18.
[0091] In the process of S16, the sharing AP 10 checks whether there is UL (uplink) / DL (downlink) traffic in the R-TWT link #k, i.e., whether there is uplink or downlink traffic assigned to the R-TWT link #k.
[0092] In the process of S16, if it is confirmed that UL / DL traffic exists in the R-TWT link #k (S16: YES), the sharing AP 10 proceeds to the process of S17.
[0093] In the process of S16, if it is confirmed that there is no UL / DL traffic in the R-TWT link #k (S16: NO), the sharing AP 10 proceeds to the process of S18.
[0094] In the process of S17, the sharing AP 10 schedules an R-TWT SP in the R-TWT link #k, that is, a TWT SP targeted at the R-TWT link #k is set during the TWT period.
[0095] In the process of S18, the sharing AP 10 does not schedule an R-TWT SP for the R-TWT link #k. That is, a TWT SP targeting the R-TWT link #k is not set during the TWT period. After completing the process of S18, the sharing AP 10 proceeds to the process of S19. Note that the sharing AP 10 may skip the process of S18 and proceed to the process of S19.
[0096] In the process of S19, the sharing AP 10 checks whether "k = K" is satisfied. That is, the sharing AP 10 checks whether the process of S17 or S18 has been executed for all R-TWT links established in the multi-AP connection.
[0097] In the process of S19, if it is confirmed that "k=K" is not satisfied (S19: NO), the sharing AP 10 increments k (S20) and proceeds to the process of S15. As a result, the sharing AP 10 executes a process of whether or not to schedule an R-TWT SP for the next R-TWT link.
[0098] If it is confirmed in the process of S19 that "k=K" is satisfied (S19: YES), the sharing AP 10 ends the series of processes in Fig. 10 (END). After that, the communication system 1 executes communication based on the R-TWT procedure. That is, in the scheduled R-TWT SP, uplink or downlink low-latency traffic is transmitted and received.
[0099] 11 is a sequence diagram showing an example of processing from multi-link setup to the start of R-TWT communication in a communication system 1 according to an embodiment. FIG. 11 shows a processing sequence between the sharing AP 10, AP MLDs #1, #2, and #3 corresponding to the shared APs 20-1, 20-2, and 20-3, respectively, and A-STAs #1, #2, and #3 corresponding to the terminal device 30 and the non-AP MLD #1. Hereinafter, with reference to FIG. 11, an example of information exchange within the communication system 1 regarding the setup of the R-TWT function will be described. Note that communication between each AP MLD and the non-AP MLD #1 is performed via a valid A-STA and A-AP (not shown) pair.
[0100] First, a multi-AP connection is set up by the process of S10. This establishes a multi-AP connection using multiple A-STAs in non-AP MLD #1 and multiple A-APs in each of AP MLDs #1 to #3 belonging to sharing AP 10.
[0101] Next, processing related to the setup of the R-TWT function is executed between the sharing AP 10, AP MLDs #1 to #3, and non-AP MLD #1. Specifically, first, each of the AP MLDs #1 to #3 transmits TWT agreement capability information (TWT AC information) for each link of its own station to the sharing AP 10 (S20). The TWT AC information may be transmitted based on a request from the sharing AP 10, or the AP MLD may transmit the information to the sharing AP 10 voluntarily.
[0102] When the sharing AP 10 collects the TWT AC information of each link, it notifies each AP MLD of information (TWT AC information) on whether the R-TWT function is available on each link among the set up links, which is determined based on the TWT AC information (S21). The information notified to each AP MLD in the process of S21 includes at least information on all target links (all target links) on which the TWT function is available.
[0103] Then, each AP MLD notifies the non-AP MLD #1 of the information on whether the R-TWT is available or not, which is notified from the sharing AP 10, via a beacon (S22). Specifically, each A-STA receives the beacon and transfers the information on whether the R-TWT is available or not, which is included in the beacon, to the non-AP MLD #1.
[0104] Based on the notified information about the TWT agreement capability, the non-AP MLD #1 selects (designates) any of the links set up in the multi-AP connection, and then requests the sharing AP 10 to set up a TWT agreement for the selected (designated) links (S23: TWT agreement request).
[0105] Based on the TWT agreement request, the sharing AP 10 selects the links that will form the TWT agreement and designates a multi-AP TWT agreement group. The sharing AP 10 then performs TWT agreement setup via a specific A-AP of the shared AP 20 and notifies the non-AP MLD (S24: TWT agreement response and TWT agreement group notification). This specific A-AP corresponds to the link for which the non-AP MLD #1 has requested TWT agreement setup, for example. When the processing of S24 is completed, the setup of the multi-AP TWT agreement is completed (S25). In response to the multi-AP TWT agreement setup, the sharing AP 10, each shared AP 20, and the terminal device 30 each update the corresponding link management information as appropriate.
[0106] Then, the sharing AP 10 specifies the timing to start the R-TWT SP and notifies each multi-AP TWT agreement group. Specifically, it notifies each AP MLD of schedule information such as the TWT start time (S26). Each AP MLD configures the R-TWT function based on the notified schedule information. Then, each AP MLD #1 notifies the notified schedule information to the non-AP MLD #1 (S27). Note that in multi-AP R-TWT SP communication, at the specified timing, the R-TWT SP is scheduled for links included in the multi-AP TWT agreement group that are valid and have UL or DL traffic, and communication based on the R-TWT procedure is executed (S28).
[0107] Fig. 12 is a time chart showing an example of R-TWT communication in the communication system 1 according to the embodiment. Fig. 12 shows processing sequences in links #1 to #3 corresponding to the shared AP 20-1, links #4 to #6 corresponding to the shared AP 20-2, and links #7 to #9 corresponding to the shared AP 20-3. Below, an overview of communication using the R-TWT function will be described with reference to Fig. 12.
[0108] In this example, link #3 and link #5 are set to enabled, and the other links are set to disabled. Then, a TWT agreement setup is executed between the sharing AP 10 and the terminal device 30 using link #3. In this example, the links included in the TWT agreement group are link #3, link #5, and link #7. The result of the TWT agreement setup is also applied to each of the TWT agreement group links #5 and #7 via the sharing AP 10. In other words, the result of the TWT agreement setup is also applied to link #7 of the shared AP 20-3 outside the communication area. That is, for the TWT agreement setup, it is sufficient that at least one link in the TWT agreement group is enabled. Thereafter, communication using the R-TWT function is performed in the communication system 1.
[0109] When the TWT cycle starts, each link simultaneously transmits (radiates) a beacon signal to announce the R-TWT SP. The beacon signal may include, for example, management information used in the R-TWT function, such as a TWT start time, a TWT duration, a TWT interval, and a transmission suppression period. Note that such management information used in the R-TWT function is included not only in the beacon signal but also in a multilink probe response during multilink setup (for example, the process included in S10 shown in FIG. 11). Upon receiving the beacon signal, the terminal device 30 acquires the TWT start time, the TWT duration, the TWT interval, and the like, and notifies each A-STA of them.
[0110] As a result, R-TWT SP can be set at the same time for each of link #3 and link #5. On the other hand, although link #7 is included in the TWT agreement group, the setting of R-TWT SP is omitted because the link is invalid. On the link to which R-TWT SP is assigned, frame exchange of low-latency traffic is performed preferentially. When the R-TWT SP ends, frame exchange using valid links is performed by the terminal device 30 and other terminal devices until the next TWT period.
[0111] In the R-TWT SP, the transmission of traffic from other terminal devices may be suppressed or prohibited based on the setting of a transmission suppression period. Furthermore, depending on the presence or absence of traffic from the sharing AP 10 or a buffer status report (BSR) from the terminal device 30, the R-TWT SP for the link may not be set, and the transmission suppression period may not be set. This is because, if no traffic is occurring, the other terminal devices must end their communication by the time the R-TWT SP starts, resulting in inefficient communication.
[0112] <3> Effects of the embodiment According to the communication system 1 of the embodiment described above, it is possible to provide a wireless communication environment capable of efficiently transmitting low-latency traffic. The effects of the embodiment will be described in detail below.
[0113] In a multi-link between one AP MLD (access point) and one non-AP MLD (terminal device), a TWT agreement can be set up in all links of the AP MLD by one pair of A-AP and A-STA executing the TWT agreement. However, such a TWT agreement setup does not assume a case where the R-TWT function is used in each of multiple shared APs 20 in a multi-AP connection environment.
[0114] In contrast, the sharing AP 10 in the communication system 1 according to the embodiment executes the setup of a TWT agreement for a specific or all links of a plurality of shared APs 20 belonging to the sharing AP 10 in response to a TWT request from a terminal device 30 connected to the sharing AP 10 to which the sharing AP 10 belongs. At this time, the sharing AP 10 aggregates TWT agreements between any plurality of A-APs of the plurality of shared APs and A-STAs into a TWT agreement between one A-AP of any shared AP and A-STA. In other words, a TWT agreement in a multi-AP connection is set up across the links of multiple shared APs. In other words, by implementing a TWT agreement using a single link, a TWT agreement can be set up without executing a TWT agreement for each of the multiple shared APs 20.
[0115] As a result, the communication system 1 according to the embodiment can perform a TWT agreement from a valid link of the shared AP 20 even for a link of the shared AP 20 whose current link is invalid, such as a shared AP 20 located outside the communication area. Even when the terminal device 30 changes the shared AP 20 to which it is connected, i.e., when a handover is performed, the terminal device 30 can use the R-TWT function without performing a TWT agreement again.
[0116] Furthermore, the sharing AP 10 schedules an R-TWT SP for a valid multi-AP TWT agreement group between the sharing AP 10 and its subordinate A-STAs that form a multi-AP connection, and notifies each shared AP 20. Then, each shared AP 20 sets an R-TWT SP according to the notified schedule.
[0117] As a result, the communication system 1 according to the embodiment can synchronize the R-TWT SP with the beacon transmission timing of each shared AP 20. As a result, the communication system 1 according to the embodiment can perform coordinated communication among multiple shared APs 20 in a multi-AP connection, thereby suppressing delays and jitters in low-latency traffic. Therefore, the communication system 1 according to the embodiment can provide a wireless communication environment capable of efficiently transmitting low-latency traffic.
[0118] Furthermore, in the communication system 1 according to the embodiment, the scheduling of the R-TWT SP can be omitted depending on the presence or absence of traffic from the sharing AP 10 or a buffer status report (BSR) from the terminal device 30. As a result, in the communication system 1 according to the embodiment, when low-latency traffic is not occurring, it is possible to omit communication restrictions on other terminal devices 30 due to the scheduling of the R-TWT SP, thereby realizing efficient communication.
[0119] <4> Others The conversion process from radio frames to radio signals described in the embodiments includes, for example, convolutional coding, interleaving, subcarrier modulation, inverse fast Fourier transform, OFDM modulation, and frequency conversion. The conversion process from radio signals to radio frames described in the embodiments includes, for example, frequency conversion, OFDM demodulation, fast Fourier transform, subcarrier demodulation, deinterleaving, and Viterbi decoding. In a multi-link, one or more radio links may be assigned to one traffic type. The association between traffic and radio links is set, for example, so that the traffic volume is equal among the multiple radio links constituting the multi-link. Traffic of similar types (priority / non-priority, etc.) may be collected on a specific link constituting the multi-link.
[0120] In the embodiments, the CPU 11 of the sharing AP 10, the CPU 21 of the shared AP 20, and the CPU 31 of the terminal device 30 may each be other circuits. For example, the sharing AP 10, the shared AP 20, and the terminal device 30 may each include an MPU (Micro Processing Unit) instead of a CPU. Each of the processes described in the embodiments may be realized by dedicated hardware. The processes of the sharing AP 10, the shared AP 20, and the terminal device 30 may be a mixture of processes executed by software and processes executed by hardware, or may be only one of them. The CPU may be called a "processor." The wireless communication module may be called a "communication circuit."
[0121] In the embodiments, the flowcharts used to explain the operations are merely examples. The order of the processes of the operations described in the embodiments may be changed to the extent possible, and other processes may be added. For example, the link setup method and R-TWT communication method described in the embodiments are merely examples. A wireless communication standard other than the IEEE 802.11 standard may be used as the wireless communication standard.
[0122] The present invention is not limited to the above-described embodiments, and various modifications can be made in the implementation stage without departing from the spirit of the invention. Furthermore, the embodiments may be implemented in appropriate combinations, in which case the combined effects can be obtained. Furthermore, the above-described embodiments include various inventions, and various inventions can be extracted by combining selected elements from the disclosed elements. For example, if the problem can be solved and the desired effect can be obtained even if some elements are deleted from all elements shown in the embodiments, the configuration from which these elements are deleted can be extracted as an invention.
[0123] DESCRIPTION OF SYMBOLS 1...Communication system 10...Sharing access point 30...Terminal device 20, 20-1, 20-2, 20-3...Shared access point 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, 320...Data processing unit 130, 220, 330...Management unit 131...Multi-AP management information 132, 221, 331...Link management information 140, 230, 340...Frame processing unit 150, 210...Transmission / reception unit 222...Beacon generation unit 240-1 to 240-3, 350-1 to 350-3...Wireless signal processing unit 300...Application execution unit
Claims
1. A sharing access point in a communication system comprising: a shared access point including a first management unit; a shared access point including a second management unit and a first wireless signal processing unit; another shared access point including a third management unit and a second wireless signal processing unit; and a terminal device including a fourth management unit, a third wireless signal processing unit, and a fourth wireless signal processing unit, wherein the first management unit is configured to establish a first wireless link between the first wireless signal processing unit and the third wireless signal processing unit and a second wireless link between the second wireless signal processing unit and the fourth wireless signal processing unit, and to collectively establish a service period during which traffic frame exchange can be preferentially performed for the first wireless link and the second wireless link by transmitting and receiving frames via the first wireless link with the third management unit, and to notify each of the second management unit and the third management unit of the start time of the service period.
2. The sharing access point according to claim 1, wherein the first management unit is configured to cause the third management unit to schedule the service period to the second wireless link when the second wireless link is enabled, and not to schedule the service period to the second wireless link when the second wireless link is disabled.
3. A shared access point in a communication system including: a shared access point including a first management unit; a shared access point including a second management unit and a first wireless signal processing unit; another shared access point including a second wireless signal processing unit; and a terminal device including a third wireless signal processing unit having a first wireless link established with the first wireless signal processing unit, and a fourth wireless signal processing unit having a second wireless link established with the second wireless signal processing unit, wherein the second management unit is configured to set the service period to the first wireless link based on receiving information regarding the start time of the service period from the first management unit, without transmitting or receiving a frame regarding setting a service period in which traffic exchange can be preferentially performed for the first wireless link and the second wireless link via the first wireless link.
4. The shared access point described in claim 3, wherein the second management unit is configured, based on instructions from the first management unit, to schedule the service period to the first wireless link when the first wireless link is valid, and not to schedule the service period to the first wireless link when the first wireless link is invalid.
5. A terminal device in a communication system comprising: a shared access point including a first management unit; a shared access point including a first wireless signal processing unit; another shared access point including a second wireless signal processing unit; and a terminal device including a second management unit, a third wireless signal processing unit having a first wireless link established with the first wireless signal processing unit, and a fourth wireless signal processing unit having a second wireless link established with the second wireless signal processing unit, wherein the second management unit is configured to transmit and receive frames between the first management unit and the first management unit via the first wireless link, thereby collectively establishing a service period during which traffic frame exchange can be preferentially performed for the first wireless link and the second wireless link, and to perform frame exchange using the service period at the same timing for each of the first wireless link and the second wireless link.
6. The terminal device of claim 5, wherein the second management unit is configured to receive a beacon signal at the same timing on each of the first wireless link and the second wireless link after the establishment, and to perform frame exchange utilizing the service period on each of the first wireless link and the second wireless link based on information on the start time of the service period contained in the beacon signal.
Citation Information
Patent Citations
Restricted TWT operations for multi-link devices
US20220303907A1
Enhanced handover for moving wi-fi multi-link devices
US20230147311A1
Methods and apparatuses for coordinated operations in a multiple access point multi-link device set in a wireless local area network
WO2023059812A1
