WO2024034846A1 - Electronic device, and method for integrated control of mlo and r-twt - Google Patents

Abstract

An electronic device according to an embodiment may comprise: one or more wireless communication modules for transmitting/receiving wireless signals; one or more processors operatively connected to the wireless communication module; and a memory, which is electrically connected to the processor and stores instructions executable by the processor. When the instructions are executed by the processor, the processor can: receive at least one beacon signal including information about an R-TWT service interval of each link included in multi-links; determine at least one link from among the multi-links on the basis of the beacon signal; and transmit/receive data on the basis of the at least one link. Other various embodiments are possible.

Description

Electronics and integrated control method of MLO and R-TWT

Embodiments of the present invention relate to an electronic device and an integrated control method of MLO and R-TWT (restricted target wake time).

With the advent of electronic devices such as smartphones, tablet PCs, or laptops, the demand for high-speed wireless connections has grown explosively. Thanks to this trend and the increasing demand for high-speed wireless connections, the IEEE 802.11 wireless communication standard is firmly established as a representative and general-purpose high-speed wireless communication standard in the IT (information technology) industry. Early wireless LAN technology developed around 1997 could support transmission speeds of up to 1 to 2 Mbps. Since then, as wireless LAN technology has steadily developed based on the demand for faster wireless connections, new wireless LAN technologies that improve transmission speeds, such as IEEE 802.11n, 802.11ac, or 802.11ax, have been steadily developed. Currently, the latest standard, IEEE 802.11ax, has a maximum transmission rate of several Gbps.

Currently, wireless LANs encompass not only private places such as homes, but also various public places such as offices, airports, stadiums, or stations, providing high-speed wireless connections to users throughout society. Accordingly, wireless LAN has had a significant impact on people's lifestyle or culture, and wireless LAN has now become a lifestyle in modern people's lives.

An electronic device according to an embodiment includes one or more wireless communication modules configured to transmit and receive wireless signals, one or more processors operatively connected to the wireless communication modules, and a device electrically connected to the processor and executable by the processor. It may include memory for storing instructions. When the instructions are executed by the processor, the processor may receive at least one beacon signal containing information about the R-TWT service section of each link included in the multiple links. The processor may determine at least one link among the multiple links based on the beacon signal. The processor may transmit and receive data based on the at least one link. The R-TWT service section may be dynamically configured based on different QoS requirements for each service type to be executed in peripheral devices including the electronic device.

A method of operating an electronic device according to an embodiment may include receiving at least one beacon signal containing information about the R-TWT service section of each link included in multiple links. The method of operating the electronic device may include determining at least one link among the multiple links based on the beacon signal. The method of operating the electronic device may include transmitting and receiving data based on the at least one link. The R-TWT service section may be dynamically configured based on different QoS requirements for each service type to be executed in peripheral devices including the electronic device.

Figure 1 shows an example of a wireless LAN system according to embodiments.

Figure 2 shows an example of a wireless LAN system according to an embodiment.

Figure 3 is a diagram for explaining an example of a link setup operation according to an embodiment.

Figure 4 is an example to explain an MLO operation according to an embodiment.

Figure 5 is an example to explain an MLO operation according to an embodiment.

Figure 6 is a diagram for explaining the R-TWT protocol according to an embodiment.

Figure 7 is a diagram for explaining TWT elements used in the R-TWT protocol according to an embodiment.

Figure 8 shows an example of a schematic block diagram of non-AP MLD according to an embodiment.

FIG. 9 is a diagram illustrating an operation of an AP MLD according to an embodiment to set different R-TWT service sections for each link included in multiple links.

Figures 10 and 11 show an example of an operation in which a non-AP MLD determines a link based on the QoS of a service according to an embodiment.

Figure 12 is an example of a flowchart to explain a non-AP MLD operation method according to an embodiment.

Figure 13 is a block diagram of an electronic device in a network environment, according to one embodiment.

Hereinafter, embodiments will be described in detail with reference to the attached drawings. In the description with reference to the accompanying drawings, identical components will be assigned the same reference numerals regardless of the reference numerals, and overlapping descriptions thereof will be omitted.

Figure 1 shows an example of a wireless LAN system according to an embodiment.

Referring to FIG. 1, according to one embodiment, the wireless LAN system 10 uses an infrastructure mode in which an access point (AP) exists in the structure of a wireless LAN (WLAN) of IEEE (Institute of Electrical and Electronic Engineers) 802.11 ( It may indicate infrastructure mode. The wireless LAN system 10 may include one or more basic service sets (BSS) (eg, BSS1, BSS2). BSS (BSS1, BSS2) is an access point (AP) and a station (STA) (e.g., the electronic device 1301, electronic device 1302, and electronic device 1304 in FIG. 13) that can synchronize and communicate with each other. It can mean a set. BSS1 may include AP1 and STA1, and BSS2 may include AP2, STA2, and STA3.

According to one embodiment, the wireless LAN system 10 includes at least one STA (STA1 to STA3), a plurality of APs (AP1, AP2) that provide distribution services, and a plurality of APs (AP1, AP2) It may include a distribution system 100 that connects. The distributed system 100 can connect a plurality of BSSs (BSS1, BSS2) to implement an extended service set (ESS), which is an extended service set. ESS can be used as a term to indicate a network formed by connecting multiple APs (AP1, AP2) through the distributed system 100. Multiple APs (AP1, AP2) included in one ESS may have the same service set identification (SSID).

According to one embodiment, STAs (STA1 to STA3) use medium access control (MAC) and physical layer for wireless media following the provisions of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. It can be any functional medium that includes an interface. STAs (STA1 to STA3) can be used to include both APs and non-AP STAs (Non-AP stations). STAs (STA1~STA3) are electronic devices, mobile terminals, wireless devices, wireless transmit/receive units (WTRU), and user equipment (UE). , a mobile station (MS), a mobile subscriber unit, or simply a user.

Figure 2 shows an example of a wireless LAN system according to an embodiment.

Referring to FIG. 2, according to one embodiment, the wireless LAN system 20, unlike the wireless LAN system 10 of FIG. 1, has a wireless LAN (WLAN) structure of IEEE (Institute of Electrical and Electronic Engineers) 802.11. This may indicate an ad-hoc mode in which communication is performed by setting up a network between a plurality of STAs (STA1 to STA3) without an AP. The wireless LAN system 20 may include a BSS that operates in an ad-hoc mode, that is, an independent basic service set (IBSS).

According to one embodiment, because the IBSS does not include an AP, there may be no centralized management entity. In IBSS, STAs can be managed in a distributed manner. In IBSS, all STAs can be mobile STAs, and access to distributed systems is not allowed, so a self-contained network (or self-contained network) can be formed.

Figure 3 is a diagram for explaining an example of a link setup operation according to an embodiment.

Referring to FIG. 3, according to one embodiment, a link setup operation may be performed between devices (e.g., STA 301 and AP 401) to communicate with each other. For link setup, network discovery, authentication, establishment of association, and security setup operations may be performed. The link setup operation may be referred to as a session initiation operation or session setup operation. Additionally, the discovery, authentication, association, and security setting operations of the link setup operation may be collectively referred to as the association operation.

According to one embodiment, the network discovery operation may include operations 310 and 320. In operation 310, the STA 301 (e.g., the electronic device 1301, electronic device 1302, or electronic device 1304 in FIG. 13) sends a probe request frame to discover which AP exists. You can transmit and wait for a response to the probe request frame. The STA 301 may perform a scanning operation to access a network to find a network in which it can participate. The probe request frame may include information of the STA 301 (e.g., device name and/or address of the STA 301). The scanning operation in operation 310 may mean an active scanning operation. In operation 320, the AP 401 may transmit a probe response frame in response to the probe request frame to the STA 301 that transmitted the probe request frame. The probe response frame may include information about the AP 401 (eg, device name and/or network information of the AP 401). Although the network discovery operation is shown in FIG. 3 as being performed through active scanning, it is not necessarily limited to this, and when the STA 301 performs passive scanning, the transmission operation of the probe request frame may be omitted. The STA 301 performing passive scanning may receive the beacon frame transmitted by the AP 401 and perform the following subsequent procedures.

According to one embodiment, after the STA 301 discovers the network, an authentication operation including operations 330 and 340 may be performed. In operation 330, the STA 301 may transmit an authentication request frame to the AP 401. In operation 340, the AP 401 may determine whether to allow authentication for the corresponding STA 301 based on information included in the authentication request frame. The AP 401 may provide the result of the authentication process to the STA 301 through an authentication response frame. The authentication frame used for authentication request/response may correspond to a management frame.

According to one embodiment, the authentication frame includes an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a robust security network (RSN), Alternatively, it may include information about a finite cyclic group.

According to one embodiment, after the STA 301 is successfully authenticated, an association operation including operations 350 and 360 may be performed. In operation 350, the STA 301 may transmit an association request frame to the AP 401. In operation 360, the AP 401 may transmit an association response frame to the STA 301 in response to the association request frame.

According to one embodiment, the association request frame and/or the association response frame may include information related to various capabilities. For example, the connection request frame contains information related to various capabilities, beacon listen interval, service set identifier (SSID), supported rates, supported channels, RSN, and mobility domain. , may include information about supported operating classes, TIM broadcast request (traffic indication map broadcast request), and/or interworking service capabilities. For example, the connection response frame may contain information related to various capabilities, status code, association ID (AID), supported rate, enhanced distributed channel access (EDCA) parameter set, received channel power indicator (RCPI), and received signal to noise (RSNI). indicator), mobility domain, timeout interval (association comeback time), overlapping BSS scan parameters, TIM broadcast response, and/or QoS map.

According to one embodiment, after the STA 301 is successfully associated with the network, a security setup operation including operations 370 and 380 may be performed. Security setup operations may be performed through RSNA (robust security network association) request/response. For example, the security setup operation may include private key setup through 4-way handshaking through an extensible authentication protocol over LAN (EAPOL) frame. The security setup operation may be performed according to a security method not defined in the IEEE 802.11 standard.

According to one embodiment, a security session is established between the STA (301) and the AP (401) according to a security setup operation, and the STA (301) and the AP (401) can perform secure data communication.

Figure 4 is an example to explain an MLO operation according to an embodiment.

Referring to FIG. 4, according to one embodiment, an AP access point multi-link device (MLD) 501 (e.g., AP 401 in FIG. 3) and a non-AP MLD 601 (e.g., in FIG. 3) The STA (301) can perform a multi-link operation (MLO) that communicates using a plurality of individual links (eg link 1, link 2, link 3). The AP MLD 501 may be a device including one or more APs (eg, AP1, AP2, AP3). The AP MLD 501 may be a device connected to a logical link control (LLC) layer through one interface (e.g., MAC service access point (SAP)). One or more APs (eg, AP1, AP2, AP3) included in the AP MLD 501 may share some functions in the MAC (medium access control) layer. APs in the AP MLD 501 may operate on different links (e.g., AP1 operates through link 1, AP2 operates through link 2, and AP3 operates through link 3). Link may refer to a channel or band. APs (eg, AP1, AP2, AP3) in the AP MLD 501 can each be responsible for a corresponding link and can perform the role of an independent AP.

According to one embodiment, the non-AP MLD 601 may be a device including one or more non-APs (eg, STA1, STA2, STA3). The non-AP MLD 601 may be a device connected to the logical link control (LLC) layer through one interface (e.g., MAC service access point (SAP)). One or more non-APs (e.g., STA1, STA2, STA3) included in the non-AP MLD 601 may share some functions in the MAC layer. STAs in the non-AP MLD 601 may operate on different links (e.g., STA1 operates through link 1, STA2 operates through link 2, and STA3 operates through link 3). STAs (e.g., STA1, STA2, STA3) in the non-AP MLD 601 may each be responsible for a corresponding link and may perform the role of an independent STA. Non-AP MLD may also be expressed as STA MLD.

According to one embodiment, when the AP MLD 501 includes multiple APs (e.g., AP1, AP2, and AP3), each AP (e.g., AP1, AP2, and AP3) has a separate link (e.g., link 1). , link 2, link 3) can be configured to perform frame transmission and reception operations using each STA (e.g., STA1, STA2, STA3) included in the non-AP MLD (601) and multiple links. For example, each link may operate in the 2.4 GHz, 5 GHz, or 6 GHz bands.

Figure 5 is an example for explaining an MLO operation according to an embodiment.

Referring to FIG. 5, according to one embodiment, MLD (e.g., AP MLD 501) (e.g., AP 401 in FIG. 3 and non-AP MLD 601 (e.g., STA 301 in FIG. 3)) You can check the schematic diagram of communication between AP MLD 501 and/or non-AP MLD 601 may transmit uplink data or downlink data through multi-link operation. AP The MLD 501 may communicate with the non-AP MLD 601 through multiple links (e.g. link 1, link 2). STA 1 of the non-AP MLD 601 communicates with the AP MLD (601) through link 1. 501) can communicate with AP 1 of the non-AP MLD 601. STA 1 of the non-AP MLD 601 can receive data from AP 1 of the AP MLD 501 through link 1. Link 1 may be downlink. STA 2 of the non-AP MLD (601) can communicate with AP 2 of the AP MLD (501) through link 2. STA 2 of the non-AP MLD (601) can communicate with AP MLD (501) through link 2. Data can be transmitted to AP 2. Link 2 can be uplink.

According to one embodiment, a mapping between a traffic identifier (TID) and a link may be established. TID may be information about the priority of traffic. Frames corresponding to a TID of a specific value can only be exchanged through a pre-designated link. The mapping between TIDs and links can be set to be directional-based. For example, link 1 may be set so that the frame corresponding to the first TID is transmitted from AP1 of the AP MLD (501) to STA1 of the non-AP MLD (601). For example, link 2 may be set so that the frame corresponding to the second TID is transmitted from STA2 of the non-AP MLD (601) to AP2 of the AP MLD (501). If no mapping is established between TIDs and links, all TIDs can be exchanged on any one link.

Figure 6 is a diagram for explaining the R-TWT protocol according to an embodiment.

According to one embodiment, in a wireless communication system (e.g., wireless communication system 10 in FIG. 1, wireless communication system 20 in FIG. 2), a non-AP MLD 601 (e.g., STA 301 in FIG. 3) )) and/or the AP MLD 501 (e.g., AP 401 in FIG. 3) may perform wireless communication according to the restricted target wake time (R-TWT) protocol. The R-TWT protocol may be a protocol for supporting a latency demanding service that transmits and receives latency sensitive traffic. The R-TWT protocol may be a technology that preferentially secures transmission and reception time for latency-sensitive traffic using broadcast TWT. Latency-sensitive traffic may be traffic included in a predefined access category (AC). Latency-sensitive traffic may be traffic assigned a predefined traffic identifier (TID). Latency may refer to latency defined in IEEE 802.11ax. Latency may refer to the interval between when a packet is transmitted from the source and when the packet reaches the destination.

According to one embodiment, the AP MLD 501 (e.g., AP 401 in FIG. 3) and/or the non-AP MLD 601 (e.g., STA 301 in FIG. 3) configures TWT settings (e.g., TWT Wireless communication can be performed based on parameters). TWT parameters may be operating parameters (e.g., periodic parameters and/or aperiodic parameters) for communication between the AP MLD 501 and the non-AP MLD 601 based on the TWT protocol. The TWT parameter may include information about the R-TWT service period (SP). For example, the TWT parameters include start time information of the R-TWT service section, duration information of the R-TWT service section, and/or R-TWT interval information of the R-TWT service section. may include.

According to one embodiment, AP MLD 501 (e.g., AP 401 in FIG. 3) may implement the R-TWT protocol through broadcast TWT. In broadcast TWT, an AP (e.g., AP 401 in FIG. 3, AP MLD 501) performs scheduling in advance for the R-TWT service section, and STA (e.g., STA 301 in FIG. 3, non- -AP MLD (601) may request membership for the scheduled R-TWT service section. Broadcast TWT includes an operation in which an AP (e.g., AP 401 and AP MLD 501 in FIG. 3) advertises a beacon signal (e.g., beacon signal 610) including a TWT element. can do. Beacon signal 610 may include a TWT element (e.g., the TWT element in FIG. 7). The TWT element may include TWT parameters. TWT parameters may include information about the R-TWT service section.

According to one embodiment, the AP MLD 501 (e.g., AP 401 in FIG. 3) includes information about the R-TWT service period (SP) of the link, information about the TID mapped to the link, and A beacon signal 610 containing information about the direction of the link (eg, uplink, downlink) may be advertised. A non-AP MLD (601) that wishes to transmit (or receive) traffic mapped to the link during the R-TWT service section of the link (e.g., the STA (301) in FIG. 3 may transmit a membership request frame to the AP MLD (501). If the AP MLD (501) allows the membership request of the non-AP MLD (601), the non-AP MLD (601) may transmit (or receive) traffic mapped to the link during the R-TWT service period. You can.

According to one embodiment, a beacon signal (eg, beacon signal 610) may be advertised for each link included in multiple links of the AP MLD (501). That is, the beacon signal may include information about the corresponding link (e.g., information about the R-TWT service section of the link, information about the TID mapped to the link, and information about the direction of the link). The beacon signal may include not only information about the corresponding link, but also information about links different from the corresponding link. The non-AP MLD 601 may request membership from the AP MLD 501 for the link corresponding to the beacon signal. The non-AP MLD (601) provides membership to the AP MLD (501) for the other link based on information about the other link included in the beacon signal (e.g., information about the link that is different from the link corresponding to the beacon signal). You can request.

Figure 7 is a diagram for explaining TWT elements used in the R-TWT protocol according to an embodiment.

Referring to FIG. 7, according to one embodiment, the TWT element may be a broadcast TWT parameter set field format according to IEEE 802.11 (eg, IEEE 802.11ax). The TWT element includes a request type field, target wake time field, nominal minimum TWT wake duration field, and TWT wake interval mantissa field. field), a broadcast TWT information field, and a restricted TWT traffic ID information field. At this time, the request type field includes a plurality of sub-fields, for example, a TWT request field, a TWT setup command field, a trigger field, and a last broadcast parameter set field ( It may include a last broadcast parameter set field, a flow type field, a broadcast TWT recommendation field, a TWT wake interval exponent field, and a reserved field. .

According to one embodiment, the TWT element may include a TWT parameter. TWT parameters may include information about the R-TWT service section. Information about the R-TWT service section may include start time information of the R-TWT service section, duration information of the R-TWT service section, and/or interval information of the R-TWT service section. TWT parameters can be determined by setting the value of one or more fields among a plurality of fields included in the TWT element. The starting point of the TWT service section may be set in the target wake time field of the TWT element, and the TWT duration for which the TWT service section continues (or is maintained) may be set in the nominal minimum TWT wake duration field of the TWT element. The TWT interval (e.g., interval value) of the TWT service section may be determined by the values set in the TWT wake interval mentisa field and the TWT wake interval exponent field of the TWT element. In the TWT wake interval mantissa field, information about the mantissa for determining the TWT interval is set, and in the TWT wake interval exponent field, an exponent value for determining the TWT interval with a base of 2 is set. Information about value) can be set. The size of the TWT interval can be determined based on TWT wake interval mentisa x2 (TWT wake interval exponent).

According to one embodiment, the broadcast TWT information field includes a plurality of sub-fields, for example, a restricted TWT traffic info present field, a restricted TWT full schedule field ( It may include a restricted TWT schedule full filed), a reserved field, a broadcast TWT ID field, and a broadcast TWT persistence field. The restricted TWT traffic info present field may be set to 1 when a restricted TWT parameter set exists, indicating the presence of a restricted TWT traffic info field. If the AP performing R-TWT scheduling is unlikely to allow new membership in the schedule, the restricted TWT schedule full field may appear set to 1. The broadcast TWT ID field may include information about the broadcast TWT ID. The broadcast TWT ID field may be used to determine the mapping between the TWT ID and the TWT service section. The broadcast TWT duration field may include information about the period during which broadcast TWT information lasts. The broadcast TWT persistence field may include information about the beacon period.

According to one embodiment, the restricted TWT traffic information field includes a plurality of sub-fields, e.g., a traffic information control field, a restricted TWT downlink traffic ID bitmap ( It may include a restricted TWT downlink traffic identifier bitmap field) and a restricted TWT uplink traffic ID bitmap (restricted TWT uplink traffic identifier bitmap field). The restricted TWT traffic information field may exist when the value of the restricted TWT traffic information present field is 1. The traffic information control field may include a downlink traffic ID bitmap valid field, an uplink traffic ID bitmap valid field, and a reserved field. The downlink traffic ID bitmap valid field may indicate whether there is valid information in the limited TWT downlink traffic ID bitmap field. If the value of the downlink traffic ID bitmap valid field is 0, downlink traffic of all traffic IDs is identified as latency sensitive traffic, and the limited TWT downlink traffic ID bitmap field may be reserved. The uplink traffic ID bitmap valid field may indicate whether there is valid information in the restricted TWT uplink traffic ID bitmap field. If the value of the uplink traffic ID bitmap valid field is 0, uplink traffic of all traffic IDs is identified as latency sensitive traffic, and the restricted TWT uplink traffic ID bitmap field may be reserved. The restricted TWT downlink traffic ID bitmap field and the restricted TWT uplink traffic ID bitmap field determine which traffic ID (TID) is used in the downlink direction in the latency sensitive traffic stream by the TWT scheduling AP or TWT scheduled STA, respectively. And it can be specified whether it is identified in the uplink direction. If the bit position k value of the bitmap is 1, traffic ID k may be classified as a latency sensitive traffic stream. If the bit position k value of the bitmap is 0, traffic ID k may not be classified as a latency sensitive traffic stream.

Figure 8 shows an example of a schematic block diagram of non-AP MLD according to an embodiment.

According to one embodiment, the non-AP MLD 601 (e.g., STA 301 in FIG. 3) can simultaneously perform a multi-link operation and a restricted target wake time (R-TWT) operation. there is. In a Wi-Fi 7 network supporting multi-link operation and R-TWT, an AP MLD (e.g., AP MLD 501 in FIG. 4) is connected to a peripheral device (e.g., STA 301 in FIG. 3, non-AP MLD in FIG. 4). Based on different QoS requirements (quality of service requirements) for each service type that can be executed in the AP MLD 601, the electronic device 1301, the electronic device 1302, and the electronic device 1304 of FIG. 13, the R of the link -TWT service section can be set dynamically (e.g. R-TWT scheduling). In a Wi-Fi 7 network supporting multi-link operation and R-TWT, the non-AP MLD (601) determines at least one link according to the type of service to be executed, and provides membership to the AP MLD (501) for the determined link. You can request it. The non-AP MLD 601 may use links that satisfy different latency requirements and throughput requirements depending on the type of service being executed, while not impairing the usability of other devices in the network.

Referring to FIG. 8, according to one embodiment, the non-AP MLD 601 includes a wireless communication module 810 (e.g., the wireless communication module 1392 of FIG. 13) and a processor 820 (e.g., the wireless communication module 1392 of FIG. 13). It may include a processor 1320), and a memory 830 (eg, memory 1330 of FIG. 13). The wireless communication module 810 may be configured to transmit and receive wireless signals. The wireless communication module 810 may be a Wi-Fi chipset. The processor 820 may be operatively connected to the wireless communication module 810. The memory 830 is electrically connected to the processor 820 and may store instructions executable by the processor 820. The non-AP MLD 601 may correspond to the electronic device described in FIG. 13 (e.g., the electronic device 1301 in FIG. 13). Therefore, descriptions that overlap with those to be explained with reference to FIG. 13 will be omitted.

According to one embodiment, the processor 820 receives at least one beacon signal (e.g., the beacon signal 610 in FIG. 6) containing information about the R-TWT service section of each link included in the multiple links. You can. The R-TWT service section is connected to peripheral devices (e.g., STA 301 in FIG. 3, non-AP MLD 601 in FIG. 4, electronic device 1301, electronic device 1302, and electronic device 1304 in FIG. 13). ) may be dynamically configured based on different QoS requirements for each service type to be executed. Each of the links included in the multiple links (e.g., link 1, link 2, and link 3 in FIG. 9) may have different R-TWT service sections to satisfy different QoS requirements for each service type to be executed on the device. At least one beacon signal 610 including R-TWT scheduling information for each link may be transmitted by the AP MLD 501. R-TWT scheduling may be performed by the AP MLD (501). The R-TWT scheduling operation of the AP MLD 501 will be described in detail with reference to FIG. 9.

According to one embodiment, a beacon signal (eg, beacon signal 610 in FIG. 6) may be advertised for each link included in the multiple links of the AP MLD 501. That is, the beacon signal may include information about the corresponding link (e.g., information about the R-TWT service section of the link, information about the TID mapped to the link, and information about the direction of the link). The beacon signal may include not only information about the corresponding link, but also information about links different from the corresponding link.

According to one embodiment, the processor 820 may determine at least one link among multiple links based on at least one beacon signal. The processor 820 provides information about different R-TWT service sections for each link (e.g., start point information of the R-TWT service section, duration information of the R-TWT service section, and/or interval information of the R-TWT service section). By comparing the QoS requirements (e.g., latency requirements of the service, and/or throughput requirements of the service) of the service to be executed in the non-AP MLD 601, at least one link among multiple links can be determined. For example, the processor 820 may determine at least one link among multiple links whose R-TWT interval is smaller than the latency requirement of a service (eg, a service to be executed in the non-AP MLD 601). For example, the processor 820 may determine, among multiple links, at least one link whose R-TWT duration is sufficiently large to exchange data to be generated in response to the throughput requirement of the service. The link determination operation of the non-AP MLD 601 will be described in detail with reference to FIGS. 10 and 11.

According to one embodiment, at least one beacon signal (e.g., beacon signal 610 in FIG. 6) including R-TWT scheduling information for each link may further include TID information mapped to the link and direction information of the link. there is. The processor 820 may compare information on the R-TWT service section and the QoS requirement of the service to be executed in the non-AP MLD 601 for each link. The processor 820 may compare TID information for each link with TID information of traffic to be generated in the service. For each link, the processor 820 may compare the direction information of the link with the direction information of traffic to be generated in the service. The processor 820 may determine at least one link among multiple links by comparing information about the link and information related to the service. According to one embodiment, the processor 820 determines the communication module based on the at least one link. Data can be transmitted and received through (810). The processor 820 may request membership from the AP MLD 501 for at least one link. The processor 820 may transmit and receive data through at least one link based on the membership request result.

According to one embodiment, the non-AP MLD 601 can transmit data simultaneously through multiple links by performing a multi-link operation. The non-AP MLD 601 can increase the transmission rate in proportion to the number of links. The non-AP MLD 601 can predict transmission delay time and reduce transmission delay time. Due to the nature of the Wi-Fi network using an unlicensed band, the transmission delay time of the non-AP MLD 601 may also vary significantly depending on the traffic usage of nearby devices (e.g., devices different from the non-AP MLD 601). A constant delay time may be required for good quality communication service, and the non-AP MLD 601 can maintain a constant transmission delay time by using multiple links simultaneously. For example, even if the transmission delay time increases on a designated link at a designated time, if smooth transmission occurs on a link different from the designated link, a constant transmission delay time can be maintained in the overall aspect of the non-AP MLD 601. The non-AP MLD 601 maintains a constant transmission delay time through multi-link operation, so the quality of communication service can also be maintained constant.

According to one embodiment, the non-AP MLD 601 can provide good communication service quality by using the R-TWT protocol. The R-TWT protocol may be a protocol that allows only devices that transmit and receive traffic corresponding to a specified priority (e.g., traffic mapped to a specified TID) as members of the R-TWT service section. The R-TWT protocol may be a protocol that allows devices that are not members of the R-TWT service section to complete all transmission before the start of the R-TWT service section. Membership of the R-TWT protocol may be permitted only to devices that wish to transmit and receive latency sensitive traffic. Even when multiple devices operate in connection with the non-AP MLD (601), latency-sensitive traffic can be transmitted and received in the R-TWT service section without interference from other devices (e.g., devices that have not obtained membership). Through the R-TWT protocol, the non-AP MLD (601) can provide constant communication quality without being affected by the traffic usage status of other devices.

FIG. 9 is a diagram illustrating an operation of an AP MLD setting different R-TWT service sections for each link included in multiple links according to an embodiment.

According to one embodiment, referring to FIG. 9, the AL MLD 501 (e.g., AP 401 in FIG. 3) may perform R-TWT scheduling for each link. AP MLD 501 can set the R-TWT service section differently for each link. The AP MLD 501 is connected to peripheral devices (e.g., STA 301 in FIG. 3, non-AP MLD 601 in FIG. 4, electronic device 1301, electronic device 1302, and electronic device 1304 in FIG. 13). ) may be dynamically configured based on different QoS requirements (e.g., latency requirements, and/or throughput requirements) for each service type (e.g., audio call, game, video call) to be executed. Latency requirements and throughput requirements may vary depending on the service type.

According to one embodiment, the R-TWT service section of link 1 may be set in consideration of the QoS requirements (e.g., latency requirements and/or throughput requirements) of the audio call. Additionally, link 1 may be a mapped TID corresponding to an audio call. The R-TWT service section of link 2 may be set in consideration of the QoS requirements of the game. link 2 may be a mapped TID corresponding to the game. The R-TWT service section of link 3 may be set in consideration of the QoS requirements of the video call. Link 3 may be a mapped TID corresponding to a video call. The AP MLD 501 sets the R-TWT service section differently for each link, so that the usability of devices that do not use the R-TWT service is not reduced. The AP MLD 501 secures sufficient sections that do not correspond to the R-TWT service section for each link, so that the usability of devices that do not use the R-TWT service is not reduced.

Figures 10 and 11 show an example of an operation in which a non-AP MLD determines a link based on the QoS of a service according to an embodiment.

According to one embodiment, the non-AP MLD 601 (e.g., STA 301 in FIG. 3) may determine at least one link among multiple links based on QoS requirements required according to the type of service to be executed. The non-AP MLD 601 can detect a latency demanding service that transmits and receives latency sensitive traffic. The non-AP MLD 601 may obtain QoS requirements (e.g., latency requirements and/or throughput requirements) of the latency demanding service to be executed. The non-AP MLD 601 can compare the QoS requirements of the service to be executed and information on different R-TWT service sections for each link. The non-AP MLD 601 can determine a link among multiple links that satisfies the latency and throughput requirements of the service to be executed. The non-AP MLD 601 may determine a link whose R-TWT interval is smaller than the latency requirement of the service among multiple links. The non-AP MLD 601 may determine, among multiple links, a link whose R-TWT duration is large enough to exchange data to be generated in response to the throughput requirements of the service. The non-AP MLD 601 may request membership from the AP MLD 501 for the determined link.

According to one embodiment, referring to FIG. 9, the non-AP MLD 601 may request R-TWT membership for link 1 that satisfies the QoS requirements of the audio call to be executed. The non-AP MLD 601 can request R-TWT membership for link 2 that satisfies the QoS requirements of the game to be executed. The non-AP MLD 601 can perform an R-TWT membership request for link 3 that satisfies the QoS requirements of the video call to be executed. The non-AP MLD 601 may use multiple services at the same time.

Referring to FIG. 10, according to one embodiment, the non-AP MLD 601 may determine a plurality of links, each corresponding to a plurality of services, among multiple links. Multiple links may each satisfy QoS requirements of multiple services. For example, in order to execute an audio call and a game simultaneously, the non-AP MLD 601 may determine link 1 that satisfies the QoS requirements of the audio call and link 2 that satisfies the QoS requirements of the game. The non-AP MLD 601 may perform an R-TWT membership request for link 1 and link 2.

Referring to FIG. 11, according to one embodiment, the non-AP MLD 601 may determine a link based on an aggregate QoS requirement that integrates the QoS requirements of a plurality of services. For example, in order to execute an audio call and a game simultaneously, the non-AP MLD 601 may determine link 3 that simultaneously satisfies the QoS requirements of the audio call and the QoS requirements of the game. The non-AP MLD 601 may perform an R-TWT membership request for link 3.

Figure 12 is an example of a flowchart to explain a non-AP MLD operation method according to an embodiment.

Operations 1210 to 1230 may be performed sequentially, but are not necessarily performed sequentially. For example, the order of each operation 1210 to 1230 may be changed, and at least two operations may be performed in parallel.

In operation 1210, the non-AP MLD 601 (e.g., STA 301 in FIG. 3) receives at least one beacon signal containing information about the R-TWT service section of each link included in the multiple link. You can. The R-TWT service section will be executed in peripheral devices (e.g., STA 301 in FIG. 3, non-AP MLD 601, electronic device 1301, electronic device 1302, and electronic device 1304 in FIG. 13). It may be dynamically configured based on different QoS requirements for each service type. Each link included in the multiple links is connected to a peripheral device (e.g., STA 301 in FIG. 3, non-AP MLD 601, electronic device 1301, electronic device 1302, and electronic device 1304 in FIG. 13). Each service type to be executed may have different R-TWT service sections to satisfy different QoS requirements.

In operation 1220, the non-AP MLD 601 may determine at least one link among multiple links based on a beacon signal (e.g., a beacon signal containing information about the R-TWT service section). The non-AP MLD 601 provides information about different R-TWT service sections for each link (e.g., start point information of the R-TWT service section, duration information of the R-TWT service section, or interval information of the R-TWT service section ) and the QoS requirements of the service to be executed in the non-AP MLD 601 (e.g., the latency requirement of the service and/or the throughput requirement of the service), at least one link among multiple links can be determined.

In operation 1230, the non-AP MLD 601 may transmit and receive data based on at least one link. The non-AP MLD 601 may request membership for at least one link. The non-AP MLD 601 may transmit and receive data through at least one link based on the membership request result.

13 is a block diagram of an electronic device in a network environment, according to one embodiment.

Referring to FIG. 13, in the network environment 1300, the electronic device 1301 communicates with the electronic device 1302 through a first network 1398 (e.g., a short-range wireless communication network) or a second network 1399. It is possible to communicate with at least one of the electronic device 1304 or the server 1308 through (e.g., a long-distance wireless communication network). According to one embodiment, the electronic device 1301 may communicate with the electronic device 1304 through the server 1308. According to one embodiment, the electronic device 1301 includes a processor 1320, a memory 1330, an input module 1350, an audio output module 1355, a display module 1360, an audio module 1370, and a sensor module ( 1376), interface 1377, connection terminal 1378, haptic module 1379, camera module 1380, power management module 1388, battery 1389, communication module 1390, subscriber identification module 1396. , or may include an antenna module 1397. In some embodiments, at least one of these components (eg, the connection terminal 1378) may be omitted or one or more other components may be added to the electronic device 1301. In some embodiments, some of these components (e.g., sensor module 1376, camera module 1380, or antenna module 1397) are integrated into one component (e.g., display module 1360). It can be.

The processor 1320, for example, executes software (e.g., program 1340) to operate at least one other component (e.g., hardware or software component) of the electronic device 1301 connected to the processor 1320. It can be controlled and various data processing or calculations can be performed. According to one embodiment, as at least part of data processing or computation, the processor 1320 stores commands or data received from another component (e.g., sensor module 1376 or communication module 1390) in volatile memory 1332. The commands or data stored in the volatile memory 1332 can be processed, and the resulting data can be stored in the non-volatile memory 1334. According to one embodiment, the processor 1320 includes a main processor 1321 (e.g., a central processing unit or an application processor) or an auxiliary processor 1323 that can operate independently or together (e.g., a graphics processing unit, a neural network processing unit ( It may include a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device 1301 includes a main processor 1321 and a auxiliary processor 1323, the auxiliary processor 1323 may be set to use lower power than the main processor 1321 or be specialized for a designated function. You can. The auxiliary processor 1323 may be implemented separately from the main processor 1321 or as part of it.

The auxiliary processor 1323 may, for example, act on behalf of the main processor 1321 while the main processor 1321 is in an inactive (e.g., sleep) state, or while the main processor 1321 is in an active (e.g., application execution) state. ), together with the main processor 1321, at least one of the components of the electronic device 1301 (e.g., the display module 1360, the sensor module 1376, or the communication module 1390) At least some of the functions or states related to can be controlled. According to one embodiment, coprocessor 1323 (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module 1380 or communication module 1390). there is. According to one embodiment, the auxiliary processor 1323 (eg, neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. Artificial intelligence models can be created through machine learning. For example, such learning may be performed in the electronic device 1301 itself on which the artificial intelligence model is performed, or may be performed through a separate server (e.g., server 1308). Learning algorithms may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but It is not limited. An artificial intelligence model may include multiple artificial neural network layers. Artificial neural networks include deep neural network (DNN), convolutional neural network (CNN), recurrent neural network (RNN), restricted boltzmann machine (RBM), belief deep network (DBN), bidirectional recurrent deep neural network (BRDNN), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the examples described above. In addition to hardware structures, artificial intelligence models may additionally or alternatively include software structures.

The memory 1330 may store various data used by at least one component (eg, the processor 1320 or the sensor module 1376) of the electronic device 1301. Data may include, for example, input data or output data for software (e.g., program 1340) and instructions related thereto. Memory 1330 may include volatile memory 1332 or non-volatile memory 1334. Non-volatile memory 1334 may include internal memory 1336 and external memory 1338.

The program 1340 may be stored as software in the memory 1330 and may include, for example, an operating system 1342, middleware 1344, or application 1346.

The input module 1350 may receive commands or data to be used in a component of the electronic device 1301 (e.g., the processor 1320) from outside the electronic device 1301 (e.g., a user). The input module 1350 may include, for example, a microphone, mouse, keyboard, keys (eg, buttons), or digital pen (eg, stylus pen).

The sound output module 1355 may output sound signals to the outside of the electronic device 1301. The sound output module 1355 may include, for example, a speaker or receiver. Speakers can be used for general purposes such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part of it.

The display module 1360 can visually provide information to the outside of the electronic device 1301 (eg, a user). The display module 1360 may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling the device. According to one embodiment, the display module 1360 may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of force generated by the touch.

The audio module 1370 can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module 1370 acquires sound through the input module 1350, the sound output module 1355, or an external electronic device (e.g., directly or wirelessly connected to the electronic device 1301). Sound may be output through an electronic device 1302 (e.g., speaker or headphone).

The sensor module 1376 detects the operating state (e.g., power or temperature) of the electronic device 1301 or the external environmental state (e.g., user state) and generates an electrical signal or data value corresponding to the detected state. can do. According to one embodiment, the sensor module 1376 includes, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, humidity sensor, or light sensor.

The interface 1377 may support one or more designated protocols that can be used to directly or wirelessly connect the electronic device 1301 to an external electronic device (e.g., the electronic device 1302). According to one embodiment, the interface 1377 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal 1378 may include a connector through which the electronic device 1301 can be physically connected to an external electronic device (eg, the electronic device 1302). According to one embodiment, the connection terminal 1378 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

The haptic module 1379 can convert electrical signals into mechanical stimulation (e.g., vibration or movement) or electrical stimulation that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module 1379 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 1380 can capture still images and moving images. According to one embodiment, the camera module 1380 may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module 1388 can manage power supplied to the electronic device 1301. According to one embodiment, the power management module 1388 may be implemented as at least a part of, for example, a power management integrated circuit (PMIC).

The battery 1389 may supply power to at least one component of the electronic device 1301. According to one embodiment, the battery 1389 may include, for example, a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.

Communication module 1390 provides a direct (e.g., wired) communication channel or wireless communication channel between the electronic device 1301 and an external electronic device (e.g., electronic device 1302, electronic device 1304, or server 1308). It can support establishment and communication through established communication channels. The communication module 1390 operates independently of the processor 1320 (e.g., an application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module 1390 may be a wireless communication module 1392 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 1394 (e.g., : LAN (local area network) communication module, or power line communication module) may be included. Among these communication modules, the corresponding communication module is a first network 1398 (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 1399 (e.g., legacy It may communicate with an external electronic device 1304 through a telecommunication network such as a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., LAN or WAN). These various types of communication modules may be integrated into one component (e.g., a single chip) or may be implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module 1392 uses subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 1396 to communicate within a communication network such as the first network 1398 or the second network 1399. The electronic device 1301 can be confirmed or authenticated.

The wireless communication module 1392 may support 5G networks and next-generation communication technologies after 4G networks, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low latency). -latency communications)) can be supported. The wireless communication module 1392 may support high frequency bands (e.g., mmWave bands), for example, to achieve high data rates. The wireless communication module 1392 uses various technologies to secure performance in high frequency bands, such as beamforming, massive MIMO (multiple-input and multiple-output), and full-dimensional multiplexing. It can support technologies such as input/output (FD-MIMO: full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module 1392 may support various requirements specified in the electronic device 1301, an external electronic device (e.g., electronic device 1304), or a network system (e.g., second network 1399). According to one embodiment, the wireless communication module 1392 supports peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mmTC, or U-plane latency (e.g., 164 dB or less) for realizing URLLC. Example: Downlink (DL) and uplink (UL) each of 0.5 ms or less, or round trip 1 ms or less) can be supported.

The antenna module 1397 may transmit or receive signals or power to or from the outside (e.g., an external electronic device). According to one embodiment, the antenna module 1397 may include an antenna including a radiator made of a conductor or a conductive pattern formed on a substrate (eg, PCB). According to one embodiment, the antenna module 1397 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network such as the first network 1398 or the second network 1399 is connected to the plurality of antennas by, for example, the communication module 1390. can be selected. Signals or power may be transmitted or received between the communication module 1390 and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (eg, radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module 1397.

According to one embodiment, the antenna module 1397 may form a mmWave antenna module. According to one embodiment, a mmWave antenna module includes: a printed circuit board, an RFIC disposed on or adjacent to a first side (e.g., bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., mmWave band); And a plurality of antennas (e.g., array antennas) disposed on or adjacent to the second side (e.g., top or side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band. can do.

At least some of the components are connected to each other through a communication method between peripheral devices (e.g., bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and signal (e.g. commands or data) can be exchanged with each other.

According to one embodiment, commands or data may be transmitted or received between the electronic device 1301 and the external electronic device 1304 through the server 1308 connected to the second network 1399. Each of the external electronic devices 1302 or 1304 may be of the same or different type as the electronic device 1301. According to one embodiment, all or part of the operations performed in the electronic device 1301 may be executed in one or more of the external electronic devices 1302, 1304, or 1308. For example, when the electronic device 1301 needs to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device 1301 may perform the function or service instead of executing the function or service on its own. Alternatively, or additionally, one or more external electronic devices may be requested to perform at least part of the function or service. One or more external electronic devices that have received the request may execute at least part of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device 1301. The electronic device 1301 may process the result as is or additionally and provide it as at least part of a response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology can be used. The electronic device 1301 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 1304 may include an Internet of Things (IoT) device. Server 1308 may be an intelligent server using machine learning and/or neural networks. According to one embodiment, the external electronic device 1304 or server 1308 may be included in the second network 1399. The electronic device 1301 may be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

An electronic device according to an embodiment disclosed in this document may be of various types. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-described devices.

An embodiment of this document and the terms used herein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various changes, equivalents, or substitutes for the embodiment. In connection with the description of the drawings, similar reference numbers may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the above items, unless the relevant context clearly indicates otherwise. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “A Each of phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one component from another, and to refer to that component in other respects (e.g., importance or order) is not limited. One (e.g., first) component is said to be “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicatively.” When mentioned, it means that any of the components can be connected to the other components directly (e.g. wired), wirelessly, or through a third component.

The term “module” used in one embodiment of this document may include a unit implemented in hardware, software, or firmware, and may be interchangeable with terms such as logic, logic block, component, or circuit, for example. can be used A module may be an integrated part or a minimum unit of the parts or a part thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

One embodiment of this document is one or more instructions stored in a storage medium (e.g., built-in memory 1336 or external memory 1338) that can be read by a machine (e.g., electronic device 1301). It may be implemented as software (e.g., program 1340) including these. For example, a processor (e.g., processor 1320) of a peripheral device (e.g., electronic device 1301) may call at least one instruction among one or more instructions stored from a storage medium and execute it. This allows the device to be operated to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain signals (e.g. electromagnetic waves), and this term refers to cases where data is semi-permanently stored in the storage medium. There is no distinction between temporary storage cases.

According to one embodiment, a method according to an embodiment disclosed in this document may be provided and included in a computer program product. Computer program products are commodities and can be traded between sellers and buyers. The computer program product may be distributed in the form of a machine-readable storage medium (e.g. compact disc read only memory (CD-ROM)) or through an application store (e.g. Play StoreTM) or on two user devices (e.g. It can be distributed (e.g. downloaded or uploaded) directly between smart phones) or online. In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

According to one embodiment, each component (e.g., module or program) of the above-described components may include a single or multiple entities, and some of the multiple entities may be separately placed in other components. . According to one embodiment, one or more of the above-described corresponding components or operations may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (eg, modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each component of the plurality of components in the same or similar manner as those performed by the corresponding component of the plurality of components prior to the integration. . According to one embodiment, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or , or one or more other operations may be added.

An electronic device (e.g., the STA 301 in FIG. 3, the non-AP MLD 601 in FIG. 4, and the electronic device 1301 in FIG. 13) according to an embodiment includes one or more wireless communication modules configured to transmit and receive wireless signals. (e.g., the wireless communication module 810 of FIG. 8, the wireless communication module 1392 of FIG. 13), one or more processors (e.g., the processor of FIG. 8) operatively connected to the wireless communication module 810 820), processor 1320 of FIG. 13); and a memory (e.g., memory 830 in FIG. 8 and memory 1330 in FIG. 13) that is electrically connected to the processor 820 and stores instructions executable by the processor 820. When the instructions are executed by the processor 820, the processor 820 may receive at least one beacon signal containing information about the R-TWT service section of each link included in the multiple links. The processor 820 may determine at least one link among the multiple links based on the beacon signal. The processor 820 may transmit and receive data based on the at least one link. The R-TWT service section is a peripheral device located around the access point that performs communication with the electronic device 601 (e.g., STA 301 in FIG. 3, non-AP MLD 601 in FIG. 4, FIG. It may be dynamically configured based on QoS requirements associated with the type of service to be executed in the electronic devices 1301, 1302, and 1304).

According to one embodiment, the R-TWT service section may have different values for each link to satisfy QoS requirements associated with the type of service to be executed in the peripheral device.

According to one embodiment, the processor 820 may determine the at least one link among the multiple links by considering information about the R-TWT service section and QoS requirements of the service to be executed on the electronic device.

According to one embodiment, the information about the R-TWT service section includes at least one of start point information of the R-TWT service section, duration information of the R-TWT service section, or interval information of the R-TWT service section. It may include

According to one embodiment, the QoS request may include at least one of a latency requirement of a service to be executed in the electronic device or a throughput requirement of a service to be executed in the electronic device.

According to one embodiment, the processor 820 may determine, among the multiple links, the at least one link whose R-TWT interval is smaller than the latency requirement of the service to be executed on the electronic device.

According to one embodiment, the processor 820 selects, among the multiple links, the at least one link whose R-TWT duration is sufficiently large to exchange data to be generated in response to the throughput requirement of the service to be executed on the electronic device. You can decide.

According to one embodiment, the processor 820 may determine a plurality of links, each corresponding to a plurality of services, among multiple links. The plurality of links can each satisfy the QoS requirements of the plurality of services.

According to one embodiment, the processor 820 may obtain an integrated QoS requirement by integrating the QoS requirements of a plurality of services. The processor 820 may determine the at least one link among the multiple links that satisfies the QoS integration requirements.

According to one embodiment, the processor 820 may request membership for the at least one link. The processor 820 may transmit and receive data through the at least one link based on the membership request result.

According to one embodiment, the at least one beacon signal (e.g., the beacon signal 610 in FIG. 6) includes information about the R-TWT service section of the link, TID information mapped to the link, and direction information of the link. can do.

According to one embodiment, the processor 820 may compare the information on the R-TWT service section with the QoS requirement of the service to be executed in the electronic device for each link included in the multiple links. The processor 820 may compare the TID information for each link included in the multiple links with the TID information of traffic to be generated from a service to be executed on the electronic device. The processor 820 may compare the direction information with the direction information of the traffic for each link included in the multiple links.

A method of operating an electronic device (e.g., the STA 301 in FIG. 3, the non-AP MLD 601 in FIG. 4, and the electronic device 1301 in FIG. 13) according to an embodiment includes the operation of each link included in a multiple link. It may include receiving at least one beacon signal including R-TWT service period information. The method of operating the electronic device 601 may include determining at least one link among the multiple links based on the beacon signal. A method of operating the electronic device 601 may include transmitting and receiving data based on the at least one link. The R-TWT service section is a peripheral device located around the access point that performs communication with the electronic device 601 (e.g., STA 301 in FIG. 3, non-AP MLD 601 in FIG. 4, FIG. It may be dynamically configured based on QoS requirements associated with the type of service to be executed in the electronic devices 1301, 1302, and 1304).

According to one embodiment, the R-TWT service section may have different values for each link to satisfy QoS requirements associated with the type of service to be executed in the peripheral device.

According to one embodiment, the determining operation includes determining the at least one link among the multiple links by considering information about the R-TWT service section and QoS requirements of the service to be executed on the electronic device. can do.

According to one embodiment, the information about the R-TWT service section includes at least one of start point information of the R-TWT service section, duration information of the R-TWT service section, or interval information of the R-TWT service section. It can be included.

According to one embodiment, the QoS request may include at least one of a latency requirement of a service to be executed in the electronic device or a throughput requirement of a service to be executed in the electronic device.

According to one embodiment, the determining operation may include determining at least one link among the multiple links whose R-TWT interval is smaller than the latency requirement of the service to be executed in the electronic device.

According to one embodiment, the determining operation includes determining at least one link among the multiple links whose R-TWT duration is sufficiently large to exchange data to be generated in response to the throughput requirement of the service to be executed in the electronic device. Can include actions.

According to one embodiment, the beacon signal may include information about the R-TWT service section of the link, TID information mapped to the link, and direction information of the link.

Claims (15)

1. In the electronic device (301; 601; 1301),

   One or more wireless communication modules (810; 1392) configured to transmit and receive wireless signals;

   One or more processors (820; 1320) operatively connected to the wireless communication module (810; 1392); and

   Comprising a memory (830; 1330) electrically connected to the processor (820; 1320) and storing instructions executable by the processor (820; 1320),

   When the instructions are executed by the processor (820; 1320), the processor (820; 1320)

   Receive at least one beacon signal 610 containing information about the R-TWT service section of each link included in the multiple links,

   Based on the at least one beacon signal 610, determine at least one link among the multiple links,

   Transmitting and receiving data based on the at least one link,

   The R-TWT service section is,

   Based on the QoS requirements associated with the service type to be executed in the peripheral devices (301; 601; 1301; 1302; 1304) located around the access point (401; 501) that communicates with the electronic device (301; 601; 1301) which is dynamically configured,

   Electronic devices.
2. According to paragraph 1,

   The R-TWT service section is,

   Having different values for each link to satisfy QoS requirements associated with the type of service to be executed in the peripheral device (300; 601; 1301; 1302; 1304).

   Electronic devices.
3. According to any one of paragraphs 1 and 2,

   The processor (820; 1320),

   Considering the information about the R-TWT service section and the QoS requirement of the service to be executed on the electronic device (301; 601; 1301), determining the at least one link among the multiple links,

   Electronic devices.
4. According to any one of claims 1 to 3,

   Information on the R-TWT service section is,

   Start point information of the R-TWT service section, duration information of the R-TWT service section, or interval information of the R-TWT service section

   An electronic device comprising at least one of:
5. According to any one of claims 1 to 4,

   The above QoS requirements are:

   Latency requirements for services to be executed on the electronic device (301; 601; 1301) or throughput requirements for services to be executed on the electronic device (301; 601; 1301)

   An electronic device comprising at least one of:
6. According to any one of claims 1 to 5,

   The processor (820; 1320),

   Among the multiple links, determining the at least one link whose R-TWT interval is smaller than the latency requirement of a service to be executed on the electronic device (301; 601; 1301),

   Electronic devices.
7. According to any one of claims 1 to 6,

   The processor (820; 1320),

   Among the multiple links, determining the at least one link whose R-TWT duration is large enough to exchange data to be generated in response to the throughput requirement of the service to be executed on the electronic device (301; 601; 1301),

   Electronic devices.
8. According to any one of claims 1 to 7,

   The processor (820; 1320),

   Among the multiple links, determine a plurality of links each corresponding to a plurality of services,

   The plurality of links each satisfy QoS requirements of the plurality of services,

   Electronic devices.
9. According to any one of claims 1 to 8,

   The processor (820; 1320),

   Obtain integrated QoS requirements by integrating the QoS requirements of multiple services,

   Among the multiple links, determining the at least one link that satisfies the QoS integration requirements,

   Electronic devices.
10. According to any one of claims 1 to 9,

    The processor (820; 1320),

    Request membership for the at least one link,

    Based on the membership request result, transmitting and receiving data through the at least one link,

    Electronic devices.
11. According to any one of claims 1 to 10,

    The at least one beacon signal 610 is,

    Information about the R-TWT service section of the link, TID information mapped to the link, and direction information of the link

    Including,

    Electronic devices.
12. According to any one of claims 1 to 11,

    The processor (820; 1320),

    For each link included in the multiple links,

    Compare the information on the R-TWT service section and the QoS requirement of the service to be executed in the electronic device (301; 601; 1301),

    Compare the TID information with the TID information of traffic to be generated from a service to be executed on the electronic device (301; 601; 1301),

    Comparing the direction information with the direction information of the traffic,

    Electronic devices.
13. In a method of operating an electronic device (301; 601; 1301),

    An operation of receiving at least one beacon signal 610 including information about the R-TWT service period of each link included in the multiple links;

    determining at least one link among the multiple links based on the at least one beacon signal (610); and

    An operation of transmitting and receiving data based on the at least one link

    Including,

    The R-TWT service section is,

    Based on the QoS requirements associated with the service type to be executed in the peripheral devices (301; 601; 1301; 1302; 1304) located around the access point (401; 501) that communicates with the electronic device (301; 601; 1301) which is dynamically configured,

    How electronic devices work.
14. According to clause 13,

    The R-TWT service section is,

    Having different values for each link to satisfy QoS requirements associated with the type of service to be executed in the peripheral device (301; 601; 1301; 1302; 1304).

    How electronic devices work.
15. According to any one of claims 13 and 14,

    The determining operation is,

    An operation of determining the at least one link among the multiple links in consideration of the information on the R-TWT service section and the QoS requirement of the service to be executed in the electronic device (301; 601; 1301)

    A method of operating an electronic device, including.

Images