Communication equipment, control methods and procedures

By sharing target wake-up time information in the IEEE 802.11be standard, the problem of non-sharing of SP scheduling in R-TWT is solved, TWT information sharing across networks is realized, communication interference is avoided, and low-latency communication is supported.

CN122095693APending Publication Date: 2026-05-26CANON KK
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
CANON KK
Filing Date
2024-10-18
Publication Date
2026-05-26

Smart Images

  • Figure CN122095693A_ABST
    Figure CN122095693A_ABST
Patent Text Reader

Abstract

According to the invention, a communication device receives a radio frame including information related to the target wake-up time (TWT) of a first network constructed by a first communication device different from the communication device. The communication device transmits a predetermined frame including predetermined elements, the predetermined elements including information for identifying the first communication device and information related to the TWT of the first network.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a communication device for performing wireless communication, a control method for the communication device, and a program. Background Technology

[0002] The IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard family is known as the primary communication standard for WLANs (Wireless Local Area Networks). The IEEE 802.11 standard family includes standards such as IEEE 802.11a, b, g, n, ac, and ax.

[0003] The IEEE 802.11ax standard described in Patent Document 1 discloses wireless communication based on OFDMA (Orthogonal Frequency Division Multiple Access). The IEEE 802.11ax standard implements OFDMA-based wireless communication to achieve peak throughput. Furthermore, the IEEE 802.11ax standard introduces a power-saving technique called TWT (Target Wake-up Time). In the IEEE 802.11ax standard, the interval between a doze state (when no frame exchange occurs between the AP (Access Point) and STAs) and a wake-up state (when frame exchange occurs) is negotiated based on the TWT, allowing the AP to control the timing of communication with each STA. Therefore, the duration of the wake-up state during periods of non-communication is reduced, allowing the STA to reduce power consumption.

[0004] Furthermore, the IEEE 802.11be standard, the successor to the IEEE 802.11ax standard, is undergoing standardization. As a new feature of the IEEE 802.11be standard, a function called multi-link communication is being considered, which involves APs and STAs establishing multiple parallel links via multiple different frequency channels to perform communication. For example, Patent Document 2 describes a mechanism for establishing multiple links for multi-link communication. Additionally, low-latency communication using the aforementioned TWT is being considered in the IEEE 802.11be standard.

[0005] Citation List

[0006] Patent documents

[0007] PTL 1: Japanese Patent Publication No. 2018-50133

[0008] PTL 2: Japanese Patent Publication No. 2021-103805 Summary of the Invention

[0009] Technical issues

[0010] R-TWT (Restricted TWT) is being considered in the IEEE 802.11be standard.

[0011] R-TWT involves setting up time periods within a network (BSS) known as SPs (Service Hours) during which only designated terminals can communicate within the network. This allows only the designated terminals to be switched to a wake-up state (communicable state) and to perform communication during those time periods. By providing SPs in this way, terminals permitted to communicate within an SP have exclusive access to the communication channel. In contrast, terminals not permitted to communicate within an SP are switched to a sleep state (non-communicable state) during those time periods, thereby saving energy.

[0012] However, SP scheduling is set for each network and is not shared across different networks (OBSS). Therefore, terminals unaware of SP scheduling on different networks may predictably perform communication during SPs on different networks. Consequently, communication by terminals permitted to communicate during SPs may be blocked by communication by terminals unaware of those SPs. This could hinder the implementation of low-latency communication using SPs.

[0013] Solution to the problem

[0014] The purpose of this invention is to provide a specific mechanism for sharing information related to TWT across different networks.

[0015] To achieve the aforementioned objectives, a communication device according to one aspect of the present invention is a communication device comprising: a receiving component for receiving a wireless frame including information relating to a target wake-up time of a first network constructed by a first communication device different from the communication device; and a transmitting component for transmitting a predetermined frame including predetermined elements, the predetermined elements including information for identifying the first communication device and information relating to the target wake-up time of the first network.

[0016] Advantages of the invention

[0017] According to one aspect of the invention, information related to TWT can be shared across different networks. Attached Figure Description

[0018] [ Figure 1 ] Figure 1 This is a diagram illustrating an example of a network configuration.

[0019] [ Figure 2 ] Figure 2 This is a diagram illustrating an example of the hardware configuration of a communication device.

[0020] [ Figure 3 ] Figure 3This is a diagram illustrating an example of the functional configuration of a communication device.

[0021] [ Figure 4 ] Figure 4 This is an example diagram illustrating a flowchart for setting TWT information.

[0022] [ Figure 5 ] Figure 5 This is a diagram illustrating a simplified example of the frame configuration for a neighbor report element.

[0023] [ Figure 6 ] Figure 6 This is a diagram illustrating an example of the values ​​of the restricted TWT scheduling information subfields.

[0024] [ Figure 7 ] Figure 7 This is an example diagram illustrating a flowchart for the process of sharing TWT information.

[0025] [ Figure 8 ] Figure 8 This is a diagram illustrating an example of the frame configuration for neighbor report elements.

[0026] [ Figure 9 ] Figure 9 This is a diagram illustrating an example of the frame configuration of a TWT element. Detailed Implementation

[0027] The embodiments will now be described in detail with reference to the accompanying drawings. The following embodiments are not intended to limit the invention according to the claims. While the embodiments indicate multiple features, not all of these features are essential to the invention, and these features can be combined arbitrarily. Furthermore, in the drawings, identical or similar components are given the same reference numerals, and repeated descriptions thereof are omitted.

[0028] <First Embodiment>

[0029] (Network configuration)

[0030] Figure 1An example of a network configuration according to this embodiment is illustrated. This embodiment consists of a network 101 as a first network and a network 104 as a second network different from the first network. In this embodiment, a STA MLD 103 operating as a terminal participates in network 101 constructed by an AP MLD 102 operating as a base station. A STAMLD 106 operating as a terminal station participates in network 104 constructed by an AP MLD 105 operating as a base station. AP MLD is an abbreviation for Access Point Multi-Link Device, while STA MLD is an abbreviation for Station Multi-Link Device. STA MLD is also referred to as a non-AP MLD. An MLD is a communication device that includes multiple STAs (or APs). By including multiple STAs, an MLD can simultaneously establish multiple links with its corresponding MLD via different frequency channels. Moreover, multi-link communication can be performed via multiple established links. Network 101 is a network identified based on a first BSS (Basic Service Set), and network 104 is a network identified based on a second BSS (Basic Service Set). When viewed from a terminal belonging to a certain network (such as AP MLD 102 or STA MLD 103), another network that is different from the network to which that terminal belongs can also be referred to as OBSS (Overlapping Basic Service Set).

[0031] Although AP MLD 102, STA MLD 103, AP MLD 105 and STAMLD 106 are described as MLDs by way of example in this embodiment, these communication devices are not required to be MLDs and can be AP 102, STA 103, AP 105 and STA 106 respectively.

[0032] Each communication device (AP MLD 102, STA MLD 103, AP MLD 105, STA MLD 106) is configured to perform wireless frame communication compliant with the IEEE 802.11bn standard, which is a successor to the IEEE 802.11be standard, aiming for a maximum transmission rate of 46.08 Gbps. IEEE stands for Institute of Electrical and Electronics Engineers. As a successor to the IEEE 802.11be standard, the main features of the IEEE 802.11bn standard are high reliability communication, low latency communication, and improved throughput under congestion conditions. Another goal of 802.11bn is to reduce power consumption at the AP. Wireless frames used for communication according to this successor standard are also called UHR (Ultra-Reliable PPDUs). PPDU is an abbreviation for PLCP Protocol Data Unit, while PLCP is an abbreviation for Physical Layer Convergence Protocol.

[0033] Given the objectives to be achieved in subsequent standards and the prominent features of related standards, the name "UHR" is provided for convenience and can be changed to another name once standardization is complete. Similarly, the name IEEE 802.11bn can be given another name once standardization is complete. On the other hand, it should be noted that this description and the appended claims apply substantially to all successor standards that are successors to the 802.11be standard. Each communication device can communicate in the 2.4 GHz band, 3.6 GHz band, 5 GHz band, and 6 GHz band, as well as millimeter-wave bands including the 45 GHz and 60 GHz bands. The frequency bands used by each communication device are not limited to the above-mentioned bands and can include different bands, such as the sub-1 GHz band. Moreover, each communication device can communicate using bandwidths of 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, 540 MHz, and 640 MHz. The bandwidth used by each communication device is not limited to the bandwidth mentioned above, and may include different bandwidths, such as 240 MHz or 4 MHz.

[0034] By implementing OFDMA communication conforming to the IEEE 802.11ax / be / bn standard, each communication device can achieve multi-user (MU, multi-user) communication, where the signals of multiple users are multiplexed. OFDMA is an abbreviation for Orthogonal Frequency Division Multiple Access. In OFDMA communication, resource elements as part of a divided frequency band are allocated to corresponding STAs so that they do not overlap with each other, and the carriers of the corresponding STAs are orthogonal to each other. Therefore, the AP can communicate with multiple STAs simultaneously within a specified bandwidth. In addition to the IEEE 802.11 series, each communication device can also conform to other communication standards, such as Bluetooth (registered trademark), NFC, UWB, ZigBee, and MBOA. UWB is an abbreviation for Ultra Wide Band, and MBOA is an abbreviation for Multi Band OFDMAlliance. NFC is an abbreviation for Near Field Communication. UWB includes Wireless USB, Wireless 1394, and WiNET. In addition, each communication device can also conform to wired communication standards, such as wired LAN.

[0035] Specific examples of AP MLD 102 and AP MLD 105 include, but are not limited to, wireless LAN routers and personal computers (PCs), as long as they are communication devices capable of operating as access points (APs). Each AP MLD can be an information processing device, such as a wireless chip, capable of performing wireless communications compliant with the IEEE 802.11bn standard. Specific examples of STA MLD 103 and STA MLD 106 include, but are not limited to, cameras, tablets, smartphones, PCs, mobile phones, video cameras, headsets, webcams, printers, projectors, and smart glasses. Each STA MLD can be an information processing device, such as a wireless chip, capable of performing wireless communications compliant with the IEEE 802.11bn standard.

[0036] Although, as an example of network configuration according to this embodiment, networks 101 and 104, each consisting of a single AP MLD and a single STA MLD, are configured to be adjacent to each other, the number of networks, the number of APs, and the number of STAs are not limited to the numbers described above. Multiple networks, multiple APs, and multiple STAs may be included.

[0037] (Hardware configuration of each communication device)

[0038] Figure 2The illustration shows an example of the hardware configuration for each communication device. Each communication device has a storage unit 201, a control unit 202, a function unit 203, an input unit 204, an output unit 205, a communication unit 206, and an antenna 207.

[0039] Storage unit 201 consists of one or more of ROM and RAM, and stores programs for performing various types of operations described later, as well as various types of information such as communication parameters for wireless communication. RAM is an abbreviation for Random Access Memory, and ROM is an abbreviation for Read Only Memory. In addition to memories such as ROM and RAM, storage media including non-volatile storage devices such as hard disks or SSDs (Solid State Drives) can also be used as storage unit 201.

[0040] The control unit 202 is composed of, for example, a processor such as a CPU or MPU, an ASIC (Application-Specific Integrated Circuit), a DSP (Digital Signal Processor), or a FPGA (Field-Programmable Gate Array). CPU stands for Central Processing Unit, and MPU stands for Micro Processing Unit. The control unit 202 executes programs stored in the storage unit 201 and controls the entire device by operating hardware circuitry such as an ASIC. The control unit 202 can cooperate with the programs and OS (Operating System) stored in the storage unit 201 to control the entire device.

[0041] Furthermore, control unit 202 controls functional unit 203 to perform predetermined processes, such as imaging, printing, or projection. Functional unit 203 is the hardware of the device used to perform the predetermined processes. For example, if the communication device is a digital still camera or a smartphone equipped with a camera, then functional unit 203 is an imaging unit that performs imaging processing for capturing surrounding images via a camera unit (not shown) included in the communication device. For example, if the communication device is a printer, then functional unit 203 is a printing unit that performs printing processing on a sheet (such as paper) based on printing data obtained from an external source via wireless communication. For example, if the communication device is a projector or smart glasses, then functional unit 203 is a projection unit that performs projection processing on image data or video data obtained from an external source via wireless communication. In the case of smart glasses, the projection surface is, for example, the end user's retina. The data to be processed by functional unit 203 may be data stored in storage unit 201 or data transmitted to another AP or STA via communication unit 206, which will be described later. In addition, the communication device (such as AP 101) may provide network storage functionality, such as NAS (Network Attached Storage). This functionality is provided to another communication device as a web service such as network storage services. For example, communication devices such as STAs connect to network storage services provided by AP MLDs using protocols such as SMB, FTP, or WebDAV. The STA then uploads files to or downloads files from the storage service. Data communication involving uploads and downloads is achieved by transmitting UHR PPDUs between devices.

[0042] Input unit 204 receives various types of operations from the user. Output unit 205 performs various types of outputs to the user. Outputs from output unit 205 include at least one of on-screen display, audio output from a speaker, and vibration output. As in a touchscreen, input unit 204 and output unit 205 can be implemented using a single module. Output unit 205 serves as a display component to present information to the user. Input unit 204 serves as a receiving component to receive user operations.

[0043] Communication unit 206 performs control of wireless communications conforming to the IEEE 802.11 standard family and control of IP communications. In this embodiment, by cooperating with antenna 207, communication unit 206 can perform communication control for transmitting and receiving UHR PPDUs as wireless frames conforming to the UHR standard, as well as PPDUs conforming to standards prior to the UHR standard. Antenna 207 is, for example, an antenna capable of transmitting and receiving signals in at least one frequency band including sub-GHz, 2.4 GHz, 5 GHz, 6 GHz, and millimeter-wave bands.

[0044] If the communication device conforms to, for example, the NFC standard, Bluetooth standard, and / or wired communication standard mentioned above, then the communication unit 206 can be configured to perform control over wireless and / or wired communication conforming to these communication standards.

[0045] (Functional configuration of communication equipment)

[0046] Figure 3 This is a block diagram illustrating an example of the functional configuration of each communication device according to this embodiment. In this embodiment, each functional block is stored as a program in storage unit 201, and its function is implemented by the control unit 202 executing the program. By executing the program, the control unit 202 controls each hardware unit and calculates and processes information, thereby implementing the corresponding function. Some or all of the functional blocks can be implemented in hardware. In this case, some or all of the functional blocks are constructed, for example, by ACIC (Application-Specific Integrated Circuit).

[0047] In this embodiment, each communication device includes a TWT information acquisition unit 301, a frame generation unit 302, a frame transmission-reception unit 303, a multi-link control unit 304, and a UI control unit 305.

[0048] TWT information acquisition unit 301 acquires TWT information set in different networks from management frames such as beacon frames, probe response frames, or association response frames from different networks.

[0049] The frame generation unit 302 generates a wireless frame to be transmitted via the frame transmission-reception unit, which will be described later. In this embodiment, a frame for sharing TWT information with another communication device is generated based on TWT information from different networks acquired by the TWT information acquisition unit 301.

[0050] The frame transmission-reception unit 303 includes an antenna and circuitry for transmitting wireless frames (or signals) to and receiving wireless frames (or signals) from another wireless communication device, and also includes a program for controlling the antenna and circuitry. According to the IEEE 802.11 standard series, the frame transmission-reception unit 303 performs wireless LAN communication control based on frames generated by the frame generation unit 302.

[0051] The multi-link control unit 304 performs control over processes related to link establishment, including link establishment processing for establishing at least one link to be used in wireless communication with the corresponding MLD, communication initiation processing, processing for adding or deleting links after link establishment, and communication termination processing for deleting all links. The link establishment process mainly consists of authentication processing, association processing, and four-way handshake (4WHS) processing.

[0052] The UI control unit 305 comprises user interface-related hardware, such as a touchscreen or buttons for receiving user input, and a program for controlling the hardware. For example, the multi-link control unit 304 receives user input via the UI control unit 305, thereby selecting the corresponding device to which the communication device connects. Furthermore, the multi-link control unit 304 receives user input via the UI control unit 306, thereby performing processing for selecting or setting STAs included in each communication device and used by the communication device during link establishment. The UI control unit 306 may also have the function of instructing the user on information such as audio output.

[0053] (TWT Information)

[0054] Next, the TWT information will be described. In this embodiment, the Target Wake-up Time (TWT) information includes at least information related to the Service Hour (SP). However, the TWT information is not limited to this and may also include other TWT-related information. Examples of information that may be included may be related to a Traffic Identifier (TID) indicating the type of data that can be sent in the SP and a TWT group indicating a group of multiple STAs sharing the SP.

[0055] SP (Service Point) is the period during which the AP and STA perform adjustment and setup processes in the network, and the STA is in a wake-up state (communicable state). Outside of the SP, the STA is typically in a sleep state (non-communicable state), but is not limited to this, and can be configured to perform communication outside of the SP. Within the SP, the STA transitions to a wake-up state to send and receive frames. In contrast, when the STA is outside the SP, it can transition to a sleep state to conserve power. TWT (Time To Wake-up) information is not limited to the above and may include information included in the TWT parameter information described later. Examples of SP-related information include information related to the start timing of the SP, information related to the duration from the start to the end of the SP, and information related to the interval between the start timings of the SP.

[0056] (TWT Information Settings)

[0057] Next, a flowchart will be described on how to set the TWT information in AP MLD 102 and STA MLD 103 of network 101.

[0058] Figure 4 The diagram illustrates an example of a flowchart in which AP MLD 102 receives a TWT request from STA MLD 103 and sets TWT information by sending a TWT response in response to the TWT request.

[0059] first, Figure 4The flowchart shown begins when STA MLD 103 sets or updates TWT information. The following description relates to how TWT information is set during the initial link setup between AP MLD 102 and STA MLD 103 in this embodiment.

[0060] In step S401, AP MLD 102 receives an association request frame via communication unit 206, which includes a TWT request sent by STA MLD 103. The TWT request is information indicating that STA MLD has requested AP MLD to set TWT information. The TWT request includes, for example, TWT information such as information indicating whether there is TWT support for the STA used as the sending source, and information related to AID (Association Identifier), SP start timing, duration from the start to the end of the SP, and the period and interval of the SP.

[0061] In step S402, AP MLD 102 sends an associated response frame, including a TWT response, to STA MLD 103 via communication unit 206. The TWT response indicates permission to set the information related to the start and end times of the SP and the SP's period in the TWT request received in step S401 as TWT information. For example, AP MLD 102 can be configured to indicate permission by including a value equal to the TWT request in the TWT response. If AP MLD 102 does not permit the received TWT request, then AP MLD 102 can be configured to indicate a different value in the TWT response than the TWT request.

[0062] In step S403, based on the TWT response sent by AP MLD 102, TWT information setting processing and link establishment processing are performed in AP MLD 102 and STA MLD 103.

[0063] After setting the TWT information in AP MLD 102 and STA MLD 103, AP MLD 102 periodically sends beacon frames including the set TWT information (step S404). Therefore, AP MLD 105 can receive and acquire the TWT information about AP MLD 102 and STA MLD 103.

[0064] Although Figure 4 The document describes an example of a process for setting up TWT information during the initial link establishment between AP MLD 102 and STA MLD 103, but the process is not limited to this. The process can begin based on STA MLD 103 sending a TWT request after the link is established.

[0065] Furthermore, although the process described above relates to how TWT information is set in AP MLD 102 and STA MLD 103 in this embodiment, TWT information setting processing and link establishment processing can be performed in AP MLD 105 and STA MLD 106 according to a similar process.

[0066] (Elements used to share TWT information)

[0067] Before proceeding with the description of the TWT information sharing process, the elements of the radio frame used when sharing TWT information used in the TWT information sharing process will be described.

[0068] Figure 5 An example of a frame format for a simplified neighbor report element according to this embodiment is illustrated. In this embodiment, TWT information of another network is shared with networks constructed by or connected to this device by using the simplified neighbor report element. In the following description of each field including the simplified neighbor report element, only the name of the field will be used, and the description of the field will be omitted.

[0069] Figure 5 The simplified neighbor report element shown includes an element ID 501, a length 502, and a neighbor AP information field 503. Element ID 501 is an identifier used to identify the information element, and in this embodiment, it includes an identifier indicating the simplified neighbor report element. Length 502 is a field indicating the data length of the element, and in this embodiment, it includes information indicating the data length of the neighbor AP information field 503. Neighbor AP information field 503 is a field indicating information about different networks, and in this embodiment, it includes TWT information about different networks. The information included in the neighbor AP information field 503 will be described later.

[0070] Each communication device is generated sequentially from element ID 501. Figure 5 The simplified neighbor report element shown is generated and sent to another communication device. In this case, each communication device performs the transmission after generating all fields within the element. Specifically, each communication device performs the transmission to another communication device after generating all element ID 501, length 502, and neighbor AP information field 503. Alternatively, each AP MLD can perform the transmission concurrently with the generation of the fields. Specifically, for example, each communication device can send length 502 concurrently with the transmission of the generated element ID 501.

[0071] Each communication device will... Figure 5The simplified neighbor reporting element shown is transmitted within a MAC (Media Access Control) frame, such as a beacon frame or probe response frame. Furthermore, in addition to such MAC frames, each communication device can add elements to MAC frames such as association response frames or reassociation response frames.

[0072] The Neighbor AP Information field 503 includes one or more neighbor AP messages. Each neighbor AP message includes a TBTT information header 504, an operation class 505, a channel number 506, and a TBTT information set 507. The AP indicated in each neighbor AP message can also be referred to as the reported AP. TBTT is an abbreviation for Target Beacon Transmission Time. The TBTT information header 504 includes information indicating the data length of the TBTT information set 507 and information indicating the number of TBTT information fields included in the TBTT information set 507. The number of TBTT information fields is indicated by subtracting 1 from the actual number included in the TBTT information set 507. The operation class 505 indicates the channel start frequency. The primary channel of the reported AP is indicated based on the information indicated by the operation class 505 and the channel number 506.

[0073] TBTT information set 507 includes one or more TBTT messages. The information included in each TBTT message in TBTT information set 507 will be described later. By including multiple neighbor AP messages, the neighbor AP information field 503 can include information related to multiple other APs. A communication device that has received the simplified neighbor report element can identify the primary channel based on the operation class 505 and channel number 506, thereby performing communication control more efficiently.

[0074] The TBTT information set 507 includes one or more TBTT messages. Each TBTT message includes a neighboring AP TBTT offset 508, a BSSID 509, a short SSID 410, BSS parameters 511, a 20-MHz PSD 511, MLD parameters 513, and TWT information 514. The neighboring AP TBTT offset 508 indicates the time unit (TU) offset from the previous TBTT to the subsequent TBTT of the reported AP. The BSSID 509 indicates the Basic Service Set Identifier (BSSID) of the reported AP. The short SSID 510 indicates a 32-bit value calculated from the Service Set Identifier (SSID) of the network constructed by the reported AP. The BSS parameters 511 indicate various types of information associated with the reported AP indicated by BSSID 509. The 20-MHz PSD 511 is information indicating the maximum transmission power and indicates, for example, the maximum transmission power corresponding to the 20-MHz primary channel of the reported AP. MLD parameter 513 includes information related to the AP MLD to which the reported AP belongs, and includes, for example, the AP MLD ID as an identifier of the AP MLD and the Link ID as an identifier of the link of the reported AP within the AP MLD. TWT information 514 is a field that includes the TWT information of the reported AP and is used for sharing by including the TWT information of another network in this element.

[0075] TWT information 514 includes control 515 and TWT parameter information 516. Control 515 is information related to the information included in TWT parameter information 516, and includes, for example, information indicating whether the TWT information is a broadcast TWT, an individual TWT, or a TWT information indicating a TBTT interval. A broadcast TWT is a TWT that sets TWT information between the AP and multiple STAs. An individual TWT is a TWT that sets TWT information between the AP and STAs on a one-to-one basis. TWT parameter information 516 includes request type 517, target wake-up time 518, nominal minimum TWT wake-up duration 519, TWT wake-up interval mantissa 520, broadcast TWT information 521, and restricted TWT traffic information 522. Request type 517 includes, for example, a TWT flow identifier for identifying the TWT flow controlled based on the TWT information included in the TWT information. Target wake-up time 518 is information indicating the time to the subsequent SP, and includes a positive integer corresponding to the timing synchronization function (TSF) time that requests to release the STA from sleep state. The nominal minimum TWT wake-up duration 519 is information indicating the expected duration from the start to the end of the SP, and includes information indicating the expected minimum time the STA needs to be in a wake-up state after being released from sleep mode in order to complete the exchange of radio frames. The TWT wake-up interval mantissa 520 is information indicating the interval between the start timings of the SP, and includes information indicating the mantissa value of the interval indicating the release of the STA from sleep mode. The information included in the broadcast TWT information 521 will be described later. The restricted TWT traffic information 522 specifies the traffic identifier (TID) in bitmap format as a specific radio frame to be transmitted in the downlink (DL) and uplink (UL) directions.

[0076] Broadcast TWT information 521 includes restricted TWT traffic information presence 523, restricted TWT scheduling information 524, broadcast TWT ID 525, and broadcast TWT persistence 526. Restricted TWT traffic information presence 523 includes information indicating whether restricted TWT traffic information 522 is included. Restricted TWT scheduling information 524 will be described later. Broadcast TWT ID 525 stores information used to identify the TWT information set by the reported AP. Broadcast TWT persistence 526 stores information indicating the number of TBTTs within the SP indicated in the TWT information.

[0077] Now refer to Figure 6 Description of restricted TWT scheduling information 524. Figure 6This is a diagram illustrating the values ​​included in the restricted TWT scheduling information 524 and the meanings indicated by those values. Values ​​0 through 3 are each used by the AP to notify STAs within its own BSS about TWT scheduling. Value 0 indicates that the TWT is idle, while values ​​1 and 3 each indicate that the TWT scheduling is active. Value 2 indicates that the scheduling is active, but the likelihood of new participation is low. Values ​​4 and 5 each mean that the TWT information indicates the TWT scheduling of another network (OBSS).

[0078] If the restricted TWT scheduling information 524 includes the value 4, then the TWT information is from another network, and the TWT scheduling based on the relevant TWT information is active in that other BSS. If field 524 includes the value 5, then the TWT information is from another network, and the TWT scheduling based on the relevant TWT information is idle in that other BSS.

[0079] (Shared processing of TWT information)

[0080] The following is for reference Figure 7 The description relates to an example flowchart of a process by which AP MLD 105 shares the TWT information of network 101 with STA MLD 106 using the simplified neighbor reporting element mentioned above. In this embodiment, AP MLD 105 acquires the TWT information of network 101 from a radio frame that includes the TWT information of network 101 sent by AP MLD 102. AP MLD 105 then shares the acquired TWT information of network 101 with STA MLD 106 of network 104. This flowchart indicates the processes performed as control unit 202 reads and executes a computer program stored in storage unit 201. For example, this flowchart begins immediately after a beacon frame periodically sent by AP MLD 105 is transmitted. This flowchart may begin when AP MLD 105 receives a radio frame (such as a beacon frame, probe response frame, or association response frame) from AP MLD 102, which constitutes a different network. This flowchart selectively illustrates the processes related to sharing the TWT information of OBSS with STAs of BSS.

[0081] First, in step S701, AP MLD 105 receives a radio frame (e.g., a beacon frame sent by AP MLD 102 in step S404) via frame transmission-reception unit 303. If the radio frame includes TWT information, the process proceeds to step S702. If it does not include TWT information, the process ends. The radio frame received in step S701 is a MAC frame sent by AP MLD 102 and is assumed to be a management frame, such as a beacon frame, probe response frame, or association response frame, but is not limited to these. For example, control frames, action frames, etc., are also possible.

[0082] Subsequently, in step S702, the TWT information acquisition unit 301 of AP MLD 105 acquires the TWT information of network 101 from the radio frame that includes the TWT information received in step S701.

[0083] In step S703, AP MLD 105 determines whether a predetermined time period has elapsed since the start of this process. In this embodiment, the predetermined time period is the transmission interval of beacon frames sent by AP MLD 105. In other words, according to this embodiment, AP MLD 105 determines whether a predetermined time period (e.g., 100 TU) has elapsed since the transmission of the previous beacon frame. If it is determined in step S703 that the predetermined time period has elapsed ("Yes" in step S703), then the process proceeds to step S704. If it is determined in step S703 that the predetermined time period has not elapsed ("No" in step S703), then the process proceeds to step S701.

[0084] Then, in step S704, it is determined whether TWT information for different BSSs was obtained within a predetermined time period. If it is determined in step S704 that TWT information for different BSSs was obtained within the predetermined time period ("Yes" in step S704), then the process proceeds to step S705. If it is determined that TWT information for different BSSs was not obtained within the predetermined time period ("Yes" in step S704), then the process proceeds to step S701.

[0085] In step S705, AP MLD 105 stores the TWT information of network 101 obtained in step S702 into the simplified neighbor report element mentioned above, and sends a radio frame including this element to STA MLD 106 via frame transmission-reception unit 303. In this element, the restricted TWT scheduling information subfield is set to 4. The radio frame sent by AP MLD 105 in step S705 is a MAC frame, assuming it is a management frame such as a beacon frame, probe response frame, or association response frame, but is not limited to this. For example, control frames, action frames, etc., are also possible. This embodiment relates to an example where only the TWT information of network 101 is included as TWT information of different networks, but is not limited to this. The hypothetical example is a case where multiple networks different from network 104 surround AP MLD 105 and the TWT information of multiple different BSSs is received until a predetermined period of time has elapsed. The TWT information sharing process in this case will be simply described using the above process. First, AP MLD 105 receives a radio frame including TWT information of a first different BSS in step S701. Then, it obtains the TWT information of the first BSS from the received radio frame. Subsequently, before a predetermined time period has elapsed, it receives a radio frame including TWT information of a second different BSS ("No" in step S703, and step S701). Then, it obtains the TWT information of the second BSS from the received radio frame. After the predetermined time period has elapsed ("Yes" in step S703), the obtained TWT information of the first BSS and the obtained TWT information of the second BSS are stored in a simplified neighbor report element, and a radio frame including this element is transmitted to STA MLD 106 via frame transmission-reception unit 303 (step S705). When TWT information of multiple networks is received in this manner within a predetermined time period, the TWT information of these multiple networks is shared all at once in step S507. When a radio frame including TWT information is transmitted in step S705, AP MLD 105 proceeds to step S706. In step S706, AP MLD 105 determines whether to stop the network. If it is determined that the network should be stopped, then the network provisioning process is terminated, and the series of processes is terminated. On the other hand, if it is determined that the network should not be stopped, then the process proceeds to step S701, and a series of notification controls are executed. Specifically, AP MLD 105 can determine to stop the network upon receiving a shutdown operation or a power-off operation (not shown).

[0086] AP MLD 105 stores the TWT information of network 101 received from AP MLD 103 into the simplified neighbor report element mentioned above and sends the simplified neighbor report element to STA MLD 106 in this manner, so that TWT-related information from different networks can be shared with the network to which this device belongs. AP MLD 105 can be configured to send information related to at least the target wake-up time 518, the nominal minimum TWT wake-up duration 519, and the TWT wake-up interval tail 520 as the TWT information mentioned above in step S703. This information is related to the SP start timing in another network, the SP duration, and the interval between the start timings of SPs, respectively. Therefore, by identifying the information included in the target wake-up time 518, STA MLD 106 can identify the start timing of subsequent SPs in another network. By identifying the information included in the nominal minimum TWT wake-up duration 519, STA MLD 106 can identify the SP duration in another network. By identifying information included in the TWT wake-up interval tail number 520, the STA MLD 106 can identify the interval between the start timings of the SPs of another network.

[0087] The STA connected to AP MLD 105 and represented by STA MLD 106, etc., performs transmission suppression control so that it does not perform its own data transmission processing during the SP of the other network mentioned above that is identified.

[0088] Therefore, STA MLD 106 can confirm the start timing and duration of the SP in network 101, and can suppress transmission in the SP of the other network mentioned above that is being confirmed. Thus, interference with communication in the SP of the other network mentioned above can be prevented.

[0089] exist Figure 7 In the aforementioned control, the beacon frame transmission interval is used as an example of a time period for collecting the TWT of the OBSS, and the STA of the BSS is notified of the TWT information of the OBSS received during that time period. However, the control is not limited to this. For example, the AP MLD 105 can be configured to manage the TWT information sent by the AP of the OBSS in association with its final acquisition duration, and provide the STA of the BSS with notification of the TWT information of the OBSS acquired within a predetermined reference time (e.g., within one minute).

[0090] <Second Embodiment>

[0091] In the first embodiment, AP MLD 105 shares the TWT information of network 101 with STA MLD 106 using a simplified neighbor report element. In the second embodiment, an example using a neighbor report element instead of the simplified neighbor report element will be described. Since the hardware and functional configurations of each communication device according to this embodiment are similar to those in the first embodiment, their description will be omitted. (Reference...) Figure 4 The TWT information setting process and reference in AP MLD 102 and STA MLD 103 in network 101 are described. Figure 7 The processing of TWT information shared by AP MLD 105 and STA MLD 106 in network 101 is similar to that in the first embodiment, and therefore its description will be omitted.

[0092] Now refer to Figure 8 The neighbor reporting element according to this embodiment is described. AP MLD 105 stores the TWT information of different BSSs obtained in step S702 above into this element, and transmits a radio frame including this element to STA MLD 106 via frame transmission-reception unit 303. The radio frame including this element is assumed to be a MAC frame, such as a beacon frame, probe response frame, or association response frame, but is not limited thereto. For example, control frames, action frames, etc., are also possible.

[0093] Figure 8 The neighbor reporting elements shown include element ID 801, length 80, BSSID 803, BSSID information 804, operation class 805, channel number 806, PHY type 807, and optional sub-element 808. Since element ID 801, length 80, BSSID 803, BSSID information 804, operation class 805, and channel number 806 each include information similar to their corresponding fields with the same names described above, their descriptions are omitted. PHY type 807 includes the PHY type of the AP indicated by BSSID 803.

[0094] Optional sub-element 808 includes sub-element ID 809, length 810, control 515, and TWT parameter information 516.

[0095] By using the neighbor reporting element mentioned above in this way, AP MLD 105 can share the TWT information of network 101 with STA MLD 106.

[0096] <Third Embodiment>

[0097] In the third embodiment, AP MLD 105 shares the TWT information of network 101 with STA MLD 106 by using TWT elements instead of the elements mentioned above.

[0098] Since the hardware and functional configurations of each communication device according to this embodiment are similar to those in the first embodiment, their descriptions will be omitted. (Reference...) Figure 4 The TWT information setting process and reference in AP MLD 102 and STA MLD 103 of network 101 are described. Figure 7 The processing of TWT information shared by AP MLD 105 and STA MLD 106 in network 101 is similar to that in the first embodiment, and therefore its description will be omitted.

[0099] Now refer to Figure 9 The TWT element according to this embodiment is described. AP MLD 105 stores the TWT information of different BSSs obtained in step S702 above into this element, and transmits a radio frame including this element to STA MLD 106 via frame transmission-reception unit 303. The radio frame including this element is assumed to be a MAC frame, such as a beacon frame, probe response frame, or association response frame, but is not limited thereto. For example, control frames, action frames, etc., are also possible.

[0100] Figure 9 The TWT element shown includes element ID 801, length 80, control 515, and TWT parameter information 903.

[0101] In this embodiment, in addition to the fields mentioned above, the TWT parameter information 903 included in the TWT element also includes a BSSID 904. The BSSID 904 stores information indicating the BSSID of the AP that has the TWT information indicated in the TWT parameter information 903 set. This embodiment relates to the case where the BSSID 904 is stored immediately after the restricted TWT traffic information 522, but is not limited thereto. For example, the BSSID 904 may be stored immediately after the broadcast TWT persistence 526, and may be stored at least in the TWT parameter information 903 included in the TWT element. Therefore, the STA becomes able to identify which network the TWT information indicated by the TWT element belongs to. Furthermore, even if multiple other networks exist, it becomes possible to identify which network each TWT message belongs to.

[0102] Therefore, by using the TWT element mentioned above, AP MLD 105 can share the TWT information of network 101 with STA MLD 106.

[0103] <Other Embodiments>

[0104] Each of the above embodiments relates to a process of how the AP MLD shares TWT information of another network with the STA MLD, but is not limited thereto. For example, if the STA MLD receives and acquires TWT information of another network, then the STA MLD can be configured to share the TWT information of the other network mentioned above by using any of the elements mentioned above.

[0105] Each of the above embodiments relates to the scenario of sharing TWT information from another network, but is not limited thereto. Each element can be configured to share only information related to R-TWT.

[0106] also, Figure 4 and Figure 7 The flowchart of the AP MLD 105 shown can be implemented at least partially or entirely in hardware. If the flowchart is to be implemented in hardware, then, for example, a dedicated circuit can be generated on an FPGA from a computer program used to implement the individual steps using a pre-defined compiler, and this dedicated circuit can be used. FPGA is an abbreviation for Field Programmable Gate Array. Furthermore, gate array circuits can be formed similarly to FPGAs and can be implemented in hardware. Moreover, the flowchart can be implemented using an ASIC (Application-Specific Integrated Circuit).

[0107] The present invention can also be implemented by supplying a program implementing at least one feature of the above embodiments to a system or device via a network or storage medium, and having at least one processor in the computer of the system or device read and execute the program. Furthermore, the present invention can also be implemented by a circuit (e.g., an ASIC) implementing at least one feature.

[0108] This invention is not limited to the embodiments described above, and various changes and modifications are possible as long as they do not depart from the spirit and scope of the invention. Therefore, the claims are appended to disclose the scope of the invention.

[0109] This application claims the benefit of Japanese Patent Application No. 2023-185970, filed on October 30, 2023, which is hereby incorporated herein by reference in its entirety.

Claims

1. A communication device, comprising: A receiving component for receiving a wireless frame, the wireless frame including information related to a target wake-up time of a first network constructed by a first communication device, the first communication device being different from the communication device; as well as A transmitting component is configured to transmit a predetermined frame including predetermined elements, the predetermined elements including information for identifying the first communication device and information related to the target wake-up time of the first network.

2. The communication device according to claim 1, further comprising: An acquisition component is configured to acquire information related to the target wake-up time of the first network based on the wireless frame received by the receiving component; as well as A generation component, which is used to generate the predetermined frame to be sent by the sending component based at least on information related to the target wake-up time of the first network obtained by the acquisition component.

3. The communication device according to claim 1 or 2, in, When the communication device is not participating in the first network, the transmitting component transmits the predetermined frame including the predetermined elements, the predetermined elements including information for identifying the first communication device and information related to the target wake-up time.

4. The communication device according to any one of claims 1 to 3, further comprising: Construction components, which are used to construct a second network.

5. The communication device according to any one of claims 1 to 4, further comprising: Establishment component, the establishment component being used to establish a link with a second communication device different from the communication device. The establishment component is capable of establishing multiple links with the second communication device via different frequency channels.

6. The communication device according to any one of claims 1 to 5, The predetermined frame mentioned above is a management frame.

7. The communication device according to any one of claims 1 to 6, The communication device described therein is an access point multilink device that conforms to the IEEE 802.11 series of standards.

8. The communication device according to any one of claims 1 to 7, The predetermined element mentioned above is a simplified neighbor reporting element, and The information used to identify the first communication device and the information related to the target wake-up time of the first network are included in the simplified neighbor report element.

9. The communication device according to any one of claims 1 to 7, The predetermined element is the neighbor report element, and The information used to identify the first communication device and the information related to the target wake-up time of the first network are included in the neighbor report element.

10. The communication device according to any one of claims 1 to 7, The predetermined element is the target wake-up time element, and The information used to identify the first communication device and the information related to the target wake-up time of the first network are included in the target wake-up time element.

11. A control method for a communication device, the control method comprising: A receiving step, the receiving step being used to receive a wireless frame, the wireless frame including information related to a target wake-up time of a first network constructed by a first communication device, the first communication device being different from the communication device; as well as The sending step is used to send a predetermined frame including predetermined elements, the predetermined elements including information for identifying the first communication device and information related to the target wake-up time of the first network.

12. A program for causing a computer to function as a control method for a communication device according to claim 11.