omniran-13-0094-00-ecsg
Cooperation and contributions of the other
WGs in the 802.1-OmniRAN project?
What is the opportunity/impact on WGs?
2013-11-16
Max Riegel
(ECSG Chair)
1
omniran-13-0094-00-ecsg
Outline
• Tentative content of OmniRAN specification
• Chapter structure and representation of access
technologies
• Creation of access technology specific
contributions
• Cooperation between OmniRAN and the other
WGs
• Attracting participation out of the other WGs
• Communication aspects towards other WGs
2
omniran-13-0094-00-ecsg
Draft ToC of the proposed specification
•
•
•
•
•
•
Introduction and Scope
Abbreviations/Acronyms, Definitions, and Conventions
References
Identifiers
Tenets for IEEE 802 Access Network Systems
Access Network Reference Model
– Overview
– Reference Points
– Access Network to Core Internetworking Relationship
•
•
Network Reference Model
Multiple deployment scenarios
Functional Design and Decomposition
–
–
–
–
–
–
–
Network Discovery and Selection
Authentication
Link establishment
QoS and policy control
Link relocation
Link teardown
Accounting
Functional Description
3
omniran-13-0094-00-ecsg
Proposed Network Reference Model for
IEEE 802 Access Network
Terminal
R2
Ctrl
Access
R3
R1
R4
Internet
R3
Access
Access
R3
Ctrl
Core
Authentication
Authentication
Authorization
Authorization
Accounting
Accounting
Location
Location
CoA
CoA
Mobility
Mobility
R5
Access
R3
Encapsulation
DataPath
Encapsulation
Transport
Internet
• Reference Points represent a bundle of functions between peer entities
- Similar to real network interfaces
• Functions are extensible but based on IEEE 802 specific attributes
4
omniran-13-0094-00-ecsg
IEEE 802 Access Network Functional Diagram
Access Network
Scanning
L2 Configuration
AAA
ANQP
Policy
DHCP
Application
Network Selection
Association
Authentication
Authorization
Link Establishment
Accounting
Host Configuration
Application
Policy Control
Link Relocation
Application
Host Config Release
Disassociation
Link Teardown
Accounting
Access Technology
Control I/f
5
omniran-13-0094-00-ecsg
Example Chapter Structure
• Functional Design and Decomposition
– Network Discovery and Selection
•
•
•
•
•
•
–
–
–
–
–
–
Generic functional requirements and information flows
Ethernet functional design <- 802.3
WPAN functional design
<- 802.15
WLAN functional design
<- 802.11
WMAN functional design
<- 802.16
WRAN functional design
<- 802.22
Authentication
Link establishment
QoS and policy control
Link relocation
Link teardown
Accounting
6
omniran-13-0094-00-ecsg
Creating the functional description
• Each main chapter consists of
– generic functional requirements and information flows
– access technology specific descriptions how this works with the current
IEEE 802 standards
• Generic functional requirements may be distilled out of the IEEE 802
standards (reverse engineered)
• Intension is to show how functional requirements can be realized by
current IEEE 802 standards
– Present IEEE 802 as a harmonized family of standards
– Functional differences between standards may become more obvious
– It is up to the WGs, whether and how to address the differences
• No final conclusion yet how to represent 802.19.1 and 802.21 in the
document
– will be considered in the project when the initial framework is available
• Access technology specific descriptions require involvement of the
PHY&MAC groups
– Different modes of operation possible
7
omniran-13-0094-00-ecsg
Cooperation between OmniRAN TG
and the other IEEE 802 WGs
• Access technology specific descriptions require knowledge
about the particular access technologies
• Feasible: Descriptions may be created in OmniRAN TG by
reading the IEEE 802 specifications
– Descriptions require at least thorough technical review by the
experts in the related WGs
• Better: Subject matter experts of the related WGs participate
in OmniRAN and provide specification text for their particular
technology and function.
– When the effort for an access technology is split up into multiple
small contributions, it is more likely to get support from members
of the MAC&PHY working groups.
• What is the motivation for the participation out of the WGs?
• What is the reward for the participants coming over to
OmniRAN?
8
omniran-13-0094-00-ecsg
What can OmniRAN do to attract
participants out of the WGs?
•
Co-located sessions
– Meet at interims with the wireless groups when input from the wireless groups needs
to be discussed
– Meet at interims with the 802.1/802.3 when topics in their domain have to be
discussed
•
Alignment of meeting schedules
– Avoid scheduling OmniRAN at plenary meeting slots of other WGs
– Can we establish a list of meeting slots, which shouldn’t used for joint meetings?
•
Arrangement of agenda for joint meetings
–
–
–
–
•
Focused on specific issues from other WGs
Define precisely the question, which should be discussed and clarified.
Solicit participation of experts in other WGs
Do not exagerate meeting duration
Attendance credit – TBD
– Reciprocal credit for F2F meetings
•
Teleconferences
–
–
–
–
May work better for subject matter experts
Usually lower participation than F2F, but more focused
WebEX required
How to avoid conflicts with other teleconferences?
9
omniran-13-0094-00-ecsg
Communication flow between OmniRAN
and the WGs
• Easy access to OmniRAN documentation and status
– mentor as document repository for comfortable access by
wireless participants
– mentor Wiki to provide transparent status reporting
– dedicated mailing list for OmniRAN with focused email volume to
remain manageable for highly loaded experts.
• Liaison representative for each of the WGs
– Regular OmniRAN status report to keep WG participants
informed
– Takes responsibility for forwarding material for review by the
WGs
– Arranges joint responses out of the WGs
• Commenting and balloting
– Contributing subject matter experts need to be involved
• They may need the power to decide about the acceptance of comments
10
omniran-13-0094-00-ecsg
Further cooperation aspects
• Peer Groups in the WGs?
– Have to be recognized in the cooperation
– Preferably the groups for regular joint
meetings
– OmniRAN may send liaison person into the
meetings of the peer groups
11
omniran-13-0094-00-ecsg
How to proceed?
• Luckily there is some time until the project
officially starts…
• The SG may try a kind of dry run for an
example chapter
– Ready for presentation to the other WGs in
March
12