EP2599357A1 - Procédé et dispositif de traitement de données dans un réseau de communication - Google Patents

Procédé et dispositif de traitement de données dans un réseau de communication

Info

Publication number
EP2599357A1
EP2599357A1 EP10734754.4A EP10734754A EP2599357A1 EP 2599357 A1 EP2599357 A1 EP 2599357A1 EP 10734754 A EP10734754 A EP 10734754A EP 2599357 A1 EP2599357 A1 EP 2599357A1
Authority
EP
European Patent Office
Prior art keywords
terminal
mode
drx
scheduling
sleep mode
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.)
Withdrawn
Application number
EP10734754.4A
Other languages
German (de)
English (en)
Inventor
Mohmmad Anas
Ralf Golderer
Uwe Herrmann
Hans Kroener
Wolfgang Payer
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.)
Nokia Solutions and Networks Oy
Original Assignee
Nokia Siemens Networks Oy
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 Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Publication of EP2599357A1 publication Critical patent/EP2599357A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • 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
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]

Definitions

  • the invention relates to a method and to a device for data processing in a communication network. Also, a communication system is suggested comprising at least one such device.
  • a radio network typically comprises a base station (BS, also called base transceiver station, NodeB, eNodeB or eNB) , a mobile device (also referred to as user equipment (UE) , mobile station or mobile terminal) and optional network elements that provide interconnections with a core network.
  • the BS connects the UE via a so-called radio interface (also re ⁇ ferred to as air-interface) .
  • DRX discontinuous Reception
  • the DRX functionality can be summarized as follows (see also 3GPP TS 36.321, section 5.7):
  • the timeline is divided into DRX cycles, each com ⁇ prising the same number of subframes (according to 3GPP TS 36.211, a subframe is 1/10 of a radio frame and the length of a subframe amounts to 1ms) , wherein one DRX cycle follows the next.
  • the start of a DRX cycle is linked to a system frame number (SFN) and a UE-specific offset.
  • SFN system frame number
  • UE-specific offset There are certain periods of time within a DRX cycle when the UE is in a "DRX Active" mode.
  • the UE If the UE is in the "DRX Active" mode, it monitors the PDCCH for UL and DL grants (UL grant and DL grant correspond to indications sent on the PDCCH in order to grant a DL or a UL transmission) . Hence, the UE can receive DL transmissions and can convey UL transmissions.
  • the UE When the UE is in a "DRX Sleep” mode (i.e. in case it is not in the "DRX Active” mode) , the UE does not monitor the PDCCH for UL and DL grants. Hence, the UE is not able to receive DL transmissions on a PDSCH for dedicated transport channels and will not perform UL transmissions on a PUSCH. Being in "DRX Sleep” mode, the UE ' s receiver that handles the reception on the PDCCH and a physical downlink shared channel
  • PDSCH PDSCH
  • DRX cycles can have the following lengths: 10ms, 20ms, 32ms, 40ms, 64ms, 80ms, 128ms, 160ms, 256ms, 320ms, 512ms, 640ms, 1024ms, 1280ms, 2048ms or 2560ms.
  • a "DRX OnDuration" timer and a “DRX Inactivity” timer are defined by 3GPP as follows:
  • One such timer is provided per UE .
  • the timer is started with the first subframe of a DRX cycle .
  • the UE is in the "DRX Active" mode.
  • One such timer is provided per UE .
  • the timer is started or restarted if the PDCCH indi ⁇ cates a new UL or DL transmission and if the UE is in "DRX Active" mode at that time. If the timer is running, the UE is in the "DRX .
  • Fig.l shows a schematic diagram visualizing the functionality of a DRX OnDuration timer and a DRX Inactivity timer in a radio network between an eNB 103 and a UE 104.
  • the DRX OnDuration timer 102 is started.
  • the UE 104 is in "DRX Active" mode for the first subframes of the DRX cycle 101 and can re ⁇ ceive DL and UL grants from the eNB 103.
  • a DL grant is sent on the PDCCH from the eNB 103 to the UE 104 and the DRX Inactivity timer is started (indicated by an arrow 107) thereby extending the duration of the "DRX Active" mode.
  • another DL grant is sent to the UE 104 and the DRX Inactivity timer is re-started (indicated by an arrow 108), which extends the "DRX Active" mode for this UE 104.
  • Restarting of the DRX Inactivity timer results in the DRX Inactivity timer window being moved (extended) with every grant indicating a new transmission in UL or DL . This only occurs in case the UE 104 is the "DRX Active" mode; otherwise, the
  • the UE 104 cannot receive such grant from the eNB 103. If the eNB 103 continuously provides such grants to the UE 103, the DRX Inactivity timer window is moved beyond the end of the DRX cycle 101, into the next DRX cycle 101. In such exemplary scenario, the UE 103 does not enter the "DRX Sleep" mode dur ⁇ ing such DRX cycle 101.
  • the DRX Inactivity timer expires and the UE 104 stops being in the "DRX Active” mode, hence it enters the "DRX Sleep” mode and is no longer able to listen on the PDCCH.
  • the UE 104 is not able to receive and process any further DL grants from the eNB 103 until it awakes again, e.g., at the beginning of the next DRX cycle when the DRX On- Duration timer will be re-started or - as an alternative - when the UE 104 sends out a "Scheduling Request" at any time within the DRX cycle in order to indicate towards the eNB 103 that data in the UE ' s buffer requires UL transmission.
  • Fig.2 shows a schematic diagram visualizing the functionality of a "Scheduling Request" 201 issued at a time tl within a DRX cycle 204 by a UE 203 towards an eNB 202.
  • the UE 203 During the DRX cycle 204 the UE 203 enters the "DRX Sleep" mode. Hence, within this DRX cycle 204 the UE 203 will not receive any information from the eNB 202 unless the UE 203 itself initiates communication with the eNB 202 via the
  • the "Scheduling Request" 201 can be sent at any time during the DRX cycle 204 when corresponding resources on PUCCH are assigned to the UE . These resources are assigned at a given periodicity (amounting to, e.g., 40ms) for one subframe.
  • the UE 203 sends the "Scheduling Request" 201 when there is UL data to be conveyed to the eNB 202. Sending the "Scheduling Request" 201, the UE 203 becomes active. Pursuant to the "Scheduling Request" 201, the UE 203 remains in the "DRX Ac- tive" mode until the eNB 202 conveys an UL grant and the UE 203 starts the DRX Inactivity timer 205.
  • the eNB 202 starts the DRX Inactivity timer 205 and conveys an UL grant on the PDCCH to the UE 203.
  • the UE 203 remains in the "DRX Active" mode due to the pending
  • the UE 203 transmits the UL data on the PUSCH towards the eNB.
  • the UE 203 remains in the "DRX Active" mode.
  • Fig.3 shows a timing diagram visualizing this problem.
  • the eNB may have first DL data to be conveyed to a first UE 301 and second DL data to be conveyed to a second UE 302.
  • the first UE 301 is near entering its "DRX Sleep” mode and the second UE 302 is still for some more time in its "DRX Active" mode.
  • the eNB decides to first convey the second data to the second UE 302 it will not be able to convey the first data to the first UE 301 within the same DRX cycle, because at a time 304 the first UE 301 will have entered "DRX Sleep” mode and cannot be reached by the eNB within this DRX cycle. This leads to a considerable delay 305 of data transmission to ⁇ wards the first UE 301.
  • This kind of uncontrolled scheduling with respect to the du ⁇ ration of "DRX Active" modes may lead to poor delay perform ⁇ ance of a UE, which enters the "DRX Sleep” mode, e.g., in a subsequent subframe.
  • the problem to be solved is to overcome the disadvantages mentioned above and in particular to provide an efficient so ⁇ lution utilizing the DRX functionality. This problem is solved according to the features of the inde ⁇ pendent claims. Further embodiments result from the depending claims .
  • a terminal is assigned a scheduling priority based on a time period until the terminal enters a sleep mode.
  • the approach described allows assigning a scheduling priority based on a time period unit the mobile or fixed terminal en- ters the sleep mode. This corresponds to the fact that the terminal has to be scheduled during its active mode. It is noted that the active mode may be a portion of an energy- saving (e.g., DRX) cycle during which the terminal could be reached by the network component, in particular the base sta- tion.
  • DRX energy- saving
  • a terminal in particular a UE may run several services in parallel.
  • providing a schedul ⁇ ing priority could be service-specific, i.e., it may be ap- plicable for a subset of services.
  • a differentiation in handling required is achieved by providing a mapping to separate bear ⁇ ers; hence, a bearer may correspond to a basic means for an eNB to utilize service differentiation. Therefore, the pri ⁇ oritization mechanism suggested could be applied for at least one bearer, in particular a subset of bearers, i.e., based on an availability of data of a certain bearer to be transmitted to/from the UE .
  • the terminal is a mobile terminal or a fixed terminal .
  • the mobile terminal may be any mobile device or mobile sta ⁇ tion with an interface to a wireless network, in particular to a mobile telecommunication network.
  • the communica ⁇ tion network may be a telecommunication network comprising a radio portion (e.g., a radio access network) and a wireline portion.
  • the duration of the "DRX Active" mode and/or the "DRX sleep” mode may be correlated over both parts of the networks and the prioritization may be aligned with regard to the end-to-end connections.
  • the terminal can be a terminal of a fixed network.
  • the terminal provides an energy-saving functionality .
  • the energy-saving functionality may comprise said sleep mode and the active mode of the terminal.
  • the energy-saving functionality com- prises a discontinuous reception functionality comprising in particular a "DRX Active” mode and a "DRX Sleep” mode.
  • the time until the terminal enters the "DRX Sleep” mode (or the time the terminal stays in the "DRX Active” mode) can be considered when assigning a scheduling priority.
  • the terminal may use a discontinuous trans ⁇ mission functionality to save energy.
  • the power amplifier or parts of the transmission chain could be powered down during the time when the system is in the "DRX Sleep” mode. Then, no uplink data may await transmission from the UE.
  • scheduling priority is assigned by a component of the communication network, in particular by a base station of a radio access network.
  • the base station e.g. eNB
  • the prioritization allows utilizing the active modes of the mo ⁇ bile terminal such that data is transmitted to the mobile terminals before a timer at the mobile terminal expires and the mobile terminal enters its sleep mode.
  • the sleep mode may in particular last a predetermined period of time (e.g., a DRX cycle) then the mobile terminal may re ⁇ enter its active mode.
  • the mobile terminal may actively get re-activated during its sleep mode in case it needs to convey data to the base station (a scheduling request is sent to the base station by the mobile terminal and the mobile terminal is thus again in its active mode) .
  • the base station for the rest of a DRX cycle to re-activate the mobile terminal after it has entered the sleep mode.
  • the terminal is assigned a scheduling priority, said priority is increased with the de ⁇ creasing time left until the terminal enters the sleep mode.
  • the priority may depend on or it may change with the remaining active time.
  • the scheduling priority com ⁇ prises a weighting factor that is based on a time left until the terminal enters the sleep mode.
  • the scheduling priority may be based on a type of the terminal, a service being used (utilizing, e.g., a service-specific weight) , a remaining delay target, a re- source utilization (time, frequency, power, codes, etc.) and any combination thereof.
  • weighting factor depending on a remain- ing active time can be applied to any combination of criteria for prioritization purposes.
  • several weighting factors may be provided depending on several criteria, in particular at least on one prioritization scheduling criterion .
  • the scheduling priority is based on at least one class or type of terminal and/or service.
  • delay-sensitive traffic can be scheduled using a higher weighting factor (and thus resulting in a higher likelihood of traffic being conveyed) compared to best effort traffic.
  • delay-sensitive terminals e.g., mobile terminals conveying VoIP
  • prob ⁇ ability in particular in case these terminals approach the end of their active modes.
  • scheduling among several terminals is prioritized based on the time the terminals en ⁇ ter the sleep mode.
  • the scheduling (e.g., by a base station) can be conducted pursu ⁇ ant to the time left for each mobile terminal (e.g., UE) in its respective "DRX Active" mode.
  • a weighting factor can be utilized dependent on the remaining time in "DRX Active” mode .
  • scheduling among several terminals is prioritized based on quality of service information and/or channel quality information.
  • the scheduling may in particular consider (in addition to the time left in active mode for each terminal) further criteria, e.g., a QoS (e.g., based on a service level agree ⁇ ment) and/or a (e.g., measured) channel quality.
  • a QoS e.g., based on a service level agree ⁇ ment
  • a channel quality may be consid ⁇ ered such that a poor channel may trigger an increase or a decrease of the prioritization for a particular terminal.
  • Timers related to DRX can be defined in the specification for the UE side, i.e., the UE may (re-) start a DRX OnDuration timer or a DRX Inactivity timer based on certain trigger conditions (e.g., the DRX Inactivity timer is (re-) started as soon as the UE has been scheduled) .
  • the eNB may thus predict or track the status of the UE ' s DRX mode based on the same configuration information (i.e., timer settings, etc.) and monitor trigger events for (re-) starting timers (e.g., scheduling of the UE, reception of a scheduling request, etc.) .
  • the terminal conveys a timing information regarding its sleep mode and/or an active mode to the network component assigning the scheduling priority.
  • the timing information regarding sleep and/or active mode can be conveyed from the (mobile) terminal to the net- work component, e.g., the base station (eNB) .
  • the terminal thus informs the network component about its intention to en ⁇ ter the sleep mode and/or about the time when it is going or intends to enter the sleep mode.
  • the terminal conveys a request to enter sleep mode to the network component assigning the scheduling priority.
  • the (mobile) terminal may ask the network component whether or not it is acceptable to enter its sleep mode.
  • the network component may indicate to the mobile terminal that it shall not yet enter the sleep mode, because additional data is to be conveyed from the network component to the terminal.
  • the terminal may obtain a confirmation from the network component to enter the sleep mode.
  • a timer could be used by the terminal in order to wait for a response from the network component for a predefined period of time; if no such response has been provided when the timer expires, the terminal enters the sleep mode.
  • the UE may determine the "DRX Active” mode and the "DRX Sleep” mode based on configuration information (e.g., timer settings, etc) and/or trigger conditions, and the eNB may predict the UE ' s "DRX Active” mode and/or the UE ' s "DRX Sleep” mode based on the same (type of) informa ⁇ tion .
  • configuration information e.g., timer settings, etc
  • the eNB may predict the UE ' s "DRX Active” mode and/or the UE ' s "DRX Sleep” mode based on the same (type of) informa ⁇ tion .
  • processing unit can comprise at least one, in particular several means that are arranged to execute the steps of the method described herein.
  • the means may be logically or physically separated; in particular sev ⁇ eral logically separate means could be combined in at least one physical unit.
  • Said processing unit may comprise at least one of the follow ⁇ ing: a processor, a microcontroller, a hard-wired circuit, an ASIC, an FPGA, a logic device.
  • the device could be a component of the com ⁇ munication network, in particular a base station of a radio access network.
  • the solution provided herein further comprises a computer program product directly loadable into a memory of a digital computer, comprising software code portions for performing the steps of the method as described herein.
  • a com ⁇ puter-readable medium e.g., storage of any kind, having com ⁇ puter-executable instructions adapted to cause a computer system to perform the method as described herein.
  • a communi ⁇ cation system comprising at least one device as described herein .
  • Fig.4 shows an exemplary diagram visualizing possible
  • Fig.5 shows a network component, e.g., a base station, a gateway, a router, a switch, etc. that is connected to a network and the network component is connected to two terminals, wherein the terminals are scheduled by the network component.
  • a network component e.g., a base station, a gateway, a router, a switch, etc. that is connected to a network and the network component is connected to two terminals, wherein the terminals are scheduled by the network component.
  • a criterion e.g., pursuant to a normal schedule
  • (2) UEs that are close to an end of their "DRX Active" mode (e.g., time remaining in "DRX Active" for the UE is be ⁇ low a given threshold value) can be scheduled, e.g., with an increased priority.
  • the priority can be increased with the decreasing time left in the
  • a prioritization of UEs can be provided pursuant to their individual time left in the "DRX Active” mode.
  • a weighting factor can be utilized dependent on the remaining time in "DRX Active” mode; such weighting factor takes into account the distance to the end of the current "DRX Active” mode phase. The closer the end of the "DRX Active” mode, the higher the weighting factor may be set so that the respective UE is scheduled by a base station (eNB) with a higher prob ⁇ ability at the end of its current "DRX Active” mode.
  • eNB base station
  • the criterion for scheduling of UEs may in particular depend on QoS information and/or channel quality.
  • a criterion C ⁇ (t) for prioritization of a UE i for scheduling with respect to an upcoming subframe t can be set as follows:
  • Ci(t) f ( QoS, channel quality (t) , 7)
  • the criterion C ⁇ (t) can be a function dependent on the QoS, the channel quality over time t, etc.
  • This new criterion CI, DRX Activity (t) can be used for prioritizing the scheduling of UEs.
  • Fig.4 shows an exemplary diagram as how the weighting factor w(t_disti) can be realized as a function of the remaining time until an end of the "DRX Active" mode is reached.
  • the weighting factor w is set to "9" (high weighting factor) .
  • the probability of scheduling this UE i is high as otherwise the UE may enter the "DRX Sleep” mode and cannot be reached from the base station within the very same DRX cycle.
  • the weighting factor w is set to "7" and if the time t_dist ⁇ amounts to "3", the weighting factor w is set to "5". If the time t_dist ⁇ amounts to "4", the weighting factor w is set to "3” and for a time t_dist ⁇ amounting to at least "5", the weight ⁇ ing factor w is set to "1". This indicates that the closer the end of a "DRX Active" mode, the higher said weighting factor w becomes.
  • This weighting factor w in particular is of advantage in case too many UEs are active in a cell and not all UEs can be served in every subframe. Hence, a decision has to be made to temporarily remove some UEs from scheduling. Such decision can be reached based on the prioritization mechanism presented herein.
  • Fig.5 shows a network component 501, e.g., a base station, a gateway, a router, a switch, etc., that is connected to a network 502. Also, the network component 501 is connected to a terminal 503 and to a terminal 504. The connection between the network component 501 and the terminals 503, 504 could be realized as a radio connection or a connection via a fixed line.
  • a network component 501 e.g., a base station, a gateway, a router, a switch, etc.
  • the connection between the network component 501 and the terminals 503, 504 could be realized as a radio connection or a connection via a fixed line.
  • Traffic (e.g. voice traffic) from the network 502 is sched ⁇ uled by the network component 501 considering the time the terminals 503, 504 remain in their active mode, i.e. the time before the terminals 503, 504 enter a sleep mode to save en ⁇ ergy .
  • the terminal 503 is scheduled at a higher priority, because of its impending sleep mode and receives its traffic prior to the terminal 504, which will be scheduled afterwards.
  • the scheduling may, as described above, further consider other parameters as the type of the terminal, the type of data, the QoS, the channel quality, etc. This may lead to a different decision, in case due to its type of traffic, the terminal 503 would have been insusceptible to delay, but terminal 504 conducts a VoIP call which is very delay-sensitive.
  • the terminals 503, 504 may convey information regarding time information of their sleep modes or active modes to the network component 501. This information can be utilized when scheduling the terminals 503, 504.
  • the terminals 503, 504 may send a request to enter the sleep mode and wait for a confirmation from the network component 501. This avoids a terminal entering its sleep mode just before it would have been served with additional data and therefore al- lows for an efficient power-saving mechanism.
  • Fig.5 could be imple ⁇ mented by a person skilled in the art as various physical units, wherein the terminal may be a mobile terminal and the network component could be realized as a the base station.
  • the terminal or the network component could be realized as or associated with at least one logical entity that may be de ⁇ ployed as hardware, program code, e.g., software and/or firm ⁇ ware, running on a processing unit, e.g., a computer, micro- controller, ASIC, FPGA and/or any other logic device.
  • program code e.g., software and/or firm ⁇ ware
  • a processing unit e.g., a computer, micro- controller, ASIC, FPGA and/or any other logic device.
  • the functionality described herein may be based on an exist ⁇ ing component of a (wireless) network, which is extended by means of software and/or hardware.
  • the base station (s) men- tioned herein could also be referred to as any base station, base transceiver station or base station controller pursuant to any communication standard.
  • the mobile device mobile terminal, mobile station, UE
  • the approach described allows assigning a scheduling priority based on a time period unit the mobile or fixed terminal en ⁇ ters the sleep mode. This corresponds to the fact that the terminal has to be scheduled during its active mode. It is noted that the active mode may be a portion of a DRX cycle during which the terminal could be reached by the network component, in particular the base station.
  • the solution presented herein can be applied to LTE and technologies other than LTE . These tech ⁇ nologies other than LTE may in particular comprise upcoming releases or Standards. Also, the solution may be applied to all kinds of mobile and/or fixed networks, in particular pro- viding corresponding interfaces, timers and/or elements of architecture .
  • the delay of transmission is reduced and/or avoided by efficiently scheduling UEs and avoiding "DRX Sleep" mode when data is to be conveyed from the base station to the UE .
  • the probability for the UE to be scheduled within its "DRX Active" mode phase is increased. This allows fulfilling QoS requirements in combination with a DRX functionality. Hence, the approach provides an efficient solution to offer an improved performance for delay-sensitive traffic like VoIP.
  • DRX prioritization By appropriately adjusting the weighting factor a tradeoff between DRX prioritization and other scheduling criteria can be adjusted meeting individual requirements, e.g. of a net ⁇ work operator and/or a subscriber.
  • w a weighting factor w that is spe ⁇ cific for classes of UEs providing different capabilities and for separate services. For example, delay-sensitive traffic can be scheduled using a higher weighting factor (and thus resulting in a higher likelihood of traffic being conveyed) compared to best effort traffic.
  • de ⁇ lay-sensitive terminals e.g., mobile terminals conveying VoIP
  • different bearers may be defined for different QoS levels, thus the types of services utilized by the termi ⁇ nal may differ, hence the prioritization could be provided considering such types of services.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention porte sur un procédé et un dispositif de traitement de données dans un réseau de communication, dans lequel un terminal se voit affecter une priorité de programmation sur la base d'une période de temps jusqu'à ce que le terminal entre dans un mode veille. En outre, l'invention porte sur un système de communication comprenant ledit dispositif.
EP10734754.4A 2010-07-26 2010-07-26 Procédé et dispositif de traitement de données dans un réseau de communication Withdrawn EP2599357A1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2010/060808 WO2012013215A1 (fr) 2010-07-26 2010-07-26 Procédé et dispositif de traitement de données dans un réseau de communication

Publications (1)

Publication Number Publication Date
EP2599357A1 true EP2599357A1 (fr) 2013-06-05

Family

ID=44201173

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10734754.4A Withdrawn EP2599357A1 (fr) 2010-07-26 2010-07-26 Procédé et dispositif de traitement de données dans un réseau de communication

Country Status (7)

Country Link
EP (1) EP2599357A1 (fr)
KR (1) KR20130041969A (fr)
CN (1) CN103109576A (fr)
AU (1) AU2010358412B2 (fr)
CA (1) CA2808505A1 (fr)
RU (1) RU2544235C2 (fr)
WO (1) WO2012013215A1 (fr)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103391549B (zh) * 2012-05-10 2018-04-06 中兴通讯股份有限公司 一种不连续接收的动态配置方法、终端和基站
EP2782409A1 (fr) * 2013-03-20 2014-09-24 Panasonic Intellectual Property Corporation of America Comportement d'UE déterministe pour rapport CSI/SRS en DRX
US10542450B2 (en) * 2013-09-30 2020-01-21 Alcatel-Lucent Usa, Inc Techniques for improving discontinuous reception in wideband wireless networks
KR102059409B1 (ko) 2013-10-10 2019-12-26 한국전자통신연구원 Ip 기반의 슬립 모드 제어 방법
DK3145251T3 (da) * 2014-05-15 2021-12-06 Ntt Docomo Inc Brugerterminal, trådløs basisstation og trådløs kommunikationsfremgangsmåde
CN105992266B (zh) * 2015-02-02 2021-02-12 中兴通讯股份有限公司 一种非连续接收能力的检测方法和终端、网络侧设备
US10159108B2 (en) * 2015-04-10 2018-12-18 Motorola Mobility Llc DRX handling in LTE license assisted access operation
CN106413119A (zh) * 2015-07-31 2017-02-15 北京信威通信技术股份有限公司 一种ue上行专用资源控制方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011172218A (ja) * 2010-02-21 2011-09-01 Ntt Docomo Inc 端末スケジューリング優先度特定方法及び装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6072784A (en) 1997-07-25 2000-06-06 At&T Corp. CDMA mobile station wireless transmission power management with adaptive scheduling priorities based on battery power level
US8320301B2 (en) * 2002-10-25 2012-11-27 Qualcomm Incorporated MIMO WLAN system
RU2295830C2 (ru) * 2003-04-30 2007-03-20 Самсунг Электроникс Ко., Лтд Система и способ для управления переходом из состояния в состояние в спящем режиме и активном режиме в системе связи с широкополосным беспроводным доступом
US7130668B2 (en) * 2003-09-01 2006-10-31 Samsung Electronics Co., Ltd. Method and system for controlling sleep mode in broadband wireless access communication system
GB0608753D0 (en) * 2006-05-03 2006-06-14 Nokia Corp User equipment

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011172218A (ja) * 2010-02-21 2011-09-01 Ntt Docomo Inc 端末スケジューリング優先度特定方法及び装置

Also Published As

Publication number Publication date
WO2012013215A1 (fr) 2012-02-02
KR20130041969A (ko) 2013-04-25
AU2010358412A1 (en) 2013-02-21
AU2010358412B2 (en) 2015-05-21
CN103109576A (zh) 2013-05-15
CA2808505A1 (fr) 2012-02-02
RU2013109215A (ru) 2014-09-10
RU2544235C2 (ru) 2015-03-20

Similar Documents

Publication Publication Date Title
US9119146B2 (en) Scheduling of user terminals in communication network
AU2010358412B2 (en) Method and device for data processing in a communication network
US9629087B2 (en) Method and apparatus for optimizing power consumption of a terminal in a mobile communication system
US9198131B2 (en) Method for improving battery life and HARQ retransmissions in wireless communications systems
JP5437243B2 (ja) 基地局装置及び通信制御方法
US9635615B2 (en) Method and apparatus for optimizing power consumption of a terminal in a mobile communication system
US20120188903A1 (en) Radio communication system, radio terminals, radio base stations, radio communication method and program
KR20100052064A (ko) 이동 통신 시스템에서 불연속 수신 동작 제어 방법 및 장치
WO2015191225A1 (fr) Gestion de c-drx adaptative
CN104871635A (zh) 用于设备到设备通信中的非连续接收的无线设备、无线电网络节点以及方法
EP3874903B1 (fr) Procédés et dispositifs pour une configuration de réception discontinue adaptative
WO2014002075A2 (fr) Attribution de ressources
US20140204820A1 (en) Method and Arrangement in a Telecommunication System
JP2019512980A (ja) リソース・スケジューリング方法、アクセス・ネットワーク・デバイス、およびユーザ機器
CN111294899B (zh) 用于drx的不活动定时器控制方法及装置、存储介质、终端、基站
CN115915359A (zh) 用于无线通信的方法及用户设备
EP4319466A1 (fr) Procédé de déclenchement d'une commande de réception discontinue de liaison latérale, appareil et système
CN114501689A (zh) 直接通信接口的drx控制方法、装置、终端及存储介质
CN114287168A (zh) 电信系统中的下行链路监测
WO2014112918A1 (fr) Procédé et agencement dans un système de télécommunications

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

17P Request for examination filed

Effective date: 20130226

AK Designated contracting states

Kind code of ref document: A1

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

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SOLUTIONS AND NETWORKS OY

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170316

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

Free format text: STATUS: EXAMINATION IS IN PROGRESS

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SOLUTIONS AND NETWORKS OY

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

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20210422