Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The CPE Authentication Event is defined here in VES StateChange domain.  It indicates if the ONT/CPE is successfully authenticated at the Edge after the ONT/CPE relocation is completed. 

Example in VES Fault domain

Following is the example CPE Authentication event and schema if this event is defined in  VES Fault domain.

Code Block
languagetext
firstline1
titleCPE Authentication Event
linenumberstrue
collapsetrue
{
    "event": {
        "commonEventHeader": {
            "sourceId": "Gateway/sn=83575443FA637D1A", // from 'traget' field
            "startEpochMicrosec": 1413378172000000,
            "eventId": "ab305d54-85b4-a31b-7db2-fb6b977766",
            "sequence": 0,
            "domain": "fault",
            "lastEpochMicrosec": 1413378172000033,
            "eventName": "Fault_CPE_AUTH_Status",
            "sourceName": ""Gateway/sn=83575443FA637D1A", // 'Target' from the restconf notification.
            "priority": "High",
            "version": 3.0,
            "reportingEntityName": "Domain_Contorller"
        },
        "faultFields": {
            "eventSeverity": "CRITICAL",
            "alarmCondition": "Route_Status",
            "faultFieldsVersion": 2.0,
            "specificProblem": "Fault_RG_Status",
            "alarmAdditionalInformation": [
                {
                "name": "gatewaySN",                   
                "value": "83575443FA637D1A"              
                },
                {
                "name": "mac",                   
                "value": "28-6E-D4-89-34-DD"               
                },              
                {
                "name": "ip",                   
                "value": "10.68.52.158"              
                },
                {
                "name": "state",
                "value": "OnLine"
                },
                {
                "name": "ontSN",
                "value": "48575443FA637D1A"
                }
            ]
            "eventSourceType": "other",
            "vfStatus": "Active"
        }
    }
}

Following is the schema of the CPE_Authentication VES event (WIP).

...

Version

...

number

...

Yes

...

Version of the event header (currently: 3.0): 3.0

...

eventName

...

string

...

Yes

...

rgActivation_vendor_pnfName where pnfName is specified by the vendor and is a PNF type; e.g. rgActivation_Huawei_xxxx

...

domain

...

string

...

Yes

...

Event domain enumeration: ‘fault’, ‘heartbeat’, ‘measurementsForVfScaling’, ‘mobileFlow’, ‘other’, ‘sipSignaling’, ‘stateChange’, ‘syslog’, ‘thresholdCrossingAlert’, ‘voiceQuality’, ‘pnfRegistration’

...

eventId

...

string

...

Yes

...

Event key that is unique to the event source

activate_yyyyyyyy where yyyyyyyy is an integer starting at 0 and incremented by 1 for every cpeAuthentication event sent by this ONT/RG.

The key must be unique within notificaiton life cycle similar to EventID from 3GPP. It could be a sequential number, or a composite key formed from the event fields, such as domain_sequence. The eventId should not include whitespace.

...

eventType

...

string

...

No

...

rgActivation

...

sourceId

...

string

...

No

...

UUID identifying the entity experiencing the event issue (note: the AT&T internal enrichment process shall ensure that this field is populated) Not used

...

sourceName

...

string

...

Yes

...

Name of the entity experiencing the event issue  

PNF-name (unique PNF correlation ID = pnf-name stored in AAI ; e.g. NOK6061ZW3)

...

reportingEntityId

...

string

...

No

...

UUID identifying the entity reporting the event, for example an OAM VM (note: the AT&T internal enrichment process shall ensure that this field is populated) Not used

...

reportingEntityName

...

string

...

Yes

...

Name of the entity reporting the event, for example, an EMS name.  May be the same as the sourceName.  For synthetic events generated by DCAE, it is the name of the app generating the event.

PNF-name (unique PNF correlation ID = pnf-name stored in AAI ; e.g. NOK6061ZW3)

...

priority

...

string

...

Yes

...

Processing priority enumeration: ‘High’, ‘Medium’, ‘Normal’, ‘Low’

Normal

...

startEpochMicrosec

...

number

...

Yes

...

the earliest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds

current time

...

lastEpochMicrosec

...

number

...

Yes

...

the latest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds

current time

...

sequence

...

integer

...

Yes

...

Ordering of events communicated by an event source instance (or 0 if not needed)

0

...

internalHeader Fields

...

Internal Header Fields

...

No

...

Fields (not supplied by event sources) that the VES Event Listener service can use to enrich the event if needed for efficient internal processing.  This is an empty object which is intended to be defined separately by each provider implementing the VES Event Listener.

Empty. Not used

...

stateChange FieldsVersion

...

number

...

Yes

...

Version of the stateChangeFields block as "#.#", where # is a digit (currently: 1.0). See the VES Event Specification for the correct digits to use.

...

serialNumber

...

string

...

Yes

...

TS 32.692 serialNumber = serial number of the unit; e.g. 6061ZW3

...

vendorName

...

string

...

Yes

...

TS 32.692 vendorName = name of manufacturer; e.g. Nokia.  Maps to AAI equip-vendor.

...

macAddress

...

string

...

Yes

...

MAC address of OAM interface of the unit.

...

softwareVersion

...

string

...

No

...

TS 32.692 swName = active SW running on the unit; e.g. 5gDUv18.05.201.

...

manufactureDate

...

string

...

No

...

TS 32.692 dateOfManufacture = manufacture date of the unit in ISO 8601 format; 2016-04-23.

...

lastServiceDate

...

string

...

No

...

TS 32.692 dateOfLastService = date of last service in ISO 8601 format; e.g. 2017-02-15.

...

additionalFields

...

hashMap

...

No

...

Additional registration fields if needed, provided as key-value pairs.

Policy

Apex Engine Triggering

...