Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/10—Flow control; Congestion control
  • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
  • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
  • H04L47/2433—Allocation of priorities to traffic types
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/12—Wireless traffic scheduling
  • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
• • 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/14—Two-way operation using the same type of signal, i.e. duplex
  • H04L5/1469—Two-way operation using the same type of signal, i.e. duplex using time-sharing
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
  • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
  • H04W52/04—Transmission power control [TPC]
  • H04W52/30—Transmission power control [TPC] using constraints in the total amount of available transmission power
  • H04W52/36—Transmission power control [TPC] using constraints in the total amount of available transmission power with a discrete range or set of values, e.g. step size, ramping or offsets
  • H04W52/367—Power values between minimum and maximum limits, e.g. dynamic range
• • 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/0446—Resources in time domain, e.g. slots or frames
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/12—Wireless traffic scheduling
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/50—Allocation or scheduling criteria for wireless resources
  • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/10—Flow control between communication endpoints
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W84/00—Network topologies
  • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
  • H04W84/04—Large scale networks; Deep hierarchical networks
  • H04W84/042—Public Land Mobile systems, e.g. cellular systems

Definitions

• This invention generally relates to the procedures used by the MAC
• the invention relates to method and algorithm for data transmission in a UMTS network.
• Transport channels form the interface between the MAC layer and the physical layer.
• a set of transport channels is combined to form a Coded Composite
• CCTrCH Transport Channel
• TFCS Transport Format Combination Set
• TFC Transport Format Combination
• the TF defines the data rate of a transport channel by setting the Transmission Time Interval (TTI) (in ms), the Transport Block (TB) size (in bits) and the Transport Block Set (TBS) size (in number of blocks).
• TTI Transmission Time Interval
• TB Transport Block
• TBS Transport Block Set
• a TB is the basic unit exchanged between the MAC and physical layers.
• a TBS is defined as a set of TBs, which are exchanged between physical and MAC layers at the same time and using the same transport channel.
• TTI is defined as the inter-arrival time of TBSs.
• a TTI is equal to the periodicity at which a TBS is transferred from the MAC to the physical layer and then by the physical layer onto the radio interface.
• the MAC gets data from the radio link control (RLC) layer.
• the interface between the MAC layer and the RLC layer is formed by logical channels, or radio bearers (RB). Each transport channel can carry more than one RB.
• the RLC maintains a buffer for each RB; each buffer contains a set of RLC service data units (SDUs).
• SDUs RLC service data units
• Some RLC configurations (but not all) allow the segmentation of SDUs into protocol data units (PDUs), some allow the concatenation of SDUs to build PDUs and some allow the use of padding PDUs.
• PDUs protocol data units
• PDUs protocol data units
• a MAC header may be added to the PDU to form a TB.
• the MAC layer selects the PDU sizes for a given TTI and requests these PDUs from the RLC layer.
• the RLC then segments and/or concatenates the SDUs in order to satisfy the MAC request.
• the MAC then builds the TBs and sends the TBs to the physical layer to be sent over the air in the next TTI.
• This invention provides a method and an algorithm for TFC selection wherein the need for the MAC to determine the power needed by each
• TFC in each time slot is obviated.
• the following description sets forth the MAC procedure to schedule data transmission wherein the scheduling may involve the selection of a TFC to be used and the selection of RBs to be serviced.
• S-RNC Serving-RNC
• UMTS universal mobile telecornmunication service
• TDD time division duplex
• All TFCs in the candidate set must generally satisfy the following six (6) rules: 1) belong to the TFCS; 2) not carry more bits than can be transmitted in a TTI; 3) respect the TTI compatibility (i.e., the TF of a TrCH cannot change in the middle of the TTI of the TrCH); 4) not be in the blocked state, as defined below; 5) be compatible with the RLC configuration; and 6) not require RLC to produce padding PDUs. If all TFCs in the TFCS require padding PDUs, this last requirement can be ignored.
• the present invention provides solutions for the last three (3) requirements. [0016]
• the blocking criterion is defined as follows:
• the UE In the case of a single CCTrCH or multiple CCTrCHs having mutually exclusive timeslot assignments, the UE considers the blocking criterion for a given TFC of a CCTrCH to be fulfilled if, for three (3) successive frames, the estimated UE transmit power is greater than the maximum UE transmitter power for at least one timeslot associated with the CCTrCH in each frame.
• the UE In the case of multiple CCTrCHs that do not have mutually exclusive timeslot assignments, if, for a given CCTrCH for three (3) successive frames, the estimated UE transmit power is greater than the maximum UE transmitter power for at least one timeslot associated with the CCTrCH in each frame, the UE considers the blocking criterion for a given TFC to be fulfilled if the use of this TFC will cause the estimated UE transmit power to continue to be greater than the maximum UE transmitter power in at least one timeslot associated with the CCTrCH.
• the UE must not consider the unblocking criterion for a given TFC (that has been blocked) to be fulfilled until the use of this TFC will not cause the estimated UE transmit power to be greater than the maximum UE transmitter power for all uplink (UL) timeslots associated with the TFC for a minimum of three (3) successive frames.
• the number of said successive frames may be greater than or lesser than three (3) without departing from the spirit and scope of the invention.
• the number of successive frames could be as few as two (2) or four (4) or more, with three (3) consecutive frames being preferred. This is also the case for all subsequent criteria for non- mutually exclusive timeslot arrangements for UEs and S-RNCs.
• the MAC is divided in MAC-c and MAC-d.
• MAC-c is responsible for common channels and MAC-d is responsible for dedicated channels.
• MAC-d is responsible for dedicated channels.
• TFC selection is done in MAC-c and MAC-d.
• the RLC configuration plays an important role during TFC selection. Depending on the amount of data available for transmission, some TFCs in the TFCS may not conform to the RLC configuration.
• Padding compatibility i.e., need for padding PDUs
• To check for padding compatibility one needs to check if a TFC requires padding PDUs from a transport channel that only carries logical channels that cannot provide padding PDUs, (i.e., logical channels in RLC-TM (transparent mode)). If so, then the TFC is incompatible with the RLC configuration and is considered invalid.
• the TF determines the number of TBs and the TB size needed.
• the number of PDUs for that logical channel is equal to the total number of SDUs in that logical channel available for transmission
• the number of PDUs for that transport channel is determined by summing the number of PDUs for each logical channel mapped to that transport channel.
• the TFC can be supported in terms of padding PDUs if the number of PDUs for that transport channel is greater than or equal to the number of TBs in the TF.
• the minimum TFC set is the set that allows the transmission of one TB of the highest priority transport channel that has data to be sent.
• the minimum TFC set includes all TFCs that have a "minimum size compatible TF" for one transport channel and empty TFs for all other transport channels, where the "minimum size compatible TF" is defined as:
• the "minimum size compatible TF" is the TF with one TB with “RLC Size” equal to the RLC PDU size.
• the "minimum size compatible TF" is the TF with one transport block with "RLC Size” equal to the RLC SDU size considered.
• the "minimum size compatible TF" is the TF such that the number of transport blocks multiplied by the "RLC Size” is equal to the RLC SDU size considered.
• TF is the TF with a single transport block (of any size since there is no restriction on PDU size for UM). If there is more than one TFs with a single transport block defined, the "minimum size compatible TF" is the one with minimum transport block size.
• the physical layer sends a notification along with the timeslot number to the MAC layer that the maximum power was reached.
• the MAC determines which CCTrCHs have allocated codes in the timeslot that reached maximum power and marks such CCTrCHs as having reached maximum power. When a CCTrCH reaches maximum power, the MAC will check whether or not it should "step down":
• Stepping down Each time a CCTrCH reaches maximum transmit power for three (3) consecutive frames, the MAC will limit the candidate TFC set to the minimum TFC set in the next common TTI boundary (common TTI to all transport channels in the CCTrCH).
• step up For stepping up, after every frame of operation of a CCTrCH at the minimum TFC set, the MAC will predict the power needed by the full TFC set of that CCTrCH in the next frame. If the predicted transmit power in all timeslots of the CCTrCH is less than the maximum allowed UE transmit power for three (3) consecutive frames, then the full TFC set can be included in the candidate TFC set. Otherwise, the minimum TFC set will be used.
• the MAC will either allow the full set (in terms of power) or the minimum set. This is a low cost solution that avoids the need for the MAC to determine the power needed by each TFC in each timeslot.
• power prediction in order to check if the full set can be supported, it is sufficient to check if the TFC that requires maximum transmit power can be supported.
• the TFC that requires maximum transmit power may be different for each timeslot (i.e., each timeslot has associated with it a TFC that requires maximum transmit power).
• One solution for this problem is for the MAC to know the procedure used by the physical layer to "fill up" timeslots and codes.
• each timeslot will depend on the TFC being used, since the transmit power is a function of the beta (fi) factors and number of codes used by the TFC in the timeslot, and each TFC may have a different beta factor and different data rate (and thus, different number of codes used).
• the MAC predicts the transmit power in each timeslot of the CCTrCH by considering the worst case scenario, by assuming that: all the assigned codes are being used in that timeslot (all codes even if they are from different CCTrCHs); and the highest beta factor among all TFCs in the TFCS is being used.
• the requirement for padding PDUs needs to be followed only if no TFCs are available among the TFCs that do not require padding PDUs. In other words, if there are TFCs available in the candidate TFC set that do not require padding PDUs, then one of those should be selected, instead of selecting a TFC that requires padding. It should be noted that, for all TFCs that require padding, PDUs from logical channels that cannot produce padding PDUs (i.e., RLC-TM logical channels) are eliminated from the candidate TFC set when the RLC configuration requirements are checked for padding compatibility.
• the TFCs that require padding PDUs and are in the candidate TFC set require padding PDUs from logical channels that can produce padding. Whether or not padding PDUs are needed for a given TFC, depends on the RLC buffer occupancy (amount of data that needs to be sent). In order to create a set with only TFCs that do not require padding PDUs, all TFCs must be tested at every TTI. However, this is an expensive solution.
• TFCs that do not require padding PDUs while performing TFC selection algorithm, as set forth below.
• all TFCs that satisfy the five requirements stated supra will be part of the candidate TFC set, and the requirement regarding padding PDUs will be fulfilled, whenever possible, at each TFC selection iteration.
• a chosen TFC must be selected from the candidate set and must satisfy the following criteria (and in the order in which they are listed): a) no other TFC allows the transmission of higher priority data than the chosen TFC; b) no other TFC allows the transmission of more data from the next lower priority channels, and c) no other TFC has a lower bit rate than the chosen TFC.
• Figures la through Id comprise a flow chart for MAC-c TFC selection algorithm implementation
• Figure 1 shows the manner in which Figures 1A through ID are arranged to form the flow chart
• Figures 2A through 2D comprise a flowchart for MAC-d TFC selection algorithm implementation
• Figure 2 shows the manner in which Figures 2 A through 2D are arranged to form the flow chart.
• Figure 3 is a flowchart for an RNC MAC-d SDU size selection procedure.
• each logical channel has an associated MLP (MAC Logical Channel Priority).
• MLP MAC Logical Channel Priority
• MLP determines the priority of the logical channel.
• the rules described in the following paragraph are based on MLPs:
• the algorithm iterates per logical channel priority (tries to serve logical channels of highest priority first), as opposed to per transport channel.
• TFC selection is to determine how much data of each priority each TFC can carry (starting with the highest priority), and then select one based on the requirements (maximizing the throughput of higher priority data). However, this requires going over all TFCs in the candidate set.
• the solution proposed here is to identify the amount of highest priority data that each TFC can carry, and then eliminate those that provide lower throughput from the candidate set. In the next iteration (for the next highest priority data), only the new set is considered.
• the final TFC selected may require padding PDUs, and the whole procedure would need to be repeated without the given TFC, until a TFC that does not require padding is found (and if no such TFC is found, the first TFC selected would be used).
• the solution proposed here is to assure that at least one TFC that does not require padding remains on the candidate set. As discussed before, certain candidate sets may have no such TFC, in which case, the above stated "candidate set" requirement need not be satisfied.
• the candidate set does not contain at least one TFC that is "filled up" (i.e., all transport blocks being used)
• a TFC that does not require padding PDUs but does not maximize throughput
• the candidate set does not contain at least one TFC that is "filled up" (i.e., all transport blocks being used)
• a TFC that does not require padding PDUs but does not maximize throughput
• the one that maximizes the throughput of the highest priority data is chosen. If more than one TFC that does not require padding has the same throughput for the highest priority data, then the TFC that maximizes throughput of the next highest priority data is chosen. This rule should be applied recursively for all priority levels.
• SDUs from logical channels with the priority are considered data with priority p.
• the candidate TFC set is referred to as TFC_Can.
• the algorithm should run only if the TFC set has valid TFCs (TFCs with data rate greater than zero). [0061] The following algorithm (shown in Figure 2) is performed for MAC-d
• S5 Check if there is at least one TFC with at least one TB available in the TFC_Can (candidate TFC set). a. If yes, S5a, go to step S6. b. If no, S5b, go to step S25 (all TFCs filled, select one). S6: Select the first TFC with at least one TB available from
• TFC_Can (candidate TFC set).
• S7 Check if there is a logical channel with priority p such that: the logical channel has available PDUs to be sent; the logical channel is not blocked for this TFC; and the transport channel that is mapped to that logical channel has available TBs. a. If yes, S7a, to go S9 and select that logical channel. If there is more than one such logical channel, select one randomly. Then go to step S10. b. If no, S7b, go to step S16 (no more data with priority
• S10 Check if there is a restriction on PDU sizes for the selected logical channel. a. If yes, SlOa, go to step Sll and check if the TB size of the transport channel is the same size as the PDU size +
• Update logical channel information as follows: a. This logical channel is blocked for this TFC selection (logical channel already served). 3. Go to S14, update TB information as follows: a. TBs used are not available anymore for this TFC selection.
• step S15 check if all the TBs in this TFC are filled. a. If yes, S15a, go to step S16 (no more space in this TFC). b. If no, S15b, return to step S7.
• Num__Bits(p,i, j) denote the number of bits of priority p data that can be transmitted on DCH iwhen using TFC j (i.e., TB size times the number of TBs being sent, including any RLC and/or MAC header that is applicable and/or padding bits).
• the normalized throughput of DCH is computed as: 10 YYis Tl ⁇ roughput(p,i, j) - Num_Bits(p,i, j)
• TTI Length(i, j) is the TTI length of TF for TrCH i given TFC j.
• the total optimal throughput of priority p data for the CCTrCH is the sum of every DCH's normalized throughput of this priority data.
• Total _Throughput(p, j) Throughput(p, i, j) i
• TFC_Can check if there are more TFCs in TFC_Can a. If yes, S17a, select the next TFC and go back to step S7. b. If no, S17b, (all TFCs were checked), go to step S18.
• TFC k wcgmax ⁇ Total _Throughput(p, j) ⁇ Equation 2 j
• TFC_NoPad TFCs that do not require padding
• TFC_NoPad select the TFC that provides highest "total optimal throughput" for priority p data.
• step S25 check if there is at least one TFC in TFC_Can that does not require padding PDUs. a. If yes, S25a, go to step S26. b. If no, S25b go to step S27.
• TFC_Can that does not require padding. If there is more than one TFC available that does not require padding, among those, select the TFC that provides the minimum data rate.
• the TFC Selection in the MAC layer is done in both MAC-c and MAC-d entities.
• MAC-c is located in the Controlling-RNC (C- RNC) and there is one MAC-c per cell;
• MAC-d is located in the S-RNC and there is one MAC-d for each UE.
• FACH forward access channel
• C-RNC MAC-c
• S-RNC MAC-d
• FACH Priority Indicator MAC-c
• the MAC-d selects an SDU size for each priority, and send the data to the MAC-c.
• the MAC-c buffers this data, before it is transmitted.
• the RNC MAC-d TFC selection algorithm is similar to that for the
• UE MAC-d with the exception that on the RNC side there is no restriction on the transmit power, and hence will not be presented here.
• the procedure discussed in the previous section applies to MAC-d in both UE and RNC sides.
• the MAC specification does not specify any requirements for TFC selection on RNC. However for the UE to decode the data properly, there are some requirements that must be followed. These requirements are summarized below. [0070] Before selecting a TFC for the case of MAC-c, the set of valid TFCs must be established. This set is referred to as the "candidate set". All TFCs in the candidate set must:
• the chosen TFC must be selected from the candidate set and must satisfy the following criteria in the order in which they are listed below:
• the data that is received from MAC-d is buffered in MAC-c. This can be done by either having one queue per UE, or one queue for all the UEs, or one queue for each priority. It is proposed to have one queue per priority, as doing so would make it easier to maintain first in first out order.
• the first approach would require the buffer to be time stamped in order to maintain the order, while the second approach would require coordination of the priorities.
• MAC-c can schedule data on any of the
• FACHs mapped on the coded composite channel If data from a logical channel is sent on a transport channel with TTI of length 't', data from the same logical channel should not be sent on other transport channels, for the duration oft' as this can lead to an out-of-order problem in the receiving side RLC (i.e., the UE side).
• UE is blocked for a period 't', if data from this UE of that priority is sent on a transport channel with TTI period 't'. This increases the amount of data that can be sent out from all UEs and also solves the out of order problem.
• MAC-c can request padding PDUs only from CCCH
• RLC entity If CCCH is blocked and if padding PDUs are required, MAC-c requests only padding PDUs from RLC.
• a buffer with transferred PDUs is referred to as a "logical channel”.
• the candidate TFC set is referred to as TFC_Can
• the algorithm should run only if the TFC set has valid TFCs (TFCs with data rate greater than zero) Making reference to Figures 1A to ID, the following steps are performed for the MAC-c TFC selection algorithm:
• TFC_Can (candidate TFC set)
• S4 Check if there is a logical channel with priority p such that: the logical channel has available PDUs to be sent; if the selected logical channel is a CCCH, the logical channel is not blocked for the selected TFC; if the selected logical channel is of transferred PDUs then check if; there is a least one PDU that is not blocked for the selected TFC; and the selected logical channel is not blocked for this TFC. a. If yes, S4a, go to S5 and select that logical channel. If there is more than one such logical channel, select one randomly. Go to step S6. b. If no, S4b, go to S17 (no more data with priority p).
• S6 Check if there is a restriction on PDU sizes for the selected logical channel. a. If yes, S6a, go to S7 and check if there is a TB available with the same size as the PDU size + MAC header, i. If yes, S7a, go to S8 and: 1. select the transport channel with that TB size. If more than one are available, select a transport channel that gives the maximum available data rate, as follows: MAX ⁇ (number of available TBs)/TTIsize ⁇ ; and 2. select PDUs that are not blocked from this logical channel to fill up as many available TBs as possible in the transport channel. PDU selection must respect FIFO; blocked PDUs must be skipped.
• Update buffer information as follows: a. PDUs selected are not available for this TFC selection, then go to Sll and: Update TB information as follows: a. TBs used are not available anymore for this TFC selection. Then go to step S14. ii. If no, S7b, go to S9 to perform:
• step S6b go to S10 and: i. select a transport channel that gives the maximum available data rate, as follows:
• step Sll to update TB information as follows:
• S12a If the selected logical channel is a CCCH, S12a, go to S14 and: Consider the CCCH to be blocked for this TFC during this TFC selection (for the next steps of the TFC selection for this TTI). 3. If the selected logical channel is not a CCCH, S12b, go to S13 to determine:
• step S16 check if all the TBs in this TFC are filled. a. If yes, S16a, go to step S17 (no more space in this TFC). b. If no, S16b, return to step S4.
• Num _ Bits(p, i, j) denote the number of bits of priority p data that can be transmitted on FACH . when using TFC (i.e., TB size times the number of TBs being sent, including any RLC and/or MAC header that is applicable and/or padding bits).
• TTI Length(i, j) is the TTI length of TF for TrCH i given TFC j.
• the total optimal throughput of priority/) data for the CCTrCH is the sum of every FACH's normalized throughput of this priority data.
• Total y ⁇ %roughput(p, j) ⁇ j Tl ⁇ roughput(p, i, j) i
• step S18 check if there are more TFCs in TFC_Can. a. If yes, S18a, select the next TFC and return to step S4. b. If no, S18b, (all TFCs were checked), go to step S19.
• TFC k there is at least one TFC, say TFC k, that provides the highest "total optimal throughput" for priority/., such as: lc - argmax ⁇ T ta/ _Throughput(p, j) ⁇ Equation 4
• At S20 check if there is at least one TFC in TFC_Can that has all the TBs filled (does not require padding). a. If not, S20a, go to S21 and check if there is at least one TFC that does not belong to TFC_Can and that has all TBs filled. i. If yes, S21a, go to S22 to:
• TFC_NoPad TFCs that do not require padding
• step S23 check if all TFCs in TFC_Can have all the TBs filled. a. If yes, S23a, go to step S26 (TFC selection is done). b. If no, S23b, go to step S24.
• step S26 check if there is at least one TFC in TFC_Can that does not require padding PDUs. a. If yes, S26a, go to step S27. b. If no, S26b, go to step S28.
• TFC_Can that provides the minimum data rate. If there is more than one TFC available with the same number of bits, select one randomly. Fill in the unfilled PDUs in the TFC with padding PDUs from RLC (CCCH). After either S27 or S28, go to S29.
• each PDU that is in that buffer and has the UE ID equal to the UE ID of a PDU selected for this TFC is considered to be blocked for all TFCs for a period of time equal to the TTI of the transport channel selected for that logical channel.
• Figure 1 which shows the flowchart for the MAC-c TFC selection algorithm implementation, includes more steps than the algorithm of Figure 2.
• the MAC-d can be configured with a set of allowed SDU sizes (the allowed sizes depend on the TFCS of the S-CCPCH (Secondary Common Control Channel)) for each common transport channel priority indicator (FACH priority).
• a FACH flow control frame is used by the C-RNC to control the user data flow. It may be generated in response to a FACH Capacity Request or at any other time.
• the FACH Flow control frame shall contain the number of credits the S- RNC MAC-d entity is allowed to transmit.
• MAC-d selects a SDU size (from within the configured set) for each logical channel, depending on the logical channel buffer occupancy (BO) and the number of available credits for that FACH priority.
• MAC-c SDUs of same size and same FACH priority may be transmitted in the same FACH data frame.
• the SDU size selection for a logical channel depends on the corresponding RLC configuration, the logical channel BO, and the number of available credits for that FACH priority.
• MAC-d In order to send SDUs to the MAC-c, MAC-d follows the following procedure (See Figure 3):
• SI Select the highest priority (i.e., highest MLP).
• S2 Select a logical channel with that priority. If there is more than one logical channel with that priority, select one randomly.
• S3 Based on the buffer occupancy of the logical channel, select the SDU size to be used for that logical channel, as follows: - Based on the number of "credits" available in MAC-d, determine the amount of information bits that can be transmitted by using each PDU size (not including padding bits). For each PDU size, the amount of information bits is given by:
• S5b go to S6.
• S6 build one "Iur" FACH data frame for each SDU size (for a given priority).
• the SDU size is the same for a given logical channel, but may be different for different logical channels of the same priority.
• the order of the SDUs for each logical channel must be maintained inside the data frame.
• S7 check if there are more logical channels available.
• TFC selection was described.
• static logical channel mode-based configuration information
• dynamic buffered data information
• the RLC provides the MAC with the buffer occupancy (BO), which is the total amount of data buffered in the RLC.
• BO buffer occupancy
• the RLC protocol specification (3GPP TS 25.322) also states that the RLC needs to provide "RLC Entity Info" to the MAC.
• the RLC protocol specification (3GPP TS 25.322) does not specify what the "RLC Entity Info" must contain.
• TFC Restriction Variables provide information about the PDUs and/or SDUs buffered in the RLC that are available for transmission in the next TTI.
• the MAC specifies the
• the RLC cannot create PDUs ahead of the TTI, and only information based on the buffered SDUs can be provided by the RLC in advance of transmission.
• the PDU size is fixed, and therefore information based on the buffered PDUs can be provided by the RLC.
• the TFC restriction variables can contain the RLC mode itself. However, since providing the RLC mode requires the MAC to make assumptions about the RLC buffered data characteristics based on the RLC mode, then the data characteristics themselves are provided instead. [0091] Since TFC selection depends upon the amount of data that is available for transmission in a given TTI, the TFC restriction variables include the SDU/PDU size and the number of SDUs/PDUs buffered in the RLC. [0092] Depending on the RLC mode, and also in order to avoid data transmission conflicts, only some of the data buffered in the RLC may be available for transmission.
• the sizes and UE Id Types of all of the PDUs transmitted to the MAC in one TTI must be the same.
• the information reported to the MAC must guarantee that the TFC is selected so that these two restrictions are not violated. Therefore, only information for SDUs and PDUs that are the same size and UE Id Type is provided. Since the data must be transmitted in the order it was received, the RLC reports only the number of consecutive SDUs/PDUs in the RLC transmission buffer (starting from the oldest SDU/PDU) that are the same size and the same UE Id Type. [0094] For transparent mode with segmentation configured, only one SDU can be transmitted per TTI, and therefore the RLC will report that only one SDU is available for transmission.
• a logical channel can carry RLC SDU data (received from the upper layer) and/or RLC peer-to-peer control data.
• the amount of available PDU data for an acknowledged mode logical channel is therefore restricted by the type of RLC data that it can support.
• the amount of available PDU data is also restricted by the size of the logical channel's RLC transmit window. Note that the RLC transmit window size is statically configured in the RLC.
• the MAC needs to know how much of the TB is taken up by the MAC header. Since the TB header size depends on the UE Id
• the TFC restriction variables also contain the UE Id Type.
• the MAC protocol specification (3GPP TS 25.321) states that the UE Id Type is provided by the RLC to the MAC for each data transmission.
• the TFC restriction variables include a segmentation indicator. Note that this indicator is statically configured in the RLC.
• padding information needs to be known by the MAC in order to be able to perform TFC selection. Since padding is only supported in certain RLC modes (UM and AM modes only), a padding PDU indicator is also included in the TFC restriction variables.
• TDD time division duplex
• FDD frequency division duplex

Landscapes

• Engineering & Computer Science (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• Mobile Radio Communication Systems (AREA)
• Small-Scale Networks (AREA)
• Communication Control (AREA)
• Information Transfer Between Computers (AREA)
• Computer And Data Communications (AREA)

Priority Applications (15)

Applications Claiming Priority (2)

Publications (1)

Family

ID=32682284

Family Applications (1)

Country Status (16)

Cited By (13)

Families Citing this family (49)

Citations (4)

Family Cites Families (62)

• 2003
  • 2003-12-19 JP JP2004563853A patent/JP4271659B2/ja not_active Expired - Fee Related
  • 2003-12-19 AT AT03814239T patent/ATE417418T1/de not_active IP Right Cessation
  • 2003-12-19 KR KR1020057011674A patent/KR100772470B1/ko not_active Expired - Fee Related
  • 2003-12-19 TW TW095146539A patent/TWI333754B/zh not_active IP Right Cessation
  • 2003-12-19 MX MXPA05006600A patent/MXPA05006600A/es active IP Right Grant
  • 2003-12-19 KR KR1020057017371A patent/KR100947914B1/ko not_active Expired - Fee Related
  • 2003-12-19 AU AU2003301161A patent/AU2003301161B2/en not_active Ceased
  • 2003-12-19 TW TW092136328A patent/TWI257796B/zh not_active IP Right Cessation
  • 2003-12-19 CN CN2008101868228A patent/CN101483454B/zh not_active Expired - Fee Related
  • 2003-12-19 EP EP08168313.8A patent/EP2017972B1/en not_active Expired - Lifetime
  • 2003-12-19 KR KR1020097014451A patent/KR101010983B1/ko not_active Expired - Fee Related
  • 2003-12-19 KR KR1020107000353A patent/KR20100018053A/ko not_active Withdrawn
  • 2003-12-19 EP EP14165482.2A patent/EP2785121B1/en not_active Expired - Lifetime
  • 2003-12-19 DK DK03814239T patent/DK1573935T3/da active
  • 2003-12-19 SG SG200703389-7A patent/SG159386A1/en unknown
  • 2003-12-19 KR KR1020087030844A patent/KR100979161B1/ko not_active Expired - Fee Related
  • 2003-12-19 KR KR1020107013083A patent/KR20100087219A/ko not_active Withdrawn
  • 2003-12-19 WO PCT/US2003/040702 patent/WO2004059869A1/en not_active Ceased
  • 2003-12-19 CA CA2511324A patent/CA2511324C/en not_active Expired - Fee Related
  • 2003-12-19 CN CN2003801067511A patent/CN1729630B/zh not_active Expired - Fee Related
  • 2003-12-19 EP EP03814239A patent/EP1573935B1/en not_active Expired - Lifetime
  • 2003-12-19 DE DE60325272T patent/DE60325272D1/de not_active Expired - Lifetime
  • 2003-12-19 TW TW093120827A patent/TWI337470B/zh not_active IP Right Cessation
  • 2003-12-19 US US10/742,539 patent/US7058032B2/en not_active Expired - Lifetime
  • 2003-12-19 EP EP14165479.8A patent/EP2797376B1/en not_active Expired - Lifetime
  • 2003-12-19 ES ES03814239T patent/ES2316874T3/es not_active Expired - Lifetime
• 2005
  • 2005-07-14 NO NO20053421A patent/NO337783B1/no not_active IP Right Cessation
• 2006
  • 2006-05-04 US US11/417,593 patent/US7596117B2/en not_active Expired - Lifetime
• 2007
  • 2007-08-07 JP JP2007205947A patent/JP4570646B2/ja not_active Expired - Fee Related
  • 2007-08-31 AU AU2007214355A patent/AU2007214355B2/en not_active Ceased
• 2009
  • 2009-09-28 US US12/568,029 patent/US8644229B2/en not_active Expired - Lifetime
• 2010
  • 2010-03-10 AU AU2010200900A patent/AU2010200900B2/en not_active Expired
• 2014
  • 2014-01-14 US US14/154,830 patent/US9392490B2/en not_active Expired - Fee Related
  • 2014-10-23 NO NO20141262A patent/NO341774B1/no not_active IP Right Cessation
• 2016
  • 2016-07-11 US US15/207,084 patent/US9867208B2/en not_active Expired - Lifetime
• 2017
  • 2017-07-19 NO NO20171210A patent/NO20171210A1/no not_active Application Discontinuation

Patent Citations (4)

Also Published As

Similar Documents

Legal Events