Version

number

Yes

Version of the event header. See the VES Event Specification for the correct digits to use.

eventName

string

Yes

The Event name that uniquely identifies the CPE Authentication event across vendor implementations.

StateChange_cpe_authentication

domain

string

Yes

stateChange

eventId

string

Yes

Event key that is unique to the event source

cpe_authentication_yyyyyyyy where yyyyyyyy is an integer starting at 0 and incremented by 1 for every CPE Authentication event sent by this CPE.

The key must be unique within notification 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

applicationNf

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  

From DHCP option 60 we get <Service-Provider-ID>,<Service-ID>,<Device-ID>,<Vendor Name>,<MAC OUI>,<Model>,<running firmware version>,<Serial number>

<PNF-name/PNF correlation ID>: Format string: <MAC OUI>_<Model>_<SerialNumber>, e.g. AB-CD-12_ABC1-01-02_2.6G1724F0417413

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.

<thirdparty-sdnc-id> from esr request

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

vesEventListenerVersion

string

Yes

Version of the VES event listener API Spec that this event is compliant with (As "#" or "#.#" or "#.#.#" where # is a digit.

timeZoneOffset

string

No

Offset to GMT to indicate local time zone for device formatted as 'UTC+/-hh.mm'; see https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations for UTC offset examples

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.

newState

string

Yes

New state of the entity: ‘inService’, ‘maintenance’, ‘outOfService’

(Authenticated = inService, Unauthenticated = outOfService)

oldState

string

Yes

Previous state of the entity: ‘inService’, ‘maintenance’, ‘outOfService’

(Authenticated = inService, Unauthenticated = outOfService)

stateInterface

string

Yes

Card or port name of the entity that changed state

Empty. Not used

additionalFields

hashMap

No

Additional syslog fields: {“name1”: ”value1”, “name2”: ”value2”}

macAddress (MAC Address of the RG for the PNF)

swVersion (Sw version from the DHCP option 60) (Optional)