100 likes | 280 Views
ADSL. IN. L. SCP. SCP. T. I . AN. T. R. FNR. ILR. L . CCN. I. SCP. HLR. GMSC. GSM. GMSC. HLR. SCP. T. TDMA. MSC. BSC. MSC. MSG. MSC. GPRS. PCU. GGSN. CSCF. T. MS BTS. IPMM/SIP. SGSN. TeS. Internet. AXE TSP CPP WPP AXD EAR TMOS/CIF. AS. HSS. AN.
E N D
ADSL IN L SCP SCP T I AN T R FNR ILR L CCN I SCP HLR GMSC GSM GMSC HLR SCP T TDMA MSC BSC MSC MSG MSC GPRS PCU GGSN CSCF T MS BTS IPMM/SIP SGSN TeS Internet AXE TSP CPP WPP AXD EAR TMOS/CIF AS HSS AN “MGW” 3G UMTS ATM Back bone RNC OSS AXE 10 Minutes, AXE based nodes
Soft Real Time AXE 10 minutes, Processors Central Processor Central Processor Hard Real Time Regional Processor Adjunct Pro,( I/O) Adjunct Pro,( I/O) Application Hardware
AXE 10 Minutes, SW Maintenance • Corrections/patches are introduced without disturbance • New SW packages are introduced in the stand-by side, inherits data from the executive-side and are switch in with a system restart => yearly disturbance
AXE 10 Minutes, Low Level Recovery A ‘forlopp’ identity, FID, is tied to each resource included in a ‘transaction’, typically a a call or a command. The processing platform provides support for creation of FID and in case of an execution error, identifies all resources concerned and orders release over a standard interface. Fx Fx Fx Fx Forlopp handler
AXE 10 Minutes, SW Recovery SW Error Low Level Recovery 99,8% No Action Filter 0,1% < 0,1% System Restart
Application SW Application SW Same Same Same APZ-CP OS APZ-CP OS ASA- compiler APZ-VM OS API HAL MIP OS (Tru64™) HW HW (-procesor) AXE 10 Minutes, CP ’Classic‘ vs ‘Modern’
AXE 10 Minutes, Multi-threaded Execution • Must be 101% compatible with application SW (includes fault compatibility!) • The problem is not to make it work • The real problem is to make an efficient implementation with limited over-head including the cost for cache coherency