EP3672137B1 - Correction d'erreurs pour une allocation de ressources constantes - Google Patents

Correction d'erreurs pour une allocation de ressources constantes Download PDF

Info

Publication number
EP3672137B1
EP3672137B1 EP20153689.3A EP20153689A EP3672137B1 EP 3672137 B1 EP3672137 B1 EP 3672137B1 EP 20153689 A EP20153689 A EP 20153689A EP 3672137 B1 EP3672137 B1 EP 3672137B1
Authority
EP
European Patent Office
Prior art keywords
persistent
map
client station
base station
allocation
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.)
Active
Application number
EP20153689.3A
Other languages
German (de)
English (en)
Other versions
EP3672137A1 (fr
Inventor
Yair Bourlas
Kirupairaj Asirvatham
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.)
Quarterhill Inc
Original Assignee
WiLAN Inc
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 WiLAN Inc filed Critical WiLAN Inc
Priority to EP23151300.3A priority Critical patent/EP4216477A1/fr
Publication of EP3672137A1 publication Critical patent/EP3672137A1/fr
Application granted granted Critical
Publication of EP3672137B1 publication Critical patent/EP3672137B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H04L5/0082—Timing of allocation at predetermined intervals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0466—Wireless resource allocation based on the type of the allocated resource the resource being a scrambling code
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/11—Semi-persistent scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H04L1/0003—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes
    • H04L1/0004—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes applied to control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H04L1/001—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding applied to control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the invention relates to the field of wireless communications. More particularly, the invention relates to the field of resource allocation in a wireless communication system.
  • Wireless communication systems may support discontinuous transmission in which the various parties to a communication link use resources only as needed. Limiting the allocation and consumption of resources to those devices actively engaged in communications increases the efficiency of a wireless communication system. However, each device may need to request an allocation of resources before it is granted the opportunity to communicate. The request and grant of communication resources can itself consume a large amount of resources that otherwise could be used to support additional users or provide increased bandwidth to active users.
  • NTT DoCoMo, Inc. "Issues regarding persistent scheduling", 3GPP TSG RAN WG2 #59, 20th - 24th August 2007, Athens, Greece addresses some details regarding the persistent resource allocation scheme for LTE in both downlink and uplink.
  • DL downlink
  • UL uplink
  • the allocation When the base station assigns a standard non-persistent downlink or uplink allocation for use by a client station, the allocation is valid for a predetermined frame, such as a frame in which the allocation is granted or the frame following the frame in which the allocation is granted, depending on the allocation relevancy. In contrast, when a base station assigns a persistent downlink or uplink allocation to a client station, the allocation typically remains valid for multiple future downlink or uplink frames. Thus, the client station does not need to repeat a request for uplink resources periodically over a long series of frames. Nor does the base station need to expressly and repeatedly identify a downlink or uplink resource allocation in a series of downlink or uplink map information element (IE) messages when the base station implements persistent resource allocation.
  • IE downlink map information element
  • a client station requests a persistent downlink or uplink allocation when the client station is producing a data stream which is predictably periodic and in which the packets are generally fixed in size. For example, when a client station has established a voice over Internet protocol (VOIP) connection, a steady stream of voice packets will typically be produced.
  • the base station can verify that the downlink or uplink resource request meets the criteria for persistent resource allocation and allocate persistent downlink or uplink resources as part of a persistent downlink or uplink map information element (IE) message that is transmitted to the client stations in the system.
  • IE map information element
  • the base station has the ability to determine that a client station is a candidate for a persistent downlink or uplink resource allocation. For example, the base station can determine that a client station is a candidate for a persistent downlink or uplink resource allocation based on one or more parameters.
  • the parameters can include, for example, repeated requests for uplink resource allocations from the client station, the consistency of the resource allocation requested, stability of characteristics of a wireless channel between the base station and the client station, knowledge of the packet arrival distribution, and the type of connection. As an example, if the connection is in support of VOIP communication, the base station typically knows that the packet arrival pattern is a good candidate for persistent resource allocation.
  • the persistent allocation remains dedicated to the client station in future frames until a predetermined terminating event, such as a passage of time, passage of a predetermined number of frames, the base station notifying the client station that the resource has been deallocated, a base station reallocating all or part of resources allocated to another client station, and the like or some combination thereof.
  • the base station may deallocate a persistent resource by sending a revised persistent downlink or uplink map IE which no longer allocates a persistent resource to the client station or reallocates resources to the client station.
  • the base station sends an express deallocation message.
  • the base station can group the client station resource request and resource allocation to any one of multiple persistence groups.
  • the base station can select a persistence group for a particular client station based on such factors as a traffic arrival pattern, a power class of the client station, load balancing at the base station, and the like or some combination thereof.
  • the base station can allocate uplink resources to the client stations in each of the persistence groups such that members of each persistence group transmit in a frame distinct from any other persistence group. Similarly, the base station can allocate persistent resources to the client stations in each of the persistent groups such that members of each persistence group transmit in a frame distinct from any other persistence group. If the base station allocates both persistent downlink and uplink resources to a particular client station, the persistence groups will coincide. For example, each persistence group can be associated with a group cycle number and a persistent resource allocation can be valid for uplink frames associated with the group cycle index.
  • the persistence groups can be time cycled in a round-robin schedule in order to provide uniform access and a uniform rate across the multiple persistence groups.
  • a simple implementation utilizes the frame number and group cycle index to identify the active persistence group associated with a particular frame.
  • the active persistence group can be identified by determining the modulo function of the frame number and the total number of persistence groups, typically notated as MOD (frame number, N), and comparing the result against the group cycle index, where N represents the number of persistence groups.
  • the modulo operation returns the remainder of division of one number by another. Given two numbers, a (the dividend) and x (the divisor), mod (a,x) is the remainder, of division of a by x. For instance, the expression MOD (7,3) would evaluate to 1, while MOD (9,3) would evaluate to 0.)
  • the client station need not have any knowledge of its group cycle index and only needs to know the number of persistence groups, N.
  • the client station can determine its group cycle index by determining the value of MOD (frame number, N) for the first frame number for which it is allocated persistent downlink or uplink resources.
  • Groups may also be identified and associated with client stations explicitly by communicating a period parameter in the persistent allocation IE.
  • an express indication of the period of the persistent allocation is sent in the UL-MAP information element, thus eliminating the need for the use of a modulo function.
  • the base station can distinguish data coming from the various client stations according to time (number of symbols) and frequency (number of subcarriers). Of course in other systems, the base station may distinguish data coming from the various client stations according to some other physical layer (PHY) characteristics associated with the system.
  • PHY physical layer
  • the base station typically does not assign individual physical layer units to the client stations. Instead, the physical layer units are grouped together into "allocation units.”
  • the base station assigns resources to the client stations by specifying allocation units, rather than designating individual physical layer units.
  • An allocation unit can be, for example, a combination of a predetermined number of subcarriers and symbols.
  • a minimum allocation unit is referred to as a "slot," and a slot encompasses a predetermined number of subcarriers in one or more OFDMA symbols.
  • Each frame includes a downlink subframe and uplink subframe.
  • the downlink subframe typically includes link management transmissions (such as synchronization signals and the like), overhead channels, a number of downlink allocation units for carrying user data from the base station to the client stations as well as other types of overhead and data transmissions.
  • the uplink subframe includes many of these same categories of transmissions, including uplink allocation units for carrying user data from the client station to the base station and control signaling channels for system control, administration and the like.
  • Modulation is the process of encoding information onto a signal for transmission.
  • Many modulation schemes are well known in the art including binary phased shift keying (BPSK), quadrature phase shift keying (QPSK) and quadrature amplitude modulation (QAM.) Modulation schemes differ from one another according to the amount of data carried by any one symbol. Higher order modulation schemes carry more data per symbol. For example, a 16 QAM symbol carries 4 bits of data per symbol while BPSK modulation carries only one bit of data per symbol.
  • error correction coding such as forward error correction (FEC)
  • FEC forward error correction
  • the code rate typically refers to the length of the uncoded information divided by the length of the resulting encoded information.
  • the redundancy can be used to correct for errors which are introduced by the wireless channel.
  • the effectiveness of a coding scheme is measured in terms of coding gain, which can be expressed as the difference between the signal to noise level required to reach the same bit error rate level for encoded and uncoded data.
  • Modern error correction coding techniques provide substantial coding gains.
  • the use of error correction coding typically decreases the effective rate at which data is transmitted over the channel. Therefore, transmissions using codes having higher redundancy rates are more robust, but less efficient than transmissions using codes having lower redundancy rates.
  • the IEEE 802.16e standard and its progeny define a variety of modulation and coding scheme (MCS) combinations.
  • MCS modulation and coding scheme
  • the MCS specifies a type of modulation as well as a type of forward error correction which the client station is to use on the uplink transmission.
  • the MCS combinations accommodate the large variation in performance associated with the client stations scattered throughout the coverage area. Proper selection of an MCS combination is important to both the efficiency and performance of a wireless link.
  • the base station When the base station assigns an allocation unit to a specific client station, it also specifies the MCS combination to be used on the allocation. This may be typical for both persistent and nonpersistent resource allocations.
  • the base station sends a persistent resource allocation, generally it need not resend the resource allocation unless a change to the downlink or uplink resource allocations makes it advantageous to resend the resource allocation.
  • a new full or partial persistent uplink map IE may be sent when there is a need to change the size of the allocation. Such a size change may occur if the operating conditions of the client station assigned a persistent allocation are altered or otherwise change to such a degree that a new MCS combination is advantageous. Therefore the base station typically resends the persistent downlink or uplink map IE to identify the new MCS combination and assign the client station fewer or more allocation units as appropriate.
  • a new persistent downlink or uplink map IE may be sent when a voice activity state changes, thus changing the rate of occurrence of the persistent allocation.
  • the base station typically resends the persistent uplink map IE if requested by the client station to do so, and may alter a persistent downlink map accordingly.
  • the base station can be configured to periodically resend the persistent downlink or uplink map IE even if no changes have occurred to permit client stations in the base station coverage area to verify the persistent downlink and uplink resource allocations.
  • persistent downlink and uplink map IE may be resent, some of which are discussed below.
  • OFDMA Orthogonal Frequency Division Multiple Access
  • FIG. 1 is a simplified functional block diagram of a wireless communication system 100.
  • the wireless communication system 100 includes a plurality of base stations 1 10a, 1 10b, each supporting a corresponding service or coverage area 112a, 112b.
  • Each base station 110a and 110b can be coupled to one another and a supporting network (not shown) via a combination of a wired and wireless links.
  • the base station for example 110a, can communicate with wireless devices within its coverage area 112a.
  • the first base station 110a can wirelessly communicate with a first client station 130a and a second client station 130b within the coverage area 112a over a downlink 116a and an uplink 116b.
  • the base stations 110a and 110b can be configured as cellular base station transceiver subsystems, gateways, access points, radio frequency (RF) repeaters, frame repeaters, nodes or any wireless network entry point
  • RF radio frequency
  • the base stations 110a and 110b also communicate with each other and a network control module (not shown) over backhaul links (also not shown.)
  • the backhaul links may include wired and wireless communication links.
  • the network control module provides network administration and coordination as well as other overhead, coupling and supervisory functions for the wireless communication system.
  • the network control module also couples the wireless link system to other communications systems such as the Internet, convention telephone systems and the like.
  • client stations 130a and 130b can be mobile, nomadic or stationary units.
  • the client stations 130a and 130b are often referred to as, for example, mobile stations, mobile units, subscriber stations, wireless terminals or the like.
  • a client station can be, for example, a wireless handheld device, a vehicle mounted device, a portable device, client premise equipment, a fixed location device, a wireless plug-in accessory or the like.
  • a client station can take the form of a handheld computer, notebook computer, wireless telephone, personal digital assistant, wireless email device, personal media player, meter reading equipment or the like in may include a display mechanism, microphone, speaker and memory.
  • the wireless communication system 100 is configured for Orthogonal Frequency Division Multiple Access (OFDMA) communications.
  • OFDMA Orthogonal Frequency Division Multiple Access
  • the wireless communication system 100 can be configured to substantially comply with a standard system specification, such as IEEE 802.16e or some other wireless standard.
  • the wireless communication system 100 can support the persistent downlink or uplink resource allocation described herein as an extension to the system standard or as part of a system standard.
  • the wireless communication system 100 is not limited to an OFDMA system, and use of persistent downlink or uplink resource allocation described herein is not limited to application in OFDMA systems.
  • the description is offered for the purposes of providing a particular example of the operation of persistent downlink or uplink resource allocation in a wireless communication environment.
  • Each base station can supervise and control the communications within its respective coverage area 112a.
  • Each active client station for example 130a, registers with the base station 110a upon entry into the coverage area 112a.
  • the client station 130a can notify the base station 110a of its presence upon entry into the coverage area 1 12a, and the base station 110a can interrogate the client station 130a to determine the capabilities of the client station 130a.
  • the base station 110a assigns one or more temporary identifiers to each data stream coming from a particular client station 130a for use in identifying the a data stream to the base station 110a.
  • the temporary identifier can be referred to as a Connection Identifier (CID).
  • the system can allocate a predetermined range of numbers or characters for the CID, and reserves a number of bits necessary to support the maximum CID value in each message requiring a CID value. More than one CID may be associated with a particular client station. For example, if a client station is conducting a voice over Internet protocol (VoIP) call while also downloading information from the Internet, the VoIP data stream will be assigned one CID and the Internet data stream will be assigned another CID.
  • VoIP voice over Internet protocol
  • a base station allocates resources for a particular CID, rather than for particular client station.
  • the base station may allocate a persistent resource for one data connection associated with a client station while continuing to sporadically assign non-persistent allocations to another data connection associated with the same client station on an as needed basis.
  • a persistent allocation is typically referred to herein as assigned to a particular client station, and many systems, the persistent allocations are assigned per connection rather than per client station.
  • the client stations 130a and 130b communicate information to the base station 110a on the uplink.
  • the client stations report information related to current operating conditions as well as request uplink resources.
  • each base station for example 1 10a, can allocate some resources to support one of more random access channel (RAC), dedicated control channel, media access control layer (MAC) signing, channel quality indication channel (CQICH), out of band signaling, piggy back messaging or other control signaling path used by the client stations 130a and 130b for such uplink communications.
  • RAC random access channel
  • MAC media access control layer
  • CQICH channel quality indication channel
  • one such a dedicated channel for transmission of allocation requests is referred to as a fast feedback channel.
  • the base station 110a can periodically allocate resources to support the control signaling channel.
  • the base station 110a can support one or more random access channels, dedicated channels etc. in each uplink frame.
  • a base station 110a can allocate a portion of the uplink resources to one or more random access and/or dedicated channels.
  • the base station 110a can allocate, for example, a time, duration, and number of OFDM subcarriers on the uplink portion for the random access and/or dedicated channels.
  • Each of the random access and/or dedicated channel parameters may be static or may be dynamic.
  • the client station 130a may transmit a bandwidth request to the base station 110a using the random access channel, dedicated control signaling channel or other channel.
  • the base station 110a may allocate uplink resources to the client station 130a.
  • the wireless communication system 100 can reduce the need for a continual request and allocation of resources by utilizing persistent uplink resource allocations.
  • a client station e.g. 130a may request a persistent resource allocation or a base station, e.g. 110a may determine that a client station 130a is a candidate for a persistent uplink resource allocation.
  • a base station 110a may determine that a particular client station 130a is a good candidate for persistent downlink resource allocation, and may allocate persistent downlink resources to eliminate the overhead and resources needed to continually communicate downlink resource allocations to the client station.
  • Each of the base station 110a and client station 130a can implement one or more processes for detecting and/or communicating an error in the receipt or processing of persistent resource allocation assignments. For example, each client station 130a can affirmatively acknowledge (ACK) receipt of a persistent downlink or uplink resource allocation IE message. Conversely, each client station 130a can communicate a negative acknowledgement (NACK) upon determining a failure to receive a persistent downlink or uplink resource allocation IE message or otherwise determining an inability to decode the persistent downlink or uplink resource allocation IE message sent by a serving base station, e.g. 110a.
  • ACK acknowledge
  • NACK negative acknowledgement
  • the base station 110a can determine the presence of the error condition, either through failure to receive an affirmative acknowledgement, through receipt of a negative acknowledgement, or via some other process.
  • the base station 110a can retransmit the persistent downlink or uplink resource allocation IE message in response to determining the error condition.
  • the base station 110a can retransmit the entire persistent downlink or uplink resource allocation IE message.
  • the base station 110a can retransmit a portion of the persistent downlink or uplink resource allocation IE message that relates to the client station 130a communicating the error condition.
  • Figure 2 is a simplified functional block diagram of a base station 200 implementing persistent downlink and uplink resource allocation and resource allocation retransmission for error correction.
  • the base station 200 can be, for example, one of the base stations in the wireless communication system of Figure 1 .
  • the base station 200 includes an antenna 202 that can be coupled to a receiver 210 and transmitter 280 within the base station 200.
  • the antenna 202 can be one or more antennas configured to support multiple transmit and receive operating bands, multiple input multiple output (MIMO) operation, beam steering, special diversity and the like.
  • MIMO multiple input multiple output
  • the base station 200 can include a duplexor (not shown) to isolate the transmit signals from the receiver 210.
  • the receiver 210 and transmitter 280 can be distinct or can be part of a transceiver.
  • the receiver 210 is configured to receive the uplink transmissions transmit by a client station (not shown), such as one of the client stations of Figure 1 . Initially, a client station can synchronize and register with a base station 200 once the client station enters a coverage area of the base station 200 or upon waking up from a sleep or idle state.
  • the receiver 210 can receive a request for uplink resources in a request from a subscriber transmitted over a random access channel, fast feedback channel, piggyback data channel, MAC signaling, CQICH signaling, in band or out of band messaging, dedicated control channel or any other type of control signaling channel.
  • a control signaling channel processor 220 is coupled to the receiver 210 and operates to determine the presence of an uplink allocation request.
  • the control signaling channel processor 220 may also perform associated duties in combination with one or more functional modules to identify the requesting client station and to identify the nature and size of the resource allocation request.
  • the control signaling channel processor 220 may operate in conjunction with a downlink signal processor 270 to communicate additional information to the client station that enables the client station to communicate the additional bandwidth, nature, and identity information.
  • a persistent candidate processor 230 can process the downlink and uplink resource allocation request, for example, processed by the control signaling channel processor 220 to determine whether the requesting client station is a good candidate for persistent resource allocation.
  • the persistent candidate processor 230 can also determine if a client station is a good candidate for persistent downlink resource allocation.
  • the persistent candidate processor 230 can, for example, determine an express request for a persistent channel or may monitor one or more parameters to determine whether the client station is a candidate for persistent resource allocation in the downlink, uplink, or both.
  • the express request for persistent channel is made by another element of the base station or infrastructure.
  • the persistent candidate processor 230 may also monitor the received signal to determine a channel characteristic associated with the requesting client station. Alternatively, the persistent candidate processor 230 may monitor the received signal for feedback information from the client station characterizing its channel characteristics. Such signaling may be processed by the control signaling channel processor 220.
  • the persistent candidate processor 230 can be coupled to a group scheduler 240 and to a downlink/uplink map generator 260. If the persistent candidate processor 230 determines that the resource request and client station are not candidates for persistent allocation, the persistent candidate processor 230 can signal the DL/UL map generator 260 to generate a non-persistent downlink or uplink resource allocation.
  • the persistent candidate processor 230 can communicate the information to the group scheduler 240.
  • the group scheduler 240 can be configured to schedule the persistent allocation to one or more group from a predetermined number of groups.
  • the group scheduler 240 can determine the group or groups based on a variety of parameters and metrics. For example, the group scheduler 240 can attempt to balance persistent allocations across each of the groups or may operate to optimize some other constraint or metric.
  • the group scheduler 240 can communicate the group information to a persistent DL/UL map IE generator 250 that operates to generate the persistent DL/UL allocation IE for the group, including the persistent resource allocation for the requesting client station.
  • the persistent DL/UL IE generator 250 can communicate the persistent DL/UL allocation IE to the DL/UL map generator 260 for inclusion in the respective DL-MAP or UL-MAP.
  • the DL/UL map generator 260 can be configured to generate the DL-MAP and UL-MAP including any persistent and non-persistent resource allocations.
  • the DL/UL map generator 260 couples the UL-MAP information element to the downlink signal processor 270 which creates the final message for transmission over the downlink.
  • the downlink information can be coupled to the transmitter 280 for transmission in the coverage area supported by the base station 200.
  • the base station 200 can determine and communicate persistent resource allocations periodically, in response to an updating event or trigger, or some combination thereof.
  • the base station 200 can be configured to update and transmit persistent resource allocation IEs each frame, where a frame corresponds to a predetermined number of symbols, packets, or some other measure of information.
  • the base station 200 can also include a NACK/ACK processing module 290 coupled to the receiver 210 output.
  • the NACK/ACK processing module 290 can be configured to determine, for example, the presence of a persistent resource allocation map error condition.
  • a map error occurs when a client station fails to properly receive the persistent downlink or uplink map IE in a frame which may have included a change to its current persistent allocation configuration, for example, such as, an initial grant of a new persistent allocation, a change to a currently active persistent allocation or termination or suspension of a currently active persistent allocation.
  • the NACK/ACK processing module 290 can be configured to determine the error condition expressly or implicitly.
  • the NACK/ACK processing module 290 can determine the error condition expressly by monitoring the received signals for ACK and/or NACK messages communicated by the client stations.
  • the NACK/ACK processing module 290 can determine the error condition implicitly by monitoring the received signals and monitoring for the absence of received signals over persistent resource allocations.
  • the NACK/ACK processing module 290 can communicate the presence of an error condition to the DL/UL map generator 260 and the persistent DL/UL IE generator 250.
  • the NACK/ACK processing module 290 can also determine the identity of a client station or group of client stations associated with the error condition.
  • the NACK/ACK processing module 290 can communicate the identity information to the DL/UL map generator 260 and the persistent DL/UL IE generator 250.
  • the persistent DL/UL IE generator 250 can generate a persistent DL or UL allocation IE that repeats at least a portion of a previously transmitted persistent allocation IE.
  • the repeated portion of the persistent allocation IE can correspond to the identified client station or group of client stations associated with the error condition.
  • the DL/ UL map generator 260 generates the error correction DL-MAP or UL-MAP, as needed, and retransmits at least the portion of a previously transmitted persistent resource allocation IE. In the absence of map error grouping, where the base station is unable to determine which client station or group of client stations transmitted the NACK, the base station may retransmit the entire persistent allocation IE.
  • FIG 3 is a simplified functional block diagram of a client station 300 configured to operate using persistent downlink and uplink resource allocation.
  • the client station 300 can be, for example, one of the client stations illustrated in the wireless system of Figure 1 .
  • the client station 300 can include an antenna 302 coupled to a receiver 310 and a transmitter 370. Although a single antenna 302 is shown as shared between a transmitter 370 and receiver 310, multiple antennas can be used.
  • the receiver 310 can be configured to operate to receive the downlink transmissions from a base station such as the base station of Figure 2 .
  • a DL/UL map module 320 coupled to the receiver 310 can be configured to extract the DL-MAP information element and the UL-MAP information element from the downlink signal.
  • the DL/ UL map module 320 can be configured to examine the DL-MAP to determine if the client station 300 has been allocated persistent or non-persistent downlink resources and can examine the UL-MAP to determine whether the client station 300 has been granted uplink resources, and if so, whether the allocation is persistent or non-persistent.
  • the DL/UL-map module 320 can store the persistent DL or UL map IE in a storage device 324.
  • the DL/UL-map module 320 can also communicate a persistent allocation to a group cycle index module 340 that is configured to determine the group cycle index associated with the persistent resource allocation.
  • the group cycle index module 340 can communicate the group cycle index value to a synchronizer 360 to permit the synchronizer 360 to synchronize the UL transmissions to the proper frames.
  • the synchronizer 360 can communicate the group cycle index value to the receiver 310 to synchronize the receiver 310 to the proper downlink frames.
  • the DL/UL-map module 320 can also communicate the persistent UL-MAP and DL-MAP information to a resource mapper 330.
  • the resource mapper 330 can be configured to compare the current persistent allocation map against the stored persistence map from the storage device 324 to determine the actual resources allocated to the client station 300.
  • the resource mapper 330 determines the resources directly from the resource allocation. If neither UL-MAP nor the DL-MAP identifies the client station 300, but instead relies on an earlier communicated persistent allocation, the resource mapper 330 compares the persistent allocations against the stored version to determine if any allocation has been temporarily deactivated, and whether such temporary deactivation affects the resources allocated to the client station 300.
  • the resource mapper 330 maps the uplink information to the proper resources in a channelizer 350 based on the resource allocation.
  • the resource mapper 330 can be configured to control the subcarriers and symbols that UL information is mapped to in the channelizer 350.
  • the output from the channelizer 350 which can specify, for example, a series of OFDM symbols, is coupled to the synchronizer 360 that can be configured to synchronize the symbol timing to the timing of the frames in which the uplink or downlink resource is allocated.
  • the output of the synchronizer 360 is coupled to a transmitter 370 that uses the information to create a signal that is upconverted to a desired operating frequency before it is transmitted using the antenna 302.
  • the output of the synchronizer 360 is also coupled to the receiver 310 to facilitate receipt of the downlink allocation.
  • a NACK/ACK generator 332 can be coupled to the output of the DL/UL-map module 320 and can be configured to generate an appropriate ACK or NACK message based on the ability of the DL/UL-map module 320 to recover and decode the persistent resource allocation IE in the DL-MAP or the UL-MAP.
  • the NACK/ACK generator 332 determines and couples the appropriate NACK or ACK message, if any, to the channelizer 350 for transmission to the base station.
  • the NACK/ACK generator 332 can selectively generate the NACK or ACK message to indicate the successful receipt of a persistent resource allocation IE, the presence or absence of a persistent resource allocation IE error condition and the like.
  • a map error occurs when a client station fails to properly receive the persistent downlink or uplink map IE in a frame which may have included a change to its persistent allocation. If a client station experiences a map error, it must refrain from using the persistent allocation or risk transmitting on an allocation assigned to another client station, possibly corrupting both transmissions. Similarly, if a client station experiences a map error in a downlink resource allocation, the client station notifies the base station. In order to avoid failed attempts to decode allocations granted to some other client station, the client station may refrain from attempting to decode data according to its most recent downlink persistent allocation until the error condition is corrected.
  • the client station may continue to decode data according to its most recent downlink persistent allocation until the map error condition is addressed, relying on the physical layer (PHY) and media access (MAC) layer data error detection/correction mechanisms commonly in use on wireless systems to correct any data errors that may occur if its most recent downlink persistent allocation is no longer valid.
  • PHY physical layer
  • MAC media access
  • the client station may resume the uplink communications on the proper persistent resource allocation or the downlink reception on the proper resource allocation as soon as possible. Therefore, it is advantageous if the persistent allocation method employs an efficient error detection and correction mechanism with very low latency between the occurrence of a map error and the correction of the error condition.
  • map errors may be addressed by having the client station send an affirmative acknowledgment (ACK) to the base station every time it properly receives a persistent downlink or uplink map IE which includes an update for the client station.
  • ACK affirmative acknowledgment
  • each client station with a persistent allocation can also be assigned a dedicated persistent ACK channel.
  • One disadvantage of assigning each client station a dedicated persistent ACK channel is that there is significant overhead associated with allocating and using these dedicated ACK channels. Even if allocation of the dedicated ACK channel is restricted to the client stations having higher probability of experiencing map error, such as client stations operating at the edge of the coverage area, the overhead associated with affirmative acknowledgement is still significant.
  • this can be implemented in conjunction with the shared NACK channel described more fully below such that client stations more like to experience a MAP error are assigned either dedicated or sparsely shared NACK channel.
  • Map errors can be addressed by implementing NACK based error recovery. If a client station experiences a map error, it sends a negative acknowledgment (NACK) message to the base station indicating the map error.
  • NACK negative acknowledgment
  • the base station can allocate dedicated NACK channel associated with just one subscriber station.
  • using dedicated NACK channels can require a significant amount of system resources as the number of client stations using the system gets large.
  • a limited number of shared NACK channels are used.
  • Each shared NACK channel can be used by more than one subscriber station to indicate a map error.
  • the NACK message can include virtually any number of bits and information. However, in order to reduce overhead, the NACK message can have as few as one bit, whose presence indicates the NACK.
  • the base station upon receipt of a message on the shared NACK channel, the base station determines that one or more of the client stations associated with the NACK channel has experienced a map error. However if multiple client stations are using the NACK channel, the base station cannot specifically identify the client station which experienced the map error.
  • the base station can specify the modulation coding scheme assigned to the NACK channels, for example, in the persistent resource allocation IE.
  • the modulation coding scheme associated with the NACK channels can be fixed to a robust modulation coding scheme and a highly repetitious coding.
  • the modulation coding scheme associated with the NACK channels is BPSK.
  • the modulation coding scheme associated with the NACK channels is QPSK with rate 1 ⁇ 2 coding according to a predetermined encoding scheme.
  • the modulation coding schemes can be virtually any type of fixed or dynamically specified schemes.
  • the client stations use pseudorandom codes to define the MAP NACK channel.
  • One common pseudorandom code can be assigned to, or otherwise used by, more than one client station to indicate a map error.
  • the base station does not know which or how many client stations experienced a map error upon receipt of an error indication on the NACK channel.
  • the base station can determine the group to which the client station is assigned based on the frame in which the map NACK channel message is received and, in some cases, the particular pseudorandom code if more than one is used.
  • pseudorandom codes if more than one client station sends a map NACK channel message, the energy from each client station can be combined in a macro-diversity sense, according to the standard operation of the physical layer, thus enhancing the probability of reception.
  • Figures 4 through 8 detail error correction in persistent uplink resource allocation utilizing NACK messaging.
  • the description is focused on correcting persistent downlink or uplink map errors in a time division multiplex (TDM) OFDMA system.
  • TDM time division multiplex
  • the apparatus and methods for error correction in persistent resource allocations are not limited to pseudorandom NACK messaging nor are they limited to TDM or OFDMA systems.
  • FIG. 4 is a simplified timing diagram 400 of a persistent resource allocation.
  • the persistent resource allocation illustrated in the timing diagram of Figure 4 supports Time Division Duplex (TDD) operation of downlink and uplink subframes, and multiple persistent resource groups within a persistence period. Additionally, the timing diagram is described in the context of persistent uplink resource allocation with a K+1 allocation relevance (resources allocated in the resource allocation IE message of frame K are active in frame K+1) and persistent downlink resource allocation with a relevance of K.
  • the error correction for persistent resource allocation methods and apparatus described herein are not limited to TDD operation, multiple resource groups, or any particular resource allocation relevance. This error recovery mechanism described herein allows for fast error detection for both DL and UL persistent allocations.
  • the timing diagram 400 of Figure 4 illustrates a number of successive frames 420, e.g. 420-K through 420-(K+8), where each frame includes a downlink subframe 412 followed by an uplink subframe 414.
  • the frames are further divided into persistence groups 410, such as persistent groups 410-N and 410-(N+1), with each persistence group 410 including a fixed number of frames 420.
  • the period of one persistence group is referred to as an allocation period (AP) or persistent period.
  • Each frame 420 in a persistence group 410 can be associated with a persistence index, also referred to as a group cycle index, which can be used to identify the position of the frame within the persistence group 410.
  • a persistent downlink or uplink resource allocation may be associated with a particular group cycle index.
  • the allocation period is four frames.
  • a persistent uplink resource allocated to the Kth UL subframe 414-K applies to the UL subframe in the frame 420-(K+4) of the next persistence group 410-(N+1).
  • a persistent downlink resource allocated to the Kth downlink subframe 412-K applies to the downlink subframe in which it occurs (i.e. DL subframe 412-K.)
  • persistence resource allocations remain valid for successive frames.
  • a persistent resource allocation IE 430-K can specify an uplink or downlink persistent resource allocation or both.
  • an uplink persistent resource allocation received in a downlink subframe 412-K can have a relevance of K+1, such that the uplink resources allocated in the Kth DL subframe 412-K occur in the K+1 uplink subframe.
  • the persistent resource allocation IE 430-K received in a downlink subframe 412-K can have a relevance of K for downlink allocations, such that the downlink persistent resources 434 allocated in the Kth DL subframe 412-K occur in the Kth downlink subframe.
  • the persistence allocation IE 430-K typically allocates the resources using multiple pieces of information.
  • the information in the persistence allocation IE 430-K can include a CID or reduced connection identifier (RCID) - indicating the connection for which this persistent allocation is directed.
  • RCID is an abbreviated connection identifier which contains fewer bits than the CID but still completely identifies the connection.
  • the information can also include an indication of the allocation period, illustrated above as the period of the persistence group 410. If a client station is allocated a persistent allocation in frame K using the persistent IE, the client station also has an allocation in frames K + N * AP, where N represents the number of persistence groups and AP is the allocation period measured in units of frames.
  • a typical IEEE 802.16 allocation period is 20ms, corresponding to four 5ms frames, representing the packet emission rate of most commonly used codecs.
  • the information in the persistence allocation IE 430-K can also include an allocation unit offset, which may also be referred to as a slot offset.
  • the slot offset is used to indicate the start of the persistent allocation relative to a known starting point. For example, in HARQ allocation, the slot offset is relative to the beginning of the HARQ region. As another example, in UL non-HARQ allocation, the offset is relative to the start of the UL sub-frame.
  • the information can also include a number of slots, also referred to as a duration. The duration indicates the number of consecutive slots in the persistent allocation.
  • the information can also include PHY related information (e.g. modulation and coding, etc.)
  • the information can include an HARQ ACK channel index (in the case of HARQ allocation) that indicates a specific HARQ ACK channel to use to acknowledge receipt of HARQ packets over the persistent resource allocation .
  • the HARQ ACK channel is also allocated persistently with the same period as the data resource assignment so that each HARQ packet received can be properly acknowledged.
  • a dedicated map ACK channel can be defined for each subscriber station.
  • the subscriber station sends a map ACK each time it successfully receives a downlink or uplink map IE.
  • this approach requires the establishment of a great number of map ACK channels as well as the transmission of many responsive acknowledgments.
  • the information in the persistence allocation IE 430-K can also include a map NACK channel index.
  • the map NACK channel index identifies a specific map NACK channel used by the client station to indicate that it was not able to decode a persistent map IE.
  • the NACK channel may be assigned to the individual client station or it may be shared among multiple client stations.
  • Figure 5 is a simplified timing diagram 500 of map NACK messaging in a system having persistent resource allocation and multiple map NACK channels.
  • UL sub-frame 414 K+1 contains the map NACK channels 510-(K+1), 512-(K+1) and 514-(K+1) for Frame K 420-K.
  • the timing diagram 500 illustrates three map NACK channel subgroups, indexed a 310-(K+1), b 512-(K+1), and c 514-(K+1). Client stations are assigned to one of these map NACK sub-groups: a, b or c. This allows the base station to narrow the group of possibly affected client stations when a map NACK message is received.
  • the the base station allocates one or more fast feedback slots for the purpose of creating one or more map NACK channels.
  • the map NACK Channel (MNCH) can be allocated a pseudorandom code to indicate a map error condition, with different codes assigned to the various subgroups.
  • the base station receives a NACK message from one or more client stations that did not properly decode a persistent downlink or uplink map IE which may carry information for that client station. In other words the base station receives a NACK message from any users who experienced a map error.
  • the base station if the base station receives a map NACK channel message and no changes were made to the persistent allocations in the corresponding frame, the base station sends a short message indicating that there were no changes. In this way the base station avoids resending a full or partial persistent downlink or uplink map information element in favor of a shorter "no changes" message.
  • the base station can use implicit means to detect map errors.
  • the client station experiences an uplink map error, it does not transmit in the next frame. Therefore, if the base station detects little or no signal energy was received from a client station over the uplink during its uplink persistent allocation for one or more frames, the base station can infer that the client station experienced a map error.
  • This implicit method of map error detection can be used alone or in conjunction with a map NACK channel or other error detection mechanisms. This implicit error detection mechanism can be used to recover from a map NACK channel error as discussed below.
  • the map NACK channel is specified within the persistent downlink or uplink map information element.
  • a problem may occur if a client station experiences a map error in a persistent allocation information element in which it is either initially assigned a map NACK channel or its map NACK channel is changed. In the first case, the client station does not know what map NACK channel to use. In the second case, the client station uses a map NACK channel that the base station does not associate with this client station. In a third case, the client station properly uses a currently assigned map NACK channel but the message is not properly received by the base station. We refer to this problem as a map NACK channel error or map NACK channel assignment error.
  • the base station uses implicit means to detect map NACK error. For example, if the base station detects little or no signal energy was received from a client station during one or more its uplink persistent allocations, the base station can infer that the client station experienced a map error and a map NACK channel error and can resend the persistent allocation information, including the map NACK channel assignment.
  • a map NACK channel error can be detected by the client station. If a client station sends a message on the map NACK channel and does not get the expected response from the base station in the next persistent map IE of interest, the client station assumes that the base station did not receive the map NACK channel message. Therefore, according to this aspect, the client station sends another map NACK message. In this case, when a base station receives a map NACK message it does not know whether the NACK message was a first or a second transmission. If this scheme is used, it may be advantageous for the base station to send updates associated with one or more frames worth of updates. For example, in response to each successfully received message on the map NACK channel, the base station can repeat all changes affected within the last two relevant frames.
  • Figure 6 is a simplified flowchart of a method 600 of persistent downlink or uplink resource allocation.
  • the method 600 can be implemented, for example, within a base station of Figure 1 or Figure 2 to enable NACK messaging used to perform error correction in persistent resource allocations.
  • the persistent resource allocation can be an initial persistent resource allocation or can be an updated persistent resource allocation.
  • the method 600 begins at block 610 where the base station determines that a particular client station, or communication link established with the client station, is a candidate for persistent resource allocation.
  • the base station proceeds to block 620 and schedules the client station for persistent resource allocation.
  • the persistent resource allocation is valid for more than one frame.
  • the persistent resource allocation can be specified according to a number of time division multiplexed persistence resource groups. Each group may be associated with a persistence slot index that identifies a downlink or uplink frame in each resource allocation period.
  • the base station can assign the client station to one of the persistence groups, for example, to balance the persistent resource loading across the allocation period.
  • the base station proceeds to block 630 and assigns the client station to a NACK subgroup within its persistence group.
  • Each NACK subgroup can be associated with a distinct map NACK channel assignment.
  • the base station can utilize NACK subgroups with a plurality of client stations assigned to subgroups in order to reduce the resources needed to support NACK channels.
  • a NACK message received by the base station on a map NACK channel associated with a particular subgroup affects all client stations associated with the group and NACK subgroup.
  • the base station can base the retransmission on the identified client stations.
  • the base station can operate to substantially uniformly distribute client stations across the various subgroups.
  • the base station proceeds to block 640 and generates for the client station a persistent resource allocation IE with a map NACK channel assignment.
  • the base station proceeds to block 650 and transmits the persistent resource allocation IE with a map NACK channel assignment, for example, as part of a DL-MAP or UL-MAP message.
  • the base station proceeds to block 660 and is done with the current persistent resource allocation for a client station.
  • Figure 7 is a simplified flowchart of a method 700 of resource reallocation in the presence of error correction.
  • the method 700 of Figure 7 can be implemented, for example, within a base station of Figure 1 or Figure 2 .
  • the method 700 begins at block 710 where the base station sends a persistent allocation IE with a NACK channel assignment to one or more client stations in its serving area.
  • the base station can, for example, generate and send the message using the method of Figure 6 .
  • the base station proceeds to decision block 720 and monitors the received uplink signals to determine whether a NACK message is received during an assigned NACK channel.
  • a presence of a NACK message is an express indication of a map error condition, while absence of a NACK message does not ensure the absence of a map error condition.
  • the base station determines, at decision block 720, that an express NACK message is received, the base station proceeds to block 740. Alternatively, if the base station determines, at decision block 730 that no NACK message has been received, the base station proceeds to decision block 730.
  • the base station determine the presence of a map error condition implicitly. That is, the base station, based on one or more parameters implicitly determines the presence of a NACK. For example, the base station may monitor uplink resource allocations and may imply a NACK for any uplink resource allocation for which no transmission is received. If the base station determines that no implicit NACK is present, the base station determines an absence of a map error condition and returns to block 710. Alternatively, if the base station, at decision block 730, implicitly determines the presence of a NACK, the base station proceeds to block 740.
  • the base station identifies the client station or group of client stations associated with a NACK message or indication. For example, the base station can examine the NACK channel, persistence group, and subgroup associated with a NACK message to identify one or more client stations. Alternatively, the base station can correlate a missing uplink transmission with a client station allocated the uplink resources to determine an identity of a client station.
  • the base station After determining the identity of one or more client stations associated with a NACK message or indication, the base station proceeds to block 750 and determines the portion of a previously transmitted uplink resource allocation IE relevant to the identified client stations.
  • the base station can format an updated persistent resource allocation IE repeating a portion of a previously transmitted uplink resource allocation IE relevant to the identified client stations.
  • the base station can transmit a "no change" persistent resource allocation IE message.
  • the base station returns to decision block 720 to determine if the latest resource allocation IE message is a source of map errors.
  • Figure 8 is a simplified flowchart of a method 800 of error correction signaling in a client station.
  • the method 800 can be implemented, for example, in a client station of Figure 1 or Figure 3 .
  • the method 800 begins at block 810 where the client station receives a DL-MAP or an UL-MAP having a persistent resource allocation IE message.
  • the client station proceeds to decision block 820 to determine if it is able to successfully decode the map and, in particular, the persistent resource allocation IE message. If so, the client station proceeds to block 840 to process the map for any resource allocations to the client device.
  • the client device proceeds to block 850. Alternatively, if the client station is unable to successfully decode the map message, the client station proceeds from decision block 820 to decision block 830.
  • the client device determines if it is already a recipient of a persistent resource allocation, such as a persistent uplink resource allocation or a persistent downlink resource allocation. If, at decision block 830, the client station determines that it has no active persistent resource allocation, the client station proceeds to block 832 in which it optionally generates ands send a global NACK to indicate the failure to potentially receive the initial resource allocation. The client station returns from block 832 to block 810 to await the next DL/UL map transmission, which likely includes a retransmission of any missed persistent resource allocation.
  • a persistent resource allocation such as a persistent uplink resource allocation or a persistent downlink resource allocation.
  • the client station determines that it has previously been allocated persistent resources, the client station proceeds to block 834 to temporarily deallocate the client station from the prior persistent resource allocation to prevent potential corruption of another device's transmissions.
  • the client device proceeds from block 834 to block 860 and determines its associated map NACK channel assignment.
  • the client station proceeds to block 870 and transmits the NACK on the assigned map NACK channel.
  • the client station returns to block 810 to await the transmission of a subsequence persistent UL allocation IE.
  • Figure 9 is a more detailed flowchart of a method 900 of addressing a persistent allocation map error from the perspective of a base station.
  • the method 900 can be implemented, for example, within a base stations such as the one shown in Figure 1 or Figure 2 .
  • the method 900 begins in block 910 in which the base station determines whether a map NACK message was received in frame K.
  • the base station 200 may determine whether a map NACK message was received over a shared map NACK channel.
  • the map NACK channel is received over the receiver 210 ( Figure 2 ) over a shared random access channel.
  • the map NACK message may comprise a pseudorandom sequence the presence of which specifies a map NACK error is being indicated by a client station assigned to the shared map NACK channel.
  • the random access channel processor 220 determines whether a map NACK message was received.
  • the base station determines whether it has a reason to send all persistent allocation assignments. For example, within the base station 200, the persistent DL/UL IE gyrator 250 determines whether it intends to send all currently active persistent allocation assignments.
  • the base station 200 determines that it will send all currently active persistent allocation assignments, flow continues to block 916.
  • the base station creates a persistent DL_map IE indicating all persistent allocations.
  • the persistent DL/UL IE generator 250 creates such a message and provides the information to the DL map generator 260 for combination with other allocations.
  • the DL map generator 260 provides the map information to the downlink processor 270 which formats the message for proper transmission over the wireless link via the transmitter 280 and an antenna 202 (such actions being omitted from Figure 9 for clarity.)
  • the base station determines whether changes to the persistent allocations were made in recent downlink map IE's. For example, if the system is configured such that a client station may send one additional map NACK messages if it does not receive an expected response to a first map NACK message, the persistent DL/UL IE generator determines whether any changes to the persistent allocations were made in the two previous relevant frames. If changes were made, flow continues to block 920 in which the base station creates a DL_map IE indicating the receipt of a map NACK and repeating any persistent allocation changes that were made in the relevant frames. For example, referring again to Figure 2 , the persistent DL/UL IE generator 250 creates a message indicating receipt of a map NACK message and repeating the relevant persistent allocation changes. This information is sent over the wireless link in the manner just described.
  • the base station determines that no changes were made in block 918, flow continues to block 922 to.
  • the base station creates a persistent downlink map IE indicating receipt of the map NACK and that no changes have been made.
  • the persistent DL UL IE generator 250 creates such a "no-changes" message and this information is sent over the wireless link in the manner just described.
  • Figure 10 is a more detailed flowchart of a method 1000 of addressing a downlink persistent allocation map error from the perspective of a client station.
  • the method 1000 can be implemented, for example, within a client station such as the one shown in Figure 1 or Figure 3 .
  • Figure 10 is described in the context of a downlink map error, a similar process can be used to address an uplink map error.
  • the client station determines whether it is expecting a persistent DL_map in frame K. If not, flow continues to block 1004 in which the frame count is incremented. If the client station is expecting a persistent DL_map, flow continues to block 1006. In block 1006, the client station determines whether the expected downlink persistent allocation map was properly received. For example, downlink messaging from the base station is received over the downlink 116a via the antenna 302 and the receiver 310 of the client station 300, as shown in Figure 3 . The DL/UL map module 320 determines whether the downlink map was properly received. If the downlink map was properly received, flow continues to block 1004 in which the frame counter is incremented.
  • the client station interrupts transmissions on any uplink control messaging associated with any active downlink persistent allocation, such as an HARQ ACK channel associated with the downlink persistent allocation.
  • the client station also stops attempting to decode downlink messaging according to any active persistent allocation in order to avoid failed attempts to decode downlink allocations granted to some other client station.
  • the client station may continue to decode data according to any active downlink persistent allocation until the map error condition is addressed, relying on the physical (PHY) layer and media access (MAC) layer data error detection/correction mechanisms commonly in use on wireless systems to correct any data errors that may occur if its most recent downlink persistent allocation is no longer valid.
  • PHY physical
  • MAC media access
  • the base station may re-map the resource associated with a shared NACK channel. For example, the base station may assign a new pseudorandom code to a shared NACK channel. Such a change is typically reported to the client station in an UL-MAP information element. If a client station fails to receive an UL-MAP information element which defined a new shared NACK channel, it may send a NACK message over an incorrect channel. Thus, according to one aspect of the invention not shown in Figure 10 , the client station determines whether the uplink map is properly received in the relevant frame following a failure to properly receive a downlink map.. For example in Figure 3 , the DL/UL map module 320 determines whether the uplink map in relevant frame was properly received. If not, the client station cannot be sure that its NACK channel information is current and a map NACK channel error recovery procedure may begin without the client station sending a message on the shared NACK channel.
  • Flow proceeds to block 1014 in which the client station sends a downlink map NACK message in the proper frame.
  • the delay between the occurrence of a map error and the transmission of the NACK is a predetermined value so that the base station can determine the affected persistence group based on the frame in which the map NACK is received.
  • the map NACK is sent two frames after the occurrence of the map error.
  • the client station sends a pseudorandom code over a shared DL map NACK channel in which the presence pseudorandom code indicates to the base station that one or more of a set of client stations using the shared DL map NACK channel has experienced an error.
  • the DL/LTL map module 320 passes is information to the NACK/ACK module 332 the NACK/ACK module 332 creates the shared channel pseudorandom code.
  • the channelizer 358 receives the message which is transmitted over the uplink 116 via the synchronizer 360, the transmitter 370 and the antenna 302.
  • the frame count is incremented and the client station awaits the arrival of the next frame in which it expects to receive a persistent allocation map.
  • the client station determines whether it has received a DL_map IE in a subsequent frame including a persistent downlink allocation expressly addressed to the client station. If so, in block 1018, the client station uses the newly assigned persistent allocation. Flow continues through block 1004.
  • the client station determines whether it has received a persistent downlink map IE indicating that a NACK message was received but that no downlink map changes were made within the relevant frames. If so, flow continues to block 1020 and the client station resumes use of any persistent allocations which were active at the time of the map error.
  • map NACK error recovery process does not commence until the client station has sent more than one map NACK, in which case, after the first pass through block 1024, the frame counter would increment and flow could continue back to block 1014.
  • a map NACK channel error can occur if the base station fails to receive the map NACK message.
  • the client station begins a map NACK channel error recovery process due to a map NACK channel error.
  • the client station sends a map NACK channel error indication on a dedicated channel, such as by using an express MAC layer message.
  • the base station uses MAC layer information to implicitly determine a map NACK channel error and the client station need not expressly address a map NACK channel error.
  • the channel is established using a Hybrid Automatic Repeat-reQuest (HARQ) error control method, each time the base station sends a downlink data packet to the client station it expects to receive from the client station over the uplink either an acknowledgment (ACK) indicating that the packet was successfully received or a negative acknowledgment (NACK) indicating that the packet was not successfully received, according to well known principles. If the base station fails to receive either a packet ACK or packet NACK for one or more HARQ packets, the base station can infer that a map NACK channel error has occurred.
  • HARQ Hybrid Automatic Repeat-reQuest
  • the base station can infer that a map NACK error has occurred.
  • the base station responds to the absence of an HARQ ACK and NACK in the same manner as it was if it received a message over the NACK channel, such as in step 910 of Figure 9 .
  • the base station knows the identity of the client station and can address the error specifically without regard to the other client stations in the persistence group.
  • a map NACK channel error can occur when a client station which is not currently assigned a persistent downlink or uplink allocation does not properly decode the persistent map IE which assigns to it a persistent allocation.
  • This scenario is referred to as a lost invitation error.
  • the client station may not been assigned a map NACK channel over which to send an indication of the map error.
  • the HARQ error detection method just described is used only the first time a persistent allocation is made in order to address a lost invitation error. After the initial persistent allocation is made and a series of packet ACKs and packets NACKs are received, the base station can assume that the client station as properly decoded the persistent map information element and has the information it needs to use the map NACK channel.
  • the base station defines a global map NACK channel in addition to the persistent group map NACK channels discussed above.
  • the global map NACK channel is used to address lost invitation errors.
  • the base station advertises the global map NACK channel information in the Uplink Channel Descriptor (UCD) rather than in the persistent uplink map IE so that all client stations in the system are aware of the global map NACK channel, whether or not they are currently assigned an active persistent allocation.
  • This global map NACK channel is used only by users without a persistent resource allocation if they fail to receive a persistent map IE.
  • the client station sends a NACK message over the global map NACK channel rather than a map NACK channel shared by a persistence group or subgroup as shown in block 1014.
  • a client station which has detected a map NACK channel error can send a NACK message on the global map NACK channel as part of the recovery process.
  • a client station which executed the process shown in Figure 10 may send a global map NACK message as part of the map NACK channel error recovery process of block 1030.
  • the base station When using a global map NACK channel, the base station implements a corresponding process similar to one shown in Figure 9 with respect to the global map NACK channel.
  • the base station determines whether it had a reason to retransmits all persistent allocations. The base station determines: any new persistent allocations were made (similar to block 918.) If no new persistent allocations were made in the frame of interest, the base station can either send a no-changes message (similar to block 922) or simply ignore the global map NACK message.
  • the base station can repeat either the entire persistent downlink and/or uplink map IE or send a partial persistent map IE including all the newly initiated persistent allocations (similar to blocks 916 and 920.) Users with persistent resource allocations typically use the map NACK channel index indicated in the persistent allocation IE rather than a global map NACK channel.
  • the global map NACK channel can be used in conjunction with one or more error recovery techniques.
  • the base station defines one or more universal map NACK channels.
  • the universal map NACK channel is used to address lost invitation errors.
  • the base station advertises one or more universal map NACK channels in the UCD.
  • the base station sends a group cycle index to the client station over an assured delivery service.
  • the assured delivery service ensures that a message is received by the client station. For example such a link requires an acknowledgment from the client station before the message is considered to have been successfully transmitted.
  • the base station may use a delivery assured dynamic service (DSx) message to send the group cycle index to the client station.
  • Client station may use the universal map NACK channels only after it has been allocated a map NACK index.
  • DSx delivery assured dynamic service
  • the base station can either send a "no changes" message or simply ignore the universal map NACK message. If new persistent allocations were made in the frame of interest, the base station can repeat either the entire persistent uplink map IE or just send a partial persistent downlink or uplink map IE.
  • the universal map NACK channel is used in addition to the map NACK channel specified in the persistent downlink or uplink map IE as discussed above.
  • the persistent map IE includes a map ACK channel for use by the client station only to acknowledge this first allocation. If the base station fails to receive a message on the map ACK channel, the base station acts in the same manner as if it received a message over the map NACK channel. Once the client station has successfully received the persistent map IE, it indicates subsequent map errors in loss using the map NACK channel assigned using the persistent allocation IE.
  • coupled or connected is used to mean an indirect coupling as well as a direct coupling or connection. Where two or more blocks, modules, devices, or apparatus are coupled, there may be one or more intervening blocks between the two coupled blocks.
  • the steps of a method, process, or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two.
  • the program code or code segments to perform the necessary tasks may be stored in a machine readable medium such as a storage medium.
  • the various steps or acts in a method or process may be performed in the order shown, or may be performed in another order. Additionally, one or more process or method steps may be omitted or one or more process or method steps may be added to the methods and processes. An additional step, block, or action may be added in the beginning, end, or intervening existing elements of the methods and processes

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Quality & Reliability (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Claims (15)

  1. Procédé exécuté par une station client (130a), le procédé comprenant :
    la réception, par la station client (130a), d'informations d'allocation de ressources persistantes (430-K), les informations d'allocation de ressources persistantes (430-K) comprenant une indication de ressources persistantes de liaison descendante, DL, un premier identifiant associé à la station client (130a), une indication d'une période d'allocation DL, une indication de ressources persistantes de liaison montante, UL, et une indication d'une période d'allocation UL, la période d'allocation DL est indiquée séparément de la période d'allocation UL;
    la réception périodique, par la station client (130a), de données d'utilisateur DL associées au premier identifiant, les données d'utilisateur DL étant reçues via les ressources persistantes DL et basées sur la période d'allocation DL, et les ressources persistantes DL se répétant à un intervalle défini par la période d'allocation DL ; et
    la transmission de manière persistante, par la station client (130a), de données d'utilisateur UL via les ressources persistantes UL et basées sur la période d'allocation UL, les ressources persistantes UL se répétant à un intervalle défini par la période d'allocation UL.
  2. Procédé selon la revendication 1, comprenant en outre :
    la réception d'informations d'allocation de ressources non persistantes comprenant une indication de ressources non persistantes et un deuxième identifiant associé à la station client ; et
    la réception de deuxièmes données d'utilisateur DL associées au deuxième identifiant en utilisant les ressources non persistantes.
  3. Procédé selon la revendication 1 ou la revendication 2, comprenant en outre :
    suite à la réception des informations d'allocation de ressources persistantes (430-K), la réception d'une indication d'une libération des ressources persistantes ; et
    la transmission d'une indication d'un accusé de réception positif, ACK, de la libération.
  4. Procédé selon l'une quelconque des revendications précédentes, comprenant en outre :
    la réception d'une indication de décalage, dans lequel l'indication de décalage indique un décalage dans une région des ressources persistantes UL, dans laquelle les ressources persistantes UL sont basées ; et
    la transmission persistante comprenant en outre la transmission des données d'utilisateur UL via des ressources sur la base du décalage.
  5. Procédé selon l'une quelconque des revendications précédentes, dans lequel au moins les unes parmi les ressources persistantes UL et les ressources persistantes DL sont utilisées dans une communication voix sur protocole Internet, VoIP.
  6. Procédé selon l'une quelconque des revendications précédentes, dans lequel la réception des informations d'allocation de ressources persistantes (430-K) comprend la réception d'une pluralité de messages d'allocation de ressources persistantes.
  7. Procédé selon l'une quelconque des revendications précédentes, dans lequel le premier identifiant est sélectionné dans une plage de valeurs prédéterminée.
  8. Station client (130a) comprenant :
    un récepteur (310) utilisable pour :
    recevoir des informations d'allocation de ressources persistantes (430-K), les informations d'allocation de ressources persistantes (430-K) comprenant une indication de ressources persistantes de liaison descendante, DL, un premier identifiant associé à la station client, une indication de période d'allocation DL, une indication de ressources persistantes de liaison montante, UL, et une indication d'une période d'allocation UL, la période d'allocation DL étant indiquée séparément de la période d'allocation UL ; et
    recevoir périodiquement des données d'utilisateur DL associées au premier identifiant, les données d'utilisateur DL étant reçues via les ressources persistantes DL et basées sur la période d'allocation DL, et les ressources persistantes DL se répétant à un intervalle défini par la période d'allocation DL ; et
    un émetteur (370) utilisable pour transmettre de manière persistante des données d'utilisateur UL via les ressources persistantes UL et basées sur la période d'allocation UL, les ressources persistantes UL se répétant à un intervalle défini par la période d'allocation UL.
  9. Station client (130a) selon la revendication 8, dans laquelle le récepteur (310) est en outre utilisable pour :
    recevoir des informations d'allocation de ressources non persistantes comprenant une indication de ressources non persistantes et un deuxième identifiant associé à la station client ; et
    recevoir des deuxièmes données d'utilisateur DL associées au deuxième identifiant en utilisant les ressources non persistantes.
  10. Station client (130a) selon la revendication 8 ou la revendication 9, dans laquelle :
    le récepteur (310) est en outre utilisable pour, suite à la réception des informations d'allocation de ressources persistantes, recevoir une indication d'une libération des ressources persistantes ; et
    l'émetteur (370) est en outre utilisable pour transmettre une indication d'un accusé de réception positif, ACK, de la libération.
  11. Station client (130a) selon l'une quelconque des revendications 8 à 10, dans laquelle :
    le récepteur (310) est en outre utilisable pour recevoir une indication de décalage, dans laquelle l'indication de décalage indique un décalage dans une région des ressources persistantes UL ; et
    l'émetteur (370) est en outre utilisable pour transmettre les données d'utilisateur UL via des ressources qui sont basées sur le décalage.
  12. Station client (130a) selon l'une quelconque des revendications 8 à 11, dans laquelle au moins les unes parmi les ressources persistantes UL et les ressources persistantes DL sont utilisées dans une communication voix sur protocole Internet, VoIP.
  13. Station client (130a) selon l'une quelconque des revendications 8 à 12, dans laquelle les informations d'allocation de ressources persistantes (430-K) comprennent en outre une indication de ressources UL pour des informations de demande de répétition automatique hybride, HARQ.
  14. Station client (130a) selon l'une quelconque des revendications 8 à 13, dans laquelle les informations d'allocation de ressources persistantes (430-K) comprennent une pluralité de messages d'allocation de ressources persistantes.
  15. Station client (130a) selon l'une quelconque des revendications 8 à 14, dans laquelle le premier identifiant est sélectionné dans une plage de valeurs prédéterminée.
EP20153689.3A 2007-09-11 2008-09-04 Correction d'erreurs pour une allocation de ressources constantes Active EP3672137B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP23151300.3A EP4216477A1 (fr) 2007-09-11 2008-09-04 Correction d'erreur pour une attribution de ressources persistante

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US97152607P 2007-09-11 2007-09-11
US1362207A 2007-12-13 2007-12-13
US1362207P 2007-12-13 2007-12-13
EP08799186.5A EP2195946B1 (fr) 2007-09-11 2008-09-04 Correction d'erreurs pour une allocation des ressources permanentes
PCT/US2008/075285 WO2009035905A2 (fr) 2007-09-11 2008-09-04 Correction d'erreurs pour une allocation des ressources permanentes

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
EP08799186.5A Division EP2195946B1 (fr) 2007-09-11 2008-09-04 Correction d'erreurs pour une allocation des ressources permanentes
EP08799186.5A Division-Into EP2195946B1 (fr) 2007-09-11 2008-09-04 Correction d'erreurs pour une allocation des ressources permanentes

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP23151300.3A Division EP4216477A1 (fr) 2007-09-11 2008-09-04 Correction d'erreur pour une attribution de ressources persistante
EP23151300.3A Division-Into EP4216477A1 (fr) 2007-09-11 2008-09-04 Correction d'erreur pour une attribution de ressources persistante

Publications (2)

Publication Number Publication Date
EP3672137A1 EP3672137A1 (fr) 2020-06-24
EP3672137B1 true EP3672137B1 (fr) 2023-03-15

Family

ID=40433156

Family Applications (4)

Application Number Title Priority Date Filing Date
EP20153689.3A Active EP3672137B1 (fr) 2007-09-11 2008-09-04 Correction d'erreurs pour une allocation de ressources constantes
EP20080799181 Withdrawn EP2195945A4 (fr) 2007-09-11 2008-09-04 Allocation de ressources permanente
EP08799186.5A Active EP2195946B1 (fr) 2007-09-11 2008-09-04 Correction d'erreurs pour une allocation des ressources permanentes
EP23151300.3A Pending EP4216477A1 (fr) 2007-09-11 2008-09-04 Correction d'erreur pour une attribution de ressources persistante

Family Applications After (3)

Application Number Title Priority Date Filing Date
EP20080799181 Withdrawn EP2195945A4 (fr) 2007-09-11 2008-09-04 Allocation de ressources permanente
EP08799186.5A Active EP2195946B1 (fr) 2007-09-11 2008-09-04 Correction d'erreurs pour une allocation des ressources permanentes
EP23151300.3A Pending EP4216477A1 (fr) 2007-09-11 2008-09-04 Correction d'erreur pour une attribution de ressources persistante

Country Status (9)

Country Link
US (10) US8423853B2 (fr)
EP (4) EP3672137B1 (fr)
JP (5) JP5362726B2 (fr)
KR (8) KR101548392B1 (fr)
CN (2) CN101849375B (fr)
BR (1) BRPI0815862A2 (fr)
MX (2) MX2010002747A (fr)
RU (2) RU2471291C2 (fr)
WO (2) WO2009035905A2 (fr)

Families Citing this family (100)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8687542B2 (en) 2006-05-18 2014-04-01 Qualcomm Incorporated Method of improving throughput in a system including sticky assignments
KR100965673B1 (ko) * 2006-11-15 2010-06-24 삼성전자주식회사 이동통신 시스템에서 데이터 송신 방법
JP5069740B2 (ja) * 2007-03-01 2012-11-07 株式会社エヌ・ティ・ティ・ドコモ 基地局装置及び通信制御方法
JP4901955B2 (ja) * 2007-03-30 2012-03-21 富士通株式会社 基地局装置、通信システム及びコンピュータプログラム
US8649334B2 (en) * 2007-05-30 2014-02-11 Samsung Electronics Co., Ltd. Radio resource reallocating method for circuit mode
US8265029B2 (en) * 2007-06-15 2012-09-11 Futurewei Technologies, Inc. Method and apparatus for assigning resources in a wireless system
US20080310359A1 (en) * 2007-06-15 2008-12-18 Mcbeath Sean Michael Method and Apparatus for Sharing Resources in a Wireless System
US8614985B2 (en) * 2007-06-15 2013-12-24 Futurewei Technologies, Inc. Method and apparatus for sharing a group resource in a wireless SDMA system
US8130780B2 (en) 2007-06-15 2012-03-06 Futurewei Technologies, Inc. Method and apparatus for assigning resources in a wireless system with multiple regions
US9544911B2 (en) * 2007-08-10 2017-01-10 Futurewei Technologies, Inc. System and method for assigning communications resources in a wireless communications system
RU2471291C2 (ru) * 2007-09-11 2012-12-27 Вай-Лэн, Инк. Распределение постоянных ресурсов
US9306709B2 (en) * 2007-09-14 2016-04-05 Futurewei Technologies, Inc. Method and apparatus for associating a packet with an H-ARQ channel identifier
KR20090030562A (ko) * 2007-09-20 2009-03-25 엘지전자 주식회사 광대역 무선 접속 시스템에서 자원할당을 위한 패킷전송방법
US9532347B2 (en) * 2007-10-18 2016-12-27 Samsung Electronics Co., Ltd. Method and apparatus for allocating resources in a wireless communication system
CN101843133B (zh) * 2007-10-31 2015-05-13 日本电气株式会社 通信系统中的资源分配方法、资源分配系统及用于其的基站
JP2011504669A (ja) * 2007-11-05 2011-02-10 ノーテル・ネットワークス・リミテッド 資源割り当てのための方法およびシステム
KR101366285B1 (ko) * 2007-11-20 2014-02-20 엘지전자 주식회사 실시간 서비스를 지원받는 단말을 위한 자원할당방법
KR101457121B1 (ko) * 2007-11-26 2014-11-03 삼성전자주식회사 광대역 무선통신 시스템에서 자가 복구가능한 고정 할당장치 및 방법
US8254942B2 (en) * 2007-11-27 2012-08-28 Futurewei Technologies, Inc. System and method for resource allocation in a wireless communications system
KR101516818B1 (ko) * 2008-01-25 2015-05-04 삼성전자주식회사 통신 시스템에서 맵 송수신 장치 및 방법
US8208433B2 (en) * 2008-02-19 2012-06-26 Broadcom Corporation Method and apparatus for allocating resources in wireless communication system
US8259662B2 (en) * 2008-02-19 2012-09-04 Futurewei Technologies Method and apparatus for assigning persistent resources dynamically in a wireless communication system
KR101464340B1 (ko) * 2008-02-29 2014-11-26 삼성전자주식회사 무선통신시스템에서 고정할당을 위한 장치 및 방법
JP4410837B2 (ja) * 2008-03-28 2010-02-03 株式会社エヌ・ティ・ティ・ドコモ 無線リソース選択方法、移動局及び無線基地局
US8570958B2 (en) * 2008-04-04 2013-10-29 Intel Corporation Method and apparatus for efficient scheduling in broadband wireless access networks
KR20110020228A (ko) * 2008-05-02 2011-03-02 가부시키가이샤 엔티티 도코모 무선기지국 및 통신제어방법
US8009620B2 (en) * 2008-05-09 2011-08-30 Nokia Siemens Networks Oy Variable header types for persistent resource allocation in a wireless network
KR20090128988A (ko) * 2008-06-12 2009-12-16 삼성전자주식회사 광대역 무선통신 시스템에서 맵 정보 송수신 장치 및 방법
US8483041B2 (en) * 2008-06-12 2013-07-09 Qualcomm Incorporated Methods and systems for sticky region allocation in OFDMA communication systems
US8526390B2 (en) * 2008-06-12 2013-09-03 Qualcomm Incorporated Methods and systems for dynamic sticky region allocation in map-based communication systems
US8412222B2 (en) * 2008-06-27 2013-04-02 Qualcomm Incorporated Broadcast-multicast transmission with rate adaption
US8582436B2 (en) * 2008-09-03 2013-11-12 Nokia Siemens Networks Oy Resource allocation during silence period for a wireless network
KR101036482B1 (ko) 2009-02-03 2011-05-24 엘지전자 주식회사 무선 통신 시스템에서 임의 접속 방법
KR20100089728A (ko) 2009-02-03 2010-08-12 엘지전자 주식회사 무선 통신 시스템에서 확인 응답 전송 및 수신 방법
US8310921B2 (en) 2008-09-04 2012-11-13 Lg Electronics Inc. Method of random access in a wireless system
KR101018855B1 (ko) * 2008-12-18 2011-03-04 삼성전자주식회사 자원 할당 정보 전송 방법 및 그 장치
US8948069B2 (en) * 2009-01-09 2015-02-03 Qualcomm Incorporated Methods and systems for improving response message transmission reliability
KR101564107B1 (ko) * 2009-03-11 2015-10-29 삼성전자주식회사 통신 시스템에서 슬립모드 동작 제어 방법 및 장치
KR101011988B1 (ko) * 2009-03-13 2011-01-31 한국항공대학교산학협력단 다양한 개수의 안테나들을 구비하는 사용자 단말들을 포함하는 통신시스템에서 피드백 정보 송수신 방법 및 장치
WO2010117206A2 (fr) 2009-04-07 2010-10-14 엘지전자 주식회사 Procédé d'allocation de ressources dans un système d'accès radio à large bande
KR101638899B1 (ko) 2009-04-08 2016-07-12 엘지전자 주식회사 무선 통신 시스템에서 확인 응답 전송 및 수신 방법
CN101867882B (zh) * 2009-04-14 2015-10-21 中兴通讯股份有限公司 消息发送及消息反馈预处理方法
CN101867971B (zh) * 2009-04-14 2016-03-02 中兴通讯股份有限公司 持久资源的处理方法、终端以及基站
CN102415177A (zh) * 2009-04-22 2012-04-11 Lg电子株式会社 宽带无线连接系统的资源分配方法和执行该方法的装置
WO2010136069A1 (fr) * 2009-05-28 2010-12-02 Nokia Siemens Networks Oy Appareil et procédé de sélection d'un utilisateur parmi un groupe d'utilisateurs partageant un canal
KR20120017470A (ko) * 2009-06-16 2012-02-28 인터디지탈 패튼 홀딩스, 인크 동기 ｈａｒｑ 동작 및 간섭 회피를 위한 방법 및 장치
US20120099556A1 (en) * 2009-06-26 2012-04-26 Lg Electronics Inc. Method for reconfiguring user bitmap in wireless access system
US20120099555A1 (en) * 2009-07-10 2012-04-26 Panasonic Corporation Terminal apparatus, base station apparatus, feedback method and retransmission control method
CN101959161B (zh) * 2009-07-16 2014-12-10 中兴通讯股份有限公司 上行固定资源分配信令的发送及接收方法
US8477711B2 (en) * 2009-12-04 2013-07-02 General Electric Company Media access control scheme for a multi-frequency TDMA network
WO2011074780A2 (fr) * 2009-12-18 2011-06-23 Lg Electronics Inc. Procédé et appareil permettant de transmettre un signal de commande de liaison montante dans un système de communication sans fil
US8458548B2 (en) * 2009-12-22 2013-06-04 Intel Corporation Adaptive H-ARQ using outage capacity optimization
KR101653637B1 (ko) * 2009-12-30 2016-09-02 삼성전자주식회사 무선통신 시스템에서 효율적인 패스트 피드백 채널 운용 장치 및 방법
US9379867B2 (en) 2009-12-30 2016-06-28 Samsung Electronics Co., Ltd. Apparatus and method for efficiently operating fast feedback channel in wireless communication system
US8903441B2 (en) * 2010-02-23 2014-12-02 Lg Electronics Inc. Group resource allocation method and device in wireless access system
EP2543224A1 (fr) 2010-03-01 2013-01-09 InterDigital Patent Holdings, Inc. Procédé et appareil pour réaliser des attributions hybrides en liaison montante par station et par flux
US8780848B2 (en) * 2010-04-15 2014-07-15 Lg Electronics Inc. Method and apparatus for persistent resource allocation in a wireless access system
US20120066396A1 (en) * 2010-09-10 2012-03-15 Samsung Electronics Co. Ltd. Apparatus and method for supporting periodic multicast transmission in machine to machine communication system
WO2012050912A1 (fr) * 2010-09-28 2012-04-19 The Ohio State University Système et procédé pour attribution de ressources proactives
WO2012050913A1 (fr) * 2010-09-28 2012-04-19 The Ohio State University Procédé et système de réseau prédictif
CN102651679B (zh) * 2011-02-28 2016-02-03 华为技术有限公司 数据传输方法、演进基站以及用户设备
CA2832067C (fr) * 2011-04-01 2019-10-01 Interdigital Patent Holdings, Inc. Procede et appareil pour la commande de la connectivite a un reseau
CN102789398A (zh) * 2011-05-16 2012-11-21 中国联合网络通信集团有限公司 主机资源自适应管理方法和装置
KR101191220B1 (ko) * 2011-10-27 2012-10-15 엘지전자 주식회사 지속적 스케줄링 변경 정보를 전송 및 수신하는 방법 및 이를 위한 장치
US9408213B2 (en) * 2012-07-04 2016-08-02 Hitachi Kokusai Electric Inc. Wireless communication system, frequency channel sharing method, and network controller device
CN111614980B (zh) 2012-08-14 2022-04-12 俄亥俄州立创新基金会 用于通过移动设备来优化网络带宽的使用的系统和方法
EP3196406B1 (fr) * 2012-11-13 2018-08-22 Exxonmobil Upstream Research Company Méthode de détermination automatique du couple appliqué à un train de tiges de forage dans une position écartée du fond de puits
US9681465B2 (en) 2013-01-17 2017-06-13 Qualcomm Incorporated Methods and apparatus for power efficient operation of LTE based machine type communications
CN103973418B (zh) * 2013-01-29 2018-10-19 中兴通讯股份有限公司 一种基于信道激活检测的传输方法及装置
WO2015103746A1 (fr) * 2014-01-08 2015-07-16 Qualcomm Incorporated Amélioration de réseau mbsfn de petite taille
US11019620B2 (en) 2014-05-19 2021-05-25 Qualcomm Incorporated Apparatus and method for inter-band pairing of carriers for time division duplex transmit- and receive-switching and its application to multiplexing of different transmission time intervals
US11452121B2 (en) * 2014-05-19 2022-09-20 Qualcomm Incorporated Apparatus and method for synchronous multiplexing and multiple access for different latency targets utilizing thin control
US11297614B2 (en) 2014-09-01 2022-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Collision avoidance for uplink radio resource allocation in reoccurring time intervals
US20160128045A1 (en) * 2014-10-31 2016-05-05 Qualcomm Incorporated Reliable transmission of information on control channels
US10873538B2 (en) * 2015-05-05 2020-12-22 Avaya Inc. Automatic cloud capacity adjustment
JP6646738B2 (ja) * 2015-09-10 2020-02-14 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． データ伝送方法、端末及びｒａｎデバイス
US10285168B2 (en) * 2015-09-16 2019-05-07 Intel Corporation Systems and methods for elimination of PDCCH in resource allocation signaling for MTC devices
WO2017124297A1 (fr) * 2016-01-19 2017-07-27 华为技术有限公司 Procédé et dispositif de rétroaction pour un canal de liaison montante
TWI637642B (zh) * 2016-03-11 2018-10-01 華碩電腦股份有限公司 在無線通訊系統中輔助數據傳輸的方法與裝置
CN107222825B (zh) * 2016-03-21 2021-08-06 阿尔卡特朗讯 用于通信设备的方法、用于基站的方法、通信设备和基站
JP2019165268A (ja) * 2016-07-27 2019-09-26 シャープ株式会社 端末装置、基地局装置、通信方法、および、集積回路
KR102606781B1 (ko) * 2016-09-02 2023-11-27 삼성전자 주식회사 무선 통신 시스템에서 효율적인 데이터 송수신 방법 및 장치
US11582214B2 (en) * 2016-09-30 2023-02-14 Nokia Technologies Oy Updating security key
US10142967B2 (en) * 2017-03-10 2018-11-27 Mediatek Inc. Method of handling radio resource
BR112019019804A2 (pt) * 2017-03-23 2020-04-22 Fraunhofer Ges Forschung transmissão de pacote de dados confiável entre entidades de uma rede de acesso de rádio de uma rede de comunicação móvel
CN108667570A (zh) * 2017-03-27 2018-10-16 索尼公司 用于无线通信的网络控制端和网络节点的电子设备和方法
WO2019061145A1 (fr) * 2017-09-28 2019-04-04 Qualcomm Incorporated Techniques et appareils de gestion de ressources radio avec de multiples parties de bande passante
CN108401481B (zh) * 2017-11-16 2020-05-22 北京小米移动软件有限公司 物理层资源映射方法、装置、用户设备及基站
CN110139237B (zh) * 2018-02-02 2022-06-28 大唐移动通信设备有限公司 一种资源分配管理方法及设备
WO2020013422A1 (fr) * 2018-07-13 2020-01-16 한국과학기술원 Procédé et système de communication de coexistence mutuelle destinés à une communication à faible puissance à large bande
EP3834542A1 (fr) * 2018-08-09 2021-06-16 Telefonaktiebolaget LM Ericsson (publ) Attribution de ressources contiguës de fréquence en liaison montante à un groupe de dispositifs sans fil
KR20200035356A (ko) * 2018-09-25 2020-04-03 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 사이드 링크 전송을 위한 피드백 리소스를 유도하는 방법 및 장치
CN110972108B (zh) 2018-09-29 2021-12-28 华为技术有限公司 车联网消息交互方法以及相关装置
KR102262496B1 (ko) 2018-12-21 2021-06-07 한화솔루션 주식회사 염소 제조용 산화루테늄 담지 촉매의 제조방법 및 이에 의해 제조된 촉매
WO2020145890A1 (fr) * 2019-01-10 2020-07-16 Panasonic Intellectual Property Corporation Of America Appareil de communication et procédé de communication pour une attribution permanente
CN111488229B (zh) * 2019-01-29 2023-10-13 上海原动力通信科技有限公司 一种基站rru的老化处理方法及装置
WO2020166032A1 (fr) * 2019-02-14 2020-08-20 富士通株式会社 Système de communication et dispositif terminal
CN113490907B (zh) * 2019-03-01 2024-06-25 株式会社和冠 传感器控制器及笔
CN113826354A (zh) * 2019-11-13 2021-12-21 支付宝(杭州)信息技术有限公司 基于纠错码的区块链数据存储
US11375526B1 (en) * 2020-12-28 2022-06-28 Charter Communications Operating, Llc Uplink resource allocation in fixed wireless access systems using WiFi controller

Family Cites Families (53)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6862622B2 (en) 1998-07-10 2005-03-01 Van Drebbel Mariner Llc Transmission control protocol/internet protocol (TCP/IP) packet-centric wireless point to multi-point (PTMP) transmission system architecture
GB2341757B (en) 1998-09-21 2003-07-02 Fujitsu Ltd Code-division multiple access mobile comunications networks
KR100329182B1 (ko) * 2000-01-25 2002-03-22 박종섭 시디엠에이 매체 접근 제어 계층 처리부의 패킷 전송을위한 지정 채널 할당 방법
KR100790131B1 (ko) * 2001-08-24 2008-01-02 삼성전자주식회사 패킷 통신시스템에서 매체 접속 제어 계층 엔터티들 간의 시그널링 방법
JP3967115B2 (ja) 2001-11-22 2007-08-29 株式会社エヌ・ティ・ティ・ドコモ 基地局、無線リソース制御装置、端末装置、通信システム及び通信方法
US7609639B2 (en) * 2002-02-07 2009-10-27 Motorola, Inc. Negative acknowledgment (NAK) suppression
US6760671B1 (en) * 2002-04-09 2004-07-06 Cisco Technology, Inc. Method and apparatus of low power energy detection for a WLAN
US6987780B2 (en) * 2002-06-10 2006-01-17 Qualcomm, Incorporated RLP retransmission for CDMA communication systems
US7557433B2 (en) 2004-10-25 2009-07-07 Mccain Joseph H Microelectronic device with integrated energy source
EP1534039B1 (fr) * 2003-11-19 2013-01-16 Samsung Electronics Co., Ltd. Appareil et méthode pour la transmission et la réception d'informations de contrôle communes dans un système de communication sans fil
JP4723564B2 (ja) 2004-03-12 2011-07-13 テレフオンアクチーボラゲット エル エム エリクソン（パブル） 受信信号品質を推定する方法および装置
KR101053610B1 (ko) * 2004-06-25 2011-08-03 엘지전자 주식회사 Ｏｆｄｍ／ｏｆｄｍａ 시스템의 무선자원 할당 방법
KR100895165B1 (ko) * 2004-07-10 2009-05-04 삼성전자주식회사 직교 분할 다중 접속 시스템을 위한 동적자원할당방법
WO2006023575A2 (fr) * 2004-08-19 2006-03-02 Cognio, Inc. Systeme et procede de monde surveillance et de renfort de zone sans fil reglementee
WO2006046894A1 (fr) 2004-10-29 2006-05-04 Telefonaktiebolaget Lm Ericsson (Publ) Affectation de ressources dans des reseaux de communication
KR20060056141A (ko) * 2004-11-19 2006-05-24 삼성전자주식회사 직교 주파수 다중 접속 방식의 무선 통신 시스템에서자원할당 방법 및 시스템
JP5055132B2 (ja) * 2004-12-27 2012-10-24 パンテック カンパニー リミテッド 直交周波数分割多重化（ｏｆｄｍ）無線接続システムにおけるデータバースト割当方法及び自動再伝送要求（ｈａｒｑ）支援方法
US8031583B2 (en) * 2005-03-30 2011-10-04 Motorola Mobility, Inc. Method and apparatus for reducing round trip latency and overhead within a communication system
US8611284B2 (en) * 2005-05-31 2013-12-17 Qualcomm Incorporated Use of supplemental assignments to decrement resources
CA2610425C (fr) 2005-05-31 2016-09-27 Qualcomm Incorporated Reconnaissance d'assignation pour systeme de communication sans fil
US8654712B2 (en) * 2005-06-16 2014-02-18 Qualcomm Incorporated OFDMA reverse link scheduling
US20100146354A1 (en) * 2005-06-27 2010-06-10 Koninklijke Philips Electronics, N.V. Method and apparatus for h-arq in a wireless communication system
KR100703287B1 (ko) 2005-07-20 2007-04-03 삼성전자주식회사 통신 시스템에서 자원 할당 정보 송수신 시스템 및 방법
RU2378775C2 (ru) 2005-08-09 2010-01-10 Самсунг Электроникс Ко., Лтд. Способ и устройство выделения ресурсов связи с использованием виртуальной коммутации цепей в системе беспроводной связи и способ передачи и приема данных в мобильной станции, в которой он используется
US20070064665A1 (en) 2005-08-23 2007-03-22 Interdigital Technology Corporation Method and apparatus for accessing an uplink random access channel in a single carrier frequency division multiple access system
KR100770847B1 (ko) * 2005-09-29 2007-10-26 삼성전자주식회사 이동통신 시스템에서 패킷을 재전송하는 방법 및 장치와 그시스템
WO2007045101A2 (fr) * 2005-10-21 2007-04-26 Nortel Networks Limited Schema de multiplexage en mrof
US8452295B2 (en) * 2006-02-03 2013-05-28 Nokia Corporation Apparatus, method, and computer program product providing persistent uplink and downlink resource allocation
JP4960389B2 (ja) 2006-02-10 2012-06-27 クゥアルコム・インコーポレイテッド 不明瞭なｕｅ認証を用いる信号方式
KR101075777B1 (ko) * 2006-02-14 2011-10-24 한국과학기술원 무선 통신 시스템에서 자원 할당 정보 송수신 시스템 및방법
KR101086820B1 (ko) * 2006-03-14 2011-11-25 삼성전자주식회사 이동통신 시스템에서 복합 재전송 방법과 이를 위한 수신방법 및 장치
JP5031822B2 (ja) * 2006-04-11 2012-09-26 サムスン エレクトロニクス カンパニー リミテッド 移動通信システムにおけるパケットを不連続的に受信する方法及び装置
KR101254801B1 (ko) * 2006-04-19 2013-04-15 삼성전자주식회사 패킷 데이터 통신 시스템에서 데이터 제어 채널의 송수신방법 및 장치
EP3253115B1 (fr) * 2006-05-02 2021-02-17 Samsung Electronics Co., Ltd. Appareil et procédé de transmission/réception d'un paquet dans un système de communication mobile
EP1855410A3 (fr) * 2006-05-08 2013-02-13 Samsung Electronics Co., Ltd. Appareil et procédé de retransmission pour traitement de données à haute vitesse
KR20070109313A (ko) * 2006-05-10 2007-11-15 삼성전자주식회사 고속 데이터 처리를 위한 효율적인 재전송 요청 장치 및방법
US7944877B2 (en) * 2006-05-15 2011-05-17 Qualcomm Incorporated Apparatus and method for allocating resources in an orthogonal frequency division multiple access mobile communication system
US20080020778A1 (en) * 2006-07-19 2008-01-24 Samsung Electronics Co., Ltd. Method for efficient persistent resource assignment in communication systems
US8848618B2 (en) * 2006-08-22 2014-09-30 Qualcomm Incorporated Semi-persistent scheduling for traffic spurts in wireless communication
US20080062944A1 (en) * 2006-09-08 2008-03-13 Motorola, Inc. Apparatus and Method For Automatic Repeat Request Signalling With Reduced Retransmission Indications in a Wireless VoIP Communication System
EP1919160A1 (fr) * 2006-11-06 2008-05-07 Samsung Electronics Co., Ltd. Procédé et appareil de négociation de session dans un système de communications mobile
US9295003B2 (en) * 2007-03-19 2016-03-22 Apple Inc. Resource allocation in a communication system
US20080268850A1 (en) * 2007-04-30 2008-10-30 Motorola, Inc. Method and apparatus for handover in a wireless communication system
US8649334B2 (en) 2007-05-30 2014-02-11 Samsung Electronics Co., Ltd. Radio resource reallocating method for circuit mode
US8031656B2 (en) * 2007-06-14 2011-10-04 Telefonaktiebolaget Lm Ericsson (Publ) Semi-persistent resource allocation method for uplink transmission in wireless packet data systems
US8412209B2 (en) * 2007-06-18 2013-04-02 Motorola Mobility Llc Use of the physical uplink control channel in a 3rd generation partnership project communication system
RU2471291C2 (ru) * 2007-09-11 2012-12-27 Вай-Лэн, Инк. Распределение постоянных ресурсов
US20090075677A1 (en) 2007-09-14 2009-03-19 Sony Ericsson Mobile Communications Ab Dynamically Updated Proximity Warning
KR20090030562A (ko) * 2007-09-20 2009-03-25 엘지전자 주식회사 광대역 무선 접속 시스템에서 자원할당을 위한 패킷전송방법
US8072875B2 (en) * 2007-11-27 2011-12-06 Intel Corporation Avoiding collisions between users if MAP containing persistent scheduling information is lost
US8244265B2 (en) * 2007-11-28 2012-08-14 Motorola Mobility Llc Techniques for aligning application output and uplink resource allocation in wireless communication systems
WO2018141091A1 (fr) * 2017-02-04 2018-08-09 华为技术有限公司 Procédé d'émission d'informations, procédé de réception d'informations, et dispositif
US11044730B2 (en) * 2018-09-25 2021-06-22 Qualcomm Incorporated Multiple semi-persistent scheduled transmission control by a single downlink control information message

Also Published As

Publication number Publication date
US20210153201A1 (en) 2021-05-20
JP2010539794A (ja) 2010-12-16
US20090075667A1 (en) 2009-03-19
EP4216477A1 (fr) 2023-07-26
CN101855843A (zh) 2010-10-06
KR20100070355A (ko) 2010-06-25
CN101855843B (zh) 2016-05-04
US10932265B2 (en) 2021-02-23
US20220124715A1 (en) 2022-04-21
KR20160039692A (ko) 2016-04-11
JP2016001920A (ja) 2016-01-07
JP2014030211A (ja) 2014-02-13
KR20150033741A (ko) 2015-04-01
US20140241292A1 (en) 2014-08-28
EP2195946A4 (fr) 2012-05-30
KR101725751B1 (ko) 2017-04-10
WO2009035905A3 (fr) 2009-04-30
EP2195945A4 (fr) 2012-05-30
KR101548392B1 (ko) 2015-08-28
RU2010114293A (ru) 2011-10-20
US8423853B2 (en) 2013-04-16
KR101606899B1 (ko) 2016-03-28
US8732541B2 (en) 2014-05-20
US11212804B2 (en) 2021-12-28
KR20150017004A (ko) 2015-02-13
US20160037529A1 (en) 2016-02-04
JP5801360B2 (ja) 2015-10-28
JP2010539795A (ja) 2010-12-16
US20130223388A1 (en) 2013-08-29
WO2009035905A2 (fr) 2009-03-19
KR101702821B1 (ko) 2017-02-06
EP2195946B1 (fr) 2020-03-04
KR20150046388A (ko) 2015-04-29
KR20100084512A (ko) 2010-07-26
KR101548026B1 (ko) 2015-08-27
JP6466994B2 (ja) 2019-02-06
KR20170015533A (ko) 2017-02-08
US20190098630A1 (en) 2019-03-28
JP6482987B2 (ja) 2019-03-13
MX2010002747A (es) 2011-02-25
JP2017158207A (ja) 2017-09-07
RU2471291C2 (ru) 2012-12-27
WO2009035904A3 (fr) 2009-05-14
US20230239849A1 (en) 2023-07-27
US20120213179A1 (en) 2012-08-23
CN101849375A (zh) 2010-09-29
KR101561812B1 (ko) 2015-10-21
US8169960B2 (en) 2012-05-01
EP3672137A1 (fr) 2020-06-24
JP5362726B2 (ja) 2013-12-11
BRPI0815862A2 (pt) 2015-09-29
US11611964B2 (en) 2023-03-21
JP5408673B2 (ja) 2014-02-05
US9161341B2 (en) 2015-10-13
US10142988B2 (en) 2018-11-27
EP2195945A2 (fr) 2010-06-16
WO2009035904A2 (fr) 2009-03-19
MX2010002748A (es) 2011-02-25
RU2010114250A (ru) 2011-10-20
KR20150034820A (ko) 2015-04-03
KR101606900B1 (ko) 2016-03-28
US20090070650A1 (en) 2009-03-12
EP2195946A2 (fr) 2010-06-16
RU2492577C2 (ru) 2013-09-10
US8908623B2 (en) 2014-12-09
CN101849375B (zh) 2016-07-13

Similar Documents

Publication Publication Date Title
US11611964B2 (en) Base station configured for operation based on persistent resource allocation information
KR20080065890A (ko) 무선통신 시스템에서 애크/내크 채널 자원을 할당하고시그널링하는 방법 및 장치
KR20090055900A (ko) 스케줄링 정보에 관한 데이터의 전송방법
JP2010524389A (ja) 通信システムにおける方法および装置
US8464127B2 (en) Method and apparatus for transmitting and receiving data in resource allocation in wireless communication system
JP2008067171A (ja) 無線通信システム、基地局、無線通信端末及び無線通信方法

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AC Divisional application: reference to earlier application

Ref document number: 2195946

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20201222

RBV Designated contracting states (corrected)

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 1/00 20060101ALI20221021BHEP

Ipc: H04L 5/00 20060101AFI20221021BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20221205

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AC Divisional application: reference to earlier application

Ref document number: 2195946

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602008064718

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1554605

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230415

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230411

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230615

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1554605

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230315

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230616

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20230719

Year of fee payment: 16

REG Reference to a national code

Ref country code: HU

Ref legal event code: AG4A

Ref document number: E062154

Country of ref document: HU

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230717

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230713

Year of fee payment: 16

Ref country code: FI

Payment date: 20230912

Year of fee payment: 16

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230715

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20230630

Year of fee payment: 16

Ref country code: HU

Payment date: 20230811

Year of fee payment: 16

Ref country code: FR

Payment date: 20230703

Year of fee payment: 16

Ref country code: DE

Payment date: 20230712

Year of fee payment: 16

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602008064718

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

26N No opposition filed

Effective date: 20231218

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230904

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20230930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20230904

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230315