Wireless terminal device, wireless communication device, and wireless communication method

Abstract

The present technology relates to a wireless terminal device, a wireless communication device, and a wireless communication method with which it is possible to normally perform peer-to-peer communication even when the link operation used for peer-to-peer communication between wireless terminal devices is restricted. A non-AP STA performs peer-to-peer communication with other non-AP MLD via a TDLS direct link on the basis of NSTR information as constraint information transmitted from an AP MLD that pertains to operational restrictions in other non-AP MLD of one or more TDLS direct links used for peer-to-peer communication with other non-AP MLD. The present technology can be applied to, for example, a wireless communication system that is configured from two non-AP MLDs and one AP MLD and in which a TDLS direct link is set between the two non-AP MLDs.

Description

Wireless terminal device, wireless communication device, and wireless communication method

[0001] The present technology relates to a wireless terminal device, a wireless communication device, and a wireless communication method, and in particular to a wireless terminal device, a wireless communication device, and a wireless communication method that enable peer-to-peer communication between wireless terminal devices to be performed normally even when there are constraints on the operation of a link used for the peer-to-peer communication.

[0002] Multi-link operation (MLO), a wireless communication method using multiple links, is being considered as a transmission method that requires high transmission speeds, such as transmission of 8K video and XR (Extended Reality) video. A link is a wireless transmission path used for transmitting data between two communication devices. Each link used in MLO is selected from multiple independent wireless transmission paths divided, for example, in the frequency domain. For example, each link used in MLO is selected from multiple channels included in one of frequency bands such as the 2.4 GHz band, the 5 GHz band, the 6 GHz band, and the 920 MHz band.

[0003] A device that supports MLO is called an MLD (Multi-link Device). An MLD is a logical entity that contains multiple STAs (stations) and has only one SAP (service access point) to a higher layer. Among MLDs, an MLD in which each STA is an AP (Access Point) is called an AP MLD, and an MLD in which each STA is not an AP is called a Non-AP MLD.

[0004] To clarify that each STA included in an MLD is an entity within the MLD, if the STA is an AP, it is referred to as an AP affiliated with AP MLD, and if the STA is not an AP, it is referred to as a Non-AP STA affiliated with Non-AP MLD.

[0005] On the other hand, conventional wireless communication not only allows communication between an AP and a non-AP STA, but also allows direct peer-to-peer communication between non-AP STAs. TDLS (Tunneled Direct Link Setup) is a method for setting up a link for peer-to-peer communication between non-AP STAs. With TDLS, non-AP STAs set up a TDLS direct link via the AP. The non-AP STAs then use the set TDLS direct link to perform peer-to-peer communication.

[0006] Therefore, a method has been devised for setting up a single TDLS direct link between non-AP MLDs (see, for example, Non-Patent Document 1).

[0007] Abhishek Patil, et al., “TDLS handling in MLO,” IEEE 802.11-20 / 1692r2, Dec. 3, 2020

[0008] However, even when there are restrictions on the operation of links such as TDLS direct links used for peer-to-peer communication between wireless terminal devices such as non-AP MLD, no method has been devised to ensure that such peer-to-peer communication is performed normally. The provision of such a method has been requested in the standardization of MLO for the IEEE (Institute of Electrical and Electronics Engineers) 802.11be.

[0009] The present technology has been developed in light of such circumstances, and enables peer-to-peer communication between wireless terminal devices to be carried out normally even when there are restrictions on the operation of the link used for the peer-to-peer communication.

[0010] A wireless terminal device according to a first aspect of the present technology is a wireless terminal device having a wireless communication unit that performs peer-to-peer communication with another wireless terminal device via one or more links, based on constraint information transmitted from the wireless communication device regarding operational constraints in the other wireless terminal device of the links used for peer-to-peer communication with the other wireless terminal device.

[0011] A wireless communication method according to a first aspect of the present technology is a wireless communication method including a wireless terminal device performing peer-to-peer communication with another wireless terminal device via one or more links, the link being transmitted from the wireless communication device, based on constraint information regarding operational constraints in the other wireless terminal device of the links used for the peer-to-peer communication with the other wireless terminal device.

[0012] In a first aspect of the present technology, the peer-to-peer communication with another wireless terminal device is performed via one or more links based on constraint information transmitted from the wireless communication device regarding operational constraints on the other wireless terminal device of the one or more links used for the peer-to-peer communication with the other wireless terminal device.

[0013] A wireless communication device according to a second aspect of the present technology is a wireless communication device that includes a wireless communication unit that transmits constraint information to a first wireless terminal device, of a first wireless terminal device and a second wireless terminal device that are connected via its own wireless communication device and perform peer-to-peer communication with each other, regarding constraints on the operation of the second wireless terminal device for one or more links used for the peer-to-peer communication.

[0014] A wireless communication method according to a second aspect of the present technology is a wireless communication method that includes a wireless communication device transmitting, to a first wireless terminal device of a first wireless terminal device and a second wireless terminal device that are connected via the wireless communication device and perform peer-to-peer communication with each other, constraint information regarding operational constraints in the second wireless terminal device of one or more links used for the peer-to-peer communication.

[0015] In a second aspect of the present technology, constraint information regarding operational constraints on the second wireless terminal device of one or more links used for the peer-to-peer communication is transmitted to the first wireless terminal device of a first wireless terminal device and a second wireless terminal device that are connected via their own wireless communication devices and perform peer-to-peer communication with each other.

[0016] The wireless terminal device according to the first aspect of the present technology and the wireless communication device according to the second aspect can be realized by causing a computer to execute a program.

[0017] In addition, in order to realize the wireless terminal device of the first aspect and the wireless communication device of the second aspect of the present technology, a program to be executed by a computer can be provided by transmitting it via a transmission medium or by recording it on a recording medium.

[0018] 3 is a diagram illustrating AAR performed between AP MLD and Non-AP MLD. FIG. 3 is a diagram illustrating setting up a single TDLS direct link between Non-AP MLDs. FIG. 4 is a diagram illustrating a configuration example of a first embodiment of a wireless communication system to which the present technology is applied. FIG. 5 is a block diagram illustrating a configuration example of the AP MLD of FIG. 3. FIG. 6 is a block diagram illustrating a configuration example of the Non-AP MLD of FIG. 3. FIG. 7 is a flowchart illustrating TDLS direct link setting processing by the wireless communication system of FIG. 3. FIG. 8 is a diagram illustrating an example of the element structure of NSTR information. FIG. 9 is a flowchart illustrating NSTR information reception processing. FIG. 10 is a flowchart illustrating TDLS Setup Request transmission processing. FIG. 11 is a flowchart illustrating TDLS Setup Request transmission processing. FIG. 12 is a flowchart illustrating TDLS Setup Request reception processing. FIG. 13 is a block diagram illustrating a configuration example of a Non-AP MLD in a second embodiment of a wireless communication system to which the present technology is applied. FIG. 14 is a flowchart illustrating TDLS direct link setting processing according to the second embodiment of the wireless communication system. FIG. 15 is a diagram illustrating an example of the element structure of EMLSR information. FIG. 16 is a block diagram illustrating a configuration example of a Non-AP MLD in a third embodiment of a wireless communication system to which the present technology is applied. FIG. 17 is a flowchart illustrating TDLS direct link setting processing according to the third embodiment of the wireless communication system. FIG. 18 is a block diagram illustrating an example of the hardware configuration of a computer. FIG. 19 is a block diagram illustrating a schematic configuration example of a smartphone to which the present technology is applied. 1 is a block diagram showing an example of a schematic configuration of an in-vehicle device to which the present technology is applied;FIG. 2 is a block diagram showing an example of a schematic configuration of a wireless AP to which the present technology is applied;FIG.

[0019] Hereinafter, modes for carrying out the present technology (hereinafter referred to as embodiments) will be described. The description will be made in the following order: 0-1. Description of AAR (AP assisted medium synchronization recovery) 0-2. Description of setting a single TDLS direct link between Non-AP MLDs 1. First embodiment (wireless communication system in which the TDLS direct link is an NSTR (Nonsimultaneous Transmit and Receive) link pair) 2. Second embodiment (wireless communication system in which the TDLS direct link is an EMLSR (Enhanced Multi-link Single Radio) link) 3. Third embodiment (wireless communication system in which the TDLS direct link is an EMLMR (Enhanced Multi-link Multi Radio) link) 4. Computer 5. Application example

[0020] <0-1. Explanation of AAR> FIG. 1 is a diagram for explaining AAR performed between AP MLD and Non-AP MLD.

[0021] AAR is an operation that requests the AP to recover media information, which is included in the operation of an NSTR link pair called NSTR Operation. An NSTR link pair is a pair of links in MLO where, due to reasons such as the operating frequencies of both links being close, transmission on one link causes interference to a level that affects operations such as reception and carrier sense on the other link. Therefore, transmission and reception cannot be performed simultaneously on both links of an NSTR link pair.

[0022] The AP MLD 11 in FIG. 1 includes three APs 21-1 to 21-3. The Non-AP MLD 12 includes three NON-AP STAs 31-1 to 31-3. The AP 21-1 and the NON-AP STA 31-1 are connected by a first link, the AP 21-2 and the NON-AP STA 31-2 are connected by a second link, and the AP 21-3 and the NON-AP STA 31-3 are connected by a third link. The first link and the second link, and the first link and the third link, are each an NSTR link pair. The second link and the third link are an STR link pair that is not an NSTR link pair.

[0023] First, the non-AP STA 31-1 starts transmitting a data frame to the AP 21-1 via the first link. At this time, the non-AP STA 31-1 requests the triggering of data frame transmission via a trigger frame on the second and third links by writing an AAR control field, which is information for controlling AAR, in the A-Control field of this data frame. When the AP 21-1 receives this data frame, it transmits a BA (Block ACK) to the non-AP STA 31-1 via the first link.

[0024] After the NON-AP STA 31-1 transmits the data frame, the NON-AP STAs 31-2 and 31-3 each start counting down the MediumSyncDelay timer to wait until the media information of the link to which they are connected is ascertained.

[0025] The AP 21-2 grasps the media information based on the AAR control field transmitted from the non-AP STA 31-1, and then transmits a trigger frame to the non-AP STA 31-2 via the second link at the timing when it acquires the transmission right, inducing the transmission of a data frame. Similarly, the AP 21-3 transmits a trigger frame to the non-AP STA 31-3 via the third link, inducing the transmission of a data frame. This allows the non-AP STAs 31-2 and 31-3 to finish counting down the MediumSyncDelay timer earlier than when the trigger frame is not used to induce the transmission of a data frame.

[0026] <0-2. Explanation of Setting a Single TDLS Direct Link Between Non-AP MLDs> FIG. 2 is a diagram for explaining setting a single TDLS direct link between Non-AP MLDs.

[0027] The AP MLD 51 in FIG. 2 is connected to two non-AP MLDs 52-1 and 52-2. The AP MLD 51 includes two APs 71-1 and 71-2. The non-AP MLD 52-1 includes two non-AP STAs 81-1 and 81-2, and the non-AP MLD 52-2 includes two non-AP STAs 91-1 and 91-2. The AP 71-1 and the non-AP STAs 81-1 and 91-1 communicate via a first link. The AP 71-2 and the non-AP STAs 81-2 and 91-2 communicate via a second link.

[0028] A single TDLS direct link between the non-AP MLDs 52-1 and 52-2 can be set up via, for example, the first link in the same way as a TDLS between non-AP STAs not included in an MLD. This allows the non-AP STAs 81-1 and 91-1 to perform peer-to-peer communication via the TDLS direct link, as shown in Figure 2.

[0029] However, if a TDLS direct link is further established via a second link in a manner similar to that of a TDLS between NON-AP STAs not included in MLD, it may be difficult to perform normal peer-to-peer communication via the two TDLS direct links.

[0030] For example, if there are restrictions on the MLO because the first link and the second link are an NSTR link pair, one of the Non-AP MLDs 52-1 and 52-2 is unaware of the restrictions on the other and is therefore unable to perform operations such as AAR that correspond to those restrictions. As a result, frame reception failures occur in peer-to-peer communication between the Non-AP MLDs 52-1 and 52-2 via the two TDLS direct links.

[0031] Therefore, in order to perform normal peer-to-peer communication between non-AP MLDs via multiple TDLS direct links, it is necessary to transmit constraint information regarding MLO constraints in one of the non-AP MLDs to the other as communication environment information.

[0032] Therefore, as will be described later, in the first to third embodiments, restriction information is exchanged between Non-AP MLDs.

[0033] 1. First Embodiment Configuration Example of Wireless Communication System FIG. 3 is a diagram showing a configuration example of a first embodiment of a wireless communication system to which the present technology is applied.

[0034] In the wireless communication system 110, the AP MLD 111 is connected to each of the non-AP MLDs 112-1 and 112-2 via the NSTR link pair, links 121 and 122. In the following, when there is no need to particularly distinguish between the non-AP MLDs 112-1 and 112-2, they will be collectively referred to as the AP MLD 112.

[0035] The AP MLD 111 is a wireless communication device equivalent to a base station that supports MLO, and the non-AP MLD 112 is a wireless terminal device that supports MLO.

[0036] The non-AP MLD 112 establishes two TDLS direct links with other non-AP MLDs 112 via links 121 and 122. The non-AP MLD 112 performs peer-to-peer communication with other non-AP MLDs 112 via the two TDLS direct links, and performs NSTR operations, etc. The links 121 and 122 may be two channels selected from the same frequency band, or two channels selected from different frequency bands.

[0037] 3, the number of links connecting the AP MLD 111 and the non-AP MLD 112 is two, but it may be three or more. The number of non-AP MLDs 112 connected to the AP MLD 111 is not limited to two, and may be three or more.

[0038] <Configuration Example of AP MLD> FIG. 4 is a block diagram showing a configuration example of the AP MLD 111 in FIG.

[0039] The AP MLD 111 includes a communication unit 141, a control unit 142, and a storage unit 143. The communication unit 141 is configured using one or more LSIs (Large Scale Integration), and includes two APs 151-1 and 151-2, a common data processing unit 152, a communication control unit 153, and a communication storage unit 154.

[0040] The AP 151-1 is an AP that belongs to the AP MLD 11 and is configured with an antenna 160-1, an amplifier 161-1, a wireless interface 162-1, a signal processor 163-1, and an individual data processor 164-1. The AP 151-1 is connected to the Non-AP MLD 112 via a link 121.

[0041] The AP 151-2 is an AP belonging to the AP MLD 11 and is configured by an antenna 160-2, an amplifier 161-2, a wireless interface 162-2, a signal processor 163-2, and an individual data processor 164-2. The AP 151-2 is connected to the non-AP MLD 112 via a link 122.

[0042] Since APs 151-1 and 151-2 have the same configuration, hereinafter, when there is no need to particularly distinguish between APs 151-1 and 151-2, they will be collectively referred to as AP 151. Similarly, antennas 160-1 and 160-2, amplifiers 161-1 and 161-2, and wireless interface units 162-1 and 162-2 will be collectively referred to as antenna 160, amplifier 161, and wireless interface unit 162, respectively. Similarly, signal processing units 163-1 and 163-2 and individual data processing units 164-1 and 164-2 will be collectively referred to as signal processing unit 163 and individual data processing unit 164, respectively.

[0043] The amplifier 161 has a transmission amplifier that amplifies a transmission signal supplied from the wireless interface unit 162, and a reception amplifier that amplifies a reception signal that is a signal received by the antenna 160. The transmission signal amplified by the transmission amplifier is transmitted from the antenna 160. The reception signal amplified by the reception amplifier is supplied to the wireless interface unit 162. Some of the components of the amplifier 161 may be provided outside the amplifier 161. For example, some of the components of the amplifier 161 can be included in the wireless interface unit 162.

[0044] Radio interface unit 162 has a transmitting radio interface unit and a receiving radio interface unit. The transmitting radio interface unit performs digital-to-analog signal conversion, filtering, up-conversion, and phase control on the symbol stream supplied from signal processing unit 163 to generate a transmission signal. The transmitting radio interface unit supplies the transmission signal to amplifier unit 161. The receiving radio interface unit performs down-conversion, filtering, and analog-to-digital signal conversion on the received signal supplied from amplifier unit 161 to generate a symbol stream. The receiving radio interface unit supplies the symbol stream to signal processing unit 163.

[0045] The signal processing unit 163 includes a transmission signal processing unit and a reception signal processing unit. The transmission signal processing unit performs encoding, interleaving, modulation, etc. on the MAC (Media Access Control) frame supplied from the individual data processing unit 164, adds a physical header, and generates a symbol stream. The signal processing unit 163 supplies the symbol stream to the transmission radio interface of the radio interface unit 162. The reception signal processing unit analyzes the physical header of the symbol stream supplied from the reception radio interface unit of the radio interface unit 162, and performs demodulation, deinterleaving, decoding, etc. on the symbol stream to generate a MAC frame. At this time, the signal processing unit 163 estimates complex channel characteristics and performs spatial separation processing as necessary. The signal processing unit 163 supplies the generated MAC frame to the individual data processing unit 164.

[0046] The individual data processing unit 164 performs channel access operations based on carrier sensing. The individual data processing unit 164 performs sequence management of transmission packets, control information, and management information for wireless communication only via the link 121 (122) corresponding to the individual data processing unit 164, which are supplied from the communication control unit 153. The individual data processing unit 164 performs encryption, modulation, etc. on the transmission packets, control information, and management information, adds a MAC header and error detection code, and generates a MAC frame (PSDU (Physical Service Data Unit)). The individual data processing unit 164 performs processing such as concatenating multiple generated MAC frames, and supplies them to the signal processing unit 163. The individual data processing unit 164 supplies to the signal processing unit 163 transmission packets, control information, and management information common to wireless communication via the links 121 and 122, which are supplied from the common data processing unit 152.

[0047] The individual data processing unit 164 performs MAC header disconnection, analysis such as demodulation and decoding, error detection, and retransmission requests on the MAC frames supplied from the signal processing unit 163. The individual data processing unit 164 supplies, as received packets, data packets for wireless communication only via the link 121 (122) from among the data packets obtained as a result of analyzing the MAC frames, to the communication control unit 153. The individual data processing unit 164 supplies, as received packets, data packets common to wireless communication via the links 121 and 122 from among the data packets obtained as a result of analyzing the MAC frames, to the common data processing unit 152.

[0048] The common data processing unit 152 performs sequence management of transmission packets, control information, and management information that are common to wireless communications via links 121 and 122 and are supplied from the communication control unit 153. The common data processing unit 152 performs encryption, modulation, etc. on the transmission packets, control information, and management information, adds a MAC header and error detection code, and generates a MAC frame. The common data processing unit 152 performs processing such as concatenating the generated multiple MAC frames, and supplies them to the individual data processing units 164-1 and 164-2. The common data processing unit 152 supplies the received packets supplied from the individual data processing units 164-1 and 164-2 to the communication control unit 153.

[0049] The communication control unit 153 controls the operation of each unit of the communication unit 141 and the exchange of information between each unit, thereby controlling wireless communication with the non-AP MLD 112 .

[0050] Specifically, the communication control unit 153 supplies data packets supplied from the control unit 142 as transmission packets to the communication storage unit 154 for storage. The communication control unit 153 supplies received packets supplied from the individual data processing unit 164 or the common data processing unit 152 to the communication storage unit 154 for storage. The communication control unit 153 reads out transmission packets specific to each AP 151 from the communication storage unit 154 and sets the transmission packets as transmission packets for wireless communication only via the link 121 (122) corresponding to that AP 151. The communication control unit 153 supplies the transmission packets for wireless communication only via the link 121 (122) to the individual data processing unit 164 of the AP 151 corresponding to that link 121 (122).

[0051] The communication control unit 153 generates control information and management information common to the APs 151 to be notified to the non-AP MLD 112, and supplies the generated information to the common data processing unit 152. The communication control unit 153 generates control information and management information specific to each AP 151 to be notified to the non-AP MLD 112, and supplies the generated information to the individual data processing unit 164 of that AP 151.

[0052] As a result of the above, the communication control unit 153 transmits, for example, NSTR information relating to the NSTR Operation of one of the Non-AP MLDs 112-1 and 112-2 to the other as constraint information.

[0053] The NSTR information includes pair information, which is information about the NSTR link pair, MSD information, which is information about the Medium Synchronization Delay, and AAR information, which is information about the AAR. The pair information includes information indicating that the links 121 and 122 are an NSTR link pair. The MSD information includes information about the length of Medium Synchronization, information about the OFDM (Orthogonal Frequency Division Multiplexing) ED (Energy Detection) threshold during Medium Synchronization, and information about the TXOP (Transmission Opportunity) that can be acquired during Medium Synchronization. The AAR information includes information indicating whether AAR is supported and information about the link that transmits transmission inducement information that induces data transmission in AAR. Note that the NSTR information does not necessarily need to include all of the pair information, MSD information, and AAR information, as long as it includes at least one of them.

[0054] The communication storage unit 154 stores information used by the communication control unit 153. The communication storage unit 154 stores transmission packets supplied from the communication control unit 153. The communication storage unit 154 stores reception packets supplied from the communication control unit 153.

[0055] The control unit 142 controls the entire AP MLD 111. For example, the control unit 142 reads out a received packet from the communication storage unit 154 via the communication control unit 153 and supplies it to the storage unit 143 for storage. The control unit 142 generates a data packet to be transmitted to the non-AP MLD 112 and supplies it to the storage unit 143 for storage. The control unit 142 reads out the data packet and supplies it to the communication control unit 153, thereby causing the data packet to be transmitted as a transmission packet.

[0056] The control unit 142 may perform part of the control by the communication control unit 153 in place of the communication control unit 153. For example, the control unit 142 may directly exchange data packets with the common data processing unit 152 or the individual data processing unit 164. The communication control unit 153 and the control unit 142 may be integrated.

[0057] The storage unit 143 stores information used by the communication unit 141 and the control unit 142. For example, the storage unit 143 stores received packets received by the communication unit 141 and data packets generated by the control unit 142. The storage unit 143 may perform some of the operations of the communication storage unit 154 in place of the communication storage unit 154. The storage unit 143 and the communication storage unit 154 may be integrated. The storage unit 143 may directly exchange data packets with the communication storage unit 154, the common data processing unit 152, and the individual data processing unit 164.

[0058] The number of APs included in the AP MLD 111 can be any number equal to or greater than one. When the AP MLD 111 includes more APs than the number of antennas, some of the APs included in the AP MLD 111 may share the same antenna via a frequency division unit. The number of processing units, each consisting of a signal processing unit 163 and an individual data processing unit 164 connected to the wireless interface unit 162, may be plural. The number of common data processing units 152 may be plural.

[0059] <Configuration Example of Non-AP MLD> FIG. 5 is a block diagram showing a configuration example of the Non-AP MLD 112 in FIG.

[0060] The Non-AP MLD 112 includes a communication unit 241, a control unit 242, and a storage unit 243. The communication unit 241 is configured using one or more LSIs, and includes two NON-AP STAs 251-1 and 251-2, a common data processing unit 252, a communication control unit 253, and a communication storage unit 254.

[0061] The NON-AP STA 251-1 is a NON-AP STA that belongs to the NON-AP MLD 112, and is configured with an antenna 260-1, an amplifier 261-1, a wireless interface 262-1, a signal processor 263-1, and an individual data processor 264-1. The NON-AP STA 251-1 communicates with the AP MLD 111 and other Non-AP MLDs 112 via the link 121.

[0062] The NON-AP STA 251-2 is a NON-AP STA that belongs to the NON-AP MLD 112, and is configured with an antenna 260-2, an amplifier 261-2, a wireless interface 262-2, a signal processor 263-2, and an individual data processor 264-2. The NON-AP STA 251-2 communicates with the AP MLD 111 and other NON-AP MLDs 112 via the link 122.

[0063] Since the NON-AP STAs 251-1 and 251-2 have the same configuration, hereinafter, when there is no need to particularly distinguish between the NON-AP STAs 251-1 and 251-2, they will be collectively referred to as the NON-AP STA 251. Similarly, the antennas 260-1 and 260-2, the amplifiers 261-1 and 261-2, and the wireless interface units 262-1 and 262-2 will be collectively referred to as the antenna 260, the amplifier 261, and the wireless interface unit 262, respectively. Similarly, the signal processing units 263-1 and 263-2 and the individual data processing units 264-1 and 264-2 will be collectively referred to as the signal processing unit 263 and the individual data processing unit 264, respectively.

[0064] The processing of the amplifier 261, the wireless interface unit 262, and the signal processor 263 is similar to the processing of the amplifier 161, the wireless interface unit 162, and the signal processor 163 in Fig. 4, respectively, and therefore description thereof will be omitted. The processing of the individual data processor 264 and the common data processor 252 is similar to the processing of the individual data processor 164 and the common data processor 152, respectively, and therefore description thereof will be omitted.

[0065] Similar to the communication control unit 153, the communication control unit 253 controls the operation of each unit of the communication unit 241 and the exchange of information between each unit, thereby controlling wireless communication with the AP MLD 111 and other Non-AP MLDs 112. As a result, the communication control unit 253 transmits, for example, NSTR information of its own Non-AP MLD 112 to the AP MLD 111, and performs NSTR operations with the other Non-AP MLDs 112 based on the NSTR information of the other Non-AP MLDs 112 transmitted from the AP MLD 111.

[0066] The processing of the communication storage unit 254 is similar to the processing of the communication storage unit 154, and therefore a description thereof will be omitted.

[0067] The control unit 242 controls the entire Non-AP MLD 112. For example, the control unit 242 reads out received packets from the communication storage unit 254 via the communication control unit 253 and supplies them to the storage unit 243 for storage. The control unit 242 generates data packets to be transmitted to the AP MLD 111 or other Non-AP MLDs 112 and supplies them to the storage unit 243 for storage. The control unit 242 reads out the data packets and supplies them to the communication control unit 253, causing the data packets to be transmitted as transmission packets.

[0068] Similar to the control unit 142, the control unit 242 may perform part of the control by the communication control unit 253 instead of the communication control unit 253. The communication control unit 253 and the control unit 242 may be integrated. The processing of the storage unit 243 is the same as the processing of the storage unit 143, and therefore a description thereof will be omitted.

[0069] The number of NON-AP STAs included in the Non-AP MLD 112 can be any number equal to or greater than one. If the Non-AP MLD 112 includes more NON-AP STAs than the number of antennas, some of the NON-AP STAs included in the Non-AP MLD 112 may share the same antenna via a frequency division unit. There may be more than one processing unit, each consisting of a signal processing unit 263 and an individual data processing unit 264, connected to the wireless interface unit 262. There may be more than one common data processing unit 252.

[0070] <Description of TDLS Direct Link Setting Process> FIG. 6 is a flowchart illustrating TDLS direct link setting process by the wireless communication system 110 of FIG.

[0071] 6, the non-AP STA 251-2 of the non-AP MLD 112-2 transmits a TDLS setup request to the AP MLD 111 via the link 122. This TDLS setup request is information requesting the setting of a TDLS direct link with the non-AP MLD 112-1 via the links 121 and 122.

[0072] In step S21, the AP 151-2 of the AP MLD 111 receives the TDLS setup request transmitted by the process of step S11. Then, the communication control unit 153 adds the NSTR information of the Non-AP MLD 112-2 to this TDLS setup request.

[0073] In step S22, the AP 152-2 (wireless communication unit) transmits a TDLS Setup request to which the NSTR information of the Non-AP MLD 112-2 has been added, to the Non-AP MLD 112-1 via the link 122.

[0074] In step S31, the non-AP STA 251-2 of the non-AP MLD 112-1 receives the TDLS Setup request to which the NSTR information of the non-AP MLD 112-2 has been added, which has been transmitted by the processing of step S22. In step S32, in response to the TDLS Setup request received by the processing of step S31, the non-AP STA 252-2 of the non-AP MLD 112-1 transmits a TDLS setup response, which is information responding to the TDLS Setup request, to the AP MLD 111 via the link 122.

[0075] In step S23, the AP 151-2 receives the TDLS setup response transmitted by the processing in step S32. The AP 151-2 adds the NSTR information of the non-AP MLD 112-1 to this TDLS setup response. In step S24, the AP 151-2 transmits the TDLS setup response, to which the NSTR information of the non-AP MLD 112-1 has been added, to the non-AP MLD 112-2 via the link 122.

[0076] In step S12, the non-AP STA 251-2 of the non-AP MLD 112-2 receives the TDLS setup response to which the NSTR information of the non-AP MLD 112-1 has been added, which has been transmitted by the processing of step S24. In step S13, the non-AP STA 251-2 of the non-AP MLD 112-2 transmits a TDLS setup confirm to the AP MLD 111 via the link 122.

[0077] In step S25, the AP 151-2 receives the TDLS setup confirm sent by the process in step S13. In step S26, the AP 151-2 sends this TDLS setup confirm to the non-AP MLD 112-1 via the link 122.

[0078] In step S33, the non-AP STA 251-2 of the non-AP MLD 112-1 receives the TDLS setup confirm sent by the processing in step S26. This completes the TDLS direct link setup processing. At this point, the non-AP MLDs 112 each have each other's NSTR information. Therefore, after the TDLS direct link setup processing is completed, the non-AP MLDs 112 can perform AAR via the TDLS direct link based on the NSTR information of the other non-AP MLD 112, as follows:

[0079] Specifically, in step S41, the non-AP STA 251-1 (wireless communication unit) of the non-AP MLD 112-2 directly transmits a data frame (including a PPDU (PLCP Protocol Data Unit)) to the non-AP STA 112-1 based on the NSTR information of the non-AP MLD 112-1. The AAR control field is written in the A-Control field of this data frame. The direct transmission in step S41 is performed via the TDLS direct link set in the link 121. The non-AP STA 251-2 of the non-AP MLD 112-2 starts counting down the MediumSyncDelay timer.

[0080] In step S51, the non-AP STA 251-1 of the non-AP MLD 112-1 receives the data frame transmitted by the processing of step S41. In step S52, the non-AP STA 251-1 of the non-AP MLD 112-1 transmits a BA directly to the non-AP MLD 112-2 via the TDLS direct link set in the link 121.

[0081] In step S42, the non-AP STA 251-1 of the non-AP MLD 112-2 receives the BA transmitted by the process of step S52.

[0082] In step S34, the Non-AP STA 251-2 (wireless communication unit) of the Non-AP MLD 112-1 directly transmits a CTS (Clear to Send) frame (including a PPDU) to the Non-AP MLD 112-2 based on the NSTR information and AAR control field of the Non-AP MLD 112-2. As a result, the Non-AP STA 251-2 of the Non-AP MLD 112-1 induces the transmission of a data frame from the Non-AP STA 251-2 of the Non-AP MLD 112-2. In other words, during peer-to-peer communication between the Non-AP MLDs 112, the Non-AP MLD 112 transmits a trigger frame instead of the AP MLD 111 that induces the transmission of a data frame from the other Non-AP MLDs 112.

[0083] From the above, it can be said that the CTS frame transmitted in step S34 is transmission inducement information that induces the transmission of a data frame from the non-AP STA 251-2 of the non-AP MLD 112-2. Note that the transmission inducement information does not have to be a CTS frame, and may be an RTS (Request to Send) frame, a data frame, a QoS (Quality of Service) Null frame, a trigger frame, or the like. The direct transmission in step S41 is performed via the TDLS direct link set in the link 122.

[0084] In step S14, the non-AP STA 251-2 of the non-AP MLD 112-2 receives the CTS frame transmitted by the processing of step S34. In step S15, the non-AP STA 251-2 of the non-AP MLD 112-2 transmits a data frame directly to the non-AP MLD 112-1 via the TDLS direct link set up in the link 122 in response to this CTS frame.

[0085] In step S35, the non-AP STA 251-2 of the non-AP MLD 112-1 receives the data frame transmitted by the process of step S15.

[0086] The AP 111 may add the NSTR information of only one of the Non-AP MLDs 112-1 and 112-2.

[0087] <Example of Element Structure of NSTR Information> FIG. 7 is a diagram showing an example of the element structure of NSTR information.

[0088] As shown in FIG. 7, an element of NSTR information is composed of fields of Element ID, Length, Element ID Extension Multi-link Control, Common Info, and Link Info.

[0089] The Element ID and Element ID Extension fields contain information indicating the identifier of this element. The Length field contains information indicating the length of this element. The Multi-link Control field contains information indicating the information contained in this element. Specifically, the Multi-link Control field is composed of the Type, Reserved, and Presence Bitmap fields.

[0090] The Type field describes information indicating that the type of this element is the type of element in which information related to TDLS in the MLO, such as constraint information, is described. The Reserved field is a reserved field that is left open so that it can be used in successor standards, etc. The Presence Bitmap field describes information indicating NSTR information as the information to be described in this element.

[0091] The Common Info field contains information common to the MLD, specifically, the Common Info field is composed of fields for Common Info Length, AP MLD MAC Address, Medium Synchronization Delay Information, and MLD Capabilities and Operations.

[0092] The Common Info Length field contains information indicating the length of this Common Info field. The AP MLD MAC Address field contains information indicating the MAC address of the AP MLD 111 that is transmitting this element. The Medium Synchronization Delay Information field contains MSD information from the NSTR information. The MLD Capabilities and Operations field contains AAR information from the NSTR information.

[0093] The Link Info field describes individual information about the links 121 and 122. Specifically, the Link Info field includes an NSTR Indication Bitmap field, etc. The NSTR Indication Bitmap field describes pair information from the NSTR information.

[0094] The MSD information, AAR information, and pair information may be written in fields other than the fields described with reference to FIG.

[0095] <Explanation of NSTR Information Reception Processing> FIG. 8 is a flowchart illustrating the NSTR information reception processing performed by the AP MLD 111 before the TDLS direct link setting processing of FIG.

[0096] 8, the AP 151 of the AP MLD 111 receives (a data packet of) the NSTR information of the Non-AP MLD 112 itself, transmitted from the Non-AP MLD 112. In step S112, the communication control unit 153 supplies the NSTR information received by the processing of step S111 to the communication storage unit 154 for storage. Then, the NSTR information reception processing ends.

[0097] 9 is a flowchart illustrating the TDLS Setup Request transmission process performed by the AP MLD 111. This TDLS Setup Request transmission process corresponds to the processes in steps S21 and S22 in FIG. 6, and is started when a TDLS Setup Request is transmitted from the non-AP MLD 112.

[0098] In step S131 of FIG. 9, the AP 151 of the AP MLD 111 receives (a data packet of) a TDLS Setup Request sent from the Non-AP MLD 112 and addressed to another Non-AP MLD 112.

[0099] In step S132, the communication control unit 153 determines whether the links 121 and 122 for which the TDLS direct link is to be set up by the TDLS Setup Request are an NSTR link pair. Specifically, the communication control unit 153 reads the NSTR information of the Non-AP MLD 112 that is the sender of the TDLS Setup Request, which is stored in the communication storage unit 154 by the processing of step S112 in FIG. 8. The communication control unit 153 determines whether the pair of links 121 and 122 for which the TDLS direct link is to be set up is an NSTR link pair based on the pair information included in this NSTR information. Note that information indicating the links 121 and 122 for which the TDLS direct link is to be set up is included in the TDLS Setup Request received by the processing of step S131.

[0100] If it is determined in step S132 that the links 121 and 122 are an NSTR link pair, the process proceeds to step S133. In step S133, the communication control unit 153 adds the NSTR information of the sender of the TDLS Setup Request received in the process of step S131 to the TDLS Setup Request, and supplies the TDLS Setup Request to the AP 151.

[0101] In step S134, the AP 151 transmits the TDLS Setup Request to which the NSTR information has been added in the process of step S133 to the non-AP MLD 112 that is the destination of the TDLS Setup Request, and the TDLS Setup Request transmission process then ends.

[0102] On the other hand, if it is determined in step S132 that the links 121 and 122 are not an NSTR link pair, the communication control unit 153 supplies the TDLS Setup Request received in the processing of step S131 to the AP 151 without adding NSTR information to it. Then, the processing proceeds to step S135. In step S135, the AP 151 transmits a normal TDLS Setup Request, to which no NSTR information has been added, to the Non-AP MLD 112 that is the destination of that TDLS Setup Request. Then, the TDLS Setup Request transmission processing ends.

[0103] The TDLS Setup Response transmission process by the AP MLD 111 differs from the TDLS Setup Request transmission process of FIG. 8 in that the TDLS Setup Request is replaced with a TDLS Setup Response, but is otherwise the same as the TDLS Setup Request transmission process, and therefore will not be described again.

[0104] <Explanation of NSTR Information Transmission Processing> FIG. 10 is a flowchart illustrating the NSTR information transmission processing performed by the NON-AP MLD 112 before the TDLS direct link setting processing of FIG.

[0105] 10, the communication control unit 253 of the NON-AP MLD 112 reads out the NSTR information of the NON-AP MLD 112 itself stored in the communication storage unit 254, and supplies it to the NON-AP STA 251. In step S152, the NON-AP STA 251 transmits the NSTR information of the NON-AP MLD 112 itself read out by the processing of step S151 to the AP MLD 111. Then, the NSTR information transmission processing ends.

[0106] 11 is a flowchart illustrating the TDLS Setup Request transmission process performed by the NON-AP MLD 112. This TDLS Setup Request transmission process corresponds to the processes in steps S11 to S13 in FIG.

[0107] 11, the NON-AP STA 251 of the NON-AP MLD 112 transmits a TDLS Setup Request addressed to another Non-AP MLD 112 to the AP MLD 111. This TDLS Setup Request is received by the processing of step S131 of FIG.

[0108] In step S172, the NON-AP STA 251 determines whether or not a TDLS Setup Response transmitted from the AP MLD 111 in response to the TDLS Setup Request transmitted in step S171 has been received.

[0109] If it is determined in step S172 that the TDLS Setup Response has not yet been received, the NON-AP STA 251 waits until the TDLS Setup Response is received.

[0110] On the other hand, if it is determined in step S172 that a TDLS Setup Response has been received, the NON-AP STA 251 supplies the TDLS Setup Response (a data packet) to the communication control unit 253. Then, the process proceeds to step S173.

[0111] In step S173, the communication control unit 253 determines whether the NSTR information of the source Non-AP MLD 112 is included in the TDLS Setup Response supplied from the NON-AP STA 251. If it is determined in step S173 that the NSTR information is included, the process proceeds to step S174.

[0112] In step S174, the communication control unit 253 supplies the NSTR information included in the TDLS Setup Response to the communication storage unit 254 for storage. This NSTR information is referenced when performing operations such as AAR on the TDLS direct link set in the NSTR link pair after the TDLS direct link has been set. After processing in step S174, the process proceeds to step S175.

[0113] On the other hand, if it is determined in step S173 that NSTR information is not included, the process of step S174 is skipped and the process proceeds to step S175.

[0114] In step S175, the NON-AP STA 251 transmits a TDLS Setup Confirm addressed to the non-AP MLD 112 that transmitted the TDLS Setup Response to the AP MLD 111. Then, the TDLS Setup Request transmission process ends.

[0115] <Description of TDLS Setup Request Reception Processing> Fig. 12 is a flowchart explaining TDLS Setup Request reception processing by the non-AP MLD 112. This TDLS Setup Request reception processing corresponds to the processing of steps S31 to S33 in Fig. 6, and is started when a TDLS Setup Request is transmitted from the AP MLD 111 by the processing of step S134 or S135 in Fig. 9.

[0116] 12, the Non-AP STA 251 of the Non-AP MLD 112 receives (a data packet of) the TDLS Setup Request transmitted from the AP MLD 111, and supplies it to the communication control unit 253. In step S192, the communication control unit 253 determines whether or not the TDLS Setup Request received by the processing of step S191 includes NSTR information of the Non-AP MLD 112 that is the transmission source.

[0117] If it is determined in step S192 that NSTR information is included, the process proceeds to step S193. In step S193, the communication control unit 253 supplies the NSTR information to the communication storage unit 254 for storage. This NSTR information is referenced when performing operations such as AAR on the TDLS direct link set in the NSTR link pair after the TDLS direct link has been set. After step S193 has been processed, the process proceeds to step S194.

[0118] On the other hand, if it is determined in step S192 that NSTR information is not included, the process skips step S193 and proceeds to step S194.

[0119] In step S194, the non-AP STA 251 determines whether or not a TDLS Setup Confirm has been transmitted from the AP MLD 111. If it is determined in step S194 that a TDLS Setup Confirm has not yet been transmitted, the non-AP STA 251 waits until a TDLS Setup Confirm is transmitted.

[0120] On the other hand, if it is determined in step S194 that a TDLS Setup Confirm has been sent, the process proceeds to step S195. In step S195, the non-AP STA 251 receives the TDLS Setup Confirm, and the TDLS Setup Request reception process ends.

[0121] As described above, the Non-AP MLD 112 performs peer-to-peer communication with other Non-AP MLDs 112 via a TDLS direct link based on the NSTR information transmitted from the AP MLD 111. Therefore, the Non-AP MLD 112 can perform NSTR operation, which is intended for communication between an AP MLD and a Non-AP MLD such as ARR, via peer-to-peer communication via a TDLS direct link with other Non-AP MLDs 112. As a result, the Non-AP MLD 112 can normally perform peer-to-peer communication with other Non-AP MLDs 112 via a TDLS direct link, and perform frame exchange, etc.

[0122] <2. Second Embodiment> <Configuration Example of Non-AP MLD> The configuration of a second embodiment of a wireless communication system to which the present technology is applied differs from the wireless communication system 110 in that the links 121 and 122 are EMLSR links and that NSTR information replaces EMLSR information. The configuration of the second embodiment of the wireless communication system also differs from the wireless communication system 110 in the configuration of the Non-AP MLD. Other than these, the configuration is the same as that of the wireless communication system 110. Therefore, the following description will focus on the configurations of the links 121 and 122 and the Non-AP MLD.

[0123] An EMLSR link is a link where EMLSR operation is performed. EMLSR operation is one of the operations specified for Non-AP MLD when the number of RF chains is insufficient due to device constraints in MLO. The RF chain corresponds to the antenna, amplifier, radio interface, signal processing unit, individual data processing unit, etc.

[0124] In EMLSR operation between non-AP MLD and AP MLD, the non-AP MLD has multiple RF chains but can only transmit through one link at a time. Specifically, the non-AP MLD operates one RF chain on each of multiple EMLSR links and waits for a trigger frame from the AP MLD. When the non-AP MLD receives a trigger frame through a certain EMLSR link, it switches the operating link of the RF chain that was operating on another EMLSR link to that EMLSR link, enabling transmission and reception of multiple streams through that EMLSR link. Therefore, when links 121 and 122 are EMLSR links, there are restrictions on MLO.

[0125] Therefore, in the second embodiment, EMLSR information related to EMLSR operation is shared as constraint information between non-AP MLDs that perform peer-to-peer communication via the TDLS direct link established in the links 121 and 122 .

[0126] FIG. 13 is a block diagram showing an example of the configuration of Non-AP MLD in the second embodiment of the wireless communication system to which the present technology is applied.

[0127] In the non-AP MLD 312 in Fig. 13, parts corresponding to those in the non-AP MLD 112 in Fig. 5 are assigned the same reference numerals. Therefore, the description of those parts will be omitted as appropriate, and the description will focus on the parts that are different from the non-AP MLD 112.

[0128] Non-AP MLD 312 differs from non-AP MLD 112 in that it includes a communication unit 341 instead of communication unit 241, and is otherwise configured in the same manner as non-AP MLD 112. Communication unit 341 differs from communication unit 241 in that it includes non-AP STAs 351-1 and 351-2 and a communication control unit 353 instead of non-AP STAs 251-1 and 251-2 and communication control unit 253, and is otherwise configured in the same manner as communication unit 241.

[0129] The NON-AP STA 351-1 differs from the NON-AP STA 251-1 in that it has a simple signal processing unit 362 instead of the signal processing unit 263-1, and in that it newly has switches 361-1 and 363-1. The NON-AP STA 351-1 also differs from the NON-AP STA 251-1 in that it is capable of communicating with the AP MLD 111 and other Non-AP MLDs 112 not only via the corresponding link 121 but also via the link 122. In other respects, it is configured in the same way as the NON-AP STA 251-1.

[0130] The NON-AP STA 351-2 differs from the NON-AP STA 251-2 in that it is newly equipped with switches 361-2 and 363-2, and that it is capable of communicating with the AP MLD 111 and other non-AP MLDs 112 not only via the corresponding link 122 but also via the link 121. Otherwise, it is configured in the same way as the NON-AP STA 251-2.

[0131] In the following description, when there is no need to distinguish between the switches 361-1 and 361-2, they will be collectively referred to as the switch 361. Similarly, the switches 363-1 and 363-2 will be referred to as the switch 363.

[0132] Switch 361 switches the connection destination of wireless interface unit 262 from one of simple signal processing unit 362 and signal processing unit 263-2 to the other. As a result, the symbol stream generated by wireless interface unit 262 is supplied to simple signal processing unit 362 or to signal processing unit 263-2. The symbol stream generated by simple signal processing unit 362 or signal processing unit 263-2 is supplied to wireless interface unit 262-1.

[0133] The simple signal processing unit 362 performs the same processing as the signal processing unit 263, but the frame formats and modulation methods that can be processed by the simple signal processing unit 362 are limited to a portion of the frame formats and modulation methods that can be processed by the signal processing unit 263.

[0134] The switch 363-1 switches the connection destination of the simple signal processing unit 362 from one of the individual data processing units 264-1 and 264-2 to the other. As a result, the MAC frame generated by the simple signal processing unit 362 is supplied to either the individual data processing unit 264-1 or 264-2. The MAC frame generated by the individual data processing unit 264-1 or 264-2 is supplied to the simple signal processing unit 362.

[0135] The switch 363-2 switches the connection destination of the signal processing unit 263-2 from one of the individual data processing units 264-1 and 264-2 to the other. As a result, the MAC frame generated by the signal processing unit 263-2 is supplied to either the individual data processing unit 264-1 or 264-2. The MAC frame generated by the individual data processing unit 264-1 or 264-2 is supplied to the signal processing unit 263-2.

[0136] Similar to the communication control unit 253, the communication control unit 353 controls the operation of each unit of the communication unit 341 and the exchange of information between each unit, thereby controlling wireless communication with the AP MLD 111 and other Non-AP MLDs 312. As a result, the communication control unit 353, for example, transmits EMLSR information of its own Non-AP MLD 312 to the AP MLD 111, and performs EMLSR operations with the other Non-AP MLDs 312 based on the EMLSR information of the other Non-AP MLDs 312 transmitted from the AP MLD 111.

[0137] The EMLSR information includes EMLSR compatibility information indicating whether or not the EMLSR operation is supported, EMLSR link information indicating the EMLSR link that performs the EMLSR operation, EMLSR delay information, etc. Since the non-AP MLD 312 supports the EMLSR operation, the EMLSR compatibility information included in the EMLSR information of the non-AP MLD 312 is information indicating support for the EMLSR operation. Since the links 121 and 122 are EMLSR links, the EMLSR link information is information indicating the links 121 and 122.

[0138] The EMLSR delay information is information about the delay time caused by switching of RF chains during EMLSR operation. Specifically, the EMLSR delay information consists of information about EMLSR padding delay and information about EMLSR transition delay. The EMLSR information also includes EMLSR transition time information about the time for state transition during EMLSR operation (transition timeout), information indicating whether EMLSR is to be performed, information about updating operating parameters during EMLSR operation, etc.

[0139] <Description of TDLS Direct Link Setting Process> FIG. 14 is a flowchart illustrating TDLS direct link setting process according to the second embodiment of the wireless communication system.

[0140] The TDLS direct link setup process consisting of steps S211 to S213, S221 to S226, and S231 to S233 in Fig. 14 is the same as the TDLS direct link setup process in Fig. 6, except that NSTR information is used instead of EMLSR information. Therefore, a description thereof will be omitted. Note that the TDLS setup response sent by the Non-AP STA 351-2 of the Non-AP MLD 312-1 to the AP MLD 111 may include information indicating that the implementation of the EMLSR operation is accepted.

[0141] After the TDLS direct link setting process is completed, the non-AP MLDs 312 perform EMLSR operation via the TDLS direct link based on the EMLSR information of the other non-AP MLD 312 as follows.

[0142] Specifically, in step S234, the non-AP STA 351-2 of the non-AP MLD 312-1 directly transmits an RTS frame (including a PPDU) to the non-AP MLD 312-2 via the TDLS direct link based on the EMLSR information of the non-AP MLD 312-2. This causes the non-AP STA 351-2 of the non-AP MLD 312-1 to switch the active link of the RF chain of the non-AP MLD 312-2 to its own active link, link 122, so that the non-AP MLD 312-2 can receive data frames. In other words, during peer-to-peer communication between the non-AP MLDs 312, instead of transmitting a trigger frame from the AP MLD 111, an RTS frame is transmitted from the non-AP MLD 312-1.

[0143] From the above, it can be said that the RTS frame transmitted in step S234 is switching inducement information that induces switching of the operating link of the RF chain of Non-AP MLD 312-2 to link 122. Note that this switching inducement information may not be an RTS frame, but may be a trigger frame such as a CTS frame, a data frame, a QoS Null frame, an MU (Multi User)-RTS frame, or a BSRP (Buffer Status Report) frame.

[0144] In step S214, non-AP STA 351-2 of non-AP MLD 312-2 receives the RTS frame transmitted by the processing of step S234. Then, based on this RTS frame and the EMLSR information, communication control unit 353 of non-AP MLD 312-2 switches the operating link of non-AP STA 351-1 so that the operating link of both non-AP STAs 351-1 and 351-2 becomes link 122.

[0145] Then, in step S215, non-AP STA 351-2 of non-AP MLD 312-2 transmits a CTS frame directly to non-AP MLD 312-1 via the TDLS direct link set in link 122. As a result, non-AP STA 351-2 of non-AP MLD 312-2 induces the transmission of a data frame from non-AP STA 351-2 of non-AP MLD 312-1. Therefore, the CTS frame transmitted in step S215 can be said to be transmission inducement information that induces the transmission of a data frame from non-AP STA 351-2 of non-AP MLD 312-1. Note that this transmission inducement information may not be a CTS frame, but may be an RTS frame, a data frame, a QoS Null frame, a trigger frame, or the like.

[0146] In step S235, non-AP STA 351-2 of non-AP MLD 312-1 receives the CTS frame transmitted by the processing of step S215. In step S236, in response to this CTS frame, non-AP STA 351-2 of non-AP MLD 312-1 transmits a data frame directly to non-AP MLD 312-2 via the TDLS direct link set up in link 122.

[0147] In step S236, the non-AP STA 351-2 of the non-AP MLD 312-2 receives the data frame transmitted by the process of step S236.

[0148] <Example of Element Structure of EMLSR Information> FIG. 15 is a diagram showing an example of the element structure of EMLSR information.

[0149] As shown in FIG. 15, an element of EMLSR information is composed of fields of Element ID, Length, Element ID Extension Multi-link Control, Common Info, and Link Info.

[0150] The Element ID, Element ID Extension, and Length fields are similar to the Element ID, Element ID Extension, and Length fields in FIG. 7, and therefore a description thereof will be omitted.

[0151] The Multi-link Control field differs from the Multi-link Control field in Fig. 7 in that information indicating EMLSR information is recorded in the Presence Bitmap field as the information recorded in this element. The rest of the Multi-link Control field is configured in the same way as the Multi-link Control field in Fig. 7.

[0152] The Common Info field describes information common within the MLD. Specifically, the Common Info field is composed of the Common Info Length, AP MLD MAC Address, and EML Capabilities fields. The Common Info Length and AP MLD MAC Address fields are similar to the Common Info Length and AP MLD MAC Address fields in Fig. 7, so a description thereof will be omitted. The EML Capabilities field describes EMLSR compatibility information, EMLSR delay information, EMLSR transition time information, and the like, which are part of the EMLSR information.

[0153] The Link Info field describes individual information about the links 121 and 122. Specifically, the Link Info field includes an EML Control field, etc. The EML Control field describes EMLSR link information from the EMLSR information, information indicating whether or not to perform EMLSR, information regarding updates to operating parameters during EMLSR operation, etc.

[0154] Each piece of information in the EMLSR information may be written in a field other than the fields described with reference to FIG.

[0155] The EMLSR information reception processing by the AP MLD 111 is the same as the NSTR information reception processing in Fig. 8 except that NSTR information is replaced with EMLSR information, so a description thereof will be omitted. The TDLS Setup Response transmission processing is the same as the TDLS Setup Request transmission processing in Fig. 9 except that NSTR information and NSTR link pair are replaced with EMLSR information and an EMLSR link, respectively, so a description thereof will be omitted. The TDLS Setup Response transmission processing by the AP MLD 111 is the same as the TDLS Setup Request transmission processing in Fig. 9 except that TDLS Setup Request, NSTR information, and NSTR link pair are replaced with TDLS Setup Response, EMLSR information, and an EMLSR link, respectively, so a description thereof will be omitted.

[0156] The EMLSR information transmission processing and TDLS Setup Request transmission processing by the NON-AP MLD 312 are similar to the NSTR information transmission processing in Fig. 10 and the TDLS Setup Request transmission processing in Fig. 11 except that NSTR information is substituted for EMLSR information, so a description thereof will be omitted. The TDLS Setup Request reception processing by the NON-AP MLD 312 is similar to the TDLS Setup Request reception processing in Fig. 12 except that NSTR information is substituted for EMLSR information, so a description thereof will be omitted.

[0157] As described above, the Non-AP MLD 312 performs peer-to-peer communication with other Non-AP MLDs 312 via a TDLS direct link based on the EMLSR information transmitted from the AP MLD 111. Therefore, the Non-AP MLD 312 can perform EMLSR operation, which is intended for communication between an AP MLD and a Non-AP MLD, via peer-to-peer communication via a TDLS direct link with other Non-AP MLDs 112. As a result, the Non-AP MLD 312 can normally perform peer-to-peer communication with other Non-AP MLDs 312 via a TDLS direct link, and can exchange frames, etc.

[0158] 3. Third Embodiment Example of Non-AP MLD Configuration The configuration of a third embodiment of a wireless communication system to which the present technology is applied differs from the wireless communication system 110 in that the links 121 and 122 are EMLMR links and that NSTR information replaces EMLMR information. The configuration of the third embodiment of the wireless communication system also differs from the wireless communication system 110 in the configuration of the Non-AP MLD. Other than these, the configuration is the same as that of the wireless communication system 110. Therefore, the following description will focus on the configurations of the links 121 and 122 and the Non-AP MLD.

[0159] An EMLMR link is a link where EMLMR operation is performed. EMLMR operation is one of the operations specified for non-AP MLD when the number of RF chains is insufficient due to device constraints in MLO.

[0160] In EMLMR operation between non-AP MLD and AP MLD, the non-AP MLD has multiple RF chains and can transmit and receive data over multiple links. Specifically, the non-AP MLD operates at least one RF chain on each of the multiple EMLMR links and waits for a trigger frame from the AP MLD. When the non-AP MLD receives a data frame over an EMLMR link, it switches the operating link of the RF chain that was operating over another EMLMR link to that EMLMR link, enabling transmission and reception of multiple streams over that EMLMR link. Therefore, when links 121 and 122 are EMLMR links, there are restrictions on MLO.

[0161] Therefore, in the third embodiment, EMLMR information related to EMLMR operation is shared as constraint information between non-AP MLDs that perform peer-to-peer communication via the TDLS direct link set in the links 121 and 122 .

[0162] FIG. 16 is a block diagram showing an example of the configuration of Non-AP MLD in the third embodiment of the wireless communication system to which the present technology is applied.

[0163] In the Non-AP MLD 412 in Fig. 16, parts corresponding to the Non-AP MLD 212 in Fig. 5 and the Non-AP MLD 312 in Fig. 13 are assigned the same reference numerals. Therefore, the description of those parts will be omitted as appropriate, and the description will focus on the parts that are different from the Non-AP MLD 212 and 312.

[0164] The non-AP MLD 412 differs from the non-AP MLD 112 in that it includes a communication unit 441 instead of the communication unit 241, and is otherwise configured in the same manner as the non-AP MLD 112. The communication unit 441 differs from the communication unit 241 in that it includes non-AP STAs 451-1 and 351-2 and a communication control unit 453 instead of the non-AP STAs 251-1 and 252-2 and the communication control unit 353, and is otherwise configured in the same manner as the communication unit 241.

[0165] The NON-AP STA 451-1 differs from the NON-AP STA 251-1 in that it is newly equipped with switches 361-1 and 363-1, and that it is capable of communicating with the AP MLD 111 and other non-AP MLDs 112 not only via the corresponding link 121 but also via the link 122. Otherwise, it is configured in the same way as the NON-AP STA 251-1.

[0166] Similar to the communication control unit 253, the communication control unit 453 controls the operation of each unit of the communication unit 441 and the exchange of information between each unit, thereby controlling wireless communication with the AP MLD 111 and other Non-AP MLDs 412. As a result, the communication control unit 453, for example, transmits EMLMR information of its own Non-AP MLD 412 to the AP MLD 111, and performs EMLMR operations with the other Non-AP MLDs 412 based on the EMLMR information of the other Non-AP MLDs 412 transmitted from the AP MLD 111.

[0167] The EMLMR information includes EMLMR compatibility information indicating whether EMLMR operation is supported, EMLMR link information indicating the EMLMR link that performs the EMLMR operation, and EMLMR delay information related to the delay time due to RF chain switching during the EMLMR operation. Since the non-AP MLD 412 supports the EMLMR operation, the EMLMR compatibility information included in the EMLMR information of the non-AP MLD 412 is information indicating that the EMLMR operation is supported. Since the links 121 and 122 are EMLMR links, the EMLMR link information is information indicating the links 121 and 122.

[0168] The EMLMR information also includes MCS information regarding the MCS (Modulation and Coding Scheme) corresponding to the EMLMR operation, EMLMR transition time information regarding the time of state transition during the EMLMR operation, and information indicating whether or not to implement EMLMR.

[0169] <Description of TDLS Direct Link Setting Process> FIG. 17 is a flowchart illustrating TDLS direct link setting process according to the third embodiment of the wireless communication system.

[0170] The TDLS direct link setup process consisting of steps S311 to S313, S321 to S326, and S331 to S333 in Fig. 17 is the same as the TDLS direct link setup process in Fig. 6, except that NSTR information is substituted for EMLMR information. Therefore, a description thereof will be omitted. Note that the TDLS setup response sent by the Non-AP STA 351-2 of the Non-AP MLD 412-1 to the AP MLD 111 may include information indicating that the implementation of the EMLMR operation is accepted.

[0171] After the TDLS direct link setting process is completed, the non-AP MLDs 412 perform EMLMR operations via the TDLS direct link based on the EMLMR information of the other non-AP MLD 412, as follows.

[0172] Specifically, in step S334, the non-AP STA 351-2 of the non-AP MLD 412-1 directly transmits a QoS Null frame (a PPDU containing the QoS Null frame) to the non-AP MLD 412-2 via the TDLS direct link based on the EMLMR information of the non-AP MLD 412-2. As a result, the non-AP STA 351-2 of the non-AP MLD 412-1 induces switching of the working link of the RF chain of the non-AP MLD 412-2 to its own working link, link 122, so that the non-AP MLD 412-2 can receive data frames. In other words, during peer-to-peer communication between the non-AP MLDs 312, instead of transmitting a trigger frame from the AP MLD 111, a QoS Null frame is transmitted from the non-AP MLD 312-1.

[0173] From the above, it can be said that the QoS Null frame transmitted in step S334 is switching inducement information that induces switching of the operating link of the RF chain of Non-AP MLD 412-2 to link 122. Note that this switching inducement information may not be a QoS Null frame, but may be a trigger frame such as an RTS frame, a CTS frame, a data frame, an MU-RTS frame, or a BSRP (Buffer Status Report) frame.

[0174] In step S314, non-AP STA 351-2 of non-AP MLD 412-2 receives the QoS Null frame transmitted by the processing of step S334. Then, in response to this QoS Null frame, communication control unit 453 of non-AP MLD 412-2 switches the operating link of non-AP STA 451-1 so that the operating link of both non-AP STAs 451-1 and 351-2 becomes link 122.

[0175] Then, in step S315, the non-AP STA 351-2 of the non-AP MLD 412-2 transmits an ACK directly to the non-AP MLD 412-1 via the TDLS direct link set in the link 122. As a result, the non-AP STA 351-2 of the non-AP MLD 412-2 induces the transmission of a data frame from the non-AP STA 351-2 of the non-AP MLD 412-1. Therefore, the ACK transmitted in step S315 can be said to be transmission inducement information that induces the transmission of a data frame from the non-AP STA 351-2 of the non-AP MLD 412-1. Note that this transmission inducement information may be a CTS frame, an RTS frame, a data frame, a QoS Null frame, a trigger frame, or the like, instead of an ACK.

[0176] In step S335, the non-AP STA 351-2 of the non-AP MLD 412-1 receives the ACK transmitted by the processing of step S315. In step S336, in response to this ACK, the non-AP STA 351-2 of the non-AP MLD 412-1 transmits a data frame directly to the non-AP MLD 412-2 via the TDLS direct link set up in the link 122.

[0177] In step S316, the non-AP STA 351-2 of the non-AP MLD 412-2 receives the data frame transmitted by the process of step S336.

[0178] The element structure of the EMLMR information is the same as the element structure of the EMLSR information in Fig. 15. However, the Presence Bitmap field contains information indicating EMLMR information as the information to be contained in this element. The EML Capabilities field contains EMLMR support information, EMLMR delay information, EMLMR transition time information, and the like, which are part of the EMLMR information. The EML Control field contains EMLMR link information, information indicating whether EMLMR is to be implemented, MCS information, and the like, which are part of the EMLMR information. Note that each piece of information in the EMLMR information may be contained in a field other than the above-mentioned fields.

[0179] The EMLMR information reception processing by the AP MLD 111 is the same as the NSTR information reception processing in Fig. 8 except that NSTR information is replaced with EMLMR information, so a description thereof will be omitted. The TDLS Setup Response transmission processing is the same as the TDLS Setup Request transmission processing in Fig. 9 except that NSTR information and NSTR link pair are replaced with EMLMR information and EMLMR, respectively, so a description thereof will be omitted. The TDLS Setup Response transmission processing by the AP MLD 111 is the same as the TDLS Setup Request transmission processing in Fig. 9 except that the TDLS Setup Request, NSTR information, and NSTR link pair are replaced with a TDLS Setup Response, EMLMR information, and EMLMR link, respectively, so a description thereof will be omitted.

[0180] The EMLMR information transmission processing and TDLS Setup Request transmission processing by the NON-AP MLD 412 are similar to the NSTR information transmission processing in Fig. 10 and the TDLS Setup Request transmission processing in Fig. 11 except that NSTR information is substituted for EMLMR information, so a description thereof will be omitted. The TDLS Setup Request reception processing by the NON-AP MLD 412 is similar to the TDLS Setup Request reception processing in Fig. 12 except that NSTR information is substituted for EMLMR information, so a description thereof will be omitted.

[0181] As described above, the Non-AP MLD 412 performs peer-to-peer communication with other Non-AP MLDs 412 via a TDLS direct link based on the EMLMR information transmitted from the AP MLD 111. Therefore, the Non-AP MLD 412 can perform, for example, EMLMR operation intended for communication between an AP MLD and a Non-AP MLD, in peer-to-peer communication via a TDLS direct link with other Non-AP MLDs 112. As a result, the Non-AP MLD 412 can normally perform peer-to-peer communication with other Non-AP MLDs 412 via a TDLS direct link, and can perform frame exchange and the like.

[0182] In the first to third embodiments, the constraint information is described in an element, but it may be described in an A-Control field or in a frame body. The non-AP MLD 112 (312, 412) may transmit its own constraint information by including it in a TDLS Setup Request or a TDLS Setup Response.

[0183] The first to third embodiments may be combined, and the constraint information may be configured to include at least one of NSTR information, EMLSR information, and EMLMR information. In this case, the links 121 and 122 are constrained links that are at least one of an NSTR link pair, an EMLSR link, and an EMLMR link.

[0184] <4. Computer> <Example of Computer Configuration> The above-described series of processes can be executed by hardware or software. When the series of processes is executed by software, the program constituting the software is installed from a program recording medium into a computer incorporated in dedicated hardware, a general-purpose personal computer, or the like.

[0185] FIG. 18 is a block diagram showing an example of the hardware configuration of a computer that executes the above-described series of processes by a program.

[0186] A CPU (Central Processing Unit) 801 , a ROM (Read Only Memory) 802 , and a RAM (Random Access Memory) 803 are interconnected by a bus 804 .

[0187] An input / output interface 805 is further connected to the bus 804. An input unit 806 including a keyboard, a mouse, etc., and an output unit 807 including a display, a speaker, etc., are connected to the input / output interface 805. Information related to the present technology may be output or displayed from the output unit 807. Information related to the present technology may be input from the input unit 806, and confirmation or a response to the information output or displayed on the output unit 807 may be input. In addition, a storage unit 808 including a hard disk or nonvolatile memory, a communication unit 809 including a network interface, etc., and a drive 810 that drives removable media 811 are connected to the input / output interface 805.

[0188] In the computer configured as above, the CPU 801 performs the above-described series of processes by, for example, loading a program stored in the storage unit 808 into the RAM 803 via the input / output interface 805 and the bus 804 and executing the program. For example, the CPU 801 may execute processing programs corresponding to the flowcharts of Figures 6, 8 to 12, 14, and 17 of the present technology.

[0189] The program executed by the CPU 801 is provided, for example, by being recorded on a removable medium 811 or via a wired or wireless transmission medium such as a local area network, the Internet, or digital broadcasting, and installed in the storage unit 808.

[0190] The program executed by the computer may be a program that processes in chronological order according to the order described in this specification, or may be a program that processes in parallel or at the required timing, such as when called.

[0191] 5. Application Examples The present technology can be applied to various products. For example, the non-AP MLD 112 in Fig. 5, the non-AP MLD 312 in Fig. 13, and the non-AP MLD 412 in Fig. 16 may be realized as a mobile terminal such as a smartphone, a tablet PC (Personal Computer), a notebook PC, a portable game terminal, or a digital camera; a fixed terminal such as a television receiver, a projector, a printer, a digital scanner, or a network storage; or an in-vehicle terminal such as a car navigation device or a drive recorder. Furthermore, the non-AP MLD 112, the non-AP MLD 312, and the non-AP MLD 412 may be realized as a machine-to-machine communication (M2M) terminal such as a smart meter, a vending machine, a remote monitoring device, or a point-of-sale (POS) terminal, or an Internet of Things (IoT) terminal. Furthermore, the non-AP MLD 112, the non-AP MLD 312, and the non-AP MLD 412 may be wireless communication modules (for example, integrated circuit modules configured on a single die) mounted on these terminals.

[0192] 4 may be realized as a wireless LAN AP (wireless base station) with or without router functionality. The AP MLD 111 may also be realized as a mobile wireless LAN router. The AP MLD 111 may also be realized as a cellular communication base station or femtocell. Furthermore, the AP MLD 111 may be a wireless communication module (e.g., an integrated circuit module configured on a single die) mounted on these devices.

[0193] <Configuration example of smartphone> Fig. 19 is a block diagram showing a schematic configuration example of a smartphone 900 to which the present technology is applied. Fig. 19 is described as a configuration example of the smartphone 900, but the present technology is not limited to this, and may be a configuration example of the various devices and functions described above.

[0194] The smartphone 900 includes a processor 901, a memory 902, a storage 903, an external connection interface 904, a camera 906, a sensor 907, a microphone 908, an input device 909, and a display device 910. The smartphone 900 also includes a speaker 911, a wireless communication interface 913, an antenna switch 914, an antenna 915, a bus 917, a battery 918, and an auxiliary controller 919. The smartphone 900 may include all or some of the above.

[0195] The processor 901 may be, for example, a CPU or a SoC (System on Chip), and controls the functions of the application layer and other layers of the smartphone 900.

[0196] The memory 902 includes RAM and ROM, and stores programs and data executed by the processor 901 .

[0197] The storage 903 includes a storage medium such as a semiconductor memory or a hard disk.

[0198] The external connection interface 904 is an interface for connecting an external device such as a memory card or a USB (Universal Serial Bus) device to the smartphone 900 .

[0199] The camera 906 has an imaging element such as a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS), and generates a captured image.

[0200] The sensor 907 includes a group of sensors such as a positioning sensor, a gyro sensor, a geomagnetic sensor, and an acceleration sensor.

[0201] The microphone 908 converts the sound input to the smartphone 900 into an audio signal.

[0202] The input device 909 includes, for example, a touch sensor that detects a touch on the screen of the display device 910, a keypad, a keyboard, a button, or a switch, and accepts operations or information input from the user.

[0203] The display device 910 has a screen such as a liquid crystal display (LCD), an organic light emitting diode (OLED) display, or a quantum dot (QD) display, and displays the output image of the smartphone 900.

[0204] The speaker 911 converts the audio signal output from the smartphone 900 into sound.

[0205] The wireless communication interface 913 supports one or more wireless LAN standards such as IEEE802.11a, 11b, 11g, 11ac, 11ad, 11ax, 11ay, 11be, 11bn, and successor standards thereof, and performs wireless communication.

[0206] The wireless communication interface 913 communicates with other devices via a wireless LAN AP in infrastructure mode, and directly with other devices in ad hoc mode or a direct communication mode such as Wi-Fi Direct.

[0207] Unlike ad hoc mode, in Wi-Fi Direct, one of the two terminals acts as an AP, but communication is carried out directly between the terminals.

[0208] The wireless communication interface 913 typically includes a baseband processor, an RF (Radio Frequency) circuit, a power amplifier, etc. The wireless communication interface 913 may be a one-chip module that integrates a memory that stores a communication control program, a processor that executes the program, and related circuits.

[0209] The wireless communication interface 913 may support other types of wireless communication methods, such as a short-range wireless communication method such as Bluetooth, a proximity wireless communication method such as NFC, or a 3GPP (registered trademark) cellular communication method such as 2G, 3G, 4G, 5G, and 6G, in addition to the wireless LAN method. The wireless communication interface 913 may be a one-chip module that supports multiple wireless communication methods, or may be a combination of modules that support some of the wireless communication methods.

[0210] The antenna switch 914 switches the connection destination of the antenna 915 between multiple circuits included in the wireless communication interface 913 (for example, circuits for different wireless communication methods, or transmission system circuits and reception system circuits).

[0211] The antenna 915 has a single or multiple antenna elements (e.g., multiple antenna elements constituting a MIMO (Multiple Input Multiple Output) antenna, or multiple antenna elements constituting an array antenna) and is used for transmitting and receiving radio signals via the wireless communication interface 913.

[0212] 19 , the smartphone 900 may include multiple antennas (for example, a wireless LAN antenna, a proximity wireless communication antenna, and a cellular communication antenna). In this case, the antenna switch 914 may be omitted from the configuration of the smartphone 900.

[0213] The bus 917 connects the processor 901, memory 902, storage 903, external connection interface 904, camera 906, sensor 907, microphone 908, input device 909, display device 910, speaker 911, wireless communication interface 913, and auxiliary controller 919 to each other.

[0214] The battery 918 supplies power to each block of the smartphone 900 shown in FIG. 19 via a power supply line partially indicated by a dashed line in the figure. The auxiliary controller 919 operates the minimum necessary functions of the smartphone 900, for example, in sleep mode. The battery 918 may also be charged via the external connection interface 904. The battery 918 may also have a function that allows reading information regarding the remaining amount of power, the cumulative power-on time, or the cumulative amount of power supply, and the processor 901, the wireless communication interface 913, or the auxiliary controller 919 may control any of the functions of the above-described embodiments based on the information read from the battery 918.

[0215] In the smartphone 900 shown in Fig. 19, for example, the non-AP MLD 112 in Fig. 5, the non-AP MLD 312 in Fig. 13, and the non-AP MLD 412 in Fig. 16 may be implemented in the wireless communication interface 913. For example, processing programs corresponding to the flowcharts in Fig. 6, 10 to 12, 14, and 17 may be executed in the wireless communication interface 913. Furthermore, at least some of these functions may be implemented in the processor 901 or the auxiliary controller 919.

[0216] The smartphone 900 may operate as a wireless AP (software AP) by the processor 901 executing an AP function at the application level. The wireless communication interface 913 may have a wireless AP function. The processor 901 or the wireless communication interface 913 may have a tethering function that uses a wireless LAN system and a cellular communication system, and may transmit payload data received via the cellular communication system via the wireless LAN system, or may transmit payload data received via the wireless LAN system via the cellular communication system. The smartphone 900 may have a tethering function enabled by user input.

[0217] Furthermore, the smartphone 900 may be provided with a biometric authentication unit (fingerprint authentication, palm shape authentication, voice authentication, blood vessel authentication, face authentication, iris authentication, retina authentication). In this case, the wireless communication interface 913 on which the Non-AP MLD 112 in Fig. 5, the Non-AP MLD 312 in Fig. 13, and the Non-AP MLD 412 in Fig. 16 are implemented is configured to receive power from the same battery 918 as the display device 910, the speaker 911, and at least one of the biometric authentication unit.

[0218] Furthermore, in the smartphone 900, information is displayed on at least one of the display device 910 and the speaker 911 based on communication with an external device via the wireless communication interface 913. At this time, information relating to the present technology may be output as information from at least one of the display device 910 and the speaker 911. Furthermore, the input device 909 may be configured to input a confirmation or response to the information output from at least one of the display device 910 and the speaker 911.

[0219] <Configuration example of in-vehicle device> Fig. 20 is a block diagram showing an example of a schematic configuration of an in-vehicle device 920 to which the present technology is applied. Fig. 20 is described as an example of the configuration of the in-vehicle device 920, but the configuration is not limited to this and may be an example of the configuration of the various devices and functions described above.

[0220] The in-vehicle device 920 is configured to include a processor 921, a memory 922, a GNSS (Global Navigation Satellite System) module 924, a sensor 925, a data interface 926, a content player 927, and a storage medium interface 928. The in-vehicle device 920 is also configured to include an input device 929, a display device 930, a speaker 931, a wireless communication interface 933, an antenna switch 934, an antenna 935, and a battery 938. The in-vehicle device 920 may be configured to include all or some of the above.

[0221] The processor 921 may be, for example, a CPU or an SoC, and controls the navigation function and other functions of the in-vehicle device 920. The processor 921 can also control the vehicle's driving system, such as the brake, accelerator, or steering, based on information obtained through communication based on the present technology.

[0222] The memory 922 includes RAM and ROM, and stores programs and data executed by the processor 921 .

[0223] The GNSS module 924 measures the position (e.g., latitude, longitude, and altitude) of the in-vehicle device 920 using GNSS signals received from GNSS satellites.

[0224] The sensor 925 includes a group of sensors such as a gyro sensor, a geomagnetic sensor, a millimeter wave radar, a camera (an imaging element such as a CCD or CMOS), and a barometric pressure sensor.

[0225] The data interface 926 is connected to an in-vehicle network 941 via a terminal (not shown), for example, and acquires data generated on the vehicle side, such as vehicle-side data.

[0226] The content player 927 plays content stored on a storage medium (e.g., a CD or DVD) inserted into the storage medium interface 928 or content received via the wireless communication interface 933 .

[0227] The input device 929 includes, for example, a touch sensor, a button, or a switch that detects a touch on the screen of the display device 930, and accepts operations or information input from the user. For example, the input device 929 may be configured to input a confirmation or response to information output from at least one of the display device 930 and the speaker 931.

[0228] The display device 930 has a screen such as an LCD, OLED display, or QD display, and displays images of navigation functions or content being played, as well as information related to the present technology.

[0229] The speaker 931 outputs the navigation function, the audio of the content being played, or information related to the present technology.

[0230] Note that the navigation function and the function of the content player 927 are optional in the in-vehicle device 920. The navigation function and the content player 927 may be removed from the configuration of the in-vehicle device 920.

[0231] The wireless communication interface 933 supports one or more wireless LAN standards such as IEEE802.11a, 11b, 11g, 11n, 11ac, 11ad, 11ax, 11ay, 11be, 11bn, and successor standards thereof, and performs wireless communication.

[0232] The wireless communication interface 933 communicates with other devices via a wireless LAN AP in infrastructure mode, and directly with other devices in ad hoc mode or a direct communication mode such as Wi-Fi Direct.

[0233] Unlike ad hoc mode, in Wi-Fi Direct, one of the two terminals acts as an AP, but communication is carried out directly between the terminals.

[0234] The wireless communication interface 933 typically includes a baseband processor, an RF circuit, a power amplifier, etc. The wireless communication interface 933 may be a one-chip module that integrates a memory that stores a communication control program, a processor that executes the program, or related circuits.

[0235] The wireless communication interface 933 may support other types of wireless communication methods in addition to the WLAN method, such as a short-range wireless communication method such as Bluetooth, a proximity wireless communication method such as NFC, or a 3GPP cellular communication method such as 2G, 3G, 4G, 5G, and 6G. The wireless communication interface 933 may be a one-chip module that supports multiple wireless communication methods, or may be a combination of modules that support some of the wireless communication methods.

[0236] The antenna switch 934 switches the connection destination of the antenna 935 between multiple circuits included in the wireless communication interface 933 (for example, circuits for different wireless communication methods, or transmission system circuits and reception system circuits).

[0237] The antenna 935 has a single or multiple antenna elements (e.g., multiple antenna elements constituting a MIMO (Multiple Input Multiple Output) antenna, or multiple antenna elements constituting an array antenna) and is used for transmitting and receiving radio signals via the wireless communication interface 933.

[0238] 20, the in-vehicle device 920 may include multiple antennas (for example, an antenna for wireless LAN, an antenna for a close-proximity wireless communication system, and an antenna for a cellular communication system). In this case, the antenna switch 934 may be omitted from the configuration of the in-vehicle device 920.

[0239] The battery 938 supplies power to each block of the in-vehicle device 920 shown in Fig. 20 via a power supply line partially indicated by a dashed line in the figure. The battery 938 may also store power supplied from the vehicle side. Alternatively, the in-vehicle device 920 may not be equipped with a battery and may instead use power supplied from the vehicle side via a voltage regulator or a capacitor.

[0240] In the in-vehicle device 920 shown in Fig. 20 , for example, the Non-AP MLD 112 in Fig. 5 , the Non-AP MLD 312 in Fig. 13 , and the Non-AP MLD 412 in Fig. 16 may be implemented in the wireless communication interface 933. For example, processing programs corresponding to the flowcharts in Fig. 6 , 10 to 12 , 14 , and 17 may be executed in the wireless communication interface 933. Furthermore, at least some of these functions may be implemented in the processor 921.

[0241] The wireless communication interface 933 may also operate as the AP MLD 111 described above and provide a wireless connection to a terminal owned by a user in the vehicle. For example, the wireless communication interface 933 may connect the in-vehicle device 920 to other peripheral devices, and the in-vehicle device 920 may use CarPlay (registered trademark) or Android Auto (registered trademark). Note that the wireless communication interface 933 may also connect the in-vehicle device 920 to other peripheral devices using a short-range wireless communication method, infrastructure mode, or a wireless LAN method using Wi-Fi Direct.

[0242] The in-vehicle device 920 may operate as a wireless AP (software AP) by the processor 921 executing an AP function at the application level. The wireless communication interface 933 may have a wireless AP function. The processor 921 or the wireless communication interface 933 may have a tethering function that uses a wireless LAN system and a cellular communication system, and may transmit payload data received via the cellular communication system via the wireless LAN system, or may transmit payload data received via the wireless LAN system via the cellular communication system. The in-vehicle device 920 may have the tethering function enabled by user input.

[0243] Furthermore, the present technology may be realized as an in-vehicle system (or vehicle) 940 including one or more blocks of the above-described in-vehicle device 920, an in-vehicle network 941, and a vehicle-side module 942. The vehicle-side module 942 may generate vehicle-side data such as vehicle speed information, engine rotation speed information, information about the vehicle-side battery, or malfunction information, and output the generated data to the in-vehicle network 941, and the processor 921 or the wireless communication interface 933 may control any of the functions of the above-described embodiments based on the vehicle-side data acquired via the in-vehicle network 941.

[0244] <Configuration example of wireless AP> Fig. 21 is a block diagram showing an example of a schematic configuration of a wireless AP 950 to which the present technology is applied. Fig. 21 is described as an example of the configuration of the wireless AP 950, but is not limited to this and may be an example of the configuration of the various devices and functions described above.

[0245] The wireless AP 950 includes a controller 951, a memory 952, an input device 954, a display device 955, a network interface 957, a wireless communication interface 963, an antenna switch 964, and an antenna 965. The wireless AP 950 may include all or some of the above.

[0246] The controller 951 may be, for example, a CPU or a DSP (Digital Signal processor) and operates various functions of the IP (Internet Protocol) layer and higher layers of the wireless AP 950 (e.g., access restriction, routing, encryption, firewall, and log management).

[0247] The memory 952 includes RAM and ROM, and stores programs executed by the controller 951 and various control information (for example, a terminal list, a routing table, an encryption key, security settings, and logs).

[0248] The input device 954 includes, for example, buttons and switches, and receives operations from the user. For example, the input device 954 may be configured to input a confirmation or response to information output from the display device 955. Furthermore, the input device 954 may be configured to input, by user operation, switching the wireless function on / off and switching between the router function and the access point function.

[0249] The display device 955 includes an LED lamp or the like and displays the operation status of the wireless AP 950. The display device 955 may also display information related to the present technology.

[0250] The network interface 957 is a wired communication interface for connecting the wireless AP 950 to a wired communication network 958. The network interface 957 may have multiple connection terminals. The network interface 957 may output payload data included in a wireless signal input from the wireless communication interface 963 as a wired signal, or may receive payload data output as a wireless signal from the wireless communication interface 963 as a wired signal. The network interface 957 may input and output wired signals in parallel with or independently of the wireless communication interface 963 inputting and outputting wireless signals. The wired communication network 958 may be a LAN such as Ethernet (registered trademark) or a WAN (Wide Area Network).

[0251] The wireless communication interface 963 supports one or more wireless LAN standards, such as IEEE 802.11a, 11b, 11g, 11n, 11ac, 11ad, 11ax, 11ay, 11be, 11bn, and their successor standards, and provides wireless connection to nearby terminals as an AP. When the wireless AP 950 is installed in a cellular communication base station or a femtocell, the wireless communication interface 963 may support other types of wireless communication systems, such as 3GPP cellular communication systems such as 2G, 3G, 4G, 5G, and 6G, in addition to the wireless LAN system. The wireless communication interface 963 may be a one-chip module that supports multiple wireless communication systems, or a combination of modules that support some of the wireless communication systems.

[0252] The wireless communication interface 963 typically includes a baseband processor, an RF circuit, a power amplifier, and the like.

[0253] The wireless communication interface 963 may be a one-chip module that integrates a memory that stores a communication control program, a processor that executes the program, or related circuits.

[0254] The antenna switch 964 switches the connection destination of the antenna 965 between multiple circuits included in the wireless communication interface 963 (for example, circuits for different wireless communication methods, or transmission system circuits and reception system circuits).

[0255] The antenna 965 has a single or multiple antenna elements (for example, multiple antenna elements constituting a MIMO (Multiple Input Multiple Output) antenna, or multiple antenna elements constituting an array antenna) and is used for transmitting and receiving radio signals via the wireless communication interface 963.

[0256] 21 , for example, the AP MLD 111 in FIG. 4 may be implemented in the wireless communication interface 963. For example, processing programs corresponding to the flowcharts in FIGS. 6 , 8 , 9 , 14 , and 17 may be executed in the wireless communication interface 963. Furthermore, at least some of these functions may be implemented in the controller 951.

[0257] The above-described embodiment shows an example for realizing the present technology, and the matters in the embodiment correspond to the matters specifying the invention in the claims. Similarly, the matters specifying the invention in the claims correspond to the matters in the embodiment of the present technology having the same title. However, the present technology is not limited to the embodiment, and can be realized by applying various modifications to the embodiment without departing from the gist of the present technology.

[0258] Furthermore, part or all of the information processing device described in the above embodiments may be realized as, for example, a semiconductor chip (IC (Integrated Circuit)) having a wireless communication control function. Also, it may be realized as a single semiconductor chip equipped with multiple functions, such as a SoC (System on Chip), or as a combination of multiple semiconductor chips each having a single function, such as a processor. Furthermore, it may be realized as a combination of multiple SoCs, or as a combination of a semiconductor chip with a single function and a SoC. It may also be realized as a semiconductor chip such as an ASIC (Application Specific Integrated Circuit) dedicated to realizing each unit, or as a combination of a general-purpose processor with software or firmware, or as a semiconductor chip such as an FPGA (Field Programmable Gate Array).

[0259] Furthermore, the processing procedures described in the above embodiments may be regarded as a method having a series of these procedures, or as a program for causing this computer to execute these procedures or a recording medium for storing the program.

[0260] Examples of the recording medium that can be used include a CD (Compact Disc), an MD (MiniDisc), a DVD (Digital Versatile Disc), a memory card, and a Blu-ray (registered trademark) Disc.

[0261] In this specification, a system refers to a collection of multiple components (devices, modules (components), etc.), regardless of whether all of the components are contained in the same housing. Therefore, multiple devices housed in separate housings and connected via a network, and a single device housed in a single housing with multiple modules, are both systems.

[0262] Furthermore, the effects described in this specification are merely examples and are not limiting, and other effects may also be present.

[0263] The embodiments of the present technology are not limited to the above-described embodiments, and various modifications are possible without departing from the spirit of the present technology.

[0264] For example, the present technology can be configured as a cloud computing system in which a single function is shared and processed collaboratively by a plurality of devices via a network.

[0265] Furthermore, each step described in the above flowchart can be executed by one device, or can be shared and executed by a plurality of devices.

[0266] Furthermore, when one step includes multiple processes, the multiple processes included in that one step can be executed by one device or can be shared and executed by multiple devices.

[0267] The effects described in this specification are merely examples and are not limiting, and other effects may also be present.

[0268] The present technology can have the following configurations. (1) A wireless terminal device including a wireless communication unit that performs peer-to-peer communication with another wireless terminal device via one or more links used for peer-to-peer communication with the other wireless terminal device, based on constraint information transmitted from the wireless communication device regarding constraints on the operation of the other wireless terminal device for the links. (2) The wireless terminal device described in (1), configured so that the constraint information is included in information requesting establishment of the link or information responding to a request for establishment of the link. (3) The wireless terminal device described in (1) or (2), configured so that the link is an NSTR link, and the constraint information is information regarding the operation of the NSTR link. (4) The wireless terminal device described in (3), configured so that the constraint information includes at least one of information regarding the NSTR link, information regarding AAR, and information regarding Medium Synchronization Delay. (5) The wireless terminal device according to (3) or (4), wherein the wireless communication unit is configured to transmit transmission inducement information inducing data transmission from the other wireless terminal device to the other wireless terminal device via a first link that is at least one of the NSTR links based on the constraint information. (6) The wireless terminal device according to (5), wherein the wireless communication unit is configured to transmit the transmission inducement information also based on information for controlling AAR transmitted from the other wireless terminal device via a second link that is at least one link other than the first link of the NSTR links. (7) The wireless terminal device according to (5) or (6), wherein the wireless communication unit is configured to receive data transmitted from the other wireless terminal device via the first link in response to the transmission inducement information. (8) The wireless terminal device according to (3) or (4), wherein the wireless communication unit is configured to transmit information for controlling AAR to the other wireless terminal device via a first link that is at least one of the NSTR links based on the constraint information.(9) The wireless terminal device according to (8), wherein the wireless communication unit is configured to transmit data to the other wireless terminal device via a second link in response to transmission inducement information for inducing data transmission, the transmission information being transmitted from the other wireless terminal device via a second link that is at least one link other than the first link among the NSTR links. (10) The wireless terminal device according to any of (1) to (4), wherein the link is an EML link consisting of at least one of an EMLSR link and an EMLMR link, and the constraint information is EML information regarding operation of the EML link. (11) The wireless terminal device according to (10), wherein the wireless communication unit is configured to transmit switching inducement information to the other wireless terminal device via the specified link, based on the EML information, for inducing switching of the operating link of the RF chain of the other wireless terminal device to a predetermined link among the links. (12) The wireless terminal device according to (11), wherein the wireless communication unit is configured to receive transmission inducement information that induces data transmission, transmitted from the other wireless terminal device via the predetermined link in response to the switching inducement information. (13) The wireless terminal device according to (12), wherein the wireless communication unit is configured to transmit data to the other wireless terminal device via the predetermined link in response to the transmission inducement information. (14) The wireless terminal device according to (10), wherein the wireless communication unit is configured to transmit transmission inducement information that induces data transmission from the other wireless terminal device to the other wireless terminal device via the predetermined link, based on the EML information and switching inducement information that induces switching of the operational link of the RF chain to the predetermined link, transmitted from the other wireless terminal device via one of the links. (15) The wireless terminal device according to (14), wherein the wireless communication unit is configured to receive data that is transmitted from the other wireless terminal device via the predetermined link in response to the transmission inducement information.(16) The wireless terminal device according to any one of (1) to (15), wherein the link is a TDLS direct link. (17) A wireless communication method including: a wireless terminal device performing peer-to-peer communication with another wireless terminal device via the link, based on constraint information transmitted from the wireless communication device regarding constraints on operation in the other wireless terminal device of one or more links used for the peer-to-peer communication with the other wireless terminal device. (18) A wireless communication device including a wireless communication unit that transmits, to the first wireless terminal device of a first wireless terminal device and a second wireless terminal device that are connected via its own wireless communication device and perform peer-to-peer communication with each other, constraint information regarding constraints on operation in the second wireless terminal device of one or more links used for the peer-to-peer communication. (19) The wireless communication device according to (18), wherein the wireless communication unit includes the constraint information in information requesting link establishment or information responding to the link establishment request transmitted from the second wireless terminal device, and transmits the constraint information to the first wireless terminal device. (20) A wireless communication method including: a wireless communication device transmitting, to a first wireless terminal device of a first wireless terminal device and a second wireless terminal device that are connected via the wireless communication device and perform peer-to-peer communication with each other, constraint information regarding constraints on operation of the second wireless terminal device for one or more links used for the peer-to-peer communication.

[0269] 111 AP MLD, 112-1, 112-2 Non-AP MLD, 151-1, 151-2 AP, 251-1, 251-2 Non-AP STA, 312 Non-AP MLD, 351-1, 351-2 Non-AP STA, 412 Non-AP MLD, 451-1 Non-AP STA

Claims

1. A wireless terminal device having a wireless communication unit that performs peer-to-peer communication with other wireless terminal devices via one or more links based on constraint information transmitted from the wireless communication device regarding operational constraints on the other wireless terminal devices for the links used for peer-to-peer communication with the other wireless terminal devices.

2. The wireless terminal device according to claim 1, wherein the restriction information is configured to be included in information requesting the establishment of the link or information responding to the request for the establishment of the link.

3. The wireless terminal device according to claim 1, wherein the link is an NSTR link, and the constraint information is information relating to the operation of the NSTR link.

4. The wireless terminal device according to claim 3, wherein the restriction information is configured to include at least one of information about the NSTR link, information about AAR, and information about Medium Synchronization Delay.

5. The wireless terminal device according to claim 3, wherein the wireless communication unit is configured to transmit transmission inducement information that induces the other wireless terminal device to transmit data based on the constraint information to the other wireless terminal device via a first link that is at least one of the NSTR links.

6. The wireless terminal device according to claim 5, wherein the wireless communication unit is configured to transmit the transmission inducement information based also on information for controlling AAR transmitted from the other wireless terminal device via a second link, which is at least one link other than the first link among the NSTR links.

7. The wireless terminal device according to claim 5, wherein the wireless communication unit is configured to receive data transmitted from the other wireless terminal device via the first link in response to the transmission inducement information.

8. The wireless terminal device according to claim 3, wherein the wireless communication unit is configured to transmit information for controlling AAR to the other wireless terminal device via a first link that is at least one of the NSTR links based on the constraint information.

9. The wireless terminal device according to claim 8, wherein the wireless communication unit is configured to transmit data to the other wireless terminal device via the second link in response to transmission inducement information that induces the transmission of data, the transmission information being transmitted from the other wireless terminal device via a second link that is at least one link other than the first link among the NSTR links.

10. The wireless terminal device according to claim 1, wherein the link is an EML link consisting of at least one of an EMLSR link and an EMLMR link, and the restriction information is EML information relating to the operation of the EML link.

11. The wireless terminal device according to claim 10, wherein the wireless communication unit is configured to transmit, based on the EML information, switching inducement information to the other wireless terminal device via the specified link, which induces switching of the operational link of the RF chain of the other wireless terminal device to a specified link among the links.

12. The wireless terminal device according to claim 11, wherein the wireless communication unit is configured to receive transmission inducement information that induces the transmission of data, the transmission inducement information being transmitted from the other wireless terminal device via the specified link in response to the switching inducement information.

13. The wireless terminal device according to claim 12, wherein the wireless communication unit is configured to transmit data to the other wireless terminal device via the predetermined link in response to the transmission inducement information.

14. A wireless terminal device as described in claim 10, wherein the wireless communication unit is configured to transmit transmission inducement information to the other wireless terminal device via the specified link, based on the EML information and switching inducement information transmitted from the other wireless terminal device via a specified link among the links, which induces switching of the operating link of the RF chain to the specified link.

15. A wireless terminal device according to claim 14, wherein the wireless communication unit is configured to receive data transmitted from the other wireless terminal device via the specified link in response to the transmission inducement information.

16. The wireless terminal device according to claim 1, wherein the link is configured as a TDLS direct link.

17. A wireless communication method including a wireless terminal device performing peer-to-peer communication with another wireless terminal device via one or more links based on constraint information transmitted from the wireless communication device regarding operational constraints on the other wireless terminal device for the links used for peer-to-peer communication with the other wireless terminal device.

18. A wireless communication device having a wireless communication unit that transmits constraint information to a first wireless terminal device, of which a first wireless terminal device and a second wireless terminal device are connected via its own wireless communication device and perform peer-to-peer communication with each other, regarding constraints on the operation of the second wireless terminal device for one or more links used for the peer-to-peer communication.

19. The wireless communication device according to claim 18, wherein the wireless communication unit includes the constraint information in information sent from the second wireless terminal device requesting the establishment of the link or information responding to the request for the establishment of the link, and transmits the information to the first wireless terminal device.

20. A wireless communication method including a wireless communication device transmitting, to a first wireless terminal device of a first wireless terminal device and a second wireless terminal device that are connected via the wireless communication device and perform peer-to-peer communication with each other, constraint information regarding operational constraints in the second wireless terminal device for one or more links used for the peer-to-peer communication.

Images