Communication device, control method, and program

Abstract

This technology provides a way to properly execute communications that may be performed simultaneously using different communication methods. [Solution] A communication device according to one aspect of the present disclosure includes: receiving means for receiving information from a first partner communication device about a first wake period for communicating with the first partner communication device using the first communication method, and determining means for determining a second wake period for communicating with a second partner communication device using a second communication method, according to the first wake period.

Description

Technical Field

[0001] The present disclosure relates to a communication device, a control method, and a program.

Background Art

[0002] With the increase in the amount of data communicated in recent years, the development of communication technologies such as wireless LAN (Local Area Network) has been promoted. As the main communication standards for wireless LAN, the IEEE (Institute of Electrical and Electronics Engineers) 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, in the latest IEEE 802.11ax standard, technologies for improving the communication speed under congested conditions in addition to a high peak throughput of up to 9.6 gigabits per second (Gbps) using OFDMA (Orthogonal Frequency Division Multiple Access) have been standardized.

[0003] On the other hand, the Wi-Fi (registered trademark) Alliance, which formulates the authentication program for wireless LAN devices, has formulated the WFD standard that defines a procedure for establishing a communication link between STAs by exchanging communication parameters between STAs of the wireless LAN without going through an AP. AP is an abbreviation for Access Point, STA is an abbreviation for station, and WFD is an abbreviation for Wi-Fi Direct (registered trademark). An STA may also be called a non-AP STA.

[0004] In addition, the Wi-Fi Aware standard, which is a standard for searching for services provided by a device, has also been formulated. Patent Document 1 discloses a technique for detecting a communication device using the provisions of the Wi-Fi Aware standard.

[0005] The IEEE 802.11ah standard introduces TWT (Target Wake Time) for power-saving and low-latency communication. By introducing TWT, communication between the AP and STA becomes possible during a predetermined period. Furthermore, by designating the remaining period as a time when no transmission or reception (communication) occurs, the communication device can achieve power savings. Hereafter, the predetermined period will be referred to as TWT SP (Service Period). TWT SP may also be called the wake period (or wake duration), awake state period, active state period, etc.

[0006] An STA can continue infrastructure communication (communication in infrastructure mode) by connecting to an AP, while also communicating with a different STA via WFD (Wide Field Dynamics). This function allows simultaneous communication with two communication devices. Hereafter, performing infrastructure communication and WFD communication simultaneously will be referred to as simultaneous operation. [Prior art documents] [Patent Documents]

[0007] [Patent Document 1] Japanese Patent Publication No. 2019-201427 [Overview of the Initiative] [Problems that the invention aims to solve]

[0008] When the simultaneous operation described above is performed, if the TWT SP is set independently for infrastructure communication and WFD communication, the overall power efficiency of the communication device may decrease, or there may be periods during which the communication device cannot operate. As a result, the communication device may not be able to properly perform at least one of the infrastructure communication and WFD communication, which use different communication methods.

[0009] One aspect of this disclosure, in view of the above, aims to provide a technology for appropriately executing communications that may be performed simultaneously using different communication methods. [Means for solving the problem]

[0010] A communication device according to one aspect of the present disclosure includes: receiving means for receiving information from a first partner communication device about a first wake period for communicating with the first partner communication device using the first communication method, and determining means for determining a second wake period for communicating with a second partner communication device using a second communication method, according to the first wake period. [Effects of the Invention]

[0011] According to one aspect of this disclosure, it is possible to appropriately perform communications that may be executed simultaneously using different communication methods. [Brief explanation of the drawing]

[0012] [Figure 1] This figure shows an example configuration of a wireless communication system according to the embodiment. [Figure 2] This figure shows an example of the hardware configuration of a communication device according to the embodiment. [Figure 3] This figure shows an example of the functional configuration of a communication device according to the embodiment. [Figure 4] This flowchart shows an example of the processing flow performed by the communication device in Example 1. [Figure 5] This flowchart shows an example of the processing flow performed by the communication device in Example 2. [Figure 6] This flowchart shows an example of the processing flow performed by the communication device in Example 3. [Figure 7] This figure shows an example of the processing sequence of a communication device related to Example 1. [Figure 8] This figure shows an example of the processing sequence of a communication device related to Example 1. [Figure 9] This figure shows an example of the processing sequence of a communication device related to Example 2. [Figure 10]A diagram showing an example of a processing sequence of a communication device according to Example 3. [Figure 11] A diagram showing a configuration example of a Channel Usage Request frame and a Channel Usage Response frame according to an embodiment. [Figure 12] A diagram showing a configuration example of a TWT Element according to an embodiment. [Figure 13] A diagram showing a configuration example of a TWT Element according to an embodiment.

Mode for Carrying Out the Invention

[0013] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the content described in the claims. Although a plurality of features are described in the embodiments, not all of these plurality of features are essential to the present disclosure, and the plurality of features may be arbitrarily combined. Further, in the accompanying drawings, the same or similar configurations are denoted by the same reference numerals, and redundant descriptions are omitted.

[0014] <Embodiment> (System Configuration) FIG. 1 is a diagram showing a configuration example of a wireless communication system according to the present embodiment. FIG. 1 shows a network formed in the present wireless communication system.

[0015] The present wireless communication system includes three or more communication devices. For example, as shown in FIG. 1, the present wireless communication system may include a communication device 101, a communication device 102, and a communication device 103. When the communication device 101, the communication device 102, and the communication device 103 are not distinguished, they may be referred to as a communication device 100.

[0016] The communication device 100 may be a wireless communication device capable of performing wireless communication compliant with the IEEE 802.11 standard series, including the IEEE 802.11bn standard. The communication device 100 may have station (STA) functionality capable of performing wireless communication compliant with the IEEE 802.11 standard series. Furthermore, the communication device 100 may also have access point (AP) functionality compliant with the IEEE 802.11 standard series. The IEEE 802.11bn standard may also be called a UHR standard. UHR is an abbreviation for Ultra High Reliability. The IEEE 802.11 standard series may include the IEEE 802.11a / b / g / n / ac / ax / be standards. These standards may be called legacy standards. That is, the communication device 100 may support one or more legacy standards in addition to the IEEE 802.11bn standard. The communication device 100 may support one or more legacy standards and not support the IEEE 802.11bn standard.

[0017] The network 110 formed by communication devices 101 and 102 represents the range within which communication devices 101 and 102 can communicate. That is, within the range of network 110, communication device 102 can receive signals transmitted by communication device 101, and signals transmitted by communication device 102 can be received by communication device 101. Also, communication device 102 can receive signals transmitted by communication device 103, and signals transmitted by communication device 102 can be received by communication device 103. Communication devices 101 and 102 are connected, and communication devices 102 and 103 are connected.

[0018] Furthermore, the communication device 100 may support other communication standards in addition to the IEEE 802.11 series standards, such as Bluetooth®, NFC, UWB, ZigBee®, and MBOA. NFC is an abbreviation for Near Field Communication, UWB is an abbreviation for Ultra Wide Band, and MBOA is an abbreviation for Multi Band OFDM Alliance. UWB includes wireless USB, wireless 1394, WiNET, etc. The communication device 100 may also support wired communication standards such as wired LAN.

[0019] Furthermore, the communication device 100 may have the function of discovering each other and establishing a communication link in accordance with the Wi-Fi Direct (WFD) standard. For example, in the establishment procedure compliant with the WFD standard, either communication device 102 or communication device 103 may take on the role of Group Owner (abbreviated as GO), and the other may take on the role of Client (abbreviated as CL or CLI). In the example shown in Figure 1, communication device 102 may become the GO, provide communication parameters to communication device 103, and construct (or create) network 111. On the other hand, communication device 103, which becomes the CL, may receive communication parameters from communication device 102 and participate in network 111. Note that communication device 103 may become the GO and communication device 102 may become the CL. In this case, communication device 103 may construct (or create) the network. Also, parameters may be passed from the CL to the GO by the Bootstrapping method described later. In this case, communication device 102 may operate as a temporary AP. For example, communication device 102 may notify other communication devices of communication parameters by broadcasting a Beacon. WFD is an example of P2P (Peer to Peer) and may be referred to as P2P in this specification and drawings.

[0020] Alternatively, the communication device 100 may have the function of establishing a communication link according to the infrastructure connection. For example, either communication device 101 or communication device 102 may act as an AP and the other as an STA. In the example shown in Figure 1, communication device 101 may act as an AP, providing communication parameters to communication device 102 and constructing (or creating) the network 110. Meanwhile, communication device 102, acting as an STA, may participate in the network 110 based on the communication parameters it receives from communication device 101. Note that communication device 102 may act as an AP and communication device 101 may act as an STA. In this case, communication device 102 may construct (or create) the network.

[0021] In this embodiment, the connection between communication device 101 and communication device 102 is an infrastructure connection for communication between AP and STA, and the connection between communication device 102 and communication device 103 is a WFD connection for communication between GO and CL. The communication between AP and STA and the communication between GO and CL use different communication methods. However, both connections may be infrastructure connections or WFD connections.

[0022] Although Figure 1 shows a state with three communication devices 100 (communication device 101, communication device 102, and communication device 103), networks 110 and 111 may be configured with four or more communication devices 100. In this case, each communication device 100 may be connected to one another, or one communication device 100 may act as a hub connecting the other communication devices 100. For example, network 110 may be constructed (or created) based on communication parameters provided by communication device 101 acting as an AP, and multiple communication devices 100 acting as STAs may participate in network 110.

[0023] The communication device 100 may be any electronic device such as a smartphone, tablet, mobile phone, PC (Personal Computer), video camera, headset, printer, or display, but is not limited to these. Similarly, the communication device 101 may be any electronic device such as a wireless LAN router or PC, but is not limited to these. The communication device 100 may also be an information processing device such as a wireless chip capable of performing wireless communication compliant with the IEEE 802.11bn standard.

[0024] The communication device 100 can communicate using radio signals in frequency bands such as the 2.4GHz, 3.6GHz, 5GHz, 6GHz bands, and millimeter wave bands such as the 45GHz and 60GHz bands. The frequency bands used by the communication device 100 are not limited to these, and may include, for example, the Sub1GHz band. The communication device 100 can also communicate using bandwidths of 20MHz, 40MHz, 80MHz, 160MHz, 320MHz, 540MHz, 640MHz, 1080MHz, and 2160MHz. The bandwidths used by the communication device 100 are not limited to these, and may include, for example, 240MHz, 4MHz, etc. The IEEE 802.11 series standard specifies frequency channels using a 20MHz bandwidth as basic channels in frequency bands such as the 2.4GHz, 5GHz, and 6GHz bands. Furthermore, this standard defines multiple usable channels in each of the 2.4GHz, 5GHz, and 6GHz frequency bands. Furthermore, this standard allows a channel to be used in combination with other adjacent channels. In this embodiment, using a channel in combination with other adjacent channels is sometimes referred to as channel bonding. Also, a bundle of channels formed by one or two or more adjacent channels is sometimes referred to as a communication link (or simply a link). That is, one link formed by two channels with a bandwidth of 20 MHz uses a bandwidth of 40 MHz. Note that the communication device 100 may be a Multi-Link MLD (STA MLD) or AP MLD that supports Multi-Link, which establishes multiple links simultaneously for communication. In Figure 1, one wireless link (link 120) is established between communication device 101 and communication device 102, and one wireless link (link 121) is established between communication device 102 and communication device 103.

[0025] (Device configuration) Figure 2 shows an example of the hardware configuration of the communication device 100 according to this embodiment. The communication device 100 includes 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. Note that there may be one antenna or multiple antennas as the antenna 207.

[0026] The storage unit 201 is composed of one or more memories such as ROM and RAM, and stores various information such as computer programs for performing various operations described later, and communication parameters for wireless communication. ROM and RAM are abbreviations for Read Only Memory and Random Access Memory, respectively. In addition to memories such as ROM and RAM, the storage unit 201 may also use storage media such as flexible disks, hard disks, SSDs, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, magnetic tapes, non-volatile memory cards, and DVDs. SSD is an abbreviation for Solid State Drive. CD-ROM is an abbreviation for Compact Disc Read Only Memory, CD-R is an abbreviation for Compact Disc Recordable, and DVD is an abbreviation for Digital Versatile Disc. Furthermore, the storage unit 201 may have multiple memories. The storage unit 201 can also store information such as setting information entered by the user to the device, the remaining battery level of the device, and information about the status of the device, such as whether or not power saving operation is being performed.

[0027] The control unit 202 is composed of one or more processors, such as a CPU and an MPU, and controls the entire communication device 100 by executing a computer program stored in the memory unit 201. CPU is an abbreviation for Central Processing Unit, and MPU is an abbreviation for Micro Processing Unit. The control unit 202 may also control the entire communication device 100 in cooperation with the computer program stored in the memory unit 201 and the OS (Operating System). The control unit 202 also generates data and signals (wireless frames) to be transmitted in communication with other communication devices. Furthermore, the control unit 202 may be equipped with multiple processors, such as a multi-core processor, and the entire communication device 100 may be controlled by multiple processors.

[0028] Furthermore, the control unit 202 controls the functional unit 203 to perform predetermined processes such as wireless communication, imaging, printing, and photography. The functional unit 203 is hardware that enables the communication device 100 to perform predetermined processes. For example, if the communication device 100 is a camera, the functional unit 203 is the imaging unit and performs imaging processing. Also, for example, if the communication device 100 is a printer, the functional unit 203 is the printing unit and performs printing processing. Also, for example, if the communication device 100 is a projector, the functional unit 203 is the projection unit and performs projection processing. The data processed by the functional unit 203 may be data stored in the storage unit 201, or data communicated with other communication devices via the communication unit 206, which will be described later.

[0029] The input unit 204 accepts various operations from the user. The output unit 205 provides various outputs to the user via a monitor screen or speaker. Here, the output from the output unit 205 may be a display on the monitor screen, audio output from the speaker, vibration output, etc. The input unit 204 and the output unit 205 may be implemented in a single module, such as a touch panel. The input unit 204 and the output unit 205 may be integrated with a communication device or may be separate components.

[0030] The communication unit 206 controls wireless communication compliant with the IEEE 802.11bn standard. In addition to the IEEE 802.11bn standard, the communication unit 206 may also control wireless communication compliant with other IEEE 802.11 standard series, or wired communication such as wired LAN. The communication unit 206 controls the antenna 207 to transmit and receive signals for wireless communication generated by the control unit 202. The communication unit 206 may be composed of multiple communication circuits corresponding to each of the multiple links. If the communication device 100 supports the NFC standard, Bluetooth standard, etc., in addition to the IEEE 802.11bn standard, it may also control wireless communication compliant with these communication standards. Furthermore, if the communication device 100 can perform wireless communication compliant with multiple communication standards, it may be configured to have separate communication units and antennas corresponding to each communication standard. The communication device 100 communicates data such as image data, document data, and video data with the other communication device via the communication unit 206. The antenna 207 may be configured separately from the communication unit 206, or it may be configured as a single module together with the communication unit 206.

[0031] Antenna 207 is an antenna capable of communication in the 2.4GHz band, 5GHz band, 6GHz band, etc. In this embodiment, there may be two or more antennas, and if the communication unit 206 is composed of multiple communication units, there may be an antenna corresponding to each communication unit. Alternatively, there may be different antennas for each frequency band.

[0032] Figure 3 shows an example of the functional configuration of the 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, a simultaneous operation control unit 304, and a TWT state control unit 305.

[0033] The WFD control unit 301 controls WFD communication. For example, the WFD control unit 301 discovers a partner device according to the frame defined in the WFD standard and controls or executes parameter exchange and connection processing using WPS or Bootstrapping. WPS is an abbreviation for Wi-Fi Protected Setup. The processing controlled or executed by the WFD control unit 301 may consist of, for example, Probe processing, SDF (Service Discovery Frame) processing, WPS processing, Bootstrapping processing, and GO Negotiation processing. The WFD control unit 301 can also transmit frames related to WFD communication generated by the frame control unit 303 and receive frames related to WFD communication from other communication devices. The WFD control unit 301 is an example of a transmitting means, receiving means, transmitting and receiving means, or communication means.

[0034] The infrastructure communication control unit 302 controls infrastructure communication. For example, the infrastructure communication control unit 302 discovers a partner device using a beacon or the like, and controls or executes the process of connecting with the partner device in the Association process. The processes controlled or executed by the infrastructure communication control unit 302 may consist of, for example, Probe processing, Authentication processing, Association processing, and 4way handshake processing. The infrastructure communication control unit 302 can also transmit frames related to infrastructure communication generated by the frame control unit 303 and receive frames related to infrastructure communication from other communication devices. The infrastructure communication control unit 302 is an example of a transmitting means, receiving means, transmitting and receiving means, or communication means.

[0035] The frame control unit 303 receives instructions from the WFD control unit 301 and the infrastructure communication control unit 302 and generates a frame.

[0036] The simultaneous operation control unit 304 integrates and processes the communication parameters and communication periods used by the WFD control unit 301 and the infrastructure communication control unit 302. The simultaneous operation control unit 304 determines the periods used by each of the WFD control unit 301 and the infrastructure communication control unit 302 (for example, the TWT SP as GO (or CL) and the TWT SP as STA (or AP), as described later). The simultaneous operation control unit 304 is an example of a determination means.

[0037] The TWT state control unit 305 receives information from the simultaneous operation control unit 304 and determines the state of the TWT in both WFD communication and infrastructure communication.

[0038] (operation) Next, we will explain the processing flow performed by the communication device 100 described above, as well as various operations such as the processing sequence in the wireless communication system.

[0039] [Example 1] In this example, communication device 101 operates as AP, communication device 102 operates as STA and GO, and communication device 103 operates as CL.

[0040] Figure 4 is a flowchart showing an example of the processing flow that occurs when the control unit 202 executes a program stored in the memory unit 201 of the communication device 102.

[0041] Specifically, Figure 4 shows an example of the process for setting the TWT with simultaneous operation of STA and WFD GO. More specifically, Figure 4 shows an example of the process for setting the TWT after communication device 102 has established infrastructure and WFD connections with communication device 101 and communication device 103, respectively. This process starts when communication device 102 establishes an infrastructure connection with communication device 101 and a WFD connection with communication device 103. Note that this process may also start if communication device 102 has established only one of the connections. Furthermore, this process may be executed repeatedly after the simultaneous operation process.

[0042] In S401, communication device 102 starts up as STA and connects to communication device 101, which operates as AP. Also in S401, communication device 102 starts up as WFD(P2P) GO and connects to communication device 103, which operates as CL.

[0043] Next, communication device 102 decides whether to perform TWT setup first as GO or first as STA (S402). Communication device 102 makes this decision based on whether it first sends a TWT Setup frame to communication device 103 as GO or first receives a TWT Setup frame from communication device 101 as STA. The TWT Setup frame may be a Beacon frame containing a TWT Element. Alternatively, the TWT Element may be included in a Probe Response frame, Association Response frame, etc. Alternatively, communication device 102 may send a Probe Request frame, Association Request frame, etc. containing a TWT Element to request TWT setup as STA. Alternatively, communication device 102 may request TWT setup from communication device 101 using the Channel Usage Request frame shown in Figure 11, which will be described later. Alternatively, communication device 102 may receive a frame requesting TWT setup from communication device 103, which is CL, as GO. A TWT Element is an example of information regarding a TWT SP. TWT SP may also be referred to as the period for communicating with the other communication device using a certain communication method, or the period during which it is possible to communicate with the other communication device using a certain communication method.

[0044] When communication device 102 receives a TWT setting from communication device 101 as an STA (No in S402), it checks (or determines; the same applies hereafter) whether it can set (or start or execute) TWT using WFD (S403). Communication device 102 may determine whether it can set TWT using WFD by, for example, whether only TWT-compatible communication devices are participating in the network created as WFD GO. If even one communication device that does not support TWT, or a communication device that supports TWT but cannot operate with TWT in the network created as GO, is connected to the network created as GO, communication device 102 makes the following determination: That is, communication device 102 determines that it cannot set TWT in the network created as WFD GO. Otherwise, communication device 102 determines that it can set TWT in the network created as WFD GO.

[0045] If the communication device 102 cannot set the TWT using WFD (No in S403), it accepts the TWT setting notified by the communication device 101 and terminates processing.

[0046] On the other hand, if the communication device 102 can set TWT using WFD (Yes in S403), it checks whether the channel operating as STA and the channel operating as GO are the same (S404).

[0047] If these channels are the same (Yes in S404), communication device 102 sets the TWT SP in the network created as GO so that it (completely) overlaps with the TWT SP notified by communication device 101 (S405). This allows communication device 102 to match the TWT SP as STA and the TWT SP as GO, and achieve power saving by making the rest of the time a transmission / reception disabled state (transmission / reception disabled period). Note that the TWT SPs may be set to partially overlap. This makes it easier to perform frame exchange, which is always necessary during TWT SP. Alternatively, communication device 102 may set the TWT SP as STA and the TWT SP as GO for consecutive periods that do not overlap. Since a preparation period is provided before and after the TWT SP to enable frame transmission and reception as a backup, the overhead can be reduced. By reducing the overhead, it becomes possible to operate with reduced power. Note that the expression "set TWT SP" (and similar expressions) may be replaced with the expression "determine TWT SP" (and similar expressions).

[0048] On the other hand, if these channels are different (No in S404), communication device 102 sets the TWT SP on the network created as GO so that it does not overlap (partially) with the TWT SP notified by communication device 101 (S406). If communication device 102 can only operate on one channel at a time, and the same period overlaps for the TWT SPs directed to communication device 101 and communication device 103, communication device 102 may be unable to perform communication with one of them. Therefore, by setting the TWT SP as in S405, both communication device 101 and communication device 103 can continue to communicate. This makes it possible to improve the reliability of communication.

[0049] If communication device 102 first performs TWT configuration as GO (Yes in S402), it checks whether it can configure (or start or execute) TWT as GO (S410). Communication device 102 determines whether it can configure TWT as GO by checking whether there are any communication devices in the network created as GO that are unable to execute WFD TWT. For example, if there is a WFD R1 communication device that is operating as WFD but does not support TWT, or if there is a communication device that does not support WFD and is operating as STA, communication device 102 makes the following determination: That is, communication device 102 determines that the communication device is a communication device that cannot execute TWT. In this case, communication device 102 does not configure TWT as GO there (No in S410), and if it then receives notification of TWT configuration from communication device 101, it follows the notified configuration.

[0050] On the other hand, if the communication device 102 can set the TWT as GO (Yes in S410), it sets the TWT as GO (S411). For example, the communication device 102 may include the TWT Element in the Beacon frame to be sent as GO and send the Beacon frame. Alternatively, the communication device 102 may notify the TWT Element using either a Probe Response frame or an Association Response frame when connecting with the communication device 103. Alternatively, the communication device 102 may set the TWT SP based on a TWT setting request from the communication device 103 (for example, receiving a Channel Usage Request frame from the communication device 103). That is, the communication device 102 may set the TWT SP in a Channel Usage Response frame.

[0051] After setting the TWT as GO, communication device 102 checks whether it can also set the TWT in the network it joins as STA (S412). Unless communication device 102 sets the TWT in the network it joins as STA, it operates as GO according to only the TWT it set as GO. The check to see if it can also set the TWT in the network it joins as STA may be performed, for example, by communication device 102 sending an Association Request frame when communication device 101 joins the network. Alternatively, communication device 102 may check whether it can also set the TWT in the network it joins as STA by sending a Channel Usage Request frame to communication device 101 after joining the network. Alternatively, communication device 102 may wait for Beacon frames, Probe Response frames, Association Response frames, Channel Usage Response frames, etc. from communication device 101. The content that communication device 102 requests from communication device 101 when checking the TWT setting as STA may be the content based on S414 to S416. In other words, communication device 102 may decide whether to request overlapping or non-overlapping TWT SPs for the network it participates in as STA and the network it creates as GO, depending on whether they operate on the same channel. Then, communication device 102 may request the TWT SP from communication device 101 as decided. Alternatively, communication device 102 may request the TWT SP from communication device 101 so that it does not overlap (at least partially) with the TWT SP set as GO. While communication device 101 has not determined the TWT SP, communication device 102 will only perform TWT-related operations with respect to the TWT SP that communication device 102 has set as GO. Communication device 102 will operate without TWT setting when communicating with communication device 101.

[0052] When communication device 101 sets the TWT, communication device 102 checks whether it is necessary to reconfigure the TWT SP in the network in which it participates as GO (S413). For example, if GO and STA are operating on different channels, but the TWT SP set for GO and the TWT SP set in the network in which STA participates partially or completely overlap, then TWT SP reconfiguration is necessary. This reconfiguration is necessary to continue communication with both communication devices. Alternatively, if GO and STA are operating on the same channel, but the TWT SP set for GO and the TWT SP set in the network in which STA participates do not overlap (even partially), it is desirable to reconfigure them so that they overlap. This allows communication device 102 to synchronize the period during which it can send and receive frames as a communication device, enabling more power-efficient simultaneous operation.

[0053] If the communication device 102 needs to reconfigure the TWT SP (Yes in S413), it checks whether the channel operating as STA and the channel operating as GO are the same (S414).

[0054] If these channels are the same (Yes in S414), communication device 102 sets the TWT SP in the network created as GO so that it overlaps with the TWT SP notified by communication device 101 (S415). On the other hand, if these channels are different (No in S414), communication device 102 sets the TWT SP in the network created as GO so that it does not overlap (partially) with the TWT SP notified by communication device 101 (S416). The specific operations in S414 to S416 are the same as the operations in S405 to S407, so the explanation is omitted.

[0055] Figures 7 and 8 show an example of the processing sequence of a communication device when setting the TWT according to Example 1.

[0056] Figure 7 shows an example where the TWT is first set between communication device 101 and communication device 102, and then the TWT is set later between communication device 102 and communication device 103. For example, the case shown in Figure 7 may apply when communication device 102 and communication device 101 are connected first, and then communication device 102 and communication device 103 are connected later.

[0057] The communication device 101 adds (includes) a TWT Element to the Beacon frame, Probe Response frame, Association Response frame, etc., and transmits the frame (701: TWT setup). This allows the communication device 101 to notify the STA connected to the communication device 101 of the TWT SP.

[0058] Communication device 102 confirms the TWT SP based on the TWT Element received from communication device 101. Then, communication device 102 sends a frame containing the TWT Element to communication device 103 in order to determine the TWT SP with communication device 103 (702: TWT setup). The frame sent by communication device 102 at this time may be a Beacon frame, a Probe Response frame, or an Association Response frame. Alternatively, the frame sent by communication device 102 at this time may be a Channel Usage Response frame. The TWT SP set in the TWT Element sent by communication device 102 is determined by communication device 102 based on the TWT SP contained in the TWT Element received from communication device 101. For example, if the channel in which communication device 102 operates as STA and the channel in which it operates as GO are the same, communication device 102 sets (all) the same period, or partially the same period, or consecutive periods. If the channel operating as STA and the channel operating as GO are different, the communication device 102 sets a period such that the TWT SP does not overlap at any point. This can be achieved, for example, by aligning the sum of the TWT Wake Interval and TWT Wake Duration (described later) and shifting only the TSF value indicated by the Target Wake Time. TSF is an abbreviation for Timing Synchronization Function.

[0059] Figure 8 shows an example where the TWT is first set between communication device 102 and communication device 103, and then the TWT is set later between communication device 101 and communication device 102. For example, the case shown in Figure 8 may apply when communication device 102 and communication device 103 are connected first, and then communication device 102 and communication device 101 are connected later.

[0060] The communication device 102 adds (includes) a TWT Element to the Beacon frame, Probe Response frame, Association Response frame, etc., and transmits the frame (801: TWT setup). This allows the communication device 102 to notify the CL connected to the communication device 102 of the TWT SP. The value of the TWT Setup Command subfield 1232, described later, may be 0 (Request TWT).

[0061] The communication device 102 requests a TWT SP from the communication device 101 based on the settings configured in GO (802: TWT suggest). The frame used by the communication device 102 at this time may be an Association Request frame or a Channel Usage Request frame. Alternatively, this frame may not be used. The TWT SP requested by the communication device 102 is determined based on the TWT SP configured by the communication device 102 as GO. For example, if the channel on which the communication device 102 operates as STA and the channel on which it operates as GO are the same, the communication device 102 sets the same period (entirely), a partially the same period, or a continuous period. If the channel on which the communication device 102 operates as STA and the channel on which it operates as GO are different, the communication device 102 sets the period so that the TWT SPs do not overlap at any point. This can be achieved, for example, by aligning the period obtained by adding the TWT Wake Interval and TWT Wake Duration (described later) and shifting only the TSF value indicated by the Target Wake Time. The value of the TWT Setup Command subfield 1232, described later, can be 1 (Suggest TWT) or 2 (Demand TWT).

[0062] On the other hand, the communication device 101 may set the TWT SP for a period different from the request (803: TWT dictate). Here, the TWT SP from the communication device 101 may be sent separately in a Beacon frame after the reply to TWT suggest(802). If the communication device 101 accepts TWT suggest(802), the value of the TWT Setup Command subfield 1232 described later may be 4 (Accept TWT). If the communication device 101 rejects or refuses TWT suggest(802), the communication device 101 may set the value of the TWT Setup Command subfield 1232 described later to 5 (Alternate TWT) and request a new TWT setting. Alternatively, the communication device 101 may set the value of the TWT Setup Command subfield 1232 described later to 6 (Dictate TWT) and present a new TWT setting. Alternatively, the communication device 101 may reject the TWT by setting the value of the TWT Setup Command subfield 1232, described later, to 7 (Reject TWT). If the communication device 101 sends a TWT SP again using a Beacon frame, the communication device 101 may set the value of the TWT Setup Command subfield 1232, described later, to 0 (Request TWT). In the example shown in Figure 8, as described above, the value of the TWT Setup Command subfield 1232 is set to 6 (Dictate TWT).

[0063] Communication device 102 receives TWT dictate(803) and determines whether it is necessary to reconfigure the TWT SP set in GO. If the result of the determination is that reconfiguration is necessary, communication device 102 updates the TWT SP and sends the updated TWT SP to communication device 103 (804: TWT update). Communication device 102 may set the value of the TWT Setup Command subfield 1232, described later, to 0 (Request TWT). Also, TWT update(804) may be sent using a Beacon frame or a Channel Usage Request frame.

[0064] In this way, the communication device 102 can calculate and set the TWT SP during simultaneous operation.

[0065] Figure 11 shows examples of frames used in communications 801 to 804 in the example shown in Figure 8. In this example, Channel Usage Request frames or Channel Usage Response frames are used in communications 801 to 804. Figure 11 is a diagram showing examples of the configuration of Channel Usage Request frames and Channel Usage Response frames according to this embodiment and example.

[0066] These frames include the Category field 1101, the WNM Action field 1102, the Dialog Token field 1103, and the Channel Usage Elements field 1104. These frames also include the Supported Operating Classes Element field 1105, the TWT Element field 1106, and the Timeout Interval Element field 1107.

[0067] The Category field 1101 stores a value of 10, indicating that the frame in question is a WNM Action frame.

[0068] The WNM Action field 1102 stores either a value 21 indicating that it is a Channel Usage Request, or a value 22 indicating that it is a Channel Usage Response frame.

[0069] The Dialog Token field 1103 is a field that indicates an identifier or identification information (ID) assigned to perform a procedure in multiple frame exchanges. For example, suppose the Dialog Token field 1103 in a Channel Usage Request frame is set to 5. In this case, the Channel Usage Response frame, which is a reply to the Channel Usage Request frame, will also be sent with the Dialog Token field 1103 set to 5.

[0070] The Channel Usage Elements field 1104 indicates the channels available to the communication device 100.

[0071] The Supported Operating Classes Element field 1105 shows a list of Operating Classes on which the communication device 100 can operate.

[0072] The TWT Element field 1106 stores the TWT Element. Specific examples of TWT Element used in TWT setup, etc., will be described later with reference to Figures 12 and 13.

[0073] The Timeout Interval Element field 1107 indicates the timeout period for a given procedure.

[0074] Examples of TWT Elements included in the frames transmitted and received in the examples shown in Figures 7 and 8 (and in the examples shown in Figures 9 and 10) will be explained with reference to Figures 12 and 13.

[0075] Figure 12 shows an example of the configuration of a TWT Element used when setting up an Individual TWT that individually sets TWT SPs according to this embodiment and example.

[0076] A TWT Element includes an Element ID field 1201, a Length field 1202, a Control field 1203, and a Request Type field 1204. A TWT Element also includes a Target Wake Time field 1205, a TWT Group Assignment field 1206, and a Nominal Minimum TWT Wake Duration field 1207. A TWT Element also includes a TWT Wake Interval Mantissa field 1208 and a TWT Channel field 1209. A TWT Element also includes a Link ID Bitmap field 1210 and an Aligned TWT Link Bitmap field 1211.

[0077] The Element ID field 1201 stores the value 216, which indicates that the element is a TWT Element.

[0078] The Length field 1202 is a field that indicates the length of the Element after the Length field.

[0079] The Control field 1203 is a field for indicating the type of TWT Element field and whether there are subsequent fields. The Control field 1203 includes the Unavailability Mode subfield 1221 and the Negotiation Type subfield 1222. The Control field 1203 also includes the TWT Information Frame Disabled subfield 1223 and the Wake Duration Unit subfield 1224. The Control field 1203 also includes the Link ID Bitmap Present subfield 1225 and the Aligned TWT subfield 1226.

[0080] The Unavailability Mode subfield 1221 indicates whether or not the system is in Unavailability Mode. A value of 1 in this field indicates that the system is in Unavailability Mode, and a value of 0 indicates that the system is not in Unavailability Mode. In this embodiment, the value of this field is set to 0.

[0081] The Negotiation Type subfield 1222 indicates whether the TWT parameter (and therefore the TWT Element) is broadcast or individual. The Negotiation Type subfield 1222 also indicates whether it represents a Wake TBTT (Target Beacon Transmission Time) interval. Figure 12 shows an example of an individual TWT Element, so in the example shown in Figure 12, the value of the first field is set to 0, indicating that it is individual (and represents an interval between individual TWT SPs).

[0082] The TWT Information Frame Disabled subfield 1223 indicates whether or not the TWT Information received by the STA is canceled (disabled). In this embodiment, the value of this field is set to 0, indicating that the TWT Information received by the STA is not canceled (disabled).

[0083] The Wake Duration Unit subfield 1224 is a field that indicates the unit of time indicated by the Nominal Minimum TWT Wake Duration field 1207. When the value of this field is 1, the unit is 256us, and when the value of this field is 0, the unit is 1TU. In this embodiment, the value of this field is set to 1.

[0084] The Link ID Bitmap Present subfield 1215 indicates whether or not the Link ID Bitmap field 1210 exists. If the Link ID Bitmap field 1210 does not exist, the TWT Element is valid only for the Link to which the TWT Element was notified. If the Link ID Bitmap field 1210 exists, the TWT Element is valid for the Link indicated by the Link ID Bitmap field 1210. A value of 1 in this field indicates that the Link ID Bitmap field 1210 exists. A value of 0 in this field indicates that the Link ID Bitmap field 1210 does not exist. In this embodiment, the value of this field is set to 1.

[0085] The Aligned TWT subfield 1226 is a field that indicates whether or not an Aligned TWT Link Bitmap field exists, which is used when negotiating TWT Elements in multiple Links at once. If the value of this field is 1, it indicates that the Aligned TWT Link Bitmap field exists. If the value of this field is 0, it indicates that the Aligned TWT Link Bitmap field does not exist. In this embodiment, the value of this field is set to 1.

[0086] The Request Type field 1204 stores parameters indicating the request type of the TWT Element. Note that when the value of the Unavailability Mode subfield 1221 is set to 0 (i.e., in this embodiment), the Request Type field 1204 includes the following subfields: the TWT Request subfield 1231 and the TWT Setup Command subfield 1232. The Request Type field 1204 also includes the TWT Flow Identifier subfield 1233 and the TWT Wake Interval Exponent subfield 1234.

[0087] The TWT Request subfield 1231 indicates whether the party requesting the value indicated by the TWT Element is the party to request the value indicated by the TWT Element, or whether the TWT is being scheduled. In communications 701 and 702 shown in Figure 7, and communications 801, 803, and 804 shown in Figure 8, subfield 1231 is set to 1, indicating that the party requesting the value indicated by the TWT Element is the party to request the value. In other TWT procedures (for example, communication 802 shown in Figure 8), subfield 1231 is set to 0.

[0088] The TWT Setup Command subfield 1232 indicates the negotiation type of the frame to which the TWT Element is attached. A value of 0 indicates Request. A value of 1 indicates Suggest. Suggest ("1") is specified when you want to make a suggestion to the other device. A value of 2 indicates Demand. Demand ("2") is specified when you want to make a request to the other device. A value of 3 indicates TWT Grouping. TWT Grouping ("3") is specified when you want to send a reply to multiple different STAs at once. A value of 4 indicates Accept. Accept ("4") is specified when you want to accept a request from the other device. A value of 5 indicates Alternate. Alternate ("5") is specified when you want to operate with different settings than Suggest or Demand from the other device and request different settings from the other device. A value of 6 indicates Dictate. Dictate("6") is specified when you want to operate with settings different from those of the remote device's Suggest or Demand, and you want to present different settings to the remote device.

[0089] The TWT Flow Identifier subfield 1233 is a field that indicates an identifier (ID) for associating a series of procedures in a TWT. In this embodiment, the value of this field is set to 0.

[0090] The TWT Wake Interval Exponent subfield 1234, together with the TWT Wake Interval Mantissa field 1208, indicates the length between periods in which communication parameters are restricted. This period is the TWT SP specified by the TWT Element. In this embodiment, the length between periods in which communication parameters are restricted is called the TWT Wake Interval, and its unit is μs. Specifically, the value indicated by the subfield 1234 is raised to the power of 2, and the result is multiplied by the value indicated by the TWT Wake Interval Mantissa field 1208 to obtain the TWT Wake Interval. The communication device may enter a sleep state (or doze state) during periods other than the TWT SP in the TWT Wake Interval. The communication device does not perform transmission or reception (communication) in the sleep state. In this case, the periods other than the TWT SP in the TWT Wake Interval may be referred to as periods when communication is not possible or impossible. Alternatively, the communication device does not need to enter the sleep state (or doze state) during periods other than TWT SP in the TWT Wake Interval. In this case, the communication device may perform transmission and reception (communication) during periods other than TWT SP in the TWT Wake Interval.

[0091] The Target Wake Time field 1205 is an 8-octet field that indicates the TSF time transmitted by the AP via Beacon at the start time of the TWT SP that is woke (started up) and communicating (in awake or active state). If the value of the TWT Setup Command subfield 1232 is 2, 3, or 4, the Target Wake Time field 1205 may be omitted. If the value of the TWT Setup Command subfield 1232 is 0 or 1, the Target Wake Time field 1205 indicates the TSF time of the AP at the start time when the communication parameters are restricted, in 8 octets.

[0092] The TWT Group Assignment field 1206 is a field that provides an identifier for the TWT Group to which the STA is assigned. The TWT Group Assignment field 1206 may contain a TWT Group ID, a TWT Unit, and a TWT Offset. The TWT Group ID is a 7-bit identifier for the TWT Group to which the STA is assigned. The TWT Unit indicates the unit of (time) between TWT values ​​within the TWT Group identified by the TWT Group ID. The TWT Offset indicates the position within the TWT Group to which the STA that received the TWT Element belongs.

[0093] The Nominal Minimum TWT Wake Duration field 1207 is a field that indicates the length of TWT SP in units indicated by the Wake Duration Unit subfield 1224.

[0094] The TWT Channel field 1209 is a field that specifies the channel to negotiate with the STA as a temporary channel during the TWT SP. A bitmap is prepared with a unit of 20MHz, starting from the lowest subchannel. The TWT SP is set on the channel corresponding to the bit with a value of 1.

[0095] The Link ID Bitmap field 1210 is a field that uses a bitmap to indicate which Link ID the parameters of the TWT Element being sent should be applied to. The TWT Element will be applied to the Link indicated by the Link ID corresponding to the bit with a value of 1. The TWT Element will not be applied to the Link indicated by the Link ID corresponding to the bit with a value of 0.

[0096] The Aligned TWT Link Bitmap field 1211 is a field that shows the Link in bitmap format, which is also applicable to the TWT SP, along with the value indicated by the Link ID Bitmap field 1210. A value of "1" indicates that it is applicable. Bits corresponding to a value of "0" in the Link ID Bitmap field 1210 will also have a value of "0" in the Aligned TWT Link Bitmap field 1211.

[0097] Figure 13 shows an example of the configuration of a TWT Element used when setting up a Broadcast TWT that applies the TWT to the entire connected STA, according to this embodiment and example. Hereinafter, the fields in Figure 13 that are the same as those in Figure 12 will not be explained.

[0098] The Request Type field 1204 includes the Broadcast TWT Recommendation subfield 1321. The Broadcast TWT Recommendation subfield 1321 indicates whether there is a recommendation for the frame sent during the Broadcast TWT SP, and if there is, the recommended frame.

[0099] A value of 0 in subfield 1321 indicates that there are no constraints on the frame being sent.

[0100] A value of 1 in subfield 1321 indicates that it is recommended that the frames to be sent be limited to the next frame. • PS-Poll frames and QoS Null frames. • QoS Control feedback. ·HE(High Efficiency) TB(Trigger Based) feedback NDP(Null Data PPDU(PHY Protocol Data Unit)). ·BQR(Bandwidth Query Report). ·BSR(Buffer Status Report). • sounding. Management framework. • Control Response frame.

[0101] A value of 2 in subfield 1321 indicates that it is recommended that the frames to be sent be limited to frames excluding HE TB feedback NDP from the above.

[0102] If the value of subfield 1321 is 3, it indicates that there are no constraints for frames except the next frame. • TIM (Traffic Indication Map) frame. • FILS (Fast Initial Link Setup) Discovery frame containing a TIM element.

[0103] The Broadcast TWT Info field 1301 is a field that contains specific information about a broadcast TWT. The Broadcast TWT Info field 1301 includes the Broadcast TWT ID and Broadcast TWT Persistence. The Broadcast TWT ID stores the identifier of the target Broadcast TWT, if the transmitting STA specifies a TWT to request participation in or provide. Broadcast TWT Persistence indicates the number of TBTTs in which the Broadcast TWT exists.

[0104] The Restricted TWT Traffic Info field 1302 is used to specify whether transmissions are permitted by STAs other than the target STA. The Restricted TWT Traffic Info field 1302 is optional. A value of 0 in this field indicates that no STAs are participating in the Restricted TWT. A value of 1 in this field indicates that one or more STAs are participating in the Restricted TWT. A value of 2 in this field indicates that it is unlikely that a new Restricted TWT will be accepted. A value of 3 in this field indicates that a nontransmitted BSSID is executing the Restricted TWT.

[0105] When an STA requests a TWT, the STA requests the setting of an Individual TWT. When an AP declares a TWT, the AP sets a Broadcast TWT. In Example 1, in communications 701 and 702 shown in Figure 7, the TWT is set as a Broadcast TWT. The disclosure is not limited thereto, and when a TWT is set between communication device 101 and communication device 102, the TWT may be set when communication device 102 requests an Individual TWT and communication device 101 replies. Similarly, the TWT may be set when communication device 103 requests an Individual TWT and communication device 102 replies. In this case, communication device 102 may decide whether to accept, alternate, dictate, or reject the request from communication device 103 based on the TWT SP agreed upon with communication device 101. Furthermore, when the communication device 102 presents the TWT setting using Dictate, it may present a value calculated based on a period determined between the communication device 101 and the communication device 102 (the value shown in S405 or S406 in Figure 4).

[0106] In this way, in situations where STA and GO can operate simultaneously, the TWT SP of one can be appropriately set according to the TWT SP of the other. This allows for the proper execution of communications that may be performed simultaneously using different communication methods.

[0107] [Example 2] In this example, communication device 101 operates as STA, communication device 102 operates as AP and GO, and communication device 103 operates as CL.

[0108] Figure 5 is a flowchart showing an example of the processing flow that occurs when the control unit 202 executes a program stored in the memory unit 201 of the communication device 102.

[0109] Specifically, Figure 5 shows an example of the process for setting the TWT when AP and WFD GO are operating simultaneously. More specifically, Figure 5 shows an example of the process for setting the TWT after communication device 102 has established infrastructure and WFD connections with communication device 101 and communication device 103, respectively. This process starts when communication device 102 establishes an infrastructure connection with communication device 101 and a WFD connection with communication device 103. Note that this process may also start if communication device 102 has established only one of the connections. Furthermore, this process may be executed repeatedly after the simultaneous operation process.

[0110] In S501, communication device 102 starts up as AP and connects to communication device 101, which operates as STA. Also in S501, communication device 102 starts up as WFD(P2P) GO and connects to communication device 103, which operates as CL.

[0111] The communication device 102 checks whether it can set (or start or execute) TWT as GO (S502). The method of checking in S502 has already been explained in Example 1 (see S410, etc.), so the explanation is omitted here.

[0112] If the communication device 102 can configure TWT (on the network created as GO) (Yes in S502), it checks whether the channel on which it is operating as AP and the channel on which it is operating as GO are the same (S503).

[0113] If these channels are the same (Yes in S503), communication device 102 sets the TWT SP in the network created as GO so that it (completely) overlaps with the TWT SP notified by communication device 101 (S504). This allows communication device 102 to match the TWT SP as AP and the TWT SP as GO, and achieve power saving by making the rest of the time a transmission / reception unavailable period. Note that the TWT SP may be set to partially overlap. This makes it easier to perform frame exchange, which is always necessary during TWT SP. Alternatively, communication device 102 may set the TWT SP as AP and the TWT SP as GO for consecutive periods that do not overlap. Since a preparation period is provided before and after the TWT SP to enable frame transmission / reception as a backup, the overhead can be reduced. By reducing the overhead, it becomes possible to operate with lower power consumption.

[0114] On the other hand, if these channels are different (No in S503), communication device 102 sets the TWT SP on the network created as GO so that it does not overlap (partially) with the TWT SP notified by communication device 101 (S505). If communication device 102 can only operate on one channel at a time, and the same period overlaps for the TWT SPs directed to communication device 101 and communication device 103, communication device 102 may be unable to perform communication with one of them. Therefore, by setting the TWT SP as in S505, both communication device 101 and communication device 103 can continue to communicate. This makes it possible to improve the reliability of communication.

[0115] If the communication device 102 cannot set the TWT as GO (No in S502), it will only set the TWT as AP.

[0116] When connecting, the communication device 102 receives a request from the STA or CL that includes a TWT Element, and then sets the TWT based on its reply. If the request from the STA or CL differs from the value determined in S504 or S505, the communication device 102 changes the TWT SP to the value specified in S504 or S505 by specifying Alternate TWT or Dictate TWT. Alternatively, the communication device 102 may set the Broadcast TWT in the Beacon frame.

[0117] Figure 9 shows an example of the processing sequence of a communication device when setting the TWT in Example 2. Figure 9 shows an example where the TWT is set first between communication device 102 and communication device 103, and then the TWT is set later between communication device 102 and communication device 101. For example, the case shown in Figure 9 may apply when communication device 102 and communication device 103 are connected first, and then communication device 102 and communication device 101 are connected later.

[0118] The communication device 102 adds (includes) a TWT Element to the Beacon frame, Probe Response frame, Association Response frame, etc., that it transmits as GO. Then, the communication device 102 transmits the frame (901: TWT setup). This allows the communication device 102 to notify the CL connected to the communication device 102 of the TWT SP.

[0119] Next, the communication device 102 similarly adds (includes) a TWT Element to the Beacon frame, Probe Response frame, Association Response frame, etc., that it transmits as an AP. Then, the communication device 102 transmits the frame (902: TWT setup). This allows the communication device 102 to notify the STA connected to the communication device 102 of the TWT SP.

[0120] In Example 2, in communications 901 and 902 shown in Figure 9, the TWT is set using Broadcast TWT. The disclosure is not limited thereto, and when a TWT is set between communication device 101 and communication device 102, the TWT may be set when communication device 102 requests an Individual TWT and communication device 101 replies. Similarly, the TWT may be set when communication device 103 requests an Individual TWT and communication device 102 replies. In this case, communication device 102 may decide whether to accept, alternate, dictate, or reject the request from communication device 101 based on the TWT SP agreed upon with communication device 103. Furthermore, when communication device 102 presents a TWT setting using Dictate, it may present a value calculated based on a period agreed upon between communication device 103 and communication device 102 (the value shown in S504 or S505).

[0121] In this way, even in situations where AP and GO can operate simultaneously, the TWT SP of one can be appropriately configured according to the TWT SP of the other. This enables the proper execution of communications that may be performed simultaneously using different communication methods.

[0122] [Example 3] In this example, communication device 101 operates as AP, communication device 102 operates as STA and CL, and communication device 103 operates as GO.

[0123] Figure 6 is a flowchart showing an example of the processing flow that occurs when the control unit 202 executes a program stored in the memory unit 201 of the communication device 102.

[0124] Specifically, Figure 6 shows an example of the process for setting the TWT with the simultaneous operation of STA and WFD CL. More specifically, Figure 6 shows an example of the process for setting the TWT after communication device 102 has established infrastructure and WFD connections with communication device 101 and communication device 103, respectively. This process starts when communication device 102 establishes an infrastructure connection with communication device 101 and a WFD connection with communication device 103. Note that this process may also start if communication device 102 has established only one of the connections. Furthermore, this process may be executed repeatedly after the simultaneous operation process.

[0125] In S601, communication device 102 starts up as STA and connects to communication device 101, which operates as AP. Also in S601, communication device 102 starts up as WFD(P2P) CL and connects to communication device 103, which operates as GO.

[0126] The communication device 102 checks whether TWT can be set (or started or executed) on both STA and CL (S602). Hereinafter, STA and CL will also be referred to as interfaces (IF). The method of checking in S602 has already been explained in Example 1 (see S410, etc.), so the explanation will be omitted here.

[0127] If the communication device 102 can set the TWT on only one of the IFs, or if it cannot set the TWT on both IFs (No in S602), it sets the TWT on only one of the IFs, or does not set the TWT (S612).

[0128] On the other hand, if TWT can be set on both IFs (Yes in S602), the communication device 102 checks whether TWT has already been set on one of the IFs (S603). For example, AP and / or GO may have set TWT in Broadcast TWT, so this check is performed. If TWT has already been set on one of the IFs (Yes in S603), the communication device 102 proceeds to S604, and if TWT has not been set on either IF (No in S603), it proceeds to S613.

[0129] If TWT is set on either IF (Yes in S603), the communication device 102 checks whether STA and CL are operating on the same channel (S604).

[0130] If STA and CL are operating on the same channel (Yes in S604), the communication device 102 sends a TWT setting request on the IF where TWT is not set so that the TWT SP is the same between the two IFs (S605). At this time, the communication device 102 sets the value of the TWT Setup Command subfield 1232 to either 1 (Suggest TWT) or 2 (Demand TWT).

[0131] On the other hand, if STA and CL are operating on different channels (No in S604), the communication device 102 sends a TWT setting request on an IF where the TWT is not set, so that the TWT SPs are different between the IFs (S606).

[0132] The communication device 102 receives a response to the request from the AP or GO and checks whether the TWT setting was rejected (S607).

[0133] In the response frame, if the value of the TWT Setup Command subfield 1232 is 4 and the request is accepted (No in S607), the TWT SP setup is completed in both IFs (S611).

[0134] If the request is rejected (not accepted) (Yes in S607), the communication device 102 first checks for values ​​that can be set in the TWT on the network to which the requesting IF participates, and then sets the TWT. At this point, if the communication device 102 cannot set the TWT, it may proceed to S610. After setting the TWT, the communication device 102 requests or requests in S605 or S606 to reset the TWT SP to match the operation on the IF that did not send the request (S608). After sending the request or request on the IF that did not send the request, the communication device 102 checks for a response from the AP or GO (S609). If the request or request is rejected (not accepted) again (Yes in S609), the communication device 102 gives up on executing the TWT (S610). Alternatively, the communication device 102 may give up on simultaneous operation altogether, leave the network to which one IF participates, and operate only on the other IF. On the other hand, if the request or demand is accepted (No in S609), the TWT SP setting is completed in both IFs (S611).

[0135] In addition, if, in S607, the value of the TWT Setup Command subfield 1232 in the response frame is 5 or 6 and a different TWT is requested, the communication device 102 may proceed to S608. Alternatively, in this case, the communication device 102 may return to S604.

[0136] Furthermore, in S607, if the value of the TWT Setup Command subfield 1232 in the response frame is 7 and the request is rejected, the communication device 102 may proceed to S610.

[0137] If, in S603, TWT is not configured in the network to which both IFs participate (or if the communication device 102 recognizes that it will operate as CL and STA but is not connected to either network), the process proceeds to S613.

[0138] The communication device 102 checks whether STA and CL are operating on the same channel (S613).

[0139] If STA and CL are operating on the same channel (Yes in S613), the communication device 102 requests TWT SP from the connected AP and GO so that the TWT SPs are either (completely) the same duration, partially overlapping, or consecutive durations (S614).

[0140] On the other hand, if the STA and CL are operating on different channels (No in S613), the communication device 102 requests the AP and GO to connect to have different TWT SP periods for each (S615).

[0141] The communication device 102 receives responses to the request from AP and GO and checks whether the request was rejected by both (both IFs) (S616). If both requests were rejected (not accepted) (Yes in S616), the communication device 102 returns to S613. On the other hand, if both requests were not rejected (not accepted) (Yes in S616), the communication device 102 checks whether the request was rejected by only one IF (S617). If the request was accepted by both IFs (No in S617), the TWT SP setting is completed at both IFs (S621). On the other hand, if the request was not accepted by one IF (Yes in S617), the communication device 102 sets the TWT that can be set at the rejected IF. At this time, if the communication device 102 cannot set the TWT at the rejected IF, it may proceed to S620. After setting the TWT, the communication device 102 requests or requests that the TWT SP on the other IF be reset to match the TWT SP that was set on the IF that was initially rejected (S618). After sending the request or request, the communication device 102 checks for a response from the AP or GO (S619). If the request or request is rejected (not accepted) again (Yes in S619), the communication device 102 gives up on executing the TWT (S620). Alternatively, the communication device 102 may give up on simultaneous operation altogether, leave the network it is participating in on one IF, and operate only on the other IF. On the other hand, if the request or request is accepted (No in S619), the setting of the TWT SP on both IFs is completed (S621).

[0142] In addition, if TWT is set on both IFs in S603, the communication device 102 may proceed to S604 or to S613. In S604, the communication device 102 selects one of the IFs and sends a TWT setting request only on the selected IF. On the other hand, in S613, the communication device 102 sends a TWT setting request on both IFs. In this case, if reconfiguration is necessary on either IF, the communication device 102 will send a request to check whether reconfiguration is possible.

[0143] Figure 10 shows an example of the processing sequence of a communication device when setting the TWT in Example 3. Figure 10 shows an example where the TWT is set first between communication device 102 and communication device 103, and then the TWT is set later between communication device 102 and communication device 101. For example, the case shown in Figure 10 may apply when communication device 102 and communication device 103 are connected first, and then communication device 102 and communication device 101 are connected later.

[0144] The communication device 103 adds (includes) a TWT Element to the Beacon frame, Probe Response frame, Association Response frame, etc., that it transmits as GO. Then, the communication device 103 transmits the frame (1001: TWT setup). This allows the communication device 103 to notify the STA connected to the communication device 103 of the TWT SP.

[0145] Next, the communication device 102 calculates the TWT SP to be set with the communication device 101 based on the TWT SP agreed upon with the communication device 103, and requests the calculated TWT SP from the communication device 101 (1002: TWT suggest).

[0146] Communication device 101 does not accept the request from communication device 102, but instead proposes a different TWT SP (1003: TWT dictate).

[0147] Communication device 102 shall accept the proposal from communication device 101. Furthermore, communication device 102 shall determine that it is necessary to reset the TWT SP determined with communication device 103 based on the TWT SP determined with communication device 101.

[0148] Communication device 102 requests communication device 103 to reconfigure the TWT SP (1004: TWT request). Communication 1004 can be implemented, for example, using a Channel Usage Request frame.

[0149] Communication device 103 receives a request from communication device 102 and accepts the request (1005: TWT accept).

[0150] In this way, even in situations where STA and CL can operate simultaneously, the TWT SP of one can be appropriately set according to the TWT SP of the other. This allows for the proper execution of communications that may be performed simultaneously using different communication methods.

[0151] [Other examples] The TWT SP settings described above are applicable when a communication device performs infrastructure communication with one or more other communication devices and performs WFD communication with one or more other communication devices, including in Examples 1 to 3.

[0152] <Other Embodiments> In the embodiments described above (Examples 1 and 2), an example was given in which the TWT on the WFD communication side is set (or reset) according to the TWT setting on the infrastructure communication side. However, this disclosure is not limited to this example. In other embodiments, conversely, the TWT on the infrastructure communication side may be set (or reset) according to the TWT setting on the WFD communication side.

[0153] The following describes an example of the processing in this other embodiment, focusing on the differences from Example 1 described above, with reference to Figure 4.

[0154] In the step corresponding to S402, if the communication device 102 performs TWT configuration first with GO, it proceeds to S403; otherwise, it proceeds to S410.

[0155] If the communication device 102 can set TWT as GO (Yes in S403), it sets TWT as GO and proceeds to S404.

[0156] If the channel operating as STA and the channel operating as GO are the same (Yes in S404), the communication device 102 requests the setting of the TWT SP as STA as follows: That is, the communication device 102 requests the communication device 101 to set the TWT SP as STA so that it overlaps with or is contiguous with the TWT SP set as GO, either in whole or in part. If the request is not rejected, in the step corresponding to S405, the communication device 102 sets the TWT SP as STA as requested.

[0157] On the other hand, if these channels are different (No in S404), communication device 102 requests communication device 101 to set a TWT SP as STA so that it does not overlap (at least partially) with the TWT SP set as GO. If this request is not rejected, in the step corresponding to S406, communication device 102 sets the TWT SP as STA as requested.

[0158] If the communication device 102 can set TWT as GO (Yes in S410), it sets TWT as GO and proceeds to S414.

[0159] If the channel operating as STA and the channel operating as GO are the same (Yes in S414), the communication device 102 requests the setting of the TWT SP as STA as follows: That is, the communication device 102 requests the communication device 101 to set the TWT SP as STA so that it overlaps with or is contiguous with the TWT SP set as GO, either in whole or in part. If the request is not rejected, in the step corresponding to S415, the communication device 102 sets the TWT SP as STA as requested.

[0160] On the other hand, if these channels are different (No in S414), communication device 102 requests communication device 101 to set a TWT SP as STA so that it does not overlap (at least partially) with the TWT SP set as GO. If this request is not rejected, in the step corresponding to S416, communication device 102 sets the TWT SP as STA as requested.

[0161] Next, referring to Figure 5, an example of the processing in this other embodiment will be described, focusing on the differences from Example 2 described above.

[0162] If the communication device 102 can set TWT as GO (Yes in S502), it sets TWT as GO and proceeds to S503.

[0163] If the channel operating as STA and the channel operating as GO are the same (Yes in S503), the communication device 102 sets the TWT SP as AP in the step corresponding to S504 as follows: That is, the communication device 102 sets the TWT SP as AP so that it overlaps with all or part of the TWT SP set as GO, or so that it is continuous with the TWT SP set as GO.

[0164] On the other hand, if these channels are different (No in S503), the communication device 102 sets a TWT SP as an AP in the step corresponding to S505 so that it does not overlap (at least partially) with the TWT SP set as GO.

[0165] A storage medium containing program code for software that implements the above-described functions may be supplied to a system or device, and the computer (CPU, MPU) of the system or device may 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-described embodiment, and the storage medium containing that program code constitutes the above-described device.

[0166] For supplying program code, storage media such as flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, DVDs, etc., can be used.

[0167] Furthermore, the above-mentioned functions may be realized not only by the computer executing the program code it reads, but also by the operating system running on the computer performing some or all of the actual processing based on the instructions of that program code.

[0168] Furthermore, the program code read from the storage medium is written to the memory of a function expansion board inserted into the computer or a function expansion unit connected to the computer. Then, based on the instructions of that program code, the CPU of the function expansion board or function expansion unit may perform some or all of the actual processing to realize the above-mentioned functions.

[0169] This disclosure can also be implemented by supplying a program that implements one or more of the functions of the embodiments described above to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. Furthermore, this disclosure can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions.

[0170] Furthermore, some of the processes described in this disclosure with reference to the flowchart may be implemented in hardware. For example, a dedicated circuit can be automatically generated on the FPGA from a program to implement each step by using a predetermined compiler. Alternatively, a Gate Array circuit may be formed in the same way as the FPGA and implemented in hardware.

[0171] The names of the functional units, messages, parameters, fields, etc., described in the embodiments described above may be changed to other names.

[0172] The order of the processing procedures, sequences, flowcharts, etc., in the embodiments described above is not limited to the specific order presented, and may be rearranged or additional steps may be added, as long as they do not contradict each other.

[0173] According to the above-described embodiment, by appropriately setting the other TWT SP in accordance with one TWT SP, simultaneous operation can be achieved with more efficient power consumption. Furthermore, it becomes possible to perform communication using multiple communication methods (infrastructure communication and WFD communication) without interfering with each other. Therefore, it is possible to properly perform communication that may be executed simultaneously using different communication methods.

[0174] Furthermore, the following additional information is disclosed regarding the above embodiments.

[0175] [Note 1] A receiving means that receives information from a first partner communication device regarding a first wake period for communicating with the first partner communication device using the first communication method, A determination means for determining a second wake period for communicating with a second partner communication device using a second communication method, in accordance with the first wake period, A communication device having the following features.

[0176] [Note 2] The communication device described in Appendix 1, wherein the first communication method is used in a network created by the first partner communication device, and the second communication method is used in a network created by the communication device.

[0177] [Note 3] The communication device according to Appendix 2, further comprising a transmission means for transmitting information requesting the second wake period to the second partner communication device using the second communication method.

[0178] [Note 4] The communication device described in Appendix 2 or 3, wherein the first counterpart communication device is an access point, and the communication device and the second counterpart communication device are stations.

[0179] [Note 5] The communication device described in Appendix 1, wherein the first communication method is used in a first network created by the communication device, and the second communication method is used in a second network created by the communication device.

[0180] [Note 6] The communication device described in Appendix 5 is an access point, and the first and second counterpart communication devices are stations.

[0181] [Note 7] The communication device described in Appendix 1, wherein the first communication method is used in a network created by the first partner communication device, and the second communication method is used in a network created by the second partner communication device.

[0182] [Note 8] The communication device according to Appendix 7, further comprising a transmission means for transmitting information requesting the second wake period to the second partner communication device using the second communication method.

[0183] [Note 9] The communication device described in Appendix 7 or 8, wherein the first counterpart communication device is an access point, and the communication device and the second counterpart communication device are stations.

[0184] [Note 10] The communication device described in Appendix 7 or 8, wherein the second counterpart communication device is an access point, and the communication device and the first counterpart communication device are stations.

[0185] [Note 11] A communication device according to any one of the appendices 1 to 10, wherein the channel used in communication with the first partner communication device using the first communication method and the channel used in communication with the second partner communication device using the second communication method are the same, and the first wake period and the second wake period overlap at least partially.

[0186] [Note 12] A communication device according to any one of the appendices 1 to 10, wherein the channel used in communication with the first partner communication device using the first communication method and the channel used in communication with the second partner communication device using the second communication method are the same, and the first wake period and the second wake period are continuous.

[0187] [Note 13] A communication device as described in any of Appendix 1 to 10, wherein the channel used in communication with the first partner communication device using the first communication method and the channel used in communication with the second partner communication device using the second communication method are different, and the first wake period and the second wake period do not overlap.

[0188] [Note 14] A method for controlling a communication device, A step of receiving information from a first partner communication device regarding a first wake period for communicating with the first partner communication device using the first communication method, A step of determining a second wake period for communicating with a second partner communication device using a second communication method, in accordance with the first wake period, A control method including

[0189] [Note 15] A program to cause the computer of the communication device to execute the control method described in Appendix 14. [Explanation of symbols]

[0190] 201 Storage section 202 Control Unit 206 Communications Department 301 WFD Control Unit 302 Infrastructure Communication Control Unit 304 Simultaneous Operation Control Unit

Claims

1. A receiving means that receives information from a first partner communication device regarding a first wake period for communicating with the first partner communication device using the first communication method, A determination means for determining a second wake period for communicating with a second partner communication device using a second communication method, in accordance with the first wake period, A communication device having the following features.

2. The communication device according to claim 1, wherein the first communication method is used in a network created by the first partner communication device, and the second communication method is used in a network created by the communication device.

3. The communication device according to claim 2, further comprising a transmission means for transmitting information requesting the second wake period to the second partner communication device using the second communication method.

4. The communication device according to claim 2 or 3, wherein the first counterpart communication device is an access point, and the communication device and the second counterpart communication device are stations.

5. The communication device according to claim 1, wherein the first communication method is used in a first network created by the communication device, and the second communication method is used in a second network created by the communication device.

6. The communication device according to claim 5, wherein the communication device is an access point, and the first and second partner communication devices are stations.

7. The communication device according to claim 1, wherein the first communication method is used in a network created by the first partner communication device, and the second communication method is used in a network created by the second partner communication device.

8. The communication device according to claim 7, further comprising a transmission means for transmitting information requesting the second wake period to the second partner communication device using the second communication method.

9. The communication device according to claim 7 or 8, wherein the first counterpart communication device is an access point, and the communication device and the second counterpart communication device are stations.

10. The communication device according to claim 7 or 8, wherein the second counterpart communication device is an access point, and the communication device and the first counterpart communication device are stations.

11. The communication device according to claim 1, wherein, when the channel used in communication with the first partner communication device using the first communication method and the channel used in communication with the second partner communication device using the second communication method are the same, the first wake period and the second wake period overlap at least partially.

12. The communication device according to claim 1, wherein if the channel used in communication with the first partner communication device using the first communication method is the same as the channel used in communication with the second partner communication device using the second communication method, the first wake period and the second wake period are continuous.

13. The communication device according to claim 1, wherein if the channel used in communication with the first partner communication device using the first communication method is different from the channel used in communication with the second partner communication device using the second communication method, the first wake period and the second wake period do not overlap.

14. A method for controlling a communication device, A step of receiving information from a first partner communication device regarding a first wake period for communicating with the first partner communication device using the first communication method, A step of determining a second wake period for communicating with a second partner communication device using a second communication method, in accordance with the first wake period, A control method including

15. A program for causing the computer of a communication device to execute the control method described in claim 14.

Images