If you have subscribers that are not managed on a separate policy charging and rules function (PCRF), you can create static subscribers. Static subscribers are individual subscribers of services that are not managed by a separate policy server. You can add static subscribers directly to the Policy Enforcement Manager, and assign enforcement policies to them. Each subscriber can have one or more enforcement policies associated with them.
You can use static subscribers alone or in combination with those managed by a PCRF.
|E.164||A numbering plan that defines the format of an MSISDN international phone number (up to 15 digits). The number typically consists of three fields: country code, national destination code, and subscriber number.|
|IMSI||International Mobile Subscriber Identity. A globally unique code number that identifies a GSM, UMTS, or LTE mobile phone user.|
|NAI||Network Access Identifier. A fully qualified network name in the form <user>@<realm>; identifies a subscriber and the home network to which the subscriber belongs.|
|Private||The subscriber ID type is private for the given deployment.|
You can upload a list of static subscribers for policy enforcement on the BIG-IP system. A CSV file is a text file in a comma-separated-values format. Microsoft Excel can be used to view and create such files. The list of subscribers must be in a text file in comma separated value (CSV) format.
Each line of the CSV file represents one subscriber in the format:subscriber_ID,subscriber_ID_type,subscriber_IP,policy_1,policy_2,policy_n
You must include Subscriber ID and at least one policy enforcement policy for each subscriber. You need to include the comma for missing fields. Do not include spaces between values. The policies listed must be included on the policies list in, and be provisioned using a listener or a policy enforcement profile.
For example, to specify subscriber 8315555555 in IMSI format with a gold policy, you can leave out the subscriber ID type and subscriber IP address:8315555555,,,gold