US20150312158A1 - Method and system for medium access control (mac) layer specialization for voice and multimedia data streams - Google Patents

Method and system for medium access control (mac) layer specialization for voice and multimedia data streams Download PDF

Info

Publication number
US20150312158A1
US20150312158A1 US14/795,248 US201514795248A US2015312158A1 US 20150312158 A1 US20150312158 A1 US 20150312158A1 US 201514795248 A US201514795248 A US 201514795248A US 2015312158 A1 US2015312158 A1 US 2015312158A1
Authority
US
United States
Prior art keywords
video data
priority level
frames
transmission
mac
Prior art date
Legal status (The legal status 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 status listed.)
Abandoned
Application number
US14/795,248
Inventor
Hooman Honary
Matthew James Fischer
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Avago Technologies International Sales Pte Ltd
Original Assignee
Broadcom Corp
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 Broadcom Corp filed Critical Broadcom Corp
Priority to US14/795,248 priority Critical patent/US20150312158A1/en
Assigned to BROADCOM CORPORATION reassignment BROADCOM CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FISCHER, MATTHEW, HONARY, HOOMAN
Publication of US20150312158A1 publication Critical patent/US20150312158A1/en
Assigned to BANK OF AMERICA, N.A., AS COLLATERAL AGENT reassignment BANK OF AMERICA, N.A., AS COLLATERAL AGENT PATENT SECURITY AGREEMENT Assignors: BROADCOM CORPORATION
Assigned to AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD. reassignment AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BROADCOM CORPORATION
Assigned to BROADCOM CORPORATION reassignment BROADCOM CORPORATION TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Assignors: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/27Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
    • H04L47/14
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/19Flow control; Congestion control at layers above the network layer
    • H04L47/193Flow control; Congestion control at layers above the network layer at the transport layer, e.g. TCP related
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2416Real-time traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/37Slow start
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04Registration at HLR or HSS [Home Subscriber Server]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L12/40143Bus networks involving priority mechanisms
    • H04L12/4015Bus networks involving priority mechanisms by scheduling the transmission of messages at the communication node
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40Bus networks
    • H04L12/407Bus networks with decentralised control
    • H04L12/413Bus networks with decentralised control with random access, e.g. carrier-sense multiple-access with collision detection (CSMA-CD)

Definitions

  • Certain embodiments of the invention relate to data communications. More specifically, certain embodiments of the invention relate to a method and system for medium access control (MAC) layer specialization for voice and multimedia data streams.
  • MAC medium access control
  • a network may comprise a plurality of communications media and communications devices that facilitate the transfer of information between a transmitting terminal and at least one receiving terminal.
  • Information may be transmitted via a network in messages, packets, and/or frames.
  • Various communication protocols may be utilized to facilitate the transfer of information in a network.
  • Some transport layer data protocols may control the amount of information that may be transmitted during a time interval.
  • the transmission control protocol (TCP) may be considered to be an example of one such protocol.
  • the TCP may limit the amount of information that is transmitted during a time interval based on a congestion window and slow start. At the beginning of transmission of an information flow, the congestion window may be set to an initial value. This may result in a relatively small amount of information being transmitted from a transmitting terminal to a receiving terminal.
  • the receiving terminal may subsequently communicate an acknowledgement upon receipt of the information that was transmitted by the transmitting terminal.
  • the transmitting terminal may increase the value associated with the congestion window to a number larger than the initial value, and transmit subsequent information based on the larger value that is associated with the congestion window. This may result in a larger amount of information being transmitted than during a comparable time interval in which the value associated with the congestion window is smaller.
  • the size of the congestion window may increase with the increase in the value associated with the congestion window. A larger congestion window may also result in a higher information transfer rate between the transmitting terminal and the receiving terminal.
  • the receiving terminal may communicate subsequent acknowledgements upon receipt of subsequent information.
  • the transmitting terminal may continue to increase the size of the congestion window upon receipt of a subsequent acknowledgement.
  • the transmitting terminal may determine that the receiving terminal did not receive the previously transmitted information.
  • the transmitting terminal may retransmit, or resend, previously transmitted information for which a corresponding acknowledgement was not received.
  • the transmitting terminal may determine that congestion may exist in the network resulting in the previously transmitted information not being received by the receiving terminal.
  • the previously transmitted information may be considered by the transmitting terminal to be “lost” in the network.
  • the transmitting terminal may also reduce the size of the congestion window. The reduction in the size of the congestion window may result in a reduction in the information transfer rate between the transmitting terminal and the receiving terminal. Once reduced, the size of the congestion window may subsequently begin to increase once again. Thus, a slow start recovery may be initiated at the transmitting terminal.
  • fading conditions within the wireless communications medium may result in transmitted information not being received by the receiving terminal.
  • the fading conditions may be temporary, thus it may be undesirable for a transmitting terminal to enter a slow start state as a result of a temporary loss of data due to fading conditions within the wireless communications medium.
  • TCP may be utilized for the transmission of multimedia information, comprising voice, video, and/or data. The real time nature of multimedia information may make it undesirable for the transmitting terminal to enter a slow start state.
  • MAC medium access control
  • FIG. 1 is a block diagram of exemplary communications circuitry that may be utilized in connection with an embodiment of the invention.
  • FIG. 2 illustrates an exemplary architecture for source layer optimization for transmitting data, in accordance with an embodiment of the invention.
  • FIG. 3 illustrates an exemplary MIMO architecture with feedback from a receiver to a transmitter, in accordance with an embodiment of the invention.
  • FIG. 4 is an exemplary flowchart illustrating message exchanges in a successful TCP communication, which may be utilized in connection with an embodiment of the invention.
  • FIG. 5 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication, which may be utilized in connection with an embodiment of the invention.
  • FIG. 6 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication for low priority level information, in accordance with an embodiment of the invention.
  • FIG. 7 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication for high priority level information, in accordance with an embodiment of the invention.
  • FIG. 8 is an exemplary flowchart illustrating exemplary steps for a system for MAC layer specialization for voice and multimedia data streams, in accordance with an embodiment of the invention.
  • Certain embodiments of the invention may be found in a method and system for medium access control (MAC) layer specialization for voice and multimedia data streams.
  • Aspects of the method comprise determining a number of attempts for transmitting one or more MAC frames.
  • Aspects of the system may comprise a processor that enables determination of a number of attempts for transmitting one or more MAC frames. A maximum number for such attempts may be determined based on one or more priority levels associated with different portions of multimedia information being communicated via a wireless medium and contained within the one or more MAC frames.
  • FIG. 1 is a block diagram of exemplary communications circuitry that may be utilized in connection with an embodiment of the invention.
  • a memory processor 172 there is shown a memory processor 172 , a transceiver 174 , an RF front end 180 , a plurality of receive antennas 176 a , . . . , 176 n , and a plurality of transmitting antennas 178 a , . . . , 178 n .
  • the transceiver 174 may comprise a processor 182 , a receiver 184 , and a transmitter 186 .
  • the memory 172 may enable storage and/or retrieval of information that may be transmitted via one or more transmitting antennas 178 a , . . . , 178 n , received via one or more receive antennas 176 a , . . . , 176 n , and/or storage of code that may enable control of the operation of the transceiver 174 .
  • the processor 182 may enable digital receiver and/or transmitter functions in accordance with applicable communications standards. These functions may comprise, but are not limited to, tasks performed at lower layers in a relevant protocol reference model. These tasks may further comprise the physical layer convergence procedure (PLCP), physical medium dependent (PMD) functions, and associated layer management functions.
  • PLCP physical layer convergence procedure
  • PMD physical medium dependent
  • the receiver 184 may be enable digital receiver functions that may comprise, but are not limited to, fast Fourier transform processing, beamforming processing, equalization, demapping, demodulation control, deinterleaving, depuncture, and decoding.
  • the transmitter 186 may enable digital transmitter functions that comprise, but are not limited to, coding, puncture, interleaving, mapping, modulation control, inverse fast Fourier transform processing, beamforming processing.
  • the RF front end 180 may enable reception of analog RF signals via antennas 176 a , . . . , 176 n , converting the RF signal to baseband, and generating digital representations of the received analog baseband signals.
  • the digital representation may be a complex quantity comprising I and Q components.
  • the RF front end 180 may also transmit analog RF signals via an antenna 178 a , . . . , 178 n , converting a digital baseband signal to an analog RF signal.
  • the processor 182 may receive data from the receiver 184 .
  • the processor 182 may store received data to the memory 172 for subsequent analysis and/or processing.
  • the processor 182 may retrieve information from the memory 172 .
  • the retrieved information may be transmitted via an RF channel by the transmitter 186 .
  • the processor 182 may associate one or more priority classes to the retrieved information.
  • the transmitter 186 may process and transmit the information via the RF channel based on the corresponding priority classes.
  • FIG. 2 illustrates an exemplary architecture for source layer optimization for transmitting data, in accordance with an embodiment of the invention.
  • the transmit block 215 may comprise a source encoder block 220 , a memory block 222 , a source layer multiplexer block 224 , a PHY/MAC block 226 , a cross-layer partitioner block 228 , a parameter control block 230 , and transmit antennas 232 a , . . . , 232 b.
  • the source encoder block 220 may comprise suitable logic, circuitry, and/or code that may be utilized to enable compression of data prior to transmission.
  • the compressed data may be video data in MPEG-4 format.
  • the source encoder block 220 may also communicate information about the compressed data to the cross-layer partitioner block 228 .
  • the information communicated may relate to the type of compression.
  • the source encoder block 220 may communicate the specific type of compression, such as MPEG-1, MPEG-2, MPEG-4, H.261, H.263, or H.264.
  • the source encoder block 220 may also communicate the type of chroma subsampling used, such as, for example, 4-4-4, 4-2-2, or 4-2-0 chroma subsampling.
  • the source layer multiplexer block 224 may comprise suitable logic, circuitry, and/or code that may be utilized to enable reading data from, for example, the memory block 222 and communicating various portions of the data to the PHY/MAC 226 .
  • the data may be split into the various portions according to information from the cross-layer partitioner block 228 .
  • the information from the cross-layer partitioner block 228 may comprise, for example, priority for the various portions of the data.
  • the cross-layer partitioner block 228 may also indicate that portions of data with certain priority may be communicated via certain outputs of the source layer multiplexer block 224 .
  • the PHY/MAC block 226 may comprise suitable logic, circuitry, and/or code that may be utilized to enable conversion of input data in a digital format to output suitably modulated analog data ready for transmission.
  • the PHY/MAC block 226 may apply a FEC code to the digital data.
  • the PHY/MAC block 226 may also apply a specific RF modulation to the analog signal, which may have been converted from the digital data.
  • the PHY/MAC block 226 may additionally communicate analog signals to different transmit antennas 232 a , . . . , 232 b , in a part of a multiple-input multiple-output (MIMO) architecture.
  • MIMO multiple-input multiple-output
  • the PHY/MAC block 226 may receive one or more streams of digital data.
  • the PHY/MAC block 226 may then operate on the multiple streams as indicated by, for example, the parameter control block 230 .
  • the PHY/MAC block 226 may, for example, apply a specific FEC code to each digital stream.
  • Each digital stream may then be converted to analog RF signal, which may be modulated by a specific RF modulation scheme.
  • Each modulated RF signal may then be communicated to one or more antennas to be transmitted.
  • the cross-layer partitioner block 228 may comprise suitable logic, circuitry, and/or code that may be utilized to enable assigning a priority to portions of data in the memory block 222 .
  • the priority may be based on, for example, perceived importance of the information in the memory block 222 .
  • a portion of the data that comprises information about an entire frame, such as, example, an I-frame may have a high priority.
  • Other frames, such as, for example, P-frames may have a lower priority than I-frames since P-frames may depend on the I-frames for additional information.
  • P-frames that depend on other primary P-frames may be, for example, assigned a lower priority than the P-frames that may only depend on I-frames.
  • a B-frame that depends on a prior and a subsequent frame may be assigned, for example, a lowest priority.
  • the number of priorities may be design and/or implementation dependent.
  • the cross-layer partitioner block 228 may also indicate to the source layer multiplexer block 224 that data with certain priorities may be communicated to the PHY/MAC block 226 via specific outputs of the source layer multiplexer block 224 .
  • the cross-layer partitioner block 228 may then communicate to the parameter control block 230 those operations that may be performed on the various streams of data communicated by the source layer multiplexer 224 .
  • Specific streams of data may be communicated to specific transmit antennas.
  • the cross-layer partitioner block 228 may have information regarding the propagation path from each transmit antenna 232 a , . . . , 232 b to a receive antenna, where data transmitted via one transmit antenna may be received with fewer bit errors, for example, than data transmitted by another transmit antenna. Accordingly, this information may be used to determine which data may be transmitted via which transmit antenna.
  • the information regarding the propagation path for each transmit antenna may be generated, for example, from feedback information from the receiving devices. Alternatively, the information may be generated from feedback information from a receiver co-located with the transmit block 215 .
  • the information may be utilized for a method of MIMO transmission referred to as beamforming.
  • the parameter control block 230 may comprise suitable logic, circuitry, and/or code that may be utilized to enable controlling of various operations to the digital data in the PHY/MAC block 226 .
  • the parameter control block 230 may determine the FEC code and/or the RF modulation that may be used by the PHY/MAC block 226 for specific portions of data.
  • the parameter control block 230 may also determine which antennas may be used to transmit which portions of data by controlling routing of the data within the PHY/MAC block 226 to the specific antennas.
  • some embodiments of the invention may select the antenna used to transmit data by selecting the source layer multiplexer 224 output used to communicate data from the source layer multiplexer 224 to the PHY/MAC 226 .
  • Data communicated to the PHY/MAC 226 via specific outputs to the PHY/MAC 226 may be transmitted via specific transmit antennas.
  • the data, Output 1 may be transmitted by the transmit antenna 232 a
  • the data, Output 2 may be transmitted by the transmit antenna 232 b.
  • the source encoder block 220 may compress data and store the compressed data in the memory block 222 .
  • the data may be assumed to be video data compressed using the MPEG-4 format, two priority levels may be used—a high priority level and a low priority level, and Output 1 data and Output 2 data may be transmitted by the transmit antennas 232 a and 232 b , respectively.
  • the source encoder block 220 may communicate to the cross layer partitioner block 228 that the compressed data is video data using the MPEG-4 format.
  • the source encoder block 220 may also communicate, for example, start and end memory addresses for the stored video data corresponding to a frame, the frame number, and the type of frame that may be stored.
  • the type of frame may be, for example, I-frame, P-frame, and B-frame. Other information may also be communicated, such as, for example, the chroma subsampling format.
  • the cross layer partitioner block 228 may then determine a priority to assign to each frame.
  • An exemplary priority level algorithm may assign a high priority for all I-frames and a low priority for all other frames.
  • the priority for the video data in the memory block 222 may be communicated to the source layer multiplexer block 224 .
  • the source layer multiplexer 224 may read data from the memory block 222 , and may output, for example, high priority data as Output 1 and the low priority data as Output 2 .
  • the cross layer partitioner block 228 may also communicate to the parameter control block 230 the operations to be applied to each stream of data, namely, Output 1 and Output 2 .
  • the parameter control block 230 may indicate that the high priority data, Output 1 , may have applied to it a forward error correction (FEC) code A that may have a greater overhead in the number of bits used than a FEC code B.
  • FEC forward error correction
  • using the FEC code A may allow a receiving unit to correct a larger number of faulty bits than when using the FEC code B.
  • the cross layer partitioner block 228 may also communicate to the parameter control block 230 to use, for example, quadrature phase shift keying (QPSK) RF modulation rather than 16 quadrature amplitude modulation (16 QAM) RF modulation for the high priority data Output 1 .
  • QPSK RF modulation may have a smaller data throughput than the 16 QAM RF modulation, however, the QPSK RF modulation may be more reliable for a given transmission environment.
  • the transmit antenna 232 a may exhibit more reliable transmission characteristics than the transit antenna 232 b . If the transmission environment changes such that the transmit antenna 232 b exhibits a more reliable transmission characteristics than the transmit antenna 232 a , then the cross layer partitioner block 228 may indicate that the higher priority data be output as Output 2 .
  • the cross layer partitioner block 228 may also take in to account feedback information from the receiving device to maximize throughput for transmission of the high priority and low priority data. This may allow, for example, the cross layer partitioner block 228 to select from a plurality of FEC codes and from a plurality of RF modulation schemes for a plurality of priority levels.
  • MIMO transmission may utilize beamforming, in which one antenna may be selected for transmission of particular stream of data, or a plurality of antennas may be selected for transmission of a particular stream of data.
  • feedback information from a receiving device may be used for transmission, the invention need not be so limited.
  • feedback data from a receiver that is co-located with the transmitting device may also be used.
  • the processor 210 may communicate the feedback data and/or instructions to the transmit block 215 .
  • the processor 210 may process the feedback data from a co-located receiving device, and communicate information to the transmit block 215 .
  • the information may be used, for example, to control the operations on the data streams by the PHY/MAC block 226 .
  • FIG. 3 illustrates an exemplary MIMO architecture with feedback from a receiver to a transmitter, in accordance with an embodiment of the invention.
  • the transmitting terminal 312 and the receiving terminal 310 may receive the data transmitted by the transmitting terminal 312 .
  • the transmitting terminal 312 may transmit signals via the transmit antennas 312 a and 312 b , and the receiving terminal may receive signals via the antennas 310 a and 310 b .
  • the transmitting terminal 312 may generate the RF signals tx 1 and tx 2 , which may be transmitted via the transmit antennas 312 a and 312 b , respectively.
  • the transmitted RF signals may be represented by s 1 and s 2 .
  • the signals received by the receive antennas 310 a and 310 b may be represented by R 1 and R 2 , respectively.
  • a receive antenna may receive signals from a plurality of transmit antennas, for example, the transmit antennas 312 a and 312 b .
  • the transmit antennas 312 a and 312 b may transmit the same data.
  • the transmit antennas 312 a and 312 b may transmit different data.
  • the receiving terminal 310 may process the received signals R 1 and R 2 to estimate what information may have been transmitted by the transmitting terminal 312 .
  • the receiving terminal 310 may also generate various signal metrics such as, for example, the SNR and bit error rate. The signal metrics may be fed back to the transmitting terminal 312 .
  • the transmitting terminal 312 may transmit different data via the transmit antennas 312 a and 312 b .
  • the receiving terminal 310 may also process the received signal R 1 for the data transmitted by the transmit antenna 312 a , and the received signal R 2 for the data transmitted by the transmit antenna 312 b . Accordingly, if the bit error rate for the received signal R 1 is less than the bit error rate for the received signal R 2 , this information may be fed back to the transmitting station 312 .
  • the transmitting station 312 may then assign, for example, the transmit antenna R 1 for the high priority data and the transmit antenna R 2 for the low priority data.
  • the bit error rate and other metrics fed back to the transmitting terminal 312 may be used by the transmitting terminal 312 to select, for example, different FEC codes and/or RF modulation schemes.
  • FIG. 4 is an exemplary flowchart illustrating message exchanges in a successful TCP communication, which may be utilized in connection with an embodiment of the invention.
  • a transmitting terminal 432 and a receiving terminal 430 may comprise a plurality of communication entities comprising a coordination function 432 a , a TCP entity 432 b , and a MAC entity 432 c .
  • the receiving terminal may comprise a plurality of communication entities comprising a TCP entity 430 a , and a MAC entity 430 b.
  • FIG. 4 illustrates an exemplary exchange of messages from a TCP entity 432 b in a transmitting terminal 432 and a corresponding TCP entity 430 a in a receiving terminal 430 .
  • the messages may be utilized to communicate multimedia information, which may comprise voice, video and/or data information, for example.
  • the messages may comprise TCP packets, and MAC frames, for example.
  • a MAC frame may comprise a TCP packet by encapsulating the TCP packet, for example.
  • a MAC frame may be defined in various IEEE 802 documents and standards, for example.
  • a TCP packet may be defined in various Internet Engineering Task Force (IETF) request for comments (RFC) documents and standards such as RFC 793, for example.
  • IETF Internet Engineering Task Force
  • RFC request for comments
  • the TCP entity 432 b may communicate a TCP packet 402 to the MAC entity 432 c .
  • the TCP entity 432 b may communicate information to the coordination function 432 a .
  • M may indicate an amount of data, as measured in octets, for example.
  • the variable M may represent a number whose value is greater than 1, for example.
  • the communicated information may also comprise a start TCP timer indication.
  • the TCP timer indication may indicate a start time for a time duration within which an acknowledgement is expected from the receiving terminal 430 .
  • TCP entity 432 b may attempt to retransmit the TCP packet (step 402 ) one or more times.
  • the MAC entity 432 c may encapsulate the TCP packet (step 402 ) and communicate a MAC frame to the MAC entity 430 b .
  • the MAC entity 430 b may communicate a MAC acknowledgement frame to the MAC entity 432 c . Receipt of the MAC acknowledgement frame by the MAC entity 432 c may indicate that the MAC frame (step 406 ) was successfully received by the MAC entity 430 b .
  • the MAC entity 430 b may communicate a TCP packet to the TCP entity 430 a .
  • the TCP packet (step 410 ) may be derived by de-encapsulation of the received MAC frame (step 406 ).
  • the TCP packet (step 410 ) may substantially comprise the information contained in the TCP packet (step 402 ).
  • the TCP entity 430 a may communicate a TCP and acknowledgement packet to the MAC entity 430 b .
  • the TCP portion of the packet may comprise information being communicated from the receiving terminal 430 to the transmitting terminal 432 , for example, feedback information.
  • the acknowledgement portion of the packet may comprise information that enables the TCP entity 432 b to determine that the TCP packet (step 402 ) was successfully received by the TCP entity 430 a .
  • the MAC entity 430 b may encapsulate the TCP and acknowledgement packet (step 412 ) and communicate a MAC frame to the MAC entity 432 c .
  • the MAC entity 432 c may communicate a MAC acknowledgement frame to the MAC entity 430 b
  • the MAC entity 432 c may communicate a TCP and acknowledgement packet to the TCP entity 432 b .
  • the TCP and acknowledgement packet (step 418 ) may be derived by de-encapsulation of the received MAC frame (step 414 ).
  • the TCP and acknowledgement packet (step 418 ) may substantially comprise the information contained in the TCP and acknowledgement packet (step 412 ).
  • the TCP entity 432 b may communicate information to the coordination function 432 a .
  • the variable A may represent a number whose value is greater than or equal to 0, for example.
  • the communicated information may also comprise a stop TCP timer indication.
  • the stop TCP timer indication may indicate that the timer, which was started in anticipation of an acknowledgement for the TCP packet (step 402 ), has been stopped.
  • FIG. 5 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication, which may be utilized in connection with an embodiment of the invention.
  • a transmitting terminal 432 and a receiving terminal 430 may comprise a plurality of communication entities comprising a coordination function 432 a , a TCP entity 432 b , and a MAC entity 432 c .
  • the receiving terminal may comprise a plurality of communication entities comprising a MAC entity 430 a.
  • the TCP entity 432 b may communicate a TCP packet 402 to the MAC entity 432 c .
  • the TCP entity 432 b may communicate information to the coordination function 432 a .
  • M may indicate an amount of data, as measured in octets, for example.
  • the variable M may represent a number whose value is greater than 1, for example.
  • the communicated information may also comprise a start TCP timer indication.
  • the TCP timer indication may indicate a start time for a time duration within which an acknowledgement is expected from the receiving terminal 430 .
  • the MAC entity 432 c may encapsulate the TCP packet (step 502 ) and communicate a MAC frame to the MAC entity 430 a .
  • the MAC entity 432 c may communicate information to the coordination function 432 a .
  • the communicated information may comprise a start MAC timer indication.
  • the MAC timer indication may indicate a start time for a time duration within which an acknowledgement is expected from the receiving terminal 430 . Failure to receive an acknowledgement within the time duration may result in the MAC entity 432 c abandoning attempts to communicate the MAC frame (step 506 ) to the receiving terminal 430 .
  • the MAC 432 c may attempt to retransmit the MAC frame.
  • the variable L may represent a number whose value is greater than or equal to 0, for example.
  • the number of retransmission attempts may occur during the time duration associated with the MAC timer (step 508 ).
  • the communicated information may also comprise a stop MAC timer indication.
  • the stop MAC timer indication may indicate that a MAC timer timeout has occurred.
  • the TCP entity 432 b may perform a plurality of retransmission attempts for the TCP packet (step 502 ).
  • the plurality of retransmission attempts may occur during the time duration associated with the TCP timer (step 504 ).
  • steps 516 a , . . . , 516 n a plurality of MAC frames may be transmitted in response to the corresponding TCP packet retransmission attempts ( 514 a , 514 n ).
  • the TCP entity 432 b may communicate information to the coordination function 432 a .
  • the communicated information may also comprise a stop TCP timer indication.
  • the stop TCP timer indication may indicate that a TCP timer timeout has occurred.
  • the response to a MAC timer timeout may be determined based on the assigned priority level associated with the information content contained within the MAC frame.
  • FIG. 6 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication for low priority level information, in accordance with an embodiment of the invention.
  • the transmitting terminal may comprise a plurality of communication entities comprising a coordination function 632 a , a source application entity 632 b , a TCP entity 632 c , and a MAC entity 632 d .
  • the receiving terminal may comprise a plurality of communication entities comprising a MAC entity 630 a .
  • Exemplary source application entities may comprise MPEG-4 encoders, database programs, and voice over IP (VOIP) encoders.
  • the source application entity 632 b may communicate source information to the TCP entity 632 c .
  • the source application entity 632 b may communicate information to the coordination function 632 a .
  • the TCP entity 632 c may communicate a TCP packet to the MAC entity 632 d .
  • the TCP entity 632 c may communicate information to the coordination function 632 a .
  • the communicated information may comprise a start TCP timer indication.
  • the unacknowledged sequence number may indicate a TCP packet (step 606 ) that was transmitted by the TCP entity 632 c , for which a corresponding acknowledgement has not been received, for example.
  • the value for the contention window parameter L Low may be determined based on the priority class (step 604 ).
  • the MAC entity 632 d may encapsulate the TCP packet (step 606 ) and communicate a MAC frame to the MAC entity 630 a .
  • the MAC entity 632 d may communicate information to the coordination function 632 a .
  • the communicated information may comprise a start MAC timer indication.
  • the communicated information may also comprise a stop MAC timer indication.
  • the stop MAC timer indication may indicate that a MAC timer timeout has occurred.
  • the coordination function 632 a may communicate a halt instruction to the TCP entity 632 c in association with the TCP packet (step 606 ).
  • the halt instruction may instruct the TCP entity 632 c to suspend attempts to retransmit the unacknowledged TCP packet (step 606 ).
  • the halt instruction may also instruct the TCP entity 632 c to suspend entry into a slow start state if an acknowledgement for the TCP packet (step 606 ) is not received.
  • the TCP entity 632 c may communicate information to the coordination function 632 a .
  • the communicated information may comprise a reset TCP timer indication.
  • the reset TCP timer indication may indicate that the TCP entity 632 c has ceased tracking a TCP timeout condition in connection with the TCP packet (step 606 ).
  • the TCP timer may continue tracking a TCP timeout condition that may occur in connection with TCP packets that may have be transmitted by the TCP entity 632 c subsequent to transmission of the TCP packet (step 606 ).
  • the variable A may represent a number whose value is greater than or equal to 0, for example.
  • FIG. 7 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication for high priority level information, in accordance with an embodiment of the invention.
  • the transmitting terminal may comprise a plurality of communication entities comprising a coordination function 632 a , a source application entity 632 b , a TCP entity 632 c , and a MAC entity 632 d .
  • the receiving terminal may comprise a plurality of communication entities comprising a MAC entity 630 a.
  • the source application entity 632 b may communicate source information to the TCP entity 632 c .
  • the source application entity 632 b may communicate information to the coordination function 632 a .
  • the TCP entity 632 c may communicate a TCP packet to the MAC entity 632 d .
  • the TCP entity 632 c may communicate information to the coordination function 632 a .
  • the communicated information may comprise a start TCP timer indication.
  • the unacknowledged sequence number may indicate a TCP packet (step 706 ) that was transmitted by the TCP entity 632 c , for which a corresponding acknowledgement has not been received, for example.
  • the value for the contention window parameter L High may be determined based on the priority class (step 704 ).
  • the MAC entity 632 d may encapsulate the TCP packet (step 706 ) and communicate a MAC frame to the MAC entity 630 a .
  • the MAC entity 632 d may communicate information to the coordination function 632 a .
  • the communicated information may comprise a start MAC timer indication.
  • the communicated information may also comprise a stop MAC timer indication.
  • the stop MAC timer indication may indicate that a MAC timer timeout has occurred.
  • the time duration spanning the start MAC timer indication (step 714 ) and the stop MAC timer indication (step 718 ) may comprise a substantial portion of the TCP timeout duration, for example.
  • the number of TCP retransmission attempts prior to a TCP timeout in various embodiments of the invention, may be 0, and/or fewer in number than in some conventional systems as represented in steps 514 a , . . . , 514 n.
  • the TCP entity 632 c may communicate information to the coordination function 632 a .
  • the communicated information may also comprise a stop TCP timer indication.
  • the stop TCP timer indication may indicate that a TCP timer timeout has occurred.
  • FIG. 8 is an exemplary flowchart illustrating exemplary steps for a system for MAC layer specialization for voice and multimedia data streams, in accordance with an embodiment of the invention.
  • priority levels may be assigned to source information. The priority levels may be assigned based on the information content associated with source information.
  • a number of MAC layer retransmission attempts associated with a transmitted MAC frame may be determined based on the priority levels.
  • a high priority level may be associated with a value L High
  • a low priority level may be associated with a value L Low , for example.
  • a response to a MAC layer timeout condition may be determined based on the priority levels.
  • a higher number of MAC layer retransmission attempts L High
  • a subsequent TCP timer timeout may occur causing the TCP layer entity to enter a slow start state.
  • a lower number of MAC layer retransmission attempts L Low
  • the coordination function may instruct the TCP layer entity to continue packet processing and not enter a slow start state in response to a failure to receive an acknowledgement from the previously transmitted TCP packet.
  • a number of retry attempts by the MAC layer entity 632 d may be based on a priority level associated with a video frame type contained with a MAC frame.
  • I frames may carry full image information and may be associated with a high priority level, for example. Consequently, a greater number of MAC layer retry attempts may be performed.
  • B frames may carry sub-picture information and motion vectors. The impact of loss of a B frame for video quality may be less than the impact of loss of an I frame. B frames may be associated with a low priority level, for example. Consequently, a lesser number of MAC layer retry attempts may be performed. If a MAC layer timeout occurs in connection with transmission and/or retransmission of B frame information, the coordination function 632 a may communicate an instruction, to the TCP entity 632 c , to skip the corresponding TCP packet.
  • aspects of a system for medium access control (MAC) layer specialization for voice and multimedia data streams may comprise a processor 210 that enables determination of a number of attempts for transmitting one or more MAC frames based on a corresponding one or more of a plurality of priority levels associated with different portion of multimedia information.
  • the number of attempts may occur within a time duration associated with a transmission control protocol (TCP) packet corresponding to the one or more MAC frames.
  • TCP transmission control protocol
  • the TCP packet may be encapsulated by utilizing a corresponding one or more MAC frames.
  • the MAC frames may be transmitted by a transmitting terminal 632 to a receiving terminal 630 via a wireless medium.
  • a maximum number of attempts for transmitting the one or more MAC frames may occur within a timeout period associated with the TCP packet.
  • the timeout period may comprise a time duration within which an acknowledgement in response to transmitting the TCP packet is expected from the receiving terminal 630 .
  • the processor 210 may enable a TCP entity 632 c to cease attempts to retransmit a TCP packet subsequent to a time duration associated with the one or more MAC frames based on the one or more of the plurality of priority levels.
  • the time duration may represent a timeout period associated with the MAC frame during which the maximum number of attempts for transmitting the MAC frame may be performed.
  • the processor 210 may instruct the TCP entity 632 c to stop a timer associated with the TCP packet.
  • the instruction to stop the timer associated with the TCP packet may be in connection with receipt of a skip instruction from a coordination function 632 a .
  • the TCP entity 632 c may continue to measure time duration associated with a subsequent TCP packet and/or previous TCP packet.
  • the subsequent TCP packet and/or previous TCP packet may have been transmitted at least once at the time instant in which timer associated with the TCP packet was stopped.
  • the TCP entity 632 c may not enter a slow start state based on failure to receive an acknowledgement in response to transmitting and/or retransmitting the TCP packet.
  • the slow start state may be defined based on TCP specifications, for example.
  • the processor 210 may enable one or more attempts to retransmit a TCP packet subsequent to a time duration associated with the one or more MAC frames based on the one or more of the plurality of priority levels.
  • the TCP entity 632 c may attempt to transmit the TCP packet subsequent to a MAC timeout.
  • the processor 210 may enable entry of a slow start state based on a failure to receive an acknowledgement in response to transmitting and/or retransmitting the TCP packet.
  • the present invention may be realized in hardware, software, or a combination of hardware and software.
  • the present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited.
  • a typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
  • the present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods.
  • Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.

Abstract

Aspects of a method and system for medium access control (MAC) layer specialization for voice and multimedia data streams are presented. Aspects of the method include determining a number of attempts for transmitting one or more medium access control (MAC) frames. Aspects of the system may include a processor that enables determination of a number of attempts for transmitting one or more MAC frames. A maximum number for such attempts may be determined based on one or more priority levels associated with different portions of multimedia information being communicated via a wireless medium and contained within the one or more MAC frames.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE
  • The present U.S. Utility Patent Application claims priority pursuant to 35 U.S.C. §120 as a continuation of U.S. Utility application Ser. No. 13/852,749, entitled “METHOD AND SYSTEM FOR MEDIUM ACCESS CONTROL (MAC) LAYER SPECIALIZATION FOR VOICE AND MULTIMEDIA DATA STREAMS”, filed Mar. 28, 2013, which is a continuation of U.S. Utility application Ser. No. 11/492,381, entitled “METHOD AND SYSTEM FOR MEDIUM ACCESS CONTROL (MAC) LAYER SPECIALIZATION FOR VOICE AND MULTIMEDIA DATA STREAMS”, filed Jul. 25, 2006, issued as U.S. Pat. No. 8,411,581 on Apr. 2, 2013, both of which are hereby incorporated herein by reference in their entirety and made part of the present U.S. Utility Patent Application for all purposes.
  • This application also makes reference to:
  • U.S. Utility application Ser. No. 11/492,667, entitled “METHOD AND SYSTEM FOR CONTENT-AWARE MAPPING/ERROR PROTECTION”, filed on Jul. 25, 2006, issued as U.S. Pat. No. 8,917,674 on Dec. 23, 2014;
    U.S. Utility application Ser. No. 11/492,391, entitled “METHOD AND SYSTEM FOR PROVIDING VISUALLY RELATED CONTENT DESCRIPTION TO THE PHYSICAL LAYER”, filed on Jul. 25, 2006, abandoned;
    U.S. Utility application Ser. No. 11/492,721, entitled “METHOD AND SYSTEM FOR CONTENT-AWARE MAPPING/ERROR PROTECTION USING DIFFERENT SPATIAL STREAMS”, filed on Jul. 25, 2006, issued as U.S. Pat. No. 8,995,411 on Mar. 31, 2015; and
    U.S. Utility application Ser. No. 11/492,390, entitled “METHOD AND SYSTEM FOR REDUNDANCY-BASED DECODING OF VOICE CONTENT IN A WIRELESS LAN SYSTEM”, filed on Jul. 25, 2006, issued as U.S. Pat. No. 7,877,674 on Jan. 25, 2011, all of which are incorporated herein by reference in their entirety for all purposes.
  • FIELD OF THE INVENTION
  • Certain embodiments of the invention relate to data communications. More specifically, certain embodiments of the invention relate to a method and system for medium access control (MAC) layer specialization for voice and multimedia data streams.
  • BACKGROUND OF THE INVENTION
  • A network may comprise a plurality of communications media and communications devices that facilitate the transfer of information between a transmitting terminal and at least one receiving terminal. Information may be transmitted via a network in messages, packets, and/or frames. Various communication protocols may be utilized to facilitate the transfer of information in a network. Some transport layer data protocols may control the amount of information that may be transmitted during a time interval. The transmission control protocol (TCP) may be considered to be an example of one such protocol. The TCP may limit the amount of information that is transmitted during a time interval based on a congestion window and slow start. At the beginning of transmission of an information flow, the congestion window may be set to an initial value. This may result in a relatively small amount of information being transmitted from a transmitting terminal to a receiving terminal. The receiving terminal may subsequently communicate an acknowledgement upon receipt of the information that was transmitted by the transmitting terminal.
  • Upon receipt of the acknowledgement, the transmitting terminal may increase the value associated with the congestion window to a number larger than the initial value, and transmit subsequent information based on the larger value that is associated with the congestion window. This may result in a larger amount of information being transmitted than during a comparable time interval in which the value associated with the congestion window is smaller. The size of the congestion window may increase with the increase in the value associated with the congestion window. A larger congestion window may also result in a higher information transfer rate between the transmitting terminal and the receiving terminal. The receiving terminal may communicate subsequent acknowledgements upon receipt of subsequent information. The transmitting terminal may continue to increase the size of the congestion window upon receipt of a subsequent acknowledgement.
  • In an instance in which the transmitting terminal does not receive a corresponding acknowledgement to previously transmitted information, the transmitting terminal may determine that the receiving terminal did not receive the previously transmitted information. The transmitting terminal may retransmit, or resend, previously transmitted information for which a corresponding acknowledgement was not received. In addition, the transmitting terminal may determine that congestion may exist in the network resulting in the previously transmitted information not being received by the receiving terminal. The previously transmitted information may be considered by the transmitting terminal to be “lost” in the network. In response to a determination of congestion in the network, or network congestion, the transmitting terminal may also reduce the size of the congestion window. The reduction in the size of the congestion window may result in a reduction in the information transfer rate between the transmitting terminal and the receiving terminal. Once reduced, the size of the congestion window may subsequently begin to increase once again. Thus, a slow start recovery may be initiated at the transmitting terminal.
  • In some wireless communications networks, fading conditions within the wireless communications medium, and not congestion within the network, may result in transmitted information not being received by the receiving terminal. The fading conditions may be temporary, thus it may be undesirable for a transmitting terminal to enter a slow start state as a result of a temporary loss of data due to fading conditions within the wireless communications medium. In some systems, TCP may be utilized for the transmission of multimedia information, comprising voice, video, and/or data. The real time nature of multimedia information may make it undesirable for the transmitting terminal to enter a slow start state.
  • Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.
  • BRIEF SUMMARY OF THE INVENTION
  • A system and/or method is provided for medium access control (MAC) layer specialization for voice and multimedia data streams, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.
  • These and other advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.
  • BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS
  • FIG. 1 is a block diagram of exemplary communications circuitry that may be utilized in connection with an embodiment of the invention.
  • FIG. 2 illustrates an exemplary architecture for source layer optimization for transmitting data, in accordance with an embodiment of the invention.
  • FIG. 3 illustrates an exemplary MIMO architecture with feedback from a receiver to a transmitter, in accordance with an embodiment of the invention.
  • FIG. 4 is an exemplary flowchart illustrating message exchanges in a successful TCP communication, which may be utilized in connection with an embodiment of the invention.
  • FIG. 5 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication, which may be utilized in connection with an embodiment of the invention.
  • FIG. 6 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication for low priority level information, in accordance with an embodiment of the invention.
  • FIG. 7 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication for high priority level information, in accordance with an embodiment of the invention.
  • FIG. 8 is an exemplary flowchart illustrating exemplary steps for a system for MAC layer specialization for voice and multimedia data streams, in accordance with an embodiment of the invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • Certain embodiments of the invention may be found in a method and system for medium access control (MAC) layer specialization for voice and multimedia data streams. Aspects of the method comprise determining a number of attempts for transmitting one or more MAC frames. Aspects of the system may comprise a processor that enables determination of a number of attempts for transmitting one or more MAC frames. A maximum number for such attempts may be determined based on one or more priority levels associated with different portions of multimedia information being communicated via a wireless medium and contained within the one or more MAC frames.
  • FIG. 1 is a block diagram of exemplary communications circuitry that may be utilized in connection with an embodiment of the invention. With reference to FIG. 1, there is shown a memory processor 172, a transceiver 174, an RF front end 180, a plurality of receive antennas 176 a, . . . , 176 n, and a plurality of transmitting antennas 178 a, . . . , 178 n. The transceiver 174 may comprise a processor 182, a receiver 184, and a transmitter 186.
  • The memory 172 may enable storage and/or retrieval of information that may be transmitted via one or more transmitting antennas 178 a, . . . , 178 n, received via one or more receive antennas 176 a, . . . , 176 n, and/or storage of code that may enable control of the operation of the transceiver 174.
  • The processor 182 may enable digital receiver and/or transmitter functions in accordance with applicable communications standards. These functions may comprise, but are not limited to, tasks performed at lower layers in a relevant protocol reference model. These tasks may further comprise the physical layer convergence procedure (PLCP), physical medium dependent (PMD) functions, and associated layer management functions.
  • The receiver 184 may be enable digital receiver functions that may comprise, but are not limited to, fast Fourier transform processing, beamforming processing, equalization, demapping, demodulation control, deinterleaving, depuncture, and decoding. The transmitter 186 may enable digital transmitter functions that comprise, but are not limited to, coding, puncture, interleaving, mapping, modulation control, inverse fast Fourier transform processing, beamforming processing. The RF front end 180 may enable reception of analog RF signals via antennas 176 a, . . . , 176 n, converting the RF signal to baseband, and generating digital representations of the received analog baseband signals. The digital representation may be a complex quantity comprising I and Q components. The RF front end 180 may also transmit analog RF signals via an antenna 178 a, . . . , 178 n, converting a digital baseband signal to an analog RF signal.
  • In operation, the processor 182 may receive data from the receiver 184. The processor 182 may store received data to the memory 172 for subsequent analysis and/or processing. The processor 182 may retrieve information from the memory 172. The retrieved information may be transmitted via an RF channel by the transmitter 186. The processor 182 may associate one or more priority classes to the retrieved information. The transmitter 186 may process and transmit the information via the RF channel based on the corresponding priority classes.
  • FIG. 2 illustrates an exemplary architecture for source layer optimization for transmitting data, in accordance with an embodiment of the invention. Referring to FIG. 2, there is shown a processor 210 and a transmit block 215. The transmit block 215 may comprise a source encoder block 220, a memory block 222, a source layer multiplexer block 224, a PHY/MAC block 226, a cross-layer partitioner block 228, a parameter control block 230, and transmit antennas 232 a, . . . , 232 b.
  • The source encoder block 220 may comprise suitable logic, circuitry, and/or code that may be utilized to enable compression of data prior to transmission. For example, the compressed data may be video data in MPEG-4 format. The source encoder block 220 may also communicate information about the compressed data to the cross-layer partitioner block 228. The information communicated may relate to the type of compression. For example, if the compressed data comprises video data, the source encoder block 220 may communicate the specific type of compression, such as MPEG-1, MPEG-2, MPEG-4, H.261, H.263, or H.264. The source encoder block 220 may also communicate the type of chroma subsampling used, such as, for example, 4-4-4, 4-2-2, or 4-2-0 chroma subsampling.
  • The source layer multiplexer block 224 may comprise suitable logic, circuitry, and/or code that may be utilized to enable reading data from, for example, the memory block 222 and communicating various portions of the data to the PHY/MAC 226. The data may be split into the various portions according to information from the cross-layer partitioner block 228. The information from the cross-layer partitioner block 228 may comprise, for example, priority for the various portions of the data. The cross-layer partitioner block 228 may also indicate that portions of data with certain priority may be communicated via certain outputs of the source layer multiplexer block 224.
  • The PHY/MAC block 226 may comprise suitable logic, circuitry, and/or code that may be utilized to enable conversion of input data in a digital format to output suitably modulated analog data ready for transmission. For example, the PHY/MAC block 226 may apply a FEC code to the digital data. The PHY/MAC block 226 may also apply a specific RF modulation to the analog signal, which may have been converted from the digital data. The PHY/MAC block 226 may additionally communicate analog signals to different transmit antennas 232 a, . . . , 232 b, in a part of a multiple-input multiple-output (MIMO) architecture.
  • In an embodiment of the invention, the PHY/MAC block 226 may receive one or more streams of digital data. The PHY/MAC block 226 may then operate on the multiple streams as indicated by, for example, the parameter control block 230. Accordingly, the PHY/MAC block 226 may, for example, apply a specific FEC code to each digital stream. Each digital stream may then be converted to analog RF signal, which may be modulated by a specific RF modulation scheme. Each modulated RF signal may then be communicated to one or more antennas to be transmitted.
  • The cross-layer partitioner block 228 may comprise suitable logic, circuitry, and/or code that may be utilized to enable assigning a priority to portions of data in the memory block 222. The priority may be based on, for example, perceived importance of the information in the memory block 222. For example, if the data in the memory block 222 comprises video data relating to video frames, a portion of the data that comprises information about an entire frame, such as, example, an I-frame, may have a high priority. Other frames, such as, for example, P-frames may have a lower priority than I-frames since P-frames may depend on the I-frames for additional information. P-frames that depend on other primary P-frames may be, for example, assigned a lower priority than the P-frames that may only depend on I-frames. A B-frame that depends on a prior and a subsequent frame may be assigned, for example, a lowest priority. The number of priorities may be design and/or implementation dependent.
  • The cross-layer partitioner block 228 may also indicate to the source layer multiplexer block 224 that data with certain priorities may be communicated to the PHY/MAC block 226 via specific outputs of the source layer multiplexer block 224. The cross-layer partitioner block 228 may then communicate to the parameter control block 230 those operations that may be performed on the various streams of data communicated by the source layer multiplexer 224.
  • Specific streams of data may be communicated to specific transmit antennas. The cross-layer partitioner block 228 may have information regarding the propagation path from each transmit antenna 232 a, . . . , 232 b to a receive antenna, where data transmitted via one transmit antenna may be received with fewer bit errors, for example, than data transmitted by another transmit antenna. Accordingly, this information may be used to determine which data may be transmitted via which transmit antenna. The information regarding the propagation path for each transmit antenna may be generated, for example, from feedback information from the receiving devices. Alternatively, the information may be generated from feedback information from a receiver co-located with the transmit block 215. The information may be utilized for a method of MIMO transmission referred to as beamforming.
  • U.S. patent application Ser. No. 11/492,721, filed on Jul. 25, 2006, issued as U.S. Pat. No. 8,995,411 on Mar. 31, 2015, provides further information on beamforming, which is incorporated herein by reference in its entirety.
  • The parameter control block 230 may comprise suitable logic, circuitry, and/or code that may be utilized to enable controlling of various operations to the digital data in the PHY/MAC block 226. For example, the parameter control block 230 may determine the FEC code and/or the RF modulation that may be used by the PHY/MAC block 226 for specific portions of data. The parameter control block 230 may also determine which antennas may be used to transmit which portions of data by controlling routing of the data within the PHY/MAC block 226 to the specific antennas.
  • However, there may be other embodiments of the invention that route signals to specific antennas using other methods. For example, some embodiments of the invention may select the antenna used to transmit data by selecting the source layer multiplexer 224 output used to communicate data from the source layer multiplexer 224 to the PHY/MAC 226. Data communicated to the PHY/MAC 226 via specific outputs to the PHY/MAC 226 may be transmitted via specific transmit antennas. For example, the data, Output1, may be transmitted by the transmit antenna 232 a, and the data, Output2, may be transmitted by the transmit antenna 232 b.
  • In operation, the source encoder block 220 may compress data and store the compressed data in the memory block 222. For simplicity, the data may be assumed to be video data compressed using the MPEG-4 format, two priority levels may be used—a high priority level and a low priority level, and Output1 data and Output2 data may be transmitted by the transmit antennas 232 a and 232 b, respectively. The source encoder block 220 may communicate to the cross layer partitioner block 228 that the compressed data is video data using the MPEG-4 format. The source encoder block 220 may also communicate, for example, start and end memory addresses for the stored video data corresponding to a frame, the frame number, and the type of frame that may be stored. The type of frame may be, for example, I-frame, P-frame, and B-frame. Other information may also be communicated, such as, for example, the chroma subsampling format.
  • The cross layer partitioner block 228 may then determine a priority to assign to each frame. An exemplary priority level algorithm may assign a high priority for all I-frames and a low priority for all other frames. The priority for the video data in the memory block 222 may be communicated to the source layer multiplexer block 224. The source layer multiplexer 224 may read data from the memory block 222, and may output, for example, high priority data as Output1 and the low priority data as Output2.
  • The cross layer partitioner block 228 may also communicate to the parameter control block 230 the operations to be applied to each stream of data, namely, Output1 and Output2. For example, the parameter control block 230 may indicate that the high priority data, Output1, may have applied to it a forward error correction (FEC) code A that may have a greater overhead in the number of bits used than a FEC code B. However, using the FEC code A may allow a receiving unit to correct a larger number of faulty bits than when using the FEC code B.
  • The cross layer partitioner block 228 may also communicate to the parameter control block 230 to use, for example, quadrature phase shift keying (QPSK) RF modulation rather than 16 quadrature amplitude modulation (16 QAM) RF modulation for the high priority data Output1. The QPSK RF modulation may have a smaller data throughput than the 16 QAM RF modulation, however, the QPSK RF modulation may be more reliable for a given transmission environment. Additionally, the transmit antenna 232 a may exhibit more reliable transmission characteristics than the transit antenna 232 b. If the transmission environment changes such that the transmit antenna 232 b exhibits a more reliable transmission characteristics than the transmit antenna 232 a, then the cross layer partitioner block 228 may indicate that the higher priority data be output as Output2.
  • The cross layer partitioner block 228 may also take in to account feedback information from the receiving device to maximize throughput for transmission of the high priority and low priority data. This may allow, for example, the cross layer partitioner block 228 to select from a plurality of FEC codes and from a plurality of RF modulation schemes for a plurality of priority levels. Similarly, MIMO transmission may utilize beamforming, in which one antenna may be selected for transmission of particular stream of data, or a plurality of antennas may be selected for transmission of a particular stream of data.
  • Although feedback information from a receiving device may be used for transmission, the invention need not be so limited. For example, feedback data from a receiver that is co-located with the transmitting device may also be used. Accordingly, for example, the processor 210 may communicate the feedback data and/or instructions to the transmit block 215. For example, the processor 210 may process the feedback data from a co-located receiving device, and communicate information to the transmit block 215. The information may be used, for example, to control the operations on the data streams by the PHY/MAC block 226.
  • U.S. application Ser. No. 11/327,690 filed Jan. 6, 2006, provides a detailed description of beamforming, and feedback in a MIMO system, which is hereby incorporated herein by reference in its entirety.
  • Although an embodiment of the invention may have been described using a plurality of functional blocks, the invention need not be so limited. Accordingly, other embodiments of the invention may use different blocks that may encompass various functionalities.
  • FIG. 3 illustrates an exemplary MIMO architecture with feedback from a receiver to a transmitter, in accordance with an embodiment of the invention. Referring to FIG. 3, there is shown the transmitting terminal 312 and the receiving terminal 310, which may receive the data transmitted by the transmitting terminal 312. The transmitting terminal 312 may transmit signals via the transmit antennas 312 a and 312 b, and the receiving terminal may receive signals via the antennas 310 a and 310 b. The transmitting terminal 312 may generate the RF signals tx1 and tx2, which may be transmitted via the transmit antennas 312 a and 312 b, respectively. The transmitted RF signals may be represented by s1 and s2. The signals received by the receive antennas 310 a and 310 b may be represented by R1 and R2, respectively.
  • In operation, a receive antenna, for example, the receive antenna 310 a, may receive signals from a plurality of transmit antennas, for example, the transmit antennas 312 a and 312 b. In some instances, the transmit antennas 312 a and 312 b may transmit the same data. In other instances, the transmit antennas 312 a and 312 b may transmit different data. The receiving terminal 310 may process the received signals R1 and R2 to estimate what information may have been transmitted by the transmitting terminal 312. The receiving terminal 310 may also generate various signal metrics such as, for example, the SNR and bit error rate. The signal metrics may be fed back to the transmitting terminal 312.
  • For example, the transmitting terminal 312 may transmit different data via the transmit antennas 312 a and 312 b. The receiving terminal 310 may also process the received signal R1 for the data transmitted by the transmit antenna 312 a, and the received signal R2 for the data transmitted by the transmit antenna 312 b. Accordingly, if the bit error rate for the received signal R1 is less than the bit error rate for the received signal R2, this information may be fed back to the transmitting station 312. The transmitting station 312 may then assign, for example, the transmit antenna R1 for the high priority data and the transmit antenna R2 for the low priority data. Similarly, the bit error rate and other metrics fed back to the transmitting terminal 312 may be used by the transmitting terminal 312 to select, for example, different FEC codes and/or RF modulation schemes.
  • FIG. 4 is an exemplary flowchart illustrating message exchanges in a successful TCP communication, which may be utilized in connection with an embodiment of the invention. Referring to FIG. 4, there is shown a transmitting terminal 432 and a receiving terminal 430. The transmitting terminal may comprise a plurality of communication entities comprising a coordination function 432 a, a TCP entity 432 b, and a MAC entity 432 c. The receiving terminal may comprise a plurality of communication entities comprising a TCP entity 430 a, and a MAC entity 430 b.
  • FIG. 4 illustrates an exemplary exchange of messages from a TCP entity 432 b in a transmitting terminal 432 and a corresponding TCP entity 430 a in a receiving terminal 430. The messages may be utilized to communicate multimedia information, which may comprise voice, video and/or data information, for example. The messages may comprise TCP packets, and MAC frames, for example. A MAC frame may comprise a TCP packet by encapsulating the TCP packet, for example.
  • A MAC frame may be defined in various IEEE 802 documents and standards, for example. A TCP packet may be defined in various Internet Engineering Task Force (IETF) request for comments (RFC) documents and standards such as RFC 793, for example.
  • In step 402, the TCP entity 432 b may communicate a TCP packet 402 to the MAC entity 432 c. In step 404, the TCP entity 432 b may communicate information to the coordination function 432 a. The communicated information may comprise an indication of the TCP window size utilized by the transmitting terminal 432 for transmitting information to the receiving terminal 430, Snd.Win=M. M may indicate an amount of data, as measured in octets, for example. The variable M may represent a number whose value is greater than 1, for example. The communicated information may also comprise a start TCP timer indication. The TCP timer indication may indicate a start time for a time duration within which an acknowledgement is expected from the receiving terminal 430. Failure to receive an acknowledgement within the time duration may result in the TCP entity 432 b reaching a TCP timeout time instant, and subsequently entering a slow start state in its communications with the corresponding TCP entity 430 a. Prior to reaching the TCP timeout time instant, the TCP entity 432 b may attempt to retransmit the TCP packet (step 402) one or more times.
  • In step 406, the MAC entity 432 c may encapsulate the TCP packet (step 402) and communicate a MAC frame to the MAC entity 430 b. In step 408, the MAC entity 430 b may communicate a MAC acknowledgement frame to the MAC entity 432 c. Receipt of the MAC acknowledgement frame by the MAC entity 432 c may indicate that the MAC frame (step 406) was successfully received by the MAC entity 430 b. In step 410, the MAC entity 430 b may communicate a TCP packet to the TCP entity 430 a. The TCP packet (step 410) may be derived by de-encapsulation of the received MAC frame (step 406). The TCP packet (step 410) may substantially comprise the information contained in the TCP packet (step 402).
  • In step 412, the TCP entity 430 a may communicate a TCP and acknowledgement packet to the MAC entity 430 b. The TCP portion of the packet may comprise information being communicated from the receiving terminal 430 to the transmitting terminal 432, for example, feedback information. The acknowledgement portion of the packet may comprise information that enables the TCP entity 432 b to determine that the TCP packet (step 402) was successfully received by the TCP entity 430 a. In step 414, the MAC entity 430 b may encapsulate the TCP and acknowledgement packet (step 412) and communicate a MAC frame to the MAC entity 432 c. In step 416, the MAC entity 432 c may communicate a MAC acknowledgement frame to the MAC entity 430 b
  • In step 418, the MAC entity 432 c may communicate a TCP and acknowledgement packet to the TCP entity 432 b. The TCP and acknowledgement packet (step 418) may be derived by de-encapsulation of the received MAC frame (step 414). The TCP and acknowledgement packet (step 418) may substantially comprise the information contained in the TCP and acknowledgement packet (step 412). In step 420, the TCP entity 432 b may communicate information to the coordination function 432 a. The communicated information may comprise an indication of an updated TCP window size, Snd.Win=M+A. The variable A may represent a number whose value is greater than or equal to 0, for example. The communicated information may also comprise a stop TCP timer indication. The stop TCP timer indication may indicate that the timer, which was started in anticipation of an acknowledgement for the TCP packet (step 402), has been stopped.
  • FIG. 5 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication, which may be utilized in connection with an embodiment of the invention. Referring to FIG. 5, there is shown a transmitting terminal 432 and a receiving terminal 430. The transmitting terminal may comprise a plurality of communication entities comprising a coordination function 432 a, a TCP entity 432 b, and a MAC entity 432 c. The receiving terminal may comprise a plurality of communication entities comprising a MAC entity 430 a.
  • In step 502, the TCP entity 432 b may communicate a TCP packet 402 to the MAC entity 432 c. In step 504, the TCP entity 432 b may communicate information to the coordination function 432 a. The communicated information may comprise an indication of the TCP window size, Snd.Win=M. M may indicate an amount of data, as measured in octets, for example. The variable M may represent a number whose value is greater than 1, for example. The communicated information may also comprise a start TCP timer indication. The TCP timer indication may indicate a start time for a time duration within which an acknowledgement is expected from the receiving terminal 430.
  • In step 506, the MAC entity 432 c may encapsulate the TCP packet (step 502) and communicate a MAC frame to the MAC entity 430 a. In step 508, the MAC entity 432 c may communicate information to the coordination function 432 a. The communicated information may comprise a start MAC timer indication. The MAC timer indication may indicate a start time for a time duration within which an acknowledgement is expected from the receiving terminal 430. Failure to receive an acknowledgement within the time duration may result in the MAC entity 432 c abandoning attempts to communicate the MAC frame (step 506) to the receiving terminal 430. If the MAC 432 c fails to receive an acknowledgement within a retransmit time duration, the MAC 432 c may attempt to retransmit the MAC frame. The number of retransmission attempts may be determined by the contention window parameter CWwin=L. The variable L may represent a number whose value is greater than or equal to 0, for example. The number of retransmission attempts may occur during the time duration associated with the MAC timer (step 508).
  • In steps 510 a, . . . , 510 n, the MAC entity 432 c may perform a plurality of retransmission attempts for the MAC frame (step 506) based on the value for the contention window parameter CWwin=L. If an acknowledgement is not received in response to the transmitted MAC frame (step 506), or any of the retransmission attempts (steps 510 a, . . . , 510 n), in step 512 the MAC entity 432 c may communicate information to the coordination function 432 a. The communicated information may also comprise a stop MAC timer indication. The stop MAC timer indication may indicate that a MAC timer timeout has occurred.
  • In steps 514 a, . . . , 514 n, the TCP entity 432 b may perform a plurality of retransmission attempts for the TCP packet (step 502). The plurality of retransmission attempts may occur during the time duration associated with the TCP timer (step 504). In steps 516 a, . . . , 516 n, a plurality of MAC frames may be transmitted in response to the corresponding TCP packet retransmission attempts (514 a, 514 n).
  • If an acknowledgement is not received in response to the transmitted TCP packet (step 502), or any of the retransmission attempts (steps 514 a, . . . , 514 n), in step 518 the TCP entity 432 b may communicate information to the coordination function 432 a. The communicated information may also comprise a stop TCP timer indication. The stop TCP timer indication may indicate that a TCP timer timeout has occurred. The communicated information may also comprise an indication of an updated TCP window size, Snd.Win=1. The updated TCP window size Snd.Win=1 may indicate that the TCP entity 432 b has entered a slow start state.
  • In some conventional systems, the value for the contention window parameter, CWwin, may be set to the value CWwin=L without regard for the information content contained within the TCP packet (step 502). Consequently, the number of retransmission attempts by the MAC entity 432 c may occur without regard to the information content contained within the MAC frame (step 506).
  • In various embodiments of the invention, the value for the contention window parameter, CWwin, may be set based on a priority level associated with the information content contained within the MAC frame. For example, for information content associated with a high priority level, the contention window parameter may be set to a value CWwin=LHigh, or for information content associated with a low priority level, the contention window parameter may be set to a value CWwin=LLow, wherein LHigh>LLow. In addition, the response to a MAC timer timeout may be determined based on the assigned priority level associated with the information content contained within the MAC frame.
  • FIG. 6 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication for low priority level information, in accordance with an embodiment of the invention. Referring to FIG. 6, there is shown a transmitting terminal 632 and a receiving terminal 630. The transmitting terminal may comprise a plurality of communication entities comprising a coordination function 632 a, a source application entity 632 b, a TCP entity 632 c, and a MAC entity 632 d. The receiving terminal may comprise a plurality of communication entities comprising a MAC entity 630 a. Exemplary source application entities may comprise MPEG-4 encoders, database programs, and voice over IP (VOIP) encoders.
  • In step 602, the source application entity 632 b may communicate source information to the TCP entity 632 c. In step 604, the source application entity 632 b may communicate information to the coordination function 632 a. The communicated information may comprise an indication for the priority level=Low associated with the source information (step 602). In step 606, the TCP entity 632 c may communicate a TCP packet to the MAC entity 632 d. The TCP packet may comprise a sequence number associated with the TCP packet as indicated by Seg.Seq=P, where the variable P may represent a sequence number.
  • In step 608, the TCP entity 632 c may communicate information to the coordination function 632 a. The communicated information may comprise an indication of the TCP window size, Snd.Win=M. The communicated information may comprise a start TCP timer indication. The communicated information may also comprise an unacknowledged sequence number as indicated by Snd.Una=P. The unacknowledged sequence number may indicate a TCP packet (step 606) that was transmitted by the TCP entity 632 c, for which a corresponding acknowledgement has not been received, for example.
  • In step 610, the coordination function 632 a may communicate a value for the contention window parameter CWwin=LLow, which may be utilized by the MAC entity 632 d in connection with a MAC frame that may be transmitted by the MAC entity 632 d in response to receipt of the TCP packet (step 606). The value for the contention window parameter LLow may be determined based on the priority class (step 604). In step 612, the MAC entity 632 d may encapsulate the TCP packet (step 606) and communicate a MAC frame to the MAC entity 630 a. In step 614, the MAC entity 632 d may communicate information to the coordination function 632 a. The communicated information may comprise a start MAC timer indication.
  • In steps 616 a, . . . , 616 n, the MAC entity 632 d may perform a plurality of retransmission attempts for the MAC frame (step 612) based on the value for the contention window parameter CWwin=LLow. If an acknowledgement is not received in response to the transmitted MAC frame (step 612), or any of the retransmission attempts (steps 616 a, . . . , 616 n), in step 618 the MAC entity 632 d may communicate information to the coordination function 632 a. The communicated information may also comprise a stop MAC timer indication. The stop MAC timer indication may indicate that a MAC timer timeout has occurred.
  • In step 620, the coordination function 632 a may communicate a halt instruction to the TCP entity 632 c in association with the TCP packet (step 606). The TCP packet may be identified based on the unacknowledged sequence number Snd.Una=P (as in step 608). The halt instruction may instruct the TCP entity 632 c to suspend attempts to retransmit the unacknowledged TCP packet (step 606). The halt instruction may also instruct the TCP entity 632 c to suspend entry into a slow start state if an acknowledgement for the TCP packet (step 606) is not received. In step 622, the TCP entity 632 c may communicate information to the coordination function 632 a. The communicated information may comprise a reset TCP timer indication. The reset TCP timer indication may indicate that the TCP entity 632 c has ceased tracking a TCP timeout condition in connection with the TCP packet (step 606). The TCP timer may continue tracking a TCP timeout condition that may occur in connection with TCP packets that may have be transmitted by the TCP entity 632 c subsequent to transmission of the TCP packet (step 606). The communicated information may also comprise an indication of an updated TCP window size, Snd.Win=M+A. The variable A may represent a number whose value is greater than or equal to 0, for example.
  • FIG. 7 is an exemplary flowchart illustrating message exchanges in an unsuccessful MAC communication for high priority level information, in accordance with an embodiment of the invention. Referring to FIG. 7, there is shown a transmitting terminal 632 and a receiving terminal 630. The transmitting terminal may comprise a plurality of communication entities comprising a coordination function 632 a, a source application entity 632 b, a TCP entity 632 c, and a MAC entity 632 d. The receiving terminal may comprise a plurality of communication entities comprising a MAC entity 630 a.
  • In step 702, the source application entity 632 b may communicate source information to the TCP entity 632 c. In step 704, the source application entity 632 b may communicate information to the coordination function 632 a. The communicated information may comprise an indication for the priority level=High associated with the source information (step 702). In step 706, the TCP entity 632 c may communicate a TCP packet to the MAC entity 632 d. The TCP packet may comprise a sequence number associated with the TCP packet as indicated by Seg.Seq=P, where the variable P may represent a sequence number.
  • In step 708, the TCP entity 632 c may communicate information to the coordination function 632 a. The communicated information may comprise an indication of the TCP window size, Snd.Win=M. The communicated information may comprise a start TCP timer indication. The communicated information may also comprise an unacknowledged sequence number as indicated by Snd.Una=P. The unacknowledged sequence number may indicate a TCP packet (step 706) that was transmitted by the TCP entity 632 c, for which a corresponding acknowledgement has not been received, for example.
  • In step 710, the coordination function 632 a may communicate a value for the contention window parameter CWwin=LHigh, which may be utilized by the MAC entity 632 d in connection with a MAC frame that may be transmitted by the MAC entity 632 d in response to receipt of the TCP packet (step 706). The value for the contention window parameter LHigh may be determined based on the priority class (step 704). In step 712, the MAC entity 632 d may encapsulate the TCP packet (step 706) and communicate a MAC frame to the MAC entity 630 a. In step 714, the MAC entity 632 d may communicate information to the coordination function 632 a. The communicated information may comprise a start MAC timer indication.
  • In steps 716 a, . . . , 716 n, the MAC entity 632 d may perform a plurality of retransmission attempts for the MAC frame (step 712) based on the value for the contention window parameter CWwin=LHigh. If an acknowledgement is not received in response to the transmitted MAC frame (step 712), or any of the retransmission attempts (steps 716 a, . . . , 716 n), in step 718 the MAC entity 632 d may communicate information to the coordination function 632 a. The communicated information may also comprise a stop MAC timer indication. The stop MAC timer indication may indicate that a MAC timer timeout has occurred.
  • The time duration spanning the start MAC timer indication (step 714) and the stop MAC timer indication (step 718) may comprise a substantial portion of the TCP timeout duration, for example. The number of TCP retransmission attempts prior to a TCP timeout, in various embodiments of the invention, may be 0, and/or fewer in number than in some conventional systems as represented in steps 514 a, . . . , 514 n.
  • In step 720, the TCP entity 632 c may communicate information to the coordination function 632 a. The communicated information may also comprise a stop TCP timer indication. The stop TCP timer indication may indicate that a TCP timer timeout has occurred. The communicated information may also comprise an indication of an updated TCP window size, Snd.Win=1. The updated TCP window size Snd.Win=1 may indicate that the TCP entity 632 c has entered a slow start state.
  • FIG. 8 is an exemplary flowchart illustrating exemplary steps for a system for MAC layer specialization for voice and multimedia data streams, in accordance with an embodiment of the invention. Referring to FIG. 8, in step 802, priority levels may be assigned to source information. The priority levels may be assigned based on the information content associated with source information. In step 804, a number of MAC layer retransmission attempts associated with a transmitted MAC frame may be determined based on the priority levels. A high priority level may be associated with a value LHigh, while a low priority level may be associated with a value LLow, for example. In step 806, a response to a MAC layer timeout condition may be determined based on the priority levels. For example, for high priority level source information, a higher number of MAC layer retransmission attempts, LHigh, may be performed prior to a MAC timer timeout. When a MAC timer timeout occurs, a subsequent TCP timer timeout may occur causing the TCP layer entity to enter a slow start state. For low priority level source information, a lower number of MAC layer retransmission attempts, LLow, may be performed prior to a MAC time timeout. When a MAC timer timeout occurs, the coordination function may instruct the TCP layer entity to continue packet processing and not enter a slow start state in response to a failure to receive an acknowledgement from the previously transmitted TCP packet.
  • In various embodiments of the invention a number of retry attempts by the MAC layer entity 632 d may be based on a priority level associated with a video frame type contained with a MAC frame. I frames may carry full image information and may be associated with a high priority level, for example. Consequently, a greater number of MAC layer retry attempts may be performed. B frames may carry sub-picture information and motion vectors. The impact of loss of a B frame for video quality may be less than the impact of loss of an I frame. B frames may be associated with a low priority level, for example. Consequently, a lesser number of MAC layer retry attempts may be performed. If a MAC layer timeout occurs in connection with transmission and/or retransmission of B frame information, the coordination function 632 a may communicate an instruction, to the TCP entity 632 c, to skip the corresponding TCP packet.
  • Aspects of a system for medium access control (MAC) layer specialization for voice and multimedia data streams may comprise a processor 210 that enables determination of a number of attempts for transmitting one or more MAC frames based on a corresponding one or more of a plurality of priority levels associated with different portion of multimedia information. The number of attempts may occur within a time duration associated with a transmission control protocol (TCP) packet corresponding to the one or more MAC frames. The TCP packet may be encapsulated by utilizing a corresponding one or more MAC frames. The MAC frames may be transmitted by a transmitting terminal 632 to a receiving terminal 630 via a wireless medium. A maximum number of attempts for transmitting the one or more MAC frames may occur within a timeout period associated with the TCP packet. The timeout period may comprise a time duration within which an acknowledgement in response to transmitting the TCP packet is expected from the receiving terminal 630.
  • In another aspect of the system, the processor 210 may enable a TCP entity 632 c to cease attempts to retransmit a TCP packet subsequent to a time duration associated with the one or more MAC frames based on the one or more of the plurality of priority levels. The time duration may represent a timeout period associated with the MAC frame during which the maximum number of attempts for transmitting the MAC frame may be performed. The processor 210 may instruct the TCP entity 632 c to stop a timer associated with the TCP packet. The instruction to stop the timer associated with the TCP packet may be in connection with receipt of a skip instruction from a coordination function 632 a. The TCP entity 632 c may continue to measure time duration associated with a subsequent TCP packet and/or previous TCP packet. The subsequent TCP packet and/or previous TCP packet may have been transmitted at least once at the time instant in which timer associated with the TCP packet was stopped. The TCP entity 632 c may not enter a slow start state based on failure to receive an acknowledgement in response to transmitting and/or retransmitting the TCP packet. The slow start state may be defined based on TCP specifications, for example.
  • In another aspect of the invention, the processor 210 may enable one or more attempts to retransmit a TCP packet subsequent to a time duration associated with the one or more MAC frames based on the one or more of the plurality of priority levels. The TCP entity 632 c may attempt to transmit the TCP packet subsequent to a MAC timeout. The processor 210 may enable entry of a slow start state based on a failure to receive an acknowledgement in response to transmitting and/or retransmitting the TCP packet.
  • Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
  • The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
  • While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.

Claims (20)

What is claimed is:
1. A method comprising:
receiving, by use of a processor, video data for transmission from a radio frequency (RF) front end that is coupled to a plurality of transmission antennas, the video data including a frame structure having I frames, P frames and B frames;
assigning, by use of the processor, a priority level associated with the video data in accordance with the frame structure so that I frames are assigned a high priority level and B frames are assigned a low priority level;
determining, by use of the processor, a transmission window based on the priority level associated with the frame structure, wherein the priority level determines a time duration of the transmission window;
assigning one or more transmission antennas based on the priority level associated with the frame structure to transmit the video data;
transmitting and retransmitting the video data in accordance with a transmission state until an acknowledgement is received from a target device receiving the video data;
when the time duration of the transmission window is reached without receiving the acknowledgement,
terminating retransmission of the video data; and
determining an updated transmission state, based on the on the priority level and triggered by determining the time duration of the transmission window is reached without receiving the acknowledgement.
2. The method of claim 1, wherein the time duration of the transmission window determines a number of times the video data is retransmitted when the acknowledgment is not received from the target device.
3. The method of claim 1, wherein the video data is transmitted in a medium access control (MAC) frame.
4. The method of claim 3, wherein the video data is sent as a transmission control protocol (TCP) packet.
5. The method of claim 1, further comprising setting a timer to determine when the time duration of the transmission window is reached.
6. The method of claim 5, wherein the processor reverts to a start state when video data transmission is terminated due to reaching end of the time duration.
7. The method of claim 1, wherein the P frames are assigned an intermediate priority level.
8. A method comprising:
receiving, by use of a processor, video data for transmission from a radio frequency (RF) front end that is coupled to a plurality of transmission antennas, the video data including a frame structure having I frames, P frames and B frames;
assigning, by use of the processor, a priority level associated with the video data in accordance with the frame structure so that I frames are assigned a high priority level and B frames are assigned a low priority level;
determining, by use of the processor, a number of times the video data is to be transmitted based on the priority level, wherein the priority level determines the number of times the video data is retransmitted;
assigning one or more transmission antennas based on the priority level to transmit the video data;
transmitting the data to a target device in accordance with a transmission state until an acknowledgement of data reception is received from a target device; and
when the number of times the video data is transmitted is reached without receiving the acknowledgement,
terminating retransmission of the video data; and
determining an updated transmission state, based on the on the priority level and triggered by determining the number of times the video data is transmitted is reached without receiving the acknowledgement.
9. The method of claim 8, wherein determining an updated transmission state, based on the on the priority level includes:
determining the updated transmission state to be a slow transmission state when the priority level associated with the video data corresponds to the high priority level.
10. The method of claim 9, wherein determining an updated transmission state, based on the on the priority level further includes:
determining the updated transmission state to be the transmission state when the priority level associated with the video data corresponds to the low priority level.
11. The method of claim 8, further comprising setting a timer to determine when the number is reached.
12. The method of claim 11, wherein the processor reverts to a start state when data transmission is terminated due to reaching the number of times video data is to be transmitted.
13. The method of claim 8, wherein the P frames are assigned an intermediate priority level.
14. The method of claim 13, wherein the video data includes associated audio data.
15. An apparatus comprising:
a radio frequency (RF) front end operable to couple to a plurality of transmission antennas; and
a processor coupled to the RF front end, wherein the processor is configured to:
assign a priority level associated with video data to be transmitted by the RF front end, the video data including a frame structure having I frames, P frames and B frames and wherein the priority level is associated with the video data in accordance with the frame structure so that I frames are assigned a highest priority level and B frames are assigned a lowest priority level;
determine a transmission window based on the priority level in accordance with the frame structure, wherein the priority level determines a time duration of the transmission window;
assign one or more transmission antennas based on the priority level to transmit the video data;
cause transmission and retransmission of the video data in accordance with a transmission state until an acknowledgement is received from a target device receiving the video data; and
when the time duration of the transmission window is reached without receiving the acknowledgement, terminating retransmission of the video data, and determining an updated processor state based on the on the priority level and triggered by determining the time duration of the transmission window is reached without receiving the acknowledgement.
16. The apparatus of claim 15, wherein the time duration of the transmission window determines a number of times the video data is retransmitted when the acknowledgment is not received from the target device.
17. The apparatus of claim 15, wherein the video data is transmitted in a medium access control (MAC) frame.
18. The apparatus of claim 17, wherein the video data is sent as a transmission control protocol (TCP) packet.
19. The apparatus of claim 15, wherein the processor is operable to set a timer to determine when the time duration of the transmission window is reached.
20. The apparatus of claim 15, wherein the P frames are assigned an intermediate priority level.
US14/795,248 2006-07-25 2015-07-09 Method and system for medium access control (mac) layer specialization for voice and multimedia data streams Abandoned US20150312158A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/795,248 US20150312158A1 (en) 2006-07-25 2015-07-09 Method and system for medium access control (mac) layer specialization for voice and multimedia data streams

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US11/492,381 US8411581B2 (en) 2006-07-25 2006-07-25 Method and system for medium access control (MAC) layer specialization for voice and multimedia data streams
US13/852,749 US20130215878A1 (en) 2006-07-25 2013-03-28 Method and system for medium access control (MAC) layer specialization for voice and multimedia data streams
US14/795,248 US20150312158A1 (en) 2006-07-25 2015-07-09 Method and system for medium access control (mac) layer specialization for voice and multimedia data streams

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US13/852,749 Continuation US20130215878A1 (en) 2006-07-25 2013-03-28 Method and system for medium access control (MAC) layer specialization for voice and multimedia data streams

Publications (1)

Publication Number Publication Date
US20150312158A1 true US20150312158A1 (en) 2015-10-29

Family

ID=38986151

Family Applications (3)

Application Number Title Priority Date Filing Date
US11/492,381 Expired - Fee Related US8411581B2 (en) 2006-07-25 2006-07-25 Method and system for medium access control (MAC) layer specialization for voice and multimedia data streams
US13/852,749 Abandoned US20130215878A1 (en) 2006-07-25 2013-03-28 Method and system for medium access control (MAC) layer specialization for voice and multimedia data streams
US14/795,248 Abandoned US20150312158A1 (en) 2006-07-25 2015-07-09 Method and system for medium access control (mac) layer specialization for voice and multimedia data streams

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US11/492,381 Expired - Fee Related US8411581B2 (en) 2006-07-25 2006-07-25 Method and system for medium access control (MAC) layer specialization for voice and multimedia data streams
US13/852,749 Abandoned US20130215878A1 (en) 2006-07-25 2013-03-28 Method and system for medium access control (MAC) layer specialization for voice and multimedia data streams

Country Status (1)

Country Link
US (3) US8411581B2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190268102A1 (en) * 2018-02-26 2019-08-29 Gainspan Corporation System and method for improving efficiency of wirelessly transmitting video packets
CN112134657A (en) * 2020-09-12 2020-12-25 安阳师范学院 Two-way asynchronous message transmission method based on perception and retransmission

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103414917B (en) 2006-09-26 2017-04-05 利弗有限公司 Distance transmission system
US20100005178A1 (en) * 2006-10-24 2010-01-07 Catalin Sindelaru Method and system for firewall friendly real-time communication
US9154247B2 (en) * 2008-01-23 2015-10-06 Liveu Ltd. Live uplink transmissions and broadcasting management system and method
PL2249599T3 (en) 2008-02-01 2020-03-31 Optis Wireless Technology, Llc Communication terminal and base station
US8341286B1 (en) 2008-07-31 2012-12-25 Alacritech, Inc. TCP offload send optimization
CA2737107C (en) * 2010-04-13 2019-08-27 Jingyuan Wang Tcp congestion control for heterogeneous networks
WO2012078082A1 (en) * 2010-12-07 2012-06-14 Telefonaktiebolaget L M Ericsson (Publ) Method for enabling traffic acceleration in a mobile telecommunication network
US8787966B2 (en) 2012-05-17 2014-07-22 Liveu Ltd. Multi-modem communication using virtual identity modules
EP2684398A4 (en) 2012-05-17 2015-05-13 Liveu Ltd Multi-modem communication using virtual identity modules
EP3897027B1 (en) * 2012-09-28 2024-02-14 Juniper Networks, Inc. Methods and apparatus for controlling wireless access points
US9980171B2 (en) 2013-03-14 2018-05-22 Liveu Ltd. Apparatus for cooperating with a mobile device
US9369921B2 (en) 2013-05-31 2016-06-14 Liveu Ltd. Network assisted bonding
US9338650B2 (en) 2013-03-14 2016-05-10 Liveu Ltd. Apparatus for cooperating with a mobile device
CN103795643B (en) * 2014-01-28 2017-02-15 广西大学 Method for processing synchronous priority bursty flow in data center network
US10986029B2 (en) 2014-09-08 2021-04-20 Liveu Ltd. Device, system, and method of data transport with selective utilization of a single link or multiple links
US9405706B2 (en) * 2014-09-25 2016-08-02 Intel Corporation Instruction and logic for adaptive dataset priorities in processor caches
DE102015216886A1 (en) * 2015-09-03 2017-03-09 Robert Bosch Gmbh Method, device and computer program for operating a data processing system
US11088947B2 (en) 2017-05-04 2021-08-10 Liveu Ltd Device, system, and method of pre-processing and data delivery for multi-link communications and for media content
US11873005B2 (en) 2017-05-18 2024-01-16 Driveu Tech Ltd. Device, system, and method of wireless multiple-link vehicular communication

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040030790A1 (en) * 2002-08-07 2004-02-12 Khiem Le Data communication method, system, and transmitter and receiver constituting the system
US20050053044A1 (en) * 2003-09-10 2005-03-10 Martin Alm Packet transmission in an adaptive antenna system
US20060034286A1 (en) * 2004-07-29 2006-02-16 Koning G P High performance TCP for systems with infrequent ACK
US20060140121A1 (en) * 2004-12-29 2006-06-29 Kakani Naveen K Optimization of a TCP connection
US20070091900A1 (en) * 2005-10-20 2007-04-26 Nokia Corporation Prioritized control packet delivery for transmission control protocol (TCP)
US20080256272A1 (en) * 2004-01-30 2008-10-16 Telefonaktiebolaget Lm Ericsson Packet Scheduling for Data Stream Transmission
US7573820B2 (en) * 2005-06-29 2009-08-11 Intel Corporation Techniques to control data transmission for a wireless system

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6725270B1 (en) * 1999-05-21 2004-04-20 Advanced Micro Devices, Inc. Apparatus and method for programmably modifying a limit of a retry counter in a network switch port in response to exerting backpressure
US6778509B1 (en) * 1999-11-19 2004-08-17 Hughes Electronics Corporation MAC layer protocol for a satellite based packet switched services
EP1361690B1 (en) * 2000-03-02 2006-01-11 Matsushita Electric Industrial Co., Ltd. Method and apparatus for retransmitting data packets based on channel conditions
EP1301041A1 (en) * 2001-10-05 2003-04-09 Matsushita Electric Industrial Co., Ltd. Video data transmission method and apparatus
US6909753B2 (en) 2001-12-05 2005-06-21 Koninklijke Philips Electronics, N.V. Combined MPEG-4 FGS and modulation algorithm for wireless video transmission
JP5054377B2 (en) * 2003-06-06 2012-10-24 メッシュネットワークス インコーポレイテッド Systems and methods for achieving fairness and service differentiation in ad hoc networks
US7426181B1 (en) * 2004-03-26 2008-09-16 Packeteer, Inc. Slow-start adaptive mechanisms to improve efficiency of bandwidth allocation
WO2005119969A1 (en) * 2004-06-02 2005-12-15 Matsushita Electric Industrial Co., Ltd. Radio transmission method
US7542478B1 (en) * 2004-06-25 2009-06-02 Meshnetworks, Inc. System and method for rate limiting in multi-hop wireless ad hoc networks
US7965639B2 (en) * 2005-03-14 2011-06-21 Sharp Laboratories Of America, Inc. Dynamic adaptation of MAC-layer retransmission value
EP1871030B1 (en) * 2005-04-15 2012-12-19 NTT DoCoMo, Inc. Packet transmission control device, and packet transmission control method

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040030790A1 (en) * 2002-08-07 2004-02-12 Khiem Le Data communication method, system, and transmitter and receiver constituting the system
US20050053044A1 (en) * 2003-09-10 2005-03-10 Martin Alm Packet transmission in an adaptive antenna system
US20080256272A1 (en) * 2004-01-30 2008-10-16 Telefonaktiebolaget Lm Ericsson Packet Scheduling for Data Stream Transmission
US20060034286A1 (en) * 2004-07-29 2006-02-16 Koning G P High performance TCP for systems with infrequent ACK
US20060140121A1 (en) * 2004-12-29 2006-06-29 Kakani Naveen K Optimization of a TCP connection
US7573820B2 (en) * 2005-06-29 2009-08-11 Intel Corporation Techniques to control data transmission for a wireless system
US20070091900A1 (en) * 2005-10-20 2007-04-26 Nokia Corporation Prioritized control packet delivery for transmission control protocol (TCP)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190268102A1 (en) * 2018-02-26 2019-08-29 Gainspan Corporation System and method for improving efficiency of wirelessly transmitting video packets
US10700818B2 (en) * 2018-02-26 2020-06-30 Gainspan Corporation System and method for improving efficiency of wirelessly transmitting video packets
CN112134657A (en) * 2020-09-12 2020-12-25 安阳师范学院 Two-way asynchronous message transmission method based on perception and retransmission

Also Published As

Publication number Publication date
US8411581B2 (en) 2013-04-02
US20080025210A1 (en) 2008-01-31
US20130215878A1 (en) 2013-08-22

Similar Documents

Publication Publication Date Title
US8411581B2 (en) Method and system for medium access control (MAC) layer specialization for voice and multimedia data streams
CN107508655B (en) Self-adaptive end-to-end network coding transmission method
US7573820B2 (en) Techniques to control data transmission for a wireless system
US7904777B2 (en) Method and system for generating block acknowledgements in wireless communications
US8144608B2 (en) Method and system for medium access control (MAC) rate selection
EP2638650B1 (en) Packet-level erasure protection coding in aggregated packet transmissions
US7562277B2 (en) Data transmitting/receiving system and method thereof
JP4454320B2 (en) Transmission apparatus, transmission control program, and transmission method
JP5425397B2 (en) Apparatus and method for adaptive forward error correction
US8132071B2 (en) Transmitting device, receiving device, packet transmission method, packet reception method, and programs for same
US9166734B2 (en) Method and device for frame aggregation transmission of wireless network system
US8495474B2 (en) Method and system for data transmission in a data network
US7668102B2 (en) Techniques to manage retransmissions in a wireless network
KR100750170B1 (en) Method and apparatus for transmitting data frame efficiently in communication network
JP2003521155A (en) Wireless network system and method
US20100165856A1 (en) Cross-layer optimization in multimedia communications
CN102013962B (en) Data transmission method and equipment
EP1873994A1 (en) Quality of service securing method and apparatus
KR100851918B1 (en) Network-adaptive Data Transmission Method, Data Transmission System, Data Sender, and Data Receiver Therefor
Chen et al. Multi-stages hybrid ARQ with conditional frame skipping and reference frame selecting scheme for real-time video transport over wireless LAN
Tsai et al. Dynamical combination of byte level and sub-packet level FEC in HARQ mechanism to reduce error recovery overhead on video streaming over wireless networks
US20230231787A1 (en) Communication method and an apparatus
KR20220124031A (en) An electronic device for transceiving video packet and operating method thereof
Kliazovich et al. Context-aware receiver-driven retransmission control in wireless local area networks

Legal Events

Date Code Title Description
AS Assignment

Owner name: BROADCOM CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HONARY, HOOMAN;FISCHER, MATTHEW;REEL/FRAME:036077/0071

Effective date: 20060404

AS Assignment

Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA

Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001

Effective date: 20160201

Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH

Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001

Effective date: 20160201

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD., SINGAPORE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001

Effective date: 20170120

Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001

Effective date: 20170120

AS Assignment

Owner name: BROADCOM CORPORATION, CALIFORNIA

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041712/0001

Effective date: 20170119