Capacitacion VE Arquitectura 2017
Capacitacion VE Arquitectura 2017
Capacitacion VE Arquitectura 2017
INDEX
LOGICAL ARCHITECTURE
TASK COMMUNICATION
MECHANISM
Self-care web
– This application is a service offered to the subscribers in which, from a PC or a
mobile phone with access to the Internet, they will be able to manage their
services once he has validated his number with an access key.
– Internet Explorer or Firefox can be used to access the Self-care web from the
graphic interface.
– Customer can carry out in this web most of the operations defined for them,
such as query their call details or manage their lists.
› During the manufacturing time, before the cards are associated to the
MSISDN, the new lines are in initial state, e. i. not registered in the
network neither in the AltamirA platform.
› Subscription begins when the provider sends the physical SIM cards to
the operator and the states changes to preactive.
› Preactive blocked
› The MSISDN is registered in the HLR and in the AltamirA platform.
› Customer can not receive or send calls or SMS, as it is restricted in the
HLR.
› Preactive unblocked
› Account is subscribed in the SDP and HLR restrictions are updated.
› Unblocking process can be requested automatically by configuration or
manually.
› Customer can make voice calls and send SMS, but can not receive
them.
› If the operator wishes to have control over the sales department, it should
use the "Preactive blocked" state, requiring to the dealers or sales points to
'unblock' the line at the moment of the sale, to avoid fraud.
› An expiration time before activation can be configured, so the lines that are
not sold shall be released or freed.
› All restrictions for each state can be configured and customized to fit the
operator specific needs.
› The line will remain active for a configurable period of time. This
period is refreshed after a top up.
› Outgoing calls and SMS are restricted, but still can receive them.
› The line can be a configurable maximum amount of days in this state before
being automatically released and changed to 'freed/released' state. In case
the suspension was requested by the customer, its original state is restored.
› The recovering process will recover the line's information and can be used
normally, keeping previous conditions before suspension: state, promotions,
timers, etc.
› pp_startprocess / pp_stopprocess
– Is in charge of the boot and halt of the processes in a certain order and a
configurable parameterization (PP_PROCESOS y PP_PROCPARAMS
tables). It checks the correct operation of the processes and launches them
if they are down.
– PPGA_INSTANCE variable in PPGA_CONFIGURACION
– The process generates a file, named pp_startprocess.up, in the /tmp
directory. This file is deleted when the application is stopped.
– In the PP_PROCESOS table, there is a record per each process, with the
process code, the binary name, the path where it is located, the number of
instances it
– In the PP_PROCPARAMS there are recorded all parameters to launch
each process
– For example, the pp_ga_solrec (SREC) process knows which table it has
to read to process the tasks by querying the PP_PROCTABTAR table. At
the same time it knows which tasks it must process by querying the
PP_TARPROC table.
– Sending processes
› PPGA sending processes check the database for pending operations
and process it when found.
– Listening processes
› Process incoming confirmation/notification from OPGE node.
› Analyze returned data from OPGE and update all necessary tables in
PPGA database. The pending operation in the main operations table
inserted by the request process updates its status.
› Analyze the data sent from OPGE and update all necessary
tables in PPGA database. An record is created in main
operations table with its final status.
The sending may be configured per action, status of the action, user,
tariff plan… (PPGA_CONFNOTEXT for external notifications and
PPGA_CONFEDR for EDRs).
› Task configuration
› Processes configuration
› Operations configuration
› Promotions configuration
› The configuration of the memory areas and the semaphores that are to be
created are located in the table POCO_CONFIPC.
- The configuration of the start and stop of the application is made by means of
the following tables: POCO_ARRANQUE, POCO_PARADA and
POCO_PROCESOS.
ADVANCED | Ericsson | 2014-03-25 | Page 68
Prepaid Operator (OPGE)
Process Architecture
› The CAP starts the batch process when a scheduler or a Tuxedo service
requests it. This process admits an undefined number of parameters.
› Two behaviours:
› Among others, it manages the next execution date, process that will
receive the request, process that originated it, info of the request, etc
› This process is po_co_plaprosis (system process scheduler).
› It is supported by the tables POCO_PLANIFICA (PLA),
POCO_PLANIFHLR (PLH), POCO_PLANIFSDP (PLD),
POCO_PLANIFSMS (PLS), where the following is stored
› Maintenance processes
Card Expiries: po_ge_mancadtar
Promotion Expiries: po_ge_mancadpro
Card Expiry Warnings po_ge_manavicad
Promotion Expiry Warnings: po_ge_manavipro
– PIA processes
› The PIA processes (IGE insertion processes) receive the messages
from the answerers and, according to the PPGA petition received, they
insert a record in the table POCO_OPERAxxx corresponding to the
answer to be sent.
› Besides, they store the input parameters received. Once the record has
been inserted, it sent the petition to the corresponding managing
process.
› Tuxedo services
› The Tuxedo services operate in the same way as in other nodes: They
are used to make certain type of calls to the operator. Ex.: Balance
query, management of lists from SIPS, etc.
› Most of the OPGE tuxedos are query ones.
› MES process:
› Allow to follow operation steps by showing the events on the screen:
› View modes:
› Mode 2: Only warning and error events are displayed (yellow and red)
› Top up tables
› Configuration tables
› PPCS receives the files with all the information of the voice calls, SMSs and
any traffic case the customer can perform.
› Receive the files from the SDP, processes and stores them in the database.
› Generic interface
› Generic interface
› Generic interface
› The listener receives as parameter the listening port when it is launched.
› Depending on this port, the listener knows whether it has to receive call
CDRs or short message CDRs.
› A temporal directory to receive the file till its download has been
completed.
› An input directory where the responder process will move the file once
fully downloaded.
› An error directory to move the CDRs with problems or errors during the
processing.
› Finally, tables where the processed files are controlled are updated:
PPCS_ARCHIVOS (information about files coming from the OCS-RE) and
PPCS_ARCH_DET (detailed information per type of records of the files coming
from the OCS-RE).
› SIN_ERRORES: 0 errors
› Fraud control
› Wholesalers management
› Administrative code:
› Not encrypted
› If a MAS direct child dies, the MAS process will try to respawn it.
› MRM: Receives messages from OPGE and starts the responder RRM
› PEI: Receives messages from SIP and starts the responder PRI
› Maintenance processes
› Tuxedo
› MES process: Allow to follow operation steps by showing the events on the
screen.
› View modes
› Mode 2: Only warning and error events are displayed (yellow and red)
› Each generation request administrative code identifies it and allow to query for
the request status
› The generated codes are stored in the system for further use and query. The
system also generates an encypted file containing the codes for distributing to
the cards manufacturers
› Once the cards are made they are sent to the sales channel
› State between the Active and the Used states. The top-up voucher will be in
this temporal state while the systems carry out the required checks and
increase the customer's balance.
› Used
› The voucher reaches this state when it is correctly used to make a top-up.
› SIP connects to the RASCA node in AltamirA and sends the top up request
› The listener process PEI receives the connection and spawns a responder PRI.
PRI receives the request data and sends it to a top up manager GTR. The
manager will check:
› The code inserted by the customer is associated to a card that exists in the
system
› OPGE will validate the customer and report back to RASCA the
operation is been processed. A request to the SDP is sent to increase
customer balance
› OPGE will also report to SIP the final status of its original top up
request. It will also notify to PPGA a top up has been made to apply
later top up logic (e.g. promotions)
› Others
O&M. Counters
System behavior and usage is logged in the form of counters that reflect what is
demanded to S2T and what is the statistical outcome of the system. This
component is responsible for generating counter files and save them, it also
controls if there is enough disk space to generate the counter or in other case
arises the proper alarm.
Finally, it is responsible for sending counter files using TCP sockets to OCS-ME
periodically. When the file is sent it is removed from S2T machine.
OCS-MS
ASN.1 ASN.1
External Notification A External Notification B
SOAP Notification
Center
SOAP SOAP
ExternalNotification A ExternalNotification B
IT System IT System
Notication Notication
consumer 1 consumer N
ADVANCED | Ericsson | 2014-03-25 | Page 132
SNC – SOAP Notification
Center
INTRODUCTION
› Examples of the events that can generate external notifications are:
– Top-Ups
– Adjustment
– Automatic changes in the lifecycle of the subscriber
– First usage: first call/sms/mms/data traffic/sertacon charge
– Promotions launched by Altamira
– Multiple recharge autocancelled
– Cyclic actions. For example, for a cyclic charge, every time there is a
change of status, an external notification has to be generated.
– With regard to wallets, when the balance has decreased below a configured
threshold or a wallet is close to its expiry date, a notification can be sent to
the subscriber.
– In connection with bolt ons, it is possible to configure the generation of an
external notification in case of:
› Bolt On subscription
› Bolt On unsubscription
ADVANCED | Ericsson | 2014-03-25 | Page 133
SNC – SOAP Notification
Center
INTRODUCTION
› Examples of the events that can generate external notifications are:
› Bolt On expiration
› Bolt On threshold reached
› Bolt On renewal
› Last Bolt on renewal
› Reminder: X days before each renewal
› Last Reminder: X days before the end of the last cycle
– End of the last cycle: End of the cyclic action
•The client (SNC) receives the external notification ASN.1 and decodes it. If a
decoding error occurs a NACK must be sent to PPGA.
•If no decoding error occurs SNC maps the ASN.1 request to a SOAP request.
This mapping process depends on the kind of notification and the parameters
received. If an error mapping occurs a NACK must be sent to PPGA
•If no mapping error occurs the SOAP message is sent to the server (IT
Notification Consumer) while the client (SNC) blocks waiting for the response.
Affected Nodes:
•SNC
•PPGA
•CPS
Counters Handling
SNC shall store statistical information into physical files. The information to store
should be relevant to the business and to the operation and maintenance of the
service..
SNC must send this files using FTP or SFTP to an external system responsible of
processing and accumulating them for statistical and monitoring purposes.
The generation of counter files and the sending of them to an external system are
features that must be configurable in the SNC
› System that receives requests for the generation of access keys which
come from the external IVRs. It generates the anonymous key to
access the web server and transfers it to the user via a short message
or a registered letter.
› The Products and Services Centre (called CPS, for its initials in Spanish) is the
interface for configuring and parameterizing the system functionalities. It
allows the network operator’s personnel (those with the necessary privileges)
to load the configuration parameters via a user-friendly and simple interface. A
browser (Internet Explorer, Mozilla Firefox, etc.) can be used to access CPS
from the graphical interface.
› The objective of the CPS is to provide an interface for the end users that allows
them to modify, without having to make requests for development, some
configuration parameters concerning the platform behaviour, especially those
related to the commercial offer that the network operator makes to their end
customers.
ADVANCED | Ericsson | 2014-03-25 | Page 141
Annexes
CPS Features
› By using this tool, the DB team will maintain control over the changes
performed by the network operators.
› The user will be able to save existing configurations and recover them later.
› Consumption controls
› Global parameterization
› Rateable services
› Web browser