hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 8 Charging Management and Small Enhancements (CH9) UID_440068 | Technical Specification Group Services and System Aspects TSGS#47(10)0090
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-101075
Meeting SA5#70, 1-5 Mar 2010, Xiamen, P.R. China revision of S5-100975
TSG SA Meeting #44 SP-090312
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Telecom Management) S5-092656
Meeting SA5#65, 11-15 May 2009, Tallinn, Estonia revision of S5-092540
Source: Orange
Title: New WID on IWLAN mobility charging
Document for: Approval
Agenda Item: 7.02
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
IWLAN mobility charging (eIWLAN_Mob) UID_440063 Moved to Rel-10 |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 9 Feasibility Studies | Technical Specification Group Services and System Aspects TSGS#36(07)0306
Meeting #36, 4 – 7 June 2007, Busan, KOREA
Source: SA5 (Telecom Management)
Title: WID Study of System Maintenance by Itf-N
Document for: Approval
Agenda Item: 11.28 (OAM-Study) - OAM&P Studies
3GPP TSG-SA5 (Telecom Management) S5-071006
Meeting SA5#53, 07 - 11 May 2007, Sophia Antipolis, FRANCE
Work Item Description
Title:
Study of System Maintenance over Itf-N UID_360006 - Moved from Rel-8
Acronym: FS_OAM-Maint-Itf-N
Is this Work Item a "Study Item"? (Yes / No): Yes
1 3GPP Work Area
X
Radio Access
X
Core Network
Services
2 Linked work items
OAM&P 8 (Operations, Administration, Maintenance & Provisioning) Feature: OAM8, ID 340063
3 Justification
The EMS (Element Management System) plays an important role in network management architecture.
In general, the EMS is provided by Vendors of the nodes and
Operators, using IRPManager, can manage the nodes through the EMS.
Therefore, when EMS is unavailable or down, the Operator, using IRPManager, would not be able to manage the nodes. Vendors of EMS supply proprietary interface via which the EMS itself can be managed and maintained.
Currently, the management of EMS is not standardized.
Issues to be part of this study:
1) If new 3GPP specification is required (e.g. use potentially existing industry or de facto commercial standards)
2) EMS configuration data backup and restoration
3) Time Synchronization between IRP Manager and IRP Agent
4) Resources monitoring on IRP Agent
5) Software version management of EMS
6) Should Communication Surveillance IRP, e.g. enhancement, to be included in this study
The currently existing 3GPP SA5 IRPs are mainly focused on the management of nodes such as UMTS network nodes (e.g. CM IRPs, Common IRPs, FM IRPs, PM IRP, Trace IRP).
As shown in figure1, currently there are no IRPs to support the management of EMS.
4 Objective
The EMS (e.g. IRPAgent and its associated YyyIRPs) is vital for network management in that network management activities would cease if EMS is unavailable or down. Because of its vital role, it is important that the EMS should be properly managed and maintained.
No doubt, vendors have been providing proprietary means to manage their EMS.
This study is to evaluate if some key or core EMS management functions can be standardized to support a better (most cost/effective) management paradigm in a multi-vendor network environment.
This study will focus on managing the EMS, including as examples:
1) what kind of maintenance operations can be standardized,
2) what kind of information in IRPAgent and YyyIRP shall be modelled.
3) what standard/de facto standards currently exist; comparison; benefits of having a 3GPP specified solution.
The study result can be the baseline of the maintenance of IRPAgent system and may lead to define a new interface IRP in a subsequent implementation work item.
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
Not known |
c5bf175a68d67c6fcb7b30b34228a53d | 30.819 | 10 Expected Output and Time scale (to be updated at each plenary) | New specifications
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
TR 32.824
Study on SOA compliant need and additional capabilities for existing/currently planned Interface IRPs
SA5
SA#43 Sep 2009
SA#44 June 2009
Affected existing specifications
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
11 Work item rapporteur(s)
Edwin TSE (Ericsson)
12 Work item leadership
SA5
13 Supporting Companies
Ericsson, Huawei, Nortel, TeliaSonera, Nokia Siemens Networks
14 Classification of the WI (if known)
X
Study Item (no further information required)
Feature (go to 14a)
Building Block (go to 14b)
Work Task (go to 14c)
Technical Specification Group Services and System Aspects TSGS#41(08)0464
Meeting #41, 15 - 18 September 2008,
Kobe, Japan
Source: SA5
Title: New SID on Rc Reference Point
Document for: Approval
Agenda Item: 12.18
3GPP TSG-SA5 (Telecom Management) S5-081204
Meeting SA5#60, 7 - 11 Jul 2008, Sophia Antipolis, FRANCE
Source: Huawei, China Mobile
Title: New SID on Rc Reference Point
Document for: Approval
Agenda Item:
Study Item Description
Title
Study on Rc Reference Point Functionalities and Message Flows UID_410044 -Moved to Rel-10
Technical Specification Group Services and System Aspects TSGS#43(09)0048
Meeting #43, 9 - 12 March 2009, Biarritz, France
3GPP TSG-SA5 (Telecom Management) S5-091460
Meeting SA5#63, 16-20 February 2009, Prague, Czech Republic
Source: Alcatel-Lucent, China Mobile, Huawei, Orange, Telefonica, T-Mobile, Vodafone
Title: Proposal for a new Study Item on Energy Savings Management
Document for: Approval
Agenda Item: 6.02 – New OAM Work Item proposals
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
Telecommunication Management; Energy Savings Management (ESM) UID_430044-Moved to Rel-10
TSG SA Meeting #44 SP-090318
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Telecom Management) S5-092147
Meeting SA5#64, 30 Mar – 3 Apr 2009 Hangzhou, CHINA revision of S5-091xyw
Source: SA5 (Telecom Management)
Title: New SID on Study on EPC Charging enhancement
Document for: Approval
Agenda Item: 7.02
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
Study on EPC Charging enhancement (FS_EPCcharg) UID_440050-Moved to Rel-10
TSG SA Meeting #44 SP-090462
01 - 04 June 2009,
Oranjestad, Aruba
3GPP TSG-SA5 (Telecom Management) S5-092064
Meeting #64 March 30 - April 3, 2009, Hangzhou, CHINA
Source: Motorola, Qualcomm Europe, Vodafone, T-Mobile, Telefonica, Telecom Italy, Orange
Title: New SID on Study on User Equipment Management (UEM)
Document for: Approval
Agenda Item: 6.x
3GPP™ Work Item Description
For guidance, see 3GPP Working Procedures, article 39; and 3GPP TR 21.900.
Study on Integration of device management information with Itf-N (FS_UEM) UID_440069-Moved to Rel-10
Annex A:
Status list of Work items
This list reflects work items, ongoing, completed or stopped.
400035
Enhanced Home NodeB / eNodeB
EHNB
420036
3G HNB Gateway and LTE HeNB Gateway OAM&P
HNB-OAM_GW
430012
3G HNB and LTE HeNB OAM&P Type 1 Interface
HNB_eHNB-OAM_Type1
440066
3G HNB and LTE HeNB OAM&P Type 2 Interface
HNB_eHNB-OAM_Type2
400032
Multi-Media Telephony Service enhancements
eMMTel
430031
Multimedia Telephony (MMTel) Service and Supplementary Services - Online Charging and completion for Offline Charging (all supplementary services)
eMMTel-SS-CH
430032
Support of Real-time Transfer of Tariff Information (RTTI) in IMS charging
IMSTSS-RTTI-CH
400034
User Data Convergence
UDC
440060
User Data Convergence - Modelling and Management
UDC-MMAN
440062
UDC – Framework for Model Handling and Management
UDC-MMAN-MFRM
440061
UDC – Common Baseline Information Model
UDC-MMAN-CBIM
400039
MBMS support in EPS
MBMS_EPS
430033
MBMS Charging in EPS
MBMS_EPS
420029
OAM&P 9
OAM9
420030
Network Infrastructure Management
OAM9-NIM
420031
Software Management for Network Elements
OAM9-NE_SWM
440064
Service Oriented Architecture (SOA) for IRP
OAM9
440065
IRP SOAP Solution Sets continuation from Rel-8
OAM9
420032
Performance Management
OAM9-PM
430041
Enhancement of E-UTRAN Performance Measurements
OAM9
430042
Enhancement of EPC Performance Measurements
OAM9
440059
Enhancement of UTRAN Performance Measurements
OAM9
420033
Deleted - Trace
OAM9-Trace
430043
Self-Organizing Networks (SON) - OAM aspects
OAM9-SON
390007
SON self-optimization management
LTE_SON-OAM
440067
Automatic Radio Network Configuration Data Preparation
OAM9
440058
Subscription Management (SuM) evolution
OAM9-SuM
440068
Charging Management small Enhancements
CH9
360006
Study on System Maintenance over Itf-N
FS_OAM-Maint-Itf-N
360007
Study on Self-Organizing Networks (SON) related OAM interfaces for Home NodeB
FS_OAM-SON-HNB
390017
Study on Self-healing of Self-Organizing Networks (SON)
FS_OAM-SON-SH
400029
Study on Service Oriented Architecture (SOA) for IRP
FS_OAM_SOA_IRP
Annex B:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2010-09
SA#49
SP-100525
--
--
Presentation to SA for Information and Approval
---
1.0.0
2010-10
--
--
--
--
Publication
1.0.0
9.0.0 |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.531 Telecommunication management; Software management; Concepts and Integration Reference Point (IRP) Requirements | |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.532 Telecommunication management; Software management Integration Reference Point (IRP); Information Service (IS) | |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.533 Telecommunication management; Software management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | |
8a916e998185fce27065b78e6b079636 | 32.535 | 32.535 Telecommunication management; Software management Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | Software Management, in general, provides the operator with the ability to manage effectively the software entities residing in the 3G network. Software Management function is useful especially when there is a need to manage a large number of software residing in the managed elements widely distributed geographically. The main focus is the management of new software releases and correction patches [1].
The software management operations are initiated by the operator or by functions in the Operations Systems (OSs) either on single NE or across several NEs of the 3G network. |
8a916e998185fce27065b78e6b079636 | 32.535 | 1 Scope | The present document provides the XML file format definition for the Software Management Integration Reference Point (IRP) IS [3] V9.2.X.
The present document specifies the XML Definitions for the Software Management Integration Reference Point (IRP) as it applies to Itf-N, in accordance with Software Management IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4]. |
8a916e998185fce27065b78e6b079636 | 32.535 | 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements”.
[2] 3GPP TS 32.102: “Telecommunication management; Architecture”.
[3] 3GPP TS 32.532: “Telecommunication management; Software management Integration Reference Point (IRP); Information Service (IS)”
[4] 3GPP TS 32.335: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): eXtensible Markup Language (XML) solution definitions”.
[5] 3GPP TS 32.331: “Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements”. |
8a916e998185fce27065b78e6b079636 | 32.535 | 3 Definitions and abbreviations | |
8a916e998185fce27065b78e6b079636 | 32.535 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2], and 3GPP TS 32.331 [5] apply. |
8a916e998185fce27065b78e6b079636 | 32.535 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
IRP Integration Reference Point
IS Information Service
NL Notification Log
NRM Network Resource Model
SwM Software Management
UML Unified Modelling Language
XML eXtensible Markup Language |
8a916e998185fce27065b78e6b079636 | 32.535 | 4 Software Management IRP XML Definitions | |
8a916e998185fce27065b78e6b079636 | 32.535 | 4.1 Software Management IRP XML Definitions | This section provides XML definitions of Software Management IRP IOCs and notifications as defined in [3].
4.2 XML Schema for Software Management IRP Notifications (file name “swManagementIRPNotif.xsd”)
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xe="http://www.3gpp.org/ftp/specs/archive/32_series/32.305#notification" xmlns:xswm="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPNotif" xmlns:xswmi="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPIOCs" targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPNotif" elementFormDefault="qualified" attributeFormDefault="unqualified">
<import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.305#notification"/>
<import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPIOCs"/>
<simpleType name="SwVersionToBeInstalledConditional">
<restriction base="string"/>
</simpleType>
<complexType name="OfferedFinalAdministrativeStateInformation">
<sequence>
<element name="OfferedFinalAdministrativeStateValue" type="xswmi:FinalAdministrativeStateValue" maxOccurs="3"/>
</sequence>
</complexType>
<simpleType name="TriggerForDeletion">
<restriction base="string">
<enumeration value="IRP_AGENT_TERMINATION"/>
<enumeration value="IRP_MANAGER_TERMINATION"/>
<enumeration value="AUTOMATED_SWM_SUCCESFULLY_CONCLUDED"/>
<enumeration value="SELF_CONFIGURATION_SUCCESFULLY_CONCLUDED"/>
</restriction>
</simpleType>
<simpleType name="RequestID">
<restriction base="unsignedLong"/>
</simpleType>
<simpleType name="DownloadNESwOperationStatus">
<restriction base="string">
<enumeration value="NE_SWDOWNLOAD_SUCCESSFUL"/>
<enumeration value="NE_SWDOWNLOAD_FAILED"/>
<enumeration value="NE_SWDOWNLOAD_PARTIALLY_SUCCESSFUL"/>
</restriction>
</simpleType>
<simpleType name="FileLocation">
<restriction base="string"/>
</simpleType>
<complexType name="NESwInfo">
<sequence>
<element name="fileLocation" type="xswm:FileLocation" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="FailedSwEntry">
<sequence>
<element name="failedSw" type="xswm:FileLocation"/>
<element name="failureReason" type="xswm:FailureReason"/>
</sequence>
</complexType>
<complexType name="FailedSwInfo">
<sequence>
<element name="failedSwEntry" type="xswm:FailedSwEntry" maxOccurs="unbounded"/>
</sequence>
</complexType>
<simpleType name="FailureReason">
<restriction base="string"/>
</simpleType>
<simpleType name="InstallNESwOperationStatus">
<restriction base="string">
<enumeration value="NE_SW_INSTALLATION_SUCCESSFUL"/>
<enumeration value="NE_SW_INSTALLATION_FAILED"/>
<enumeration value="NE_SWINSTALLATION_PARTIALLY_SUCCESSFUL"/>
</restriction>
</simpleType>
<simpleType name="ActivateNESwOperationStatus">
<restriction base="string">
<enumeration value="NE_SW_ACTIVATION_SUCCESSFUL"/>
<enumeration value="NE_SW_ACTIVATION_FAILED"/>
<enumeration value="NE_SWACTIVATION_PARTIALLY_SUCCESSFUL"/>
</restriction>
</simpleType>
<complexType name="NotifySwMProfileChange">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="versionNumber" type="xswmi:VersionNumber"/>
<element name="nEInformation" type="xswmi:NEInformation"/>
<element name="swVersionToBeInstalled" type="xswm:SwVersionToBeInstalledConditional"/>
<element name="stepsAndSelectedStopPointList">
<complexType>
<complexContent>
<extension base="xswmi:StepsAndSelectedStopPointList"/>
</complexContent>
</complexType>
</element>
<element name="selectedFinalAdministrativeState" type="xswmi:FinalAdministrativeStateValue"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifyNewSwAvailability">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="nEandSWversion" type="string"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProcessDeletion">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="triggerForDeletion" type="xswm:TriggerForDeletion"/>
<element name="additionalInformation" type="string" minOccurs="0"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProcessStage">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="stepInfoList" type="xswmi:StepInfoList"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProcessCreation">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="nEIdentification" type="xswmi:Id"/>
<element name="profileId" type="xswmi:ProfileId"/>
<element name="matchingNEInformation" type="xswmi:NEInformation"/>
<element name="stepInfoList" type="xswmi:StepInfoList"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProfileDeletion">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifySwMProfileCreation">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="versionNumber" type="xswmi:VersionNumber"/>
<element name="nEInformation" type="xswmi:NEInformation"/>
<element name="swVersionToBeInstalled" type="xswm:SwVersionToBeInstalledConditional"/>
<element name="stepsAndSelectedStopPointList">
<complexType>
<complexContent>
<extension base="xswmi:StepsAndSelectedStopPointList"/>
</complexContent>
</complexType>
</element>
<element name="selectedFinalAdministrativeState" type="xswmi:FinalAdministrativeStateValue"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifyDownloadNESwStatusChanged">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="downloadProcessId" type="xswm:RequestID"/>
<element name="downloadOperationStatus" type="xswm:DownloadNESwOperationStatus"/>
<element name="downloadedNESwInfo" type="xswm:NESwInfo" minOccurs="0"/>
<element name="failedSwInfo" type="xswm:FailedSwInfo" minOccurs="0"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifyInstallNESwStatusChanged">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="installProcessId" type="xswm:RequestID"/>
<element name="installOperationStatus" type="xswm:InstallNESwOperationStatus"/>
<element name="installedNESwInfo" type="xswm:NESwInfo" minOccurs="0"/>
<element name="failedSwInfo" type="xswm:FailedSwInfo" minOccurs="0"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="NotifyActivateNESwStatusChanged">
<complexContent>
<extension base="xe:Notification">
<sequence>
<element name="body">
<complexType>
<sequence>
<element name="activateProcessId" type="xswm:RequestID"/>
<element name="activateOperationStatus" type="xswm:ActivateNESwOperationStatus"/>
<element name="swVersionActivated" type="string" minOccurs="0"/>
<element name="failureReason" type="xswm:FailureReason" minOccurs="0"/>
</sequence>
</complexType>
</element>
</sequence>
</extension>
</complexContent>
</complexType>
<element name="NotifySwMProfileCreation" type="xswm:NotifySwMProfileCreation"/>
<element name="NotifySwMProfileDeletion" type="xswm:NotifySwMProfileDeletion"/>
<element name="NotifySwMProcessCreation" type="xswm:NotifySwMProcessCreation"/>
<element name="NotifySwMProcessStage" type="xswm:NotifySwMProcessStage"/>
<element name="NotifySwMProcessDeletion" type="xswm:NotifySwMProcessDeletion"/>
<element name="NotifyNewSwAvailability" type="xswm:NotifyNewSwAvailability"/>
<element name="NotifySwMProfileChange" type="xswm:NotifySwMProfileChange"/>
<element name="NotifyDownloadNESwStatusChanged" type="xswm:NotifyDownloadNESwStatusChanged"/>
<element name="NotifyActivateNESwStatusChanged" type="xswm:NotifyActivateNESwStatusChanged"/>
<element name="NotifyInstallNESwStatusChanged" type="xswm:NotifyInstallNESwStatusChanged"/>
</schema>
4.3 XML Schema for Software Management IRP IOCs (file name “swManagementIRPIOCs.xsd”)
<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xswmi="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPIOCs" xmlns:xn="http://www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrm" targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.535#swManagementIRPIOCs" elementFormDefault="qualified" attributeFormDefault="unqualified">
<import namespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrm" schemaLocation="genericNrm.xsd"/>
<simpleType name="NEInformation">
<restriction base="string"/>
</simpleType>
<simpleType name="Id">
<restriction base="xn:dn"/>
</simpleType>
<simpleType name="VersionNumber">
<restriction base="unsignedShort"/>
</simpleType>
<complexType name="ProfileId">
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="versionNumber" type="xswmi:VersionNumber"/>
</sequence>
</complexType>
<simpleType name="FinalAdministrativeStateValue">
<restriction base="string">
<enumeration value="LOCKED"/>
<enumeration value="UNLOCKED"/>
<enumeration value="DETERMINED_BY_CONFIGURATION_DATA"/>
</restriction>
</simpleType>
<complexType name="OfferedFinalAdministrativeStateInformation">
<sequence>
<element name="OfferedFinalAdministrativeStateValue" type="xswmi:FinalAdministrativeStateValue" maxOccurs="3"/>
</sequence>
</complexType>
<complexType name="StepsAndOfferedStopPointListEntry">
<sequence>
<element name="nameOfStep" type="xswmi:NameOfStep"/>
<element name="sequenceNumberInProcess" type="xswmi:SequenceNumberInProcess"/>
<element name="stopPointCanBeSetBeforeThisStep" type="xswmi:StopPointCanBeSetBeforeThisStep"/>
</sequence>
</complexType>
<complexType name="StepsAndOfferedStopPointList">
<sequence>
<element name="stepsAndOfferedStopPointListEntry" type="xswmi:StepsAndOfferedStopPointListEntry" maxOccurs="unbounded"/>
</sequence>
</complexType>
<simpleType name="StopPointCanBeSetBeforeThisStep">
<restriction base="boolean"/>
</simpleType>
<complexType name="StepsAndSelectedStopPointListEntry">
<sequence>
<element name="nameOfStep" type="xswmi:NameOfStep"/>
<element name="sequenceNumberInProcess" type="xswmi:SequenceNumberInProcess"/>
<element name="stopPointSetIndication" type="xswmi:StopPointSetIndication"/>
</sequence>
</complexType>
<complexType name="StepsAndSelectedStopPointList">
<sequence>
<element name="stepsAndSelectedStopPointListEntry" type="xswmi:StepsAndSelectedStopPointListEntry" maxOccurs="unbounded"/>
</sequence>
</complexType>
<simpleType name="StopPointSetIndication">
<restriction base="string">
<enumeration value="STOP_POINT_IS_SET_BEFORE_THIS_STEP"/>
<enumeration value="STOP_POINT_IS_NOT_SET"/>
</restriction>
</simpleType>
<simpleType name="SequenceNumberInProcess">
<restriction base="unsignedShort"/>
</simpleType>
<simpleType name="NameOfStep">
<restriction base="string">
<enumeration value="SW_DOWNLOAD"/>
<enumeration value="SW_INSTALLATION"/>
<enumeration value="SW_ACTIVATION"/>
<enumeration value="PREPARE_BASIC_CONFIGURATION_AND_OAMLINK"/>
<enumeration value="RETRIEVE_CONFIGURATION_DATA"/>
<enumeration value="SETUP_PRECONFIGURED_SIGNALLING_LINKS"/>
<enumeration value="SET_FINAL_STATE_OF_NE "/>
</restriction>
</simpleType>
<simpleType name="StepProgress">
<restriction base="string">
<enumeration value="NOT_YET_STARTED"/>
<enumeration value="RUNNING"/>
<enumeration value="COMPLETED"/>
<enumeration value="AWAITING_RESUME"/>
<enumeration value="FAILURE"/>
<enumeration value="TERMINATED"/>
</restriction>
</simpleType>
<complexType name="StepInfoListEntry">
<sequence>
<element name="nameOfStep" type="xswmi:NameOfStep"/>
<element name="sequenceNumberInProcess" type="xswmi:SequenceNumberInProcess"/>
<element name="stopPointSetIndication" type="xswmi:StopPointSetIndication"/>
<element name="stepProgress" type="xswmi:StepProgress"/>
</sequence>
</complexType>
<complexType name="StepInfoList">
<sequence>
<element name="stepInfoListEntry" type="xswmi:StepInfoListEntry" maxOccurs="unbounded"/>
</sequence>
</complexType>
<complexType name="swMCapabilityIOC">
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="neInformation" type="xswmi:NEInformation"/>
<element name="stepsAndOfferedStopPointList" type="xswmi:StepsAndOfferedStopPointList"/>
<element name="offeredFinalAdministrativeStateInformation" type="xswmi:OfferedFinalAdministrativeStateInformation"/>
</sequence>
</complexType>
<complexType name="swMProfileIOC">
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="versionNumber" type="xswmi:VersionNumber"/>
<element name="neInformation" type="xswmi:NEInformation"/>
<element name="stepsAndSelectedStopPointList" type="xswmi:StepsAndSelectedStopPointList"/>
<element name="selectedFinalAdministrativeState" type="xswmi:FinalAdministrativeStateValue"/>
</sequence>
</complexType>
<complexType name="swMProcessIOC">
<sequence>
<element name="id" type="xswmi:Id"/>
<element name="nEIdentification" type="xswmi:NEInformation"/>
<element name="profileId" type="xswmi:ProfileId"/>
<element name="stepInfoList" type="xswmi:StepInfoList"/>
</sequence>
</complexType>
</schema>
Annex A (informative):
Void
Annex B (informative):
Change history
Change history
Date
TSG #
TSG Doc.
CR
R
Subject/Comment
Cat
Old
New
Dec 2009
SA#46
SP-090736
--
--
Presentation to SA for Information and Approval
--
--
1.0.0
Dec 2009
--
--
--
--
Publication
--
1.0.0
8.0.0
Dec 2009
-
-
-
-
Update to Rel-9 version
--
8.0.0
9.0.0
Mar 2010
SA#47
SP-100035
0001
-
Discontinue from Rel-9 onwards the XML schema extraction and storage
F
9.0.0
9.1.0
Mar 2010
SA#47
SP-100035
0002
-
To add XML solution set for Non Automated Software Management notifications
F
9.0.0
9.1.0 |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 1 Scope | This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
The present document shall analyse the current network selection mechanism and will highlight its limitations based on known operational problems. It will also consider issues brought about by the advent of new access systems.
Potential changes shall be described to the selection mechanism to provide a better user and network operator experience.
The present document is applicable to both GERAN and UTRAN. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TS 22.011: "Service Accessibility"
[2] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station"
[3] 3GPP TS 22.234: "Requirements on 3GPP system to Wireless Local Area Network (WLAN) interworking"
[4] 3GPP TS 24.234: "3GPP System to Wireless Local Area Network (WLAN) interworking; User Equipment (UE) to network protocols" |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3 Definitions, symbols and abbreviations | |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply.
R-UIM Removable User Identity Module (note this is a 3GPP2 term) |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply:
AP Access Point
CN Core Network
CS Circuit Switched
CSD Circuit Switched Data
FBS Full Band Scan
FPLMN Forbidden Public Land Mobile Network
HPLMN Home Public Land Mobile Network
I-WLAN Interworking WLAN
ME Mobile Equipment
OOS Out Of Service
OTA Over The Air
PLMN Public Land Mobile Network
PS Packet Switched
RAN Radio Access Network
RAT Radio Access Technology
R-UIM Removable User Identity Module
SMS Short Message Service
SN Service Network
UE User Equipment
VPLMN Visited Public Land Mobile Network
WLAN Wireless Local Area Network |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 4 Network Selection overview | The Stage 1 Requirements for Network Selection are found in TS 22.011 [1]. This describes the behaviour that is expected from a UE in order to select a PLMN from which to gain service.
Two modes of operation are supported: Automatic and Manual. At power on, and the UE is required to revert to the last mode used at power off. At any time, the user may request the UE to initiate reselection and registration onto an alternative available PLMN.
As defined in Release 6 the Automatic Mode will attempt to connect the UE to a PLMN using the following order; the RPLMN (or its EPLMNs) followed by the HPLMN followed by PLMNs indicated on the User and then the Operator controlled Preferred Lists, followed by those PLMNs with sufficient signal quality in random order, and finally those in descending order of signal strength.
The Manual Mode presents the user with a list of the networks that are available and the user then selects which network the UE should connect to in order to gain service.
In the case of the Automatic mode periodic network selection attempts may be enabled by the HPLMN to search for and connect to higher priority PLMNs if they have become available. In Release 7 the Equivalent HPLMN feature has been introduced which allows multiple PLMNs to be treated as the HPLMN and hence share the highest priority during network selection attempts.
The detailed Network Selection Procedure is contained in TS23.122 [2]
The Stage 1 Requirements for Network Selection when access is available through I-WLAN are detailed in TS 22.234 [3]. This is provides for both an automatic and a manual mode similar to that specified in TS 22.011 [1]. This introduces a number of additional priority lists, which enable Network Operators to give different preferences to PLMNs that are available via I-WLAN and also to indicate preferred WLAN ID’s in the case that it is possible to connect to the same PLMN via more than one WLAN AP.
The detailed Network Selection Procedure for I-WLAN is contained in TS 24.234 [4]. The Network Selection Procedures defined for I-WLANs are decoupled from the network selection procedures for cellular protocols specified in TS 23.122 [2], though they share some similarities. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5 High level principles | |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.1 General | This clause describes the principles that are applicable in network selection up to Rel-6 and that are not expected to be challenged by the enhancements introduced to the network selection procedures. Furthermore the expectations of the three main stakeholders in the network selection procedures (customer, home operator, visited network operator) are also described. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.2 Key principles | The following is a set of principles that should be preserved when devising a new procedure to perform the registration to the serving mobile network. The assumption made in this paragraph is that the term “network” has to be interpreted as the core network of the mobile operator with whom the subscriber has direct relation (i.e. the home PLMN) or indirect via the home PLMN (e.g. a Visited PLMN).
Principle 1: the subscriber selects and registers with a public land mobile network regardless of the radio access technology employed to attain connectivity. This is then regarded as the registered PLMN (RPLMN).
Principle 2: the home PLMN operator and the user can prioritise by means of lists the available PLMNs/Access technologies combinations for roaming. If only networks for which no priority is defined are available, then those networks with sufficient radio quality are chosen at random, then the rest are chosen in order of decreasing signal strength. Furthermore the home PLMN operator has control over the periodicity the UE attempt to register on a PLMN with higher priority than the current registered one.
Principle 3: the HPLMN and any other PLMN declared as equivalent to the HPLMN (EHPLMN) of the subscriber has by default the highest priority, however the UE shall first attempt to attain service from the last PLMN it successfully registered on (last registered PLMN or the equivalent PLMNs).
Principle 4: the PLMN has priority over the particular radio access technology that the UE may prefer to use. When the PLMN supports multiple access technologies, the UE shall use in priority preferred RAT on the USIM preferred list to attain connectivity on that PLMN. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.3 Backward compatibility | Enhancements to the network selection principles will not negatively affect the functionality of existing devices.
Enhancements to the Network Selection procedure in the core network shall be done such that backwards compatibility with existing UEs is maintained.
The network selection principles should allow for at least the following combination of entities:
- HPLMN and USIM are Rel-7: HPLMN/EHPLMN (Rel-7) - VPLMN (pre-Rel-7) - ME (pre-Rel-7) - USIM (Rel-7)
- HPLMN and ME are Rel-7: HPLMN/EHPLMN (Rel-7) - VPLMN (pre-Rel-7) - ME(Rel-7) - (U)SIM (pre-Rel-7)
- VPLMN is Pre-Rel-7: HPLMN/EHPLMN (Rel-7) - VPLMN (pre-Rel-7) - ME (Rel-7) - USIM (Rel-7)
- All the entities are Rel-7: HPLMN/EHPLMN (Rel-7) - VPLMN (Rel-7) - ME(Rel-7) - USIM (Rel-7) |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.4 Customer expectations | Following switch-on where there is no last registered PLMN, the user should be registered on non-forbidden PLMN as fast as possible (typically within 20 seconds). This period includes the execution of any 3GPP defined functionality (e.g. after any PIN verification) that is performed by the mobile device but excludes any additional functionality (e.g. operating system device initialisation).
Following switch-on if the last registered PLMN is available, and no higher priority PLMN is available (e.g. HPLMN) the user should be registered on that PLMN (typically within 5 seconds). This period includes the execution of any 3GPP defined functionality as described above.
Following switch-on if the last registered PLMN is available, and a higher priority PLMN is available (e.g. HPLMN) the user should be registered on the Highest priority PLMN available (typically within 20 seconds). This period includes the execution of any 3GPP defined functionality as described above.
If not limited by subscriptions and other commercial framework and technical feasible, roaming users should always be able to access all their services and their services shall always work correctly as if they were on the home network.
Users shall be able to choose the PLMN they wish to receive service from. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.5 Home operator expectations | The home operator's users' devices should select the home operator's preferred network and access type while roaming.
The home operator should be able to set which preferred networks are in the customer’s device. The home operator should be able to set the mix of networks and access types that can be used by each roaming user for each visited network (i.e. apply per user per country). This should include which networks are preferred in selected countries in priority order.
User preferences or manual PLMN selection may override operator preferences.
The HPLMN can direct the user to a VPLMN that is capable of providing the best possible service to match the "at home experience". However, the VPLMN needs to have over-riding control over the use of its own capabilities. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.6 Visited operator expectations | It should be possible for the visited operator to direct traffic from roamers onto the appropriate access technology to manage network capacity and loading (e.g. to use 2G for voice and 3G for high speed data services). The ability to change the access in real-time for roamers according to their usage should be possible. The visited operator should be able to choose the most appropriate access technology in order to meet the service requirements of the user subject to network conditions and availability. This should cover data rates also, for example, the visited network should be able to allocate 128kbps even though the user may usually use 384kbps. The visited operator should be able to allocate access technology and data rates on the basis of the IMSI of the inbound roamer. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 5.7 UICC and USIM considerations | In terms of Network Selection Procedures, the USIM contains several sets of data that are used either for automatic or manual selection:
- User controlled PLMN selector with Access Technology
- Operator controlled PLMN selector with Access Technology
- Higher Priority PLMN search period
- Forbidden PLMNs
- HPLMN selector with Access Technology
- Network Parameters
And for I-WLAN:
- User controlled PLMN selector for WLAN Access
- Operator controlled PLMN selector for WLAN Access
- User controlled WLAN Specific Identifier List
- Operator controlled WLAN Specific Identifier List |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6 Identified issues with current specifications | |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.1 HPLMN initiated network reselection | No dynamic mechanism exists for the HPLMN to request that a UE selects a different VPLMN whilst roaming. Currently this happens through the use of the background scan when the UE is on a non-preferred network. This mechanism is not considered dynamic since updating the preference lists in the UE and taking the new lists into use is not efficient enough at the moment.
Means should be provided that allow the HPLMN to dynamically direct the UE to select a different VPLMN whenever it is already registered on a VPLMN. National roaming situations must be taken into account in this case.
The timing of when the new network is selected should happen at a point where the user is not inconvenienced.
The HPLMN request to select a different VPLMN should not over-ride a manual network selection made by the user, or a selection that is done according to user preferences. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.2 Single priority or no priorities on VPLMNs | Currently the only standardised automatic network selection mechanism by which the HPLMN can control which VPLMN is selected is through the Operator preferred list. The intended behaviour is that one network in the visited country takes precedence over all the others, and in the case where a UE has selected an alternate network, the background scan should cause the UE to re-select to the preferred network.
As a consequence the HPLMN has a choice to direct “all” of its roaming users to one VPLMN, or alternatively to distribute the users randomly between all of the VPLMNs 1 in the visited country (by not stating a preferred network for that country).
It is currently not possible to distribute traffic between, say, 2 or 3 of the networks in the visited country. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.3 Manual network selection | Manual selection is a useful tool in cases where the selected PLMN is not providing adequate quality. However, in other circumstances it prevents the mobile operator from providing the user with the best possible service.
One key limitation of manual network selection is that the user is presented only with the network name and is not given any other information on which to base an informed decision on which network to select. As an example, the user could be informed of the PLMNs that are recommended by its HPLMN to give an "at home" experience .(e.g. availability of CAMEL, GPRS, 3G etc).
Further examples of such information could include; the ability for the HPLMN to indicate which services (e.g. voice and/or data) a user will be able to gain from each network and the ability for the HPLMN to indicate if 3G Roaming is available. Any such mechanism should be extensible so as new features and commercial arrangements are introduced the HPLMN will be able to inform the user of their availability.
Such information on the network capabilities available for presentation to the user needs to be defined. How it is presented to the user would be in accordance with vendor implementations. The gathering of such information shall not adversely impact the time the user has to wait before the list is presented.
Other limitations are:
- The network name presented to the user cannot show PLMN name changes on legacy devices unless NITZ is implemented in the VPLMN and device. For the HPLMN, operators can program their current network name in the USIM card which will then be displayed on the device.
- The HPLMN has no method of restricting the networks visible in manual selection e.g. to cater for a proposition that gives users a choice of certain networks only.
- When the customer manually selects a network, some devices use manual selection from that point onwards. The problem this gives is that if the manually selected network runs out of coverage another network is not automatically selected. This can be a problem either in the foreign country or with some devices when returning to the home network.
- In manual mode, a UE returning to an area served by the HPLMN (e.g. when the user returns from holiday) will look only for the RPLMN, potentially leaving the user without service. Ideally it should be possible for example for the user to set a preference for either manual or automatic network selection on power-up. At power on, if the RPLMN is not found, but the HPLMN is available then the UE should automatically register with it. -
- In the case of Equivalent HPLMNs where 2 or more PLMNs can equate to a single PLMN the user is only presented with the highest priority EHPLMN name allowing them no way to choose the other network if network selection fails.
If a PLMN is inserted into the forbidden PLMN list the only way to remove that PLMN is via manual network selection and successful registration on that PLMN. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.4 Time to select a network | When multiple bands and multiple technologies are available the time to select a PLMN may be too long. The new procedure should address this area |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.5 RAT preference for PLMNs not prioritised by the USIM | This refers specifically to the case of the initial PLMN selection. Subsequent to that, the serving PLMN may change the RAT used by the UE .The visited operator should be able to allocate access technology and data rates on the basis of the identity (e.g. MCC-MNC) of the home operator of the inbound roamer.
TS 23.122 [2] specifies that preferred PLMNs can be prioritised with their preferred RAT on the USIM preferred list. Therefore, when 2 different PLMNs are detected by the UE and they are both in the preferred list, the UE should select the highest priority one. If two RATs of the same PLMN are detected by the UE but the preferred list specifies only one RAT for this PLMN, the UE should select the RAT that is in the preferred list.
Where a PLMN entry on the preferred list has multiple RATs specified or if there is no RAT specified, then the end user experience is not known because how the UE uses this information is not standardised and so it is not predictable which RAT will be used.
What currently happens is that when roaming in a country where none of the available PLMN/RATs are prioritised relative to each other, the UE will select randomly a PLMN+RAT out of the high quality PLMNs available. Therefore when a PLMN selection is made and no priority is given on the USIM for the available PLMN+RATs the UE should choose the highest capability RAT, consistent with its own capabilities, provided it is above a usable signal level. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.6 A new PLMN can only be selected after an exhaustive scan | This section highlights that the time from loss of coverage to registration on a new PLMN is already quite long and with future developments will possibly be even longer.
TS 23.122 [2] and TS 25.304 mandate that the UE shall search for its last RPLMN in every supported RAT and bands at power on or recovery from lack of coverage before attempting to register on another PLMN.
The reason for selecting the RPLMN instead of the HPLMN was due to the experience found during GSM Phase 1 where the mobile was required to search for its HPLMN first. This meant that in the roaming case the mobile would search for a non-existent PLMN before moving on to select a VPLMN. By making the mobile search for the RPLMN the whole process is speeded up. When in the HPLMN the RPLMN=HPLMN so no delay in selecting HPLMN and when roaming the mobile will have been on the preferred PLMN so again using RPLMN gives the most efficient behaviour.
The issue for operators is that when a UE loses coverage from the RPLMN, it is obliged to perform a full scan of all supported bands (UMTS2100, EGSM900, GSM1800 and possibly even GSM850 and GSM1900 depending on the implementation) before possibly reselecting a different PLMN, such as a National Roaming Partner. Today, such a scan takes a long time in dense or complex radio environment, which means the UE can spend over a minute searching/synchronising/decoding cells where only FPLMNs are to be found. In the future, as more frequency bands are introduced or refarmed for 3G (UMTS1900, UMTS800, 2.5GHz, TDD, FDD in GSM bands, etc.) and more technologies are integrated to 3GPP (WiFi, WiMax, etc.) the UE may require an even longer time to complete a scan of all supported technologies.
It should be possible for the UE to register immediately with its HPLMN when found during the scan.
In order to allow fast network selection, the specifications should not require exhaustive band scans to be performed at moments when they cause unnecessary delays in network selection.
6.7 Size of lists
Currently different handsets support different list sizes of the various PLMN lists on the (U)SIM (as specified in 31.102) and this leads to problems for operators when trying to guide the behaviour of the handset in selecting a PLMN. It may be beneficial to standardise a minimum size of list to be supported by the ME. The agreed minimum lengths of the lists should support the normal operational requirements of operators, i.e. not necessarily the longest possible list sizes but a reasonable portion of them.
The lists concerned include: Operator PLMN, User PLMN, and Forbidden PLMN.
6.8 Management of PLMN access
Currently means are provided to prevent the handset from constantly attempting to obtain service from PLMNs that it is unable to use (e.g. due to roaming restrictions). One means of achieving this is through the use of the PLMN Forbidden List.
It is possible for PLMN entries to be removed from the Forbidden List due to limitations on its size or on successful PLMN registration by manual selection As the Forbidden List can also be controlled by the operator via OTA, this could create a position where the operator can not effectively control the user's Forbidden List for the following purposes:
- Use of the Forbidden List to change or improve user experience
- Any form of guaranteed experience through OTA updates (as the OTA update can quickly be over written by the handset)
It would be useful to introduce a means for the home operator to have greater control over the PLMN selection procedure while maintaining the use of the current Forbidden List which is dynamically updated by the UE. Specifically, it should be possible for the HPLMN to prevent user access to specified PLMNs or PLMN + RAT combinations that the user cannot over-ride. It should be possible to hide barred PLMNs or PLMN + RAT from user selection or indicate in some way to the user that these selections are not possible. Any restriction shall not preclude access to networks for emergency calls.
6.9 Management of devices
There are two situations of device use which makes it difficult how they select networks
- Devices that are always on – The problem here is that in some cases, any USIM OTA updates take effect only when the device is power cycled. If the device is not power cycled the customer will not receive the benefit of the new list of preferred networks. Note the re-reading of the USIM files by the device, could possibly be improved with more uniform support of the "refresh" command by device manufacturers. Ideally the HPLMN should be able to request that UE performs a refresh when it sends an OTA update and this refresh should be invisible to the user.
- Devices that are often off – The problem here being that to update this type of device operators may need complex configurations that send out updates as soon as the device is powered on. Any type of "bulk" USIM OTA updates will fail on these device types as the device is normally off.
The handling of OTA updates should be improved and the refreshing of data used by the UE should be as quick as possible so long as this does not adversely impact the user (e.g. data should not be refreshed if doing so would lead to a dropped call). Means should be provided to allow the subscriber’s operator to update information, used by the UE, in the most optimum manner possible.
Note: This might be addressed by OMA Device Management |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.10 Ping ponging between Registration Areas | Currently the mechanisms standardised do not seem to adequately cater for the national roaming scenario nor formulti RAT (3G, WLAN, 2G etc.) environments. This, when associated with fluctuating signal condition, can lead to UE ping-ponging between 2G and 3G , causing significant signalling load on the network as well as severely affecting user experience.
The currently specified behaviour is as follows:
- If less than 12 seconds, the UE will be momentarily out of coverage but will not declare out of service (OOS), and then it will come back to the serving cell.
- If slightly more than 12 seconds, the UE will declare Out-of-service(OOS) and start scanning, but then will most likely come back to the same 3G cell.
- If longer (~30 sec) the UE may go to a national roaming partner, but after 6 minutes it is likely to come back to the same weak 3G cell upon the first background HPLMN search.
This will create instability that will affect user experience as this is a source of missed calls, failed call setups and possible denial of certain services.
Means should be reviewed to improve the effect of ping ponging between registration areas. It should be possible for allow the network to be configured by the operator so as to enable the definition of different quality criteria for leaving and coming back to a cell/PLMN. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.11 The last RPLMN is always the highest priority | TS 23.122 [2] mandates that the UE shall always select in priority its last RPLMN or an ePLMN when recovering from out of coverage or at power-on.
The main reason for this RPLMN requirement was due to the fact that in all roaming cases at that time the mobile will not find its HPLMN and this introduced an unnecessary (and unacceptable) delay to getting into service. In the case the mobile was in its home country it will, in the majority of cases, be on its HPLMN (i.e. the RPLMN is the HPLMN) so there is no problem with looking for the RPLMN first.
TS 23.122 [2] requires the UE to wait for at least 2 minutes following power-on before attempting to access the HPLMN or an EHPLMN or higher priority PLMN, thus enabling the UE to receive any messages from the network
At recovery from lack of coverage (e.g. tube or tunnel) and if the UE lost coverage whilst registered on the National Roaming Partner, the UE will go directly to the National roaming partner even if the HPLMN is present. Then the UE will have to wait for the HPLMN timer to expire before it can attempt to register on the HPLMN.
At power on scenario and if the UE was last registered on the National Roaming Partner, then no HPLMN search is permitted for the first 2 minutes after registration (again according to 23.122 [2]).
Consideration should be given to reducing this time to 1 minute, if feasible.
Ideally the UE should be allowed to reselect any available higher priority PLMN (e.g. the HPLMN) possible and not be forced to return to the RPLMN if a higher priority PLMN is available. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.12 Network selection in border areas | A problem exists for mobile users when commuting across national borders. Whilst manual network selection may be used to ensure that the user can select the HPLMN / EHPLMN, many users use Automatic Selection mode; and the ME is only permitted to select PLMNs of a higher priority within the same country in automatic mode. This leads to the situation that, having crossed back into its home country and within HPLMN coverage, an ME might remain camped on the VPLMN in the adjacent territory.
As a consequence, the user will be charged international roaming rates for all calls made or received until such time as he either
(a) moves out of VPLMN coverage or
(b) manually selects the HPLMN.
Note: The power cycling the ME does not solve the problem because the mobile will look for the RPLMN. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 6.13 Multiple EHPLMNs | Currently the TS 23.122 [2] allows an operator to define a list of EHPLMNs which may have different priority. Thus under automatic network selection it is possible to for one of the constituent networks to be given priority over another. Manual network selection only allows the highest EHPLMN to be displayed to the subscriber even when there are other EHPLMNs. The subscriber is not allowed to select any other EHPLMN. If the highest priority EHPLMN is not available while the user has selected it in the manual network selection, UE will select the highest available EHPLMN without interaction with the user.
Another choice is to make the user aware, during a manual network selection attempt that more than one EHPLMN has been found and allow the user to select one over the other. However, the impact on user experience should be evaluated carefully.
Since each choice is expected by different operators, there should be a mechanism to fulfil both requirements. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 7 Impact of technology changes | This section looks at how technology changes can impact the current Network Selection mechanism. When a new technology has been introduced typically one of two options are taken:
- Replication of the network selection principles.
Replicating the user experience provides the same over all "look and feel" to the user, however from an operators perspective it is possible to use a different set of variables to assist the UE in choosing the most appropriate network. There is also the opportunity to provide some additional control, however the experience to the user should be technology independent. Current examples include the ability to define a different set of preferred PLMNS for I-WLAN
- Do nothing to the network selection principles.
Some technology changes do not allow replication of the user experience. Core network technologies such as CAMEL, IMS, etc fall into this category. In these instances the UE is not aware of the capabilities of the core network when it performs a scan of the radio broadcast information.
As technology changes are introduced there is the possibility that the “ideal” network for a given user may not correspond to the preferred network as indicated by the HPLMN currently on the (U)SIM. In order to ensure the best user experience operators may need to regularly update their preferred lists, and also verify that all users receive those updates. The “ideal” network may also change from user to user depending on the services that she decides to use.
This becomes a more complex model as more technology changes are introduced into the 3GPP system. For example an operator may have roaming services based upon CAMEL with one operator in the visited country but only have GPRS roaming with one of the other operators. The UE should be directed to the best network at the time for the user at that time taking into consideration variables such as service(s) availability, cost etc. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 7.1 Multi-provider environments | The network selection procedures in TS 22.011 [1] focuses on PLMN selection defined in Section 3.2.2.1 as “an UE based procedure, whereby candidate PLMNs are chosen, one at a time, for attempted registration”.
Upcoming usage scenarios may require taking into consideration for network selection where there are different ownerships of the Radio Access Network (RAN), the Core Network (CN) and Service Network (SN). For example, taking the I-WLAN case, at a particular location several WLAN access networks could provide access to the HPLMN services. Figure 1 depicts the generic situation where there are multiple RANs, CNs and Service Networks that all have different business relationships:
Figure 1: Example PLMN business relationships
Each of the RANs and CNs has different capabilities e.g. HSPDA, EDGE, CAMEL. Thus if a UE is turned on and performs an initial scan or does a background scan there is need to choose a RAN / CN that provides the services that the UE wants to use.
Also given that there could be multitude of RANs in different technologies the coverage area of each RAN technology would be different. It could be advantageous that the UE is aware of the RANs / CN combinations that are available to it at any given time. Possible solution approaches could be, for example, the definition of specific background scan timers for different RATs. The UE could also determine the capabilities of the RATs and corresponding connecting CNs.
Given that multiple technologies may be available in a given location, it would be useful to provide a single mechanism for identifying preferences.
For example, the HPLMN may wish to give the highest priority to Operator A being accessed via the I-WLAN Access System over Operator B via 2G. If Operator A cannot be accessed via that I-WLAN, then the second priority, Operator B (possibly with a preferred RAT) will be attempted.
Furthermore, in certain situations it could be advantageous for a PLMN to be able to instruct a terminal to gain access over a particular RAT and/or intermediate core network. To this avail, appropriate system reselection mechanisms could be of interest. |
e6f57f912523fc54acca00719a764ae8 | 22.811 | 8 Conclusions | This Technical Report has reviewed current practice with regard to Network Selection Principles and considered the impact of some future developments within 3GPP on the existing mechanisms. It is concluded that it would be beneficial to consider enhancements to the current specifications in a number of areas.
1) A number of concerns over the time the network selection process takes have been raised, especially in the cases where UE's support multiple bands and multiple modes.
- Ideal performance targets have been identified as: less than 20 seconds to select a PLMN in the case where the RPLMN is not available and less than 5 seconds in the case where the RPLMN is available.
- Methods to improve the time taken for a UE to regain service and hence avoid time consuming searches of all the bands in which a UE can operate should be considered.
2) There is a requirement to provide the tools to a network operator to allow them to offer their customers the best possible experience when roaming into other networks. This includes the ability of the home operator to control their user’s selection of visited network from the perspective of service provisioning, access technology, terminal capability, and so on. Such tools include
- The ability for the HPLMN to dynamically direct a UE to select a different VPLMN.
- The ability to prevent users from selecting specific PLMNs.
- Enhancements to Manual Network Selection to provide the user with additional information to assist their choice.
3) To allow Network Operators to dynamically distribute their roaming customers across multiple VPLMNs in a given country.
4) Practical experience from the implementation of National Roaming has highlighted a number of areas where enhancements to the 3GPP specifications could be considered.
- In the case where a UE is registered to a national roaming partner and loses coverage, the UE will attempt to select the RPLMN (the national roaming partner). In some cases, but not all, it is desirable to register to the HPLMN if it has become available.
- In the case where a UE may oscillate between two PLMNs.
5) The performance of PLMN selection in border areas should be improved, as it has been noted that network operators are advising their customers to manually select the HPLMN to avoid accidental roaming.
6) In the course of the development of the TR some additional areas for enhancements to the 3GPP specifications have been identified. These are:
- It may be beneficial to standardise a minimum size of list to be supported by the ME and any conclusion should support the normal operational requirements of operators
- The use of the Refresh command should be reviewed to allow the subscriber’s operator to update information, used by the UE, in the most optimum manner possible.
- At power on, in manual mode, if the RPLMN is not found, but the HPLMN is available then the UE should automatically register with it.
- It should be possible for the user to set a preference for either manual or automatic network selection on power-up
In any future developments of the 3GPP specifications backwards compatibility is essential and the utilisation of entities from different 3GPP releases should also be considered as detailed in clause 5.3.
Annex A:
Change history
Change history
TSG SA#
SA Doc.
SA1 Doc
Spec
CR
Rev
Rel
Cat
Subject/Comment
Old
New
WI
15/07/05
S1-29
S1-050917
22.811
-
-
Rel-7
-
Raised to version 1.0.0
1.0.0
NSP
13/10/05
S1-050983
22.811
Rel-7
Updated to version 1.1.0 following joint meeting with CT1.
1.0.0
1.1.0
NSP
25/10/05
22.811
Rel-7
Updated to incorporate text from S1-050984
1.1.0
1.2.0
NSP
27/10/05
22.811
Rel-7
Updated to incorporate material agreed during NSP SWG meeting at SA1#30
1.2.0
1.3.0
NSP
27/10/05
22.811
Rel-7
Updated to 2.0.0 for presentation to SA #30
1.3.0
2.0.0
NSP
SP-30
SP-050758
S1-051217
22.811
Rel-7
Approved for Rel-7 at SA #30
2.0.0
7.0.0
NSP
SP-31
SP-060032
S1-060326
22.811
0001
-
Rel-7
F
Clarification of using EHPLMN for Network Selection Principles
7.0.0
7.1.0
NSP-CR
SP-32
SP-060312
S1-060631
22.811
0002
-
Rel-7
F
Simplification of the scope of TR 22.811
7.1.0
7.2.0
NSP-CR |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 1 Scope | The purpose of this document is to contain the updated Work Item Descriptions (WIDs) and capture status of all SA5 work items of the current 3GPP Release in order for the group to get an overview of current ongoing work.
This TR is used as a mean to provide input to the complete 3GPP work plan that is handled by MCC.
Status list of Work items can be found at the end of the present document.
List of SA5 Release 7 specifications can be found at the end of the present document.
The SA5 Release 7 work has been started in September 2005 and finished in June 2007. |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] http://www.3gpp.org/ftp/Information/WORK_PLAN/
[2] http://www.3gpp.org/ftp/Information/WI_Sheet/ |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 3 Operations, Administration, Maintenance & Provisioning - OAM&P | Feature: Operations, Administration, Maintenance & Provisioning (OAM7) Unique_ID: 35041
BB: Network Infrastructure Management (OAM7-NIM) Unique_ID: 35042
Technical Specification Group Services and System Aspects TSGS#28(05)0302
Meeting #28, Quebec, CANADA, 06-08 June 2005
Source: SA5 (Telecom Management)
Title: WID WT Enhance NRM to accommodate NGN (IMS as basis of the Next Generation Network)
Document for: Approval
Agenda Item: 7.5.3
3GPP TSG-SA5 (Telecom Management) S5-050280
Meeting #42, Montreal, CANADA, 09 - 13 May 2005
Work Item Description
Title:
WT Enhance NRM to accommodate NGN (IMS as basis of the Next Generation Network) Unique_ID: 35044
Acronym: OAM7-NIM
1 3GPP Work Area
X
Radio Access
X
Core Network
Services
2 Linked work items
OAM&P (Operations, Administration, Maintenance & Provisioning) (Feature: OAM7)
WI
Unique_ID
OAM7
35041
Network Infrastructure Management (BB: OAM7-NIM)
WI
Unique_ID
OAM7-NIM
35042
3 Justification
The IMS has been adopted as the basis of the Next Generation Network (NGN).
It is proposed to enhance the 3GPP NRM in TS 32.63x Configuration Management (CM); Core Network Resources Integration Reference Point (IRP) - to accommodate any additional requirements identified.
4 Objective
In liaison with other groups (e.g. ETSI TISPAN, TeleManagement Forum (TMF), ITU-T SG4, Multiservice Switching Forum (MSF) to enhance the Core Network Resource Model to support the requirements of NGN Release 1 and Voice over IP (VoIP).
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
None |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 9 Impacts | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
No
X
X
X
Don't know
X |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 10 Expected Output and Time scale (to be updated at each plenary) | New specifications
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
NA
Affected existing specifications
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
32.240
TBD
Add new principles on chargeable features, if needed
SA#36
Jun 2007
Charging architecture and principles
32.272
TBD
Add new message flow description and CDR parameters
SA#36
Jun 2007
Push-to-talk over Cellular (PoC) charging
32.299
TBD
Add new AVPs (an extension of the PoC information AVP is needed)
SA#36
Jun 2007
Diameter charging applications
32.298
TBD
Add new CDR parameter
SA#36
Jun 2007
Charging Data Record (CDR) parameter description
11 Work item rapporteur(s)
Gerald GÖRMER ([email protected])
13 Work item leadership
SA5
13 Supporting Companies
Cingular, Ericsson, Huawei, Nokia, Orange, Siemens, Telefonica
14 Classification of the WI (if known)
Study Item (no further information required)
Feature (go to 14a)
Building Block (go to 14b)
X
Work Task (go to 14c) |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 14c The WI is a Work Task: parent Building Block | • SA5's Charging Management small Enhancements (UID 320007, CH7) |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 32.307 Notification IRP SOAP SS | |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 32.317 Generic IRP Management SOAP SS | |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 32.607 Basic CM IRP SOAP SS | 32.665 Kernel CM IRP XML definitions |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 32.667 Kernel CM IRP SOAP SS | 5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
None |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 3.2 Principle of radio channel power monitoring | The transport channels and physical channels have mapping relations. The following is mapping of transport channels onto physical channels.
25.211
From the figure above, the mapping from transport channel to physical channel is mostly one to one. So, in most cases, we just need to monitor the physical channels.
It is proposed to monitor the power of the following channels:
• Transport channel: FACH、PCH
• Uplink physical channel: DPCH (DPDCH/DPCCH)、PRACH
• Downlink physical channel: DPCH (DPDCH/DPCCH)、CPICH、P-CCPCH、S-CCPCH、SCH、AICH、PICH
In the above channel list, DPCH、PRACH、PDSCH are involved in power control. So, we should record the maximum and mean value of power level for those channels as performance measurements. For other channels, only the configured value will be retrieved.
The following channel power parameters are already present in TS 32.642:
• primaryCpichPower(1)
• maximumTransmissionPower(2)
• bchPower(3)
• primaryCcpchPower(4)
• dlpchPower(5)
• schPower(6)
The following parameters should be added:
• fachPower (7)
• dpchPower(8)
• prachPower (9)
• sccpchPower(10)
• pdschPower(11)
• pichPower(12)
• aichPower(13)
(8)、(9)、(11) are channels which are involved in power control.
4 Objective
Add (7) (10) (12) (13) to TS 32.642
Add (8) (9) (11) to TS 32.405
Update UTRAN Network Resource Model (NRM) Requirements (if needed)
Update UTRAN Network Resource Model (NRM)
Update UTRAN NRM CORBA Solution Set (SS)
Update UTRAN NRM CMIP Solution Set (SS)
Update UTRAN NRM XML format definition
Add UTRAN channel Measurements
5 Service Aspects
None
6 MMI-Aspects
None
7 Charging Aspects
None
8 Security Aspects
None |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 14b The WI is a Building Block: parent Feature | |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 4 Charging Management | WT Charging aspects of FBI for PacketCable Unique_ID: 7032
Acronym: FBI-PCBL-CH
Technical Specification Group Services and System Aspects TSGS#31(06)0145
Meeting #31, 13 - 16 March 2006, Sanya, China
Source: SA WG2
Title: Revised WID: "System enhancements for fixed broadband access to IMS".
Document for: Approval
Agenda Item: 10.17
___________________________________________________________________________
Work Item Description
Title: System enhancements for fixed broadband access to IMS
1 3GPP Work Area
Radio Access
X
Core Network
X
Services
2 Linked work items
• QoS Improvements (32016)
• FS on Dynamic Policy control enhancements for end-to-end QoS (32017)
• WLAN - UMTS Interworking (32018)
• QoS Improvements
◦ Gq interface specification for Dynamic Policy control enhancements (13016)
• Interworking aspects and migration scenarios for IPv4 based IMS Implementations (32062)
• Interoperability and Commonality between IMS using different "IP-connectivity Networks“ (32061)
• IP flow based bearer level charging (32030)
3 Justification
The standardization of fixed broadband access to IMS is addressed by a number of SDOs, e.g. ETSI and ITU-T in the framework of next generation networking (NGN).
During the joint 3GPP/TISPAN workshop it was agreed that ETSI/TISPAN will define NGN session control using IMS as a platform. This will embed IMS as the framework for advanced multimedia services for many types of operators. It is expected that some enhancements of the 3GPP specifications will be needed for IMS to enable external organizations to reuse IMS as a platform for session control for systems with fixed broadband access.
This work item studies and intends to implement the necessary enhancements to IMS within 3GPP for fixed broadband access, as seen appropriate from a 3GPP system perspective. Note that 3GPP SA and CN intend to evaluate whether those enhancements are expected to be generally useful to IMS from a 3GPP perspective when deciding to incorporate them.
During the SA#30 it was then agreed to incorporate changes on fixed broadband access to IMS stemming from PacketCable2.0 requirements also within this work item. Work to address PacketCable 2.0 requirements will not delay or impact TISPAN related work.
4 Objective
The objective of this work item is to provide possible IMS architectural enhancements necessary in the 3GPP system to support fixed broadband access to IMS, (e.g. as stated in ETSI TISPAN release 1 and PacketCable 2.0). Where there are impacts to the IMS core, 3GPP intends to develop specifications or changes to specifications necessary to enable reuse of IMS as a platform for session control in systems with fixed broadband access. Any enhancements shall not break the integrity of the 3GPP system.
The requirements for fixed broadband access to IMS, received from other 3GPP OPs and MRPs, shall be considered as well to study the impacts on IMS.
This work item is limited to the current scope of the IMS, i.e. session control (e.g. mobility management is not included).
5 Service Aspects
For service requirements related to fixed broadband access to IMS, see ETSI TR 01016: TISPAN_NGN1; Release 1: Release Definition.
Service requirements impacting 3GPP service requirements within the scope of this Work Item have to be analyzed by SA1. Any new requirements deemed applicable to 3GPP system need to be captured by the SA1 service requirements.
SA1 and CN will be involved to ensure consistent stage 1, 2, 3 specifications and to ensure there are no conflicting requirements.
6 MMI-Aspects
No MMI aspects are expected in the context of this WI.
7 Charging Aspects
For the charging aspects of fixed broadband access, see ETSI TR 01016: TISPAN_NGN2; Release 1: Release Definition.
Offline charging aspects related to fixed broadband access, including cable access, are within the scope of this work item.
8 Security Aspects
For the security aspects of fixed broadband access, see ETSI TR 01016: TISPAN_NGN3; Release 1: Release Definition.
Security aspects impacting 3GPP security architecture and mechanisms within the scope of this Work Item have to be analyzed by SA3. |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 14a The WI is a Feature: List of building blocks under this feature | |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 5 Status list of Work items | This list reflects work items ongoing, completed, stopped or moved to Rel-8.
Feature: Operations, Administration, Maintenance & Provisioning (OAM7) Unique_ID: 35041 5
BB: Network Infrastructure Management (OAM7-NIM) Unique_ID: 35042 5
WT Enhance NRM to accommodate NGN (IMS as basis of the Next Generation Network) Unique_ID: 35044 5
WT Co-operative Element Management interface (CO-OP) Unique_ID: 35046 7
WT Network Management (NM) Itf-N performance criteria Unique_ID: 35047 9
WT Delta synchronization between IRP Manager and IRP Agent Unique_ID: 35048 11
WT Subscription Management (SuM) IRP Solution Sets Unique_ID: 35049 13
WT Integration Reference Point (IRP) Security Management Unique_ID: 35050 15
WT Partial suspension of Itf-N during maintenance/testing Unique_ID: 35052 17
WT Backward and Forward Compatibility of IRP systems Unique_ID: 35064 19
WT Repeater Network Resource Model (NRM) Definition Unique_ID: 35071 21
WT UTRAN radio channel power monitoring Unique_ID: 35072 23
WT Notification XML Schema Unique_ID: 340009 26
BB: Performance Management (OAM7-PM) Unique_ID: 35043 29
WT Performance measurements definition for CN CS Unique_ID: 35057 29
WT Enhancement UTRAN performance measurements definition Unique_ID: 35058 31
WT Add TDD specific counters in Performance measurement definitions Unique_ID: 35059 33
WT ATM bearer network Performance measurements Unique_ID: 35060 35
WT Performance measurements definition for IMS Unique_ID: 35069 37
WT HSDPA performance measurements Unique_ID: 35073 39
BB Trace Management Unique_ID: 35039 41
WT End-to-end Service Level tracing for IMS Unique_ID: 35040 43
WT IRP for Subscriber and Equipment Trace Management Unique_ID: 35063 45
Feature: OAM&P (OAM7-Studies) Unique_ID: 35075 48
BB: Network Infrastructure Management Unique_ID: 35076 48
WT Study of SOAP/HTTP Integration Reference Point (IRP) Solution Sets Unique_ID: 35066 49
WT Study of Interface-N Implementation Conformance Statement (ICS) template Unique_ID: 35067 51
WT Study of Integration Reference Point (IRP) Information Model Unique_ID: 35068 53
4 Charging Management 55
WT Charging aspects of FBI for PacketCable Unique_ID: 7032 55
WT Charging aspects of PCC Unique_ID: 7033 58
WT Charging aspects of VCC Unique_ID: 35079 60
WT Charging aspects of ServID Unique_ID: 7035 63
WT Alternate Charged Party (ACP) for IMS Unique_ID: 320008 66
WT SA5 Charging harmonization for NGN between 3GPP and ATIS-TMOC Unique_ID: 330011 69
WT Align 3GPP Charging with OMA PoC Enabler Release 2.0 Unique_ID: 330004 71 |
6f66d26dac8f429a6caa37fbbb67038b | 30.817 | 6 List of SA5 Release 7 specifications | Type
Number
Title
Rapporteur
TR
30.817
Telecommunication management; Project scheduling and open issues for SA5, Release 7
ZOICAS, Adrian
TS
32.101
Telecommunication management; Principles and high level requirements
TOCHE, Christian
TS
32.102
Telecommunication management; Architecture
BERGGREN, Tommy
TS
32.111-1
Telecommunication management; Fault Management; Part 1: 3G fault management requirements
TRUSS, Michael
TS
32.111-2
Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)
TRUSS, Michael
TS
32.111-3
Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TSE, Edwin
TS
32.111-5
Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions
TRUSS, Michael
TS
32.140
Telecommunication management; Subscription Management (SuM) requirements
TOCHE, Christian
TS
32.141
Telecommunication management; Subscription Management (SuM) architecture
ABA, Istvan
TS
32.150
Telecommunication management; Integration Reference Point (IRP) Concept and definitions
TOCHE, Christian
TS
32.151
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template
TOVINGER, Thomas
TS
32.152
Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire
POLLAKOWSKI, Olaf
TS
32.154
Telecommunication management; Backward and Forward Compatibility (BFC); Concept and definitions
PETERSEN, Robert
TS
32.171
Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
DAI, Peng
TS
32.172
Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
DAI, Peng
TS
32.175
Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definition
ABA, Istvan
TS
32.240
Telecommunication management; Charging management; Charging architecture and principles
GOERMER, Gerald
TS
32.250
Telecommunication management; Charging management; Circuit Switched (CS) domain charging
GOERMER, Gerald
TS
32.251
Telecommunication management; Charging management; Packet Switched (PS) domain charging
GOERMER, Gerald
TS
32.252
Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging
ALEXANDER, Benni
TS
32.260
Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging
ALEXANDER, Benni
TS
32.270
Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging
GOERMER, Gerald
TS
32.271
Telecommunication management; Charging management; Location Services (LCS) charging
BIBAS, Alain
TS
32.272
Telecommunication management; Charging management; Push-to-talk over Cellular (PoC) charging
GOERMER, Gerald
TS
32.273
Telecommunication management; Charging management; Multimedia Broadcast and Multicast Service (MBMS) charging
NEAL, Adrian
TS
32.274
Telecommunication management; Charging management; Short Message Service (SMS) charging
WONG, Gavin
TS
32.295
Telecommunication management; Charging management; Charging Data Record (CDR) transfer
GOERMER, Gerald
TS
32.296
Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces
GOERMER, Gerald
TS
32.297
Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer
MAZZARELLA, Nick
TS
32.298
Telecommunication management; Charging management; Charging Data Record (CDR) parameter description
GOERMER, Gerald
TS
32.299
Telecommunication management; Charging management; Diameter charging applications
ALEXANDER, Benni
TS
32.300
Telecommunication management; Configuration Management (CM); Name convention for Managed Objects
TOVINGER, Thomas
TS
32.301
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements
TRUSS, Michael
TS
32.302
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)
TSE, Edwin
TS
32.303
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
POLLAKOWSKI, Olaf
TS
32.305
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): eXtensible Markup Language (XML) definition
POLLAKOWSKI, Olaf
TS
32.307
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Simple Object Access Protocol (SOAP) Solution Set (SS)
DAI, Peng
TS
32.311
Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements
TSE, Edwin
TS
32.312
Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)
TSE, Edwin
TS
32.313
Telecommunication management; Generic Integration Reference Point (IRP) management; Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TSE, Edwin
TS
32.317
Telecommunication management; Generic Integration Reference Point (IRP) management; Simple Object Access Protocol (SOAP) Solution Set (SS)
DAI, Peng
TS
32.321
Telecommunication management; Test management Integration Reference Point (IRP): Requirements
POLLAKOWSKI, Olaf
TS
32.322
Telecommunication management; Test management Integration Reference Point (IRP): Information Service (IS)
POLLAKOWSKI, Olaf
TS
32.323
Telecommunication management; Test management Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TSE, Edwin
TS
32.325
Telecommunication management; Test management Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
YANG, Li
TS
32.331
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Requirements
TRUSS, Michael
TS
32.332
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Information Service (IS)
TRUSS, Michael
TS
32.333
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TSE, Edwin
TS
32.335
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): eXtensible Markup Language (XML) solution definitions
TRUSS, Michael
TS
32.341
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Requirements
TRUSS, Michael
TS
32.342
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)
LI, Yewen
TS
32.343
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
LI, Yewen
TS
32.345
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
YANG, Li
TS
32.351
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP): Requirements
LI, Yewen
TS
32.352
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP): Information Service (IS)
LI, Yewen
TS
32.353
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
LI, Yewen
TS
32.354
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
SUERBAUM, Clemens
TS
32.361
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP): Requirements
LI, Yewen
TS
32.362
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP): Information Service (IS)
LI, Yewen
TS
32.363
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
LI, Yewen
TS
32.365
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
YANG, Li
TS
32.371
Telecommunication management; Security Management concept and requirements
YANG, Li
TS
32.372
Telecommunication management; Security services for Integration Reference Point (IRP): Information Service (IS)
YANG, Li
TS
32.373
Telecommunication management; Security services for Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution
YANG, Li
TS
32.375
Telecommunication management; Security services for Integration Reference Point (IRP): File integrity solution
YANG, Li
TS
32.381
Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP): Requirements
SUERBAUM, Clemens
TS
32.382
Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP): Information Service (IS)
SUERBAUM, Clemens
TS
32.383
Telecommunication management; Security Services for Integration Reference Points (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
SUERBAUM, Clemens
TS
32.385
Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
SUERBAUM, Clemens
TS
32.391
Telecommunication management; Delta synchronization Integration Reference Point (IRP): Requirements
SUERBAUM, Clemens
TS
32.392
Telecommunication management; Delta synchronization Integration Reference Point (IRP): Information Service (IS)
SUERBAUM, Clemens
TS
32.393
Telecommunication management; Delta synchronization Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
SUERBAUM, Clemens
TS
32.395
Telecommunication management; Delta synchronization Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
SUERBAUM, Clemens
TS
32.401
Telecommunication management; Performance Management (PM); Concept and requirements
HÜBINETTE, Ulf
TS
32.403
Telecommunication management; Performance Management (PM); Performance measurements - UMTS and combined UMTS/GSM
TOCHE, Christian
TS
32.404
Telecommunication management; Performance Management (PM); Performance measurements - Definitions and template
LI, Yewen
TS
32.405
Telecommunication management; Performance Management (PM); Performance measurements Universal Terrestrial Radio Access Network (UTRAN)
WANG, Lan
TS
32.406
Telecommunication management; Performance Management (PM); Performance measurements Core Network (CN) Packet Switched (PS) domain
LI, Yewen
TS
32.407
Telecommunication management; Performance Management (PM); Performance measurements Core Network (CN) Circuit Switched (CS) domain
WANG, Lan
TS
32.408
Telecommunication management; Performance Management (PM); Performance measurements Teleservice
LI, Yewen
TS
32.409
Telecommunication management; Performance Management (PM); Performance measurements IP Multimedia Subsystem (IMS)
YU, Chengzhi
TS
32.411
Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Requirements
HÜBINETTE, Ulf
TS
32.412
Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Information Service (IS)
LI, Yewen
TS
32.413
Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
LI, Yewen
TS
32.415
Telecommunication management; Performance Management (PM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
YANG, Li
TS
32.421
Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements
TOCHE, Christian
TS
32.422
Telecommunication management; Subscriber and equipment trace; Trace control and configuration management
TOCHE, Christian
TS
32.423
Telecommunication management; Subscriber and equipment trace; Trace data definition and management
TOCHE, Christian
TS
32.432
Telecommunication management; Performance measurement: File format definition
TOCHE, Christian
TS
32.435
Telecommunication management; Performance measurement: eXtensible Markup Language (XML) file format definition
TOCHE, Christian
TS
32.436
Telecommunication management; Performance measurement: Abstract Syntax Notation 1 (ASN.1) file format definition
TOCHE, Christian
TS
32.441
Telecommunication management; Trace Management Integration Reference Point (IRP): Requirements
BÓDOG, Gyula
TS
32.442
Telecommunication management; Trace Management Integration Reference Point (IRP): Information Service (IS)
BÓDOG, Gyula
TS
32.443
Telecommunication management; Trace Management Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
BÓDOG, Gyula
TS
32.445
Telecommunication management; Trace Management (Trace) Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
BÓDOG, Gyula
TS
32.600
Telecommunication management; Configuration Management (CM); Concept and high-level requirements
TOVINGER, Thomas
TS
32.601
Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements
PIRT, Trevor
TS
32.602
Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)
TOVINGER, Thomas
TS
32.603
Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TSE, Edwin
TS
32.607
Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Simple Object Access Protocol (SOAP) Solution Set (SS)
DAI, Peng
TS
32.611
Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements
PIRT, Trevor
TS
32.612
Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)
PIRT, Trevor
TS
32.613
Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
PIRT, Trevor
TS
32.615
Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
TOCHE, Christian
TS
32.621
Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Requirements
PIRT, Trevor
TS
32.622
Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)
TOVINGER, Thomas
TS
32.623
Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
PIRT, Trevor
TS
32.625
Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
TOCHE, Christian
TS
32.631
Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP): Requirements
PIRT, Trevor
TS
32.632
Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP): Network Resource Model (NRM)
TOCHE, Christian
TS
32.633
Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TOCHE, Christian
TS
32.635
Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
TOCHE, Christian
TS
32.641
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements
PIRT, Trevor
TS
32.642
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)
PETERSEN, Robert
TS
32.643
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
PIRT, Trevor
TS
32.645
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
TOCHE, Christian
TS
32.651
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Requirements
PIRT, Trevor
TS
32.652
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)
PETERSEN, Robert
TS
32.653
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
PIRT, Trevor
TS
32.655
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
TOCHE, Christian
TS
32.661
Telecommunication management; Configuration Management (CM); Kernel CM; Requirements
TOVINGER, Thomas
TS
32.662
Telecommunication management; Configuration Management (CM); Kernel CM; Information service (IS)
TOVINGER, Thomas
TS
32.663
Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TSE, Edwin
TS
32.665
Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions
YANG, Li
TS
32.667
Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP): Simple Object Access Protocol (SOAP) Solution Set (SS)
DAI, Peng
TS
32.671
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Requirements
POLLAKOWSKI, Olaf
TS
32.672
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Information Service (IS)
POLLAKOWSKI, Olaf
TS
32.673
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
PIRT, Trevor
TS
32.675
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
POLLAKOWSKI, Olaf
TS
32.682
Telecommunication management; Inventory Management (IM) Integration Reference Point (IRP); Information Service (IS)
TOCHE, Christian
TS
32.683
Telecommunication management; Inventory Management (IM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TOCHE, Christian
TS
32.690
Telecommunication management; Inventory Management (IM): Requirements
TOCHE, Christian
TS
32.691
Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP): Requirements
TOCHE, Christian
TS
32.692
Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP): Network Resource Model (NRM)
TOCHE, Christian
TS
32.695
Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP): Bulk Configuration Management (CM) eXtensible Markup Language (XML) file format definition
TOCHE, Christian
TS
32.711
Telecommunication management; Configuration Management (CM); Transport Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
TOCHE, Christian
TS
32.712
Telecommunication management; Configuration Management (CM); Transport Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
TOCHE, Christian
TS
32.713
Telecommunication management; Configuration Management (CM); Transport Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TOCHE, Christian
TS
32.715
Telecommunication management; Configuration Management (CM) Transport Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
TOCHE, Christian
TS
32.721
Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP): Requirements
LIANG, Shuangchun
TS
32.722
Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP): information Service (IS)
LIANG, Shuangchun
TS
32.723
Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
LIANG, Shuangchun
TS
32.725
Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
LIANG, Shuangchun
TS
32.731
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
TOCHE, Christian
TS
32.732
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
TOCHE, Christian
TS
32.733
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TOCHE, Christian
TS
32.735
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
TOCHE, Christian
TS
32.741
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
LI, Yewen
TS
32.742
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
LI, Yewen
TS
32.743
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
LI, Yewen
TS
32.745
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
LI, Yewen
TR
32.806
Telecommunication management; Application guide for use of Integration Reference Points (IRPs) on peer-to-peer (p2p) interface
TRUSS, Michael
TR
32.808
Telecommunication management; Study of Common Profile Storage (CPS) Framework of User Data for network services and management
ABA, Istvan
TR
32.809
Telecommunication management; Feasibility study of XML-based (SOAP/HTTP) IRP solution sets
DUGUAY, Jean
TR
32.810
Telecommunication management; Information model Integration Reference Point (IRP) Study
PIRT, Trevor
TR
32.811
Telecommunication management; Itf-N performance criteria: Requirements
LI, Yewen
TR
32.812
Telecommunication management; Itf-N Implementation Conformance Statement (ICS) template
LI, Yewen
TR
32.814
Telecommunication management; UTRAN and GERAN Key Performance Indicators (KPI)
TRUSS, Michael
TS
52.008
Telecommunication management; GSM subscriber and equipment trace
TOCHE, Christian
TS
52.402
Telecommunication management; Performance Management (PM); Performance measurements - GSM
TOCHE, Christian
Annex A:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
Nov 2005
S5-44
S5-050529
--
--
Initial draft agreed by SA5#44
--
--
Dec 2005
SP-30
SP-050734
--
--
Submitted to SA#30 for Information
--
0.0.1
Mar 2006
SP-31
SP-060073
--
--
Converted to TR 32.807. Submitted to SA#31 for Information
0.0.1
0.0.2
Apr 2006
S5-46
S5-060119
--
--
Submitted to SA5#46 for Updating
0.0.2
0.0.3
May 2006
S5-47
S5-060212
--
--
Submitted to SA5#47 for Updating
0.0.3
0.0.4
May 2006
S5-47
S5-060212
--
--
Post SA5#47 Updates
0.0.4
0.0.5
Jun 2006
SP-32
S5-060601
--
--
Post SA#32 Updates
0.0.5
0.0.6
Jul 2006
S5-48
S5-060814
--
--
Post SA5#48 Updates
0.0.6
0.0.7
Oct 2006
SP-33
S5-061308
--
--
Post SA#33 Updates
0.0.7
0.0.8
Dec 2006
SP-34
--
--
--
Post SA#34 Updates
0.0.8
0.0.9
Mar 2007
SP-35
S5-070413
--
--
Post SA#35 Updates
0.0.9
0.0.10
Apr 2007
S5-52
S5-070532
--
--
Pre S5#52 Updates
0.0.10
0.0.11
Jun 2007
SA-32
S5-071111
--
--
Post SA#36 Updates (freezing of 3GPP Release 7)
0.0.11
0.0.12
Jul 2007
S5-55
S5-071429
--
--
Post S5#54 Updates
0.0.12
0.0.13
Jun 2008
SP-40
SP-080273
--
--
Submitted to SA#40 for Information + Approval
1.0.0
7.0.0 |
997ad2510cb826711e63f644e1d2617f | 23.873 | 1 Scope | The scope of this Technical Report (TR) is to capture the results of a feasibility study on how to introduce a clear separation of transport and control functions in the PS CN domain, with minimum impacts on the reference logical architecture for R’00.
With this separation in view, functional elements of the PS CN domain that provide both significant control and transport functions may be decomposed into two separate functional entities: one entity taking care of the control functionality and an other entity handling the payload transport. An exact distribution of the functions currently supported by a single functional entity between new functional entities and other network entities will be defined as the result of this feasibility study, if necessary.
A standard control protocol should be used between the control and transport entities, if applicable, e.g. H.248. The required functionality, e.g. extensions to H.248 or any other protocol which may be chosen for this task, would have to be defined and standardised within 3GPP. This TR will identify and define these extensions, and extensions to other interfaces if applicable.
More generally, the aim of this TR is to identify and strive to solve all issues introduced by such evolution of the PS CN domain. At the end of the feasibility study, the remaining open issues will be reported and their importance will be assessed. An analysis of the benefits and drawbacks of separating the control and transport functions in the PS CN domain will also be performed. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 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. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3G TS 23.060: “General Packet Radio Service (GPRS); Service Description; Stage 2”.
[2] 3G TS 23.078: “Customised Applications for Mobile Network Enhanced Logic (CAMEL) Phase 3 – Stage 2”.
[3] 3G TR 23.821: “Architecture Principles for Release 2000”.
[4] 3G TR 23.923: “Combined GSM and Mobile IP Mobility Handling in UMTS IP CN”
[5] 3G TS 29.060: “ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface”.
[6] 3G TS 32.015: “Telecommunications Management; Charging and billing; 3G call and event data for the Packet Switched (PS) domain”.
[7] 3G TS 33.107: “3G Security; Lawful Interception Architecture and Functions”. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 3 Symbols and Abbreviations | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 3.1 Symbols | For the purposes of the present document, the following symbols apply:
Mp Interface between an SGSN server and a PS-MGW. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
cSGSN Control Serving GPRS Support Node
PS-MGW Packet Switching Media Gateway
SGSN server Serving GPRS Support Node server
xGGSN Extended Gateway GPRS Support Node |
997ad2510cb826711e63f644e1d2617f | 23.873 | 4 Introduction | This technical report (TR) was created in order to study a clear separation of transport and control functions in the PS CN domain, with minimum impacts on the reference architecture for R’00. As different approaches can be considered for achieving this goal, the following sections describe and analyse a few alternatives that have been identified as the most viable. The summary will then compare the different alternatives and formulate a conclusion about which alternative is proposed to be adopted for release 2000. This will constitute the base for the decision to be taken by S2.
NOTE: This feasibility study has been concluded without reaching consensus on which alternative to recommend and consequently none of them is retained for standardisation. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 5 Reference Logical Architecture | This chapter describes a reference architecture which we use as a basis for the evolved architecture.
The full view of Release 2000 architecture (as specified in 3G TR 23.821) is the reference logical architecture for this TR and is provided in figure 1.
Figure 1: Reference logical architecture |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6 Alternative 1: SGSN Server – PS Media Gateway Approach | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.1 Introduction | In the PS CN domain the node that comprises the more user and control plane functions is undoubtedly the SGSN. It is therefore judicious to consider the SGSN as the primary target for a split of its user and control plane functions.
This approach consists in decomposing the SGSN into an SGSN server and a PS media gateway (PS-MGW). The SGSN server handles all the signalling interfaces (Gs, Gr, Gd, etc) as well as the GTP-C protocol, whereas the PS-MGW handles the user traffic, in particular the GTP-U protocol.
With this approach, the total load solely supported by the SGSN in the R’99 architecture is distributed over two different network elements. The dynamic allocation of PS-MGW resources should lead to an increase in the ability to better utilise the total network capacity.
The functional allocation between SGSN server and PS-MGW can be summarised as follows.
Functions of the SGSN server:
- Session Management
- Mobility Management
- GTP-C termination
- MAP termination
- RANAP termination
- CDR handling
- Provision of Intercept Related Information (Lawful Interception)
- Media gateway management (registration, selection)
- CAP termination
- PS Media Gateway Control
- etc.
Functions of the PS-MGW:
- GTP-U termination
- Quality of Service Provision
- Collection of data for charging or detection of data threshold if required
- Reporting of data on demand or event to the SGSN server
- Provision of Content of Communications (Lawful Interception)
- Iu release procedure support (packet buffering, indication to SGSN server)
- etc.
The SGSN server controls the PS-MGW through the Mp interface and the GGSN through the Gn interface by means of GTP-C messages. GTP-U packets are transferred between the PS-MGW and the GGSN over the Gn interface, and between the PS-MGW and the RNC over the Iu interface, following the GTP-U specification.
The SGSN server supports only the Iu interface. When the Gb interface has to be supported (GSM/GERAN access), a 2G-SGSN is required. It is then an implementation/operator option whether both Gb and Iu interfaces are supported in the same physical node, by combining the SGSN server and 2G-SGSN, or whether the Gb interface is supported exclusively through a 2G-SGSN. For a 2G-SGSN the Gn interface supports both user and control data.
The functional impacts of the decomposition into an SGSN server and PS-MGW are confined to the SGSN itself and hence neither RNCs, GGSNs or other SGSNs, nor the protocols used between these nodes are impacted. Besides the Mp interface between SGSN server and PS-MGW, no other interfaces are impacted by this proposal. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2 Logical Architecture | The logical architecture for this approach, as an evolution of the reference logical architecture, is depicted in figure 2.
Figure 2: Evolved logical architecture with SGSN server and PS-MGW
NOTE: Putting SGSN server and 2G-SGSN in the same node is an implementation option. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.1 Functional Nodes | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.1.1 SGSN Server | The SGSN server is the main control node for GPRS. It handles all the signalling interfaces of an SGSN, including the GTP-C protocol on the Gn and Gp interfaces and the RANAP protocol on the Iu interface. The SGSN server controls the PS Media Gateway (PS-MGW) through the Mp interface. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.1.2 2G-SGSN | This evolved architecture has no impact on the 2G-SGSN. A 2G-SGSN is necessary to support the Gb interface. The Gn interface of a 2G-SGSN supports both user and control data. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.1.3 PS Media Gateway (PS-MGW) | The PS-MGW handles the user plane for GPRS. It terminates the GTP-U tunnels towards the GGSN over the Gn and Gp interfaces and towards the RNC over the Iu interface.
The relation between the SGSN server and the PS-MGW represents the architectural association between a master and a slave, respectively. Therefore, this association implies that the Mp interface is a master-slave interface. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.2 Interfaces | Only interfaces for which some clarification is felt useful are mentioned in this section. Interfaces that are not described here conform to their definition in the relevant specifications.
The protocols GTP-U, GTP-C, RANAP and BSSGP referred to in the following subclauses conform to their current specifications and are not impacted by the decomposition of the SGSN. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.2.1 SGSN server – PS-MGW (Mp) (Iu Mode Only) | The PS-MGW is controlled by the SGSN server through the Mp interface. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.2.2 UTRAN – SGSN server (Iu) (Iu Mode Only) | The Iu interface between the RNC and the SGSN server supports the RANAP protocol. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.2.3 UTRAN – PS-MGW (Iu) (Iu Mode Only) | The Iu interface between the RNC and the PS-MGW supports the GTP-U protocol. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.2.4 BSS – 2G-SGSN (Gb) (Gb Mode Only) | The Gb interface between the BSS and the 2G-SGSN supports the BSSGP protocol. This interface belongs to both to the user and control planes. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.2.5 2G-SGSN/SGSN server – GGSN (Gn, Gp) | In Iu mode, the Gn interface between the SGSN server and the GGSN supports the GTP-C protocol.
In Gb mode, the interface between the 2G-SGSN and the GGSN supports the GTP-C protocol in the control plane and the GTP-U protocol in the user plane.
The Gp interface provides the same functionality as the Gn interface, except that it applies only when the 2G-SGSN/SGSN server and the GGSN belong to different PLMNs. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.2.6 PS-MGW – GGSN (Gn) (Iu Mode Only) | The Gn interface between the PS-MGW and the GGSN supports the GTP-U protocol. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.2.7 Gn interface for inter SGSN procedures | At inter SGSN intersystem change (UMTS to/from GSM):
- the Gn interface between the SGSN server and the 2G-SGSN supports the GTP-C protocol.
- the Gn interface between the 2G-SGSN and the PS-MGW controlled by the peer SGSN server supports the GTP-U protocol.
When the MS moves between GSM cells served by two different 2G-SGSNs:
- the Gn interface between 2G-SGSNs supports both the GTP-C and GTP-U protocols.
When the MS moves between UMTS cells served by two different SGSN servers:
- the Gn interface between SGSN servers supports the GTP-C protocol. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.2.3 User plane | The protocol stack for the user plane is shown in figure 3.
Figure 3: User plane protocol stack |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3 H.248 option over Mp | NOTE: Two options are considered in this TR as to the protocol to use over the Mp interface; H.248 with extensions and GTP-C with extensions. Both options are described for comparison purposes, however only one of them shall eventually be retained. The protocol selection might be deferred to the stage 3 work. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.1 Mobility Management (H.248 option) | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.1.1 Detach Procedures | The detach procedure can be initiated by the MS, by the SGSN and by the HLR. The latter two sequences are omitted in this description as they are similar to the first sequence, and they do not add any complexity to the detach sequences.
Figure 4: MS-Initiated Combined PS/CS Detach Procedure
1) The MS detaches by sending Detach Request to the SGSN server. Switch Off indicates whether the detach is due to a switch off situation or not.
2) If GPRS detach, the active PDP contexts in the GGSNs regarding this particular MS are deactivated by the SGSN server sending Delete PDP Context Request (TEID) to the GGSNs. The GGSNs acknowledge with Delete PDP Context Response (TEID).
3) If there are active PDP contexts, the SGSN server sends the “SUBTRACT Request” message to remove the corresponding GTP tunnel end points in the PS-MGW. When the PS-MGW has done this, it returns the “SUBTRACT Response” message to the SGSN server.
4) If IMSI detach, the SGSN server sends an IMSI Detach Indication (IMSI) message to the VLR.
5) If the MS wants to remain IMSI-attached and is doing a GPRS detach, the SGSN server sends a GPRS Detach Indication (IMSI) message to the VLR.
6) If Switch Off indicates that the detach is not due to a switch off situation, the SGSN server sends a Detach Accept to the MS.
7) If there were active PDP contexts, the corresponding RABs are released.
8) If the MS was GPRS detached, then the SGSN server releases the PS signalling connection. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.1.2 Routing Area Update Procedure | The Iu connection is not active in the RA update procedure shown here. If the MS is in PMM-connected state, the SRNS relocation procedure would take place. After a SRNS relocation procedure is performed, a simplified RA update procedure would take place.
Figure 5: UMTS RA Update Procedure
1) The MS sends a Routeing Area Update Request message to the new SGSN server.
2) If the RA update is an Inter-SGSN Routeing area update and if the MS was in PMM‑IDLE state, the new SGSN server sends SGSN Context Request message to the old SGSN server to get the MM and PDP contexts for the MS. The old SGSN server responds with a SGSN Context Response message. The old SGSN server starts a timer.
3) Security functions may be executed.
4) If the RA update is an Inter-SGSN RA Update and if the MS was in PMM‑IDLE state, the new SGSN server selects a PS-MGW and sends the “ADD Request” message to the new PS-MGW to order setup of two GTP tunnel end points for every PDP context existing for the MS. The GTP tunnel end points are one towards UTRAN, and one towards the GGSN. The QoS attributes and the Allocation/Retention Priority parameter are included in the request.
The new PS-MGW returns the “ADD Response” message to the new SGSN server with the TEID(s) and the IP address(es) which UTRAN and GGSN shall use when sending GTP-U packets towards the new PS-MGW, for every PDP context existing for the MS.
[Note: see the note on QoS handling in the subclause “PDP Context Activation Procedure”.]
5) Context Acknowledge message to the old SGSN server.
6) If the RA update is an Inter-SGSN RA Update and if the MS was in PMM‑IDLE state, the new SGSN server sends an Update PDP Context Request to each of the GGSNs concerned. Included are the TEIDs and the IP addresses the GGSN(s) requires for communicating with the SGSN server and the PS-MGW. The GGSNs update their PDP context fields and return an Update PDP Context Response message, which includes the TEIDs and the IP addresses the SGSN server and the PS-MGW requires for communicating with the GGSN.
7) If the RA update is an Inter-SGSN RA Update and if the MS was in PMM‑IDLE state, the new SGSN server sends the “MODIFY Request” message to the new PS-MGW. The TEIDs and the IP Addresses given are the one the new PS-MGW shall use when sending GTP-U packets towards the GGSN(s), and this is given for all the PDP contexts which are setup for the MS.
The PS-MGW returns the “MODIFY Response” message.
8) If the RA update is an Inter-SGSN RA Update, the new SGSN server informs the HLR of the change of SGSN server by sending Update Location to the HLR.
9) If the RA update is an Inter-SGSN RA Update, the HLR sends Cancel Location to the old SGSN server. If the timer described in step 2 is not running, then the old SGSN server removes the MM context. Otherwise, the contexts are removed only when the timer expires. The old SGSN server acknowledges with Cancel Location Ack.
10) If the RA update is an Inter-SGSN RA Update and if the MS was in PMM‑IDLE state, the old SGSN server sends the “SUBTRACT Request” message to remove the GTP tunnel end points in the old PS-MGW.
The PS-MGW returns the “SUBTRACT Response” message.
The rest of the procedure is performed as described in TS 23.060. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.1.3 Serving SRNS Relocation Procedure | Figure 6: Serving SRNS Relocation procedure
1) The source SRNC decides to perform/initiate a SRNS relocation.
2) The source SRNC initiates the relocation preparation procedure by sending a Relocation Required message to the old SGSN server.
3) The old SGSN server determines from Target ID if the SRNS Relocation is intra SGSN SRNS relocation or inter SGSN SRNS relocation. In case of inter SGSN SRNS relocation the old SGSN server initiates the relocation resource allocation procedure by sending a Forward Relocation Request message to the new SGSN server. At the same time a timer is started on the MM and PDP contexts in the old SGSN server.
4) The new SGSN server selects a PS-MGW and sends the “ADD Request” message to the new PS-MGW to order setup of two GTP tunnel end points (one on the Iu interface and one on the Gn interface) for every PDP context that exists for the MS. The QoS attributes and the Allocation/Retention Priority parameter are included in the request.
The new PS-MGW returns the “ADD Response” message to the new SGSN server with the TEIDs and the IP Addresses that the RNC and the GGSNs shall use when sending GTP-U packets towards the new PS-MGW.
[Note: see the note on QoS handling in the subclause “PDP Context Activation Procedure”.]
5) The new SGSN server sends a Relocation Request message to the target RNC. The new SGSN server passes the TEID(s) and the IP address(es) required at the target RNC for communicating with the new PS-MGW. Also, the SGSN server receives in the Relocation Request Acknowledge message the TEID(s) and the IP address(es) required at the PS-MGW to communicate with the target RNC.
6) When resources for the transmission of user data between the target RNC and the new PS-MGW has been allocated and the new SGSN server is ready for relocation of SRNS, the Forward Relocation Response message is sent from the new SGSN server to the old SGSN server. This message indicates that the target RNC is ready to receive from source SRNC the downstream packets not yet acknowledged by MS.
The Forward Relocation Response message is applicable only in case of inter SGSN SRNS relocation.
7) The old SGSN server continues the relocation of SRNS by sending a Relocation Command message to the source SRNC.
8) Upon reception of the Relocation Command message from the PS domain, the source RNC shall start the data-forwarding timer. When the relocation preparation procedure is terminated successfully and when the source SRNC is ready, the source SRNC shall trigger the execution of relocation of SRNS by sending a Relocation Commit message (SRNS Contexts) to the target RNC. The purpose of this procedure is to transfer SRNS contexts from the source RNC to the target RNC.
9) After having sent the Relocation Commit message, the source SRNC begins the forwarding of data for the RABs to be subject for data forwarding. The data forwarding at SRNS relocation shall be carried out through the Iu interface, meaning that the data exchanged between the source SRNC and the target RNC are duplicated in the source SRNC and routed at IP layer towards the target RNC.
10) The target RNC shall send a Relocation Detect message to the new SGSN server when the relocation execution trigger is received. When the Relocation Detect message is sent, the target RNC shall start SRNC operation.
11) After having sent the Relocation Detect message, target SRNC responds to the MS by sending a RNTI Reallocation message.
12) Upon reception of Relocation Detect message, CN may switch the user plane from the source RNC to the target SRNC. If the SRNS Relocation is an inter SGSN SRNS relocation, the new SGSN server sends Update PDP Context Request messages to the GGSNs concerned, with the TEIDs and the IP addresses required at the GGSNs for communicating with the SGSN server and the PS-MGW. The GGSNs update their PDP context fields and return an Update PDP Context Response with the TEIDs and the IP addresses required at the SGSN server and the PS-MGW for communicating with the GGSN.
14) The new SGSN server sends the “MODIFY Request” message to the new PS-MGW with the TEIDs and the IP Addresses that the new PS-MGW requires for communicating with the target RNC and the GGSNs. This is given for all the PDP contexts that are setup for the MS.
The PS-MGW returns the “MODIFY Response” message.
15) When the MS has reconfigured itself, it sends the RNTI Reallocation Complete message to the target SRNC.
From now on the exchange of packets with the MS can start.
16) When the target SRNC receives the RNTI Reallocation Complete message, the target SRNC shall initiate the Relocation Complete procedure by sending the Relocation Complete message to the new SGSN server.
If the SRNS Relocation is an inter SGSN SRNS relocation, the new SGSN server signals to the old SGSN server the completion of the SRNS relocation procedure by sending a Forward Relocation Complete message.
17) The old SGSN server sends an Iu Release Command message to the source RNC. When the RNC data-forwarding timer has expired the source RNC responds with an Iu Release Complete.
18) Upon receiving the Forward Relocation Complete message, the old SGSN server sends the “SUBTRACT Request” message to remove the GTP tunnel end points in the old PS-MGW.
The PS-MGW returns the “SUBTRACT Response” message.
19) After the MS has finished RNTI reallocation procedure and if the new Routing Area Identification is different from the old one, the MS initiates the Routing Area Update procedure.
C1) CAMEL-GPRS-SGSN-Context-Acknowledge.
C2) CAMEL-GPRS-Routing-Area-Update. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.1.4 UMTS to GSM Intra SGSN Change | Figure 7: UMTS to GSM Intra SGSN Change
1) The MS or BSS or UTRAN decides to perform an intersystem change, which makes the MS switch to a new cell that supports GSM radio technology, and stops transmission to the network.
2) The MS sends a Routeing Area Update Request message to the 2G‑SGSN+SGSN server.
3) The 2G‑SGSN+SGSN server sends an SRNS Context Request message to the SRNS.
4) Upon reception of this message the SRNS buffers and stops sending downlink PDUs to the MS and returns an SRNS Context Response message.
5) Security functions may be executed.
6) The 2G-SGSN+SGSN server sends the “MODIFY Request” message to the old PS-MGW to modify the TEID(s) and the IP address(es) earlier pointing to the GGSN(s) into now pointing to the new 2G-SGSN+SGSN server for every PDP context existing for the MS. For each active PDP context using acknowledged mode, an indicator is included to tell the PS-MGW that the eight most significant bits of the PDCP sequence numbers accompanying the received G-PDUs must be stripped off. This enables the old PS-MGW to forward packets to the 2G-SGSN+SGSN server in the appropriate format.
The old PS-MGW returns the “MODIFY Response” message.
7) If the MS is PMM‑CONNECTED the 2G-SGSN+SGSN server sends an SRNS Data Forward Command message to the SRNS with the TEID(s) and IP address(es) required at the SRNS for packet forwarding to the old PS-MGW. Upon reception of SRNS Data Forward Command message from the 2G-SGSN+SGSN server, the SRNS shall start the data-forwarding timer.
8) The SRNS shall start tunnelling the partly transmitted and the transmitted but not acknowledged PDCP‑PDUs and start duplicating and tunnelling the buffered GTP PDUs to the old PS-MGW.
9) The old PS-MGW tunnels the G-PDUs to the 2G‑SGSN+SGSN server. For each active PDP context using acknowledged mode, the PS-MGW must strip off the eight most significant bits of the PDCP sequence numbers.
10) The 2G‑SGSN+SGSN server sends an Update PDP Context Request message to each GGSN concerned with the TEIDs and the IP addresses required at the GGSNs for communication towards the 2G-SGSN+SGSN server. Each GGSN updates its PDP context fields and returns an Update PDP Context Response message.
11) When the MS is PMM‑CONNECTED the 2G-SGSN+SGSN server sends an Iu Release Command message to the SRNS. When the RNC data-forwarding timer has expired, the SRNS responds with an Iu Release Complete message.
12) The 2G-SGSN+SGSN server sends the “SUBTRACT Request” message to remove the GTP tunnel end points in the old PS-MGW.
The PS-MGW returns the “SUBTRACT Response” message.
The rest of the procedure is performed as described in TS 23.060.
[Note: the PS-MGW may be implemented with the SGSN server in a combined node, and in this case the signalling towards the PS-MGW and the GGSN may be omitted.] |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.1.5 GSM to UMTS Intra SGSN Change | Figure 8: GSM to UMTS Intra SGSN Change
1) The MS or BSS or UTRAN decides to perform an intersystem change, which makes the MS switch to a new cell that supports UMTS radio technology, and stops transmission to the network.
2) The MS sends a Routeing Area Update Request message to the 2G-SGSN+SGSNserver. The 2G-SGSN+SGSN server starts a timer and stops the transmission of N-PDUs to the MS.
3) Security functions may be executed.
4) The 2G-SGSN+SGSN server selects a PS-MGW and sends the “ADD Request” message to the new PS-MGW to order setup of two GTP tunnel end points for every PDP context existing for the MS. The GTP tunnel end points are one towards UTRAN, and a common one towards the GGSN and towards the 2G-SGSN+SGSN server. The QoS attributes and the Allocation/Retention Priority parameter are included in the request.
The new PS-MGW returns the “ADD Response” message to the 2G-SGSN +SGSN server with the TEID(s) and the IP address(es) which UTRAN, the 2G-SGSN+SGSN server and the GGSN shall use when sending G-PDUs towards the new PS-MGW, for every PDP context existing for the MS.
[Note: see the note on QoS handling in the subclause “PDP Context Activation Procedure”.]
5) The 2G-SGSN+SGSN server duplicates the buffered G‑PDUs and starts tunnelling them to the new PS-MGW. No G-PDUs shall be forwarded to the new PS-MGW after expiry of the timer described in step 2.
6) The 2G-SGSN+SGSN server sends an Update PDP Context Request message to each GGSN concerned with the TEIDs and the IP addresses required at the GGSNs for communication towards the 2G-SGSN+SGSN server and the PS-MGW. Each GGSN updates its PDP context fields and return an Update PDP Context Response message with the TEIDs and the IP addresses required at the 2G-SGSN+SGSN server and the PS-MGW for communication towards the GGSN.
7) to 12) As described in TS 23.060.
13) The MS sends a Service Request message to the 2G-SGSN+SGSN server with the Service Type indicating Data or Signalling.
14) The 2G-SGSN+SGSN server requests the SRNS to establish a radio access bearer by sending a RAB Assignment Request message to the SRNS. Included are the TEID(s) and the IP address(es) which the SRNS requires to communicate with the new PS-MGW. The SRNS sends a Radio Bearer Setup Request message to the MS. The MS responds with a Radio Bearer Setup Complete message.The SRNS responds with a RAB Assignment Response message with the TEID(s) and the IP address(es) required at the PS-MGW for communicating with the SRNS.
15) The 2G-SGSN+SGSN server sends the “MODIFY Request” message to the new PS-MGW. The TEIDs and the IP Addresses given are the one the new PS-MGW must use when sending G-PDUs towards UTRAN and the GGSN(s), and this is given for all the PDP contexts which are setup for the MS.
The PS-MGW returns the “MODIFY Response” message.
16) Traffic flow is resumed between the PS-MGW and the SRNS. The SRNS shall discard all G‑PDUs with PDCP‑PDU sequence numbers older than the downlink PDCP‑PDU sequence number received from the MS. Other G‑PDUs shall be transmitted to the MS. The MS shall discard all PDCP‑PDUs with sequence numbers older than the GTP‑SNU received from the SRNS. If this is not the case, the PDCP‑PDUs shall be transmitted to the SRNS.
17) The traffic flow is resumed between the SRNS and the MS.
[Note, the PS-MGW may be implemented with the SGSN server in a combined node, and in this case the signalling towards the PS-MGW and the GGSN may be omitted.] |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.1.6 UMTS to GSM Inter SGSN Change | Figure 9: UMTS to GSM Inter SGSN Change
1) The MS or BSS or UTRAN decides to perform an intersystem change, which makes the MS switch to a new cell that supports GSM radio technology, and stops transmission to the network.
2) The MS sends a Routeing Area Update Request message to the new 2G‑SGSN.
3) The new 2G‑SGSN sends an SGSN Context Request message to the old SGSN server to get the MM and PDP contexts for the MS. The old SGSN server starts a timer.
4) If the MS is PMM‑CONNECTED, the old SGSN server sends an SRNS Context Request message to the SRNS. Upon reception of this message the SRNS buffers and stops sending downlink PDUs to the MS and returns an SRNS Context Response message.
5) The old SGSN server responds with an SGSN Context Response message.
6) Security functions may be executed.
7) The new 2G‑SGSN sends an SGSN Context Acknowledge message to the old SGSN server with the TEID(s) and the IP address required at the old PS-MGW for packet forwarding. This informs the old SGSN server that the new 2G‑SGSN is ready to receive data packets belonging to the activated PDP contexts.
8) The old SGSN server sends the “MODIFY Request” message to the old PS-MGW to modify the TEID(s) and the IP address(es) earlier pointing to the GGSN(s) into now pointing to the new 2G-SGSN for every PDP context existing for the MS. For each active PDP context using acknowledged mode, an indicator is included to tell the PS-MGW that the eight most significant bits of the PDCP sequence numbers accompanying the received G-PDUs must be stripped off, thus converting them to SNDCP sequence numbers. This enables the old PS-MGW to forward packets to the new 2G-SGSN in the appropriate format.
The old PS-MGW returns the “MODIFY Response” message.
9) If the MS is PMM‑CONNECTED the old SGSN server sends an SRNS Data Forward Command message to the SRNS with the TEID(s) and IP address(es) required at the SRNS for packet forwarding to the old PS-MGW. The SRNS shall start tunnelling the partly transmitted and the transmitted but not acknowledged PDCP‑PDUs and start duplicating and tunnelling the buffered GTP PDUs to the old PS-MGW. Upon reception of SRNS Data Forward Command message from the SGSN server, the SRNS shall start the data-forwarding timer.
10) The old PS-MGW tunnels the G-PDUs to the new 2G‑SGSN. For each active PDP context using acknowledged mode, the PS-MGW must strip off the eight most significant bits of the PDCP sequence numbers accompanying the received G-PDUs.
11) The new 2G‑SGSN sends an Update PDP Context Request message to each GGSN concerned. Each GGSN updates its PDP context fields and returns an Update PDP Context Response message.
12) The new 2G‑SGSN informs the HLR of the change of SGSN by sending an Update GPRS Location message to the HLR.
13) The HLR sends a Cancel Location message to the old SGSN server. The old SGSN server acknowledges with a Cancel Location Ack message. The old SGSN server removes the MM and PDP contexts if the timer described in step 3 is not running. If the timer is running, then the MM and PDP context shall be removed when the timer expires.
14) When the MS is PMM‑CONNECTED the old SGSN server sends an Iu Release Command message to the SRNS. When the RNC data-forwarding timer has expired the SRNS responds with an Iu Release Complete message.
15) The old SGSN server sends the “SUBTRACT Request” message to remove the GTP tunnel end points in the old PS-MGW.
The PS-MGW returns the “SUBTRACT Response” message.
The rest of the procedure is performed as described in TS 23.060. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.1.7 GSM to UMTS Inter SGSN Change | Figure 10: GSM to UMTS Inter SGSN Change
1) The MS or BSS or UTRAN decides to perform an intersystem change, which makes the MS switch to a new cell that supports UMTS radio technology, and stops transmission to the network.
2) The MS sends a Routeing Area Update Request message to the new SGSN server.
3) The new SGSN server sends an SGSN Context Request message to the 2G‑SGSN to get the MM and PDP contexts for the MS. The old 2G-SGSN starts a timer and stops the transmission of N-PDUs to the MS.
4) The old 2G‑SGSN responds with an SGSN Context Response message.
5) Security functions may be executed.
6) The new SGSN server selects a PS-MGW and sends the “ADD Request” message to the new PS-MGW to order setup of two GTP tunnel end points for every PDP context existing for the MS. The GTP tunnel end points are one towards UTRAN, and a common one towards the GGSN and towards the old 2G-SGSN. The QoS attributes and the Allocation/Retention Priority parameter are included in the request.
The new PS-MGW returns the “ADD Response” message to the new SGSN server with the TEID(s) and the IP address(es) which UTRAN, old 2G-SGSN and GGSN shall use when sending G-PDUs towards the new PS-MGW, for every PDP context existing for the MS.
[Note: see the note on QoS handling in the subclause “PDP Context Activation Procedure”.]
7) The new SGSN server sends an SGSN Context Acknowledge message to the old 2G‑SGSN. This informs the old 2G‑SGSN that the new PS-MGW is ready to receive data packets belonging to the activated PDP contexts. Included are the TEID(s) and the IP address that the old 2G-SGSN requires to forward packets to the new PS-MGW.
8) The old 2G‑SGSN duplicates the buffered G‑PDUs and starts tunnelling them to the new PS-MGW. No G-PDUs shall be forwarded to the new PS-MGW after expiry of the timer described in step 3.
9) The new SGSN server sends an Update PDP Context Request message to each GGSN concerned with the TEIDs and the IP addresses required at the GGSNs for communication towards the new SGSN server and the PS-MGW. Each GGSN updates its PDP context fields and return an Update PDP Context Response message with the TEIDs and the IP addresses required at the new SGSN server and the PS-MGW for communication towards the GGSN.
10) to 19) As described in TS 23.060.
20) If the MS was in GPRS MM state READY, it sends a Service Request message to the new SGSN server.
21) If the MS has sent the Service Request the new SGSN server requests the SRNS to establish a radio access bearer by sending a RAB Assignment Request message to the SRNS. Included are the TEID(s) and the IP address(es) which the SRNS requires to communicate with the new PS-MGW. The SRNS responds with a RAB Assignment Response message with the TEID(s) and IP address(es) required at the PS-MGW for communicating with the SRNS.
22) The new SGSN server sends the “MODIFY Request” message to the new PS-MGW. The TEIDs and the IP Addresses given are the one the new PS-MGW shall use when sending G-PDUs towards UTRAN and GGSN(s), and this is given for all the PDP contexts which are setup for the MS.
The PS-MGW returns the “MODIFY Response” message. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.2 Session Management (H.248 option) | |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.2.1 PDP Context Activation Procedure | Figure 11: PDP Context Activation Procedure for UMTS
1) The MS sends an Activate PDP Context Request (NSAPI, TI, PDP Type, PDP Address, Access Point Name, QoS Requested, PDP Configuration Options) message to the SGSN server.
2) The SGSN server validates the Activate PDP context request message. The SGSN server may restrict the requested QoS attributes, given the subscribed QoS profile. If the SGSN server determines that the PDP context activation can be completed, the SGSN server selects a PS-MGW and sends the “ADD Request” message to the PS-MGW to order it to setup two GTP tunnel end points (one on the Iu interface and one on the Gn interface). The (possibly restricted) QoS attributes and the Allocation/Retention priority parameter are included in the “ADD Request” message so that the MGW can handle the different sessions accordingly.
The PS-MGW returns the “ADD Response” message with the TEIDs and the IP addresses for the GTP tunnel end points to be used at the RNC and the GGSN when these send GTP-U packets towards the PS-MGW.
[Note: With H.248 the PS-MGW cannot select a different QoS than proposed by the SGSN server. H.248 allows the SGSN server to send a prioritised list of QoS values, either discrete values or between a minimum and a maximum. The PS-MGW will then return the chosen value in the response to the SGSN server. If the PS-MGW cannot support any of the indicated values, a negative response is returned to the SGSN server.
Note that this QoS handling is similar to the QoS handling in the RANAP protocol. Currently, the RNC can only accept or reject the QoS value indicated by the SGSN server. There is an ongoing discussion to extend this functionality. E.g. that the SGSN server can relay to the RNC several proposed values indicated by the MS. The RNC could then choose the value it can support. This handling is currently possible to support by H.248. It is proposed to choose the same QoS handling mechanism over the Mp interface as will eventually be standardised in RANAP].
3) In UMTS, RAB setup is done by the RAB Assignment procedure. The TEID and the IP address which UTRAN requires for communication towards the PS-MGW, and vice versa, are handled in this procedure.
4) If trace is activated, then the SGSN server shall send an Invoke Trace message to the UTRAN.
5) The SGSN server sends a Create PDP Context Request message to the affected GGSN with the TEIDs and the IP addresses that the GGSN requires for communication towards the SGSN server and the PS-MGW.
The GGSN then returns a Create PDP Context Response message to the SGSN server with the TEIDs and the IP addresses that the SGSN server and the PS-MGW require for communication towards the GGSN. The GGSN may further restrict the QoS negotiated returned in the response message.
6) The SGSN server sends the “MODIFY Request” message to the PS-MGW with the TEIDs and the IP addresses that the PS-MGW requires for communication towards the RNC and the GGSN. Also the GTP version negotiated in the control plane layer is sent in this message.
If a new negotiated value of the QoS attributes is received from the GGSN, this value is transferred to the PS-MGW in the “MODIFY Request” message.
The PS-MGW returns the “MODIFY Response” message.
7) The SGSN server returns an Activate PDP Context Accept (PDP Address, Packet Flow Id) message to the MS. The SGSN server is now able to route PDP PDUs between the GGSN and the MS, and charging can be started.
C1) CAMEL-GPRS-Activate-PDP-Context.
C2) CAMEL-GPRS-SGSN-Create-PDP-Context. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.2.2 Secondary PDP Context Activation Procedure | The Secondary PDP Context Activation procedure may be used to activate a PDP context while reusing the PDP address and other PDP context information from an already active PDP context.
Figure 12: Secondary PDP Context Activation Procedure for UMTS
1) The MS sends an Activate Secondary PDP Context Request (Linked TI, NSAPI, TI, QoS Requested, TFT) message to the SGSN server. Linked TI indicates the TI value assigned to any one of the already activated PDP contexts for this PDP address and APN.
2) The SGSN server validates the Activate Secondary PDP context request message. The SGSN server may restrict the requested QoS attributes, given the subscribed QoS profile. If the SGSN server determines that the PDP context activation can be completed, the SGSN server selects a PS-MGW and sends the “ADD/MODIFY Request” message to the PS-MGW to order it to setup two GTP tunnel end points (one on the Iu interface and one on the Gn interface). The (possibly restricted) QoS attributes and the Allocation/Retention priority parameter are included in the “ADD/MODIFY Request” message so that the MGW can handle the different sessions accordingly.
The PS-MGW returns the “ADD/MODIFY Response” message with the TEIDs and the IP addresses for the GTP tunnel end points to be used at the RNC and the GGSN when these send GTP-U packets towards the PS-MGW.
If each of the GTP tunnel end points for every PDP context are set up in a separate H.248 Termination, the “ADD” command is used in this step. If the GTP tunnel end points on the same interface (Iu or Gn) are set up in the same H.248 Termination for all the PDP contexts sharing a given PDP address and APN, then the “MODIFY” command is used in this step.
[Note: see the note on QoS handling in the subclause “PDP Context Activation Procedure”.]
3) In UMTS, RAB setup is done by the RAB Assignment procedure. The TEID and the IP address which UTRAN requires for communication towards the PS-MGW, and vice versa, are handled in this procedure.
4) The SGSN server sends a Create PDP Context Request message to the affected GGSN with the TEIDs and the IP addresses that the GGSN requires for communication towards the SGSN server and the PS-MGW.
The GGSN then returns a Create PDP Context Response message to the SGSN server with the TEIDs and the IP addresses that the SGSN server and the PS-MGW require for communication towards the GGSN. The GGSN may further restrict the QoS negotiated returned in the response message.
5) The SGSN server sends the “MODIFY Request” message to the PS-MGW with the TEIDs and the IP addresses that the PS-MGW requires for communication towards the RNC and the GGSN. Also the GTP version negotiated in the control plane layer is sent in this message.
If a new negotiated value of the QoS attributes is received from the GGSN, this value is transferred to the PS-MGW in the “MODIFY Request” message.
The PS-MGW returns the “MODIFY Response” message.
6) The SGSN server returns an Activate Secondary PDP Context Accept message to the MS. The SGSN server is now able to route PDP PDUs between the GGSN and the MS.
C1) CAMEL-GPRS-Activate-PDP-Context.
C2) CAMEL-GPRS-SGSN-Create-PDP-Context. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.2.3 Network-Requested PDP Context Activation Procedure | The Network-Requested PDP Context Activation procedure allows the GGSN to initiate the activation of a PDP context. This procedure is a request in the control plane towards the MS to initiate a PDP Context Activation procedure. The PDP Context Activation procedure itself is performed as shown above in Section . Therefore the Network-Requested PDP Context Activation procedure does not add any new sequences for the split of the SGSN (into an SGSN server and a PS-MGW).
Note that push services will require some attention. Push services are not yet standardised, but there might be a need for the SGSN server to ask the PS-MGW for its capability of handling the push service before the SGSN server requests the MS to initiate the activation of a PDP context. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.2.4 PDP Context Modification Procedures | The following parameters can be modified in a PDP context modification procedure:
- QoS Negotiated;
- Radio Priority;
- Packet Flow Id;
- PDP Address (in case of the GGSN-initiated modification procedure); and
- TFT (in case of MS-initiated modification procedure).
Of these parameters, only the modification of the QoS Negotiated affects the PS-MGW.
The modification procedure can be initiated by:
- the SGSN;
- the GGSN;
- the MS; or
- the RNC
Since the principle of modifying the QoS attributes in the PS-MGW is the same for all these cases, only one of them is shown – the MS initiated PDP context modification. As a downgrade of the QoS attributes is a simplified case of the upgrade modification procedure, the latter case is described.
Figure 13: MS-Initiated PDP Context Modification Procedure for UMTS
1) The MS sends a Modify PDP Context Request (TI, QoS Requested, TFT) message to the SGSN server.
2) The SGSN server may restrict the requested QoS attributes, given the subscribed QoS profile. The SGSN server sends the “MODIFY Request” message to the PS-MGW. This message includes the (possibly restricted) QoS attributes.
The PS-MGW returns the “MODIFY Response” message.
[Note: see the note on QoS handling in the subclause “PDP Context Activation Procedure”.]
3) The SGSN server sends an Update PDP Context Request (TEID, NSAPI, QoS Negotiated, TFT) message to the GGSN. The GGSN may further restrict QoS Negotiated given its capabilities and the current load, and returns an Update PDP Context Response (TEID, QoS Negotiated) message.
If QoS Negotiated and/or TFT received from the SGSN is incompatible with the PDP context being modified (e.g., TFT contains inconsistent packet filters), then the GGSN rejects the Update PDP Context Request.
4) In UMTS, radio access bearer modification may be performed by the RAB Assignment procedure.
5) In case the QoS now is different than the value previously indicated to the PS-MGW, the new value is sent from the SGSN server to the PS-MGW in the “MODIFY Request” message.
The PS-MGW returns the “MODIFY Response” message.
6) The SGSN server selects Radio Priority and Packet Flow Id based on QoS Negotiated, and returns a Modify PDP Context Accept (TI, QoS Negotiated, Radio Priority, Packet Flow Id) message to the MS.
NOTE: If the SGSN server or the PS-MGW do not accept QoS Requested, then steps 2 and 3 of this procedure are skipped, and the existing QoS Negotiated is returned to the MS in step 4.
C1) CAMEL-GPRS-Modify-PDP-Context. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.2.5 PDP Context Deactivation Procedure | PDP context deactivation can be initiated by the MS, by the SGSN and by the GGSN. The latter two sequences are omitted in this description as they are similar to the first sequence, and they do not add any complexity to the deactivation sequences.
Figure 14: PDP Context Deactivation Initiated by MS Procedure for UMTS
1) The MS sends a Deactivate PDP Context Request (TI, Teardown Ind) message to the SGSN server.
2) The SGSN server sends a Delete PDP Context Request (TED, NSAPI, Teardown Ind) message to the GGSN. If Teardown Ind was included by the MS in the Deactivate PDP Context Request message, then the SGSN server deactivates all PDP contexts associated with this PDP address by including Teardown Ind in the Delete PDP Context Request message. The GGSN removes the PDP context(s) and returns a Delete PDP Context Response (TEID) message to the SGSN server.
3) The SGSN server sends the “SUBTRACT/MODIFY Request” message to remove the corresponding GTP tunnel end points in the PS-MGW. When the PS-MGW has done this, it returns the “SUBTRACT/MODIFY Response” message to the SGSN server.
If each of the GTP tunnel end points for every PDP context are set up in a separate H.248 Termination, the “SUBTRACT” command is used in this step. If the GTP tunnel end points on the same interface (Iu or Gn) are set up in the same H.248 Termination for all the PDP contexts sharing a given PDP address and APN, then the “MODIFY” command is used in this step, unless the Teardown Ind was included in the Delete PDP Context Request message. If the Teardown Ind was included, the “SUBTRACT” command is used.
4) The SGSN server returns a Deactivate PDP Context Accept (TI) message to the MS.
5) The radio access bearer release is done by the RAB Assignment procedure.
C1) CAMEL-GPRS-Deactivate-PDP-Context |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.2.6 Iu Release Procedure | Figure 15: Iu Release Procedure
1) The RNC sends an Iu Release Request message to the SGSN server.
2) The SGSN server sends the “MODIFY Request” message to the PS-MGW to remove the TEID(s) and the IP address(es) that the PS-MGW requires for communication towards the RNC. The maximum bit rate is included in this message to downgrade it to 0 kbit/s for both uplink and downlink in the PS-MGW. An Event is set to request the PS-MGW to inform the SGSN server when downlink PDP PDUs again are received from the GGSN. This is done for each of the PDP contexts for the MS.
The PS-MGW returns the “MODIFY Response” message.
3) The SGSN server sends an Iu Release Command message to the RNC.
4) The RRC connection is released if still existing.
5) The RNC confirms the Iu release by sending an Iu Release Complete message to the SGSN server for each released RAB. The GTP SND and the GTP SNU are included to enable the SGSN server to restore the values in case the PDP context is maintained and the RAB is re-established at a later stage. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.2.7 Service Request Initiated by MS Procedure | Figure 16: Service Request Initiated by MS Procedure
1) The MS establishes an RRC connection if none exists for CS traffic.
2) The MS sends a Service Request message to the SGSN server.
If Service Type indicates Data, then a signalling connection is established between the MS and the SGSN server, and resources for active PDP context(s) are allocated, i.e. RAB establishment for the activated PDP context(s).
If Service Type indicates Signalling, then the signalling connection is established between the MS and the SGSN server for sending upper-layer signalling messages.
3) The SGSN server shall perform the security functions if the service request was initiated by an MS in PMM‑IDLE state.
4) In case Service Type indicates Data, the SGSN server sends a Radio Access Bearer Assignment Request message to re-establish radio access bearer for the activated PDP context(s). The TEID and the IP address that the RNC requires for communication towards the PS-MGW, for each of the activated PDP contexts, are included in this message.
5) The RNC indicates to the MS the new Radio Bearer Identity established and the corresponding RAB ID with the RRC radio bearer set up procedure.
6) The SRNC responds with the Radio Access Bearer Assignment Response message. The TEID and the IP address that the PS-MGW requires for communication towards the RNC, for each of the activated PDP context, are included in this message.
7) The SGSN server sends the “MODIFY Request” message to the PS-MGW with the TEID(s) and the IP address(es) that the PS-MGW requires for communication towards the RNC. Also the QoS attributes are included in this message. The Event, which was set to request the PS-MGW to inform the SGSN server when downlink PDP PDUs again are received from the GGSN, is deactivated. This is done for all the active PDP contexts for the MS.
`The PS-MGW returns the “MODIFY Response” message.
`[Note: see the note on QoS handling in the subclause “PDP Context Activation Procedure”.]
8) For each RAB re-established with a modified QoS profile, the SGSN server initiates a PDP Context Modification procedure to inform the MS and the GGSN of the new negotiated QoS profile for the corresponding PDP context.
9) The MS sends the uplink packet. |
997ad2510cb826711e63f644e1d2617f | 23.873 | 6.3.2.8 Service Request Initiated by Network Procedure | Figure 17: Service Request Initiated by Network Procedure
1) The PS-MGW receives a downlink PDP PDU for an MS in PMM‑IDLE state.
2) The PS-MGW sends the “NOTIFY” message to the SGSN server to indicate that the previously set Event (inform upon reception of downlink PDP PDU) is encountered for the PDP context.
3) The SGSN server sends a Paging message to the RNC. The RNC pages the MS by sending a Paging message to the MS.
4) The MS establishes an RRC connection if none exists for CS traffic.
5) The MS sends a Service Request message to the SGSN server. Service Type specifies Paging Response.
6) to 9) Similar to “Service Request Initiated by Network Procedure”.
10) The PS-MGW sends the downlink packet. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.