Rel. 6 Gx Interface
Introduction
IMPORTANT:
Supported Networks and Platforms
License Requirements
Supported Standards
How it Works
Step | Description |
---|---|
1
|
|
2
|
Session manager allocates
IP address to MN.
|
3
|
Session manager sends
IMS authorization request to IMS Authorization service (IMSA).
|
4
|
IMSA creates a session
with the CRF on the basis of CRF configuration.
|
5
|
IMSA sends request
to DPCA module to issue the authorization request to selected CRF.
|
6
|
DPCA sends a CCR-initial
message to the selected CRF. This message includes the IP address allocated
to MN.
|
7
|
|
8
|
DPCA module calls
the callback function registered with it by IMSA.
|
9
|
After processing the
charging rules, IMSA sends Policy Authorization Complete message
to session manager.
|
10
|
The rules received
in CCA message are used for dynamic rule configuration structure
and session manager sends the message to ECS.
|
11
|
ECS installs the rules
and performs credit authorization by sending CCR-Initial to Online
Charging System (OCS) with CC-Request-Type set to INITIAL_REQUEST
to open the credit control session. This request includes the active
rule base ID and 3GPP specific attributes (for example, APN, QoS
and so on).
|
12
|
OCS returns a CCA-Initial
message to activate the statically configured rulebase and includes preemptive
credit quotas.
|
13
|
ECS responds to session
manager with the response message for dynamic rule configuration.
|
14
|
On the basis of response
for the PDP context authorization, Session Manager sends the response
to the MN and activates/rejects the call.
|
IMPORTANT:
Configuring IMS Authorization Service at Context Level
configure
context <context_name>
ims-auth-service <imsa_service_name>
p-cscf
table { 1 | 2 } row-precedence <precedence_value> { address <ip_address> | ipv6-address <ipv6_address> }
p-cscf
discovery { table { 1 | 2 } [ algorithm { ip-address-modulus | msisdn-modulus | round-robin } ] | diameter-configured }
policy-control
diameter
origin endpoint <endpoint_name>
diameter
dictionary <dictionary>
failure-handling
cc-request-type { any-request | initial-request | terminate-request | update-request } { diameter-result-code { any-error | <result_code> [ to <end_result_code> ] } } { continue | retry-and-terminate | terminate }
diameter
host-select row-precedence <precedence_value> table { 1 | 2 } host <host_name> [ realm <realm_name> ] [ secondary
host <host_name> [ realm <realm_name> ] ]
diameter
host-select reselect subscriber-limit <subscriber_limit> time-interval <duration>
diameter
host-select table { 1 | 2 } algorithm { ip-address-modulus | msisdn-modulus | round-robin }
end
IMPORTANT:
Applying IMS Authorization Service to an APN
configure
context <context_name>
apn <apn_name>
ims-auth-service <imsa_service_name>
end
Rel. 7 Gx Interface
Introduction
Supported Networks and Platforms
License Requirements
Supported Standards
Terminology and Definitions
Policy Control
IMPORTANT:
IMPORTANT:
IMPORTANT:
Charging Control
IMPORTANT:
Charging Correlation
Policy and Charging Control (PCC) Rules
IMPORTANT:
IMPORTANT:
IMPORTANT:
PCC Procedures over Gx Reference Point
Request for PCC rules
Provisioning of PCC rules
Selecting a PCC Rule for Uplink IP Packets
IMPORTANT:
Selecting a PCC Rule and IP CAN Bearer for Downlink IP Packets
IMPORTANT:
Volume Reporting Over Gx
License Requirements
Feature Overview
IMPORTANT:
IMPORTANT:
IMPORTANT:
IMPORTANT:
Usage Monitoring
Usage Reporting
IMPORTANT:
How Rel. 7 Gx Works
Step | Description |
---|---|
1
|
UE (IMS subscriber)
requests for primary PDP context activation/creation.
|
2
|
SessMgr allocates
an IP address to the UE.
|
3
|
SessMgr requests IMS
Authorization, if IMSA is enabled for the APN.
|
4
|
IMSA allocates resources
for the IP CAN session and the bearer, and selects the PCRF to contact based
on the user's selection key (for example, msisdn).
|
5
|
IMSA requests the
DPCA module to issue an auth request to the PCRF.
|
6
|
DPCA sends a CCR initial
message to the selected PCRF. This message includes the Context-Type
AVP set to PRIMARY and the IP address allocated to the UE. The message
may include the Bearer-Usage AVP set to GENERAL. The Bearer-Operation
is set to Establishment. The Bearer ID is included if the PCRF does
the bearer binding.
|
7
|
PCRF may send preconfigured
charging rules in CCA, if a preconfigured rule set for general purpose
PDP context is provided in PCRF. The dynamic rules and the authorized
QoS parameters could also be included by the PCRF.
|
8
|
DPCA passes the charging
rule definition, charging rule install, QoS information received
from the PCRF, event triggers, and so on, along with the Bearer
ID that corresponds to the rules received from the PCRF to IMSA.
IMSA stores the information. If the Bearer ID is absent, and PCRF
does the bearer binding, the rule is skipped. Whereas, if the Bearer
ID is absent and the PCEF does the bearer binding, the rule is passed
onto the ECS to perform bearer binding.
|
9
|
DPCA calls the callback
function registered with it by IMSA.
|
10
|
IMSA stores the bearer
authorized QoS information and notifies the SessMgr. Other PCRF provided
information common to the entire PDP session (event trigger, primary/secondary
OCS address, and so on) is stored within the IMSA. After processing
the information, IMSA notifies the SessMgr about the policy authorization
complete.
|
11
|
If the validation
of the rules fails in IMSA/DPCA, a failure is notified
to PCRF containing the Charging-Rule-Report AVP. Else, IMSA initiates
creation of ECS session. The APN name, primary/secondary
OCS server address, and so on are sent to the ECS from the SessMgr.
|
12
|
ECS performs credit
authorization by sending CCR(I) to OCS with CC-Request-Type set
to INITIAL_REQUEST to open the credit control session.
This request includes the active Rulebase-Id (default rulebase ID
from the APN/AAA) and GPRS specific attributes (for example,
APN, UMTS QoS, and so on).
|
13
|
OCS returns a CCA
initial message that may activate a statically configured Rulebase
and may include preemptive quotas.
|
14
|
ECS responds to SessMgr
with the response message.
|
15
|
SessMgr requests IMSA
for the dynamic rules.
|
16
|
IMSA sends the dynamic
rules to SessMgr.
Note that until the
primary PDP context is established, all RAR messages from the PCRF
are rejected.
|
17
|
SessMgr sends the
dynamic rule information to the ECS. The gate flow status information
and the QoS per flow (charging rule) information are also sent in
the message.
|
18
|
ECS activates the
predefined rules received, and installs the dynamic rules received.
Also, the gate flow status and the QoS parameters are updated by
ECS as per the dynamic charging rules. The Gx rulebase is treated
as an ECS group-of-ruledefs. The response message contains the Charging
Rule Report conveying the status of the rule provisioning at the
ECS. ECS performs PCEF bearer binding for rules without bearer ID.
|
19
|
If the provisioning
of rules fails partially, the context setup is accepted, and a new
CCR-U is sent to the PCRF with the Charging-Rule-Report containing
the PCC rule status for the failed rules. If the provisioning of
rules fails completely, the context setup is rejected.
|
20
|
Depending on the response
for the PDP Context Authorization, SessMgr sends the response to
the UE and activates/rejects the call. If the Charging-Rule-Report
contains partial failure for any of the rules, the PCRF is notified,
and the call is activated. If the Charging-Rule-Report contains
complete failure, the call is rejected.
|
21
|
Based on the PCEF
bearer binding for the PCC rules at Step 18, the outcome could be
one or more network-initiated PDP context procedures with the UE
(Network Requested Update PDP Context (NRUPC) / Network
Requested Secondary PDP Context Activation (NRSPCA)).
|
IMPORTANT:
Configuring IMS Authorization Service at Context Level
configure
context <context_name>
ims-auth-service <imsa_service_name>
p-cscf
discovery table { 1 | 2 } algorithm { ip-address-modulus | msisdn-modulus | round-robin }
p-cscf
table { 1 | 2 } row-precedence <precedence_value> { address <ip_address> | ipv6-address <ipv6_address> } [ secondary { address <ip_address> | ipv6-address <ipv6_address> } ]
policy-control
diameter
origin endpoint <endpoint_name>
diameter
dictionary <dictionary>
diameter
request-timeout <timeout_duration>
diameter
host-select table { { { 1 | 2 } algorithm { ip-address-modulus | msisdn-modulus | round-robin } } | prefix-table { 1 | 2 } }
diameter
host-select row-precedence <precedence_value> table { { { 1 | 2 } host <host_name> [ realm <realm_id> ] [ secondary
host <host_name> [ realm <realm_id> ] ] } | { prefix-table { 1 | 2 } msisdn-prefix-from <msisdn_prefix_from> msisdn-prefix-to <msisdn_prefix_to> host <host_name> [ realm <realm_id> ] [ secondary
host <sec_host_name> [ realm <sec_realm_id> ] algorithm { active-standby | round-robin } ] } } [ -noconfirm ]
diameter
host-select reselect subscriber-limit <subscriber_limit> time-interval <duration>
failure-handling
cc-request-type { any-request | initial-request | terminate-request | update-request } { diameter-result-code { any-error | <result_code> [ to <end_result_code> ] } } { continue | retry-and-terminate | terminate }
end
IMPORTANT:
Applying IMS Authorization Service to an APN
configure
context <context_name>
apn <apn_name>
ims-auth-service <imsa_service_name>
active-charging
rulebase <rulebase_name>
end
Configuring Volume Reporting over Gx
configure
active-charging
service <ecs_service_name>
rulebase <rulebase_name>
action
priority <priority> dynamic-only ruledef <ruledef_name> charging-action <charging_action_name> monitoring-key <monitoring_key>
exit
exit
context <context_name>
ims-auth-service <imsa_service_name>
policy-control
event-update
send-usage-report [ reset-usage ]
end
Gathering Statistics
Statistics/Information | Action to perform |
---|---|
Information and statistics
specific to policy control in IMS Authorization service.
|
show ims-authorization policy-control
statistics
|
Information and statistics
specific to the authorization servers used for IMS Authorization service.
|
show ims-authorization servers
ims-auth-service
|
Information of all
IMS Authorization service.
|
show ims-authorization service
all
|
Statistics of IMS Authorization
service.
|
show ims-authorization service
statistics
|
Information, configuration,
and statistics of sessions active in IMS Authorization service.
|
show ims-authorization sessions
all
|
Complete information,
configuration, and statistics of sessions active in IMS Authorization service.
|
show ims-authorization sessions
full
|
Summarized information
of sessions active in IMS Authorization service.
|
show ims-authorization sessions
summary
|
Complete statistics
for active charging service sessions.
|
show active-charging sessions
full
|
Information for all
rule definitions configured in the service.
|
show active-charging ruledef
all
|
Information for all
rulebases configured in the system.
|
show active-charging rulebase
all
|
Information on all
group of ruledefs configured in the system.
|
show active-charging group-of-ruledefs
all
|
Information on policy
gate counters and status.
|
show ims-authorization policy-gate { counters | status }
This command is no
longer an option in StarOS release 11.0 and beyond.
|
Rel. 8 Gx Interface
HA/PDSN Rel. 8 Gx Interface Support
Introduction
License Requirements
Supported Standards
Terminology and Definitions
Policy Control
Gating Control
Event Reporting
IMPORTANT:
IMPORTANT:
QoS Control
IMPORTANT:
Other Features
PCC Rule Error Handling
Time of the Day Procedures
Charging Control
IMPORTANT:
IMPORTANT:
Policy and Charging Control (PCC) Rules
IMPORTANT:
IMPORTANT:
PCC Procedures over Gx Reference Point
Request for PCC Rules
Provisioning of PCC Rules
Selecting a PCC Rule for Uplink IP Packets
IMPORTANT:
Selecting a PCC Rule for Downlink IP Packets
IMPORTANT:
How it Works
Step | Description |
---|---|
1
|
UE (IMS subscriber)
requests for MIP Registration Request.
|
2
|
SessMgr allocates
an IP address to the UE.
|
3
|
SessMgr requests IMS
Authorization, if IMSA is enabled for the subscriber.
IMSA service can either
be configured in the subscriber template, or can be received from
the AAA.
|
4
|
IMSA allocates resources
for the IP-CAN session, and selects the PCRF to contact based on
the user's selection key (for example, round-robin).
|
5
|
IMSA requests the
DPCA module to issue an auth request to the PCRF.
|
6
|
DPCA sends a CCR initial
message to the selected PCRF.
|
7
|
PCRF may send preconfigured
charging rules in CCA. The dynamic rules and the authorized QoS parameters
could also be included by the PCRF.
|
8
|
DPCA passes the charging
rule definition, charging rule install, QoS information received
from the PCRF, event triggers, etc. IMSA stores the information.
|
9
|
DPCA calls the callback
function registered with it by IMSA.
|
10
|
PCRF-provided information
common to the entire IP-CAN session (event trigger, primary/secondary
OCS address, etc.) is stored within the IMSA. After processing the
information, IMSA notifies the SessMgr about the policy authorization
complete.
|
11
|
If the validation
of the rules fails in IMSA/DPCA, a failure is notified
to PCRF containing the Charging-Rule-Report AVP. Else, IMSA initiates
creation of ECS session. The primary/secondary OCS server
address, etc. are sent to the ECS from the SessMgr.
|
12
|
ECS performs credit
authorization by sending CCR(I) to OCS with CC-Request-Type set
to INITIAL_REQUEST to open the credit control session.
This request includes the active Rulebase-Id (default rulebase ID
from the AAA).
|
13
|
OCS returns a CCA
initial message that may activate a statically configured Rulebase
and may include preemptive quotas.
|
14
|
ECS responds to SessMgr
with the response message.
|
15
|
SessMgr requests IMSA
for the dynamic rules.
|
16
|
IMSA sends the dynamic
rules to SessMgr.
Note that until the
MIP session is established, all RAR messages from the PCRF are rejected.
|
17
|
SessMgr sends the
dynamic rule information to the ECS. The gate flow status information
and the QoS per flow (charging rule) information are also sent in
the message.
|
18
|
ECS activates the
predefined rules received, and installs the dynamic rules received.
Also, the gate flow status and the QoS parameters are updated by
ECS as per the dynamic charging rules. The Gx rulebase is treated
as an ECS group-of-ruledefs. The response message contains the Charging
Rule Report conveying the status of the rule provisioning at the
ECS.
|
19
|
If the provisioning
of rules fails partially, the context setup is accepted, and a new
CCR-U is sent to the PCRF with the Charging-Rule-Report containing
the PCC rule status for the failed rules. If the provisioning of
rules fails completely, the context setup is rejected.
|
20
|
Depending on the response
for the MIP Session Authorization, SessMgr sends the response to
the UE and activates/rejects the call. If the Charging-Rule-Report
contains partial failure for any of the rules, the PCRF is notified,
and the call is activated. If the Charging-Rule-Report contains
complete failure, the call is rejected.
|
Configuring HA/PDSN Rel. 8 Gx Interface Support
IMPORTANT:
Configuring IMS Authorization Service at Context Level
configure
context <context_name>
ims-auth-service <imsa_service_name>
policy-control
diameter
origin endpoint <endpoint_name>
diameter
dictionary <dictionary>
diameter
request-timeout <timeout_duration>
diameter
host-select table { 1 | 2 } algorithm
round-robin
diameter
host-select row-precedence <precedence_value> table { 1 | 2 } host <primary_host_name> [ realm <primary_realm_id> ] [ secondary host <secondary_host_name> [ realm <secondary_realm_id> ] ] [ -noconfirm ]
failure-handling
cc-request-type { any-request | initial-request | terminate-request | update-request } { diameter-result-code { any-error | <result_code> [ to <end_result_code> ] } } { continue | retry-and-terminate | terminate }
exit
exit
diameter
endpoint <endpoint_name> [ -noconfirm ]
origin
realm <realm_name>
use-proxy
origin
host <host_name> address <ip_address>
no
watchdog-timeout
response-timeout <timeout_duration>
connection
timeout <timeout_duration>
connection
retry-timeout <timeout_duration>
peer <primary_peer_name> [ realm <primary_realm_name> ] address <ip_address> [ port <port_number> ]
peer <secondary_peer_name> [ realm <secondary_realm_name> ] address <ip_address> [ port <port_number> ]
end
Applying IMS Authorization Service to Subscriber Template
configure
context <context_name>
subscriber default
encrypted
password <encrypted_password>
ims-auth-service <imsa_service_name>
ip
access-group <access_group_name> in
ip
access-group <access_group_name> out
ip
context-name <context_name>
mobile-ip
home-agent <ip_address>
active-charging
rulebase <rulebase_name>
end
Gathering Statistics
Statistics/Information | Action to perform |
---|---|
Information and statistics
specific to policy control in IMS Authorization service.
|
show ims-authorization policy-control
statistics
|
Information and statistics
specific to the authorization servers used for IMS Authorization service.
|
show ims-authorization servers
ims-auth-service
|
Information of all
IMS Authorization service.
|
show ims-authorization service
all
|
Statistics of IMS Authorization
service.
|
show ims-authorization service
statistics
|
Information, configuration,
and statistics of sessions active in IMS Authorization service.
|
show ims-authorization sessions
all
|
Complete information,
configuration, and statistics of sessions active in IMS Authorization service.
|
show ims-authorization sessions
full
|
Summarized information
of sessions active in IMS Authorization service.
|
show ims-authorization sessions
summary
|
Complete statistics
for active charging service sessions.
|
show active-charging sessions
full
|
Information for all
rule definitions configured in the service.
|
show active-charging ruledef
all
|
Information for all
rulebases configured in the system.
|
show active-charging rulebase
all
|
Information on all
group of ruledefs configured in the system.
|
show active-charging group-of-ruledefs
all
|
Information on policy
gate counters and status.
|
show ims-authorization policy-gate { counters | status }
This command is no
longer an option in StarOS release 11.0 and beyond.
|
P-GW Rel. 8 Gx Interface Support
Introduction