1 / 32

A Common Framework for Integrating Wireless, Wireline and Internet Networks

A Common Framework for Integrating Wireless, Wireline and Internet Networks. PROJECT GROUP: Maurizio Bonuccelli Piero Lauri Francesca Martelli Renata Bandelloni. JAIN FOR MAP. Cellular Systems. The geographic area is divided into cells

leola
Télécharger la présentation

A Common Framework for Integrating Wireless, Wireline and Internet Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Common Framework forIntegrating Wireless, Wireline and Internet Networks PROJECT GROUP: • Maurizio Bonuccelli • Piero Lauri • Francesca Martelli • Renata Bandelloni JAIN FOR MAP PISATEL

  2. Cellular Systems • The geographic area is divided into cells • Each cell has a Base Station managing the communications • A set of cells managed by a single MSC is called Location Area MSC VLR HLR land link land link VLR MSC BaseStation Radio link MSC Mobile Switching Center VLR Visitor Location Register HLR Home Location Register PISATEL

  3. Functional Planes • TRASMISSION: manage the trasmissive medium • COMMUNICATION MANAGEMENT: provides the means to control user communications • MOBILITY MANAGEMENT: manage the databases for the location of any mobile station • RADIO RESOURCE MANAGEMENT: provides a stable link between MS and MSC CM MM RR TRASMISSION PISATEL

  4. GSM ARCHITECTURE NSS Network and Switching Subsystem EIR Equipment Identity Register AuC Authentication Center GMSC Gateway MSC BSS Base Station System BSC Base Station Controller BTS Base Transceiver Station MS Mobile Station SSP Service Switching Point PLMN Databases EIR VLR VLR HLR AuC PSTN MSC MSC GMSC SSP NSS Switches SSP BSS BSC BSS MS BTS Radio Systems PISATEL

  5. G D H EIR VLR VLR HLR AuC C C F B B E E SMSgwy MSC MSC GMSC A BSC Abis BTS The interfaces Each entity communicate with each other through the appropriate interface PISATEL

  6. Call-related signaling No call-related signaling MAP ISUP TCAP SCCP MTP3 MTP2 MTP1 The SS7 Signaling protocol • TCAP (TRANSACTION CAPABILITIES APPLICATION PART): provides the capability to exchange information between applications using non-circuit related signaling • SCCP (SIGNALING CONNECTION CONTROL PART): realyze both connectionless and connection oriented network service and provides additional functions such as Global Title Translation • MTP (MESSAGE TRANSFER PART): three levels corresponding to the OSI physical layer, data link layer and network layer. • ISUP (ISDN User Part): used to setup and release calls • MAP (Mobile Application Part): used for signaling related to a number of services PISATEL

  7. Services of the MAP protocol PISATEL

  8. GSM MAP Service Framework The GSM entities communicate with each other to carry out some service, through MAP dialogues by invoking one of four MAP primitives: • REQUEST • INDICATION • RESPONSE • CONFIRM PISATEL

  9. Common services of MAP • OPEN and CLOSE MAP dialogue • Data DELIMITER • User ABORT • Provider ABORT • Provider NOTICE PISATEL

  10. GSM MAP service model DIALOGUE INITIATOR DIALOGUE RESPONDER MAP Service User MAP Service User 1 4 3 2 REQUEST CONFIRM RESPONSE INDICATION MAP Service Provider MAP Service Provider PISATEL

  11. The Short Message Service • Not requiring the end-to-end establishment of a traffic path • Asymmetric: Mobile Originating Short Message trasmission is considered as a different service from Mobile Terminating Short Message trasmission • Ultimate destination (identified by some field in the message) is relevant only for the user and the SMSC, not for the GSM infrastructure PISATEL

  12. MAP Services for SMS • Provision of routing information • Forwarding of Mobile Originating and Mobile Terminating SMS message • Delivery status reporting • Alert service centre • Miscellaneous information services PISATEL

  13. MAP Primitives for SMS • FROM MSC TO VLR (B): MAP_SEND_INFO_FOR_MO_SM MAP_SEND_INFO_FOR_MT_SM • FROM SMSgwy TO HLR (C): MAP_SEND_ROUTING_INFO_SM MAP_REPORT_SM_DELIVERY_STATUS • FROM HLR TO SMSgwy (C): MAP_ALERT_SERVICE_CENTRE MAP_INFORM_SERVICE_CENTRE • FROM MSC TO HLR (D, via VLR): • MAP_READY_FOR_SM • FROM MSC TO SMSgwy (E): • MAP_MO_FORWARD_SM • FROM SMSgwy TO MSC (E): • MAP_MT_FORWARD_SM D VLR HLR B C E SMSgwy MSC SMSC PISATEL

  14. Protocols in the Short Message Service D E C BSC MSC/VLR SMS-gwy HLR BTS MS SM-TP SM-RP MAP MAP SM-CP TCAP TCAP LAPD SS7 SS7 SS7 PISATEL

  15. Submit SM Forward MO SM Ack Ack Send routing info Routing info Forward MT SM Nack (MS2 switched off) Report SM waiting Ack MS2 switched on Report ready for SM Ack Alert SMSC Ack Forward MT SM Deliver SM Ack Ack Example: short message (SM) E D MSC1 + VLR MSC2 + VLR SMSgwy + SMSC C MS1 MS2 HLR PISATEL

  16. MAP dialogue for SMS SMS-gwy HLR MAP User MAP User MAP_Open_IND() MAP_Open_REQ() MAP_SendRoutingInfoForSM_REQ() MAP_SendRoutingInfoForSM_IND() MAP_Delimiter_REQ() MAP_Delimiter_IND() MAP MAP TCAP primitives TCAP primitives TCAP TCAP Underling protocols and network PISATEL

  17. MAP dialogue for SMS SMS-gwy HLR MAP User MAP User MAP_Open_CON() MAP_SendRoutingInfoForSM_CON() MAP_Open_RES() MAP_Close_IND() MAP_SendRoutingInfoForSM_RES(…) MAP_Close_REQ() MAP MAP TCAP primitives TCAP primitives TCAP TCAP Underling protocols and network PISATEL

  18. JAINIntegrated Network APIs for the Java platformThe objective of the JAIN initiative is to create an open value chain from 3rd-party service providers, facility-based service providers, telecom providers, and network equipment providers to telecom, consumer and computer equipment manufactures The JAIN initiative wants to integrate: wireline (PSTN), wireless (PLMN) and packet based (IP and ATM) networks by providing a new level of abstraction PISATEL

  19. Business Drivers and Industry GoalsThe JAIN initiative takes the telecommunications/Internet market from many proprietary closed systems to a single open environment able to host a large variety of services making next generation telecom application development faster, simpler and less expensive • Portability: Write Once Run Anywhere • Network Convergence: Any network !!! • Secure Network Access The JAIN initiative brings: PISATEL

  20. The JAIN initiative is divided in two areas of development • The Protocol API Specification specify interfaces to wireline, wireless and IP signaling prtocols • The Application API Specifications address the APIs required for service creation within a JAVA framework spanning across all protocols covered by the Protocol API Specification PISATEL

  21. JAIN Community Organization PISATEL

  22. JAIN application layer Coordination model Transaction model Call model JAIN protocol layer INAP/AIN H323/SIP MAP MGCP Wireline JAIN layeredapproach Service Layer Packet Gateway Wireless Network Layer PISATEL

  23. JAIN: JCC & JCT JAIN Call Control and JAIN Call Transaction are API for creating, monitoring, controlling, manipulating and tearing down communications sessions in a converged PSTN, PLMN and packed-switched environment. JCC allows to develop applications rapidly and efficiently that can execute on any platform Supported services: • First and Third-party originated and terminated calls • Voice virtual private networks (VPN) • Toll-free number translation • Voice-activated dialing • Click-to-dial • Meet-me conference PISATEL

  24. Idle The API provides four key objects: • Provider • Call • Address • Connection Provider Authorize Call Attempt Failed Address Collect Disconnected Call Unkown Address Analyze All valid states IN_SERVICE Connection Connection CallDelivery IDLE ACTIVE INVALID SHUTDOWN Address Alerting Address Model of a two-party call JCC Model of a Connection FSM OUT_OF_SERVICE JCC Provider FSM JCC Call FSM Suspended Connected JAIN: JCC & JCT PISATEL

  25. Service Creation S S S A A SIP MGCP JAIN Architecture … JAIN Parlay SLEE … S S S OAM JAIN Call Control Adapters PSTN VoIP MAP A A A A SS7 INAP GSM IS41 PISATEL

  26. JAIN: What has already published today ? PISATEL

  27. JAIN MAP API developers PISATEL

  28. Functionalities to be supported: • Short Message Service (SMS) • User to service data transfer (Unstructured Supplementary Service Data) • Subscriber Information (Any Time Interrogation) • Location Service and Emergency Location Information Delivery JAIN for MAPThe first version of the JAIN MAP API will include a subset of all capabilities of the MAP protocol PISATEL

  29. JAIN MAP API scoping space Scope for the first version of the JAIN MAP API Level of abstraction Protocol High level of abstraction ANSI 41 No hiding of primitives / parameters ETSI MAPl Short Message Sevice Subscriber information Location Service Capability User to Service data transfer PISATEL

  30. JAIN MAP API User Application JAIN MAP API implementation MAP Stack JAIN MAP API communication overview System where the JAIN MAP API is implemented Other system MAP User Application JAIN MAP layer primitives MAP layer primitives Request Message Response Message SS7 Network MAP Stack PISATEL

  31. GSM on the Net System JAIN MAP AUC HLR MAP MAP (over SS7) ISUP (over SS7) GSM PLMN GSM A H.225 H.225 Q.931 (over E1/T1) RNS MCP (G)MSC/VLR G.711 (over E1/T1) RTP (over UDP) GSM Abis GSM Abis (over E1/T1) GSM on the Net System Users STP VGW SS7GW NAC SN AGW RBS MS MS MS MS MS GSM on the Net: Traffic view ISUP PISATEL

  32. Our Goals • Contribute with JAIN MAP Editor team to complete theJAIN MAP API specifications • JAIN MAP model using UML • JAIN MAP demo • JAIN MAP on GSM on the Net Future Goals • Complete JAIN MAP capabilities • Extend JAIN architecture on GSM on the Net PISATEL

More Related