WO2022181050A1 - 通信装置及び通信方法 - Google Patents
通信装置及び通信方法 Download PDFInfo
- Publication number
- WO2022181050A1 WO2022181050A1 PCT/JP2021/048889 JP2021048889W WO2022181050A1 WO 2022181050 A1 WO2022181050 A1 WO 2022181050A1 JP 2021048889 W JP2021048889 W JP 2021048889W WO 2022181050 A1 WO2022181050 A1 WO 2022181050A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- link
- transmission
- information
- mld
- communication
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 214
- 238000000034 method Methods 0.000 title claims description 24
- 230000005540 biological transmission Effects 0.000 claims abstract description 469
- 230000008859 change Effects 0.000 claims abstract description 25
- 238000012545 processing Methods 0.000 claims description 84
- 230000000977 initiatory effect Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 20
- 230000001360 synchronised effect Effects 0.000 description 14
- OVGWMUWIRHGGJP-WVDJAODQSA-N (z)-7-[(1s,3r,4r,5s)-3-[(e,3r)-3-hydroxyoct-1-enyl]-6-thiabicyclo[3.1.1]heptan-4-yl]hept-5-enoic acid Chemical compound OC(=O)CCC\C=C/C[C@@H]1[C@@H](/C=C/[C@H](O)CCCCC)C[C@@H]2S[C@H]1C2 OVGWMUWIRHGGJP-WVDJAODQSA-N 0.000 description 10
- 101000988961 Escherichia coli Heat-stable enterotoxin A2 Proteins 0.000 description 10
- 101000752249 Homo sapiens Rho guanine nucleotide exchange factor 3 Proteins 0.000 description 7
- 102100021689 Rho guanine nucleotide exchange factor 3 Human genes 0.000 description 7
- 230000004044 response Effects 0.000 description 7
- 238000007726 management method Methods 0.000 description 4
- 230000003321 amplification Effects 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000003199 nucleic acid amplification method Methods 0.000 description 3
- 238000004904 shortening Methods 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 239000000470 constituent Substances 0.000 description 2
- 230000003111 delayed effect Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 239000013589 supplement Substances 0.000 description 2
- OVGWMUWIRHGGJP-WTODYLRWSA-N (z)-7-[(1r,3s,4s,5r)-3-[(e,3r)-3-hydroxyoct-1-enyl]-6-thiabicyclo[3.1.1]heptan-4-yl]hept-5-enoic acid Chemical compound OC(=O)CCC\C=C/C[C@H]1[C@H](/C=C/[C@H](O)CCCCC)C[C@H]2S[C@@H]1C2 OVGWMUWIRHGGJP-WTODYLRWSA-N 0.000 description 1
- 101100366889 Caenorhabditis elegans sta-2 gene Proteins 0.000 description 1
- 230000002730 additional effect Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 230000006866 deterioration Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/005—Transmission of information for alerting of incoming communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/04—Scheduled access
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/34—Selective release of ongoing connections
Definitions
- this disclosure relates to a communication device and a communication method for wireless communication.
- an access point AP or BS
- a user terminal STA or UE (User Equipment)
- BSS basic service set
- IEEE 802.11 TG (Task Group) be is considering a transmission method with a substantially wider frequency bandwidth by simultaneously using a plurality of frequency bands such as the 5 GHz band and the 6 GHz band.
- An object of the present disclosure is to provide a communication device and communication method that perform wireless communication using a plurality of frequency bands.
- the present disclosure has been made in consideration of the above problems, and a first aspect thereof is a communication device that performs wireless communication using a plurality of links, Notifying information about a change in the transmission period on the first link due to further transmission using the second link during the transmission period using the first link; A communication device.
- the communication device uses the second link to notify the transmission partner of the information. Specifically, whether or not the communication device according to the first aspect attempts acquisition of the transmission right on the second link for each transmission unit constituting a data frame to be transmitted using the first link. While describing information indicating whether or not, at least the information about the transmission period described in the frame transmitted over the first link is changed for each transmission unit constituting the data frame transmitted using the second link. information indicating whether or not the transmission period has been changed, and the information regarding the amount of change in the transmission period on the first link.
- the communication device can perform another transmission using at least one of the first link and the second link within the original transmission period on the first link. .
- the communication device can notify other terminals of the release of the second link within the original transmission period on the first link.
- a second aspect of the present disclosure is a communication method for performing wireless communication using a plurality of links, initiating transmission on the first link; during the period of transmission using the first link, further initiating transmission using a second link; reporting information about a change in transmission period on the first link due to transmission using the second link; is a communication method having
- a third aspect of the present disclosure is a communication device that performs wireless communication using a plurality of links, When data is received over a second link while data is being received over the first link, information about a change in the transmission period over the first link due to transmission over the second link is received. do, A communication device.
- the communication device controls communication operations on the first link based on the information received on the second link.
- the communication device when the communication device according to the second aspect receives information indicating that a communication partner is attempting to acquire a transmission right for the second link on the first link, Receive processing is performed on the second link. Information indicating whether or not at least information relating to the transmission period described in the frame to be transmitted over the first link has been changed, and the information relating to the change in the transmission period in the first link are sent to the second link. to control communication operations on the first link.
- a communication device includes a MAC layer processing unit that performs processing in the MAC layer for each link, and a common data processing unit that performs data processing common to all links. Then, the MAC layer processing unit of the second link notifies the MAC layer processing unit of the first link of the information received on the second link through the common data processing unit.
- a fourth aspect of the present disclosure is a communication method for performing wireless communication using a plurality of links, receiving data on the first link; a step of performing reception processing on the second link when information indicating that the communication partner is attempting to acquire the transmission right on the second link is received on the first link; receiving information about a change in transmission period on the first link due to transmission using the second link when data is received on the second link; controlling communication operations on the first link based on the information received on the second link; is a communication method having
- FIG. 1 is a diagram showing an operation example of transmitting data from a STR AP MLD to a non-STR non-AP MLD.
- FIG. 2 is a diagram showing an operation example in which a STR MLD receives data from another MLD using multiple links.
- FIG. 3 is a diagram showing a configuration example of a wireless network system to which the present disclosure is applied.
- FIG. 4 is a diagram showing a configuration example of the communication device 400.
- FIG. 5 is a diagram showing a communication sequence example (first embodiment) implemented in the wireless network system.
- FIG. 6 is a diagram showing an example of transmission operation in DL Transmission.
- FIG. 7 is a diagram showing a configuration example of a frame notified by Capabilities Exchange.
- FIG. 1 is a diagram showing an operation example of transmitting data from a STR AP MLD to a non-STR non-AP MLD.
- FIG. 2 is a diagram showing an operation example in which a STR MLD receives data from another MLD
- FIG. 8 is a diagram showing a specific operation example of DL Transmission and UL Transmission.
- FIG. 9 is a diagram showing a configuration example of a PPDU.
- FIG. 10 is a diagram showing an operation example within the communication unit 410 in the non-STR non-AP MLD1.
- FIG. 11 is a flow chart showing the operations performed by the common entity in the non-STR non-AP MLD.
- FIG. 12 is a diagram showing a communication sequence example (second embodiment) implemented in the wireless network system.
- FIG. 13 is a diagram showing a specific operation example of DL Transmission and UL Transmission.
- FIG. 14 is a diagram showing a configuration example of a frame notified by Enhanced CF-End.
- FIG. 15 is a diagram showing an operation example in the communication unit 410 in the non-STR non-AP MLD1.
- FIG. 16 is a diagram showing a communication sequence example (third embodiment) implemented in the wireless network system.
- FIG. 17 is a diagram showing a configuration example of a frame notified by Capabilities Exchange.
- FIG. 18 is a diagram showing a configuration example of a frame notified by Capabilities Exchange.
- FIG. 19 is a diagram showing a specific operation example of DL Transmission and UL Transmission.
- FIG. 20 is a diagram showing a configuration example of a PPDU.
- FIG. 21 is a diagram showing an operation example within the communication unit 410 in the STR non-AP MLD1.
- a terminal capable of transmitting using multiple frequency bands, ie, multiple links, is also called an MLD (Multi-Link Device).
- An AP that is MLD is called “AP MLD (Access Point Multi-Link Device)”
- STA that is MLD is called “non-AP MLD”.
- “Simultaneously using multiple links for transmission” does not mean that multiple links are independently controlled and transmitted, but that communication operations between multiple links are separately controlled in order to improve communication quality. point to For example, transmission using a plurality of links at the same time is realized by the following operation.
- a link refers to a radio transmission path through which data can be transmitted between two communication devices, and each link may have a different frequency band.
- STR and NSTR in Multilink Transmission Since some terminals can transmit on multiple links and terminals can only transmit on a single frequency, it is conceivable to acquire the transmission right for each frequency. Therefore, for example, one STA may perform uplink transmission in the 5 GHz band and downlink transmission in the 6 GHz band at the same time, or may perform only uplink transmission or only downlink transmission on both links. can be considered. That is, using a plurality of links, performing transmission and reception simultaneously for each link (STR: Simultaneous Transmit and Receive), or performing either transmission or reception between a plurality of links (NSTR: non-STR) is assumed.
- STR Simultaneous Transmit and Receive
- Non-Patent Document 1 When a non-AP MLD implements STR, its own transmission signal leaks into the signal it receives, causing a problem that self-interference increases and communication quality deteriorates (see Non-Patent Document 1 thing). This problem is caused, for example, by:
- a non-AP MLD that causes the above problem is defined as a terminal that does not implement STR as "non-STR non-AP MLD" or "STA is NSTR limited”. However, since it depends not only on the profile of the terminal but also on the links that are used at the same time, the same terminal is controlled to operate as non-STR MLD on a specific link pair and as STR MLD on another link pair. may occur.
- a non-STR non-AP MLD is defined as "a non-AP MLD that operates as a non-STR for at least the link pair of interest”.
- non-STR terminal necessity of reception data end time control at the time of reception
- the reception end times must be the same. This is based on the fact that in a wireless LAN, it is a common operation for a terminal to transmit an acknowledgment (Ack: Acknowledgment) within a specified period after the end of reception of a received signal. That is, if the reception end times of the received signals are not aligned, the non-STR non-AP MLD transmits Ack on one link, but receives the signal independently on another link, and unintentionally STR (that is, simultaneously performing transmission of Ack and reception of a signal).
- Ack Acknowledgment
- the above signal is a data unit having a certain time width, and is called a PPDU (PLCP (Physical Layer Convergence Protocol) Protocol Data Unit) (see Non-Patent Document 2).
- PPDU Physical Layer Convergence Protocol
- the above specified period is determined to be about 16 microseconds, although the value depends on the implementation of the device, and multiple links are used with the same non-STR non-AP MLD as the destination. It is mentioned that the transmission end time of the transmission signal of each link is within 8 microseconds difference when transmitting the signal on each link.
- Non-Patent Document 2 defines the following two types when transmitting over multiple links for non-AP MLD.
- the reception end time (or the transmission end time of the transmission signal) of each link must be the same.
- Synchronized transmission Synchronized Transmission
- Asynchronous transmission Asynchronous transmission
- Transmission start time of data to be transmitted is not aligned between different links.
- Non-Patent Document 1 The condition for synchronous transmission described in Non-Patent Document 1 is that synchronous transmission is performed only when a transmission right can be acquired on each link after each backoff has expired on a plurality of links. .
- the reason why this condition is necessary is that the backoff is determined by the degree of congestion of transmission on each link, so that the fairness of each link can be expected.
- asynchronous transmission it is possible to acquire the transmission right from the link whose backoff has expired, and improve the probability of implementing multi-link transmission from AP MLD to non-STR non-AP MLD. , asynchronous transmission contributes to the throughput improvement of the whole system.
- Non-Patent Document 2 mentions implementing asynchronous transmission using the following methods (A) to (C). However, the link that has acquired the transmission right first is called “link 1" (or basic link), and the link that has acquired the transmission right later is called “link 2" (or support link). Also, the data to be transmitted is called PPDU.
- TXOP Transmission Opportunity
- the transmission end times of PPDUs transmitted on each link must be the same.
- the reception operation end time t 1 on link 1 may be later than the reception operation end time t 2 on link 2 .
- the transmission time of the Ack frame at the receiving terminal becomes a problem.
- FIG. 1 shows an operation example of transmitting data (PPDU) from STR AP MLD to non-STR non-AP MLD.
- PPDU transmitting data
- each horizontal axis is a time axis.
- the upper part of FIG. 1 shows an operation example of transmission using only link 1
- the lower part of FIG. 1 shows an operation example of transmission using link 1 and link 2.
- the PPDU includes a preamble and a plurality of MPDUs (Media Access Control Protocol Data Units).
- MPDUs Media Access Control Protocol Data Units
- the STR AP MLD sends the PPDU to the non-STR non-AP MLD after the backoff expires.
- the non-STR non-AP MLD returns Ack on link 1 after demodulating the PPDU.
- the transmission period is T1
- the transmission end time is t1 .
- the STR AP MLD transmits PPDUs to the non-STR non-AP MLD for each link after the backoff has expired on each link. .
- the non-STR non-AP MLD returns Ack on the links 1 and 2 after demodulating the PPDU on the links 1 and 2 respectively.
- the transmission period is T2
- the transmission end time is t2 .
- a difference ⁇ T (T 1 ⁇ T 2 ) in the transmission period occurs between the transmission using only link 1 and the transmission using both link 1 and link 2 .
- information indicating the length of the PPDU (that is, the time length of the data) is included in the preamble, which is the beginning of the PPDU.
- the termination of reception of the received signal in the terminal is determined by notifying PHY-RXEND.indication, which is information indicating the termination of reception, from the PHY (PHYsical) layer in the terminal to the MAC (Media Access Control) layer. Also, PHY-RXEND. The indication is notified to the MAC layer only after the reception time estimated from the length of the PPDU included in the preamble of the received signal.
- the STR AP MLD uses the link 2 to transmit the data originally transmitted using only the link 1, as shown in the lower part of FIG. , the data transmission period can be shortened by ⁇ T from T 1 to T 2 .
- the above PHY-RXEND Due to restrictions on the notification timing of the indication, the MAC layer of link 1 behaves as a receive operation until the transmission period before shortening, ie, time t1. This is essentially due to the fact that the MAC layers of the links 1 and 2 do not define information for notifying that the transmission period has been shortened and an interface for notifying that information.
- the reception operation end time on link 1 is later than the reception operation end time on link 2 .
- Ack can only be transmitted after time t 1 instead of time t 2 on link 1, and data is transmitted in a shortened transmission period ( ⁇ T in FIG. 1). I can't do it and have to wait. That is, in asynchronous transmission, although a certain transmission period can be shortened, the transmission time of Ack is delayed, and the problem of deterioration in transmission efficiency as a system becomes apparent.
- the non-STR non-AP MLD in FIG. No if another terminal exists on link 1, that terminal refrains from transmitting until time t 1 when the transmission period T 1 notified in the original PPDU is completed, so non-STR non-AP MLD After the end of the Ack transmission, transmission is not possible during the period up to t 1 , and the problem that the transmission efficiency of the system deteriorates becomes obvious.
- FIG. 2 shows an operation example of transmitting data (PPDU) from STR AP MLD to STR non-AP MLD.
- PPDU data
- each horizontal axis is a time axis.
- the upper part of FIG. 2 shows an example of operation in which only link 1 is used for transmission
- the lower part of FIG. 2 shows an example of operation in which link 1 and link 2 are used for transmission.
- link 1 and link 2 unlike the case of reception by the non-STR MLD shown in the lower part of FIG. 1, the reception end times of each link need not be the same. This is due to the removal of the non-STR MLD constraint.
- link 1 is shortened by ⁇ T(T 1 -T 2 ).
- the PPDU included in the PPDU received on link 1 According to the information indicating the length of T 1 , the receiving operation is continued on the link 1 for the transmission period T 1 before shortening.
- Ack can only be transmitted after time t1 instead of time t2 on link 1 , and data can be transmitted in a shortened transmission period ( ⁇ T in FIG. 2). I can't do it and have to wait. In other words, although the transmission period can be shortened, the Ack transmission time is delayed, resulting in a similar problem that the transmission efficiency of the system deteriorates.
- FIG. 3 shows a configuration example of a wireless network system to which the present disclosure is applied.
- non-STR non-AP MLD1 non-AP STA2 and non-AP STA3, which are terminals that are not access points, are connected to one access point (AP MLD).
- AP MLD access point
- the non-AP STA may be any of non-STR non-AP MLD, STR non-AP MLD, and non-MLD non-AP STA.
- two non-AP STAs (that is, non-AP STA 2 and non-AP STA 3) are connected to AP MLD, but the number of non-AP STAs is not particularly limited. There may be no non-AP STAs other than the non-STR non-AP MLD1, or there may be one or more non-AP STAs other than the non-STR non-AP MLD1. Also, instead of the non-STR non-AP MLD, the STR non-AP MLD may be connected to the AP MLD.
- non-AP STAs other than non-STR non-AP MLD1
- non-AP STAs refer to one or more non-AP STAs.
- AP MLD shall be STR AP MLD.
- the links in the wireless network system shown in FIG. 3 will be explained. There are multiple links that non-STR non-AP MLD1 can transmit with AP MLD, and each non-AP STA of non-AP STAs can transmit with AP MLD on one or more links. It should be noted that the links that can be transmitted by each non-AP STA need not match each other.
- link 1 or Basic Link
- link 2 or Support Link
- FIG. 4 shows a configuration example of a communication device 400 that operates as an MLD (AP MLD or non-AP MLD) capable of multilink transmission using links 1 and 2 in the wireless network system shown in FIG. is shown.
- the illustrated communication device 400 includes a communication section 410 , a control section 420 , a storage section 430 and an antenna 440 .
- the communication unit 410 includes a communication control unit 411, a communication storage unit 412, a common data processing unit 413, an individual data processing unit 414, a signal processing unit 415, a wireless interface unit 416, and an amplification unit 417. .
- the individual data processing unit 414, the signal processing unit 415, the wireless interface unit 416, the amplifier unit 417, and the antenna 440 in the communication unit 410 are provided for each link. -1", and each part for link 2 is suffixed with "-2". However, hereinafter, the notations of "-1" and "-2" are omitted when the description is common. Each part will be described below.
- the amplifier 417 amplifies the signal input from the wireless interface 416 or the antenna 440 .
- a part of the amplification unit 417 may be a component outside the communication unit 410 . Also, part of the amplification section 417 may be included in the wireless interface section 414 .
- the radio interface unit 416 performs digital-analog signal conversion, filtering, up-conversion, and phase control on the symbol stream to generate a transmission signal. Also, during reception, the radio interface unit 416 down-converts, filters, and analog-to-digital signal converts the received signal to generate a symbol stream.
- the signal processing unit 415 performs encoding, interleaving, modulation, etc. on the data unit, adds a physical header, and generates a symbol stream. Also, upon reception, the signal processing unit 415 analyzes the physical header, demodulates, deinterleaves, and decodes the symbol stream, and generates data units. Also, the signal processing unit 415 performs estimation of complex channel characteristics and spatial separation processing as necessary.
- the communication device 400 includes a common data processing unit 413 and an individual data processing unit 414 for each link as data processing units.
- the common data processing unit 413 performs sequence management of the data held in the communication storage unit 412 and the control information and management information received from the communication control unit 411, and performs encryption processing and the like to generate data units. , to the individual data processing unit 414 for each link. Also, at the time of reception, the common data processing unit 413 performs decoding processing and reordering processing of the data unit.
- the individual data processing unit 414 performs channel access operations based on carrier sense, addition of MAC headers and error detection codes to data to be transmitted, and multiple concatenation processing of data units. Also, at the time of reception, the individual data processing unit 414 performs decoupling processing of the MAC header of the received data unit, analysis and error detection, and retransmission request operation.
- the individual data processing unit 414, the signal processing unit 415, the wireless interface unit 416, the amplifier unit 417 and the antenna 440 arranged for each link are regarded as one set (hereinafter also referred to as "individual communication set"), and two or more The individual communication set is a component of the communication device 400, and wireless communication is performed on each link for each individual communication set.
- a storage unit (not shown) may also be included in each individual communication set.
- a link is a wireless transmission path that allows data transmission between two communication devices, and the links used by each individual communication set may have different frequency bands.
- the individual data processing unit 414 and the signal processing unit 415 may be combined into one group, and two or more groups may be connected to one wireless interface unit 416 .
- the communication control unit 411 controls the operation of each unit and information transmission between each unit. It also controls the transfer of control information and management information to be notified to other communication devices to each data processing unit.
- the communication control unit 411 includes individual control units 411-1 and 411-2 for controlling individual communication sets, a common data processing unit 413, and common control for each individual communication set.
- a common control unit 411-3 is included.
- each individual control unit 411-1 and 411-2 receives the data unit in its own individual communication set from the control information (Length and Duration information) included in the received data unit. It has a function of transmitting information indicating the end (PHY-RXEND.indication) to other individual control units.
- Each of the individual control units 411-1 and 411-2 may perform the above transmission via the common control unit 411-3.
- the present disclosure assumes that signal reception periods can be controlled between individual communication sets or individual controllers while signals are being received from multiple links.
- the communication storage unit 412 holds information used by the communication control unit 411. Further, the communication storage unit 412 holds data transmitted through each link and data received from each link.
- the control unit 420 controls the communication unit 410 and the communication control unit 411. Also, the control unit 420 may perform part of the operation of the communication control unit 411 instead. Also, the communication control unit 411 and the control unit 420 may be physically configured as one block.
- the storage unit 430 holds information used by the control unit 420 and the communication unit 410 .
- Storage unit 430 may perform part of the operation of communication storage unit 412 instead.
- Storage unit 430 and communication storage unit 412 may be physically configured as one block.
- the wireless interface unit 416, the amplifier unit 417, and the antenna 440 may be one set, and two or more sets may be components of the communication device.
- the communication unit 410 can be realized by one or more LSIs (Large Scale Integration).
- the common data processing unit 413 is also called Upper MAC or Higher MAC, and the individual data processing unit 414 is also called Lower MAC.
- a set of the individual data processing unit 414 and the signal processing unit 415 is also called an AP entity or a non-AP entity.
- the communication control unit 411 is also called an MLD management entity.
- FIG. 5 shows an example of a communication sequence implemented in a wireless network system as a first embodiment.
- the vertical axis is the time axis.
- STAs STAs
- the communication sequence example shown in FIG. 5 shows the following four types of transmission. Details such as the frame notified in each transmission will be given later.
- Capabilities Exchange Information notification indicating capabilities of each terminal
- DL (Downlink) Transmission Data transmission from AP MLD to non-STR non-AP MLD
- UL (Uplink) Transmission non-STR non - Data transmission from AP MLD to AP MLD
- Ack Receipt acknowledgment for each data transmission in (2) and (3) above
- FIG. 5 shows the sequence of transmission between AP MLD and non-STR non-AP MLD, but does not describe transmission with STAs. This is because FIG. 5 shows an example in which AP MLD or non-STR non-AP MLD acquires the transmission right before STAs and performs each transmission.
- transmission from STAs to AP MLD or transmission from AP MLD to STAs may occur.
- DL Transmission may be performed after transmission occurs between AP MLD and some STAs immediately after Capabilities Exchange.
- link 1 In DL Transmission, while transmission is being performed on one link (hereinafter referred to as "link 1"), transmission on another link occurs.
- Ack transmission and UL transmission on two links from non-STR non-AP MLD may be performed within the transmission rights (period allowed for transmission) secured by transmission on link 1 of AP MLD. good.
- FIG. 6 shows an operation example in which transmission is performed on link 1 and link 2 in DL Transmission.
- the horizontal axis is the time axis.
- link 1 and link 2 between the re-STR AP MLD and the non-STR non-AP MLD, the transmission on link 2 starts after the transmission on link 1 starts. It shows an example of what happens.
- the AP MLD transmits a data unit (PPDU) on link 1.
- PPDU data unit
- control information such as the PPDU length is included in the preamble that is the head of the PPDU.
- MPDU which is data follows the preamble.
- the transmission end time or reception end time of each PPDU is the same (non-AP MLD will send an Ack within a predetermined period on the link where reception has ended. If the reception end times are not aligned, Ack must be transmitted on the other link while the reception operation on one link has not ended, violating the constraint of non-STR. .). However, it is sufficient that this end time is within a certain time width, and an error may occur within a range of, for example, 16 microseconds.
- FIG. 5 shows a case where Capabilities Exchange is performed from AP MLD to non-STR non-AP MLD. Capabilities Exchange may be transmitted at the same time.
- the AP MLD may be implemented by a beacon signal that is periodically transmitted to a plurality of surrounding terminals.
- Capabilities Exchange may also occur from STAs to AP MLD.
- Capabilities Exchange may be transmitted from the STAs to the AP MLD. Note that the order of Capabilities Exchange performed from non-STR non-AP MLD and STAs is not particularly limited.
- Each sequence may be partially omitted as necessary, and the order may not be as shown in FIG. For example, if it is determined that Ack is not necessary depending on the type of data to be transmitted, Ack may not be transmitted.
- Capabilities Exchange The AP MLD and the non-STR non-AP MLD perform information notification (hereinafter referred to as “Capabilities Exchange”) regarding the capabilities of their own terminals to each other. Capability here refers to, but is not limited to, whether a terminal can perform STR transmission and the number of links that can transmit simultaneously.
- Capability Exchange may be implemented by being included in, for example, a beacon signal periodically transmitted by each terminal, or information notification (Association) for establishing connection between terminals after a beacon signal.
- Fig. 7 shows a configuration example of a frame notified by Capabilities Exchange.
- the illustrated frame is composed of fields of Frame Control, RA (Receiving STA address), TA (Transmitting STA address), and Multi-Link element.
- RA Receiving STA address
- TA Transmitting STA address
- Multi-Link element the constituent elements of the frame are not limited to these.
- the Frame Control field stores information indicating that the frame is a frame notified by Capabilities Exchange. Information indicating a source terminal and a destination terminal are stored in the RA and TA fields, respectively.
- the Multi-Link element field stores information indicating whether or not STR transmission is possible, usable links, and the number of simultaneously usable links for the terminal itself that transmits the frame.
- RA and TA may indicate, for example, a terminal-specific MAC address.
- a plurality of MAC addresses may be assigned to one MLD. Specifically, this is the case where a MAC address is assigned to each individual communication set within one MLD or to each link used by one MLD. That is, the RA and TA are information for identifying not only the MLD but also the MLD that notifies the frame and the individual communication set or link of the MLD. As will be described later, it may be identified together with the MLD MAC Address in the Multi-Link element.
- Multi-Link element Each field of Element ID, Length, Element ID Extension, Multi-Link Control, MLD MAC Address, and Per-STA Profile is stored in the Multi-Link element.
- the Element ID field stores information indicating that the element is a Multi-Link element.
- the Length field stores information indicating the bit length of the Multi-Link element.
- the Multi-Link Control field stores information indicating whether or not there is a subsequent MLD MAC Address.
- the MLD MAC Address field stores identification information that is individually assigned to the MLD terminal regardless of the link or individual communication set.
- the Per-STA Profile field stores information about each link or each individual communication set.
- the Multi-Link Control field stores MLD MAC Address Present and Rapid Non-STR Rx subfields.
- the MLD MAC Address Present field stores information indicating the presence of the MLD MAC Address.
- Rapid Non-STR Rx field when the terminal transmitting the frame operates as non-STR MLD in DL transmission, asynchronous transmission as shown in FIG. 6 (that is, transmission start time between multiple links Information indicating that reception of unaligned asynchronous transmission) is possible is stored.
- the Per-STA Profile field stores the Subelement ID, Length, and Per-STA Control subfields. A plurality of Per-STA Profiles may exist, and information for different links or individual communication sets is indicated.
- the Subelement ID field stores information indicating that the subfield is a Per-STA Profile.
- the Length field stores information indicating the bit length of the Per-STA Profile.
- the Per-STA Control field stores information about the target link or individual communication set indicated in the Per-STA Profile field.
- the Per-STA Control field may store Link ID, Bandwidth, and Non-STR Pair Link ID subfields.
- the Link ID field stores information indicating the target link or individual communication set.
- the Bandwidth field stores information indicating the frequency band that can be transmitted by the link indicated by the Link ID or the individual communication set.
- the Non-STR Pair Link ID field stores information indicating a link or individual communication set that operates as a non-STR MLD when used simultaneously with the link or individual communication set indicated by the Link ID.
- DL Transmission carries out data transmission from AP MLD to non-STR non-AP MLD. Also, in UL Transmission, data transmission is performed from non-STR non-AP MLD to AP MLD. As described above, here the AP MLD acquires the transmission right on a certain link (link 1) and performs data transmission, but data transmission is started on another link (link 2) during transmission. However, the end times of transmission on each link are aligned within a specific error range.
- FIG. 8 shows in detail a specific operation example of DL Transmission and UL Transmission. However, the horizontal axis is the time axis.
- AP MLD transmits to non-STR non-AP MLD1 on link 1, but immediately after that, it also transmits on link 2.
- link 1 and link 2 Through prior Capabilities Exchange, AP MLD understands that non-STR non-AP MLD1 supports multi-link transmission using link 1 and link 2 and is capable of receiving asynchronous transmission. It is assumed that there is
- the AP MLD determines that transmission period T1 is required to transmit the PPDU at the start of transmission. After that, AP MLD acquires a new transmission right on link 2, so that part of the data originally sent on link 1 can be sent on link 2, so the PPDU transmission period on link 1 is T 1 is shortened to T 2 . At this time, since the receiving terminal is NSTR, the transmission end times of PPDU on link 1 and link 2 are aligned within a specific error range.
- the preamble in the PPDU transmitted by the AP MLD on link 1 contains information indicating the length of the PPDU transmitted on link 1.
- the preamble is placed at the beginning of the PPDU, even if the PPDU length is changed after the preamble is notified, the receiving terminal cannot recognize the changed PPDU length.
- STA2 which is a terminal that does not use link 2
- STA3 which is a terminal that does not use link 1
- the AP MLD includes information indicating that the length of the PPDU transmitted on link 1 is changed from T1 to T2 in the PPDU transmitted on link 2 , if transmission rights on link 2 can be obtained and notified. By doing so, it is possible to notify the non-STR non-AP MLD1 that the transmission period on the link 1 has been shortened. Also, STA 3 using link 2 receives a similar notification and can make an idle state determination for link 1 after the transmission period T2. On the other hand, since STA2 is not using link 2 , it is not informed that the transmission period on link 1 has been shortened from T1 to T2. Therefore, STA2 cannot judge the idle state of link 1 until after T1.
- the AP MLD and the non-STR non-AP MLD1 perform another PPDU transmission again within the transmission period T1 notified in advance by the link 1 preamble.
- the one to be transmitted on link 1 is PPDU#2-1
- the one to be transmitted on link 2 is PPDU#2-2, both from AP MLD.
- An example of uplink transmission from the non-STR non-AP MLD to the AP MLD is shown. That is, the non-STR non-AP MLD1 transmits to the AP MLD within the period T 1 covered by the transmission right acquired by the AP MLD.
- AP MLD notifies non-STR non-AP MLD of uplink transmission permission (that is, Reverse Direction Grant: RDG) with RDG/More PPDU described in PPDU transmitted on link 1 and link 2.
- RDG Reverse Direction Grant
- another PPDU transmission can be performed again within the period T1.
- FIG. 9 shows a configuration example of PPDUs transmitted on link 1 and link 2.
- a PPDU consists of a preamble and one or more MPDUs. Note that an area (padding) for adjusting the data length may be included at the end of the PPDU as needed.
- the preamble contains information necessary for demodulating the subsequent MPDU in addition to time synchronization, frequency synchronization and channel estimation in the terminal that receives the PPDU.
- information such as the frequency band in which the MPDU is transmitted and the MCS (Modulation and Coding Scheme) indicating the modulation and coding schemes used may be included.
- the MPDU contains data to be sent other than the preamble.
- Each MPDU may store Control, Duration, RA and TA, HT (High Throughput) Control, and Payload fields.
- the Frame Control field stores information indicating the frame type of the MPDU.
- the Duration field stores information representing the transmission period in DL Transmission. Information indicating the source terminal and information indicating the destination terminal are stored in the RA and TA fields, respectively. Other control information is stored in the HT Control field. Data information sent in addition to the above control information is stored in the Payload field.
- the HT Control field stores EHT variant ID, Control ID, and ML-CAS (Command and Status) subfields.
- Information indicating the type of HT Control is stored in each of the EHT variant ID and Control ID.
- the ML-CAS field stores the type of data transmitted on the link and information on links other than the link on which the frame is transmitted.
- At least one of the AC Constraint, RDG/More PPDU, Support Link Effort, Basic Link Overwrite Flag, and Renewal Length subfields is stored in the ML-CAS field.
- the AC Constraint field stores information indicating that there are restrictions on the types of traffic that can be transmitted in the DL Transmission. Information indicating either (1) or (2) below is stored in the RDG/More PPDU field.
- the terminal transmitting the frame is a terminal that has acquired the transmission right
- the destination terminal is permitted to transmit within the range of the transmission right (that is, Reverse Direction Grant: RDG).
- RDG Reverse Direction Grant
- the Support Link Effort field stores information indicating whether the terminal reporting the frame is attempting to acquire the transmission right on a link other than the link reporting the frame.
- Basic Link Overwrite Flag field some information contained in the preamble and ML-CAS is sent to the receiving terminal when a link other than the link that is notifying the frame is already being used for transmission. Information indicating whether to overwrite is stored.
- the Renewal Length field is included in the PPDU sent on link 2, and stores information indicating the changed PPDU length of link 1 or the changed PPDU length of link 1.
- a Support Link Effort subfield is stored in MPDU in PPDU #1-1 transmitted by AP MLD on link 1
- Basic Link is stored in PPDU #1-2 transmitted by AP MLD on link 2.
- Overwrite Flag subfield and Renewal Length subfield are stored.
- the AP MLD attempts to acquire the transmission right on link 2 (ie, Support Link) in the Support Link Effort field of the PPDU to be transmitted on link 1 (ie, Basic Link). can be shown. Also, when the AP MLD is already using the link 2 (that is, the Support Link) for transmission, the information contained in the ML-CAS (specifically, the link 1 (that is, the changed portion of the PPDU length of Basic Link or the changed PPDU length of link 1) has been overwritten in the Basic Link Overwrite Flag subfield.
- FIG. 9 shows that ML-CAS is stored in each MPDU, ML-CAS need not be stored in all MPDUs.
- the ML-CAS may be stored only in the first MPDU, or the ML-CAS may be stored in the preamble instead of the MPDU.
- the Duration field has stores information indicating T 3 ' in FIG.
- data may be transmitted to non-STR non-AP MLD and to AP MLD within the period of T 3 '.
- RDG Reverse Direction Grant
- FIG. 10 shows each logical entity in communication section 410 in non-STR non-AP MLD1 to which PPDU#1-1 and PPDU#1-2 are notified in DL transmission. shows an example of the operation of However, the horizontal axis is the time axis.
- multiple MPDUs in a PPDU are collectively described as a PSDU (PHY Service Data Unit).
- an individual control unit 1 for link 1 and an individual control unit 2 for link 2 are arranged.
- the individual control unit 1 and the individual control unit 2 respectively have PHY Layer #1 and PHY Layer #2 that control the physical layers of link 1 and link 2, and MAC Lower Sublayer #1 that controls data processing of link 1 and link 2. and MAC Lower Sublayer #2 logical entities.
- a Common Entity is further arranged as a logical entity that controls data processing common to the link 1 and the link 2.
- SAP Service Access Point
- the PHY Layer is composed of the antenna 440, the amplifier 417 in the communication section 410, the wireless interface section 416, the signal processing section 415, and the individual control section 414.
- the MAC Lower Sublayer is the individual data It is composed of a processing unit 414 and a corresponding individual control unit in the communication control unit 411 .
- the components of the PHY Layer and MAC Lower Sublayer need not be limited to these.
- Ack is transmitted from non-STR non-AP MLD1 when each PSDU is received, but a series of flow is omitted in FIG. 10 for convenience of explanation. That is, for example, in period T3 , in addition to reception of PSDU including preamble and padding, transmission of Ack is included, but the description of transmission of Ack is omitted in FIG. 10 for the sake of convenience.
- PHY Layer #1 receives data transmitted from AP MLD1 on link 1, demodulates it, and then delivers MPDU to MAC Lower Sublayer #1. Similar operations are performed on link 2 as well.
- E-4-1 PHY Layer operation in link 1, information notified between PHY ⁇ MAC
- the arrow indicated by reference number 1001 in FIG. 10 indicates received signal strength indicator (RSSI) or
- RXVECTOR control information
- each MPDU is shown to be notified from PHY Layer #1 to MAC Lower Sublayer #1.
- PHY Layer # 1 calculates T1, which is the demodulation operation period, based on the information indicated in the preamble, and performs demodulation. After the demodulation operation is completed, PHY Layer #1 notifies MAC Lower Sublayer # 1 that reception has been completed. end of period T1 ) is determined. An arrow indicated by reference number 1001' in FIG. 10 indicates a reception end notification. In this reception end notification, not only is the reception end notified, but also the idle state of the channel determined by PHY Layer #1 is notified to MAC Lower Sublayer #1.
- the PHY Layer # 1 does not need to perform the demodulation operation.
- MAC Lower Sublayer #1 Operation of MAC Lower Sublayer in Link 1, information notified between MAC Lower ⁇ Common Entity In MAC Lower Sublayer #1, information contained in MPDU after notification indicated by arrow 1001 from PHY Layer #1 is performed is analyzed, and necessary information is notified to the Common Entity.
- the arrow with reference number 1002 in FIG. 10 indicates this notification.
- MAC Lower Sublayer #1 analyzes whether it is indicated in the Support Link Effort subfield in the MPDU that the AP MLD is trying to acquire the transmission right on link 2, and uses this information as a Common entity. to notify.
- MAC Lower Sublayer #1 analyzes whether permission for another transmission within the period T 1 is indicated in the RDG/More PPDU subfield, and converts the information indicated in this field to The Common Entity may be notified.
- PHY Layer #1 analyzes the information in Support Link Effort in the same way and notifies the information to Common Entity via MAC Lower Sublayer #1.
- E-4-3 PHY Layer operation in link 2, information notified between PHY ⁇ MAC As described in the above section E-4-1, as indicated by the arrow of reference number 1003 in FIG. 10, PHY Layer # 2 notifies MAC Lower Sublayer #2 of each MPDU in addition to control information (RXVECTOR) such as received power (RSSI), number of spatial streams, PPDU format, etc., based on information indicated in the preamble.
- RXVECTOR received power
- RSSI received power
- number of spatial streams PPDU format, etc.
- PHY Layer# 2 calculates T3, which is the demodulation operation period, based on the information indicated in the preamble, and performs demodulation. After the demodulation operation is completed, PHY Layer #2 notifies MAC Lower Sublayer # 2 that reception has been completed. end of period T3 ) is determined. An arrow indicated by reference number 1003' in FIG. 10 indicates a reception end notification. In this reception end notification, not only is the reception end notified, but also the idle state of the channel determined by PHY Layer #2 is notified to MAC Lower Sublayer #2.
- the PHY Layer #2 does not need to perform the demodulation operation.
- E-4-4 Operation of MAC Lower Sublayer in Link 2
- information notified between MAC Lower ⁇ Common Entity information contained in MPDU after notification indicated by arrow 1003 from PHY Layer #2 is performed is analyzed, and necessary information is notified to the Common Entity.
- the arrow with reference number 1004 in FIG. 10 indicates this notification.
- MAC Lower Sublayer # 2 receives the signal from AP MLD, the information indicated by ML-CAS including Renewal Length (that is, the information indicated in the preamble notified on link 1 information indicating changes), and notifies the Common Entity of these pieces of information.
- MAC Lower Sublayer #2 analyzes whether information in the preamble and ML-CAS already transmitted on link 1 is overwritten in the Basic Link Overwrite Flag subfield, and Notifies the Common Entity of the information to indicate and the information to be changed.
- MAC Lower Sublayer # 2 analyzes whether permission for another transmission within the period T 1 is indicated in the RDG / More PPDU subfield, and the information indicated in this field may be notified to the Common Entity.
- PHY Layer #1 similarly analyzes the information in the ML-CAS field and notifies the information to the Common Entity via MAC Lower Sublayer #1. You may do so.
- the Common Entity may notify MAC Lower Sublayer #1 of this information as well. That is, in the RDG/More PPDU subfield in ML-CAS notified on link 2, non-STR non-AP MLD1 to AP MLD When the information indicating that transmission to is permitted is included, the Common Entity notifies the MAC Lower Sublayer #1 or PHY Layer #1 of the information. In FIG. 10, the Common Entity notifies PHY Layer #1 via MAC Lower Sublayer #1, but the Common Entity may notify PHY Layer #1 directly.
- FIG. 11 shows in the form of a flowchart the operations performed by the Common Entity in the non-STR non-AP MLD.
- PHY Layer#1 When receiving end time notification PHY Layer#1 is directly or indirectly notified of a change in the reception period from the Common Entity, it sends the changed reception end time based on the notified information to the reference number in FIG. As indicated by the arrow 1007, the MAC Lower Sublayer #1 is notified of the reception end time. At this time, the PHY Layer#1 may notify the MAC Lower Sublayer#1 of the channel idle state.
- PHY Layer #2 at the time of implementation of the reception end notification of PSDU transmitted on link 2, as indicated by the arrow of reference number 1003' in FIG. to implement the notice of
- the timing of notification from MAC Lower Sublayer #1 to PHY Layer #1 may be after all data (MPDU) has been notified from PHY Layer #1 to MAC Sublayer #1.
- MAC Lower Sublayer #1 when MPDU is notified every octet (byte) from PHY Layer #1 to MAC Lower Sublayer #1, after change of link 1 based on the information indicated by Renewal Length notified from PHY Layer #2 can estimate the transmission data length of Therefore, after PHY Layer#1 notifies MAC Lower Sublayer#1 of the data of the number of octets corresponding to the estimated changed transmission data length, MAC Lower Sublayer#1 sends PHY Layer#1 to PHY Layer#1. Information indicating a reception operation end request may be notified. Upon receiving this request, PHY Layer #1 may notify MAC Lower Sublayer #1 of at least one of the reception end time notification and channel availability information notification.
- Non-Patent Document 1 the data notified from PHY Layer#1 to MAC Lower Sublayer#1 for each octet is PHY-DATA. Notified by indication.
- the Common Entity generates information necessary to generate a response confirmation frame in response to the error judgment for the received MPDU. For example, when the received MPDU is managed by a certain number (sequence number, etc.), it broadens whether or not the MPDU of which number was successfully received, and passes information indicating the recorded information to each MAC Lower Sublayer.
- control information necessary for operating as non-STR non-AP MLD to MAC Lower Sublayer or PHY Layer.
- This control information includes, as non-STR non-AP MLD, information indicating synchronous transmission through a plurality of links and information indicating the length of PPDU generated by the PHY layer.
- each PHY Layer After passing information from each MAC Lower Sublayer to each PHY Layer, each PHY Layer simultaneously transmits PPDU. At this time, the acknowledgment frame and the MPDU representing the received data may be collectively transmitted as one PPDU.
- FIG. 12 shows an example of a communication sequence implemented in a wireless network system as a second embodiment.
- the vertical axis is the time axis.
- UL transmission is performed only in non-STR non-AP MLD in the extra period.
- another STA STA2 in the example shown in FIG. 12 performs UL transmission in the extra period after DL transmission.
- the operations of Capabilities Exchange and DL Transmission are basically the same as in the first embodiment.
- FIG. 13 shows in detail a specific operation example of DL Transmission and UL Transmission.
- the horizontal axis is the time axis.
- AP MLD transmits on link 1 to non-STR non-AP MLD1, and immediately thereafter also transmits on link 2.
- the AP MLD transmits PPDU#1-2 on the link 2
- the AP MLD provides Enhanced CF (Contention Free) indicating release of the link 2 transmission right to other terminals. - Notify End.
- Enhanced CF Contention Free
- the AP MLD determines at the start of transmission that a transmission period of T1 is required to transmit the PPDU. After that, the AP MLD acquires a new transmission right on the link 2, so that part of the data originally sent on the link 1 can be sent on the link 2, so the PPDU transmission period on the link 1 is T. shortened to 2 . At this time, the PPDU transmission end times on the link 1 and the link 2 are aligned within a specific error range.
- the preamble in the PPDU transmitted by the AP MLD on link 1 contains information indicating the length of the PPDU transmitted on link 1. Since the preamble is placed at the beginning of the PPDU, even if the PPDU length is changed after the preamble is notified, the receiving terminal cannot recognize the changed PPDU length.
- a terminal STA2 that does not use link 2 and a terminal STA3 that does not use link 1 exist separately from non-STR non-AP MLD1.
- the AP MLD After AP MLD has transmitted PPDU#1-2 on link 2, if transmission from terminals other than non-STR non-AP MLD1 may be permitted, the AP MLD transmits to other terminals. Notifies Enhanced CF-End indicating release of right. Therefore, when STA3 subsequently obtains the transmission right on link 2, it can transmit PPDU#3.
- AP MLD includes a transmission prohibited period for non-STR non-AP MLD1 in Enhanced CF-End (in the example shown in FIG. 13, the transmission prohibited period is T 3 ′-T 3 ). When the non-STR non-AP MLD1 receives this Enhanced CF-End, it refrains from acquiring the transmission right for the specified transmission prohibited period.
- the frame structure of Enhanced CF-End will be explained in the next section F-2 with reference to FIG.
- the AP MLD indicates permission for transmission within the transmission period T 1 in the RDG/More PPDU field of the PPDU transmitted on the link 1, so that the non-STR non-AP MLD on the link 1 Again another (ie, uplink) PPDU transmission can be implemented.
- the AP MLD indicates that transmission is not permitted within the transmission period T 1 in the RDG/More PPDU field of the PPDU transmitted over the link 2, so that the non-STR non-AP MLD can transmit the link 1 within the transmission period T 1 will not perform another PPDU transmission again.
- FIG. 14 shows a configuration example of a frame notified by Enhanced CF-End.
- Enhanced CF-End is a frame for notifying the communication partner of multilink transmission including the relevant link of the transmission prohibited period in the relevant link. It can indicate the release of the transmission right of the corresponding link.
- the frame shown in FIG. 14 includes Frame Control, Duration, RA, BSSID or TA, HT Control, and FCS fields, but may include other components not shown.
- the Duration field stores information indicating the period for acquiring the transmission period in addition to the time for transmitting the frame.
- the RA field stores information indicating one or more destination terminals.
- the BSSID (TA) field stores information indicating the BSSID to which the frame transmission destination terminal or the frame transmission destination terminal belongs. Other control information is stored in the HT Control field.
- An FCS (Frame Check Sequence) field stores information for error correction to be performed when the frame is received.
- the HT Control field includes EHT variant ID, Control ID, STA ID, and Prohibited period subfields.
- Each subfield of EHT variant ID and Control ID stores information indicating the type of HT Control.
- the STA ID field stores the identification information of terminals that are prohibited from being used as the destination.
- the Prohibited period stores information representing the period during which transmission to the terminal specified in the STA ID field is prohibited. It should be noted that the STA ID field may store information indicating the MAC address of the relevant link of the relevant terminal.
- information indicating non-STR non-AP MLD1 is stored in the STA ID field in the Enhanced CF-End frame, and the prohibited period (T 3 '-T 3 ) is set in the prohibited period. It stores information that represents Therefore, the terminal receiving the Enhanced CF-End frame refrains from transmitting to the non-STR non-AP MLD1 for the transmission prohibited period (T 3 '-T 3 ).
- the STA ID field may store information indicating the MAC address of the link 2 of the non-STR non-AP MLD1.
- the terminal notified of the Enhanced CF-End frame is restricted not to notify information to non-STR non-AP MLD1 for a specific period based on the information indicated in the STA ID and Prohibited period subfields. be done.
- FIG. 15 shows an operation example in the communication unit 410 in the non-STR non-AP MLD1 in which PPDU#1-1 and PPDU#1-2 are notified in DL transmission. showing. However, the horizontal axis is the time axis. In addition, in FIG. 15, a plurality of MPDUs in a PPDU are collectively described as a PSDU.
- an individual control unit 1 for link 1 and an individual control unit 2 for link 2 are arranged.
- the individual control unit 1 and the individual control unit 2 respectively have PHY Layer #1 and PHY Layer #2 that control the physical layers of link 1 and link 2, and MAC Lower Sublayer #1 that controls data processing of link 1 and link 2. and MAC Lower Sublayer #2 logical entities.
- a Common Entity is further arranged as a logical entity that controls data processing common to the link 1 and the link 2.
- FIG. Information is exchanged between Layer and Layer and between Layer and Entity via SAP.
- parameters to be applied by each MAC Lower Sublayer and PHY Layer are calculated.
- Ack is transmitted from non-STR non-AP MLD1
- FIG. 15 a series of flows related to transmission of Ack is omitted for convenience of explanation.
- the Common Entity When the Common Entity receives notification of the reception end time from each PHY Layer, it performs the following (1) to (3) as operations for the MAC Lower Sublayer indicated by the arrow of reference number 1508 in FIG.
- the Common Entity generates information necessary to generate a response confirmation frame in response to the error judgment for the received MPDU. For example, when the received MPDU is managed by a certain number (sequence number, etc.), it broadens whether or not the MPDU of which number was successfully received, and passes information indicating the recorded information to each MAC Lower Sublayer.
- control information necessary for operating as non-STR non-AP MLD to MAC Lower Sublayer or PHY Layer.
- This control information includes, as non-STR non-AP MLD, information indicating synchronous transmission through a plurality of links and information indicating the length of PPDU generated by the PHY layer.
- the Common Entity notifies the transmission prohibited period as an operation (corresponding to the arrow 1508 in FIG. 15) to the individual communication unit 2 of the link 2 when receiving the notification of the reception end time from each PHY layer. That is, the Common Entity notifies link 2 of information indicating that transmission is prohibited at least during the transmission period of PPDU#2-1.
- the AP MLD transmits an Enhanced CF-End frame on link 2 after completing multilink transmission using links 1 and 2 .
- the AP MLD notifies the non-STR non-AP MLD1 of the transmission prohibited period (T 3 '-T 3 ) in this Enhanced CF-End frame.
- the terminal notified of Enhanced CF-End on link 2 transmits to terminals other than non-STR non-AP MLD1.
- FIG. 13 shows that a terminal other than AP MLD, that is, STA3 transmits on link 2, AP MLD may transmit to terminals other than non-STR non-AP MLD on link 2. .
- FIG. 16 shows an example of a communication sequence implemented in a wireless network system as a third embodiment.
- the vertical axis is the time axis.
- STAs STAs
- the communication sequence example shown in FIG. 16 shows the following four types of transmission. Details such as the frame notified in each transmission will be given later.
- Capabilities Exchange Information notification indicating the capabilities of each terminal
- DL Transmission Data transmission from AP MLD to STR non-AP MLD
- UL Transmission Data transmission from STR non-AP MLD to AP MLD
- Ack Receipt acknowledgment for each data transmission in (2) and (3) above
- FIG. 16 shows the sequence of transmission between AP MLD and STR non-AP MLD, but does not describe transmission with STAs. This is because FIG. 16 shows an example in which AP MLD or STR non-AP MLD acquires the transmission right before STAs and carries out each transmission. Although not shown, transmission from or to STAs may occur. For example, DL Transmission may be performed after transmission occurs between AP MLD and some STAs immediately after Capabilities Exchange.
- link 1 While transmission is being performed on one link (hereinafter referred to as "link 1"), transmission on another link occurs. Also, two Acks and UL Transmission may be performed within the transmission right (the period during which transmission is permitted) secured by transmission on link 1.
- FIG. 17 shows an operation example in which transmission is performed on link 1 and link 2 in DL Transmission.
- the horizontal axis is the time axis.
- the figure shows an example in which there are two links, link 1 and link 2, and transmission on link 2 occurs after transmission on link 1 starts.
- the AP MLD transmits a data unit (PPDU) on link 1.
- PPDU data unit
- control information such as the PPDU length is included in the preamble that is the head of the PPDU.
- MPDU which is data follows the preamble. It should be noted that if the receiving terminal is STRMLD, the transmission end time or reception end time of each PPDU need not be the same.
- FIG. 16 shows a case where Capabilities Exchange is performed from AP MLD to STR non-AP MLD, but it is simultaneously transmitted to STR non-AP MLD and STAs.
- the AP MLD may be implemented by a beacon signal that is periodically transmitted to a plurality of surrounding terminals.
- Capabilities Exchange may also occur from STAs to AP MLD.
- the AP MLD emits a beacon signal, it may be transmitted from the STAs to the AP MLD.
- the order of Capabilities Exchange performed from STR non-AP MLD and STAs is not particularly limited.
- Each sequence may be partially omitted as necessary, and the order does not have to be as shown in FIG. For example, if it is determined that Ack is not necessary depending on the type of data to be transmitted, Ack may not be transmitted.
- Capabilities Exchange The AP MLD and the STR non-AP MLD perform information notification (Capabilities Exchange) regarding the capabilities of their own terminals to each other. Capability here refers to, but is not limited to, whether a terminal can perform STR transmission and the number of links that can transmit simultaneously. Capability Exchange may be implemented by being included in, for example, a beacon signal periodically transmitted by each terminal, or information notification (Association) for establishing connection between terminals after the beacon signal.
- Fig. 18 shows a configuration example of a frame notified by Capabilities Exchange.
- the illustrated frame is composed of Frame Control, RA, TA, and Multi-Link element fields.
- the constituent elements of the frame are not limited to these.
- the Frame Control field stores information indicating that the frame is a frame notified by Capabilities Exchange. Information indicating a source terminal and a destination terminal are stored in the RA and TA fields, respectively.
- the Multi-Link element field stores information indicating whether or not STR transmission is possible, usable links, and the number of simultaneously usable links for the terminal itself that transmits the frame.
- RA and TA may indicate, for example, a terminal-specific MAC address.
- a plurality of MAC addresses may be assigned to one MLD. Specifically, this is the case where a MAC address is assigned to each individual communication set within one MLD or to each link used by one MLD. That is, the RA and TA are information for identifying not only the MLD but also the MLD that notifies the frame and the individual communication set or link of the MLD. As will be described later, it may be identified together with the MLD MAC Address in the Multi-Link element.
- Multi-Link element Each field of Element ID, Length, Element ID Extension, Multi-Link Control, MLD MAC Address, and Per-STA Profile is stored in the Multi-Link element.
- the Element ID field stores information indicating that the element is a Multi-Link element.
- the Length field stores information indicating the bit length of the Multi-Link element.
- the Multi-Link Control field stores information indicating whether or not there is a subsequent MLD MAC Address.
- the MLD MAC Address field stores identification information that is individually assigned to the MLD terminal regardless of the link or individual communication set.
- the Per-STA Profile field stores information about each link or each individual communication set.
- the Multi-Link Control field stores MLD MAC Address Present and Rapid STR Rx subfields.
- the MLD MAC Address Present field stores information indicating the presence of the MLD MAC Address.
- the Rapid STR Rx field stores information indicating that asynchronous transmission reception as shown in FIG. 17 is possible when the terminal transmitting the frame operates as STR MLD in DL Transmission.
- the Per-STA Profile field stores Subelement ID, Length, and Per-STA Control subfields. A plurality of Per-STA Profiles may exist, and information for different links or individual communication sets is indicated.
- the Subelement ID field stores information indicating that the subfield is a Per-STA Profile.
- the Length field stores information indicating the bit length of the Per-STA Profile.
- the Per-STA Control field stores information about the target link or individual communication set indicated in the Per-STA Profile field.
- the Per-STA Control field may store Link ID, Bandwidth, and STR Pair Link ID subfields.
- the Link ID field stores information indicating the target link or individual communication set.
- the Bandwidth field stores information indicating the frequency band that can be transmitted by the link indicated by the Link ID or the individual communication set.
- the STR Pair Link ID field stores information indicating the link or individual communication set that operates as the STR MLD when used simultaneously with the link or individual communication set indicated by the Link ID.
- the terminal that notifies the frame will link 1 and link 2.
- the transmission can be performed as STR MLD.
- DL Transmission carries out data transmission from AP MLD to STR non-AP MLD
- UL Transmission carries out data transmission from STR non-AP MLD to AP MLD.
- the AP MLD acquires the transmission right on a certain link (link 1) and performs data transmission, but data transmission is started on another link (link 2) during transmission.
- FIG. 19 shows in detail a specific operation example of DL Transmission and UL Transmission. However, the horizontal axis is the time axis.
- AP MLD transmits to STR non-AP MLD1 on link 1, but immediately after that, it also transmits on link 2. Through prior Capabilities Exchange, AP MLD understands that STR non-AP MLD1 supports multi-link transmission using link 1 and link 2, and is capable of receiving asynchronous transmission. and
- the AP MLD determines at the start of transmission that a transmission period of T1 is required to transmit the PPDU. After that, the AP MLD acquires a new transmission right on the link 2, so that part of the data originally sent on the link 1 can be sent on the link 2, so the PPDU transmission period on the link 1 is T. shortened to 2 . At this time, since the receiving terminal is the STR, the PPDU transmission end times on link 1 and link 2 may be arbitrary and do not have to be the same.
- the preamble in the PPDU transmitted by the AP MLD on link 1 contains information indicating the length of the PPDU transmitted on link 1.
- the preamble is placed at the beginning of the PPDU, even if the PPDU length is changed after the preamble is notified, the receiving terminal cannot recognize the changed PPDU length.
- STA2 which is a terminal that does not use link 2
- STA3 which is a terminal that does not use link 1
- the AP MLD includes information indicating that the length of the PPDU transmitted on link 1 is changed from T1 to T2 in the PPDU transmitted on link 2 , if transmission rights on link 2 can be obtained and notified. Thus, it is possible to notify the STR non-AP MLD1 that the transmission period on the link 1 has been shortened. Also, STA 3 using link 2 receives a similar notification and can make an idle state determination for link 1 after the transmission period T2. On the other hand, since STA2 is not using link 2 , it is not informed that the transmission period on link 1 has been shortened from T1 to T2. Therefore, STA2 cannot judge the idle state of link 1 until after T1.
- the AP MLD and the STR non-AP MLD1 perform another PPDU transmission again within the transmission period T1 notified in advance by the link 1 preamble.
- the one to be transmitted on link 1 is PPDU#2-1
- the one to be transmitted on link 2 is PPDU#2-2, both from AP MLD.
- AP MLD is RDG / More PPDU described in PPDU transmitted on link 1 and link 2, to STR non-AP MLD by notifying permission of uplink transmission (that is, Reverse Direction Grant: RDG) , another PPDU transmission can be performed again within the period T 1 .
- RDG Reverse Direction Grant
- FIG. 19 shows an example in which the transmission end times of PPDU#2-1 and PPDU#2-2 are the same, but since the non-AP MLD of the transmission source is STR, transmission ends It doesn't have to be on time.
- STR non-AP MLD returns Ack for PPDU#1-1 on link 1 before finishing receiving PPDU#1-2 from AP MLD on link 2.
- FIG. 20 shows a configuration example of PPDUs transmitted on link 1 and link 2.
- a PPDU consists of a preamble and one or more MPDUs. Note that an area (padding) for adjusting the data length may be included at the end of the PPDU as necessary.
- the preamble contains information necessary for demodulating the subsequent MPDU in the terminal that receives the PPDU.
- information such as the frequency band in which the MPDU is transmitted and the MCS used may be included.
- the MPDU contains data to be sent other than the preamble.
- Each MPDU may store Control, Duration, RA and TA, HT Control, and Payload fields.
- the Frame Control field stores information indicating the frame type of the MPDU.
- the Duration field stores information representing the transmission period in DL Transmission. Information indicating the source terminal and information indicating the destination terminal are stored in the RA and TA fields, respectively. Other control information is stored in the HT Control field. Data information sent in addition to the above control information is stored in the Payload field.
- the EHT variant ID, Control ID, and ML-CAS subfields are stored in the HT Control field.
- Information indicating the type of HT Control is stored in each of the EHT variant ID and Control ID.
- the ML-CAS field stores the type of data transmitted on the link and information on links other than the link on which the frame is transmitted.
- At least one of the AC Constraint, RDG/More PPDU, Support Link Effort, Basic Link Overwrite Flag, and Renewal Length subfields is stored in the ML-CAS field.
- the AC Constraint field stores information indicating that there are restrictions on the types of traffic that can be transmitted in the DL Transmission. Information indicating either (1) or (2) below is stored in the RDG/More PPDU field.
- the terminal transmitting the frame is a terminal that has acquired the transmission right
- the destination terminal is permitted to transmit within the range of the transmission right (that is, Reverse Direction Grant: RDG).
- RDG Reverse Direction Grant
- the Support Link Effort field stores information indicating whether the terminal reporting the frame is attempting to acquire the transmission right on a link other than the link reporting the frame.
- Basic Link Overwrite Flag field some information contained in the preamble and ML-CAS is sent to the receiving terminal when a link other than the link that is notifying the frame is already being used for transmission. Information indicating whether to overwrite is stored.
- the Renewal Length field is included in the PPDU sent on link 2, and stores information indicating the changed PPDU length of link 1 or the changed PPDU length of link 1.
- a Support Link Effort subfield is stored in MPDU in PPDU #1-1 transmitted by AP MLD on link 1
- Basic Link is stored in PPDU #1-2 transmitted by AP MLD on link 2.
- Overwrite Flag subfield and Renewal Length subfield are stored.
- AP MLD attempts to acquire the transmission right on link 2 (ie, Support Link) in the Support Link Effort field of the PPDU to be transmitted on link 1 (ie, Basic Link).
- link 2 that is, the Support Link
- the information contained in the ML-CAS specifically, the link 1 (that is, the changed portion of the PPDU length of Basic Link or the changed PPDU length of link 1) has been overwritten in the Basic Link Overwrite Flag subfield.
- FIG. 20 shows that ML-CAS is stored in each MPDU, ML-CAS need not be stored in all MPDUs.
- the ML-CAS may be stored only in the first MPDU, or the ML-CAS may be stored in the preamble instead of the MPDU.
- the Duration field is shown in FIG. Information indicative of T 3 ' is stored therein.
- data may be transmitted to AP MLD within the period of T 3 ' on link 1 and link 2 (that is, Information indicating Reverse Direction Grant (RDG) is included.
- RDG Reverse Direction Grant
- the STR non-AP MLD will allow another ( That is, uplink) PPDU transmission can be implemented.
- FIG. 21 shows an operation example of each logical entity in communication section 410 in STR non-AP MLD1 to which PPDU#1-1 and PPDU#1-2 are notified in DL transmission. showing. However, the horizontal axis is the time axis.
- a plurality of MPDUs in a PPDU are collectively described as a PSDU.
- an individual control unit 1 for link 1 and an individual control unit 2 for link 2 are arranged.
- the individual control unit 1 and the individual control unit 2 respectively have PHY Layer #1 and PHY Layer #2 that control the physical layers of link 1 and link 2, and MAC Lower Sublayer #1 that controls data processing of link 1 and link 2. and MAC Lower Sublayer #2 logical entities.
- a Common Entity is further arranged as a logical entity that controls data processing common to the link 1 and the link 2.
- FIG. Information is exchanged between Layer and Layer and between Layer and Entity via SAP.
- parameters to be applied by each MAC Lower Sublayer and PHY Layer are calculated.
- the PHY Layer is composed of the antenna 440, the amplifier 417 in the communication section 410, the wireless interface section 416, the signal processing section 415, and the individual control section 414.
- the MAC Lower Sublayer is the individual data It is composed of a processing unit 414 and a corresponding individual control unit in the communication control unit 411 .
- the components of the PHY Layer and MAC Lower Sublayer need not be limited to these.
- the data transmitted from AP MLD1 on link 1 is received by PHY Layer #1, and after demodulation, the MPDU is passed to MAC Lower Sublayer #1. Similar operations are performed on link 2 as well.
- G-4-1 PHY Layer operation in link 1, information notified between PHY ⁇ MAC
- the arrow indicated by reference number 2101 in FIG. 21 indicates received power (RSSI), number of spatial streams, PPDU
- RSSI received power
- RXVECTOR control information
- each MPDU shows an operation of notifying MAC Lower Sublayer #1 from PHY Layer #1.
- PHY Layer # 1 calculates T1, which is the demodulation operation period, based on the information indicated in the preamble, and performs demodulation. After the demodulation operation is completed, PHY Layer #1 notifies MAC Lower Sublayer # 1 that reception has been completed. end of period T1 ) is determined. An arrow indicated by reference number 2101' in FIG. 21 indicates a reception end notification. In this reception end notification, not only is the reception end notified, but also the idle state of the channel determined by PHY Layer #1 is notified.
- the PHY Layer # 1 does not need to perform the demodulation operation.
- MAC Lower Sublayer #1 Operation of MAC Lower Sublayer in link 1, information notified between MAC Lower ⁇ Common Entity In MAC Lower Sublayer #1, information contained in MPDU after notification indicated by arrow 2101 from PHY Layer #1 is performed is analyzed, and necessary information is notified to the Common Entity.
- the arrow with reference number 2102 in FIG. 21 indicates this notification.
- MAC Lower Sublayer #1 analyzes whether it is indicated in the Support Link Effort subfield in the MPDU that the AP MLD is trying to acquire the transmission right on link 2, and uses this information as a Common entity. to notify.
- MAC Lower Sublayer # 1 analyzes whether permission for another transmission within the period T1 is indicated in the RDG/More PPDU subfield, and uses the information indicated in this field as a Common Entity may be notified.
- the preamble contains Support Link Effort, even if PHY Layer #1 analyzes the information in Support Link Effort and notifies the information to Common Entity via MAC Lower Sublayer #1 good.
- PHY Layer # 2 notifies MAC Lower Sublayer #2 of each MPDU in addition to control information (RXVECTOR) such as received power (RSSI), number of spatial streams, PPDU format, etc., based on information indicated in the preamble.
- RXVECTOR received power (RSSI), number of spatial streams, PPDU format, etc.
- PHY Layer# 2 calculates T3, which is the demodulation operation period, based on the information indicated in the preamble, and performs demodulation. After the demodulation operation is completed, PHY Layer #2 notifies MAC Lower Sublayer # 2 that reception has been completed. end of period T3 ) is determined. An arrow indicated by reference number 2103' in FIG. 21 indicates a reception end notification. In this reception end notification, not only is the reception end notified, but also the idle state of the channel determined by PHY Layer #2 is notified to MAC Lower Sublayer #2.
- the PHY Layer #2 does not need to perform the demodulation operation.
- G-4-4 MAC Lower Sublayer operation on link 1, information notified between MAC Lower ⁇ Common Entity
- MAC Lower Sublayer #2 analyzes the information contained in the MPDU after the notification indicated by arrow 2103 from PHY Layer #2 is performed, and notifies the Common Entity of necessary information.
- the arrow with reference number 2104 in FIG. 21 indicates this notification.
- MAC Lower Sublayer # 2 receives the signal from AP MLD, the information indicated by ML-CAS including Renewal Length (that is, the information indicated in the preamble notified on link 1 information indicating changes), and notifies the Common Entity of these pieces of information.
- MAC Lower Sublayer #2 analyzes whether information in the preamble and ML-CAS already transmitted on link 1 is overwritten in the Basic Link Overwrite Flag subfield, and Notifies the Common Entity of the information to indicate and the information to be changed.
- MAC Lower Sublayer # 2 analyzes whether permission for another transmission within the period T 1 is indicated in the RDG / More PPDU subfield, and the information indicated in this field may be notified to the Common Entity.
- the preamble contains Support Link Effort, even if PHY Layer #1 analyzes the information in Support Link Effort and notifies the information to Common Entity via MAC Lower Sublayer #1 good.
- the Common Entity may notify MAC Lower Sublayer #1 of this information as well. That is, in the RDG/More PPDU subfield in the ML-CAS notified on link 2, for the surplus period caused by shortening the reception period, the STR non-AP MLD1 to AP MLD If information indicating that transmission is permitted is included, the Common Entity notifies the MAC Lower Sublayer #1 or PHY Layer #1 of the information. In FIG. 21, the Common Entity notifies PHY Layer #1 via MAC Lower Sublayer #1, but the Common Entity may notify PHY Layer #1 directly.
- the Common Entity operates according to the processing procedure shown in FIG.
- the description of the operation of the Common Entity that is, the flowchart shown in FIG. 11 is omitted.
- the reception end time notification PHY Layer #1 is directly or indirectly notified of a change in the reception period from the Common Entity, the reception end time changed based on the notified information is indicated by the reference number in FIG. As indicated by an arrow 2107, the MAC Lower Sublayer #1 is notified of the reception end time. At this time, the Common Entity may notify the MAC Lower Sublayer #1 of the idle state of the channel.
- PHY Layer #2 at the time of implementation of the reception end notification of PSDU transmitted on link 2, as indicated by the arrow of reference number 2103' in FIG. to implement the notice of
- the timing of notification from MAC Lower Sublayer #1 to PHY Layer #1 may be after all data (MPDU) has been notified from PHY Layer #1 to MAC Sublayer #1.
- MAC Lower Sublayer #1 when MPDU is notified every octet (byte) from PHY Layer #1 to MAC Lower Sublayer #1, after change of link 1 based on the information indicated by Renewal Length notified from PHY Layer #2 can estimate the transmission data length of Therefore, after PHY Layer #1 notifies MAC Lower Sublayer #1 of the data of the number of octets corresponding to the estimated changed transmission data length, MAC Lower Sublayer #1 sends PHY Layer #1 to PHY Layer #1. Information indicating a request to end the receiving operation may be notified. In response to this request, PHY Layer #1 may notify MAC Lower Sublayer #1 of at least one of reception end time notification and channel availability information notification.
- the Common Entity generates information necessary to generate a response confirmation frame in response to the error judgment for the received MPDU. For example, when the received MPDU is managed by a certain number (sequence number, etc.), it broadens whether or not the MPDU of which number was successfully received, and passes information indicating the recorded information to each MAC Lower Sublayer.
- control information necessary for operating as non-STR non-AP MLD to MAC Lower Sublayer or PHY Layer.
- This control information includes, as non-STR non-AP MLD, information indicating synchronous transmission through a plurality of links and information indicating the length of PPDU generated by the PHY layer.
- each PHY Layer After passing information from each MAC Lower Sublayer to each PHY Layer, each PHY Layer simultaneously transmits PPDU. At this time, the acknowledgment frame and the MPDU representing the received data may be collectively transmitted as one PPDU.
- STR AP MLD transmits using link 1 to non-AP MLD and further transmits using link 2
- STR AP MLD and non- Each AP MLD can implement the following operations (1) to (3).
- the STR AP MLD can realize the operation of notifying the non-AP MLD using the link 2 of the shortened transmission period in the link 1 by using the link 2.
- the MAC layer of the link 2 notifies the MAC layer of the link 1 of the shortened transmission period ⁇ T in the link 1. It is possible to realize the internal operation of (3)
- the non-AP MLD can perform transmissions to the STR AP MLD at least on link 1 during the shortened transmission period ⁇ T.
- the transmission period can be shortened by further transmitting using link 2 while STR AP MLD is transmitting to non-AP MLD using link 1, from non-AP MLD delay of the transmission time of Ack can be prevented, and the transmission efficiency of the system can be improved.
- the present disclosure can be applied, for example, to a wireless network system that performs transmission using multiple links in accordance with IEEE 802.11 TG (Task Group) be, but of course multiple links in accordance with other communication standards It is equally applicable to various types of wireless network systems that transmit using .
- a communication device that performs wireless communication using a plurality of links, Notifying information about a change in the transmission period on the first link due to further transmission using the second link during the transmission period using the first link; Communication device.
- the notification includes information identifying a terminal prohibited from transmitting on the second link and information indicating a transmission prohibited period;
- a communication method for performing wireless communication using a plurality of links initiating transmission on the first link; during the period of transmission using the first link, further initiating transmission using a second link; reporting information about a change in transmission period on the first link due to transmission using the second link; communication method.
- a communication device that performs wireless communication using a plurality of links, When data is received over a second link while data is being received over the first link, information about a change in the transmission period over the first link due to transmission over the second link is received. do, Communication device.
- a MAC layer processing unit that performs processing in the MAC layer for each link and a common data processing unit that performs data processing common to all links, and the MAC layer processing unit of the second link performs the common data processing notifying the MAC layer processing unit of the first link of the information received on the second link through a unit;
- the communication device according to any one of (11) to (15) above.
- a communication method for wireless communication using a plurality of links receiving data on the first link; a step of performing reception processing on the second link when information indicating that the communication partner is attempting to acquire the transmission right on the second link is received on the first link; receiving information about a change in transmission period on the first link due to transmission using the second link when data is received on the second link; controlling communication operations on the first link based on the information received on the second link; communication method.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
第1のリンクを用いた伝送期間中に、さらに第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を通知する、
通信装置である。
第1のリンクで伝送を開始するステップと、
前記第1のリンクを用いた伝送期間中に、さらに第2のリンクを用いて伝送を開始するステップと、
前記第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を通知するステップと、
を有する通信方法である。
第1のリンクでデータ受信中にさらに第2のリンクでデータを受信したときに、前記第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を受信する、
通信装置である。
第1のリンクでデータを受信するステップと、
前記第1のリンクにおいて通信相手が第2のリンクの送信権の獲得を試みていることを示す情報を受信したときに、前記第2のリンクで受信処理を行うステップと、
前記第2のリンクでデータを受信したときに、前記第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を受信するステップと、
前記第2のリンクで受信した前記情報に基づいて、前記第1のリンクにおける通信動作を制御するステップと、
を有する通信方法である。
B.本開示の概要
C.システム構成例
D.装置構成例
E.第1の実施例
F.第2の実施例
G.第3の実施例
H.まとめ
A-1.マルチリンクの導入
限りある周波数帯域でより広い周波数帯域を確保するために、複数の周波数帯を同時に用いて伝送する方法が検討されている(前述)。ここで、周波数帯は「リンク」とも呼ばれる。また、複数の周波数帯、すなわち複数のリンクを同時に用いて伝送できる端末は、MLD(Multi-Link Device)とも呼ばれる。MLDであるAPは「AP MLD(Access Point Multi-Link Device)」と呼ばれ、MLDであるSTAは「non-AP MLD」と呼ばれる。
(2)あるリンクにおいてSTAからAPへアップリンク伝送を実施するとともに、異なるリンクにおいてAPからSTAへダウンリンク伝送を実施すること。
複数のリンクで伝送できる端末と単一の周波数でのみ伝送できる端末が混在することから、周波数毎に送信権を獲得することが考えられる。このため、1台のSTAがAPに対し、例えば5GHz帯ではアップリンク伝送すると同時に6GHz帯ではダウンリンク伝送を実施するケースや、両方のリンクでアップリンク伝送のみ又はダウンリンク伝送のみを実施するケースが考えられる。すなわち、複数のリンクを用いて、リンク毎に送信及び受信を同時に実施すること(STR:Simultaneous Transmit and Receive)、又は、複数のリンク間で送信又は受信のいずれか一方を実施すること(NSTR: non-STR)が想定される。
(2)STA-MLDがリンク毎に異なるアンテナを用いる場合、STA-MLDのアンテナ間の相関や、アンテナに付属するバンドパスフィルタの特性。
non-STR non-AP MLDが、ある1つの端末から、複数のリンクで同時に信号を受信する場合、各リンクの受信信号における受信終了時刻は揃っていなければならない。これは、無線LANにおいて、端末は受信信号に対して受信終了後から規定期間内に受信確認応答(Ack:Acknowledgment)を送信することが一般的な動作であることに依拠する。すなわち、各受信信号の受信終了時刻が揃っていなければ、non-STR non-AP MLDはあるリンクでAckを送信するが、別のリンクでは独立に信号を受信しており、意図せずにSTR(すなわち、Ackの送信と信号の受信を同時に行うこと)が実施されてしまうことを回避するためである。
非特許文献2では、non-AP MLDに対して複数のリンクで伝送する際、以下の2種類を定義している。特にnon-STR non-AP MLDに対する伝送では、各リンクの受信終端時刻(又は送信信号の送信終了時刻)が揃っている必要がある。
- 異なるリンク間で、送信するデータの送信開始時刻を揃えて送信。
(2)非同期送信(Async.Tx:Ansynchronized Transmission)
- 異なるリンク間で、送信するデータの送信開始時刻を揃えず送信。
主に非特許文献1において記述に基づいて、同期送信を実施するための条件について説明する。
非特許文献2では、以下の方法(A)~(C)を用いて非同期送信を実施することが言及されている。但し、先に送信権を獲得できたリンクを「リンク1」(又は、Basic Link)と呼び、後に送信権を獲得できたリンクを「リンク2」(又は、Support Link)と呼ぶ。また、伝送されるデータをPPDUと呼ぶ。
(B)リンク1ではRTS(Request to send)フレーム及びCTS(Clear to send)フレームを通知することでTXOP(Transmission Opportunity)を獲得した後、PPDUを伝送するが、リンク2ではRTSフレーム及びCTSフレームを送信せずにPPDUを送信する。
(C)各リンクでRTSフレーム及びCTSフレームを通知して、リンク毎にTXOPを獲得した後にPPDUを送信する。
本開示では、上記A項で説明した課題を解決するために、STR AP MLDがリンク1を用いてnon-AP MLDに伝送中にさらにリンク2を用いて伝送を行う場合に、以下の(1)~(3)の動作を提案する。
(2)非同期送信された信号をnon-AP MLDが複数のリンクで受信する場合、non-AP MLD内において、リンク2のMAC層からリンク1のMAC層へ、リンク1における短縮された伝送期間ΔTを通知すること。
(3)短縮された伝送期間ΔTに、少なくともリンク1においてnon-AP MLDからSTR AP MLDへの伝送を実施すること。
図3には、本開示が適用される無線ネットワークシステムの構成例を示している。図示の無線ネットワークシステムでは、1台のアクセスポイント(AP MLD)に対し、1台のnon-STR non-AP MLD1に加え、アクセスポイントではない端末であるnon-AP STA2及びnon-AP STA3が接続している。但し、non-AP STAは、non-STR non-AP MLD、STR non-AP MLD、MLDでないnon-AP STAのいずれであってもよい。
図4には、図3に示す無線ネットワークシステムにおいて、リンク1及びリンク2を用いたマルチリンク伝送が可能なMLD(AP MLD又はnon-AP MLD)として動作する通信装置400の構成例を示している。図示の通信装置400は、通信部410と、制御部420と、記憶部430と、アンテナ440を備えている。通信部410は、通信制御部411と、通信記憶部412と、共通データ処理部413と、個別データ処理部414と、信号処理部415と、無線インターフェース部416と、増幅部417を備えている。
図5には、第1の実施例として無線ネットワークシステムにおいて実施される通信シーケンス例を示している。但し、縦軸を時間軸とする。ここでは、図3と同様に、1台のAP MLDと、1台のnon-STR non AP MLDと、1台又は複数台のSTA(以下、「STAs」とする)が存在する無線ネットワークシステムを想定している。
(2)DL(Downlink) Transmission:AP MLDからnon-STR non-AP MLDへのデータ伝送
(3)UL(Uplink) Transmission:non-STR non-AP MLDからAP MLDへのデータ伝送
(4)Ack:上記(2)及び(3)の各データ伝送に対する受信確認応答
図5に示した各伝送について説明する前に、いくつかの留意点について説明しておく。
図5中には、AP MLDとnon-STR non-AP MLDとの伝送におけるシーケンスを示しているが、STAsとの伝送については記載していない。図5では、AP MLD又はnon-STR non-AP MLDがSTAsよりも先に送信権を獲得して各伝送を実施している例を示しているからである。なお、図示していないが、STAsからAP MLDへの伝送、又はAP MLDからSTAsへの伝送は生じてもよい。例えば、Capabilities Exchangeの直後にAP MLDと一部のSTAs間で伝送が発生した後に、DL Transmissionが実施されてよい。
上述したように、DL Transmissionでは、あるリンク(リンク1)での伝送中に他のリンク(リンク2)の伝送が発生する。
図5中にはCapabilities ExchangeはAP MLDからnon-STR non-AP MLDに対して実施されている場合が示されているが、non-STR non-AP MLD及びSTAsに対して同時にCapabilities Exchangeが伝送されてもよい。具体例としてAP MLDが周期的に周囲の複数端末宛てに発信するビーコン信号で実施されてよい。
AP MLD及びnon-STR non-AP MLDは、互いに自端末の能力に関する情報通知(以下、「Capabilities Exchange」とする)を実施する。ここで言う能力は、端末がSTR伝送を実施できるか否か、並びに同時に伝送できるリンク数を指すが、これらだけに限定されるものではない。
DL Transmissionでは、AP MLDからnon-STR non-AP MLDへのデータ伝送を実施する。また、UL Transmissionでは、non-STR non-AP MLDからAP MLDへのデータ伝送を実施する。上述したように、ここではAP MLDがあるリンク(リンク1)で送信権を獲得してデータ伝送を行うが、伝送中に別のリンク(リンク2)でデータ伝送が開始される。但し、各リンクにおける伝送の終了時刻は特定の誤差の範囲内で揃っている。
(2)(1)で許可することが通知され、PPDUを送信する場合、後続にPPDUが存在するか否かを示す情報。
図10には、DL Transmissionにおいて、PPDU♯1-1及びPPDU♯1-2が通知されたnon-STR non-AP MLD1における通信部410内の各論理エンティティの動作例を示している。但し、横軸を時間軸とする。なお、図10ではPPDU内の複数のMPDUをまとめてPSDU(PHY Service Data Unit)と記述している。
図10中の参照番号1001で示す矢印は、プリアンブル内で示される情報に基づいて、受信電力(RSSI:Received Signal Strenght Indicator)や空間ストリーム数、PPDUのフォーマットなどの制御情報(以下、RXVECTORとも呼ぶ)に加え、各MPDUが、PHY Layer#1からMAC Lower Sublayer♯1に通知される動作を示している。
MAC Lower Sublayer♯1では、PHY Layer♯1からの矢印1001で示す通知が実施された後、MPDU内に含まれる情報を解析して、必要な情報をCommon Entityに通知する。図10中の参照番号1002の矢印は、この通知を示している。例えば、MAC Lower Sublayer♯1は、MPDU内のSupport Link Effortサブフィールド内でAP MLDがリンク2で送信権の獲得を試みていることが示されているか否かを解析し、この情報をCommon entityに通知する。また同様に、MAC Lower Sublayer♯1は、RDG/More PPDUサブフィールド内で上記期間T1内における別の伝送の許可が示されているか否かを解析して、このフィールド内で示される情報をCommon Entityに通知するようにしてもよい。
上記E-4-1項で説明したのと同様に、図10中の参照番号1003の矢印で示すように、PHY Layer#2は、プリアンブル内で示される情報に基づいて、受信電力(RSSI)や空間ストリーム数、PPDUのフォーマットなどの制御情報(RXVECTOR)に加え、各MPDUを、MAC Lower Sublayer♯2に通知する。
MAC Lower Sublayer♯2では、PHY Layer♯2からの矢印1003で示す通知が実施された後、MPDU内に含まれる情報を解析して、必要な情報をCommon Entityに通知する。図10中の参照番号1004の矢印は、この通知を示している。例えば、MAC Lower Sublayer♯2は、AP MLDからの信号を受信していること、Renewal Lengthを含むML-CASで示された情報(すなわち、リンク1で通知されたプリアンブル内で示された情報の変更分を示す情報)を解析して、これらの情報をCommon Entityに通知する。例えば、MAC Lower Sublayer♯2は、Basic Link Overwrite Flagサブフィールド内でリンク1に既に伝送されているプリアンブルやML-CAS内の情報を上書きすることが示されているか否かを解析し、これを示す情報と、変更される情報をCommon Entityに通知する。また、同様に、MAC Lower Sublayer#2は、RDG/More PPDUサブフィールド内で上記期間T1内における別の伝送の許可が示されているか否かを解析して、このフィールド内で示される情報をCommon Entityに通知するようにしてもよい。
Common Entityは、MAC Lower Sublayer♯2からの通知に基づいて、図10中の参照番号1005及び1006の矢印で示すように、個別制御部1に含まれるリンク1のPHY Layer♯1又はMAC Lower Sublayer♯1に対し、少なくとも変更された受信期間(又は受信終了時刻)を示す情報を通知する。このとき、Common Entityは各リンクのPHY LayerからMAC Lower Sublayerを介して以下の(1)及び(2)の情報が通知されている。
(2)リンク1でプリアンブルによって通知された情報を変更することが示された情報
PHY Layer♯1は、Common Entityから直接又は間接的に受信期間の変更が通知されると、通知された情報に基づいて変更された受信終了時刻に、図10中の参照番号1007の矢印で示すように、MAC Lower Sublayer♯1に対して受信終了時刻の通知を実施する。このとき、PHY Layer♯1は、MAC Lower Sublayer♯1に対してチャネルの空き状態の通知を実施してもよい。
Common Entityは、各PHY Layerから受信終了時刻の通知を受け取ると、図10中の参照番号1008の矢印で示すMAC Lower Sublayerに対する動作として、以下の(1)~(3)を実施する。
Common Entityは、受信したMPDUに対する誤り判定に対し、応答確認フレームを生成するのに必要な情報を生成する。例えば受信したMPDUがある番号(シーケンス番号など)によって管理されている場合、どの番号のMPDUが正常に受信できたか否かを広くし、記録された情報を示す情報を各MAC Lower Sublayerに引き渡す。
Common Entityは、non-STR non-AP MLDとして動作するために必要な制御情報を、MAC Lower Sublayer又はPHY Layerに引き渡す。この制御情報には、non-STR non-AP MLDとして、複数のリンクにより同期送信することを示す情報や、PHY Layerで生成するPPDUの長さを示す情報が含まれる。
Common Entityは、各MAC Lower Sublayer又は各PHY Layerに、送信するデータに相当するMPDUの情報を引き渡す(図10中の矢印1009で示す動作に相当)。このとき、送信するデータ長はリンク1における期間T1を超えない範囲であり、図10中ではT2´として示している。また、AP MLDから直前に通知されたAC Constraintで示された情報に従って、データの種別を制限するようにしてもよい。例えば、音声通信のように優先されるデータのみの送信が許容されている場合には、Common Entityは、許容されているデータのみをMAC Lower Sublayer又はPHY Layerに引き渡し、これらのデータのみをPHY Layerが送信するように制御する。
上記E項で説明した第1の実施例では、余剰期間においてnon-STR non-AP MLD1がリンク1とリンク2を同時に用いるマルチリンク伝送の方法について説明した。これに対し、このF項で説明する第2の実施例では、余剰期間において、non-STR non-AP MLD1はリンク1のみを用いて伝送する一方、リンク2ではその期間又はそれ以上の期間、他のSTA(図12に示す例では、STA2)が送信する。
図13には、DL Transmission及びUL Transmissionの具体的な動作例を詳細に示している。但し、横軸を時間軸とする。図8中では、AP MLDがnon-STR non-AP MLD1に対しリンク1で送信し、その直後にリンク2でも送信を実施する。これに対し、図13中では、AP MLDは、リンク2でAP MLDがPPDU♯1-2を送信した後に、他の端末に対してリンク2の送信権の開放を示すEnhanced CF(Contention Free)-Endを通知する。
図14には、Enhanced CF-Endで通知されるフレームの構成例を示している。Enhanced CF-Endは、該当リンクにおいて、該当リンクを含むマルチリンク伝送の通信相手に対して、送信禁止期間を通知するためのフレームであり、このフレームを送信することによって、他の端末に対して該当リンクの送信権の開放を示すことができる。
図15には、DL Transmissionにおいて、PPDU♯1-1及びPPDU♯1-2が通知されたnon-STR non-AP MLD1における通信部410内の動作例を示している。但し、横軸を時間軸とする。なお、図15ではPPDU内の複数のMPDUをまとめてPSDUと記述している。
Common Entityは、受信したMPDUに対する誤り判定に対し、応答確認フレームを生成するのに必要な情報を生成する。例えば受信したMPDUがある番号(シーケンス番号など)によって管理されている場合、どの番号のMPDUが正常に受信できたか否かを広くし、記録された情報を示す情報を各MAC Lower Sublayerに引き渡す。
Common Entityは、non-STR non-AP MLDとして動作するために必要な制御情報を、MAC Lower Sublayer又はPHY Layerに引き渡す。この制御情報には、non-STR non-AP MLDとして、複数のリンクにより同期送信することを示す情報や、PHY Layerで生成するPPDUの長さを示す情報が含まれる。
Common Entityは、各MAC Lower Sublayer又は各PHY Layerに、送信するデータに相当するMPDUの情報を引き渡す(図15中の矢印1509で示す動作に相当)。このとき、送信するデータ長はリンク1における期間T1を超えない範囲であり、図15中ではT2´として示している。
Enhanced CF-Endが通知された他の端末は、Enhanced CF-Endフレーム内のSTA IDフィールドで指定された端末への、Prohibited periodで指定された送信禁止期間にわたる送信を差し控える。
図13に示す例では、AP MLDは、リンク1及びリンク2を用いたマルチリンク伝送を終了後に、リンク2でEnhanced CF-Endフレームを送信する。AP MLDは、このEnhanced CF-Endフレームで、non-STR non-AP MLD1への送信禁止期間(T3´-T3)を通知する。
リンク2でEnhanced CF-Endが通知された端末は、non-STR non-AP MLD1以外の端末に対して送信を実施する。図13中では、AP MLD以外の端末すなわちSTA3がリンク2で送信することを示しているが、AP MLDがリンク2においてnon-STR non-AP MLD以外の端末への送信を実施してもよい。
上記の第1及び第2の実施例では、DL Transmissionの受信端末がnon-STR non-AP MLDである場合について説明したが、第3の実施例では、DL Transmissionの受信端末がSTR non-AP MLDである場合について説明する。したがって、第3の実施例では、各リンクで受信端末に送信されるPPDUの送信終了時刻は揃っている必要がない。
(2)DL Transmission:AP MLDからSTR non-AP MLDへのデータ伝送
(3)UL Transmission:STR non-AP MLDからAP MLDへのデータ伝送
(4)Ack:上記(2)及び(3)の各データ伝送に対する受信確認応答
各伝送について説明する前に、いくつかの留意点について説明しておく。
図16中には、AP MLDとSTR non-AP MLDとの伝送におけるシーケンスを示しているが、STAsとの伝送については記載していない。図16では、AP MLD又はSTR non-AP MLDがSTAsよりも先に送信権を獲得して各伝送を実施している例を示しているからである。なお、図示していないが、STAsからの伝送、又はSTAsへの伝送は生じてもよい。例えば、Capabilities Exchangeの直後にAP MLDと一部のSTAs間で伝送が発生した後、DL Transmissionが実施されてよい。
上述したように、DL Transmissionでは、あるリンク(リンク1)での伝送中に他のリンク(リンク2)の伝送が発生する。
図16中にはCapabilities ExchangeはAP MLDからSTR non-AP MLDに対して実施されている場合が示されているが、STR non-AP MLD及びSTAsに対して同時に伝送されてもよい。具体例としてAP MLDが周期的に周囲の複数端末宛てに発信するビーコン信号で実施されてよい。
AP MLD及びSTR non-AP MLDは、互いに自端末の能力に関する情報通知(Capabilities Exchange)を実施する。ここで言う能力は、端末がSTR伝送を実施できるか否か、並びに同時に伝送できるリンク数を指すが、これらだけに限定されるものではない。Capability Exchangeは、例えば各端末が周期的に発信するビーコン信号や、ビーコン信号後に端末間で接続を確立するための情報通知(Association)に含まれて実施されてよい。
DL TransmissionではAP MLDからSTR non-AP MLDへのデータ伝送を実施し、UL TransmissionではSTR non-AP MLDからAP MLDへのデータ伝送を実施する。上述したように、ここではAP MLDがあるリンク(リンク1)で送信権を獲得してデータ伝送を行うが、伝送中に別のリンク(リンク2)でデータ伝送が開始される。
(2)(1)で許可することが通知され、PPDUを送信する場合、後続にPPDUが存在するか否かを示す情報。
図21には、DL Transmissionにおいて、PPDU♯1-1及びPPDU♯1-2が通知されたSTR non-AP MLD1における通信部410内の各論理エンティティの動作例を示している。但し、横軸を時間軸とする。なお、図21ではPPDU内の複数のMPDUをまとめてPSDUと記述している。
図21中の参照番号2101で示す矢印は、プリアンブル内で示される情報に基づいて、受信電力(RSSI)や空間ストリーム数、PPDUのフォーマットなどの制御情報(RXVECTOR)に加え、各MPDUが、PHY Layer#1からMAC Lower Sublayer♯1に通知される動作を示している。
MAC Lower Sublayer♯1では、PHY Layer♯1からの矢印2101で示す通知が実施された後、MPDU内に含まれる情報を解析して、必要な情報をCommon Entityに通知する。図21中の参照番号2102の矢印は、この通知を示している。例えば、MAC Lower Sublayer♯1は、MPDU内のSupport Link Effortサブフィールド内にAP MLDがリンク2で送信権の獲得を試みていることが示されているか否かを解析し、この情報をCommon entityに通知する。また同様に、MAC Lower Sublayer♯1はRDG/More PPDUサブフィールド内で上記期間T1内における別の伝送の許可が示されているか否かを解析して、このフィールド内で示される情報をCommon Entityに通知するようにしてもよい。
上記G-4-1項で説明したのと同様に、図21中の参照番号2103の矢印で示すように、PHY Layer#2は、プリアンブル内で示される情報に基づいて、受信電力(RSSI)や空間ストリーム数、PPDUのフォーマットなどの制御情報(RXVECTOR)に加え、各MPDUを、MAC Lower Sublayer♯2に通知する。
Common Entityは、MAC Lower Sublayer♯2からの通知に基づいて、図21中の参照番号2105及び2106の矢印で示すように、個別制御部1に含まれるリンク1のPHY Layer♯1又はMAC Lower Sublayer♯1に対し、少なくとも、変更された受信期間(又は受信終了時刻)を示す情報を通知する。このとき、Common Entityは各リンクのPHY LayerからMAC Lower Sublayerを介して以下の(1)及び(2)の情報が通知されている。
(2)リンク1でプリアンブルによって通知された情報を変更することが示された情報
PHY Layer♯1は、Common Entityから直接又は間接的に受信期間の変更が通知されると、通知された情報に基づいて変更された受信終了時刻に、図21中の参照番号2107の矢印で示すように、MAC Lower Sublayer♯1に対して受信終了時刻の通知を実施する。このとき、Common Entityは、MAC Lower Sublayer♯1に対してチャネルの空き状態の通知を実施してもよい。
Common Entityは、各PHY Layerから受信終了時刻の通知を受け取ると、図21中の参照番号2108の矢印で示すMAC Lower Sublayerに対する動作として、以下の(1)~(3)を実施する。
Common Entityは、受信したMPDUに対する誤り判定に対し、応答確認フレームを生成するのに必要な情報を生成する。例えば受信したMPDUがある番号(シーケンス番号など)によって管理されている場合、どの番号のMPDUが正常に受信できたか否かを広くし、記録された情報を示す情報を各MAC Lower Sublayerに引き渡す。
Common Entityは、non-STR non-AP MLDとして動作するために必要な制御情報を、MAC Lower Sublayer又はPHY Layerに引き渡す。この制御情報には、non-STR non-AP MLDとして、複数のリンクにより同期送信することを示す情報や、PHY Layerで生成するPPDUの長さを示す情報が含まれる。
Common Entityは、各MAC Lower Sublayer又は各PHY Layerに、送信するデータに相当するMPDUの情報を引き渡す(図21中の矢印2109で示す動作に相当)。このとき、送信するデータ長はリンク1における期間T1を超えない範囲であり、図21中ではT2´として示している。また、AP MLDから直前に通知されたAC Constraintで示された情報に従って、データの種別を制限するようにしてもよい。例えば、音声通信のように優先されるデータのみの送信が許容されている場合には、Common Entityは、許容されているデータのみをMAC Lower Sublayer又はPHY Layerに引き渡し、これらのデータのみをPHY Layerが送信するように制御する。
各実施例で説明したように、本開示によれば、STR AP MLDがリンク1を用いてnon-AP MLDに伝送中にさらにリンク2を用いて伝送を行う場合、STR AP MLD及びnon-AP MLDはそれぞれ以下の(1)~(3)の動作を実施することができる。
(2)non-AP MLDは、AP MLDから非同期送信された信号を複数のリンクで受信する場合、リンク2のMAC層からリンク1のMAC層へ、リンク1における短縮された伝送期間ΔTを通知するという内部動作を実現することができる。
(3)non-AP MLDは、短縮された伝送期間ΔTに、少なくともリンク1においてSTR AP MLDへの伝送を実施することができる。
第1のリンクを用いた伝送期間中に、さらに第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を通知する、
通信装置。
上記(1)に記載の通信装置。
上記(1)又は(2)のいずれかに記載の通信装置。
上記(1)乃至(3)のいずれかに記載の通信装置。
上記(1)乃至(4)のいずれかに記載の通信装置。
上記(1)乃至(5)のいずれかに記載の通信装置。
上記(6)に記載の通信装置。
上記(6)に記載の通信装置。
上記(8)に記載の通信装置。
第1のリンクで伝送を開始するステップと、
前記第1のリンクを用いた伝送期間中に、さらに第2のリンクを用いて伝送を開始するステップと、
前記第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を通知するステップと、
を有する通信方法。
第1のリンクでデータ受信中にさらに第2のリンクでデータを受信したときに、前記第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を受信する、
通信装置。
上記(11)に記載の通信装置。
上記(11)又は(12)のいずれかに記載の通信装置。
上記(11)乃至(13)のいずれかに記載の通信装置。
上記(11)乃至(14)のいずれかに記載の通信装置。
上記(11)乃至(15)のいずれかに記載の通信装置。
上記(16)に記載の通信装置。
上記(11)乃至(17)のいずれかに記載の通信装置。
上記(11)乃至(18)のいずれかに記載の通信装置。
第1のリンクでデータを受信するステップと、
前記第1のリンクにおいて通信相手が第2のリンクの送信権の獲得を試みていることを示す情報を受信したときに、前記第2のリンクで受信処理を行うステップと、
前記第2のリンクでデータを受信したときに、前記第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を受信するステップと、
前記第2のリンクで受信した前記情報に基づいて、前記第1のリンクにおける通信動作を制御するステップと、
を有する通信方法。
412…通信記憶部、413…共通データ処理部
414…個別データ処理部、415…信号処理部
416…無線インターフェース部、417…増幅部、420…制御部
430…記憶部、440…アンテナ
Claims (20)
- 複数のリンクを用いて無線通信を行う通信装置であって、
第1のリンクを用いた伝送期間中に、さらに第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を通知する、
通信装置。 - 前記第2のリンクを使って、伝送相手に前記情報を通知する、
請求項1に記載の通信装置。 - 前記第2のリンクを使って伝送するデータフレームを構成する伝送単位毎に前記情報を記載する、
請求項1に記載の通信装置。 - 前記第1のリンクを使って伝送するデータフレームを構成する伝送単位毎に、前記第2のリンクにおいて送信権の獲得を試みているか否かを示す情報を記載する、
請求項1に記載の通信装置。 - 前記第2のリンクを使って伝送するデータフレームを構成する伝送単位毎に、前記第1のリンクで伝送するフレーム中に記載された少なくとも伝送期間に関する情報が変更したか否かを示す情報と、前記第1のリンクにおける伝送期間の変更分に関する前記情報を記載する、
請求項1に記載の通信装置。 - 前記第1のリンクにおける元の伝送期間内で、前記第1のリンク及び前記第2のリンクのうち少なくとも一方を用いた別の伝送を実施する、
請求項1に記載の通信装置。 - 前記複数のリンクを用いた通信相手に対して、前記第1のリンクにおける元の伝送期間内で前記第1のリンク及び前記第2のリンクのうち少なくとも一方を用いた伝送を許可する、
請求項6に記載の通信装置。 - 他の端末に対して、前記第1のリンクにおける元の伝送期間内で前記第2のリンクの開放を通知する、
請求項6に記載の通信装置。 - 前記通知は、前記第2のリンクで送信を禁止する端末を識別する情報及び送信禁止期間を示す情報を含む、
請求項8に記載の通信装置。 - 複数のリンクを用いて無線通信を行う通信方法であって、
第1のリンクで伝送を開始するステップと、
前記第1のリンクを用いた伝送期間中に、さらに第2のリンクを用いて伝送を開始するステップと、
前記第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を通知するステップと、
を有する通信方法。 - 複数のリンクを用いて無線通信を行う通信装置であって、
第1のリンクでデータ受信中にさらに第2のリンクでデータを受信したときに、前記第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を受信する、
通信装置。 - 前記情報を前記第2のリンクで受信する、
請求項11に記載の通信装置。 - 前記第2のリンクで受信した前記情報に基づいて、前記第1のリンクにおける通信動作を制御する、
請求項11に記載の通信装置。 - 前記第1のリンクにおいて、通信相手が前記第2のリンクの送信権の獲得を試みていることを示す情報を受信したときに、前記第2のリンクで受信処理を行う、
請求項11に記載の通信装置。 - 前記第1のリンクで伝送するフレーム中に記載された少なくとも伝送期間に関する情報が変更したか否かを示す情報と、前記第1のリンクにおける伝送期間の変更分に関する前記情報を前記第2のリンクで受信して、前記第1のリンクにおける通信動作を制御する、
請求項11に記載の通信装置。 - リンク毎にMAC層における処理を行うMAC層処理部と、すべてのリンクに共通したデータ処理を行う共通データ処理部を備え、前記第2のリンクのMAC層処理部は前記共通データ処理部を通じて前記第2のリンクで受信した前記情報を前記第1のリンクのMAC層処理部に通知する、
請求項11に記載の通信装置。 - 前記第2のリンクのMAC層処理部が、前記第1のリンクで伝送するフレーム中に記載された少なくとも伝送期間に関する情報が変更したか否かを示す情報と、前記第1のリンクにおける伝送期間の変更分に関する前記情報を前記第2のリンクで受信して、前記共通データ処理部を通じて前記第1のリンクのMAC層処理部に通知する、
請求項16に記載の通信装置。 - 前記通信装置が前記複数のリンク間で送信又は受信のいずれか一方しか実施できない場合に、前記複数のリンク間で送信開始時刻を揃えない非同期伝送の受信が可能か否かに関する情報を、前記複数のリンクを用いた通信相手に通知する、
請求項11に記載の通信装置。 - 送信と受信を同時にできないが非同期伝送の受信が可能となるリンクの組み合わせに関する情報を、前記複数のリンクを用いた通信相手に通知する、
請求項11に記載の通信装置。 - 複数のリンクを用いて無線通信を行う通信方法であって、
第1のリンクでデータを受信するステップと、
前記第1のリンクにおいて通信相手が第2のリンクの送信権の獲得を試みていることを示す情報を受信したときに、前記第2のリンクで受信処理を行うステップと、
前記第2のリンクでデータを受信したときに、前記第2のリンクを用いて伝送を行うことによる前記第1のリンクにおける伝送期間の変更分に関する情報を受信するステップと、
前記第2のリンクで受信した前記情報に基づいて、前記第1のリンクにおける通信動作を制御するステップと、
を有する通信方法。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18/546,976 US20240129985A1 (en) | 2021-02-26 | 2021-12-28 | Communication device and communication method |
KR1020237026107A KR20230150265A (ko) | 2021-02-26 | 2021-12-28 | 통신 장치 및 통신 방법 |
JP2023502125A JPWO2022181050A1 (ja) | 2021-02-26 | 2021-12-28 | |
EP21928143.3A EP4301064A1 (en) | 2021-02-26 | 2021-12-28 | Communication device and communication method |
CN202180094158.8A CN116889060A (zh) | 2021-02-26 | 2021-12-28 | 通信装置和通信方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021-030010 | 2021-02-26 | ||
JP2021030010 | 2021-02-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022181050A1 true WO2022181050A1 (ja) | 2022-09-01 |
Family
ID=83048818
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/048889 WO2022181050A1 (ja) | 2021-02-26 | 2021-12-28 | 通信装置及び通信方法 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20240129985A1 (ja) |
EP (1) | EP4301064A1 (ja) |
JP (1) | JPWO2022181050A1 (ja) |
KR (1) | KR20230150265A (ja) |
CN (1) | CN116889060A (ja) |
WO (1) | WO2022181050A1 (ja) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020195029A1 (ja) * | 2019-03-27 | 2020-10-01 | ソニー株式会社 | 通信装置及び通信方法 |
-
2021
- 2021-12-28 EP EP21928143.3A patent/EP4301064A1/en active Pending
- 2021-12-28 WO PCT/JP2021/048889 patent/WO2022181050A1/ja active Application Filing
- 2021-12-28 CN CN202180094158.8A patent/CN116889060A/zh active Pending
- 2021-12-28 US US18/546,976 patent/US20240129985A1/en active Pending
- 2021-12-28 KR KR1020237026107A patent/KR20230150265A/ko unknown
- 2021-12-28 JP JP2023502125A patent/JPWO2022181050A1/ja active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020195029A1 (ja) * | 2019-03-27 | 2020-10-01 | ソニー株式会社 | 通信装置及び通信方法 |
Non-Patent Citations (4)
Title |
---|
LIWEN CHU (NXP): "Multiple Link Operation Follow Up", IEEE DRAFT; 11-20-0487-05-00BE-MULTIPLE-LINK-OPERATION-FOLLOW-UP, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 EHT; 802.11be, no. 5, 24 April 2020 (2020-04-24), Piscataway, NJ USA , pages 1 - 15, XP068167623 * |
TAEWON SONG (LG ELECTRONICS): "Multi-link Acknowledgement Follow Up", IEEE DRAFT; 11-20-0012-03-00BE-MULTI-LINK-ACKNOWLEDGEMENT-FOLLOW-UP, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11 EHT; 802.11be, no. 3, 23 April 2020 (2020-04-23), Piscataway, NJ USA , pages 1 - 12, XP068172761 * |
YONGHO SEOK ET AL.: "Proposed Draft Text for MLO Multi-Link Channel Access: PPDU End Time Alignment", IEEE802.11-20/1271R8, 9 September 2020 (2020-09-09) |
ZHOU LAN ET AL.: "MLO a-synchronize and synchronize operation discussions", IEEE 802.11-20/291R1, 20 January 2020 (2020-01-20) |
Also Published As
Publication number | Publication date |
---|---|
CN116889060A (zh) | 2023-10-13 |
JPWO2022181050A1 (ja) | 2022-09-01 |
US20240129985A1 (en) | 2024-04-18 |
EP4301064A1 (en) | 2024-01-03 |
KR20230150265A (ko) | 2023-10-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10687314B2 (en) | Data transmission method and device in wireless communication system | |
AU2015404488B2 (en) | Method for transmitting data in wireless communication system and apparatus therefor | |
JP5518952B2 (ja) | 高速媒体アクセス制御および直接のリンクプロトコル | |
JP5149224B2 (ja) | 高速媒体アクセス制御 | |
JP5175314B2 (ja) | 無線基地局の信頼性強化のためのアーキテクチャ | |
KR101948082B1 (ko) | 다중 사용자 다중 안테나 기반 무선통신 시스템에서 데이터 보호 방법 | |
US20170311310A1 (en) | Method and device for allocating uplink transmission resource on basis of buffer status information in wireless lan | |
US20060268886A1 (en) | Wireless communication method and system for enhancing the capability of WLAN control frames | |
EP3606271B1 (en) | Method for transmitting frame on basis of multiple channelized channels in wireless lan system, and wireless terminal using same | |
CN105493608B (zh) | 在无线局域网中发送数据的方法和设备 | |
US10128988B2 (en) | Method and apparatus for reporting information about transmission failure frame | |
JP2012519426A (ja) | 送信機会において情報をピギーバックすること | |
US10004109B2 (en) | Method and apparatus for recovering data unit in wireless communication system | |
WO2022181050A1 (ja) | 通信装置及び通信方法 | |
JP2023101035A (ja) | 通信装置、通信方法 | |
WO2022209212A1 (ja) | 通信装置 | |
WO2023033184A1 (ja) | 通信装置および通信方法 | |
US20210235447A1 (en) | Method for transmitting frame on basis of plurality of channels in wireless lan system and wireless terminal using same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21928143 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2023502125 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18546976 Country of ref document: US Ref document number: 202180094158.8 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021928143 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021928143 Country of ref document: EP Effective date: 20230926 |