Nexus Telecom

1
Nexus Telecom

• NexusHOP Receiver
• Sales / VAR Training

2
Real Time BillingNew Challenge

• Data collection
• The network element must support a reliable
  application protocol that transmits
  charge-related data to the billing platform in
  real-time.
• The data collection is not done on demand but
  as soon as the relevant information is available.
• Billing
• The billing platform must support an event driven
  architecture that means as soon new accounting
  data is sent to the billing system, it must be
  processed immediately.

3
HOT Billing Definition

• Transmit call and charge data immediately after
  generation

4
Hot Billing Benefits

• Operator benefits
• Rapid access to the charging information for
  statistics and fraud prevention
• Immediate provision of current charge information
  for further processing
• Subscriber benefits
• Knowledge of the current bill amount at any time

5
Hot Operation Protocol (HOP)

• Reliable transmit all charge related data from a
  switch to a server
• Implemented by Siemens for SURPASS (hiQ9200 V4)
  and EWSD (V15) switching
• Charge related data include
• AMA records
• IN AMA records
• IACAMA records

6
Variants of HOP

• Tickets can be transmitted in
• Near Real Time
• All generated AMA tickets are transferred via HOP
• Transmission is performed within minutes after
  generation
• Real Time
• Tickets for a limited number of subscribers is
  transferred via HOP
• Transmission is performed within seconds after
  generation

7
Variants of Real Time HOPTCP/IP Only

• Non Usage Sensitive Real Time Billing
• Tickets are normally send via HOP for the HOP
  enabled subscribers
• All tickets (HOP and non-HOP) are available on
  the switch and are marked whether they have been
  send successfully or not
• Usage Sensitive Real Time billing
• Tickets are normally send via HOP for the HOP
  enabled subscribers
• A backup is available for the tickets that could
  not be transmitted successfully
• Nexus HOPReceiver will automatically pull the
  backup data in case of failure.
• No risk of data loss!

8
Restrictions of HOP

• For Real Time for switch set up for 250.000
  subscribers the maximum HOP enabled subscribers
  is 2
• For Near Real Time this restriction does not
  apply
• Usage Sensitive Real Time is only offered on a
  TCP/IP enabled transport. On X.25 only Non Usage
  Sensitive is available

9
Nexus HOPReceiver

• First implementation to serve Siemens Hot
  Operation Protocol
• Supports
• Near Real Time
• Real Time, Usage Sensitive
• Real Time, Non-usage Sensitive
• TCP/IP transport
• Single switch, Multiple receiver
• Multiple switch, Singe receiver

10
Data CollectionSiemens HOP
SiemensEWSD-Surpass
Alternatepath
Central Processor
Caller A
Caller B
CDRs
HOP
TCP/IP or X.25
FTP (TCP/IP) FTAM (X.25)
Hot Operation Protocol Receiver
Billing Center
NexusDBS (Billing System)

• Nexus supports the Hot Operation Protocol (HOP)
  for real time and near real-time data collection.
• Real-Time (RT) Data collection within a few
  seconds
• Near Real-Time (NRT) Data collection within a
  few minutes

11
NexusHOPReceiverData Transfer Options
HOP Receiver A
X.25
Switch 1
Switch 2
ADC (Mediation)
TCP/IP
HOP Receiver B
TCP/IP
Switch 3
DB
12
NexusHOPReceiver Availability

• Release 1.0 (November 2004)
• TCP/IP support
• High Availability support
• Windows 2000 tested
• Release 1.1 (April 2005)
• X.25 support
• Sun Solaris, Linux, HP-UX tested