Communication control device and communication control method

The communication control device manages RTT Delay Bounds to ensure timely data transmission in Wi-Fi standards, addressing deadline discrepancies and maintaining service quality in applications like VR/AR/XR.

WO2026100334A1PCT designated stage Publication Date: 2026-05-15SONY GROUP CORP
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
SONY GROUP CORP
Filing Date
2025-10-20
Publication Date
2026-05-15

AI Technical Summary

Technical Problem

In Wi-Fi standards, there is a lack of methods to set deadlines based on Round Trip Time (RTT) Delay Bounds, leading to discrepancies between requested and set deadlines, especially in applications like VR/AR/XR, where backhaul transmission and application processing delays can cause downlink data to miss the requested deadline.

Method used

A communication control device and method that includes a control unit to manage deadlines based on RTT Delay Bounds, ensuring data transmission meets the recipient's deadline by controlling wireless communication units to transmit and receive signals with defined deadlines.

Benefits of technology

Ensures timely data delivery by setting and managing deadlines based on RTT Delay Bounds, maintaining high service quality despite backhaul and application processing delays.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2025036788_15052026_PF_FP_ABST
    Figure JP2025036788_15052026_PF_FP_ABST
Patent Text Reader

Abstract

[Problem] To provide a communication control device and a communication control method that make it possible to transmit data acquired in response to a request from a reception destination by a time limit requested by the reception destination. [Solution] A communication control device according to the present disclosure comprises a control unit that controls a wireless communication unit so as to transmit a first wireless data signal including first data (data), wherein the control unit: controls the wireless communication unit so as to receive a second wireless data signal including second data (data) generated on the basis of the first data; and controls the wireless communication unit so as to transmit a signal including first information indicating a time limit related to transmission processing of the second wireless data signal, where the time limit is specified on the basis of the timing of the transmission or reception of the first wireless data signal.
Need to check novelty before this filing date? Find Prior Art

Description

Communication control device and communication control method

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

[0002] In Wi-Fi 7 (IEEE 802.11be) of the Wi-Fi standard (IEEE 802.11 standard), several functions for low-latency traffic (LL Traffic) transmission have been adopted in the standard. On the other hand, in Wi-Fi 7 (IEEE 802.11be), the method for selecting the packet to be transmitted with the highest priority is not defined and depends on the implementation. For example, by designating the packet to be prioritized with a TID (Traffic Identifier) or AC (Access Category) as low-latency traffic, the packet can be transmitted with low latency. However, in this method, when the terminal holds packets that should be preferentially transmitted in addition to the packets that can be treated as low-latency traffic with the above TID or AC, etc., the terminal cannot preferentially transmit such packets.

[0003] In the technical discussion of Wi-Fi 8 (TGbn), the next-generation Wi-Fi standard (IEEE 802.11 standard), a proposal has been made to manage the delay budget of each packet and determine the packet to be prioritized based on that value. As a result, it is expected to perform low-latency transmission more efficiently.

[0004] In the Wi-Fi standard (IEEE 802.11 standard), as part of the SCS (Stream Clarification Service) function, the Delay Bound field in the "QoS Characteristics element" where information is exchanged between the AP and the STA can be used to manage the transmission deadline of the packet.

[0005] However, the deadline specified by the Delay Bound (UL Delay Bound or DL ​​Delay Bound) of the QoS Characteristic element by SCS starts from the moment the uplink (UL) or downlink (DL) packet enters the MAC Layer. Therefore, it is possible to manage the deadline from the moment the packet enters the MAC Layer. When considering applications such as VR (Virtual Reality) / AR (Augmented Reality) / XR (Extended Reality / Cross Reality), the RTT Delay Bound (e.g., Motion-to-Photon Latency), which is the allowable delay time from the generation of a request sent from the terminal (uplink traffic) to the acquisition of data received by the terminal (downlink traffic), becomes important.

[0006] Currently, it is not possible to set deadlines based on RTT Delay Bounds. Therefore, there is a risk of discrepancies between the deadline requested by the device and the deadline set by the Delay Bound.

[0007] For example, consider a scenario where an application application (AP) retrieves data from a server in response to a terminal's request and then sends the data to the terminal. The terminal has a deadline for retrieving the data, determined by the application's request. If the backhaul transmission between the server and the AP, or the application processing on the server, is delayed more than expected, the delay budget for data transmission to the terminal becomes more stringent. However, the DL Delay Bound set in the SCS cannot take this processing delay into account, and therefore cannot prioritize data transmission to ensure it is completed within the terminal's requested deadline. In other words, since the deadline set by the DL Delay Bound is determined from the point in time when the AP receives the data from the server, if the delay is large, the deadline set by the DL Delay Bound may be later than the deadline requested by the terminal, and the downlink data transmission may not be completed within the deadline.

[0008] IEEE802.11-24 / 0264r1, “Timing Information Sharing for Next Generation WLANs,” Peshal Nayak (Samsung)

[0009] This disclosure provides a communication control device and a communication control method that enable the transmission of data acquired in response to a request from a recipient by a deadline requested by the recipient.

[0010] The communication control device of this disclosure includes a control unit that controls a wireless communication unit to transmit a first wireless data signal including first data, the control unit controls the wireless communication unit to receive a second wireless data signal including second data generated based on the first data, and controls the wireless communication unit to transmit a signal including first information indicating a deadline for the transmission process of the second wireless data signal, which is determined based on the timing of the transmission or reception of the first wireless data signal.

[0011] A diagram showing an example configuration of a communication system according to the first embodiment. A block diagram of the AP according to the first embodiment. A block diagram of the STA according to the first embodiment. A diagram showing an example format of a QoS Characteristics Element. A diagram illustrating the problems in a conventional configuration. A diagram showing a first example of a newly defined QoS Characteristics Element in the first embodiment. A diagram showing a second example of a newly defined QoS Characteristics Element in the first embodiment. A diagram showing an example format of the RTT-SCS Request frame Action field newly defined in the first embodiment. A flowchart of a first example of AP operation after RTT Delay Bound setting. A flowchart of a second example of AP operation after RTT Delay Bound setting. A flowchart of an example of STA operation setting RTT Delay Bound. A diagram illustrating the effects of the first embodiment. A diagram illustrating the problems that the second embodiment aims to solve. A diagram showing a New QoS Characteristics Element in the second embodiment. A diagram illustrating the problems that the third embodiment aims to solve. A diagram showing an example format of a New QoS Characteristics Element in the third embodiment. A diagram showing an example configuration of a UL DATA frame in the third embodiment. A flowchart of an example of AP operation in the third embodiment. A block diagram showing an example of computer hardware configuration for executing a series of processes in this disclosure by program. A block diagram showing a schematic configuration example of a smartphone to which the technology disclosed herein applies. A block diagram showing an example of a schematic configuration of an in-vehicle device to which the technology disclosed herein applies. A block diagram showing an example of a schematic configuration of a wireless AP to which the technology disclosed herein applies.

[0012] Embodiments of this disclosure will be described below with reference to the drawings. The following description will focus on the main components of this disclosure, but there may be components and functions not shown or described. The following description does not exclude any components or functions not shown or described.

[0013] (First Embodiment) [System Configuration] Figure 1 shows an example of the configuration of a communication system according to the first embodiment of this disclosure.

[0014] The communication system shown in Figure 1 comprises one AP (Access Point or base station) 100 and one STA (Station, slave unit or terminal device) 200. Furthermore, this system includes a Rendering Server 300 connected to the AP 100 via a wired backhaul network 400, which is a communication network.

[0015] STA200 is connected to AP100 via a wireless link, forming a BSS (Basic Service Set) that allows for wireless information exchange between STA200 and AP100. Here, STA200 is a device (commonly known as a Head Mount Display: HMD) that runs VR / AR / XR applications. Rendering Server 300 is a server or data generation device that generates data related to the video displayed by the application used by STA200 (e.g., a VR application). For example, STA200 detects the position and orientation of the HMD at regular intervals, and generates a request to acquire video (first data) corresponding to the position and orientation. STA200 sends the acquisition request, including the detected position and orientation, to Rendering Server 300 via AP100. Rendering Server 300 generates video-related data (second data, such as video data and data related to video display control) in response to the acquisition request, and sends the generated data to STA200 via AP100. Based on the acquired data, STA200 displays the video on the HMD's display unit. The first and second data may be data generated at the application layer in the OSI (Open Systems Interconnection) reference model. The first and second data may also be data stored in the "Frame body" of a "Data frame" defined as one of the frames in the MAC layer of the WiFi standard (IEEE 802.11 standard). In this case, the first and second data are transmitted or received in the format of a "Data frame".

[0016] There is a time limit, according to the application specifications (requests), between the time a data acquisition request is made in STA 200 and the time STA 200 acquires the data generated by Rendering Server 300. In this embodiment, a method is disclosed that enables AP 100 to control the transmission of data to STA 200 in order to meet this time limit, even if there is a communication delay in the backhaul network 400 or a delay in application processing in Rendering Server 300.

[0017] This disclosure is not limited to the system configuration shown in Figure 1. For example, the STA 200 is not limited to an HMD, but can be any general communication device that receives and displays data generated by the Rendering Server 300, such as a smartphone. The number of STAs may be two or more. The Rendering Server 300 may be located on the cloud side. The backhaul network 400 may be a wireless backhaul network.

[0018] (Configuration of AP100) Figure 2 is a block diagram of AP100 as a wireless communication device or information processing device according to the present disclosure. AP100 mainly comprises a wireless communication unit 110, a control unit 130, a storage unit 140, an antenna 150, and a backhaul communication unit 160. Except for the operations described in this embodiment, AP100 operates as a wireless LAN base station in accordance with IEEE802.11 standards such as IEEE802.11a / b / g / n / ac / ax / be / bn, based on CSMA / CA (Carrier Sense Multiple Access with Carrier Avoidance). In addition to the configuration shown in Figure 2, the wireless communication device or information processing device according to the present disclosure may also include other components such as a display unit and a user operation unit.

[0019] The wireless communication unit 110 communicates wirelessly with other wireless communication devices (devices having a wireless communication unit), namely STAs, to which it is connected. The wireless communication unit 110 includes a communication control unit 111, a communication storage unit 112, a data processing unit 121, a signal processing unit 122, a wireless interface unit 123, and an amplification unit 124.

[0020] The communication control unit 111 controls the operation of each part and the transmission of information between each part. The communication control unit 111 also passes control information and management information to be notified to other wireless communication devices to the data processing unit 121.

[0021] The communication storage unit 112 holds information used by the communication control unit 111. The communication storage unit 112 also holds data to be transmitted and data received. The transmission buffer that holds the data to be transmitted is included in the communication storage unit 112.

[0022] The data processing unit 121 manages the sequence of information to be transmitted during transmission. The information to be transmitted includes data held in the communication storage unit 112, control information received from the communication control unit 111, and management information. After encrypting the information to be transmitted, the data processing unit 121 adds a MAC (Media Access Control) header and an error detection code to generate a MAC frame (hereinafter referred to as a frame). The data processing unit 121 may also perform a process to concatenate multiple frames. Upon reception, the data processing unit 121 performs a process to deconcatenate the MAC header of the received frame, analyzes it, and detects errors. The data processing unit 121 also performs a reorder process in response to a retransmission request. The frame type may be a data frame, a management frame, or a control frame.

[0023] During transmission, the signal processing unit 122 performs encoding, interleaving, and modulation of the frame, adds a physical header, and generates a symbol stream. During reception, the signal processing unit 122 analyzes the physical header, demodulates, deinterleaves, and decodes the symbol stream, and generates a frame. The signal processing unit 122 also performs complex channel characteristic estimation and spatial separation processing as needed.

[0024] During transmission, the wireless interface unit 123 performs digital-to-analog signal conversion, filtering, upconversion, and phase control on the symbol stream to generate a transmission signal. During reception, the wireless interface unit 123 performs downconversion, filtering, and analog-to-digital signal conversion on the received signal to generate a symbol stream.

[0025] The amplification unit 124 amplifies the signal input from the wireless interface unit 123 or the antenna 150. A part of the amplification unit 124 may be an external component of the communication unit. Alternatively, a part of the amplification unit 124 may be included in the wireless interface unit 123.

[0026] Figure 2 shows an example of a SISO (Single-Input Single-Output) configuration with one set of amplifier 124 and antenna 150. However, it is also possible to use multiple sets of antenna 150 and amplifier 124 to enable MIMO (Multi-Input Multi-Output) transmission and reception processing. Furthermore, it is possible to have a configuration with multiple sets of wireless interface units, signal processing units, and data processing units to enable parallel operation of multiple links (multilink) or multiple frequency channels.

[0027] Although the wireless communication unit 110 is assumed to be composed of a single IC, the IC configuration is not limited to this. For example, the wireless interface unit may be configured as a separate IC.

[0028] The control unit 130 controls the wireless communication unit 110 and the communication control unit 111. The control unit 130 may also perform some of the operations of the communication control unit 111. The communication control unit 111 and the control unit 130 may be configured as a single block. The control unit 130 may be configured by a processor such as a CPU (Central Processing Unit) of a computer.

[0029] The storage unit 140 holds information used by the control unit 130 and the wireless communication unit 110. The storage unit 140 may also perform some of the operations of the communication storage unit 112. The storage unit 140 and the communication storage unit 112 may be configured as a single block.

[0030] The backhaul communication unit 160 communicates with other devices via a backhaul network, which is a wired or wireless communication network. These other devices include the Rendering Server 300. The backhaul communication unit 160 decodes packets received from the backhaul network and passes them to the wireless communication unit 110 via the control unit 130. The packets passed here may be in either an access point mode with the IP header intact or a router mode with the IP header decoded and removed by the backhaul communication unit 160. In this embodiment, communication with the Rendering Server 300 is performed via the backhaul communication unit 160, but communication via the wireless communication unit 110 is also possible.

[0031] The communication control device according to this embodiment includes at least one control unit, which includes the functions of at least one of the communication control unit 111 and the control unit 130. This control unit controls the wireless communication unit 110 to receive a first wireless data signal containing first data from the STA 200. The first data is, for example, data that includes a request to acquire second data (e.g., video data) generated by the Rendering Server 300. The control unit also acquires second data generated based on the first data from the Rendering Server 300 and controls the wireless communication unit 110 to transmit a second wireless data signal containing the acquired second data to the STA 200. The control unit controls the wireless communication unit 110 to receive a signal from the STA 200 that includes first information indicating a deadline for the transmission process of the second wireless data signal, which is determined based on the timing of the transmission of the first wireless data signal at the STA 200 or the timing of the reception of the first wireless data signal at the AP 100. The control unit controls the wireless communication unit 110 to perform the transmission process of the second wireless data signal by the deadline indicated by the first information. Details of the operation by this control unit will be described later.

[0032] (Configuration of STA200) Figure 3 is a block diagram of STA200 as a wireless communication device or information processing device according to the present disclosure. STA200 mainly comprises a wireless communication unit 210, a control unit 230, a storage unit 240, and an antenna 250. In addition to the operations described in this embodiment, STA200 also operates as a wireless LAN station in accordance with IEEE802.11 standards such as IEEE802.11a / b / g / n / ac / ax / be / bn. For example, STA200 may operate based on CSMA / CA (Carrier Sense Multiple Access with Carrier Avoidance). In addition to the configuration shown in Figure 3, the wireless communication device or information processing device according to the present disclosure may also include other components such as a display unit and a user operation unit.

[0033] The wireless communication unit 210 performs processing for wireless communication with other wireless communication devices (devices having a wireless communication unit), such as the AP 100 or other STAs, to which it is connected. The wireless communication unit 210 includes a communication control unit 211, a communication storage unit 212, a data processing unit 221, a signal processing unit 222, a wireless interface unit 223, and an amplification unit 224.

[0034] The communication control unit 211 controls the operation of each part and the transmission of information between each part. The communication control unit 211 also passes control information and management information to be notified to other wireless communication devices to the data processing unit 221.

[0035] The communication storage unit 212 holds information used by the communication control unit 211. The communication storage unit 212 also holds data to be transmitted and data received. The transmission buffer that holds the data to be transmitted is included in the communication storage unit 212.

[0036] The data processing unit 221 manages the sequence of information to be transmitted during transmission. The information to be transmitted includes data held in the communication storage unit 212, control information received from the communication control unit 211, and management information. After encrypting the information to be transmitted, the data processing unit 221 adds a MAC (Media Access Control) header and an error detection code to generate a MAC frame (hereinafter referred to as a frame). The data processing unit 221 may also perform a process to concatenate multiple frames. Upon reception, the data processing unit 221 performs a process to deconcatenate the MAC header of the received frame, analyzes it, and detects errors. The data processing unit 221 also performs a reorder process in response to a retransmission request. The frame type may be a data frame, a management frame, or a control frame.

[0037] During transmission, the signal processing unit 222 performs encoding, interleaving, and modulation of the frame, adds a physical header, and generates a symbol stream. During reception, the signal processing unit 222 analyzes the physical header, demodulates, deinterleaves, and decodes the symbol stream, and generates a frame. The signal processing unit 222 also performs complex channel characteristic estimation and spatial separation processing as needed.

[0038] During transmission, the wireless interface unit 223 performs digital-to-analog signal conversion, filtering, upconversion, and phase control on the symbol stream to generate a transmission signal. During reception, the wireless interface unit 223 performs downconversion, filtering, and analog-to-digital signal conversion on the received signal to generate a symbol stream.

[0039] The amplification unit 224 amplifies the signal input from the wireless interface unit 223 or the antenna 250. A part of the amplification unit 224 may be an external component of the communication unit. Alternatively, a part of the amplification unit 224 may be included in the wireless interface unit 223.

[0040] Figure 3 shows an example of an SISO configuration in which one set of amplification unit 224 and antenna 250 is provided. However, it is also possible to use multiple sets of antenna 250 and amplification unit 224 to enable MIMO transmission and reception processing. Furthermore, it is possible to have a configuration with multiple sets of wireless interface units, signal processing units, and data processing units, etc., to enable operation of multiple links (multilink) or multiple frequency channels in parallel.

[0041] Although the wireless communication unit 210 is assumed to be composed of a single IC, the IC configuration is not limited to this. For example, the wireless interface unit may be configured as a separate IC.

[0042] The control unit 230 controls the wireless communication unit 210 and the communication control unit 211. The control unit 230 may also perform some of the operations of the communication control unit 211. The communication control unit 211 and the control unit 230 may be configured as a single block. The control unit 230 may be configured by a processor such as a CPU (Central Processing Unit) of a computer.

[0043] The storage unit 240 holds information used by the control unit 230 and the wireless communication unit 210. The storage unit 240 may also perform some of the operations of the communication storage unit 212. The storage unit 240 and the communication storage unit 212 may be configured as a single block.

[0044] The communication control device according to the present embodiment includes at least a control unit including at least one of the functions of the communication control unit 211 and the control unit 230. This control unit controls the wireless communication unit 210 to transmit a first wireless data signal including first data to the AP 100. The first data is data including, for example, a request for acquiring second data (for example, video data) generated by the Rendering Server 300. Further, this control unit controls the wireless communication unit 210 to receive a second wireless data signal including the second data generated based on the first data from the AP 100. The control unit controls to transmit from the wireless communication unit 210 to the AP 100 a signal including first information indicating a deadline related to the transmission process of the second wireless data signal in the AP 100, which is specified based on the timing of transmission of the first wireless data signal or the timing of reception of the first wireless data signal in the AP 100. Details of the operation by this control unit will be described later.

[0045] (Problems in the conventional configuration) As described in the background art section, in the technical discussion of Wi-Fi 8 (TGbn), there has been a proposal to manage the delay budget of each packet and determine the packet to be prioritized based on the value of the delay budget. Thereby, it is expected to efficiently perform low-delay transmission.

[0046] In Non-Patent Document 1, a terminal (STA) manages an expiration time for each packet, and uses the "Expiration Time" to perform prioritized transmission. According to this, for example, it becomes possible to realize a scheduling function in which the STA notifies the AP of the "Expiration Time" and preferentially triggers the uplink transmission from the STA to the AP before the expiration time. Also, it becomes possible to realize a function in which the AP notifies other APs of the "Expiration Time" of the packets it holds and requests permission for cooperative transmission (for example, temporarily sharing frequency resources). However, with the method of Non-Patent Document 1, although it is possible for the STA or the AP to realize transmitting the data it holds before the expiration time, for example, when the STA requests the AP to transmit the data acquired from the Rendering Server 300 to the STA, a method for transmitting the data before the expiration time required by the STA is not disclosed.

[0047] As an example of a method for setting the expiration time for the AP to transmit the data acquired from the Rendering Server 300 to the STA, a method using the Delay Bound field in the QoS Characteristics element can be considered.

[0048] FIG. 4 shows an example format of the QoS Characteristics Element. The format of FIG. 4 is defined by the WiFi standard (IEEE802.11 standard). The QoS Characteristics Element is exchanged between the AP and the STA as part of the SCS (Stream Clarification Service) function for exchanging / setting QoS information of specific traffic between the AP and the STA.

[0049] The Delay Bound field in the QoS Characteristics Element stores time information indicating the allowable time (Delay Bound) for a packet (more specifically, an MSDU, or the first MSDU constituting an A-MSDU) belonging to the target traffic flow (hereinafter referred to as the target traffic flow) to be transmitted or retransmitted from the MAC layer of the transmitting device (e.g., AP) to the destination device (e.g., STA). Therefore, the transmitting device (e.g., AP) can perform priority transmission using the expiration time of each packet by adding the time information indicated by the Delay Bound field to the time when the packet belonging to the target traffic flow was entered into the MAC layer. The target traffic flow is defined in advance by a traffic flow configuration procedure between the AP and STA. A traffic flow is identified by a combination of various pieces of information, such as source address, destination address, and port number, and is assigned a traffic flow identification information (SCS ID). The receiving side of a packet can determine the traffic flow (SCS ID) to which the received packet belongs by detecting the above combination of information from the header.

[0050] Thus, the expiration time, which is set based on the Delay Bound of the QoS Characteristic element, starts from the moment the UL or DL ​​packet enters the MAC layer. On the other hand, in applications using head-mounted displays (HMDs) such as VR (Virtual Reality) / AR (Augmented Reality) / XR (Extended Reality / Cross Reality), the RTT Delay Bound (e.g., Motion-to-Photon Latency), which is the allowable time from the generation of a request (UL Traffic) in the STA to the acquisition of data (DL DATA), is important. In other words, the STA needs to acquire the data by the expiration time obtained by adding the RTT Delay Bound from the generation time of the UL Traffic. The generation time of UL Traffic corresponds to the time when a request to acquire video data according to position and orientation is generated in the STA, for example, in the VR / AR application example above, and the acquisition time of DL DATA corresponds to the time when the video data generated by the Rendering Server 300 in response to the acquisition request is acquired in the STA.

[0051] Currently, APs cannot set deadlines based on such RTT Delay Bounds. Therefore, there is a risk of discrepancies between the deadline requested by the STA and the deadline set by the Delay Bound. In other words, since the deadline set by the Delay Bound (DL Delay Bound) is determined from the point in time when the AP receives data (packets) from the Rendering Server 300, if there are significant delays in the backhaul network or application processing, the deadline set by the Delay Bound may be later than the deadline requested by the terminal, potentially resulting in the transmission of downlink data not being completed within the terminal's requested deadline. This will be explained in detail below using Figure 5.

[0052] Figure 5 illustrates the problem that this disclosure aims to solve.

[0053] As shown in the upper sequence diagram of Figure 5, a data acquisition request is generated in the STA 200 as UL MSDU#1 (S101), and uplink data (UL DATA) including UL MSDU#1 is sent to the AP 100 (S102). The acquisition request includes information about the position and orientation of the HMD and is a request to acquire data generated by the Rendering Server 300 according to that position and orientation. The acquisition request is generated in the application layer, which is a layer higher than the MAC layer, and the STA 200 detects the generated acquisition request at the MAC layer upon notification from the application.

[0054] AP100 transmits the UL DATA received from STA200 to Rendering Server300 via the backhaul network (S103). Rendering Server300 generates multiple video-related data (DL MSDU#1 to #n) in response to the acquisition request from STA200 and transmits them to AP100 (S103). Step S103 includes backhaul transmission from AP100 to Rendering Server300, application processing in Rendering Server300, and backhaul transmission from Rendering Server300 to AP100.

[0055] AP100 receives DL MSDU#1 to #n sent from Rendering Server 300 (S104) and sends downlink data (DL DATA) containing DL MSDU#1 to #n to STA200. DL MSDU#1 to #n may be aggregated and sent in a single packet, or they may be sent in separate packets. The example in the figure shows an example where DL MSDU#1 to #n are aggregated and sent in a single packet. Note that a packet refers to any unit of data transmission and may include TCP / IP packets, frames such as MAC frames, and segments such as TCP segments.

[0056] STA200 receives downlink data (DL DATA) transmitted from AP100 and controls the video display on the HMD based on MSDU#1 to #n included in the DL DATA.

[0057] In steps S104 and S105, AP100 determines the allowable delay time from the pre-set DL Delay Bound value and performs priority control to ensure that transmission to STA200 (S105) is completed by the expiration time of this delay time. The expiration time is, for example, the time obtained by adding the delay time to the reception time of DL MSDU#1. If the backhaul transmission in step S103 and the application processing in Rendering Server 300 are completed on schedule, this expiration time will match or be shorter than the application's allowable delay time (Application Delay Bound), and packet transmission to STA200 can be completed by the application's allowable expiration time.

[0058] The sequence diagram at the bottom of Figure 5 shows the sequence when the completion of backhaul transmission and application processing in the Rendering Server 300 is delayed beyond the expected time. In step S103, the backhaul transmission and application processing are delayed by time T1. As a result, the expiration time allowed by the DL Delay Bound is set later than the expiration time corresponding to the application's acceptable delay time (Application Delay Bound). The AP prioritizes sending the downlink data (DL DATA) including DL MSDU#1 to #n to the STA 200 by this expiration time. In other words, priority control is not performed to complete transmission by the deadline requested by the application. As a result, there is a higher possibility of malfunctions in the application or degradation of service quality (for example, in VR use cases, image quality degradation / frame drops / increased black areas in the displayed image, etc.).

[0059] Because the time required for such backhaul transmission and application processing varies due to various factors, it is difficult to assume a fixed value. Setting the Expiration Time to the worst-case scenario will likely result in the inability to meet application requirements and a deterioration in service quality.

[0060] Based on the above, in this embodiment, the Expiration Time is set considering the Round Trip Time (RTT), which is the time from the generation of uplink traffic (UL MSDU#1) in the STA200 to the reception of downlink data (DL DATA), that is, considering the application's requirements. The AP prioritizes sending downlink data to the STA200 by the set Expiration Time. As a result, regardless of delays in backhaul transmission and application processing, the downlink data (DL DATA) is delivered to the STA200 by the deadline requested by the application, thereby achieving high service quality. This embodiment is expected to make a significant contribution to improving the quality of the next-generation WiFi standard (IEEE802.11 standard), i.e., the next-generation wireless LAN. The following describes this embodiment in more detail.

[0061] (Details of this embodiment) Figure 6 shows a first format example of a New QoS Characteristics Element as newly defined in this disclosure. The Element in Figure 6 may also be referred to as the first extended QoS Characteristics Element.

[0062] The QoS Characteristics Element in Figure 4 has been expanded, with the addition of RTT Delay Bound and Base SCS ID fields. The inclusion of the RTT Delay Bound and Base SCS ID fields within the Element can be specified in the Control Info field. The Control Info field also has a "Direction" subfield where uplink (UL) or downlink (DL) can be specified. UL corresponds to the direction from STA200 to AP100, and DL corresponds to the direction from AP100 to STA200. While this description is based on the QoS Characteristics element of the WiFi standard (IEEE802.11), any format is acceptable as long as it includes at least some of the following information.

[0063] • RTT Delay Bound: Time information indicating the time (deadline) that is allowed between the time the source device receives or acquires a UL packet (e.g., data including UL MSDU #1) belonging to the target traffic flow specified by the destination device (e.g., STA) and the time the DL packet (e.g., MSDU, or the first MSDU constituting the A-MSDU) belonging to the said traffic flow is sent to the destination device or retransmitted. The time information may be the value of the time length itself, or it may be an index indicating one of a given number of time lengths. In this embodiment, the destination device corresponds to STA200, and the source device corresponds to AP100.

[0064] • Base SCS ID: Identification information (SCS identification information) that indicates the target traffic flow mentioned above. The Base SCS ID field is optional.

[0065] In this embodiment, the RTT Delay Bound and Base SCS ID information is included in the MAC frame as an Element in Figure 6, but it may also be included in other types of packets, such as TCP / IP packets.

[0066] Figure 7 shows a second format example of the New QoS Characteristics Element as newly defined in this disclosure. The Element in Figure 7 may also be referred to as the second extended QoS Characteristics Element.

[0067] Figure 4 shows that the Element now includes the RTT Delay Start Point field and the Base SCS ID field. The inclusion of the RTT Delay Start Point field and the Base SCS ID field within the Element can be specified in the Control Info field. While this description is based on the QoS Characteristics element of the WiFi standard (IEEE 802.11), any format is acceptable as long as it includes at least some of the following information.

[0068] ・Delay Bound Start Point: This element contains information indicating the starting point of the Delay Bound. For example, "0" means "the time when a packet belonging to the target traffic flow (e.g., an MSDU, or the first MSDU constituting an A-MSDU) is received by the source device from Rendering Server 300 (more specifically, the time when the packet is input to the MAC layer)," and "1" means "the time when the source device receives or acquires a packet belonging to the target traffic flow (e.g., UL data including UL MSDU #1) from the destination device." The source device corresponds to AP100, for example, and the destination device corresponds to STA200, for example. In either case, the length of time from the starting point to the expiration time is the time indicated by the Delay Bound.

[0069] • Base SCS ID: SCS identification information indicating the "target traffic flow" mentioned above. The Base SCS ID field is optional.

[0070] In this embodiment, the above-mentioned Delay Bound Start Point and Base SCS ID information is included in the MAC frame as an Element in Figure 7, but it may also be included in other types of packets, such as TCP / IP packets.

[0071] Figure 8 shows an example format of the RTT-SCS Request frame Action field, which is newly defined in this disclosure. The RTT-SCS Request frame Action field is used in the Action frame. The New QoS Characteristics element shown in Figure 6 or Figure 7 can be used in addition to this frame. In order to indicate that the Action frame is an RTT-SCS Request frame, it is necessary to define bits in the “Robust Action field” to specify the new frame.

[0072] The conventional SCS Request frame Action field is extended to store SCS Descriptor elements for each direction in the SCS Descriptor List, allowing simultaneous configuration of SCS for two directions (UL / DL) in each. The SCS Descriptor element for DL ​​includes the New QoS Characteristics element shown in Figure 6 or Figure 7, and the optional Base SCS ID field is not required. The SCS Descriptor element for UL includes the existing QoS Characteristics element. The SCS ID field of the DL SCS Descriptor element is set to identify information about the target traffic flow. The SCS ID field of the UL SCS Descriptor element is also set to identify information about the target traffic flow, and the value of this identification information may be the same as or different from the value of the identification information set in the SCS ID field of the DL SCS Descriptor element. The TCLAS Elements of each UL and DL SCS Descriptor element store information that defines the target traffic flow (e.g., source address, destination address, port number, etc.). Information from the Rendering Server 300 may be used for this purpose.

[0073] STA200 can configure the corresponding UL and DL traffic flows, as well as the RTT Delay Bound or Delay Bound Start Point, in a single frame by sending an Action frame containing the RTT-SCS Request frame Action field to AP100. Furthermore, by sending the RTT-SCS Request frame Action field, STA can specify the target traffic flow without using the Base SCS ID field (see Figure 6 or Figure 7).

[0074] Furthermore, the RTT-SCS Response frame, which is the response frame to the RTT-SCS Request frame, may also be newly defined in a similar format.

[0075] It is also possible to replace the New QoS Characteristics element (see Figure 6 or Figure 7) using an existing SCS-Request frame without using the RTT-SCS Request frame shown in Figure 8. In this case, the SCS for UL traffic flow and the SCS for DL ​​traffic flow are configured in separate SCS-Request frames. At this time, the SCS for UL traffic flow is configured first. The New QoS Characteristics element included in the SCS-Request frame that configures the SCS for DL ​​traffic flow uses the optional Base SCS ID field.

[0076] Using the RTT-SCS Request frame shown in Figure 8 has the advantage of allowing simultaneous execution of both UL and DL SCS settings, as well as enabling the setting of RTT Delay Bound or Delay Bound Start Point without using the Base SCS ID field.

[0077] Figure 9 shows a flowchart of a first example of the operation of AP100 after setting the RTT Delay Bound. The following operations are performed under the control of at least one of the communication control unit 111 or control unit 130 of AP100.

[0078] First, AP100 receives UL data (first data) containing the acquisition request from STA200, which has generated an acquisition request for data (second data) to be generated by Rendering Server300, as UL traffic (S201). In other words, it receives the first wireless data signal containing the first data. The acquisition request corresponds to, for example, UL MSDU#1 shown in Figure 5.

[0079] The system checks whether the UL traffic belongs to the target traffic flow, that is, whether it is the traffic that will serve as the starting point for setting the RTT Delay Bound (S202). Specifically, it checks whether the SCS ID for the UL traffic matches the Base SCS ID in the New QoS Characteristics element configured for the DL traffic. Alternatively, it checks whether the SCS ID for the UL traffic was configured through an RTT-SCS Request (e.g., an exchange of an RTT-SCS Request and an RTT-SCS Response).

[0080] If the traffic flow to which this UL traffic belongs matches the traffic flow of the traffic that will serve as the starting point for setting the RTT Delay Bound (YES in S202), AP100 sets the RTT Expiration Time (S203). Specifically, the acquisition time (reception time) of this UL traffic plus the time information of the RTT Delay Bound field of the New QoS Characteristics element shown in Figure 6 (or the time information of the Delay Bound field of the New QoS Characteristics element with Delay Bound Start Point = 1 in Figure 7) is set as the expiration time for sending DL traffic corresponding to this UL traffic. A timer with the expiration time set may also be started.

[0081] The acquisition time of the UL traffic described above may be, for example, the time when the FCS check of the packets in the UL traffic is completed. Alternatively, it may be the time when the packets leave the MAC layer for transmission to the Rendering Server 300 after the completion of the FCS check. As long as packets belonging to this UL traffic are used, any other time defined by other criteria may also be used.

[0082] After setting the RTT Expiration Time in step S203, or if it is determined that this UL traffic is not the traffic that will initiate the RTT Delay Bound (NO in S202), AP100 sends this UL traffic to the Rendering Server 300 and receives DL data from the Rendering Server 300 as DL traffic (S204). The DL data received from the Rendering Server 300 corresponds to DL MSDU#1 to #n shown in Figure 5. AP100 checks whether the RTT Expiration Time corresponding to this DL traffic has already been set (S205). Specifically, it checks whether the RTT Expiration Time has already been set for the SCS ID corresponding to this DL traffic. If the RTT Expiration Time has already been set (YES in S205), AP100 prioritizes sending the DL traffic to STA200 within the set RTT Expiration Time (S207). In other words, priority control is given to sending a second wireless data signal, which includes data generated by the Rendering Server 300 (second data), to the STA 200 within the set RTT Expiration Time.

[0083] On the other hand, if the RTT Expiration Time is not set (NO in S205), AP100 sets the Expiration Time (DL Expiration Time) from the time information of the DL Delay Bound (see Figure 6 or Figure 7) (S206), and prioritizes sending DL traffic to STA200 within the set DL Expiration Time (S207). In other words, it prioritizes sending a second wireless data signal containing data generated by Rendering Server 300 (second data) to STA200 within the set DL Expiration Time.

[0084] Through the above operations, AP100 can deliver the DL data acquired from Rendering Server 300 to STA200 by the RTT Expiration Time, which is the deadline requested by STA200, even if there are delays in backbone transmission or application processing on Rendering Server 300.

[0085] Figure 10 shows a flowchart of a second example of AP100's operation after setting the RTT Delay Bound. Steps similar to those in Figure 9 are denoted by the same reference numerals, and detailed explanations are omitted.

[0086] The difference from the operation example in Figure 9 is that step S210 is added between steps S205 and S206. In step S210, the RTT Expiration Time and DL Expiration Time are compared to determine which time is earlier. In the format of Figure 6, DL Expiration Time is obtained by adding the input time of DL traffic to the MAC layer to the DL Delay Bound time information, for example, and RTT Expiration Time is obtained by adding the input time of UL traffic to the MAC layer to the RTT Delay Bound time information. If DL Expiration Time is earlier than RTT Expiration Time, the RTT Expiration Time set in step S203 is rewritten to DL Expiration Time (S206), and priority control is performed (S207). If DL Expiration Time is later than RTT Expiration Time or the same time, the currently set RTT Expiration Time is used as is, and priority control is performed (S207).

[0087] Figure 11 is a flowchart showing an example of STA operation for setting the RTT Delay Bound. This example shows how to set the RTT Delay Bound using the RTT-SCS Request frame Action field, but as mentioned above, it is also possible to set it using the existing SCS Request frame.

[0088] STA200 generates an RTT-SCS Request frame, including the RTT-SCS Request frame Action field shown in Figure 8, at the start or during the execution of a VR / AR application, and sends it to AP100 (S301). At this time, the RTT Delay Bound of the New Oos Characteristic Element of the DL's SCS Descriptor element is set to time information indicating the delay time that the application can tolerate. The optional Base SCS ID is not required. The SCS ID field of the DL's SCS Descriptor element is set to identification information related to the target traffic flow. The value of the identification information may be arbitrarily determined, or a predetermined value may be set. The SCS ID field of the UL's SCS Descriptor element is also set to identification information related to the target traffic flow, and the value of this identification information may be the same as the value of the identification information set in the SCS ID field of the DL's SCS Descriptor element, or it may be a different value. The TCLAS Elements of the respective SCS Descriptor elements of UL and DL store information that defines the target traffic flow. At this time, information from Rendering Server 300 may be used.

[0089] After sending the RTT-SCS Request frame, STA200 receives an RTT-SCS Request response from AP100 (S302). Based on this, STA200 determines that the procedure for setting the RTT Delay Bound has been completed at AP100.

[0090] STA200 determines whether a data acquisition request (e.g., UL MSDU#1) has occurred from Rendering Server 300 (S303). If no acquisition request has occurred (NO), STA200 waits until an acquisition request occurs. If an acquisition request occurs (YES), STA200 transmits UL DATA (UL Traffic), which includes the acquisition request (first data) including the HMD's position and orientation, to AP100 as a first radio data signal (S304). STA200 receives DL DATA (DL Traffic), which includes data generated by Rendering Server 300 (e.g., DL MSDU#1 to #n or second data), transmitted from AP100 as a second radio data signal (S305). The DL DATA is received (acquired) by STA200 by the transmission deadline (the deadline for the transmission processing of the second radio data signal at AP100) set at AP100 based on the RTT Delay Bound set in step S301.

[0091] In the operation described above, the transmission deadline set by AP100 upon reception of UL DATA based on the RTT Delay Bound corresponds to the deadline for the transmission processing of the second radio data signal, which is determined based on the timing of the transmission or reception of the first radio data signal. The RTT Delay Bound corresponds to the first information indicating this deadline and is time information related to the transmission processing of the second radio data signal. The RTT-SCS Request frame is an example of a signal containing this first information.

[0092] The deadline for transmission processing (transmission deadline) is, for example, the time obtained by adding the RTT Delay Bound to the time of transmission or reception of the first wireless data signal. The reception time is the time when AP 100 receives the first wireless data signal (for example, the time when the packet of the first wireless data signal is input to the MAC layer), and the transmission time is the time when STA 200 transmits the first wireless data signal. When using the transmission time, a timestamp is added to the first wireless data signal, and AP 100 can determine the transmission time based on the timestamp included in the first wireless data signal.

[0093] The RTT Delay Bound (the length of time indicated by the first information) may be set to a value shorter than the delay time (Application Delay Bound) that the application allows. In other words, the RTT Delay Bound may be set to a value shorter than the length of time from the time the acquisition request occurs in STA200 to the deadline for acquiring the second data (the data from Rendering Server300) as defined by the application.

[0094] Furthermore, the Delay Bound (see Figure 6) included in the New QoS Characteristics Element of the RTT-SCS Request frame transmitted in step S301 is identified based on the timing of the acquisition of data (second data) from the Rendering Server 300 at AP 100, and corresponds to second information indicating the deadline for the transmission processing of the second wireless data signal. The RTT-SCS Request frame contains information on two deadlines: the deadline indicated by the first information and the deadline indicated by the second information. In the operation example in Figure 9 above, the deadline indicated by the first information for the target traffic flow is used as the deadline for DL, while in the operation example in Figure 10, the deadline used is switched according to the relationship between the two deadlines.

[0095] Figure 12 illustrates the effects of this embodiment. The upper figure shows a sequence diagram when there is no delay exceeding expectations in backhaul transmission and application processing, while the lower figure shows a sequence diagram when there is a delay of time T1 exceeding expectations in backhaul transmission and application processing.

[0096] STA200 generates an RTT-SCS Request frame including the RTT-SCS Request frame Action field shown in Figure 8 and sends it to AP100 (S107), and receives an RTT-SCS Request response from AP100 as a response (S108). This configures the target traffic flow and sets the RTT Delay Bound on AP100. The details of the operations in steps S107 and S108 are the same as steps S301 and S302 in the flowchart of Figure 11.

[0097] Whether there is a delay or not, AP100 sets the starting point of the Delay Bound (RTT Delay Bound) when it receives UL DATA (UL traffic) from STA200 (S102) (S110). In other words, the time after the Delay Bound is set as the transmission expiration time (RTT Expiration Time), starting from the time of UL DATA reception. Because the starting point is the time of UL DATA reception, even if delays (time fluctuations) occur in backhaul transmission or application processing, causing fluctuations in the time when DL MSDU#1 to #n from Rendering Server 300 are acquired by AP100, the transmission expiration time remains unchanged. This makes it possible to stably set a transmission expiration time that is appropriate for the delay time (Application Delay Bound) that the application can tolerate. When UL DATA is sent from STA200 in step S102, the transmission expiration time (RTT Expiration Time) may fluctuate slightly due to fluctuations in the time required to complete the transmission. However, since fluctuations during UL DATA transmission are more stable than fluctuations in backhaul transmission or application processing time, this embodiment enables AP100 to perform effective transmission control.

[0098] (Second Embodiment) Figure 13 illustrates the problem that the second embodiment aims to solve. In step S102, UL DATA (UL traffic) is transmitted multiple times over a predetermined period. The UL DATA transmitted each time is the same data. In some applications such as VR / AR, the same UL traffic is transmitted multiple times (redundant transmission) to improve reliability. In this case, AP 100 needs to be able to determine which UL DATA acquisition time (reception time) to use as the basis for setting the RTT Expiration Time. If it is left to the arbitrary judgment of AP 100, for example, as shown in Figure 13, if AP 100 sets the RTT Expiration Time at the timing of the completion of the last UL DATA reception, there is a possibility that the Expiration Time will significantly exceed the transmission completion deadline according to the delay bound allowed by the application.

[0099] Figure 14 shows a third format example of the New QoS Characteristics Element as a New QoS Characteristics Element in the second embodiment. The Element in Figure 14 may also be called the third extended QoS Characteristics Element. A new RTT Delay Bound Start Point Info field has been added to the QoS Characteristics element for UL traffic. This field stores information (start point reference information) for determining how to set the starting point of the Expiration Time setting when the same UL DATA (UL signal) is transmitted multiple times.

[0100] For example, if the origin criterion information is "00", a flag is added to the HT Control field of the MAC Header in UL traffic indicating whether or not it is a packet that will be the origin of the RTT Expiration Time setting. The system then checks the flag information to determine whether or not the target UL traffic (packet) will be used as the origin of the Expiration Time setting. For example, if the flag information is "1", it is determined that it is a packet that will be the origin of the RTT Expiration Time setting, and if it is "0", it is determined that it is not a packet that will be the origin of the RTT Expiration Time setting.

[0101] The number of repetitions is set as the starting point reference information value other than "00". If the RTT Expiration Time is set to the acquisition of the first UL DATA among the repeatedly transmitted UL DATA, a value that identifies the time of the first acquisition (e.g., "01") is set. Which of the multiple transmitted UL DATAs to use as the reference should be determined according to the application specifications or requirements. AP100 can identify the UL packet that will be the starting point for determining the RTT Expiration Time by referring to the starting point reference information in the RTT Delay Bound Start Point Info field.

[0102] Note that the method for determining the UL DATA that serves as the starting point for setting the RTT Expiration Time is not limited to the method described above. For example, even if the RTT Delay Bound Start Point Info field contains a value other than "00", if there is flag information with a value of "1" in the HT Control field of the MAC Header in the UL traffic, you may set the RTT Expiration Time.

[0103] As described above, according to this embodiment, even if the same UL DATA is transmitted multiple times from STA 200, AP 100 can identify the UL DATA that will serve as the starting point for setting the RTT Expiration Time.

[0104] (Third Embodiment) Figure 15 illustrates the problem that the third embodiment aims to solve. If STA200 fails to transmit UL DATA in step S102, STA200 waits for a certain period (backoff) and then attempts to retransmit (S112). Transmission failure means that an Ack was not received from the destination AP100, and this can occur if the AP100 fails to decode the UL DATA signal (wireless data signal) or if the UL DATA signal does not reach the AP100. When retransmitting UL DATA, a large discrepancy occurs between the generation timing of UL MSDU#1 in step S101 and the completion timing of UL DATA transmission in step S112. As a result, there is a risk of a large discrepancy T2 occurring between the RTT Expiration Time set based on the RTT Dealy Bound and the transmission deadline according to the Delay Bound requested by the application.

[0105] Figure 16 shows a fourth format example of the New QoS Characteristic Element in the third embodiment. The Element in Figure 16 may also be referred to as the fourth extended QoS Characteristic Element. It includes multiple RTT Delay Bounds, and the number of RTT Delay Bounds is set in the RTT Delay Bound Info Count field. AP 100 selects an appropriate RTT Delay Bound based on the index information included in the UL DATA and sets the RTT Expiration Time.

[0106] Figure 17 shows an example of the configuration of a UL DATA frame in the third embodiment. Here, a new RTT Delay Bound Index field is defined within the HT Control field. The RTT Delay Bound Index field contains index information indicating which of the multiple RTT Delay Bounds included in the New QoS Characteristics Element in Figure 16 should be selected. For example, "00" is used to select the first one, "01" to select the second one, and "10" to select the third one. The Frame Body field stores the UL DATA body (e.g., UL MSDU#1).

[0107] STA200 determines which RTT Delay Bound to use on AP100 based on the difference between the UL traffic generation timing (the generation timing of UL MSDU#1) and the transmission time of the UL DATA frame (for example, the transmission start time). The index information of the value indicating the determined RTT Delay Bound is set in the RTT Delay Bound Index field. This instructs AP100 to use one of the multiple RTT Delay Bounds.

[0108] For example, in Figure 15, when transmitting UL DATA in the first step S102, i.e., transmitting a wireless data signal containing UL DATA (the first wireless data signal), the value of the RTT Delay Bound Index field is set to "00". When transmitting UL DATA again in the second step S102 after a transmission failure, i.e., transmitting a wireless data signal containing UL DATA (the third wireless data signal), the value of the RTT Delay Bound Index field is set to "01".

[0109] Figure 18 shows a flowchart of an example of the operation of AP100 in the third embodiment. Step S203 in the flowchart of Figure 9 according to the first embodiment has been changed to step S220. The other steps are the same as in Figure 9, so a detailed explanation is omitted.

[0110] In step S220, AP100 selects one of several RTT Delay Bounds to use based on the value of the RTT Delay Bound Index field in the HT Control field of UL DATA, and sets the RTT Expiration Time.

[0111] As described above, according to this embodiment, STA 200 instructs AP 100 to use from among multiple RTT Delay Bounds, and AP 100 selects the RTT Delay Bound instructed by STA 200. This allows AP 100 to set a transmission deadline that satisfies the application's requirements, regardless of when STA 200 transmits UL DATA.

[0112] (Effects) The first to third embodiments enable AP 100 to perform priority transmission control that takes into account the acquisition deadline for DL ​​traffic required by the application, even in wireless communication transmissions where DL traffic is generated in the Rendering Server 300, starting from UL traffic (e.g., UL MSDU#1) generated in the STA, such as in VR / AR / XR applications. Conventionally, Expiration Time was set for each type of traffic, either UL or DL, based on the packet reception timing (the timing of packet input to the MAC layer). In this embodiment, AP 100 applies an Expiration Time based on the transmission timing of UL DATA to DL traffic. This makes it possible to perform appropriate priority control to the STA 200 regardless of fluctuations in the processing time of the upper layers (application processing time and backhaul transmission time of the Rendering Server 300).

[0113] <Example of Computer Configuration> The series of processes described above can be executed by hardware or by software. When the series of processes are executed by software, the programs that make up the software are installed from a program storage medium onto a computer that is built into dedicated hardware, or a general-purpose personal computer.

[0114] Figure 19 is a block diagram showing an example of the hardware configuration of a computer that executes the series of processes described above by a program.

[0115] The CPU (Central Processing Unit) 801, ROM (Read Only Memory) 802, and RAM (Random Access Memory) 803 are interconnected by a bus 804.

[0116] An input / output interface 805 is further connected to the bus 804. An input unit 806, consisting of a keyboard, mouse, etc., and an output unit 807, consisting of a display, speaker, etc., are connected to the input / output interface 805. The output unit 807 may output or display information related to this technology, for example, information indicating the expiration time set based on DL Delay Bound. The input unit 806 may input information related to this technology, for example, information related to one or more DL Delay Bounds, and confirmation or response to the information output or displayed to the output unit 807. In addition, a storage unit 808, consisting of a hard disk or non-volatile memory, a communication unit 809, consisting of a network interface, etc., and a drive 810 that drives removable media 811 are connected to the input / output interface 805.

[0117] In a computer configured as described above, the CPU 801 performs the series of processes described above by loading a program stored in the memory unit 808 into the RAM 803 via the input / output interface 805 and the bus 804 and executing it. For example, the CPU 801 may execute a processing program corresponding to the processes shown in Figures 5, 9, 10, 12, 13, 15, and 18 of this technology.

[0118] The program executed by the CPU 801 is recorded on removable media 811, for example, or provided via a wired or wireless transmission medium such as a local area network, the internet, or digital broadcasting, and installed in the storage unit 808.

[0119] The programs executed by the computer may be programs that are processed chronologically in the order described herein, or they may be programs that are processed in parallel or at necessary times, such as when a call is made.

[0120] <Application Examples> This technology can be applied to a variety of products. For example, the wireless communication devices 100 and 200 may be implemented as mobile terminals such as smartphones, tablet PCs (Personal Computers), notebook PCs, portable game terminals, or digital cameras; fixed terminals such as television receivers, projectors, printers, digital scanners, or network storage devices; or in-vehicle terminals such as car navigation systems and drive recorders. Furthermore, the wireless communication devices 100 and 200 may be implemented as M2M (Machine To Machine Communication) terminals or IoT (Internet of Things) terminals such as smart meters, vending machines, remote monitoring devices, or POS (Point of Sale) terminals. In addition, the wireless communication devices 100 and 200 may be wireless communication modules (for example, integrated circuit modules consisting of a single die) mounted on these terminals.

[0121] On the other hand, for example, the wireless communication devices 100 and 200 may be implemented as wireless LAN APs (wireless base stations) with or without router functionality. Alternatively, the wireless communication devices 100 and 200 may be implemented as mobile wireless LAN routers. Furthermore, the wireless communication devices 100 and 200 may be implemented as cellular communication base stations and femtocells. In addition, the wireless communication devices 100 and 200 may be wireless communication modules (for example, integrated circuit modules consisting of a single die) mounted on these devices.

[0122] <Example of Smartphone Configuration> Figure 20 is a block diagram showing a schematic configuration example of a smartphone 900 to which this technology is applied. Although Figure 20 is shown as an example of the configuration of a smartphone 900, it is not limited to this and may also be an example of the configuration of various devices and functions described above.

[0123] The smartphone 900 includes a processor 901, memory 902, storage 903, external connection interface 904, camera 906, sensor 907, microphone 908, input device 909, and display device 910. The smartphone 900 also includes a speaker 911, wireless communication interface 913, antenna switch 914, antenna 915, bus 917, battery 918, and auxiliary controller 919. The smartphone 900 may include all of the above features, or only some of them.

[0124] The processor 901 may be, for example, a CPU or a SoC (System on Chip), and controls the functions of the application layer and other layers of the smartphone 900.

[0125] The memory 902 includes RAM and ROM and stores programs and data executed by the processor 901.

[0126] The storage 903 includes a storage medium such as semiconductor memory or a hard disk.

[0127] The external connection interface 904 is an interface for connecting external devices such as memory cards or USB (Universal Serial Bus) devices to the smartphone 900.

[0128] The camera 906 has an image sensor, such as a CCD (Charge Coupled Device) or CMOS (Complementary Metal Oxide Semiconductor), and generates an image.

[0129] The sensor 907 includes, for example, a group of sensors such as a positioning sensor, a gyroscope, a geomagnetic sensor, and an accelerometer.

[0130] Microphone 908 converts the audio input to smartphone 900 into an audio signal.

[0131] The input device 909 includes, for example, a touch sensor that detects touches on the screen of the display device 910, a keypad, a keyboard, a button, or a switch, and accepts operations or information input from the user.

[0132] The display device 910 has a screen such as a liquid crystal display (LCD), an organic light-emitting diode (OLED) display, or a quantum dot (QD) display, and displays the output image of the smartphone 900.

[0133] Speaker 911 converts the audio signal output from smartphone 900 into audio.

[0134] The wireless communication interface 913 supports one or more wireless LAN standards such as IEEE 802.11a, 11b, 11g, 11ac, 11ad, 11ax, 11ay, 11be, and 11bn, and performs wireless communication.

[0135] In infrastructure mode, the wireless communication interface 913 communicates with other devices via the wireless LAN access point (AP). In ad-hoc mode or direct communication modes such as Wi-Fi Direct, the wireless communication interface 913 communicates directly with other devices.

[0136] In Wi-Fi Direct, unlike ad-hoc mode, one of the two devices acts as the access point (AP), but communication takes place directly between those devices.

[0137] The wireless communication interface 913 typically includes a baseband processor, an RF (Radio Frequency) circuit, and a power amplifier. The wireless communication interface 913 may also be a single-chip module integrating a memory for storing a communication control program, a processor for executing the program, and associated circuits.

[0138] The wireless communication interface 913 may support other types of wireless communication methods in addition to the wireless LAN method, such as short-range wireless communication methods like Bluetooth, proximity wireless communication methods like NFC, or 3GPP cellular communication methods such as 2G, 3G, 4G, 5G, and 6G. The wireless communication interface 913 may be a single-chip module that supports multiple wireless communication methods, or it may be a combination of modules that support some of the wireless communication methods.

[0139] The antenna switch 914 switches the destination of the antenna 915 among multiple circuits included in the wireless communication interface 913 (for example, circuits for different wireless communication methods, or transmitting and receiving circuits).

[0140] The antenna 915 has one or more antenna elements (for example, multiple antenna elements that make up a MIMO (Multiple Input Multiple Output) antenna, or multiple antenna elements that make up an array antenna) and is used for transmitting and receiving radio signals via the wireless communication interface 913.

[0141] Note that the smartphone 900 is not limited to the example shown in Figure 20, and may be equipped with multiple antennas (for example, an antenna for wireless LAN, an antenna for proximity wireless communication, and an antenna for cellular communication). In that case, the antenna switch 914 may be omitted from the configuration of the smartphone 900.

[0142] The bus 917 connects the processor 901, memory 902, storage 903, external connection interface 904, camera 906, sensor 907, microphone 908, input device 909, display device 910, speaker 911, wireless communication interface 913, and auxiliary controller 919 to each other.

[0143] The battery 918 supplies power to each block of the smartphone 900 shown in Figure 20 via power supply lines partially shown by dashed lines in the figure. The auxiliary controller 919 operates the minimum necessary functions of the smartphone 900, for example, in sleep mode. The battery 918 may also be charged via the external connection interface 904. The battery 918 may also have a function that allows reading of information regarding the remaining power, cumulative power supply time, or cumulative power supply amount, and the processor 901, wireless communication interface 913, or auxiliary controller 919 may control any of the functions of the above embodiments based on the information read from the battery 918.

[0144] In the smartphone 900 shown in Figure 20, for example, the communication control unit 111 or control unit 130 in Figure 2, or the communication control unit 211 or control unit 230 in Figure 3, may be implemented in the wireless communication interface 913. For example, processing programs corresponding to the processes shown in Figures 5, 9, 10, 12, 13, 15, and 18 may be executed in the wireless communication interface 913. Furthermore, at least some of these functions may be implemented in the processor 901 or auxiliary controller 919.

[0145] The smartphone 900 may also operate as a wireless AP (software AP) by having the processor 901 execute AP functions at the application level. Alternatively, the wireless communication interface 913 may have wireless AP functionality. Furthermore, the processor 901 or the wireless communication interface 913 may have tethering functionality using both wireless LAN and cellular communication methods.

[0146] Furthermore, the smartphone 900 may be equipped with a biometric authentication unit (fingerprint authentication, palm print authentication, voice authentication, vascular authentication, facial authentication, iris authentication, retinal authentication). In this case, the wireless communication interface 913 on which the communication control unit 111 or control unit 130 in Figure 2 or the communication control unit 211 or control unit 230 in Figure 3 is implemented is configured to receive power from the same battery 918 as at least one of the display device 910, speaker 911, and biometric authentication unit.

[0147] Furthermore, in the smartphone 900, information is displayed from at least one of the display device 910 and the speaker 911 based on communication with an external device via the wireless communication interface 913. In this case, the information displayed may include information related to this technology, such as information indicating the expiration time set based on DL Delay Bound, which may be output from at least one of the display device 910 and the speaker 911. The input device 909 may also be configured to input confirmation or a response to the information output from at least one of the display device 910 and the speaker 911.

[0148] <Example of In-Vehicle Device Configuration> Figure 21 is a block diagram showing an example of the schematic configuration of an in-vehicle device 920 to which this technology is applied. Although Figure 21 is described as an example of the configuration of an in-vehicle device 920, it is not limited to this, and may also be an example of the configuration of various devices and functions described above.

[0149] The in-vehicle device 920 is configured to include a processor 921, memory 922, GNSS (Global Navigation Satellite System) module 924, sensor 925, data interface 926, content player 927, and storage medium interface 928. The in-vehicle device 920 is also configured to include an input device 929, display device 930, speaker 931, wireless communication interface 933, antenna switch 934, antenna 935, and battery 938. The in-vehicle device 920 may include all of the above, or it may include some of them.

[0150] The processor 921 may be, for example, a CPU or a SoC, and controls the navigation and other functions of the in-vehicle device 920. The processor 921 can also control the vehicle's drive system, such as the brakes, accelerator, or steering, based on information obtained through communication based on this technology.

[0151] The memory 922 includes RAM and ROM and stores programs and data executed by the processor 921.

[0152] The GNSS module 924 uses GNSS signals received from GNSS satellites to measure the position (e.g., latitude, longitude, and altitude) of the on-board device 920.

[0153] The sensor 925 includes, for example, a group of sensors such as a gyro sensor, a geomagnetic sensor, a millimeter-wave radar, a camera (image sensor such as a CCD or CMOS), and a barometric pressure sensor.

[0154] The data interface 926 is connected to the in-vehicle network 941 via, for example, terminals (not shown), and acquires data generated on the vehicle side, such as in-vehicle data.

[0155] The content player 927 plays content stored on a storage medium (for example, a CD or DVD) inserted into the storage medium interface 928, or content received via the wireless communication interface 933.

[0156] The input device 929 includes, for example, a touch sensor, button, or switch that detects touches on the screen of the display device 930, and accepts operations or information input from the user. For example, the input device 929 may also receive confirmation or a response to information output from at least one of the display device 930 and the speaker 931.

[0157] The display device 930 has a screen such as an LCD, OLED display, or QD display, and displays navigation functions or images of content being played, as well as information related to this technology, such as information indicating the expiration time set based on DL Delay Bound.

[0158] The speaker 931 outputs navigation functions, audio of the content being played, or information related to this technology, such as information indicating the expiration time set based on DL Delay Bound.

[0159] Note that in the in-vehicle device 920, the navigation function and the functions provided by the content player 927 are optional. The navigation function and the content player 927 may be omitted from the configuration of the in-vehicle device 920.

[0160] The wireless communication interface 933 supports one or more wireless LAN standards such as IEEE 802.11a, 11b, 11g, 11n, 11ac, 11ad, 11ax, 11ay, 11be, and 11bn, and performs wireless communication.

[0161] In infrastructure mode, the wireless communication interface 933 communicates with other devices via the wireless LAN access point (AP). In ad-hoc mode or direct communication modes such as Wi-Fi Direct, the wireless communication interface 933 communicates directly with other devices.

[0162] In Wi-Fi Direct, unlike ad-hoc mode, one of the two devices acts as the access point (AP), but communication takes place directly between those devices.

[0163] The wireless communication interface 933 typically includes a baseband processor, RF circuitry, and power amplifier. The wireless communication interface 933 may also be a single-chip module integrating a memory for storing a communication control program, a processor for executing the program, or related circuitry.

[0164] The wireless communication interface 933 may support other types of wireless communication methods in addition to the wireless LAN method, such as short-range wireless communication methods like Bluetooth, proximity wireless communication methods like NFC, or 3GPP cellular communication methods such as 2G, 3G, 4G, 5G, and 6G. The wireless communication interface 933 may be a single-chip module that supports multiple wireless communication methods, or it may be a combination of modules that support some of the wireless communication methods.

[0165] The antenna switch 934 switches the destination of the antenna 935 among multiple circuits included in the wireless communication interface 933 (for example, circuits for different wireless communication methods, or transmitting and receiving circuits).

[0166] The antenna 935 has one or more antenna elements (for example, multiple antenna elements that make up a MIMO (Multiple Input Multiple Output) antenna, or multiple antenna elements that make up an array antenna) and is used for transmitting and receiving radio signals via the wireless communication interface 933.

[0167] Note that the in-vehicle device 920 is not limited to the example shown in Figure 21, and may include multiple antennas (for example, an antenna for wireless LAN, an antenna for proximity wireless communication, and an antenna for cellular communication). In that case, the antenna switch 934 may be omitted from the configuration of the in-vehicle device 920.

[0168] Battery 938 supplies power to each block of the on-board device 920 shown in Figure 21 via power supply lines partially shown by dashed lines in the figure. Battery 938 may also store power supplied from the vehicle. Alternatively, the on-board device 920 may not have a battery and may utilize power supplied from the vehicle via a voltage regulator or capacitor.

[0169] In the in-vehicle device 920 shown in Figure 21, for example, the communication control unit 111 or control unit 130 in Figure 2, or the communication control unit 211 or control unit 230 in Figure 3, may be implemented in the wireless communication interface 933. For example, processing programs corresponding to the processes shown in Figures 5, 9, 10, 12, 13, 15, and 18 may be executed in the wireless communication interface 933. Furthermore, at least some of these functions may be implemented in the processor 921.

[0170] Furthermore, the wireless communication interface 933 may operate as the communication control unit 111 or control unit 130 in Figure 2 or the communication control unit 211 or control unit 230 in Figure 3, providing wireless connectivity to a terminal held by a user in the vehicle. For example, the wireless communication interface 933 may connect the in-vehicle device 920 to other peripheral devices, and the in-vehicle device 920 may utilize CarPlay® or Android Auto®. The wireless communication interface 933 may also connect the in-vehicle device 920 to other peripheral devices using a short-range wireless communication method, infrastructure mode, or a Wi-Fi Direct wireless LAN method.

[0171] The in-vehicle device 920 may also operate as a wireless AP (software AP) by having the processor 921 execute AP functions at the application level. Alternatively, the wireless communication interface 933 may have wireless AP functionality. Furthermore, the processor 921 or the wireless communication interface 933 may have tethering functionality using both wireless LAN and cellular communication methods.

[0172] Furthermore, this technology may be implemented as an in-vehicle system (or vehicle) 940 including one or more blocks of the above-described in-vehicle device 920, an in-vehicle network 941, and a vehicle-side module 942. The vehicle-side module 942 may generate vehicle-side data such as vehicle speed information, engine speed information, vehicle-side battery information, or fault information, and output the generated data to the in-vehicle network 941. The processor 921 or wireless communication interface 933 may control any of the functions of the above-described embodiments based on the information acquired via the in-vehicle network 941.

[0173] <Example of Wireless AP Configuration> Figure 22 is a block diagram showing an example of a schematic configuration of a wireless AP 950 to which this technology is applied. Although Figure 22 is described as an example of the configuration of a wireless AP 950, it is not limited to this, and may also be an example of the configuration of various devices and functions described above.

[0174] The wireless AP 950 includes a controller 951, memory 952, input device 954, display device 955, network interface 957, wireless communication interface 963, antenna switch 964, and antenna 965. The wireless AP 950 may include all of the above, or some of them.

[0175] The controller 951 may be, for example, a CPU or a DSP (Digital Signal Processor), and it operates various functions of the wireless AP 950 at the IP (Internet Protocol) layer and higher layers (e.g., access restriction, routing, encryption, firewall, and log management).

[0176] Memory 952 includes RAM and ROM and stores programs executed by the controller 951, as well as various control information (e.g., terminal list, routing table, encryption key, security settings, and logs).

[0177] The input device 954 includes, for example, buttons and switches, and accepts operations from the user. For example, the input device 954 may input confirmation or response to information output from the display device 955.

[0178] The display device 955 includes an LED lamp or the like and displays the operating status of the wireless AP 950. The display device 955 may also display information related to this technology, such as information indicating the expiration time set based on DL Delay Bound.

[0179] The network interface 957 is a wired communication interface for the wireless AP 950 to connect to the wired communication network 958. The network interface 957 may have multiple connection terminals. The network interface 957 may input and output wireless signals input and output by the wireless communication interface 963 as wired signals, or it may operate in parallel with or independently of the wireless communication interface 963's input and output of wireless signals to input and output wired signals. The wired communication network 958 may be a LAN such as Ethernet (registered trademark), or a WAN (Wide Area Network).

[0180] The wireless communication interface 963 supports one or more wireless LAN standards such as IEEE 802.11a, 11b, 11g, 11n, 11ac, 11ad, 11ax, 11ay, 11be, and 11bn, and provides wireless connectivity as an AP to nearby terminals. When the wireless AP 950 is mounted on a cellular communication base station and femtocell, the wireless communication interface 963 may support other types of wireless communication methods in addition to wireless LAN, such as 3GPP cellular communication methods like 2G, 3G, 4G, 5G, and 6G. The wireless communication interface 963 may be a single-chip module supporting multiple wireless communication methods, or a combination of modules supporting some of the wireless communication methods.

[0181] The wireless communication interface 963 typically includes a baseband processor, RF circuitry, and power amplifiers, among others.

[0182] The wireless communication interface 963 may be a single-chip module integrating a memory for storing a communication control program, a processor for executing the program, or related circuits.

[0183] The antenna switch 964 switches the destination of the antenna 965 among multiple circuits included in the wireless communication interface 963 (for example, circuits for different wireless communication methods, or transmitting and receiving circuits).

[0184] Antenna 965 has one or more antenna elements (for example, multiple antenna elements that make up a MIMO (Multiple Input Multiple Output) antenna, or multiple antenna elements that make up an array antenna) and is used for transmitting and receiving radio signals via wireless communication interface 963.

[0185] In the wireless AP 950 shown in Figure 22, for example, the communication control unit 111 or control unit 130 in Figure 2, or the communication control unit 211 or control unit 230 in Figure 3, may be implemented in the wireless communication interface 963. For example, the processing programs corresponding to Figures 4, 13, and 14 may be executed in the wireless communication interface 963. Furthermore, at least some of these functions may be implemented in the controller 951.

[0186] The above-described embodiments are merely examples of how to realize this technology, and there is a corresponding relationship between the matters in the embodiments and the inventive features in the claims. Similarly, there is a corresponding relationship between the inventive features in the claims and the matters in the embodiments of this technology that bear the same name. However, this technology is not limited to the embodiments and can be realized by making various modifications to the embodiments without departing from the gist of the technology.

[0187] Furthermore, the processing procedure described in the above-described embodiment may be considered as a method comprising these steps, or as a program or recording medium that stores such a program for causing the computer to execute these steps.

[0188] For example, CDs (Compact Discs), MDs (MiniDiscs), DVDs (Digital Versatile Discs), memory cards, and Blu-ray Discs (Blu-ray® Discs) can be used as recording media.

[0189] In this specification, a system refers to a collection of multiple components (devices, modules (parts), etc.), regardless of whether all components are located in the same enclosure. Therefore, multiple devices housed in separate enclosures and connected via a network, and a single device containing multiple modules within a single enclosure, are both considered systems.

[0190] Furthermore, the effects described herein are merely illustrative and not limiting, and other effects may also occur.

[0191] The embodiments of this technology are not limited to those described above, and various modifications are possible without departing from the spirit of this technology.

[0192] For example, this technology can be configured as cloud computing, where a single function is shared and processed collaboratively by multiple devices via a network.

[0193] Furthermore, each step described in the flowchart above can be performed by a single device, or it can be divided and performed by multiple devices.

[0194] Furthermore, if a single step includes multiple processes, those processes can be executed by a single device or shared among multiple devices.

[0195] The embodiments described above are merely examples of how to implement this disclosure, and it is possible to implement this disclosure in various other forms. For example, various modifications, substitutions, omissions, or combinations thereof are possible without departing from the gist of this disclosure. Such modified, substituted, or omission forms are also included within the scope of the invention described in the claims and its equivalents, as are included within the scope of this disclosure.

[0196] Furthermore, the effects described herein are merely illustrative, and other effects may also occur.

[0197] Furthermore, this disclosure may also take the following configurations: [Item 1] A communication control device comprising a control unit that controls a wireless communication unit to transmit a first wireless data signal including a first data, the control unit controls the wireless communication unit to receive a second wireless data signal including a second data generated based on the first data, and controls the wireless communication unit to transmit a signal including first information indicating a deadline for the transmission process of the second wireless data signal, which is determined based on the timing of the transmission or reception of the first wireless data signal. [Item 2] The communication control device according to Item 1, wherein the signal further includes identification information relating to the traffic flow of the first data. [Item 3] The communication control device according to Item 1 or 2, wherein the first information includes information on the length of time that is permitted from the timing of the transmission or reception until the transmission process is performed. [Item 4] The communication control device according to any one of Items 1 to 3, wherein the control unit controls the wireless communication unit to transmit the first wireless data signal and the signal to a wireless communication device, and controls the wireless communication unit to receive the second wireless data signal from the wireless communication device, and the signal further includes second information that is identified based on the timing of acquisition of the second data in the wireless communication device and indicates a deadline for the transmission process of the second wireless data signal. [Item 5] The communication control device according to Item 4, wherein the signal further includes information that specifies which of the first information and the second information to use. [Item 6] The communication control device according to any one of Items 1 to 5, wherein the signal includes a plurality of the first information.[Item 7] The communication control device according to any one of Item 6, wherein the first wireless data signal includes information specifying one of the plurality of first pieces of information to be used, the control unit controls the wireless communication unit to transmit a third wireless data signal for retransmitting the first data when it is determined that the transmission of the first wireless data signal has failed, and the third wireless data signal includes information specifying one of the plurality of first pieces of information to be used, which is different from the first piece of information specified in the first wireless data signal transmitted before the third wireless data signal. [Item 8] The communication control device according to any one of Item 1 to 7, wherein the control unit transmits the first wireless data signal multiple times, and the signal includes information determining which of the multiple transmissions or receptions of the first wireless data signal the deadline indicated by the first piece of information is specified according to the timing of transmission or reception. [Item 9] The communication control device according to Item 3, wherein the deadline is the time of transmission or reception of the first wireless data signal plus the time indicated by the first piece of information. [Item 10] The communication control device according to Item 9, wherein the control unit controls the transmission of the first wireless data signal in response to the occurrence of a request to acquire the second data, and the length of time indicated by the first information is shorter than the length of time from the time the acquisition request occurs to the deadline for acquiring the second data. [Item 11] The communication control device according to Item 10, wherein the control unit controls the processing of the MAC layer and detects the acquisition request that occurs from an application in a layer higher than the MAC layer. [Item 12] The communication control device according to any one of Items 1 to 11, wherein the first data includes at least one of the position and orientation of the device on which the communication control device is provided, and the second data is data generated by the server according to at least one of the position and orientation of the device. [Item 13] The communication control device according to Item 12, wherein the device is a head-mounted display, and the data generated by the server is video data displayed on the head-mounted display.[Item 14] A communication control method comprising: transmitting a first wireless data signal containing first data; receiving a second wireless data signal containing second data generated based on the first data; and transmitting a signal containing first information that is specified based on the timing of the transmission or reception of the first wireless data signal and indicates a deadline for the transmission process of the second wireless data signal. [Item 15] A communication control device comprising a control unit that controls a wireless communication unit to receive a first wireless data signal containing first data; the control unit acquires second data generated based on the first data and controls the wireless communication unit to transmit a second wireless data signal containing the second data; the wireless communication unit receives a signal containing first information that is specified based on the timing of the transmission or reception of the first wireless data signal and indicates a deadline for the transmission process of the second wireless data signal; and controls the wireless communication unit to perform the transmission process of the second wireless data signal by the deadline indicated by the first information. [Item 16] A communication control method comprising: receiving a first wireless data signal containing first data; acquiring second data generated based on the first data; transmitting a second wireless data signal containing the second data; receiving a signal containing first information that is identified based on the timing of the transmission or reception of the first wireless data signal and indicates a deadline for the transmission process of the second wireless data signal; and controlling the system to perform the transmission process of the second wireless data signal by the deadline indicated by the first information. [Item 17] The communication control device according to Item 15, wherein the first information includes time information relating to the length of time, and the control unit acquires the deadline by adding the time to the time of transmission or reception of the first wireless data signal. [Item 18] The communication control device according to Item 15 or 17, wherein the signal further includes identification information relating to traffic flow, and the control unit controls the system to perform the transmission process of the second wireless data signal by the deadline indicated by the first information when the traffic flow of the first data contained in the first wireless data signal matches the traffic flow indicated by the identification information.[Item 19] The communication control device according to item 15, 17, or 18, wherein the signal further includes second information indicating a deadline for the transmission process of the second wireless data signal, which is identified based on the timing of the acquisition of the second data in the wireless communication unit, and information specifying which of the first information and the second information to use, and the control unit selects one of the deadlines indicated by the first information and the deadline indicated by the second information based on the information specifying which of the first information and the second information to use, and controls the transmission process of the second wireless data signal to be performed by the selected deadline. [Item 20] The communication control device according to any one of items 15, 17 to 19, wherein the signal includes a plurality of first information, the first wireless data signal includes information specifying which of the plurality of first information to use, and the control unit determines the deadline based on the first information specified by the first wireless data signal. [Item 21] The communication control device according to any one of items 15, 17 to 20, wherein the control unit controls the wireless communication unit to receive the first wireless data signal multiple times, the signal includes information that determines which of the multiple transmissions or receptions of the first wireless data signal the deadline indicated by the first information is specified according to the timing of transmission or reception of the first wireless data signal, and the control unit determines the deadline according to the timing of transmission or reception of the first wireless data signal specified according to the information, and controls the unit to perform the transmission process of the second wireless data signal by the determined deadline.

[0198] 100 Wireless communication device (AP) 110 Wireless communication unit 111 Communication control unit 112 Communication memory unit 121 Data processing unit 122 Signal processing unit 123 Wireless interface unit 124 Amplifier unit 130 Control unit 140 Memory unit 150 Antenna 200 Wireless communication device (STA) 210 Wireless communication unit 211 Communication control unit 212 Communication memory unit 221 Data processing unit 222 Signal processing unit 223 Wireless interface unit 224 Amplifier unit 230 Control unit 240 Memory unit 250 Antenna 804 Bus 805 Input / Output interface 806 Input unit 807 Output unit 808 Memory unit 809 Communication unit 810 Drive 811 Removable media 900 Smartphone 901 Processor 902 Memory 903 Storage 904 External connection interface 906 Camera 907 Sensor 908 Microphone 909 Input device 910 Display device 911 Speaker 913 Wireless communication interface 914 Antenna switch 915 Antenna 917 Bus 918 Battery 919 Auxiliary controller 920 Onboard equipment 921 Processor 922 Memory 924 GNSS module 925 Sensor 926 Data interface 927 Content player 928 Storage medium interface 929 Input device 930 Display device 931 Speaker 933 Wireless communication interface 934 Antenna switch 935 Antenna 938 Battery940 In-vehicle system (or vehicle) 941 In-vehicle network 942 Vehicle-side module 951 Controller 952 Memory 954 Input device 955 Display device 957 Network interface 958 Wired communication network 963 Wireless communication interface 964 Antenna switch 965 Antenna

Claims

1. A communication control device comprising a control unit that controls a wireless communication unit to transmit a first wireless data signal containing first data, the control unit controls the wireless communication unit to receive a second wireless data signal containing second data generated based on the first data, and controls the wireless communication unit to transmit a signal containing first information indicating a deadline for the transmission process of the second wireless data signal, which is determined based on the timing of the transmission or reception of the first wireless data signal.

2. The communication control device according to claim 1, wherein the signal further includes identification information relating to the traffic flow of the first data.

3. The communication control device according to claim 1, wherein the first information includes information on the length of time that is permitted from the timing of transmission or reception until the transmission process is performed.

4. The communication control device according to claim 1, wherein the control unit controls the wireless communication unit to transmit the first wireless data signal and the signal to a wireless communication device, and controls the wireless communication unit to receive the second wireless data signal from the wireless communication device, the signal further includes second information indicating a deadline for the transmission process of the second wireless data signal, which is identified based on the timing of the acquisition of the second data in the wireless communication device.

5. The communication control device according to claim 4, wherein the signal further includes information specifying which of the first information and the second information to use.

6. The communication control device according to claim 1, wherein the signal includes a plurality of the first pieces of information.

7. The communication control device according to claim 6, wherein the first wireless data signal includes information specifying one of the plurality of first pieces of information to be used, the control unit controls the wireless communication unit to transmit a third wireless data signal for retransmitting the first data when it determines that the transmission of the first wireless data signal has failed, and the third wireless data signal includes information specifying one of the plurality of first pieces of information to be used, which is different from the first piece of information specified in the first wireless data signal transmitted before the third wireless data signal.

8. The communication control device according to claim 1, wherein the control unit repeatedly transmits the first wireless data signal multiple times during a predetermined period, and the signal includes information that determines which of the multiple transmissions or receptions of the first wireless data signal the deadline indicated by the first information is identified according to the timing of transmission or reception.

9. The communication control device according to claim 3, wherein the deadline is the time obtained by adding the time indicated by the first information to the time of transmission or reception of the first wireless data signal.

10. The communication control device according to claim 9, wherein the control unit controls the transmission of the first wireless data signal in response to the occurrence of the second data acquisition request, and the length of time indicated by the first information is shorter than the length of time from the time the acquisition request occurs to the deadline for acquiring the second data.

11. The communication control device according to claim 10, wherein the control unit controls the processing of the MAC layer and detects the acquisition request originating from an application layer higher than the MAC layer.

12. The communication control device according to claim 1, wherein the first data includes at least one of the position and orientation of the device on which the communication control device is provided, and the second data is data generated by the server according to at least one of the position and orientation of the device.

13. The communication control device according to claim 12, wherein the device is a head-mounted display, and the data generated by the server is video data displayed on the head-mounted display.

14. A communication control method comprising: transmitting a first wireless data signal containing first data; receiving a second wireless data signal containing second data generated based on the first data; and transmitting a signal containing first information, which is determined based on the timing of the transmission or reception of the first wireless data signal and indicates a deadline for the transmission process of the second wireless data signal.

15. A communication control device comprising: a control unit that controls a wireless communication unit to receive a first wireless data signal including first data; the control unit acquires second data generated based on the first data and controls the wireless communication unit to transmit a second wireless data signal including the second data; the wireless communication unit receives a signal containing first information, which is determined based on the timing of the transmission or reception of the first wireless data signal and indicates a deadline for the transmission process of the second wireless data signal; and controls the wireless communication unit to perform the transmission process of the second wireless data signal by the deadline indicated by the first information.

16. A communication control method comprising: receiving a first wireless data signal containing first data; acquiring second data generated based on the first data; transmitting a second wireless data signal containing the second data; receiving a signal containing first information, which is identified based on the timing of the transmission or reception of the first wireless data signal and indicates a deadline for the transmission process of the second wireless data signal; and controlling the system to perform the transmission process of the second wireless data signal by the deadline indicated by the first information.

17. The communication control device according to claim 15, wherein the first information includes time information relating to the length of time, and the control unit obtains the deadline by adding the time to the time of transmission or reception of the first wireless data signal.

18. The communication control device according to claim 15, wherein the signal further includes identification information relating to a traffic flow, and the control unit controls the transmission of the second radio data signal by the deadline indicated by the first information when the traffic flow of the first data included in the first radio data signal matches the traffic flow indicated by the identification information.

19. The communication control device according to claim 15, wherein the signal is identified based on the timing of acquisition of the second data in the wireless communication unit and further includes second information indicating a deadline for the transmission process of the second wireless data signal, and information specifying which of the first information and the second information to use, and the control unit selects one of the deadlines indicated by the first information and the deadline indicated by the second information based on the information specifying which of the first information and the second information to use, and controls the transmission process of the second wireless data signal to be performed by the selected deadline.

20. The communication control device according to claim 15, wherein the signal includes a plurality of the first pieces of information, the first wireless data signal includes information that specifies which of the plurality of the first pieces of information to use, and the control unit determines the deadline based on the first piece of information specified by the first wireless data signal.