A. Subscription-ID
B. 3GPP-Quota-Consumption-Time
C. Event-Trigger
D. Used-Service-Unit
E. Session-ID
F. Request-Service-Unit
A. active-charging service acme_acs url-blacklisting method exact-match rulebase acme_rulebase url-blacklisting action discard
B. active-charging service acme_acs url-blacklisting method exact-match rulebase acme_rulebase url-blacklisting action terminate-flow
C. active-charging service acme_acs url-blacklisting method http post url-blacklisting method http get rulebase acme_rulebase url-blacklisting action discard
D. active-charging service acme_acs url-blacklisting method http post url-blacklisting method http get rulebase acme_rulebase url-blacklisting action terminate-flow
A. dynamic IP address allocation to a subscriber
B. deep packet inspection
C. mobility management
D. dynamic policy control
E. charging
A. TCP
B. GRE
C. SCTP
D. UDP
E. DCCA
F. DCCP
A. HTTP header enrichment allows the operator to define a policy that inserts x-header fields into HTTP POST or GET request packets to provide specific subscriber information such as IMSI or MSISDN to the HTTP server without changing the protocol.
B. HTTP header enrichment is the process that allows HTTP headers to be compressed for optimal transfer across the network.
C. HTTP header enrichment allows the operator to define a policy that detects the HTTP packet that requires header enrichment. If a match occurs, the policy drops the packet, modifies the packet inline with quality of service definitions, or creates a log message and forwards the packet unmodified.
D. HTTP header enrichment is the process in which a HTTP packet is analyzed for missing or partial header fields. If missing fields are detected or incomplete, the Cisco ASR 5000 can then take action to insert a new header, repair an existing header, create a log entry, and forward the packet.
A. Application layer
B. Transport layer
C. Network layer
D. Data link layer
E. Presentation layer