Reference record for OID 0.4.0.819.0.3.2


parent
0.4.0.819.0.3 (managedObjectClass)
node code
2
node name
fileGeneratingLog
dot oid
0.4.0.819.0.3.2
asn1 oid
  • {itu-t(0) identified-organization(4) etsi(0) usageMeteringInformationManagement(819) informationModel(0) managedObjectClass(3) fileGeneratingLog(2)}
  • {ccitt(0) identified-organization(4) etsi(0) usageMeteringInformationManagement(819) informationModel(0) managedObjectClass(3) fileGeneratingLog(2)}
  • iri oid
  • /itu-t/identified-organization/etsi/usageMeteringInformationManagement/informationModel/managedObjectClass/fileGeneratingLog
  • /ccitt/identified-organization/etsi/usageMeteringInformationManagement/informationModel/managedObjectClass/fileGeneratingLog
  • iri by oid_info
    /ITU-T/Identified-Organization/0/819/0/3/2

    Description by oid_info

    fileGeneratingLog MANAGED OBJECT CLASS
    DERIVED FROM "Recommendation X.721 | ISO/IEC 10165-2: 1992": log;
    CHARACTERIZED BY
    fileGeneratingLogPkg PACKAGE
    BEHAVIOUR
    fileGeneratingLogBhv BEHAVIOUR
    DEFINED AS "This log is used to create files that can be exchanged using an appropriate file transfer
    protocol. The log provides the value (sequence number) for the "recordId" (field of tne UMR).
    - The action create file is used to generate the file to be exchanged. The file created consists of a
    concatenation of stripped record,; i.e. the UMRs without the log overhead (Log Record Id, Managed
    Object Class and Instance and Logging Time). The layout of the file is defined in the ASN1 module
    as UsageMeteringRecordFile. The firstRecordId and LastRecordId included in the file header and
    trailer contain the record id of the first and the last UMR stored in the file.
    - To avoid duplication of UMRs, logging of blockRecord notifications emitted by the block generating
    log should be excluded by configuration of the fileGeneratingLogs discriminator construct. Files
    may also be created due to internal trigger events. One such internal trigger is based on time of
    day. When files are created the corresponding records in the log will be deleted automatically.";;
    ACTIONS
    createFile;;;
    CONDITIONAL PACKAGES
    dailyTriggeringPackage
    PRESENT IF "if the file creation is to be triggered on a daily basis",
    fileCreationNotificationPackage
    PRESENT IF "if the file creation is triggered using the
    daily scheduling mechanism triggering method
    or an internal mechanism.";

    View at oid-info.com

    Information by oid_info

    Automatically extracted from Interim European Telecommunication Standard (I-ETS) 300 819: Functional Specification of usage metering information management on the OS/NE interface

    Current Registration Authority (recovered by parent 0.4.0)

    Anthony Wiles

    Brothers (4)

    OIDNameSub childrenSub Nodes TotalDescription
    0.4.0.819.0.3.1 usageMeteringLogRecord 0 0 usageMeteringLogRecord MANAGED OBJECT CLASS
    DERIVED FROM "Recommendation X.721 | ISO/IEC 10165-2: 1992": eventLogRecord;
    CHARAC…
    0.4.0.819.0.3.3 blockGeneratingLog 0 0 blockGeneratingLog MANAGED OBJECT CLASS
    DERIVED FROM "Recommendation X.721 | ISO/IEC 10165-2: 1992": log;
    CHARACTERIZED BY
    bloc…
    0.4.0.819.0.3.4 simpleUsageMeteringControl 0 0 simpleUsageMeteringControl MANAGED OBJECT CLASS
    DERIVED FROM "Recommendation X.742 | ISO/IEC 10164-10: 1995": usageMeteringCont…
    0.4.0.819.0.3.5 usageMeteringData 0 0 usageMeteringData MANAGED OBJECT CLASS
    DERIVED FROM "Recommendation X.721 | ISO/IEC 10165-2: 1992": top;
    CHARACTERIZED BY
    usage…