Embed Size (px)
Citation preview
May 2014 doc.: IEEE 15-14-0265-00-0008
Submission QL, CW, HL, ZC, TH @InterDigitalSlide 1
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Power Control for PAC]Date Submitted: [5 May 2014]Source: [Qing Li, Chonggang Wang, Hongkun Li, Zhuo Chen, Tao Han]Company [InterDigital Communications Corporation]Address [781 Third Avenue, King of Prussia, PA 19406-1409, USA] Voice:[610-878-5695], FAX: [610-878-7885], E-Mail:[[email protected]]
Re: [ Call for Final Contributions]
Abstract: [This document proposes power control schemes for 802.15.8 TG]
Purpose: [To discuss technical feasibility of the proposed power control schemes for 802.15.8 TG]
Notice: This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 2
PAC Requirements
• Excerpt from IEEE 802.15.8 PFD [1]– 5.12 Interference management: Interference among multiple links
is managed by the threshold level. – 5.13 Transmit power control: A PD may perform transmit power
control based on channel measurement status.
• Excerpt from IEEE 802.15.8 TGD [2]– 6.7 Interference Management: IEEE 802.15.8 shall provide the
functionality to mitigate interference from other PDs.– 6.8 Transmit Power Control: IEEE 802.15.8 shall support the
functionality for PDs to control the transmit power to minimize interference and power consumption.
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 3
Conventional Power Control
– Open-loop or closed-loop power control based on path-loss.– Provide similar QoS to all the UEs in the cell no matter what
kind of applications or services that the UEs are engaged, i.e. chat on social network, or video conference.
Increase power
Decrease power
UE1UE2
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 4
Context-aware Power Control– Different applications or services [3] require different power control schemes
Application-aware or Context-aware
Peer1
Peer2
Peer3 Peer4Peer5
Peer3-1 Peer3-2
Peer5-1
Peer5-2
Peer5-3
Peer9
Peer10
Peer8
Peer12
Peer11
Peer6
Peer7
Application1: Video Conference· high data rate· high QoS
Application2: Chat · low data rate · low QoS
Application3: Keep Alive
· very low duty cycle· very low data rate · very low QoS
Application4: Game· high data rate· high QoS· short distance
Distributed Group Communication
Centralized Group Communication
Pair Communication
Pair Communication
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 5
Inter-P2PNWs Power Control
– Many P2P networks (P2PNWs) coexist within a short radio range of each other without a central controller to manage the transmission power among the P2PNWs, therefore inter-P2PNWs power control is needed.
For examples:1. What’s the initial transmitting power for a PD when it enters
the proximity?2. Is the “Video Conference Meeting” too loud to affect the other
P2P communications in proximity?3. What’s the transmitting power that a PD may use if
participates in “Chatting” as well as “Gaming”.
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 6
Examples of Context and Power Control InformationApplication Context Info Power Control Info
Video Conf. Meeting
1. Service Power Category: e.g. Cat1 – very high data rate & low error rate
2. QoS: 1-to-N group based -- guaranteed or best effort to all PDs
3. Service Range: medium
1. Max. Tx Power: medium2. Power Control Interval: long3. Measurements at Rx: SINR, CQI, etc. 4. Info from Tx: Tx power level, location,
etc.
Gaming 1. Service Power Category: e.g. Cat2 - high data rate & low error rate
2. QoS: distributive group based -- guaranteed to all PDs
3. Service Range: small
1. Max. Tx Power: medium2. Power Control Interval: long3. Measurements at Rx: SINR, CQI, etc. 4. Info from Tx: Tx power level, location,
etc.
Chat 1. Service Power Category: e.g. Cat3 - low data rate & high error rate
2. QoS: average
1. Power Control Interval: medium2. Measurements at Rx: SINR, RSSI,
etc. 3. Info from Tx: Tx power level, speed,
etc.
Keep Alive 1. Service Power Category: e.g. Cat4 - very low data rate & high error rate
2. QoS: low
1. Measurements at Rx: RSSI, etc. 2. Info from Tx: Tx power level, speed,
etc.
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 7
Context-aware Power Control for PAC
Peer1 starts TPC for Application i
Higher layerPeering
OthersDiscovery
Context and Power Control Information (CPCI)
Inter-P2PNWs Power Control
Intra-P2PNW Power Control
· Higher layer passes the default CPCI values (preconfigured and/or updated from previous sessions) to Power Control function.
· Power Control function extracts the CPCI values in proximity by scanning Beacon, Paging, and Broadcast channels.
· Power Control function calculates the initial Tx power level based on the CPCI values passed from higher layer and/or detected in proximity.
· Broadcast at Common channel at the initial power level, and wait for the response(s) form the PD(s) in proximity.
· Adjust the Tx power level based on the response(s) from PD(s).
· Transmit at the power level updated from the Inter-P2PNWs Power Control stage, and wait for the response(s) form the PD(s) within the P2PNW.
· Adjust the Tx power level based on the response(s) from PD(s).
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 8
Examples of CPCI
SPCat
Beacon
SerR PCInt TxP
CPCI
SPCat
Common Control/Data Channel
SerRBW/MCS
TxP
CPCI
PCInt
Transmission Frame
TxP1 EP1 TxP2
CPCI
EP2
TxP
Transmission Frame
SINR
CPCI
Control/Data
Control/Data PAdj
CPCI in Beacon: CPCI is inserted in the beacon and can be detected and extracted by a peer in the proximity.
CPCI on Common Control/Data Channel: CPCI is broadcasted on a common control or data channel to be detected and used for collaborating power control among the peers in proximity.
CPCI in a Transmission Frame: CPCI is transmitted with control information for Point-to-Multipoints power control request, or with data information for initial or open loop power control from a multicast transmitter.
CPCI in a Transmission Frame: CPCI is transmitted with control information for power control response, or with data information for closed loop power control with required power adjustment from a receiver.
Note The exact location of CPCI may vary depending on the specification or implementation of CPCI for context-aware power control.
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 9
Context-aware Power Control -- CPCI Detection (1/2)
Peer1 starts TPC for Appi
1. Receive CPCIAppiPr1 from the higher layer.2. Extract CPCI from beacon/paging/common channel.3. Update the list of CPCIs in proximity CPCIProS.4. Collect measured RxSQProS corresponding to CPCIProS.
CPCIProS empty?
Yes
No
Higher layer
PA OthersPD
Timed outtOutDetCPCI?
CPCI Detection
Yes
No
Set initial value of TxPAppiPr1 based on Appi’s default min power
Set initial value of TxPAppiPr1 based on detected CPCI
Inter-P2PNWs Power Control
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 10
Context-aware Power Control -- CPCI Detection (2/2)
Peer1Power Control
Peer1Higher Layer
App j SuperVL
Peer2Power Control
App 1 VL1
App 2 VL2
App 4 Peer1
App 4 Peer2
App 5 Peer1
App 3 VL3
Centralized Control
App i
1. Trigger Power Control Load CPCIAppiPr1
2. Detect CPCIProS
& measure RxSQProS
CPCIAppjSupVLj
CPCIApp1VL1, CPCIApp2VL2, CPCIApp3VL3
CPCIApp4Pr1~2, CPCIApp5Pr1
In Proximity of App i Peer1
CP
CI
De
tect
ion
in
Pro
xim
ity
Peer2Higher Layer
(CPCIProS: CPCIs detected in proximity of App i Peer1)
Hybrid ControlDistributed
Control
10.4.1 Inter-P2PNWs Power Control
10.4.2 Intra-P2PNW Power Control
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 11
Context-aware Power Control Procedure- Inter-P2PNWs Power Control (1/2)
From “CPCI Detection in Proximity”
Set initial value of TxPAppiPr1 based on Appi’s min power
Set initial value of TxPAppiPr1 based on CPCIProS, RxSQProS and CPCIAppiPr1
Inter-P2PNWs Power Control
Response?
Yes
No
Send power request with CPCIAppiPr1 at TxPAppiPr1 on Common Channel for Appi.
1. Adjust TxPAppiPr1 with responses2. Update CPCIAppiPr1
1. Increase TxPAppiPr1= min{MaxTxPAppi,, (TxPAppiPr1 + PAdjAppi)}2. Update CPCIAppiPr1
Time out?
Yes
No
1. Increase TxPAppiPr1 = min{MaxTxPAppi, (TxPAppiPr1 +PAdjAppi)}2. Update CPCIAppiPr1
To “Intra-P2PNW Power Control”
(CPCIProS empty)(CPCIProS not empty)
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 12
Context-aware Power Control- Inter-P2PNWs Power Control (2/2)
Peer1Power Control
Peer1Higher Layer
App j SuperVL
Peer2Power Control
App 1 VL1
App 2 VL2
App 4 Peer1
App 4 Peer2
App 5 Peer1
App 3 VL3
Centralized Control
App i
CPCIAppiPr1
CPCIAppjSupVLj, PAdjAppjSupVLj
CPCIApp1VL1, PAdjAppiVL1; CPCIApp2VL2, PAdjApp2VL2...
CPCIApp4Pr1, PAdjApp4Pr1; CPCIApp4Pr2, PAdjApp4Pr2; CPCIApp5Pr1, PAdjApp5Pr1
In Proximity of App i Peer1
Inte
r-P
2P
NW
Po
we
r C
on
tro
l
Peer2Higher Layer
Hybrid ControlDistributed
Control
(3B. Power Control Reponses to Peer1 with the Peers’ CPCIs in proximity)
(3A. Power Control Request from Peer1with Peer1's CPCIAppiPr1)
3. Appi Peer1 collaborates with the SupVL/VLs/Peers in proximity on Common Channel by exchanging the CPCIs
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 13
Context-aware Power Control Procedure- Intra-P2P Power Control (1/2)
Peer1 ends TPC for Appi
From “Inter-P2PNWs Power Control”
Responsefrom Peer2?
Yes
No
Intra-P2PNW Power Control
1.Transmit on Appi channel at power level TxPAppiPr1 with updated CPCIAppiPr1
2. Feedback updated CPCIAppiPr1 to higher layer.
1. Increase TxPAppiPr1 = min{MaxTxPAppi, (TxPAppiPr1 +PAdjAppi)}2. Update CPCIAppiPr1
Appi transmission?
No
1. Send power request with CPCIAppiPr1 at TxPAppiPr1 on Appi channel to Peer22. Feedback updated CPCIAppiPr1 to higher layer.
Time out?Response
from Peer2?Yes No1. Adjust TxPAppiPr1 with Peer2's
response2. Update CPCIAppiPr1 with PAdjAppiPr1Pr2 Yes
No 1. Increase TxPAppiPr1 = min{MaxTxPAppi, (TxPAppiPr1 +PAdjAppi)}2. Update CPCIAppiPr1
Yes
(abort)
No
Yes
Time out?
1. Adjust TxPAppiPr1 with Peer2's response2. Update CPCIAppiPr1with PAdjAppiPr1Pr2
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 14
Context-aware Power Control- Intra-P2PNW Power Control (2/2)
Peer1Power Control
Peer1Higher Layer
App j SuperVL
Peer2Power Control
App 1 VL1
App 2 VL2
App 4 Peer1
App 4 Peer2
App 5 Peer1
App 3 VL3
Centralized Control
App i
4A.Send Power Request @TxPAppiPr1 with CPCIAppiPr1
4B.Feedback CPCIAppiPr1
6B. Response @TxPAppiPeer2
w. PAdjAppiPeer2 & CPCIAppiPr2
8A.Trans. data @TxPAppiPr1
with PAdjAppiPr1 & CPCIAppiPr1
8B.Feedback CPCIAppiPr1
10B. ACK @TxPAppiPr2
w. PAdjAppiPr2 & CPCIAppiPr2
In Proximity of App i Peer1
5. Adjust TxPAppiPeer2
& update CPCIAppiPeer2
7. Adjust TxPAppiPr1
& update CPCIAppiPr1
9. Adjust TxPAppiPr2
& update CPCIAppiPr2
Intr
a-P
2PN
W P
ower
Con
trol
Peer2Higher Layer
Hybrid ControlDistributed
Control
1. Peer1 exchanges CPCIs with Peer22. Peer1 updates CPCIs to high layer
6A.Feedback CPCIAppiPr2
10A.Feedback CPCIAppiPr2
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 15
Context-aware Power Control – Multi-App (1/2)
Peer1 starts TPC for Appi
CPCI Detection for Appi
Application i
Higher layer
PA OthersPD
Multi-App CPCI Management
YesNo
Application j
Inter-P2PNWs CPCI Management for Appi
Peer1 starts TPC for Appj
CPCI detection for Appj
Higher layer
PA OthersPD
Inter-P2PNWs CPCI Management for Appj
TxPAppiPr1 (initial) TxPAppjPr1 (initial)
Appj trans? Yes NoAppi trans?
Yes
NoAppi trans? Appj trans?
No
Yes
Peer1 ends TPC for Appi Peer1 ends TPC
for Appj
Yes
No
Yes
No
Appj trans?
Appi trans?
(abort)
Yes
No
Appj trans? Yes
No
Appi trans?
PHY / MAC Procedures for Appi transmission
(abort)
PHY / MAC Procedures for Appi transmission
PHY / MAC Procedures for Appj transmission
PHY / MAC Procedures for Appj transmission
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 16
Context-aware Power Control - Multi-App (2/2)Peer1Power Control
Peer1Higher Layer
Peer2Power Control
App i
1. Appi Starts: trigger Power Control Load CPCIAppiPr1
2. Appi: CPCI Detection in Proximity
3. Appi: Inter-P2PNW CPCIAppi Management
Peer2Higher Layer
4. Appi: Intra-P2PNW CPCIAppi Management between Peer1 and Peer2
Peer3Power Control
Peer3Higher Layer
6. Appj Starts: trigger Power Control Load CPCIAppjPr1
7. Appj: CPCI Detection in Proximity
8. Appj: Inter-P2PNW CPCIAppj Management
5. Upload CPCIAppiPr1
10. Appi transmits: Load CPCIAppiPr1
11. Appi: Intra-P2PNW CPCIAppi Management between Peer1 and Peer2
9. Upload CPCIAppjPr1
12. Upload CPCIAppiPr1
13. Appj transmits: Load CPCIAppjPr1
14. Appj: Intra-P2PNW CPCIAppi Management between Peer1 and Peer3
15. Upload CPCIAppjPr1
App j
May 2014 doc.: IEEE 15-14-0265-00-0008
Submission QL, CW, HL, ZC, TH @InterDigitalSlide 17
Simulation Performance of Context Aware Power control
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 18
Test Case 1:– For short range application (e.g. game) with high data rate
and low error rate requirement, context aware power control keeps the same Tx power when a peer moves out of service range.
– Distance between peer 0 and 1: 20m increases to 80m
Game App
01
1'
Moving out of service range
App 1
App 2
Proximity
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 19
Test Case 1: Simulation ParametersParameters for Game Application Value
Initial Tx Power 0 dBm
(Max, Min) Tx Power (30, -20) dBm
MCS 64QAM, ¾ Coding rate
SINR threshold 13 dB
Mapped PER 1.03e-4
Service Range 30 meters
Bandwidth 10 MHz
Physical Data Rate 27 Mbps
Power Adjustment Step 0.1 dB
Slot Length 1 ms
Close Loop Power Control Interval 100 ms
Traffic Model full buffer
Simulation Time 20 s
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 20
Test Case 1: Simulation Result Results
• Context aware power control maintains the same Tx power level when peer 1 moves out of the service range for the short range game application.
• Conventional power control continues increasing the Tx power considering only distance.
0 10 20 30 40 50 60-20
-10
0
10
20
30
Time (s)
Inst
an
tan
eo
us
Tx
Po
we
r (d
Bm
)
0 20 40 605
10
15
Time (s)
Re
ceiv
ed
SIN
R(d
B)
0 20 40 6020
40
60
80
Time (s)
Dis
tan
ce (
m)
Context Aware PC
Conventional PCPeer 1 moves outof service range(30m) at 10s
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 21
• Test Case 2:– Context aware power control differentiates the QoS
requirement for different applications, and applies different power control schemes accordingly.
– For example, chatting application is high error tolerable and low data rate requirement; game application requires low error rate and high data rate.
Chat App
3 (moving)2
Game App
0 (moving) 10'
out of service range
3'
Proximity
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 22
Test Case 2: Simulation ParametersParameters for Chat Application Value
Initial Tx Power 0 dBm
(Max, Min) Tx Power (30, -20) dBm
MCS QPSK, ¾ Coding rate
SINR threshold 5 dB
Mapped PER 2.51e-3
Bandwidth 10 MHz
Physical Data Rate 9 Mbps
Power Adjustment Step 0.1 dB
Slot Length 1 ms
Close Loop Power Control Interval 50 ms
Traffic Model Bursty traffic (arrival probability=0.1)
Simulation Time 20 s
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 23
Test Case 2: Simulation Results
• Context aware power control treats different applications with different QoS requirements
• Conventional power control is not aware of different requirements of applications.
0 2 4 6 8 10 12 14 16 18 20-20
-15
-10
-5
Time (Seconds)
Inst
anta
neou
s T
x P
ower
(dB
m)
Context Aware PC for ChatContext Aware PC for GameConventional PC for Chat & Game
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 24
• Test Case 3:– Context aware power control reduces the overall interference
among different P2P networks (i.e. applications). It adjusts the power not only considering the interference within a P2P network also the interference among P2P networks.
– Parameters follows those used in test 1 and 2 for game and chat applications, respectively.
– Peer 0 and 4 is moving toward to 1 and 5 respectively to the shortest distance at 10 seconds, and then move away.
Game App 1
1
0 (moving)
Chat App
5
4 (moving)
Game App 2
23
D(2,3)=28m
D(0,1): 25m->15m->25mD(4,5)=44.7m->28.3m->44.7m
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 25
Test Case 3: Simulation Results (1/2)• Context aware
power control limits to increase Tx power for chat application (low data rate and high error tolerable) by considering not to generate too strong interference to the game application, which requires high data rate and low error rate.10 12 14 16 18 20
-18
-16
-14
-12
-10
-8
-6
Time (Seconds)
Inst
anta
neou
s T
x P
ower
(dB
m)
Context Aware PC for Game 1
Conventional PC for Game 1
Context Aware PC for Game 2Conventional PC for Game 2
Context Aware PC for Chat
Conventional PC for Chat
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 26
Test Case 3: Simulation Results (2/2)
• Context aware power control achieves higher efficiency ratio of power consumption by mitigating the interference among P2P networks, i.e. using less power for successfully receiving a packet.
Efficiency ratio of power consumption=total consumed power to send all the pktstotal number of received pkts
0 2 4 6 8 10 12 14 16 18 200
0.05
0.1
0.15
0.2
0.25
Time (Seconds)
Effi
cien
cy R
atio
of
Pow
er C
onsu
mpt
ion
(mw
/pkt
)
Context Aware PCConventional PC
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 27
Conclusions Context-aware
– Different P2PNWs, formed for different applications or services, conduct different Power Control schemes optimized with different Context and Power Control Information (CPCI).
– A peer participated in multi-applications may conduct different power control schemes based on the CPCI.
Co-existence– Optimized the transmitting power level not only for the individual
transmitter or receiver, but also for over all P2PNWs in proximity, i.e. inter-P2P power control to reduce interference to other PDs in proximity.
Infrastructure-less– No central controller to specify the initial power level and the max.
power level, etc. CPCI detection in proximity
Cooperation among PDs in proximity, i.e. Inter-P2PNWs power control
Submission QL, CW, HL, ZC, TH @InterDigital
May 2014 doc.: IEEE 15-14-0265-00-0008
Slide 28
References
• [1] PAC Framework Document (PFD) 15-14-0085-01 • [2] Technical Guidance Document (TGD) 15-12-0568r9 • [3] Application Matrix 15-12-0684r0 • [4] Power Control for PAC – Final Contribution Doc, IEEE
15-14-0266-00-008.
May 2014 doc.: IEEE 15-14-0265-00-0008
Submission QL, CW, HL, ZC, TH @InterDigitalSlide 29
Thank You!
Any Questions?
