Scribd Logo
Importer

Bienvenue sur Scribd !

  • FNG 3.2 Dcca GTP Codes 2

    Transféré par

    jrashev
    89 vues3 pages
    The document describes how result codes from the Online Charging System (OCS) are mapped to GTP responses during bearer activation and termination. It lists the possible result codes from the OCS, and how each maps to either a "Request accepted", "User authentication failed", or "No resources available" GTP response. It also describes the termination cause codes that may be sent in a termination CCR from the Flexi NG system.

    Description originale:

    Fng 3.2 Dcca Gtp Codes 2

    Titre original

    Fng 3.2 Dcca Gtp Codes 2

    Copyright

    © © All Rights Reserved

    Formats disponibles

    PDF, TXT ou lisez en ligne sur Scribd

    Avez-vous trouvé ce document utile ?

    Ce contenu est-il inapproprié ?

    Signaler ce document
    The document describes how result codes from the Online Charging System (OCS) are mapped to GTP responses during bearer activation and termination. It lists the possible result codes from the OCS, and how each maps to either a "Request accepted", "User authentication failed", or "No resources available" GTP response. It also describes the termination cause codes that may be sent in a termination CCR from the Flexi NG system.

    Droits d'auteur :

    © All Rights Reserved
    Téléchargez comme PDF, TXT ou lisez en ligne sur Scribd
    Signaler comme contenu inapproprié
    89 vues3 pages

    FNG 3.2 Dcca GTP Codes 2

    Transféré par

    jrashev
    The document describes how result codes from the Online Charging System (OCS) are mapped to GTP responses during bearer activation and termination. It lists the possible result codes from the OCS, and how each maps to either a "Request accepted", "User authentication failed", or "No resources available" GTP response. It also describes the termination cause codes that may be sent in a termination CCR from the Flexi NG system.

    Droits d'auteur :

    © All Rights Reserved
    Téléchargez comme PDF, TXT ou lisez en ligne sur Scribd
    Signaler comme contenu inapproprié
    sur 3

    Gy application

    Diameter Credit-Control Application Interface


    Description

    6.8.4 Result code mapping to GTP responses


    The OCS can send a CCA-I response message with a result code which affects the
    bearer activation. The following responses can be sent back to the SGSN when
    receiving the answer from the OCS upon PDP context creation (CCA-I):

    No resources available
    Request accepted
    User authentication failed

    If the Always-on mode is enabled, bearer activation does not trigger CCR/CCA-I
    messages.
    Table Result codes at command level and GTP responses describes the impact of
    command level result codes to GTP responses.

    Table 17

    Result codes at command level and GTP responses

    Value (Code)

    GTP response when Failure handling prohibits


    continuation

    SUCCESS (2001)

    Request accepted

    LIMITED_SUCCESS (2002)

    Request accepted

    CMD_UNSUPPORTED (3001)

    User authentication failed

    REALM_NOT_SERVED (3003)

    User authentication failed

    DIAMETER_TOO_BUSY (3004)

    User authentication failed

    DIAMETER_LOOP_DETECTED (3005)

    User authentication failed

    REDIRECT_INDICATION (3006)

    User authentication failed

    APP_UNSUPPORTED (3007)

    User authentication failed

    INVALID_HDR_BITS (3008)

    User authentication failed

    INVALID_AVP_BITS (3009)

    User authentication failed

    UNKNOWN_PEER (3010)

    User authentication failed

    AUTHENTICATION_REJECTED (4001)

    User authentication failed

    OUT_OF_SPACE (4002)

    User authentication failed

    ELECTION_LOST (4003)

    User authentication failed

    END_USER_SERVICE_DENIED (4010)

    User authentication failed

    78

    DN0822736

    Issue: 3-6

    Diameter Credit-Control Application Interface


    Description

    Table 17

    Gy application

    Result codes at command level and GTP responses (Cont.)

    Value (Code)

    GTP response when Failure handling prohibits


    continuation

    CREDIT_CONTROL_NOT_APPLICABLE (4011)

    User authentication failed

    CREDIT_LIMIT_REACHED (4012)

    User authentication failed

    AVP_UNSUPPORTED (5001)

    User authentication failed

    UNKNOWN_SESSION_ID (5002)

    User authentication failed

    AUTH_REJECTED (5003)

    User authentication failed

    INVALID_AVP_VALUE (5004)

    User authentication failed

    MISSING_AVP (5005)

    User authentication failed

    RESOURCES_EXCEEDED (5006)

    No resources available

    CONTRADICTING_AVPS (5007)

    User authentication failed

    AVP_NOT_ALLOWED (5008)

    User authentication failed

    TOO_MANY_TIMES (5009)

    User authentication failed

    NO_COMMON_APPLICATION (5010)

    User authentication failed

    UNSUPPORTER_VERSION (5011)

    User authentication failed

    UNABLE_TO_COMPLY (5012)

    User authentication failed

    INVALID_BIT_IN_HEADER (5013)

    User authentication failed

    INVALID_AVP_LENGTH (5014)

    User authentication failed

    INVALID_MESSAGE_LENGTH (5015)

    User authentication failed

    INVALID_AVP_BIT_COMBO (5016)

    User authentication failed

    NO_COMMON_SECURITY (5017)

    User authentication failed

    USER_UNKNOWN (5030)

    User authentication failed

    RATING_FAILED (5031)

    User authentication failed

    BEARER_NOT_AUTHORIZED (5143)

    User authentication failed

    Issue: 3-6

    DN0822736

    79

    Gy application

    Diameter Credit-Control Application Interface


    Description

    GTP response when Failure handling allows continuation


    If failure handling CONTINUE is selected, according to the state machine in RFC 4006,
    permanent errors allow the bearer to be created with response Request accepted. GTP
    response User authentication failed is applicable only to result codes 4010, 4012, 5003
    and 5031. In all other cases, the response is Request accepted.

    6.9 Termination cause codes with Gy


    A termination CCR sent by Flexi NG contains one of the cause codes listed in Table
    Termination cause codes sent by Flexi NG. Flexi NG does not send other termination
    cause codes.
    Table 18

    Termination cause codes sent by Flexi NG

    Value (Code)

    Meaning

    ADMINISTRATIVE (4)

    This termination cause code is used when Flexi NG meets the following conditions:

    OCS terminates the bearer by sending the result code


    CREDIT_LIMIT_REACHED (4012) in CCA at command level.
    A received CCA update contains the result code AUTHORIZATION_REJECTED
    (5003) at command level.
    Flexi NG sends a Delete Bearer Request message if a Diameter RAR including
    the Session-Release-Cause (1045) AVP is received from the PCRF.
    Flexi NG sends a Delete Bearer Request message if the PCRF is unreachable
    and no Gx failover takes place.

    BAD_ANSWER (3)

    This termination code is used whenever the OCS returns an unknown AVP or an
    unexpected result code.

    LOGOUT (1)

    This is the default cause code. It is used if the reason for closing the DCCA session
    is none of the reasons listed above.

    80

    DN0822736

    Issue: 3-6

    Vous aimerez peut-être aussi