decode_3gpp_access_network_info

This section includes the following information:

• Access-Network-Information Fields
• Message Types
• Access Type Concatenation
• Access Class Concatenation
• Access Type Parts
• Total Digits
• Keywords and Field Names
• Parsing Configuration

Access-Network-Information AVP Fields lists the Access-Network-Information fields for decode_3gpp_access_network_info decoding. The fields are set if they are listed.

The message types include:

• 3GPP2
• 3GPP2-1X
• 3GPP2-1X-Femto
• 3GPP2-1X-HRPD
• 3GPP2-UMB
• 3GPP-E-UTRAN
• 3GPP-E-UTRAN-FDD
• 3GPP-E-UTRAN-ProSe-UNR
• 3GPP-E-UTRAN-TDD
• 3GPP-GAN
• 3GPP-GERAN
• 3GPP-HSPA
• 3GPP-NR
• 3GPP-NR-FDD
• 3GPP-NR-TDD
• 3GPP-UTRAN
• 3GPP-UTRAN-FDD
• 3GPP-UTRAN-TDD
• 3GPP-WLAN
• ADSL
• ADSL2
• ADSL2+
• DOCSIS
• DVB-RCS2
• GPON
• G.SHDSL
• GSTN
• HDSL
• HDSL2
• IDSL
• IEEE-802.11
• IEEE-802.11a
• IEEE-802.11b
• IEEE-802.11g
• IEEE-802.11n
• IEEE-802.3
• IEEE-802.3a
• IEEE-802.3ab
• IEEE-802.3ae
• IEEE-802.3ah
• IEEE-802.3ak
• IEEE-802.3an
• IEEE-802.3aq
• IEEE-802.3e
• IEEE-802.3i
• IEEE-802.3j
• IEEE-802.3u
• IEEE-802.3y
• IEEE-802.3z
• RADSL
• SDSL
• untrusted-non-3GPP-VIRTUAL-EPC
• VDSL
• VIRTUAL-no-PS
• WLAN-no-PS
• xDSL
• XGPON1

If the string is 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=3114809000002583e;network-provided, then:

• The message type is 3GPP-E-UTRAN-FDD.
• The keyword utran-cell-id-3gpp has a value 3114809000002583e.
• The keyword network-provided does not have a value.

Example Field Results lists the results for the example BLOB, 3GPP-E-UTRAN-FDD;utran-cell-id-3gpp=3114809000002583e.

The code looks for the specified parameter name based upon the access type and decodes its value. The format of the parameter name values is defined in 3GPP TS 24.229 and differs based upon the access-type / access-class field. Access Type Concatenation describes how concatenation is determined according to the access-type.

Access Class Concatenation describes how concatenation is determined according to the access-class.

Access Type Parts describes the parts concatenated in Access Type Concatenation and Access Class Concatenation. Each part in a concatenation has 1 or 2 possible number of digits. For example, MCC has 3 decimal digits and MNC has 2 or 3 decimal digits.

Depending on which parts are in a concatenation and their number of digits, an access type can have multiple possible total digits. For example, 3GPP-NR-FDD Concatenation Total Digits Example shows some possible total digit values for the concatenation of 3GPP-NR-FDD.

Keywords and Field Names lists the defined keywords and their associated fields.

You can add and delete keywords and add, delete, and modify the message types with create_config.py. Answer y to the following question and then answer the remaining questions:

SelectiveUpdate:Parser:3gppAccessNetworkInfo:Do you want to modify this parser (y/n)?y 

For example:

SelectiveUpdate:Parser:3gppAccessNetworkInfo:Do you want to modify this parser (y/n)?y
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Do you want to allow a missing cell ID (y/n)?y
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Do you want to ignore parsing errors (y/n)?y
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Do you want to ignore unknown message types and keywords (y/n)?y
SelectiveUpdate:Parser:3gppAccessNetworkInfo:What message types do you want to delete?3GPP2-1X-Femto;3GPP-GAN
SelectiveUpdate:Parser:3gppAccessNetworkInfo:What message types do you want to modify?common;3GPP-E-UTRAN
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Modify:common:What keywords do you want to delete?dsl-location
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Modify:common:What keywords and their field name suffixes do you want to add?man,Man;woman,Woman
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Modify:3GPP-E-UTRAN:What keywords do you want to delete?
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Modify:3GPP-E-UTRAN:What keywords and their field name suffixes do you want to add?dog,Dog;cat,Cat
SelectiveUpdate:Parser:3gppAccessNetworkInfo:What message types do you want to add?5GPP;6GPP
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Add:5GPP:What existing message type do you want copy?common
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Add:5GPP:What keywords and their field name suffixes do you want to add?mouse,Mouse;snake,Snake
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Add:6GPP:What existing message type do you want copy?common
SelectiveUpdate:Parser:3gppAccessNetworkInfo:Add:6GPP:What keywords and their field name suffixes do you want to add?lion,Lion;tiger,Tiger 

For example, to add the keyword daylight-saving-time as a STRING, configure the selective update as follows:

SelectiveUpdate:Parser:3gppAccessNetworkInfo:Modify:3GPP-E-UTRAN:What keywords and their field name suffixes do you want to add?daylight-saving-time,Extra1AsString

When you add a new keyword,fieldname, the selective update parser looks for AccessNetworkFieldName in the MDC to store the field value. The MtxDiamAccessNetworkData MDC has the following spare fields that you can use when adding keywords:

DataContainer::set: Field is already set. Multiple sets are not allowed. Descriptor=<MDC>, Field key=<Key>

You can configure MATRIXX to accept a message with an empty cell ID by answering y to the following questions:

• SelectiveUpdate:Parser:3gppAccessNetworkInfo:Do you want to modify this parser (y/n)?y 

• SelectiveUpdate:Parser:3gppAccessNetworkInfo:Do you want to allow a missing cell ID (y/n)?y

If the inbound message into Diameter Gateway has a message type that is unknown or a keyword within a type that is unknown, the gateway returns an error. Answer y to the following question to ignore unrecognized types or keywords.

SelectiveUpdate:Parser:3gppAccessNetworkInfo:Do you want to ignore unknown message types and keywords (y/n)?

To ignore all Diameter Gateway parsing errors, answer y to the following question:

SelectiveUpdate:Parser:3gppAccessNetworkInfo:Do you want to ignore parsing errors (y/n)?

MdcSelectiveUpdateParser::setFieldKeys: Unable to create a field key for <prefix><suffix>. Passed field name=<prefix>Info, expected suffix=Info, replacing suffix=<suffix>. MDC Descriptor name=<MDC>

Output fields must be on the same hierarchical level. For example:

Container:
    <prefix>Info
    <prefix>InfoAsString
    <prefix>Type
    ... 
    <prefix>NewField

You cannot decode into an extended NewField such as this:

Container:
    <prefix>NewField
Base Container:
    <prefix>Info
    <prefix>InfoAsString
    <prefix>Type
    ...