Diameter

Ten przewodnik pełni rolę deklaracji zgodności implementacji protokołu Diameter.
Kategoria:

Tematy w tym dokumencie:

Podstawowy protokół Diameter

Ta podsekcja opisuje, jak AAA Gateway mapuje komunikaty dla Diameter Base Protocol zdefiniowanego w RFC-3588.

Zgodność sekcji

Tabela 1-1 zawiera informacje o zgodności sekcji protokołu Diameter Base.

Tabela 1-1: Zgodność sekcji Diameter Base Protocol

Numer sekcjiSekcjaStatusUwagi
1WprowadzenieNie dotyczy-
1.1Diameter ProtocolNie dotyczy-
1.1.1Description of the document setNie dotyczy-
1.2Approach to extensibilityNie dotyczy-
1.2.1Defining new attribute-value pairsNie dotyczy-
1.2.2Creating new AVPsNie dotyczy-
1.2.3Creating new authentication appsNie dotyczy-
1.2.4Creating new accounting appsNie dotyczy-
1.2.5Application authenticationNie dotyczy-
1.3TerminologyNie dotyczy-
2Protocol overviewNie dotyczy-
2.1TransportObsługiwaneObsługuje TCP i SCTP
2.1.1SCTP guidelinesObsługiwane-
2.2Securing diameter messagesNieobsługiwane-
2.3Diameter application complianceObsługiwane-
2.4Application identifiersObsługiwane-
2.5Connections vs SessionsBrak wymagań-
2.6Peer tableObsługiwane-
2.7Realm-based routing tableNie dotyczy-
2.8Rola agentów DiameterNie dotyczy-
2.8.1Relay agentsNie dotyczy-
2.8.2Proxy agentsNie dotyczy-
2.8.3Redirect agentsNie dotyczy-
2.8.4Translation agentsNie dotyczy-
2.9End-to-end security frameworkNieobsługiwane-
2.10Diameter path authorizationNieobsługiwane-
3Diameter headerObsługiwane-
3.1Kody poleceńObsługiwane-
3.2Command code ABNF specificationBrak wymagań-
3.3Diameter command naming conventionsObsługiwane-
4Diameter AVPsObsługiwane-
4.1AVP headerObsługiwane-
4.1.1Opcjonalne elementy nagłówkaObsługiwane-
4.2Basic AVPObsługiwane-
4.3Derived AVP data formatsObsługiwane-
4.4Grouped AVP valuesObsługiwane-
4.4.1Example AVP with grouped data typeBrak wymagań-
4.5Diameter base protocol AVPsObsługiwane-
5Diameter peersBrak wymagań-
5.1Peer connectionsObsługiwane-
5.2Diameter peer discoveryNieobsługiwaneDiameter Gateway nie obsługuje routingu, proxy ani relay
5.3Capabilities exchangeObsługiwane-
5.3.1Capabilities-Exchange-RequestObsługiwane-
5.3.2Capabilities-Exchange-AnswerObsługiwane-
5.3.3Vendor-Id AVPObsługiwane-
5.3.4Firmware-Revision AVPObsługiwane-
5.3.5Host-IP-Address AVPNieobsługiwane-
5.3.6Supported-Vendor-Id AVPObsługiwane-
5.3.7Product-Name AVPObsługiwane-
5.4Disconnecting peer connectionsCzęściowo obsługiwaneDiameter Gateway tylko odpowiada na komunikaty, nie generuje ich
5.4.1Disconnect-Peer-RequestCzęściowo obsługiwaneDiameter Gateway tylko odpowiada na komunikaty, nie generuje ich
5.4.2Disconnect-Peer-AnswerCzęściowo obsługiwaneDiameter Gateway tylko odpowiada na komunikaty, nie generuje ich
5.4.3Disconnect-Cause AVPCzęściowo obsługiwaneDiameter Gateway tylko odpowiada na komunikaty, nie generuje ich
5.5Transport failure detectionObsługiwane-
5.5.1Device-Watchdog-RequestObsługiwane-
5.5.2Device-Watchdog-AnswerObsługiwane-
5.5.3Transport failure algorithmObsługiwane-
5.5.4Failover and failback proceduresCzęściowo obsługiwane-
5.6Peer state machineObsługiwane-
5.6.1Incoming connectionsObsługiwane-
5.6.2EventsObsługiwane-
5.6.3ActionsObsługiwane-
5.6.4Proces wyboruObsługiwane-
6Diameter message processingBrak wymagań-
6.1Diameter żądanie routing overviewBrak wymagań-
6.1.1Originating a żądanieObsługiwane-
6.1.2Sending a żądanieObsługiwane-
6.1.3Receiving requestsObsługiwane-
6.1.4Processing local requestsNieobsługiwane-
6.1.5Request forwardingNieobsługiwane-
6.1.6Request routingNie dotyczy-
6.1.7Redirecting requestsNie dotyczy-
6.1.8Relaying and proxying requestsNie dotyczy-
6.2Diameter answer processingObsługiwane-
6.2.1Processing received answersObsługiwane-
6.2.2Relaying and proxying answersNie dotyczyConfigurable per Diameter Gateway instance
6.3Origin-Host AVPObsługiwaneConfigurable per Diameter Gateway instance
6.4Origin-Realm AVPObsługiwane-
6.5Destination-Host AVPObsługiwane-
6.6Destination-Realm AVPObsługiwane-
6.7Routing AVPsNie dotyczy-
6.7.1Route-Record AVPNie dotyczy-
6.7.2Proxy-Info AVPNie dotyczy-
6.7.3Proxy-Host AVPNie dotyczy-
6.7.4Proxy-State AVPNie dotyczy-
6.8Auth-Application-Id AVPObsługiwane-
6.9Acct-Application-Id AVPNie dotyczy-
6.10Inband-Security-Id AVPObsługiwaneSupports only 0, where 0 specifies NO_INBAND_SECURITY
6.11Vendor-Specific-Application-Id AVPObsługiwane-
6.12Redirect-Host AVPNie dotyczy-
6.13Redirect-Host-Usage AVPNie dotyczy-
6.14Redirect-Max-Cache-Time AVPNie dotyczy-
6.15E2E-Sequence AVPNie dotyczy-
7Support błędówObsługiwane-
7.1Result-Code AVPObsługiwane-
7.1.1InformacyjneObsługiwane-
7.1.2SuccessObsługiwane-
7.1.3Protocol errorsObsługiwane-
7.1.4Transient FailuresObsługiwane-
7.1.5Permanent FailuresObsługiwane-
7.2Error bitObsługiwane-
7.3Error-Message AVPNieobsługiwane-
7.4Error-Reporting-Host AVPNieobsługiwane-
7.5Failed-AVP AVPObsługiwane-
7.6Experimental-Result AVPObsługiwane-
7.7Experimental-Result-Code AVPObsługiwane-
8Diameter użytkownik sessionsBrak wymagań-
8.1Authorization session state machineObsługiwane-
8.2Accounting session state machineNie dotyczy-
8.3Server-Initiated Re-AuthObsługiwane-
8.3.1Re-Auth-RequestObsługiwane-
8.3.2Re-Auth-AnswerObsługiwane-
8.4Session terminationObsługiwane-
8.4.1Session-Termination-RequestObsługiwane-
8.4.2Session-Termination-AnswerObsługiwane-
8.5Aborting a sessionNieobsługiwane-
8.5.1Abort-Session-RequestNieobsługiwane-
8.5.2Abort-Session-AnswerNieobsługiwane-
8.6Inferring session termination from Origin-State-IdNieobsługiwane-
8.7Auth-Request-Type AVPNie dotyczy-
8.8Session-Id AVPObsługiwane-
8.9Authorization-Lifetime AVPNie dotyczy-
8.10Auth-Grace-Period AVPNie dotyczy-
8.11Auth-Session-State AVPNie dotyczy-
8.12Re-Auth-Request-Type AVPNie dotyczy-
8.13Session-Timeout AVPNie dotyczy-
8.14User-Name AVPNie dotyczy-
8.15Termination-Cause AVPObsługiwane-
8.16Origin-State-Id AVPNieobsługiwane-
8.17Session-Binding AVPNie dotyczy-
8.18Session-Server-Failover AVPNie dotyczy-
8.19Multi-Round-Time-Out AVPNie dotyczy-
8.20Class AVPNie dotyczy-
8.21Event-Timestamp AVPObsługiwane-
9AccountingNie dotyczy-
9.1Server directed modelNie dotyczy-
9.2Protocol messagesNie dotyczy-
9.3Application document requirementsNie dotyczy-
9.4Fault resilienceNie dotyczy-
9.5Accounting recordsNie dotyczy-
9.6Correlation of accounting recordsNie dotyczy-
9.7Accounting Command-CodesNie dotyczy-
9.7.1Accounting-RequestNie dotyczy-
9.7.2Accounting-AnswerNie dotyczy-
9.8Accounting AVPsNie dotyczy-
9.8.1Accounting-Record-Type AVPNie dotyczy-
9.8.2Acct-Interim-Interval AVPNie dotyczy-
9.8.3Accounting-Record-Number AVPNie dotyczy-
9.8.4Acct-Session-Id AVPNie dotyczy-
9.8.5Acct-Multi-Session-Id AVPNie dotyczy-
9.8.6Accounting-Sub-Session-Id AVPNie dotyczy-
9.8.7Accounting-Realtime-Required AVPNie dotyczy-
10AVP occurrence tableBrak wymagań-
10.1Base protocol command AVP TableBrak wymagań-
10.2Accounting AVP TableBrak wymagań-
11IANA ConsiderationsBrak wymagań-
11.1AVP headerBrak wymagań-
11.1.1AVP codeBrak wymagań-
11.1.2AVP flagsBrak wymagań-
11.2Diameter headerBrak wymagań-
11.2.1Kody poleceńBrak wymagań-
11.2.2Command FlagsBrak wymagań-
11.3Application identifiersBrak wymagań-
11.4AVP ValuesBrak wymagań-
11.4.1Result-Code AVP ValuesBrak wymagań-
11.4.2Accounting-Record-Type AVP ValuesBrak wymagań-
11.4.3Termination-Cause AVP ValuesBrak wymagań-
11.4.4Redirect-Host-Usage AVP ValuesBrak wymagań-
11.4.5Session-Server-Failover AVP ValuesBrak wymagań-
11.4.6Session-Binding AVP ValuesBrak wymagań-
11.4.7Disconnect-Cause AVP ValuesBrak wymagań-
11.4.8Auth-Request-Type AVP ValuesBrak wymagań-
11.4.9Auth-Session-State AVP ValuesBrak wymagań-
11.4.10Re-Auth-Request-Type AVP ValuesBrak wymagań-
11.4.11Accounting-Realtime-Required AVP ValuesBrak wymagań-
11.5Diameter TCP/SCTP port numbersBrak wymagań-
11.6Naming authority pointer (NAPTR) Service FieldsBrak wymagań-
12Diameter Protocol Related Configurable ParametersObsługiwane-
13Security considerationsNieobsługiwane-
13.1IPsec usageNieobsługiwane-
13.2TLS usageNieobsługiwane-
13.3Peer-to-Peer ConsiderationsNieobsługiwane-
14ReferencesBrak wymagań-
14.1Normative ReferencesBrak wymagań-
14.2Informative ReferencesBrak wymagań-
15AcknowledgementsBrak wymagań-
Appendix ADiameter usługa templateBrak wymagań-
Appendix BNAPTR exampleBrak wymagań-
Appendix CDuplicate detectionObsługiwane-

Protokół Diameter Gy

Ten rozdział opisuje, jak AAA Gateway mapuje komunikaty Diameter dla protokołu Diameter Gy zdefiniowanego w 3GPP TS 32.299 Version 12.0. Więcej informacji znajdziesz w szczegółach specyfikacji 3GPP:

http://www.3gpp.org/ftp/Specs/html-info/32299.htm

Zgodność sekcji

Tabela 2-1 zawiera informacje o zgodności dla sekcji protokołu Diameter Gy.

Tabela 2-1: Diameter Gy Zgodność sekcji

Numer sekcjiSekcjaStatusUwagi
1ScopeNie dotyczy-
2ReferencesNie dotyczy-
3Definitions, symbols and abbreviationsNie dotyczy-
3.1DefinitionsNie dotyczy-
3.2SymbolsNie dotyczy-
3.3AbbreviationsNie dotyczy-
4Architecture considerationsObsługiwane-
4.1High level architectureObsługiwane-
4.1.0Informacje ogólneObsługiwane-
4.1.1Charging related transfer requirementsObsługiwane-
53GPP charging applications requirementsObsługiwane-
5.1Offline charging scenariosObsługiwane-
5.1.1Basic principlesObsługiwane-
5.1.1.0WprowadzenieObsługiwane-
5.1.1.1Event based chargingObsługiwane-
5.1.1.2Session based chargingObsługiwane-
5.1.2Basic operacjaObsługiwane-
5.2Online charging scenariosObsługiwane-
5.2.0WprowadzenieObsługiwane-
5.2.1Basic principlesObsługiwane-
5.2.2Charging scenariosObsługiwane-
5.2.2.0WprowadzenieObsługiwane-
5.2.2.1Immediate event charging (IEC)Obsługiwane-
5.2.2.1.1Decentralized unit determination and centralized ratingNieobsługiwane-
5.2.2.1.2Centralized unit determination and centralized ratingObsługiwane-
5.2.2.1.3Decentralized unit determination and decentralized ratingNieobsługiwane-
5.2.2.1.4Further optionsObsługiwane-
5.2.2.2Event charging with unit reservation (ECUR)Obsługiwane-
5.2.2.2.1Decentralized unit determination and centralized ratingNieobsługiwane-
5.2.2.2.2Centralized unit determination and centralized ratingObsługiwane-
5.2.2.2.3Decentralized unit determination and decentralized ratingNieobsługiwane-
5.2.2.3Session charging with reservationObsługiwane-
5.2.2.3.1Decentralized unit determination and centralized ratingNieobsługiwane-
5.2.2.3.2Centralized unit determination and centralized ratingObsługiwane-
5.2.2.3.3Decentralized unit determination and decentralized ratingNieobsługiwane-
5.2.3Basic operationsObsługiwane-
5.3Other requirementsObsługiwane-
5.3.1Re-authorizationObsługiwane-
5.3.2Threshold based re-authorization triggersObsługiwane-
5.3.3Termination actionObsługiwane-
5.3.4Konto expirationNieobsługiwane-
63GPP charging applications – protocol aspectsObsługiwane-
6.1Basic principles for diameter offline chargingObsługiwane-
6.1.0WprowadzenieObsługiwane-
6.1.1Event based chargingObsługiwane-
6.1.2Session based chargingObsługiwane-
6.1.3Offline charging error cases - diameter proceduresObsługiwane-
6.1.3.1Charging data function (CDF) connection failureObsługiwane-
6.1.3.2No reply from CDFObsługiwane-
6.1.3.3Duplicate detectionObsługiwane-
6.1.3.4CDF detected failureObsługiwane-
6.2Message contents for offline chargingNieobsługiwane-
6.2.1Podsumowanie of offline charging message formatsNieobsługiwane-
6.2.1.1Informacje ogólneNieobsługiwane-
6.2.1.2Structure for the accounting message formatsNieobsługiwane-
6.2.2Accounting-Request messageNieobsługiwane-
6.2.3Accounting-Answer (ACA) messageNieobsługiwane-
6.3Basic principles for diameter online chargingObsługiwane-
6.3.1Online specific Credit-Control application requirementsObsługiwane-
6.3.2Diameter description on the Ro reference pointObsługiwane-
6.3.2.1Basic principlesObsługiwane-
6.3.3Immediate event charging (IEC)Obsługiwane-
6.3.4Event charging with unit reservation (ECUR)Obsługiwane-
6.3.5Session charging with unit reservation (SCUR)Obsługiwane-
6.3.6Error cases and scenariosObsługiwane-
6.3.6.0WprowadzenieObsługiwane-
6.3.6.1Duplicate detectionObsługiwane-
6.3.6.2Reserve units/Debit units operation failureObsługiwane-
6.3.7Support of tariff changes during an active user sessionObsługiwane-
6.3.7.1Support of tariff changes using the tariff switch mechanismObsługiwane-
6.3.7.2Support of tariff changes using Validity-Time attribute-value pair (AVP)Nieobsługiwane-
6.3.8Support of re-authorizationObsługiwane-
6.3.9Support of failure supportObsługiwane-
6.3.10Support of failoverObsługiwane-
6.3.11Credit poolingNieobsługiwane-
6.4Message formats for online chargingObsługiwane-
6.4.1Podsumowanie of online charging message formatsObsługiwane-
6.4.1.1Informacje ogólneObsługiwane-
6.4.1.2Structure for the Credit-Control message formatsObsługiwane-
6.4.2Credit-Control-Request messageObsługiwane-
6.4.3Credit-Control-Answer messageObsługiwane-
6.4.4Re-Auth-Request messageObsługiwane-
6.4.5Re-Auth-Answer messageObsługiwane-
6.4.6Capabilities-Exchange-Request-messageObsługiwane-
6.4.7Capabilities-Exchange-Answer messageObsługiwane-
6.4.8Device-Watchdog-Request messageObsługiwane-
6.4.9Device-Watchdog-Answer messageObsługiwane-
6.4.10Disconnect-Peer-Request messageCzęściowo obsługiwane-
6.4.11Disconnect-Peer-Answer messageCzęściowo obsługiwane-
6.4.12Abort-Session-Request messageNieobsługiwane-
6.4.13Abort-Session-Answer messageNieobsługiwane-
6.5Other procedural description of the 3GPP charging applicationsObsługiwane-
6.5.1Re-AuthorizationObsługiwane-
6.5.1.1Idle timeoutObsługiwane-
6.5.1.2Change of charging conditionsNieobsługiwane-
6.5.1.3Reporting quota usageNieobsługiwane-
6.5.1.4Quota consumptionNieobsługiwane-
6.5.2Threshold based Re-Authorization triggersObsługiwane-
6.5.3Termination actionObsługiwane-
6.5.4Quota consumption timeObsługiwane-
6.5.5Service terminationNieobsługiwane-
6.5.6Envelope reportingNieobsługiwane-
6.5.7Combinational quotaNieobsługiwane-
6.5.8Online control of offline charging informationObsługiwane-
6.5.9Support of multiple usługaObsługiwane-
6.6Bindings of the operation to protocol applicationObsługiwane-
6.6.0Informacje ogólneObsługiwane-
6.6.1Bindings of charging data transfer to accountingObsługiwane-
6.6.2Bindings of debit/reserve units to Credit-ControlObsługiwane-
7Summary of used attribute-value pairs (AVPs)Nie dotyczy-
7.1Diameter attribute-value pairs (AVPs)Nie dotyczy-
7.1.0Informacje ogólneNie dotyczy-
7.1.1Accounting-Input-Octets AVPNieobsługiwane-
7.1.2VoidNie dotyczy-
7.1.3Accounting-Output-Octets AVPNieobsługiwane-
7.1.4VoidNie dotyczy-
7.1.5Acct-Application-Id AVPObsługiwane-
7.1.6Auth-Application-Id AVPObsługiwane-
7.1.7Called-Station-Id AVPObsługiwane-
7.1.8Event-Timestamp AVPObsługiwane-
7.1.9Multiple-Services-Credit-Control AVPObsługiwane-
7.1.10Rating-Group AVPObsługiwane-
7.1.11Result-Code AVPObsługiwane-
7.1.12Service-Context-Id AVPObsługiwane-
7.1.13Service-Identifier AVPObsługiwane-
7.1.14Used-Service-Unit AVPObsługiwane-
7.1.15User-Name AVPObsługiwane-
7.1.16Vendor-Id AVPObsługiwane-
7.1.17User-Equipment-Info AVPObsługiwane-
7.23GPP specific AVPsNieobsługiwane-
7.2.0Informacje ogólneNieobsługiwane-
7.2.1Access-Network-Information AVPNieobsługiwane-
7.2.1AAccess-Transfer-Information AVPNieobsługiwane-
7.2.1BAccess-Transfer-Type AVPNieobsługiwane-
7.2.2Account-Expiration AVPNieobsługiwane-
7.2.3Accumulated-Cost AVPNieobsługiwane-
7.2.4Adaptations AVPNieobsługiwane-
7.2.5Additional-Content-Information AVPNieobsługiwane-
7.2.6Additional-Type-Information AVPNieobsługiwane-
7.2.7Address-Data AVPNieobsługiwane-
7.2.8Address-Domain AVPNieobsługiwane-
7.2.9Address-Type AVPNieobsługiwane-
7.2.10Addressee-Type AVPNieobsługiwane-
7.2.11AF-Correlation-Information AVPObsługiwane-
7.2.12Alternate-Charged-Party-Address AVPNieobsługiwane-
7.2.13AoC-Cost-Information AVPNieobsługiwane-
7.2.14AoC-Format AVPNieobsługiwane-
7.2.15AoC-Information AVPObsługiwane-
7.2.16AoC-Request-Type AVPObsługiwane-
7.2.17AoC-Service AVPNieobsługiwane-
7.2.18AoC-Service-Obligatory-Type AVPNieobsługiwane-
7.2.19AoC-Service-Type AVPNieobsługiwane-
7.2.20AoC-Subscription-Information AVPNieobsługiwane-
7.2.21Applic-ID AVPNieobsługiwane-
7.2.22Application-provided-Called-Party-Address AVPNieobsługiwane-
7.2.23Application-Server AVPNieobsługiwane-
7.2.24Application-Server-Information AVPNieobsługiwane-
7.2.25Associated-Party-Address AVPNieobsługiwane-
7.2.26Associated-URI AVPNieobsługiwane-
7.2.27Authorised-QoS AVPNieobsługiwane-
7.2.28Aux-Applic-Info AVPNieobsługiwane-
7.2.29Base-Time-Interval AVPObsługiwane-
7.2.29ABasic-Service-Code AVPNieobsługiwane-
7.2.29BBearer-Capability AVPNieobsługiwane-
7.2.30Bearer-Service AVPNieobsługiwane-
7.2.30ABasic service set identifier (BSSID) AVPNieobsługiwane-
7.2.31Called-Asserted-Identity AVPNieobsługiwane-
7.2.32Called-Party-Address AVPNieobsługiwane-
7.2.33Calling-Party-Address AVPNieobsługiwane-
7.2.34Carrier-Select-Routing-Information AVPNieobsługiwane-
7.2.35Cause-Code AVPNieobsługiwane-
7.2.36CG-Address AVPObsługiwane-
7.2.37Change-Condition AVPObsługiwane-
7.2.38Change-Time AVPNieobsługiwane-
7.2.38ACharge-Reason-Code AVPNieobsługiwane-
7.2.39Charged-Party AVPNieobsługiwane-
7.2.39ACharging-Characteristics-Selection-Mode AVPNieobsługiwane-
7.2.40Class-Identifier AVPNieobsługiwane-
7.2.41Client-Address AVPNieobsługiwane-
7.2.41ACN-Operator-Selection-Entity AVPNieobsługiwane-
7.2.42Content-Class AVPNieobsługiwane-
7.2.43Content-Disposition AVPNieobsługiwane-
7.2.44Content-Length AVPNieobsługiwane-
7.2.45Content-Size AVPNieobsługiwane-
7.2.46Content-Type AVPNieobsługiwane-
7.2.46ACSG-Access-Mode AVPObsługiwane-
7.2.46BCSG-Membership-Indication AVPObsługiwane-
7.2.47Current-Tariff AVPNieobsługiwane-
7.2.48CUG-Information AVPNieobsługiwane-
7.2.49Data-Coding-Scheme AVPNieobsługiwane-
7.2.50DCD-Information AVPObsługiwane-
7.2.51Deferred-Location-Event-Type AVPNieobsługiwane-
7.2.52Delivery-Report-Requested AVPNieobsługiwane-
7.2.53Destination-Interface AVPNieobsługiwane-
7.2.54Diagnostics AVPObsługiwane-
7.2.55Domain-Name AVPNieobsługiwane-
7.2.56DRM-Content AVPNieobsługiwane-
7.2.57Dynamic-Address-Flag AVPObsługiwane-
7.2.57ADynamic-Address-Flag-Extension AVPNieobsługiwane-
7.2.58Early-Media-Description AVPNieobsługiwane-
7.2.59Envelope AVPObsługiwane-
7.2.60Envelope-End-Time AVPObsługiwane-
7.2.61Envelope-Reporting AVPObsługiwane-
7.2.62Envelope-Start-Time AVPObsługiwane-
7.2.62AePDG-Address AVPNieobsługiwane-
7.2.63Event AVPNieobsługiwane-
7.2.64Event-Charging-TimeStamp AVPObsługiwane-
7.2.65Event-Type AVPNieobsługiwane-
7.2.66Expires AVPNieobsługiwane-
7.2.67File-Repair-Supported AVPNieobsługiwane-
7.2.67AForwarding-Pending AVPNieobsługiwane-
7.2.67BFrom-Address AVPNieobsługiwane-
7.2.68GGSN-Address AVPObsługiwane-
7.2.69IM-Information AVPObsługiwane-
7.2.70Incremental-Cost AVPNieobsługiwane-
7.2.70AInstance-Id AVPNieobsługiwane-
7.2.71Interface-Id AVPNieobsługiwane-
7.2.72Interface-Port AVPNieobsługiwane-
7.2.73Interface-Text AVPNieobsługiwane-
7.2.74Interface-Type AVPNieobsługiwane-
7.2.74AIMS-Application-Reference-Identifier AVPNieobsługiwane-
7.2.75IMS-Charging-Identifier AVPNieobsługiwane-
7.2.76IMS-Communication-Service-Identifier AVPNieobsługiwane-
7.2.76AIMS-Emergency-Indicator AVPNieobsługiwane-
7.2.77IMS-Information AVPObsługiwane-
7.2.77AIMS-Visited-Network-Identifier AVPNieobsługiwane-
7.2.78IMSI-Unauthenticated-Flag AVPNieobsługiwane-
7.2.79Incoming-Trunk-Group-ID AVPNieobsługiwane-
7.2.79AInitial-IMS-Charging-Identifier AVPNieobsługiwane-
7.2.80Inter-Operator-Identifier AVPNieobsługiwane-
7.2.80AIP-Realm-Default-Indication AVPNieobsługiwane-
7.2.80BISUP-Cause AVPNieobsługiwane-
7.2.80CISUP-Cause-Diagnostics AVPNieobsługiwane-
7.2.80DISUP-Cause-Location AVPNieobsługiwane-
7.2.80EISUP-Cause-Value AVPNieobsługiwane-
7.2.80FISUP-Location-Number AVPNieobsługiwane-
7.2.81LCS-APN AVPNieobsługiwane-
7.2.82LCS-Client-Dialed-By-MS AVPNieobsługiwane-
7.2.83LCS-Client-External-ID AVPNieobsługiwane-
7.2.84LCS-Client-ID AVPNieobsługiwane-
7.2.85LCS-Client-Name AVPNieobsługiwane-
7.2.86LCS-Client-Type AVPNieobsługiwane-
7.2.87LCS-Data-Coding-Scheme AVPNieobsługiwane-
7.2.88LCS-Format-Indicator AVPNieobsługiwane-
7.2.89LCS-Information AVPObsługiwane-
7.2.90LCS-Name-String AVPNieobsługiwane-
7.2.91LCS-Requestor-ID AVPNieobsługiwane-
7.2.92LCS-Requestor-ID-String AVPNieobsługiwane-
7.2.92ALocal-GW-Inserted-Indication AVPNieobsługiwane-
7.2.93Local-Sequence-Number AVPNieobsługiwane-
7.2.94Location-Estimate AVPNieobsługiwane-
7.2.95Location-Estimate-Type AVPNieobsługiwane-
7.2.96Location-Type AVPNieobsługiwane-
7.2.97Low-Balance-Indication AVPObsługiwane-
7.2.97ALow-Priority-Indicator AVPNieobsługiwane-
7.2.97BMBMS-Charged-Party AVPNieobsługiwane-
7.2.98MBMS-GW-Address AVPNieobsługiwane-
7.2.99MBMS-Information AVPObsługiwane-
7.2.100MBMS-User-Service-Type AVPNieobsługiwane-
7.2.101Media-Initiator-Flag AVPNieobsługiwane-
7.2.102Media-Initiator-Party AVPNieobsługiwane-
7.2.103Message-Body AVPNieobsługiwane-
7.2.104Message-Class AVPNieobsługiwane-
7.2.105Message-ID AVPNieobsługiwane-
7.2.106Message-Size AVPNieobsługiwane-
7.2.107Message-Type AVPNieobsługiwane-
7.2.108MM-Content-Type AVPNieobsługiwane-
7.2.109MMBox-Storage-Requested AVPNieobsługiwane-
7.2.110MMS-Information AVPObsługiwane-
7.2.111MMTel-Information AVPObsługiwane-
7.2.111AMMTel-Service-Type AVPNieobsługiwane-
7.2.111BMSC-Address AVPNieobsługiwane-
7.2.111CMTC-IWF-Address AVPNieobsługiwane-
7.2.111DNeighbour-Node-Address AVPNieobsługiwane-
7.2.112Next-Tariff AVPNieobsługiwane-
7.2.112ANNI-Information AVPNieobsługiwane-
7.2.112BNNI-Type AVPNieobsługiwane-
7.2.113Node-Functionality AVPNieobsługiwane-
7.2.114Node-Id AVPObsługiwane-
7.2.115Number-Of-Diversions AVPNieobsługiwane-
7.2.116Number-Of-Messages-Sent AVPNieobsługiwane-
7.2.117Number-Of-Participants AVPNieobsługiwane-
7.2.118Number-Of-Received-Talk-Bursts AVPNieobsługiwane-
7.2.119Number-Of-Talk-Bursts AVPNieobsługiwane-
7.2.120Number-Portability-Routing-Information AVPNieobsługiwane-
7.2.121Offline-Charging AVPObsługiwane-
7.2.122Online-Charging-Flag AVPNieobsługiwane-
7.2.123Originating-IOI AVPNieobsługiwane-
7.2.124Originator AVPNieobsługiwane-
7.2.125Originator-Address AVPNieobsługiwane-
7.2.126Originator-Interface AVPNieobsługiwane-
7.2.127Originator-Received-Address AVPNieobsługiwane-
7.2.128Originator-SCCP-AddressNieobsługiwane-
7.2.128AOutgoing-Session-Id AVPNieobsługiwane-
7.2.129Outgoing-Trunk-Group-ID AVPNieobsługiwane-
7.2.185SDP-TimeStamps AVPNieobsługiwane-
7.2.186SDP-Type AVPNieobsługiwane-
7.2.186ASession-Direction AVPNieobsługiwane-
7.2.187Served-Party-IP-Address AVPNieobsługiwane-
7.2.188VoidNie dotyczy-
7.2.189Service-Data-Container AVPObsługiwane-
7.2.190Service-ID AVPNieobsługiwane-
7.2.191Service-Generic-Information AVPObsługiwane-
7.2.192Service-Information AVPObsługiwane-
7.2.193Service-Mode AVPNieobsługiwane-
7.2.194Service-Specific-Data AVPNieobsługiwane-
7.2.195Service-Specific-Info AVPObsługiwane-
7.2.196Service-Specific-Type AVPNieobsługiwane-
7.2.197VoidNie dotyczy-
7.2.198Serving-Node-Type AVPObsługiwane-
7.2.199SGSN-Address AVPObsługiwane-
7.2.199ASGW-Address AVPNie dotyczy-
7.2.200SGW-Change AVPObsługiwane-
7.2.201SIP-Method AVPNieobsługiwane-
7.2.202SIP-Request-Timestamp AVPNieobsługiwane-
7.2.203SIP-Request-Timestamp-Fraction AVPNieobsługiwane-
7.2.204SIP-Response-Timestamp AVPNieobsługiwane-
7.2.205SIP-Response-Timestamp-Fraction AVPNieobsługiwane-
7.2.205ASM-Device-Trigger-Indicator AVPNieobsługiwane-
7.2.205BSM-Device-Trigger-Information AVPNieobsługiwane-
7.2.206SM-Discharge-Time AVPNieobsługiwane-
7.2.207SM-Message-Type AVPNieobsługiwane-
7.2.208SM-Protocol-Id AVPNieobsługiwane-
7.2.208ASM-Sequence-Number AVPNieobsługiwane-
7.2.209SM-Status AVPNieobsługiwane-
7.2.210SM-User-Data-Header AVPNieobsługiwane-
7.2.211SMS-Information AVPObsługiwane-
7.2.212SMS-Node AVPNieobsługiwane-
7.2.212ASMS-Result AVPNieobsługiwane-
7.2.213SM-Service-Type AVPNieobsługiwane-
7.2.214SMSC-Address AVPNieobsługiwane-
7.2.214AStart-of-Charging AVPNieobsługiwane-
7.2.215Start-Time AVPObsługiwane-
7.2.215AStatus-Code AVPNieobsługiwane-
7.2.216Stop-Time AVPObsługiwane-
7.2.217Submission-Time AVPNieobsługiwane-
7.2.218Subscriber-Role AVPNieobsługiwane-
7.2.219Supplementary-Service AVPNieobsługiwane-
7.2.219ATAD-Identifier AVPNieobsługiwane-
7.2.220Talk-Burst-Exchange AVPNieobsługiwane-
7.2.221Talk-Burst-Time AVPNieobsługiwane-
7.2.222Talk-Burst-Volume AVPNieobsługiwane-
7.2.223Tariff-Information AVPNieobsługiwane-
7.2.224Tariff-XML AVPNieobsługiwane-
7.2.224ATeleservice AVPNieobsługiwane-
7.2.225Terminating-IOI AVPNieobsługiwane-
7.2.226Time-First-Usage AVPNieobsługiwane-
7.2.227Time-Last-Usage AVPNieobsługiwane-
7.2.228Time-Quota-MechanismObsługiwane-
7.2.229Time-Quota-Threshold AVPObsługiwane-
7.2.230Time-Quota-Type AVPObsługiwane-
7.2.231Time-Stamps AVPNieobsługiwane-
7.2.232Time-Usage AVPNieobsługiwane-
7.2.233Traffic-Data-Volumes AVPObsługiwane-
7.2.233ATranscoder-Inserted-Indication AVPNieobsługiwane-
7.2.233BTransit-IOI-List AVPNieobsługiwane-
7.2.234Token-Text AVPNieobsługiwane-
7.2.235Trigger AVPObsługiwane-
7.2.236Trigger-Type AVPObsługiwane-
7.2.237Trunk-Group-ID AVPNieobsługiwane-
7.2.237AVoidNie dotyczy-
7.2.237BVoidNie dotyczy-
7.2.237CTWAN-User-Location-Info AVPNieobsługiwane-
7.2.238Type-Number AVPNieobsługiwane-
7.2.239Unit-Cost AVPNieobsługiwane-
7.2.240Unit-Quota-Threshold AVPObsługiwane-
7.2.240AUser-CSG-Information AVPNieobsługiwane-
7.2.241User-Participating-Type AVPNieobsługiwane-
7.2.242User-Session-Id AVPNieobsługiwane-
7.2.242AVCS-Information AVPNieobsługiwane-
7.2.242BVLR-Number AVPNieobsługiwane-
7.2.243Volume-Quota-Threshold AVPObsługiwane-
7.2.244VoidNie dotyczy-
7.2.245VoidNie dotyczy-
7.2.246VoidNie dotyczy-
7.2.247VoidNie dotyczy-
7.2.248VoidNie dotyczy-
7.2.249VoidNie dotyczy-
7.2.250VoidNie dotyczy-
7.33GPP2 access specific AVPsNie dotyczy-
7.4Fixed access specific AVPsNie dotyczy-

Polecenia sesji Diameter

Tabela 2-2 zawiera polecenia sesji Diameter obsługiwane przez Diameter Gateway.

Tabela 2-2: Polecenia sesji Diameter

Diameter CommandStatusUwagi
Credit-Control-RequestObsługiwane-
Credit-Control-AnswerObsługiwane-

Komunikaty żądania Diameter Credit-Control

Tabela 2-3 zawiera komunikaty żądania Diameter credit-control obsługiwane przez Diameter Gateway.

Tabela 2-3: Komunikaty żądania Diameter Credit-Control

Diameter Gy MessageStatusUwagi
Session ChargingObsługiwane-
Top-UpObsługiwane-
Balance-QueryObsługiwaneSupports both summary and detailed Balance-Query modes
Debit/RefundObsługiwane-
Price EnquiryObsługiwane-

AVP żądania Gy Session Charging (IUT)

Tabela 2-4 zawiera informacje o zgodności dla Gy Session Charging attribute-value pairs (AVPs) for the session-based operacji żądania, such as INITIATE, Update, and TERMINATE (IUT).

Tabela 2-4: AVP żądania Gy Session Charging (IUT)

Diameter AVPStatusUwagi
Session-IdObsługiwane-
Service-Context-IdObsługiwane-
CC-Request-TypeObsługiwane1 - INITIATE
2 - UPDATE
3 - TERMINATE
CC-Request-NumberObsługiwane-
Event-TimestampObsługiwane-
Subscription-IdObsługiwane-
– Subscription-Id-DataObsługiwane-
– Subscription-Id-TypeObsługiwane-
Termination-CauseObsługiwane-
Service-InformationObsługiwane-
– PS-InformationObsługiwane-
– – Called-Station-IdObsługiwane-
– – SGSN-AddressObsługiwane-
– – GGSN-AddressObsługiwane-
– – MS-TimeZone-3GPPObsługiwane-
– – DiagnosticsObsługiwane-
User-NameNieobsługiwaneSubscription-Id-Data AVP is used instead
Multiple-Services-Credit-ControlObsługiwaneZobacz Tabela 2-5 for more information.

Multiple-Services-Credit-Control

Tabela 2-5 zawiera informacje o zgodności dla Multiple-Services-Credit-Control AVPs for the Gy Session Charging operacji żądania.

Tabela 2-5: Multiple-Services-Credit-Control AVPs for Gy Session Charging Request

Diameter AVPStatusUwagi
Service-IdentifierObsługiwane-
Rating-GroupObsługiwane-
Requested-Service-UnitObsługiwane-
– CC-TimeObsługiwane-
– CC-MoneyNieobsługiwane-
– CC-Total-OctetsObsługiwane-
– CC-Input-OctetsObsługiwane-
– CC-Output-OctetsObsługiwane-
– CC-Service-Specific-UnitsObsługiwane-
Used-Service-UnitObsługiwane-
– CC-TimeObsługiwane-
– CC-MoneyNieobsługiwane-
– CC-Total-OctetsObsługiwane-
– CC-Input-OctetsObsługiwane-
– CC-Output-OctetsObsługiwane-
– CC-Service-Specific-UnitsObsługiwane-

AVP odpowiedzi Gy Session Charging (IUT)

Tabela 2-6 zawiera informacje o zgodności dla Diameter Credit-Control-Answer AVPs for the Gy Session Charging operacji odpowiedzi.

Tabela 2-6: AVP odpowiedzi Gy Session Charging (IUT)

Diameter AVPStatusUwagi
Session-IdObsługiwane-
Result-CodeObsługiwane-
CC-Request-TypeObsługiwane-
CC-Session-FailoverObsługiwane-
Credit-Control-Failure-HandlingObsługiwane-
Multiple-Services-Credit-ControlObsługiwaneZobacz Tabela 2-7 for more info

Multiple-Services-Credit-Control

Tabela 2-7 lists the Multiple-Services-Credit-Control AVPs for the Gy Session Charging operacji odpowiedzi.

Tabela 2-7: Multiple-Services-Credit-Control AVPs for Gy Session Charging Response

Diameter AVPStatusUwagi
Requested-Service-UnitObsługiwaneContains the AVPs submitted in the message request.
Granted-Service-UnitObsługiwane-
– CC-TimeObsługiwane-
– CC-MoneyNieobsługiwane-
– CC-Total-OctetsObsługiwane-
– CC-Input-OctetsObsługiwane-
– CC-Output-OctetsObsługiwane-
– CC-Service-Specific-UnitsObsługiwane-
– Cost-InformationObsługiwane-
– – Unit-ValueObsługiwane-
– – – Value-DigitsObsługiwane-
– – – ExponentObsługiwane-
– – Currency-CodeObsługiwane-
ORA-Customer-Cost-InformationObsługiwane-
– ORA-Subscriber-IdObsługiwane-
– ORA-Cost-InformationObsługiwane-
– – Unit-ValueObsługiwane-
– – – Value-DigitsObsługiwane-
– – – ExponentObsługiwane-
– – ORA-Balance-Element-IdObsługiwane-
ORA-Remaining-BalanceObsługiwane-
– ORA-Balance-ElementObsługiwane-
– – ORA-Balance-Element-IdObsługiwane-
– – Unit-ValueObsługiwane-
– – – Value-DigitsObsługiwane-
– – – ExponentObsługiwane-
– – ORA-Balance-ItemObsługiwane-
– ORA-Subscriber-IdObsługiwane-
ORA-Credit-Threshold-BreachObsługiwane-
– ORA-Balance-Element-IdObsługiwane-
– ORA-Current-BalanceObsługiwane-
– ORA-Fixed-Threshold-ValuesObsługiwane-
– – ORA-Fixed-ThresholdObsługiwane-
ORA-Percentage-Threshold-ValuesObsługiwane-
– ORA-Percentage-ThresholdObsługiwane-
– ORA-Breach-DirectionObsługiwane0 - THRESHOLD_BREACH_UP
1 - THRESHOLD_BREACH_DOWN
Final-Unit-IndicationCzęściowo obsługiwaneTERMINATE and REDIRECT are supported.
Validity-TimeObsługiwane-
Result-CodeObsługiwane-

AVP żądania Gy Top-Up

Tabela 2-8 zawiera informacje o zgodności dla Gy Top-Up AVPs for the operacji żądania.

Tabela 2-8: AVP żądania Gy Top-Up

Diameter AVPStatusUwagi
CC-Request-TypeObsługiwane4 - EVENT_REQUEST
Requested-ActionObsługiwane4 - TOP-UP
Subscription-IdObsługiwane-
– Subscription-Id-TypeObsługiwane-
– Subscription-Id-DataObsługiwane-
Event-TimestampObsługiwane-
Rating-GroupObsługiwane-
Service-IdentifierObsługiwane-
ORA-Account-TopupObsługiwane-
– ORA-Recharge-ReferenceObsługiwane-
– ORA-BalanceObsługiwane-
– – ORA-Balance-Element-IdObsługiwane-
– – Unit-ValueObsługiwane-
– – – Value-DigitsObsługiwane-
– – – ExponentObsługiwane-
– – ORA-Validity-Start-TimeObsługiwane-
– – ORA-Validity-End-TimeObsługiwane-
– – ORA-Validity-Start-RelativeObsługiwane-
– – – ORA-Validity-OffsetObsługiwane-
– – – ORA-Validity-UnitObsługiwane0 - SECONDS
1- MINUTES
2 - HOURS
3 - DAYS
4 - MONTHS
5 - ACC_CYCLE
6 - BILL_CYCLE
7 - ABSOLUTE
8 - INFINITE
– – ORA-Validity-End-RelativeObsługiwane-
– – – ORA-Validity-OffsetObsługiwane-
– – – ORA-Validity-UnitObsługiwane0 - SECONDS
1- MINUTES
2 - HOURS
3 - DAYS
4 - MONTHS
5 - ACC_CYCLE
6 - BILL_CYCLE
7 - ABSOLUTE
8 - INFINITE
– – ORA-First-Usage-ValidityObsługiwane-
– – – ORA-Validity-OffsetObsługiwane-
– – – ORA-Validity-UnitObsługiwane0 - SECONDS
1- MINUTES
2 - HOURS
3 - DAYS
4 - MONTHS
5 - ACC_CYCLE
6 - BILL_CYCLE
7 - ABSOLUTE
8 - INFINITE
– – ORA-Extend-Bucket-ValidityObsługiwane0 - FALSE
1 - TRUE
– – Service-IdentifierObsługiwane-
– – Rating-GroupObsługiwane-
Multi-Services-IndicatorNieobsługiwaneDoes not apply

AVP odpowiedzi Gy Top-Up

Tabela 2-9 zawiera informacje o zgodności dla Gy Top-Up AVPs for the operacji odpowiedzi.

Tabela 2-9: AVP odpowiedzi Gy Top-Up

Diameter AVPStatusUwagi
ORA-Remaining-BalanceObsługiwane-
– ORA-Balance-ElementObsługiwane-
– ORA-Applicable-ServicesObsługiwane-
– – Service-IdentifierObsługiwane-
– – Rating-GroupObsługiwane-
– ORA-Balance-ElementObsługiwane-
– – Unit-ValueObsługiwane-
– – – Value-DigitsObsługiwane-
– – – ExponentObsługiwane-
– – ORA-Balance-ItemObsługiwane-
– – – Unit-ValueObsługiwane-
– – – – Value-DigitsObsługiwane-
– – – – ExponentObsługiwane-
– – – ORA-Validity-Start-TimeObsługiwane-
– – – ORA-Validity-End-TimeObsługiwane-
– – ORA-Earliest-Expiry-TimeObsługiwane-
CC-Session-FailoverObsługiwane-
Credit-Control-Failure-HandlingObsługiwane-

AVP żądania Gy Balance Query

Tabela 2-10 zawiera informacje o zgodności dla Gy Balance Query AVPs for the operacji żądania.

Tabela 2-10: AVP żądania Gy Balance Query

Diameter AVPStatusUwagi
CC-Request-TypeObsługiwane4 - EVENT_REQUEST
Requested-ActionObsługiwane5 - BALANCE_QUERY
Event-TimestampObsługiwane-
Subscription-IdObsługiwane-
– Subscription-Id-DataObsługiwane-
– Subscription-Id-TypeObsługiwane-
Service-IdentifierObsługiwane-
Rating GroupObsługiwane-
ORA-Balance-Query-ModeObsługiwane1- Podsumowanie
2 - Detailed
Multi-Services-IndicatorNieobsługiwaneDoes not apply

AVP odpowiedzi Gy Balance Query

Tabela 2-11 zawiera informacje o zgodności dla Gy Balance Query AVPs for the operacji odpowiedzi.

Tabela 2-11: AVP odpowiedzi Gy Balance Query

Diameter AVPStatusUwagi
Service-IdentifierObsługiwaneReturned only when it is set in the original request; indicates the corresponding product for which the Balance query is returned.
Rating-GroupObsługiwaneReturned only when it is set in the original request; indicates the corresponding product for which the Balance query is returned.
ORA-Balance-DetailsObsługiwane
– ORA-Balance-ElementObsługiwane
—- ORA-Balance-Element-IdObsługiwane
—- Unit-ValueObsługiwane
—— Value-DigitsObsługiwane
—— ExponentObsługiwane
—- ORA-Earliest-Expiry-TimeObsługiwane
—- ORA-Balance-ItemObsługiwane
—— Unit-ValueObsługiwane
——– Value-DigitsObsługiwane
——– ExponentObsługiwane
—— ORA-Validity-Start-TimeObsługiwane
—— ORA-Validity-End-TimeObsługiwane
—— ORA-Consumed-Reservation-AmountObsługiwane
——– Value-DigitsObsługiwane
——– ExponentObsługiwane
—— ORA-Active-Reservation-AmountObsługiwane
——– Value-DigitsObsługiwane
——– ExponentObsługiwane
—- ORA-Credit-FloorObsługiwane
—— Value-DigitsObsługiwane
—— ExponentObsługiwane
—- ORA-Credit-CeilingObsługiwane
—— Value-DigitsObsługiwane
—— ExponentObsługiwane
—- ORA-Percent-Credit-ThresholdObsługiwane
—— ORA-Threshold-ValueObsługiwane
—- ORA-Fixed-Credit-ThresholdObsługiwane
—— ORA-Threshold-ValueObsługiwane
CC-Session-FailoverObsługiwane
Credit-Control-Failure-HandlingObsługiwane

AVP żądania Gy Debit/Refund

Tabela 2-12 zawiera informacje o zgodności dla Gy Debit/Refund AVPs for the operacji żądania.

Tabela 2-12: AVP żądania Gy Debit/Refund

Diameter AVPStatusUwagi
Session-IdObsługiwane-
Service-Context-IdObsługiwane-
CC-Request-TypeObsługiwane-
CC-Request-Number-
Refund-InformationObsługiwane-
CC-Correlation-IdObsługiwane-
Destination-HostNieobsługiwane-
User-NameNieobsługiwaneSubscription-Id-Data AVP is used instead
CC-Sub-Session-IdNieobsługiwane-
Acct-Multi-Session-IdNieobsługiwane-
Origin-State-IdNieobsługiwane-
Event-TimestampObsługiwane-
Subscription-IdObsługiwane-
– Subscription-Id-DataObsługiwane-
– Subscription-Id-TypeObsługiwane-
Requested-ActionObsługiwane0 - DIRECT_DEBITING
1 - REFUND_ACCOUNT.
Więcej informacji: RFC 4006 Section 8.41
Multiple-Services-IndicatorObsługiwaneAlways expected to be True
Service-Parameter-InfoNieobsługiwane-
User-Equipment-InfoNieobsługiwane-
Proxy-InfoNieobsługiwane-
Route-RecordNieobsługiwane-
Service-InformationObsługiwane-
– PS-InformationObsługiwane-
– – Called-Station-IdObsługiwane-
– – MS-TimeZone-3GPPObsługiwane-
Multiple-Services-Credit-ControlObsługiwaneZobacz Tabela 2-13

Multiple-Services-Credit-Control

Tabela 2-13 zawiera informacje o zgodności dla Multiple-Services-Credit-Control AVPs for Gy Debit/Refund operacji żądania.

Tabela 2-13: Multiple-Services-Credit-Control AVPs for Gy Debit/Refund Request

Diameter AVPStatusUwagi
Service-IdentifierObsługiwane-
Rating-GroupObsługiwane-
Requested-Service-UnitObsługiwane-
– CC-TimeObsługiwane-
– CC-MoneyObsługiwane-
– – Unit-Value-
– – – Value-Digits-
– – – ExponentObsługiwane-
– – Currency-CodeObsługiwane-
CC-ORA-Balance-ElementObsługiwane-
– – Unit-Value-
– – – Value-Digits-
– – – ExponentObsługiwane-
– – ORA-Balance-Element-IdObsługiwane-
CC-Total-OctetsObsługiwane-
CC-Input-OctetsObsługiwane-
CC-Output-OctetsObsługiwane-
CC-Service-Specific-UnitsObsługiwane-

AVP odpowiedzi Gy Debit/Refund

Tabela 2-14 zawiera informacje o zgodności dla Gy Debit/Refund AVPs for the operacji odpowiedzi.

Tabela 2-14: AVP odpowiedzi Gy Debit/Refund

Diameter AVPStatusUwagi
Session-IdObsługiwane-
Result-CodeObsługiwane-
Remaining-BalanceObsługiwane-
Cost-InformationObsługiwane-
ORA-Customer-Cost-InformationObsługiwane-
CC-Session-FailoverObsługiwane-
Credit-Control-Failure-HandlingObsługiwane-
Direct-Debiting-Failure-HandlingObsługiwane-
Multiple-Services-Credit-ControlObsługiwaneZobacz Tabela 2-15

Multiple-Services-Credit-Control

Tabela 2-15 zawiera informacje o zgodności dla Multiple-Services-Credit-Control AVPs for Gy Debit/Refund operacji odpowiedzi.

Tabela 2-15: Multiple-Services-Credit-Control AVPs for Gy Debit/Refund Response

Diameter AVPStatusUwagi
Result-CodeObsługiwane-
Service-IdentifierObsługiwane-
Rating-GroupObsługiwane-
Refund-InformationObsługiwaneTylko dla refund
Granted-Service-UnitsObsługiwaneDostarczane tylko w odpowiedzi debit
Requested-Service-UnitObsługiwaneContains the AVPs submitted in the message request
ORA-Remaining-BalanceObsługiwane-
ORA-Customer-Cost-InformationObsługiwane-
ORA-Cost-InformationObsługiwane-
ORA-Subscriber-IdObsługiwane-
ORA-Balance-ElementObsługiwane-
ORA-Balance-Element-IdObsługiwane-
CC-TimeObsługiwane-
CC-MoneyObsługiwane-
Unit-ValueObsługiwane-
Value-DigitsObsługiwane-
ExponentObsługiwane-
Currency-CodeObsługiwane-
CC-Total-OctetsObsługiwane-
CC-Input-OctetsObsługiwane-
CC-Output-OctetsObsługiwane-
CC-Service-Specific-UnitsObsługiwane-

AVP żądania Gy Price Enquiry

Tabela 2-16 zawiera informacje o zgodności dla Gy Price Enquiry AVPs for the operacji żądania.

Tabela 2-16: AVP żądania Gy Price Enquiry

Diameter AVPStatusUwagi
Session-IdObsługiwane-
Service-Context-IdObsługiwane-
CC-Request-TypeObsługiwane-
CC-Request-NumberObsługiwane-
Destination-HostNieobsługiwane-
User-NameNieobsługiwaneSubscription-Id-Data AVP is used instead.
CC-Sub-Session-IdNieobsługiwane-
Acct-Multi-Session-IdNieobsługiwane-
Origin-State-IdNieobsługiwane-
Event-TimestampObsługiwane-
Subscription-IdObsługiwane-
– Subscription-Id-DataObsługiwane-
– Subscription-Id-TypeObsługiwane-
Requested-ActionObsługiwane3 - PRICE_ENQUIRY
Multiple-Services-IndicatorObsługiwaneAlways expected to be True
Service-InformationObsługiwane-
– PS-InformationObsługiwane-
– – Called-Station-IdObsługiwane-
– – SGSN-AddressObsługiwane-
– – GGSN-AddressObsługiwane-
– – MS-TimeZone-3GPPObsługiwane-
– – DiagnosticsObsługiwane-
Service-Parameter-InfoNieobsługiwane-
CC-Correlation-IdNieobsługiwane-
User-Equipment-InfoNieobsługiwane-
Proxy-InfoNieobsługiwane-
Multiple-Services-Credit-ControlObsługiwaneZobacz Tabela 2-17

Multiple-Services-Credit-Control

Tabela 2-17 zawiera informacje o zgodności dla Multiple-Services-Credit-Control AVPs for Gy price enquiry operacji żądania.

Tabela 2-17: Multiple-Services-Credit-Control AVPs for Gy Price Enquiry Request

Diameter AVPStatusUwagi
Multiple-Services-Credit-ControlObsługiwane-
– Service-IdentifierObsługiwane-
– Rating-GroupObsługiwane-
– Requested-Service-UnitObsługiwane-
– – CC-TimeObsługiwane-
– – CC-Input-OctetsObsługiwane-
– – CC-Output-OctetsObsługiwane-
– – CC-Total-OctetsObsługiwane-

AVP odpowiedzi Gy Price Enquiry

Tabela 2-18 zawiera informacje o zgodności dla Gy Price Enquiry AVPs for the operacji odpowiedzi.

Tabela 2-18: AVP odpowiedzi Gy Price Enquiry

Diameter AVPStatusUwagi
Session-IdObsługiwane-
Result-CodeObsługiwane-
Multiple-Services-Credit-ControlObsługiwaneZobacz Tabela 2-19
Cost-InformationObsługiwane-
– Unit-ValueObsługiwane-
– – Value-DigitsObsługiwane-
– – ExponentObsługiwane-
– Currency-CodeObsługiwane-
CC-Session-FailoverObsługiwane-
Credit-Control-Failure-HandlingObsługiwane-

Multiple-Services-Credit-Control

Tabela 2-19 zawiera informacje o zgodności dla Multiple-Services-Credit-Control AVPs for Gy Price Enquiry operacji odpowiedzi.

Tabela 2-19: Multiple-Services-Credit-Control AVPs for Gy Price Enquiry Response

Diameter AVPStatusUwagi
– Service-IdentifierObsługiwane-
– Rating-GroupObsługiwane-
– Requested-Service-UnitObsługiwane-
– – CC-TimeObsługiwane-
– – CC-Input-OctetsObsługiwane-
– – CC-Output-OctetsObsługiwane-
– – CC-Total-OctetsObsługiwane-
– ORA-Customer-Cost-InformationObsługiwane-
– – ORA-Subscriber-IdObsługiwane-
– – ORA-Cost-InformationObsługiwane-
– – – Unit-ValueObsługiwane-
– – – – Value-DigitsObsługiwane-
– – – – ExponentObsługiwane-
– – – ORA-Balance-Element-IdObsługiwane-

Polecenia ponownej autoryzacji sesji Diameter

Tabela 2-20 zawiera informacje o zgodności dla Diameter Session Reauthorization commands.

Tabela 2-20: Polecenia ponownej autoryzacji sesji Diameter

Diameter CommandStatusUwagi
Re-Auth-Request (RAR)Obsługiwane-
Re-Auth-Answer (RAA)Obsługiwane-

Re-Auth-Request AVPs

Tabela 2-21 zawiera informacje o zgodności dla Re-Auth-Request (RAR) AVPs.

Tabela 2-21: Re-Auth-Request AVPs

Diameter AVPStatusUwagi
Session-IdObsługiwane-
Origin-HostObsługiwane-
Origin-RealmObsługiwane-
Destination-HostObsługiwane-
Destination-RealmObsługiwane-
Origin-State-IdObsługiwane-
Service-IdentifierObsługiwane-
Rating-GroupObsługiwane-

Re-Auth-Answer AVPs

Tabela 2-22 zawiera informacje o zgodności dla Re-Auth-Answer (RAA) AVPs.

Tabela 2-22: Re-Auth-Answer AVPs

Diameter AVPStatusUwagi
Session-IdObsługiwane-
Origin-HostObsługiwane-
Origin-RealmObsługiwane-
Result-CodeObsługiwane-

Polecenia zakończenia sesji Diameter

Tabela 2-23 zawiera informacje o zgodności dla Diameter Session Termination commands.

Tabela 2-23: Polecenia zakończenia sesji Diameter

Diameter CommandStatusUwagi
Session-Termination-RequestObsługiwane-
Session-Termination-AnswerObsługiwane-

Session-Termination-Request AVPs

Tabela 2-24 zawiera informacje o zgodności dla Session-Termination-Request (STR) AVPs.

Tabela 2-24: Session-Termination-Request AVPs

Diameter AVPStatusUwagi
Session-IdObsługiwane-

Session-Termination-Answer AVPs

Tabela 2-25 zawiera informacje o zgodności dla Session-Termination-Answer (STA) AVPs.

Tabela 2-25: Session-Termination-Answer AVPs

Diameter AVPStatusUwagi
Session-IdObsługiwane-
Result-CodeObsługiwane-
Failed-AVPObsługiwane-

Protokół Diameter Gx

Aplikacja Gx jest wyspecjalizowaną aplikacją Diameter dla określonych dostawców. W kontekście protokołu Diameter przez interfejs Gx urządzenie 7x50 (Policy and Charging Enforcement Function, PCEF) działa jako Diameter Client, natomiast Policy and Charging Rules Function (PCRF) działa jako Diameter Server. Aplikacja Gx Diameter wykorzystuje istniejące kody poleceń zarówno z Diameter Base Protocol (zgodnie z RFC 6733), jak i z Diameter Credit Control Application (zgodnie z RFC 4006).

Do reprezentowania danych w strukturach komunikatów, w szczególności kodów poleceń, Gx używa par Attribute-Value Pair (AVP).

AVP w Gx pochodzą z różnych źródeł, w tym:

  • AVP unikalne dla Gx, zgodnie z dokumentem 3GPP Gx TS 29.212.
  • AVP zapożyczone z innych aplikacji Diameter (np. RFC 4006, RFC 4005), innych specyfikacji 3GPP, European Telecommunications Standards Institute (ETSI) itd.
  • Atrybuty ponownie wykorzystane z RADIUS (kody AVP 0-255 są zarezerwowane dla tych ponownie użytych atrybutów).
  • AVP specyficzne dla dostawców.

Proces inicjowania i utrzymywania połączenia między 7x50 (PCEF) a PCRF jest regulowany przez podstawowy protokół Diameter opisany w RFC 3588/6733.

Gx AVP

Ten przewodnik zawiera podsumowanie par Attribute Value Pair (AVP) Gx obsługiwanych przez 7750 SR. Implementacja jest zgodna ze specyfikacją Gx Release v11.12, dokument 3GPP 29212-bc0.doc.

Tabela 3-1 przedstawia konwencje używane w tym przewodniku.

Tabela 3-1: Konwencje atrybutów

AtrybutOpis
0Ten atrybut nie może występować w pakiecie.
0+W pakiecie może występować zero lub więcej instancji tego atrybutu.
0-1W pakiecie może występować zero albo jedna instancja tego atrybutu.
1W pakiecie musi występować dokładnie jedna instancja tego atrybutu.

AVPs

Niektóre AVP mają zastosowanie tylko w jednym kierunku, a inne w obu kierunkach.

AVP wysyłane przez 7750 SR służą do:

  • informowania PCRF o utworzeniu lub zakończeniu hosta oraz o tożsamości hosta subskrybenta w 7750 SR
  • informowania PCRF o funkcjonalności obsługiwanej w 7750 SR
  • raportowania określonych zdarzeń związanych z hostem subskrybenta
  • raportowania statusu reguły
  • raportowania monitorowania użycia
  • raportowania statusu hosta (istnieje/nie istnieje)

AVP wysyłane przez PCRF do 7750 SR służą do:

  • instalowania albo aktywowania polityk
  • żądania monitorowania użycia
  • kończenia hosta subskrybenta
  • żądania statusu hosta subskrybenta (istnieje/nie istnieje)

AVP mające zastosowanie w obu kierunkach są używane do podstawowych funkcji Diameter, takich jak ustanawianie peeringu, routing komunikatów Diameter, identyfikacja sesji i raportowanie awarii krytycznych (zmiana OSI).

Zastrzeżone słowa kluczowe w 7750 SR

Zarezerwowane słowa kluczowe używane do identyfikowania typu obiektu referencyjnego w 7750 SR wymieniono w Tabeli 3-2. Dodatkowe odniesienia zawiera Tabela 3-4.

Tabela 3-2: Zastrzeżone słowa kluczowe w 7750 SR

Reserved KeywordsUsed in AVPComments
ingr-v4charging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
ingr-v6charging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
egr-v4charging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
egr-v6charging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
in-othr-v4charging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
in-othr-v6charging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
sub-idcharging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
sla-profilecharging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
sub-profilecharging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
inter-destcharging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
cat-mapcharging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
aa-functionsadc-rule-name, charging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.
aa-functions:appcharging-rule-nameUsed to identify the AA app-profile directly in the charging-rule-name AVP in a charging-rule-install. Zobacz Tabela 3-4 and Table 1-5.
aa-functions:asocharging-rule-nameUsed to identify the AA ASO characteristic and value directly in a charging-rule-name AVP in a charging rule-install. Table 3-4 and Table 1-5.
aa-functions:urlparamcharging-rule-nameUsed to identify the AA Sub HTTP URL parameter directly in a charging-rule-name AVP in a charging rule-install. Zobacz Tabela 3-4 and Table 1-5.
aa-functions:subscopecharging-rule-nameUsed to identify the AA Sub scope directly in a charging-rule-name AVP in a charging rule-install. Zobacz Tabela 3-4 and Table 1-5.
aa-umcharging-rule-nameUsed to identify referenced object type within 7x50. Zobacz Tabela 3-3.

Standardowe AVP Diameter

AVP mają zastosowanie w następujących aplikacjach:

  • Gx-PM-ESM — Policy Management for Enhanced Subscriber Management
  • Gx-UM-ESM — Usage Monitoring for Enhanced Subscriber Management
  • Gx-PM-AA — Policy Management for Application Assurance
  • Gx-UM-AA — Usage Monitoring Application Assurance

AVP wymienione w poniższej Tabeli 3-3, które nie mają powiązanej aplikacji, są używane do celów ogólnych i mogą być stosowane we wszystkich aplikacjach.

Tabela 3-3: Description of Standard Diameter AVPs

AVP IDAVP NameSekcja DefinedApplicationDescription
5NAS-PortRFC 2865 / §5.5Zobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
8Framed-IP-AddressRFC 4005 / §6.11.1Ten AVP określa the IPv4 address of the subscriber host. The IPv4 address is obtained before Gx session establishment. The IPv4 address cannot be assigned to the subscriber host by PCRF via Gx but is instead used only for reporting.
183GPP-SGNS-MCC-MNC29.061For GTP S11 Access contains the value configured under configure>subscriber-mgmt>gtp>serving-network.
223GPP-User-Location-Info29.061In CCR-I, this contains the User Location Information as signaled in the incoming GTP-C message for GTP Access hosts.
For a CCR-U triggered by either USER_LOCATION_CHANGE (ULC), ECGI_CHANGE, or TAI_CHANGE will include ULI values as follows:
- If the trigger was ULC and the ULI contains anything other than ECGI or TAI, the ULI is signaled as received in GTP.
- If the trigger was ULC and either TAI or ECGI changed from its last known value, both TAI and ECGI will be included.
- If the trigger was ECGI_CHANGE and ECGI changed from its last known value, ECGI is included.
- If the trigger was TAI_CHANGE and TAI change from its last known value, TAI is included.
25ClassRFC 2865 / §5.25Ten atrybut jest dostępny to be sent by the PCRF to the 7750 SR and is echoed unmodified by the 7750 SR to the PCRF. The 7750 SR does not interpret this attribute locally.
30Called-Station-IdRFC 2865 / §5.30RFC 4005 / §4.5Zobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
31Calling-Station-IDRFC 4005 / §4.6Zobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
55Event-TimestampRFC 6733 / §8.21Ten AVP rejestruje the time that this event occurred on the 7750 SR, in seconds since January 1, 1900 00:00 UTC.
61NAS-Port-TypeRFC 2865 / §5.41RFC 4005 / §4.4RFC 4603
Zobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
87NAS-Port-IdRFC 2869 / §5.17RFC 4005 / §4.3Zobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
92NAS-Filter-RuleRFC 4849Gx-PM-ESMZobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
Ten AVP jest zagnieżdżony w the Charging-Rule-Definition AVP.
97Framed-IPv6-PrefixRFC 4005 / §6.11.6Ten AVP określa the IPv6-prefix and prefix-length that is assigned to the host via SLAAC (Router Advertisement) to the WAN side of the user.
The IPv6-prefix and prefix-length is obtained before Gx session establishment.
The facilities to provide the IPv6-prefix and prefix-length to the subscriber-host are DHCP server/local pools, RADIUS or LUDB.
The IPv6-prefix/prefix-length cannot be assigned to the subscriber host by PCRF via Gx. Instead the IPv6-prefix and prefix-length is the one being reported to the PCRF during the host instantiation phase.
123Delegated-IPv6-PrefixRFC 4818Ten atrybut przenosi the Prefix (ipv6-prefix/prefix-length) assigned to the host via DHCPv6 (IA-PD) for the LAN side of the user (IPoE, PPPoE).
The IPv6-prefix/prefix-length is obtained before Gx session establishment.
The facilities to provide the IPv6-prefix/prefix-length to the subscriber-host are DHCP server/local pools, RADIUS or LUDB.
The IPv6-prefix/prefix-length cannot be assigned to the subscriber host by PCRF via Gx. Instead the IPv6-prefix and prefix-length is the one being reported to the PCRF during the host instantiation phase.
257Host-IP-AddressRFC 6733 / §5.3.5Ten AVP jest używany to inform a Diameter peer of the sender’s IP address.
The IPv4 address used is the one configured in the diameter-peer-policy. If none is configured, then system-ip address is used.
258Auth-Application-IdRFC 6733 / §6.8Ten AVP wskazuje supported Diameter applications.
The application support is exchanged in CER/CEA when the peering sessions is established.
The diameter base protocol does not require application ID because its support is mandatory.
The Gx application ID value is 16777238 and it is advertised in Auth-Application-Id AVP within the grouped Vendor-Specific-Application-Id AVP in CER message.
In addition, each Gx specific message carries Auth-Application-Id AVP with the value of 16777238.
260Vendor-Specific-Application-IdRFC 6733 / §6.11To jest zgrupowany AVP that is used to advertise support of a vendor-specific Diameter application in CER/CEA messages. Gx is one such application. Ten AVP zawiera the Vendor-Id AVP of the application and the auth-application-id AVP.
263Session-idRFC 6733 / §8.8Ten AVP musi występować in all messages and it is used to identify a specific IP-Can session. IP-Can session corresponds to a subscriber host, which can be DHCPv4/v6, PPPoX or ARP host. Session-id AVP is unique per host.
Dual stack host (IPoE or PPPoX) share a single session-id.
264Origin-HostRFC 6733 / §6.3Ten AVP musi występować in all messages and it is used to identify the endpoint (Diameter peer) that originated the message.
265Supported-Vendor-IdRFC 6733 / §5.3.6Ten AVP jest używany in CER/CEA messages to inform the peer that the sender supports a subset of the vendor-specific AVPs defined by the vendor identified in this AVP.
266Vendor-IdRFC 6733 / §5.3.3Wartość tego AVP jest kodem przypisanym przez IANA do określonego dostawcy.
This AVP may be part of the Vendor-Specific-Application-Id AVP, Failed-AVP AVP, Experimental-Result AVP to identify the vendor associated with the relevant message/AVP.
In case of a standalone Vendor-Id AVP (outside of any grouped AVP) that is conveyed in CER/CEA messages, it is envisioned that this AVP along with the Product-Name AVP and the Firmware-Revision AVP may provide useful debugging information.
267Firmware-RevisionRFC 6733 / §5.3.4Wersja SR OS jest raportowana.
268Result-CodeRFC 6733 / §7.1Ten AVP wskazuje whether a particular request was completed successfully or an error occurred.
All answer messages in Diameter/Gx must include one Result-Code AVP or Experimental-Result AVP.
269Product-NameRFC 6733 / §5.3.7Ten AVP określa the vendor-assigned name.
278Origin-State-IdRFC 6733 / §8.16Ten AVP jest używany to inform the PCRF of the loss of the state on the 7750 SR side. Its value monotonically increases each time the PCRF is rebooted with the loss of the previous state.
Because Gx sessions are not persistent in the 7750 SR, Origin-State-Id increases each time the 7750 SR is rebooted.
279Failed-AVPRFC 6733 / §7.5To zgrupowany AVP, który dostarcza informacje diagnostyczne, gdy żądanie zostaje odrzucone albo nie jest w pełni przetworzone z powodu błędnych informacji w określonym AVP. Wartość AVP Result-Code zawiera informacje o przyczynie Failed-AVP. AVP Failed-AVP zawiera cały AVP, którego nie udało się pomyślnie przetworzyć.
281Error-MessageRFC 6733 / §7.3Ten AVP dostarcza more information of the failure that is indicated in the Result-Code AVP.
282Route RecordRFC 6733 / §6.7.1Ten AVP identyfikuje the peer from which the request is received and is used for routing loop detection. An SR node inserts the origin-host of the peer in the Route-Record AVP of all transit request messages.
283Destination-RealmRFC 6733 / §6.6Ten AVP reprezentuje the realm to which this message is to be routed.
285Re-Auth-Request-TypeRFC 6733 / §8.12This AVP is mandatory in RAR requests. The content of this AVP is ignored by the 7750 SR.
293Destination-HostRFC 6733 / §6.5Ten AVP reprezentuje the host to which this message is to be sent.
Wartość tego AVP można skonfigurować jawnie.
In case that it is omitted, the DRA (Diameter relay-agent) that receives the message selects the destination host to which the message is sent.
295Termination-CauseRFC 6733 / §8.15Ten AVP jest używany to indicate the reason why a session was terminated on the 7750 SR.
296Origin-RealmRFC 6733 / §6.4Ten AVP zawiera the realm of the originator of message. In the 7750 SR, the Origin-Realm is explicitly configured per Diameter peer.
297Experimental-ResultRFC 6733 / §7.6To jest zgrupowany AVP that indicates whether a particular vendor-specific request completed successfully or whether an error occurred. It contains a vendor-assigned value representing the result of processing a request.
The result-code AVP values defined in Diameter Base RFC (6733, §7.1) are also applicable to Experimental-Result AVP.
Dla listy Gx-specific Experimental-Result-Code values supported in the 7750 SR, see Table 3-7. For Gx application, the Vendor-Id AVP is set to 10415 (3GPP).
All answer messages defined in vendor-specific application must include either one Result-Code AVP or one Experimental-Result AVP.
298Experimental-Result-CodeRFC 6733 / §7.729.214 / §5.5Ten AVP określa vendor-assigned (3GPP — Gx) values representing the result of processing the request.
Dla listy the 7750 SR supported values for Gx see Table 3-7.
302Logical-Access-IdETSI TS 283 034 / §7.3.3BBF TR-134 (§7.1.4.1)Ten AVP zawiera information describing the subscriber agent circuit identifier corresponding to the logical access loop port of the Access Node from which the subscriber’s requests are initiated, namely: circuit-id from DHCPv4 Option (82,1) circuit-id from PPPoE tag (0x105, 0x00000de9 [dsl forum], 0x01 — DSL Forum TR-101) interface-id from DHCPv6 option 18. The Vendor-Id in CER is set to ETSI (13019).
313Physical-Access-IdETSI TS283 034 / §7.3.14BBF TR-134 (§7.1.4.1)Ten AVP zawiera information about the identity of the physical access to which the user device is connected, namely: remote-id from DHCPv4 Option (82,2) remote-id from PPPoE tag (0x105, 0x00000de9 [dsl forum], 0x02 — DSL Forum TR-101) remote-id from DHCPv6 option 37. The Vendor-Id in CER is set to ETSI (13019).
412CC-Input-OctetsRFC 4006 / §8.24Gx-UM-ESM Gx-UM-AATen AVP zawiera the number of requested, granted or used octets from the user.
414CC-Output-OctetsRFC 4006 / §8.25Gx-UM-ESM Gx-UM-AATen AVP zawiera the number of requested, granted or used octets toward the user.
415CC-Request-NumberRFC 4006 / §8.2Ten AVP identyfikuje each request within one session. Each request within a session has a unique CC-Request-Number that is used for matching requests with answers.
416CC-Request-TypeRFC 4006 / §8.3Ten AVP identyfikuje the request type: INITIAL_REQUEST (CCR-I) UPDATE_REQUEST (CCR-U) TERMINATION_REQUEST (CCR-T)
418CC-Session-FailoverRFC 4006 / §8.4Ten AVP kontroluje whether the secondary peer will be used in case that the primary peer is unresponsive (peer failover behavior). The unresponsiveness is determined by the timeout of the previously sent message. If this AVP is not supplied via PCRF, the locally configured options in the 7750 SR will determine the peer failover behavior. For further details on the peer failover behavior, see “Gx Fallback Function” section in the Gx Configuration Guide.
421CC-Total-OctetsRFC 4006 / §8.23Gx-UM-ESM Gx-UM-AATen AVP zawiera the number of requested, granted or used octets regardless of the direction (sent or received).
427Credit-Control-Failure-HandlingRFC 4006 / §8.14Ten AVP kontroluje whether the subscriber is terminated or instantiated with default parameters in case that the PCRF is unresponsive. The unresponsiveness is determined by the timeout of the previously sent message. If this AVP is not supplied via PCRF, the locally configured options in the 7750 SR determines the behavior. For further details, see the “Gx Fallback Function” section in the Gx Configuration Guide.
431Granted-Service-UnitRFC 4006 / §8.17Gx-UM-ESM Gx-UM-AATen zgrupowany AVP jest wysyłany by PCRF to the 7750 SR for usage monitoring purposes. When the granted amount of units is consumed by the user, a report is sent from the 7750 SR to the PCRF. The amount of consumed units can be measured on three different levels: Session level (host level) PCC rule level (credit category in the 7750 SR) ADC rule level (AA level in the 7750 SR)
433Redirect-Address-TypeRFC 4006 / §8.38Gx-PM-ESMTen AVP określa the address type of the HTTP redirect server. URL (2) type is the only address type supported in the 7750 SR.
435Redirect-Server-AddressRFC 4006 / §8.39Gx-PM-ESMTen AVP określa the URL string of the redirect server.
443Subscription-IdRFC 4006 / §8.46This AVP is of type Grouped and is used to identify the subscriber host in the 7750 SR. The nested AVPs are subscription-id-data and subscription-id-type.
444Subscription-Id-DataRFC 4006 / §8.48This AVP is part of the subscription-id AVP and is used to identify the host by: Circuit-id Dual-stack-remote-id Imei Imsi Mac of the host Msisdn Subscriber-id Username (ppp-username or a string returned in the Username attribute via RADIUS or NASREQ) Subscription type (subscription-id-type AVP) has to be explicitly set via CLI. The data will be formatted according to the type set. Dla dostępu GTP S11, the value under configure>subscriber-mgmt>diameter-application-policyapplication-policy-name>gxavp-subscription-id is ignored and the session always includes two subscription-Id AVPs for both IMSI and MSISDN.
446Used-Service-UnitRFC 4006 / §8.19Gx-UM-ESM Gx-UM-AAThis AVP is of type Grouped and it represents the measured volume threshold for usage monitoring control purposes. It is sent in the Usage-Monitoring-Report AVP from the 7750 SR to the PCRF when the granted unit threshold is reached or in response to a usage-report request from the PCRF.
450Subscription-Id-TypeRFC 4006 / §8.47Ten AVP jest używany to determine which type of identifier is carried by the subscription-id AVP. The following formats (types) are supported in the 7750 SR: E.164 format (ITU-T E.164) IMSI format (ITU-T E.212) NAI format (RFC 2486) Private format
458User-Equipment-InfoRFC 4006 / §8.49To jest zgrupowany AVP that carries information about the identity and the capabilities of the host.
459User-Equipment-Info-TypeRFC 4006 / §8.50Ten AVP jest zagnieżdżony w the User-Equipment-Info AVP. The following types are supported in the 7750 SR: IMEISV – contains the IMEI and software version according to 3GPP TS 23.003 document. MAC address Eui64 based on 48-bit MAC address with 0xfffe inserted in the middle. Modified_eui64 — similar to eui64 but with inverted ‛u’ bit as defined in: http://standards.ieee.org/develop/regauth/tut/eui64.pdf and RFC 4291. The equipment type must be explicitly set through the CLI. Dla dostępu GTP S11, the configuration is ignored and always uses IMEISV.
460User-Equipment-Info-ValueRFC 4006 / §8.51Ten AVP przenosi the value that is defined by the User-Equipment-Info-Type AVP.
507Flow-Description29.214 / §5.3.8Gx-PM-ESMTen AVP jest zagnieżdżony w Flow-Information AVP. It identifies traffic within the PCC rule based on the 5 tuple.
511Flow-Status29.214 / §5.3.11Gx-PM-ESMTen AVP jest używany to set the service gating action for the service represented by the PCC rule. It is nested inside of Charging-Rule-Definition AVP. Supported values are: ENABLED (2) DISABLED (3) The service identified by PCC rule is by default enabled (Flow-Status = ENABLED). If explicitly configured within the PCC rule, it must be accompanied with one or more additional actions. Otherwise, the entire PCC rule instantiation fails. Flow-Status = DISABLED can be the sole action within the PCC rule. Traffic associated with this action, is dropped.
515Max-Requested-Bandwidth-DL29.214 / §5.3.14Gx-PM-ESMDepending on the context in which it is configured (nested), this AVP represents the egress PIR of a queue or a policer.
516Max-Requested-Bandwidth-UL29.214 / §5.3.15Gx-PM-ESMDepending on the context in which it is configured (nested), this AVP represents the ingress PIR of a queue or a policer.
554Extended-Max-Requested-BW-DL29.214 / §5.3.52Gx-PM-ESMPrzy wyższych wymaganiach dotyczących przepływności, this AVP can be used in place of the Max-Requested-Bandwidth-DL AVP.
555Extended-Max-Requested-BW-UL29.214 / §5.3.52Gx-PM-ESMPrzy wyższych wymaganiach dotyczących przepływności, this AVP can be used in place of the Max-Requested-Bandwidth-UL AVP.
628Supported-Features29.229 / §6.3.2929.212 / §5.4.1To jest zgrupowany AVP that is used during Gx session establishment to inform the destination host about the required and optional features that the origin-host supports. One instance of Supported-Features AVP is needed per Feature-List-id.
629Feature-List-Id29.229 / §6.3.30Ten AVP zawiera the identity of a feature list. This AVP allows differentiation between multiple feature lists in case that an application has multiple feature lists defined.
630Feature-List29.229 / §6.3.31Ten AVP zawiera a bitmask indicating the supported feature in Gx. The Gx features in the Feature-List AVP are defined in 3GPP TS 29.212, §5.4.1.
909RAI29.061Dla dostępu GTP S11, this contains the RAI if it was signaled in GTP.
1001Charging-Rule-Install29.212 / §5.3.2This AVP is of type Grouped and is used to enforce overrides, install NAS filter inserts and install or modify PCC rules in the node as instructed by PCRF.
1002Charging-Rule-Remove29.212 / §5.3.3This AVP is of type Grouped and is used to remove PCC rules from an IP CAN session.
1003Charging-Rule-Definition29.212 / §5.3.4This AVP is of type Grouped and is used for rule overrides, NAS filter inserts or PCC rules installation. It contains nested AVPs that define the overrides (rate changes of a subscriber, a queue or a policer, and so on), NAS filter insert or a completely new PCC rule definition.
1005Charging-Rule-Name29.212 / §5.3.6Ten AVP jest używany to reference a predefined rule in the node, name the PCC rule which is defined through Charging-Rule-Definition AVP, and report rule/override status in case of a rule/override activation failure.
1006Event-Trigger29.212 / §5.3.7This AVP can be sent from the PCRF to subscribe to a particular event in the 7750 SR.
1010Precedence29.212 / §5.3.11Gx-PM-ESMThis AVP is carried within a PCC rule definition (Charging-Rule-Definition) and it determines the order in which PCC rules are installed for the subscriber-host.
1014ToS-Traffic-Class29.214 / §5.3.15Gx-PM-ESMTen AVP jest zagnieżdżony w Flow-Information AVP. It identifies traffic within the PCC rule based on DSCP bits.
1016QoS-Information29.212 / §5.3.16Gx-PM-ESMTen AVP pełni wieloaspektową funkcję: As part of PCC rule definition in CCA or RAR, this AVP is used to rate-limit a flow. The AVP defines QoS overrides that can be submitted from PCRF to the SR OS router in a CCA or RAR message. The AVP defines APN Uplink and Downlink Aggregate Maximum Bitrate (AMBR) in a CCA or RAR message.
1018Charging-Rule-Report29.212 / §5.3.18This AVP is of type Grouped and is used to report the status of PCC rules in the 7750 SR.
1019PCC-Rule-Status29.212 / §5.3.19Ten AVP opisuje the status of the rules as active or inactive and is nested within the Charging-Rule-Report AVP.
1025Guaranteed-Bitrate-DL29.212 / §5.3.25Gx-PM-ESMDepending on the context in which it is configured (nested), this AVP represents the egress CIR of a queue or a policer.
1026Guaranteed-Bitrate-UL29.212 / §5.3.26Gx-PM-ESMDepending on the context in which it is configured (nested), this AVP represents the ingress CIR of a queue or a policer.
1027IP-CAN-Type29.212 / §5.3.27Ten AVP wskazuje the type of Connectivity Access Network in which the user is connected.
1028QoS-Class-Identifier29.212 / §5.3.17Ten AVP identyfikuje a QoS forwarding class within the router.
1031Rule-Failure-Code29.212 / §5.3.38Ten AVP jest wysyłany from the router to the PCRF within a Charging-Rule-Report or ADC-Rule-Report AVP to identify the reason a rule is being reported.
1032RAT-Type29.212 / §5.3.31Ten AVP identyfikuje the radio access technology used for this connection.
1040APN-Aggregate-Max-Bitrate-DL29.212When received in an RAR or CCA, this value can be mapped to a local egress QoS override.
1045Session-Release-Cause29.212 / §5.3.33Gx-PM-ESMGx-PM-AA
1050AN-GW-Address29.212 / §5.3.49This AVP is the system IPv4 address of the 7750 SR.
1058Flow-Information29.212 / §5.3.53Gm-PM-ESMTo jest zgrupowany AVP carrying information about traffic identification with the PCC rule. Ten AVP jest zagnieżdżony w Charging-Rule-Definition AVP.
1065PDN-Connection-ID29.212For GTP S11, the access value contains the APN as received in GTP.
1066Monitoring-Key29.212 / §5.3.59Gx-UM-ESMGx-UM-AA
1067Usage-Monitoring-Information29.212 / §5.3.60Gx-UM-ESMGx-UM-AA
1068Usage-Monitoring-Level29.212 / §5.3.61Gx-UM-ESMGx-UM-AA
1069Usage-Monitoring-Report29.212 / §5.3.62Gx-UM-ESMGx-UM-AA
1070Usage-Monitoring-Support29.212 / §5.3.63Gx-UM-ESMGx-UM-AA
1080Flow-Direction29.212 / §5.3.65Gx-PM-ESMTen AVP jest zagnieżdżony w the Flow-Information AVP. It identifies the direction in which the PCC rule is applied (ingress or egress).
1085Redirect-Information29.212 / §5.3.82Gx-PM-ESMTo jest zgrupowany AVP that contains HTTP redirect information.
1086Redirect-Support29.212 / §5.3.83Gx-PM-ESMThis AVP is nested inside of Redirect-Information AVP.
1088TDF-Application-Identifier29.212 / §5.3.77Gx-UM-AAThis AVP is of type OctetString.
1092ADC-Rule-Install29.212 / §5.3.85Gx-PM-AAGx-UM-AA
1093ADC-Rule-Remove29.212 / §5.3.86Gx-PM-AAGx-UM-AA
1094ADC-Rule-Definition29.212 / §5.3.87Gx-PM-AAGx-UM-AA
1096ADC-Rule-Name29.212 / §5.3.89Gx-PM-AAGx-UM-AA
1097ADC-Rule-Report29.212 / §5.3.90Gx-PM-AAGx-UM-AA
2848Extended-APN-AMBR-DL29.212 / §5.3.134Przy wyższych wymaganiach dotyczących przepływności, this AVP can be used in place of the APN-Aggregate-Max-Bitrate-DL AVP.
2849Extended-APN-AMBR-UL29.212 / §5.3.135Przy wyższych wymaganiach dotyczących przepływności, this AVP can be used in place of the APN-Aggregate-Max-Bitrate-UL AVP.
2850Extended-GBR-DL29.212 / §5.3.136Gx-PM-ESMPrzy wyższych wymaganiach dotyczących przepływności, this AVP can be used in place of the Guaranteed-Bitrate-DL AVP.
2851Extended-GBR-UL29.212 / §5.3.137Gx-PM-ESMPrzy wyższych wymaganiach dotyczących przepływności, this AVP can be used in place of the Guaranteed-Bitrate-UL AVP.

Standardowe AVP Diameter (format)

Tabela 3-4 lists standard diameter AVPs.

Incl/Excl – The atrybut can be suppressed via CLI.

Flags (as set by the 7750 SR when the AVP is constructed):

  • V — Vendor specific bit
  • M — Mandatory bit
  • P — Ten bit jest zawsze ustawiony na 0

UTF8String is a human-readable string using UTF-8 transformation format (which is for 7-bit encoding the same as US-ASCII).

OctetString jest podstawowym typem danych zawierającym dowolne dane. Na przykład AVP Charging-Rule-Name jest OctetString zgodnie z RFC 6733, ale w 7750 SR jest wyświetlany jako czytelny ciąg znaków (UTF8String).

Flags for Gx specific AVPs are defined in RFC 6733, §4.5; 29.212, §5.3.

Flagi dla AVP ponownie używanych w Gx są ustawiane zgodnie z RFC 6733, §4.5 oraz 3GPP 29.219, §5.4 — ‟The AVPs from Diameter base protocol are not included in Tabela 5.4, but they are re-used for the Gx reference point. Unless otherwise stated, re-used AVPs shall maintain their ‘M’, ‘P’ and ‘V’ ustawienia flag. Where 3GPP RADIUS AVPs are re-used, unless otherwise stated, they shall be translated to Diameter AVPs as described in RFC 4005 [12] with the exception that the ‘M’ flag shall be set and the ‘P’ flag may be set”.

NA — to słowo kluczowe (Not Advertised) oznacza, że AVP nie pochodzi z 7750 SR, dlatego 7750 SR nie ustawia bitów flag. 7750 SR rozpoznaje jednak AVP i odpowiadające im wartości wymienione w tabeli niezależnie od flag M-bit ustawionych przez PCRF. Jeśli w odebranym AVP występuje V-bit, pole Vendor-Id w układzie AVP również musi być obecne i ustawione na poprawną wartość, ponieważ AVP z ustawionym V-bit jest identyfikowany przez parę <avp-id, vendor-id>.

Tabela 3-4: Standardowe AVP Diameter (format)

AVP IDAVP NameIncl/ ExclTypeFlagsLimitsFormat
5NAS-PortYesUnsigned32M4 octetsZobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
8Framed-IP-AddressNoOctetStringM4 octetsExample: ip-address 10.11.12.13 Framed-IP-Address = 0a0b0c0d As defined in RFC 4005, §6.11.1.
223GPP-User-Location-InfoYesOctetStringV—Vendor-Id = 10415 (3GPP) Szczegóły kodowania zawiera 3GPP TS 29.061.
30Called-Station-IdYesUTF8StringM64 charsExample: Called-Station-Id = mac:ssid or mac only if ssid is not available.
31Calling-Station-IDYesUTF8StringM64 charsExample: llid
55Event-Time stampNoTimeM4 octetsZobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
61NAS-Port-TypeYesEnumeratedM4 octetsThe values for this attribute are defined in the RFC 2865, 4005 and 4603. Zobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
87NAS-Port-IdYesUTF8StringM253 octetsZobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
92NAS-Filter-RuleNAUTF8StringNAMax 10 attributes per message or max 10 filter entries per message.Zobacz 7750 SR and VSR RADIUS Attributes Reference Guide.
97Framed-IPv6-PrefixNoOctetStringM—SLAAC wan-host <ipv6-prefix/prefix-length> with prefix-length 64 The AVP layout is: <1 octet Reserved> <1 octet Length> <max 16 octets for Prefix>
123Delegated-IPv6-PrefixNoOctetStringM—<ipv6-prefix/prefix-length> with prefix-length [48 to 64] The AVP layout is: <1 octet Reserved> <1 octet Length> <max 16 octets for Prefix>
257Host-IP-AddressNoAddressM—IPv4 Address
258Auth-Application-IdNoUnsigned32M—Example: Gx Auth-Application-Id = 16777238
260Vendor-Specific-Application-IdNoGroupedM—Ten AVP zawiera the Vendor-Id AVP and Auth-Application-Id AVP. For Gx, the Vendor-Id = 10415 (3GPP) and the Auth-Application-Id = 16777238.
263Session-idNoUTF8StringM102 bytesThe session-id must be globally and eternally unique. The format of the session-id is the following: ;<high 32 bits>;<low 32 bits> In the 7750 SR the session-id is defined as: diameter-identity;boxuptime; seq-number Example: router.workstation.be;1391362206;1
264Origin-HostNoDiameterIdentityM80 bytesExample: Origin-Host = host-name-1@domain-name-1
265Supported-Vendor-IdNoUnsigned32M—IANA assigned vendor number: 3GPP — 10415 ETSI — 13019 Tridens — 6527
266Vendor-IdNoUnsigned32M—IANA assigned vendor number: 3GPP — 10415 ETSI — 13019 Tridens — 6527 BBF — 3561
267Firmware-RevisionNoUnsigned32——Reference to the major/minor release version. Example: 805 — Release 8R5
268Result-CodeNoUnsigned32M—Zobacz Tabela 3-7 for Error Codes.
269Product-NameNoUTF8String——Vendor-assigned name for the product. Example: ‟SR OS”
278Origin-State-IdNoUnsigned32M—Example: Origin-State-Id = 10
279Failed-AVPNoGroupedM—Ten AVP zawiera the AVP that could not be processed successfully.
281Error-MessageNoUTF8String——String describing the cause of the failure.
282Route-RecordNoDiameterIdentityM80 bytesExample: Route-Record: host-1
283Destination-RealmNoDiameterIdentityM80 bytesExample: Destination-Realm = domain.com
285Re-Auth-Request-TypeNoEnumeratedNA—Ten AVP jest zawsze odbierany in RAR message and it is never sent by the 7750 SR.
293Destination-HostNoDiameterIdentityM80 bytesOperator configurable.
295Termination-CauseNoEnumeratedM—Dla listy the 7750 SR supported values for Gx see Table 3-10.
296Origin-RealmNoDiameterIdentityM80 bytesExample: Origin-Realm = origin-domain.com
297Experimental-ResultNoGroupedM—A grouped AVP containing: Vendor-Id AVP Experimental-Result-Code AVP Example: Experimental-Result = {Vendor-Id = 10415 (3GPP) Experimental-Result-Code = DIAMETER_PCC_RULE_EVENT (5142)}
298Experimental-Result-CodeNoUnsigned32M—Dla listy the 7750 SR supported values for Gx see Table 3-7.
302Logical-Access-IdYesOctetStringV—Vendor ID = 13019 (ETSI)
313Physical-Access-IdYesUTF8StringV—Vendor ID = 13019 (ETSI)
412CC-Input-OctetsNoUnsigned64M—Example: CC-Input-Octets = 1000000
414CC-Output-OctetsNoUnsigned64M—Example: CC-Output-Octets = 1000000
415CC-Request-NumberNoUnsigned32M—Monotonically increasing from 0 for all requests within one session.
416CC-Request-TypeNoEnumeratedM—Example: CC-Request-Type = 1 (CCR-i) 3. CC-Request-Type = 2 (CCR-u) CC-Request-Type = 3 (CCR-t)
418CC-Session-FailoverNoEnumeratedM—FAILOVER_NOT_SUPPORTED (0) FAILOVER_SUPPORTED (1) Example: CC-Session-Failover = 1
421CC-Total-OctetsNoUnsigned64M—Example: CC-Total-Octets = 2000000
427Credit-Control-Failure-HandlingNoEnumeratedM—TERMINATE (0) CONTINUE (1) RETRY_AND_TERMINATE (2) Example: Credit-Control-Failure-Handling = 1
431Granted-Service-UnitNoGroupedM—Ten AVP może zawierać the following AVPs: CC-Total-Octets CC-Input-Octets CC-Output-Octets
433Redirect-Address-TypeNoEnumeratedM—Example: Redirect-Address-Type = 2 (URL type)
435Redirect-Server-AddressNoUTF8StringM255 charsExample: Redirect-Server-Address = http://www.operator.com/portal.php&
443Subscription-IdYesGroupedM—Ten AVP zawiera the following AVPs: Subscription-Id-Type Subscription-Id-Data
444Subscription-Id-DataYesUTF8StringM—Example: Username — Subscription-Id-Data = user1@domain.com
446Used-Service-UnitNoGroupedM—Ten AVP zawiera the following AVPs: CC-Total-Octets CC-Input-Octets CC-Output-Octets
450Subscription-Id-TypeYesEnumeratedM—Example: Subscription-Id-Type = 0 (end_user_e164) Subscription-Id-Type = 1 (end_user_imsi)
458User-Equipment-InfoYesGroupedM—Ten AVP zawiera the following AVPs: User-Equipment-Info-Type User-Equipment-Info-Value
459User-Equipment-Info-TypeYesEnumerated——Example: User-Equipment-Info-Type = 0 (emissive) User-Equipment-Info-Type =1 (mac)
460User-Equipment-Info-ValueYesOctetString———
507Flow-DescriptionNoIPFilterRule (RFC6733, §4.3.1)NA,M—The IPFilterRule format within PCC rule in the 7750 SR has the following syntax: action dir proto from src to dst Example: Flow-Description = allow in 6 from 192.168.7.0/24 3000-40000 to 172.16.10.0/26 10000-20000
511Flow-StatusNoEnumeratedNA,M—Example: Flow-Status = 3 — matched traffic inside of the PCC rule is dropped.
515Max-Requested-Bandwidth-DLNoUnsigned32NA, V—Vendor-Id = 10415 (3GPP) Example: Max-Requested-Bandwidth-DL = 1000 — 1 Mb/s in overrides
516Max-Requested-Bandwidth-ULNoUnsigned32NA, V—Vendor-Id = 10415 (3GPP) Example: Max-Requested-Bandwidth-UL = 1000 — 1 Mb/s for overrides
554Extended-Max-Requested-BW-DLNAUnsigned32NA, V—Vendor-Id = 10415 (3GPP) Example: Extended-Max-Requested-BW-DL = 1000 — 1 Mb/s
555Extended-Max-Requested-BW-ULNAUnsigned32NA, V—Vendor-Id = 10415 (3GPP) Example: Extended-Max-Requested-BW-UL = 1000 — 1 Mb/s
628Supported-FeaturesNoGroupedV—Ten AVP zawiera the following AVPs: Vendor-Id Feature-List-Id Feature-List
629Feature-List-IdNoUnsigned32V—Vendor-Id = 10415 (3GPP) Example: Feature-List-Id = 2
630Feature-ListNoUnsigned32V—Vendor-Id = 10415 (3GPP) Example: Feature-List = 128
909RAIYesOctetstringV12 octetsVendor-Id = 10415 (3GPP) Szczegóły kodowania zawiera 3GPP TS 29.061.
1001Charging-Rule-InstallNoGroupedNA, V—Vendor-Id = 10415 (3GPP) Ten AVP zawiera the following AVPs: Charging-Rule-Definition Charging-Rule-Name
1002Charging-Rule-RemoveNoGroupedNA, V—Vendor-Id = 10415 (3GPP) Ten AVP zawiera the following AVP: Charging-Rule-Name
1003Charging-Rule-DefinitionNoGroupedNA, V—Vendor-Id = 10415 (3GPP) Ten AVP zawiera the following nested AVPs: Charging-Rule-Name, QoS-Information, NAS-Filter-Rule, Alc-NAS-Filter-Rule-Shared, AA-Functions
1005Charging-Rule-NameNoOctetStringV,M100 chars for PCC rules (defined via Charging-Rule-Definition AVP) 128 chars for overrides. Vendor-Id = 10415 (3GPP)
1006Event-TriggerNoEnumeratedV—Vendor-Id = 10415 (3GPP)
1010PrecedenceNoUnsigned32NA, M0 to 65535Vendor-Id = 10415 (3GPP) Example: Precedence = 100
1014Tos-Traffic-ClassNoOctetStringNA, M—Encoded as two octets. Pierwszy oktet zawiera the IPv4 Type-of-Service or the IPv6 Traffic-Class field and the second octet contains the ToS/Traffic Class mask field. Jedyną obsługiwaną maską jest 11111100 (6 bits denoting DSCP support). Example: ToS-Traffic-Class = 00101000 11111100 — DSCP AF11
1016QoS-InformationNAGroupedNA, V—Vendor-Id 10415 (3GPP) When used to signal a flow rate limiter in a PCC rule, this AVP contains the following nested AVPs: Max-Requested-Bandwidth-UL, Max-Requested-Bandwidth-DL, Guaranteed-Bitrate-UL, Guaranteed-Bitrate-DL
1018Charging-Rule-ReportNoGroupedV,M—Vendor-Id = 10415 (3GPP) Ten AVP zawiera the following nested AVPs: Charging-Rule-Name, PCC-Rule-Status, Rule-Failure-Code
1019PCC-Rule-StatusNoEnumeratedV,M—Vendor-Id = 10415 (3GPP) Supported values in the 7750 SR: 1 – inactive Example: PCC-Rule-Status = 0 — rule is active
1025Guaranteed-Bitrate-DLNAUnsigned32NA,V—Jednostkami tego parametru są kb/s for overrides and b/s when used within PCC rules. The rate accounts for the IP header and above (no Layer 2 header). Vendor-Id = 10415 (3GPP) Example: Guaranteed-Bandwidth-DL = 1000 — 1 Mb/s in overrides Guaranteed-Bandwidth-DL = 1000000 — 1 Mb/s in PCC rules
1026Guaranteed-Bitrate-ULNAUnsigned32V—Jednostkami tego parametru są kb/s for overrides and b/s when used within PCC rules. The rate accounts for the IP header and above (no Layer 2 header). Vendor-Id = 10415 (3GPP) Example: Guaranteed-Bandwidth-UL = 1000 — 1 Mb/s in overrides Guaranteed-Bandwidth-UL = 1000000 — 1 Mb/s in PCC rules
1027IP-CAN-TypeYesEnumeratedV—Vendor-Id = 10415 (3GPP) Example: IP-CAN-Type = 2 — xDSL IP-CAN-Type = 5 — 3GPP-EPS
1028QoS-Class-IdentifierNAEnumeratedNA,M—Vendor-Id = 10415 (3GPP) Example: QoS-Class-Identifier = 3 — maps to FC EF.
1031Rule-Failure-CodeNoEnumeratedV,M—Vendor-Id = 10415 (3GPP) Example: Rule-Failure-Code = 1 — UNKNOWN_RULE_NAME
1032RAT-TypeYesEnumeratedV—Vendor-Id = 10415 (3GPP) Example: RAT-Type = 0 — WLAN RAT-Type = 1004 — EUTRAN
1040APN-Aggregate-Max-Bitrate-DLYesUnsigned32V2^32-1 b/sVendor-Id = 10415 (3GPP) Rate in bits per second (b/s) Example: APN-Aggregate-Max-Bitrate-DL = 100000000 (100 Mb/s)
1041APN-Aggregate-Max-Bitrate-ULYesUnsigned32V2^32-1 b/sVendor-Id = 10415 (3GPP) Rate in bits per second (b/s) Example: APN-Aggregate-Max-Bitrate-UL = 10000000 (10 Mb/s)
1045Session-Release-CauseNAEnumeratedV,M—Vendor-Id = 10415 (3GPP) Ten AVP jest tylko odbierany by the 7750 SR and it is never sent by the 7750 SR. 0 — UNSPECIFIED-REASON 1 — UE_SUBSCRIPTION_REASON Ta wartość jest używana to indicate that the subscription of UE has changed (for example, removed) and the session needs to be terminated. 2 — INSUFFICIENT_SERVER_ RESOURCES Ta wartość jest używana to indicate that the server is overloaded and needs to abort the session. Example: Session-Release-Cause = 0
1050AN-GW-AddressYesIPv4AddressV—Vendor-Id = 10415 (3GPP) Example: AN-GW-Address = 10.10.10.10
1058Flow-InformationNoGroupedV—Vendor-Id = 10415 (3GPP) Następujące AVP mogą być zagnieżdżone wewnątrz: Flow-Description, ToS-Traffic-Class, Flow-Direction
1065PDN-Connection-IDYesUTF8StringV100 charsVendor-Id = 10415 (3GPP) For example: PDN-Connection-ID = example-apn.mnc001.mcc001.gprs
1066Monitoring-KeyNoOctetStringNA,V32 bytesVendor-Id = 10415 (3GPP) Category name configured in the 7750 SR, a string used for session monitoring or a Monitoring-Key AVP set in PCC rule definition with the Charging-Rule-Definition AVP. Example: Monitoring-Key = monitor-pcc-rule-1
1067Usage-Monitoring-InformationNoGroupedV—Vendor-Id = 10415 (3GPP) Ten AVP zawiera the following nested AVPs: Monitoring-Key, Granted-Service-Unit, Used-Service-Unit, Usage-Monitoring-Level, Usage-Monitoring-Report, Usage-Monitoring-Support
1068Usage-Monitoring-LevelNoEnumeratedV—Vendor-Id = 10415 (3GPP) Zdefiniowano następujące wartości: 0 – session_level 1 – pcc_rule_level 2 – adc_rule_level Example: Usage-Monitoring-Level = 0 — usage monitoring is performed based on sla-profile (IP-CAN session level) of the host.
1069Usage-Monitoring-ReportNoEnumeratedV—Vendor-Id = 10415 (3GPP) Example: Usage-Monitoring-Report = 0 (usage_monitoring_report_required)
1070Usage-Monitoring-SupportNoEnumeratedNA,V—Vendor-Id = 10415 (3GPP) Example: Usage-Monitoring-Support = 0 — usage_ monitoring_disabled
1080Flow-DirectionNoEnumeratedNA,M—Vendor-Id = 10415 (3GPP) Example: Flow-Direction = 1 — egress Flow-Direction = 2 — ingress
1085Redirect-InformationNoGroupedNA,V—Vendor-Id = 10415 (3GPP) Ten AVP może zawierać the flowing AVPs: Redirect-Support, Redirect-Address-Type, Redirect-Server-Address
1086Redirect-SupportNoEnumeratedNA,V—Vendor-Id = 10415 (3GPP) Example: Redirect-Support = 1 — redirection is enabled
1088TDF-Application-IdentifierOctetStringNA,V32 charsVendor-Id = 10415 (3GPP) Example: 0_rated, BitTorrent
1092ADC-Rule-InstallNoGroupedNA,V—Vendor-Id = 10415 (3GPP) Ten AVP zawiera the following nested AVPs: ADC-Rule-Definition
1093ADC-Rule-RemoveGroupedNA,V—Vendor-Id = 10415 (3GPP) Ten AVP zawiera the following nested AVPs: ADC-Rule-Name
1094ADC-Rule-DefinitionNoGroupedNA,V—Vendor-Id = 10415 (3GPP) Ten AVP zawiera the following nested AVPs: ADC-Rule-Name, MonitoringKey, TDF-Application-Id, AA-Functions
1096ADC-Rule-NameNoOctetStringV17 chars for prefix/separator (optional) plus 32 chars for nameVendor-Id = 10415 (3GPP) Example: For app-profile and ASO changes: ADC-Rule-Name = ‟AA-Functions: AdcRuleWithAAFtn”
1097ADC-Rule-ReportNoGroupedV—Vendor-Id = 10415 (3GPP) Ten AVP zawiera the following nested AVPs: ADC-Rule-Name, PCC-Rule-Status, Rule-Failure-Code
2848Extended-APN-AMBR-DLNAUnsigned32NA, V—Jednostkami tego parametru są kb/s. Vendor-Id = 10415 (3GPP) Example: Extended-APN-AMBR-DL = 1000 — 1 Mb/s
2849Extended-APN-AMBR-ULNAUnsigned32NA, V—Jednostkami tego parametru są kb/s. Vendor-Id = 10415 (3GPP) Example: Extended-APN-AMBR-UL = 1000 — 1 Mb/s
2850Extended-GBR-DLNAUnsigned32NA, V—Jednostkami tego parametru są kb/s. Vendor-Id = 10415 (3GPP) Example: Extended-GBR-DL = 1000 — 1 Mb/s
2851Extended-GBR-ULNAUnsigned32NA, V—Jednostkami tego parametru są kb/s. Vendor-Id = 10415 (3GPP) Example: Extended-GBR-UL = 1000 — 1 Mb/s

Zastosowanie AVP opartych na Diameter

Poniższe tabele używają następujących symboli:

  • 0 — AVP nie może występować w komunikacie.
  • 0+ — W komunikacie może występować zero lub więcej instancji AVP.
  • 0-1 — W komunikacie może występować zero albo jedna instancja AVP. Więcej niż jedna instancja AVP jest uznawana za błąd.
  • 1 — W komunikacie musi występować jedna instancja AVP.
  • 1+ — W komunikacie musi występować co najmniej jedna instancja AVP.
  • N — AVP jest zagnieżdżony w zgrupowanym AVP obecnym w tym komunikacie.

Tabela 3-5: Zastosowanie AVP opartych na Diameter

AVP IDAVP NameCERCEADPRDPADWRDWAASRASA
257Host-IP-Address11+000000
258Auth-Application-Id10+000010
260Vendor-Specific-Application-Id0+0+000000
263Session-id00000011
264Origin-Host11111111
265Supported-Vendor-Id1+0+000000
266Vendor-Id11000000
267Firmware-Revision10-1000000
268Result-Code01010101
269Product-Name11000000
273Disconnect-Cause00100000
278Origin-State-Id10-10000-10-10-1
279Failed-AVP00-100-100-100-1
281Error-Message00000000
283Destination-Realm00000010
293Destination-Host00000010
294Error-Reporting-Host00000000-1
296Origin-Realm11111111

Zastosowanie Gx AVP

Tabela 3-6: Zastosowanie Gx AVP

AVP IDAVP NameCCRCCARARRAA
5NAS-Port0-1000
8Framed-IP-Address0-1000-1
183GPP-SGNS-MCC-MNC0-1000-1
223GPP-User-Location-Info0-1000
30Called-Station-Id0-1000
31Calling-Station-ID0-1000
55Event-Timestamp0-10-10-11
61NAS-Port-Type0-1000
87NAS-Port-Id0-1000
92NAS-Filter-Rule00+0+0
97Framed-IPv6-Prefix0-1000-1
123Delegated-IPv6-Prefix0-1000-1
258Auth-Application-Id1110
263Session-id1111
264Origin-Host1111
266Vendor-Id0N00
268Result-Code0100-1
278Origin-State-Id10-10-11
279Failed-AVP0-10+00-1
281Error-Message0-10-100-1
282Route-Record0+00+0
283Destination-Realm1010
285Re-Auth-Request-Type0010
293Destination-Host0-1010
295Termination-Cause0-1000
296Origin-Realm1111
297Experimental-Result00-100-1
298Experimental-Result-Code0N0N
302Logical-Access-Id0-1000
313Physical-Access-Id0-1000
412CC-Input-OctetsNNN0
414CC-Output-OctetsNNN0
415CC-Request-Number1100
416CC-Request-Type1100
418CC-Session-Failover00-100
421CC-Total-OctetsNNN0
427Credit-Control-Failure-Handling00-100
431Granted-Service-Unit00-1N0
433Redirect-Address-Type0NN0
433Redirect-Server-Address0NN0
443Subscription-Id1-2000
444Subscription-Id-DataN000
446Used-Service-UnitN000
450Subscription-Id-TypeN000
458User-Equipment-Info0-1000
459User-Equipment-Info-TypeN000
460User-Equipment-Info-ValueN000
507Flow-Description0NN0
511Flow-Status0NN0
515Max-Requested-Bandwidth-DL0NN0
516Max-Requested-Bandwidth-UL0NN0
554Extended-Max-Requested-BW-DL0NN0
555Extended-Max-Requested-BW-UL0NN0
628Supported-Features0-10+00
629Feature-List-IdNN00
630Feature-ListNN00
909RAI0-1000
1001Charging-Rule-Install00+0+0
1002Charging-Rule-Remove00+0+0
1003Charging-Rule-Definition0NN0
1005Charging-Rule-NameNNNN
1006Event-Trigger0+0+0+0
1010Precedence0NN0
1014ToS-Traffic-Class0NN0
1016QoS-Information0-10-1, N0-1, N0
1018Charging-Rule-Report0+000+
1019PCC-Rule-StatusN00N
1025Guaranteed-Bitrate-DL0NN0
1026Guaranteed-Bitrate-UL0NN0
1027IP-CAN-Type0-1000-1
1028QoS-Class-Identifier0NN0
1031Rule-Failure-CodeN00N
1032RAT-Type0-1000-1
1033Event-Report-Indication000-10
1040APN-Aggregate-Max-Bitrate-DLNNN0
1041APN-Aggregate-Max-Bitrate-ULNNN0
1045Session-Release-Cause000-10
1050AN-GW-Address0-1000-1
1058Flow-Information00+0+0
1065PDN-Connection-ID0-1000
1066Monitoring-KeyNNN0
1067Usage-Monitoring-Information0+0+0+0
1068Usage-Monitoring-Level0NN0
1069Usage-Monitoring-Report0NN0
1070Usage-Monitoring-Support0NN0
1080Flow-Direction0NN0
1085Redirect-Information00-10-10
1086Redirect-Support0NN0
1088TDF-Application-Identifier0NN0
1092ADC-Rule-Install00+0+0
1093ADC-Rule-Remove0000
1094ADC-Rule-Definition0000
1096ADC-Rule-NameNNNN
1097ADC-Rule-Report0+0+00+
2848Extended-APN-AMBR-DL0NN0
2849Extended-APN-AMBR-UL0NN0
2850Extended-GBR-DL0NN0
2850Extended-GBR-UL0NN0

Codes wyników (Result-Code AVP)

Tabela 3-7: Codes wyników (Result-Code AVP)

Result Code IdResult Code NameDescriptionSuccess
Success
2001DIAMETER_SUCCESSŻądanie was successfully completed.
Protocol Errors
3001DIAMETER_COMMAND_UNSUPPORTEDRx: traktowane jako błąd. Tx: nieobsługiwane.
3002DIAMETER_UNABLE_TO_DELIVERRx: peer failover procedure on the Diameter base level is invoked. After the same response (3002) is received from all eligible peers, the application level (NASREQ/Gx/Gy) is notified. The message can then be retransmitted one last time with the destination-host AVP cleared. For a message to be retransmitted on the application level, server failover procedure must be enabled. Tx: diameter base replies with 3002 if it cannot route the received request message to its destination (this applies to Diameter multi-chassis configuration).
3003DIAMETER_REALM_NOT_SERVEDRx: traktowane jako błąd. Tx: nieobsługiwane.
3004DIAMETER_TOO_BUSYRx - The peer failover procedure on the Diameter base level is invoked. After the same response (3004) is received from all eligible peers, the application level (NASREQ, Gx, Gy) is notified. The message can then be retransmitted one last time with the destination-host AVP cleared. For a message to be retransmitted on the application level, server failover procedure must be enabled. Tx: nieobsługiwane.
3005DIAMETER_LOOP_DETECTEDRx: traktowane jako błąd. Tx: nieobsługiwane.
3006DIAMETER_REDIRECT_INDICATIONRx: traktowane jako błąd. Tx: nieobsługiwane.
3007DIAMETER_APPLICATION_UNSUPPORTEDRx: traktowane jako błąd. Tx: nieobsługiwane.
3008DIAMETER_INVALID_HDR_BITSRx: traktowane jako błąd. Tx: nieobsługiwane.
3009DIAMETER_INVALID_AVP_BITSRx: traktowane jako błąd. Tx: nieobsługiwane.
3010DIAMETER_UNKNOWN_PEERRx: traktowane jako błąd. Tx: nieobsługiwane.
Permanent Failures
5001DIAMETER_AVP_UNSUPPORTEDRx: traktowane jako błąd. Tx: Reception of an unrecognized AVP with M-bit set triggers a response (RAA) message that contains the Result-Code AVP whose value is set to DIAMETER_AVP_UNSUPORTED, and the Failed-AVP AVP containing the offending AVP.
5002DIAMETER_UNKNOWN_SESSIONRx: traktowane jako błąd. Tx: In case that a message from PCRF is received for a non-existing session, the 7750 SR replies with this value.
5004DIAMETER_INVALID_AVP_VALUERx: traktowane jako błąd. Tx: Reception of an AVP with invalid value triggers a response message (RAA) that contains the Result-Code AVP whose value is set to DIAMETER_INVALID_AVP_VALUE, and the Failed-AVP containing the AVP that caused the error.
5005DIAMETER_MISSING_AVPRx: traktowane jako błąd. Tx: nieobsługiwane.
5007DIAMETER_CONTRADICTING_AVPSRx: traktowane jako błąd. Tx: nieobsługiwane.
5008DIAMETER_AVP_NOT_ALLOWEDRx: traktowane jako błąd. Tx: nieobsługiwane.
5009DIAMETER_AVP_OCCURS_TOO_MANY_TIMESRx: traktowane jako błąd. Tx: nieobsługiwane.
5010DIAMETER_NO_COMMON_APPLICATIONRx: traktowane jako błąd. Tx: nieobsługiwane.
5011DIAMETER_UNSUPPORTED_VERSIONRx: traktowane jako błąd. Tx: As an example, a RAA message carries this AVP as a response to a RAR message that was received by a SR OS node while the Gx session was in a session terminating state. A session terminating state is considered a state where the SR OS node is waiting for a CCA-T message as a response to a previously initiated CCR-T message by the SR OS node.
5012DIAMETER_UNABLE_TO_COMPLYRx: traktowane jako błąd. Tx: For example, a RAA message carries this AVP as a response to a RAR message that was received by a SR OS node while the Gx session was in a session terminating state. A session terminating state is considered a state where the SR OS node is waiting for a CCA-T message as a response to a previously initiated CCR-T message by the SR OS node.
5013DIAMETER_INVALID_BIT_IN_HEADERRx: traktowane jako błąd. Tx: nieobsługiwane.
5014DIAMETER_INVALID_AVP_LENGTHRx: traktowane jako błąd. Tx: nieobsługiwane.
5015DIAMETER_INVALID_MESSAGE_LENGTHRx: traktowane jako błąd. Tx: nieobsługiwane.
5016DIAMETER_INVALID_AVP_BIT_COMBORx: traktowane jako błąd. Tx: nieobsługiwane.
5017DIAMETER_NO_COMMON_SECURITYRx: traktowane jako błąd. Tx: nieobsługiwane.
Gx Specific Permanent Failures
5140DIAMETER_ERROR_INITIAL_PARAMETERSRx: traktowane jako błąd. Tx: nieobsługiwane.
5141DIAMETER_ERROR_TRIGGER_EVENTRx: traktowane jako błąd. Tx: nieobsługiwane.
5142DIAMETER_PCC_RULE_EVENTRx: traktowane jako błąd. Tx: nieobsługiwane.
5148DIAMETER_ADC_RULE_EVENTRx: traktowane jako błąd. Tx: nieobsługiwane.

Codes niepowodzenia reguł (Rule-Failure-Code AVP)

Tabela 3-8: Codes niepowodzenia reguł (Rule-Failure-Code AVP)

Reguła Failure Code IdReguła Failure NameDescription
1UNKNOWN_RULE_NAMERx: traktowane jako błąd. Tx: nieobsługiwane.
4GW/7750 SR_MALFUNCTIONTa wartość wskazuje the problem related to the value carried in the AVP. For example, the value references a non-existing object (rule), the value is out of bounds or any other unexpected error. The error-message AVP in CCR/RAA carried on the top level or Failed-AVP provides more information about the event for debugging purposes.
5RESOURCE_LIMITATIONRx: traktowane jako błąd. Tx: nieobsługiwane.
14TDF_APPLICATION_IDENTIFIER_ERRORRx: traktowane jako błąd. Tx: nieobsługiwane.

Wyzwalacze zdarzeń (Event-Trigger AVP)

Tabela 3-9: Wyzwalacze zdarzeń (Event-Trigger AVP)

Event Trigger IdEvent Trigger NameDescription
2RAT_CHANGEDla dostępu GTP S11, this is triggered if a new RAT Type is received in GTP.
13USER_LOCATION_CHANGEDla WLAN-GW, this is triggered for any UE location change. Dla dostępu GTP S11, this is triggered if a ULI was received in GTP with either non-ECGI/TAI values or a ECGI/TAI value that changed.
14NO_EVENT_TRIGGERSSent in CCA and RAR by the PCRF to indicate that PCRF does not require any Event Trigger notification except for those events that do not require subscription and are always provisioned.
18UE_IP_ADDRESS_ALLOCATEWhen used in a CCR command, this value indicates that the 7750 SR generated the request because a client’s IPv4 address is allocated. The Framed-IP-Address, Framed-IPv6-Prefix, Delegated-IPv6-Prefix or Alc-IPv6-Address AVPs is provided in the same request. This event trigger is reported when the corresponding event occurs, even if the event trigger is not provisioned by the PCRF.
19UE_IP_ADDRESS_RELEASEWhen used in a CCR command, this value indicates that the 7750 SR generated the request because a client’s IP address/prefix is released. The Framed-IP-Address, Framed-IPv6-Prefix, Delegated-IPv6-Prefix or Alc-IPv6-Address AVPs is provided in the same request. This event trigger shall be reported when the corresponding event occurs, even if the event trigger is not provisioned by the PCRF.
21AN_GW_CHANGEThis value is sent by the PCRF to inform the Diameter client in the SR to trigger a notification for every subscriber during a switchover in a multi-chassis configuration. This notification contains the IP address of the newly active BNG (AN_GW_ADDRESS) sent in a CCR-U message. If the Diameter client in the SR OS node is not armed with this event-trigger, the subscriber switchover is not reported to the PCRF.
22SUCCESSFUL_RESOURCE_ALLOCATIONNieobsługiwane.
26TAI_CHANGEDla dostępu GTP S11, this is triggered if a ULI is signaled in GTP with a TAI that changed from the last value received.
27ECGI_CHANGEDla dostępu GTP S11, this is triggered if a ULI is signaled in GTP with a ECGI that changed from the last value received.
33USAGE_REPORTTa wartość jest używana in a CCA and RAR commands by the PCRF when requesting usage monitoring on the 7750 SR. The PCRF also provides in the CCA or RAR command the Usage-Monitoring-Information AVPs including the Monitoring-Key AVP and the Granted-Service-Unit AVP. When used in a CCR command, this value indicates that the 7750 SR generated the request to report the accumulated usage for one or more monitoring keys. The 7750 SR provides the accumulated usage volume using the Usage-Monitoring-Information AVPs including the Monitoring-Key AVP and the Used-Service-Unit AVP.

Przyczyny zakończenia (Termination-Cause AVP)

Tabela 3-10: Przyczyny zakończenia (Termination-Cause AVP)

Termination Cause IdTermination Cause NameDescriptionReference
1DIAMETER_LOGOUTExample reasons: Clear subscriber via CLI, PADT Received[RFC 3588][RFC 6733]
2DIAMETER_SERVICE_NOT_PROVIDEDExample reason: Subscriber-host is terminated via force-NACK received via RADIUS CoA[RFC 3588][RFC 6733]
3DIAMETER_BAD_ANSWERExample reason: Problem with initial parameters during sub-host instantiation while Gx fallback is disabled or default subscriber parameters are not available.[RFC 3588][RFC 6733]
4DIAMETER_ADMINISTRATIVEExample reasons: Host deleted via RADIUS DISCONNECT, Service shutdown for PPPoE subscriber[RFC 3588][RFC 6733]
5DIAMETER_LINK_BROKENExample reasons: SAP is deleted, SHCV check fails[RFC 3588][RFC 6733]
8DIAMETER_SESSION_TIMEOUTExample reason: When idle timeout for the subscriber-host is enabled and its value is reached.[RFC 3588][RFC 6733]

Support standardów i protokołów

Access Node Control Protocol (ANCP)

draft-ietf-ancp-protocol-02, Protocol for Access Node Control Mechanism in Broadband Networks

RFC 5851, Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks

Application Assurance (AA)

3GPP Release 12, ADC reguły over Gx interfaces

RFC 3507, Internet Content Adaptation Protocol (ICAP)

Asynchronous Transfer Mode (ATM)

AF-ILMI-0065.000 Version 4.0, Integrated Local Management Interface (ILMI)

AF-PHY-0086.001 Version 1.1, Inverse Multiplexing for ATM (IMA) Specification

AF-TM-0121.000 Version 4.1, Traffic Management Specification

GR-1113-CORE Issue 1, Asynchronous Transfer Mode (ATM) and ATM Adaptation Layer (AAL) Protocols Generic Requirements

GR-1248-CORE Issue 3, Generic Requirements for Operations of ATM Network Elements (NEs)

RFC 1626, Domyślne IP MTU for use over ATM AAL5

RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5

Bidirectional Forwarding Detection (BFD)

draft-ietf-idr-bgp-ls-sbfd-extensions-01, BGP Link-State Extensions for Seamless BFD

RFC 5880, Bidirectional Forwarding Detection (BFD)

RFC 5881, Bidirectional Forwarding Detection (BFD) IPv4 and IPv6 (Single Hop)

RFC 5882, Generic Application of Bidirectional Forwarding Detection (BFD)

RFC 5883, Bidirectional Forwarding Detection (BFD) for Multihop Paths

RFC 7130, Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces

RFC 7880, Seamless Bidirectional Forwarding Detection (S-BFD)

RFC 7881, Seamless Bidirectional Forwarding Detection (S-BFD) for IPv4, IPv6, and MPLS

RFC 7883, Advertising Seamless Bidirectional Forwarding Detection (S-BFD) Discriminators in IS-IS

RFC 7884, OSPF Extensions to Advertise Seamless Bidirectional Forwarding Detection (S-BFD) Cel Discriminators

Border Gateway Protocol (BGP)

draft-hares-idr-update-attrib-low-bits-fix-01, Update Attribute Flag Low Bits Clarification

draft-ietf-idr-add-paths-guidelines-08, Best Practices for Advertisement of Multiple Paths in IBGP

draft-ietf-idr-best-external-03, Advertisement of the best external route in BGP

draft-ietf-idr-bgp-flowspec-oid-03, Revised Validation Procedure for BGP Flow Specifications

draft-ietf-idr-bgp-gr-notification-01, Notification Message support for BGP Graceful Restart

draft-ietf-idr-bgp-ls-app-specific-attr-01, Application Specific Attributes Advertisement with BGP Link-State

draft-ietf-idr-bgp-optimal-route-reflection-10, BGP Optimal Route Reflection (BGP-ORR)

draft-ietf-idr-error-handling-03, Revised Error Support for BGP Update Messages

draft-ietf-idr-flowspec-interfaceset-03, Applying BGP flowspec reguły on a specific interface set

draft-ietf-idr-flowspec-path-redirect-05, Flowspec Indirection-id Redirect - localised ID

draft-ietf-idr-flowspec-redirect-ip-02, BGP Flow-Spec Redirect to IP Action

draft-ietf-idr-link-bandwidth-03, BGP Link Bandwidth Extended Community

draft-ietf-idr-long-lived-gr-00, Support for Long-lived BGP Graceful Restart

draft-ietf-sidr-origin-validation-signaling-04, BGP Prefix Origin Validation State Extended Community

RFC 1772, Application of the Border Gateway Protocol in the Internet

RFC 1997, BGP Communities Attribute

RFC 2385, Protection of BGP Sessions via the TCP MD5 Signature Option

RFC 2439, BGP Route Flap Damping

RFC 2545, Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing

RFC 2858, Multiprotocol Extensions for BGP-4

RFC 2918, Route Refresh Capability for BGP-4

RFC 3107, Carrying Label Information in BGP-4

RFC 4271, A Border Gateway Protocol 4 (BGP-4)

RFC 4360, BGP Extended Communities Attribute

RFC 4364, BGP/MPLS IP Virtual Private Networks (VPNs)

RFC 4456, BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)

RFC 4486, Subcodes for BGP Cease Notification Message

RFC 4659, BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN

RFC 4684, Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)

RFC 4724, Graceful Restart Mechanism for BGP - helper mode

RFC 4760, Multiprotocol Extensions for BGP-4

RFC 4798, Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)

RFC 5004, Avoid BGP Best Path Transitions from One External to Another

RFC 5065, Autonomous System Confederations for BGP

RFC 5291, Outbound Route Filtering Capability for BGP-4

RFC 5396, Textual Representation of Autonomous System (AS) Numbers - asplain

RFC 5492, Capabilities Advertisement with BGP-4

RFC 5549, Advertising IPv4 Network Layer Reachability Information with an IPv6 Next Hop

RFC 5575, Dissemination of Flow Specification Rules

RFC 5668, 4-Octet AS Specific BGP Extended Community

RFC 6286, Autonomous-System-Wide Unique BGP Identyfikator for BGP-4

RFC 6793, BGP Support for Four-Octet Autonomous System (AS) Numer Space

RFC 6810, The Resource Public Key Infrastructure (RPKI) to Router Protocol

RFC 6811, Prefix Origin Validation

RFC 6996, Autonomous System (AS) Reservation for Private Use

RFC 7311, The Accumulated IGP Metric Attribute for BGP

RFC 7607, Codification of AS 0 Processing

RFC 7674, Clarification of the Flowspec Redirect Extended Community

RFC 7752, North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP

RFC 7854, BGP Monitoring Protocol (BMP)

RFC 7911, Advertisement of Multiple Paths in BGP

RFC 7999, BLACKHOLE Community

RFC 8092, BGP Large Communities Attribute

RFC 8212, Domyślne External BGP (EBGP) Route Propagation Behavior without Policies

RFC 8571, BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions

Broadband Network Gateway (BNG) - Control and User Plane Separation (CUPS)

3GPP 23.007, Restoration procedures

3GPP 29.244, Interface between the Control Plane and the User Plane nodes

3GPP 29.281, General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)

BBF TR-459, Control and User Plane Separation for a Disaggregated BNG

RFC 8300, Network Service Header (NSH)

Circuit Emulation

RFC 4553, Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP)

RFC 5086, Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN)

RFC 5287, Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS Networks

Ethernet

IEEE 802.1AB, Station and Media Access Control Connectivity Discovery

IEEE 802.1ad, Provider Bridges

IEEE 802.1ag, Connectivity Fault Management

IEEE 802.1ah, Provider Backbone Bridges

IEEE 802.1ak, Multiple Registration Protocol

IEEE 802.1aq, Shortest Path Bridging

IEEE 802.1ax, Link Aggregation

IEEE 802.1D, MAC Bridges

IEEE 802.1p, Traffic Class Expediting

IEEE 802.1Q, Virtual LANs

IEEE 802.1s, Multiple Spanning Trees

IEEE 802.1w, Rapid Reconfiguration of Spanning Tree

IEEE 802.1X, Port Based Network Access Control

IEEE 802.3ac, VLAN Tag

IEEE 802.3ad, Link Aggregation

IEEE 802.3ah, Ethernet in the First Mile

IEEE 802.3x, Ethernet Flow Control

ITU-T G.8031/Y.1342, Ethernet Linear Protection Switching

ITU-T G.8032/Y.1344, Ethernet Ring Protection Switching

ITU-T Y.1731, OAM functions and mechanisms for Ethernet based networks

Ethernet VPN (EVPN)

draft-ietf-bess-evpn-igmp-mld-proxy-05, IGMP and MLD Proxy for EVPN

draft-ietf-bess-evpn-irb-mcast-04, EVPN Optimized Inter-Subnet Multicast (OISM) Forwarding - ingress replication

draft-ietf-bess-evpn-pref-df-06, Preference-based EVPN DF Election

draft-ietf-bess-evpn-prefix-advertisement-11, IP Prefix Advertisement in EVPN

draft-ietf-bess-evpn-proxy-arp-nd-08, Operational Aspects of Proxy-ARP/ND in EVPN Networks

draft-ietf-bess-pbb-evpn-isid-cmacflush-00, PBB-EVPN ISID-based CMAC-Flush

RFC 7432, BGP MPLS-Based Ethernet VPN

RFC 7623, Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)

RFC 8214, Virtual Private Wire Service Support in Ethernet VPN

RFC 8317, Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) an Provider Backbone Bridging EVPN (PBB-EVPN)

RFC 8365, A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)

RFC 8560, Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) Equivalents

RFC 8584, DF Election and AC-influenced DF Election

Frame Relay

ANSI T1.617 Annex D, DSS1 - Signalling Specification For Frame Relay Bearer Service

FRF.1.2, PVC User-to-Network Interface (UNI) Implementation Agreement

FRF.12, Frame Relay Fragmentation Implementation Agreement

FRF.16.1, Multilink Frame Relay UNI/NNI Implementation Agreement

FRF.5, Frame Relay/ATM PVC Network Interworking Implementation

FRF2.2, PVC Network-to-Network Interface (NNI) Implementation Agreement

ITU-T Q.933 Annex A, Additional procedures for Permanent Virtual Connection (PVC) status management

Generalized Multiprotocol Label Switching (GMPLS)

draft-ietf-ccamp-rsvp-te-srlg-collect-04, RSVP-TE Extensions for Collecting SRLG Information

RFC 3471, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description

RFC 3473, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions

RFC 4204, Link Management Protocol (LMP)

RFC 4208, Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model

RFC 4872, RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery

RFC 5063, Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart - helper mode

gRPC Remote Procedure Calls (gRPC)

cert.proto Version 0.1.0, gRPC Network Operations Interface (gNOI) Certificate Management Service

file.proto Version 0.1.0, gRPC Network Operations Interface (gNOI) File Service

gnmi.proto Version 0.7.0, gRPC Network Management Interface (gNMI) Service Specification

PROTOCOL-HTTP2, gRPC over HTTP2

system.proto Version 1.0.0, gRPC Network Operations Interface (gNOI) System Service

Intermediate System to Intermediate System (IS-IS)

draft-ietf-isis-mi-02, IS-IS Multi-Instance

draft-kaplan-isis-ext-eth-02, Extended Ethernet Frame Size Support

ISO/IEC 10589:2002 Second Edition, Intermediate system to Intermediate system intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473)

RFC 1195, Use of OSI IS-IS for Routing in TCP/IP and Dual Environments

RFC 2973, IS-IS Mesh Groups

RFC 3359, *Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate System

RFC 3719, Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS)

RFC 3787, Recommendations for Interoperable IP Networks using Intermediate System to Intermediate System (IS-IS)

RFC 4971, Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information

RFC 5120, M-ISIS: Multi Topology (MT) Routing in IS-IS

RFC 5130, A Policy Control Mechanism in IS-IS Using Administrative Tags

RFC 5301, Dynamic Hostname Exchange Mechanism for IS-IS

RFC 5302, Domain-wide Prefix Distribution with Two-Level IS-IS

RFC 5303, Three-Way Handshake for IS-IS Point-to-Point Adjacencies

RFC 5304, IS-IS Cryptographic Authentication

RFC 5305, IS-IS Extensions for Traffic Engineering TE

RFC 5306, Restart Signaling for IS-IS - helper mode

RFC 5307, IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)

RFC 5308, Routing IPv6 with IS-IS

RFC 5309, Point-to-Point Operacja over LAN in Link State Routing Protocols

RFC 5310, IS-IS Generic Cryptographic Authentication

RFC 6119, IPv6 Traffic Engineering in IS-IS

RFC 6213, IS-IS BFD-Enabled TLV

RFC 6232, Purge Originator Identification TLV for IS-IS

RFC 6233, IS-IS Registry Extension for Purges

RFC 6329, IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging

RFC 7775, IS-IS Route Preference for Extended IP and IPv6 Reachability

RFC 7794, IS-IS Prefix Attributes for Extended IPv4 and IPv6 Reachability

RFC 7987, IS-IS Minimum Remaining Lifetime

RFC 8202, IS-IS Multi-Instance - single topology

RFC 8570, IS-IS Traffic Engineering (TE) Metric Extensions - delay metric

RFC 8919, IS-IS Application-Specific Link Attributes

Internet Protocol (IP) — Fast Reroute

draft-ietf-rtgwg-lfa-manageability-08, Operational management of Loop Free Alternates

RFC 5286, Basic Specification for IP Fast Reroute: Loop-Free Alternates

RFC 7431, Multicast-Only Fast Reroute

RFC 7490, Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)

Internet Protocol (IP) — Informacje ogólne

draft-grant-tacacs-02, The TACACS+ Protocol

RFC 768, User Datagram Protocol

RFC 793, Transmission Control Protocol

RFC 854, Telnet Protocol Specifications

RFC 1350, The TFTP Protocol (revision 2)

RFC 2347, TFTP Option Extension

RFC 2348, TFTP Blocksize Option

RFC 2349, TFTP Timeout Interval and Transfer Size Options

RFC 2428, FTP Extensions for IPv6 and NATs

RFC 2784, Generic Routing Encapsulation (GRE)

RFC 2818, HTTP Over TLS

RFC 2890, Key and Sequence Numer Extensions to GRE

RFC 3164, The BSD syslog Protocol

RFC 4250, The Secure Shell (SSH) Protocol Assigned Numbers

RFC 4251, The Secure Shell (SSH) Protocol Architecture

RFC 4252, The Secure Shell (SSH) Authentication Protocol - publickey, password

RFC 4253, The Secure Shell (SSH) Transport Layer Protocol

RFC 4254, The Secure Shell (SSH) Connection Protocol

RFC 4511, Lightweight Directory Access Protocol (LDAP): The Protocol

RFC 4513, Lightweight Directory Access Protocol (LDAP): Authentication Metody and Security Mechanisms - TLS

RFC 4632, Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan

RFC 5082, The Generalized TTL Security Mechanism (GTSM)

RFC 5246, The Transport Layer Security (TLS) Protocol Version 1.2 - TLS client, RSA public key

RFC 5656, Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer - ECDSA

RFC 5925, The TCP Authentication Option

RFC 5926, Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)

RFC 6398, IP Router Alert Considerations and Usage - MLD

RFC 6528, Defending against Sequence Numer Attacks

RFC 7011, Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information

RFC 7012, Information Model for IP Flow Information Export

RFC 7230, Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing

RFC 7231, Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content

RFC 7232, Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests

RFC 7301, Transport Layer Security (TLS) Application Layer Protocol Negotiation Extension

Internet Protocol (IP) — Multicast

cisco-ipmulticast/pim-autorp-spec01, Auto-RP: Automatic discovery of Group-to-RP mappings for IP multicast - version 1

draft-ietf-bier-pim-signaling-08, PIM Signaling Through BIER Core

draft-ietf-idmr-traceroute-ipm-07, A “traceroute” facility for IP Multicast

draft-ietf-l2vpn-vpls-pim-snooping-07, Protocol Independent Multicast (PIM) over Virtual Private LAN Service (VPLS)

RFC 1112, Host Extensions for IP Multicasting

RFC 2236, Internet Group Management Protocol, Version 2

RFC 2365, Administratively Scoped IP Multicast

RFC 2375, IPv6 Multicast Address Assignments

RFC 2710, Multicast Listener Discovery (MLD) for IPv6

RFC 3306, Unicast-Prefix-based IPv6 Multicast Addresses

RFC 3376, Internet Group Management Protocol, Version 3

RFC 3446, Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)

RFC 3590, Source Address Selection for the Multicast Listener Discovery (MLD) Protocol

RFC 3618, Multicast Source Discovery Protocol (MSDP)

RFC 3810, Multicast Listener Discovery Version 2 (MLDv2) for IPv6

RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address

RFC 3973, Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised) - auto-RP groups

RFC 4541, Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches

RFC 4604, Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast

RFC 4607, Source-Specific Multicast for IP

RFC 4608, Source-Specific Protocol Independent Multicast in 232/8

RFC 4610, Anycast-RP Using Protocol Independent Multicast (PIM)

RFC 4611, Multicast Source Discovery Protocol (MSDP) Deployment Scenarios

RFC 5059, Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM)

RFC 5186, Internet Group Management Protocol Version 3 (IGMPv3) / Multicast Listener Discovery Version 2 (MLDv2) and Multicast Routing Protocol Interaction

RFC 5384, The Protocol Independent Multicast (PIM) Join Attribute Format

RFC 5496, The Reverse Path Forwarding (RPF) Vector TLV

RFC 6037, Cisco Systems’ Solution for Multicast in MPLS/BGP IP VPNs

RFC 6512, Using Multipoint LDP When the Backbone Has No Route to the Root

RFC 6513, Multicast in MPLS/BGP IP VPNs

RFC 6514, BGP Encodings and Procedures for Multicast in MPLS/IP VPNs

RFC 6515, IPv4 and IPv6 Infrastructure Addresses in BGP Updates for Multicast VPNs

RFC 6516, IPv6 Multicast VPN (MVPN) Support Using PIM Control Plane and Selective Provider Multicast Service Interface (S-PMSI) Join Messages

RFC 6625, Wildcards in Multicast VPN Auto-Discover Routes

RFC 6826, Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Path

RFC 7246, Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Tabela Context

RFC 7385, IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code Points

RFC 7716, Global Tabela Multicast with BGP Multicast VPN (BGP-MVPN) Procedures

RFC 7761, Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)

RFC 8279, Multicast Using Bit Index Explicit Replication (BIER)

RFC 8296, Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks - MPLS encapsulation

RFC 8401, Bit Index Explicit Replication (BIER) Support via IS-IS

RFC 8444, OSPFv2 Extensions for Bit Index Explicit Replication (BIER)

RFC 8487, Mtrace Version 2: Traceroute Facility for IP Multicast

RFC 8534, Explicit Tracking with Wildcard Routes in Multicast VPN - (C-,C-) wildcard

RFC 8556, Multicast VPN Using Bit Index Explicit Replication (BIER)

Internet Protocol (IP) — Version 4

RFC 791, Internet Protocol

RFC 792, Internet Control Message Protocol

RFC 826, An Ethernet Address Resolution Protocol

RFC 951, Bootstrap Protocol (BOOTP) - relay

RFC 1034, Domain Names - Concepts and Facilities

RFC 1035, Domain Names - Implementation and Specification

RFC 1191, Path MTU Discovery - router specification

RFC 1519, Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy

RFC 1534, Interoperation between DHCP and BOOTP

RFC 1542, Clarifications and Extensions for the Bootstrap Protocol

RFC 1812, Requirements for IPv4 Routers

RFC 1918, Address Allocation for Private Internets

RFC 2003, IP Encapsulation within IP

RFC 2131, Dynamic Host Configuration Protocol

RFC 2132, DHCP Options and BOOTP Vendor Extensions

RFC 2401, Security Architecture for Internet Protocol

RFC 3021, Using 31-Bit Prefixes on IPv4 Point-to-Point Links

RFC 3046, DHCP Relay Agent Information Option (Option 82)

RFC 3768, Virtual Router Redundancy Protocol (VRRP)

RFC 4884, Extended ICMP to Support Multi-Part Messages - ICMPv4 and ICMPv6 Time Exceeded

Internet Protocol (IP) — Version 6

RFC 2464, Transmission of IPv6 Packets over Ethernet Networks

RFC 2529, Transmission of IPv6 over IPv4 Domains without Explicit Tunnels

RFC 3122, Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification

RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

RFC 3587, IPv6 Global Unicast Address Format

RFC 3596, DNS Extensions to Support IP version 6

RFC 3633, IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6

RFC 3646, DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)

RFC 3736, Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6

RFC 3971, SEcure Neighbor Discovery (SEND)

RFC 3972, Cryptographically Generated Addresses (CGA)

RFC 4007, IPv6 Scoped Address Architecture

RFC 4193, Unique Local IPv6 Unicast Addresses

RFC 4291, Internet Protocol Version 6 (IPv6) Addressing Architecture

RFC 4443, Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification

RFC 4861, Neighbor Discovery for IP version 6 (IPv6)

RFC 4862, IPv6 Stateless Address Autoconfiguration - router functions

RFC 4890, Recommendations for Filtering ICMPv6 Messages in Firewalls

RFC 4941, Privacy Extensions for Stateless Address Autoconfiguration in IPv6

RFC 5007, DHCPv6 Leasequery

RFC 5095, Deprecation of Type 0 Routing Headers in IPv6

RFC 5722, Support of Overlapping IPv6 Fragments

RFC 5798, Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 - IPv6

RFC 5952, A Recommendation for IPv6 Address Text Representation

RFC 6092, Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service - Internet Control and Management, Upper-Layer Transport Protocols, UDP Filters, IPsec and Internet Key Exchange (IKE), TCP Filters

RFC 6106, IPv6 Router Advertisement Options for DNS Configuration

RFC 6164, Using 127-Bit IPv6 Prefixes on Inter-Router Links

RFC 8021, Generation of IPv6 Atomic Fragments Considered Harmful

RFC 8200, Internet Protocol, Version 6 (IPv6) Specification

RFC 8201, Path MTU Discovery for IP version 6

Internet Protocol Security (IPsec)

draft-ietf-ipsec-isakmp-mode-cfg-05, The ISAKMP Configuration Method

draft-ietf-ipsec-isakmp-xauth-06, Extended Authentication within ISAKMP/Oakley (XAUTH)

RFC 2401, Security Architecture for the Internet Protocol

RFC 2403, The Use of HMAC-MD5-96 within ESP and AH

RFC 2404, The Use of HMAC-SHA-1-96 within ESP and AH

RFC 2405, The ESP DES-CBC Cipher Algorithm With Explicit IV

RFC 2406, IP Encapsulating Security Payload (ESP)

RFC 2407, IPsec Domain of Interpretation for ISAKMP (IPsec DoI)

RFC 2408, Internet Security Association and Key Management Protocol (ISAKMP)

RFC 2409, The Internet Key Exchange (IKE)

RFC 2410, The NULL Encryption Algorithm and Its Use With IPsec

RFC 3526, More Modular Exponential (MODP) Diffie-Hellman group for Internet Key Exchange (IKE)

RFC 3566, The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec

RFC 3602, The AES-CBC Cipher Algorithm and Its Use with IPsec

RFC 3706, A Traffic-Based Method of Detecting Dead Internet Key Exchange (IKE) Peers

RFC 3947, Negotiation of NAT-Traversal in the IKE

RFC 3948, UDP Encapsulation of IPsec ESP Packets

RFC 4106, The Use of Galois/Counter Mode (GCM) in IPsec ESP

RFC 4210, Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)

RFC 4211, Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)

RFC 4301, Security Architecture for the Internet Protocol

RFC 4303, IP Encapsulating Security Payload

RFC 4307, Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)

RFC 4308, Cryptographic Suites for IPsec

RFC 4434, The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)

RFC 4543, The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH

RFC 4868, Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPSec

RFC 4945, The Internet IP Security PKI Profile of IKEv1/ISAKMP, IKEv2 and PKIX

RFC 5019, The Lightweight Online Certificate Status Protocol (OCSP) Profile for High-Volume Environments

RFC 5280, Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile

RFC 5282, Using Authenticated Encryption Algorithms with the Encrypted Payload of the IKEv2 Protocol

RFC 5903, ECP Groups for IKE and IKEv2

RFC 5998, An Extension for EAP-Only Authentication in IKEv2

RFC 6379, Suite B Cryptographic Suites for IPsec

RFC 6380, Suite B Profile for Internet Protocol Security (IPsec)

RFC 6712, Internet X.509 Public Key Infrastructure – HTTP Transfer for the Certificate Management Protocol (CMP)

RFC 6960, X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP

RFC 7296, Internet Key Exchange Protocol Version 2 (IKEv2)

RFC 7321, Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)

RFC 7383, Internet Key Exchange Protocol Version 2 (IKEv2) Message Fragmentation

RFC 7427, Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)

RFC 7468, Textual Encodings of PKIX, PKCS, and CMS Structures

Label Distribution Protocol (LDP)

draft-pdutta-mpls-ldp-adj-capability-00, LDP Adjacency Capabilities

draft-pdutta-mpls-ldp-v2-00, LDP Version 2

draft-pdutta-mpls-mldp-up-redundancy-00, Upstream LSR Redundancy for Multi-point LDP Tunnels

draft-pdutta-mpls-multi-ldp-instance-00, Multiple LDP Instances

draft-pdutta-mpls-tldp-hello-reduce-04, Targeted LDP Hello Reduction

RFC 3037, LDP Applicability

RFC 3478, Graceful Restart Mechanism for Label Distribution Protocol - helper mode

RFC 5036, LDP Specification

RFC 5283, LDP Extension for Inter-Area Label Switched Paths (LSPs)

RFC 5443, LDP IGP Synchronization

RFC 5561, LDP Capabilities

RFC 5919, Signaling LDP Label Advertisement Completion

RFC 6388, Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths

RFC 6512, Using Multipoint LDP When the Backbone Has No Route to the Root

RFC 6826, Multipoint LDP in-band signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths

RFC 7032, LDP Downstream-on-Demand in Seamless MPLS

RFC 7473, Controlling State Advertisements of Non-negotiated LDP Applications

RFC 7552, Updates to LDP for IPv6

Layer Two Tunneling Protocol (L2TP) Network Server (LNS)

draft-mammoliti-l2tp-accessline-avp-04, Layer 2 Tunneling Protocol (L2TP) Access Line Information Attribute Value Pair (AVP) Extensions

RFC 2661, Layer Two Tunneling Protocol “L2TP”

RFC 2809, Implementation of L2TP Compulsory Tunneling via RADIUS

RFC 3438, Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers: Internet Assigned Numbers Authority (IANA) Considerations Update

RFC 3931, Layer Two Tunneling Protocol - Version 3 (L2TPv3)

RFC 4719, Transport of Ethernet Frames over Layer 2 Tunneling Protocol Version 3 (L2TPv3)

RFC 4951, Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP) “failover”

Multiprotocol Label Switching (MPLS)

draft-ietf-mpls-lsp-ping-ospfv3-codepoint-02, OSPFv3 CodePoint for MPLS LSP Ping

RFC 3031, Multiprotocol Label Switching Architecture

RFC 3032, MPLS Label Stack Encoding

RFC 3270, Multi-Protocol Label Switching (MPLS) Support of Differentiated Usługi - E-LSP

RFC 3443, Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks

RFC 4023, Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)

RFC 4182, Removing a Restriction on the use of MPLS Explicit NULL

RFC 5332, MPLS Multicast Encapsulations

RFC 5884, Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)

RFC 6374, Packet Loss and Delay Measurement for MPLS Networks - Delay Measurement, Channel Type 0x000C

RFC 6424, Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels

RFC 6425, Detecting Data Plane Failures in Point-to-Multipoint Multiprotocol Label Switching (MPLS) - Extensions to LSP Ping

RFC 6790, The Use of Entropy Labels in MPLS Forwarding

RFC 7510, Encapsulating MPLS in UDP

RFC 7746, Label Switched Path (LSP) Self-Ping

RFC 7876, UDP Return Path for Packet Loss and Delay Measurement for MPLS Networks - Delay Measurement

RFC 8029, Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures

Multiprotocol Label Switching — Transport Profile (MPLS-TP)

RFC 5586, MPLS Generic Associated Channel

RFC 5921, A Framework for MPLS in Transport Networks

RFC 5960, MPLS Transport Profile Data Plane Architecture

RFC 6370, MPLS Transport Profile (MPLS-TP) Identifiers

RFC 6378, MPLS Transport Profile (MPLS-TP) Linear Protection

RFC 6426, MPLS On-Demand Connectivity and Route Tracing

RFC 6427, MPLS Fault Management Operations, Administration, and Maintenance (OAM)

RFC 6428, Proactive Connectivity Verification, Continuity Check and Remote Defect indication for MPLS Transport Profile

RFC 6478, Pseudowire Status for Static Pseudowires

RFC 7213, MPLS Transport Profile (MPLS-TP) Next-Hop Ethernet Addressing

Network Address Translation (NAT)

draft-ietf-behave-address-format-10, IPv6 Addressing of IPv4/IPv6 Translators

draft-ietf-behave-v6v4-xlate-23, IP/ICMP Translation Algorithm

draft-miles-behave-l2nat-00, Layer2-Aware NAT

draft-nishitani-cgn-02, Common Functions of Large Scale NAT (LSN)

RFC 4787, Network Address Translation (NAT) Behavioral Requirements for Unicast UDP

RFC 5382, NAT Behavioral Requirements for TCP

RFC 5508, NAT Behavioral Requirements for ICMP

RFC 6146, Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers

RFC 6333, Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion

RFC 6334, Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite

RFC 6887, Port Control Protocol (PCP)

RFC 6888, Common Requirements For Carrier-Grade NATs (CGNs)

RFC 7753, Port Control Protocol (PCP) Extension for Port-Set Allocation

RFC 7915, IP/ICMP Translation Algorithm

Network Configuration Protocol (NETCONF)

RFC 5277, NETCONF Event Powiadomienia

RFC 6020, YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)

RFC 6022, YANG Module for NETCONF Monitoring

RFC 6241, Network Configuration Protocol (NETCONF)

RFC 6242, Using the NETCONF Protocol over Secure Shell (SSH)

RFC 6243, With-defaults Capability for NETCONF

RFC 8342, Network Management Datastore Architecture (NMDA) - Startup, Candidate, Running and Intended datastores

RFC 8525, YANG Library

RFC 8526, NETCONF Extensions to Support the Network Management Datastore Architecture - operacja

Open Shortest Path First (OSPF)

RFC 1586, Guidelines for Running OSPF Over Frame Relay Networks

RFC 1765, OSPF Database Overflow

RFC 2328, OSPF Version 2

RFC 3101, The OSPF Not-So-Stubby Area (NSSA) Option

RFC 3509, Alternative Implementations of OSPF Area Border Routers

RFC 3623, Graceful OSPF Restart Graceful OSPF Restart - helper mode

RFC 3630, Traffic Engineering (TE) Extensions to OSPF Version 2

RFC 4203, OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)

RFC 4222, Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion Avoidance

RFC 4552, Authentication/Confidentiality for OSPFv3

RFC 4576, Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)

RFC 4577, OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)

RFC 5185, OSPF Multi-Area Adjacency

RFC 5187, OSPFv3 Graceful Restart - helper mode

RFC 5243, OSPF Database Exchange Podsumowanie List Optimization

RFC 5250, The OSPF Opaque LSA Option

RFC 5309, Point-to-Point Operacja over LAN in Link State Routing Protocols

RFC 5340, OSPF for IPv6

RFC 5642, Dynamic Hostname Exchange Mechanism for OSPF

RFC 5709, OSPFv2 HMAC-SHA Cryptographic Authentication

RFC 5838, Support of Address Families in OSPFv3

RFC 6549, OSPFv2 Multi-Instance Extensions

RFC 6987, OSPF Stub Router Advertisement

RFC 7684, OSPFv2 Prefix/Link Attribute Advertisement

RFC 7770, Extensions to OSPF for Advertising Opcjonalne Router Capabilities

RFC 8362, OSPFv3 Link State Advertisement (LSA) Extensibility

RFC 8920, OSPF Application-Specific Link Attributes

OpenFlow

TS-007 Version 1.3.1, OpenFlow Switch Specification - OpenFlow-hybrid switches

Path Computation Element Protocol (PCEP)

draft-alvarez-pce-path-profiles-04, PCE Path Profiles

draft-dhs-spring-pce-sr-p2mp-policy-00, PCEP extensions for p2mp sr policy

draft-ietf-pce-segment-routing-08, PCEP Extensions for Segment Routing

RFC 5440, Path Computation Element (PCE) Communication Protocol (PCEP)

RFC 8281, PCEP Extensions for PCE-initiated LSP Setup in a Stateful PCE Model

RFC 8321, Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE

Point-to-Point Protocol (PPP)

RFC 1332, The PPP Internet Protocol Control Protocol (IPCP)

RFC 1377, The PPP OSI Network Layer Control Protocol (OSINLCP)

RFC 1661, The Point-to-Point Protocol (PPP)

RFC 1662, PPP in HDLC-like Framing

RFC 1877, PPP Internet Protocol Control Protocol Extensions for Name Server Addresses

RFC 1989, PPP Link Quality Monitoring

RFC 1990, The PPP Multilink Protocol (MP)

RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP)

RFC 2153, PPP Vendor Extensions

RFC 2516, A Method for Transmitting PPP Over Ethernet (PPPoE)

RFC 2615, PPP over SONET/SDH

RFC 2686, The Multi-Class Extension to Multi-Link PPP

RFC 2878, PPP Bridging Control Protocol (BCP)

RFC 4638, Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU) Greater Than 1492 in the Point-to-Point Protocol over Ethernet (PPPoE)

RFC 5072, IP Version 6 over PPP

Policy Management and Credit Control

3GPP TS 29.212 Release 11, Policy and Charging Control (PCC); Reference points - Gx support as it applies to wireline environment (BNG)

RFC 4006, Diameter Credit-Control Application

RFC 6733, Diameter Base Protocol

Pseudowire

draft-ietf-l2vpn-vpws-iw-oam-04, OAM Procedures for VPWS Interworking

MFA Forum 9.0.0, The Use of Virtual trunks for ATM/MPLS Control Plane Interworking

MFA Forum 12.0.0, Multiservice Interworking - Ethernet over MPLS

MFA Forum 13.0.0, Fault Management for Multiservice Interworking v1.0

MFA Forum 16.0.0, Multiservice Interworking - IP over MPLS

RFC 3916, Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)

RFC 3985, Pseudo Wire Emulation Edge-to-Edge (PWE3)

RFC 4385, Pseudo Wire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN

RFC 4446, IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)

RFC 4447, Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)

RFC 4448, Encapsulation Metody for Transport of Ethernet over MPLS Networks

RFC 4619, Encapsulation Metody for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) Networks

RFC 4717, Encapsulation Metody for Transport Asynchronous Transfer Mode (ATM) over MPLS Networks

RFC 4816, Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport Service

RFC 5085, Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control Channel for Pseudowires

RFC 5659, An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge

RFC 5885, Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)

RFC 6073, Segmented Pseudowire

RFC 6310, Pseudowire (PW) Operations, Administration, and Maintenance (OAM) Message Mapping

RFC 6391, Flow-Aware Transport of Pseudowires over an MPLS Packet Switched Network

RFC 6575, Address Resolution Protocol (ARP) Mediation for IP Interworking of Layer 2 VPNs

RFC 6718, Pseudowire Redundancy

RFC 6829, Label Switched Path (LSP) Ping for Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6

RFC 6870, Pseudowire Preferential Forwarding Status bit

RFC 7023, MPLS and Ethernet Operations, Administration, and Maintenance (OAM) Interworking

RFC 7267, Dynamic Placement of Multi-Segment Pseudowires

RFC 7392, Explicit Path Routing for Dynamic Multi-Segment Pseudowires - ER-TLV and ER-HOP IPv4 Prefix

Quality of Service (QoS)

RFC 2430, A Provider Architecture for Differentiated Usługi and Traffic Engineering (PASTE)

RFC 2474, Definition of the Differentiated Usługi Field (DS Field) in the IPv4 and IPv6 Headers

RFC 2597, Assured Forwarding PHB Group

RFC 3140, Per Hop Behavior Identification Codes

RFC 3246, An Expedited Forwarding PHB (Per-Hop Behavior)

Remote Authentication Dial In User Service (RADIUS)

RFC 2865, Remote Authentication Dial In User Service (RADIUS)

RFC 2866, RADIUS Accounting

RFC 2867, RADIUS Accounting Modifications for Tunnel Protocol Support

RFC 2868, RADIUS Attributes for Tunnel Protocol Support

RFC 2869, RADIUS Extensions

RFC 3162, RADIUS and IPv6

RFC 4818, RADIUS Delegated-IPv6-Prefix Attribute

RFC 5176, Dynamic Authorization Extensions to RADIUS

RFC 6911, RADIUS atrybuty for IPv6 Access Networks

RFC 6929, Remote Authentication Dial-In User Service (RADIUS) Protocol Extensions

Resource Reservation Protocol — Traffic Engineering (RSVP-TE)

draft-newton-mpls-te-dynamic-overbooking-00, A Diffserv-TE Implementation Model to dynamically change booking factors during failure events

RFC 2702, Requirements for Traffic Engineering over MPLS

RFC 2747, RSVP Cryptographic Authentication

RFC 2961, RSVP Refresh Overhead Reduction Extensions

RFC 3097, RSVP Cryptographic Authentication – Updated Message Type Value

RFC 3209, RSVP-TE: Extensions to RSVP for LSP Tunnels

RFC 3473, Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions - IF_ID RSVP_HOP object with unnumbered interfaces and RSVP-TE graceful restart helper procedures

RFC 3477, Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)

RFC 3564, Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering

RFC 3906, Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering Tunnels

RFC 4090, Fast Reroute Extensions to RSVP-TE for LSP Tunnels

RFC 4124, Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering

RFC 4125, Maximum Allocation Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering

RFC 4127, Russian Dolls Bandwidth Constraints Model for Diffserv-aware MPLS Traffic Engineering

RFC 4561, Definition of a Record Route Obiekt (RRO) Node-Id Sub-Object

RFC 4875, Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)

RFC 4950, ICMP Extensions for Multiprotocol Label Switching

RFC 5151, Inter-Domain MPLS and GMPLS Traffic Engineering – Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Extensions

RFC 5712, MPLS Traffic Engineering Soft Preemption

RFC 5817, Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks

Routing Information Protocol (RIP)

RFC 1058, Routing Information Protocol

RFC 2080, RIPng for IPv6

RFC 2082, RIP-2 MD5 Authentication

RFC 2453, RIP Version 2

Segment Routing (SR)

draft-bashandy-rtgwg-segment-routing-uloop-06, Loop avoidance using Segment Routing

draft-ietf-idr-bgp-ls-segment-routing-ext-16, BGP Link-State extensions for Segment Routing

draft-ietf-idr-bgp-ls-segment-routing-msd-09, Signaling MSD (Maximum SID Depth) using Border Gateway Protocol Link-State

draft-ietf-idr-segment-routing-te-policy-09, Advertising Segment Routing Policies in BGP

draft-ietf-isis-mpls-elc-10, Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS - advertising ELC

draft-ietf-lsr-flex-algo-08, IGP Flexible Algorithm

draft-ietf-ospf-mpls-elc-12, Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF - advertising ELC

draft-ietf-rtgwg-segment-routing-ti-lfa-01, Topology Independent Fast Reroute using Segment Routing

draft-ietf-spring-conflict-resolution-05, Segment Routing MPLS Conflict Resolution

draft-ietf-spring-segment-routing-policy-08, Segment Routing Policy Architecture

draft-ietf-teas-sr-rsvp-coexistence-rec-02, Recommendations for RSVP-TE and Segment Routing LSP co-existence

draft-voyer-pim-sr-p2mp-policy-02, Segment Routing Point-to-Multipoint Policy

draft-voyer-spring-sr-p2mp-policy-03, SR Replication Policy for P2MP Service Delivery

RFC 8287, Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes

RFC 8476, Signaling Maximum SID Depth (MSD) Using OSPF - node MSD

RFC 8491, Signaling Maximum SID Depth (MSD) Using IS-IS - node MSD

RFC 8660, Segment Routing with the MPLS Data Plane

RFC 8661, Segment Routing MPLS Interworking with LDP

RFC 8663, MPLS Segment Routing over IP - BGP SR with SR-MPLS-over-UDP/IP

RFC 8665, OSPF Extensions for Segment Routing

RFC 8666, OSPFv3 Extensions for Segment Routing

RFC 8667, IS-IS Extensions for Segment Routing

RFC 8669, Segment Routing Prefix Segment Identyfikator Extensions for BGP

Simple Network Management Protocol (SNMP)

RFC 1157, A Simple Network Management Protocol (SNMP)

RFC 1215, A Convention for Defining Traps for use with the SNMP

RFC 1901, Introduction to Community-based SNMPv2

RFC 3410, Introduction and Applicability Statements for Internet Standard Management Framework

RFC 3411, An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks

RFC 3412, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)

RFC 3413, Simple Network Management Protocol (SNMP) Applications

RFC 3414, User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)

RFC 3415, View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)

RFC 3416, Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)

RFC 3417, Transport Mappings for the Simple Network Management Protocol (SNMP) - SNMP over UDP over IPv4

RFC 3584, Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework

RFC 3826, The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model

Simple Network Management Protocol (SNMP) - Management Information Base (MIB)

draft-ietf-snmpv3-update-mib-05, Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)

draft-ietf-isis-wg-mib-06, Management Information Base for Intermediate System to Intermediate System (IS-IS)

draft-ietf-mboned-msdp-mib-01, Multicast Source Discovery protocol MIB

draft-ietf-mpls-ldp-mib-07, *Definitions of Managed Objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP)

draft-ietf-mpls-lsr-mib-06, Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base Using SMIv2

draft-ietf-mpls-te-mib-04, Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base

draft-ietf-ospf-mib-update-08, OSPF Version 2 Management Information Base

draft-ietf-vrrp-unified-mib-06, Definitions of Managed Objects for the VRRP over IPv4 and IPv6 - IPv6

ianaaddressfamilynumbers-mib, IANA-ADDRESS-FAMILY-NUMBERS-MIB

ianagmplstc-mib, IANA-GMPLS-TC-MIB

ianaiftype-mib, IANAifType-MIB

ianaiprouteprotocol-mib, IANA-RTPROTO-MIB

IEEE8021-CFM-MIB, IEEE P802.1ag(TM) CFM MIB

IEEE8021-PAE-MIB, IEEE 802.1X MIB

IEEE8023-LAG-MIB, IEEE 802.3ad MIB

LLDP-MIB, IEEE P802.1AB(TM) LLDP MIB

RFC 1212, Concise MIB Definitions

RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II

RFC 1724, RIP Version 2 MIB Extension

RFC 2021, Remote Network Monitoring Management Information Base Version 2 using SMIv2

RFC 2115, Management Information Base for Frame Relay DTEs Using SMIv2

RFC 2206, RSVP Management Information Base using SMIv2

RFC 2213, Integrated Usługi Management Information Base using SMIv2

RFC 2494, Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type

RFC 2514, Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management

RFC 2515, Definitions of Managed Objects for ATM Management

RFC 2578, Structure of Management Information Version 2 (SMIv2)

RFC 2579, Textual Conventions for SMIv2

RFC 2580, Conformance Statements for SMIv2

RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol

RFC 2819, Remote Network Monitoring Management Information Base

RFC 2856, Textual Conventions for Additional High Capacity Data Types

RFC 2863, The Interfaces Group MIB

RFC 2864, The Inverted Stack Tabela Extension to the Interfaces Group MIB

RFC 2933, Internet Group Management Protocol MIB

RFC 3014, Notification Log MIB

RFC 3165, Definitions of Managed Objects for the Delegation of Management Scripts

RFC 3231, Definitions of Managed Objects for Scheduling Management Operations

RFC 3273, Remote Network Monitoring Management Information Base for High Capacity Networks

RFC 3419, Textual Conventions for Transport Addresses

RFC 3498, Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures

RFC 3592, Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type

RFC 3593, Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals

RFC 3635, Definitions of Managed Objects for the Ethernet-like Interface Types

RFC 3637, Definitions of Managed Objects for the Ethernet WAN Interface Sublayer

RFC 3877, Alarm Management Information Base (MIB)

RFC 3895, Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types

RFC 3896, Definitions of Managed Objects for the DS3/E3 Interface Type

RFC 4001, Textual Conventions for Internet Network Addresses

RFC 4022, Management Information Base for the Transmission Control Protocol (TCP)

RFC 4113, Management Information Base for the User Datagram Protocol (UDP)

RFC 4220, Traffic Engineering Link Management Information Base

RFC 4273, Definitions of Managed Objects for BGP-4

RFC 4292, IP Forwarding Tabela MIB

RFC 4293, Management Information Base for the Internet Protocol (IP)

RFC 4631, Link Management Protocol (LMP) Management Information Base (MIB)

RFC 4878, Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces

RFC 7420, Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) Module

SFLOW-MIB Version 1.3 (Draft 5), sFlow MIB

Timing

GR-1244-CORE Issue 3, Clocks for the Synchronized Network: Common Generic Criteria

GR-253-CORE Issue 3, SONET Transport Systems: Common Generic Criteria

IEEE 1588-2008, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems

ITU-T G.781, Synchronization layer functions

ITU-T G.813, Timing characteristics of SDH equipment slave clocks (SEC)

ITU-T G.8261, Timing and synchronization aspects in packet networks

ITU-T G.8262, Timing characteristics of synchronous Ethernet equipment slave clock (EEC)

ITU-T G.8264, Distribution of timing information through packet networks

ITU-T G.8265.1, Precision time protocol telecom profile for frequency synchronizacja

ITU-T G.8275.1, Precision time protocol telecom profile for phase/time synchronization with full timing support from the network

RFC 3339, Date and Time on the Internet: Timestamps

RFC 5905, Network Time Protocol Version 4: Protocol and Algorithms Specification

Two-Way Active Measurement Protocol (TWAMP)

RFC 5357, A Two-Way Active Measurement Protocol (TWAMP) - server, unauthenticated mode

RFC 5938, Individual Session Control Feature for the Two-Way Active Measurement Protocol (TWAMP)

RFC 6038, Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features

RFC 8545, Well-Known Port Assignments for the One-Way Active Measurement Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP) - TWAMP

RFC 8762, Simple Two-Way Active Measurement Protocol - Unauthenticated

Virtual Private LAN Service (VPLS)

RFC 4761, Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling

RFC 4762, Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling

RFC 5501, Requirements for Multicast Support in Virtual Private LAN Usługi

RFC 6074, Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)

RFC 7041, Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Backbone Bridging

RFC 7117, Multicast in Virtual Private LAN Service (VPLS)

Voice and Video

DVB BlueBook A86, Transport of MPEG-2 TS Based DVB Usługi over IP Based Networks

ETSI TS 101 329-5 Annex E, QoS Measurement for VoIP - Method for determining an Equipment Impairment Factor using Passive Monitoring

ITU-T G.1020 Appendix I, Performance Parameter Definitions for Quality of Speech and other Voiceband Applications Utilizing IP Networks - Mean Absolute Packet Delay Variation & Markov Models

ITU-T G.107, The E Model - A computational model for use in planning

ITU-T P.564, Conformance testing for voice over IP transmission quality assessment models

RFC 3550, RTP: A Transport Protocol for Real-Time Applications - Appendix A.8

RFC 4585, Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)

RFC 4588, RTP Retransmission Payload Format

Wireless Local Area Network (WLAN) Gateway

3GPP TS 23.402, Architecture enhancements for non-3GPP accesses - S2a roaming based on GPRS

Yet Another Next Generation (YANG)

RFC 6991, Common YANG Data Types

RFC 7950, The YANG 1.1 Data Modeling Language

RFC 7951, JSON Encoding of Data Modeled with YANG

Yet Another Next Generation (YANG) - OpenConfig Modules

openconfig-aaa.yang version 0.4.0, OpenConfig AAA Module

openconfig-aaa-radius.yang version 0.3.0, OpenConfig AAA RADIUS Module

openconfig-aaa-tacacs.yang version 0.3.0, OpenConfig AAA TACACS+ Module

openconfig-acl.yang version 1.0.0, OpenConfig ACL Module

openconfig-bfd.yang version 0.1.0, OpenConfig BFD Module

openconfig-bgp.yang version 3.0.1, OpenConfig BGP Module

openconfig-bgp-common.yang version 3.0.1, OpenConfig BGP Common Module

openconfig-bgp-common-multiprotocol.yang version 3.0.1, OpenConfig BGP Common Multiprotocol Module

openconfig-bgp-common-structure.yang version 3.0.1, OpenConfig BGP Common Structure Module

openconfig-bgp-global.yang version 3.0.1, OpenConfig BGP Global Module

openconfig-bgp-neighbor.yang version 3.0.1, OpenConfig BGP Neighbor Module

openconfig-bgp-peer-group.yang version 3.0.1, OpenConfig BGP Peer Group Module

openconfig-bgp-policy.yang version 4.0.1, OpenConfig BGP Policy Module

openconfig-if-aggregate.yang version 2.0.0, OpenConfig Interfaces Aggregated Module

openconfig-if-ethernet.yang version 2.0.0, OpenConfig Interfaces Ethernet Module

openconfig-if-ip.yang version 2.0.0, OpenConfig Interfaces IP Module

openconfig-if-ip-ext.yang version 2.0.0, OpenConfig Interfaces IP Extensions Module

openconfig-interfaces.yang version 2.0.0, OpenConfig Interfaces Module

openconfig-isis.yang version 0.3.0, OpenConfig IS-IS Module

openconfig-isis-policy.yang version 0.3.0, OpenConfig IS-IS Policy Module

openconfig-isis-routing.yang version 0.3.0, OpenConfig IS-IS Routing Module

openconfig-lacp.yang version 1.1.0, OpenConfig LACP Module

openconfig-lldp.yang version 0.1.0, OpenConfig LLDP Module

openconfig-local-routing.yang version 1.0.1, OpenConfig Local Routing Module

openconfig-network-instance.yang version 0.8.0, OpenConfig Network Instance Module

openconfig-mpls.yang version 2.3.0, OpenConfig MPLS Module

openconfig-mpls-rsvp.yang version 2.3.0, OpenConfig MPLS RSVP Module

openconfig-mpls-te.yang version 2.3.0, OpenConfig MPLS TE Module

openconfig-packet-match.yang version 1.0.0, OpenConfig Packet Match Module

openconfig-platform.yang version 0.12.2, OpenConfig Platform Module

openconfig-platform-fan.yang version 0.1.1, OpenConfig Platform Fan Module

openconfig-platform-linecard.yang version 0.1.2, OpenConfig Platform Linecard Module

openconfig-relay-agent.yang version 0.1.0, OpenConfig Relay Agent Module

openconfig-routing-policy.yang version 3.0.0, OpenConfig Routing Policy Module

openconfig-system-logging.yang version 0.3.1, OpenConfig System Logging Module

openconfig-system-terminal.yang version 0.3.0, OpenConfig System Terminal Module

openconfig-telemetry.yang version 0.5.0, OpenConfig Telemetry Module

openconfig-vlan.yang version 2.0.0, OpenConfig VLAN Module

Poprzednia
AAA Gateway
Następna
5G CHF