Concurrent Volume and Duration Based PrePaid

Transcription

1 GPP X.S00-0 v0. JuneSeptember, 0 Concurrent Volume and Duration Based PrePaid 0 GPP GPP and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the GPP Secretariat at secretariat@gpp.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See for more information.

2 REVISION HISTORY Revision Description of Changes Date Rev 0 v0. Initial contribution March 0 Rev 0 v0. (R&F version) Incorporation of changes from: June 0 Rev 0 v0. (V&V version) Incorporation of changes from R&F comment resolution September 0

3 CONTENTS Concurrent Volume and Duration Based PrePaid Introduction.... Scope.... Document Conventions... References.... Normative References... Definitions, Symbols and Abbreviations.... Definitions.... Symbols and Abbreviations... GPP RADIUS Attributes.... PrePaidAccountingQuota (PPAQ).... PrePaidAccountingCapability (PPAC)... PrePaid Client in the PDSN PrePaid Capable PDSN Requirements Service Description for Concurrent Volume and Duration Based PrePaid at the PDSN... PrePaid Client in the HA.... Service Description for PrePaid at the HA.... Interaction with Remote IP Address based Accounting.... Interaction with Flow Control over the A0 connection.... Interaction with Hot-Lining.... Sequence diagrams.... PrePaid Capable HA Requirements... i

4 LIST OF FIGURES Figure PrePaidAccountingQuota (PPAQ) VSA format... Figure PrePaidAccountingCapability (PPAC) VSA format... Figure PrePaid authorization from the PrePaid capable HA... Figure Handoff from a Non-PrePaid to a PrePaid Capable PDSN ii

5 LIST OF TABLES This document does not contain any tables. iii

6 FOREWORD (This foreword is not part of this document.) This document was prepared by GPP TSG-SX. It describes concurrent volume and duration aspects for PrePaid service. This document is the first version of revision 0 of this specification. This document is subject to change following formal approval. Should this document be modified, it will be re-released with a change of release date and an identifying change in version number as follows: X.S00-X version n.0 where: X is an uppercase numerical or alphabetic character [0, A, B, C, ] that represents the revision level. n is a numeric string [,,, ] that indicates a point release level iv

7 Introduction. Scope This document provides a delta of some sections of GPP X.S00-00-E v.0 and GPP X.S00-00-E v.0. When an operator chooses to implement concurrent volume and duration aspects for prepaid, the text of this document takes precedence over the samenumbered text in those documents. The scope of this document covers support for concurrent volume and duration control of prepaid service.. Document Conventions Shall and shall not identify requirements to be followed strictly to conform to the standard and from which no deviation is permitted. Should and should not indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others; that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. May and need not indicate a course of action permissible within the limits of the standard. Can and cannot are used for statements of possibility and capability, whether material, physical, or causal. All fields that are marked as Reserved shall be filled with zeros by the sender of that field, and shall be ignored by the receiver of that field.

8 References. Normative References This section provides references to other specifications and standards that are necessary to implement this document. The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. [] GPP: X.S00-00-E v.0: cdma000 Wireless IP Network Standard: Introduction, November 00. [] GPP: X.S00-00-E v.0: cdma000 Wireless IP Network Standard: Simple IP and Mobile IP Access Services, November 00. [] GPP: X.S00-00-E v.0: cdma000 Wireless IP Network Standard: Data Mobility and Resource Management, November 00. [] GPP: X.S00-00-E v.0: cdma000 Wireless IP Network Standard: Quality of Service and Header Reduction, November 00. [] GPP: X.S00-00-E v.0: cdma000 Wireless IP Network Standard: Accounting Services and GPP Radius VSAs, November 00. [] GPP: X.S00-00-E v.0: cdma000 Wireless IP Network Standard: PrePaid Packet Data Service, November 00. [] IETF: RFC : C. Rigney et al., RADIUS Extensions, June

9 Definitions, Symbols and Abbreviations. Definitions A0 This section contains definitions, symbols and abbreviations that are used throughout the document. A bearer connection between the AN/PCF and the PDSN. Hot-Lining A method of directly routing IP packets, e.g., from an access terminal, to a specific destination, regardless of the destination address specified in the IP packets.. Symbols and Abbreviations GPP rd Generation Partnership Project AN Access Network AT Access Terminal CoA Care of Address CVDPP Concurrent Volume and Duration for PrePaid DNS Dynamic Name Server DT Duration Threshold GRE Generic Routing Encapsulation HA Home Agent HTTP HyperText Transport Protocol IP Internet Protocol IPv Internet Protocol version IPv Internet Protocol version MIP Mobile IP MIP Mobile IPv NAI Network Access Identifier NAK Negative AcKnowledgement PCF Packet Control Function PDSN Packet Data Serving Node PPAC PrePaid Accounting Capability PPAQ PrePaid Account Quote (duration/volume) PPC PrePaid Client PPS PrePaid Server PTS PrePaid Traffic Switch RRP Registration ResponseReply RRQ Registration Request STC Session Termination Capability TITSU Time Interval after Tariff Switch Update TSI Traffic Switch Interval

10 VSA Vendor Specific Attribute VT Volume Threshold

11 GPP RADIUS Attributes The following subsections take precedence over the same-numbered subsections of X.S00-00-E v.0 [].. PrePaidAccountingQuota (PPAQ) This attribute specifies the characteristics for PrePaid accounting of the volume and/or duration of a packet data session. It shall be present in all on-line RADIUS Access-Request and on-line RADIUS Access-Accept messages and may be included in other RADIUS Access-Accept messages. Non-used Sub-Types by the PPC and PPS shall be omitted Type Length Vendor-ID Vendor-ID (cont) Vendor-Type Vendor-Length Sub-Type (=) Length Value(QuotaIDentifier) Value (QuotaIDentifier) Sub-Type (=) Length Value (VolumeQuota) Sub-Type (=) Length Value(VolumeQuotaOverflow) Sub-Type (=) Length Value(VolumeThreshold) Value (VolumeThreshold) Sub-Type (=) Length Value(VolumeThresholdOverflow) Sub-Type (=) Length Value (DurationQuota ) Sub-Type (=) Length Value(DurationThreshold) Value (DurationThreshold) Sub-Type (=) Length Value (Update-Reason) Sub-Type (=) Length PrePaidServer (IPv or IPv Address) PrePaidServer (IPv Address) PrePaidServer IPv Address) PrePaidServer (IPv Address) Figure Type: PrePaidAccountingQuota (PPAQ) VSA format Length: variable, greater than Vendor-ID: Vendor-Type: 0 Vendor-Length: variable, greater than Sub-Type (=): Sub-Type for QuotaIDentifier attribute Length: length of QuotaIDentifier attribute (= octets) QuotaIDentifier (QID): The QuotaIDentifier Sub-Type is generated by the PrePaid server at allocation of a Volume and/or Duration Quota. The on-line quota update RADIUS Access-

12 Request message sent from the PPC to the PPS shall include a previously received QuotaIDentifier. Sub-Type (=): Sub-Type for VolumeQuota attribute Length: length of VolumeQuota attribute (= octets) VolumeQuota (VQ): The optional VolumeQuota Sub-Type is present if Volume Based charging is used or concurrent Volume and Duration based charging is used. In RADIUS Access-Accept message (PPS to PPC direction), it indicates the Volume (in octets) allocated for the session by the PrePaid server. In on-line RADIUS Access-Request message (PPC to PPS direction), it indicates the total used volume (in octets) for both forward and reverse traffic applicable to PrePaid accounting. If a Tariff Switch condition was reached during the session, this Sub-Type contains the complete (before and after) volume used, while the VolumeUsedAfterTariffSwitch attribute contains the volume used after the tariff switch condition. Sub-Type (=): Sub-Type for VolumeQuotaOverflow Length: length of VolumeQuotaOverflow attribute (= octets) VolumeQuotaOverflow (VQO): The optional VolumeQuotaOverflow Sub-Type is used to indicate how many times the VolumeQuota counter has wrapped around ^ over the course of the service being provided. Sub-Type (=): Sub-Type for VolumeThreshold attribute Length: length of VolumeThreshold attribute (= octets) VolumeThreshold (VT): The VolumeThreshold Sub-Type shall always be present if VolumeQuota is present in a RADIUS Access-Accept message (PPS to PPC direction). It is generated by the PrePaid server and indicates the volume (in octets) that shall be used before requesting quota update. This threshold should not be larger than the VolumeQuota. Sub-Type (=): Sub-Type for VolumeThresholdOverflow Length: length of VolumeThresholdOverflow attribute (= octets) VolumeThresholdOverflow (VTO): The optional VolumeThresholdOverflow Sub-Type is used to indicate how many times the VolumeThreshold counter has wrapped around ^ over the course of the service being provided. Sub-Type (=): Sub-Type for DurationQuota attribute Length: length of DurationQuota attribute (= octets) Remote Address identified as exempt from PrePaid accounting shall not be accounted for in the volume used returned in the VolumeQuota

13 DurationQuota (DQ): The optional DurationQuota Sub-Type is present if Duration Based charging is used or concurrent Volume and Duration based charging is used. In RADIUS Access-Accept message (PPS to PPC direction), it indicates the Duration (in seconds) allocated for the session by the PrePaid server. In on-line RADIUS Access-Accept message (PPC to PPS direction), it indicates the total Duration (in seconds) since the start of the accounting session related to the QuotaID. Sub-Type (=): Sub-Type for DurationThreshold attribute Length: length of DurationThreshold attribute (= octets) DurationThreshold (DT): The DurationThreshold Sub-Type shall always be present if DurationQuota is present in a RADIUS Access-Accept message (PPS to PPC direction). It represents the duration (in seconds) that shall be used by the session before requesting quota update. This threshold should not be larger than the DurationQuota and shall always be sent with the DurationQuota. Sub-Type (=): Sub-Type for Update-Reason attribute Length: length of Update-Reason attribute (= octets) Update-Reason attribute (UR): The Update-Reason Sub-Type shall be present in the on-line RADIUS Access- Request message (PPC to PPS direction). It indicates the reason for initiating the on-line quota update operation. Update reasons,,, and indicate that the associated resources are released at the client side, and therefore the PPS shall not allocate a new quota in the RADIUS Access-Accept message.. Pre-initialization. Initial request. Threshold reached. Quota reached. Remote Forced disconnect. Client Service termination. Main SC released. Service Connection not established. Tariff Switch Update 0. Incorrect Quota Type Received. Poorly Formed Quota Attribute Sub-Type (=): Sub-Type for PrePaidServer attribute Length: Length of PrePaidServer (IPv = octets, IPv= octets PrePaidServer: The optional, multi-value PrePaidServer indicates the address of the serving PrePaid System. If present, the Home RADIUS server uses this address to route

14 the message to the serving PrePaid Server. The attribute may be sent by the Home RADIUS server. If present in the incoming RADIUS Access-Accept message, the PDSN shall send this attribute back without modifying it in the subsequent RADIUS Access-Request message, except for the first one. If multiple values are present, the PDSN shall not change the order of the attributes.. PrePaidAccountingCapability (PPAC) This attribute specifies the capability for PrePaid accounting for a packet data session. It contains the possible capabilities of the PrePaid client and the selected (by the PrePaid server) capability for the session. The absence of this VSA indicates that the client is not capable of PrePaid Accounting and the session shall not use PrePaid accounting Type Length Vendor-ID Vendor-ID (cont) Vendor-Type Vendor-Length Sub-Type (=) Length Value(AvailableInClient) Value (AvailableInClient) Sub-Type (=) Length Value (SelectedForSession) Figure Type: PrePaidAccountingCapability (PPAC) VSA format Length: variable, greater than Vendor-ID: Vendor-Type: Vendor-Length: variable, greater than Sub-Type (=): Sub-Type for AvailableInClient attribute Length: length of AvailableInClient attribute (= octets) AvailableInClient (AiC): The optional AvailableInClient Sub-Type, generated by the PrePaid client, indicates the PrePaid Accounting capabilities of the client in the PDSN or HA and shall be bitmap encoded. The possible values are: 0x x x x Others Sub-Type (=): Sub-Type for SelectedForSession attribute Length: length of SelectedForSession attribute (= octets) SelectedForSession (SfS): PrePaid Accounting for Volume supported PrePaid Accounting for Duration supported PrePaid Accounting for Volume and Duration supported (non concurrently) PrePaid Accounting for Volume and Duration supported concurrently Reserved, treat like Not Capable of PrePaid Accounting (=0)

15 The optional SelectedForSession Sub-Type, generated by the PrePaid server, indicates the PrePaid Accounting capability to be used for a given session. The possible values are: 0x x x x x PrePaid Accounting not used Usage of PrePaid Accounting for Volume. (only possible if the AvailableInClient supports PrePaid Accounting for Volume) Usage of PrePaid Accounting for Duration. (only possible if the AvailableInClient supports PrePaid Accounting for Duration) Usage of PrePaid Accounting for Volume and Duration (non concurrent) (only possible if the AvailableInClient supports PrePaid Accounting for Volume and duration) Usage of PrePaid Accounting for Volume and Duration concurrent (only possible if the AvailableInClient supports PrePaid Accounting for Volume and duration concurrently) Others Reserved, treat like PrePaid Accounting not used (=0).

16 PrePaid Client in the PDSN The following subsections take precedence over the same-numbered subsections of X.S00-00-E v.0 [].. PrePaid Capable PDSN Requirements The PDSN shall assume the role of the PrePaid Client if the PPAC VSA and an initial PPAQ is included in the RADIUS Access-Accept message at packet data session establishment as authorized by the Home RADIUS/PPS. The on-line RADIUS Access-Request/Accept messages are RADIUS Access-Request/Accept messages that are subsequent to the initial RADIUS Access-Request/Accept message and shall be used for PrePaid quota update operations. The PrePaid capable PDSN shall include in the on-line RADIUS Access-Request messages the attributes Message Authenticator and Service-Type () set to PrePaid Authorize Only to indicate that the RADIUS Access- Request message is for authorization only, and the PPAQ VSA to indicate that the authorization is for PrePaid quota update. Other attributes shall be included as indicated in X.S00-00-E [] Table. Only the on-line quota update RADIUS Access-Request/Accept messages and the initial RADIUS Access-Accept message from the Home RADIUS/PPS shall be allowed to include the PrePaidAccountingQuota VSA (PPAQ) as defined in [] section.. The on-line RADIUS Access-Request message shall use the same Correlation ID value as used in the RADIUS Access-Request message sent at packet data session establishment. PrePaid service for non-authenticated users (Simple IP users with no CHAP or PAP) is not supported in this document... Authorization and Quota Initialization Requirements. A PrePaid capable PDSN shall measure volume (octets) and/or total session duration (seconds) per service connection for all PrePaid packet data sessions.. The PrePaid capable PDSN shall indicate to the Home RADIUS/PPS that it supports PrePaid Accounting. The PrePaid capable PDSN shall include the PPAC VSA defined in [Chapter ]section. in the RADIUS Access-Request message at Simple IP or MIP establishment. The PDSN shall also include the SessionTerminationCapability (STC) (see [] ) with value.. If the PPAC VSA is not received from the Home RADIUS/PPS in the initial RADIUS Access-Accept message, or is included but it indicates PrePaid Accounting not used, the PrePaid capable PDSN shall initiate release of the user s PrePaid packet data session if the RADIUS Access-Accept message from the Home RADIUS/PPS includes a PPAQ VSA.. The PrePaid capable PDSN shall terminate a packet data session when the RADIUS Access-Accept message includes a PPAQ VSA containing only the VolumeQuota Sub- Type for a packet data session identified by the PPAC VSA as Duration only. The PrePaid capable PDSN shall send an on-line RADIUS Access-Request message with the Update-Reason Sub-Type Incorrect Quota Type Received to indicate the release of the packet data session. In this online Access-Request, the PDSN shall not include the VQ and VQO sub-types in the PPAQ VSA

17 The PrePaid capable PDSN shall establish a packet data session as duration-based when the RADIUS Access-Accept message includes a PPAQ VSA containing both the VolumeQuota Sub-Type and Duration Sub-type for a packet data session identified by the PPAC VSA as Duration only; and ignore the received Volume Quota.. The PrePaid capable PDSN shall terminate a packet data session when the RADIUS Access-Accept message includes a PPAQ VSA containing only the DurationQuota Sub- Type for a packet data session identified by the PPAC VSA as Volume only. The PrePaid capable PDSN shall send an on-line RADIUS Access-Request message with the Update-Reason Sub-Type Incorrect Quota Type Received to indicate the release of the packet data session In this online Access-Request, the PDSN shall not include the DQ and DQO sub-types in the PPAQ VSA. The PrePaid capable PDSN shall establish a packet data session as volume-based when the RADIUS Access-Accept message includes a PPAQ VSA containing both the VolumeQuota Sub-Type and Duration Sub-type for a packet data session identified by the PPAC VSA as Volume only; and ignore the received Duration Quota. PrePaid capable PDSN shall initiate release of the user s PrePaid packet data session if the RADIUS Access-Accept message from the Home RADIUS/PPS includes a PPAQ VSA and the PPAQ does not contain any Quota-ID subtype, The PDSN shall also generate online Access Request with Update Reason as Poorly-Formed-Quota- Attribute. In this online Access-Request, the PDSN shall not include the VQ, VQO or DQ, DQO sub-types in the PPAQ VSA.. The PrePaid capable PDSN shall terminate a packet data session when the RADIUS Access-Accept message includes a PPAQ VSA containing only the DurationQuota Sub- Type or VolumeQuota Sub-Type for a packet data session identified by the PPAC VSA as Concurrent Volume and Duration. The PrePaid capable PDSN shall send an on-line RADIUS Access-Request message with the Update-Reason Sub-Type Incorrect Quota Type Received to indicate the release of the packet data session.. If the PDSN receives the RADIUS Access-Accept message containing the PPAC VSA indicating PrePaid, but the initial quota is not included, the PDSN shall release the main service connection, and consequently the packet data session without further notifying the Home RADIUS server/pps.. If the PDSN is not PrePaid capable, it shall not include the PPAC VSA in the RADIUS Access-Request message to the Home RADIUS server.. The PrePaid capable PDSN shall support PrePaid over a service connection based on either VolumeQuota and VolumeThreshold or a DurationQuota and DurationThreshold or both. If both VolumeQuota and DurationQuota are received for the same service connection, the PrePaid capable PDSN without concurrent Volume and Duration based Prepaid support shall use its local policy to determine which type of PrePaid accounting should be used for that service connection and shall ignore the non-used subtype. 0. If the Class attribute has been received by the PDSN during the RADIUS Access-Accept message, the PDSN shall include the Class attribute as received on all subsequent RADIUS Accounting-Request messages associated with the session. The PDSN shall support one Class attribute per packet data session. If more than one Class attribute is received in the RADIUS Access-Accept message, the PDSN shall accept the first Class attribute that appears in the message.. Upon receiving a RADIUS Access-Accept message indicating that PrePaid packet data service shall be provided, the PrePaid capable PDSN shall store the initial quota, threshold and Quota ID for the main service connection received in the PPAQ VSA, and shall start metering the traffic when the MS has successfully been assigned an IP address

18 (Simple IP) or has successfully registered with the home network (MIP) for the PrePaid packet data session.. If the RADIUS Access-Accept message, in addition to the PPAC VSA, includes the Service Option Profile VSA and indicates that the user is allowed to establish auxiliary service connection, the PrePaid Capable PDSN may immediately initiate an on-line RADIUS Access-Request message to request pre-initialization of quota. The PDSN may request one quota for each service option. The PPAQ VSA shall include the Update- Reason Sub-Type to indicate pre-initialization. Note that pre-initialization of quota shall only be applicable for auxiliary service connection.. If the auxiliary service connection is never requested by the MS, then upon PrePaid packet data session termination, an on-line RADIUS Access-Request message message shall be sent containing the PPAQ VSA with the Update-Reason Sub-Type indicating, service connection not established. If the user eventually requests establishment of an auxiliary service connection for which quota pre-initialization is not done, the PrePaid capable PDSN shall trigger an on-line RADIUS Access-Request message to request initialization of the quota, as the auxiliary service connection is being setup by the user. The PPAQ VSA shall include the Update-Reason to indicate initial request.. If the PrePaid user attempts to establish an additional packet data session while a PrePaid packet data session is already active over the same PPP session, the PrePaid capable PDSN shall reject the second packet data session.. If the initial packet data session established by the user is not PrePaid and a subsequent packet data session is requested by the MS, the PDSN shall not include the PPAC VSA in the RADIUS Access-Request message. The home network may determine if the HA can provide the PrePaid packet data service for the user.. At MIP re-registration of a PrePaid packet data session, if the PDSN sends a RADIUS Access-Request message to the Home RADIUS/PPS to authenticate the user, it shall include the Session-Continue VSA with the value set to true.. If both DurationQuota and TariffSwitchInterval are received for the same service connection, the PrePaid capable PDSN shall discard the TariffSwitchInterval and shall provide PrePaid based on the DurationQuota only.. If the PTS VSA is received, it shall include the TariffSwitchInterval (TSI) Sub-Type, and may include the TimeIntervalafterTariffSwitchUpdate timer (TITSU) Sub-Type. The TITSU Sub-Type may be included when more than one tariff switch boundary exists, and the user may not reach the VolumeThreshold before the next tariff switch boundary is crossed. The PrePaid capable PDSN shall monitor both the Volume and the Duration concurrently to support tariff switching... On-line Quota Update Procedure Requirements PrePaid capable PDSN shall terminate the session and generate the final online Access Request with the used quota if the online Access Accept is received with the following errors:. if the PPAQ received without quota-id subtype.. if the PPAQ received without Volume Quota subtype for a Volume based prepaid session.. if the PPAQ received without Duration Quota subtype for a Duration based prepaid session

19 if the PPAQ received without Volume Quota subtype and Duration Quota subtype for a concurrent Volume and Duration based prepaid session. The prepaid capable PDSN should set the volume threshold to an implementation specific value if the received volume threshold is not greater than the current volume used. This could prevent a loop of online Access-Requests and online Access-Accepts. The prepaid capable PDSN should set the duration threshold to an implementation specific value if the received duration threshold is not greater than the current duration used. This could prevent a loop of online Access-Requests and online Access-Accepts. When PPP is renegotiated at the PDSN, the prepaid capable PDSN shall terminate the prepaid session and generate online Access Access-Request with the used quota and update reason as Client-Service-Termination.. The PrePaid capable PDSN shall support on-line quota update on a service connection basis as identified by IP/NAI/SO/SI association.. The PrePaid capable PDSN shall include the Service Reference ID VSA defined in [] in the RADIUS Access-Request message and subsequent on-line RADIUS Access-Request messages. However at quota pre-initialization for auxiliary service connection, its value shall be zero. The main SI indicator in the Service Reference ID VSA shall only be included in the on-line RADIUS Access-Request messages associated with the main service connection.. The PDSN shall include the Message Authenticator (0) in on-line RADIUS Access- Request message and set the value as described in RFC []. Upon receiving an online RADIUS Access- Accept message, the PDSN shall validate the value of the Message-Authenticator as described in RFC []. The PDSN shall silently discard an on-line RADIUS Access-Accept message that does not contain a Message Authenticator Attribute.. The PrePaid capable PDSN shall provide usage of PrePaid resources in new PrePaid counters (i.e.,volumequota, VolumeUsedAfterTariffSwitch and/or DurationQuota) which represent the usage at the service connection level.. For a PrePaid packet data session, the used Volume reported in the VolumeQuota shall be incremented before compression and fragmentation by the number of octets in IP packets sent to the user.. For a PrePaid packet data session, the used Volume reported in the VolumeQuota shall be incremented after decompression by the number of octets in IP packets received from the user.. If the VSAs for Remote IP Address accounting are received and the Qualifier in the VSAs indicate that the IP traffic to and from the remote IP addresses is exempt from PrePaid charges, the PrePaid capable PDSN shall exclude the octet count from those IP packets in the VolumeQuota within the PPAQ VSA reported to the Home RADIUS/PPS.. Upon receiving a RADIUS Disconnect-Request message or MIP Registration Revocation message, the PrePaid capable PDSN shall send an on-line RADIUS Access-Request message containing the used quota and the Update-Reason Sub-Type set to Remote forced disconnect, and release the resources that will trigger sending the existing off-line RADIUS Accounting-Request (stop) message.. When a quota (volume or duration) assigned to the main service connection is consumed, the PrePaid capable PDSN shall release the main service connection and send an on-line RADIUS Access-Request message with Update-Reason Quota reached. Because the main service connection is released, the PrePaid capable PDSN shall release all auxiliary

20 service connections established by the MS. For each service connection, the PrePaid capable PDSN shall send an on-line RADIUS Access-Request message with Update- Reason Main SI released. 0. When the Quota for a service connection is consumed, the PrePaid capable PDSN shall release the associated service connection, regardless if other non-prepaid packet data sessions are active, and shall send an on-line RADIUS Access-Request message to report the used quota with the appropriate Update-Reason value Quota Reached.. If a threshold (e.g., VT or DT) is provided by the Home RADIUS/PPS, and is reached, the PrePaid capable PDSN shall send an on-line RADIUS Access-Request message to request a quota update. The Update-Reason shall be set to Threshold reached. The message shall include the VolumeQuota and/or DurationQuota in the PPAQ VSA and may include the PPAC VSA.. If the MS closes the PPP session or if the PPP session is closed in the PDSN, or if the MIP RRQ Lifetime has expired, the PrePaid capable PDSN shall send an on-line RADIUS Access-Request message with an Update-Reason indicating Client Service termination. An off-line RADIUS Accounting-Request message (Stop) with the appropriate release indicator shall be sent eventually.. If the PrePaid capable PDSN and the HA successfully negotiated Registration Revocation in MIP, the PrePaid capable PDSN shall send a MIP Registration Revocation message to the HA when the user s quota is consumed.. If a TariffSwitchInterval condition is reached during an accounting session, the PrePaid capable PDSN shall accumulate the subsequent volume traffic into the VolumeUsedAfterTariffSwitch counter and shall send an on-line RADIUS Access- Request message to the Home RADIUS/PPS when either VT is reached or when TariffIntervalafterTariffSwitchUpdate (TITSU) has expired, whichever comes first. The on-line RADIUS Access-Request message shall include the VolumeQuota (total quota used) in the PPAQ VSA and the thevolumeusedaftertariffswitch counter in the PTS VSA.. If VT is reached prior to expiration of TITSU, the PrePaid capable PDSN shall send an on-line RADIUS Access-Request message with the PPAQ VSA that includes the VQ Sub-Type, and the Update-Reason set to Threshold Reached and the PTS VSA that includes the VUATS Sub-Type. The PrePaid capable PDSN shall then discard TITSU. A new value of TSI and TITSU in a PTS VSA may be received in the on-line RADIUS Access-Accept message.. If TITSU has expired prior to VT, the PrePaid capable PDSN shall send an on-line RADIUS Access-Request message with the PPAQ VSA that includes the VQ Sub-Type, and the Update-Reason set to Tariff Switch Update and the PTS VSA that includes the VUATS Sub-Type.. If the Volume Quota is consumed in a middle of a packet, the PrePaid capable PDSN shall send the complete packet, release the resources and report back to the Home RADIUS/PPS with an on-line RADIUS Access-Request containing the PPAQ VSA. It shall return the used VolumeQuota and the Update-Reason Sub-Type set to Quota Reached.. If the PrePaid capable PDSN receives an on-line RADIUS Access-Reject message as a result of an on-line RADIUS Access-Request message, it shall release the corresponding service connection and send a final on-line RADIUS Access-Request message to report the used VolumeQuota and the Update-Reason Sub-Type set to Remote Forced Disconnect

21 Service Description for Concurrent Volume and Duration Based PrePaid at the PDSN As with volume based PrePaid, quota initialization for the main service connection is received in a RADIUS Access-Accept message during user authentication and authorization. Quota pre-initialization and initialization for the auxiliary service connections and subsequent quota updates use on-line RADIUS Access-Accept messages in response to on-line RADIUS Access-Request messages from the PrePaid capable PDSN. The Event-Timestamp () attribute shall be included in the RADIUS Access-Request message for initial quota allocation and subsequent on-line RADIUS Access-Request messages. The Event-Timestamp attribute () is used for DurationQuota/DurationThreshold allocation by the Home RADIUS/PPS. Upon receipt of the RADIUS Access-Accept message indicating that the PrePaid packet data service is allowed and which includes the initial VolumeQuata,DurationQuota, Quota ID and the VolumeThreshold and DurationThreshold for the main service connection in the PPAQ VSA, the PrePaid capable PDSN stores the information and starts measuring the volume and duration over the specific service connection against the allocated quota at successful PrePaid packet data session establishment (i.e., IP address assigned for Simple IP or MIP RRP received from the HA and sent to the MS). The PrePaid capable PDSN performs subsequent on-line quota update operation with the Home RADIUS/PPS when the VolumeThreshold value or DurationThreshold value is reached. At subsequent on-line quota update operation, the PDSN sends an on-line RADIUS Access-Request message containing the PPAQ VSA and which includes the Update-Reason Sub-Type to indicate Threshold reached, the Quota ID previously received, the used Volume and the used Duration in the VolumeQuata Sub-type and DurationQuota Sub-Type. The Home RADIUS/PPS apportions a fraction of the PrePaid account balance into a VolumeQuota and a VolumeThreshold, a DurationQuota and a DurationThreshold and assigns a Quota ID, all of which are encoded in a PPAQ VSA in the on-line RADIUS Access-Accept message to the PrePaid capable PDSN in response to the on-line RADIUS Access-Request message. The Home RADIUS/PPS assigns a new Quota ID to the allocated VolumeQuota and VolumeThreshold, DurationQuota and DurationThreshold at each quota update operation. If either VolumeQuota or DurationQuota is consumed before the PrePaid capable PDSN receives a response from the Home RADIUS/PPS for a quota update request or if the quota is consumed when either the VolumeQuota value and the VolumeThreshold value are the same or the DurationQuota value and the DurationThreshold value are the same, the PrePaid capable PDSN sends an on-line RADIUS Access-Request message containing the PPAQ VSA with the Update Reason indicating Quota Reached and releases the corresponding service connection. The PDSN sends the RADIUS Accounting-Request message (stop) to indicate the release of the service connection, per the existing off-line accounting procedures... Interaction with Remote IP Address Based Accounting The Prepaid capable PDSN performs Volume based Prepaid as X.S00-00-E [] section... Duration based PrePaid has no interaction with remote IP address based accounting as the duration of the session is not related to the remote destination/source of the packets.

22 .. Interaction with Flow Control over the A0 connection The Prepaid capable PDSN performs Volume based Prepaid as X.S00-00-E [] section... Duration based PrePaid has no interaction with the GRE flow control functionality... Interaction with Hot-Lining.. Sequence Diagrams The Prepaid capable PDSN performs Volume based Prepaid as X.S00-00-E [] section... Duration based PrePaid has no interaction with the Hot-lining functionality. Similar Sequence Diagrams as in X.S00-00-E [] section.. apply to concurrent Volume and Duration based PrePaid.... Successful PrePaid Authorization Similar to X.S00-00-E [] section... but the PrePaidAccountCapability VSA included in the RADIUS Access-Request message shall indicate concurrent Volume and Duration based PrePaid if supported by the PrePaid capable PDSN. The RADIUS Access- Accept message is returned indicating in the PPAC VSA that the PrePaid packet data service is based on concurrent Volume and Duration. The RADIUS Access-Accept message includes a PPAQ VSA to initialize the quota to be used on the main service connection. The Home RADIUS/PPS assigns a Quota ID to the initialized VolumeQuota and a VolumeThreshold, and the initialized DurationQuota and a DurationThreshold.... Volume Usage and Duration Usage until Account Depletion... Tariff Switch Similar to X.S00-00-E [] section... but the PPAQ VSA in the RADIUS Access- Accept message includes VolumeQuota, DurationQuota, VolumeThreshold and DurationThreshold Sub-Types. When the Quota or Threshhold of either volume or duration is reached, no matter whichever comes first, or when the Quota value and the Threshold value of either volume or duration are the same, the Prepaid capable PDSN shall interact with the PPS, the PPAQ VSA includes both the VolumeQuota and DurationQuota. For Concurrent Volume and Duration Based PrePaid, different tariff for different time of a day, the PPS shall allocate the quota so that the quota does not overlap the two charging rate

23 PrePaid Client in the HA The following subsections take precedence over the same-numbered sections of X.S00-00-E v.0 [].. Service Description for PrePaid at the HA If the HA supports a PPC, it shall also support Dynamic Authorization with RADIUS and Registration Revocation for MIP capabilities (see X.S00-00-E v.0 [] ). The HA is referred to as a PrePaid capable HA, and the PrePaid capability is based on the following principles: Upon receiving an initial MIP RRQ message, the PrePaid capable HA sends a RADIUS Access-Request message to the Home RADIUS server/pps, which includes the PPAC VSA, the STC VSA with value and the MIP RRQ Lifetime VSA containing the received RRQ lifetime Sub-Type. The PrePaid capable HA accepts an initial quota in the RADIUS Access-Accept message if it contains the PPAC VSA that indicates that PrePaid is allowed for the user. Subsequent on-line quota update operation is performed for a packet data session by the PrePaid capable HA using on-line RADIUS Access-Request/Accept messages. The on-line RADIUS Access-Request shall contain at least the attributes Message Authenticator, Service-Type set to authorize only and the PPAQ VSA. The on-line RADIUS Access-Accept message shall contain at least the PPAQ VSA. Off-line Accounting is not supported by the HA The Home RADIUS/PPS determines whether the HA or the PDSN should provide PrePaid packet data service for the user based on the Session Termination Capability (STC), the PPAC VSAs received from the PDSN and the HA, the user profile and the home network policy. The STC VSA, if received from the PDSN and the HA, indicates to the Home RADIUS/PPS that the resource management through both Dynamic Authorization with RADIUS and Registration Revocation for MIP are supported (See X.S00-00-E v.0 [] ). If the PDSN has not included the STC VSA in the RADIUS Access-Request and if the home network policy and the user profile allow, the Home RADIUS/PPS may allow duration based PrePaid packet data session to be provided by the PrePaid capable HA. In this case, the PrePaid packet data session may be controlled, by using the RRQ lifetime as an allocation unit for the DurationQuota and/or DurationThreshold to synchronize the MIP re-registration operation with the on-line quota update operation. The RRQ Lifetime received in the RRQ message is sent to the Home RADIUS/PPS server as a Sub-Type in the MIP Lifetime VSA. The Home RADIUS/PPS may send a new RRQ Lifetime in the RADIUS Access-Accept message towards the PrePaid capable HA, which the HA forwards to the PDSN in the MIP RRP message. If the PDSN has included the STC VSA (value ), the Home RADIUS/PPS may determine based on the home network policy, the user s profile if volume based or duration based or concurrent volume and duration based can be provided by the PrePaid capable HA. In this case, duration quota does not require to be synchronized with the RRQ Lifetime received in the MIP Lifetime VSA. Upon receiving a new MIP registration request, the PrePaid capable HA sends a RADIUS Access-Request message to the Home RADIUS/PPS. The RADIUS Access-Request message

24 includes the PPAC VSA, the MIP RRQ Lifetime VSA containing the RRQ Lifetime Sub- Type (value received in the RRQ message) and a newly generated Correlation ID VSA. Upon receiving a MIP re-registration request (same CoA) or a MIP registration for the same IP, NAI but different CoA, the PrePaid capable HA sends an on-line RADIUS Access- Request message to the Home RADIUS/PPS. The on-line RADIUS Access-Request message includes the PPAC VSA, the MIP Lifetime VSA containing the RRQ Lifetime Sub-Type (value received in the RRQ) and the Used Lifetime from Existing Session Sub-Type (value of used lifetime of the existing MIP session) and the Correlation ID VSA containing the same Correlation ID value that is in use at that time. If a RADIUS Access-Accept message is received and contains a PPAC VSA indicating PrePaid, the RADIUS Access-Accept message shall contain an initial quota. Subsequent online quota update operations shall use on-line RADIUS Access-Request messages with the quota allocation delivered in the on-line RADIUS Access-Accept messages. Off-line accounting procedures for the HA are not defined in this document.. Interaction with Remote IP Address based Accounting If attributes for remote address accounting are included in the RADIUS Access-Accept message, the qualifier Sub-Type is included to indicate to the PrePaid capable HA that the IP traffic to and from the remote IP addresses is exempt from the PrePaid charges. The PrePaid capable HA does not include the octet count from those IP packets in the totals reported to the Home RADIUS/PPS. See X.S00-00-E v.0 [] for updated Remote IPv/IPv Address and Remote Address Table Index VSAs.. Interaction with Flow Control over the A0 connection PrePaid at the HA has no interaction with the GRE flow control functionality.. Interaction with Hot-Lining If the PrePaid capable HA receives a RADIUS Access-Accept message indicating that PrePaid service should be provided and includes a PPAQ VSA and a Filter Rule VSA for New-Session Hot-Lining, the PDSN HA shall apply PrePaid service based on the rules indicated in the Filter Rule VSA. If the PrePaid capable HA receives a PPAQ VSA and an HTTP Redirection Rule or an IP Redirection Rule VSA for New-Session Hot-Lining, the HA shall apply the rule and shall not apply PrePaid until the Hot-Lining status is corrected. If the PrePaid capable HA receives an Active-Session Hot-Lining for a PrePaid session containing HTTP Redirection Rule VSA or IP Redirection Rule VSA, the HA send a CoA NAK message to the Home RADIUS server with Error-Cause 0 Administratively Prohibited. If the PrePaid capable HA receives an HTTP Redirection Rule or an IP Redirection Rule VSA in an on-line RADIUS Access-Accept message, it shall ignore the VSAs

25 Sequence diagrams.. Successful PrePaid Authorization PDSN Figure Flow Description: HA Access-Request (STC, correlation ID) Access_Accept (Reverse Tunneling) MIP RRQ MIP RRP Access-Request (RRQ lifetime, PPAC, correlation ID) Access-Accept (PPAC, PPAQ) Home RADIUS /PPS PrePaid authorization from the PrePaid capable HA a. The PDSN is not PrePaid capable. The PDSN receives a MIP RRQ from the MS and sends a RADIUS Access-Request message to the Home RADIUS/PPS, which includes a STC VSA indicating to the Home RADIUS/PPS that the PDSN can receive requests to close user s packet data sessions from authorized remote node. b. The Home RADIUS/PPS performs the regular Authentication and Authorization. The authorization includes the following tasks: the Home RADIUS/PPS verifies the home network policy and the user profile and determines that the user is a PrePaid user, checks if the PPAC is sent by the PDSN, in this scenario it is not, checks if the HA in the home network is configured to provide PrePaid, checks if the STC VSA is included. [Note: if the STC VSA is not included, the Home RADIUS/PPS may either reject the RADIUS Access-Request message or limit the service to duration based PrePaid only at the HA]. In this scenario, the STC VSA is sent by the PDSN. The Home RADIUS/PPS returns a RADIUS Access- Accept indicating that reverse tunneling shall be applied. The PDSN performs regular off-line accounting. c. The PDSN forwards the MIP RRQ to the PrePaid capable HA d. Upon receiving the MIP RRQ, the PrePaid capable HA sends a RADIUS Access-Request message to the Home RADIUS/PPS. The request shall contain the PPAC VSA, the STC VSA, a generated Correlation ID VSA and the MIP Lifetime VSA containing the RRQ Lifetime. e. The Home RADIUS/PPS performs authorization of the request and allows the PrePaid capable HA to provide PrePaid for the user. The Home RADIUS/PPS includes the PPAC VSA along with a PPAQ VSA containing an initial quota. If the PPAC VSA indicates support of concurrent Volume and Duration based PrePaid, the Home RADIUS/PPS may includes PPAQ VSA containing both a intial VolumeQuota and a initial DurationQuota a b c d e f

26 based on the user profile and the home network policy.a MIP Lifetime VSA may be included to contain an updated RRQ Lifetime, which is allocated based on the PrePaid user profile (i.e., Duration based PrePaid) and the local policy. However, since the PDSN has indicated support for Session Termination Capability, the MIP Lifetime VSA containing an updated RRQ Lifetime is not required in the RADIUS Access-Accept message. f. The PrePaid capable HA sends a successful MIP RRP to the PDSN, which it forwards to the MS. If a MIP Lifetime VSA is received from the Home RADIUS/PPS, the PrePaid capable HA includes the received RRQ Lifetime Sub-Type value in the MIP RRP... Volume Usage or Duration Usage until Account Depletion.. Tariff Switch Same as section... in X.S00-00-E [], with the exception of the off-line accounting messages (start and stop) sent at the beginning and end of the session. If Concurrent Volume and Duration Prepaid is used, the PPAQ VSA in the RADIUS Access-Accept message received from Home RADIUS/PPS includes VolumeQuota, DurationQuota, VolumeThreshold and DurationThreshold Sub-Types. When the Quota or Threshhold of either volume or duration is reached, no matter whichever comes first, or when the Quota value and the Threshold value of either volume or duration are the same, the Prepaid capable HA shall interact with the Home RADIUS/PPS, the PPAQ VSA includes both the VolumeQuota and DurationQuota. Same as section... in X.S00-00-E []. For Concurrent Volume and Duration Based PrePaid, different tariff for different time of a day, the Home RADIUS/PPS shall allocate the quota so that the quota does not overlap the two charging rate... Handoff from a PrePaid Capable PDSN to a Non-PrePaid Capable PDSN A PrePaid user established a PrePaid packet data session with a PDSN that has PrePaid and session termination capability. The MS performs handoff and moves to a new PDSN that does not have PrePaid and session termination capability. A RADIUS Access-Request message containing the same HA IP address is sent to the Home RADIUS/PPS from the new PDSN. The Home RADIUS/PPS determines that a PrePaid packet data session is ongoing at the previous PDSN. A RADIUS Disconnect-Request message is sent to the previous PDSN. The Home RADIUS/PPS allows the PrePaid Capable HA to provide Duration based PrePaid for the user if the user profile allows it... Handoff from a Non-PrePaid Capable PDSN to a PrePaid Capable PDSN This scenario is based on the Home RADIUS/PPS policy that allows the PrePaid capable HA to continue providing PrePaid packet data service for the user, even after the user moves to a new PDSN that has PrePaid capability

27 Previous PDSN (Non-PrePaid capable) Figure MS New PDSN (PrePaid capable) IP-IP tunnel MIP RRQ MIP RRP Flow Description: HA Access-Request (PPAC, STC) Access-Accept (PPAC=PrePaid Accounting not used) MIP RRQ MIP RRP Access-Request (PPAC, Correlation ID) Access-Accept (PPAC) on-line quota update operation Home RADIUS/ PPS Handoff from a Non-PrePaid to a PrePaid Capable PDSN a. A PrePaid user establishes a packet data session through a non-prepaid capable PDSN with session termination capabilities. In this scenario, it is assumed that the HA was allowed by the Home RADIUS/PPS to provide PrePaid packet data service for the user. b. The user moves to the coverage area of a PrePaid capable PDSN and send a MIP Registration Request through the PDSN. c. A RADIUS Access-Request message containing the same HA IP address used prior to handoff, the PPAC VSA and the STC VSA is sent to the Home RADIUS/PPS. d. The Home RADIUS/PPS sends a RADIUS Access-Accept message to the new PrePaid capable PDSN, and which may contain the PPAC VSA set to PrePaid Accounting not used or the PPAC VSA may be omitted. e. The New PDSN forwards the MIP RRQ to the HA f. The HA sends an RADIUS Access-Request message to the Home RADIUS/PPS. The request shall contain the PPAC, the Session Continue VSA, the same Correlation ID in use before the handoff and the MIP Lifetime VSA containing both the RRQ Lifetime Sub-Type (lifetime value received in the RRQ) and the Used Lifetime From Existing Session Sub-Type (value of used lifetime of the existing MIP session) if duration based PrePaid is being provided for the session. g. The Home RADIUS/PPS performs authorization of the request and based on the home policy allows the PrePaid capable HA to continue PrePaid packet data service for the user. The PPAC VSA is included in the response back to the HA. The HA continues to use the allocated quota. h. The HA returns the MobileIP Registration Reply to the PDSN. i. The PDSN send the MobileIP Registration Reply to the MS. a b c d e f g h i j