Revision as of 14:02, 21 February 2017

Overview

Service identifiers are, as the name suggests, used to identify a service or a component of a service. Many service types contain a single identifier to identify the service, known as the core service identifier. A home telephone line for example, will adopt the resident's phone number as the service identifier. A mobile service will use the mobile number. Other service types are more complex using multiple service identifiers to identify an entire service, or parts of a service. A number ranged service type will use one single number as the core identifier and a range of numbers as secondary identifiers.

The format of a service identifier will vary across different types of services. However, they all contain one or more of the following characteristics:

1. They are all unique to a service type.
2. They may be used to identify and rate usage.
3. One service identifier must be nominated as the 'core' service identifier.
4. Service identifiers may be used for provisioning.
5. Service identifiers may be used for authentication purposes.

Cumulus contains a Service Identifier Management module enabling users to manage multiple identifiers for a service. Since not all service types require identifier management the module is enabled on an as-needed basis. Should you require access to manage multiple service identifiers for a service, please raise a ticket to the Customer Service team.

Service Identifier Business Rules

The following rules apply to entering service identifiers.

• There cannot be more than 1 core service identifier covering the same date range as another core identifier.
• If a replacement core identifier is entered, the core identifier it is replacing will be automatically end dated to prevent overlap.
• Usage received for any service identifier received that is outside the active date range will fall into quarantine.
• Service identifiers cannot be backdated to a date prior to the service subscription start date.
• Service identifiers cannot be forward dated.
• Service identifiers are validated by the system. Different service types have different requirements the service identifier needs to use. E.g. an FNN, a username@realm, etc.

Service ID vs Service Identifier

It is important to know that the service ID and the service identifier are not the same.

The Service ID is the Emersion-generated unique number that identifies this service from all others in the system. The number is unique to the system. It is not known by, or displayed to, an end-user. You may give this number to our support team to identify the service if you ever need help with it.

The Service Identifier is the identifier known by the end-user of the service. It is unique to a service type, and displayed on the customer's invoice. Your customer may give this identifier to you when making a query regarding the service.

Core Service Identifier

The core service identifier may also referred to as the 'primary' identifier. This identifier is displayed on the customer's invoice in the service subscription section. It is also used to identify usage for rating where the service type includes a usage feed.

There cannot be more than 1 core service identifier covering the same date range. If a user enters a new core identifier, the system will prompt the user for a date from when this identifier will be used. The system will then end-date the existing core identifier automatically.

The core service identifier can be seen in several places in Cumulus. Here are the two obvious ones:

• On the Services > List screen.

• On the Customer > Service Subscriptions section.

• On the Customer > Service Subscription > Configuration users can edit the core identifier, subject to the business rules at the top of this article. Users can add additional service identifiers in the Service Identifier management screen.

=

Service Identifier Management

To manage service identifiers complete the steps below.

Nav: Customer > Service Subscription > Service Identifiers

The tab will open with any service identifiers listed in the table.

To add a new identifier, click the Add New Identifier button, and complete the fields as follows.

Service Identifier

Enter the service identifier.

Realm

Enter an optional realm if needed.

Password

Enter the password provided to the end user for authentication. This is used when the Authentication Identifier flag is enabled.

Vanity name

Use this field to override the service identifier with a client-friendly name that will display on the invoice and end user portal. e.g: Jack's Mobile, Collins Street Office, etc.

Identifier start date

Give the start date of the service identifier commences. This date will be used by the system to collect and rate usage. Be aware that usage prior to the start date will not be rated and will fall into quarantine. While a service identifier may not be unique across different service types, it is unique within the service type. While the system will allow 'duplicate' service identifiers, they cannot overlap in terms of start/end dates.

Identifier end date

Give an optional end date to the service identifier

Core Identifier flag

Tick this box if the service identifier you are entering is the core identifier. It is mandatory for all services to have a single service identifier marked as core.

Provisioning Identifier flag

Tick this box if the service identifier you are entering is used to provision. This is only required for service types with fully automated provisioning.

Authentication Identifier flag

Tick this box if the service identifier is used to authenticate the service. This is used in RADIUS based service types. If this is ticked, the password field will be displayed under the realm field, and prompt the user to enter a password.