Patent Application
20230122740
The present disclosure relates to a wireless local area network (wireless LAN) communication technique, and more particularly, to a technique for data transmission and reception in a device not supporting a simultaneous transmit and receive (STR).
Recently, as the spread of mobile devices expands, a wireless local area network technology capable of providing fast wireless communication services to mobile devices is in the spotlight. The wireless local area network (wireless LAN) technology may be a technology that supports mobile devices such as smart phones, smart pads, laptop computers, portable multimedia players, embedded devices, and the like to wirelessly access the Internet based on wireless communication technology.
The standards using the wireless LAN technology are being standardized as IEEE802.11 standards mainly in the Institute of Electrical and Electronics Engineers (IEEE). The initial version of the IEEE 802.11 standard can support a communication speed of 1 to 2 megabits per second (Mbps). The later versions of the IEEE 802.11 standard are being standardized in the direction of improving the communication speed.
The revised version of the IEEE 802.11a standard can support a communication speed of up to 54 Mbps using an orthogonal frequency division multiplexing (OFDM) scheme in a 5 giga hertz (GHz) band. The IEEE 802.11b standard utilizes a direct sequence spread spectrum (DSSS) scheme to support a communication speed of up to 11 Mbps in a 2.4 GHz band where the initial version operates.
The IEEE 802.11n standard supporting a high throughput (HT) wireless LAN technology has been developed due to the demand for higher speed. The IEEE 802.11n standard may support the OFDM scheme. By supporting channel bandwidth expansion techniques and multiple input multiple output (MIMO) techniques in the IEEE 802.11n standard, the maximum communication speeds in the 2.4 GHz band and the 5 GHz band can be improved. For example, the IEEE 802.11n standard can support a communication speed of up to 600 Mbps by using 4 spatial streams and a 40 MHz bandwidth.
As the above-described wireless LAN technologies have been developed and spread, applications using the wireless LAN technologies have been diversified, and a demand for a wireless LAN technology supporting a higher throughput has arisen. Accordingly, a frequency bandwidth (e.g., ‘maximum 160 MHz bandwidth’ or ‘80+80 MHz bandwidth’) used in the IEEE 802.11ac standard has been expanded, and the number of supported spatial streams has also increased. The IEEE 802.11ac standard may be a very high throughput (VHT) wireless LAN technology supporting a high throughput of 1 gigabit per second (Gbps) or more. The IEEE 802.11ac standard can support downlink transmission for multiple stations by utilizing the MIMO techniques.
As the demand for wireless LAN technologies further increases, the IEEE 802.11ax standard has been developed to increase a frequency efficiency in a dense environment. In the IEEE 802.11ax standard, a communication procedure may be performed using multi-user (MU) orthogonal frequency division multiple access (OFDMA) techniques. In the IEEE 802.11ax standard, uplink communication may be performed using the MU MIMO techniques and/or OFDMA techniques.
As applications requiring higher throughput and applications requiring real-time transmission occur, the IEEE 802.11be standard, which is an extreme high throughput (EHT) wireless LAN technology, is being developed. The goal of the IEEE 802.11be standard may be to support a high throughput of 30 Gbps. The IEEE 802.11be standard may support techniques for reducing a transmission latency. In addition, the IEEE 802.11be standard can support a more expanded frequency bandwidth (e.g., 320 MHz bandwidth), multi-link transmission and aggregation operations including multi-band operations, multiple access point (AP) transmission operations, and/or efficient retransmission operations (e.g., hybrid automatic repeat request (HARQ) operations).
However, since the multi-link operation is an operation that is not defined in the existing WLAN standard, it may be necessary to define detailed operations according to the environment in which the multi-link operation is performed. In particular, when two or more bands performing the multi-link operation are close to each other, simultaneous transmission and reception operations through a multi-link may not be performed within one device due to signal interference between adjacent channels (e.g., adjacent links). In particular, when a signal interference level between the adjacent channels is equal to or greater than a specific level, a backoff operation for transmission in another link may not be performed due to the interference while performing a transmission operation in one link. Therefore, in the above-described situations, a method for updating parameter(s) for multi-link operations and a method for transmitting/receiving data based on the updated parameter(s) may be required.
Meanwhile, the technologies that are the background of the present disclosure are written to improve the understanding of the background of the present disclosure and may include content that is not already known to those of ordinary skill in the art to which the present disclosure belongs.
The present disclosure is directed to providing a method and an apparatus for data transmission/reception in a device not supporting a simultaneous transmit and receive (STR) in a wireless LAN system supporting a multi-link.
An operation method of a first device, according to a first embodiment of the present disclosure for achieving the above-described objectives, may comprise: performing an operation for receiving a first frame from a second device in a first link in the multi-link; performing a channel access operation to transmit a second frame to the second device in a second link in the multi-link during a period corresponding to a reception period of the first frame; and transmitting the second frame to the second device in the second link after the channel access operation is completed and the reception period ends.
A backoff counter value may be maintained at 0 from an end time of the channel access operation to an end time of the reception period.
The operation method may further comprise performing a channel sensing operation in the second link from an end time of the channel access operation to an end time of the reception period. When a channel state is determined to be in an idle state as a result of the channel sensing operation, the second frame is transmitted in the second link.
When a channel state of the second link is a busy state at an end time of the reception period, the second frame may be transmitted when the channel state is in an idle state for a preset period from an end time of the busy state.
The channel access operation may be performed when a channel state is in an idle state for a preset period in the second link.
A period in which a transmission operation is stopped may be configured in the second link for a period corresponding to a reception period of the first frame, and a transmission operation to the second device may be stopped in the period in which the transmission operation is stopped.
The second device may not support simultaneous transmit and receive (STR) operations.
A packet associated with the second frame may be input to an additional queue of the first device, a transmission operation for the packet located in the additional queue may not be performed before the reception period ends, and the packet located in the additional queue may have a transmission priority after the reception period ends.
An operation method of a first device, according to a second embodiment of the present disclosure for achieving the above-described objective, may comprise: performing a channel access operation to transmit a second frame to a second device in a second link in the multi-link; starting a reception operation for receiving a first frame from the second device in a first link in the multi-link while performing the channel access operation; and transmitting the second frame to the second device in the second link after the channel access operation is completed and a reception period of the first frame ends.
When the reception operation is started in the first link, the channel access operation may be continuously performed in the second link.
A backoff counter value may be maintained at 0 from an end time of the channel access operation to an end time of the reception period.
When the reception operation is started in the first link, the channel access operation may be stopped in the second link, and the channel access operation may be resumed before the reception period ends.
The resumed channel access operation may be performed according to a remaining backoff counter value of the stopped channel access operation.
A period in which a transmission operation is stopped may be configured in the second link for a period corresponding to a reception period of the first frame, and a transmission operation to the second device may be stopped in the period in which the transmission operation is stopped.
A first device according to a third embodiment of the present disclosure for achieving the above-described objective may comprise: a processor; a first node supporting communications in a first link in the multi-link according to control of the processor; a second node supporting communications in a second link in the multi-link according to control of the processor; and a memory storing one or more instructions executable by the processor. The one or more instructions cause the first node to perform an operation for receiving a first frame from a second device in a first link in the multi-link. The one or more instructions also cause the second node to perform a channel access operation to transmit a second frame to the second device in a second link in the multi-link during a period corresponding to a reception period of the first frame. The one or more instructions also cause the second node to transmit the second frame to the second device in the second link after the channel access operation is completed and the reception period ends.
A backoff counter value may be maintained at 0 from an end time of the channel access operation to an end time of the reception period.
The one or more instructions may cause the second node to perform a channel sensing operation in the second link from an end time of the channel access operation to an end time of the reception period. When a channel state is determined to be in an idle state as a result of the channel sensing operation, the second frame is transmitted in the second link.
When a channel state of the second link is a busy state at an end time of the reception period, the second frame may be transmitted when the channel state is in an idle state for a preset period from an end time of the busy state.
The channel access operation may be performed when a channel state is in an idle state for a preset period in the second link.
A period in which a transmission operation is stopped may be configured in the second link for a period corresponding to a reception period of the first frame, and a transmission operation to the second device may be stopped in the period in which the transmission operation is stopped.
According to the present disclosure, communications between devices (e.g., STA or AP) may be performed using a multi-link. When some links (e.g., some channels) among multiple links are adjacent to each other so that a simultaneous transmit and receive (STR) operation cannot be performed, and a first STA performs transmission using a first link among the multiple links, an AP may not be able to transmit a frame to a second STA using a second link among the multiple links. In this case, the AP may perform a channel access operation for transmission of the frame in the second link in advance and may transmit the frame to the second STA in the second link when the transmission of the first STA in the first link is completed. Accordingly, transmission efficiency can be improved.
Since the embodiments of the present disclosure may be variously modified and may have several forms, specific embodiments are shown in the accompanying drawings and are described in the detailed description. It should be understood, however, that it is not intended to limit the present disclosure to the specific embodiments. On the contrary, the present disclosure is intended to cover all modifications and alternatives falling within the spirit and scope of the present disclosure.
Relational terms such as first, second, and the like may be used for describing various elements, but the elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first component may be named as a second component without departing from the scope of the present disclosure, and the second component may also be similarly named as the first component. The term “and/or” means any one or a combination of a plurality of related and described items.
When it is mentioned that a certain component is “coupled with” or “connected with” another component, it should be understood that the certain component is directly “coupled with” or “connected with” to the other component or a further component may be disposed therebetween. In contrast, when it is mentioned that a certain component is “directly coupled with” or “directly connected with” another component, it should be understood that a further component is not disposed therebetween.
The terms used in the present disclosure are only used to describe specific embodiments and are not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present disclosure, terms such as ‘comprise’ or ‘have’ are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, but it should be understood that the terms do not preclude existence or addition of one or more features, numbers, steps, operations, components, parts, or combinations thereof.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. Terms that are generally used and have been in dictionaries should be construed as having meanings matched with contextual meanings in the art. In this description, unless defined clearly, terms are not necessarily construed as having formal meanings.
Hereinafter, forms or embodiments of the present disclosure are described in detail with reference to the accompanying drawings. In describing the embodiments, to facilitate the entire understanding of the disclosure, like numbers refer to like elements throughout the description of the figures. The repetitive description thereof has been omitted.
In the following, a wireless communication system to which embodiments according to the present disclosure are applied is described. The wireless communication system to which the embodiments according to the present disclosure are applied is not limited to the contents described below, and the embodiments according to the present disclosure can be applied to various wireless communication systems. A wireless communication system may be referred to as a ‘wireless communication network’.
As shown in
The communication node 100 may include at least one processor 110, a memory 120, and a plurality of transceivers 130 connected to a network to perform communications. The transceiver 130 may be referred to as a transceiver, a radio frequency (RF) unit, an RF module, or the like. In addition, the communication node 100 may further include an input interface device 140, an output interface device 150, a storage device 160, and the like. The components included in the communication node 100 may be connected by a bus 170 to communicate with each other.
However, the respective components included in the communication node 100 may be connected through individual interfaces or individual buses centering on the processor 110 instead of the common bus 170. For example, the processor 110 may be connected to at least one of the memory 120, the transceiver 130, the input interface device 140, the output interface device 150, or the storage device 160 through a dedicated interface.
The processor 110 may execute at least one instruction stored in at least one of the memory 120 or the storage device 160. The processor 110 may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the methods according to the embodiments of the present invention are performed. Each of the memory 120 and the storage device 160 may be configured as at least one of a volatile storage medium or a nonvolatile storage medium. For example, the memory 120 may be configured with at least one of a read only memory (ROM) or a random access memory (RAM).
As shown in
The MAC address of the MLD may be used in a multi-link setup procedure between the non-AP MLD and the AP MLD. The MAC address of the AP MLD may be different from the MAC address of the non-AP MLD. AP(s) affiliated with the AP MLD may have different MAC addresses, and station(s) (STA(s)) affiliated with the non-AP MLD may have different MAC addresses. Each of the APs having different MAC addresses may be in charge of each link among multiple links supported by the AP MLD and may perform a role of an independent AP.
Each of the STAs having different MAC addresses may be in charge of each link among multiple links supported by the non-AP MLD and may perform a role of an independent STA. The non-AP MLD may be referred to as a STA MLD. The MLD may support a simultaneous transmit and receive (STR) operation. In this case, the MLD may perform a transmission operation in a link 1 and may perform a reception operation in a link 2. The MLD supporting the STR operation may be referred to as an STR MLD (e.g., STR AP MLD, STR non-AP MLD). In embodiments, a link may mean a channel or a band. A device that does not support the STR operation may be referred to as a non-STR (NSTR) AP MLD or an NSTR non-AP MLD (or NSTR STA MLD).
The MLD may transmit and receive frames in multiple links (i.e., multi-link) by using a non-contiguous bandwidth extension scheme (e.g., 80 MHz+80 MHz). The multi-link operation may include multi-band transmission. The AP MLD may include a plurality of APs, and the plurality of APs may operate in different links. Each of the plurality of APs may perform function(s) of a lower MAC layer. Each of the plurality of APs may be referred to as a ‘communication node’ or ‘lower entity’. The communication node (i.e., AP) may operate under control of an upper layer (or the processor 110 shown in
The MLD may perform communications in multiple bands (i.e., multi-band). For example, the MLD may perform communications using an 80 MHz bandwidth according to a channel expansion scheme (e.g., bandwidth expansion scheme) in a 2.4 GHz band and may perform communications using a 160 MHz bandwidth according to a channel expansion scheme in a 5 GHz band. The MLD may perform communications using a 160 MHz bandwidth in the 5 GHz band and may perform communications using a 160 MHz bandwidth in a 6 GHz band. One frequency band (e.g., one channel) used by the MLD may be defined as one link. Alternatively, a plurality of links may be configured in one frequency band used by the MLD. For example, the MLD may configure one link in the 2.4 GHz band and two links in the 6 GHz band. The respective links may be referred to as a first link, a second link, and a third link. Alternatively, the respective links may be referred to as a link 1, a link 2, and a link 3. A link number may be set by the AP, and an identifier (ID) may be assigned to each link.
The MLD (e.g., AP MLD and/or non-AP MLD) may configure a multi-link by performing an access procedure and/or a negotiation procedure for a multi-link operation. In this case, the number of links and/or link(s) to be used in the multi-link may be configured. The non-AP MLD (e.g., STA) may identify information on band(s) capable of communicating with the AP MLD. In the negotiation procedure for a multi-link operation between the non-AP MLD and the AP MLD, the non-AP MLD may configure one or more links among links supported by the AP MLD to be used for the multi-link operation. A station that does not support a multi-link operation (e.g., IEEE 802.11a/b/g/n/ac/ax STA) may be connected to one or more links of the multi-link supported by the AP MLD.
When a band separation between multiple links (e.g., a band separation between the link 1 and the link 2 in the frequency domain) is sufficient, the MLD may perform an STR operation. For example, the MLD may transmit a physical layer convergence procedure (PLCP) protocol data unit (PPDU) 1 using the link 1 among multiple links and may receive a PPDU 2 using the link 2 among multiple links. On the other hand, if the MLD performs the STR operation when the band separation between multiple links is insufficient, in-device coexistence (IDC) interference, which is interference between the multiple links, may occur. Therefore, when the band separation between multiple links is not sufficient, the MLD may not be able to perform the STR operation. A link pair having the above-described interference relationship may be a non-simultaneous transmit and receive (NSTR) limited link pair. Here, the MLD may be an NSTR AP MLD or an NSTR non-AP MLD.
For example, a multi-link including a link 1, a link 2, and a link 3 may be configured between the AP MLD and the non-AP MLD 1. If the band separation between the link 1 and the link 3 is sufficient, the AP MLD may perform an STR operation using the link 1 and the link 3. In other words, the AP MLD may transmit a frame using the link 1 and may receive a frame using the link 3. If the band separation between the link 1 and the link 2 is not sufficient, the AP MLD may not be able to perform an STR operation using the link 1 and the link 2. If a band separation between the link 2 and the link 3 is not sufficient, the AP MLD may not be able to perform an STR operation using the link 2 and the link 3.
Meanwhile, in a wireless LAN system, a negotiation procedure for a multi-link operation may be performed in an access procedure between a STA and an AP.
A device (e.g., AP or STA) supporting a multi-link may be referred to as a multi-link device (MLD). An AP supporting a multi-link may be referred to as an AP MLD, and a STA supporting a multi-link may be referred to as a non-AP MLD or STA MLD. The AP MLD may have a physical address (e.g., MAC address) for each link. The AP MLD may be implemented as if an AP in charge of each link exists separately. A plurality of APs may be managed within one AP MLD. Accordingly, coordination between the plurality of APs belonging to the same AP MLD may be possible. The STA MLD may have a physical address (e.g., MAC address) for each link. The STA MLD may be implemented as if an STA in charge of each link exists separately. A plurality of STAs may be managed within one STA MLD.
Accordingly, coordination between the plurality of STAs belonging to the same STA MLD may be possible.
For example, an AP1 of the AP MLD and a STA1 of the STA MLD may each be in charge of a first link and may communicate using the first link. An AP2 of the AP MLD and a STA2 of the STA MLD may each be in charge of a second link, and may communicate using the second link. The STA2 may receive state change information for the first link in the second link. In this case, the STA MLD may collect information (e.g., state change information) received from each link, and may control operations performed by the STA1 based on the collected information.
As shown in
In the probe step, the STA may detect one or more APs using a passive scanning scheme or an active scanning scheme. When the passive scanning scheme is used, the STA may detect one or more APs by overhearing beacons transmitted by the one or more APs. When the active scanning scheme is used, the STA may transmit a probe request frame and may detect one or more APs by receiving probe response frames that are responses to the probe request frame from the one or more APs.
When the one or more APs are detected, the STA may perform an authentication step with the detected AP(s). In this case, the STA may perform the authentication step with a plurality of APs. An authentication algorithm according to the IEEE 802.11 standard may be classified into an open system algorithm of exchanging two authentication frames, a shared key algorithm of exchanging four authentication frames, and the like.
The STA may transmit an authentication request frame based on the authentication algorithm according to the IEEE 802.11 standard, and may complete authentication with the AP by receiving an authentication response frame that is a response to the authentication request frame from the AP.
When the authentication with the AP is completed, the STA may perform an association step with the AP. In particular, the STA may select one AP among AP(s) with which the STA has performed the authentication step and may perform the association step with the selected AP. In other words, the STA may transmit an association request frame to the selected AP and may complete the association with the AP by receiving an association response frame that is a response to the association request frame from the selected AP.
Meanwhile, a multi-link operation may be supported in the wireless LAN system. A multi-link device (MLD) may include one or more STAs affiliated with the MLD. The MLD may be a logical entity. The MLD may be classified into an AP MLD and a non-AP MLD. Each STA affiliated with the AP MLD may be an AP, and each STA affiliated with the non-AP MLD may be a non-AP STA. In order to configure a multi-link, a multi-link discovery procedure, a multi-link setup procedure, and the like may be performed. The multi-link discovery procedure may be performed in the probe step between an STA and an AP. In this case, multi-link information elements (ML IEs) may be included in the beacon frame, the probe request frame, and/or the probe response frame.
For example, in order to perform a multi-link operation, in the probe step, the AP (e.g., AP affiliated with an MLD) may exchange information indicating whether the multi-link operation can be used and information on available link(s) with the STA (e.g., non-AP STA affiliated with an MLD). In a negotiation procedure for the multi-link operation (e.g., multi-link setup procedure), the STA may transmit information of link(s) to be used for the multi-link operation. The negotiation procedure for the multi-link operation may be performed in the access procedure (e.g., association step) between the STA and the AP, and information element(s) required for the multi-link operation may be configured or changed by an action frame in the negotiation procedure.
In addition, in the access procedure (e.g., association step) between the STA and the AP, available link(s) of the AP may be configured, and an identifier (ID) may be assigned to each link. Thereafter, in the negotiation procedure and/or change procedure for the multi-link operation, information indicating whether each link is activated may be transmitted, and the information may be expressed using the link ID(s).
The information indicating whether the multi-link operation can be used may be transmitted and received in a procedure of exchanging capability information element(s) (e.g., EHT capability information element(s)) between the STA and the AP. The capability information element(s) may include information of supporting band(s), information of supporting link(s) (e.g., ID(s) and/or number of supporting link(s)), information of links capable of simultaneous transmission and reception (STR) operations (e.g., information on bands of the links, information on a separation between the links), and/or the like. In addition, the capability information element(s) may include information that individually indicates a link capable of the STR operation.
As shown in
When the independent transmission scheme is used, a lower layer (e.g., physical (PHY) layer and/or a MAC layer) may separately perform a channel access operation in each link (e.g., the first link and the second link) to transmit a frame (e.g., PDU) obtained from an upper layer. When a transmission opportunity (TXOP) is secured by the channel access operation, the lower layer may transmit the frame within the corresponding TXOP.
The channel access operation may be a carrier sensing operation performed for an arbitration interframe space (AIFS) according to data (e.g., access category (AC) of the data) included in the frame. The carrier sensing operation may be referred to as a ‘channel sensing operation’. When a channel (e.g., link) is determined to be in a busy state by the carrier sensing operation or when a transmission of a data frame of another station is completed, the channel access operation may include a carrier sensing operation within the AIFS and a backoff operation.
The carrier sensing operation may be classified into a physical (PHY layer) carrier sensing operation and a virtual carrier sensing operation. The physical carrier sensing operation may be an energy detection (ED) operation of sensing a received power in an operating channel (e.g., operating link). The virtual carrier sensing operation may include a setting operation based on a value of a length field included in a preamble of a frame (e.g., PPDU or MPDU) received from another station and a network allocation vector (NAV) setting operation based on a value of a duration field of a MAC header included in a frame or a value of a length parameter of Signal field included in a preamble of a frame received from another station. The NAV setting operation may be an operation of setting a parameter for configuring a transmission prohibition period or the transmission prohibition period as a time when a terminal does not start transmission (i.e., a time when another terminal performs a transmission operation). A transmission time may be independent of a physical channel sensing result. The NAV setting operation may be an operation of setting a period (e.g., busy period) in which transmission of a frame is prohibited by a value of a duration field included in a MAC header of a frame transmitted by terminals within and/or out of a basic service set (BSS). When the virtual carrier sensing is successful and a NAV is set, a period for which the NAV is set may be determined as a busy period without performing actual carrier sensing.
When the independent transmission scheme is used, transmission times of frames in the links (e.g., link 1 and link 2) may not match. Since the channel access operation in each of the links is performed independently, the links can be used efficiently. In embodiments, a backoff operation (e.g., backoff procedure, random backoff operation) may mean a channel access procedure performed when a channel state is determined to be a busy state.
On the other hand, when the band separation between the plurality of links is not sufficient, a transmission operation in the first link may cause interference to the second link of the same device. The aforementioned interference may be in-device coexistence interference (IDC). In embodiments, the device may mean an MLD, an AP, and/or a STA. When such an IDC interference occurs, an STR operation may not be possible in the plurality of links. A link pair in which an STR operation is not possible may be referred to as an ‘NSTR-limited link pair’. For example, when a device uses two links (e.g., first link and second link) operating in a 5 GHz band, if a separation between the links is not sufficient, it may not be possible to simultaneously perform a transmission operation in the first link and a reception operation in the second link. Therefore, the multi-link operation may not be implemented in the per-link independent transmission scheme. In this case, the multi-link operation may be implemented in a synchronized transmission scheme. In embodiments, the multi-link operation may mean a transmission/reception operation using a multi-link.
When a transmission event occurs, the device may perform a channel connection operation. For example, the device may identify a channel occupancy state, and when a channel state is in an idle state, the device may perform an additional channel sensing operation for a specific time period (e.g., AIFS). When the channel state is in an idle state for the specific time period, the device may finally determine that the channel is in the idle state. In other words, the device may determine that the channel access is successful. In this case, a backoff operation may not be performed, and a backoff counter value may be 0.
On the other hand, when the channel state is in a busy state (e.g., occupied state), the device may wait until the channel state becomes an idle state. When the channel state is changed from the busy state to the idle state, the device may perform a backoff operation after waiting for an AIFS. The AIFS may start from a time when the channel state is changed from the busy state to the idle state. When the backoff operation is successfully completed, the device may transmit a frame.
When the backoff operation is performed, the device may select an arbitrary number (e.g., backoff counter value) from 0 to a contention window (CW). The CW may be set differently according to an access category (AC) of data. The device may perform a channel sensing operation in slot(s) corresponding to the selected backoff counter value. For example, when the backoff count value is 5, the device may perform the channel sensing operation in 5 slots (e.g., slots 1 to 5).
The channel sensing operation may be performed in each slot, and when the channel sensing operation is successful in each slot, the backoff counter value may decrease by one. When the channel state in the slot 1 is determined to be the idle state as a result of the channel sensing operation in the slot 1, the backoff counter value may be set to 4 (e.g., 5-1). When the channel state in the slot 2 after the slot 1 is determined to be the idle state as a result of the channel sensing operation, the backoff counter value may be set to 3 (e.g., 4-1). When the channel state in the slot 5 that is the last slot is determined to be the idle state as a result of the channel sensing operation, the backoff counter value may be set to 0 (e.g., 1-1). When the backoff counter value becomes 0, the device may determine that the backoff operation is successful.
When the channel access operation is successful and a transmission event does not occur, the device may wait for transmission of a frame (e.g., data). Thereafter, when a transmission event occurs, the device may immediately transmit the frame without a backoff operation because the channel access operation has already succeeded. In other words, when the backoff counter value is maintained at 0, the device may transmit a frame without a backoff operation.
When the synchronized transmission scheme is used, transmission start times and/or transmission end times of frames transmitted in the respective links may be set identically. In order to match the frame transmission times equally in the multi-link operation based on the synchronized transmission scheme, if the lengths of frames transmitted in the respective links are different, padding bits may be added to a frame having a shorter length to match the lengths of the frames. When channel access operations for simultaneous transmissions are performed, a backoff operation is performed in the first link, and a channel state of the second link from a specific time to an end time (e.g., success time) of the backoff operation in the first link is an idle state, the device may perform transmission operations using the plurality of links (e.g., the first link and the second link). A time from the specific time to the end time of the backoff operation in the first link may be a point coordination function (PIFS) interframe space (PIFS), a distributed coordination function (DCF) interframe space (DIFS), AIFS, or a total time of the backoff operation in the first link.
‘Identifying the channel occupancy state of the second link for the time from the specific time to the end time of the backoff operation in the first link’ may be for ‘identifying whether the channel occupancy state of the second link is the idle state in which frame transmission is possible’. In other words, ‘identifying the channel occupancy state of the second link for the time from the specific time to the end time of the backoff operation in the first link’ may mean ‘performing the channel sensing operation (e.g., carrier sensing operation) in the second link for the time from the specific time to the end time of the backoff operation in the first link’.
In order to perform simultaneous transmissions using the first link and the second link, channel access operations may be performed. In this case, the channel access operations may be simultaneously performed in the first link and the second link. If the second link is in an idle state at a start time of the channel access operation, and the idle state of the second link is maintained for a specific time (e.g., AIFS), the device may determine the second link to be in the idle state. In this case, since a backoff operation may not be performed in the second link, a backoff counter value thereof may be 0. Here, a link other than the first link may be configured as the second link.
Meanwhile, after the backoff operation ends in the first link, an operation of identifying a channel occupancy state may be performed in the second link for a specific time period. When the channel state of the second link is a busy state for some time within the specific time period, the device may transmit a frame using only the first link. Alternatively, the device may perform a backoff operation in the second link. Alternatively, the device may perform a backoff operation in a plurality of the first links for channel access. The plurality of first links may be configured, and the backoff operation may be performed in the plurality of first links. In this case, when the channel state of the second link is in an idle state for a time period (hereinafter, referred to as ‘specific time period’) from an end time of a backoff operation in a link in which the backoff operation is first completed to a time before a specific time (e.g., PIFS, DIFS, AIFS, or a total time of the backoff operation of the first link), the device may perform transmission operations using the plurality of links.
‘Identifying whether another link is in an idle state for the specific time period’ may be ‘identifying whether the link is in an idle state in which frame transmission is possible’. ‘Identifying whether another link is in an idle state for the specific time period’ may mean ‘performing a channel sensing operation (e.g., carrier sensing operation) for the specific time period from the end time of the backoff operation in the first link to a time before a specific time’. In order to perform simultaneous transmissions using the first link and other link(s), a channel access operation may be performed. In other words, when the channel access operation is started in the first link, a channel access operation may be started in other link(s) at the same time. When a link in an idle state exists at the start time of the channel access operation and the idle state of the link is maintained for a specific time period (e.g., AIFS), the corresponding link may be determined as a link capable of simultaneous transmission. Since the backoff operation is not performed in the link in the idle state at the start of the channel access operation, a backoff counter value may be 0 in the link, which is in the idle state.
When a multi-link operation is performed based on the synchronized transmission scheme, a receiving device (e.g., STA or AP) may receive a plurality of frames simultaneously. Accordingly, a frame reception operation may be simplified. A frame (e.g., data) transmitted in the synchronized transmission scheme may include information on the links used for the simultaneous transmissions. The information (e.g., link IDs, etc.) of the links used for the simultaneous transmissions may be indicated in a bitmap form by an EHT signal (SIG) including information on a signal of the IEEE 802.11be in a preamble of a PPDU. Alternatively, the information (e.g., link IDs, etc.) of the links used for the simultaneous transmissions may be indicated by an EHT control field included in the frame.
As shown in
At a time when a transmission operation can be performed in a link, a priority of the packet located in the queue R_TX may be higher than that of a packet located in another queue (e.g., VO, VI, BE, or BK). As a method of setting the priority, when transmission of a packet is impossible, a queue (e.g., a queue in which the packet is located) may be deactivated, when transmission of a packet is possible, a corresponding queue may be activated, and the packet located in the activated queue may be excluded from an internal contention operation. In other words, a transmission operation of a packet located in other queues may be stopped, and a channel access operation for the packet located in the activated queue may be performed preferentially.
As another method of setting the priority, a backoff counter value for an internal contention operation for the packet located in the queue R_TX may be set to be smaller than a backoff counter value for an actual channel access operation. For example, the backoff counter value for the internal contention operation for the packet located in the queue R_TX may be half of the backoff counter value for the actual channel access operation. The actual channel access operation for the packet located in the queue R_TX may be performed using a conventional backoff counter value.
As shown in
The additional queue may be activated at a time when packets can be transmitted. A priority of the packet located in the additional queue may be higher than that of a packet located in the conventional queue. In other words, the packet located in the additional queue may have a transmission priority. As a method of setting the priority, a packet located in the conventional queue may be excluded from an internal contention operation (e.g., transmission of the packet located in the conventional queue may be waited), and a channel access operation for the packet located in the additional queue may be configured to be performed preferentially. As another method of setting the priority, a backoff counter value for an internal contention operation for the packet located in the additional queue may be set to be smaller than a backoff counter value for an actual channel access operation. For example, the backoff counter value for the internal contention operation for the packet located in the additional queue may be half of the backoff counter value for the actual channel access operation. The actual channel access operation for the packet located in the additional queue may be performed using a conventional backoff counter value.
As shown in
The AP MLD may transmit the update beacon frame after a SIFS or point coordination function (PCF) interframe space (PIFS) from a specific time. Alternatively, the AP MLD may perform a backoff operation after a SIFS or PIFS from the specific time and may transmit the update beacon frame when the backoff operation is completed. In other words, transmission of the update beacon frame may be delayed. The specific time may be an end time of the transmission operation (e.g., a reception completion time of a BA frame (or ACK frame) for a PPUD1) in the second link of the STA MLD (e.g., STA2). The update beacon frame may have a higher priority than a frame to which a longer time (e.g., DIFS or arbitration interframe space (AIFS)) than a SIFS or PIFS is applied.
If a transmission delay of the delayed update beacon frame is T2, and a time from an end time of the transmission delay to the next beacon transmission period (TBTT) when the beacon frame is transmitted without the transmission delay is T1, the beacon transmission period (TBTT) in which the delayed update beacon frame is transmitted may be T1+T2. In this case, the TBTT (e.g., T1+T2) may be a time excluding an execution time of the channel access operation. Alternatively, since only the transmission of the current update beacon frame is exceptionally delayed, a TBTT indicated by information included in the subsequent beacon frame may be T2. In this case, one beacon frame after the delayed beacon frame may be transmitted quickly, and then the beacon frame may be transmitted according to an originally scheduled beacon transmission period.
The AP MLD may set a non-STR virtual NAV for the transmission delay of the update beacon frame. Since the STA1 of the STA MLD cannot receive in the first link while the STA2 of the STA MLD that does not support STR operations performs a transmission operation for the STA MLD in the second link, the non-STR virtual NAV may be set to delay frame transmission to the STA1 of the STA MLD in the first link during the corresponding period. In other words, the non-STR virtual NAV may be used so that frame transmission to the STA1 of the STA MLD is guaranteed not to be performed in the first link during the time for the STA2 of the STA MLD to perform the transmission for the STA MLD in the second link. The non-STR virtual NAV may be set in the first link based on a frame (e.g., PPDU1) transmitted by the STA2 of the STA MLD in the second link.
For example, the STA2 of the STA MLD may transmit a PPDU1 in the second link, and the AP2 of the AP MLD may receive the PPDU1 in the second link. The AP MLD may identify that the STA MLD does not support STR operations during an initial access process. Therefore, when the PPDU1 is received from the STA2 of the STA MLD that does not support STR operations, the AP MLD may set a non-STR virtual NAV not to transmit a frame to a STA in charge of another link of the STA MLD during a transmission time of the PPDU1. The AP MLD may identify that the STA that transmitted the PPDU1 does not support STR operations and the transmission time of the PPDU1 based on a value of a duration field included in the PPDU1, an address of a transmitter that transmitted the PPDU1 and/or a length value of a preamble. In this case, the AP MLD may set a non-STR virtual NAVs for other STAs in charge of other links of the STA MLD for the duration. When the duration of the PPDU1 includes a reception time of a BA frame, the non-STR virtual NAV may be set only for the transmission time of the PPDU1. The transmission time of the PPDU1 may be identified based on a length parameter (e.g., 12 bits) included in a signal field of the preamble of the PPDU1. When the AP1 of the AP MLD sets a non-STR virtual NAV for the STA1 of the STA MLD in the first link, in a time period corresponding to the non-STR virtual NAV in the first link, the AP1 of the AP MLD may perform a transmission to other communication nodes but may not perform a transmission operation to the STA1 of the STA MLD. When a packet to be transmitted to the STA1 of the STA MLD occurs in the period for which the non-STR virtual NAV is set, the packet may be transmitted after the period for which the non-STR virtual NAV is set ends. In other words, the transmission of the packet may be delayed.
The non-STR virtual NAV may be set for each STA of the STA MLD that does not support STR operations. The setting information of the non-STR virtual NAV may include an identifier of the STA (e.g., MAC address, association identifier (AID), or the like) to which a NAV timer and/or the non-STR virtual NAV is applied. For example, a non-STR virtual NAV for the STA1 of the STA MLD may be set independently of a non-STR virtual NAV for the STA2 of the STA MLD. When a non-STR virtual NAV is set, the following transmission operation(s) may be prohibited to the STA to which the non-STR virtual NAV is applied in a time period corresponding to the non-STR virtual NAV.
Multicast transmission operation: transmission operation of a frame having a receiver address (e.g., destination address) indicating a multicast group to which a STA for which the non-STR virtual NAV is set belongs.
Broadcast transmission operation: All frames transmitted in a broadcast scheme.
As shown in
The STA MLD1 that does not support STR operations may transmit a frame (e.g., PPDU) in the second link when the first link is occupied. The AP2 of the AP MLD may receive the frame of the STA2 of the STA MLD1 in the second link. The AP MLD may identify the STA MLD1 of the STA2 based on the transmitter address of the frame transmitted by the STA2 of the STA MLD1 and information registered at the time of initial access. The AP MLD may identify whether the STA MLD1 supports STR functions and/or whether the first link (i.e., STA1) and the second link (i.e., STA2) are an NSTR pair by referring to capability registered by the STA MLD1 in the AP MLD. After identifying that the STA MLD1 cannot perform STR operations in the first link (i.e., STA1) and the second link (i.e., STA2), the AP MLD may set a non-STR virtual NAV for prohibiting frame transmission to the STA1 of the STA MLD1 for a duration or a length of the preamble based on a value of a duration field or the length of the preamble included in a header of a frame of the STA1 of the STA MLD1 received in the second link.
The non-STR virtual NAV may be set together with another NAV (e.g., normal NAV). The AP1 of the AP MLD may set a normal NAV in the first link, and may set a non-STR virtual NAV in the first link independently of the normal NAV. The non-STR virtual NAV may be set for the STA1 of the STA MLD1 in the first link based on a value of a duration field or a length value of a preamble included in a header of a frame transmitted by the STA2 of the STA MLD1 in the second link.
If there is a frame (e.g., PPDU) to be transmitted to the STA MLD2 after an end of the normal NAV, since the non-STR virtual NAV is not applied to the STA MLD2, the AP1 of the AP MLD may transmit a frame to the STA1 of the STA MLD2 in the first link even in the period to which the non-STR virtual NAV is applied. The frame from the STA MLD2 to the STA1 may be transmitted according to a channel contention operation. The frame for the STA MLD1 may be transmitted after an end of the non-STR virtual NAV applied to the STA1 of the STA MLD1. For example, the AP1 of the AP MLD may perform a channel contention operation in the first link after the end of the non-STR virtual NAV, and if the channel contention operation succeeds, the AP1 of the AP MLD may transmit a frame (i.e., PPUD of the STA MLD1) to the STA MLD1. When direct communication (e.g., peer-to-peer (P2P) communication) between the STA MLDs is performed, other STA MLDs receiving the frame of the STA MLD1 may set a non-STR virtual NAV applied to the STA MLD1.
If whether STR operations are supported or/and an NSTR link pair relationship is not identified by the previously registered information, the link for which the non-STR virtual NAV is set may be identified based on the value of the duration field. A link that does not support STR operations may be identified based on a result of a modulo operation between the value of the duration field and a slot time. For example, a modulo operation may be performed on the value of the duration field and the slot time (e.g., 9 μs). A link to which the non-STR virtual NAV is applied may be determined as shown in Table 1 below according to the result of the modulo operation.
The length of the non-STR virtual NAV may be set as ‘the value of the duration field—the result of the modulo operation’. For example, when the slot time is 9 μs and the value of the duration field is 452 μs, since a result of (452 mod 9) is 2, the STR operation may not be supported in the link #1 (e.g., the first link). Accordingly, the non-STR virtual NAV may be set in the link #1, and in this case, the length of the non-STR virtual NAV may be 450 μs.
When the number of links available in the AP MLD is 4 or less, whether to set a non-STR virtual NAV in each of the links in which transmission is not performed may be indicated in form of a bitmap. For example, the STA MLD may transmit a frame in the link #2, and a value of a duration field included in the frame may be 453 μs. In this case, since a result of (453 mod 90) is 3 and a binary number of 3 is ‘101’, the non-STR virtual NAV may be set in the link #1 and the link #3, and the non-STR virtual NAV may not be set in the link #4. When an aggregated (A)-MPDU is transmitted, information on link(s) having a non-STR relationship may be transmitted. The A-MPDU may include a plurality of MPDUs, and a MAC header of each of the plurality of MPDUs may include information on link(s) having a non-STR relationship as in the above-described method.
A frame including information indicating setting of the above-described non-STR virtual NAV may be transmitted. When a frame including the information indicating the setting of the non-STR virtual NAV is received, the communication node (e.g., AP MLD or STA MLD) may identify a link, a duration, and an STA of a target STA MLD to which the non-STR virtual NAV associated with the frame is set, and may immediately set the non-STR virtual NAV for the STA of the STA MLD in the corresponding link. In other words, since the setting information of the non-STR virtual NAV is included in the frame header, the non-STR virtual NAV may be set in another link based on the decoding result of the header. In this case, when the AP MLD or the STA MLD is transmitting a frame to a communication node in which the non-STR virtual NAV is set, the transmission operation of the corresponding frame may be stopped.
As shown in
A period in the second link, which corresponds to a period (e.g., PPDU1 transmission period) in which the transmission operation of the STA1 of the STA MLD1 is performed in the first link, may be referred to as a deaf period for the STA2 of the STA MLD1. In the second link, a reception operation (e.g., sensing operation) may not be performed in a period corresponding to the deaf period. Since the transmission operation of the STA1 of the STA MLD1 in the first link acts as interference to the STA2 of the STA MLD1 in the second link, and the STA2 of the STA MLD1 cannot perform a sensing operation in the period in which the interference acts, the reception operation may not be performed in the second link. The second link may be in a deaf period for the STA2 of the STA MLD1 during the period in which the STA1 of the STA MLD1 that does not support STR operations performs the transmission operation in the first link, and a non-STR NAV for setting a period in which a transmission operation of a frame to be received by the STA2 of the STA MLD1 is not performed may be set within the deaf period of the second link.
A non-STR NAV may be set for a period in which an AP or STA does not perform transmission to the corresponding STA (e.g., STA2) of the MLD (e.g., STA MLD1) in another link (e.g., the second link) in which the MLD (e.g., STA MLD1) cannot perform an STR operation while the STA (e.g., STA1) of the MLD (e.g., STA MLD1) that does not support STR operations is transmitting in the first link.
After the non-STR NAV is terminated, frame transmission to the STA of the STA MLD (e.g., the STA2 of the STA MLD1) may become possible. A packet (e.g., PPDU2) to be transmitted to the STA2 of the STA MLD1 may occur in the period for which the non-STR NAV is set. In this case, according to the embodiment shown in
When the non-STR NAV is terminated, the packet located in the additional queue may be transmitted according to the following two methods. In the first transmission method (e.g., the embodiment shown in
In the second transmission method (e.g., the embodiment shown in
In the above-described embodiments, a channel state of the period for which the non-STR NAV is set may be interpreted as a busy state, and the channel access operation may be performed based on the above-described interpretation. Alternatively, in the above-described embodiments, the channel state of the period for which the non-STR NAV is set may be interpreted as another state (e.g., idle state), and the channel access operation may be performed based on the above-described interpretation.
As shown in
A packet to be transmitted to the STA2 of the STA MLD1 in the second link may occur while the STA1 of the STA MLD1 is performing the transmission operation (e.g., PPDU1 transmission operation) in the first link. In this case, after the non-STR NAV is terminated, it may be possible to transmit the packet (e.g., PPDU2) to the STA2 of the STA MLD1. A packet to be transmitted to the STA2 of the STA MLD1 may occur in the period for which non-STR NAV is set. In this case, according to the embodiment shown in
When the non-STR NAV is terminated, the packet located in the additional queue may be transmitted according to the following two methods. In the first transmission method (e.g., the embodiment shown in
As shown in
A packet to be transmitted to the STA2 of the STA MLD1 may occur in the period for which non-STR NAV is set. In this case, according to the embodiment shown in
In the embodiment shown in
In the embodiment shown in
In the embodiment shown in
The channel sensing operation may be performed before a preset period (e.g., PIFS or AIFS) from the end time of the non-STR NAV instead of an entire period from a success time of the channel access operation (e.g., backoff operation) to the end time of the non-STR NAV. In other words, the channel sensing operation may be performed for the preset period. If the channel state is in an idle state for the preset period, the device (e.g., the AP2 of the AP MLD) may transmit the packet (e.g., PPDU2) at the end time of the non-STR NAV. On the other hand, if the channel state is in a busy state for the preset period, the device (e.g., the AP2 of the AP MLD) may perform a channel sensing operation for a preset period (e.g., PIFS or AIFS) after the busy state ends, and if the channel state is in an idle state as a result of the channel sensing operation, the device may transmit the packet (e.g., PPDU2).
In the above-described embodiments, the transmission operation according to the result (e.g., idle state) of the channel sensing operation for the preset period (e.g., PIFS or AIFS) before the end time of the non-STR NAV may be replaced with a transmission operation according to a result (e.g., idle state) of a channel sensing operation for a preset period (e.g., PIFS or AIFS) from the end time of the non-STR NAV.
Meanwhile, a transmission operation for a packet located in the conventional queue to a device which is not a target of the non-STR NAV in a period from a completion time of a channel access operation or backoff operation for the packet located in the additional queue to the end time of the non-STR NAV may be performed according to an EDCA scheme regardless of the non-STR NAV. In this case, operations after transmission of the packet located in the conventional queue may be performed identically or similarly to the above-described operations (e.g., operations when a busy state is determined by a channel sensing operation).
As shown in
A packet to be transmitted to the STA2 of the STA MLD1 may occur in the period in which non-STR NAV is set. In this case, according to the embodiment shown in
Alternatively, if the channel state is in an idle state at the time of occurrence of the PPDU2, the device (e.g., the AP2 of the AP MLD) may perform a channel sensing operation for a preset period (e.g., AIFS). If the channel state is in an idle state for the preset period, the device (e.g., the AP2 of AP the MLD) may perform a channel sensing operation for a preset period (e.g., PIFS or AIFS) before the end time of the non-STR NAV. If the channel state is determined to be an idle state as a result of the channel sensing operation, the device (e.g., the AP2 of the AP MLD) may transmit the PPDU2 to the STA2 of the STA MLD1.
If the channel state is in a busy state for the preset period (e.g., PIFS or AIFS) before the end time of the non-STR NAV, the device (e.g., the AP2 of the AP MLD) may transmit the PPDU2 when the channel state is in an idle state for a PIFS or AIFS from an end time of the busy state (i.e., a time when the channel state changes from the busy state to an idle state). Alternatively, when the channel state changes from the busy state to an idle state, the device (e.g., the AP2 of the AP MLD) may transmit the PPDU2 by performing a channel access operation (e.g., ‘channel sensing operation for an AIFS+backoff operation’).
In the above-described embodiments, the transmission operation according to the result (e.g., idle state) of the channel sensing operation for the preset period (e.g., PIFS or AIFS) before the end time of the non-STR NAV may be replaced with a transmission operation according to a result (e.g., idle state) of a channel sensing operation for a preset period (e.g., PIFS or AIFS) from the end time of the non-STR NAV.
Meanwhile, a transmission operation for a packet located in the conventional queue to a device which is not a target of the non-STR NAV in a period from a completion time of a channel access operation or backoff operation for the packet located in the additional queue to the end time of the non-STR NAV may be performed according to an EDCA scheme regardless of the non-STR NAV. In this case, operations after transmission of the packet located in the conventional queue may be performed identically or similarly to the above-described operations (e.g., operations when a busy state is determined by a channel sensing operation).
As shown in
The STA MLD1 may not support STR operations, and the AP2 of the AP MLD may perform a backoff operation for transmission of the PPDU2 for the STA2 of the STA MLD1 in the second link. While the backoff operation of the device (e.g., the AP2 of the AP MLD) is performed in the second link, the STA1 of the STA MLD1 may start transmission of the PPDU1 after a channel access operation for the transmission of the PPDU1 in the first link (e.g., ‘channel sensing for an AIFS’ or ‘channel sensing for an AIFS+backoff operation’) is completed. When the transmission of the packet (e.g., PPDU1) of the device (e.g., the STA1 of the STA MLD1) that does not support STR operations starts in the first link, the AP MLD or STA MLD may set the non-STR NAV in the second link, for prohibiting transmission to the device (e.g., the STA2 of the STA MLD1) that cannot perform a reception operation because it does not support STR operations. Even when the non-STR NAV is set by starting transmission of the packet to the device (e.g., STA MLD1) in the first link while performing a channel access operation for transmission to the device that does not support STR operations in the second link, the device (e.g., the AP2 of the AP MLD) setting the non-STR NAV may continue to perform the backoff operation in the second link (i.e., the embodiment shown in
As another method (i.e., the embodiment shown in
Meanwhile, a transmission operation for a packet located in the conventional queue to a device which is not a target of the non-STR NAV in a period from a completion time of a channel access operation or backoff operation for the packet located in the additional queue to the end time of the non-STR NAV may be performed according to an EDCA scheme regardless of the non-STR NAV. In this case, operations after transmission of the packet located in the conventional queue may be performed identically or similarly to the above-described operations (e.g., operations when a busy state is determined by a channel sensing operation).
The embodiments of the present disclosure may be implemented as program instructions executable by a variety of computers and recorded on a computer-readable medium. The computer-readable medium may include a program instruction, a data file, a data structure, or a combination thereof. The program instructions recorded on the computer-readable medium may be designed and configured specifically for the present disclosure or can be publicly known and available to those having ordinary skill in the field of computer software.
Examples of the computer-readable medium may include a hardware device such as ROM, RAM, and flash memory, which are specifically configured to store and execute the program instructions. Examples of the program instructions include machine codes made by, for example, a compiler, as well as high-level language codes executable by a computer, using an interpreter. The above hardware device can be configured to operate as at least one software module in order to perform the embodiments of the present disclosure, and vice versa.
While the embodiments of the present disclosure and their advantages have been described in detail, it should be understood that various changes, substitutions and alterations may be made herein without departing from the scope of the present disclosure.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2020-0038452 | Mar 2020 | KR | national |
| 10-2020-0041788 | Apr 2020 | KR | national |
This application is a U.S. national stage of International Application No. PCT/KR2021/003736, filed on Mar. 25, 2021, which claims priority to Korean Patent Application No. KR 10-2020-0038452 filed on Mar. 30, 2020, and Korean Patent Application No. KR10-2020-0041788 filed on Apr. 6, 2020, the entire disclosures of each of which are incorporated by reference.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/KR2021/003736 | 3/25/2021 | WO |
