1. Information Model for AN Setup
Date: [ ]
Authors:
Name
Affiliation
Phone
Hao Wang
Fujitsu R&D Center
Xiaojing Fan
Su Yi
Ryuichi Matsukura
Fujitsu/Fujitsu Laboratory
Notice:
This document does not represent the agreed view of the IEEE OmniRAN TG. It represents only the views of the participants listed in the ‘Authors:’ field above. It is offered as a basis for discussion. It is not binding on the contributor, who reserve the right to add, amend or withdraw material contained herein.
Copyright policy:
The contributor is familiar with the IEEE-SA Copyright Policy <
Patent policy:
The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
< and <
Abstract
This presentation summarizes the contents of AN Setup in 802.1CF draft and explorers a way forward for creating the 802.1CF information model.

2. Information Model for AN Setup
Hao Wang
Fujitsu R&D Center

3. Background (1)
On July F2F, chapter 7.1 has been thoroughly reviewed and revised. The update is also captured in this report, and used as basis for the discussion on the 802.1CF information model (IM). - when still fresh
802.1CF IM is expected to be essential part of chapter 7
Graphical representation of the configuration and management information of P802.1CF
Proposal for structure of data model* of IEEE 802 access network
Make it easier for the operators, users, developers, etc. to understand the modeled objects, the functionalities, the key elements, and inherent relationship among them.
IMs can be defined in an informal way, using natural languages such as English. [RFC3444]
The functional descriptions should be consistent with the IM.
The attributes and functions should be shown explicitly on the IM.
The procedures and messages should not be conflicted with information and logical relationship indicated by the IM.

4. Background (2) Agreements reached on the TG meeting are noted,
Guided by the generic programming rules for creating the texts and the IM
Basic attributes (attribute declaration)
Functional requirement (function declaration)
Basic functions (comments of the functions)
Detail procedures (main loop of the function)
The information model should show the information going over the reference points
Structured according to the functional entities
Indicating source and destination
Differentiating config (rw) and statistics (ro)
Details to be left to the IEEE 802 technologies
Using ‘containers’ where appropriate
UML class diagram (like) is preferred as it is widely adopted as a standard graphical tool to represent objects and the relationships.
Related contributions

5. Summary for AN Setup (Config?)
Unlicensed spectrum (use cases?)
AN initialization (initial config)
AN operation (re-config, adjustment)
AN shutdown (release)
Shared spectrum

6. An Example for AN Initialization (unlicensed spectrum)
CIS SS NA
ANC BH
NMS AR
Power up
Formalize AN (R5 & R7)
Retrieve configuration (R11)
Connection setup (R10 & R4)
Config AN elements (R5 & R7)
Connection setup (R6 & R3)
Radio coordination (R5)

7. Attributes (Containers, IEs) To Be Clarified
Formalize AN (R5 & R7)
Retrieve configuration (R11)
Connection setup (R10 & R4)
Config AN elements (R5 & R7)
Connection setup (R6 & R3)
Radio coordination (R5)
ANC-NA (R5)
NA info. &
indication
NA config & indication
Channel info. & indic.
ANC-BH (R7)
BH info. & indication
BH config & indication
NMS-ANC (R11)
AN info. & AN config.
NA-BH (R6)
NA info. & indication
BH-ARI (R3)
SS-ANC (R4)
AN info. & indication
CIS-ANC (R10)

8. Information Model for AN Initialization
802.1CF IM
Ctrl_ID * *
Control
Service
Intf_ID *
ANC SS AN
Interface
ARC
CIS AR
Port_ID *
TEC
NMS TE
Port NA NA
ANC
AN info. & config
Default config BH BH NA
NA info. & config
Channel info.
Default config
TEI TE
ARI AR BH
BH info. & config
Default config

9. Questions, Comments Thank YOU!