For Internal Use Only IN Attribute Analysis (FN1620) 1 © Nokia Siemens Networks

FN1620
IN Attribute Analysis
(INAA)
For internal use only

1 © Nokia Siemens Networks IN Attribute Analysis (FN1620)
• Attribute Analyses basics

• Architecture – from operator point of view
• Files
• Architecture – the algorithm

Attribute Analyses basics
• Register analysis
– Performed via direct analysis file readings with synchronous
services
– Register analysis files are distributed into signalling units, so Call
Control PRBs can directly access them
• Attributes of calls are examined
• Executed during setup
• Final result: call characteristics changes

Attribute Analyses basics
• Attribute Analyses (ZRQ command group)

– AIF (MOC and MTC) attribute analysis / R, E commands
– Charging attribute analysis / J, F
– EOS attribute analysis / K, G
– Routing attribute analysis / L, H
– Intelligent Network attribute analysis / S, V
– Service attribute analysis / P, U
– Web Service attribute analysis / W, X
• IN Attribute Analysis
– Operator can change IN-related characteristics


• Files

Architecture – from operator point of view
• Inputs to be analyzed  subanalyses
• Changes on IN characteristics  results
• Operator wants to
– analyze several attributes
– to decide whether IN-behaviour shall be changed


• Inputs to be analyzed  subanalyses

• Changes on IN characteristics  IN results
• Operator wants to
– analyze several attributes  Analysis Chain
– to decide wheter IN-behaviour should be changed or not.

• Operator can configure inputs and results via MML

• Register analysis  config saved to files
• Operator interface
ATTRIBUTE ANALYSIS HANDLING COMMANDS
S: ..... CREATE IN RESULT
V: ..... MODIFY IN RESULT
T: ..... DELETE FINAL RESULT
Q: ..... INTERROGATE FINAL RESULT
C: ..... CREATE SUBANALYSIS
D: ..... DELETE SUBANALYSIS
M: ..... MODIFY SUBANALYSIS
I: ..... INTERROGATE SUBANALYSIS
N: ..... CHANGE STATE OF SUBANALYSIS

• Creating an analysis chain

1. Creating starting subanalysis
ZRQC:IN,<name>,START:<name and value of input>:<ANA>,<DEFANA>;
2. Creating continuation subanalyses

ZRQC:IN,<name>,CONT:<name and value of input>:<RES>,<DEFRES>;
3. Creating result
ZRQS:<result name>:<final result data>;
• Every analysis chain has a result

• During setup
– Analysis chain is executed
– Result is applied

Service Attribute Analysis

• Files

Files
• Input values are always represented by digits

– Numeric inputs are not changed (but possible)
– Alphabetic inputs are mapped to constants, e.g. CBTYPE:
 „speech” = call_bearer_type_t_speech_c (0x1)
 „audio” = call_bearer_type_t_audio_c (0x2)
 „fax” = call_bearer_type_t_fax_c (0x3)
– How to store subanalysis chains?
 Modified linked list
 Stored in AAFILE and AVFILE
• Results are in one STRUCT
– Stored in AR5FIL

IN Attribute Analysis files
AAFILE (file number: 81A)

• Contains the basic information of subanalyses
• Record representation: aafile_t
• 1 subanalysis = 1 record
• Records 1..15 are reserved for starting subanalyses – the
entry points of the analysis chains
• Records 16..512 are used for continuation subanalyses
• Record structure (with the most important fields only):
Name of ID of the attribute Pointer to UNK Pointer to DEF Pointer to AVFILE
subanalysis to be analyzed result result (entry point of digit chain)

AVFILE (file number: 829)

• AVFILE is the analysis file of the attribute values
• Record representation: avfile_t
• Entry point (record) is determined by the AAFILE
• One record contains 20 subrecords: av_subrec_t
• Every subrecord means one digit (0..F and special marks)
• That is, the position of a subrecord within a record means
the exact digit to be analyzed
• The structure of one subrecord:
Pointer to next record Place of the next record Digit counter
00 = not matching digit
01 = AR5FIL
02 = AAFILE
For internal use only 03 = AVFILE
AR5FIL (file number: 822)

• AR5FIL contains the results
• One result – one record
• Record representation: ar5fil_t
• Last pointer of the subanalysis chain points to an
AR5FIL record, if every digit matched

Example (result):
• Create results for matching and non-matching analyses
• ZRQS:MATCH:SCPSET=111;
– Record No. 0x0001 reserved in AR5FIL
• ZRQS:NMATCH;
– Record No. 0x0002 reserved in AR5FIL

Example (subanalysis):
ZRQC:IN,SUB1,START:AADDRC=128:RES=MATCH,DEFRES=NMATCH;
• New record reserved in AAFILE on position 0x0006:
Name = SUB1
06 91 06=INAA, 91=AADDRC
0002 is a record pointer...
01 ... in AR5FIL
• Record in AVFILE on position 0x0019:
Subrec on position 8 first digit is 8
Pointer type is 03  next AVFILE
record
Digit counter = 1  1 more digit
• Record in AVFILE on position 0x001A:

Subrec on position 0 next digit is 0
Pointer type is 01  pointer to
AR5FIL record, chain has ended
Digit counter = 0  end of subana

Example (execution):
• IN AA called  is there starting subanalysis?
• Yes, on AAFILE record no. 0x0006
• It analyzes AADDRC attribute
• First digit pointer to AVFILE record no. 0x0019
• Subrecord is on position 8, if incoming digit is 8, pointer of
next digit (1A) is followed
• Subrecord is on position 0, if next incoming digit is 0,
pointer of result (01) is followed
• AR5FIL record no. 0x0001 is the result which is applied to
the call finally


• Files

Architecture – the algorithm
AR5FIL
C0FANA ATBPRB AAFILE Call Control / IN
AVFILE

Architecture – the algorithm
subana := read_start_record(AAFILE, IN_Attribute_Analysis);
WHILE (subana)
{
IF ( subana.attribute_id != input.attribute_id )
RETURN UNKNOWN;
digit = read_start_digit(AVFILE, subana);
IF ( digit.digit_cntr != input.nbr_of_digits )
RETURN ERROR;
WHILE ( digit.type = AVFILE )

{
IF ( subrec_position(digit) != input.digits[i] )
RETURN DEFAULT;
i++;
get_next_digit(digit);
}
IF ( digit.type = AAFILE )
get_next_subana(subana);
}
RETURN subana.result;
• To see the exact algorithm, refer to <Call Control code>/CL0/cl0atbgx.c file

Implementation practices
• IN AA MML is handled by C0FANAGX PRB

• Moved to iSource recently
– https://svne1.access.nokiasiemensnetworks.com/isource/svnroot/pac-c0fana-e1
• Lavalamp
– http://uprresult/IN/Output/Lavalamp/status_IN_MML.html
• Saving the config given in MML is done by ATBPRBGX

• Being moved to iSource
• Reads/writes AAFILE, AVFILE, AR5FIL
– and actually all arXfiles, X=1..7, results of other attribute analyses


For Internal Use Only IN Attribute Analysis (FN1620) 1 © Nokia Siemens Networks

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

For Internal Use Only IN Attribute Analysis (FN1620) 1 © Nokia Siemens Networks

Uploaded by

Copyright:

Available Formats

FN1620

For internal use only

• Attribute Analyses basics

For internal use only

For internal use only

• Attribute Analyses (ZRQ command group)

For internal use only

• Attribute Analyses basics

For internal use only

• Inputs to be analyzed  subanalyses

• Changes on IN characteristics  results

For internal use only

For internal use only

• Inputs to be analyzed  subanalyses

For internal use only

• Operator can configure inputs and results via MML

For internal use only

• Creating an analysis chain

2. Creating continuation subanalyses

• Every analysis chain has a result

For internal use only

• Attribute Analyses basics

For internal use only

• Input values are always represented by digits

For internal use only

AAFILE (file number: 81A)

For internal use only

AVFILE (file number: 829)

AR5FIL (file number: 822)

For internal use only

For internal use only

• Record in AVFILE on position 0x001A:

For internal use only

For internal use only

• Attribute Analyses basics

For internal use only

C0FANA ATBPRB AAFILE Call Control / IN

For internal use only

WHILE ( digit.type = AVFILE )

• To see the exact algorithm, refer to <Call Control code>/CL0/cl0atbgx.c file

For internal use only

• IN AA MML is handled by C0FANAGX PRB

• Saving the config given in MML is done by ATBPRBGX

For internal use only

You might also like