* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Comments - Home | School of Electrical Engineering and
Distributed firewall wikipedia , lookup
SIP extensions for the IP Multimedia Subsystem wikipedia , lookup
Computer network wikipedia , lookup
Deep packet inspection wikipedia , lookup
TV Everywhere wikipedia , lookup
Cracking of wireless networks wikipedia , lookup
Network tap wikipedia , lookup
Zero-configuration networking wikipedia , lookup
Architectures and Services for the UMTS IMT-2000 family member Wei Lin [email protected] Mingdi Zhao [email protected] CSI5171 Network Architectures, Services, Protocols and Standards Professor: Dr. Luigi Logrippo Dept. of Computer Science 3/21/2002 1 Contents Overview Architectures for UMTS system Services of UMTS system References 3/21/2002 2 History of Mobile Communications First Generation: is Analog Cellular. the most prominent systems: Advanced Mobile Phone System (AMPS). Nordic Mobile Telephone (NMT), and Total Access Communication System (TACS). Second Generation: is Multiple Digital Systems. which includes Global System for Mobile Communications (GSM), Digital AMPS (D-AMPS), Personal Communication Services(PCS), and Japanese standard Personal Digital Communication (PDC). Third generation: extend the services provided by current second generation systems to offer high data rates services. such as multimedia telephone, video conference,video games, and provide universal coverage and enable terminals to be able to move seamlessly between all networks in anywhere of the world. 3/21/2002 3 IMT-2000 IMT-2000: a global standard for third generation systems, is defined by the International Telecommunication Union(ITU) The main objectives for IMT-2000 are: high data rates: 144 Kbps/384 Kbps for high mobility users with full coverage; 2 Mbps for low mobility users with limited coverage. capability for multimedia application and all mobile applications. high spectrum efficiency compared to existing systems high flexibility to introduce new services high degree of commonality of design worldwide use of a small pocket terminal with seamless global roaming. 3/21/2002 4 UMTS system UMTS: The most important IMT–2000 proposal is a 3G GSM successor standard; is being developed by 3GPP, a joint venture of several SDOs: ETSI (Europe), ARIB/TTC (Japan), ANSI T-1 (USA), TTA (South Korea), and CWTS (China); incorporates enhanced GSM Phase 2+ CNs with GPRS and CAMEL. In UMTS, a new radio access network UMTS terrestrial radio access network (UTRAN) is introduced, which will support PS data and CS data. Handover between UMTS and GSM is supported, and handover between UMTS and other 3G systems will be supported to achieve true worldwide access. 3/21/2002 5 UMTS Architectures Home Network Domain [Zu] Cu Uu Iu [Yu] Serving Network Domain USIM Domain Mobile Equipment Domain User Equipment Domain Access Network Domain Transit Network Domain Core Network Domain Infrastructure Domain the basic domains in UMTS (copy from CWTS.org) 3/21/2002 6 UMTS Architectures (cont.) Domain split: User Equipment Domain: user equipment is a device allowing a user access to UMTS network services; it has a radio interface to the infrastructure. Infrastructure Domain: the infrastructure consists of the physical nodes which perform the various functions required to terminate the radio interface and to support the telecommunication services requirements of the users. 3/21/2002 7 User Equipment Domain The user equipment is further sub-divided into: Mobile Equipment Domain (ME) Mobile Termination(MT) performs the radio transmission & related functions Terminal Equipment(TE) contains the end-to-end application User Services Identity Module Domain (USIM) contains data and procedures which unambiguously and securely identify itself. MT USIM TE ME UE (copy from CWTS.org) 3/21/2002 8 Infrastructure Domain The Infrastructure domain is further split into: Access Network Domain is the system of base station equipments (transceivers, controllers, etc...) which manage the resources of the AN and provides the user with a mechanism to access the CN domain. Core Network Domain consists of the physical entities which provide support for the network features & telecommunication services. the support provided includes functionality such as the management of user location information, control of network features and services, the transfer (switching and transmission) mechanisms for signalling and for user generated information. the core network domain may result from evolutions of existing network infrastructures, e.g., a GSM infrastructure, a N-ISDN infrastructure, a B-ISDN infrastructure or a PDN infrastructure. 3/21/2002 9 Access Network Two different types of access network are used: Base Station System (BSS) for GSM: is viewed by the MSC through a single A-interface as being the entity responsible for communicating with Mobile Stations in a certain area. Similarly, in PLMNs supporting GPRS, the BSS is viewed by the SGSN through a single Gb interface. It offers a TDMA based technology to access the Mobile Station. Radio Network System (RNS) for UMTS: is viewed by the MSC through a single Iu-interface as being the entity responsible for communicating with Mobile Stations in a certain area. Similarly, in PLMNs supporting GPRS, the RNS is viewed by the SGSN through a single Iu-PS interface. It offers a W-CDMA based technology to access the Mobile Station. 3/21/2002 10 Core Network Domain (1) The core network domain is sub-divided into: Serving Network Domain: represents the core network functions that are local to the user’s access point and thus their location changes when the user moves. The serving network domain is responsible for routing calls and transport user data/information from source to destination. It has the ability to interact with the home domain to cater for user specific data/services and with the transit domain for non user specific data/services purposes Home Network Domain: represents the core network functions that are conducted at a permanent location regardless of the location of the user’s access point. The USIM is related by subscription to the home network domain. The home network domain therefore contains at least permanently user specific data and is responsible for management of subscription information. It may also handle home specific services, potentially not offered by the serving network domain. Transit Network Domain: located on the communication path between the serving network domain and the remote party. 3/21/2002 11 Core Network Domain (2.1) In another logical point of view, the CN encompasses: Circuit Switched (CS) service domain, earlier named PSTN/ISDN domain, refers to the set of all the CN entities offering "CS type of connection" for user traffic as well as all the entities supporting the related signalling. A "CS type of connection" is a connection for which dedicated network resources are allocated at the connection establishment and released at the connection release. The entities specific to the CS domain are: MSC, GMSC. Packet Switched (PS) service domain, earlier named IP domain, refers to the set of all the CN entities offering "PS type of connection" for user traffic as well as all the entities supporting the related signalling. A "PS type of connection" transports the user information using autonomous concatenation of bits called packets: each packet can be routed independently from the previous one. The entities specific to the PS domain are the GPRS specific entities, i.e. SGSN and GGSN. 3/21/2002 12 Core Network Domain (2.2) Common subscription data base HLR PS location CS location Two CN service domains CS service domain 3G SGSN 3G MSC/VLR PS service domain PS state CS state CN Two Iu signalling connections (“two RANAP instances”) UTRAN with distribution functionality UTRAN AN One RRC connection CS state PS state UE the separate CN architecture case (copy from CWTS.org) 3/21/2002 13 Core Network Domain (2.3) Common subscription data base HLR PS location CS location Two CN service domains CS service domain UMSC PS service domain PS state CS state Two Iu signalling connections “two RANAP instances” UTRAN UTRAN with distribution functionality One RRC connection CS state PS state UE the integrated CN architecture case (copy from CWTS.org) 3/21/2002 14 Core Network Domain (2.4) UE, that is supporting both CS services and PS services, The two peers of the service state machine are working independently to each other (synchronization). A single RRC connection (between UTRAN and UE) shall carry all user plane and signalling flows to/from a UE. The aim of UTRAN is to offer one unified set of radio bearers which may be used for burst packet traffic and for traditional telephony traffic. For the mobility functionality, four different area concepts are used. Location Areas and Routing Areas are used in the Core Network. UTRAN Registration Areas and Cell Areas are used in UTRAN. Location Areas are related to CS services. Routing Areas are related to PS services. 3/21/2002 15 Core Network Domain (2.5) In the separate CN architecture case, the CN consists of both a CS service domain with evolved MSC/VLR, 3G_MSC/VLR, as the main serving node and an PS service domain with evolved SGSN/GGSN, 3G_SGSN and 3G GGSN, as the main serving nodes. In the integrated CN architecture case, the CN consists of both a CS service domain and an PS service domain with an UMSC as the main serving node. The use of separated PS and CS mobility mechanisms within the UE and within the CN may lead to non-optimal usage of the radio resource 3/21/2002 16 PLMN The public land mobile network (PLMN) described in UMTS Rel. ’99 incorporates three major categories of network elements: GSM Phase 1/2 core network elements: mobile services switching center (MSC), visitor location register (VLR), home location register (HLR), authentication center (AC), and equipment identity register (EIR) GSM Phase 2+ enhancements: GPRS (serving GPRS support node [SGSN] and gateway GPRS support node [GGSN]) and CAMEL (CAMEL service environment [CSE]) UMTS specific modifications and enhancements, particularly UTRAN may be regarded as an extension of a network (e.g. ISDN) 3/21/2002 17 Basic configuration of a PLMN (1) PSTN/ISDN Gp PDN Gi GMSC GGSN AuC C PSTN HLR PSTN F G VLR B Gf Gs B MSC Gn Gr EIR D VLR Gc H SGSN MSC E CN A Gb IuPS IuCS RNS BSS Iur BSC RNC Abis BTS RNC Iubis BTS Node B Node B cell Um Uu ME bold lines show interfaces supporting user traffic; dashed lines show interfaces supporting signalling. SIM-ME i/f SIM or Cu USIM MS 3/21/2002 (copy from CWTS.org) 18 Basic configuration of a PLMN (2) The figure presents the basic configuration of a Public Land Mobile Network (PLMN) supporting GPRS and the interconnection to the PSTN/ISDN and PDN. The figure shows direct interconnections between the entities. The actual links may be provided by an underlying network (e.g. SS7 or IP): this needs further studies. The most important evolutionary step of GSM toward UMTS is GPRS. GPRS introduces PS into the GSM CN and allows direct access to packet data networks (PDNs). GPRS prepares and optimizes the CN for high–data rate PS transmission, as does UMTS with UTRAN over the RAN. Two functional units extend the GSM NSS architecture for GPRS PS services: the GGSN and the SGSN. The GGSN has functions comparable to a gateway MSC (GMSC). The SGSN resides at the same hierarchical level as a visitedMSC /VLR and therefore performs comparable functions such as routing and mobility management. The MSC provides functions such as switching, signaling, paging, and inter– MSC handover. 3/21/2002 19 Basic configuration of a PLMN (3) Existing network elements, such as MSC, and HLR, can be extended to adopt the UMTS requirements. But RNC, Node B, and the handsets must be completely new designs: RNC will become the replacement for BSC, and Node B fulfills nearly the same functionality as BTS. GSM and GPRS networks will be extended, and new services will be integrated into an overall network. UMTS defines four new interfaces: 3/21/2002 Uu: UE to Node B, the UMTS W–CDMA air interface Iu: RNC to GSM Phase 2+ CN interface (MSC/VLR or SGSN) Iu-CS for circuit-switched data Iu-PS for packet-switched data Iub: RNC to Node B interface Iur: RNC to RNC interface, not comparable to any interface in GSM The Iu, Iub, and Iur interfaces are based on ATM transmission principles. 20 Basic configuration of a PLMN (4) (copy from iec.org) 3/21/2002 21 Basic Configuration with GLR (1) The Gateway Location Register (GLR) handles location management of roaming subscriber in visited network without involving HLR. The benefit of the GLR is the reduction in signalling traffic between networks. This entity can be only located in a visited PLMN. SGSN GLk GLc GLe IM-GSN GLj VLRb/MS C GLh GLb GLR GLd PLMN Network B IM-MSC GLg GLa GLi GLf GGSN HLRa SMS-GMSC GMLC PLMN Network A Signalling interface User traffic interface. User traffic includes Short Message. 3/21/2002 (copy from CWTS.org) 22 Basic Configuration with GLR (2) In above figure, the GLR interacts with HLRa and VLRb for roamers on Network B. The GLR is part of the roaming subscriber's Home Environment. When a subscriber to HLRa is roaming on Network B the GLR plays the role of an HLR towards VLRb and the role of a VLR towards HLRa. The GLR handles any location change between different VLR service areas in the visited network without involving HLRa. The sequence of events when the subscriber roams to network B is: VLRb sends the registration message to HLRa via the GLR, (i.e. HLRa stores the GLR's SCCP address and the GLR stores VLRb's SCCP address); HLRa returns the subscriber profile data; the subscriber profile is stored in the GLR and VLRb. As the roaming subscriber moves between VLRs in network B, then the GLR is updated, but no message is sent to HLRa, therefore the number of messages between Network A and Network B is reduced. 3/21/2002 23 Service Aspects of IMT2000 Services structure in PLMNs Services principles for PLMNs Categories of services Supplementary services (11) Line identification Advice of Charging Other services 3/21/2002 24 The Service Structure in PLMNs 3/21/2002 (copy from CWTS.org) 25 Service principles for PLMNs to provide a single integrated system in which the user can access services in an easy to use and uniform way in all environments. to provide a wide range of telecommunications services. to provide support of roaming users by enabling users to access services provided by their home environment in the same way even when roaming. to provide audio, data, video and particularly multimedia services; 3/21/2002 26 Categories of telecommunication services BEARER SERVICE TELESERVICE Basic Bearer Service Basic Teleservice Basic Bearer service Basic Teleservice + +supplementary services supplementary service 3/21/2002 27 Supplementary services Supported by PLMNs (1) Line identification Supplementary Services 3/21/2002 CLIP --- Calling line identification presentation. CLIR --- Calling line identification restriction. COLP --- Connected line identification presentation. COLR --- Connected line identification restriction. 28 CLIP Process (1) Idle Initial handling of CLIP Yes CLIP Provisioned no set provision Indication =not provisioned set provision Indication=provisioned Called subscriber in HPLMN country no yes Override category no yes set override Category=yes set override Category=No Continue call handling CLIP—Calling line Identification Presentation idle Determination of calling line identification presentation subscription(VLR) 3/21/2002 (copy from CWTS.org) 29 CLIP Process (2) no CLIP provisioned yes no CLI available Idle yes Initiate handling Of CLIP yes CLI received from VLR Use CLI received from VLR no use CLI received from signaling PI = presentation restricted? Yes no Cause of no CLI override category yes Additional CLI available No no no Additional CLI available yes yes PI = presentation restricted by network? Yes override category CLI in case of override category No CLI Yes set PI = Presentation restricted Additional CLI Pass Additional CLI pass CLI Set PI = number not available pass CLI pass Additional CLI set PI = number not available Continue Call handling idle CLIP: Calling Line Identification Presentation. CLI: Calling Line Identity. PI: Presentation Indicator. Determination of the information for offering to the called party (destination MSC) 3/21/2002 (copy from CWTS.org) 30 CLIR Process (1) idle Initiate handling Of CLIR no CLIR provisioned yes set provision indication = not provisioned set provision Indication=provisioned subscription option = permanent yes no temporary mode default =present restricted no yes mode indication = temporary (pres. restricted) mode indication = temporary (pres. allowed) set mode indication = permanent continue Call handling CLIR: Calling Line Identification Restriction idle Determination of calling line identification restriction subscription (VLR) 3/21/2002 (copy from CWTS.org) 31 CLIR Process (2) idle Initiate handling Of CLIR no yes CLIR provisioned yes restrict CLI note2 no permanent no yes yes temporary mode default = pres. restricted present CLI note1 no Clear call no yes Error notification no present CLI note 1 yes no restrict CLI note 2 yes Set PI= Presentation allowed set PI = presentation restricted Continue call handling idle Set PI= Presentation allowed Set PI= Presentation restricted note 1: present CLI is input received from the MS note 2: restrict CLI is input received from the MS CLIR: Calling Line Identification Restriction CLI: Calling Line Identity PI: Presentation Indicator Determination of the presentation indicator (originating MSC) 3/21/2002 (copy from CWTS.org) 32 COLP Process idle Initiate handling Of COLP COLP provisioned no yes COL available no yes yes Override category Presentation restricted yes no additional COL available no Additional COL available no yes no yes COL in case of override category Additional COL Pass additional COL COL pass COL Continue COL handling Pass additional COL set PI = Number not available COLP: Connected Line Identification Presentation. COL: Connected Line Identity. PI: Presentation Indicator. idle Determination of the information for offering to the connected party (originating MSC) 3/21/2002 (copy from CWTS.org) 33 COLR Process idle initiate handling of COLR COLR provisioned no yes set PI = presentation restricted continue call handling set PI = presentation allowed COLR: Connected Line Identification Restriction. PI: Presentation Indicator. idle Determination of the presentation indicator 3/21/2002 (copy from CWTS.org) 34 Supplementary services Supported by PLMNs (2) Call Forwarding (CF) supplementary services 3/21/2002 (copy from CWTS.org) 35 Supplementary services Supported by PLMNs (3-10) 3. Follow Me service 4. Call Waiting (CW) and Call Holding (HOLD) Supplementary 5. 6. 7. 8. 9. 10. Services MultiParty (MPTY) Supplementary Services Closed User Group (CUG) Supplementary Services User-to-User Signalling (UUS) Call Barring (CB) Supplementary Services Explicit Call Transfer (ECT)--Supplementary Service Unstructured Supplementary Service Data (USSD) 3/21/2002 36 Supplementary services Supported by PLMNs (11) Advice of Charge (AoC) Supplementary Services (information) call in progress or Call set up in progress request generation of CAI Request of generation of CAI applies to AoC initiation or charge modification. generate CAI send CAI continue call Or call set up CAI: Charge Advice Information SDL diagram of advice of charge (information) in the MSC 3/21/2002 (copy from CWTS.org) 37 Supplementary services Supported by PLMNs (11) Advice of Charge (AoC) Supplementary Services (information) call set up In progress charging information AoC active call ends Start charge calculations AoC acknowledge AoC active charging information AoC acknowledge Stop charge calculations Amend charging calculation clear call Point at which charging calculations are amended can occur before or after sending the AoC acknowledge. AoC active SDL diagram of advice of charge (information) in the Mobile Equipment 3/21/2002 (copy from CWTS.org) 38 Supplementary services Supported by PLMNs (11) Advice of Charge (AoC) Supplementary Services (charging) call in progress or Call set up in progress request generation of CAI generate CAI send CAI wait for AoC acknowledge Request of generation of CAI applies to AoC initiation or charge modification. AoC acknowledge Timer T(AoC) expired stop timer T(Aoc) Clear call call in progress idle Call cleared stop timer T(AoC) start timer T(AoC) CAI: Charge Advice Information wait for AoC acknowledge SDL diagram of advice of charge (charging) in the Mobile Equipment 3/21/2002 (copy from CWTS.org) 39 Supplementary services Supported by PLMNs (11) Advice of Charge (AoC) Supplementary Services (chageing) •This service provides the means by which the MS may indicate the charge that will be made for the use of telecommunication services. It is intended for applications where the user is generally not the subscriber but is known to the subscriber, and where the user pays the subscriber, rather than the Service Provider. •When required to indicate the total accumulated charge, the MS shall be able to display, and the SIM/USIM shall store in the ACM, the running cumulative unit charge. This value must be stored securely, and all reasonable steps shall be taken to ensure that the written value cannot be interrupted, reset or corrupted (except resetting under control of the unblocking key). 3/21/2002 40 Other services supported by PLMNs(1) International Mobile Station Equipment Identity (IMEI) Personalization of Mobile Equipment (ME) Man-Machine Interface (MMI) of the User Equipment (UE) High Speed Circuit Switched Data (HSCSD) USIM/SIM Application Toolkit (USAT/SAT) Operator Determined Barring (ODB) Network Identity and Time zone (NITZ) Support of Localised Service Area (SoLSA) Mobile Station Application Execution Environment (MExE) 3/21/2002 41 Other services supported by PLMNs(2) General Packet Radio Service (GPRS) Support of Mobile Number Portability (MNP) enhanced Multi-Level Precedence and Pre-emption service (eMLPP) Location Services (LCS) Call Deflection (CD) Customised Applications for Mobile network Enhanced Logic(CAMEL) Completion of Calls to Busy Subscriber (CCBS) Multiple Subscriber Profile (MSP) Multimedia Messaging Service (MMS) 3/21/2002 42 References http://www.cwts.org/cwts/itu.htm http://www.iec.org/online/tutorials/umts/index.html 3/21/2002 43