throbber
(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2008/0254804 A1
`Lohr et al.
`(43) Pub. Date:
`Oct. 16, 2008
`
`US 20080254804A1
`
`(54) SCHEDULING OF MOBILE TERMINALS INA
`MOBILE COMMUNICATION SYSTEM
`
`75) Inventors:
`(75)
`
`Joachim Lohr, Langen (DE);
`Hitoshi Iochi, Ot E. began
`Petrovic, Langen (DE)
`
`Correspondence Address:
`DCKNSON WRIGHT PLLC
`1901 L STREET NW, SUITE 800
`WASHINGTON, DC 20036 (US)
`
`(73) Assignee:
`
`MATSHSHTAELECTRIC
`INDUSTRIAL CO.,LTD.,
`OSAKA (JP)
`
`(21) Appl. No.:
`
`11/909,981
`
`(22) PCT Filed:
`
`Feb. 7, 2006
`
`(86). PCT No.:
`
`PCT/EP2006/OO1060
`
`S371 (c)(1),
`(2), (4) Date:
`
`May 9, 2008
`
`Foreign Application Priority Data
`(30)
`Apr. 1, 2005 (EP) .................................. 05.007165.3
`O
`O
`Publication Classification
`
`(51) Int. Cl.
`(2006.01)
`H04O 7/20
`(52) U.S. Cl. ........................................................ 455/442
`(57)
`ABSTRACT
`The invention relates to a method for scheduling mobile ter
`minals within a mobile communication network and to a base
`station performing this method. Further, the invention relates
`to a method for acting upon the reception of scheduling grants
`in a mobile communication system and to a mobile terminal
`performing this method. To allow the serving cell to control
`resource utilization for uplink transmissions of UEs in soft
`handover, without thereby decreasing the system throughput
`of UEs in the serving cell which are not in soft-handover, the
`invention proposes to use control information transmitted via
`a shared absolute grant channel to the UEs along with an
`absolute grant, wherein the control information indicate
`whether the absolute grant is valid for mobile terminals in
`soft-handover only.
`
`
`
`
`
`from
`
`1202 or 1210
`
`1211
`
`DOWN"
`received from
`non-serving cel?
`
`yes
`
`
`
`MAX SG = PR - delta
`
`SG = MAXSG
`
`happy bit Setting
`decision
`
`-- power statuS
`-- buffer Occupancy
`-- PR, MAXSG
`
`1213
`
`124
`
`
`
`
`
`
`
`
`
`Select TF for current
`SG value
`
`
`
`1216
`
`
`
`
`
`transmit uplink data with
`selected TF and associated
`Control information
`(inter alia TFCl, happy bit)
`
`to
`
`1202
`
`
`Ex.1009 / Page 1 of 25Ex.1009 / Page 1 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`Patent Application Publication
`
`Oct. 16, 2008 Sheet 1 of 9
`
`US 2008/0254804 A1
`
`O2
`
`COre Network
`
`103
`
`Fig. 1
`
`
`
`101
`
`Core network
`
`
`Ex.1009 / Page 2 of 25Ex.1009 / Page 2 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`Patent Application Publication
`
`Oct. 16, 2008 Sheet 2 of 9
`
`US 2008/0254804 A1
`
`101
`
`Core network
`
`103
`
`RLC and higher layer entities
`
`
`
`
`
`physical layer
`
`Fig. 4
`
`
`Ex.1009 / Page 3 of 25Ex.1009 / Page 3 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`Patent Application Publication
`
`-
`
`-
`
`
`
`
`
`LEEFTIÐp?ET] ndd OTNH010 HO10] HOOG]0TH
`
`
`
`
`
`
`Ex.1009 / Page 4 of 25Ex.1009 / Page 4 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`Patent Application Publication
`
`Oct. 16, 2008 Sheet 4 of 9
`
`US 2008/0254804 A1
`
`from MAC-d
`
`- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
`i
`
`MAC Control
`
`E-TFC Selection
`
`P
`
`multiplexing &
`TSN setting
`
`
`
`------- al
`
`92
`9.
`S.---------
`v
`asSociated Scheduling
`downlink signalling
`(E-AGCH (ERGCH(s))
`
`- - - - - - - - - :
`
`associated ACK E-DCH associated uplink
`NACK signatting
`signalling E-TFC
`(E-HICH)
`(E-DPCCH)
`
`Fig. 6
`
`
`
`to MAC-es
`
`
`
`
`
`
`
`E-DCH
`Scheduling
`
`E-DCH
`Control
`
`
`
`MAC Control
`
`i
`
`associated uplink associated downlink
`signalling
`signalling
`(E-HICH, E-DPCCH) (E-AGCH, E-RGCH(s))
`
`Fig. 8
`
`
`Ex.1009 / Page 5 of 25Ex.1009 / Page 5 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`Patent Application Publication
`
`Oct. 16, 2008 Sheet 5 of 9
`
`US 2008/0254804 A1
`
`HOCI |-
`
`HOCH
`
`I "fil
`
`
`
`
`
`poo?io my HOSCIHOSCIHOSI) HOST, HOdp HOVY HOVI HOVH HOd
`
`
`
`
`
`
`
`
`
`| | | | | <!
`
`ºs–––––––––––––-----------*
`
`| | | r
`
`HOCI-FI}
`
`| †
`
`
`Ex.1009 / Page 6 of 25Ex.1009 / Page 6 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`Patent Application Publication
`
`Oct. 16, 2008 Sheet 6 of 9
`
`US 2008/0254804 A1
`
`to MAC-d
`
`to MAC-d
`
`to MAC-d
`
`disassembly
`
`disassembly
`
`disassembly
`
`MAC Control
`
`reordering
`Combining
`
`reordering
`Combining
`
`reordering
`combining
`
`----
`
`MAC-d flow#1 It
`
`KI. MAC-d flow in
`
`from MAC-e
`of Node B #1
`
`from MAC-e
`of Node Bik
`
`Fig. 9
`
`RG interpreted relative
`to the previous TT in the
`
`HARQ process (no. 1) - N
`
`E-DCH SN 2
`
`
`
`scheduling decision
`
`3
`
`4 NN 2
`
`3
`
`4
`
`time
`Fig. 10
`
`
`Ex.1009 / Page 7 of 25Ex.1009 / Page 7 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`Patent Application Publication
`
`Oct. 16, 2008 Sheet 7 of 9
`
`US 2008/0254804 A1
`

`
`ERC
`NS:
`%ion.
`Noir
`ERISOct.
`S. CN.
`".
`2:
`Es:
`N NS:
`2.
`ess
`HISOct.
`
`uffs
`
`92
`
`a has a
`
`92
`
`as
`
`s Ying
`
`s
`
`HEG
`SS
`as:
`If
`NS
`2.
`Esri:
`Illi
`SS:
`23.
`es:
`If
`SS
`
`
`
`
`
`t
`
`S3
`
`ca
`
`3.
`s
`S
`
`
`Ex.1009 / Page 8 of 25Ex.1009 / Page 8 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`Patent Application Publication
`
`Oct. 16, 2008 Sheet 8 of 9
`
`US 2008/0254804 A1
`
`(9%)
`
`
`
`
`
`
`Ex.1009 / Page 9 of 25Ex.1009 / Page 9 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`Patent Application Publication
`
`Oct. 16, 2008 Sheet 9 of 9
`
`US 2008/0254804 A1
`
`
`
`
`
`
`
`
`
`
`
`from Fig 12, 1202 or 1210
`
`1211
`
`DOWN"
`received from
`non-serving cel?
`
`yes
`
`
`
`MAXSG = PR-delta
`
`SG := MAXSG
`
`happy bit Setting
`decision
`
`-- power status
`-- buffer OCCupancy
`-- PR, MAXSG
`
`1213
`
`1214
`
`
`
`
`
`
`
`
`
`Select TF for Current
`SG value
`
`
`
`1216
`
`
`
`
`
`transmit uplink data with
`Selected TF and associated
`COntrol information
`(inter alia TFCl, happy bit)
`
`to Fig 12, 1202
`
`Fig. 13
`
`
`Ex.1009 / Page 10 of 25Ex.1009 / Page 10 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`US 2008/0254804 A1
`
`Oct. 16, 2008
`
`SCHEDULING OF MOBILE TERMINALS INA
`MOBILE COMMUNICATION SYSTEM
`
`FIELD OF THE INVENTION
`
`0001. The invention relates to a method for scheduling
`mobile terminals within a mobile communication network
`and to a base station performing this method. Further, the
`invention relates to a method for acting upon the reception of
`scheduling grants in a mobile communication system and to a
`mobile terminal performing this method.
`
`TECHNICAL BACKGROUND
`
`0002 W-CDMA (Wideband Code Division Multiple
`Access) is a radio interface for IMT-2000 (International
`Mobile Communication), which was standardized for use as
`the 3' generation wireless mobile telecommunication sys
`tem. It provides a variety of services such as Voice services
`and multimedia mobile communication services in a flexible
`and efficient way. The standardization bodies in Japan,
`Europe, USA, and other countries have jointly organized a
`project called the 3' Generation Partnership Project (3GPP)
`to produce common radio interface specifications for
`W-CDMA
`0003. The standardized European version of IMT-2000 is
`commonly called UMTS (Universal Mobile Telecommuni
`cation System). The first release of the specification of UMTS
`has been published in 1999 (Release 99). In the mean time
`several improvements to the standard have been standardized
`by the 3GPP in Release 4 and Release 5 and discussion on
`further improvements is ongoing under the scope of Release
`6
`0004. The dedicated channel (DCH) for downlink and
`uplink and the downlink shared channel (DSCH) have been
`defined in Release 99 and Release 4. In the following years,
`the developers recognized that for providing multimedia Ser
`vices—or data services in general high speed asymmetric
`access had to be implemented. In Release 5 the high-speed
`downlink packet access (HSDPA) was introduced. The new
`high-speed downlink shared channel (HS-DSCH) provides
`downlink high-speed access to the user from the UMTS
`Radio Access Network (RAN) to the communication termi
`nals, called user equipments in the UMTS specifications.
`
`Hybrid ARQ Schemes
`0005. A common technique for error detection and correc
`tion in packet transmission systems over unreliable channels
`is called hybrid Automatic Repeat request (HARQ). Hybrid
`ARQ is a combination of Forward Error Correction (FEC)
`and ARQ.
`0006 If a FEC encoded packet is transmitted and the
`receiver fails to decode the packet correctly (errors are com
`monly detected based on a CRC (Cyclic Redundancy
`Check)), the receiver requests a retransmission of the packet.
`Commonly the transmission of additional information is
`called “retransmission (of a packet), although this retrans
`mission does not necessarily mean a transmission of the same
`encoded information, but could also mean the transmission of
`any information belonging to the packet (e.g. additional
`redundancy information).
`0007 Depending on the information (generally code-bits/
`symbols), of which the transmission is composed of, and
`
`depending on how the receiver processes the information, the
`following hybrid ARQ schemes are defined:
`HARQ Type I
`0008 If the receiver fails to decode a packet correctly, the
`information of the encoded packet is discarded and a retrans
`mission is requested. This implies that all transmissions are
`decoded separately. Generally, retransmissions contain iden
`tical information (code-bits/symbols) to the initial transmis
`S1O.
`
`HARQ Type II
`0009. If the receiver fails to decode a packet correctly, a
`retransmission is requested, where the receiver Stores the
`information of the (erroneous received) encoded packet as
`soft information (soft-bits/symbols). This implies that a soft
`buffer is required at the receiver. Retransmissions can be
`composed out of identical, partly identical or non-identical
`information (code-bits/symbols) according to the same
`packet as earlier transmissions.
`0010 When receiving a retransmission the receiver com
`bines the stored information from the soft-buffer and the
`currently received information and tries to decode the packet
`based on the combined information. The receiver may also try
`to decode the transmission individually, however generally
`performance increases when combining transmissions.
`0011. The combining of transmissions refers to so-called
`soft-combining, where multiple received code-bits/symbols
`are likelihood combined and solely received code-bits/sym
`bols are code combined. Common methods for soft-combin
`ing are Maximum Ratio Combining (MRC) of received
`modulation symbols and log-likelihood-ratio (LLR) combin
`ing (LLR combing only works for code-bits).
`0012 Type II schemes are more sophisticated than Type I
`schemes, since the probability for correct reception of a
`packet increases with receive retransmissions. This increase
`comes at the cost of a required hybrid ARQ soft-buffer at the
`receiver. This scheme can be used to perform dynamic link
`adaptation by controlling the amount of information to be
`retransmitted.
`0013 E.g. if the receiver detects that decoding has been
`"almost successful, it can request only a small piece of
`information for the next retransmission (smaller number of
`code-bits/symbols than in previous transmission) to be trans
`mitted. In this case it might happen that it is even theoretically
`not possible to decode the packet correctly by only consider
`ing this retransmission by itself (non-self-decodable retrans
`missions).
`
`HARQ Type III
`0014. This is a subset of Type II with the restriction that
`each transmission must be self-decodable.
`
`Packet Scheduling
`Packet scheduling may be a radio resource manage
`00.15
`ment algorithm used for allocating transmission opportuni
`ties and transmission formats to the users admitted to a shared
`medium. Scheduling may be used in packet based mobile
`radio networks in combination with adaptive modulation and
`coding to maximize throughput/capacity by e.g. allocating
`transmission opportunities to the users in favorable channel
`conditions. The packet data service in UMTS may be appli
`cable for the interactive and background traffic classes,
`
`Ex.1009 / Page 11 of 25Ex.1009 / Page 11 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`US 2008/0254804 A1
`
`Oct. 16, 2008
`
`though it may also be used for streaming services. Traffic
`belonging to the interactive and background classes is treated
`as non real time (NRT) traffic and is controlled by the packet
`scheduler. The packet scheduling methodologies can be char
`acterized by:
`0016 Scheduling period/frequency: The period over
`which users are scheduled ahead in time.
`0017 Serve order: The order in which users are served,
`e.g. random order (round robin) or according to channel
`quality (C/I or throughput based).
`0018 Allocation method: The criterion for allocating
`resources, e.g. same data amount or same power/code/
`time resources for all queued users per allocation inter
`val.
`0019. The packet scheduler for uplink is distributed
`between Radio Network Controller (RNC) and user equip
`ment in 3GPP UMTS R99/R4/R5. On the uplink, the air
`interface resource to be shared by different users is the total
`received power at a Node B, and consequently the task of the
`scheduler is to allocate the power among the user equipment
`(s). In current UMTS R99/R4/R5 specifications the RNC
`controls the maximum rate/power a user equipment is
`allowed to transmit during uplink transmission by allocating
`a set of different transport formats (modulation scheme, code
`rate, etc.) to each user equipment.
`0020. The establishment and reconfiguration of such a
`TFCS (transport format combination set) may be accom
`plished using Radio Resource Control (RRC) messaging
`between RNC and user equipment. The user equipment is
`allowed to autonomously choose among the allocated trans
`port format combinations based on its own status e.g. avail
`able power and buffer status. In current UMTS R99/R4/R5
`specifications there is no control on time imposed on the
`uplink user equipment transmissions. The scheduler may e.g.
`operate on transmission time interval basis. UMTS Architec
`ture
`0021. The high level R99/4/5 architecture of Universal
`Mobile Telecommunication System (UMTS) is shown in
`FIG. 1 (see 3GPP TR 25.401: “UTRAN Overall Descrip
`tion', available from http://www.3gpp.org). The networkele
`ments are functionally grouped into the Core Network (CN)
`101, the UMTS Terrestrial Radio Access Network (UTRAN)
`102 and the User Equipment (UE) 103. The UTRAN 102 is
`responsible for handling all radio-related functionality, while
`the CN 101 is responsible for routing calls and data connec
`tions to external networks. The interconnections of these
`network elements are defined by open interfaces (Iu, Uu). It
`should be noted that UMTS system is modular and it is
`therefore possible to have several network elements of the
`same type.
`0022. In the sequel two different architectures will be dis
`cussed. They are defined with respect to logical distribution of
`functions across network elements. In actual network deploy
`ment, each architecture may have different physical realiza
`tions meaning that two or more network elements may be
`combined into a single physical node.
`0023 FIG. 2 illustrates the current architecture of
`UTRAN. A number of Radio Network Controllers (RNCs)
`201, 202 are connected to the CN 101. Each RNC 201, 202
`controls one or several base stations (Node Bs) 203, 204, 205,
`206, which in turn communicate with the user equipments.
`An RNC controlling several base stations is called Control
`ling RNC (C-RNC) for these base stations. A set of controlled
`base stations accompanied by their C-RNC is referred to as
`
`Radio Network Subsystem (RNS) 207, 208. For each con
`nection between User Equipment and the UTRAN, one RNS
`is the Serving RNS (S-RNS). It maintains the so-called Iu
`connection with the Core Network (CN) 101. When required,
`the Drift RNS 302 (D-RNS) 302 supports the Serving RNS
`(S-RNS) 301 by providing radio resources as shown in FIG.
`3. Respective RNCs are called Serving RNC (S-RNC) and
`Drift RNC (D-RNC). It is also possible and often the case that
`C-RNC and D-RNC are identical and therefore abbreviations
`S-RNC or RNC are used.
`
`Mobility Management Within Rel99/415 UTRAN
`0024. Before explaining some procedures connected to
`mobility management, some terms frequently used in the
`following are defined first.
`0025 A radio link may be defined as a logical association
`between single UE and a single UTRAN access point. Its
`physical realization comprises radio bearer transmissions.
`0026. A handover may be understood as a transfer of a UE
`connection from one radio bearer to another (hard handover)
`with a temporary break in connection or inclusion/exclusion
`of a radio bearer to/from UE connection so that UE is con
`stantly connected UTRAN (soft handover). Soft handover is
`specific for networks employing Code Division Multiple
`Access (CDMA) technology. Handover execution may con
`trolled by S-RNC in the mobile radio network when taking
`the present UTRAN architecture as an example.
`0027. The active set associated to a UE comprises a set of
`radio links simultaneously involved in a specific communi
`cation service between UE and radio network. An active set
`update procedure may be employed to modify the active set of
`the communication between UE and UTRAN, for example
`during soft-handover. The procedure may comprise three
`functions: radio link addition, radio link removal and com
`bined radio link addition and removal. The maximum number
`of simultaneous radio links is set to eight. New radio links are
`added to the active set once the pilot signal strengths of
`respective base stations exceed certain threshold relative to
`the pilot signal of the strongest member within active set.
`0028. A radio link is removed from the active set once the
`pilot signal strength of the respective base station exceeds
`certain threshold relative to the strongest member of the
`active set. Threshold for radio link addition is typically cho
`sen to be higher than that for the radio link deletion. Hence,
`addition and removal events form a hysteresis with respect to
`pilot signal strengths.
`0029 Pilot signal measurements may be reported to the
`network (e.g. to S-RNC) from UE by means of RRC signal
`ing. Before sending measurement results, some filtering is
`usually performed to average out the fast fading. Typical
`filtering duration may be about 200 ms contributing to han
`dover delay. Based on measurement results, the network (e.g.
`S-RNC) may decide to trigger the execution of one of the
`functions of active set update procedure (addition/removal of
`a Node B to/from current Active Set).
`
`Enhanced Uplink Dedicated Channel (E-DCH)
`0030 Uplink enhancements for Dedicated Transport
`Channels (DTCH) are currently studied by the 3GPP Tech
`nical Specification Group RAN (see 3GPP TR 25.896: “Fea
`sibility Study for Enhanced Uplink for UTRA FDD (Release
`6)', available at http://www.3gpp.org). Since the use of IP
`based services become more important, there is an increasing
`
`Ex.1009 / Page 12 of 25Ex.1009 / Page 12 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`US 2008/0254804 A1
`
`Oct. 16, 2008
`
`demand to improve the coverage and throughput of the RAN
`as well as to reduce the delay of the uplink dedicated transport
`channels. Streaming, interactive and background services
`could benefit from this enhanced uplink.
`0031 One enhancement is the usage of adaptive modula
`tion and coding schemes (AMC) in connection with Node B
`controlled scheduling, thus an enhancement of the Uu inter
`face. In the existing R99/R4/R5 system the uplink maximum
`data rate control resides in the RNC. By relocating the sched
`uler in the Node B the latency introduced due to signaling on
`the interface between RNC and Node B may be reduced and
`thus the scheduler may be able to respond faster to temporal
`changes in the uplink load. This may reduce the overall
`latency in communications of the user equipment with the
`RAN. Therefore Node B controlled scheduling is capable of
`better controlling the uplink interference and Smoothing the
`noise rise variance by allocating higher data rates quickly
`when the uplink load decreases and respectively by restricting
`the uplink data rates when the uplink load increases. The
`coverage and cell throughput may be improved by a better
`control of the uplink interference.
`0032. Another technique, which may be considered to
`reduce the delay on the uplink, is introducing a shorter TTI
`(Transmission Time Interval) length for the E-DCH com
`pared to other transport channels. A transmission time inter
`Val length of 2 mS is currently investigated for use on the
`E-DCH, while a transmission time interval of 10 ms is com
`monly used on the other channels. Hybrid ARQ, which was
`one of the key technologies in HSDPA, is also considered for
`the enhanced uplink dedicated channel. The Hybrid ARQ
`protocol between a Node B and a user equipment allows for
`rapid retransmissions of erroneously received data units, and
`may thus reduce the number of RLC (Radio Link Control)
`retransmissions and the associated delays. This may improve
`the quality of service experienced by the end user.
`0033. To support enhancements described above, a new
`MAC sub-layer is introduced which will be called MAC-e in
`the following (see 3GPP TSG RAN WG1, meeting #31, Taoc
`R01-030284, “Scheduled and Autonomous Mode Operation
`for the Enhanced Uplink”). The entities of this new sub-layer,
`which will be described in more detail in the following sec
`tions, may be located in user equipment and Node B. On user
`equipment side, the MAC-e performs the new task of multi
`plexing upper layer data (e.g. MAC-d) data into the new
`enhanced transport channels and operating HARQ protocol
`transmitting entities.
`0034) Further, the MAC-e sub-layer may be terminated in
`the S-RNC during handover at the UTRAN side. Thus, the
`reordering buffer for the reordering functionality provided
`may also reside in the S-RNC.
`
`E-DCH MAC Architecture UE Side
`0035 FIG. 4 shows the exemplary overall E-DCH MAC
`architecture on UE side. A new MAC functional entity, the
`MAC-eles, is added to the MAC architecture of Release 99.
`0036. The MAC interworking on the UE side is illustrated
`in FIG. 5. There are M different data flows (MAC-d) carrying
`data packets from different applications to be transmitted
`from UE to Node B. These data flows can have different QoS
`requirements (e.g. delay and error requirements) and may
`require different configuration of HARQ instances. Each
`MAC-d flow represents a logical unit to which specific physi
`cal channel (e.g. gain factor) and HARO (e.g. maximum
`number of retransmissions) attributes can be assigned.
`
`0037. Further, MAC-d multiplexing is supported for an
`E-DCH, i.e. several logical channels with different priorities
`may be multiplexed onto the same MAC-d flow. Data of
`multiple MAC-d flows can be multiplexed in one MAC-e
`PDU. In the MAC-e header, the DDI (Data Description Indi
`cator) field identifies logical channel, MAC-d flow and
`MAC-d PDU size. A mapping table is signaled over RRC, to
`allow the UE to set DDI values. The N field indicates the
`number of consecutive MAC-d PDUs corresponding to the
`same DDI value.
`0038. The MAC-eles entity is depicted in more detail in
`FIG. 6. The MAC-es?e handles the E-DCH specific functions.
`The selection of an appropriate transport format for the trans
`mission of data on E-DCH is done in the E-TFC Selection
`entity, which represents a function entity. The transport for
`mat selection is done according to the scheduling information
`(Relative Grants and Absolute Grants) received from
`UTRAN via L1, the available transmit power, priorities, e.g.
`logical channel priorities. The HARQ entity handles the
`retransmission functionality for the user. One HARQ entity
`supports multiple HARQ processes. The HARQ entity
`handles all HARQ related functionalities required. The mul
`tiplexing entity is responsible for concatenating multiple
`MAC-d PDUs into MAC-es PDUs, and to multiplex one or
`multiple MAC-es PDUs into a single MAC-e PDU, to be
`transmitted at the next TTI, and as instructed by the E-TFC
`selection function. It is also responsible for managing and
`setting the TSN per logical channel for each MAC-es PDU.
`The MAC-eles entity receives scheduling information from
`Node B (network side) via Layer 1 signaling as shown in FIG.
`6. Absolute grants are received on E-AGCH (Enhanced Abso
`lute Grant Channel), relative grants are received on the
`E-RGCH (Enhanced Relative Grant Channel).
`
`E-DCH MAC Architecture UTRAN Side
`
`0039. An exemplary overall UTRAN MAC architecture is
`shown in FIG. 7. The UTRAN MAC architecture includes a
`MAC-e entity and a MAC-es entity. For each UE that uses an
`E-DCH, one MAC-e entity per Node-B and one MAC-es
`entity in the S-RNC are configured.
`0040. The MAC-e entity is located in the Node B and
`controls access to the E-DCH. Further, the MAC-e entity is
`connected to MAC-es located in the S-RNC.
`0041. In FIG. 8 the MAC-e entity in Node B is depicted in
`more detail. There is one MAC-e entity in Node B for each UE
`and one E-DCH scheduler function in the Node-B for all UEs.
`The MAC-e entity and E-DCH scheduler handle HSUPA
`(High-Speed Uplink Packet Access) specific functions in
`Node B. The E-DCH scheduling entity manages E-DCH cell
`resources between UES. Commonly, scheduling assignments
`are determined and transmitted based on Scheduling requests
`from the UEs. The De-multiplexing entity in the MAC-e
`entity provides de-multiplexing of MAC-e PDUs. MAC-es
`PDUs are then forwarded to the MAC-esentity in the S-RNC.
`0042. One HARQ entity is capable of supporting multiple
`instances (HARO processes), e.g. employing a stop and wait
`HARO protocols. Each HARQ process is assigned a certain
`amount of the soft buffer memory for combining the bits of
`the packets from outstanding retransmissions. Furthermore
`each process is responsible for generating ACKs or NACKs
`indicating delivery status of E-DCH transmissions. The
`HARO entity handles all tasks that are required for the HARQ
`protocol.
`
`
`Ex.1009 / Page 13 of 25Ex.1009 / Page 13 of 25
`
`TESLA, INC.TESLA, INC.
`
`

`

`US 2008/0254804 A1
`
`Oct. 16, 2008
`
`0043. In FIG.9 the MAC-es entity in the S-RNC is shown.
`It comprises the reordering buffer which provides in-se
`quence delivery to RLC and handles the combining of data
`from different Node Bs in case of soft handover. The com
`bining is referred to as Macro diversity selection combining.
`0044. It should be noted that the required soft buffer size
`depends on the used HARQ scheme, e.g. an HARQ scheme
`using incremental redundancy (IR) requires more soft buffer
`than one with chase combining (CC).
`
`E-DCH-Node B Controlled Scheduling
`0045 Node B controlled scheduling is one of the technical
`features for E-DCH which may enable more efficient use of
`the uplink resources in order to provide a higher cell through
`put in the uplink and may increase the coverage. The term
`“Node B controlled scheduling denotes the possibility for a
`Node B to control uplink resources, e.g. the E-DPDCH/
`DPCCH power ratio, which the UE may use for uplink trans
`missions on the E-DCH within limits set by the S-RNC. Node
`B controlled scheduling is based on uplink and downlink
`control signaling together with a set of rules on how the UE
`should behave with respect to this signaling.
`0046. In the downlink, a resource indication (scheduling
`grant) is required to indicate to the UE the (maximum)
`amount of uplink resources it may use. When issuing sched
`uling grants, the Node B may use QoS-related information
`provided by the S-RNC and from the UE in the scheduling
`requests to determine the appropriate allocation of resources
`for servicing the UE at the requested QoS parameters.
`0047. For the UMTS E-DCH, there are commonly two
`different UE scheduling modes defined depending on the type
`of scheduling grants used. In the following the characteristics
`of the scheduling grants are described.
`
`Scheduling Grants
`0048 Scheduling grants are signaled in the downlink in
`order to indicate the (maximum) resource the UE may use for
`uplink transmissions. The grants affect the selection of a
`suitable transport format (TF) for the transmission on the
`E-DCH (E-TFC selection). However, they usually do not
`influence the TFC selection (Transport Format Combination)
`for legacy dedicated channels.
`0049. There are commonly two types of scheduling grants
`which are used for the Node B controlled scheduling:
`0050 absolute grants (AGs), and
`0051
`relative grants (RGs)
`0052. The absolute grants provide an absolute limitation
`of the maximum amount of uplink resources the UE is
`allowed to use for uplink transmissions. Absolute grants are
`especially Suitable to rapidly change the allocated UL
`SOUCS.
`0053 Relative grants are transmitted every TTI (Trans
`mission Time Interval). They may be used to adapt the allo
`cated uplink resources indicated by absolute grants by granu
`lar adjustments: A relative grant indicates the UE to increase
`or decrease the previously allowed maximum uplink
`resources by a certain offset (step).
`0054 Absolute grants are only signaled from the E-DCH
`serving cell. Relative grants can be signaled from the serving
`cell as well as from a non-serving cell. The E-DCH serving
`cell denotes the entity (e.g. Node B) actively allocating uplink
`resources to UEs controlled by this serving cell, whereas a
`
`non-serving cell can only limit the allocated uplink resources,
`set by the serving cell. Each UE has only one serving cell.
`0055 Absolute grants may be valid for a single UE. An
`absolute grant valid for a single UE is referred to in the
`following as a "dedicated grant. Alternatively, an absolute
`grant may also be valid for a group of or all UEs within a cell.
`An absolute grant valid for a group of or all UEs will be
`referred to as a “common grant' in the following. The UE
`does not distinguish between common and dedicated grants.
`0056 Relative grants can be sent from serving cell as well
`as from a non-serving cell as already mentioned before. A
`relative grant signaled from the serving cell may indicate one
`of the three values, “UP”, “HOLD and “DOWN’. “UP”
`respectively "DOWN’ indicates the increase/decrease of the
`previously maximum used uplink resources (maximum
`power ratio) by one step. Relative grants from a non-serving
`cell can either signala"HOLD" or “DOWN’ command to the
`UE. As mentioned before relative grants from non-serving
`cells can only limit the uplink resources set by the serving cell
`(overload indicator) but can not increase the resources that
`can be used by a UE.
`UE Scheduling Operation
`0057 Two different UE scheduling mode operations are
`defined for E-DCH, “RG' based and “non-RG' based mode
`of operation.
`0058. In the RG based mode, the UE obeys relative grants
`from the E-DCH serving cell. The RG based scheduling mode
`is also often referred to as the dedicated rate control mode,
`because the scheduling grants usually address a single UE in
`the most cases.
`0059. In the following the UE behavior in this RG based
`scheduling mode is described. The UE maintains a serving
`grant (SG) for each HARQ process. The serving grant indi
`cates the maximum power ratio (E-DPDCH/DPCCH) the UE
`is allowed to use for transmissions on the E-DCH and is for
`the selection of an appropriate TFC during E-TFC selection.
`The serving grant is updated by the scheduling grants sig
`naled from serving/non-serving cells. When the UE receives
`an absolute grant from the serving cell the serving grant is set
`to the power ratio signaled in the absolute grant. The absolute
`grant can be valid for each HARQ process or only for one
`HARO process.
`0060. When no absolute grant is received from the serving
`cell the UE should follow the relative grants from the serving
`cell, which are signaled every TTI. A serving relative grant is
`interpreted relative to the UE power ratio in the previous TTI
`for the same hybrid ARQ process as the transmission, which
`the relative grant will affect. FIG. 10 illustrates the timing
`relation for relative grants. In FIG. 10 it is assumed for exem
`plary purposes that there are four HARQ processes. The
`relative grant received by the UE, which affects the serving
`grant of the first HARQ process, is relative to the first HARQ
`process of the previous TTI (reference process).
`0061 The UE behavior in accordance to serving E-DCH
`relative grants is shown in the following:
`0062. When the UE receives an “UP command from
`Serving E-DCH Radio Link Set (RLS):
`0063 New SG, Last used power ratio (i)+Delta;
`0064. When the UE receives a “DOWN’ command
`from Serving E-DCH RLS:
`0065 New SG, Last used power ratio (i)-Delta;
`0066. The “UP and “DOWN’ command is relative to the
`power ratio used

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket