Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan Moby Dick Consolidated System Integration Plan
D0103v1.doc Version 1 6.7.2003 Parameters of the Meter_Start message are Session_ID and CoA. Parameters of the get_Meter are the Session_ID. The Meter_Stop parameter is the Session_ID only. The Session_ID will be created and maintained by the AAAC Attendant. This session_ID will be combined with a CoA after Meter_Start is called. AAAC client can use it to get Accounting data from meter and inform meter to stop counting for this CoA. Get_Meter_Data return a pointer to the structure. The accounting data are stored in this structure list. The list end with a null point in next. 4.2.2.6.2 Logger Figure 46 depicts the logging framework. It is required that the impact caused by the Integrated Loggers to the main tasks performed by the hosting entity should be reduced to minimum. Therefore Integrated Loggers are required to be non-blocking and must log as fast as possible. The logs will be stored locally before being transferred to the Auditing Framework by the Local Log Management. Access Router AAAC Client Integrated Logger QoS Manager Integrated Logger Local Log Local Log Mgmt Auditing Framework Figure 46: Logger QoS Manager’s Integrated Logger does not know NAI but CoA. In order to allow for logging NAI in Service Authorization Events, the mapping from CoA to NAI must be made available to the QoS Manager’s Integrated Logger. AAAC Client’s Integrated Logger knows this mapping, therefore both Integrated Loggers need to communicate. 4.2.2.6.3 Local Log The Local Log is implemented as a MySQL database consisting of three tables: SoL, UsrReg, and SvcAuth. The table SoL is used to store Availability Event Logs. The table UsrReg is used to store User Registration Event Logs, and the table SvcAuth is used to store Service Authorization Event Logs. The data structure of each of the tables are shown below. Field Type Null allowed? Default LoggerID varchar(255) NO “” LogTime Datetime NO 0000-00-00 00:00:00 EventID tinyint(3) unsigned NO 0 EventID is 1. Table 7: SoL data structure LoggerID is the unique identity of QoSManager (e.g., “:QoSManager”) or AAAC Client (e.g., “:AAACClient”). Field Type Null allowed? Default LoggerID varchar(255) NO “” LogTime Datetime NO 0000-00-00 00:00:00 D0103v1.doc 58 / 168
D0103v1.doc Version 1 6.7.2003 EventID tinyint(3) unsigned NO 0 NAI varchar(255) NO “” CoA varchar(255) NO “” ResultCode int(10) unsigned YES NULL Table 8: UsrReg data structure EventID is 11 for the registration request event from the MN and 12 for the registration response to the MN. NAI is the user identifier. CoA: Care-of Address in hexadecimal text format. ResultCode: result code from the AAAC Server if EventID is 12, 0 if EventID is 11. Field Type Null allowed? Default LoggerID varchar(255) NO “” LogTime Datetime NO 0000-00-00 00:00:00 EventID tinyint(3) unsigned NO 0 NAI varchar(255) NO “” CoA varchar(255) NO “” DestAddr varchar(255) YES NULL DSCP tinyint(3) unsigned NO 0 ResultCode int(10) unsigned YES NULL Table 9: SvcAuth data structure EventID is 21 for the authorization request event to the QoSBroker and 22 for the authorization response from the QoSBroker. CoA: captured and requested traffic source address (Care-of Address) in hexadecimal text format. DestAddr: captured and requested traffic destination address in hexadecimal text format. DSCP: captured and requested traffic DSCP in decimal format. ResultCode: QoSBroker Authorization code: ‘1’=admit/install, ‘2’=reject/block, 0 if EventID is 21. 4.2.2.6.4 Interface between Integrated Loggers for CoA-NAI Mapping The purpose of this communication is to allow the Integrated Logger of QoS Manager to map a CoA to NAI. The message exchange between the Integrated Logger of QoS Manager (ILQoSM) and the Integrated Logger of AAAC Client (ILAAACCl) is simple and defined as follows: ILQoSM à ILAAACCl : GetMap(CoA) ILAAACCl à ILQoSM : Map(NAI, CoA) The format of the message GetMap and Map is shown in the following figure. The Type of the TLV for CoA is 1 and NAI is 2. D0103v1.doc 59 / 168
- Page 7 and 8: D0103v1.doc Version 1 6.7.2003 Abbr
- Page 9 and 10: D0103v1.doc Version 1 6.7.2003 1 In
- Page 11 and 12: D0103v1.doc Version 1 6.7.2003 3 Mo
- Page 13 and 14: D0103v1.doc Version 1 6.7.2003 Doma
- Page 15 and 16: D0103v1.doc Version 1 6.7.2003 NCP
- Page 17 and 18: D0103v1.doc Version 1 6.7.2003 It w
- Page 19 and 20: D0103v1.doc Version 1 6.7.2003 curr
- Page 21 and 22: D0103v1.doc Version 1 6.7.2003 •
- Page 23 and 24: D0103v1.doc Version 1 6.7.2003 No A
- Page 25 and 26: D0103v1.doc Version 1 6.7.2003 o Fo
- Page 27 and 28: D0103v1.doc Version 1 6.7.2003 NCP
- Page 29 and 30: D0103v1.doc Version 1 6.7.2003 4.1.
- Page 31 and 32: D0103v1.doc Version 1 6.7.2003 4.1.
- Page 33 and 34: D0103v1.doc Version 1 6.7.2003 asso
- Page 35 and 36: D0103v1.doc Version 1 6.7.2003 Mobi
- Page 37 and 38: D0103v1.doc Version 1 6.7.2003 WP4
- Page 39 and 40: D0103v1.doc Version 1 6.7.2003 Para
- Page 41 and 42: D0103v1.doc Version 1 6.7.2003 Ackn
- Page 43 and 44: D0103v1.doc Version 1 6.7.2003 inst
- Page 45 and 46: D0103v1.doc Version 1 6.7.2003 MT P
- Page 47 and 48: D0103v1.doc Version 1 6.7.2003 The
- Page 49 and 50: D0103v1.doc Version 1 6.7.2003 RtSo
- Page 51 and 52: D0103v1.doc Version 1 6.7.2003 auth
- Page 53 and 54: D0103v1.doc Version 1 6.7.2003 In a
- Page 55 and 56: D0103v1.doc Version 1 6.7.2003 AR s
- Page 57: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 61 and 62: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 63 and 64: D0103v1.doc Version 1 6.7.2003 Filt
- Page 65 and 66: D0103v1.doc Version 1 6.7.2003 4.2.
- Page 67 and 68: D0103v1.doc Version 1 6.7.2003 •
- Page 69 and 70: D0103v1.doc Version 1 6.7.2003 The
- Page 71 and 72: D0103v1.doc Version 1 6.7.2003 is t
- Page 73 and 74: D0103v1.doc Version 1 6.7.2003 4.3
- Page 75 and 76: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 77 and 78: D0103v1.doc Version 1 6.7.2003 This
- Page 79 and 80: D0103v1.doc Version 1 6.7.2003 This
- Page 81 and 82: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 83 and 84: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 85 and 86: D0103v1.doc Version 1 6.7.2003 The
- Page 87 and 88: D0103v1.doc Version 1 6.7.2003 4.3.
- Page 89 and 90: D0103v1.doc Version 1 6.7.2003 be u
- Page 91 and 92: D0103v1.doc Version 1 6.7.2003 o Ma
- Page 93 and 94: D0103v1.doc Version 1 6.7.2003 Gene
- Page 95 and 96: D0103v1.doc Version 1 6.7.2003 Upli
- Page 97 and 98: D0103v1.doc Version 1 6.7.2003 Now
- Page 99 and 100: D0103v1.doc Version 1 6.7.2003 3. D
- Page 101 and 102: D0103v1.doc Version 1 6.7.2003 User
- Page 103 and 104: D0103v1.doc Version 1 6.7.2003 Inte
- Page 105 and 106: D0103v1.doc Version 1 6.7.2003 User
- Page 107 and 108: D0103v1.doc Version 1 6.7.2003 Serv
D0103v1.doc Version 1 6.7.2003<br />
Parameters of the Meter_Start message are Session_ID and CoA. Parameters of the get_Meter are the<br />
Session_ID. The Meter_Stop parameter is the Session_ID only.<br />
The Session_ID will be created and maintained by the AAAC Attendant. This session_ID will be<br />
combined with a CoA after Meter_Start is called. AAAC client can use it to get Accounting data from<br />
meter and inform meter to stop counting for this CoA.<br />
Get_Meter_Data return a pointer to the structure. The accounting data are stored in this structure list. The<br />
list end with a null point in next.<br />
4.2.2.6.2 Logger<br />
Figure 46 depicts the logging framework. It is required that the impact caused by the Integrated Loggers<br />
to the main tasks performed by the hosting entity should be reduced to minimum. Therefore Integrated<br />
Loggers are required to be non-blocking and must log as fast as possible. The logs will be stored locally<br />
before being transferred to the Auditing Framework by the Local Log Management.<br />
Access Router<br />
AAAC Client<br />
Integrated<br />
Logger<br />
QoS Manager<br />
Integrated<br />
Logger<br />
Local<br />
Log<br />
Local<br />
Log Mgmt<br />
Auditing<br />
Framework<br />
Figure 46: Logger<br />
QoS Manager’s Integrated Logger does not know NAI but CoA. In order to allow for logging NAI in<br />
Service Authorization Events, the mapping from CoA to NAI must be made available to the QoS<br />
Manager’s Integrated Logger. AAAC Client’s Integrated Logger knows this mapping, therefore both<br />
Integrated Loggers need to communicate.<br />
4.2.2.6.3 Local Log<br />
The Local Log is implemented as a MySQL database consisting of three tables: SoL, UsrReg, and<br />
SvcAuth. The table SoL is used to store Availability Event Logs. The table UsrReg is used to store User<br />
Registration Event Logs, and the table SvcAuth is used to store Service Authorization Event Logs.<br />
The data structure of each of the tables are shown below.<br />
Field Type Null allowed? Default<br />
LoggerID varchar(255) NO “”<br />
LogTime Datetime NO 0000-00-00 00:00:00<br />
EventID tinyint(3) unsigned NO 0<br />
EventID is 1.<br />
Table 7: SoL data structure<br />
LoggerID is the unique identity of QoSManager (e.g., “:QoSManager”) or AAAC<br />
Client (e.g., “:AAACClient”).<br />
Field Type Null allowed? Default<br />
LoggerID varchar(255) NO “”<br />
LogTime Datetime NO 0000-00-00 00:00:00<br />
D0103v1.doc 58 / 168