Naming Conventions in IEEE 802.15 TG3d Proposal
September 2016
Slide 1
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks
Project: IEEE P802.15 Working Group for Wireless Personal Area Networks
(WPANs)
(WPANs)
Submission Title:
Some thoughts on naming conventions in TG3d
Date Submitted:
15 September 2016
Source:
Thomas Kürner (TU Braunschweig)
Address Schleinitzstr. 22, D-38092 Braunschweig, Germany
Voice:+495313912416, FAX: +495313915192, E-Mail: kuerner@ifn.ing.tu-bs.de
Re:
15-16-0595-00-003d-proposal-for-ieee802-15-3d-thz-phy
Abstract:
This document discusses naming conventions wrt to the THz, parinet and HRCP nature of
TG3d
Purpose:
To be considered in TG3d baseline document
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.
Thomas Kürner (TU Braunschweig)
Scope of TG3d
•
Within TG3d a new PHY operating at 252 to 325 GHz
is developed for switched point-to-point links
•
The amendment developed inTG3d distinguishes
from the baseline standard by introducing
–
a
P
H
Y
f
o
r
n
e
w
f
r
e
q
u
e
n
c
y
r
a
n
g
e
-
>
T
H
z
P
H
Y
–
t
h
e
c
o
n
c
e
p
t
o
f
p
o
i
n
t
-
t
o
-
p
o
i
n
t
l
i
n
k
s
,
w
h
e
r
e
o
n
l
y
t
w
o
d
e
v
i
c
e
s
a
r
e
i
n
v
o
l
v
e
d
.
T
h
i
s
i
s
t
h
e
s
a
m
e
c
o
n
c
e
p
t
a
s
i
n
t
r
o
d
u
c
e
d
b
y
t
h
e
p
a
r
a
l
l
e
l
r
u
n
n
i
n
g
p
r
o
j
e
c
t
T
G
3
e
a
n
d
i
s
c
a
l
l
e
d
t
h
e
r
e
a
p
a
i
r
n
e
t
September 2016
Slide 2
Thomas Kürner (TU Braunschweig)
Scope of TG3e
•
W
i
t
h
i
n
T
G
3
e
a
n
e
w
P
H
Y
,
b
u
t
s
t
i
l
l
o
p
e
r
a
t
i
n
g
a
t
6
0
G
H
z
i
s
d
e
v
e
l
o
p
e
d
f
o
r
H
i
g
h
-
R
a
t
e
C
l
o
s
e
p
r
o
x
i
m
i
t
y
(
H
R
C
P
)
a
p
p
l
i
c
a
t
i
o
n
s
.
•
H
R
C
P
a
l
s
o
i
n
v
o
l
v
e
s
o
n
l
y
t
w
o
d
e
v
i
c
e
s
.
T
h
e
r
e
f
o
r
e
t
h
e
c
o
n
c
e
p
t
o
f
p
a
i
r
n
e
t
i
s
i
n
t
r
o
d
u
c
e
d
.
•
HRCP devices are always operating in a pairnet.
September 2016
Slide 3
Thomas Kürner (TU Braunschweig)
Commonalities and Differences between
TG3d and TG3e
•
C
o
m
m
o
n
a
l
i
t
i
e
s
:
I
n
b
o
t
h
c
a
s
e
s
t
h
e
d
e
v
i
c
e
s
a
r
e
a
l
w
a
y
s
o
p
e
r
a
t
e
d
a
s
p
a
i
r
n
e
t
•
D
i
f
f
e
r
e
n
c
e
s
:
T
G
3
d
o
p
e
r
a
t
o
r
e
s
a
t
t
h
e
3
0
0
G
H
z
b
a
n
d
(
T
H
z
)
a
n
d
T
G
3
e
o
p
e
r
a
t
e
s
a
t
t
h
e
6
0
G
H
z
b
a
n
d
.
•
Partly commonalities/partly differences
: Some
applications in TG3d are HRCP applications, soem
are not (see next slide)
July 2016
Slide 4
Thomas Kürner (TU Braunschweig)
HRCP and non-HRCP applications are
considered in TG3d
September 2016
Slide 5
HRCP
Non-HRCP
Oberservations made in P802.15.3e D04
•
T
h
e
t
e
r
m
s
p
a
i
r
n
e
t
a
n
d
H
R
C
P
a
r
e
s
o
m
e
t
i
m
e
s
u
s
e
d
a
s
„
s
y
n
o
n
y
m
“
.
I
t
i
s
n
o
t
a
l
w
a
y
s
c
l
e
a
r
,
w
h
i
c
h
e
l
e
m
e
n
t
s
a
r
e
d
u
e
t
o
t
h
e
H
R
C
P
n
a
t
u
r
e
a
n
d
w
h
i
c
h
f
e
a
t
u
r
e
s
a
r
e
d
u
e
t
o
t
h
e
p
a
r
i
n
e
t
n
a
t
u
r
e
.
•
Example: The HRCP PNC is rather a pairnet coordinator
September 2016
Slide 6
Thomas Kürner (TU Braunschweig)
Proposal for the naming conventions
(1/2)
•
Throughout both amendments a clear
distinction has to be made:
–
T
h
e
t
e
r
m
T
H
z
P
H
Y
s
h
o
u
l
d
b
e
u
s
e
d
,
w
h
e
n
e
v
e
r
t
h
e
f
e
a
t
u
r
e
i
s
a
s
p
e
c
i
a
l
c
a
s
e
t
h
a
t
a
p
p
l
i
e
s
f
o
r
t
h
e
3
0
0
G
H
z
b
a
n
d
a
n
d
t
h
e
c
o
r
r
e
s
p
o
n
d
i
n
g
T
H
z
P
H
Y
.
–
T
h
e
t
e
r
m
H
R
C
P
P
H
Y
s
h
o
u
l
d
b
e
u
s
e
d
,
w
h
e
n
e
v
e
r
t
h
e
f
e
a
t
u
r
e
i
s
a
s
p
e
c
i
a
l
c
a
s
e
t
h
a
t
a
p
p
l
i
e
s
f
o
r
s
p
e
c
i
f
i
c
H
R
C
P
P
H
Y
(
o
e
p
r
a
t
i
n
g
a
t
6
0
G
H
z
)
.
–
T
h
e
t
e
r
m
p
a
i
r
n
e
t
s
h
o
u
l
d
b
e
u
s
e
d
,
w
h
e
n
e
v
e
r
i
t
i
s
a
s
p
e
c
i
a
l
c
a
s
e
f
o
r
p
a
i
r
n
e
t
s
i
n
g
e
n
e
r
a
l
a
n
d
n
o
t
r
e
s
t
r
i
c
t
e
d
t
o
H
R
C
P
o
n
l
y
–
T
h
e
t
e
r
m
H
R
C
P
s
h
o
u
l
d
b
e
u
s
e
d
,
w
h
e
n
e
v
e
r
i
t
i
s
a
s
p
e
c
i
a
l
c
a
s
e
f
o
r
H
R
C
P
a
p
p
l
i
c
a
t
i
o
n
s
o
n
l
y
.
Slide 7
September 2016
Proposal for the naming conventions
(2/2)
–
T
h
e
t
e
r
m
T
H
z
p
a
i
r
n
e
t
s
h
o
u
l
d
b
e
u
s
e
d
,
w
h
e
n
e
v
e
r
t
h
e
f
e
a
t
u
r
e
i
s
a
s
p
e
c
i
a
l
c
a
s
e
t
h
a
t
a
p
p
l
i
e
s
f
o
r
a
p
a
i
r
n
e
t
a
n
d
t
h
e
T
H
z
P
H
Y
o
n
l
y
.
–
T
h
e
t
e
r
m
T
H
z
H
R
C
P
s
h
o
u
l
d
b
e
u
s
e
d
,
w
h
e
n
e
v
e
r
t
h
e
f
e
a
t
u
r
e
i
s
a
s
p
e
c
i
a
l
c
a
s
e
t
h
a
t
a
p
p
l
i
e
s
f
o
r
t
h
e
c
o
m
b
i
n
a
t
i
o
n
o
f
a
n
H
R
C
P
a
n
d
t
h
e
T
H
z
P
H
Y
o
n
l
y
.
–
T
h
e
t
e
r
m
T
H
z
n
o
n
-
H
R
C
P
p
a
i
r
n
e
t
s
h
o
u
l
d
b
e
u
s
e
d
,
w
h
e
n
e
v
e
r
t
h
e
f
e
a
t
u
r
e
i
s
a
s
p
e
c
i
a
l
c
a
s
e
t
h
a
t
a
p
p
l
i
e
s
f
o
r
t
h
e
c
o
m
b
i
n
a
t
i
o
n
a
T
H
z
p
a
i
r
n
e
t
a
n
d
n
o
n
-
H
R
C
P
o
n
l
y
.
Slide 8
Thomas Kürner (TU Braunschweig)
September 2016
Overview of Features adressed and
names (to be) used in TG3d and TG3e
September 2016
Slide 9
HRCP
PHY
THz
PHY
Pairnet
HRCP
Non
-
HRCP
Piconet
PHY
Pairnet/
Piconet
HRCP/
Non-
HRCP
3e
3d
future
3??
Thomas Kürner (TU Braunschweig)
This document discusses naming conventions in the context of IEEE 802.15 TG3d, focusing on the THz PHY, pairnet concept, and HRCP applications. It distinguishes between TG3d and TG3e, highlighting commonalities and differences in device operations, frequency bands, and application scenarios.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
September 2016 doc.: IEEE 802.15-16-0690-01-003d_Final_Proposal_3d_Explanations Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Some thoughts on naming conventions in TG3d Date Submitted: 15 September 2016 Source: Thomas K rner (TU Braunschweig) Address Schleinitzstr. 22, D-38092 Braunschweig, Germany Voice:+495313912416, FAX: +495313915192, E-Mail: kuerner@ifn.ing.tu-bs.de Re: 15-16-0595-00-003d-proposal-for-ieee802-15-3d-thz-phy Abstract: This document discusses naming conventions wrt to the THz, parinet and HRCP nature of TG3d Purpose: To be considered in TG3d baseline document 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 Slide 1 Thomas K rner (TU Braunschweig)
September 2016 doc.: IEEE 802.15-16-0690-01-003d_Final_Proposal_3d_Explanations Scope of TG3d Within TG3d a new PHY operating at 252 to 325 GHz is developed for switched point-to-point links The amendment developed inTG3d distinguishes from the baseline standard by introducing a PHY for new frequency range -> THz PHY the concept of point-to-point links, where only two devices are involved. This is the same concept as introduced by the parallel running project TG3e and is called there a pairnet Submission Slide 2 Thomas K rner (TU Braunschweig)
September 2016 doc.: IEEE 802.15-16-0690-01-003d_Final_Proposal_3d_Explanations Scope of TG3e Within TG3e a new PHY, but still operating at 60 GHz is developed for High-Rate Close proximity (HRCP) applications. HRCP also involves only two devices. Therefore the concept of pairnet is introduced. HRCP devices are always operating in a pairnet. Submission Slide 3 Thomas K rner (TU Braunschweig)
July 2016 doc.: IEEE 802.15-16-0690-01-003d_Final_Proposal_3d_Explanations Commonalities and Differences between TG3d and TG3e Commonalities: In both cases the devices are always operated as pairnet Differences: TG3d operatores at the 300 GHz band (THz) and TG3e operates at the 60 GHz band. Partly commonalities/partly differences: Some applications in TG3d are HRCP applications, soem are not (see next slide) Submission Slide 4 Thomas K rner (TU Braunschweig)
September 2016 doc.: IEEE 802.15-16-0690-01-003d_Final_Proposal_3d_Explanations HRCP and non-HRCP applications are considered in TG3d 10...100 Gbit/s 10...100 Gbit/s HRCP Intra-Device Communication Kiosk downloads 10...100 Gbit/s 10..100 Gbit/s Non-HRCP Wireless Links in Data Centers Backhaul/Fronthaul links Submission Slide 5
September 2016 doc.: IEEE 802.15-16-0690-01-003d_Final_Proposal_3d_Explanations Oberservations made in P802.15.3e D04 The terms pairnet and HRCP are sometimes used as synonym . It is not always clear, which elements are due to the HRCP nature and which features are due to the parinet nature. Example: The HRCP PNC is rather a pairnet coordinator Submission Slide 6 Thomas K rner (TU Braunschweig)
September 2016 doc.: IEEE 802.15-16-0690-01-003d_Final_Proposal_3d_Explanations Proposal for the naming conventions (1/2) Throughout both amendments a clear distinction has to be made: The term THz PHY should be used, whenever the feature is a special case that applies for the 300 GHz band and the corresponding THz PHY. The term HRCP PHY should be used, whenever the feature is a special case that applies for specific HRCP PHY (oeprating at 60 GHz). The term pairnet should be used, whenever it is a special case for pairnets in general and not restricted to HRCP only The term HRCP should be used, whenever it is a special case for HRCP applications only. Submission Slide 7
September 2016 doc.: IEEE 802.15-16-0690-01-003d_Final_Proposal_3d_Explanations Proposal for the naming conventions (2/2) The term THz pairnet should be used, whenever the feature is a special case that applies for a pairnet and the THz PHY only. The term THz HRCP should be used, whenever the feature is a special case that applies for the combination of an HRCP and the THz PHY only. The term THz non-HRCP pairnet should be used, whenever the feature is a special case that applies for the combination a THz pairnet and non-HRCP only. Submission Slide 8 Thomas K rner (TU Braunschweig)
September 2016 doc.: IEEE 802.15-16-0690-01-003d_Final_Proposal_3d_Explanations Overview of Features adressed and names (to be) used in TG3d and TG3e future 3?? HRCP PHY THz PHY 3d PHY Piconet Pairnet 3e Pairnet/ Piconet HRCP/ Non- HRCP HRCP Non- HRCP Submission Slide 9 Thomas K rner (TU Braunschweig)
