WO2024074343A1 - Dispositifs et procédés de communication - Google Patents

Dispositifs et procédés de communication Download PDF

Info

Publication number
WO2024074343A1
WO2024074343A1 PCT/EP2023/076476 EP2023076476W WO2024074343A1 WO 2024074343 A1 WO2024074343 A1 WO 2024074343A1 EP 2023076476 W EP2023076476 W EP 2023076476W WO 2024074343 A1 WO2024074343 A1 WO 2024074343A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication device
communication
communication devices
retransmission
joint
Prior art date
Application number
PCT/EP2023/076476
Other languages
English (en)
Inventor
Ken Tanaka
Thomas Handte
Kosuke Aio
Daniel VERENZUELA
Original Assignee
Sony Group Corporation
Sony Europe B.V.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sony Group Corporation, Sony Europe B.V. filed Critical Sony Group Corporation
Publication of WO2024074343A1 publication Critical patent/WO2024074343A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022—Site diversity; Macro-diversity
    • H04B7/026—Co-operative diversity, e.g. using fixed or mobile stations as relays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H04L1/0003—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0097—Relays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/16—Multipoint routing

Definitions

  • the present disclosure relates to communication devices and methods, in particular to multi-access point (multi-AP) devices and methods for use in a multi-AP network.
  • multi-AP multi-access point
  • a multi-AP device is generally understood as a wireless Access Point (AP) that can transmit and/or receive signals in cooperation with (an)other AP(s). This cooperation includes joint processing, which means that several multi-AP devices transmit or receive signals at the same time to yield better performance leveraging spatial diversity. Multi-AP has particularly been considered for coverage extension and/or increasing robustness of wireless networks.
  • AP wireless Access Point
  • a wireless network making use of multi-AP may comprise a source node (also called “first multi-AP device” herein), one or more relay nodes (also called “second multi-AP device” herein) and one or more sink nodes (also called “third communication devices” or “non-AP STA” (station)).
  • the source node is a communication device which is the source of sent data
  • the relay node is a communication device which relays the data to (an)other communication device
  • the sink node is a communication device which is the destination of the data.
  • reception errors of data units transmitted from a source node to relay nodes may appear for different reasons, i.e., one or more data units may not be correctly received or decoded by one or more relay nodes. Retransmission of one or more data units may hence be needed.
  • a first communication device configured to operate as source node and communicate with one or more second communication devices that are configured to operate as relay nodes and communicate with one or more third communication devices
  • the first communication device comprising circuitry configured to: transmit one or more at least partly identical data units to two or more second communication devices that intend to perform coherent joint transmission to one or more third communication devices; receive reception status feedback from the two or more second communication devices indicating reception status of the transmitted one or more data units; and transmit a joint retransmission request to at least one of the two or more second communication devices if the received reception status feedback indicates at least one failed data unit that failed to be received or decoded by one or more second communication devices, said joint retransmission request indicating to the at least one of the two or more second communication devices which data unit to retransmit to which other second communication device.
  • a second communication device configured to operate as relay node and communicate with a first communication device configured to operate as source node, one or more other second communication devices configured to operate as relay nodes and/or one or more third communication devices configured to communicate with one or more second communication devices
  • the second communication device comprising circuitry configured to: perform coherent joint transmission with one or more other second communication devices; transmit reception status feedback to the first communication device indicating reception status of one or more data units received from the first communication device; receive a joint retransmission request from the first communication device indicating which at least one failed data unit that failed to be received or decoded by another second communication device to retransmit to which other second communication device; and retransmit the at least one failed data unit to the second communication device as indicated in the joint retransmission request.
  • another second communication device configured to operate as another relay node and communicate with a first communication device configured to operate as source node, one or more other second communication devices configured to operate as relay nodes and/or one or more third communication devices configured to communicate with one or more second communication devices
  • the second communication device comprising circuitry configured to: performing coherent joint transmission with one or more other second communication devices; transmitting reception status feedback to the first communication device indicating reception status of one or more data units received from the first communication device; and receiving a joint retransmission request from the first communication device indicating which at least one failed data unit that failed to be received or decoded by the second communication device to retransmit to by another second communication device.
  • a computer program comprising program means for causing a computer to carry out the steps of the method disclosed herein, when said computer program is carried out on a computer, as well as a non- transitory computer-readable recording medium that stores therein a computer program product, which, when executed by a processor, causes the method disclosed herein to be performed are provided.
  • One of the aspects of the disclosure is to make use of a retransmission scheme and information controlling the retransmission in a way that shortens the retransmission time needed for necessary retransmissions of two or more data units to one or more second communication devices so that coherent joint transmission of data units from the second communication devices to third communication devices can be performed afterwards.
  • Fig. 1 shows a schematic diagram of a multi-AP network in which the communication devices according to the present disclosure may be used.
  • Fig. 2 shows schematic diagrams illustrating different types of collaborative transmission, non-joint transmission and dynamic point selection.
  • Fig. 3 shows a flow chart of an embodiment of a first communication method according to the present disclosure.
  • Fig. 4 shows a flow chart of an embodiment of a second communication method according to the present disclosure.
  • Fig. 5 shows a flow chart of an embodiment of another second communication method according to the present disclosure.
  • Fig. 6 shows a diagram illustrating a more detailed embodiment of a communication scheme of the communication between the different communication devices according to the present disclosure.
  • Fig. 7 shows two embodiments of the configuration of an MPDll according to embodiments of the present disclosure.
  • Fig. 8 shows a diagram illustrating an embodiment of a communication scheme of the communication between the different communication devices according to a first case.
  • Fig. 9 shows an embodiment of a joint retransmission request frame according to the present disclosure.
  • Fig. 10 shows a diagram illustrating another embodiment of a communication scheme of the communication between the different communication devices according to the first case, in which more than two relay nodes are participating in the communication.
  • Fig. 11 shows a flow chart of an exemplary method of setting a Joint Retransmission REQ bitmap subfield according to the present disclosure.
  • Fig. 12 shows a diagram illustrating a more detailed embodiment of a communication scheme the communication between the different communication devices according to the present disclosure for a second case.
  • Fig. 13 shows a diagram illustrating an embodiment of a communication scheme of the communication between the different communication devices according to a second case.
  • Fig. 14 shows a flow chart of the operation of a relay node according to an embodiment of the present disclosure.
  • the terms as beforefronthaul AP” andußbackhaul STA“ refer to the entities that are generally included in a multi-AP device and communicate with each other when communicating between multi-AP devices.
  • a provokefronthaul AP” is either connected to a sansbackhaul STA“ or to a non-AP STA.
  • source node refers to a communication device (also called “first communication device” herein), which is the source of sent data.
  • relay node refers to a communication device (also called “second communication device” herein) which relays the data to (an)other communication device (another relay node or a sink node (also called “third communication device” herein)).
  • Each of source nodes and relay nodes have at least one fronthaul AP.
  • source nodes have fronthaul APs and Ethernet ports, and relay nodes have backhaul STAs and fronthaul APs.
  • FIG. 1 shows a schematic diagram of a multi-AP network in which the communication devices according to the present disclosure may be used.
  • multi-AP device 10 operates as source node and multi-AP devices 11 and 12 operate as relay nodes.
  • Multi-AP Device 10 has a multi-AP Entity and a fronthaul AP and can send signals made by fronthaul AP to non-AP STA 13 (operating as sink node; also called “third communication device herein), multi-AP device 11 and multi-AP device 12. If multi-AP device 10 is connected by Ethernet, it may have an Ethernet port instead of a backhaul STA. In the Fig. 1 , an Ethernet port entity is shown as “Logical Ethernet Port”. Each of the multi-AP devices 11 and 12 has a backhaul STA, a multi-AP entity, and a fronthaul AP. As shown in Fig. 1, each of them executes signal processing of received signals from multi-AP device 1. Multi-AP devices 11 and 12 can communicate with each other.
  • multi-AP device 11 sends control information to multi-AP device 12, the signal is sent from fronthaul AP of multi-AP device 11 to backhaul STA of multi-AP device 12, as shown by the dotted line in Fig. 1.
  • Each fronthaul AP configures its own BSS (Basic Service Set) to differentiate its link.
  • the fronthaul AP of multi-AP device 10 has a first BSS that includes the fronthaul AP of multi-AP device 10, the non-AP STA 13, the backhaul STA of multi-AP device 11, and the backhaul STA of multi-AP device 12.
  • the fronthaul APs of multi-AP devices 11 and 12 have different BSSs and communicate with other non-AP STAs 14 and 15.
  • Multi-AP has been considered for coverage extension and/or robust network.
  • Easy MeshTM is standardized to provide functions for multi-AP network as well as IEEE 802.11s.
  • a multi-AP network uses collection link metrics so that multi-AP devices can decide which route to choose to relay data to non-AP STAs.
  • BocLink Metric is referred to as link quality between communication devices independent of wireless or tethered link.
  • Easy MeshTM several formats are standardized to notify link metrics depending on a multi-AP device profile version, but fundamentally estimated data rate and/or measured data rate are chosen as link metrics.
  • collaborative transmission which is usually called joint processing in 3GPP (Third Generation Partnership Project)
  • CTP collaborative transmission
  • JT Joint Transmission
  • DPS Dynamic Point Selection
  • DPS Joint Transmission
  • DPS Dynamic Point Selection
  • CFO residual carrier frequency offset
  • Especially JT can be further divided into several types, as illustrated in Fig. 2 showing schematic diagrams illustrating different types of joint transmission. These types are 1) Coherent Joint Transmission (CJT; Fig. 2A), 2) Non-Coherent Joint Transmission (NCJT; Fig. 2B), and 3) Coordinated Beam Forming (CBF; Fig. 2C).
  • CJT Coherent Joint Transmission
  • NCJT Non-Coherent Joint Transmission
  • CBF Coordinated Beam Forming
  • multi-AP devices perform as if they were one big multi-AP device, and consequently yield most spatial streams and beam gains in JT.
  • each AP of the multi-AP device is required to have the same transmit data to be distributed via a backhaul CJT.
  • each multi-AP device does not need to share data to be sent, but performance might be worse than in CJT.
  • CBF each multi-AP device sends data to different non-AP STAs while they are likely to make null to unintended receivers. Since each multi-AP device makes null at the cost of spatial degree of freedom, performance might be even worse than CJT. If overhead such as data sharing is taken into account, the above performance relationship might be different, but performance might be different depending on the JT type.
  • Figs. 2D and 2E show diagrams of Non-Joint T ransmission, in particular for Single-User (SU) MIMO and Multi-User (MU) MIMO.
  • Fig. 2F shows a diagram of Dynamic Point Selection (DPS).
  • DPS Dynamic Point Selection
  • Fig. 3 shows a flow chart of an embodiment of a first communication method 100 according to the present disclosure.
  • the first communication method is generally performed by the first communication device (the multi-AP device 10) that is configured to operate as source node and communicate with one or more second communication devices (multi-AP devices 11 and 12) that are configured to operate as relay nodes and communicate with one or more third communication devices (multi-AP devices 14, 15).
  • a first step 101 of the first communication method one or more at least partly identical data units are transmitted to two or more second communication devices 11, 12 that intend I are planned to perform coherent joint transmission to one or more third communication devices 14, 15.
  • reception status feedback is received from the two or more second communication devices 11, 12 indicating reception status of the transmitted one or more data units.
  • a joint retransmission request is transmitted to at least one of the two or more second communication devices 11 , 12 if the received reception status feedback indicates at least one failed data unit that failed to be received or decoded by one or more second communication devices 11 , 12.
  • the joint retransmission request indicates to the at least one of the two or more second communication devices 11, 12 which data unit to retransmit to which other second communication device.
  • reception status feedback may be understood as acknowledgement (Ack) or block acknowledgement (BAck), but that it may also mean to include or represent Channel State Information (CSI) feedback and/or Modulation and Coding Scheme (MCS) feedback.
  • the step to "retransmit" a data unit refers to a retransmission of a data unit by a second communication device, wherein the communication device that previously transmitted the original data unit does not need to be the same communication device as the one that retransmits said data unit.
  • the "joint retransmission request” preferably indicates explicitly to which second communication device the data unit shall be retransmitted, but in other embodiments there may be no explicit indication in the joint retransmission request.
  • Fig. 4 shows a flow chart of an embodiment of a second communication method 200 according to the present disclosure.
  • the second communication method is generally performed by a second communication device 11 that is configured to operate as relay node and communicate with the first communication device 10, one or more other second communication devices 12 and/or one or more third communication devices 14, 15 configured to communicate with one or more second communication devices 11 , 12.
  • a first step 201 coherent joint transmission (CJT) with one or more other second communication devices 12 may be performed.
  • CJT coherent joint transmission
  • a second communication device 11 receives data units which are transmitted to two or more second communication devices 12 that intend / are planned to perform coherent joint transmission to one or more third communication devices 14, 15.
  • CJT may not be performed, because the second communication devices 11 and 12 make sure that they have identical data units, which are transmitted in CJT to each other.
  • reception status feedback is transmitted to the first communication device 10 indicating reception status of one or more data units received from the first communication device 10.
  • a joint retransmission request is received from the first communication device 10 indicating which at least one failed data unit that failed to be received or decoded by another second communication device 12 to retransmit to which other second communication device 12.
  • the at least one failed data unit is retransmitted to the second communication device 12 as indicated in the joint retransmission request.
  • FIG. 5 shows a flow chart of an embodiment of another second communication method 300 according to the present disclosure.
  • This other second communication method 300 is generally performed by another second communication device 12 than the second communication method 200.
  • This other second communication device 12 is configured to operate as relay node and communicate with the first communication device 10, one or more other second communication devices 11 and/or one or more third communication devices 14, 15 configured to communicate with one or more second communication devices 11, 12.
  • CJT may be performed with one or more other second communication devices 11.
  • a second communication device 12 receives data units which are transmitted to two or more second communication devices 11 that intend I are planned to perform coherent joint transmission to one or more third communication devices 14, 15.
  • reception status feedback is transmitted to the first communication device 10 indicating reception status of one or more data units received from the first communication device 11.
  • a joint retransmission request is received from the first communication device 10 indicating which at least one failed data unit that failed to be received or decoded by the second communication device 11 to retransmit by another second communication device 12, i.e., the second communication device 12 then obtains the failed data unit via retransmission.
  • MBF Multicast Beamforming
  • MBF packet error rate
  • a Multi-AP network as shown in Fig. 1 the two relay nodes 11, 12 can perform CJT and the source node 10 knows the channel qualities between the relay nodes 11, 12 and the sink nodes 14, 15.
  • the source node 10 sends the same data to both of the relay nodes 11, 12 so that the relay nodes 11, 12 can perform CJT afterwards.
  • the source node 10 can send the data to both relay nodes 11, 12 in MBF leveraging on the knowledge of channel qualities, but packet error rates at relay nodes are different in most cases. This is because it is hard to realize the same SNR of all intended receivers at any time, which means different link qualities among receivers, and thus common MCS cannot be adapted to all link qualities.
  • the source node 10 gets the knowledge of channel qualities at one moment, but in a typical case not always before each transmission because channel sounding costs large overhead time. Also, channel fluctuations over time are typically independent on each link, and thus it may be difficult to yield the same SNR of all receivers at any time. From this perspective, retransmission may play a more important role in MBF. MBF potentially yields shorter transmission time in this scenario, but still may have issues in reliability and may lead to degradation of the end-to-end throughput due to retransmission time. [0033]
  • One of the ideas of the present disclosure is the retransmission way for communication between the source node 10 and relay nodes 11, 12 to mitigate retransmission time, which will now explained in more detail.
  • Fig. 6 shows a diagram illustrating a more detailed embodiment of a communication scheme 400 of the communication between the different communication devices according to the present disclosure.
  • this communication scheme there are one multi-AP device 10 (a source node), several multi-AP devices 11, 12 (relay nodes) connected with the multi-AP device 10, and non-AP STA(s) 14 (a sink node) associated with the multi-AP devices 11 and 12.
  • an acknowledgement for each step is not illustrated in Fig. 6, but an acknowledgement may be carried out after each step.
  • two relay nodes are depicted as an example. In general, one or more relay nodes may be provided.
  • a packet error occurs in the communication between the source 10 and at least one of the relay nodes 11, 12.
  • the packet error is assumed to occur in a communication link, for example in step 403, between the source 10 and at least relay node 12.
  • the relay nodes 11 , 12 intend (or are planned) to perform CJT to the sink node 14.
  • a first step 401 the source node, the relay nodes and the non-AP STA(s) exchange their capabilities, including association.
  • the ..capabilities refer to the kind of functions each communication device has, e.g. whether a multi-AP device can operate as source node and/or relay node, which collaborative transmission can be performed at each multi- AP device, and/or by which beamforming (BF) types each non-AP STA can receive transmitted signals, etc.
  • BF beamforming
  • the source node 10 may inform the other nodes 11 and 12 that it can perform joint retransmission as well as multicast beamforming, and each of the relay nodes 11, 12 may inform the other nodes that it can receive multicast-beamformed signals and also perform joint retransmission.
  • Beamforming shall generally be understood as a technique for directional signal transmission or reception such as MRC (Maximal Ratio Combination), etc.
  • Collaborative transmission such as CJT, NCJT and CBF can also be seen as a part of BF because essentially transmitters form beams jointly or non-jointly to leverage spatial degree of freedom.
  • BF type shall be understood as the type of beamforming as well as collaborative transmission.
  • capabilities exchange between relay nodes 11 , 12 and non-AP STA(s) 14 follows the capabilities exchange between the source node 10 and the relay nodes 11, 12, but the sequence can be different. Furthermore, it is not illustrated in Fig. 6 that each non-AP STA's capabilities are relayed via relay nodes, but the capabilities can be directly sent to the source node from the non-AP STA. In this step, routing can also be determined.
  • link measurement which is measurement of each link quality
  • link measurement takes place in step 402.
  • link measurement means that data rates on communication links are measured by sending test packets or are estimated based on channel state information. Link measurements may be performed as described in IEEE standards of the 802.11 family, in particular 802.11s, or in EasyMesh standard and may include that the data rate can be estimated for each Joint Transmission Type.
  • the source node 10 can decide routing in transmitting data to sink node(s) 14 via relay nodes 11 , 12 as well as which kinds of relay nodes 11 , 12 are used for relaying data to the sink node(s) 14.
  • the source node 10 sends the same data to both of the relay nodes 11, 12 in multicast beamforming (MBF) in step 403. Due to the nature of multicast, which is that a common MCS (Modulation Coding and Scheme) is used in the transmission, each relay node 11 , 12 may generally face a different packet error rate.
  • MCS Modulation Coding and Scheme
  • a data unit e.g. a MPDll (MAC Data Protocol Unit)
  • MPDll MAC Data Protocol Unit
  • a data unit e.g. MPDll decoding failure happens at both of the relay nodes, but the failed data units (e.g. MPDlls) are partially/fully different among the relay nodes (case 2).
  • An MPDll can be identical to an MPDll 20 referred to in the IEEE 802.11 standard as shown in Fig. 7A, according to which it includes a MAC header, a payload and an FCS (Frame Check Sequence).
  • an MPDll 21 can be identical to the frame shown in Fig. 7B, according to which it includes two MAC headers, two FCSs and a payload.
  • An essential difference among the configurations of an MPDU shown in Figs. 7A and 7B is whether each of the relay nodes 11, 12 is required to generate the MAC header and FCS or not. If an MPDU 20 as shown in Fig. 7A is used, each of the relay node generates the MAC header by itself as well as FCS.
  • each of the relay nodes decodes MAC Header #2, Payload, and FCS #2, and then the relay node can send the decoded data to sink nodes.
  • FCS#1 is based on central part 22 indicated in bold (i.e. MAC Header#2, Payload, and FCS#2) of the MPDU 21.
  • FIG. 8 shows a diagram illustrating an embodiment of a communication scheme of the communication between the different communication devices according to case 1 , which illustrates steps 403 to 408 of the communication scheme 400 shown in Fig. 6 in more detail for case 1.
  • an aggregated MPDU which includes N MPDUs
  • A-MPDU which includes N MPDUs
  • link quality between the source node 10 and relay node 11 are better than the one between the source node 10 and the relay node 12, and thus erroneous MPDUs occur only at relay node 12, while the relay node 11 decodes all MPDUs correctly.
  • a BAR Block Ack Request
  • the source node knows which MPDUs failed to be decoded at each relay node 11 , 12, i.e., the Block Ack in step 405 represents reception status feedback indicating reception status of the transmitted data units.
  • decoding failure only happens at relay node 12 while relay node 11 decoded each of MPDlls correctly.
  • the BAR frame and the BA can be configured as described in IEEE standards of the 802.11 family, in particular IEEE 802.11e. The BAR may not be needed in case of implicit signaling in MPDlls.
  • a Joint Retransmission REQ (Request) is sent from the source node 10 to both relay nodes 11, 12 in step 406, which solicits relay node 11 which MPDlls to send to relay node 12 and which solicits relay node 12 to send a trigger frame for joint retransmission.
  • Fig. 9 shows an embodiment of a Joint Retransmission REQ frame 30 according to the present disclosure.
  • This frame 30 may comprise one or more of the following fields (in an embodiment, all these fields are included; in other embodiments only single fields or groups of fields are included; additional fields may be included as well):
  • Frame Control indicates types of this frame; basically, this field is interpreted so that this frame is a Joint Retransmission REQ frame;
  • RA Receiveiving STA Address: indicates to which non-AP STA(s) this frame is intended to be sent; in Fig. 6, for example, this field indicates both relay nodes 11 and 12; this field can indicate a broadcast address;
  • TA Transmitting STA Address: indicates from which non-AP STA this frame is transmitted; in the example of Fig. 6, this field indicates the source node 10.
  • Joint Retransmission REQ Control includes information such as variant of the next joint retransmission, the numbers of joint retransmission subfields, sender and recipient in the joint retransmission step excluding source node;
  • Joint Retransmission REQ Info indicates which data units (e.g. MSDUs and/or A- MSDU) are requested to be sent from which relay node (details will be explained below); this field may additionally designate a TID (Traffic Identifier); there may be multiple Joint Retransmission REQ fields.
  • data units e.g. MSDUs and/or A- MSDU
  • TID Traffic Identifier
  • the Joint Retransmission REQ Control field shown in Fig. 9 may comprise one or more of the following fields (in an embodiment, all these fields are included; in other embodiments only single fields or groups of fields are included; additional fields may be included as well):
  • Num of Joint Retransmission REQ Info indicates the number of Joint Retransmission REQ Info fields in the Joint Retransmission Request frame; as shown in Fig. 9, for example, N Joint Retransmission REQ Info fields are included, and this field indicates ‘N’;
  • Sender Info indicates which relay node(s) will send data units (e.g. MSDU/A- MSDlls), which are referred to in each of Joint Retransmission REQ Info fields, in the next Joint Retransmission; the corresponding data units (e.g. MSDU/A-MSDUs) are designated with both of Joint Retransmission REQ Starting Sequence Control subfields and Joint Retransmission REQ bitmap subfields in Joint Retransmission REQ Info fields; the sender Info subfield can be expressed as AID, which is referred in the IEEE 802.11 standards;
  • Recipient Info indicates which relay node will receive data units (e.g. MSDU/A- MSDUs), which are referred to in Joint Retransmission REQ Info fields, in the next Joint Retransmission; this subfield can be expressed as AID, which is referred to in the IEEE 802.11 standards; this information also can be interpreted by the relay node which will send a trigger frame after the Joint Retransmission REQ frame is received.
  • data units e.g. MSDU/A- MSDUs
  • the Joint Retransmission REQ #k Info field may comprise one or more of the following subfields (in an embodiment, all these subfields are included; in other embodiments only single subfields or groups of subfields are included; additional subfields may be included as well):
  • Per TID Info indicates which TID of data units, e.g. MSDUs or A-MSDUs, are requested in the Joint Retransmission REQ Info #k field;
  • Joint Retransmission REQ Starting Sequence Control includes the sequence number of the first data unit (e.g. an MSDU or A-MSDU) with TID indicated in Per TID subfield in Joint Retransmission;
  • the first data unit e.g. an MSDU or A-MSDU
  • TID indicated in Per TID subfield in Joint Retransmission
  • Joint Retransmission REQ bitmap contains certain octets bitmap; each bit that is equal to 1 in this subfield indicates a data unit (e.g. an MSDU or A-MSDU), which the relay node indicated in Sender Info subfield is solicited to send to the relay node indicated in Recipient Info subfield in the order of sequence number with the first bit of Joint Retransmission REQ bitmap subfield corresponding to the data unit with the sequence number that matches the information of Joint Retransmission REQ Starting Sequence subfield in Joint Retransmission REQ Info #k.
  • a data unit e.g. an MSDU or A-MSDU
  • the trigger frame is sent from relay node 12 in step 407 to solicit the source node 10 and the relay node 11 to send (i.e. retransmit) the MPDlls.
  • the way of this retransmission can be identical to UL (Uplink) MU (Multi-User) operation described in IEEE standards of the 802.11 family, in particular IEEE 802.11ax such as UL OFDMA (Orthogonal Frequency-Division Multiple Access).
  • the trigger frame can be sent from the source node 10 to both relay node 11, 12, and may also be included in the Joint Retransmission REQ frame transmitted in step 406 in an embodiment.
  • the trigger frame includes information of joint retransmission such as PPDU (PHY data Protocol Data Unit) length, which resource unit to be used by which relay nodes and source node, and MCS.
  • PPDU PHY data Protocol Data Unit
  • the trigger frame can be configured as defined in IEEE standards of the 802.11 family, in particular IEEE 802.11 ax.
  • step 408 the joint retransmission is performed.
  • the relay node 12 fails to decode (or receive) MPDU#1 and MPDU#2 (these MPDU thus generally represent “failed data units”). These MPDUs are thus retransmitted in the joint retransmission, wherein in this embodiment both MPDUs are retransmitted simultaneously.
  • MPDU#1 is retransmitted from source node 10 to relay node 12 and MPDU#2 is retransmitted from relay node 11 to relay node 12.
  • step 409 the relay node 12 sends a BA to all triggered nodes, i.e., the source node 10 and the relay node 11 , after receiving the retransmitted MPDUs in the joint retransmission, which may be seen as another reception status feedback.
  • step 410 the relay nodes 11 and 12 perform the CJT of the received MPDU to the sink node 14.
  • step 406 the steps of Joint Retransmission REQ (step 406) and Joint Retransmission (step 408) are performed once. In other embodiments, however, these steps can be performed multiple times, especially if there are more than two relay nodes available.
  • An embodiment of such a communication scheme is schematically illustrated in Fig. 10, in which three relay nodes 11, 12 and 16 are participating in the communication.
  • relay node 12 failed to correctly receive and/or decode MPDU#1 and MPDU#2, and relay node 16 failed to correctly receive and/or decode MPDU#3 and MPDU#4.
  • step 408 following step 406 of transmitting a first joint retransmission request in step 406 (from the source node 10 to relay nodes 11 and 12) and the step 407 of transmitting a trigger by relay node 12, MPDU#1 and MPDU#2 are simultaneously retransmitted from source node 10 and relay node 11 to relay node 12, which is then acknowledged in step 409 by relay node 12.
  • a second joint retransmission request is transmitted in step 411 (from the source node 10 to relay nodes 11 and 16) and a trigger is transmitted by relay node 16 in step 412.
  • MPDU#3 and MPDU#4 are simultaneously retransmitted from source node 10 and relay node 11 to relay node 16, which is then acknowledged in step 414 by relay node 16.
  • Fig. 11 shows a flow chart of an exemplary method 500 of setting a Joint Retransmission REQ bitmap subfield (of the Joint Retransmission REQ shown in Fig. 9) at the source node 10.
  • parameter k indicating the sequence number of the bitmap
  • k is incremented by 1 in step 503.
  • it is checked in step 504 if the BA frame indicates that MPDll with the last k-th sequence number is not decoded correctly.
  • the source node 10 will then set the last k-th bit of the corresponding Joint Retransmission REQ Bitmap subfield to 1 in step 505 if the BA frame indicates that MPDll with the last k-th sequence number is not decoded correctly. On the other hand, if the BA frame indicates that the last k-the sequence number is decoded correctly, the source node 10 set the last k-th bit of the correspond Retransmission REQ Bitmap subfield to 0 in step 506. This operation ends (step 508 when k reaches the number of the maximum bit length of Joint Retransmission REQ Bitmap field as checked in step 507.
  • Fig. 12 shows a diagram illustrating a more detailed embodiment of a communication scheme 600 of the communication between the different communication devices according to the present disclosure for case 2.
  • steps 601 to 605 correspond to steps 401 to 405 of the communication scheme 400 illustrated in Fig. 6.
  • Steps 606 to 608 are different than steps 406 to 408 and will be explained in the following.
  • Fig. 13 shows a diagram illustrating an embodiment of a communication scheme of the communication between the different communication devices according to case 2, which illustrates steps 603 to 609 of the communication scheme 600 shown in Fig. 12 in more detail for case 2.
  • an A-MPDll which includes N MPDlls, is sent to both relay nodes 11, 12 from the source node 10 in Multicast Beamforming in the multicast transmission step 603.
  • Some MPDlls fail to be decoded correctly at both relay nodes 11 and 12, wherein the MPDlls that failed at the relay nodes 11 and 12 are partially or fully different.
  • MPDU#1 failed to be received or decoded at relay node 11
  • MPDU#2 and MPDU#3 failed to be received or decoded at relay node 12.
  • the source node 10 sends a Joint Retransmission REQ frame and MPDU#1, which failed to be decoded at relay node 11, to relay node 11 in step 606.
  • the frame format of Joint Retransmission REQ may be identical to the frame mentioned above for case 1 , but the source node 11 preferably includes MPDU#1 and Joint Retransmission REQ frame into the same data unit (e.g. the same PPDU; also called single user (SU) PPDU), which is going to be sent to relay node 11.
  • the MPDU#1 may be added to Joint Retransmission REQ frame.
  • the source node 11 may further include a Reverse Direction Grant (RDG) in the frame, which solicits relay node 11 to send data in the TXOP while the source node 11 is the TXOP owner.
  • RDG Reverse Direction Grant
  • the relay node 11 knows which MPDU to be sent to which relay nodes by decoding the Joint Retransmission REQ frame, and also knows that the relay node 11 is solicited to send data to both the relay node 12 and the source node 11. After receiving the PPDU from the source node 11 , in a joint retransmission step 607, the relay node 11 sends a (Block) Ack frame and MPDU#2 and MPDU#3 in the same PPDU.
  • relay node 11 sends the PPDll to both the source node 11 and the relay node 12, wherein the relay node 11 can allocate (Block) Ack frame and MPDU#2 and MPDU#3 into the different resource units (Rlls) and/or spatial streams (SSs) so that the length of the (Block) Ack frame and the MPDlls are likely to be the same in the time domain. If the lengths are different, padding may be applied to align the lengths.
  • the source nodel 1 sends BAR in step 608 to relay node 12 to solicit to send Block Ack regarding MPDll #2 and MPDU#3 to the source node 10 in step 609.
  • the destination of the Block Ack frame can include relay node 11.
  • the MPDUs can be sent in Multicast BF in conjunction with Joint Retransmission REQ frame. If the TXOP owner is the source node 10 over the Joint Retransmission period and RDG is included in the frame, then any relay node except the relay node indicated in the Sender Info subfield in the Joint Retransmission REQ frame shall not send any frame unless the source node 10 sends another Joint Retransmission REQ frame or BAR frame.
  • the Joint Retransmission REQ frame is common among cases 1 and 2, but the behavior of the relay nodes 11 and 12 may be different.
  • the Code subfield in the Joint Retransmission REQ frame shown in Fig. 9 may be used.
  • Fig. 14 shows a flow chart of the operation 700 of a relay node, which is an intended receiver of the Joint Retransmission REQ frame and also indicated in the Sender Info subfield in a Joint Retransmission REQ frame received in step 701 by the relay node. If the Code subfield is set to ‘O’, as checked in step 702, the relay node recognizes that it is supposed to jointly send MPDUs together with the source node, which is indicated in Joint Retransmission Info fields in the Joint Retransmission REQ frame (step 703; case 1).
  • the relay node recognizes that it can send BA to the source node as well as MPDlls indicated in the Joint Retransmission REQ Info fields in the Joint Retransmission REQ frame (step 704; case 2).
  • a circuit is a structural assemblage of electronic components including conventional circuit elements, integrated circuits including application specific integrated circuits, standard integrated circuits, application specific standard products, and field programmable gate arrays. Further, a circuit includes central processing units, graphics processing units, and microprocessors which are programmed or configured according to software code. A circuit does not include pure software, although a circuit includes the abovedescribed hardware executing software. A circuit or circuitry may be implemented by a single device or unit or multiple devices or units, or chipset(s), or processor(s).
  • First communication device configured to operate as source node and communicate with two or more second communication devices that are configured to operate as relay nodes and communicate with one or more third communication devices, the first communication device comprising circuitry configured to: transmit one or more at least partly identical data units to two or more second communication devices that intend to perform coherent joint transmission to one or more third communication devices; receive reception status feedback from the two or more second communication devices indicating reception status of the transmitted one or more data units; and transmit a joint retransmission request to at least one of the two or more second communication devices if the received reception status feedback indicates at least one failed data unit that failed to be received or decoded by one or more second communication devices, said joint retransmission request indicating to the at least one of the two or more second communication devices which data unit to retransmit to which other second communication device.
  • First communication device wherein the circuitry is configured to retransmit at least one of the failed data units to the second communication device that had failed to receive or decode said failed data unit.
  • First communication device configured to transmit the one or more at least partly identical data units simultaneously to the two or more second communication devices in multicast or broadcast transmission mode.
  • circuitry is configured to retransmit the at least one failed data unit together with or as part of the transmission of the joint retransmission request.
  • circuitry is configured to retransmit the at least one failed data unit simultaneously with the retransmission of another failed data unit by the second communication device indicated in the joint retransmission request.
  • circuitry is configured to retransmit the at least one failed data unit before or after the retransmission of another failed data unit by the second communication device indicated in the joint retransmission request.
  • First communication device configured to include in or add to the transmission of the joint retransmission request (a) a trigger request requesting the one or more second communication devices that had indicated one or more failed data units in their reception status feedback to transmit retransmission information or (b) a trigger including retransmission information to be used for the retransmissions of the failed data units.
  • the circuitry is configured to include in or add to the joint retransmission request (a) a request that solicits a second communication device to which the joint retransmission request is transmitted to transmit to one or more other second communication devices at least one of the first data units indicated in the request, and/or (b) a granted duration for the second communication device to which the joint retransmission request is transmitted to transmit at least one of the first data units within the first communication device’s transmit opportunity.
  • the circuitry is configured to choose the first data units from data units failed to be received or failed to be decoded correctly at the other second communication devices but not at the second communication device to which the joint retransmission request is transmitted.
  • First communication device wherein the circuitry is configured to include in or add to the joint retransmission request information indicating that a second communication device to which the joint retransmission request is transmitted shall include the first communication device as a destination communication device in the granted transmission.
  • the retransmission information includes one or more of a group of retransmission parameters, the group including retransmission time, retransmission duration, target received signal strength indicator (RSSI), modulation and coding scheme (MCS) and second communication device identification information.
  • group of retransmission parameters including retransmission time, retransmission duration, target received signal strength indicator (RSSI), modulation and coding scheme (MCS) and second communication device identification information.
  • First communication device configured to include in or add to the joint retransmission request (a) a retransmission bitmap of length k, in which each bit indicates if a corresponding one of the last k data units transmitted from the first communication device shall be retransmitted from which second communication device, and (b) a sequence number of the last k-th data units transmitted from the first communication device.
  • First communication device wherein the circuitry is configured to include in the joint retransmission request said retransmission bitmap per Traffic Identifier (TID).
  • TID Traffic Identifier
  • circuitry is configured to include in or add to the joint retransmission request a retransmission indicator indicating if the first communication device intends to retransmit one or more failed data units simultaneously with or separately from the retransmission of one or more failed data units by the one or more second communication devices.
  • Second communication device configured to operate as relay node and to communicate with a first communication device configured to operate as source node, one or more other second communication devices configured to operate as relay nodes and/or one or more third communication devices configured to communicate with one or more second communication devices, the second communication device comprising circuitry configured to: perform coherent joint transmission with one or more other second communication devices; transmit reception status feedback to the first communication device indicating reception status of one or more data units received from the first communication device; receive a joint retransmission request from the first communication device indicating which at least one failed data unit that failed to be received or decoded by another second communication device to retransmit to which other second communication device; and retransmit the at least one failed data unit to the second communication device as indicated in the joint retransmission request.
  • circuitry is configured to receive one or more data units from the first communication device for subsequent transmission to one or more third communication devices in coherent joint transmission with one or more other second communication devices.
  • Second communication device wherein the circuitry is configured to retransmit the at least one failed data unit simultaneously with the retransmission of another failed data unit by the first communication device.
  • Second communication device according to embodiment 19, wherein the circuitry is configured to include the first communication device as a destination communication device within the granted transmission duration.
  • Second communication device configured to receive, included in or added to the joint retransmission request from the first communication device, (a) a retransmission bitmap of length k, in which each bit indicates if a corresponding one of the last k data units transmitted from which second communication device and (b) the sequence number of the last k-th data unit transmitted from the first communication device, and to retransmit the one or more data units indicated by the retransmission bitmap and the sequence number.
  • Second communication device configured to operate as relay node and communicate with a first communication device configured to operate as source node, one or more other second communication devices configured to operate as relay nodes and/or one or more third communication devices configured to communicate with one or more second communication devices, the second communication device comprising circuitry configured to: perform coherent joint transmission with one or more other second communication devices; transmit reception status feedback to the first communication device indicating reception status of one or more data units received from the first communication device; and receive a joint retransmission request from the first communication device indicating which at least one failed data unit that failed to be received or decoded by the second communication device to retransmit by another second communication device.
  • the circuitry is configured to:
  • Second communication device according to any one of embodiments 22 to 23, wherein the circuitry is configured to transmit, in response to a trigger request from the first communication device, retransmission information or a trigger including retransmission information to be used for the retransmissions of one or more failed data units to the second communication device.
  • Second communication device wherein the retransmission information includes one or more of a group of retransmission parameters, the group including retransmission time, retransmission duration, target received signal strength indicator (RSSI), modulation and coding scheme (MCS) and second communication device identification information.
  • the group including retransmission time, retransmission duration, target received signal strength indicator (RSSI), modulation and coding scheme (MCS) and second communication device identification information.
  • RSSI target received signal strength indicator
  • MCS modulation and coding scheme
  • Second communication device configured to transmit, in the coherent joint transmission with the one or more other second communication devices, the data units that have been correctly received in the original transmission and the retransmission to one or more third communication devices.
  • First communication method of a first communication device that is configured to operate as source node and communicate with one or more second communication devices that are configured to operate as relay nodes and communicate with one or more third communication devices, the first communication method comprising: transmitting one or more at least partly identical data units to two or more second communication devices that intend to perform coherent joint transmission to one or more third communication devices; receiving reception status feedback from the two or more second communication devices indicating reception status of the transmitted one or more data units; and transmitting a joint retransmission request to at least one of the two or more second communication devices if the received reception status feedback indicates at least one failed data unit that failed to be received or decoded by one or more second communication devices, said joint retransmission request indicating to the at least one of the two or more second communication devices which data unit to retransmit to which other second communication device.
  • Second communication method of a second communication device configured to operate as relay node and communicate with a first communication device configured to operate as source node, one or more other second communication devices configured to operate as relay nodes and/or one or more third communication devices configured to communicate with one or more second communication devices, the second communication method comprising: performing coherent joint transmission with one or more other second communication devices; transmitting reception status feedback to the first communication device indicating reception status of one or more data units received from the first communication device; receiving a joint retransmission request from the first communication device indicating which at least one failed data unit that failed to be received or decoded by another second communication device to retransmit to which other second communication device; and retransmitting the at least one failed data unit to the second communication device as indicated in the joint retransmission request.
  • Second communication method of a second communication device configured to operate as relay node and communicate with a first communication device configured to operate as source node, one or more other second communication devices configured to operate as relay nodes and/or one or more third communication devices configured to communicate with one or more second communication devices, the second communication method comprising: performing coherent joint transmission with one or more other second communication devices; transmitting reception status feedback to the first communication device indicating reception status of one or more data units received from the first communication device; and receiving a joint retransmission request from the first communication device indicating which at least one failed data unit that failed to be received or decoded by the second communication device to retransmit by another second communication device.
  • a non-transitory computer-readable recording medium that stores therein a computer program product, which, when executed by a processor, causes the method according to embodiment 27, 28 or 29 to be performed.
  • a computer program comprising program code means for causing a computer to perform the steps of said method according to embodiment 27, 28 or 29 when said computer program is carried out on a computer.

Abstract

L'invention concerne un premier dispositif de communication qui est configuré pour fonctionner en tant que nœud source et communiquer avec au moins deux deuxièmes dispositifs de communication qui sont configurés pour fonctionner en tant que nœuds relais et communiquer avec un ou plusieurs troisièmes dispositifs de communication. Le premier dispositif de communication comprend des circuits configurés pour transmettre une ou plusieurs unités de données au moins partiellement identiques à au moins deux deuxièmes dispositifs de communication qui ont l'intention d'effectuer une transmission conjointe cohérente à un ou plusieurs troisièmes dispositifs de communication ; recevoir une rétroaction d'état de réception en provenance des deux deuxièmes dispositifs de communication ou plus indiquant un état de réception desdites unités de données transmises ; et transmettre une demande de retransmission conjointe à au moins l'un des deux deuxièmes dispositifs de communication ou plus si la rétroaction d'état de réception reçue indique au moins une unité de données défaillante qui a échoué à être reçue ou décodée par un ou plusieurs deuxièmes dispositifs de communication, ladite demande de retransmission conjointe indiquant à l'au moins un des deux deuxièmes dispositifs de communication ou plus quelle unité de données à retransmettre à quel autre deuxième dispositif de communication.
PCT/EP2023/076476 2022-10-06 2023-09-26 Dispositifs et procédés de communication WO2024074343A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP22200051 2022-10-06
EP22200051.5 2022-10-06

Publications (1)

Publication Number Publication Date
WO2024074343A1 true WO2024074343A1 (fr) 2024-04-11

Family

ID=83688720

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/076476 WO2024074343A1 (fr) 2022-10-06 2023-09-26 Dispositifs et procédés de communication

Country Status (1)

Country Link
WO (1) WO2024074343A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060159054A1 (en) * 2004-12-21 2006-07-20 Ntt Docomo, Inc. Controller apparatus, mobile terminal, and communication control method
US20080168322A1 (en) * 2007-01-04 2008-07-10 Ntt Docomo, Inc. Communication device, radio communication terminal, radio base station and communication method
US20160212661A1 (en) * 2013-08-09 2016-07-21 Prateek Basu Mallick Efficient status reporting for ues in dual connectivity during mobility
WO2022139825A1 (fr) * 2020-12-22 2022-06-30 Nokia Technologies Oy Demande de répétition automatique hybride de liaison latérale améliorée avec relais d'équipement utilisateur-à équipement utilisateur intégré
WO2022154652A1 (fr) * 2021-01-12 2022-07-21 주식회사 아이티엘 Procédé et dispositif pour opération de drx dans un système de communication sans fil

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060159054A1 (en) * 2004-12-21 2006-07-20 Ntt Docomo, Inc. Controller apparatus, mobile terminal, and communication control method
US20080168322A1 (en) * 2007-01-04 2008-07-10 Ntt Docomo, Inc. Communication device, radio communication terminal, radio base station and communication method
US20160212661A1 (en) * 2013-08-09 2016-07-21 Prateek Basu Mallick Efficient status reporting for ues in dual connectivity during mobility
WO2022139825A1 (fr) * 2020-12-22 2022-06-30 Nokia Technologies Oy Demande de répétition automatique hybride de liaison latérale améliorée avec relais d'équipement utilisateur-à équipement utilisateur intégré
WO2022154652A1 (fr) * 2021-01-12 2022-07-21 주식회사 아이티엘 Procédé et dispositif pour opération de drx dans un système de communication sans fil
US20230363048A1 (en) * 2021-01-12 2023-11-09 Innovative Technology Lab Co., Ltd. Drx operation method and device in wireless communication system

Similar Documents

Publication Publication Date Title
US11095417B2 (en) Method for transmitting data in wireless communication system and apparatus therefor
KR101864977B1 (ko) 무선랜에서 재전송 방법 및 장치
JP6437653B2 (ja) 無線ｌａｎにおけるデータフレームの再送信なしにエラーを回復する方法及び装置
US11259204B2 (en) Method and system for improving responsiveness in exchanging frames in a wireless local area network
WO2018059282A1 (fr) Système et procédé de communication d2d
US9337954B2 (en) Protocol for channel state information feedback
JP4934666B2 (ja) 無線通信システムにおける制御情報の送信方法及びこれを用いた送信ウィンドウの更新方法
US8462690B2 (en) Apparatus and method for asynchronous control message transmission for data retransmission in wireless relay communication system
US8699525B2 (en) Method for sending an acknowledgement to an ingress mesh point in a mesh network and a medium access control frame format
US20120213308A1 (en) Managing acknolwledgement messages from multiple destinations for multi user mimo transmissions
US8554148B2 (en) Data transmission/reception apparatus and method for wireless communication system
US20110305205A1 (en) Response mechanisms for wireless networks using wide bandwidth
KR101279735B1 (ko) 무선랜에서의 프레임 교환시의 응답성을 개선하는 방법 및시스템
US11375577B2 (en) Method and apparatus for retransmission
US20190069213A1 (en) Support of a-msdu in a-mpdu
WO2017219756A1 (fr) Procédé de transmission de données, point d'accès et station
US11271686B2 (en) Hybrid automatic repeat request acknowledgement and upload multiuser operation
WO2024074343A1 (fr) Dispositifs et procédés de communication
KR101267726B1 (ko) 통신시스템에서 데이터 송수신 방법 및 장치
WO2023222321A1 (fr) Dispositifs et procédés de communication
CN117997482A (zh) 中继辅助重传
TW202345652A (zh) 用於多鏈路設備網路的網路譯碼