WO2019182347A1 - Procédé de prise en charge de planification tdd dans un système lan sans fil et terminal sans fil l'utilisant - Google Patents

Procédé de prise en charge de planification tdd dans un système lan sans fil et terminal sans fil l'utilisant Download PDF

Info

Publication number
WO2019182347A1
WO2019182347A1 PCT/KR2019/003235 KR2019003235W WO2019182347A1 WO 2019182347 A1 WO2019182347 A1 WO 2019182347A1 KR 2019003235 W KR2019003235 W KR 2019003235W WO 2019182347 A1 WO2019182347 A1 WO 2019182347A1
Authority
WO
WIPO (PCT)
Prior art keywords
tdd
information
slot
wireless terminal
slot structure
Prior art date
Application number
PCT/KR2019/003235
Other languages
English (en)
Korean (ko)
Inventor
방세희
류기선
최진수
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2019182347A1 publication Critical patent/WO2019182347A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/04—Scheduled access

Definitions

  • the present disclosure relates to wireless communication, and more particularly, to a method for supporting TDD scheduling in a WLAN system and a wireless terminal using the same.
  • the Institute of Electrical and Electronics Engineers (IEEE) 802.11ad standard is a high-speed wireless communications standard that operates in the band above 60 GHz.
  • the signal's reach is around 10 meters, but throughput can support more than 6 Gbps. Since operating in higher frequency bands, signal propagation is dominated by ray-like propagation.
  • Signal quality may be improved as the TX (remit) or RX (receive) antenna beam is aligned to face a strong spatial signal path.
  • IEEE 802.11ad provides a beamforming training process for antenna beam alignment.
  • IEEE 802.11ay is the next generation of standards under development aimed at throughputs of 20Gbps and higher based on IEEE 802.11ad.
  • An object of the present specification is to provide a method for supporting TDD scheduling in a WLAN system having improved performance and a wireless terminal using the same.
  • a method for supporting DD performed by a first wireless terminal may include receiving a beacon frame including an information element associated with a TDD SP structure of a TDD SP for TDD channel access from a second wireless terminal.
  • the element comprising slot structure change time information associated with a time point at which the TDD SP structure is to be applied; Applying a TDD SP structure based on the slot structure change time information; And communicating with the second wireless terminal based on the applied TDD SP structure.
  • a method for supporting TDD scheduling in a WLAN system having improved performance and a wireless terminal using the same may be provided.
  • FIG. 1 is a conceptual diagram illustrating a structure of a WLAN system.
  • FIG. 2 is a conceptual diagram of a layer architecture of a WLAN system supported by IEEE 802.11.
  • 3 is a diagram for describing an access period within a beacon interval.
  • FIG. 4 is a conceptual diagram illustrating a structure of a TDD SP.
  • FIG. 5 is a diagram illustrating a format of a TDD slot structure element defining a structure of a TDD SP.
  • FIG. 6 illustrates the format of a slot structure control field for a TDD slot structure element.
  • FIG. 7 illustrates the format of a slot structure field of a TDD slot structure element.
  • FIG. 8 is a diagram illustrating a format of a TDD slot schedule element defining a schedule for TDD channel access.
  • FIG. 9 is a diagram illustrating a format of a control field of a TDD slot schedule element.
  • FIG. 10 is a flowchart illustrating an STA view of a method for supporting TDD in a WLAN system according to an exemplary embodiment.
  • 11 and 12 are diagrams illustrating a frame format for supporting TDD in a WLAN system according to an embodiment.
  • FIG. 13 and 14 illustrate a frame format for supporting TDD in a WLAN system according to another exemplary embodiment.
  • FIG. 15 is a flowchart illustrating an AP view of a method for supporting TDD in a WLAN system according to an exemplary embodiment.
  • 16 is a block diagram illustrating a wireless device to which an embodiment can be applied.
  • 17 is a block diagram illustrating an example of an apparatus included in a processor.
  • FIG. 1 is a conceptual diagram illustrating a structure of a WLAN system.
  • FIG. 1A shows the structure of an infrastructure network of the Institute of Electrical and Electronic Engineers (IEEE) 802.11.
  • IEEE Institute of Electrical and Electronic Engineers
  • the WLAN system 10 of FIG. 1A may include at least one basic service set (hereinafter, referred to as 'BSS', 100, 105).
  • the BSS is a set of access points (APs) and stations (STAs) that can successfully synchronize and communicate with each other, and is not a concept indicating a specific area.
  • APs access points
  • STAs stations
  • the first BSS 100 may include a first AP 110 and one first STA 100-1.
  • the second BSS 105 may include a second AP 130 and one or more STAs 105-1, 105-2.
  • the infrastructure BSS may include at least one STA, AP (110, 130) providing a distribution service (Distribution Service) and a distribution system (DS, 120) connecting a plurality of APs. have.
  • the distributed system 120 may connect the plurality of BSSs 100 and 105 to implement an extended service set 140 which is an extended service set.
  • the ESS 140 may be used as a term indicating one network to which at least one AP 110 or 130 is connected through the distributed system 120.
  • At least one AP included in one ESS 140 may have the same service set identification (hereinafter, referred to as SSID).
  • the portal 150 may serve as a bridge for connecting the WLAN network (IEEE 802.11) with another network (for example, 802.X).
  • a network between APs 110 and 130 and a network between APs 110 and 130 and STAs 100-1, 105-1, and 105-2 may be implemented. Can be.
  • FIG. 1B is a conceptual diagram illustrating an independent BSS.
  • the WLAN system 15 of FIG. 1B performs communication by setting a network between STAs without the APs 110 and 130, unlike FIG. 1A. It may be possible to.
  • a network that performs communication by establishing a network even between STAs without the APs 110 and 130 is defined as an ad-hoc network or an independent basic service set (BSS).
  • BSS basic service set
  • the IBSS 15 is a BSS operating in an ad-hoc mode. Since IBSS does not contain an AP, there is no centralized management entity. Thus, in the IBSS 15, the STAs 150-1, 150-2, 150-3, 155-4, and 155-5 are managed in a distributed manner.
  • All STAs 150-1, 150-2, 150-3, 155-4, and 155-5 of the IBSS may be mobile STAs, and access to a distributed system is not allowed. All STAs of the IBSS form a self-contained network.
  • the STA referred to herein includes a medium access control (MAC) conforming to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard and a physical layer interface to a wireless medium.
  • MAC medium access control
  • IEEE Institute of Electrical and Electronics Engineers 802.11
  • any functional medium it can broadly be used to mean both an AP and a non-AP Non-AP Station (STA).
  • the STA referred to herein includes a mobile terminal, a wireless device, a wireless transmit / receive unit (WTRU), a user equipment (UE), and a mobile station (MS). It may also be called various names such as a mobile subscriber unit or simply a user.
  • WTRU wireless transmit / receive unit
  • UE user equipment
  • MS mobile station
  • a hierarchical architecture of a WLAN system includes a physical medium dependent (PMD) sublayer 200, a physical layer convergence procedure (PLCP) sublayer ( 210 and a medium access control (MAC) sublayer 220.
  • PMD physical medium dependent
  • PLCP physical layer convergence procedure
  • MAC medium access control
  • the PMD sublayer 200 may serve as a transmission interface for transmitting and receiving data between a plurality of STAs.
  • the PLCP sublayer 210 is implemented such that the MAC sublayer 220 can operate with a minimum dependency on the PMD sublayer 200.
  • the PMD sublayer 200, the PLCP sublayer 210, and the MAC sublayer 220 may conceptually include management entities.
  • the management unit of the MAC sublayer 220 is referred to as a MAC Layer Management Entity (MLME) 225.
  • the management unit of the physical layer is referred to as a PHY Layer Management Entity (PLME) 215.
  • Such management units may provide an interface for performing a layer management operation.
  • the PLME 215 may be connected to the MLME 225 to perform management operations of the PLCP sublayer 210 and the PMD sublayer 200.
  • the MLME 225 may be connected to the PLME 215 to perform a management operation of the MAC sublayer 220.
  • a STA management entity (hereinafter, referred to as “SME”, 250) may exist.
  • the SME 250 may operate as an independent component in each layer.
  • the PLME 215, the MLME 225, and the SME 250 may transmit and receive information from each other based on primitives.
  • the PLCP sublayer 210 may include a MAC protocol data unit (MAC protocol data unit) received from the MAC sublayer 220 according to an indication of the MAC layer between the MAC sublayer 220 and the PMD sublayer 200.
  • MAC protocol data unit MAC protocol data unit
  • the MPDU is transmitted to the PMD sublayer 200 or the frame coming from the PMD sublayer 200 is transferred to the MAC sublayer 220.
  • the PMD sublayer 200 may be a PLCP lower layer to perform data transmission and reception between a plurality of STAs over a wireless medium.
  • the MPDU delivered by the MAC sublayer 220 is referred to as a physical service data unit (hereinafter, referred to as a PSDU) in the PLCP sublayer 210.
  • PSDU physical service data unit
  • the MPDU is similar to the PSDU. However, when an aggregated MPDU (AMPDU) that aggregates a plurality of MPDUs is delivered, individual MPDUs and PSDUs may be different from each other.
  • AMPDU aggregated MPDU
  • the PLCP sublayer 210 adds an additional field including information required by the transceiver of the physical layer in the process of receiving the PSDU from the MAC sublayer 220 and transmitting the PSDU to the PMD sublayer 200.
  • the added field may be a PLCP preamble, a PLCP header, tail bits required to return the convolutional encoder to a zero state in the PSDU.
  • the PLCP sublayer 210 adds the above-described fields to the PSDU to generate a PPCP (PLCP Protocol Data Unit), which is then transmitted to the receiving station via the PMD sublayer 200, and the receiving station receives the PPDU to receive the PLCP preamble and PLCP. Obtain and restore information necessary for data restoration from the header.
  • PPCP PLCP Protocol Data Unit
  • 3 is a diagram for describing an access period within a beacon interval.
  • a time of a wireless medium may be defined based on a beacon interval between a beacon frame and a beacon frame.
  • the beacon interval may be 1024 milliseconds (msec).
  • the plurality of lower periods in the beacon interval may be referred to as an access period. Different access intervals within one beacon interval may have different access rules.
  • the information about the access interval may be transmitted to the non-AP STA or the non-PCP by the AP or Personal Basic Service Set Control Point (PCP).
  • PCP Personal Basic Service Set Control Point
  • one beacon interval may include a beacon header interval (BHI) and a data transfer interval (DTI).
  • BHI beacon header interval
  • DTI data transfer interval
  • the BHI may be a time interval starting from the target beacon transmission time (TBTT) of the beacon interval and ending before the start of the DTI.
  • TBTT target beacon transmission time
  • the BHI of FIG. 3 is a beacon transmission interval (BTI), association beamforming training (A-BFT), and announcement transmission interval (ATI). May include ').
  • the BTI may be a time interval from the start of the first beacon frame to the end of the last beacon frame transmitted by the wireless terminal within the beacon interval. That is, the BTI may be a section in which one or more DMG beacon frames may be transmitted.
  • the A-BFT may be a section in which beamforming training is performed by an STA that transmits a DMG beacon frame during a preceding BTI.
  • the ATI may be a request-response based management connection interval between the PCP / AP and the non-PCP / non-AP STA.
  • the data transfer interval (DTI) of FIG. It may be a period in which frames are exchanged between STAs.
  • one or more Contention Based Access Periods (CBAPs) and one or more Service Periods (SPs) may be allocated to the DTI.
  • CBAPs Contention Based Access Periods
  • SPs Service Periods
  • the schedule of the DTI of the beacon interval of FIG. 3 may be communicated through an extended schedule element included in a beacon frame (or an announce frame). That is, the extended schedule element may include schedule information for defining a plurality of allocations included in the beacon interval.
  • beacon frame For a detailed description of the beacon frame, see IEEE Draft P802.11-REVmc TM / D8.0, Aug 2016 'IEEE Standard for Information Technology elecommunications and information exchange between systems--Local and metropolitan area networks--Specific requirements Part. 11: Reference is made through section 9.4.2.132 of the Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications (hereafter IEEE 802.11).
  • MAC Wireless LAN Medium Access Control
  • PHY Physical Layer
  • FIG. 3 shows an example in which two CBAPs and two SPs are allocated for one DTI, but it will be understood that the present specification is not limited thereto.
  • TDD time division duplex
  • the field may include a first subfield and a second subfield.
  • the first subfield included in the allocation field for the second service interval SP2 of FIG. 4 may be set to a value indicating SP allocation.
  • the second subfield included in the allocation field for the second service interval SP2 of FIG. 4 may be set to a value indicating that the second service interval is a TDD SP based on TDD channel access.
  • the extended schedule element when information for a TDD SP is included in an extended schedule element, the extended schedule element may be included in each beacon frame transmitted.
  • the content of the extended schedule element may not change except for a special case.
  • the structure of the second service interval SP2 which is a TDD SP may include a plurality of consecutive and adjacent TDD intervals (TDD interval 1 to TDD interval Q, Q being a natural number).
  • TDD interval 1 to TDD interval Q being a natural number
  • the number of TDD intervals of FIG. 4 may be Q.
  • each of the plurality of TDD intervals may include one or more TDD slots.
  • the first TDD interval 1 may include M + 1 TDD slots (M is a natural number).
  • a time interval from the start of the first TDD interval 1 until the start of the first TDD slot may be defined as a first guard time (hereinafter, referred to as GT1). Can be.
  • the time interval between each TDD slot included in the first TDD interval 1 may be defined as the second guard time GT2.
  • a time interval from the end of the M + 1 th TDD slot M to the end of the first TDD interval TDD interval 1 may be defined as the third guard time GT3.
  • each of the plurality of TDD intervals may have the same length.
  • the length of M + 1 TDD slots (eg, TDD slots 0 to TDD slot M of FIG. 4) included in one TDD interval (eg, TDD interval 1 of FIG. 4) may be different.
  • the structure of one or more TDD slots included in the first TDD interval may be repeatedly applied to the remaining TDD intervals (ie, TDD interval 2 to TDD interval Q).
  • FIG. 5 is a diagram illustrating a format of a TDD slot structure element defining a structure of a TDD SP.
  • the TDD slot structure element 500 of FIG. 5 may define the structure of the TDD SP within the beacon interval.
  • the TDD slot structure element 500 may be included in a beacon frame transmitted periodically by the AP.
  • the beacon frame may be a frame according to the broadcast technique.
  • the beacon frame may be transmitted in the BTI of FIG.
  • the TDD slot structure element 500 may include a plurality of fields 510-570.
  • a value for identifying the TDD slot structure element 500 may be set.
  • a value indicating the length of the TDD slot structure element 500 may be set.
  • a value for identifying the TDD slot structure element 500 may be set together with the element ID field 510.
  • the slot structure control field 540 of FIG. 5 may include additional control information for the TDD slot structure element 500.
  • the slot structure control field 540 of FIG. 5 is described in detail with reference to FIG. 6 described below.
  • a timing synchronization function corresponding to the start time of the first TDD SP applying the TDD slot structure element 500 (eg, the start time of SP2 of FIG. 4).
  • Information corresponding to the lower 4 octets of the timer may be included.
  • parameter information for the TDD structure and parameter information for the guard time included in the TDD slot structure element 500 of FIG. 5 may be used for the TDD SP in the beacon interval.
  • a value for indicating a duration of a corresponding TDD SP may be set.
  • the TDD SP block duration field 560 may include information corresponding to the total length of the second service interval SP2 of FIG. 4.
  • the slot structure field 570 of FIG. 5 may be a field for defining one or more TDD slots included in each TDD interval.
  • the slot structure field 570 of FIG. 5 is described in detail with reference to FIG. 7 described below.
  • FIG. 6 illustrates the format of a slot structure control field for a TDD slot structure element.
  • slot structure control fields 540 and 600 for the TDD slot structure element 500 may include a plurality of subfields 610-660.
  • the subfield 610 for the number of TDD slots per TDD interval of FIG. 6 may include information for the number of TDD slots (eg, M in FIG. 4) included in each TDD interval.
  • the subfield 610 for the number of TDD slots per TDD interval may be defined based on 4 bits (B0-B4).
  • the GT1 duration subfield 620 of FIG. 6 may include information for the duration of the first guard time (eg, GT1 of FIG. 4).
  • the GT2 duration subfield 630 of FIG. 6 may include information for the duration of the second guard time (eg, GT2 of FIG. 4).
  • the GT3 duration subfield 640 of FIG. 6 may include information for the duration of the third guard time (eg, GT3 of FIG. 4).
  • information for identifying a TDD SP (eg, SP2 of FIG. 4) is set among information included in an extended schedule element defining a schedule of a DTI of a beacon interval. Can be.
  • the remaining 9 bits B23-B31 of FIG. 6 may be reserved.
  • FIG. 7 is a diagram illustrating a format of a slot structure field of a TDD slot structure element.
  • slot structure fields 570 and 700 for the TDD slot structure element 500 may include first to Mth TDD slot duration subfields 700 # 1 to 700 # M. Can be.
  • M may correspond to a value included in the subfield 610 for the number of TDD slots per TDD interval of FIG. 6.
  • the i th TDD slot duration subfield (eg, 1 ⁇ i ⁇ M, i and M are natural numbers) may include information for the duration of the i th TDD slot in each TDD interval.
  • FIG. 8 is a diagram illustrating a format of a TDD slot schedule element defining a schedule for TDD channel access.
  • a schedule for TDD channel access may be referred to as a TDD schedule.
  • the TDD slot schedule element 800 may define a schedule (ie, a TDD schedule) for TDD channel access of a particular second wireless terminal within the TDD SP.
  • the TDD slot schedule element 800 may be delivered through an announce frame or an association response frame.
  • the announcement frame or combined response frame may be a frame according to the unicast technique.
  • the announcement frame or the combined response frame may be transmitted in the ATI of FIG. 4.
  • the TDD slot schedule element 800 may include a plurality of fields 810 ⁇ 860.
  • a value for identifying the TDD slot schedule element 800 may be set.
  • a value indicating the length of the TDD slot schedule element 800 may be set.
  • a value for identifying the TDD slot schedule element 800 may be set together with the element ID field 810.
  • the slot schedule control field 840 of FIG. 8 may include additional control information for the TDD slot schedule element 800.
  • the slot schedule control field 840 of FIG. 8 is described in detail with reference to FIG. 9 described later.
  • the bitmap and access type schedule field 850 of FIG. 8 may be associated with operation type information permitted in each of a plurality of TDD slots included in at least one TDD interval for a wireless terminal receiving the TDD slot schedule element 800. Can be.
  • bitmap and access type schedule field 850 of FIG. 8 may be bitmap information having a length determined based on Equation 1 below.
  • the length of the bitmap and access type schedule field 850 of FIG. 8 may be understood as a value obtained by increasing the value of the product of Q and M divided by four.
  • Q of Equation 1 may be understood as the number of at least one TDD interval after a start time to which the TDD slot schedule element 800 for the wireless terminal is applied in the TDD SP.
  • M of Equation 1 may be understood as the number of one or more TDD slots included in each of the plurality of TDD intervals of FIG. 4.
  • each of the plurality of TDD slots included in the at least one TDD interval to which the TDD slot schedule element 800 is applied each of two consecutive bits included in the bitmap and access type schedule field 850 of FIG. 8. It may correspond to a pair (each pair of consecutive 2 bits) in sequence.
  • each pair of consecutive 2 bits included in the bitmap and access type schedule field 850 of FIG. 8 may be set to any one of encoding values of Table 1 below.
  • the wireless terminal when two consecutive bits included in the bitmap and access type schedule field 850 of Table 1 indicate '0', the wireless terminal unassigns the corresponding TDD slot to itself. It can be understood as a slot.
  • the wireless terminal corresponding to the non-AP STA may be understood as a TDD slot that is permitted to receive.
  • the wireless terminal corresponding to the AP STA corresponds to a corresponding TDD slot.
  • TDD slot can be understood as a TDD slot that is permitted to transmit.
  • the wireless terminal corresponding to the non-AP STA (or non-PCP STA)
  • the corresponding TDD slot may be understood as a TDD slot that is permitted to transmit.
  • the wireless terminal corresponding to the AP STA corresponds to a corresponding TDD slot.
  • TDD slot can be understood as a TDD slot that is allowed to receive operations.
  • the wireless terminal may not use a corresponding TDD slot in its own TDD. It can be understood as a slot.
  • the slot category schedule field 860 of FIG. 8 may be associated with category information of each of a plurality of TDD slots included in at least one TDD interval after the time point at which the TDD slot schedule element 800 is applied.
  • the slot category schedule field 860 of FIG. 8 may be bitmap information having a length determined based on Equation 1 above.
  • each pair of consecutive 2 bits included in the slot category schedule field 860 of FIG. 8 is a sequence of two consecutive bits included in the bitmap and access type schedule field 850. May correspond to each pair.
  • each pair of two consecutive bits included in the slot category schedule field 860 of FIG. 8 may indicate a type of a frame allowed in a corresponding TDD slot.
  • the corresponding TDD slot may be understood as a basic TDD slot.
  • all types of frames can be transmitted in the basic TDD slot.
  • the corresponding TDD slot may be understood as a data-only TDD slot.
  • only data frames can be transmitted in a Data-only TDD slot.
  • FIG. 9 is a diagram illustrating a format of a control field of a TDD slot schedule element.
  • the slot schedule control fields 840 and 900 for the TDD slot schedule element 800 may include a plurality of subfields 910 to 970.
  • the channel aggregation subfield 910 of FIG. 9 may include information for channel aggregation for PPDU transmission.
  • the BW subfield 920 of FIG. 9 may include information for channel bandwidth for PPDU transmission.
  • the slot schedule start time subfield 930 of FIG. 9 corresponds to the start time of the first TDD interval to which the TDD slot schedule element 800 for the wireless terminal is to be applied (for example, the start time of TDD interval 1 of FIG. 4).
  • Information about lower 4 octets of a timing synchronization function (TSF) timer may be included.
  • TSF timing synchronization function
  • information about the number of at least one TDD interval following the start time indicated by the slot schedule start time subfield 930 in the TDD SP is included. May be included.
  • the allocation ID subfield 950 of FIG. 9 includes information for identifying a TDD SP (eg, SP2 of FIG. 4) among information included in an extended schedule element defining a schedule of a DTI of a beacon interval. Can be.
  • the TDD slot schedule duration subfield 960 of FIG. 9 may include information associated with a duration to which the TDD slot schedule element 800 is applied.
  • the duration may be a time interval corresponding to the end of the last TDD interval at which the TDD slot schedule element 800 expires at the start of the first TDD interval applying the TDD slot schedule element 800.
  • bitmap information included in the bitmap and access type schedule field 850 may be repeated based on the TDD slot schedule duration subfield 960.
  • the TDD slot schedule duration subfield 960 may be set to an integer multiple (Y) of time intervals corresponding to at least one TDD interval within the TDD SP for the wireless terminal.
  • bitmap information included in the bitmap and access type schedule field 850 may be repeated over a beacon interval corresponding to an integer multiple (Y).
  • bitmap information included in the slot category schedule field 860 may be repeated based on the TDD slot schedule duration subfield 960.
  • bitmap information included in the slot category schedule field 860 may be repeated over a beacon interval corresponding to an integer multiple (Y).
  • the bitmap information included in the slot category schedule field 860 and the bitmap information included in the slot category schedule field 860 correspond to an integer multiple (Y). Can be repeated over a beacon interval.
  • the TDD slot schedule element 800 is included in the TDD slot schedule element 800.
  • Bitmap information 850 and 860 may be allocated only at the current beacon interval without repetition.
  • the TDD slot schedule element Bitmap information 850 and 860 included in 800 may be repeated during subsequent beacon intervals of an integer multiple (Y).
  • the last bits 970 and B71 of the slot schedule control field 900 of FIG. 9 may be reserved.
  • FIG. 10 is a flowchart illustrating an STA view of a method for supporting TDD in a WLAN system according to an exemplary embodiment.
  • the application time point may be adjusted such that adjacent distribution networks (DNs) simultaneously apply the same TDD slot structure, and it may be easy to apply the same TDD slot structure.
  • DNs adjacent distribution networks
  • the TDD slot structure element when the TDD slot structure element is not received, a problem caused by access based on the corresponding information can be prevented.
  • the TDD slot structure element is transmitted only once, a malfunction caused by not receiving the TDD slot structure element can be prevented by using a count down technique.
  • the slot structure is applied when the TDD slot structure element is received.
  • the TDD slot structure element is not received, there is a possibility of malfunction, and it may be difficult to meet the application timing of the TDD slot structure element between the DNs.
  • the first wireless terminal may include an information element associated with a TDD SP structure of a TDD SP for a TDD channel access (hereinafter, referred to as a 'TDD SP'). And a beacon frame containing the " structure information element ") from the second wireless terminal.
  • a 'TDD SP' an information element associated with a TDD SP structure of a TDD SP for a TDD channel access
  • the information element (that is, the TDD SP structure information element) according to the present embodiment may include slot structure change time information associated with a time point when the TDD SP structure is applied.
  • the first wireless terminal determines that information element (that is, a TDD SP).
  • a TDD SP structure associated with a structure information element) may be applied.
  • the first wireless terminal may apply the TDD SP structure based on the slot structure change time information. For example, when a time point based on slot structure change time information elapses, a TDD SP structure included in an information element (that is, a TDD SP structure information element) may be applied.
  • a TDD SP structure included in an information element that is, a TDD SP structure information element
  • a TDD SP structure preset for the first wireless terminal may be applied until a time point based on the slot structure change time information elapses.
  • the slot structure change time information may be set based on a timing synchronization function (TSF) timer.
  • TSF timing synchronization function
  • the TDD SP structure may include a plurality of consecutive and adjacent TDD intervals of FIG. 4.
  • each of the plurality of TDD intervals may include one or more TDD slots of FIG. 4.
  • the information element may include information associated with the number of one or more TDD slots included in each of the plurality of TDD intervals.
  • the information element ie, the TDD SP structure information element
  • the information element may include information associated with the duration of each of the plurality of TDD intervals.
  • an information element ie, TDD SP structure information element
  • TDD SP structure information element may include information associated with a guard time between one or more TDD slots (eg, GT2 of FIG. 4).
  • the first wireless terminal may communicate with the second wireless terminal based on the applied TDD SP structure.
  • information on a specific time to which the corresponding TDD SP structure is to be signaled may be signaled based on the slot structure change time information.
  • the slot structure change time information may be set based on N (positive integer) bits.
  • N bits may be included in a TDD slot structure element format, a Slot structure control field format, a TDD slot schedule element format, or a Slot schedule control field format.
  • reserved bits of a previously defined format may be used for N bits.
  • N bits may be defined in addition to the previously defined format.
  • the time unit informed by the defined N bits may be determined by one of a timing synchronization function (TSF), a time in seconds (ns, us, ms), or a time in minutes.
  • TSF timing synchronization function
  • 11 and 12 are diagrams illustrating a frame format for supporting TDD in a WLAN system according to an embodiment.
  • a slot structure change time field 1180 having an N octet length may be added to the format (eg, 1110 to 1170) of the TDD slot structure element of FIG. 5.
  • a slot structure change time field 1270 having an N bit length may be added to a format (eg, 1210 to 1260) of the slot structure control field of FIG. 6.
  • a value in which a predefined time unit is applied to a value converted based on the slot structure change time fields 1180 and 1270 is associated with the slot structure change time information mentioned in FIG. 10. Will be understood.
  • FIG. 13 and 14 illustrate a frame format for supporting TDD in a WLAN system according to another exemplary embodiment.
  • a method for notifying how many beacon intervals are applied after a TDD SP structure associated with an information element included in a beacon frame ie, a TDD SP structure information element
  • information about how many beacon intervals the TDD SP structure is applied after may be set based on N (positive integer) bits.
  • N bits may be included in a TDD slot structure element format, a Slot structure control field format, a TDD slot schedule element format, or a Slot schedule control field format. Meanwhile, reserved bits of a previously defined format may be used for N bits. Alternatively, N bits may be defined in addition to the previously defined format.
  • the slot structure element information is directly applied in the current beacon interval.
  • the value of the N bit is another positive integer value M, it may be signaled that the content of the slot structure element included in the currently transmitted beacon frame is applied after the M beacon intervals.
  • a slot structure change count field for indicating when a TDD slot included in an information element ie, a TDD SP structure information element
  • a slot structure change count field for indicating when a TDD slot included in an information element may be defined as follows. have.
  • a slot structure change time field 1380 having an N octet length may be added to the format (eg, 1310 to 1370) of the TDD slot structure element of FIG. 5.
  • a slot structure change time field 1470 having an N bit length may be added to a format (eg, 1410 to 1460) of the slot structure control field of FIG. 6.
  • the slot structure change time field may be defined as an integer number of N bits of 1 bit or more.
  • the slot structure change time field defined by N bits is converted into a specific value M
  • the TDD SP structure included in the corresponding information element that is, the TDD SP structure information element
  • Application after the beacon interval may be signaled.
  • FIG. 15 is a flowchart illustrating an AP view of a method for supporting TDD in a WLAN system according to an exemplary embodiment.
  • the first wireless terminal determines an information element (ie, TDD SP structure information element) associated with a TDD SP structure of a TDD SP (service period) for TDD channel access.
  • Beacon frame including a) may be transmitted to the second wireless terminal.
  • the information element (that is, the TDD SP structure information element) according to the present embodiment may include slot structure change time information associated with a time point when the TDD SP structure is applied.
  • the first wireless terminal may apply the TDD SP structure based on the received slot structure change time information. For example, when a time point based on slot structure change time information elapses, a TDD SP structure included in an information element (that is, a TDD SP structure information element) may be applied.
  • a TDD SP structure included in an information element that is, a TDD SP structure information element
  • a TDD SP structure preset for the first wireless terminal may be applied until a time point based on the slot structure change time information elapses.
  • the slot structure change time information may be set based on a timing synchronization function (TSF) timer.
  • TSF timing synchronization function
  • the TDD SP structure may include a plurality of consecutive and adjacent TDD intervals of FIG. 4.
  • each of the plurality of TDD intervals may include one or more TDD slots of FIG. 4.
  • the information element may include information associated with the number of one or more TDD slots included in each of the plurality of TDD intervals.
  • the information element may include information associated with the duration of each of the plurality of TDD intervals.
  • the information element may include information associated with a guard time between one or more TDD slots (eg, GT2 of FIG. 4).
  • the first wireless terminal may communicate with the second wireless terminal based on the slot structure change time information included in the TDD SP structure information element. That is, the first wireless terminal can communicate with the second wireless terminal based on the applied TDD SP structure.
  • information on a specific time to which the corresponding TDD SP structure is to be signaled may be signaled based on the slot structure change time information.
  • the slot structure change time information may be set based on N (positive integer) bits.
  • N bits may be included in a TDD slot structure element format, a Slot structure control field format, a TDD slot schedule element format, or a Slot schedule control field format.
  • reserved bits of a previously defined format may be used for N bits.
  • N bits may be defined in addition to the previously defined format.
  • the time unit informed by the defined N bits may be determined by one of a timing synchronization function (TSF), a time in seconds (ns, us, ms), or a time in minutes.
  • TSF timing synchronization function
  • 16 is a block diagram illustrating a wireless device to which an embodiment can be applied.
  • the wireless device may be implemented as an AP or a non-AP STA as an STA capable of implementing the above-described embodiment.
  • the wireless device may correspond to the above-described user, or may correspond to a transmitting terminal for transmitting a signal to the user.
  • the wireless device of FIG. 16 includes a processor 1610, a memory 1620, and a transceiver 1630 as shown.
  • the illustrated processor 1610, memory 1620, and transceiver 1630 may be implemented as separate chips, or at least two blocks / functions may be implemented through one chip.
  • the transceiver 1630 is a device including a transmitter and a receiver. When a specific operation is performed, only one of the transmitter and the receiver may be performed, or both the transmitter and the receiver may be performed. have.
  • the transceiver 1630 may include one or more antennas for transmitting and / or receiving wireless signals.
  • the transceiver 1630 may include an amplifier for amplifying a received signal and / or a transmitted signal and a bandpass filter for transmission on a specific frequency band.
  • the processor 1610 may implement the functions, processes, and / or methods proposed herein.
  • the processor 1610 may perform an operation according to the present embodiment described above. That is, the processor 1610 may perform the operation disclosed in the embodiment of FIGS. 1 to 15.
  • the processor 1610 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, a data processing device, and / or a converter for translating baseband signals and wireless signals.
  • ASIC application-specific integrated circuit
  • Memory 1620 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices.
  • ROM read-only memory
  • RAM random access memory
  • flash memory memory cards, storage media, and / or other storage devices.
  • 17 is a block diagram illustrating an example of an apparatus included in a processor.
  • FIG. 17 For convenience of description, an example of FIG. 17 is described based on a block for a transmission signal, but it is obvious that the reception signal can be processed using the block.
  • the illustrated data processor 1710 generates transmission data (control data and / or user data) corresponding to the transmission signal.
  • the output of the data processor 1710 may be input to the encoder 1720.
  • the encoder 1720 may perform coding through a binary convolutional code (BCC) or a low-density parity-check (LDPC) technique. At least one encoder 1720 may be included, and the number of encoders 1720 may be determined according to various information (eg, the number of data streams).
  • BCC binary convolutional code
  • LDPC low-density parity-check
  • the output of the encoder 1720 may be input to the interleaver 1730.
  • the interleaver 1730 performs an operation of distributing consecutive bit signals over radio resources (eg, time and / or frequency) to prevent burst errors due to fading or the like.
  • Radio resources eg, time and / or frequency
  • At least one interleaver 1730 may be included, and the number of the interleaver 1730 may be determined according to various information (eg, the number of spatial streams).
  • the output of the interleaver 1730 may be input to a constellation mapper 1740.
  • the constellation mapper 1740 may perform constellation mapping such as biphase shift keying (BPSK), quadrature phase shift keying (QPSK), quadrature amplitude modulation (n-QAM), and the like.
  • the output of the constellation mapper 1740 may be input to the spatial stream encoder 1750.
  • the spatial stream encoder 1750 may perform data processing to transmit a transmission signal through at least one spatial stream.
  • the spatial stream encoder 1750 may perform at least one of space-time block coding (STBC), cyclic shift diversity (CSD) insertion, and spatial mapping on a transmission signal.
  • STBC space-time block coding
  • CSS cyclic shift diversity
  • the output of the spatial stream encoder 1750 may be input to an IDFT 1760 block.
  • the IDFT 1760 block may perform an inverse discrete Fourier transform (IDFT) or an inverse Fast Fourier transform (IFFT).
  • IDFT inverse discrete Fourier transform
  • IFFT inverse Fast Fourier transform
  • the output of the IDFT 1760 block may be input to the Guard Interval (GI) inserter 1770, and the output of the GI inserter 1770 may be input to the transceiver 1630 of FIG. 16.
  • GI Guard Interval

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de prise en charge de TDD qui est exécuté par un premier terminal sans fil dans un système LAN sans fil, comprenant les étapes consistant à : recevoir, en provenance d'un second terminal sans fil, une trame de balise comprenant un élément d'informations associé à une structure de SP TDD d'un SP TDD pour un accès au canal TDD, l'élément d'informations comprenant des informations d'instant de changement de structure de créneau associées à un instant auquel la structure de SP TDD doit être appliquée ; appliquer la structure de SP TDD sur la base des informations d'instant de changement de structure de créneau ; et communiquer avec le second terminal sans fil sur la base de la structure de SP TDD appliquée.
PCT/KR2019/003235 2018-03-20 2019-03-20 Procédé de prise en charge de planification tdd dans un système lan sans fil et terminal sans fil l'utilisant WO2019182347A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2018-0031932 2018-03-20
KR20180031932 2018-03-20
KR20180040280 2018-04-06
KR10-2018-0040280 2018-04-06

Publications (1)

Publication Number Publication Date
WO2019182347A1 true WO2019182347A1 (fr) 2019-09-26

Family

ID=67987913

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2019/003235 WO2019182347A1 (fr) 2018-03-20 2019-03-20 Procédé de prise en charge de planification tdd dans un système lan sans fil et terminal sans fil l'utilisant

Country Status (1)

Country Link
WO (1) WO2019182347A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017043950A1 (fr) * 2015-09-12 2017-03-16 엘지전자 주식회사 Procédé pour réaliser une communication par tdd par un terminal dans un système de communication sans fil et terminal l'utilisant
WO2017069432A1 (fr) * 2015-10-18 2017-04-27 엘지전자 주식회사 Procédé et dispositif de communication à l'aide d'une trame sans fil dans un système de communication sans fil à base de tdd
WO2017086566A1 (fr) * 2015-11-18 2017-05-26 엘지전자 주식회사 Procédé d'émission/réception de signaux au moyen d'un schéma de duplexage par répartition dans le temps dans un système de communication sans fil, et dispositif de communication associé
WO2017179921A1 (fr) * 2016-04-14 2017-10-19 엘지전자 주식회사 Procédé de fonctionnement conformément à une configuration de liaison montante-liaison descendante tdd modifiée dans un système de communication sans fil, et appareil associé

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017043950A1 (fr) * 2015-09-12 2017-03-16 엘지전자 주식회사 Procédé pour réaliser une communication par tdd par un terminal dans un système de communication sans fil et terminal l'utilisant
WO2017069432A1 (fr) * 2015-10-18 2017-04-27 엘지전자 주식회사 Procédé et dispositif de communication à l'aide d'une trame sans fil dans un système de communication sans fil à base de tdd
WO2017086566A1 (fr) * 2015-11-18 2017-05-26 엘지전자 주식회사 Procédé d'émission/réception de signaux au moyen d'un schéma de duplexage par répartition dans le temps dans un système de communication sans fil, et dispositif de communication associé
WO2017179921A1 (fr) * 2016-04-14 2017-10-19 엘지전자 주식회사 Procédé de fonctionnement conformément à une configuration de liaison montante-liaison descendante tdd modifiée dans un système de communication sans fil, et appareil associé

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHEN, CHENG: "Resolution to CIDs related to TDD scheduling-part 1", IEEE 802.1 1-18/0355R2, 3 March 2018 (2018-03-03) *

Similar Documents

Publication Publication Date Title
WO2018190697A1 (fr) Procédé de communication sans fil utilisant un identifiant bss et terminal de communication sans fil l'utilisant
WO2016175435A1 (fr) Procédé de transmission mu ul d'une station fonctionnant en mode d'économie d'énergie, et dispositif pour l'exécution du procédé
WO2016204574A1 (fr) Procédé de communication sans fil et terminal de communication sans fil permettant de recevoir des données en provenance d'une pluralité de terminaux de communication sans fil
WO2017026784A1 (fr) Procédé et dispositif permettant de former un signal de commande comprenant un champ de commande dans un système de réseau local (lan) sans fil
WO2021033945A1 (fr) Procédé de configuration de ressource de liaison latérale dans un système de communication
WO2016111435A1 (fr) Procédé et dispositif permettant de transmettre une trame contenant des bits de contrôle d'erreurs pour un en-tête dans un réseau lan sans fil
WO2018164554A1 (fr) Procédé d'émission et de réception d'un signal contenant une unité de données de protocole physique (ppdu) dans un système lan sans fil (wlan), et un appareil associé.
WO2018131800A1 (fr) Procédé d'émission et de réception d'un signal dans un système de réseau local sans fil et dispositif associé
WO2016068669A1 (fr) Procédé et dispositif d'attribution d'unités de ressource dans un lan sans fil
WO2017164687A1 (fr) Procédé de gestion de puissance dans un système lan sans fil et terminal sans fil l'utilisant
WO2021251696A1 (fr) Procédé et appareil pour effectuer une reconfiguration de liaison entre des mld dans un système lan sans fil
WO2019009596A1 (fr) Procédé de transmission de trame basé sur de multiples canaux canalisés dans un système lan sans fil et terminal sans fil utilisant ledit procédé
WO2019107848A1 (fr) Procédé d'émission ou de réception d'informations de mesure de canal dans un système lan sans fil et appareil associé
WO2017065543A1 (fr) Procédé de transmission d'informations indiquant un type de trame au sein d'un système de réseau local sans fil et dispositif associé
WO2016056830A1 (fr) Procédé et appareil de transmission de données sur une unité de ressources comprenant une tonalité pilote dans un wlan
WO2017030428A1 (fr) Procédé de communication sans fil utilisant des informations de commande, et terminal de communication sans fil
WO2016137201A1 (fr) Procédé et dispositif de transmission de signal en utilisant une unité de ressource incluant une pluralité de sous-porteuses
WO2022060186A1 (fr) Dispositif et procédé de transmission fronthaul dans un système de communication sans fil
WO2018084404A1 (fr) Procédé et dispositif de réutilisation spatiale, pour transmettre une ppdu dans un système lan sans fil
WO2018194233A1 (fr) Procédé d'émission et de réception de signal dans un système de réseau local sans fil et appareil pour ledit procédé
WO2018194234A1 (fr) Procédé d'émission et de réception d'un signal dans un système de réseau local sans fil et appareil pour ledit procédé
WO2020180007A1 (fr) Transmission de signal à l'aide d'une pluralité d'ap
WO2022186672A1 (fr) Procédé et dispositif d'émission et de réception d'un profil complet dans un élément ml dans un système lan sans fil
WO2016064168A2 (fr) Procédé de communication sans fil, et terminal de communication sans fil
WO2019045213A1 (fr) Procédé de prise en charge de formation de faisceau dans un système lan sans fil et appareil correspondant

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: 19772392

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19772392

Country of ref document: EP

Kind code of ref document: A1