Subscription Profile Repository (SPR) Release 9.1 Subscriber Provisioning Reference Manual Table 133: Interfaces supporting policy data manipulation Note: When using the XML (TCP/SOAP) or XML-REST interfaces, the Public Identity is generated by the SPR based on the primary key configured at installation of the system (MSISDN, IMSI, or NAI), and the SubscriptionID is automatically defined by the SPR with the same value as the Public Identity value.
XML (TCP/SOAP) interface considerations When provisioning Policy profiles and their Subscriber and Pool profile data using the XML interface, you must create XML requests to define the Policy data or manipulate (update, select, delete, etc.) the quota/poolquota, dynamic quota/pooldynamicquota, or state/poolstate data. These XML requests can then be sent either through SOAP or directly over a TCP socket (in batch mode using the CommandFileLoader or Command Template loader. See also User Interfaces . For more information on: How to provision using SOAP or TCP, refer to chapter User Interfaces in the SDM Subscriber Provisioning User Guide .
XML requests examples to provision policy data, refer to chapter Examples of XML templates for subscriber provisioning in the SDM Subscriber Provisioning User Guide . XML-REST interface considerations Prior to being able to provision policy profiles and their Subscriber or Pool profile data using the XML-REST interface, the RAS Server must be configured properly in the system. Note: Tekelec configured the RAS server at installation of the system. Contact the Tekelec Customer Care Center for installation issues.
253 910-6701-001 Revision A, June 2013 Provisioning Interface Elements of the Subscriber and Pool profiles Other elements outside of the policy profiles (Tekelec ngHLR, etc.) Subscriber/Pool profile Quota PoolQuota Dynamic Quota/ Pool Dynamic Quota State/ Pool State *XML/TCP, XML/SOAP Read/write (per field) Read/write (per field) Read/write (as a blob) Read/write (as a blob) Read/write (per field) XML-REST Read/write (per field) Read/write (per field) Read/write (as a blob) Read/write (as a blob) n/a WebCI Read/write (per field) Read/write (per field) Read-only (as a blob) Read-only (as a blob) Read/write (per field) CLI Read/write (per field) Read/write (per field) Read-only (as a blob) Read-only (as a blob) Read/write (per field) LDAP Read-only (per field) Read-only (as a blob) Read-only (as a blob) Read-only (as a blob) Read-only (per field) *XML/TCP and XML/SOAP are also referred to as XML.
Both, XML and XML-REST are referred to as XML interfaces in the provisioning documentation.