Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on

  • Be the first to comment

  • Be the first to like this


  1. 1. Intelligent Networks Park Jung Wan ( Kang Tai Hun ( < Telephone & Internet Telephony Networks >
  2. 2. Contents <ul><li>Introduction </li></ul><ul><li>Related standard </li></ul><ul><li>Operation procedure </li></ul><ul><li>Technical issues </li></ul><ul><li>The method of performance evaluations of the systems </li></ul><ul><li>Others </li></ul>
  3. 3. Introduction <ul><li>System which is attractive to subscriber and create new earnings can be introduced quickly? </li></ul><ul><li>Smallest change of network? </li></ul><ul><li>Adaptive System to subscriber’s taste which is changed? </li></ul><ul><li>There is no solution, because network is composed of MSC which is difficult to be changed quickly </li></ul><ul><li>Survival solution in extreme competition circumstance is quick and adaptive service to subscriber </li></ul><ul><li>Service network delivered easily is needed </li></ul>Intelligent Network Introduction! <ul><li>Specification have started from early in 1990’ </li></ul><ul><li>Wired communication network is first adapted </li></ul><ul><li>Introduction in Korea </li></ul><ul><li>- KT->SST->SKT->KTF->HST->LGT </li></ul>BSC MSC BTS MS SC HLR STP SSP IP SMP SCP No.7 No.7/ISUP No.7/ISUP No.7 No.7 TCP/IP TCP/IP Intelligent Network • SMP: Service Management Point • SCP: Service Control Point • IP: Intelligent Peripheral • SC: Subscriber Center • BTS: Base station Transceiver Subsystem • BSC: Base Station Controller • STP: Signal Transfer Point • HLR: Home Location Register • SSP: Service Switching Point • MSC: Main Switching Center • MS: Mobile Station • ISUP: ISDN User Part
  4. 4. Related Standard (1) <ul><li>IN Standard History </li></ul>Europe SMG GSM MAP NA6 INAP ITU-T SG 11/6 IN CS-1 SG 11/8 FPLMTS North America SG 11/6 IN CS-1 SG 11/8 IS-41 CTM INAP+ UMTS CAMEL IN CS-2 ANSI IN Phase 1 WIN Phase 1 IN CS-3 ANSI IN Phase x WIN Phase x Cellular PCS/PCN 3G • GSM: Global System for Mobile communication • MAP: Mobile Application Part • Intelligent Network Application Protocol • CS: Capability Set • UMTS: Universal Mobile Telecommunication System • IN: Intelligent Network • ANSI: American National Standard Institute • IS: International Standard • FPLMTS: Future Public Land Mobile Telecommunication System • WIN: Wireless Intelligent Network • PCS: Personal Communication Service • CAMEL: Customized Applications for Mobile network Enhanced Logic
  5. 5. Related Standard (2) <ul><li>Adapted IN Standard </li></ul><ul><li>Dual Stack Architecture </li></ul>• PDSN: Packet Data Serving Node • AAA: Authentication Authorization Accounting • SMSC: Short Message Service Center • SGSN: Serving GPRS Support Node • GGSN: Gateway GPRS Support Node • IMX: IMT2000 Mobile Exchange • CA : CAMEL Application Part Release 1999 Phase 3 : 3G TS 22.078, 23.078, 29.078 Phase 1 : TIA/EIA/IS-771 TIA/EIA/IS-826, IS-848 IN CS-1 (Q. 121x) IN CS-2 (Q. 122x) CAMEL WIN ITU-T SC SMP SCP IP SSP MSC SMSC PDSN AAA HLR HLR IMX SMSC SGSN GGSN No.7 / ISUP No.7 / ISUP No.7 / ISUP WIN(No.7) WIN(No.7) (No.7) 3G MAP (No.7) 3G MAP (No.7) CAP (No.7) WIN(No.7) WIN / CAP (No.7) TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP Dual Stack IN 2G 3G
  6. 6. Operation Procedure (1) <ul><li>IN Service Registration </li></ul>Creation of subscriber information in HLR, SMP(SCP) DB <ul><li>MS Location Registration </li></ul>Location of MS is registration in HLR and Intelligent Service Information of subscriber is delivered from HLR to VLR (1) (2) (2) (4) (1) (2) BTS BSC MSC/VLR STP HLR Service registration request SC SMP HLR SCP
  7. 7. Operation Procedure (2) <ul><li>IN Service Origination </li></ul>for example ) Prepaid voice call origination MSC/SSP IP SCP Origination MS Announcement Delivering and connection & release to gather DTMF Command achievement result Resource control command Call control command Triggering and Event report (1) Call of prepaid subscriber is triggering to SCP (2) SCP authenticates intelligent subscriber (3) Deliver announcement prepaid remainder to MS (4) SCP commands progressing call routing to termination MSC will page & connect to termination MS (5) If MS requests to release call, MSC reports call release to SCP (6) SCP account and update DB (charge deduction in prepaid remainder for this call) Termination MS MSC
  8. 8. Technical issues <ul><li>Security issue </li></ul><ul><ul><li>Evolution toward IP network </li></ul></ul><ul><ul><li>Cost effective </li></ul></ul><ul><ul><li>Flexibility </li></ul></ul><ul><ul><li>Security problem </li></ul></ul><ul><ul><li>: easy to access system </li></ul></ul><ul><li>Load balancing issue </li></ul><ul><ul><li>SCP A : not available </li></ul></ul><ul><ul><li>↓ </li></ul></ul><ul><ul><li>SCP B : single SCP </li></ul></ul><ul><ul><li>Dual SCP (active & active) </li></ul></ul><ul><ul><li>DB sync. </li></ul></ul>SCP A SCP B DB No. 7 IP
  9. 9. The method of performance evaluations of the systems <ul><li>“Performance evaluation of AIN (Advanced Intelligent Networks) supporting mobile communications” </li></ul><ul><li>(Y.W Chung, M.Y Chung, Y,H Kwon, and D.K Sung, IEEE, 1997) </li></ul><ul><li>AIN architectures supporting mobile communication </li></ul><ul><ul><li>Functional reference model </li></ul></ul><ul><ul><li>AIN architecture scenario </li></ul></ul><ul><li>Signaling procedures </li></ul><ul><li>Performance evaluation </li></ul><ul><ul><li>Signaling load </li></ul></ul><ul><ul><li>Processing load </li></ul></ul><ul><ul><li>Processing delay </li></ul></ul>
  10. 10. AIN architectures supporting mobile communication (1) <ul><li>Functional reference model </li></ul><ul><ul><li>Functional (logical) entity </li></ul></ul>
  11. 11. AIN architectures supporting mobile communication (2) <ul><li>AIN architecture scenario </li></ul><ul><ul><li>Functional (logical) entity -> physical entity </li></ul></ul><ul><ul><li>Comparison of network architectures </li></ul></ul>
  12. 12. Signaling procedures <ul><li>Mobility related </li></ul><ul><ul><li>Location update (Intra-SSP, Inter-SSP) </li></ul></ul><ul><ul><li>Handoff (Intra-BSC, Inter-BSC, Inter-SSP) </li></ul></ul><ul><li>Call related </li></ul><ul><ul><li>Call origination </li></ul></ul><ul><ul><li>Call termination </li></ul></ul><ul><ul><li>Call release </li></ul></ul><ul><li>UPT outgoing and incoming calls </li></ul>
  13. 13. Performance evaluation (1) <ul><li>Signaling load </li></ul><ul><ul><li>Comparison of signaling load on various links (messages / sec) </li></ul></ul>
  14. 14. Performance evaluation (2) <ul><li>Processing load </li></ul><ul><ul><li>Comparison of processing load on various physical entities (messages / sec) </li></ul></ul>
  15. 15. Performance evaluation (3) <ul><li>Processing delay </li></ul><ul><ul><li>Assumption </li></ul></ul><ul><ul><ul><li>Each functional entity is simply modeled by an M/M/1 queueing model. </li></ul></ul></ul><ul><ul><ul><li>The propagation delay on each signaling link is ignored. </li></ul></ul></ul><ul><ul><li>Processing delay in the case of intra-SSP location update </li></ul></ul>Network 1,3,5 Network 2,4
  16. 16. <ul><li>Current problem Deploying new Service </li></ul>Others : OSA (Open Service Architecture) / Parlay (1) <ul><li>Each new service accesses systems in it’s own way </li></ul><ul><li>It makes systems complex and spends high cost & much time </li></ul><ul><li>Especially, if M&A occurs, this architecture gives much load to operator </li></ul>SDP Introduction <ul><li>Each new service accesses systems in a standard way </li></ul><ul><li>Systems are connected into standard SDP </li></ul><ul><li>System can be changed without affecting services that use the system </li></ul><ul><li>Time & Cost Effective !! </li></ul><ul><li>Improving way using SDP </li></ul>• SDP: Service Delivery Platform
  17. 17. Others : OSA / Parlay (2) <ul><li>OSA/Parlay is the common term used to refer to an industry-standard that underpins many SDPs now in development. </li></ul><ul><li>The OSA/Parlay standard defines an API that aids the rapid creation of telecommunications services by enabling IT application developers to create telecom services </li></ul>The Parlay APIs – What do they offer? • API: Application Programming Interface Connectivity Management Account Management Data Session Control Framework Common Data Definitions General Content based Charging Messaging Terminal Policy management Availability management and presence Mobility User Interaction Call Control