Communication device, control method, and storage medium

CN122970718APending Publication Date: 2026-10-23CANON KK
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202610378881.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-04-17
Filing Date
2026-03-26
Publication Date
2026-10-23

AI Technical Summary

Technical Problem

因此,由于该操作可能增加电力消耗

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122970718A_ABST
    Figure CN122970718A_ABST
Patent Text Reader

Abstract

The present disclosure provides a communication device, a control method, and a storage medium. A communication device configured to establish a direct connection with another communication device and construct a network related to the direct connection includes a receiving unit configured to receive first information from a first other communication device, the first information indicating whether the first other communication device supports power saving based on a wake-up time reduction.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to communication devices, control methods, and storage media. Background Technology

[0002] In recent years, with the increase in the amount of data to be communicated, communication technologies such as Wireless Local Area Networks (LANs) have been developed. As the main communication standard for using wireless LANs, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard series is known. The IEEE 802.11 standard series includes standards such as IEEE 802.11a / b / g / n / ac / ax. For example, IEEE 802.11ax, as the latest standard, uses Orthogonal Frequency Division Multiple Access (OFDMA) and, in addition to peak throughput (i.e., a maximum of 9.6 gigabits per second (Gbps)), standardizes techniques for improving communication speed under congested conditions.

[0003] On the other hand, the Wi-Fi (registered trademark) Alliance, which develops certification procedures for wireless LAN devices, has developed the Wi-Fi Direct (WFD) standard. The Wi-Fi Direct standard defines the process for exchanging communication parameters and establishing communication links between stations (STAs) in a wireless LAN without using an access point (AP). Wi-Fi is an abbreviation for Wireless Fidelity. AP is an abbreviation for Access Point. STA is an abbreviation for Station. WFD is an abbreviation for Wi-Fi Direct (registered trademark). STAs are sometimes also referred to as "non-AP STAs." WFD communication is an example of point-to-point (P2P) communication, device-to-device (D2D) communication, or direct connection communication.

[0004] The Wi-Fi Alliance (registered trademark) also developed the Wi-Fi Aware standard, which is a standard for searching for services provided by devices. Japanese Patent Application Publication No. 2019-201427 describes a technique for detecting communication devices using the Wi-Fi Aware standard.

[0005] Starting with the IEEE 802.11ah standard, a Target Wake-Up Time (TWT) was introduced for power saving and low-latency communication. The introduction of TWT allows access points (APs) and stations (STAs) to communicate with each other during a pre-determined time period. Time periods outside the pre-determined period are designated as periods without transmission or reception (communication), thus enabling these communication devices to save power. In the following text, the pre-determined time period is referred to as the "TWT Service Period (SP)".

[0006] TWT SP can also be referred to as "wake-up time period (or wake-up duration)", "awake state time period", "active state time period", etc.

[0007] Wi-Fi Direct Release 2 (WFD R2) considers TWT-based P2P power management as a power-saving feature within TWT. Devices that do not support TWT-based P2P power management are not allowed to join P2P groups that perform TWT-based P2P power management. Japanese Unexamined Patent Application Publication No. 2023-547311 describes a TWT technology for P2P communication.

[0008] However, no specific mechanism is defined or clarified for preventing devices from joining P2P groups that perform TWT-based P2P power management. Without such a mechanism, devices that do not support TWT-based P2P power management may inadvertently join P2P groups. In this case, the intended device (e.g., the group owner) cannot operate in TWT-based P2P power management, and may even operate during periods when the intended device should normally be inactive. Therefore, this operation may increase power consumption. Summary of the Invention

[0009] This disclosure aims to provide techniques for preventing or reducing increases in electricity consumption.

[0010] According to one aspect of this disclosure, a communication device is provided, configured to establish a direct connection with other communication devices and construct a network in relation to the direct connection, the communication device comprising: a receiving unit configured to receive first information from a first other communication device, the first information indicating whether the first other communication device supports power saving based on a shortened wake-up time.

[0011] The features of this disclosure will become apparent from the following description of embodiments with reference to the accompanying drawings. The following description of embodiments is given by way of example. Attached Figure Description

[0012] Figure 1 This is a diagram illustrating an example of the construction of a wireless communication system according to an embodiment.

[0013] Figure 2 This is a diagram illustrating an example of the hardware construction of a communication device according to an embodiment.

[0014] Figure 3 This is a diagram illustrating an example of the functional structure of a communication device according to an embodiment.

[0015] Figure 4 This is a flowchart illustrating an example of the process performed by the communication device according to Example 1.

[0016] Figure 5 This is a diagram illustrating an example of the construction of a Target Wake Time (TWT) element according to an embodiment.

[0017] Figure 6 This is a flowchart illustrating an example of the process performed by the communication device according to Example 2. Detailed Implementation

[0018] Embodiments will be described in detail below with reference to the accompanying drawings. The following embodiments do not limit the subject matter described in the appended claims. Although multiple features are described in the embodiments, not all of these features are essential to this disclosure, and multiple features may be selectively combined together. Furthermore, in the drawings, the same or similar parts are designated by the same reference numerals, and redundant descriptions are avoided.

[0019] <Example> (System Structure) Figure 1 This is a diagram illustrating an example of the construction of a wireless communication system according to this embodiment. Figure 1 This illustrates a network formed within a communication system.

[0020] A communication system comprises two or more communication devices. For example, such as Figure 1 As shown, the communication system may include communication device 101, communication device 102, and communication device 103. When communication devices 101, 102, and 103 are not distinguished from each other, communication devices 101, 102, and 103 are sometimes referred to as "communication device 100".

[0021] Each communication device 100 may be a wireless communication device capable of performing wireless communications conforming to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard family, including the IEEE 802.11bn standard. Communication device 100 may have a Station (STA) function capable of performing wireless communications conforming to the IEEE 802.11bn standard family. Communication device 100 may have an Access Point (AP) function conforming to the IEEE 802.11 standard family. IEEE is an abbreviation for the Institute of Electrical and Electronics Engineers. The IEEE 802.11bn standard can also be referred to as the Ultra-High Reliability (UHR) standard. The IEEE 802.11 standard family may include the IEEE 802.11a / b / g / n / ac / ax / be standards. These standards may be referred to as legacy standards. That is, in addition to the IEEE 802.11bn standard, communication device 100 is also compatible with one or more legacy standards. Conversely, communication device 100 may be compatible with one or more legacy standards but not compatible with the IEEE 802.11bn standard.

[0022] The network 110 formed by communication devices 101, 102, and 103 indicates the range within which communication devices 101, 102, and 103 can communicate with each other. That is, within the range of network 110, communication devices 102 and 103 can receive signals transmitted from communication device 101, and communication device 101 can receive signals transmitted from communication devices 102 and 103.

[0023] In addition to the IEEE 802.11 standard family, each communication device 100 is also compatible with other communication standards such as Bluetooth®, Near Field Communication (NFC), Ultra Wideband (UWB), Zigbee (registered trademark), and Multiband OFDM Alliance (MBOA). NFC is an abbreviation for Near Field Communication. UWB is an abbreviation for Ultra Wideband. MBOA is an abbreviation for Multiband OFDM Alliance. UWB includes Wireless Universal Serial Bus (USB), Wireless 1394, WiNET, etc. Communication device 100 is also compatible with wired communication standards such as wired local area networks (LANs).

[0024] Communication device 100 may also have the function of discovering other communication devices 100 and establishing communication links according to the Wi-Fi Direct (WFD) standard. For example, in the process of establishing a WFD-compliant connection, either communication device 101 or 102 can act as a group owner (referred to as "GO"), while the other can act as a client (referred to as "CL"). In this embodiment, communication device 101 can be the GO, providing communication parameters to communication devices 102 and 103, and constructing (or forming, or creating) network 110.

[0025] On the other hand, communication devices 102 and 103, acting as CLs, can receive communication parameters from communication device 101 and join network 110. Alternatively, communication device 102 or 103 can become GOs, and communication devices 101 and 102 or 103 that are not GOs can become CLs. Parameters can be passed from the CL to the GO using bootstrapping technology. In this case, communication device 101 can operate as a temporary AP. For example, communication device 101 notifies other communication devices 100 of beacons, thereby enabling it to notify other communication devices 100 of communication parameters.

[0026] Alternatively, each communication device 100 may have the function of establishing a communication link based on the infrastructure connection.

[0027] Although Figure 1The diagram shows a state with three communication devices 100 (communication devices 101, 102, and 103), but network 110 can be formed by four or more communication devices 100. In this case, the communication devices 100 can communicate with each other, or one of the communication devices 100 can act as a hub and connect to other communication devices 100. For example, network 110 can be constructed based on communication parameters provided by communication device 101 acting as an access point (AP), and multiple communication devices 100 acting as STAs can join network 110.

[0028] Each communication device 100 can be any electronic device, such as a smartphone, tablet, mobile phone, personal computer (PC), camera, headset, printer, monitor, etc., but is not limited to these. Communication device 101 can be any electronic device, such as a wireless LAN router, PC, etc., but is not limited to these. Each communication device 100 can be an information processing device, such as a wireless chip capable of performing wireless communication conforming to the IEEE 802.11bn standard.

[0029] Communication device 100 can communicate wirelessly using frequency bands such as the 2.4 GHz band, 3.6 GHz band, 5 GHz band, 6 GHz band, 45 GHz band, and the 60 GHz band, also known as the millimeter wave band. The frequency bands used by communication device 100 are not limited to these and can also be the Sub-1 GHz band, etc. Communication device 100 can also communicate using bandwidths of 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, 540 MHz, 640 MHz, 1080 MHz, and 2160 MHz. The bandwidth used by communication device 100 is not limited to these and can also be 240 MHz bandwidth, 4 MHz bandwidth, etc. The IEEE 802.11 standard series defines a frequency channel using a 20 MHz bandwidth as a basic channel in frequency bands such as the 2.4 GHz band, 5 GHz band, and 6 GHz band. These standards also define multiple channels that can be used in frequency bands such as the 2.4 GHz band, 5 GHz band, and 6 GHz band. In these standards, a channel can be used in combination with other channels adjacent to it. In this embodiment, the combined use of a channel with other channels adjacent to it is sometimes referred to as "channel bonding." A channel bundle formed by a single channel or two or more channels adjacent to each other is sometimes referred to as a "communication link" (or simply a "link"). That is, a single link formed by two channels with a bandwidth of 20 MHz uses a bandwidth of 40 MHz. The communication device 100 can be a STA multilink device (MLD) or AP MLD that is compatible with multiple links that are established and communicate simultaneously. Figure 1In this process, a single wireless link (link 120) is established between communication device 101 and communication device 102, and a single wireless link (link 121) is established between communication device 101 and communication device 103.

[0030] (Device Structure) Figure 2 This diagram illustrates an example of the hardware configuration of each communication device 100 according to this embodiment. The communication device 100 includes a storage unit 201, a control unit 202, a functional unit 203, an input unit 204, an output unit 205, a communication unit 206, and an antenna 207. The antenna 207 may be a single antenna or multiple antennas.

[0031] Storage unit 201 includes one or more memories such as read-only memory (ROM) and random access memory (RAM), and stores computer programs for performing various operations, as well as various information such as communication parameters for wireless communication. ROM is an abbreviation for read-only memory. RAM is an abbreviation for random access memory. In addition to memories such as ROM and RAM, storage media such as floppy disks, hard disks, solid-state drives (SSDs), optical discs, magneto-optical discs, read-only optical disc memory (CD-ROM), recordable optical discs (CD-R), magnetic tapes, non-volatile memory cards, and digital versatile optical discs (DVDs) can be used as storage unit 201. SSD is an abbreviation for solid-state drive. CD-ROM is an abbreviation for read-only optical disc memory. CD-R is an abbreviation for recordable optical disc. DVD is an abbreviation for digital versatile optical disc. Storage unit 201 may include multiple memories. Storage unit 201 can store setting information input by the user to the communication device 100, information about the status of the communication device 100, such as the remaining battery power included in the communication device 100, and information indicating whether power-saving operation is being performed.

[0032] For example, control unit 202 includes one or more processors such as a central processing unit (CPU) and a microprocessor unit (MPU), and controls the entire communication device 100 by executing computer programs stored in storage unit 201. CPU is an abbreviation for Central Processing Unit. MPU is an abbreviation for Microprocessor Unit. Control unit 202 can control the entire communication device 100 through cooperation with an operating system (OS) and the computer programs stored in storage unit 201. Control unit 202 can also generate data and signals (wireless frames) to be transmitted through communication with other communication devices 100. Control unit 202 may also include multiple processors such as multi-core processors, and use multiple processors to control the entire communication device 100.

[0033] The control unit 202 also controls the functional unit 203 to perform predetermined processes such as wireless communication, video recording, printing, and projection. The functional unit 203 is hardware that enables the communication device 100 to perform the predetermined processes. For example, if the communication device 100 is a camera, then the functional unit 203 is a video recording unit and performs video recording. For example, if the communication device 100 is a printer, then the functional unit 203 is a printing unit and performs printing. For example, if the communication device 100 is a projector, then the functional unit 203 is a projection unit and performs projection. The data to be processed by the functional unit 203 may be data stored in the storage unit 201, or data communicated with other communication devices 100 via the communication unit 206.

[0034] Input unit 204 receives various operations from the user. Output unit 205 provides various outputs to the user via a monitor screen or speaker. The outputs provided by output unit 205 can be displays on the monitor screen, sound output from the speaker, vibration output, etc. Input unit 204 and output unit 205 can both be implemented as a single module, similar to a touchscreen. Each of input unit 204 and output unit 205 can be integrated with or separate from communication device 100.

[0035] Communication unit 206 controls wireless communication conforming to the IEEE 802.11bn standard. Besides the IEEE 802.11bn standard, communication unit 206 can also control wireless communication conforming to other standards in the IEEE 802.11 standard family, or control wired communication using wired LAN, etc. Communication unit 206 can also control antenna 207 to transmit and receive wireless communication signals generated by control unit 202. Communication unit 206 may include multiple communication circuits corresponding one-to-one with multiple links. When communication device 100 is compatible with NFC, Bluetooth®, etc., in addition to the IEEE 802.11bn standard, communication device 100 can control wireless communication conforming to these communication standards. When communication device 100 is capable of performing wireless communication conforming to multiple communication standards, communication device 100 may include communication units and antennas compatible with each communication standard. Communication device 100 communicates data such as image data, document data, and video data with partner communication device 100 via communication unit 206.

[0036] Antenna 207 and communication unit 206 can be constructed as separate components or as a single module.

[0037] The wireless antenna 207 is an antenna capable of communication in the 2.4 GHz band, 5 GHz band, 6 GHz band, etc. In this embodiment, two or more antennas may be present. If the communication unit 206 includes multiple communication units, antennas corresponding to each of the communication units may be present. Alternatively, different antennas may be present for each frequency band.

[0038] Figure 3 This diagram illustrates an example of the functional configuration of each communication device 100 according to this embodiment. The communication device 100 includes a WFD control unit 301, an infrastructure communication control unit 302, a frame control unit 303, and a point-to-point (P2P) power management group control unit 304 based on target wake-up time (TWT). TWT-based P2P power management (TWT-based power management), (in a P2P group or in a direct connection), is an example of power management or power saving based on shortening or limiting the wake-up time. In the following description, TWT-based P2P power management is abbreviated as "P2P PM". A P2P group is a network including one or more CLs communicating with the GO via WFD, and may also be referred to as a "network related to a direct connection," etc.

[0039] WFD control unit 301 controls WFD communication. For example, WFD control unit 301 controls or performs the following processes: finding partner devices according to frames defined by the WFD standard, and exchanging parameters with partner devices and connecting to partner devices via Wi-Fi Protected Setup (WPS) or bootstrapping. WPS is an abbreviation for Wi-Fi Protected Setup. For example, the processes controlled or performed by WFD control unit 301 may include probing, Service Discovery Frame (SDF) processing, WPS processing, bootstrapping, GO negotiation, etc. WFD control unit 301 also builds a network (P2P group) related to WFD (direct connection). WFD control unit 301 can also transmit frames related to WFD communication generated by frame control unit 303 via communication unit 206 and antenna 207, and receive frames related to WFD communication from other communication devices 100. WFD control unit 301 is an example of a construction method or unit, a transmission method or unit, a reception method or unit, a transmission / reception method or unit, a communication method or unit, etc.

[0040] The infrastructure communication control unit 302 controls infrastructure communication. For example, the infrastructure communication control unit 302 controls or performs processes such as discovering partner devices using beacons or the like, and connecting to partner devices through association processes. For example, the processes controlled or performed by the infrastructure communication control unit 302 may include probing processes, authentication processes, association processes, four-way handshake processes, etc. The infrastructure communication control unit 302 can also transmit frames related to infrastructure communication generated by the frame control unit 303 via the communication unit 206 and the antenna 207, and receive frames related to infrastructure communication from other communication devices 100. The infrastructure communication control unit 302 is an example of a transmission method or unit, a receiving method or unit, a transmission / reception method or unit, a communication method or unit, etc.

[0041] The frame control unit 303 receives instructions from the WFD control unit 301 and the infrastructure communication control unit 302 and generates frames. The frame control unit 303 is an example of a generation method or generation unit, etc.

[0042] The P2P PM group control unit 304 determines whether to allow the communication device 100, which has sent a connection request, to be added to a P2P group performing P2P PM. The connection request is a request to directly connect to the communication device 100, which includes the P2P PM group control unit 304, and is, for example, an association request (frame). Specifically, the P2P PM group control unit 304 identifies the P2P PM value belonging to the P2P capability extension attribute from the connection request (frame) sent by the communication device 100. The P2P PM value is included in the capability information field of the P2P capability extension attribute. A P2P PM value of 1 indicates that the communication device 100 supports P2P PM. A P2P PM value of 0 indicates that the communication device 100 does not support P2P PM. Subsequently, based on the P2P PM value, the P2P PM group control unit 304 determines whether the communication device 100 is allowed to be added to the P2P group. Specifically, if the P2P PM value is 1, the P2P PM group control unit 304 determines that the communication device 100 is allowed to be added to the P2P group. On the other hand, if the P2P PM value is 0, the P2P PM group control unit 304 determines that the communication device 100 is not allowed to join the P2P group. In other words, the P2P PM group control unit 304 determines that the communication device 100 should be prevented from joining the P2P group. Alternatively, the P2P PM group control unit 304 performs control to prevent the communication device 100 from joining the P2P group. The P2P capability extension attribute is included in the following frames, etc. These frames are beacon frames, probe request / response frames, association request / response frames, and GO negotiation request / response frames. In this case, " / " means "and / or". The P2P PM group control unit 304 is an example of a network control method or network control unit, a determination method or determination unit, a determination method or determination unit, etc.

[0043] A communication device 100 having only the following functions (e.g., communication device 101 among communication devices 101, 102, and 103) may include a P2P PM group control unit 304: • Communication device 100 is capable of WFD communication; • Communication device 100 is capable of building (forming) a network (P2P group) (capable of operating as a GO); and • Communication device 100 supports P2P PM.

[0044] (operate) Next, a description of the various operations of the processing flow performed by each communication device 100, the processing order in the wireless communication system, etc., will be given.

[0045] [Example 1] In Example 1, communication device 101 performs a GO operation, while communication devices 102 and 103 perform CL operations.

[0046] Figure 4 This is a flowchart illustrating an example of the process for forming a P2P group for P2P PM using communication device 101. This example is based on the premise that the control unit 202 of communication device 101 initiates communication unit 206 of communication device 101 as a GO and causes communication unit 206 of communication device 101 to send beacon frames. For example, this can be executed by the control unit 202 of communication device 101, which executes a program stored in the storage unit 201 of communication device 101. Figure 4 The processing is shown.

[0047] First, in step S401, the communication unit 206 of communication device 101 (hereinafter referred to as "communication unit 206") receives a connection request from communication device 102. At this time, in step S402, communication devices 101 and 102 exchange capability information via beacon frames, connection requests, etc. The capability information regarding P2P is called P2P capability extension attributes. The P2P capability extension attributes included in the above frames include information that enables determination of whether the communication device 100, which has sent the above frames, is compatible with P2P PM. The statement "whether the communication device 100 is compatible with P2P PM" can be replaced by the statement "whether the communication device 100 supports P2P".

[0048] In step S403, the communication unit 206 notifies the control unit 202 of the communication device 101 (hereinafter referred to as "control unit 202") of the received connection request, and based on the connection request notified to the control unit 202, the control unit 202 determines whether the communication device 102 is compatible with P2P PM.

[0049] If the control unit 202 determines that the communication device 102 is compatible with P2P PM ("Yes" in step S403), then in step S404, the control unit 202 performs the following control: That is, in step S404, the control unit 202 notifies the communication unit 206 that P2P PM will be enabled and that beacon frames will be sent via a broadcast TWT schedule, and the communication unit 206 sends beacon frames. Therefore, communication devices 101 and 102 can synchronize with each other in a power-saving state. Furthermore, in step S404, the control unit 202 establishes a connection with the communication device 102 via the communication unit 206. In this way, the control unit 202 constructs a P2P group based on information included in the connection request that enables the determination of whether the communication device 100 is compatible with P2P PM. The following will refer to... Figure 5 Describe the broadcast TWT scheduling.

[0050] After the control unit 202 establishes a connection with the communication device 102, in step S405, the communication unit 206 receives a connection request from the communication device 103 as a new connection request. In step S406, similar to step S402, the communication devices 101 and 103 exchange capability information via beacon frames, connection requests, etc. In step S407, similar to step S403, the communication unit 206 notifies the control unit 202 of the received connection request, and based on the connection request notified to the control unit 202, the control unit 202 determines whether the communication device 103 is compatible with P2P PM.

[0051] If the control unit 202 determines that the communication device 103 is compatible with the P2P PM ("Yes" in step S407), then, as in step S404, the control unit 202 establishes a connection with the communication device 103 via the communication unit 206. The process then returns to step S405.

[0052] On the other hand, if the control unit 202 determines that the communication device 103 is not compatible with P2P PM ("No" in step S407), then in step S408, the control unit 202 sends a message indicating that the connection has been refused (a response to the connection request) to the communication device 103 via the communication unit 206. Subsequently, the process returns to step S405.

[0053] If the control unit 202 determines in step S403 that the communication device 102 is not compatible with the P2P PM ("No" in step S403), then in step S409, the control unit 202 performs the following control: That is, in step S409, the control unit 202 notifies the communication unit 206 that the communication unit 206 will disable the P2P PM and send beacon frames via a TWT broadcast schedule, and the communication unit 206 sends the beacon frames. Furthermore, in step S409, the control unit 202 establishes a connection with the communication device 102 via the communication unit 206 while the TWT is disabled.

[0054] Alternatively, if control unit 202 determines in step S407, in this example, that communication device 103 is not compatible with P2P PM ("No" in step S407), then control unit 202 can operate similarly to step S409. That is, control unit 202 can notify communication unit 206 that communication unit 206 will disable P2P PM and send beacon frames via a broadcast TWT schedule, and communication unit 206 can send beacon frames. Furthermore, control unit 202 can establish a connection with communication device 103 via communication unit 206 while TWT is disabled. In this case, control unit 202 can also establish a connection with communication device 103 via communication unit 206 while TWT is disabled.

[0055] Figure 5 This is a diagram illustrating an example of the construction of a TWT element. Figure 5 The TWT element 500 shown includes references Figure 4 Describes the broadcast TWT scheduling.

[0056] TWT element 500 includes an element ID field 501, a length field 502, a control field 503, a request type field 504, and a target wake-up time field 505. TWT element 500 also includes a nominal minimum TWT wake-up duration field 506 and a TWT wake-up interval tail number field 507. TWT element 500 also includes a broadcast TWT information field 508 and a limit TWT traffic information field 509.

[0057] The element ID field 501 stores 216 as an indicator that TWT element 500 is the value of TWT element.

[0058] The length field 502 is a field that indicates the length of the elements starting from and following the length field 502.

[0059] Control field 503 is used to indicate the type of the TWT element field and whether there are subsequent fields. Control field 503 includes an unavailable mode subfield 510 and a negotiation type subfield 511. Control field 503 also includes a TWT information frame disabled subfield 512 and a wake-up duration unit subfield 513. Control field 503 also includes a link ID bitmap present subfield 514 and an aligned TWT subfield 515.

[0060] The unavailable mode subfield 510 is a field that indicates whether the TWT element 500 is in an unavailable mode. A value of 1 for the unavailable mode subfield 510 indicates that the TWT element 500 is in an unavailable mode. A value of 0 for the unavailable mode subfield 510 indicates that the TWT element 500 is not in an unavailable mode. In this embodiment, the value of the unavailable mode subfield 510 is 0.

[0061] The negotiation type subfield 511 is a field indicating whether the TWT parameter (i.e., TWT element 500) is for all (broadcast) or for individual (individual). The negotiation type subfield 511 is also a field indicating the Wake-up Target Beacon Transmission Time (TBTT) interval. In this embodiment, TWT element 500 is for individual TWT elements, and therefore, the value of the negotiation type subfield 511 is 0.

[0062] The TWT information frame disable subfield 512 is a field indicating whether the TWT information received by the STA is canceled (disabled). In this embodiment, the value of the TWT information frame disable subfield 512 is 0, indicating that the TWT information received by the STA will not be canceled (disabled).

[0063] The wake-up duration unit subfield 513 is a field that indicates the time unit indicated by the nominal minimum TWT wake-up duration field 506. If the value of the wake-up duration unit subfield 513 is 1, the unit is 256 µs. If the value of the wake-up duration unit subfield 513 is 0, the unit is 1 unit of time (TU). In this embodiment, the value of the wake-up duration unit subfield 513 is 1.

[0064] The Link ID Bitmap Existence subfield 514 is a field that indicates whether the Link ID Bitmap field exists. If the Link ID Bitmap field does not exist, the TWT element 500 is enabled only on the links that notified the TWT element 500. If the Link ID Bitmap field exists, the TWT element 500 is enabled on the links indicated by the Link ID Bitmap field. In this embodiment, the Link ID Bitmap field does not exist, and therefore, the value of the Link ID Bitmap Existence subfield 514 is 0.

[0065] The Aligned TWT subfield 515 is an indicator of whether an Aligned TWT link bitmap field exists when negotiating TWT elements across multiple links in a centralized manner. In this embodiment, there is no Aligned TWT link bitmap field, and therefore, the value of the Aligned TWT subfield 515 is 0.

[0066] The request type field 504 stores parameters indicating the request type of the TWT element 500. If the value of the unavailable mode subfield 510 is 0 (i.e., in this embodiment), the request type field 504 includes the following subfields: The request type field 504 includes a TWT request subfield 516 and a TWT setting command subfield 517. The request type field 504 also includes a broadcast TWT recommendation subfield 518 and a TWT wake-up interval index subfield 519.

[0067] TWT Request subfield 516 is a field indicating whether the value indicated by TWT element 500 is requested or required by communication device 100, or whether a TWT is arranged for communication device 100.

[0068] TWT setting command subfield 517 is a field indicating the negotiation type of the frame providing TWT element 500. A value of 0 for TWT setting command subfield 517 indicates a request. A value of 1 indicates a suggestion. This is specified when making a suggestion to a partner device (“1”). A value of 2 indicates a demand. This is specified when making a demand to a partner device (“2”). A value of 3 indicates TWT grouping. This is specified when responding to multiple different STAs in a centralized manner (“3”). A value of 4 indicates accept. This is specified when accepting a request from a partner device (“4”). A value of 5 indicates alternative. This is specified when operating with a different setting than the suggestion or demand from the partner device and requesting a different setting from the partner device (“5”). The TWT setting command subfield 517 has a value of 6 indicating dictate (command). dictate ("6") is specified when operating with a different setting than the suggestion or demand from the partner device and when a different setting is presented to the partner device.

[0069] The Broadcast TWT Recommendation Subfield 518 is a field that indicates whether there is a recommendation for the frames to be sent during the (broadcast) TWT service period (SP), and indicates the recommended frames if a recommendation exists.

[0070] The value of 0 in the recommended subfield 518 of the broadcast TWT indicates that there is no restriction on the frames to be sent.

[0071] A value of 1 in the broadcast TWT recommendation subfield 518 indicates that the recommended frames to be sent are limited to the following frames: •PS-Poll frames and QoS empty frames; •QoS control feedback; • High-efficiency (HE) trigger-based (TB) feedback NDP (null data PHY protocol data unit (PPDU)); • Bandwidth Query Report (BQR); • Buffer Status Report (BSR); • Sounding frames; •Management frames; and • Control response frames.

[0072] The value of 2 in the recommended subfield 518 of the broadcast TWT indicates that the recommended frames to be sent are limited to those other than HETB feedback NDP frames.

[0073] A value of 3 for the recommended subfield 518 in the broadcast TWT indicates that there are no restrictions on frames other than the following: • Flow Indication Map (TIM) frame; and • Fast Initial Link Establishment (FILS) discovery frames that include TIM elements.

[0074] The TWT wake-up interval index subfield 519 is a field indicating the length of the time period between the time periods restricting communication parameters, along with the TWT wake-up interval tail number field 507. This time period is the TWT SP specified by the TWT element 500. In this embodiment, the length of the time period between the time periods restricting communication parameters is called the "TWT wake-up interval," and the unit of the TWT wake-up interval is µs. Specifically, the TWT wake-up interval is the value obtained by exponentiating 2 with the value indicated by the TWT wake-up interval index subfield 519 and multiplying the result by the value indicated by field 507. During the time period outside the TWT SP at the TWT wake-up interval, the communication device 100 may switch to a sleep state (or a dozing state). In the sleep state, the communication device 100 does not perform sending and receiving (communication). In this case, the time period outside the TWT SP at the TWT wake-up interval may be referred to as a "time period during which communication is not possible" or a "time period during which communication is impossible." Alternatively, during the time period outside the TWT SP at the TWT wake-up interval, the communication device 100 may not switch to a sleep state (or a dozing state).

[0075] In this case, during the time period outside the TWT SP at the TWT wake-up interval, the communication device 100 can perform sending and receiving (communication).

[0076] The Target Wake-up Time field 505 is an 8-byte field that indicates the timing synchronization function (TSF) time at which the AP wakes up (operates) (is awake or active) and communication begins, as specified by the TWT SP sent by the AP using a beacon. TSF is an abbreviation for Timing Synchronization Function. If the value of the TWT setting command subfield 517 is 2, 3, or 4, the Target Wake-up Time field 505 may not exist. If the value of the TWT setting command subfield 517 is 0 or 1, the Target Wake-up Time field 505, with an 8-byte length, indicates the AP's TSF time at the start of the communication parameters.

[0077] The nominal minimum TWT wake-up duration field 506 is a field that indicates the length of the TWT SP in units indicated by the wake-up duration unit subfield 513.

[0078] The broadcast TWT information field 508 includes a broadcast TWT ID and a broadcast TWT persistence. When a STA (e.g., communication devices 102 and 103) requests to join or specifies a TWT to provide, the broadcast TWT ID stores the identifier of the target broadcast TWT. The broadcast TWT persistence indicates the TBTT value of the existing broadcast TWT. (See reference...) Figure 4 The described broadcast TWT schedule corresponds to broadcast TWT information field 508.

[0079] The Limit TWT Traffic Information field 509 is used to specify whether STAs other than the target STA are allowed to send. The Limit TWT Traffic Information field 509 may be absent. A value of 0 indicates that no STA has joined the Limit TWT. A value of 1 indicates that one or more STAs have joined the Limit TWT. A value of 2 indicates that it is unlikely that a new Limit TWT will be accepted. A value of 3 indicates that the Basic Service Set Identifier (BSSID) for non-transmitting STAs is performing the Limit TWT.

[0080] Although the above has been referenced Figure 4 An example of constructing a TWT element including broadcast TWT scheduling is described, but similarly in the following examples, the TWT element is referenced above. Figure 5 The described constructs have the same or similar constructions.

[0081] As described above, according to Example 1, the communication device 101, acting as the GO, can form a P2P group for performing TWT-based P2P power management (P2P PM). The communication device 101 verifies whether the communication device 100 that has sent a connection request supports P2P PM. If the communication device 100 that has sent a connection request supports P2P PM, the communication device 101 allows the communication device 100 to join or connect to an existing P2P group. Conversely, if the communication device 100 that has sent a connection request does not support P2P PM, the communication device 101 refuses the communication device 100 from joining or connecting to an existing P2P group. Therefore, P2P groups that support (perform) P2P PM can be maintained. Thus, an increase in power consumption can be prevented or reduced.

[0082] If communication device 102 or 103, which does not support P2P PM, confirms that communication device 101 supports P2P PM based on a beacon frame from communication device 101 (which is the GO), then communication device 102 or 103 can operate as follows: That is, the output unit 205 of communication device 102 or 103 may not display a button for performing the process of connecting to communication device 101 (such as a button for sending a connection request from communication device 102 or 103 to communication device 101). Therefore, if communication device 102 or 103 does not support P2P PM, communication device 102 or 103 does not need to attempt an unnecessary connection with communication device 101.

[0083] [Example 2] In Example 2, similar to Example 1, communication device 101 performs a GO operation, while communication devices 102 and 103 perform CL operations.

[0084] Figure 6 This is a flowchart illustrating an example of the process for forming a P2P group for P2P PM using communication device 101. This example is based on the premise that the control unit 202 of communication device 101 initiates communication unit 206 of communication device 101 as a GO and causes communication unit 206 of communication device 101 to send beacon frames. For example, this can be executed by the control unit 202 of communication device 101, which executes a program stored in the storage unit 201 of communication device 101. Figure 6 The processing is shown.

[0085] Figure 6 Steps S601 to S607 and step S609 shown are respectively similar to Figure 4 Steps S401 to S407 and step S409 are shown and therefore will not be described.

[0086] If the control unit 202 determines that the communication device 103 is compatible with the P2P PM ("Yes" in step S607), then, as in step S604, the control unit 202 establishes a connection with the communication device 103 via the communication unit 206. The process then returns to step S605.

[0087] On the other hand, if the control unit 202 determines that the communication device 103 is not compatible with P2P PM ("No" in step S607), then in step S608, the control unit 202 performs the following control: That is, in step S608, the control unit 202 sends a message indicating that the connection has been refused (a response to the connection request) to the communication device 103 via the communication unit 206. Furthermore, in step S608, the control unit 202 constructs a P2P group that does not support P2P PM. Therefore, in step S608, the control unit 202 constructs a P2P group that does not support P2P PM independently, and the communication unit 206 sends a message to the communication device 103 urging the communication device 103 to join or connect to the newly constructed P2P group. Then, the process returns to step S605. The communication device 103 joins or connects to the newly constructed P2P group.

[0088] As described above, according to Example 2, similar to Example 1, the communication device 101, acting as the GO, is capable of forming a P2P group for TWT-based P2P power management (P2P PM). The communication device 101 verifies whether the communication device 100 that has sent a connection request supports P2P PM. If the communication device 100 that has sent a connection request supports P2P PM, the communication device 101 allows the communication device 100 to join or connect to an existing P2P group. Conversely, if the communication device 100 that has sent a connection request does not support P2P PM, the communication device 101 refuses the communication device 100 from joining or connecting to an existing P2P group and also constructs a P2P group that does not support P2P PM. Therefore, by urging the communication device 100 whose connection was refused to join or connect to the newly constructed P2P group, it is possible to maintain a P2P group that supports (performs) P2P PM.

[0089] Therefore, it can prevent or reduce the increase in electricity consumption.

[0090] In this example, if communication device 101 receives a connection request from communication device 100 that does not support P2P PM, communication device 101 can cancel or terminate a group that supports (performs) P2P PM. Subsequently, communication device 101 can create a P2P group that does not support P2P PM and connect to communication device 100 that has already sent a connection request to the created P2P group. Then, communication device 101 can recreate a P2P group that supports P2P PM. At this time, communication device 100 that is already in or connected to the canceled or terminated P2P group joins or connects to the recreated P2P group, thereby restoring the P2P group that supports P2P PM.

[0091] <Other Embodiments> The arrangement of the above fields (including subfields) is not limited to the example shown in the accompanying drawings of this disclosure, and these fields may be arranged in other orders. The above frame may not include all the fields shown in the accompanying drawings of this disclosure, and may include only some of the fields. Other fields different from those shown in the accompanying drawings of this disclosure may be added to the above frame.

[0092] The combinations of values ​​for each field and their corresponding meanings (indications provided by the values) are not limited to the examples above. For instance, for a 1-bit field, the value "1" and the value "0" can have opposite meanings.

[0093] A storage medium storing program code for software to implement the above functions can be provided to a system or apparatus, and the computer (CPU or MPU) of the system or apparatus can read and execute the program code stored in the storage medium. In this case, the program code read from the storage medium itself implements the functions of the above embodiments, and the storage medium storing the program code constitutes the above apparatus.

[0094] For example, floppy disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, DVDs, etc., can be used as storage media for providing program code.

[0095] The above functions can be achieved not only by executing program code read by the computer, but also by the operating system (OS) running on the computer performing some or all of the actual processing according to the instructions from the program code.

[0096] Furthermore, program code read from the storage medium can be written into a function expansion board inserted into the computer or into the memory included in a function expansion unit connected to the computer.

[0097] Subsequently, the CPU included in the function expansion board or function expansion unit can perform some or all of the actual processing based on instructions from the program code, thereby realizing the above functions.

[0098] This disclosure can also be implemented by providing a program for implementing one or more functions in the above embodiments to a system or device via a network or storage medium, and causing one or more processors of the computer of the system or device to read and execute the program. This disclosure can also be implemented by circuitry (e.g., application-specific integrated circuits (ASICs)) for implementing one or more functions.

[0099] Some of the processes described with reference to the flowcharts in this disclosure can be implemented in hardware. For example, a dedicated circuit can be automatically generated on a field-programmable gate array (FPGA) based on a program used to implement the steps using a pre-defined compiler. Alternatively, the gate array circuit can be formed in a similar manner to the FPGA and implemented as hardware.

[0100] The names of the function boxes, messages, parameters, fields, etc., described in the above embodiments can be changed to other names.

[0101] The order of processes, sequences, flowcharts, etc., in the above embodiments is not limited to the specific order shown, and unless there is a contradiction, substitutions or additional steps can be made. Alternatively, some steps can be omitted.

[0102] The features shown in the above embodiments and the accompanying drawings can all be considered as independent elements with unique technical contributions. In other words, although these features work synergistically in the text of the above detailed description, these features are not limited to such a combination and can be extracted and used independently to solve a specific problem or enhance a specific function. Furthermore, the specific embodiments shown in the above detailed description can include many variations. These embodiments are merely illustrative and do not limit the scope, applicability, control, or configuration of this disclosure in any way. Rather, the above detailed description provides guiding examples for those skilled in the art to implement feasible embodiments. In summary, the operations, methods, steps, units, and schemes described in the above detailed description can be changed in various ways without departing from the scope of the appended claims. In other words, the subject matter including components in the form of replacement, alteration, reconstruction, removal, and / or combination of operations, steps, units, schemes, etc., in a portion of the above embodiments is also considered to be patentable subject matter capable of having unique technical contributions in this disclosure. Furthermore, the subject matter consisting of components in the form of deletion of operations, steps, units, schemes, etc., in a portion of the above embodiments is also considered to be patentable subject matter capable of having unique technical contributions in this disclosure. Furthermore, the subject matter consisting of components in the form of replacing, altering, reconstructing, dismantling and / or combining a portion of the above embodiments and deleting other portions of the above embodiments is also considered to be patentable subject matter capable of having unique technical contributions in this disclosure.

[0103] Based on the above, it is possible to prevent communication devices that do not support TWT-based P2P power management from joining P2P groups that do support TWT-based P2P power management. Therefore, it is possible to prevent or reduce the increase in power consumption of communication devices that support TWT-based P2P power management.

[0104] According to one aspect of this disclosure, it is possible to prevent or reduce the increase in electricity consumption.

[0105] Other embodiments The embodiments of this disclosure can also be implemented by a computer that reads and executes computer-executable instructions (e.g., one or more programs) recorded on a storage medium (which may also be more fully referred to as a "non-transitory computer-readable storage medium") to perform one or more functions of the above embodiments, and / or includes one or more circuits (e.g., application-specific integrated circuits (ASICs)) for performing one or more functions of the above embodiments. The embodiments of this disclosure can also be implemented by a method performed by a computer of a system or device, for example, reading and executing computer-executable instructions from a storage medium to perform one or more functions of the above embodiments, and / or controlling one or more circuits to perform one or more functions of the above embodiments. The computer may include one or more processors (e.g., a central processing unit (CPU), a microprocessor unit (MPU)) and may include a network of separate computers or separate processors to read and execute computer-executable instructions. The computer-executable instructions may be provided to the computer, for example, from a network or storage medium. Storage media may include, for example, hard disks, random access memory (RAM), read-only memory (ROM), storage devices for distributed computing systems, optical discs (such as optical discs (CD), digital versatile optical discs (DVD), or Blu-ray discs (BD)). TM One or more of the following: flash memory devices, memory cards, etc.

[0106] Although this disclosure has been described with reference to embodiments, it should be understood that this disclosure is not limited to the disclosed embodiments. The scope of the appended claims should be interpreted in the broadest possible sense to cover all such variations and equivalent structures and functions.

Claims

1. A communication device configured to establish a direct connection with other communication devices and construct a network associated with said direct connection, said communication device comprising: A receiving unit is configured to receive first information from a first other communication device, the first information indicating whether the first other communication device supports power saving based on a shortened wake-up time.

2. The communication apparatus according to claim 1, wherein The receiving unit receives from the first other communication device a request for direct connection with the communication device, the request including the first information.

3. The communication device according to claim 2, further comprising a transmitting unit configured to, in response to the request, send a response indicating rejection of the direct connection to the first other communication device when the first information indicates that the first other communication device does not support power saving based on the shortened wake-up time.

4. The communication device of claim 1, further comprising a network control unit configured to prevent the first other communication device from joining a first network related to supporting power saving based on the shortened wake-up time when the first information indicates that the first other communication device does not support power saving based on the shortened wake-up time.

5. The communication apparatus of claim 4, further comprising a construction unit configured to construct the first network.

6. The communication device according to claim 5, wherein Before receiving the first information, the receiving unit receives second information from the second other communication device, instructing the second other communication device to support power saving based on the shortened wake-up time. The construction unit constructs the first network based on the second information.

7. The communication apparatus according to claim 5, wherein If the first information indicates that the first other communication device does not support power saving based on the shortened wake-up time, the building unit constructs a second network, which is associated with a direct connection that allows the first other communication device, which does not support power saving based on the shortened wake-up time, to join.

8. The communication apparatus according to claim 7, wherein If the first information indicates that the first other communication device does not support power saving based on the shortened wake-up time, the building unit terminates the first network before building the second network.

9. The communication apparatus according to claim 8, wherein If the first information indicates that the first other communication device does not support power saving based on the reduced wake-up time, and after the construction unit constructs the second network, the construction unit constructs a third network, which is associated with a direct connection that allows one or more other communication devices that support power saving based on the reduced wake-up time and have already joined the first network to join.

10. A control method for controlling a communication device configured to establish a direct connection with other communication devices and construct a network associated with the direct connection, the control method comprising: Receive first information from a first other communication device, the first information indicating whether the first other communication device supports power saving based on a shortened wake-up time.

11. A computer program product for causing a computer to execute a control method of a function for a communication apparatus according to claim 10.

Citation Information

Patent Citations

  • Communication device, search method, and program

    JP2019201427A

  • System and method for target wake times for peer-to-peer communications

    JP2023547311A