Navigation
Back up to About Overview
[+] Expand All
[-] Collapse All
Symbols
- 3GPP
- 3GPP gateway
- charging rule
- charging rule installation
- charging rule removal
- charging rule report
- Charging-Rule-Base-Name
- Charging-Rule-Install
- Charging-Rule-Name
- configuration statements
- configuration summary
- directory-connection
- directory-eventing
- file logging
- grouped configurations
- Gx interface
- initial properties
- Juniper-Substitution
- Juniper-Substitution-Name
- Juniper-Substitution-Value
- local properties
- managing
- NIC proxies
- NIC proxy
- non-parameterized charging rule
- object adapter Internet address
- overview
- parameterized charging rule
- PCRF
- peer communication
- restarting
- SAE
- service accounting
- service activation sequence
- service deactivation sequence
- service modification sequence
- session termination sequence
- starting
- stopping
- subscriber login sequence
- subscriber logout sequence
- subscriber type
- system logging
- 3GPP Gy
- configuration statements
- configuration summary
- directory-connection
- directory-eventing
- file logging
- grouped configurations
- initial properties
- interface
- local properties
- managing
- NIC proxies
- NIC proxy
- object adapter Internet address
- overview
- peer communication
- restarting
- service activation sequence
- service deactivation sequence
- starting
- stopping
- subscriber login sequence
- subscriber logout sequence
- subscriber type
- system logging
- 3GPP Gy NIC proxies
A
- Application Services Gateway. See Web Services Gateway
- arguments for scripts and methods
- ASG (Application Services Gateway). See Web Services Gateway
B
- B2B environments
- business partner responsibilities
- business partners
- business-to-business environments
C
- classify-traffic condition
- expanded classifiers
- clients
- configuration namespace
- conventions
- customer support 1
D
- Diameter
- documentation
- dynamic properties
- Dynamic Service Activator
- access constraints
- access to attributes
- access to methods
- access to methods and scripts
- access to scripts
- access to service sessions
- API
- attributes
- configuring with C-Web interface
- configuring with SRC CLI
- gateway extension
- general properties
- groups
- interacting with Web application server 1, 2
- loading
- logging properties
- configuring, C-Web interface 1, 2
- configuring, SRC CLI
- methods 1
- monitoring with SRC CLI
- NIC proxies, monitoring
- NIC proxies, viewing
- overview
- properties for clients and scripts
- redundancy
- sample data 1, 2
- scripts
- service sessions
- session handles
- SOAP operations, monitoring
- SOAP operations, viewing
- starting with C-Web interface
- starting with SRC CLI
- statistics, viewing
- subscriber types
- test environment
- configuring, SRC CLI 1, 2
- PCMM services
- testing 1
E
G
- gateway
- gateway extension
I
- IMS service sessions
- configuring
- test environment
- testing 1, 2
L
M
- managing
- SAE via external applications 1, 2
- services via external application
- manuals
- methods
N
- namespace, configuration
- NIC (network information collector)
- Dynamic Service Activator and
- testing
- test data 1, 2
- test data, 3GPP Gy
- NIC proxies
- notice icons
O
- operation
P
R
S
- SAE (service activation engine)
- configuring 3GPP gateway as external plug-in
- configuring 3GPP Gy as external plug-in
- configuring IMS as external plug-in
- managing via external applications 1, 2
- scripts
- services
- sessions
- service
- SOAP
- SRC owners 1
- SRC SOAP Gateway. See Web Services Gateway
- static properties
- support, technical See technical support
T
- technical support
- text conventions defined
W
- Web application gateway client
- Web application server 1
- Web applications
- Web Services Description Language. See WSDL
- Web Services Gateway 1
- clients 1
- Web application
- wholesaler-retailer environments
- WSDL files
Running Methods for PCMM Services (SRC CLI)
To run a method for the PCMM Web service interface:
- Run the test dsa pcmm-service command.user@host> test dsa pcmm-service (commit-resources | release-resources | query-contexts | query-available-services)
where:
- commit-resources—Specifies the resources that are being requested in the CommitResource message.
- release-resources—Specifies the resources that are being requested to be released in the ReleaseResources message.
- query-contexts—Searches for the context ID and context status for a subscriber.
- query-available-services—Searches for the services that are available to the calling application.
- Testing Resource Requests (SRC CLI)
- Testing Resource Release Requests (SRC CLI)
- Testing Queries for Subscriber Contexts (SRC CLI)
- Testing Queries for Available Services (SRC CLI)
Testing Resource Requests (SRC CLI)
Use the following command to test the method that specifies the resources that are being requested in the CommitResource message:
test dsa pcmm-service commit-resources <subscriber-address subscriber-address> <subscriber-uri subscriber-uri> service-name service-name <context-id context-id> <time-usage-limit time-usage-limit> <classifier classifier> <traffic-profile traffic-profile> <flow-spec flow-spec> <client-id client-id> <client-password client-password>
To test the method:
- Issue the test dsa pcmm-service commit-resources command.
- To specify the name of the SRC service, use the service-name option.
- (Optional) To specify the IP address of the subscriber, use the subscriber-address option.
- (Optional) To specify the subscriber’s Uniform Resource Identifier (URI), use the subscriber-uri option.
- (Optional) To specify the globally unique identifier that the application manager must use if it is included in the message, use the context-id option. The context ID is used as the SRC session name when the PCMM gateway activates a service.
- (Optional) To specify a limit on the lifetime of a context, use the time-usage-limit option. An application server may specify multiple time usage limits to request different limits in the upstream and downstream directions. If the application server does not specify a time usage limit, the application manager determines the time usage limit.
- (Optional) To specify the object that identifies the traffic flow for which the application server is requesting services, use the classifier option.
- (Optional) To specify information about the bandwidth and QoS characteristics desired for a request, use the traffic-profile option. You express the traffic profile by configuring the SRC policies with FlowSpec, service class name, or DOCSIS actions.
- (Optional) To specify a FlowSpec action, use the flow-spec option.
- (Optional) To specify the username that Dynamic Service Activator uses to authenticate this client, use the client-id option.
- (Optional) To specify the password that Dynamic Service Activator uses to authenticate this client, use the client-password option.
Testing Resource Release Requests (SRC CLI)
Use the following command to test the method that specifies the resources that are being requested to be released in the ReleaseResources message:
test dsa pcmm-service release-resources <subscriber-address subscriber-address> <subscriber-uri subscriber-uri> <service-name service-name> <context-id context-id> <client-id client-id> <client-password client-password>
To test the method:
- Issue the test dsa pcmm-service release-resources command.
- (Optional) To specify the IP address of the subscriber, use the subscriber-address option.
- (Optional) To specify the subscriber’s Uniform Resource Identifier (URI), use the subscriber-uri option.
- (Optional) To specify the name of the SRC service, use the service-name option.
- (Optional) To specify the globally unique identifier that the application manager must use if it is included in the message, use the context-id option. The context ID is used as the SRC session name when the PCMM gateway activates a service.
- (Optional) To specify the username that Dynamic Service Activator uses to authenticate this client, use the client-id option.
- (Optional) To specify the password that Dynamic Service Activator uses to authenticate this client, use the client-password option.
Testing Queries for Subscriber Contexts (SRC CLI)
Use the following command to test the method that searches for the context ID and context status for a subscriber:
test dsa pcmm-service query-contexts <subscriber-address subscriber-address> <subscriber-uri subscriber-uri> <service-name service-name> <context-id context-id> <client-id client-id> <client-password client-password>
To test the method:
- Issue the test dsa pcmm-service query-contexts command.
- (Optional) To specify the IP address of the subscriber, use the subscriber-address option.
- (Optional) To specify the subscriber’s URI, use the subscriber-uri option.
- (Optional) To specify the name of the SRC service, use the service-name option.
- (Optional) To specify the globally unique identifier that the application manager must use if it is included in the message, use the context-id option. The context ID is used as the SRC session name when the PCMM gateway activates a service.
- (Optional) To specify the username that Dynamic Service Activator uses to authenticate this client, use the client-id option.
- (Optional) To specify the password that Dynamic Service Activator uses to authenticate this client, use the client-password option.
Testing Queries for Available Services (SRC CLI)
Use the following command to test the method that searches for the services that are available to the calling application:
test dsa pcmm-service query-available-services <client-id client-id> <client-password client-password>
To test the method:
- Issue the test dsa pcmm-service query-available-services command.
- (Optional) To specify the username that Dynamic Service Activator uses to authenticate this client, use the client-id option.
- (Optional) To specify the password that Dynamic Service Activator uses to authenticate this client, use the client-password option.
Related Documentation
- Testing the Web Application Gateway Client
- Sample Data for Dynamic Service Activator
- Running Methods and Scripts for Dynamic Service Activator Services (SRC CLI)
- Configuring the Test Environment for PCMM Services
