Subject: [AAA-WG]: DCC: Issue: Final consistency alignments across the document

From: <[email-masked]>
Date: Mon, 16 Feb 2004 10:50:16 +0200

Description of issue: Final consistency alignements across the document
Submitter name:  
Date first submitted: 16.02.2004 
Reference: 
Document: draft-ietf-aaa-diameter-cc-02.txt 
Comment type: T 
Priority: 1 
Section: Various 

Rationale/Explanation of issues: 

After the introduction of the multiple services in a credit control session there is need for some polishing and consistency alignments across the document due to existing old text, listed hereafter.

We can have cases with multiple services where we may change from time to volume (or viceversa) with the tariff switch. Tariff switch should carry before quota and after quota i.e. two instances of the same unit type associated with a service/rating group.

Also, result code/validity-time/final unit may be sent at M-S-C-C level hence it is not always true that the specified behavior applies to the whole session.

Finally, some consistency update along the document concerning the Service-Identifier AVP (done according to section 4.1) is required.

The old text need to be made consistent.

Requested change:

-Section 5.1 second - seventh paragraphs

FROM

If the Diameter credit-control client knows the cost of the service event (e.g. a content server delivering ringing tones may know their cost) the monetary amount to be charged is included in the Requested-Service-Unit AVP. If the Diameter credit-control client does not know the cost of the service event, the Requested-Service-Unit AVP MAY contain the number of requested service events and the Service-Parameter-Info AVP MAY contain the service event information to be rated by the credit-control server. The Service-Parameter-Info AVP always refers to the requested service units. Alternatively, service event information to be rated can be sent as service specific AVPs.
 
The Event-Timestamp AVP contains the time when the service event is requested in the service element.
................. 

The credit-control server returns the Granted-Service-Unit AVP in the Answer message to the Diameter credit-control client. The Granted-Service-Unit AVP contains the amount of service units that the Diameter credit-control client can provide to the end user until a new Credit-Control-Request MUST be sent to the credit-control server. If several unit types are sent in the Answer message the credit-control client MUST handle each unit type separately.  There MUST be maximum one instance of the same unit type in one Answer message. In case multiple quotas are conveyed to the credit control client, there MUST be maximum one instance of the same unit type associated to a Service-Identifier, or set of Service-Identifiers, or associated to a Rating-Group. The type of the Granted-Service-Unit AVP can be time, volume, service specific or money depending on the type of service event. It is not allowed to change the unit type(s) within the session.
    
If the credit-control server determines that no further control is needed for the service it MAY include the result code indicating that the credit-control is not applicable (e.g. service is free of charge) and terminate the credit-control session.

The Credit-Control-Answer message MAY also include the Final-Unit-Indication AVP to indicate that the answer message contains the final units for the service session. After the end user has consumed these units, the Diameter credit-control-client MUST behave as described in section 5.5.

TO

If the Diameter credit-control client knows the cost of the service event (e.g. a content server delivering ringing tones may know their cost) the monetary amount to be charged is included in the Requested-Service-Unit AVP. If the Diameter credit-control client does not know the cost of the service event, the Requested-Service-Unit AVP MAY contain the number of requested service events. The Service-Identifier AVP, in case of multiple services the Service-Identifier AVP or the Rating-Group AVP within the Multiple-Services-Credit-Control AVP, always indicates the concerned service.  Additional service event information to be rated MAY be sent as service specific AVPs or MAY be sent within the Service-Parameter-Info AVP at command level.

The Event-Timestamp AVP contains the time when the service event is requested in the service element. The Subscription-Id AVP SHOULD be included to identify the End-User in the credit-control server. 
.................................

The credit-control server returns the Granted-Service-Unit AVP in the Answer message to the Diameter credit-control client. The Granted-Service-Unit AVP contains the amount of service units that the Diameter credit-control client can provide to the end user until a new Credit-Control-Request MUST be sent to the credit-control server. If several unit types are sent in the Answer message the credit-control client MUST handle each unit type separately. The type of the Granted-Service-Unit AVP can be time, volume, service specific or money depending on the type of service event. The unit type(s) SHOULD NOT be changed within an ongoing credit-control session. 

There MUST be maximum one instance of the same unit type in one Answer message. However, in case multiple quotas are conveyed to the credit control client in the Multiple-Services-Credit-Control AVPs, it is possible to carry two instances of the same unit type associated to a service-identifier/rating-group for instance when a tariff time change is expected.

If the credit-control server determines that no further control is needed for the service it MAY include the result code indicating that the credit-control is not applicable (e.g. service is free of charge). This result code at command level implies that the credit-control session is to be terminated.

The Credit-Control-Answer message MAY also include the Final-Unit-Indication AVP to indicate that the answer message contains the final units for the service. After the end user has consumed these units, the Diameter credit-control-client MUST behave as described in section 5.5.

- Section 5.2 third paragraph

FROM

When the used units are reported to the credit-control 
server the credit-control client will not have any units in 
its possession before new granted units are received from the 
credit-control server. When the new granted units are 
received from the credit-control server these units apply 
from the point where the measurement of the reported used 
units stopped.

TO

When the used units are reported to the credit-control 
server, the credit-control client will not have any units in 
its possession before new granted units are received from the 
credit-control server. When the new granted units are 
received from the credit-control server these units apply 
from the point where the measurement of the reported used 
units stopped. Where independent credit-control of multiple 
services is supported, this process may be executed for
one or more services, a single rating-group or for a pool 
within the (sub-)session.

- Section 5.2 fifth and last paragraphs 

FROM

The Requested-Service-Unit AVP contains the new amount of requested service units. The Used-Service-Unit AVP contains the amount ..............

The Credit-Control-Answer message MAY also include the Final-Unit-Indication AVP to indicate that the answer message contains the final units for the service session. After the end user has consumed these units, the Diameter credit-control-client MUST behave as described in section 5.5.

TO

The Requested-Service-Unit AVP MAY contains the new amount of requested service units. The Used-Service-Unit AVP contains the amount ..............

The Credit-Control-Answer message MAY also include the Final-Unit-Indication AVP to indicate that the answer message contains the final units for the service. After the end user has consumed these units, the Diameter credit-control-client MUST behave as described in section 5.6.

- Section 5.5.1

FROM

The Final-Unit-Indication AVP with Final-Unit-Action TERMINATE does not include any other information. Upon the subscriber has consumed the final granted units the service element MUST terminate the service session and MUST send a final Credit-Control-Request message to the credit control server. The CC-Request-Type AVP in the request is set to the value TERMINATION_REQUEST. This is the default handling applicable whenever the credit control client receives an unsupported Final-Unit-Action value and MUST be supported by all the Diameter credit control client implementations conforming to this specification..

TO

The Final-Unit-Indication AVP with Final-Unit-Action TERMINATE does not include any other information. Upon the subscriber has consumed the final granted units the service element MUST terminate the service. This is the default handling applicable whenever the credit control client receives an unsupported Final-Unit-Action value and MUST be supported by all the Diameter credit control client implementations conforming to this specification. A final Credit-Control-Request message to the credit control server MUST be sent if the Final-Unit-Indication AVP indicating action TERMINATE was present at command level. The CC-Request-Type AVP in the request is set to the value TERMINATION_REQUEST.

- section 5.5.2 fifth paragraph

FROM

..............Therefore, the credit control client MUST NOT include any rating related AVP in the request sent upon all the final granted units have been consumed as a hint to the server that the requested final unit action started, rating and money reservation are not required. ..................

TO

..........................
Therefore, the credit control client MUST NOT include any rating related AVP in the request sent upon all the final granted units have been consumed as a hint to the server that the requested final unit action started, rating and money reservation are not required (when the Multiple-Services-Credit-Control AVP is used, the Service-Identifier or Rating-Group AVPs is included to indicate the concerned services). ..................

- section 5.5.2 sixth paragraph

FROM

............................. The server will return the appropriate Result-Code (see section 9.1) in the Credit-Control-Answer message in order to close the credit control session and implement the policy-defined action.  ...................

TO

............................. The server will return the appropriate Result-Code (see section 9.1) in the Credit-Control-Answer message in order to implement the policy-defined action.  ...................................................

- Section 6.1 second paragraph

FROM

A Diameter credit-control client requesting the cost information MUST set the CC-Request-Type AVP equal to EVENT_REQUEST, include the Requested-Action AVP set to PRICE_ENQUIRY and set the requested service event information into the Service-Parameter-Info AVP in the Credit-Control-Request message.

TO

A Diameter credit-control client requesting the cost information MUST set the CC-Request-Type AVP equal to EVENT_REQUEST, include the Requested-Action AVP set to PRICE_ENQUIRY and set the requested service event information into the Service-Identifier AVP in the Credit-Control-Request message. Additional service event information MAY be sent as service specific AVPs or MAY be sent within the Service-Parameter-Info AVP.

- Section 6.3 third paragraph

FROM

The Diameter credit-control client can include the monetary amount to be charged in the Requested-Service-Unit AVP, if it knows the cost of the service event. If the Diameter credit-control client does not know the cost of the service event, then the Service-Parameter-Info AVP SHOULD contain the service event information to be rated by the credit-control server. The Service-Parameter-Info AVP always refers to the requested service unit.

TO

The Diameter credit-control client MAY include the monetary amount to be charged in the Requested-Service-Unit AVP, if it knows the cost of the service event. If the Diameter credit-control client does not know the cost of the service event, the Requested-Service-Unit AVP MAY contain the number of requested service events. The Service-Identifier AVP always indicates the concerned service, additional service event information to be rated MAY be sent as service specific AVPs or MAY be sent within the Service-Parameter-Info AVP.

- Section 6.4 third paragraph

FROM

The Diameter credit-control client MAY include the monetary amount to be refunded in the Requested-Service-Unit AVP. If the Diameter credit-control client does not know the monetary amount to be refunded, then the Service-Parameter-Info AVP, or other rating AVPs, SHOULD contain the service event information to be rated by the credit-control server

TO

The Diameter credit-control client MAY include the monetary amount to be refunded in the Requested-Service-Unit AVP. The Service-Identifier AVP always indicates the concerned service. If the Diameter credit-control client does not know the monetary amount to be refunded, in addition to the Service-Identifier AVP it MAY send service specific AVPs or the Service-Parameter-Info AVP containing additional service event information to be rated.

- Section 8.20

FROM

DIRECT_DEBITING                              0 

Direct debiting indicates that the request is to decrease the end user's account according to information specified in the Requested-Service-Unit AVP and/or Service-Parameter-Info AVP. The Granted-Service Unit AVP in the Credit-Control-Answer command contains the debited units.

REFUND_ACCOUNT                               1 

Refund account indicates that the request is to increase the end user's account according to information specified in the Requested-Service-Unit AVP and/or Service-Parameter-Info AVP. The Granted-Service Unit AVP in the Credit-Control-Answer command contains the refunded units.  

TO

DIRECT_DEBITING                              0 

Direct debiting indicates that the request is to decrease the end user's account according to information specified in the Requested-Service-Unit AVP and/or Service-Identifier AVP (additional rating information may be included in service specific AVPs or in the Service-Parameter-Info AVP). The Granted-Service Unit AVP in the Credit-Control-Answer command contains the debited units. 

REFUND_ACCOUNT                               1 

Refund account indicates that the request is to increase the end user's account according to information specified in the Requested-Service-Unit AVP and/or Service-Identifier AVP (additional rating information may be included in service specific AVPs or in the Service-Parameter-Info AVP). The Granted-Service Unit AVP in the Credit-Control-Answer command contains the refunded units. 

- Section 8.36

FROM

The CC-Service-Specific-Units AVP (AVP Code 417) is of type OctetString, and specifies the number of service specific units (e.g. number of events, points) given in a selected service. 

TO

The CC-Service-Specific-Units AVP (AVP Code 417) is of type OctetString, and specifies the number of service specific units (e.g. number of events, points) given in a selected service. The service specific units always refer to the service identified in the Service-Identifier AVP (or Rating-Group AVP when the Multiple-Services-Credit-Control AVP is used).