JBoss.orgCommunity Documentation
Diameter Base Resource Adaptor Type is defined by Mobicents team as part of effort to standardize RA Types.
Diameter Base Type 2.2.1.FINAL defines the following Activities:
This type of activity represents client side of Base Authentication session. Abort-Session-Request (ASR) and Re-Auth-Request (RAR) messages are received in this Activity and respective Answers are sent from it. Session-Termination-Request (STR) can be created and sent in this Activity, receiving the respective Answer (or timeout) later on this Activity.
This activity type can be created with call to the appropriate createAuthenticationClientSessionActivity
method of net.java.slee.resource.diameter.base.DiameterProvider
. It ends once underlying Base Authentication session ends.
State machine for client Base Authorization sessions can be found at Section 8.1 of Diameter Base Protocol RFC.
This type of activity represents server side of Base Authentication session. Session-Termination-Request (STR) messages are received in this Activity and respective Answers are sent from it. Abort-Session-Request (ASR) and Re-Auth-Request (RAR) can be created and sent in this Activity, receiving the respective Answer (or timeout) later on this Activity.
This activity type can be created with call to the appropriate createAuthenticationServerSessionActivity
method of net.java.slee.resource.diameter.base.DiameterProvider
. It ends once underlying Base Authentication session ends.
State machine for client Base Authorization sessions can be found at Section 8.1 of Diameter Base Protocol RFC.
This type of activity represents client side of Base Accounting session. Accounting-Request (ACR) messages can be created and sent in this Activity, receiving the respective Answer (or timeout) later on this Activity.
This activity type can be created with call to the appropriate createAccountingClientSessionActivity
method of net.java.slee.resource.diameter.base.DiameterProvider
. It ends once underlying Base Accounting session ends.
State machine for client Base Accounting sessions can be found at Section 8.2 of Diameter Base Protocol RFC.
This type of activity represents server side of Base Accounting session. Accounting-Request (ACR) messages are received in this Activity and respective Answers are sent from it.
This activity type is created explicitly for incoming requests by Resource Adaptor. It ends once underlying Base Accounting session ends, either by timeout or proper answer delivery.
State machine for server Base Accounting can be found at Section 8.2 of Diameter Base Protocol RFC.
This type of activity represents a generic Diameter session and it's the super type for all other Diameter Activities. It can be used as an extension point for Diameter Applications.
This activity type is created explicitly for unknown (not defined in other Activities) incoming requests by Resource Adaptor or by calling the appropriate createActivity
method of net.java.slee.resource.diameter.base.DiameterProvider
. It ends once underlying session ends, either by timeout or proper answer delivery.
All activities define methods required to properly function and expose necessary information to JAIN SLEE services. Common part for all Diameter Activities is defined as follows:
DiameterMessageFactory getDiameterMessageFactory();
DiameterAvpFactory getDiameterAvpFactory();
void sendMessage(DiameterMessage message) throws IOException;
String getSessionId();
void endActivity();
Returns message factory capable of creating Diameter Base or other (extension) messages.
Returns AVP factory capable of creating Diameter Base or other (extension) AVPs.
Provides means to send generic Diameter messages.
Returns Session ID of underlying Diameter session.
Terminates underlying session.
Common part for Authentication Activities is defined as follows:
AuthSessionState getSessionState();
Return current Auth session state. It can have values as follows:
IDLE
PENDING
OPEN
DISCONNECTED
DISCONNECTED value implies that activity is ending.
Client part for Authentication Activities is defined as follows:
AbortSessionAnswer createAbortSessionAnswer();
AbortSessionAnswer createAbortSessionAnswer(AbortSessionRequest abortSessionRequest);
void sendAbortSessionAnswer(AbortSessionAnswer abortSessionAnswer)
throws IOException, IllegalArgumentException;
ReAuthAnswer createReAuthAnswer();
ReAuthAnswer createReAuthAnswer(ReAuthRequest reAuthRequest);
void sendReAuthAnswer(ReAuthAnswer reAuthAnswer)
throws IOException, IllegalArgumentException;
SessionTerminationRequest createSessionTerminationRequest(
TerminationCauseType terminationCause);
void sendSessionTerminationRequest(
SessionTerminationRequest sessionTerminationRequest)
throws IOException, IllegalArgumentException;
Create an empty Abort-Session-Answer with the Auth-Application-Id set to 0.
Create an Abort-Session-Answer with some AVPs populated from the provided Abort-Session-Request.
Send an Abort-Session-Answer.
Create an empty Re-Auth-Answer with the Auth-Application-Id set to 0.
Create an Re-Auth-Answer with some AVPs populated from the provided Re-Auth-Request.
Send an Re-Auth-Answer.
Create an Session-Termination-Request message populated with the following AVPs:
Send an Session Termination Request. An event containing the answer will be fired on this activity.
Server part for Authentication Activities is defined as follows:
AbortSessionRequest createAbortSessionRequest();
void sendAbortSessionRequest(AbortSessionRequest request) throws IOException;
ReAuthRequest createReAuthRequest(ReAuthRequestType reAuthRequestType);
void sendReAuthRequest(ReAuthRequest request) throws IOException;
SessionTerminationAnswer createSessionTerminationAnswer();
SessionTerminationAnswer createSessionTerminationAnswer(
SessionTerminationRequest sessionTerminationRequest);
void sendSessionTerminationAnswer(SessionTerminationAnswer request)
throws IOException;
Create an Abort-Session-Request message populated with the following AVPs:
Send session abort session request to client
Create an Re-Auth-Request message populated with the following AVPs:
Send Re-Auth-Request.
Create an Session-Termination-Answer with the Auth-Application-Id set to 0.
Create an Session-Termination-Answer with some AVPs populated from the provided Session-Termination-Request.
Send session termination answer to client.
Common part for Accounting Activities is defined as follows:
AccountingSessionState getAccountingSessionState();
Returns current Accounting session state of underlying session. Valid values are:
Idle
PendingS
PendingE
PendingB
Open
PendingI
PendingL
Client part for Accounting Activities is defined as follows:
AccountingRequest createAccountingRequest(AccountingRecordType accountingRecordType);
void sendAccountRequest(AccountingRequest accountingRequest)
throws IOException, IllegalArgumentException;
Create an Accounting-Request message populated with the following AVPs:
Send an Accounting Request. An event containing the answer or timeout will be fired on this activity.
Server part for Accounting Activities is defined as follows:
AccountingAnswer createAccountingAnswer();
AccountingAnswer createAccountingAnswer(AccountingRequest acr);
void sendAccountingAnswer(AccountingAnswer aca)
throws IOException, IllegalArgumentException;
Create an Accounting-Answer with the Acct-Application-Id set to 3.
Create an Accounting-Answer with some AVPs populated from the provided Accounting-Request. The ACA will contain the AVPs specified in createAccountingAnswer() and the following AVPs from the Accounting-Request:
Send an Accounting Answer.
It is safe to type cast all the mentioned Diameter Activities to it's super interface net.java.slee.resource.diameter.base.DiameterActivity
defined in this section.
Diameter Base Resource Adaptor Type declares all the Diameter Base messages but the Peer Management related messages are not usable by Services, ie, are not fired.
The following tables shows which events are fired on each activity and the ones which aren't fired on any.
Table 2.1. Events received on Authorization Server Activity
Name | Vendor | Version | Class |
---|---|---|---|
net.java.slee.resource. diameter.base.events. SessionTerminationRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. SessionTerminationRequest |
net.java.slee.resource. diameter.base.events. AbortSessionAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. AbortSessionAnswer |
net.java.slee.resource. diameter.base.events. ReAuthAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ReAuthAnswer |
net.java.slee.resource. diameter.base.events. ErrorAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ErrorAnswer |
Table 2.2. Events received on Authorization Client Activity
Name | Vendor | Version | Class |
---|---|---|---|
net.java.slee.resource. diameter.base.events. AbortSessionRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. AbortSessionRequest |
net.java.slee.resource. diameter.base.events. SessionTerminationAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. SessionTerminationAnswer |
net.java.slee.resource. diameter.base.events. ReAuthRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ReAuthRequest |
net.java.slee.resource. diameter.base.events. ErrorAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ErrorAnswer |
Table 2.3. Events received on Accounting Server Activity
Name | Vendor | Version | Class |
---|---|---|---|
net.java.slee.resource. diameter.base.events. AccountingRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. AccountingRequest |
Table 2.4. Events received on Accounting Client Activity
Name | Vendor | Version | Class |
---|---|---|---|
net.java.slee.resource. diameter.base.events. AccountingAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. AccountingAnswer |
net.java.slee.resource. diameter.base.events. ErrorAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ErrorAnswer |
Table 2.5. Events received on Generic Diameter Activity
Name | Vendor | Version | Class |
---|---|---|---|
net.java.slee.resource. diameter.base.events. ExtensionDiameterMessage | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ExtensionDiameterMessage |
net.java.slee.resource. diameter.base.events. ErrorAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. ErrorAnswer |
Table 2.6. Events defined but not received on any Activity (for possible future usage)
Name | Vendor | Version | Class |
---|---|---|---|
net.java.slee.resource. diameter.base.events. CapabilitiesExchangeRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. CapabilitiesExchangeRequest |
net.java.slee.resource. diameter.base.events. CapabilitiesExchangeAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. CapabilitiesExchangeAnswer |
net.java.slee.resource. diameter.base.events. DeviceWatchdogRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. DeviceWatchdogRequest |
net.java.slee.resource. diameter.base.events. DeviceWatchdogAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. DeviceWatchdogAnswer |
net.java.slee.resource. diameter.base.events. DisconnectPeerRequest | java.net | 0.8 | net.java.slee.resource. diameter.base.events. DisconnectPeerRequest |
net.java.slee.resource. diameter.base.events. DisconnectPeerAnswer | java.net | 0.8 | net.java.slee.resource. diameter.base.events. DisconnectPeerAnswer |
Spaces where introduced in Name
and Event Class
column values, to correctly render the table. Please remove them when using copy/paste.
The JBoss Communications Diameter Base Activity Context Interface Factory is defined as follows:
package net.java.slee.resource.diameter.base;
import javax.slee.ActivityContextInterface;
import javax.slee.FactoryException;
import javax.slee.UnrecognizedActivityException;
public interface DiameterActivityContextInterfaceFactory {
public ActivityContextInterface
getActivityContextInterface(DiameterActivity activity)
throws UnrecognizedActivityException, FactoryException;
public ActivityContextInterface
getActivityContextInterface(AccountingClientSessionActivity activity)
throws UnrecognizedActivityException;
public ActivityContextInterface
getActivityContextInterface(AccountingServerSessionActivity activity)
throws UnrecognizedActivityException;
}
The JBoss Communications Diameter Base Resource Adaptor SBB Interface provides SBBs with access to the Diameter objects required for creating and sending messages. It is defined as follows:
package net.java.slee.resource.diameter.base;
import net.java.slee.resource.diameter.base.events.DiameterMessage;
import net.java.slee.resource.diameter.base.events.avp.DiameterIdentity;
import java.io.IOException;
public interface DiameterProvider {
public DiameterMessageFactory
getDiameterMessageFactory();
public DiameterAvpFactory getDiameterAvpFactory();
public DiameterActivity createActivity() throws CreateActivityException;
public DiameterActivity createActivity(DiameterIdentity destinationHost,
DiameterIdentity destinationRealm) throws CreateActivityException;
public AccountingClientSessionActivity createAccountingClientSessionActivity()
throws CreateActivityException;
public AccountingClientSessionActivity createAccountingClientSessionActivity(
DiameterIdentity destinationHost, DiameterIdentity destinationRealm)
throws CreateActivityException ;
public AuthClientSessionActivity createAuthenticationClientSessionActivity()
throws CreateActivityException;
public AuthClientSessionActivity createAuthenticationClientSessionActivity(
DiameterIdentity destinationHost, DiameterIdentity destinationRealm)
throws CreateActivityException;
public DiameterMessage sendSyncRequest(DiameterMessage message)
throws IOException;
public DiameterIdentity[] getConnectedPeers();
public int getPeerCount();
}
This method returns a DiameterMessageFactory
implementation to be used to create DiameterMessage
objects.
This method returns a DiameterAvpFactory
implementation to be used to create DiameterAvp
objects.
This method creates a new activity to send and receive Diameter messages.
This method creates a new activity to send and receive Diameter messages.
This method create a new activity to send Diameter Accounting request messages.
This method create a new activity to send Diameter Accounting request messages.
This method create a new activity to send Diameter Authorization request messages.
This method create a new activity to send Diameter Authorization request messages.
Synchronously send a Diameter request and block until a response is received.
This method returns the identities of peers this Diameter resource adaptor is connected to.
This method returns the number of peers this Diameter resource adaptor is connected to.
Simple Client-Side Example that creates and sends an Accounting-Request and receives an Accounting-Answer.
/* Method for creating and sending ACR with pre-defined values. */
private void sendAccountingRequest() {
try {
AccountingClientSessionActivity activity = provider.createAccountingClientSessionActivity();
List<DiameterAvp> avps = new ArrayList<DiameterAvp>();
avps.add(avpFactory.createAvp(DiameterAvpCodes.SESSION_ID,
activity.getSessionId().getBytes()));
DiameterAvp avpVendorId = avpFactory.createAvp(DiameterAvpCodes.VENDOR_ID, 193);
DiameterAvp avpAcctApplicationId = avpFactory.createAvp(
DiameterAvpCodes.ACCT_APPLICATION_ID, 19302);
avps.add(avpFactory.createAvp(
DiameterAvpCodes.VENDOR_SPECIFIC_APPLICATION_ID,
new DiameterAvp[] { avpVendorId, avpAcctApplicationId }));
avps.add(avpFactory.createAvp(DiameterAvpCodes.ORIGIN_HOST,
this.originIP.getBytes()));
avps.add(avpFactory.createAvp(DiameterAvpCodes.ORIGIN_REALM,
this.originRealm.getBytes()));
avps.add(avpFactory.createAvp(DiameterAvpCodes.DESTINATION_HOST,
(this.destinationIP + ":" + this.destinationPort).getBytes()));
avps.add(avpFactory.createAvp(DiameterAvpCodes.DESTINATION_REALM,
this.destinationRealm.getBytes()));
// Subscription ID
DiameterAvp subscriptionIdType = avpFactory.createAvp(193, 555, 0);
DiameterAvp subscriptionIdData = avpFactory.createAvp(193, 554, "00001000");
avps.add(avpFactory.createAvp(193, 553, new DiameterAvp[] {subscriptionIdType,
subscriptionIdData}));
// Requested Service Unit
DiameterAvp unitType = avpFactory.createAvp(193, 611, 2);
DiameterAvp valueDigits = avpFactory.createAvp(193, 617, 10L);
DiameterAvp unitValue = avpFactory.createAvp(193, 612, new DiameterAvp[] {valueDigits});
avps.add(avpFactory.createAvp(193, 606, new DiameterAvp[] {unitType, unitValue}));
// Record Number and Type
avps.add(avpFactory.createAvp(
DiameterAvpCodes.ACCOUNTING_RECORD_NUMBER, 0));
avps.add(avpFactory.createAvp(
DiameterAvpCodes.ACCOUNTING_RECORD_TYPE, 1));
// Requested action
avps.add(avpFactory.createAvp(193, 615, 0));
// Service Parameter Type
DiameterAvp serviceParameterType = avpFactory.createAvp(193, 608, 0);
DiameterAvp serviceParameterValue = avpFactory.createAvp(193, 609, "510");
avps.add(avpFactory.createAvp(193, 607, new DiameterAvp[] {serviceParameterType,
serviceParameterValue}));
// Service Parameter Type
DiameterAvp serviceParameterType2 = avpFactory.createAvp(193, 608, 14);
DiameterAvp serviceParameterValue2 = avpFactory.createAvp(193, 609, "20");
avps.add(avpFactory.createAvp(193, 607, new DiameterAvp[] {serviceParameterType2,
serviceParameterValue2}));
DiameterAvp[] avpArray = new DiameterAvp[avps.size()];
avpArray = avps.toArray(avpArray);
if (tracer.isInfoEnabled())
tracer.info("Creating Custom Message...");
AccountingRequest acr = messageFactory.createAccountingRequest(avpArray);
if (tracer.isFineEnabled()) {
tracer.fine("Created Custom Message[" + acr + "]");
tracer.fine("Sending Custom Message...");
}
ActivityContextInterface aci = acif.getActivityContextInterface(activity);
activity.sendAccountRequest(acr);
aci.attach(sbbContext.getSbbLocalObject());
if (tracer.isInfoEnabled()) {
tracer.info("Sent Custom Message[" + acr + "]");
}
}
catch (Exception e) {
tracer.severe("", e);
}
}
...
/* Method for handling ACA messages. Just print the Result-Code AVP. */
public void onAccountingAnswer(AccountingAnswer aca, ActivityContextInterface aci) {
if (tracer.isInfoEnabled()) {
tracer.info("Accounting-Answer received. Result-Code[" + aca.getResultCode() + "].");
}
}
Simple Server-Side Example for receiving Accounting-Request and proxy it to it's destination, if acting as proxy, or answer with Accounting-Answer, if in Server mode.
/* Method for handling ACR messages and either proxy or answer them. */
public void onAccountingRequest(AccountingRequest acr, ActivityContextInterface aci) {
long start = System.currentTimeMillis();
if (tracer.isInfoEnabled())
tracer.info("Accounting-Request received. [" + acr + "]");
boolean actAsProxy = false;
try {
// Are we gonna act as a proxy?
if (actAsProxy) {
// In here we act as a "proxy". Just for testing we take the original message,
// replace the Origin/Destination Host/Realm AVPs and send it to the emulator.
boolean hasDestinationHost = false;
boolean hasDestinationRealm = false;
List<DiameterAvp> avps = new ArrayList<DiameterAvp>();
for (DiameterAvp avp : acr.getAvps()) {
switch (avp.getCode()) {
case DiameterAvpCodes.ORIGIN_HOST:
avps.add(avpFactory.createAvp(DiameterAvpCodes.ORIGIN_HOST, ("aaa://" +
originIP + ":" + originPort).getBytes()));
break;
case DiameterAvpCodes.ORIGIN_REALM:
avps.add(avpFactory.createAvp(DiameterAvpCodes.ORIGIN_REALM,
originRealm.getBytes()));
break;
case DiameterAvpCodes.DESTINATION_HOST:
avps.add(avpFactory.createAvp(DiameterAvpCodes.DESTINATION_HOST,
("aaa://" + destinationIP + ":" + destinationPort).getBytes()));
hasDestinationHost = true;
break;
case DiameterAvpCodes.DESTINATION_REALM:
avps.add(avpFactory.createAvp(DiameterAvpCodes.DESTINATION_REALM,
destinationRealm.getBytes()));
hasDestinationRealm = true;
break;
default:
avps.add(avp);
}
}
if (!hasDestinationHost)
avps.add(avpFactory.createAvp(DiameterAvpCodes.DESTINATION_HOST,
"127.0.0.1".getBytes()));
if (!hasDestinationRealm)
avps.add(avpFactory.createAvp(DiameterAvpCodes.DESTINATION_REALM,
"mobicents.org".getBytes()));
if (tracer.isInfoEnabled())
tracer.info("AVPs ==> " + avps);
DiameterAvp[] avpArray = new DiameterAvp[avps.size()];
avpArray = avps.toArray(avpArray);
if (tracer.isInfoEnabled())
tracer.info("Creating Custom Message...");
DiameterMessage ms = messageFactory.createAccountingRequest(avpArray);
if (tracer.isInfoEnabled()) {
tracer.info("Created Custom Message[" + ms + "]");
tracer.info("Sending Custom Message...");
}
provider.createActivity().sendMessage(ms);
if (tracer.isInfoEnabled()) {
tracer.info("Sent Custom Message[" + ms + "]");
}
}
else {
// In here we act as a server and just say it's SUCCESS.
if (aci.getActivity() instanceof AccountingServerSessionActivity) {
AccountingServerSessionActivity assa =
(AccountingServerSessionActivity) aci.getActivity();
AccountingAnswer ans = assa.createAccountingAnswer(acr);
ans.setResultCode(2001); // 2001 = SUCCESS
if (tracer.isInfoEnabled()) {
tracer.info("Sending Accounting-Answer [" + ans + "]");
}
assa.sendAccountingAnswer(ans);
if (tracer.isInfoEnabled()) {
tracer.info("Accounting-Answer sent.");
}
}
}
}
catch (Exception e) {
tracer.severe("", e);
}
long end = System.currentTimeMillis();
if (tracer.isInfoEnabled()) {
tracer.info("Accounting-Request proccessed. [" + (end - start) + "ms]");
}
}