1. Subscriber Event Service Help
  2. Using SES Feature Nodes

2 Using SES Feature Nodes

This chapter explains how SES uses ACS. This includes details on the SES specific feature nodes that are used in the ACS Control Plan Editor (CPE). These check subscribers on entering or leaving a network using SES and determine whether to send them messages and if so, determine the number of messages to be sent.

For an overview of ACS and the ACS Control Plan Editor, see the relevant ACS or CPE user's guides.

This chapter contains the following topics.

In-Roamer Contact Check

In-Roamer Messages Selection

Out-Roamer Contact Check

Out-Roamer Messages Selection

In-Roamer Contact Check

When a roaming subscriber enters your network, this node checks the duration since any previous inbound roaming contact with the subscriber, by looking up the contact history, and compares the duration with the period of days configured in the node.

Node exits - In-Roamer Contact Check

This node has one entry and two exits. The number of exits cannot be changed.

Exit Cause Description
1 Contacted The subscriber has been contacted within the configured number of days.
2 Not Contacted The subscriber has not been contacted within the configured number of days (includes never been contacted and any system failures).

Using the node - In-Roamer Contact Check

For descriptions of how this node is used, refer to the following topics in SES User's and Technical Guide:

  • Example Control Plan - In-Roamer

  • Example scenarios

Configuring the node - In-Roamer Contact Check

Follow these steps to edit the node.

  1. Type a value in days in the Period field.

    Note: Blank or zero means the subscriber will be contacted every time they enter the network.

  2. Click Save.

In-Roamer Messages Selection

This node selects the messages for sending to the subscriber, based on the message priority, the number of messages to be sent, and the message selection option used. For more information, see SES User's and Technical Guide, System Overview chapter.

Node exits - In-Roamer Messages Selection

This node has one entry and two exits. The number of exits cannot be changed.

Exit Cause Description
1 No Messages Selected No messages were selected (includes system failures).
2 Messages Selected At least one message was selected.

Using the node - In-Roamer Messages Selection

For descriptions of how this node is used, refer to the following topics in SES User's and Technical Guide:

  • Example Control Plan - In-Roamer

  • Example scenarios

Editing the node - In-Roamer Messages Selection

Follow these steps to edit the In-Roamer Messages Selection node.

  1. Type the maximum number of messages to send to the subscriber in the Number field.

    Note: Currently the maximum is about 2 billion.

  2. Select either the Random or Latest message Selection Method.

    Note: Messages are configured to be priority, or non priority (see SES User's and Technical Guide, SES Configuration - Messages Tab). For either option, the priority messages are used to fulfill the Number parameter before the non priority messages. See SES User's and Technical Guide, SES Example scenarios.

    Note: Latest is the message with the most recent availability date.

  3. Click Save.

Out-Roamer Contact Check

When a roaming subscriber leaves your network, this node checks the duration since any previous out-roaming contact with the subscriber, by looking up the contact history, and compares the duration with the period of days configured in the node.

Node exits - Out-Roamer Contact Check

This node has one entry and three exits. The number of exits cannot be changed.

Exit Cause Description
1 Opted Out

The subscriber has opted out of being contacted on leaving the network.

Note: This flag is configurable. Refer to SES User's and Technical Guide, macroNodes configuration, for the value of the tag used.

2 Contacted The subscriber has been contacted within the configured number of days.
3 Not Contacted The subscriber has not been contacted within the configured number of days (includes never been contacted and any system failures).

Using the node - Out-Roamer Contact Check

For descriptions of how this feature node is used, see the following topics in Subscriber Event Service User's and Technical Guide:

  • Example Control Plan - Out-Roamer

  • Example scenarios

Configuring the node - Out-Roamer Contact Check

Follow these steps to edit the node.

  1. Type a value in days in the Period field.

    Note: Blank or zero means the subscriber will be contacted every time they exit the network.

  2. Click Save.

Out-Roamer Messages Selection

This node selects the messages for sending to the subscriber, based on the message priority, the number of messages to be sent, and the message selection option used. For more information, see the discussion of system overview in Subscriber Event Service User's and Technical Guide.

Node exits - Out-Roamer Messages Selection

This node has one entry and two exits. The number of exits cannot be changed.

Exit Cause Description
1 No Messages Selected No messages were selected (includes system failures).
2 Messages Selected At least one message was selected.

Using the node - Out-Roamer Messages Selection

For descriptions of how this feature node is used, see the following topics in Subscriber Event Service User's and Technical Guide:

  • Example Control Plan - Out-Roamer

  • Example scenarios

Configuring the node - Out-Roamer Messages Selection

Follow these steps to edit the Out-Roamer Messages Selection node.

  1. Type the maximum number of messages to send to the subscriber in the Number field.

    Note: Currently this is about 2 billion.

  2. Select either the Random or Latest message Selection Method.

    Note: Messages are configured to be priority or no priority (see Messages). For either option, the priority messages are used to fulfill the Number parameter before the no priority messages. See SES Example scenarios.

    Note: Latest is the message with the most recent availability date.

  3. Click Save.