Split (1)

train · 194k rows

hash stringlengths 32 32	doc_id stringlengths 7 13	section stringlengths 3 121	content stringlengths 0 3.82M
cacf9eed93e6daf37d9a13b7cf85a487	132 102	12 TMN planning and design considerations	.............................................................................................32
cacf9eed93e6daf37d9a13b7cf85a487	132 102	12.1 Function attributes	........................................................................................................................................... 32
cacf9eed93e6daf37d9a13b7cf85a487	132 102	12.2 Functional characteristics	................................................................................................................................ 33
cacf9eed93e6daf37d9a13b7cf85a487	132 102	12.3 Critical attributes	............................................................................................................................................. 33
cacf9eed93e6daf37d9a13b7cf85a487	132 102	12.4 Protocol selection	............................................................................................................................................. 33
cacf9eed93e6daf37d9a13b7cf85a487	132 102	12.5 Communications considerations	...................................................................................................................... 34 ETSI ETSI TS 132 102 V3.2.0 (2000-07) 4 3G TS 32.102 version 3.2.0 Release 1999 13 Mediation/Integration ............................................................................................................................35 Annex A (informative): Technology considerations ...........................................................................37 A.1 TMN physical blocks.............................................................................................................................37 A.1.1 Operations System (OS) .................................................................................................................................. 37 A.1.2 Transformation ................................................................................................................................................ 37 A.1.2.1 Adaptation device....................................................................................................................................... 37 A.1.2.2 Mediation Device (MD)............................................................................................................................. 37 A.1.3 Network Element (NE).................................................................................................................................... 38 A.1.4 Workstation (WS)............................................................................................................................................ 38 A.1.5 Data Communication Network (DCN) ............................................................................................................ 38 A.1.6 TMN logical layered architecture within the TMN physical architecture ....................................................... 39 A.1.7 Interoperable interface concept........................................................................................................................ 39 A.2 TMN standard interfaces .......................................................................................................................40 A.2.1 Q interface ....................................................................................................................................................... 40 A.2.2 F interface........................................................................................................................................................ 41 A.2.3 X interface ....................................................................................................................................................... 41 A.2.4 Relationship of TMN interfaces to TMN physical blocks............................................................................... 41 Annex B (informative): Change history...............................................................................................42 ETSI ETSI TS 132 102 V3.2.0 (2000-07) 5 3G TS 32.102 version 3.2.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 6 3G TS 32.102 version 3.2.0 Release 1999 1 Scope The present document identifies identify and standardises the most important and strategic contexts in the physical architecture for the management of UMTS. It serves as a framework to help define a telecom management physical architecture for a planned UMTS and to adopt standards and provide products that are easy to integrate. The present document is applicable to all further Technical Specifications regarding the Telecom Management of UMTS. 2 References The following documents contain provisions, which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. 2.1 Normative references [1] ITU-T Recommendation M.3010 (2000): "Principles for a telecommunications management network". [2] 3G TS 32.101: "3G Telecom Management principles and high level requirements". [3] ITU-T Recommendation X.721: "Information technology - Open Systems Interconnection - Structure of management information: Definition of management information". [4] ITU-T Recommendation X.200 (1994): "Information technology – Open Systems Interconnection – Basic reference model: The basic model". [5] ITU-T Recommendation X.733: "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function". [6] ITU-T Recommendation X.736: “Information technology – Open Systems Interconnection – Security Alarm Reporting Function”. [7] ITU-T Recommendation M.3100-1995: “Generic network information model”. [8] GSM 12.11: Digital cellular telecommunications system (Phase 2); Fault management of the Base Station System (BSS). 2.2 Informative references [20] TMF GB910. Smart TMN Telecom Operations Map (Release 1.1). [21] TMF GB909. Smart TMN Technology Integration Map (Issue 1.1). [22] ITU-T Recommendation M.3013 (2000): “Considerations for a telecommunications management network”. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 7 3G TS 32.102 version 3.2.0 Release 1999 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the following definitions apply: Architecture: The organisational structure of a system or component, their relationships, and the principles and guidelines governing their design and evolution over time. Closed interfaces: Privately controlled system/subsystem boundary descriptions that are not disclosed to the public or are unique to a single supplier. De facto standard: A standard that is widely accepted and used but that lacks formal approval by a recognised standards organisation. Interface standard: A standard that specifies the physical or functional interface characteristics of systems, subsystems, equipment, assemblies, components, items or parts to permit interchangeability, interconnection, interoperability, compatibility, or communications. Interoperability: The ability of two or more systems or components to exchange data and use information. Intra-operability: The ability to interchange and use information, functions and services among components within a system. IRPAgent: The IRPAgent encapsulates a well-defined subset of network (element) functions. It interacts with IRPManagers using an IRP. From the IRPManager’s perspective, the IRPAgent behaviour is only visible via the IRP. IRPManager: The IRPManager models a user of the IRPAgent and it interacts directly with the IRPAgent using the IRP. Since the IRPManager represents an IRPAgent user, they help delimit the IRPAgent and give a clear picture of what the IRPAgent is supposed to do. From the IRPAgent perspective, the IRPManager behaviour is only visible via the IRP. IRP Information Model: An IRP Information Model consists of an IRP Information Service and a Network Resource Model (see below for definitions of IRP Information Service and Network Resource Model). IRP Information Service: An IRP Information Service describes the information flow and support objects for a certain functional area, e.g. the alarm information service in the fault management area. As an example of support objects, for the Alarm IRP there is the "alarm information" and "alarm list". IRP Solution Set: An IRP Solution Set is a mapping of the IRP Information Service to one of several technologies (CORBA/IDL, SNMP/SMI, CMIP/GDMO etc.). An IRP Information Service can be mapped to several different IRP Solution Sets. Different technology selections may be done for different IRPs. Management Infrastructure: The collection of systems (computers and telecommunications) a UMTS Organisation has in order to manage UMTS. Market Acceptance: Market acceptance means that an item has been accepted in the market as evidenced by annual sales, length of time available for sale, and after-sale support capability. Modular: Pertaining to the design concept in which interchangeable units are employed to create a functional end product. Module: An interchangeable item that contains components. In computer programming, a program unit that is discrete and identifiable with respect to compiling, combining with other modules, and loading is called a module. Network Resource Model (NRM): A protocol independent model describing managed objects representing network resources, e.g. an RNC or NodeB. Open Specifications: Public specifications that are maintained by an open, public consensus process to accommodate new technologies over time and that are consistent with international standards. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 8 3G TS 32.102 version 3.2.0 Release 1999 Open Standards: Widely accepted and supported standards set by recognised standards organisation or the commercial market place. These standards support interoperability, portability, and scalability and are equally available to the general public at no cost or with a moderate license fee. Open Systems Architecture (OSA): An architecture produced by an open systems approach and employing open systems specifications and standards to an appropriate level. Open Systems Strategy: An open systems strategy focuses on fielding superior telecom capability more quickly and more affordably by using multiple suppliers and commercially supported practices, products, specifications, and standards, which are selected based on performance, cost, industry acceptance, long term availability and supportability, and upgrade potential. Physical Architecture: A minimal set of rules governing the arrangement, interaction, and interdependence of the parts or elements whose purpose is to ensure that a conformant system satisfies a specified set of requirements. The physical architecture identifies the services, interfaces, standards, and their relationships. It provides the technical guidelines for implementation of systems upon which engineering specifications are based and common building blocks are built. Plug&play: Term for easy integration of HW/SW. Portability: The ease with which a system, component, data, or user can be transferred from one hardware or software environment to another. Proprietary Specifications: Specifications, which are exclusively owned by a private individual or corporation under a trademark or patent, the use of which would require a license. Reference Model: A generally accepted abstract representation that allows users to focus on establishing definitions, building common understandings and identifying issues for resolution. For TMN Systems acquisitions, a reference model is necessary to establish a context for understanding how the disparate technologies and standards required to implement TMN relate to each other. A reference model provides a mechanism for identifying the key issues associated with applications portability, modularity, scalability and interoperability. Most importantly, Reference Models will aid in the evaluation and analysis of domain-specific architectures. Scalability: The capability to adapt hardware or software to accommodate changing workloads. Specification: A document that prescribes, in a complete, precise, verifiable manner, the requirements, design, behaviour, or characteristics of a system or system component. Standard: A document that establishes uniform engineering and technical requirements for processes, procedures, practices, and methods. Standards may also establish requirements for selection, application, and design criteria of material. Standards Based Architecture: An architecture based on an acceptable set of open standards governing the arrangement, interaction, and interdependence of the parts or elements that together may be used to form a TMN System, and whose purpose is to insure that a conformant system satisfies a specified set of requirements. System : Any organised assembly of resources and procedures united and regulated by interaction or interdependence to accomplish a set of specific functions. System Architecture: A description, including graphics, of systems and interconnections providing for or supporting management functions. The SA defines the physical connection, location, and identification of the key nodes, circuits, networks, platforms, etc., and specifies system and component performance parameters. It is constructed to satisfy Operational Architecture requirements per standards defined in the Physical Architecture. The SA shows how multiple systems within a subject area link and inter-operate, and may describe the internal construction or operations of particular systems within the architecture. UMTS Organisation: A legal entity that is involved in the provisioning of UMTS. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: 3G 3rd Generation ATM Asynchronous Transfer Mode BG Border Gateway ETSI ETSI TS 132 102 V3.2.0 (2000-07) 9 3G TS 32.102 version 3.2.0 Release 1999 BSC Base Station Controller BSS Base Station Subsystem BTS Base Transceiver Station CIM Common Information Model Specification (from DMTF) CMIP Common Management Information Protocol CMIS Common Management Information Service CMISE Common Management Information Service Element CORBA Common Object Request Broker Architecture DCN Data Communication Network DECT Digital Enhanced Cordless Telecommunications DSS1 Digital Subscriber System 1 FM Fault Management FTAM File Transfer, Access and Management F/W Firewall GDMO Guidelines for the Definition of Managed Objects GGSN Gateway GPRS Support Node GPRS General Packet Radio Service HLR Home Location Register HTTP HyperText Transfer Protocol IDL Interface Definition Language IIOP Internet Inter-ORB Protocol INAP Intelligent Network Application Part IP Internet Protocol IRP Integration Reference Point ISDN Integrated Services Digital Network IWU Inter Working Unit MD Mediation Device MIB Management Information Base MMI Man-Machine Interface MML Man-Machine Language MSC Mobile service Switching Centre NE Network Element NR Network Resource NRM Network Resource Model NSS Network Switching Subsystem NW Network OMG Object Management Group OS Operations System OSF Operations System Functions PDH Plesiochronous Digital Hierarchy PSA Product Specific Applications PSTN Public Switched Telephone Network QA Q-Adapter QoS Quality of Service RNC Radio Network Controller RSVP Resource ReserVation Protocol SDH Synchronous Digital Hierarchy SGSN Serving GPRS Support Node SLA Service Level Agreement SMI Structure of Management Information SNMP Simple Network Management Protocol SS7 Signalling System No. 7 TM Telecom Management TMN Telecommunications Management Network as defined in ITU-T Recommendation M.3010 [1]. UML Unified Modelling Language UMTS Universal Mobile Telecommunications System UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network VHE Virtual Home Environment VLR Visitor Location Register WBEM Web Based Enterprise Management WS Workstation ETSI ETSI TS 132 102 V3.2.0 (2000-07) 10 3G TS 32.102 version 3.2.0 Release 1999 4 General 4.1 UMTS 4.1.1 UMTS Reference Model A Universal Mobile Telecommunications System is made of the following components: - one or more Access Networks, using different types of access techniques (GSM, UTRA, DECT, PSTN, ISDN,...) of which at least one is UTRA; - one or more Core Networks; - one or more Intelligent Node Networks, service logic and mobility management, (IN, GSM...); - one or more transmission networks (PDH, SDH etc) in various topologies (point-to-point, ring, point-to- multipoint etc) and physical means (radio, fibre, copper etc). The UMTS components have signalling mechanisms among them (DSS1, INAP, MAP, SS7, RSVP etc.). From the service perspective, the UMTS is defined to offer: - service support transparent to the location, access technique and core network, within the bearer capabilities available in one particular case; - user to terminal and user to network interface (MMI) irrespective of the entities supporting the services required (VHE); - multimedia capabilities. 4.1.2 UMTS Provisioning Entities Two major entities, which cover the set of UMTS functionalities involved in the provision of the UMTS services to the user, are identified as follows: Home Environment. This entity holds the functionalities that enable a user to obtain UMTS services in a consistent manner regardless of the user's location or the terminal used. Serving Network. This entity provides the user with access to the services of the Home Environment. 4.1.3 UMTS Management Infrastructure Every UMTS Organisation has it's own Management Infrastructure. Each Management Infrastructure will contain different functionality depending on the role-played and the equipment used by that UMTS Entity. However, the core management architecture of the UMTS Organisation is very similar. Every UMTS Organisation: - provides services to it's customers; - needs an infrastructure to fulfil them (advertise, ordering, creation, provisioning,...); - assures them (Operation, Quality of Service, Trouble Reporting and Fixing,...); - bills them (Rating, Discounting,...). Not every UMTS Organisation will implement the complete Management Architecture and related Processes. Some processes may be missing dependent on the role a particular UMTS Organisation is embodying. Processes not implemented by a particular UMTS Organisation are accessed via interconnections to other UMTS organisations, which have implemented these processes (called X-interfaces in the TMN architecture). The Management architecture itself does not distinguish between external and internal interfaces. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 11 3G TS 32.102 version 3.2.0 Release 1999 4.2 TMN TMN (Telecommunications Management Network), as defined in [1], provides: - an architecture, made of OS (Operations Systems) and NEs (Network Elements), and the interfaces between them (Q, within one Operator Domain and X, between different Operators); - the methodology to define those interfaces; - other architectural tools such as LLA (Logical Layered Architecture) that help to further refine and define the Management Architecture of a given management area; - a number of generic and/or common management functions to be specialised/applied to various and specific TMN interfaces. The UMTS Management Architecture is largely based on TMN, and will reuse those functions, methods and interfaces already defined (or being defined) that are suitable to the management needs of UMTS. However, the UMTS Management needs to explore the incorporation of other concepts (other management paradigms widely accepted and deployed) since: - UMTS incorporates other technologies to which TMN is not applied fully; - UMTS faces new challenges that TMN does not address today. It shall be noted, that these concerns are applicable to other telecommunication areas as well as to UMTS, it is expected that the eventual evolution of TMN will cover this ground. Indeed, most of the above concepts are already being taken into account by TMN evolution (protocols and methodologies). 5 General view of UMTS Management Physical architectures Telecom Management Architectures can vary greatly in scope and detail. The architecture for a large service provider, with a lot of existing legacy systems and applications, upon which many services are based, will be of high complexity. In contrast, the architectural needs of a start-up mobile operator providing its services to a small group of value added Service Providers will be much less and will probably focus on more short-term needs. A mobile network operator has to manage many different types of networks as radio networks, exchanges, transmission networks, area networks, intelligent nodes and substantial amounts of computer hardware/software. This wide variety of network equipment shall be obtained from a variety of equipment vendors. The nature of a mobile radio network will be heterogeneous and will present a number of operational difficulties for the service provider on enabling effective and efficient network management. The standardisation work for the management of UMTS has adopted the top-down approach and will from business needs identify functional and informational architectures. The physical architecture will have to meet these requirements and as there are many ways to build a UMTS it will vary greatly from one TMN solution to another. There will be many physical implementations, as different entities will take different roles in a UMTS. It is obvious that it will not be meaningful or even possible to fully standardise a common telecom management physical architecture for UMTS. This document will identify and standardise the most important and strategic contexts and serve as a framework to help define a physical architecture for a planned UMTS. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 12 3G TS 32.102 version 3.2.0 Release 1999 6 Basic objectives for a UMTS Physical Architecture The management of UMTS will put a lot of new requirements to the management systems compared to the second generation of Mobile telephony. Some of the challenging requirements affecting the physical architecture are: - To be capable of managing equipment supplied by different vendors. - To enable TM automation in a more cost efficient way - TM optimised for maximum efficiency and effectiveness. - To provide UMTS configuration capabilities that are flexible enough to allow rapid deployment of services. - To report events and reactions in a common way in order to allow remote control. - To allow interoperability between Network Operators/Service Providers for the exchange of management/charging information. - To be scaleable and applicable to both larger and small deployments. - Accessibility to information. - To profit from advances and standards in IT and datacom industry. The second generation of mobile networks can - from management point of view - be characterised as the era of net-element vendor-dependent NE managers. The different OSs had very low interoperability with other systems and functional blocks could rarely be re-used. The Mobile Telecom Management Networks were far away from the TMN vision where one vendor’s OS should be able to manage other vendor’s net elements. For UMTS Management it is clearly stated the necessity of cost-effective solutions and better time to market focus. Interoperability, scalability and re-use are keywords for the new generation of management systems. Many of the new requirements on the management of UMTS can only be solved by defining and establish a suitable physical architecture. Thou it is not possible to standardise the one single UMTS TM physical architecture, it is evidently so that the success of a telecom management network of a UMTS will heavily depend on critical physical architectural issues. This document will identify those architectural critical issues. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 13 3G TS 32.102 version 3.2.0 Release 1999 7 TM Architectural aspects 7.1 Architectural relationship The basic aspects of a TM architecture, which can be, considered when planning and designing a TM network are: - The functional architecture. - The information architecture. - The physical architecture. The management requirements - from the business needs - will be the base for the functional architecture, which will describe the functions that have to be achieved. The information architecture defines what information that has to be provided so the functions defined in the functional architecture can be achieved. The physical architecture has to meet both the functional architecture and the information architectures. Other constraints from realty will also have impact to the physical architecture as cost, performance, legacy systems and all preferences any operator will have on a big capital investment as a TM network. Business needs Functional Architecture Information Architecture Physical Architecture Cost Performance Legacy Preferences Figure 1: Architectural relationship 7.2 Architectural constraints Large software systems, such as a network management system, are a capital investment that operators cannot afford to scrap every time its requirements change. Network operators are seeking cost-effective solutions to their short-term needs. All these reality-related issues are vital constraints that shall be addressed in the definition of the architecture. The standardisation of UMTS will bring new and different services that will add new demands on network management. Every UMTS organisation will include different functionality depending on the role-played and the equipment used by that UMTS entity. Regulation may force some of the roles that shall be taken. The need to link systems across corporate boundaries will be a consequence of this. The rapid evolution of new services and technologies will also put requirements on the UMTS physical management architecture to accommodate market and technology trends. To future-proof investments and continuously be able to take advantage of new technologies are important constraints to the physical architecture. A UMTS TMN shall also adopt an architecture that will achieve scalability and extensibility of systems and networks so the TMN can grow as the services expand over time. To start with a small TMN and easily be able to expand the TMN after new requirements will be important issues for most UMTS operators. The telecom management network will be just one part of the overall business of a company. System management, general security issues and development strategies can be the target for company policies. System architectures and technology choices, as well as the availability of off-the-shelf commercial systems and software components that fulfil ETSI ETSI TS 132 102 V3.2.0 (2000-07) 14 3G TS 32.102 version 3.2.0 Release 1999 the requirements established in this specification, may be critical to an operator’s implementation of the specified UMTS management architecture. 7.3 Interoperability The new requirement on a UMTS TMN will imply a focus change from net element management towards management of information "information management". Network providers make use of different information in several different ways which also may vary from network to network and from time to time. Basic information as alarms is of course essential information for localising faults but may also be the key information to be able to set up a service with a service level agreement. Numerous of different interfaces can be identified in a UMTS network in the areas of network element management, network management and service management. The most important and complex of these interfaces will be standardised but many interfaces of less importance are unlikely to be fully standardised and will be up to the individual operator and vendor to develop. To adopt mainstream computing technologies, re-use widely used protocols, standards and an open system architecture will be essential to secure interworking between all physical entities in a UMTS. Low-cost and general access to management systems information will be needed. Obviously this is the critical issue and challenging task in the heterogeneous, distributed and complex network of a UMTS. 7.3.1 Interfaces A UMTS will consist of many different types of components based on different types of technologies. There will be access-, core-, transmission- and intelligent node networks and many of the UMTS components have already been the targets for Telecom Management standardisation at different levels. Many of these standards will be reused and the management domain of a UMTS will thereby consist of many TMNs. An architectural requirement for UMTS management shall be to support distributed TMNs and TMN-interworking on peer-to-peer basis. The Telecom Management Architecture can vary greatly in scope and detail, because of scale of operation and that different organisations may take different roles in a UMTS (see clause 5). The architecture of UMTS TMNs shall provide a high degree of flexibility to meet the various topological conditions as the physical distribution and the number of NEs. Flexibility is also required to allow high degree of centralisation of personnel and the administrative practices as well as allowing dispersion to administrative domains (see further clause 10). The 3G Telecom Management architecture shall be such that the NEs will operate in the same way, independently of the OS architecture. The following common NE management domains and interfaces can be identified in a UMTS: - Itf-N between the NE OSFs and NM/SM OSFs (see figure 2). This interface could be used by the network- and service management systems to transfer management messages, notifications and service management requests via the NE OSF to the Network Elements (NEs). This interface shall be open and the information models standardised. OSF GSM NSS OSF UTRAN OSF GPRS NEs OSF GSM BSS OSF Terminal OSF for Network Management and Service Management Itf-N NE Management Figure 2: Overview of UMTS Telecom Management Domains and Itf-N All the following interfaces are in illustrated in figure 3: ETSI ETSI TS 132 102 V3.2.0 (2000-07) 15 3G TS 32.102 version 3.2.0 Release 1999 - Itf-T between a terminal and a NE Manager. This interface will in some extent manage the 3G terminal and the USIM of the subscriber. Requirements of this interface are for further study. - Itf-B and Itf-R between UTRAN and a NE Manager. - Itf-G1 between GSM NSS and NE Manager. - Itf-G2 between GSM BSS and NE Manager. This interface is standardised in GSM 12-series specifications. - Itf-G3 between GPRS NEs and a NE Manager. This interface is based on SNMP, GSM 12.15 (charging) and GSM 12.04 (performance management). OSF GSM BSS OSF UTRAN Itf-B and Itf-R OSF Terminal Itf-T OSF GPRS NE's Itf-G3 SNMP/ GSM12.15,12.04 Itf-G2 Q3/GSM 12.xx Iu Terminal BTS BSC GSM BSS Uu UTRAN RNC NodeB Iub SGSN GGSN GGSN GPRS Network Other GPRS operator BG F/W F/W GPRS Backbone Data network (Internet) Data network (X.25) Data network (Intranet) IWU Terminal PSTN MSC/VLR HLR OSF GSM NSS Itf-G1 Q3 F/W GSM NSS Figure 3: Overview of a UMTS Network, showing management interfaces and management domains - Itf-T between a terminal and a NE Manager. This interface will in some extent manage the 3G terminal and the USIM of the subscriber. Requirements of this interface are for further study. - Itf-B and Itf-R between UTRAN and a NE Manager. - Itf-G1 between GSM NSS and NE Manager. - Itf-G2 between GSM BSS and NE Manager. This interface is standardised in GSM 12-series specifications. - Itf-G3 between GPRS NEs and a NE Manager. This interface is based on SNMP, GSM 12.15 (charging) and GSM 12.04 (performance management). ETSI ETSI TS 132 102 V3.2.0 (2000-07) 16 3G TS 32.102 version 3.2.0 Release 1999 Telecom management interfaces may be considered from two perspectives: - the management information model; - the management information exchange. The management information models will be standardised in other 3GPP documents but the management information exchange will be further described in this architectural standard. The management task will vary greatly between different network elements in a UMTS. Some NEs are of high complexity e.g. a RNC, while others e.g. a border gateway is of less complexity. Different application protocols can be chosen to best suite the management requirements of the different Network Elements and the technology used. Application protocols can be categorised out of many capabilities as: - Functionality; - Implementation complexity; - Processor requirements; - Cost efficiency; - Market acceptance, availability of "off the shelf commercial systems and software". For each telecom management interface that will be standardised by 3GPP at least one of the accepted protocols will be recommended. Accepted application protocols (e.g. CMIP, SNMP, CORBA IIOP) are defined in [2], Annex A. 7.3.2 Open systems approach Even in the second generation of mobile radio networks the operators has to cope with heterogeneous environments in many different ways. No single vendor is likely to deliver all the management systems needed for a mobile operator. The many different types of network elements, some with very high management complexity as an exchange and some less complex as a repeater system, are generally supported with unique vendor specific management systems with very low interoperability. Duplicated TMN applications is another obvious reality of this generation of management systems. This will be further discussed under Chapter 9 (TMN Applications). The new UMTS requirements call for open systems that can be supported by the marketplace, rather than being supported by a single (or limited) set of suppliers, due to the unique aspects of the design chosen. Open systems architectures are achieved by having the design focus on commonly used and widely supported interface standards. This should ensure costs and quality that are controlled by the forces of competition in the marketplace. The open systems approach is a technical and business strategy to: - Choose commercially supported specifications and standards for selected system interfaces. - Build systems based on modular hardware and software design. Selection of commercial specifications and standards in the Open systems approach should be based on: - Those adopted by industry consensus based standards bodies or de facto standards (those successful in the market place). - Market research that evaluates the short and long term availability of products. - Trade-offs of performance. - Supportability and upgrade potential within defined cost constraint. - Allowance for continued access to technological innovation supported by many customers and a broad industrial base. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 17 3G TS 32.102 version 3.2.0 Release 1999 7.3.3 Level of openness The level the interfaces conform to open standards is critical for the overall behaviour. A low level of openness will severely impact on long-term supportability, interoperability, development lead-time, and lifecycle cost and overall performance. Interfaces are expensive parts in a TMN and interfaces with low level of openness severely impact on development lead-time for the introduction of any system, application component or service. Easy implementation (plug & play) is a requirement for UMTS TMN physical entities and requires a high the level of openness. 7.3.4 Closed interfaces Many second-generation mobile network physical management entities have vendor controlled system/subsystem boundary descriptions that are not disclosed to the public or are unique to this single supplier - closed interfaces. In a UMTS network, such interfaces will not fulfil the basic requirements and can not be a part of a UMTS TMN. Closed interfaces can only be used as internal interfaces where no information what so ever has to be shared to other physical management entities. 7.4 Data communication networks Within a TMN, the necessary physical connection (e.g. circuit-switched or packet-switched) may be offered by communication paths constructed with all kinds of network components, e.g. dedicated lines, packet-switched data network, ISDN, common channel signalling network, public-switched telephone network, local area networks, terminal controllers, etc. In the extreme case the communication path provides for full connectivity, i.e. each attached system can be physically connected to all others. The TMN should be designed such that it has the capability to interface with several types of communications paths, to ensure that a framework is provided which is flexible enough to allow the most efficient communications: - between NE and other elements within the TMN; - between WS and other elements within the TMN; - between elements within the TMN; - between TMNs; - between TMNs and enterprise. In this case the term efficiency relates to the cost, reliability and maintainability of the data transported. Two aspects impact costs. The first is the actual cost to transport data across the network between the TMN and the NE. The second aspect is the design of the interface including the selection of the appropriate communications protocol. Whatever standardised protocol suite at the networking level that is capable of meeting the functional and operational requirements (including the network addressing aspects) of the Logical and Application Protocol levels of a given UMTS management interface, is a valid Networking Protocol for that interface. A number of requirements shall be met by the Networking Protocol, as follows: - Capability to run over any bearer (leased lines, X.25, ATM, Frame Relay,...) - Support of existing transport protocols and their applications, such as OSI, TCP/IP family, etc. - Widely available, cheap and reliable. The Internet Protocol (IP) is a Networking Protocol that ideally supports these requirements. IP also adds flexibility to how management connectivity is achieved when networks are rolled out, by offering various implementation choices. For instance, these may take the form of: - Dedicated management intranets. - Separation from or integration into an operator’s enterprise network. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 18 3G TS 32.102 version 3.2.0 Release 1999 - Utilisation, in one way or another, of capacities of the public Internet and its applications or other resources. 7.5 New technologies Meeting application requirements in the most affordable manner is together with development lead-time important issues identified in early UMTS management standardisation work. But the TMN functional, information and physical architectures shall also keep pace with the introduction of new technologies, services and evolving network infrastructures. Technology is advancing so rapidly today that this shall be a fundamental part of the physical architecture – to be able to easily adopt new important technologies. A UMTS will need to incorporate new successful technologies from the IT-world to which TMN standardisation is not fully applicable. Today distributed computing implementations have matured to a point where the goals of TMN can be realised using commonly available technologies for a reasonable cost. Widely accepted open standards and new IT-technologies will be indispensable to fulfil the challenging managing requirements of UMTS. New technologies in the IT business as generic application components together with distributed processing technology are new important drivers upon application design of management systems. The possibility to purchase functional components from the open market are of great importance from many aspects as cost-efficiency and time-to-market. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 19 3G TS 32.102 version 3.2.0 Release 1999 8 UMTS Management Physical architectures A UMTS Telecom Management Network will consist of many different management layers and many different building blocks. The complexity will vary greatly in detail because every organisation has different needs. The following clause will identify the most critical architectural issues and compliance conditions for a given UMTS Management Interface. It should serve as fundamental requirements for any UMTS entity (network element or management system) being a part of a UMTS TMN. 8.1 Compliance Conditions For a UMTS entity (Management System or NE) to be compliant to a given UMTS Management Interface, all the following conditions shall be satisfied: 1) It implements the management functionality following the Information Model and flows specified by the relevant 3GPP UMTS Management Interface Specifications applicable to that interface. 2) It provides at least one of the IRP Solution Sets (were available) related to the valid Application Protocols specified by 3GPP UMTS Application Protocols for that interface, [2] Annex C. 3) It provides at least one standard networking protocol. 4) In case the entity does not offer the management interface on its own, a Q-Adapter shall be provided. This Q-Adapter shall be provided independently of any other UMTS NE and/or UMTS Management System. 5) Support for Bulk Transfer Application Protocols specified by the relevant 3GPP UMTS Management Interface Specifications applicable to that interface. 8.2 Network elements management architecture The following figure demonstrates two possible options for management interface from the OS upper layers to NE. Option 1, provides access to the NE via element manager, and Option 2, provides a direct access. It is sufficient to provide one or the other. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 20 3G TS 32.102 version 3.2.0 Release 1999 OS Upper layers OSF OS Element Management LAYER OSF Network Element Fully standardized (3GPP Management Application Protocol + 3GPP Object Model) DCN DCN Open (3GPP Management Application Protocol + Vendor defined Object Model) Note: 3GPP Management Application Protocols are listed in 32.101 Annex A. Option 1 Option 2 Figure 4: Network Element Management Architecture For a UMTS entity (network element or management system) to be compliant to a given UMTS Management Interface the following conditions shall all be satisfied: Item Compliance conditions 1 Implements relevant 3GPP UMTS Management Information Model and flows 2 Application protocol ( e.g. CMIP,SNMP,CORBA IIOP) (Defined in [2], Annex A) Implements relevant IRP Solution Sets, if available for that application protocol. (Defined in TS 32.101 [2], Annex C) 3 Valid Network Layer Protocol (see Annex B of TS 32.101 [2]) 4 Lower protocol levels required by Item 1,2 and 3 ETSI ETSI TS 132 102 V3.2.0 (2000-07) 21 3G TS 32.102 version 3.2.0 Release 1999 Any other entity taking part in a UMTS, as an implementation choice, shall satisfy the following condition: Item Compliance conditions 1 Not standardised but open 8.3 Network & Subnetwork Element Management Architecture (Example UMTS RNC / NodeB) An important special case of the network element management architecture is where one type of network element as the RNC will need management information for co-ordination of a subnetwork of other types of network elements as NodeB. This management information shared between the RNC and NodeB will not reach the operators and is not considered to be a part of the UMTS TMN. All other management information related to NodeB will transparently be transferred by the RNC towards the UMTS TMN. DCN Management Systems O&M functions O&M functions for Co-located equipment Resource Mgt functions O&M functions Resource mgt functions for NodeB RNC NodeB I NodeB n Interface for resource management functions for NodeB. Will be fully standardised by other 3GPP bodies. Network element management interface. DCN Figure 5: Network and Subnetwork Management Architecture For a UMTS entity (network element, subnetwork element or management system) to be compliant to a given UMTS Management Interface the following conditions shall be satisfied: ETSI ETSI TS 132 102 V3.2.0 (2000-07) 22 3G TS 32.102 version 3.2.0 Release 1999 Item Compliance conditions 1 Implements relevant 3GPP UMTS Management Information Model and flows 2 Application protocol ( e.g. CMIP,SNMP,CORBA IIOP) (Defined in [2], Annex A) Implements relevant IRP Solution Sets, if available for that application protocol. (Defined in [2], Annex C) 3 Valid Network Layer Protocol (see Annex B of TS 32.101 [2]) 4 Lower protocol levels required by Item 1,2 and 3 8.4 Operations Systems interoperability architecture. Interoperability between operations systems is an important issue in a UMTS. Different organisations may take different roles in a UMTS. The need to share information across corporate boundaries will be a consequence of this. The heterogeneous, distributed and complex network of a UMTS will be a market for many different vendors. All operations systems have to interoperate and shall be able to share information. This is a critical issue in the management of third generation systems. OS1 OS2 OSF OSF DCN Figure 6: Operations Systems interoperability Architecture For a Operations System to be UMTS TMN compliant the following conditions shall all be satisfied: Item Compliance conditions 1 Implements relevant 3GPP UMTS Management Information Model and flows 2 Application protocol ( e.g. CMIP,SNMP,CORBA IIOP) (Defined in [2], Annex A) Implements relevant IRP Solution Sets, if available for that application protocol. (Defined in [2], Annex C) 3 Valid Network Layer Protocol (see Annex B of TS 32.101 [2]) 4 Lower protocol levels required by Item 1,2 and 3 ETSI ETSI TS 132 102 V3.2.0 (2000-07) 23 3G TS 32.102 version 3.2.0 Release 1999 8.5 Operations Systems intra-operability architecture OS-QExternal OS1 OS2 OSF 1 OSF 2 OSF 3 OS-QInternal DCN Figure 7: Operations Systems intra-operability Architecture OS-QInternal indicates an internal flow and should to be compliant with a given UMTS Management Interface satisfy the following conditions: Item Compliance conditions 1 Implements relevant 3GPP UMTS Management Information Model and flows 2 Application protocol ( e.g. CMIP,SNMP,CORBA IIOP) defined in [2], Annex A Implements relevant IRP Solution Sets, if available for that application protocol. (Defined in [2], Annex C) OS-QExternal indicates an external flow and shall to be compliant to a given UMTS Management Interface satisfy the following conditions: Item Compliance conditions 1 Implements relevant 3GPP UMTS Management Information Model and flows 2 Application protocol ( e.g. CMIP,SNMP,CORBA IIOP) (Defined in [2], Annex A) Implements relevant IRP Solution Sets, if available for that application protocol. (Defined in [2], Annex C) 3 Valid Network Layer Protocol (see Annex B of TS 32.101 [2]) 4 Lower protocol levels required by Item 1,2 and 3 8.6 Business System interconnection architecture The business management layer has in the second-generation systems a very low degree of standardisation. Operators have legacy systems or more IT influenced systems often adopted to every organisations different needs. Business systems are not a part of a UMTS TMN. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 24 3G TS 32.102 version 3.2.0 Release 1999 Business Systems QA OSF 1 OSF 2 OS-QExternal OS-QExternal OS IFx Figure 8: Business Systems interconnection architecture OS-QExteral Indicates an external flow and shall to be compliant to a given UMTS Management Interface satisfy the following conditions: Item Compliance conditions 1 Implements relevant 3GPP UMTS Management Information Model and flows 2 Application protocol ( e.g. CMIP,SNMP,CORBA IIOP) (Defined in [2], Annex A) Implements relevant IRP Solution Sets, if available for that application protocol. (Defined in [2], Annex C) 3 Valid Network Layer Protocol (see Annex B of TS 32.101 [2]) 4 Lower protocol levels required by Item 1,2 and 3 IFX indicates an external flow and shall to be compliant to a given UMTS Management Interface satisfy the following condition: Item Compliance conditions 1 Not standardised but open ETSI ETSI TS 132 102 V3.2.0 (2000-07) 25 3G TS 32.102 version 3.2.0 Release 1999 9 TMN applications Telecom management applications can be implemented in many different ways depending on constraints presented in previous clauses of the present document. Consistent operational processes are required for the management of the network irrespective of vendor equipment. A mobile operator can because of the very heterogeneous nature of their networks easily end of with dozens of duplicated applications for e g alarm surveillance. Most vendors of network equipment offers dedicated net-element managers and the ones not built with an open system approach will severely limit the possibility to report and manage the network in a consistent way. Network element vendors with closed and unique net-element managers or operations systems with closed interfaces or interfaces with low level off openness will not fulfil the basic requirements as a part of a UMTS. It will not be possible to design and build the telecom management network to support the operational processes as required. Such physical entities are not under consideration in the present document. Many TM application functions can be identified as generic functions used by all major types of telecom equipment. Alarm surveillance applications and performance analysing applications are generic necessities to manage most network elements. Security and system management applications are also common to many TM components and may be the scope for overall business policies. To identify and specify the design criteria that will allow re-usable application components to be developed across multiple telecom business scenarios are important issues to fulfil the basic UMTS Management requirement. "To minimise the costs of managing a UMTS network such that it is a small component of the overall operating cost". The implication of the top down approach in the standardising work of UMTS is that consistent operational management processes are required irrespective of vendor equipment. Generic management applications is required to facilitate: - Reduced management application development costs. - Simplification of operational processes and associated reduction in costs. - Reduced time to deploy new services as management systems already exist. - Consistent representation of basic information. NE Vendor A NE Vendor B NW Mgt layer EM layer FM Vendor A FM Vendor B FM Vendor x NE Vendor C FM Vendor C NE Type A FM Vendor x Figure 9: Unique NE fault management Figure 9 represents a very common situation in the management of second generation of mobile networks. Different vendors supplied their network elements with unique net-element managers. The interfaces were mostly proprietary or unique. The information models for generic information as alarms were rarely standardised. All together the consequence for the operators became very complex. Similar information at many levels, repeated acknowledge of alarms, inconsistent representation of similar information are a few of all the difficulties the operators had to cope with. Some of the more severe implication of this situation is the difficulty to add more intelligence into the applications to better support the processes of the network providers. The operators who tried to brake up this situation had to put in a lot of effort into software development and proprietary interfaces. The marketplace did not support the needs of the operators. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 26 3G TS 32.102 version 3.2.0 Release 1999 NE Vendor A NE Vendor B FM NE Vendor C NE Type A Figure 10: Generic fault management Figure 10 indicates the situation were the telecom management process alarm surveillance is supported by a generic application for fault management. A common information model and accessibility to all related information will make it possible to add more intelligence to the management systems and to better support the management task. TMN application functions as billing information collection or configuration management of a specialised network element are examples of application that can be identified as unique applications. Even these applications will need to interoperate with other applications and will also need the open system approach to be a part of a UMTS TMN. With a network with many different types of network elements a common graphical user interface as a web browser for configuration management applications could be an important issue to create consistent operational processes. The complexity and heterogeneous nature of UMTS calls for easy integration (plug&play) of HW/SW. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 27 3G TS 32.102 version 3.2.0 Release 1999 10 Integration Reference Points (IRPs) 10.1 General Relating to the OSI functional areas "FCAPS", IRPs are here introduced addressing parts of "FCPS" – Fault, Configuration, Performance, and Security management. Comparing with TMF TOM (Telecom Operations Map) [20], the introduced IRPs address process interfaces at the EML-NML (Element Management Layer – Network Management Layer) boundary. In 3GPP/SA5 context, this can also be applied to the Itf-N between EM-NM and NE-NM. The three cornerstones of the IRP concept are: - Top-down, process-driven modelling approach The purpose of each IRP is automation of one specific task, related to TMF TOM. This allows taking a "one step at a time" approach with a focus on the most important tasks. - Protocol-independent modelling Each IRP consists of a protocol-independent model (the IRP information model) and several protocol-dependent models (IRP solution sets). - Standard based protocol dependent modelling Models in different IRP solution sets (CMIP, SNMP, WBEM etc.) will be different as existing standard models of the corresponding protocol environment need to be considered. The means that solution sets largely need to be "hand crafted". 10.2 Integration levels Virtually all types of telecom/datacom networks comprise many different technologies purchased from several different vendors. This implies that the corresponding management solution need to be built by integrating product-specific applications from different vendors with a number of generic applications that each provide some aspect of multi- vendor and/or multi-technology support. A complete management solution is thus composed of several independent applications. The following levels of integration are defined: - Screen Integration: Each application provides its own specific graphical user interface (GUI) that need to be accessible from a single, unified screen (a common desktop). A seamless integration between the various GUIs is then required. Screen Integration will not be standardised in the present document. - Application Integration: Applications need to interwork, on a machine-machine basis, in order to automate various end-to-end processes of a communication provider. 10.2.1 Application integration Interfaces related to application integration can be divided in the following three categories: - High-level generic interfaces between generic applications on the network and service management layers. The same approach and concepts apply for these as the next category: - High-level (technology-independent to the extent possible) interfaces between product-specific and generic applications are needed in order to automate and streamline frequently occurring tasks applicable to several types of network elements. A top-down approach shall be taken when defining these interfaces, where the main input is (1) business processes of a communication provider, and (2) the types of generic applications that are used to implement the process support. The interfaces need to be stable, open and (preferably) standardised. These IRPs are discussed below under the heading Network Infrastructure IRPs. - Detailed (product-specific) interfaces between product-specific applications and the corresponding network elements are of course also needed. These interfaces are defined using the traditional bottom-up approach, where the actual network infrastructure is modelled. This is the traditional TMN approach to element management. The management information in these interfaces is not further discussed in this document, as it is internal to a ETSI ETSI TS 132 102 V3.2.0 (2000-07) 28 3G TS 32.102 version 3.2.0 Release 1999 specific development organisation and does not need to be open. In fact, by publishing the management information in these interfaces, too much of the internal design may be revealed and it may become impossible to later enhance the systems that are using the interfaces. The management services (operations and notifications) and protocol shall however be open and standardised as long as they are independent of the NRM describing the managed NEs/NRs. 10.3 Network infrastructure IRPs When providing integrated management solutions for multi-vendor networks, there is a strong requirement that the NEs and the management solutions that go together with them are systems integrateable. It is here proposed that the telecom vendors provide a set of Network Infrastructure IRPs. It should be noted that these IRPs could be provided by either the NE, or the Element Manager (EM) or Sub-Network Manager (SNM) that goes together with the type of NE. There is actually not a clear distinction any more between NE and element management applications, mainly due to the increased processing capacity of the equipment platforms. Embedded Element Managers providing a web user interface is a common example of that. These IRPs are introduced to ensure interoperability between Product-Specific Applications (PSA) and the types of generic applications shown in the figure below. These IRPs are considered to cover the most basic needs of task automation. Alarm IRP Service Activation Performance data IRP Inventory Management Performance Monitoring / Data Warehouse Fault Managagement NE PSA NE PSA IRP (alternative 2) IRP (alternative 1) EM/ SNM EM/ SNM Figure 11: IRPs for application integration The following gives examples of some basic IRPs: The most basic need of a fault management (FM) application is to support alarm surveillance. Product-specific applications need to supply an Alarm IRP to forward alarms from all kinds of NEs and equipment to the FM application. A Basic Configuration Management IRP is needed for management of topology and logical resources in the network (retrieval of the configuration and status of the network elements). It can also be used by inventory management applications, to track individual pieces of equipment and related data, as well as for all types of Configuration Management e.g. Service Activation applications, as a provisioning interface for frequent configuration activities that require automation. This IRP defines an IRP Information Model, covering both an IRP Information Service and a Network Resource Model. Performance Monitoring (PM) information is made available through the Performance Data IRP. It is realised that the Alarm IRP, Performance Data IRP and Basic Configuration Management IRP all have similar needs to use notifications. The corresponding service is formalised as a Notification IRP. It specifies: firstly, an ETSI ETSI TS 132 102 V3.2.0 (2000-07) 29 3G TS 32.102 version 3.2.0 Release 1999 interface through which subscriptions to different types of notifications can be set up (or cancelled), and secondly, common attributes for all notifications. Further, applying a common Name Convention for Managed Objects is useful for co-operating applications that require identical interpretation of names assigned to network resources under management. 10.4 Defining the IRPs It is important to avoid dependency on one specific technology, as the technologies will change over time. Applications need to be future-proof; One fundamental principle for achieving this is to clearly separate information models from protocols for the external interfaces, where the information models are more important than the selection of protocols. Thus, the detailed IRP specifications are divided into two main parts, following the directives from TMF’s SMART TMN: • Information models specified with an implementation neutral modelling language. The Unified Modelling language (UML) has been selected, as it is standardised (by OMG), supported by most object-oriented tools and used in several ongoing standardisation efforts (CIM etc.). • Solution sets, i.e. mappings of the information models to one or several protocols (CORBA/IDL, SNMP/SMI, CMIP/GDMO, COM/IDL etc.). Different protocol selections may be done for different IRPs. Figure 12 shows an example of how an IRP can be structured (the Alarm IRP). ETSI ETSI TS 132 102 V3.2.0 (2000-07) 30 3G TS 32.102 version 3.2.0 Release 1999 Figure 12: IRP example 10.5 Mandatory, Optional and Conditional qualifiers This subclause defines a number of terms used to qualify the relationship between the ‘Information Service’, the ‘Solution Sets’ and their impact on the IRP implementations. The qualifiers defined in this section are used to qualify IRPAgent behaviour only. This is considered sufficient for the specification of the IRPs. Table 1 defines the meaning of the three terms Mandatory, Conditional and Optional when they are used to qualify the relations between operations, notifications and parameters specified in ‘Information Service’ documents and their equivalents in Solution Set (SS) documents. Table 1: Definitions of Mandatory, Optional and Conditional Used in Information Service Documents Mandatory (M) Conditional (C) Optional (O) Operation and Notification Each Operation and Notification shall be mapped to its equivalents in all SS’s. Mapped equivalent shall be M. Each Operation and Notification shall be mapped to its equivalents in at least one SS. Mapped equivalent can be M or O. Each Operation and Notification shall be mapped to its equivalents in all SS’s. Mapped equivalent shall be O. Input and output parameter Each parameter shall be mapped to one or more information elements of all SS’s. Mapped information elements shall be M. Each parameter shall be mapped to its equivalent in at least one SS. Mapped equivalent can be M or O. Each parameter shall be mapped to its equivalent in all SS’s. Mapped equivalent shall be O. IRP Solution Sets Application Layer Protocol independent Protocol specific IRP Information Service Corba/IIOP Alarm IRP: Information Service - Alarm reporting parameters consistent with ITU-T M.3100, X.721, X.733, X.736 and ETSI GSM 12.11 standards, and UMTS-specific probable causes (Text) - Operations possible over the Alarm IRP (UML/Text) SNMP solution set - Alarm IRP SNMP (SMIv2) MIB - IRP operation mapping matrix to SNMP Corba solution set - Alarm reporting parameters mapped to OMG Structured Event - Corba IDL files defining IRP operations SNMP Transport Layer Network Layer UDP TCP IP CMIP solution set - Profile of relevant ITU-T/ ETSI standards OSI network protocol OSI transport protocol CMIS CMIP ETSI ETSI TS 132 102 V3.2.0 (2000-07) 31 3G TS 32.102 version 3.2.0 Release 1999 Table 2 defines the meaning of the two terms Mandatory and Optional when they are used to qualify the relations between operations, notifications and parameters equivalents specified in Solutions Sets and their impact on IRPAgent implementation. The terms are used in Solution Set documents. Table 2: Definitions of Mandatory and Optional Used in Solution Set Documents Mandatory Optional Mapped notify equivalent IRPAgent shall generate it. IRPManager should be prepared to receive and process it. IRPAgent may generate it. IRPManager should be prepared to receive it but can ignore it. Mapped operation equivalent IRPAgent shall have an implementation. IRPManager may use (e.g., invoke) it. IRPAgent may have an implementation. IRPManager may use (e.g., invoke) it and should be prepared that IRPAgent may not have an implementation. input parameter of the mapped operation equivalent IRPAgent shall accept and behave according to its value. IRPManager should use it with a legal value. If the optional parameter is present the IRPAgent may reject the invocation or the IRPAgent may accept the invocation but ignore the parameter. IRPManager may use it but should be prepared that IRPAgent may reject or ignore it. Input parameter of mapped notify equivalent AND output parameter of mapped operation equivalent IRPAgent shall generate it with a legal value. IRPManager should be prepared to receive it but can ignore it. IRPAgent may generate it. If IRPAgent generates it, it shall use a legal value. IRPManager should be prepared to receive it but can ignore it. 11 Implementation aspects 11.1 Layering of the OS applications UMTS operators might categories and organise its operation systems in many different ways as: - A national fault and performance OS. - A national charging, billing and accounting OS. - Regional configuration OS. - Regional fault, performance and configuration OS. - etc. This geographical dependent categorisation may change after time and the growth of the network. A physical architecture based on an open system design and re-usable application components would ease the work to adopt such structural changes. A management system build for a UMTS shall provide the possibility of layering the applications. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 32 3G TS 32.102 version 3.2.0 Release 1999 12 TMN planning and design considerations A TMN should be designed such that it has the capability to interface with several types of communications paths to ensure that a framework is provided which is flexible enough to allow for the most efficient communications: - Between one NE and other elements within the TMN; - Between a WS and other elements within the TMN; - Between elements within the TMN; - Between TMNs. The basis for choosing the appropriate interfaces, however, should be the functions performed by the elements between which appropriate communications are performed. The interface requirements are specified in terms of function attributes needed to provide the most efficient interface. 12.1 Function attributes a) Reliability – The capability of the interface to ensure that data and control are transferred such that integrity and security are maintained. b) Frequency – How often data is transferred across the interface boundary (Normal behaviour). c) Quantity – The amount of data that is transferred across the interface during any transaction. d) Priority – Indicates precedence to be given to data in case of competition for network resources with other functions. e) Availability – Determines the use of redundancy in the design of the communications channels between interfacing elements. f) Delay – Identifies the amount of buffering that may be tolerable between interfacing elements. This also impacts communications channel designs. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 33 3G TS 32.102 version 3.2.0 Release 1999 Table 3 suggests a possible ranges for these function attributes. Table 3: Possible ranges for TMN function attributes [1] Attributes Requirements Nature of attributes Delay (speed) Short Medium Long Performance or grade of service (P) Reliability (accuracy) High Medium Low Objective of design and control (acceptable/unacceptable but available/unavailable) Availability High Medium Low Quantity Large Medium Small Characteristics of TMN traffic (C) Frequency Often continuous Periodic Sparse Condition or parameter of design Priority High Medium Low 12.2 Functional characteristics Each major type of telecommunications equipment has functional characteristic needs that can be used to describe the complexity of the interface. There are, however, a basic group of TMN application functions that cross all major types of telecommunications equipment. There are also unique TMN application functions that are performed by specific categories of major telecommunications equipment. Alarm surveillance is an example of the former, whereas billing information collection is an example of the latter. Functional characteristics of the elements within a TMN, e.g. OS, DCN and MD also describe the complexity of interfaces between these elements. 12.3 Critical attributes Attribute values for a given function are generally consistent across the network elements. When considering a single interface, it is important to identify the controlling attribute ranges for the design of the interface. If there are conflicting attribute values for different functions in a given network element, more than one instance of an interface may be needed. Overall TMN attribute values for the interfacing of elements within the TMN depend on the type and number of functions performed within these elements. In this case the functions are not consistent across TMN elements, but are controlled by the individual TMN design of an Administration. 12.4 Protocol selection In many cases, more than one protocol suite will meet the requirements for the network element or TMN element under consideration. It is the approach for the 3GPP Telecom management standardisation to concentrate on protocol independent information models, allowing the mapping to several protocol suites. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 34 3G TS 32.102 version 3.2.0 Release 1999 The rational behind this is: - The blurring of Information and Telecommunication technologies in UMTS, it is required to work on a more open approach (acknowledging the market status and foreseen evolutions). - The life-cycle of information flows is 10 to 20 years, while the protocols is 5 to 10 years. - The developments on automatic conversion allows for a more pragmatic and open approach. The choice of the individual protocol from the recommended family will be left open to the vendors and operators. To provide the most efficient interface care should be taken to select the protocol suite that optimises the relationship between the total cost to implement that protocol suite, the functional attributes and the data communications channels that carry the information across the interface. DCN architectures shall be planned and designed to ensure that their implementation provides appropriate degrees of availability and network delay while minimising cost. One shall consider the selection of communications architectures, e.g. star, multipoint, loop, tree, etc.. The communications channels, e.g. dedicated lines, circuit-switched networks and packet networks used in providing the communications paths, also play an important role. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 35 3G TS 32.102 version 3.2.0 Release 1999 13 Mediation/Integration The increase in the need to incorporate a hybrid set of technologies, multiple protocols and heterogeneous resources requires the availability of open management interfaces between the management systems and the different network resources. These interfaces require an underlying mechanism to mediate - interpret, translate, and handle data – between the various data representations and protocols. A set of Technology Integration Points [21] can be identified and will need to be supported. Software components on the open market as automatic conversion applications, gateways, mediation applications will be valuable products to fulfil the challenging task to incorporate multiple protocols and heterogeneous resources. Figure 13 summarises Technology Integration Points for some technologies: pplication Objects CORBA Facilities Domain I/Fs Object Request Broker Agents CORBA Services Web Browsers Java Internet 1 2 3 4 CMIS / SNMP GDMO / SMI Manager Manager / Agent Environment 5 Figure 13: Technology Integration Points [21] Essentially, figure 13 indicates that from the technologies selected, three technology areas will need to be integrated. These are: - Internet/Web based services; - Object Request Broker (CORBA) based services; - Telecom based Manager/Agent services (i.e. CMIP/GDMO and SNMP/SMI). ETSI ETSI TS 132 102 V3.2.0 (2000-07) 36 3G TS 32.102 version 3.2.0 Release 1999 In order to provide adequate points of integration between these areas of technology, five Integration Points (IPs) have been identified - as outlined in table 4 below: Table 4: Technology Integration Points [21] Managed Objects (GDMO/SMI) Management Services (CMISE/SNMP) Java Objects Web Browser (HTTP/HTML) TMN Agent CORBA Objects IP1 IP4 IP3 CORBA Services IP2 TMN Manager IP5 IP1 Provides mapping of objects defined in CORBA/IDL to managed objects defined in GDMO or SMI. IP2 Provides mapping of appropriate CORBA Services to CMIS and SNMP services. IP3 Provides a mapping of Web Browser technology access to CORBA objects (for situations where this may be needed as an addition to/replacement of Browser access to a database). IP4 Provides a mapping between Java based objects and CORBA objects. IP5 Provides a high level convenient programming interface for the rapid development of TMN based manager/agent interactions. It also provides a convenient point of integration if it is necessary to separate out the two sides of the manager/agent interface from the point of view of technology selection. For example, allowing the manager role to perhaps be supported in a Web-based environment, but giving a good point of integration with a TMN based agent. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 37 3G TS 32.102 version 3.2.0 Release 1999 Annex A (informative): Technology considerations A.1 TMN physical blocks TMN functions can be implemented in a variety of physical configurations (M.3010 [1]). The relationship of the functional blocks to physical equipment is shown in Table A.1 which names the TMN physical blocks according to the set of function blocks which each is allowed to contain. For each physical block there is a function block which is characteristic of it and is mandatory for it to contain. There also exist other functions, which are optional for the physical blocks to contain. Table A.1 does not imply any restriction of possible implementations, but defines those identified within this Recommendation. The subclauses below give the definitions for consideration in implementation schemes. Table A.1: Relationship of TMN physical block names to TMN function blocks (Note 2 & Note 3) NEF TF OSF WSF NE M O O O (Note 3) QA, XA, QM, XM M OS O M O WS M M Mandatory O Optional NOTE 1: Within this table, where more than one name is possible, the choice of the physical block name is determined by the predominant usage of the block. NOTE 2: TMN physical blocks may contain additional functionality, which allows them to be managed. NOTE 3: For the WSF to be present the OSF shall also be present. This means that the WSF shall address an OSF. The local man-machine access is not considered part of the TMN. A.1.1 Operations System (OS) The OS is the system, which performs OSFs. The OS may optionally provide QAFs and WSFs. A.1.2 Transformation Transformation provides conversion between different protocols and data formats for information interchange between physical blocks. There are two types of transformation: adaptation and mediation that can apply at q or x reference points. A.1.2.1 Adaptation device An Adaptation Device (AD), or adapter, provides transformation between a non-TMN physical entity to a NE to OS within a TMN. A Q-adapter (QA) is a physical block used to connect NE-like or OS-like physical blocks with non- TMN compatible interfaces (at m reference points) to Q interfaces. An X-adapter (XA) is a physical block used to connect non-TMN physical entities having a non-TMN communication mechanism in a non-TMN environment to an OS at the edge of a TMN. A.1.2.2 Mediation Device (MD) A Mediation Device (MD) provides transformation between TMN physical blocks that incorporate incompatible communication mechanisms. A Q-Mediation Device (QMD) is a physical block that supports connections within one TMN. An X-Mediation Device (XMD) is a physical block that supports connections of OSs in different TMNs. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 38 3G TS 32.102 version 3.2.0 Release 1999 A.1.3 Network Element (NE) The NE is comprised of telecommunication equipment (or groups/parts of telecommunication equipment) and support equipment or any item or groups of items considered belonging to the telecommunications environment that performs NEFs. The NE may optionally contain any of the other TMN function blocks according to its implementation requirements. The NE has one or more standard Q-type interfaces and may optionally have F and X interfaces. Existing NE-like equipment that does not possess a TMN standard interface will gain access to the TMN via a Q Adapter Function, which will provide the necessary functionality to convert between a non-standard and standard management interface. NEs may be distributed or centralised. Various parts of a NE are not geographically constrained to one physical location. For example, the parts may be distributed along a transmission system. An example of a distributed NE is illustrated in Figure A.1 (M.3013 [22]). T0412200-99 OS OSF Q NE NE NE NEF NEF Figure A.1: Distributed network element A.1.4 Workstation (WS) The WS is the system, which performs WSFs. The workstation functions translate information at the f reference point to a displayable format at the g reference point, and vice versa. If equipment incorporates other TMN functionality as well as the WSF, then it is named by one of the other names in Table A.1 A.1.5 Data Communication Network (DCN) A DCN supporting a TMN has traditionally conformed to the network service of the OSI reference model for ITU-T applications as specified in Recommendation X.200 [4]. ITU-T Recommendation X.25 has been a commonly used packet protocol. However, the evolution of telecommunication services is merging circuit-switched and packet- switched modes with advancing technologies of ISDN, ATM, SDH, and the Internet. A variety of telecommunications services can be employed as long as integrity of information transfer can be preserved. Within a TMN, the necessary physical connection, such as circuit-switched or packet-switched, may be offered by communication paths constructed with various network components, including dedicated lines, X.25 packet-switched data network, ISDN, common channel signalling network, public-switched telephone network, local area networks, terminal controllers, etc. The facilities can be either dedicated to a DCN or shared resources (for example, using SS No. 7 or an existing X.25 or IP-based packet-switched network). Equipment supporting an OSF shall provide for two modes of data communication. These are spontaneous transmission of messages (e.g. for the NEF to the OSF) and a two-way dialogue (e.g. as the OSF obtains supporting information from the NEF and sends commands to the NEF or transfer messages to or from another OSF). In addition, an OSF is responsible for assuring the integrity of the data channels through a DCN. Physical connectivity in a local environment may be provided by a variety of subnetwork configurations including point-to-point, star, bus or ring. The DCN may consist of a number of individual subnetworks of different types, interconnected together. The DCN may be a local path or a wide-area connection among distributed physical blocks. The DCN is technology independent and may employ any single or combination of transmission technologies. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 39 3G TS 32.102 version 3.2.0 Release 1999 A.1.6 TMN logical layered architecture within the TMN physical architecture Four specialisations of the OS physical block are defined to support a physical realisation of function blocks in logical layers. The four specialised OS physical blocks are the Business (B-OS), the Service (S-OS), the Network (N-OS) and the Element (E-OS) Operations Systems. These physical blocks are named according to the predominant function block they contain. Specifically, B-OS, S-OS, N-OS and E-OS predominantly contain B-OSF, S-OSF, N-OSF and E-OSF respectively. When physical blocks contain more than one kind of specialised OS function block that provide substantial functionality to the physical block, thus spanning more than one logical layer, the physical block is named according to the highest hierarchically layered function block. For example, a physical block containing both N-OSF and E-OSF, providing substantial network functionality is called an N-OS. The exchange of management information between logical layers employs the managing roles and managed roles of the TMN interaction model. This allows management activities to be clustered into layers and to be decoupled. The managed roles will be associated with a set of information elements from information model(s) exposing a view at the layer's level of abstraction (e.g. equipment, element, network, service, etc.). Generally, managing and managed roles may be placed in logical layers without restriction. A managed role may be associated with a set of information elements from any layer. Managed roles may be placed in any layer and invoke operations associated with any other managed roles. A.1.7 Interoperable interface concept In order for two or more TMN physical blocks to exchange management information they shall be connected by a communications path and each element shall support the same interface onto that communications path. It is useful to use the concept of an interoperable interface to simplify the communications problems arising from a multi-vendor, multi-capability network. The interoperable interface defines the protocol suite and the messages carried by the protocol. Transaction-oriented interoperable interfaces are based upon an object-oriented view of the communication and therefore, all the messages carried deal with object manipulations. It is the formally defined set of protocols, procedures, message formats and semantics used for the management communications. The message component of the interoperable interface provides a generalised mechanism for managing the objects defined for the information model. As part of the definition of each object there is a list of management operations types which are valid for the object. In addition, there are generic messages that are used identically for many classes of managed objects. In the architecture, what predominantly distinguishes one interface from another is the scope of the management activity that the communication at the interface shall support. This common understanding of the scope of operation is termed Shared Management Knowledge. Shared Management Knowledge includes an understanding of the information model of the managed network (object classes supported, functions supported, etc.), management support objects, options, application context supported, etc. The Shared Management Knowledge ensures that each end of the interface understands the exact meaning of a message sent by the other end. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 40 3G TS 32.102 version 3.2.0 Release 1999 A.2 TMN standard interfaces Figure A.2 shows an example of a physical architecture. It represents each of the functions as physical blocks and illustrates how a number of interfaces might share communication paths within a given TMN physical architecture. T0412190-99 OS WS MD F X Q QA NE QA NE Q/F Q Q X F WS X/Q/F X/Q/F X/Q/F TMN DCN DCN Figure A.2: Examples of interfaces for the TMN physical architecture M.3010 [1] Figure A.2 shows the interconnection of the various TMN physical blocks by a set of standard interoperable interfaces. The allowable interconnections of these standard interfaces within a given TMN may be controlled by both the actual interfaces provided and/or by security and routing restrictions provided within the various physical block entities (e.g. passwords, log-ons, DCN routing assignment, etc.). TMN standard interfaces are defined corresponding to the reference points. They are applied at these reference points when external physical connections to them are required. There is a family of protocol suites for each of the TMN interfaces: Q, X and F. The choice of the protocol is dependent on the implementation requirements of the physical configuration. A.2.1 Q interface The Q interface is applied at q reference points. To provide flexibility of implementation, the class of Q interfaces is made up of the following subclasses: - the interface Q is applied at the q reference point; - the Q interface is characterised by that portion of the information model shared between the OS and those TMN elements to which it directly interfaces. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 41 3G TS 32.102 version 3.2.0 Release 1999 A.2.2 F interface The F interface is applied at f reference points. The F interfaces connecting workstations to the TMN building blocks containing OSFs or MFs through a data communication network are included in this Recommendation. Connections of implementation specific, WS-like entities to OSs or NEs, are not subject of this Recommendation. A.2.3 X interface The X interface is applied at the x reference point. It will be used to interconnect two TMNs or to interconnect a TMN with other network or systems which accommodates a TMN-like interface. As such, this interface may require increased security over the level, which is required by a Q-type interface. It will therefore be necessary that aspects of security are addressed at the time of agreement between associations, e.g. passwords and access capabilities. The information model at the X interface will set the limits on the access available from outside the TMN. The set of capabilities made available at the X interface for access to the TMN will be referred to as TMN Access. Additional protocol requirements may be required to introduce the level of security, non-repudiation, etc. which is required. A.2.4 Relationship of TMN interfaces to TMN physical blocks Table A.1 defines the possible interfaces, which each named TMN physical block can support. It is based upon the function blocks which Table A.1 associates with each physical block and the reference points between function blocks. ETSI ETSI TS 132 102 V3.2.0 (2000-07) 42 3G TS 32.102 version 3.2.0 Release 1999 Annex B (informative): Change history This annex lists all change requests approved for this document since the specification was first approved by 3GPP TSG-SA. Change history TSG SA# Version CR Tdoc SA New Version Subject/Comment S_06 - - SP-99578 3.0.0 Approved at TSG SA #6 and placed under Change Control S_07 3.0.0 001 SP-000015 3.1.0 resolving remaining R99 inconsistency between 32.101 & 32.102 S_07 3.0.0 002 SP-000015 3.1.0 Correction of IRP-related terminology Mar 2000 3.1.0 3.1.1 Cosmetic S_08 3.1.1 003 SP-000227 3.2.0 Clarification of compliance conditions S_08 3.1.1 004 SP-000228 3.2.0 Update ITU-T TMN related reference material S_08 3.1.1 005 SP-000229 3.2.0 Definition of the Mandatory/Optional/Conditional qualifiers used in the IRPs S_08 3.1.1 006 SP-000230 3.2.0 Correction of erroneous editing and usage of undefined term 43 ETSI ETSI TS 132 102 V3.2.0 (2000-07) 3G TS 32.102 version 3.2.0 Release 1999 History Document history V3.0.0 January 2000 Publication V3.1.1 March 2000 Publication V3.2.0 July 2000 Publication
9f1d172320d152e366512ff4afa2ff1b	129 119	1 Scope	........................................................................................................................................................5
9f1d172320d152e366512ff4afa2ff1b	129 119	1.1 References	.......................................................................................................................................................... 5
9f1d172320d152e366512ff4afa2ff1b	129 119	2 Definitions and abbreviations	..................................................................................................................5
9f1d172320d152e366512ff4afa2ff1b	129 119	2.1 Definitions	......................................................................................................................................................... 5
9f1d172320d152e366512ff4afa2ff1b	129 119	2.2 Abbreviations	..................................................................................................................................................... 6
9f1d172320d152e366512ff4afa2ff1b	129 119	3 General	.....................................................................................................................................................6
9f1d172320d152e366512ff4afa2ff1b	129 119	4 Transmission order and bit definitions	....................................................................................................7
9f1d172320d152e366512ff4afa2ff1b	129 119	5 GTP header	..............................................................................................................................................7
9f1d172320d152e366512ff4afa2ff1b	129 119	6 GTP Message and Message Formats	.......................................................................................................7
9f1d172320d152e366512ff4afa2ff1b	129 119	6.1 Signalling Message Formats	.............................................................................................................................. 7
9f1d172320d152e366512ff4afa2ff1b	129 119	6.2 Path Management messages	.............................................................................................................................. 7
9f1d172320d152e366512ff4afa2ff1b	129 119	6.3 Tunnel Management messages	.......................................................................................................................... 8
9f1d172320d152e366512ff4afa2ff1b	129 119	6.4 Location Management message	......................................................................................................................... 8 6.5 Mobility Management messages........................................................................................................................ 9
9f1d172320d152e366512ff4afa2ff1b	129 119	6.6 Reliable delivery of signalling messages	........................................................................................................... 9
9f1d172320d152e366512ff4afa2ff1b	129 119	6.7 Information element	........................................................................................................................................... 9
9f1d172320d152e366512ff4afa2ff1b	129 119	7 Signalling Plane (GTP-C)	........................................................................................................................9
9f1d172320d152e366512ff4afa2ff1b	129 119	8 GTP-U	......................................................................................................................................................9
9f1d172320d152e366512ff4afa2ff1b	129 119	9 Path Protocol	............................................................................................................................................9
9f1d172320d152e366512ff4afa2ff1b	129 119	10 Error handling	..........................................................................................................................................9
9f1d172320d152e366512ff4afa2ff1b	129 119	11 Inter-PLMN GTP communication over the Gp Interface	......................................................................10
9f1d172320d152e366512ff4afa2ff1b	129 119	12 IP, the networking technology used by GTP	.........................................................................................10
9f1d172320d152e366512ff4afa2ff1b	129 119	13 GTP parameters	.....................................................................................................................................10 Annex A (informative): Change history...............................................................................................11 ETSI 4 3G TS 29.119 version 3.0.0 Release 1999 ETSI TS 129 119 V3.0.0 (2000-03) Foreword The present document has been produced by the 3rd Generation Partnership Project (3GPP). The present document specifies the signalling requirements and procedures used at network elements related to the Gateway Location Register (GLR) for GPRS Tunnelling Protocol (GTP) within the 3GPP system. (i.e. the present document specifies the delta against 3G TS 29.060). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI 5 3G TS 29.119 version 3.0.0 Release 1999 ETSI TS 129 119 V3.0.0 (2000-03) 1 Scope The present document describes the signalling requirements and procedures used at network elements related to the GLR for GTP within the 3GPP system at the application level. The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3G TS 29.060. 1.1 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. [1] 3G TS 23.060: "General Packet Radio Service (GPRS); Service description Stage2". [2] 3G TS 23.119: "Gateway Location Register (GLR) – stage2". [3] 3G TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols – Stage 3". [4] 3G TS 29.002: "Mobile Application Part (MAP) specification". [5] 3G TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". 2 Definitions and abbreviations 2.1 Definitions For the purposes of the present document, the following terms and definitions apply. Gateway Location Register: this entity handles location management of roaming subscriber in visited network without involving HLR Intermediate GSN: this entity is used as serving GSN towards home network and relay some PDU notification messages between serving GSN and Gateway GSN MM context: information sets held in MS and GSNs for a GPRS subscriber related to mobility management (MM) MM Context ID: IMSI or equivalent for use in conjunction with Anonymous Access (please refer to section GTP Header) Path: UDP/IP path and TCP/IP path are examples of paths that may be used to multiplex GTP tunnels Path Protocol: path Protocol is the protocol(s) used as a bearer of GTP between GSNs PDP: packet Data Protocol (PDP) is a network protocol used by an external packet data network interfacing to GPRS PDP Context: information sets held in MS and GSNs for a PDP address Signalling message: GTP signalling messages are exchanged between GSN pairs in a path. The signalling messages are used to transfer GSN capability information between GSN pairs and to create, update and delete GTP tunnels ETSI 6 3G TS 29.119 version 3.0.0 Release 1999 ETSI TS 129 119 V3.0.0 (2000-03) T-PDU: original packet, for example an IP datagram, from an MS or a network node in an external packet data network. A T-PDU is the payload that is tunnelled in the GTP tunnel Tunnel Endpoint Identifier (TEID): this field unambiguously identifies a tunnel endpoint in the receiving GTP-U or GTP-C protocol entity. The receiving end side of a GTP tunnel locally assigns the TEID value the transmitting side has to use. The TEID values are exchanged between tunnel endpoints using GTP-C messages 2.2 Abbreviations For the purposes of the present document, the following abbreviations apply: GGSN Gateway GPRS support node GLR Gateway Location Register GPRS General Packet Radio Service GTP GPRS Tunnelling Protocol IM_GSN Intermediate GSN IP Internet Protocol GLR Gateway Location Register SGSN Serving GPRS support node TEID Tunnel Endpoint IDentifier UDP User Datagram Protocol 3 General The present document defines the GPRS Tunnelling Protocol (GTP) specific to the network with the GLR, i.e. the protocol between IM_GSN and other nodes (i.e. GGSN, SGSN and GTP-MAP protocol converting GSN). It includes only the GTP signalling but not data transfer procedures. The interface between IM_GSM and GGSN is either intra-PLMN interface or inter-PLMN interface. SGSN GGSN IM_GSN GTP-MAP Protocol Converting GSN HLR Signalling Interface Signalling and Data Transfer Interface GLR GTP-MAP Protocol Converting GSN Figure 1: Logical Architecture for PS domain in the network with GLR The GTP protocol is implemented only by IM_GSNs, SGSNs and GGSNs. No other systems need to be aware of GTP. GPRS MSs are connected to a SGSN without being aware of GTP. ETSI 7 3G TS 29.119 version 3.0.0 Release 1999 ETSI TS 129 119 V3.0.0 (2000-03) It is assumed that there will be a many-to-many relationship between IM_GSNs, SGSNs and GGSNs. An IM_GSN may provide service to many GGSNs. A SGSN may provide service to many IM_GSNs and GGSNs. 4 Transmission order and bit definitions Transmission order and bit definitions on the interface between the IM_GSN and other nodes in the network with GLR are the same as that used in the network without the GLR, see 3G TS 29.060. 5 GTP header The GTP header used on interface between the IM_GSN and other nodes in the network with GLR is the same as that used in the network without the GLR, see 3G TS 29.060. 6 GTP Message and Message Formats The only signalling plane exists between the IM_GSN and other nodes (i.e. GGSN, SGSN and GTP-MAP protocol converting GSN). 6.1 Signalling Message Formats GTP defines a set of signalling messages between two associated GSNs. The signalling messages to be used between the IM_GSN and other nodes are defined in the table below. For the GTP signalling messages to be used on other interfaces see 3G TS 29.060. Table 1: Signalling messages Message Type value (Decimal) Signalling message Reference 3 Version Not Supported 7.4.3 in 3G TS 29.060 27 PDU Notification Request 7.5.12 in 3G TS 29.060 28 PDU Notification Response 7.5.13 in 3G TS 29.060 29 PDU Notification Reject Request 7.5.14 in 3G TS 29.060 30 PDU Notification Reject Response 7.5.15 in 3G TS 29.060 32 Send Routeing Information for GPRS Request 7.6.1 in 3G TS 29.060 33 Send Routeing Information for GPRS Response 7.6.2 in 3G TS 29.060 34 Failure Report Request 7.6.3 in 3G TS 29.060 35 Failure Report Response 7.6.4 in 3G TS 29.060 6.2 Path Management messages The messages, which are listed in following table, are used on the interface between the IM_GSN and other nodes. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3G TS 29.060. Messages Sending node Receiving node IM_GSN GGSN, SGSN Version Not Supported GGSN, SGSN IM_GSN ETSI 8 3G TS 29.119 version 3.0.0 Release 1999 ETSI TS 129 119 V3.0.0 (2000-03) 6.3 Tunnel Management messages In following table, only the messages used between the IM_GSN and GGSN and between the IM_GSN and SGSN are listed. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3G TS 29.060. Messages Sending node Receiving node GGSN IM_GSN PDU Notification Request IM_GSN SGSN SGSN IM_GSN PDU Notification Response IM_GSN GGSN SGSN IM_GSN PDU Notification Reject Request IM_GSN GGSN GGSN IM_GSN PDU Notification Reject Response IM_GSN SGSN 6.4 Location Management message In the network with the GLR, The optional Location Management messages are defined to support the case when Network-Requested PDP Context Activation procedures are used and an IM_GSN does not have a SS7 MAP interface. GTP is then used to transfer signalling messages between the IM_GSN and a GTP-MAP protocol-converting GSN in the GPRS backbone network. The GTP-MAP protocol-converting GSN converts the signalling messages described in this section between GTP and MAP. The MAP messages are sent to and received from the GLR. The GTP-MAP protocol-converting function is described in 3G TS 23.060. The MAP protocol describing the corresponding procedures and messages is described in 3G TS 29.002. This alternative method is illustrated in Figure 2. L2 L1 MTP2 MTP3 IP L1 SCCP UDP TCAP MAP GTP-MAP Interworking GTP GSN IM_GSN L1 MTP2 MTP3 SCCP TCAP MAP L1 L2 IP UDP GTP GLR Figure 2: IM_GSN - GLR Signalling via a GTP-MAP protocol-converter in a GSN ETSI 9 3G TS 29.119 version 3.0.0 Release 1999 ETSI TS 129 119 V3.0.0 (2000-03) In following table, only the messages used between the IM_GSN and The GTP-MAP protocol-converting GSN are listed. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3G TS 29.060. Messages Sending node Receiving node Send Routeing Information for GPRS Request IM_GSN GTP-MAP protocol- converting Send Routeing Information for GPRS Response GTP-MAP protocol-converting IM_GSN Failure Report Request IM_GSN GTP-MAP protocol- converting Failure Report Response GTP-MAP protocol-converting IM_GSN 6.5 Mobility Management messages The messages belonging to the mobility management messages are not used on the interface between the IM_GSN and other nodes in the network with the GLR. 6.6 Reliable delivery of signalling messages For the Reliability mechanism in the IM_GSN, see section 7.8 in 3G TS 29.060. 6.7 Information element The format of information elements in the message used on the interface between the IM_GSN and other nodes in the network with GLR is the same as that in the network without the GLR. See 3G TS 29.060. 7 Signalling Plane (GTP-C) The definition of signalling plane used in the network with the GLR is the same as that used in the network without the GLR, see in 3G TS 29.060. 8 GTP-U GTP-U is not used on the interface between the IM_GSN and other nodes. For the definition of GTP-U on the other interfaces, see in 3G TS 29.060. 9 Path Protocol The Path Protocol on the interface between the IM_GSN and other nodes in the network with the GLR is the same as that used in the network without the GLR. See 3G TS 29.060. 10 Error handling The error handling on the interface between the IM_GSN and other nodes is the same as that in the network without the GLR. See 3G TS 29.060. One exception is that the IM_GSN doesn’t have a Restart Counter because the IM_GSM stores no PDP and MM context and therefore the synchronisation of the status of these with other GSNs is not needed. ETSI 10 3G TS 29.119 version 3.0.0 Release 1999 ETSI TS 129 119 V3.0.0 (2000-03) 11 Inter-PLMN GTP communication over the Gp Interface Refer to the corresponding section in 3G TS 29.060. 12 IP, the networking technology used by GTP Refer to the corresponding section in 3G TS 29.060. The definitions and directions for use of the parameters in GTP (inc. timer values or counter values and so on) on the interface between the IM_GSN and other nodes is the same as that used in the network without the GLR. See 3G TS 29.060. ETSI 11 3G TS 29.119 version 3.0.0 Release 1999 ETSI TS 129 119 V3.0.0 (2000-03) Annex A (informative): Change history Document history V0.0.1 Oct 1999 The GTP protocol part is separated from MAP protocol part, and new specification related to GTP issue is generated. V0.1.0 Nov 1999 For approval by N2#8 V1.0.0 Dec 1999 For information and approval by TSG CN#6. V1.0.1 Jan 2000 Only editorial modifications including some alignment with 29.060 V2.0.0 Mar 2000 Submitted for approval to TSG CN#07 V3.0.0 Mar 2000 Approved by TSG CN#07 12 ETSI ETSI TS 129 119 V3.0.0 (2000-03) 3G TS 29.119 version 3.0.0 Release 1999 History Document history V3.0.0 March 2000 Publication
32dca953c19f1349b85cfc45d684f611	129 011	1 Scope	........................................................................................................................................................6
32dca953c19f1349b85cfc45d684f611	129 011	1.1 Normative references	......................................................................................................................................... 7
32dca953c19f1349b85cfc45d684f611	129 011	1.2 Definitions and abbreviations	............................................................................................................................ 8
32dca953c19f1349b85cfc45d684f611	129 011	2 Introduction	..............................................................................................................................................8 2.1 MSC/VLR procedures for handling supplementary service signalling received over the A-interface .............. 8 2.2 MSC/VLR procedures for handling supplementary service signalling received over the D-interface .............. 9
32dca953c19f1349b85cfc45d684f611	129 011	3 SS version negotiation	.............................................................................................................................9
32dca953c19f1349b85cfc45d684f611	129 011	3.1 Call related supplementary services interworking	............................................................................................. 9
32dca953c19f1349b85cfc45d684f611	129 011	3.2 Call independent supplementary services interworking	..................................................................................... 9
32dca953c19f1349b85cfc45d684f611	129 011	4 Mapping between TC transaction sublayer messages and layer 3 radio path messages	........................10
32dca953c19f1349b85cfc45d684f611	129 011	4.1 D-interface to A-interface mapping	................................................................................................................. 10
32dca953c19f1349b85cfc45d684f611	129 011	4.2 A-interface to D-interface mapping	................................................................................................................. 10
32dca953c19f1349b85cfc45d684f611	129 011	4.3 Procedures	....................................................................................................................................................... 10
32dca953c19f1349b85cfc45d684f611	129 011	5 Call related supplementary services management	.................................................................................11
32dca953c19f1349b85cfc45d684f611	129 011	5.1 SS management in connection establishment phase	........................................................................................ 11
32dca953c19f1349b85cfc45d684f611	129 011	5.1.1 Line Identification services	........................................................................................................................ 11
32dca953c19f1349b85cfc45d684f611	129 011	5.1.1.1 Calling Line Identification Presentation (CLIP)	................................................................................... 11
32dca953c19f1349b85cfc45d684f611	129 011	5.1.1.2 Calling Line Identification Restriction (CLIR)	.................................................................................... 12
32dca953c19f1349b85cfc45d684f611	129 011	5.1.1.3 Connected Line Identification Presentation (COLP)	............................................................................ 12
32dca953c19f1349b85cfc45d684f611	129 011	5.1.1.4 Connected Line Identification Restriction (COLR)	.............................................................................. 12
32dca953c19f1349b85cfc45d684f611	129 011	5.1.2 Call Forwarding services	............................................................................................................................ 13
32dca953c19f1349b85cfc45d684f611	129 011	5.1.2.1 Notification to served mobile subscriber	.............................................................................................. 13
32dca953c19f1349b85cfc45d684f611	129 011	5.1.3 Call Waiting service (CW)	......................................................................................................................... 13
32dca953c19f1349b85cfc45d684f611	129 011	5.1.3.1 Offering a waiting call	.......................................................................................................................... 13
32dca953c19f1349b85cfc45d684f611	129 011	5.1.3.2 Notification of waiting call to calling subscriber	.................................................................................. 13
32dca953c19f1349b85cfc45d684f611	129 011	5.1.4 Closed User Group service (CUG)	............................................................................................................. 14
32dca953c19f1349b85cfc45d684f611	129 011	5.1.4.1 Explicit invocation of a CUG call	........................................................................................................ 14
32dca953c19f1349b85cfc45d684f611	129 011	5.1.4.2 Notification of CUG invocation to served MS	..................................................................................... 14
32dca953c19f1349b85cfc45d684f611	129 011	5.1.4.3 Notification of rejection of CUG invocation to served MS	.................................................................. 14
32dca953c19f1349b85cfc45d684f611	129 011	5.1.4.4 Notification of CUG invocation to terminating MS	............................................................................. 16
32dca953c19f1349b85cfc45d684f611	129 011	5.1.5 Advice of Charge services	.......................................................................................................................... 16
32dca953c19f1349b85cfc45d684f611	129 011	5.1.5.1 Notification of Charging information to served MS, mobile originated call	........................................ 16
32dca953c19f1349b85cfc45d684f611	129 011	5.1.5.2 Notification of Charging information to served MS, mobile terminated call	....................................... 16
32dca953c19f1349b85cfc45d684f611	129 011	5.1.6 Call Barring services	.................................................................................................................................. 17
32dca953c19f1349b85cfc45d684f611	129 011	5.1.6.1 Barring of outgoing calls	...................................................................................................................... 17
32dca953c19f1349b85cfc45d684f611	129 011	5.1.6.2 Barring of incoming calls	..................................................................................................................... 17 5.1.7 CCBS call outcome................................................................................................................................... 18
32dca953c19f1349b85cfc45d684f611	129 011	5.2 SS Management in stable connection state	...................................................................................................... 18
32dca953c19f1349b85cfc45d684f611	129 011	5.2.1 Call Forwarding services	............................................................................................................................ 18
32dca953c19f1349b85cfc45d684f611	129 011	5.2.1.1 Notification of invocation of CFB to served mobile subscriber	........................................................... 18
32dca953c19f1349b85cfc45d684f611	129 011	5.2.2 Call Hold service (HOLD)	......................................................................................................................... 19
32dca953c19f1349b85cfc45d684f611	129 011	5.2.3 Multi Party service (MPTY)	...................................................................................................................... 20
32dca953c19f1349b85cfc45d684f611	129 011	5.2.4 Advice of Charge services	.......................................................................................................................... 20
32dca953c19f1349b85cfc45d684f611	129 011	5.2.5 Explicit Call Transfer service (ECT)	.......................................................................................................... 21
32dca953c19f1349b85cfc45d684f611	129 011	5.3 SS Management in disconnecting phase	.......................................................................................................... 21
32dca953c19f1349b85cfc45d684f611	129 011	5.3.1 Call Forwarding services	............................................................................................................................ 22
32dca953c19f1349b85cfc45d684f611	129 011	5.3.2 CCBS Request Activation	.......................................................................................................................... 22
32dca953c19f1349b85cfc45d684f611	129 011	5.3.3 Call Deflection service	............................................................................................................................... 23
32dca953c19f1349b85cfc45d684f611	129 011	5.3.3.1 Call Deflection Operation Request	....................................................................................................... 23
32dca953c19f1349b85cfc45d684f611	129 011	5.3.3.2 Call Deflection Operation Response	.................................................................................................... 23
32dca953c19f1349b85cfc45d684f611	129 011	6 Call independent supplementary services management	.........................................................................24
32dca953c19f1349b85cfc45d684f611	129 011	6.1 MS initiated SS Management	.......................................................................................................................... 24 (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 4 3G TS 29.011 version 3.0.0
32dca953c19f1349b85cfc45d684f611	129 011	6.1.1 Connection establishment phase	................................................................................................................ 24
32dca953c19f1349b85cfc45d684f611	129 011	6.1.2 Connection established	............................................................................................................................... 25
32dca953c19f1349b85cfc45d684f611	129 011	6.1.3 Connection release	..................................................................................................................................... 26
32dca953c19f1349b85cfc45d684f611	129 011	6.2 Network initiated SS Management	.................................................................................................................. 27
32dca953c19f1349b85cfc45d684f611	129 011	6.2.1 Connection establishment phase	................................................................................................................ 27
32dca953c19f1349b85cfc45d684f611	129 011	6.2.2 Connection established	............................................................................................................................... 27
32dca953c19f1349b85cfc45d684f611	129 011	6.2.3 Connection release	..................................................................................................................................... 27
32dca953c19f1349b85cfc45d684f611	129 011	6.2.4 ForwardCheckSSIndication	....................................................................................................................... 28
32dca953c19f1349b85cfc45d684f611	129 011	6.2.5 CCBS Recall	.............................................................................................................................................. 28
32dca953c19f1349b85cfc45d684f611	129 011	6.2.6 CCBS Monitoring	...................................................................................................................................... 29
32dca953c19f1349b85cfc45d684f611	129 011	6.3 Mapping of Operation Codes, Error Codes, Parameter Tags and Parameter Contents	.................................... 29
32dca953c19f1349b85cfc45d684f611	129 011	6.3.1 Operation codes	.......................................................................................................................................... 29
32dca953c19f1349b85cfc45d684f611	129 011	6.3.2 Error codes	................................................................................................................................................. 29
32dca953c19f1349b85cfc45d684f611	129 011	6.3.3 Parameter tags and parameter values	......................................................................................................... 30 Annex A: Change history......................................................................................................................31 History..............................................................................................................................................................32 (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 5 3G TS 29.011 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This TS provides a detailed specification for interworking between the A-interface protocol and the Mobile Application Part (MAP) for handling of supplementary services within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 6 3G TS 29.011 version 3.0.0 1 Scope The scope of this Technical Specification is to provide a detailed specification for interworking between the A interface protocol and the Mobile Application Part for handling of supplementary services. The MAP interfaces of interest are the B-, C-, D- and E-interfaces. The A-, C-, D- and E-interfaces are physical interfaces while the B-interface is an internal interface defined for modelling purposes. Information relating to the modelling interface is not normative in this specification. Supplementary service signalling may be passed by the MSC/VLR between the A- and E-interfaces after inter-MSC handover. This procedure is transparent as far as supplementary services are concerned therefore interworking concerning this process is not described in this specification. Clause 2 describes general procedures for interworking between the A- and D- physical interfaces. Clause 3 describes the general procedures for the SS version negotiation. Clause 4 describes the mapping of layer 3 radio path messages with Transaction Capabilities (TC) transaction sublayer messages for interworking between the A- and D- physical interfaces. Clause 5 describes specific interworking procedures for all interfaces relating to call related SS activity. Clause 6 describes specific interworking procedures for all interfaces relating to call independent SS activity. Clause 6 also covers the interworking between the MAP User (see GSM 09.02) and the SS handling functions of the network entities (see GSM 04.10 and GSM 04.80). Reference is made to the following Technical Specifications: - GSM 02.04 and GSM 02.8x and GSM 02.9x-series, for definition of supplementary services; - GSM 03.11, GSM 03.8x and GSM 03.9x-series, for technical realisation of supplementary services; - GSM 04.10, GSM 04.80, GSM 04.8x and GSM 04.9x-series, for radio path signalling procedures for supplementary services; - GSM 09.02 (MAP). (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 7 3G TS 29.011 version 3.0.0 1.1 Normative references The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [3] GSM 02.24: "Digital cellular telecommunications system (Phase 2+); Description of Charge Advice Information (CAI)". [4] GSM 02.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 1". [5] GSM 02.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 1". [6] GSM 02.93: "Digital cellular telecommunications system (Phase 2+); Completion of Calls to Busy Subscriber - Stage 1". [7] GSM 03.11: "Digital cellular telecommunications system (Phase 2+); Technical realization of supplementary services". [8] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 2". [9] GSM 03.93: "Digital cellular telecommunications system (Phase 2+); Completion of Calls to Busy Subscriber - Stage 2". [10] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". [11] GSM 04.10: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 Supplementary services specification General aspects". [12] GSM 04.72: "Digital cellular telecommunications system (Phase 2+); Call Deflection supplementary service - Stage 3". [13] GSM 04.80: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 supplementary services specification Formats and coding". [14] GSM 04.81: "Digital cellular telecommunications system (Phase 2+); Line identification supplementary services - Stage 3". [15] GSM 04.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF) supplementary services - Stage 3". [16] GSM 04.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". [17] GSM 04.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY) supplementary services - Stage 3". (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 8 3G TS 29.011 version 3.0.0 [18] GSM 04.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG) supplementary services - Stage 3". [19] GSM 04.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC) supplementary services - Stage 3". [20] GSM 04.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB) supplementary services - Stage 3". [21] GSM 04.90: "Digital cellular telecommunications system (Phase 2+); Unstructured supplementary services operation - Stage 3". [22] GSM 04.91: "Digital cellular telecommunications system (Phase 2+); Explicit Call Transfer (ECT) supplementary services - Stage 3". [23] GSM 04.93: "Digital cellular telecommunications system (Phase 2+); Completion of Calls to Busy Subscriber - Stage 3". [24] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". [25] GSM 09.10: "Digital cellular telecommunications system (Phase 2+); Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)". 1.2 Definitions and abbreviations Abbreviations used in this specification are listed in GSM 01.04. 2 Introduction This clause describes general procedure at the MSC/VLR for SS interworking between the A- and D-interfaces. 2.1 MSC/VLR procedures for handling supplementary service signalling received over the A-interface Upon receipt of supplementary service signalling on the A-interface, the MSC/VLR shall: - perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5); - if necessary request access to the HLR over the D-interface using the procedures defined in this specification and MAP, GSM 09.02; - use the version indicator received from the MS to set up the right AC context name towards the HLR (see clause 3). The version indicator is described in GSM 04.10 and GSM 04.80. AC names are defined in GSM 09.02; - perform mapping between layer 3 messages on the radio path and TC transaction sublayer messages as required (see clause 3). (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 9 3G TS 29.011 version 3.0.0 2.2 MSC/VLR procedures for handling supplementary service signalling received over the D-interface Upon receipt of supplementary service signalling on the D-interface, the MSC/VLR shall: - perform any internal SS checks or procedures appropriate to the signal (see clauses 4 and 5); - handle any information elements according to the screening indicator procedure as described in GSM 04.10; - perform mapping between TC transaction sublayer messages and layer 3 messages on the radio path as required (see clause 3). 3 SS version negotiation This clause describes the general procedures for the call related and call independent supplementary services version negotiation. 3.1 Call related supplementary services interworking No interworking identified. 3.2 Call independent supplementary services interworking On receipt of the REGISTER message from the MS, the MSC/VLR will include the appropriate AC name in the dialogue control portion of the BEGIN message based on the following rules: - if no version indicator is present, no AC name is included in the BEGIN message towards the HLR (no AC name indicates "version1"); - if the version indicator is less or equal to the highest AC name the MSC/VLR and HLR both support, the "dialogue" will be handled according to the AC name corresponding to the version indicator and to the SS operation received; - if the version indicator is greater than the highest commonly supported AC name within the network (MSC/VLR, HLR), the "dialogue" will be handled according to this highest AC name if the request from the MS can also be fulfilled with this version of the "dialogue". The selection of the highest commonly supported AC name by the network is described in GSM 09.02. It should be noted that unknown parameters of the extension field within the Facility Information Element shall be forwarded to a phase 2 HLR according to the Extensibility rules as defined in GSM 09.02. They may be discarded when sent to a phase 1 HLR. According to this version of the standards, the highest AC name is "version3". The description method employed in the clauses 4 to 6 is tabled showing the mapping of parameter values. The exact values of the parameters and parameter tags can be found in the referenced specifications. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 10 3G TS 29.011 version 3.0.0 4 Mapping between TC transaction sublayer messages and layer 3 radio path messages This clause describes the mapping of TC transaction sublayer messages to layer 3 radio path messages over the external interfaces. The precise coding of these messages is given in other technical specifications. 4.1 D-interface to A-interface mapping Table 4.1 shows the mapping of TC transaction sublayer messages to layer 3 messages on the radio path. Table 4.1: Mapping of TC transaction sublayer messages to layer 3 radio path messages TC transaction sublayer message Layer 3 radio path message BEGIN REGISTER (note 1) CONTINUE (note 2) FACILITY/REGISTER (note 3) END (note 2) RELEASE COMPLETE/REGISTER (note 3) ABORT (note 2) RELEASE COMPLETE NOTE 1: AC name is not mapped to a version indicator. NOTE 2: The user information field if present is discarded. NOTE 3: A CONTINUE or END is mapped to REGISTER if a new transaction has to be established. 4.2 A-interface to D-interface mapping Table 4.2 shows the mapping of layer 3 radio path messages to TC transaction sublayer messages. Table 4.2: Mapping of layer 3 radio path messages to TC transaction sublayer messages Layer 3 radio path message TC transaction sublayer message REGISTER BEGIN (note) FACILITY CONTINUE RELEASE COMPLETE END NOTE: The right AC name shall be included, see clause 3. 4.3 Procedures The mapping from TC Transaction Sublayer messages to Layer 3 radio path messages must include a replacement of the tag and length of the Component Portion in the Transaction Sublayer message with the Information element identifier and length of the Facility Information Element for the Layer 3 message. Similarly for the reverse mapping. However, if a version indicator is received an AC name will be provided in the BEGIN message, see clause 3. All transaction sublayer messages, except the ABORT message, will normally contain one or more components. If components are included, the conversion algorithm described below applies. If a message does not contain a component, then the corresponding message is also sent without a component: messages shall not be withheld by the interworking function. For call independent SS operations each message shall only contain a single component. If a message contains more than one component then a RELEASE COMPLETE message with the cause "Facility rejected" (see GSM 04.08) and without any component shall be sent on the radio path (see GSM 04.10). TC Transaction sublayer messages can also contain a dialogue portion. If a user-information is received within this dialogue portion, it will not be conveyed in a Layer 3 radio path message. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 11 3G TS 29.011 version 3.0.0 If an ABORT message is received in TC, a RELEASE COMPLETE message is to be sent on the radio path. The RELEASE COMPLETE message shall not contain any component. If a cause is to be provided to the MS, one of the cause codes of GSM 04.08 shall be used. If an ABORT message with a dialogue portion indicating "version fallback" (e.g. the cause "AC-not-supported") is received in TC then, if the MSC does not re-attempt the "dialogue" (e.g. by using a different AC name), it shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected" (see GSM 04.08) and without any component. If an END message with a dialogue portion indicating "dialogue refused" is received in TC then the MSC shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected" (see GSM 04.08) and without any component. If a layer 3 radio path message or a component in the layer 3 radio path message is rejected by the MSC, the MSC shall: - return a RELEASE COMPLETE message to the MS. If the reject condition is not associated with a component, one of the cause codes of GSM 04.08 shall be inserted, as described below. If it is a component (except a REJECT component), a REJECT component with the appropriate problem code shall be inserted in the RELEASE COMPLETE message, as described below. If the reject condition concerns a REJECT component the RELEASE COMPLETE message may be empty; - terminate the transaction with the VLR by use of an ABORT message. If a dialogue cannot be established with the HLR because no common AC name is available then the MSC shall send a RELEASE COMPLETE to the MS with the cause "Facility rejected". 5 Call related supplementary services management 5.1 SS management in connection establishment phase When a CM connection is being set up between an MS and an MSC, setting up of a connection between the MSC and the VLR to request access proceeds as for normal call set-up (see GSM 09.02). Moreover, the MSC will also assess the capabilities of the MS according to the screening indicator (see GSM 04.10 and GSM 04.80). As the call set-up proceeds, the following supplementary services may apply: 5.1.1 Line Identification services These supplementary services (described in GSM 04.81) require interworking in the MSC between both GSM 04.08, MAP (GSM 09.02) and the fixed network protocol, see also GSM 09.10. 5.1.1.1 Calling Line Identification Presentation (CLIP) The signalling at invocation of the CLIP supplementary service is shown in figure 5.1. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G 6(783 G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.1: Signalling for CLIP supplementary service When a call terminates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that the CLIP service is provided (and CLIR is not indicated in the incoming call set-up message from the PSTN), then the number of the calling subscriber (if received in the incoming call set-up) shall be mapped onto the Calling Party BCD number parameter in the SETUP message sent to the mobile. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.81. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 12 3G TS 29.011 version 3.0.0 5.1.1.2 Calling Line Identification Restriction (CLIR) The signalling at invocation of the CLIR supplementary service is shown in figure 5.2. MS MSC VLR HFI HFI HFI G G G G G G G G 6(783 G G6(1' ,1)250$7,21 )25 2872,1 &$// 6(783G G G GFFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G G G G G Figure 5.2: Signalling for CLIR supplementary service When a call originates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that the CLIR service is provided and if the CLIR service shall be invoked (according to the presentation mode and possible subscriber request), then this information is indicated in the initial address message sent using the fixed network protocol (if possible). If this parameter indicates that the CLIR service is not provided and the calling subscriber has attempted to invoke CLIR, then the call set-up shall be rejected as defined in GSM 04.81. 5.1.1.3 Connected Line Identification Presentation (COLP) The signalling at invocation of the COLP supplementary service is shown in figure 5.3. MS MSC VLR HFI HFI HFI G G G G G G G G 6(783 G G6(1' ,1)250$7,21 )25 2872,1 &$// 6(783G G G GFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G &211(&7 G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFG G G G G G G G G G Figure 5.3: Signalling for COLP supplementary service When a call originates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that the COLP service is provided, then if the connected line identity is made available by the terminating network (i.e. no interworking or presentation restrictions apply) then the connected number is passed to the calling mobile subscriber in the ConnectedNumber parameter in the CONNECT message. 5.1.1.4 Connected Line Identification Restriction (COLR) The signalling at invocation of the COLR supplementary service is shown in figure 5.4. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G 6(783 G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.4: Signalling for COLR supplementary service When a call terminates at a mobile subscriber, the MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that the COLR service is provided, then this information is sent to the originating network using the fixed network protocol (if possible). (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 13 3G TS 29.011 version 3.0.0 5.1.2 Call Forwarding services 5.1.2.1 Notification to served mobile subscriber As described in GSM 02.82, when a subscriber has any (set of) Call Forwarding service(s) active, a notification of this fact is sent to the MS at mobile originated call set-up from the served mobile subscriber. The signalling for this notification is shown in figure 5.5. MS MSC VLR HFI HFI HFI G G 6(783 G G G G G GFFFFFFFFFF!G G6(1' ,1)250$7,21 )25 2872,1 &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G $/(57,1* G G G G G G &211(&7 G G &203/(7( &$// G G G G )$&,/,7< G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.5: Signalling for notification of invocation of Call Forwarding supplementary service The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that a call forwarding service is active, then any of the ALERTING, CONNECT or FACILITY messages may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.82. 5.1.3 Call Waiting service (CW) 5.1.3.1 Offering a waiting call The signalling for this situation is shown in figure 5.6. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G 352&(66 &: G G G G 6(783 G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.6: Signalling for setting up a waiting call A waiting call is offered to a busy MS using a normal SETUP message including a "Signal" information element with value #7 (call waiting tone on), as described in GSM 04.83. This is the required MSC behaviour if it has received a MAP_PROCESS_CALL_WAITING service primitive as a response to a MAP_SEND_INFO_FOR_INCOMING_CALL service primitive on the B-interface. Exact values of the parameter and parameter tag are indicated in GSM 04.08. 5.1.3.2 Notification of waiting call to calling subscriber The signalling for this notification is shown in figure 5.7. MS MSC HFI HFI G G G G G G $/(57,1* G G G G FFFFFFFFFFFFFFFFFFFG G G G G G Figure 5.7: Signalling for notification of waiting call to calling subscriber (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 14 3G TS 29.011 version 3.0.0 If there are no network interworking limitations between the originating and destination MSCs, then the calling MS receives notification of his waiting call as follows: A Facility Information element in the ALERTING message includes a NotifySS operation with the following parameters: - SS-Code parameter indicates "callWaiting"; - CallIsWaitingIndicator parameter indicates "callIsWaiting". Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.83. 5.1.4 Closed User Group service (CUG) 5.1.4.1 Explicit invocation of a CUG call The signalling for this situation is shown in figure 5.8. MS MSC VLR HFI HFI HFI G G G G G G G G 6(783 G G6(1' ,1)250$7,21 )25 2872,1 &$// 6(783G G G GFFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 5.8: Signalling at explicit invocation of a CUG call When a subscriber to the CUG supplementary service sets up a call, an explicit invocation involves transport of a ForwardCUG-Info operation in a Facility information element in the SETUP message. Parameter mapping between the air-interface SETUP message and the B-interface MAP_SEND_INFO_FOR_OUTGOING_CALL service primitive shall take place in the MSC. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. The parameter tags and values are mapped as follows: Table 5.1: Mapping of parameter names and values for explicit invocation of a CUG call GSM 04.80 parameter name GSM 09.02 parameter name cug-Index cug-Index suppressPrefCUG suppressPrefCUG suppressOA suppressOutgoingAccess 5.1.4.2 Notification of CUG invocation to served MS The signalling for this situation is shown in figure 5.9. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G&$// 352&((',1G G &203/(7( &$// G G G G )$&,/,7< G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.9: Signalling flow for notification of CUG invocation to served MS The network may indicate to the MS that a CUG has been invoked for the outgoing call by sending a NotifySS operation in the Facility information element in the FACILITY or CALL PROCEEDING message towards MSa. The parameter to be included in this operation (cug-Index) is obtained from the MAP_COMPLETE_CALL service primitive. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. 5.1.4.3 Notification of rejection of CUG invocation to served MS The signalling for this situation is shown in figure 5.10. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 15 3G TS 29.011 version 3.0.0 MS MSC VLR HFI HFI HFI G G 6(783 G G 6(1' ,1)250$7,21 )25 2872,1* &$// 6(783 G G G GFFFFFFFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G6(1' ,1)250$7,21 )25 2872,1 &$// 6(783 (5525G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G ',6&211(&7 G G G G G G 5(/($6( G G G G G G5(/($6( &203/(7(G G G G G G FFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.10: Signalling flow for notification of rejection of CUG invocation to served MS When an attempted CUG call is rejected for CUG related reasons, mapping of parameter values take places in order to inform the MSa of the failure in the DISCONNECT, RELEASE or RELEASE COMPLETE message. If the call is rejected by the serving VLR, a mapping of errors received on the B-interface (as response to MAP_SEND_INFO_FOR_OUTGOING_CALL) to diagnostics (in the diagnostics field of the Facility Rejected cause value) must be performed. The mapping from error code to diagnostic is as follows (detailed values of tags, cause values and diagnostics are found in GSM 09.02, GSM 04.08, and GSM 04.80 respectively): Table 5.2: Mapping of GSM 09.02 error causes to diagnostics at notification of rejection of CUG invocation to served MS GSM 09.02 error cause Facility rejected #29 diagnostic field outgoingCallsBarredWithinCUG Outgoing calls barred within the CUG noCUG-Selected No CUG selected unknownCUG-Index Unknown CUG index indexIncompatibleWith RequestedBasicService Index incompatible with requested basic service If there are no network interworking restrictions (i.e. originating MSC = gateway MSC = terminating MSC), interworking between MAP and the air-interface takes place also for rejection of CUG calls by terminating end. The signalling for this situation is shown in figure 5.11. MSa MSC HLR HFI HFI HFI G G G G G G G G G G 6(1'B5287,1B,1)2 G G G G G G6(1'B5287,1B,1)2B606G G G G G G IRU 06E G G G G G GFFFFFFFFFFFFFFFFFFFF!G G G G ',6&211(&7 G G G G G G 5(/($6( G G G G G G5(/($6( &203/(7(G G 6(1'B5287,1B,1)2 G G G G FFFFFFFFFFFFFFFG G FFFFFFFFFFFFFFFFFFFFG G G G G G G G Figure 5.11: Signalling flow for notification of rejection of CUG invocation from terminating end The mapping from error code to diagnostic is as follows (detailed values of tags, cause values and diagnostics are found in GSM 09.02, GSM 04.08, and GSM 04.80 respectively): Table 5.3: Mapping of GSM 09.02 error causes to cause values at notification of rejection by terminating end GSM 09.02 error cause Cause information element (cause value) calledPartySSInteractionViolation Facility Rejected #29, Diagnostic = CUG call failure, unspecified incomingCallsBarredWithinCUG Incoming calls barred within the CUG #55 subscriberNotMemberOfCUG User not a member of CUG #87 (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 16 3G TS 29.011 version 3.0.0 requestedBasicServiceViolatesCUG-Constraints Facility Rejected #29 5.1.4.4 Notification of CUG invocation to terminating MS The signalling for this situation is shown in figure 5.12. MS MSC VLR HFI HFI HFI G G G G G G G G G G 6(1' ,1)250$7,21 )25 ,1&20,1 &$// 6(783 G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// 352&(66 &$// :$,7,1* G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G 6(783 G G G G G G FFFFFFG G G G G G G G G G Figure 5.12: Signalling flow for notification of CUG invocation to terminating end When a CUG call arrives at the terminating end, the CUG index associated with the invoked CUG may be passed to the mobile station. The cug-Index parameter is obtained from the fixed network connection establishment request message, or if no fixed network protocol is involved (i.e. originating = terminating MSC), it is obtained from the MAP_COMPLETE_CALL or MAP_PROCESS_CALL_WAITING service primitive. Its value is mapped onto the cug- Index parameter in the NotifySS operation in the Facility Information element of the SETUP message on the air- interface. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. 5.1.5 Advice of Charge services 5.1.5.1 Notification of Charging information to served MS, mobile originated call The signalling for this situation is shown in figure 5.13. MSa MSC VLR HFI HFI HFI G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFG G G G &211(&7 G G G G G G )$&,/,7< G G G G G G FFFFFFFFFG G G G G G G G G G Figure 5.13: Signalling flow for notification of Mobile originated Charging Information to served MS The network may indicate charging information to the MS at mobile originated call set-up. The MSC knows charging information is applicable due to the inclusion of an SS-Code indicating Advice Of Charge Charging or Advice Of Charge Information in the MAP_COMPLETE_CALL service indication from the VLR. This parameter's value is mapped onto the SS-Code parameter in the ForwardChargeAdvice operation which is to be sent to the MS together with the relevant charging parameters. The ForwardChargeAdvice operation shall be sent in the facility information element of either the CONNECT or the FACILITY message. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. 5.1.5.2 Notification of Charging information to served MS, mobile terminated call The signalling for this situation is shown in figure 5.14. MSb MSC VLR HFI HFI HFI G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFG G G G )$&,/,7< G G G G G G FFFFFFFFFG G G G G G G G G G Figure 5.14: Signalling flow for notification of Mobile terminated Charging Information to served MS (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 17 3G TS 29.011 version 3.0.0 The network may indicate charging information to the MS at mobile terminated call set-up. The MSC knows charging information is applicable due to the inclusion of an SS-Code indicating Advice Of Charge Charging or Advice of Charge Information in the SS-Data parameter included in the MAP_COMPLETE_CALL service indication from the VLR. This parameter's value is mapped onto the SS-Code parameter in the ForwardChargeAdvice operation which is to be sent to the MS together with the relevant charging parameters. The ForwardChargeAdvice operation shall be sent in the facility information element of the FACILITY message. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. 5.1.6 Call Barring services These supplementary services (described in GSM 04.88) require the following interworking in the MSC: 5.1.6.1 Barring of outgoing calls The signalling for this situation is shown in figure 5.15. MS MSC VLR HFI HFI HFI G G G G 6(1' ,1)250$7,21 )25 2872,1 &$// 6(783 G G G G G G 6(1' ,1)250$7,21 )25 02%,/( 25,,1$7(' 606 G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G 6(1' ,1)250$7,21 )25 2872,1* &$// 6(783 (5525G G G G G G6(1' ,1)250$7,21 )25 02%,/( 25,,1$7(' 606 (5525G G G G 5(/($6( G G (5525 G G G G &203/(7( G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFG G G G G G G G G G Figure 5.15: Signalling flow for barring of an outgoing call If the error code "CallBarred" is received as a response to the MAP_SEND_INFO_FOR_OUTGOING_CALL or MAP_SEND_INFO_FOR_MO_SMS service primitives on the B-interface, then a RELEASE COMPLETE message with a NotifySS operation shall be sent to the originating MS, as described in GSM 04.88. The mapping of GSM 09.02 callBarringCause to GSM 04.08 cause values is shown in table 5.4. Exact values of the parameter and parameter tags are indicated in GSM 04.80, GSM 04.88 and GSM 04.08. Table 5.4: Mapping of GSM 09.02 callBarringCause to GSM 04.08 cause values at barring of outgoing call GSM 09.02 callBarringCause GSM 04.08 Cause value barringServiceActive #31: Normal Unspecified operatorBarring #8: Operator Determined Barring (None) #21: Call Rejected 5.1.6.2 Barring of incoming calls The signalling for this situation is shown in figure 5.16. MSa GMSC HLRb HFI HFI HFI G G G G 6(1'B5287,1B,1)2 G G G G G G6(1'B5287,1B,1)2B606G G G G G G IRU 06E G G G G G GFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G ',6&211(&7 G G 6(1'B5287,1B,1)2 G G G G 5(/($6( G G (5525 G G G G 5(/($6( &203/(7( G G FFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.16: Signalling flow for barring of an incoming call (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 18 3G TS 29.011 version 3.0.0 If the error code "CallBarred" is received as a response to the MAP_SEND_ROUTING_INFO or MAP_SEND_ROUTING_INFO_FOR_SM service primitives on the D-interface, then if no network interworking limitations apply, a NotifySS operation shall be sent to the originating MS in the first clearing message, as described in GSM 04.88. The mapping of GSM 09.02 error causes to GSM 04.08 cause values is shown in table 5.5. Exact values of the parameter and parameter tags are indicated in GSM 04.80, GSM 04.88 and GSM 04.08. Table 5.5: Mapping of GSM 09.02 error causes to cause values at barring of incoming call GSM 09.02 error cause Cause value barringServiceActive #21: Call Rejected operatorBarring #21: Call Rejected (None) #21: Call Rejected 5.1.7 CCBS call outcome For the purpose of monitoring the destination B (the target of a CCBS request activated by subscriber A), the HLR on the B-side needs to know the outcome of a CCBS call. A CCBS call is a call being set-up after acceptation of a recall (indication to subscriber A that B is idle). Thus, in case of a CCBS call, on receipt of call related messages from the MS, the MSC shall send (via the VLR) the MAP_STATUS_REPORT to the HLR. MS MSC VLR HLR HFI HFI HFI HFI G G 6(783 G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G G G &211(&7 G G G G G G G G $/(57,1* G G G G G G G G ',6&211(&7 G G G G G G G G 5(/($6( G G G G G G G G 5(/($6( G G G G G G G G &203/(7( G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G&&%6 &$// '(/,9(5<G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G 67$786B5(3257 G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G Figure 5.16a: Signalling for CCBS call outcome The CONNECT or ALERTING messages imply that the call establishment has been successful. Then the value of the Outcome information element in the MAP_STATUS_REPORT is set to success. The DISCONNECT and RELEASE are, in this case, error messages and can contain different causes (e.g. Call Rejected or User Busy). The MSC translates the message and/or the cause received into the proper value for the Outcome information element (Failure or Busy). Exact coding and values of the messages and parameter tags can be found in GSM 04.08 and GSM 09.02. 5.2 SS Management in stable connection state When a stable CM connection is set up between a mobile station and the network, the following supplementary services may apply: 5.2.1 Call Forwarding services 5.2.1.1 Notification of invocation of CFB to served mobile subscriber As described in GSM 02.82, when the Call Forwarding on MS Busy service is invoked by the network, a notification of this fact may be sent to the MS. The signalling for the situation when the user is NDUB is shown in figure 5.17. Note that if the subscriber is not NDUB, this notification does not apply. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 19 3G TS 29.011 version 3.0.0 MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G 1'8% G G G G HVWDEOLVKHG G G G G G G G G G G )$&,/,7< G G G G G G FFFFFFFFFFG G G G G G G G G G Figure 5.17: Signalling for notification of invocation of CFB supplementary service The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that CFB is active, then the FACILITY message may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.82. 5.2.2 Call Hold service (HOLD) As described in GSM 04.83, an MS can at any time during the active phase of a call signal invocation of the Call Hold supplementary service towards the network. This is done by use of the HOLD message (defined in GSM 04.80). When the MSC receives such a message, it requests access to the VLR and sends the MAP_INVOKE_SS service primitive to the VLR (as described in GSM 09.02). The interworking function triggers this behaviour by sending an internal MAP_INVOKE_SS signal to the MAP Service User of the MSC, indicating the following parameter values: - SS-Code = Call Hold; - BS-Code = Basic service of the on-going call. The signalling for this situation is shown in figure 5.18. Exact values of the parameter and parameter tags are indicated in GSM 04.80, GSM 04.83 and GSM 09.02. MS MSC VLR HFI HFI HFI G G G G G G G G +2/' G G ,192.(66 G G G GFFFFFFFFFF!G GFFFFFFFFFFFFF!G G G G G G G G G G G G ,192.(66 $&. G G G G +2/' $&. G G FFFFFFFFFFFFFG G G G +2/' 5(- G G G G G G FFFFFFFFFFG G G G G G G G G G Figure 5.18: Signalling flow at invocation of Call Hold supplementary service If the A_INVOKE_SS signal from the MAP Service User in the MSC is empty, the HOLD ACKNOWLEDGE message is returned to the MS. If it refers to an error, the mapping of error causes takes place according to table 5.6. Exact values of the parameter tags are indicated in GSM 04.80 and GSM 09.02. Table 5.6: Mapping of GSM 09.02 operation errors to GSM 04.80 HOLD REJECT causes GSM 09.02 operation error GSM 04.80 HOLD REJECT cause SystemFailure #63: Service/Option not available DataMissing #100: Invalid Information Element contents UnexpectedDataValue #100: Invalid Info. element contents CallBarred #29: Facility Rejected IllegalSS-Operation #50: Requested Facility not subscribed SS-ErrorStatus #50: Requested facility not subscribed SS-NotAvailable #69: Requested facility not implemented Note that Call Retrieval requires no communication on the B-interface, and thus no interworking requirements have been identified. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 20 3G TS 29.011 version 3.0.0 5.2.3 Multi Party service (MPTY) As described in GSM 04.84, an MS can at any time during the active phase of a call signal invocation of the Multi Party supplementary service towards the network. This is done by including a BuildMPTY operation (defined in GSM 04.80) in a FACILITY message. When the MSC receives such a request, it requests access to the VLR and sends the MAP_INVOKE_SS service primitive to the VLR (as described in GSM 09.02). The interworking function triggers this behaviour by sending an internal MAP_INVOKE_SS signal to the MAP Service User of the MSC, indicating the following parameter values: - SS-Code = MPTY; - BS-Code = Basic Service Code of the on-going calls. Note that the MSC does not allow the MPTY to be invoked if the two calls are not telephony calls. The signalling for this situation is shown in figure 5.19. MS MSC VLR HFI HFI HFI G G G G G G G G EXLOG037< G G ,192.(66 G G G GFFFFFFFFFF!G GFFFFFFFFFFFFF!G G G G G G G G G G G G ,192.(66 $&. G G G G EXLOG037< G G FFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.19: Signalling flow at invocation of Multi Party supplementary service If the A_INVOKE_SS signal from the MAP Service User in the MSC is empty, the BuildMPTY return result is returned to the MS in a FACILITY message. If it refers to an error, the mapping of errors takes place according to table 5.7. Table 5.7: Mapping of GSM 09.02 operation errors to GSM 04.80 BuildMPTY errors GSM 09.02 operation error GSM 04.80 BuildMPTY error SystemFailure SystemFailure DataMissing SystemFailure UnexpectedDataValue SystemFailure CallBarred IllegalSS-Operation IllegalSS-Operation IllegalSS-Operation SS-ErrorStatus SS-ErrorStatus SS-NotAvailable SS-NotAvailable Note that Holding, Retrieving and Splitting a multi party requires no communication on the B-interface, and thus no interworking requirements have been identified. 5.2.4 Advice of Charge services Notification of Charging information to served MS during the call The network may indicate revised charging parameters (as required according to GSM 02.24, GSM 02.86, GSM 03.86 and GSM 04.86) to the MS during a call. The parameters are forwarded to MSa using the ForwardChargeAdvice operation in the facility information element of the FACILITY message. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.85. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 21 3G TS 29.011 version 3.0.0 5.2.5 Explicit Call Transfer service (ECT) As described in GSM 04.91, an MS can at any time during the active phase of a call signal invocation of the Explicit Call Transfer supplementary service towards the network. This is done by including a ExplicitCT operation (defined in GSM 04.80) in a FACILITY message. When the MSC receives such a request, it requests access to the VLR and sends the MAP_INVOKE_SS service primitive to the VLR (as described in GSM 09.02). The interworking function triggers this behaviour by sending an internal MAP_INVOKE_SS signal to the MAP Service User of the MSC, indicating the following parameter values: - SS-Code = ect; - BS-Code = Basic Service Code of the on-going calls. Note that the MSC does not allow the ECT to be invoked if the two calls are not telephony calls. The signalling for this situation is shown in the following figure 5.21. MS MSC VLR HFI HFI HFI G G G G G G G G H[SOLFLW&7G G ,192.(66 G G G GFFFFFFFFFF!G GFFFFFFFFFFFFF!G G G G G G G G G G G G ,192.(66 $&. G G G G H[SOLFLW&7G G FFFFFFFFFFFFFG G G G FFFFFFFFFFG G G G G G G G G G Figure 5.21: Signalling flow at invocation of Explicit Call Transfer supplementary service If the A_INVOKE_SS signal from the MAP Service User in the MSC is empty, the ExplicitCT return result is returned to the MS in a DISCONNECT/RELEASE/RELEASE COMPLETE message. If it refers to an error, the mapping of errors takes place according to table 5.8. Table 5.7: Mapping of GSM 09.02 operation errors to GSM 04.80 ExplicitCT errors GSM 09.02 operation error GSM 04.80 ExplicitCT error SystemFailure SystemFailure DataMissing SystemFailure UnexpectedDataValue SystemFailure CallBarred CallBarred IllegalSS-Operation IllegalSS-Operation SS-ErrorStatus SS-ErrorStatus SS-NotAvailable SS-NotAvailable 5.3 SS Management in disconnecting phase When a CM connection is being released, the following supplementary services may apply: (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 22 3G TS 29.011 version 3.0.0 5.3.1 Call Forwarding services Notification of invocation of CFNRy to served mobile subscriber As described in GSM 02.82, when the Call Forwarding on No Reply service is invoked by the network, a notification of this fact may be sent to the MS as the call attempt is disconnected. The signalling for this situation is shown in figure 5.20. MS MSC VLR HFI HFI HFI G G G G G G G G G G6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G &203/(7( &$// G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G 6(783 G G G G G G FFFFFFFFFFFFFFFG G G G G G G G G G G G 15&7 G G G G 7LPHRXW G G G G G G G G G G )$&,/,7< G G G G G G ',6&211(&7 G G G G G G 5(/($6( G G G G G G5(/($6( &203/(7(G G G G G G FFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.20: Signalling for notification of invocation of CFNRy supplementary service The MSC obtains information on what supplementary services are active by analysing the SS-Data parameter in the MAP_COMPLETE_CALL service primitive on the B-interface. If this parameter indicates that CFNRy is active, then if required, either one of the DISCONNECT, RELEASE, RELEASE COMPLETE or FACILITY messages may be used to convey the required NotifySS operation in a Facility information element. Exact values of the parameter and parameter tags are indicated in GSM 04.80 and GSM 04.82. 5.3.2 CCBS Request Activation As described in GSM 02.93, when subscriber A encounters a busy destination B, subscriber A can request the CCBS supplementary service (i.e. activate a CCBS request against destination B). The signalling for this situation is shown in figure 5.21. MS MSC VLR HLR HFI HFI HFI HFI G G ',6&211(&7 G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G G G 5(/($6( G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G &&%6 5(48(67 G G G G G G G GFFFFFFFFFFFFFFFFF!G G 5(,67(5B&& (175<G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G G G G G 5(,67(5B&& G G G G G G G G (175<B$&. G G G G G G G G 5(,67(5B&& G G G G G G G G (175<B(5525 G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G&&%6 5(48(67 (5525G G G G G G G G &&%6 5(48(67 $&. G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G 5(/($6( &203/(7( G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G Figure 5.21: Signalling for CCBS Request Activation (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 23 3G TS 29.011 version 3.0.0 The MS request the activation of CCBS in a Facility information element of a RELEASE message in response to a DISCONNECT message containing the diagnostic CCBS is possible and the Allowed Actions information element set to Recall is possible. Then, the MSC transmits the request in an Invoke component together with the call information towards the VLR in a CCBS_REQUEST message on the B-interface. The VLR forwards it in a MAP_REGISTER_CC_ENTRY on the D-interface. The outcome of the activation is sent back by the HLR in a MAP_REGISTER_CC_ENTRY_ACK or a MAP_REGISTER_CC_ENTRY_ERROR message. This outcome is subsequently mapped and inserted in the Facility information element of the RELEASE COMPLETE message from the MSC to the MS. Exact values of the parameters and parameter tags are indicated in GSM 04.08, GSM 04.80, GSM 04.93 and GSM 09.02. 5.3.3 Call Deflection service 5.3.3.1 Call Deflection Operation Request As described in GSM 04.72, a MS may signal invocation of the Call Deflection supplementary service for a mobile terminated call at any time after call confirmation until the call is accepted. The signalling for this situation is shown in figure 5.22. MS MSC VLR HFI HFI HFI G G G G G G G G ',6&211(&7 G G &203/(7( &$// (5525 352&(66 &$// :$,7,1 (5525 G G G GFFFFFFFFFFF!G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G G G Figure 5.22: Signalling of a Call Deflection Request The MS requests Invocation of Call Deflection by including a CallDeflection operation (defined in GSM 04.80) in a DISCONNECT message. The parameters of the CallDeflection operation of the DISCONNECT message shall be transferred by the MSC to the VLR with the B-interface COMPLETE_CALL_ERROR or PROCESS_CALL_WAITING_ERROR message. 5.3.3.2 Call Deflection Operation Response Optimal Routeing of late call forwarding is not invoked The signalling for this situation is shown in figure 5.23. MS MSC VLR HFI HFI HFI G G G G G G G G G G &203/(7( &$// (5525 352&(66 &$// :$,7,1* (5525 G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G 6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783 $&. G G G G G G 6(1' ,1)250$7,21 )25 ,1&20,1* &$// 6(783 (5525 G G G G 5(/($6( G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFG G G G G G G G G G Figure 5.23: Mapping of Call Deflection Response without SOR The MSC shall send a CallDeflection return result to the MS if the SEND_INFO_FOR_INCOMING_CALL_ACK message is received from the VLR and the invocation of Optimal Routeing is not requested. The MSC shall send a CallDeflection return error to the MS if a SEND_INFORMATION_FOR_INCOMING_CALL_SETUP ERROR message is received from the VLR. The MSC shall obtain the value of the CallDeflection error from the error received in the SEND_INFORMATION_FOR_INCOMING_CALL_SETUP ERROR message. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 24 3G TS 29.011 version 3.0.0 Optimal Routeing of late call forwarding is invoked: The signalling for this situation is shown in figure 5.24. MS MSC VLR GMSC HFI HFI HFI HFI G G G G 6(1' ,1)250$7,21 G G G G G G G G )25 ,1&20,1* &$//G G G G G G G G 6(783 $&. G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G 5(680( &$// +$1'/,1* G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G G G 5(680( &$// +$1'/,1* $&. G G G G G G 5(680( &$// +$1'/,1* (5525 G G G G G G FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFG G G G 5(/($6( G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 5.24: Mapping of Call Deflection Response in case of SOR If for a Call Deflection Request Optimal Routeing of late call forwarding is invoked the MSC shall send a CallDeflection return result to the MS if the MAP_RESUME_CALL_HANDLING_ACK is received from the GMSC. If a MAP_RESUME_CALL_HANDLING_ERROR message with error "ForwardingFailed" is received from the GMSC the MSC shall send a CallDeflection return error "ForwardingFailed" to the MS. Reception of other errors than "ForwardingFailed" in the MAP_RESUME_CALL_HANDLING_ERROR message shall lead to local processing in the MSC. Exact values of the parameters and parameter tags are indicated in GSM 04.80 and GSM 09.02. 6 Call independent supplementary services management 6.1 MS initiated SS Management 6.1.1 Connection establishment phase Call independent supplementary service management takes place on a separate, dedicated CM connection between the mobile station and the MSC. When a request to open such a connection arrives at the MSC, the MSC will request access permission from the VLR, as described in GSM 09.02. It will also assess the capabilities of the MS according to the screening indicator, as described in GSM 04.10 and GSM 04.80. The signalling for this situation is shown in figure 6.1. MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G &0 VHUYLFH UHTXHVW G G G G G G &0 VHUYLFH W\SH G G G G G G 66 $FWLYDWLRQ G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFF!G G $B&0B6(59B5(4 G G G G G G &0 VHUYLFH W\SH G G G G G G 66 $FWLYDWLRQ G G G G G GFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 6.1: Signalling flow for SS connection establishment (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 25 3G TS 29.011 version 3.0.0 6.1.2 Connection established At this stage of the connection, the version negotiation mechanism will be invoked as described in clause 3. The abstract definition of the protocol used for call independent SS operations is imported directly from GSM 09.02 into GSM 04.80. The signalling for invocation of a supplementary service operation is shown in figure 6.2, while figure 6.3 shows the signalling for returning the result of the supplementary service operation. Tables 6.1 and 6.2 show the mapping of GSM 04.80 operation codes to MAP service primitives, and vice versa respectively. The detailed mapping of the contents of the facility information elements to the service primitives triggering the MAP user are described in subclause 6.3. MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G 5(,67(5)$&,/,7< G G G G G G 66 23(5$7,21 G G G G G GFFFFFFFFFFFFFFFFFFFFFFFFF!G G66B6(59,&( 35,0,7,9( 5(4G G G G G GFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 6.2: Signalling flow for SS operation invocation (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 26 3G TS 29.011 version 3.0.0 Choice of service primitive on the basis of received facility information element is as follows: Table 6.1: Mapping of GSM 04.80 operations to GSM 09.02 service primitives Facility information element operation Service primitive for MAP Service user RegisterSS A_REGISTER_SS EraseSS A_ERASE_SS ActivateSS A_ACTIVATE_SS DeactivateSS A_DEACTIVATE_SS InterrogateSS A_INTERROGATE_SS RegisterPassword A_REGISTER_PASSWORD ProcessUnstructuredSS-Request A_PROCESS_UNSTRUCTURED_SS_REQUEST EraseCC-Entry A_ERASE_CC_ENTRY MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G 5(,67(5)$&,/,7< G G66B6(59,&( 35,0,7,9( &1)G G G G 66 23(5$7,21 G G FFFFFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 6.3: Signalling flow for SS operation return result Choice of facility information element on the basis of received service primitive is as follows: Table 6.2: Mapping of GSM 09.02 service primitives to GSM 04.80 operations Service primitive for MAP Service user Facility information element operation A_REGISTER_SS RegisterSS A_ERASE_SS EraseSS A_ACTIVATE_SS ActivateSS A_DEACTIVATE_SS DeactivateSS A_INTERROGATE_SS InterrogateSS A_REGISTER_PASSWORD RegisterPassword A_PROCESS_UNSTRUCTURED_SS_REQUEST ProcessUnstructuredSS-Request A_UNSTRUCTURED_SS_REQUEST UnstructuredSS-Request A_UNSTRUCTURED_SS_NOTIFY ProcessUnstructuredSS-Notify A_GET_PASSWORD GetPassword A_REGISTER_CC_ENTRY AccessRegisterCCEntry A_ERASE_CC_ENTRY EraseCCEntry 6.1.3 Connection release A supplementary service control connection is usually released by the network. The signalling for this situation is shown in figure 6.4. MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G G G $B&0B5(/B&203 G G G G 5(/($6( &203/(7( G G FFFFFFFFFFFFFFFFFFFFG G G G FFFFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 6.4: Signalling flow for SS connection release by the network (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 27 3G TS 29.011 version 3.0.0 However, in exceptional circumstances, the MS may request release of the connection. The signalling for this situation is shown in figure 6.5. MS MSC MAP User in MSC HFI HFI HFI G G G G G G G G 5(/($6( &203/(7( G G G G G GFFFFFFFFFFFFFFFFFFF!G G $B&0B6(59B5(/ G G G G G GFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 6.5: Signalling flow for SS connection release by the MS 6.2 Network initiated SS Management 6.2.1 Connection establishment phase Call independent supplementary service management takes place on a separate, dedicated CM connection between the mobile station and the MSC. The MSC may need to open a connection towards the MS (as described in GSM 04.08) to send the Network initiated SS operation to the MS. Detailed mapping rules are described in subclause 6.3. 6.2.2 Connection established The abstract definition of the protocol used for call independent SS operations is imported directly from GSM 09.02 into GSM 04.80. The signalling for invocation of a Network initiated SS operation is shown in figure 6.6, while figure 6.7 shows the signalling for returning the result of supplementary service operation. Choice of facility information element on the basis of received service primitive is described in table 6.2. MS MSC MAP User in MSC HFI HFI HFI G G G G66B6(59,&( 35,0$7,9( 5(4G G G G G G FFFFFFFFFFFFFFFFFFFFFFFG G G G 5(,67(5)$&,/,7< G G G G G G 66 23(5$7,21 G G G G G G FFFFFFFFFFFFFFFFFFFG G G G G G G G G G Figure 6.6: Signalling flow for Network Initiated SS operation invocation Choice of service primitive on the basis of received facility information element is described in table 6.2. MS MSC MAP User in MSC HFI HFI HFI G G )$&,/,7< G G G G G G 66 23(5$7,21 G G G G G GFFFFFFFFFFFFFFFFFFF!G G G G G G G G66B6(59,&( 35,0$7,9( &1)G G G G G GFFFFFFFFFFFFFFFFFFFFFFF!G G G G G G G G Figure 6.7: Signalling flow for Network Initiated SS operation return result 6.2.3 Connection release A Network initiated SS connection is usually released by the network. The signalling for this situation is shown in figure 6.4. However, in exceptional circumstances, the MS may request release of the connection. The signalling for this situation is shown in figure 6.5. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 28 3G TS 29.011 version 3.0.0 6.2.4 ForwardCheckSSIndication When a mobile station first makes contact with the network after there has been a HLR restart, an indication may be sent by the HLR to the MS to inform of possible unintended consequences with respect to supplementary services. This indication is a separate service in the MAP (MAP_FORWARD_CHECK_SS_INDICATION service), and the abstract definition of its operation (ForwardCheckSSIndication) is imported into the GSM 04.80 protocol. Upon receipt of ForwardCheckSSIndication from the VLR, the MSC shall create a new call independent SS transaction and then send ForwardCheckSSIndication (see GSM 04.10). The MSC is only required to deliver ForwardCheckSSIndication if there is an active RR connection to the MS. The network shall not page the MS in order to deliver ForwardCheckSSIndication. MS MSC VLR HLR HFI HFI HFI HFI G G G G G G)RUZDUG&KHFN66,QGG G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G)RUZDUG&KHFN66,QGG G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G)RUZDUG&KHFN66,QGG G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G Figure 6.8: ForwardCheckSSIndication 6.2.5 CCBS Recall As described in GSM 02.93, when destination B, target of a CCBS request activated by subscriber A, becomes idle, the network shall automatically recall subscriber A. When subscriber A accepts the recall, the network will automatically generate a CCBS call to destination B. The signalling for this situation is shown in figure 6.9. MS MSC VLR HLR HFI HFI HFI HFI G G G G G G 5(027(B86(5 )5(( G G G G G G G G FFFFFFFFFFFFFFFFFFFG G G G G G &&%6 58) G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G&0 6(59,&( 352037 G G G G G G G G FFFFFFFFFFFFFFFFFG G G G G G G G G G G G G G G G 3URFHGXUH GHILQHGG G G G G G G G LQ 60 G G G G G G G G G G G G G G G G G G G G G G G G 6(783 G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G &&%6 58) $&. G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G5(027(B86(5 )5((B$&.G G G G G G G GFFFFFFFFFFFFFFFFFFF!G G G G G G G G G G Figure 6.9: Signalling for CCBS Recall The indication of destination B idle is sent in the MAP_REMOTE_USER_FREE service primitive. It is transmitted on the D-interface and relayed on the B-interface. Then, the recall procedure starts with the establishment of a CC connection initiated by the network with the CM SERVICE PROMPT message. The following exchange of message concerns only the A-interface and is not described here since it is already done in GSM 04.93. The acceptation of the recall by the user is implicit in the SETUP message sent by the MS to the MSC. This message contains the call information previously sent to the MS and the indication that the call in its establishment phase is a CCBS call. The MSC informs the HLR of this acceptation by sending a MAP_REMOTE_USER_FREE_ACK message on the B-interface and further on the D-interface. In case an error occurs (e.g. MS not reachable or Incompatible terminal), at any time of the recall procedure (i.e. just after the error has been received), the MSC shall send the MAP_REMOTE_USER_FREE_ERROR with the appropriate value for the Error information element. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 29 3G TS 29.011 version 3.0.0 Exact values of the parameters and parameter tags are indicated in GSM 04.08, GSM 04.93 and GSM 09.02. 6.2.6 CCBS Monitoring The monitoring process is initiated by the network. It is started on the B-side as soon as subscriber B becomes a target of a CCBS request. It is started on the A-side when subscriber A is found to be busy or suspends a request while being offered a recall. Since the status of a subscriber is linked to its activity, a message sent by the MS to the MSC may lead to the transmission of a message containing the new status on the D-interface (i.e. the MAP_STATUS_REPORT service primitive). This message contains a Status information element which can take the value Idle, Not_Reachable or Not Idle. Several situations might occur, they are described in the figure 6.10. MS MSC VLR HLR HFI HFI HFI HFI G G G G G G G G a. G G&0 6(59,&( 5(48(67G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G 06 $&7,9,7< G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G ___G G G G G G 67$786 5(3257 G G G G G G G GFFFFFFFFFFFFFFFFF!G G b. G G ,06, '(7$&+ G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G '(7$&+ ,06, G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G ___G G G G G G 67$786 5(3257 G G G G G G G GFFFFFFFFFFFFFFFFF!G G c. G G 5(/($6( G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G &$// (1' G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G ___G G G G G G 67$786 5(3257 G G d. G G 6(783 G G G GFFFFFFFFFFFFFFFFF!G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G 127 ,'/( G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G ___G G G G G G 67$786 5(3257 G G G G G G G GFFFFFFFFFFFFFFFFF!G G G G G G G G G G Figure 6.10: Signalling for CCBS Monitoring For all these situations (from a to d), the transmission of the MAP_STATUS_REPORT service primitive depends on the possible change of status of the MS. The detailed behaviour of this procedure is described in GSM 03.93. Exact coding and values of the messages are indicated in GSM 04.08 and GSM 09.02. 6.3 Mapping of Operation Codes, Error Codes, Parameter Tags and Parameter Contents 6.3.1 Operation codes The same operation codes are used for equivalent operations in GSM 04.80 and GSM 09.02 for call independent supplementary service management. 6.3.2 Error codes For call independent supplementary service management, the same error codes are used for equivalent error types in GSM 04.80 and GSM 09.02. The RETURN ERROR components are also constructed in the same way on both sides of the interface. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 30 3G TS 29.011 version 3.0.0 The same parameter tags and parameter values are used for equivalent parameters in GSM 04.80 and GSM 09.02. (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 3GPP 3G TS 29.011 V3.0.0 (1999-05) 31 3G TS 29.011 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 09.11 7.0.0 Transferred to 3GPP CN1 CN#03 29.011 3.0.0 Approved at CN#03 (3G TS 29.011 version 3.0.0 Release 1999) ETSI TS 129 011 V3.0.0 (2000-01) ETSI 32 ETSI ETSI TS 129 011 V3.0.0 (2000-01) (3G TS 29.011 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
2db8737326eb47c66bc9dbdbc50e66e0	124 084	0.1 References	.......................................................................................................................................................... 5
2db8737326eb47c66bc9dbdbc50e66e0	124 084	0.2 Abbreviations	..................................................................................................................................................... 6
2db8737326eb47c66bc9dbdbc50e66e0	124 084	1 MultiParty service (MPTY)	.....................................................................................................................7
2db8737326eb47c66bc9dbdbc50e66e0	124 084	1.1 Beginning the MultiParty service	...................................................................................................................... 7
2db8737326eb47c66bc9dbdbc50e66e0	124 084	1.2 Managing an active MultiParty call	................................................................................................................... 8
2db8737326eb47c66bc9dbdbc50e66e0	124 084	1.2.1 Served mobile subscriber	............................................................................................................................. 8
2db8737326eb47c66bc9dbdbc50e66e0	124 084	1.2.1.1 Put the MultiParty call on hold	............................................................................................................... 8
2db8737326eb47c66bc9dbdbc50e66e0	124 084	1.2.1.2 Create a private communication with one of the remote parties	............................................................. 8
2db8737326eb47c66bc9dbdbc50e66e0	124 084	1.2.1.3 Terminate the entire MultiParty call	....................................................................................................... 9

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.