Open APIs

 View Only
Back to discussions
Expand all | Collapse all

TMF642 - Security Service and Mechanism Violation alarm types appear separated in documentation but they are in the same event type in 3GPP TS 32.11-2.

  • 1.  TMF642 - Security Service and Mechanism Violation alarm types appear separated in documentation but they are in the same event type in 3GPP TS 32.11-2.

    Posted Feb 07, 2023 11:22
    The Alarm Management User Guide presents an enumerated list of possible values for the alarmType attribute (pag.8). The documentation refers that the values are based on ITU-T X.733 8.1.1 and 3GPP TS 32.11-2. The problem is that I checked this two standards and the values securityService and mechanismViolation are presented together as the same event type ( Security Service or Mechanism Violation ):

    I don't understand why they are separated in the TM Forum documentation, does it come from other standard not mentioned?
    This is making the alarm type values mapping difficult as the alarm system i'm working with doesn't differentiate this two types either.

    Is there a possibility to use both together in one single alarm type, such as securityServiceOrMechanismViolation?
    or
    Is there another attribute value that allows to differentiate this two types?

    Thank you for your help,

    Adriano Oliveira

    ------------------------------
    Adriano Oliveira
    Altice Labs, S.A
    ------------------------------


Related Content